ISO/IEC 29341-10-11:2008

Information technology - UPnP Device Architecture - Part 10-11: Quality of Service Device Control Protocol - Quality of Service Manager Service

Ingrid Glavich Ingrid Glavich 2 18 1995-11-10T13:27:00Z 2008-11-17T15:21:00Z 2008-11-17T15:21:00Z 1 94 537 4 1 630 10.6845    Clean 21 0 0            MicrosoftInternetExplorer4    /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman";}        
ISO/IEC 29341-10-11:2008(E) enables modeling of QoS Manager function capabilities. QoS Manager function is a combination of QoS Manager service and a control point functionality that discovers and controls QoS Device and QoS Policy Holder services running on the network. The series of ISO/IEC 29341 publications defines an architecture for pervasive peer-to-peer network connectivity of intelligent appliances, wireless devices and PCs. It is designed to bring easy to use, flexible, standards-based connectivity to ad-hoc or unmanaged networks whether in the home, in a small business, public spaces or attached to the Internet.

General Information

• Status: Published
• Publication Date: 27-Nov-2008
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: PPUB - Publication issued
• Start Date: 18-Nov-2008
• Completion Date: 30-Nov-2008

Overview - ISO/IEC 29341-10-11:2008 (UPnP QoS Manager Service)

ISO/IEC 29341-10-11:2008 defines the Quality of Service (QoS) Manager Service as part of the UPnP Device Architecture. It specifies the UPnP Device Control Protocol model for a QoS Manager function - a combined service and control-point role that discovers and controls QoS-capable devices and QoS Policy Holder services on a local network. The standard supports requesting, updating and releasing QoS reservations for traffic streams and provides the XML service description, eventing model and conformance tests needed for interoperable implementations.

Key topics and technical requirements

• Service modeling and types: Defines the ServiceType for the QoS Manager and the structure used to represent QoS-related entities.
• State variables and argument types: Includes A_ARG_TYPE_TrafficDescriptor, A_ARG_TYPE_TrafficHandle, A_ARG_TYPE_NumTrafficDescriptors, A_ARG_TYPE_NumPolicyHolders and related state variables for representing traffic and policy metadata.
• Actions (control operations): Standardizes key actions such as RequestTrafficQos, UpdateTrafficQos, ReleaseTrafficQos and BrowseAllTrafficDescriptors, with inputs/outputs and associated error codes.
• Eventing and moderation: Specifies the UPnP event model and moderation rules for notifying control points about state changes.
• XML service description: Provides the formal XML service description used in UPnP device announcements and discovery.
• Schemas and testability: Normative TrafficDescriptor XML Schema and Traffic Descriptor Matrix (annexes) plus test clauses for interoperability and validation.
• Error handling and common error codes: Defined error responses for action failures to ensure robust control-point interactions.

Practical applications and who uses it

• Home and small-business networking: Enables devices (routers, access points, media servers, set‑top boxes, IP cameras) to request or manage QoS for latency‑sensitive streams (voice, video, gaming) in unmanaged or ad‑hoc networks.
• IoT and consumer electronics manufacturers: Use the standard to implement UPnP-compliant QoS Manager services or clients so devices interoperate across vendors.
• Software developers and integrators: Implement control points (apps, gateways) that orchestrate QoS reservations across QoS-capable devices.
• Network engineers and system architects: Reference the standard when designing end-to-end QoS interactions in UPnP environments and testing multi-vendor setups.

Related standards

• ISO/IEC 29341-1 - UPnP Device Architecture (core)
• ISO/IEC 29341-10-1 - UPnP QoS Architecture
• ISO/IEC 29341-10-10 - QoS Device Service
• ISO/IEC 29341-10-12 - QoS Policy Holder Service

By following ISO/IEC 29341-10-11:2008, implementers ensure consistent UPnP QoS control-point behavior, standard XML service descriptions, and interoperable QoS reservation workflows across consumer and small-business networks. Keywords: UPnP QoS, QoS Manager Service, ISO/IEC 29341-10-11, Quality of Service Device Control Protocol, traffic descriptor, RequestTrafficQos.

Standards Content (Sample)

ISO/IEC 29341-10-11
Edition 1.0 2008-11
INTERNATIONAL
STANDARD
Information technology – UPnP Device Architecture –
Part 10-11: Quality of Service Device Control Protocol – Quality of Service
Manager Service
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about ISO/IEC copyright or have an enquiry about obtaining additional rights to this
publication, please contact the address below or your local IEC member National Committee for further information.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: [e-mail]
Web: www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: [e-mail]
Tel.: [phone]
Fax: [phone]
ISO/IEC 29341-10-11
Edition 1.0 2008-11
INTERNATIONAL
STANDARD
Information technology – UPnP Device Architecture –
Part 10-11: Quality of Service Device Control Protocol – Quality of Service
Manager Service
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
Q
ICS 35.200 ISBN 978-2-88910-900-5

