Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 29341-8-10: UPnP Quality of Service — QoS Manager v2
Exploring the central coordination entity of UPnP QoS — admission control, policy distribution, and resource management
ISO/IEC 29341-8-10 defines the QoS Manager v2 service, the central coordination entity within the UPnP QoS architecture. The QoS Manager acts as the intermediary between applications requesting Quality of Service treatment and the network devices that enforce QoS policies. It receives QoS requests from applications via the UPnP control point interface, translates these requests into appropriate policy configurations, and distributes the configurations to the relevant QoS Device instances across the network. As the brains of the QoS system, the QoS Manager v2 is responsible for policy conflict resolution, resource admission control, and end-to-end QoS path establishment.
The QoS Manager should be deployed on a reliable, always-on network node. As the central coordinator, its availability directly impacts the network’s ability to dynamically adjust QoS policies in response to changing conditions.
QoS Manager v2 Service Model and Operations
The QoS Manager v2 exposes a comprehensive set of UPnP actions that enable applications and control points to interact with the QoS subsystem. The primary operations include RequestTrafficQoS, which initiates a QoS reservation for a specific traffic flow by specifying the traffic descriptor and desired traffic class; ReleaseTrafficQoS, which tears down an active reservation; GetQosDeviceInfo, which retrieves capabilities from a specific QoS Device; and UpdatePolicy, which distributes new or modified policy rules to devices. The QoS Manager maintains a database of all active QoS reservations and the mapping between traffic flows and the devices involved in their forwarding path.
A key engineering aspect of the QoS Manager v2 is its admission control functionality. When an application requests QoS for a new flow, the manager must determine whether sufficient network resources are available to satisfy the request without degrading existing reservations. The specification defines a resource availability model based on traffic class capacities and per-device utilization tracking. The QoS Manager queries the relevant QoS Devices along the traffic path, aggregates their reported utilization, and makes an admission decision. If resources are insufficient, the manager can either reject the request, downgrade the traffic class, or trigger policy renegotiation.
| Operation | Description | Key Input Parameters |
|---|---|---|
| RequestTrafficQoS | Request QoS treatment for a traffic flow | TrafficDescriptor, TrafficClass, Priority |
| ReleaseTrafficQoS | Release an active QoS reservation | TrafficDescriptor, ReservationID |
| GetQosDeviceInfo | Retrieve QoS Device capabilities | DeviceUDN, InterfaceIndex |
| UpdatePolicy | Distribute policy updates to devices | PolicyXML, TargetDeviceList |
| GetActiveReservations | List all current QoS reservations | FilterCriteria |
| ResolvePolicyConflict | Identify and resolve conflicting rules | PolicySet |
Multiple QoS Managers operating on the same network segment without coordination can cause conflicting policy updates. Designate a primary QoS Manager and configure secondary instances in standby mode for high availability.
Engineering Considerations for QoS Manager Deployment
Deploying the QoS Manager v2 in a real-world network requires careful architectural planning. The manager’s database of active reservations and device capabilities must be kept consistent with the actual network state. The specification addresses this through a heartbeat mechanism — the QoS Manager periodically sends keep-alive messages to managed QoS Devices, and devices report their status back. If a device fails to respond, the manager marks its reservations as stale and can optionally trigger re-routing or policy adjustment. The heartbeat interval is configurable, with typical values ranging from 30 seconds for latency-sensitive environments to 5 minutes for stable networks.
Performance scalability is another important consideration. A QoS Manager serving a network with hundreds of QoS Devices and thousands of concurrent traffic flows must efficiently handle policy computation and distribution. The v2 specification introduces batch policy updates, allowing the manager to push multiple policy changes to a device in a single UPnP action, significantly reducing control plane overhead. Additionally, the specification supports policy caching on devices, so that commonly used policy sets are stored locally and activated with minimal latency when needed.
QoS Manager v2 enables dynamic, application-driven QoS management that adapts to changing network conditions. Real-time monitoring allows the manager to proactively adjust policies before congestion impacts application performance.
If the QoS Manager goes offline, QoS Devices continue operating with their last known policies, but no new QoS reservations can be established and no dynamic adjustments can be made. Deploy redundant QoS Manager instances to ensure service continuity.
Frequently Asked Questions
Q: How does the QoS Manager discover QoS Devices on the network?
A: The QoS Manager uses UPnP discovery (SSDP) to locate QoS Device instances. Devices advertise their presence using the QoSDevice:2 service type, and the manager subscribes to these advertisements to maintain an up-to-date device inventory.
A: The QoS Manager uses UPnP discovery (SSDP) to locate QoS Device instances. Devices advertise their presence using the QoSDevice:2 service type, and the manager subscribes to these advertisements to maintain an up-to-date device inventory.
Q: Can the QoS Manager operate across multiple network segments?
A: Yes, provided that UPnP multicast traffic can traverse the network boundaries. In routed environments, SSDP multicast forwarding must be configured, or the QoS Manager can be configured with static device UDN entries for devices on remote subnets.
A: Yes, provided that UPnP multicast traffic can traverse the network boundaries. In routed environments, SSDP multicast forwarding must be configured, or the QoS Manager can be configured with static device UDN entries for devices on remote subnets.
Q: What happens when an application requests QoS but the network path includes non-UPnP devices?
A: The QoS Manager can only configure QoS on UPnP QoS-capable devices. Non-UPnP devices in the path are treated as transparent, and the manager focuses on configuring the QoS-capable devices at the edges of each UPnP-controlled network segment. Best-effort treatment is assumed for non-UPnP segments.
A: The QoS Manager can only configure QoS on UPnP QoS-capable devices. Non-UPnP devices in the path are treated as transparent, and the manager focuses on configuring the QoS-capable devices at the edges of each UPnP-controlled network segment. Best-effort treatment is assumed for non-UPnP segments.
