Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 29341-8-13: UPnP Quality of Service — QoS Device Configuration
Managing and persisting QoS device parameters — configuration architecture, parameter groups, and deployment best practices
ISO/IEC 29341-8-13 defines the QoS Device Configuration service, the component of the UPnP QoS architecture responsible for managing and persisting the configuration parameters of QoS-capable network devices. While the QoS Device v2 service handles real-time packet processing operations, the Device Configuration service provides the management interface for setting device-level parameters such as maximum queue counts, default traffic classes, marking methods, administrative states, and capability reporting. This separation of concerns between operational data plane functions and management plane configuration aligns with standard network management best practices and enables flexible deployment scenarios.
Always back up the current QoS device configuration before making significant policy changes. The QoS Device Configuration service provides a
GetConfiguration action that returns the complete device configuration in a structured XML format for archival purposes.Configuration Service Architecture and Parameters
The QoS Device Configuration service defines a set of configuration parameters that govern the device’s QoS behavior at the system level. These parameters are organized into logical groups: system parameters including administrative state, default traffic class, and maximum number of queues; interface parameters covering per-interface settings such as marking trust mode, default 802.1p priority, and interface speed; queue parameters for each configured queue including depth, scheduling discipline, and drop policy; and capability parameters that report the device’s hardware and software QoS capabilities. Configuration changes take effect immediately by default, but the specification supports a commit model where changes can be staged and applied atomically.
The service exposes actions including SetConfiguration for applying configuration changes, GetConfiguration for retrieving the current configuration, SetDefaultTrafficClass for changing the default classification for unmarked traffic, and ResetConfiguration for reverting to factory defaults. Configuration persistence is implementation-specific — devices may store configuration in non-volatile memory, flash storage, or retrieve it from a network management server on boot. The specification recommends that devices support both local persistence and network-based configuration retrieval for maximum deployment flexibility.
| Parameter Group | Parameter | Type | Description |
|---|---|---|---|
| System | AdminState | Boolean | Enable or disable QoS processing on the device |
| System | MaxQueues | Integer | Maximum number of configurable queues |
| System | DefaultTrafficClass | String | Traffic class assigned to unclassified packets |
| Interface | MarkingTrustMode | Enum | Trusted (preserve) or Untrusted (re-mark) incoming markings |
| Interface | Default8021pPriority | Integer | Default 802.1p priority for untrusted ingress |
| Queue | QueueDepth | Integer | Maximum packets in the queue |
| Queue | SchedulingDiscipline | Enum | SP, WFQ, CBWFQ, LLQ, or FIFO |
| Capability | SupportedTrafficClasses | List | Traffic classes the device can handle |
Configuration changes applied via the QoS Device Config service take effect immediately by default. Schedule configuration changes during maintenance windows to avoid disrupting active QoS reservations and real-time traffic flows.
Engineering Best Practices for Device Configuration
Effective management of QoS device configurations requires a structured approach to change control and version management. The QoS Device Configuration service supports configuration version tracking through the ConfigurationVersion state variable, which increments with each change. Engineers should implement a configuration management workflow that includes pre-change validation — using the ValidateConfiguration action to verify that proposed parameters are within device capabilities — post-change verification by comparing actual device behavior against expected behavior, and automated rollback procedures in case of configuration errors.
A particularly important design consideration is configuration scaling. In networks with many QoS devices, manually configuring each device is impractical. The QoS Device Configuration service is designed to work in conjunction with the QoS Manager, which can push configuration templates to multiple devices simultaneously. A recommended approach is to define configuration profiles for different device roles (edge switch, core router, wireless access point, residential gateway) and deploy role-appropriate configurations using the QoS Manager’s bulk configuration capabilities. This role-based approach ensures consistency across devices of the same type while allowing appropriate variation between different network segments.
The standardized QoS Device Configuration interface ensures interoperability across different UPnP QoS device implementations, allowing network administrators to manage multi-vendor QoS deployments through a unified interface.
Factory resetting a QoS device without first removing its UPnP QoS configuration may leave orphaned policy entries in the QoS Manager’s database. Always use the
ReleaseTrafficQoS and RemoveTrafficRule actions before performing a factory reset on managed devices.Frequently Asked Questions
Q: Are configuration changes applied immediately or do they require a restart?
A: Configuration changes take effect immediately by default. However, the specification supports a staged commit model where changes are validated first, applied atomically, and can be rolled back if validation fails. Certain hardware-dependent parameters (such as changing queue counts) may require a device restart in some implementations.
A: Configuration changes take effect immediately by default. However, the specification supports a staged commit model where changes are validated first, applied atomically, and can be rolled back if validation fails. Certain hardware-dependent parameters (such as changing queue counts) may require a device restart in some implementations.
Q: Can the QoS Device Configuration service be accessed remotely?
A: Yes. As a UPnP service, the QoS Device Configuration service is accessible over the network to any authenticated UPnP control point. The specification recommends implementing access control to restrict configuration changes to authorized QoS Manager instances.
A: Yes. As a UPnP service, the QoS Device Configuration service is accessible over the network to any authenticated UPnP control point. The specification recommends implementing access control to restrict configuration changes to authorized QoS Manager instances.
Q: How does device configuration interact with the QoS Policy system?
A: The QoS Device Configuration service sets the device-level parameters that define how the device processes QoS policies. For example, the
A: The QoS Device Configuration service sets the device-level parameters that define how the device processes QoS policies. For example, the
MaxQueues parameter determines how many distinct traffic classes can be simultaneously active, and the MarkingTrustMode parameter determines whether incoming DSCP/802.1p markings are preserved or reclassified before policy evaluation.Q: Is there a mechanism to detect configuration drift on managed devices?
A: Yes. The QoS Manager can periodically query the
A: Yes. The QoS Manager can periodically query the
ConfigurationVersion state variable on each device and compare it with the expected version. A mismatch indicates that the device configuration has drifted from the desired state, triggering remediation through the SetConfiguration action.