– 2 – 29341-10-11 © ISO/IEC:2008(E)
CONTENTS
FOREWORD .4
ORIGINAL UPNP DOCUMENTS (informative) .6
1. Overview and Scope .8
1.1. Referenced Specifications .8
2. Service Modeling Definitions .9
2.1. ServiceType .9
2.2. State Variables.9
2.2.2. A_ARG_TYPE_TrafficDescriptor.10
2.2.3. A_ARG_TYPE_TrafficHandle.15
2.2.4. A_ARG_TYPE_NumTrafficDescriptors .15
2.2.5. A_ARG_TYPE_NumPolicyHolders.15
2.2.6. A_ARG_TYPE_ ListOfTrafficDescriptors.15
2.2.7. Relationships Between State Variables .16
2.3. Eventing and Moderation .17
2.3.1. Event Model .17
2.4. Actions.18
2.4.1 RequestTrafficQos.18
2.4.2. UpdateTrafficQos.21
2.4.3. ReleaseTrafficQos .23
2.4.4. BrowseAllTrafficDescriptors.23
2.4.5. Non-Standard Actions Implemented by a UPnP Vendor .24
2.4.6. Relationships Between Actions.25
2.4.7. Common Error Codes.25
2.5. Theory of Operation .27
3. XML Service Description .29
4. Test .31
Annex A (normative) TrafficDescriptor XML Schema .32
Annex B (normative) Traffic Descriptor Matrix .39

29341-10-11 © ISO/IEC:2008(E) – 3 –
LIST OF TABLES
Table 2-1: State Variables .10
Table 2-2: Event Moderation .17
Table 2-3: Actions.18
Table 2-4: Arguments for RequestTrafficQos.18
Table 2-5: Error Codes for RequestTrafficQos.20
Table 2-6: Arguments for UpdateTrafficQos .21
Table 2-7: Error Codes for UpdateTrafficQos .22
Table 2-8: Arguments for ReleaseTrafficQos.23
Table 2-9: Error Codes for ReleaseTrafficQos.23
Table 2-10: Arguments for BrowseAllTrafficDescriptors .23
Table 2-11: Error Codes for BrowseAllTrafficDescriptors .24
Table 2-12: Common Error Codes .25

– 4 – 29341-10-11 © ISO/IEC:2008(E)
INFORMATION TECHNOLOGY –
UPNP DEVICE ARCHITECTURE –
Part 10-11: Quality of Service Device Control Protocol
Quality of Service Manager Service
FOREWORD
1) ISO (International Organization for Standardization) and IEC (International Electrotechnical Commission) form
the specialized system for worldwide standardization. National bodies that are members of ISO or IEC
participate in the development of International Standards. Their preparation is entrusted to technical
committees; any ISO and IEC member body interested in the subject dealt with may participate in this
preparatory work. International governmental and non-governmental organizations liaising with ISO and IEC
also participate in this preparation.
2) In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC
1. Draft International Standards adopted by the joint technical committee are circulated to national bodies for
voting. Publication as an International Standard requires approval by at least 75 % of the national bodies
casting a vote.
3) The formal decisions or agreements of IEC and ISO on technical matters express, as nearly as possible, an
international consensus of opinion on the relevant subjects since each technical committee has representation
from all interested IEC and ISO member bodies.
4) IEC, ISO and ISO/IEC publications have the form of recommendations for international use and are accepted
by IEC and ISO member bodies in that sense. While all reasonable efforts are made to ensure that the
technical content of IEC, ISO and ISO/IEC publications is accurate, IEC or ISO cannot be held responsible for
the way in which they are used or for any misinterpretation by any end user.
5) In order to promote international uniformity, IEC and ISO member bodies undertake to apply IEC, ISO and
ISO/IEC publications transparently to the maximum extent possible in their national and regional publications.
Any divergence between any ISO/IEC publication and the corresponding national or regional publication should
be clearly indicated in the latter.
6) ISO and IEC provide no marking procedure to indicate their approval and cannot be rendered responsible for
any equipment declared to be in conformity with an ISO/IEC publication.
7) All users should ensure that they have the latest edition of this publication.
8) No liability shall attach to IEC or ISO or its directors, employees, servants or agents including individual
experts and members of their technical committees and IEC or ISO member bodies for any personal injury,
property damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including
legal fees) and expenses arising out of the publication of, use of, or reliance upon, this ISO/IEC publication or
any other IEC, ISO or ISO/IEC publications.
9) Attention is drawn to the normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
IEC and ISO draw attention to the fact that it is claimed that compliance with this document may involve the use of
patents as indicated below.
ISO and IEC take no position concerning the evidence, validity and scope of the putative patent rights. The holders
of the putative patent rights have assured IEC and ISO that they are willing to negotiate free licences or licences
under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect,
the statements of the holders of the putative patent rights are registered with IEC and ISO.
Intel Corporation has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
Intel Corporation
Standards Licensing Department
5200 NE Elam Young Parkway
MS: JFS-98
USA – Hillsboro, Oregon 97124
Microsoft Corporation has informed IEC and ISO that it has patent applications or granted patents as listed below:

