Overview
ISO/IEC 29341-17-13:2011 is an addendum to the UPnP QosDevice Service specification that defines underlying technology interfaces for Quality of Service (QoS) in UPnP devices. Its purpose is to provide implementers with recommended, consistent mappings of UPnP QoS methods and parameters to a variety of lower transport (Layer‑2 and higher) technologies so that device vendors and integrators achieve interoperable QoS behavior across different link layers.
Key topics and requirements
- Scope and intent: Recommendations for implementing interfaces between the UPnP QosDevice Service (UPnP‑QoS v3) and various lower transport layers. Ensures consistent mapping of methods and parameters from UPnP to L2 technologies.
- Layer assumptions: QosDevice Services are expected to run directly on top of Layer‑2 MAC/PHYs but MAY run on higher‑layer mechanisms; both types are considered “L2 technologies” in this document.
- Mandatory references: Implementers must follow normative references (e.g., UPnP QosDevice:3, UPnP Device Architecture) when required by this specification.
- Default handling: If an optional parameter is omitted by an L2 technology and UPnP‑QoS defines a default, the QosDevice Service MUST use the UPnP‑QoS default (over the L2 default).
- Per‑technology clauses: Normative mappings and requirements are provided for specific technologies, including:
- DSCP
- HomePlug AV
- HPNA
- IEEE 802.1Q (Annex G)
- MoCA
- Wi‑Fi WMM‑AC
- UPA
- Technical elements addressed:
- Priority mapping tables for each L2 technology
- QosSegmentId formation and Layer2StreamId representation
- Mapping of UPnP QoS parameters to technology‑specific traffic specification (TSPEC) and CSPEC parameters
- Identification of blocking traffic streams and responsibility for QoS setup
- Mapping of returned parameters to ProtoTspec, AdmitTrafficQosExtendedResult, and AllocatedResources
Applications and who uses it
- Device vendors and firmware developers implementing UPnP QosDevice Service to ensure consistent QoS behavior across home and enterprise networks.
- Network equipment manufacturers integrating UPnP‑based QoS control with link‑layer QoS mechanisms (Ethernet, Wi‑Fi, MoCA, HomePlug).
- System integrators and service providers needing predictable QoS mappings for multimedia streaming, real‑time communication, and prioritized traffic in UPnP ecosystems.
- Test labs and QA teams validating interoperability between UPnP QoS controllers and various L2 technologies.
Related standards (examples)
- UPnP QosDevice:3 (service document)
- UPnP Device Architecture v1.0
- IEEE 802.1Q (Annex G)
- IANA interface type MIB listings
This standard is most useful when you need clear, prescriptive guidance for mapping UPnP QoS abstractions to concrete link‑layer QoS primitives (priority, TSPEC/CSPEC, stream identifiers) to achieve interoperable, predictable Quality of Service across heterogeneous networks. Keywords: UPnP QosDevice, UPnP QoS, Quality of Service Device Service, underlying technology interfaces, Layer 2, priority mapping, WMM‑AC, MoCA, HomePlug AV.
Open preview (PDF)Information technology — UPnP Device Architecture — Part 17-13: Quality of Service Device Control Protocol — Level 3 — Quality of Service Device Service — Underlying Technology Interfaces