29341-10-11 © ISO/IEC:2008(E) – 5 –
6101499 / US; 6687755 / US; 6910068 / US; 7130895 / US; 6725281 / US; 7089307 / US; 7069312 / US;
10/783 524 /US
Information may be obtained from:
Microsoft Corporation
One Microsoft Way
USA – Redmond WA 98052
Philips International B.V. has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
Philips International B.V. – IP&S
High Tech campus, building 44 3A21
NL – 5656 Eindhoven
NXP B.V. (NL) has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
NXP B.V. (NL)
High Tech campus 60
NL – 5656 AG Eindhoven
Matsushita Electric Industrial Co. Ltd. has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
Matsushita Electric Industrial Co. Ltd.
1-3-7 Shiromi, Chuoh-ku
JP – Osaka 540-6139
Hewlett Packard Company has informed IEC and ISO that it has patent applications or granted patents as listed
below:
5 956 487 / US; 6 170 007 / US; 6 139 177 / US; 6 529 936 / US; 6 470 339 / US; 6 571 388 / US; 6 205
466 / US
Information may be obtained from:
Hewlett Packard Company
1501 Page Mill Road
USA – Palo Alto, CA 94304
Samsung Electronics Co. Ltd. has informed IEC and ISO that it has patent applications or granted patents.
Information may be obtained from:
Digital Media Business, Samsung Electronics Co. Ltd.
416 Maetan-3 Dong, Yeongtang-Gu,
KR – Suwon City 443-742
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights
other than those identified above. IEC and ISO shall not be held responsible for identifying any or all such patent
rights.
ISO/IEC 29341-10-11 was prepared by UPnP Implementers Corporation and adopted, under the PAS procedure, by
joint technical committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of
ISO and IEC.
The list of all currently available parts of the ISO/IEC 29341 series, under the general title Universal plug and play
(UPnP) architecture, can be found on the IEC web site.
This International Standard has been approved by vote of the member bodies, and the voting results may be
obtained from the address given on the second title page.

– 6 – 29341-10-11 © ISO/IEC:2008(E)
ORIGINAL UPNP DOCUMENTS
(informative)
Reference may be made in this document to original UPnP documents. These references are retained in order to
maintain consistency between the specifications as published by ISO/IEC and by UPnP Implementers Corporation.
The following table indicates the original UPnP document titles and the corresponding part of ISO/IEC 29341:
UPnP Document Title ISO/IEC 29341 Part
UPnP Device Architecture 1.0 ISO/IEC 29341-1
UPnP Basic:1 Device ISO/IEC 29341-2
UPnP AV Architecture:1 ISO/IEC 29341-3-1
UPnP MediaRenderer:1 Device ISO/IEC 29341-3-2
UPnP MediaServer:1 Device ISO/IEC 29341-3-3
UPnP AVTransport:1 Service ISO/IEC 29341-3-10
UPnP ConnectionManager:1 Service ISO/IEC 29341-3-11
UPnP ContentDirectory:1 Service ISO/IEC 29341-3-12
UPnP RenderingControl:1 Service ISO/IEC 29341-3-13
UPnP MediaRenderer:2 Device ISO/IEC 29341-4-2
UPnP MediaServer:2 Device ISO/IEC 29341-4-3
UPnP AV Datastructure Template:1 ISO/IEC 29341-4-4
UPnP AVTransport:2 Service ISO/IEC 29341-4-10
UPnP ConnectionManager:2 Service ISO/IEC 29341-4-11
UPnP ContentDirectory:2 Service ISO/IEC 29341-4-12
UPnP RenderingControl:2 Service ISO/IEC 29341-4-13
UPnP ScheduledRecording:1 ISO/IEC 29341-4-14
UPnP DigitalSecurityCamera:1 Device ISO/IEC 29341-5-1
UPnP DigitalSecurityCameraMotionImage:1 Service ISO/IEC 29341-5-10
UPnP DigitalSecurityCameraSettings:1 Service ISO/IEC 29341-5-11
UPnP DigitalSecurityCameraStillImage:1 Service ISO/IEC 29341-5-12
UPnP HVAC_System:1 Device ISO/IEC 29341-6-1
UPnP HVAC_ZoneThermostat:1 Device ISO/IEC 29341-6-2
UPnP ControlValve:1 Service ISO/IEC 29341-6-10
UPnP HVAC_FanOperatingMode:1 Service ISO/IEC 29341-6-11
UPnP FanSpeed:1 Service ISO/IEC 29341-6-12
UPnP HouseStatus:1 Service ISO/IEC 29341-6-13
UPnP HVAC_SetpointSchedule:1 Service ISO/IEC 29341-6-14
UPnP TemperatureSensor:1 Service ISO/IEC 29341-6-15
UPnP TemperatureSetpoint:1 Service ISO/IEC 29341-6-16
UPnP HVAC_UserOperatingMode:1 Service ISO/IEC 29341-6-17
UPnP BinaryLight:1 Device ISO/IEC 29341-7-1
UPnP DimmableLight:1 Device ISO/IEC 29341-7-2
UPnP Dimming:1 Service ISO/IEC 29341-7-10
UPnP SwitchPower:1 Service ISO/IEC 29341-7-11
UPnP InternetGatewayDevice:1 Device ISO/IEC 29341-8-1
UPnP LANDevice:1 Device ISO/IEC 29341-8-2
UPnP WANDevice:1 Device ISO/IEC 29341-8-3
UPnP WANConnectionDevice:1 Device ISO/IEC 29341-8-4
UPnP WLANAccessPointDevice:1 Device ISO/IEC 29341-8-5
UPnP LANHostConfigManagement:1 Service ISO/IEC 29341-8-10
UPnP Layer3Forwarding:1 Service ISO/IEC 29341-8-11
UPnP LinkAuthentication:1 Service ISO/IEC 29341-8-12
UPnP RadiusClient:1 Service ISO/IEC 29341-8-13
UPnP WANCableLinkConfig:1 Service ISO/IEC 29341-8-14
UPnP WANCommonInterfaceConfig:1 Service ISO/IEC 29341-8-15
UPnP WANDSLLinkConfig:1 Service ISO/IEC 29341-8-16
UPnP WANEthernetLinkConfig:1 Service ISO/IEC 29341-8-17
UPnP WANIPConnection:1 Service ISO/IEC 29341-8-18
UPnP WANPOTSLinkConfig:1 Service ISO/IEC 29341-8-19
UPnP WANPPPConnection:1 Service ISO/IEC 29341-8-20
UPnP WLANConfiguration:1 Service ISO/IEC 29341-8-21
UPnP Printer:1 Device ISO/IEC 29341-9-1
UPnP Scanner:1.0 Device ISO/IEC 29341-9-2
UPnP ExternalActivity:1 Service ISO/IEC 29341-9-10
UPnP Feeder:1.0 Service ISO/IEC 29341-9-11
UPnP PrintBasic:1 Service ISO/IEC 29341-9-12
UPnP Scan:1 Service ISO/IEC 29341-9-13
UPnP QoS Architecture:1.0 ISO/IEC 29341-10-1
UPnP QosDevice:1 Service ISO/IEC 29341-10-10
UPnP QosManager:1 Service ISO/IEC 29341-10-11
UPnP QosPolicyHolder:1 Service ISO/IEC 29341-10-12
UPnP QoS Architecture:2 ISO/IEC 29341-11-1
UPnP QOS v2 Schema Files ISO/IEC 29341-11-2

29341-10-11 © ISO/IEC:2008(E) – 7 –
UPnP Document Title ISO/IEC 29341 Part
UPnP QosDevice:2 Service ISO/IEC 29341-11-10
UPnP QosManager:2 Service ISO/IEC 29341-11-11
UPnP QosPolicyHolder:2 Service ISO/IEC 29341-11-12
UPnP RemoteUIClientDevice:1 Device ISO/IEC 29341-12-1
UPnP RemoteUIServerDevice:1 Device ISO/IEC 29341-12-2
UPnP RemoteUIClient:1 Service ISO/IEC 29341-12-10
UPnP RemoteUIServer:1 Service ISO/IEC 29341-12-11
UPnP DeviceSecurity:1 Service ISO/IEC 29341-13-10
UPnP SecurityConsole:1 Service ISO/IEC 29341-13-11

– 8 – 29341-10-11 © ISO/IEC:2008(E)
1. Overview and Scope
This service definition is compliant with the UPnP Device Architecture version 1.0.
This service-type enables modeling of ‘Quality of Service Manager’ function capabilities. QosManager function
is a combination of QosManager service and a control point functionality that discovers and controls QosDevice
and QosPolicyHolder services running on the network. QosManager function is responsible for requesting,
updating, releasing and in general controlling the Quality of Service assigned by networking devices to various
traffic streams. The QosManager service will be invoked from a UPnP Control Point to perform the functions
related to setting up Quality of Service for that traffic. Once the network is configured with respect to the Quality
of Service for the upcoming traffic stream, the QosManager service will hand back control to the control point.
This service provides a mechanism for Control Points to:
ƒ Be agnostic of the Quality of Service capabilities and associated details about the various devices on the
network.
ƒ Hand-over the tasks of setting up, modifying and revoking the Quality of Service associated with every
traffic stream
ƒ Hand-over the task of control point functionality with respect to the UPnP QosDevice service – its
discovery, control and eventing.
ƒ Hand-over the task of control point functionality with respect to the UPnP QosPolicyHolder service – its
discovery, control and eventing.
Thus, a QosManager is a dual-role entity in the sense that it exposes QosManager service to the Control Point
while acting as a Control Point for the QosPolicyHolder and QosDevice services running on the network. This
document describes the components of the UPnP QosManager service.
• This service template does not address:
The control point functionality within a QosManager. However, useful information about the control point
functionality in the QosManager can be found in the following documents:
• UPnP QoS Architecture document
• UPnP QosDevice Service Definition Document
• UPnP QosPolicyHolder Service Definition Document
1.1. Referenced Specifications
Unless explicitly stated otherwise herein, implementation of the mandatory provisions of any standard
referenced by this specification shall be mandatory for compliance with this specification.
This section lists the normative references used in this document and includes the tag inside square brackets
that is used for each sub reference:
[IEEE] - IEEE 802.1D-2004, Annex G, IEEE Standard for Information technology – Telecommunications
and information exchange between systems - IEEE standard for local and metropolitan area networks,
Common specifications - Media access control (MAC) Bridges, 2004.
[XML] – Extensible Markup Language (XML) 1.0 (Second Edition), T. Bray, J.Paoli, C. M. Sperberg
McQueen, E Maler, eds. W3C Recommendations, 6 October 2000.
[DEVICE] - UPnP Device Architecture, version 1.0.
[POLICY HOLDER] – UPnP QosPolicyHolder:1 Service Document.
[QOS DEVICE] – UPnP QosDevice:1 Service Document.

29341-10-11 © ISO/IEC:2008(E) – 9 –
2. Service Modeling Definitions
2.1. ServiceType
The following service type identifies a service that is compliant with this template:
xmlns=”urn:schemas-upnp-org:service:QosManager:1”
xmlns=http://www.upnp.org/schemas/TrafficDescriptorv1.xsd
2.2. State Variables
Reader Note: For first-time reader, it may be more insightful to read the action definitions before reading the
state variable definitions.
2.2.1.1. XML Fragments as UPnP Arguments
The UPnP QoS Framework often uses XML Fragments as arguments in UPnP actions. The containing UPnP data
type is a string. This places restrictions on a string’s content; it has to represent a well-formed XML fragment
(this includes a complete XML document).
The XML schemas used in UPnP-QoS are defined in the respective files located on
http://www.upnp.org/schemas/
In their XML fragments, implementations may use an explicit reference to appropriate name spaces.
At several places in the XML schemas there is room for vendor differentiation through the use of the “any”-tag.
When extending UPnP-QoS with their own XML tags, vendors should use a name space to prevent collisions of
their tags with those of other vendors. It is recommended that implementations are not required to retrieve the
corresponding schemas from the Internet.
Finally, an XML fragment, in adherence to the UPnP Device Architecture 1.0 [DEVICE] , needs to be escaped
[XML] Section 2.4 Character Data and Markup, before embedding it in a SOAP
by using the normal XML rules,
request or response message. The XML escaping rules are summarized from the [XML] reference mentioned
above:
• The (<) character is encoded as (<)
• The (>) character is encoded as (>)
• The (&) character is encoded as (&)
• The (”) character is encoded as (")
• The (‘) character is encoded as (')

– 10 – 29341-10-11 © ISO/IEC:2008(E)
Table 2-1: State Variables
Variable Name Req. Data Allowed Value Default Eng.
or Type Value Units
Opt.
A_ARG_TYPE_TrafficDescriptor R string Escaped XML fragment n/a n/a
of trafficDescriptor
Schema (See Appendix
A for details).
A_ARG_TYPE_TrafficHandle R string n/a n/a
A_ARG_TYPE_NumTrafficDescriptors R integer Non-negative integer. n/a n/a
R integer Non-negative integer. n/a n/a
A_ARG_TYPE_NumPolicyHolders
R string Escaped XML fragment n/a n/a
A_ARG_TYPE_
ListOfTrafficDescriptors
R = Required, O = Optional, X = Non-standard.
Values listed in this column are required. To specify standard optional values or to delegate assignment of
values to the vendor, you must reference a specific instance of an appropriate table below.
2.2.2. A_ARG_TYPE_TrafficDescriptor
This state variable contains information about a particular traffic stream. A Traffic Descriptor consists of an
XML structure consisting of:
ƒ TrafficHandle
ƒ TrafficID
ƒ AvailableOrderedTspecList
ƒ QosBoundarySourceAddress
ƒ TrafficImportanceNumber
ƒ QosBoundaryDestinationAddress
ƒ UserName
ƒ CpName
ƒ VendorApplicationName
ƒ PortName
ƒ ServiceProviderServiceName
ƒ TrafficLeaseTime
Please refer to the detailed TrafficDescriptor XML schema in Appendix A. Here are some details about
information in Traffic Descriptor:

Tspec
Tspec contains a description of Content QoS Requirements. Tspec is represented in the form of a XML structure.
In UPnP AV scenario, this information is extracted from the Content Directory Service of the Media Server. In
the Content Directory Service, Tspec is represented either as a string containing escaped XML structure, or an
URI pointing to the escaped XML structure. UPnP AV Control Point uses CDS:Browse and/or CDS:Search
action calls to acquire the Tspec(s) associated with the content and creates an AvailableOrderedTspecList field in
the Traffic Descriptor.
Tspec XML structure consists of the following:
‰ TspecIndex: Unique numerical index associated with a particular Tspec. The value of Tspecindex
indicates preference (as defined by the application or the end user). A Tspec with smaller Index is more
preferred compared to a Tspec with larger Index.
‰ AVTransportURI: This string field contains a unique URI associated with the UPnP AV content item
for which QoS is being requested.

29341-10-11 © ISO/IEC:2008(E) – 11 –
‰ AVTransportInstanceID: This integer field contains a unique Instance ID associated with the UPnP AV
Transport service associated with the content item for which QoS is being requested.
‰ TrafficClass: The traffic class associated with the traffic stream. This is an enumerated variable that can
be assigned to one of the following list of values:
o Network Control
o Streaming Control
o Voice
o AV
o Data
o Audio
o Image
o Gaming
o Other
o Background
TspecIndex must be filled in by the Control Point. Other Tspec parameters may be omitted if they are not known.
TspecIndexs need not be consecutive numbers. The Tspec with lower TspecIndex is more preferred than a higher
TspecIndex. In this example, the Tspec with 2 is more preferred than that with 300. The order of Tspec
structures in the AvailableOrderedTspecList is not relevant. All Tspecs must have unique TspecIndex value
within an AvailableOrderedTspecList.


300
AV


2
Audio


TrafficHandle
TrafficHandle is a unique identifier associated with a particular instance of TrafficDescriptor; i.e. a particular
traffic stream. It is a unique string generated by the QosManager and provided to the Control Point in response to
the RequestTrafficQos action. The QosManager must insure that the generated Traffic Handle string is unique for
all Traffic Descriptors on the network. In all subsequent communication between the CP and the QosManager
service, TrafficHandle is used to reference a particular traffic stream.
AvailableOrderedTspecList
Contains one or more Tspec components. The Tspec index reflects the order of preference. Tspecs with smaller
index values are more preferred. AvailableOrderedTspecList is required. A Tspec may be defined via any
combination of its components.

ActiveTspecIndex
Active TspecIndex contains an integer which indicates the index of the current active Tspec from the TspecList.
Tspec and Tspec List are defined above.
QosBoundarySourceAddress
If a traffic stream originates outside the home network (e.g. on the Internet), the CP application must provide the
QoS boundary point IP address. This address will be treated as the QoS termination point for UPnP QoS.
Optional, because it is applicable only to traffic streams originating outside the home network. It should be noted
that this address is not part of traffic identifier, because the IP packets will carry the IP address of the actual
source address. QosBoundarySourceAddress is used by QosManager for decisions related to path determination
and device selection.
– 12 – 29341-10-11 © ISO/IEC:2008(E)
QosBoundaryDestinationAddress
If a traffic stream terminates outside the home network (e.g. on the Internet), the CP application must provide the
QoS boundary point IP address. This address will be treated as the QoS termination point for UPnP QoS.
Optional, because it is applicable only to traffic streams terminating outside the home network. It should be noted
that this address is not part of traffic identifier, because the IP packets will carry the IP address of the actual
destination address. QosBoundaryDestinationAddress is used by QosManager for decisions related to path
determination and device selection.

TrafficId
TrafficId contains information about identifying / classifying packets that belong to that particular traffic stream.
It consists of an XML structure consisting of: SourceIP; DestinationIP; SourcePort; DestinationPort; Protocol.
Any of these arguments that are not known are represented as null.
UserName
UserName field contains a string associated with the user who requested a particular traffic stream. This field, if
present, shall identify the name of the user initiating the UPnP QoS Action. The field must be <= 64 UTF-8
characters. At present this specification does not define the semantics for this field. This field represents the name
of the user initiating the QoS action. Examples include, “Dad”, “Jimmy”, “CN#1234567”. The latter is an
example of a name provided by a service provider to uniquely identify its individual customers.
CpName
CpName field contains a string associated with the Control Point requesting the traffic stream. This field, if
present, shall identify the name of the control point initiating the UPnP QoS Action. The field must be <= 64
UTF-8 characters. At present this specification does not define the semantics for this field. The CpName may
specify the brand name of the control point or it may indicate the location of the control point such as “living
room”
VendorApplicationName
VendorApplicationName field contains a single URI string associated with an application. This field, if present,
shall identify the name of the application initiating the UPnP QoS Action. For applications specified by vendors,
the value of this field must begin with “urn:”,followed by an ICANN domain name owned by the vendor,
followed by “:application:”, followed by an application name. i.e. the value of this field should be constructed as
follows:
urn:domain-name:application:appl-name
domain-name: Application vendor domain name. This must follow the syntax specified for Namespace Identifier
(NID) in the RFC 2141. The domain-name field must be <= 64 UTF-8 characters.
appl-name: Name of the application provided by a vendor. This must follow the syntax specified for Name
Specific String (NSS) in the RFC 2141. The appl-name field must be <= 64 UTF-8 characters. The application-
name must not contain the colon character.
When requesting QoS it may be useful to know the manufacturer and name of the application software client or
server that will process the traffic stream.

PortName:
PortName field contains a single URI string associated with the fixed port used by an application for its
connection set-up. This field, if present, shall identify the port number used by the application. The value of this
field must begin with “urn:”, followed by an ICANN domain name owned by the vendor, followed by “:port:”,
followed by the port name. i.e. the value of this field should be constructed as follows
urn:domain-name:port:port-number

29341-10-11 © ISO/IEC:2008(E) – 13 –
domain-name: Application vendor domain name. This must follow the syntax specified for Namespace Identifier
(NID) in the RFC 2141. The domain-name field must be <= 64 UTF-8 characters.
port-number: A fixed port number used by the application either for connection set-up. This must be an integer
value in the range 1 to 65535. If the application uses a range of port numbers then the starting port number of
that range shall be specified. This value is either a vendor specific port used for the application or an IANA
assigned port number for the application. The list of all the IANA assigned port numbers is maintained by IANA
http://www.iana.org/assignments/port-numbers.
and is available at
These fields indicate the port that is used by an application for its connection set-up. The use of IANA assigned
port numbers is encouraged, but if not available for a particular application, a vendor assigned port number may
be used.
ServiceProviderServiceName
ServiceProviderServiceName field contains a single URI string associated with a service offered by a service
provider. This field, if present, shall identify the name of the service offered by a service provider. For services
provided by service providers, the value of this field must begin with “urn:”, followed by an ICANN domain
name owned by a service provider , followed by “service:”, followed by a service name. i.e. the value of this field
should be constructed as follows:
urn:domain-name:service:serv-name
domain-name: Service Provider domain name. This must follow the syntax specified for Namespace Identifier
(NID) in the RFC 2141. The domain-name field must be <= 64 UTF-8 characters.
serv-name: Name of the service provided by a service vendor. This must follow the syntax specified for Name
Specific String (NSS) in the RFC 2141. The serv-name field must be <= 64 UTF-8 characters. The serv-name
must not contain the colon character.
This represents the name of a particular service being offered by a service provider. Note that while multiple
services provided by the same service provider may use the same software application, different Service offerings
may be given different priorities (traffic importance).
TrafficLeaseTime
This field contains the lease-time associated with a particular traffic stream. The lease time is expressed in
‘Seconds’. When not specified, it indicates an indefinite lease.
MediaServerConnectionId:
This is an optional field. This field may be useful in case of UPnP AV based streaming with multiple Tspecs.
MediaServerConnectionId may be used by the QosManager to identify the traffic stream that is being setup by
the UPnP AV Control Point which is requesting Qos. Please refer to UPnP QoS Architecture document for more
details. The connection Id is obtained from the Media Server via CM::PrepareForConnection action.
MediaRendererConnectionId:
This is an optional field. This field may be useful in case of UPnP AV based streaming with multiple Tspecs.
MediaRendererConnectionId may be used by the QosManager to identify the traffic stream that is being setup by
the UPnP AV Control Point which is requesting Qos. Please refer to UPnP QoS Architecture document for more
details. The connection Id is obtained from the Media Renderer via CM::PrepareForConnection action.
Use the following XML documents as examples for TrafficDescriptor schema.
Example 1:
xmlns="http://www.upnp.org/schemas/TrafficDescriptorv1.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.upnp.org/schemas/TrafficDescriptorv1.xsd">
kiwin1


192.168.1.50
– 14 – 29341-10-11 © ISO/IEC:2008(E)

23

192.168.1.53

23
1



300
AV


2
Audio


300
5

Amy's CP


Example 2:
xmlns="http://www.upnp.org/schemas/TrafficDescriptorv1.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:prv="http://myPrivate.com"
xmlns:prv2="http://myPrivate2.com"
xsi:schemaLocation="http://www.upnp.org/schemas/TrafficDescriptorv1.xsd">

kiwin1


192.168.1.50

23

192.168.1.53

23
1



300
AV


2
Audio


300
5

Amy's CP


29341-10-11 © ISO/IEC:2008(E) – 15 –
2.2.3. A_ARG_TYPE_TrafficHandle
This state variable contains a unique identifier associated with a particular instance of TrafficDescriptor i.e. a
particular traffic stream. It is a unique string generated by the QosManager and provided to the Control Point in
response to the RequestTrafficQos action. In all subsequent communication between the CP and the QosManager
service, TrafficHandle is used to reference a particular traffic stream. QosManager must insure that
TrafficHandle is a unique string that identifies one and only one TrafficDescriptor on the network.
2.2.4. A_ARG_TYPE_NumTrafficDescriptors
This state variable contains the number of Traffic Descriptors registered / admitted by a given instance of the
QosManager service. This information is returned in response to the BrowseAllTrafficDescriptors service action
call from the Control Point.
2.2.5. A_ARG_TYPE_NumPolicyHolders
This state variable contains the number of instances of QosPolicyHolder service discovered by a given instance
of the QosManager service. This variable is returned in response to RequestTrafficQos and UpdateTrafficQos
actions (as an output argument) to convey to a Control Point the number of active Policy Holders on the network.
If the value of this variable is not equal to 1, it means that the default policy was used by the QosManager to
make admission control decisions.
2.2.6. A_ARG_TYPE_ ListOfTrafficDescriptors
This state variable contains one or more instances of the state variable A_ARG_TYPE_TrafficDescriptor. Here
is the XML schema for this state variable:

targetNamespace="http://www.upnp.org/schemas/ListOfTrafficDescriptors.xsd"
xmlns="http://www.upnp.org/schemas/ListOfTrafficDescriptors.xsd"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:td="http://www.upnp.org/schemas/TrafficDescriptorv1.xsd"
elementFormDefault="qualified" id="ListOfTrafficDescriptors">

namespace="http://www.upnp.org/schemas/TrafficDescriptorv1.xsd"
schemaLocation="TrafficDescriptorv1.xsd"/>


List of Traffic Descriptors schema.
Copyright 2004, 2005 UPnP(tm). All rights reserved.


type="ListOfTrafficDescriptorsType"/>


minOccurs="0" maxOccurs="unbounded"/>



Use the following XML document as an example for ListOfTrafficDescriptors schema.

xmlns="http://www.upnp.org/schemas/ListOfTrafficDescriptors.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.upnp.org/schemas/ListOfTrafficDescriptors.xs
d">

kiwin1

– 16 – 29341-10-11 © ISO/IEC:2008(E)

192.168.1.50

23

192.168.1.50

23
1



300
AV


2
Audio


1
5

Amy's CP



kiwin2


192.168.1.53

23

192.168.1.55

23
1



300
AV


2
Audio


1
5

Amy's CP



2.2.7. Relationships Between State Variables

29341-10-11 © ISO/IEC:2008(E) – 17 –
2.3. Eventing and Moderation
Table 2-2: Event Moderation
Variable Name Evented Moderated Max Event Logical Min Delta
1 2
Event Rate Combination per Event
A_ARG_TYPE_TrafficDescrip
NO n/a n/a n/a n/a
tor
A_ARG_TYPE_TrafficHandle
NO n/a n/a n/a n/a
A_ARG_TYPE_NumTrafficDe
NO n/a n/a n/a n/a
scriptors
A_ARG_TYPE_NumPolicyHolNO n/a n/a n/a n/a
ders
A_ARG_TYPE_ NO n/a n/a n/a n/a
ListOfTrafficDescriptors
Determined by N, where Rate = (Event)/(N secs).
(N) * (allowedValueRange Step).
2.3.1. Event Model
– 18 – 29341-10-11 © ISO/IEC:2008(E)
2.4. Actions
Immediately following this table is detailed information about these actions, including short descriptions of t
...