ISO/IEC 29341-11-1:2008
(Main)Information technology - UPnP Device Architecture - Part 11-1: Quality of Service Device Control Protocol - Level 2 - Quality of Service Architecture
Information technology - UPnP Device Architecture - Part 11-1: Quality of Service Device Control Protocol - Level 2 - Quality of Service Architecture
Ingrid Glavich Ingrid Glavich 2 18 1995-11-10T13:27:00Z 2008-11-17T15:22:00Z 2008-11-17T15:22:00Z 1 80 460 3 1 539 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-11-1:2008(E) describes prioritized QoS. UPnP QoS architecture defines 3 services. These are the QoS Policy Holder Service, QoS Manager Service and QoS Device Service. 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
Standards Content (Sample)
ISO/IEC 29341-11-1
Edition 1.0 2008-11
INTERNATIONAL
STANDARD
Information technology – UPnP Device Architecture –
Part 11-1: Quality of Service Device Control Protocol – Level 2 – Quality of
Service Architecture
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: inmail@iec.ch
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: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
ISO/IEC 29341-11-1
Edition 1.0 2008-11
INTERNATIONAL
STANDARD
Information technology – UPnP Device Architecture –
Part 11-1: Quality of Service Device Control Protocol – Level 2 – Quality of
Service Architecture
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
M
ICS 35.200 ISBN 978-2-88910-902-9
– 2 – 29341-11-1 © ISO/IEC:2008(E)
CONTENTS
FOREWORD .4
ORIGINAL UPNP DOCUMENTS (informative) .6
1. Glossary .8
2. Introduction .10
2.1. Referenced Specifications .10
3. Architecture Overview .11
3.1. Motivation.12
3.1.1. Policy-based QoS .12
3.2. Key Concepts.13
3.2.1. Admission Control.13
3.2.2. Admission Policy.13
3.2.3. Traffic Descriptor .13
4. UPnP QoS Services.14
4.1. QosPolicyHolder Service.14
4.1.1. Role.14
4.1.2. Traffic Stream QoS Policy Description .14
4.2. QoS Manager.15
4.2.1. Role.15
4.2.2. Behavior.15
4.2.3. Dealing with Policy.15
4.2.4. QoS Update .16
4.3. QosDevice Service.16
4.3.1. Role.16
4.3.2. Behavior.16
4.3.3. Setup Traffic QoS .17
4.3.4. Traffic Admission Control.17
4.3.5. Path Information.17
4.3.6. Events .17
5. System Operation.18
5.1. Initiation of QoS Setup .18
5.1.1. Integrated Control Point .18
5.1.2. Independent AV Control Point.19
5.1.3. Determination of TrafficId .19
5.1.4. Creation of Optional Traffic Specification (Tspec) .20
5.2. Determination of Policy for the Traffic Stream .20
5.2.1. QosPolicyHolder Service .20
5.2.2. Default Policy .21
5.3. Determination of QosDevice Services that should be configured.22
5.3.1. Path Determination (Optional) .22
5.3.2. Setup Capabilities Determination.22
5.4. Configuration of QoS Devices.22
5.4.1. Priority Setup Strategy .23
5.4.2. Admission Control Strategy .23
5.4.3. Traffic Observation Strategy .23
5.5. Run time Operation .23
5.5.1. Lease Management .23
5.5.2. Traffic revocation .23
5.5.3. Violation of TSPEC .23
29341-11-1 © ISO/IEC:2008(E) – 3 –
5.5.4. The Use of Traffic Descriptor.23
5.6. Relationship to other UPnP Services and non UPnP Traffic Streams .24
5.6.1. UPnP IGD .24
5.6.2. Legacy Devices.24
6. Prioritized QoS .25
6.1. Management of Packet Priorities .25
7. Usage of Tspec.27
Annex A (normative) Layer 2 Implementation Guidelines .28
A.1 IEEE 802.1D, Annex G.28
A.2 HomePlug .28
A.3 HPNA .29
A.4 DSCP .29
Annex B (normative) XML Namespaces .30
– 4 – 29341-11-1 © ISO/IEC:2008(E)
INFORMATION TECHNOLOGY –
UPNP DEVICE ARCHITECTURE –
Part 11-1: Quality of Service Device Control Protocol – Level 2 –
Quality of Service Architecture
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-11-1 © 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-11-1 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-11-1 © 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-11-1 © 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-11-1 © ISO/IEC:2008(E)
1. Glossary
Access Domain
A set of LAN or MAN stations together with interconnecting data transmission media and related equipment
(e.g., connectors, repeaters), in which the LAN or MAN stations use the same MAC protocol to establish the
sequence of stations that are in temporary control of the shared transmission media.
Access Priority
The Access Priority is a parameter that indicates the priority handling when accessing the communication
resource. The range of access priorities is defined by the layer 2 networking technology.
AV Control Point
A Control Point that is used in an AV scenario and utilizes UPnP AV.
Best Effort
Best effort is a service of the Internet Protocol; i.e. it makes almost no guarantees about a packet other than
attempting to transmit it. At the destination, the packet may arrive damaged, it may be out of order (compared to
other packets sent between the same hosts), it may be duplicated, or it may be dropped entirely. If reliability is
needed, it is provided by upper level protocols transported using IP.
With the introduction of IEEE 802.1D priority tagging the priority associated with untagged packets is also
called "Best Effort".
Bridge
A functional unit that interconnects two or more LANs that use the same Data Link layer protocols above the
MAC sublayer, but can use different MAC protocols
Hub
A device, with two or more physical ports, that forwards all traffic received on any individual port to all other
ports. This device is also referred to as a “repeater”. In a home network, a hub connects networks segments of the
same physical medium.
IGD
Internet Gateway Device: a border device that physically connects the Home Network with a WAN. This device
performs routing. QoS mechanisms associated with routing are not addressed by this architecture; the IGD may
present a QosDevice interface on the Home Network.
Intermediate Device
An intermediate device is physically connected between the Source and Sink device data flow. There may be
more than one intermediate device in the Source to Sink connection.
Path
A path is the physical course that traffic will flow on from source to sink. For UPnP QoS, a path must reside
within a single IP subnet, but a path may comprise multiple segments.
Packet Priority
The Packet Priority is a layer 2 parameter that indicates the priority handling requested by the originating service.
Typically this parameter is part of a packet header and indicates the relative importance of the packet compared
to other packets. It is used to differentiate packets to determine which are given preferential access to the
communication medium. This parameter is typically mapped to an Access Priority value supported by the
network device.
Policy Management
A function that makes decisions on the traffic streams allowed to use network resources.
29341-11-1 © ISO/IEC:2008(E) – 9 –
Prioritized Services
Prioritized services refer to a general methodology for providing QoS by differentiating traffic. Messages types
are grouped by order of importance and assigned a priority. Message types assigned a higher priority are given
preferential access to the communications medium.
Quality of Service (QoS)
The term QoS refers to a broad collection of networking capabilities and techniques. The goal of QoS is to
improve the user experience of a network’s ability to deliver predictable results for sensitive applications such as
audio, video, and voice applications. Elements of network performance within the scope of QoS often include
bandwidth (throughput), latency (delay), and error rate. There are two broad classes of QoS: data reliability and
temporal reliability. Each makes different demands on network technologies. This architecture is primarily
concerned with delivering temporal reliability
Router
A device, with two or more physical ports, that makes port to port traffic forwarding decisions based on layer 3
information (source and destination IP addresses).
Segment
A segment refers to a section of a network that shares a common physical medium. The boundaries of a network
segment are established by devices capable of regulating the flow of traffic into and out of the segment. This
includes routers, bridges, hubs, switches, and adapters (e.g., PCI, PCCard, or USB NICs). With particular
relevance to UPnP QoS, a segment is typically a physically distinct portion of a larger network that is in turn
defined logically by devices residing on a common IP subnet.
Sink Device
A Sink device provides media data receiving, playback, storage, or rendering capabilities. Some examples
include TV monitors, Stereo and Home Theaters, PDAs, Wireless Monitors, DVD Recorders, and Printers.
Source Device
A Source device provides media transmission and data sourcing capabilities. Examples include STBs, PVRs,
PCs, Music Servers, Broadcast Tuners and Video Imaging Capture Devices. A source device acts as the source
of a traffic stream, regardless of other functions on the device.
Subnet
Subnet as defined in IETF RFC 3927 [RFC3927].
Traffic Class
The Traffic Class indicates the kind of traffic in the traffic stream. The Traffic Class is used to distinguish, for
example, audio from video. The distinction is at the application layer and the Traffic Class is mapped into the
applicable layer 2 representations for the technology bearing the stream. An example is the mapping in IEEE
802.1D, Annex G.
Traffic Identifier (TID)
A Traffic Identifier is a set of information that uniquely identifies a set of data packets as belonging to a traffic
stream. This information is typically used by a packet classifier function to associate a Traffic Specification’s
QoS contract to the service provided to the Traffic stream. Other technologies may refer to this as a Filter Spec
(RFC2205) or Traffic Classifier (IEEE 802.11e).
Traffic Specification (TSPEC)
A Traffic Specification contains a set of parameters that define the characteristics of the traffic stream. The
TSPEC may be used to define the operating requirement for carrying the traffic stream and may define the
operation of the packet scheduling function.
Traffic Stream (TS)
Traffic Stream is a unidirectional flow of data that originates at a source device and terminates at one or more
sink device(s).
– 10 – 29341-11-1 © ISO/IEC:2008(E)
2. Introduction
This architecture document describes the motivation, use and interaction of the three services that comprise the
UPnP QoS Framework:
• QosDevice
• QosPolicyHolder
• QosManager
It should be noted that while UPnP QoS defines three services (listed above), it does not define a new device
type.
Since Quality of Service issues need to be solved for multiple usage scenarios, it is expected that vendors may
use any UPnP device as a container for the services defined by UPnP QoS. The Control Points and QoS
Management Entities must look for UPnP QoS Services embedded in all UPnP device types.
The UPnP QoS Framework is compliant with the UPnP Device Architecture version 1.0.
2.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.
[Annex_G] – 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.
[QM] – UPnP QosManager:2 Service Document:
[QD] – UPnP QosDevice:2 Service Document:
[QPH] – UPnP QosPolicyHolder:2 Service Document:
[AV] – UPnP AV Architecture Document V0.83
[DEVICE] - UPnP Device Architecture, version 1.0.
[DSCP] - IETF RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6
Headers, K. Nichols, Cisco Systems, S. Blake, Torrent Networking Technologies, F. Baker, Cisco Systems,
D.Black, EMC Corporation, December 1998.
[RFC3927] IETF RFC 3927, Dynamic Configuration of IPv4 Link-Local Addresses.
[RFC3339] – Date and Time on the Internet: Timestamps, G. Klyne, July 2002.
http://www.ietf.org/rfc/rfc3339.txt
[RFC2474] - Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers.
http://www.ietf.org/rfc/rfc2474.txt
29341-11-1 © ISO/IEC:2008(E) – 11 –
3. Architecture Overview
This version of the architecture document only describes prioritized QoS. UPnP QoS architecture defines 3
services. These are the QosPolicyHolder[QPH] Service[QPH] , QosManager[QM] Service[QM] and
QosDevice[QD] Service[QD] . All three are shown in the following figure. The numbers in parenthesis indicate
the order of the QoS actions.
Set Policy
QoS Policy
(unspecified interface)
Holder
Traffic Policy (3)
Traffic Descriptor (2)
Control
Request QoS (1)
Point
QoS Manager
Traffic Descriptor (4)
QoS Device Service QoS Device Service QoS Device Service
Layer 2 Layer 2 Layer 2
Traffic
802.3 / 802.11 802.3 / 802.11 802.3 / 802.11
Importance
Device Device Device
converted to
specific Layer
2 QoS
Traffic Traffic
Streams Streams
Source Intermediate Sink
Figure 1 – UPnP QoS Architecture Overview
The following describes an overall architecture of the QoS subsystem and the interaction between various
components. To illustrate the relationships of various QoS components, an example scenario with a simple
sequence of setup steps is described below. The detailed operations are described in section 5.
In this scenario, a Control Point application is assumed to have the knowledge of source, sink and content to be
streamed, along with the content’s Tspec. The Control Point constructs a TrafficDescriptor structure and
requests a QosManager in the network to setup QoS for a traffic stream (step 1). The Control Point may
optionally indicate the QosPolicyHolder service of its choice when calling the QosManager service. The
QosManager component, acting as a Control Point (often referred to as QoS Management Entity), requests the
QosPolicyHolder service (step 2) to provide appropriate policy for the traffic stream described by the
TrafficDescriptor (step 3). Based on this policy, the QosManager configures the QosDevice(s) for handling the
new traffic stream (step 4).
The QosPolicyHolder Service provides traffic policy for the network on which it resides. It can be used to set the
relative importance of a traffic stream by returning a TrafficImportanceNumber and a UserImportanceNumber
(these are elements of TrafficPolicy). The TrafficImportanceNumber in turn, is conveyed to QosDevice(s) by the
QosManager and is used by the QosDevice to derive the technology specific layer 2 access priority. For
Parameterized Services, the allocation of resources for QoS instances, by a QosDevice, is determined by the
UserImportanceNumber. The mechanisms for setting up parameterized QoS are not defined in this version of
UPnP QoS architecture.
The QosManager communicates with the QosPolicyHolder , to get the TrafficImportanceNumber (part of
TrafficPolicy) for the requested traffic stream (described by the traffic descriptor). The Control Point may select
a QosPolicyHolder that the QosManager must use. If the Control Point does not specify a QosPolicyHolder, then
the QosManager searches for all QosPolicyHolder instances on the network. If there are zero or more than one
– 12 – 29341-11-1 © ISO/IEC:2008(E)
QosPolicyHolder instances on the network, then the QosManager applies a default policy based on the
TrafficClass supplied by the Control Point. However, if the QosManager finds exactly one QosPolicyHolder on
the network and the Control Point has not selected any QosPolicyHolder then the QosManager queries that
QosPolicyHolder for traffic policy.
Additionally, the QosManager may perform admission control for a traffic stream on behalf of a QosDevice, if
the “AdmissionPolicy” attribute is set to “enabled” by the QosPolicyHolder. If admission control is performed,
4.1.2.)
the UserImportanceNumber is used to determine the relative importance of the traffic streams (see Section
otherwise this parameter must be ignored.
Fundamentally, UPnP QoS operates on a traffic stream that flows between two or more devices. A traffic stream
is viewed as a uni-directional flow from a source device to a sink device, possibly passing through intermediate
devices. The QosDevice Service exists within one or more devices to receive and apply the
TrafficImportanceNumber (e.g., implied access priority) for a traffic stream.
The internal mechanism used by the QosDevice for applying the TrafficImportanceNumber is not defined by
UPnP. For a prioritized environment, it is envisioned that either an application on the source QosDevice directly
tags the packets to be transmitted or there is a classifier function in the QosDevice that examines and tags
packets.
It should be noted that a fundamental assumption for UPnP QoS is that every device on the home network will be
on the same IP subnet. Therefore routing between devices in the Home Network is out of scope for UPnP QoS.
This section is meant as a brief overview of the UPnP QoS Architecture. The following section will explain the
motivation behind UPnP QoS. It also introduces some key concepts and terms that will be explored in the
following sections of this document.
3.1. Motivation
3.1.1. Policy-based QoS
Policy-based QoS provides a way to allocate network resources, e.g., network bandwidth, according to a set of
defined preferences. It provides criteria for resolving conflicts when applications simultaneously compete for the
resources. Policy is the basis for responding to questions such as these:
• Who and what can access which resources on the network?
• What is the highest importance traffic or application that is in use, what is the lowest importance traffic,
and what levels of traffic are in between?
A policy-based QoS system allows an individual or entity to define rules, based on these types of questions and
to manage them in the context of the policy system. These rules are then applied to network resources and
requests based upon a set of pre-defined criteria and/or conditions such as network address, application type
and/or bandwidth needs and availability.
UPnP QoS is a policy-based QoS system. The QosPolicyHolder Service, in particular, provides a mechanism for
enabling or disabling Admission Policy [ 3.2.2] for the entire network and for classifying traffic according to
information provided in the request for QoS for a particular traffic stream. The type of information is provided in
the Traffic Descriptor includes, among other items, traffic class (best-effort, video, voice, etc.), the source and
destination network IP addresses for the stream, and the protocol, application name, username, etc. Whenever a
request for QoS is made, it is forwarded to the QosPolicyHolder Service (if present) by the QosManager Service.
The QosPolicyHolder Service then examines the information provided in the request and returns the importance,
in the form of a TrafficPolicy that shall be given to the traffic stream.
There were several goals taken into account in the design of the UPnP QoS Architecture and in particular the
QosPolicyHolder Service. These included:
1. Consistent and predictable classification of a traffic stream.
2. Allow for flexibility in QosPolicyHolder implementation, to meet the diverse needs of applications
and requirements.
29341-11-1 © ISO/IEC:2008(E) – 13 –
3.2. Key Concepts
3.2.1. Admission Control
Admission control is the procedure followed to permit the instantiation of a traffic stream at any of the following
QoS capable devices: a source, zero or more intermediate devices on a traffic stream's path, or a sink. This
procedure is based on a device’s resources and is a go/no-go decision for a single traffic stream instantiation
request. The decision is made based on the instantaneous state of the device. The procedure may be executed by
the QosManager or the QosDevice, depending on the device's advertised capabilities. In the UPnP QoS version
2.0 Specification, QosDevice Admission Control is not supported.
3.2.2. Admission Policy
Admission Policy is the procedure followed by the QosManager, which is responsible for managing the end to
end instantiation of a traffic flow. This procedure uses policy information, obtained from the QosPolicyHolder
Service, to determine the continuing viability of existing end to end traffic instances. If policy permits, existing
end-to-end traffic stream instances may be modified or de-committed by the managing entity (QosManager), in
order to allow the instantiation of the prospective traffic flow. The policy information used for making decisions
is AdmissionPolicy, UserImportanceNumber and TrafficImportanceNumber.
3.2.3. Traffic Descriptor
The TrafficDescriptor is composed of a TrafficId and other pertinent information that must be provided by the
Control Point. It is the representation of a traffic stream for purposes of providing QoS. Once the
QosPolicyHolder returns a policy, or if the QoS Management Entity uses a default policy, this policy information
is placed into the TrafficDescriptor by the QosManager before setting up QoS on each QosDevice. This
information in the TrafficDescriptor may later be used for diagnostic purposes. The QosDevice service must
store the traffic descriptors of the traffics that have been successfully set up.
– 14 – 29341-11-1 © ISO/IEC:2008(E)
4. UPnP QoS Services
4.1. QosPolicyHolder Service
4.1.1. Role
The UPnP QosPolicyHolder Service is a repository of QoS policies for Home Network. These QoS Policies can
be configured by the user or a third party on behalf of the user to indicate the treatment of traffic on the Home
Network. The QosPolicyHolder Service provides a UPnP-defined interface for a QosManager to access the
Home Network QoS policies. The Policy within the QosPolicyHolder Service is populated in a non-specified
manner that is out of scope for the UPnP QoS specifications. For example, methods such as an HTML GUI or
other vendor dependent applications may be used.
The main function of this service is to judiciously allocate the use of traffic importance numbers by applications
so that traffic importance levels are not overused. In a prioritized system the traffic importance number is mapped
into a priority and if a given priority were overused, it would essentially loose differentiation. QosPolicyHolder
also provides additional information[QPH] to identify the source of the QoS policy.
4.1.2. Traffic Stream QoS Policy Description
The QoS traffic policy consists of three QoS-specific elements, namely AdmissionPolicy (a Boolean value),
TrafficImportanceNumber (an integer in the range of 0-7), and UserImportanceNumber (an integer in the range
of 0-255). In addition, QosPolicyHolder also provides 4 optional parameters (PolicyHolderId,
PolicyLastModified, PolicyModifyingUserName, PolicyHolderConfigUrl) that are used for identifying the source
of the QoS policy.
If a QosPolicyHolder administrator chooses to set AdmissionPolicy (enabled/disabled) to “enabled”, the
QosManager enforces admission policy for the traffic streams being setup.
The TrafficImportanceNumber indicates a traffic stream’s relative importance priority as described in Section
3.1.
The UserImportanceNumber will be used by the QosManager as the basis for admission policy decisions when
the network resources are saturated. The UserImportanceNumber allows the QosManager to admit new requests
or revoke previous requests so that the traffic streams with higher UserImportanceNumber are accommodated
first. This value allows users the ability to fine tune their preferences for particular types of traffic streams that
otherwise might have had the same TrafficImportanceNumber. The UserImportanceNumber value is applicable
only when AdmissionPolicy is “enabled”. The value of 255 indicates highest importance and the value 0
indicates lowest importance. In the case where two or more traffic streams have the same
UserImportanceNumber value, a first come first serve policy is applied to them.
The PolicyHolderId uniquely identifies the QosPolicyHolder in the home network. PolicyLastModified indicates
when the policy was last modified, while the PolicyModifyingUserName identifies the home user or other entity
that modified the policy last time. PolicyHolderConfigUrl points to the policy configuration page of the device
The QosPolicyHolder Service provides an interface to retrieve the QoS policy for a given traffic stream,
described by the TrafficDescriptor. Although the UPnP QoS 1.0 architecture only allows a single policy holder
in the home network, the 2.0 version allows the existence of multiple policy holders. The Control Point
optionally supplies a QosPolicyHolder of its choice to the QosManager. The behavior of QosManager (version
1.0 or 2.0 when the Control Point does not select a QosPolicyHolder), when there are multiple or zero
QosPolicyHolder Services in the home network, is described in section 4.2 (QoS Manager).
29341-11-1 © ISO/IEC:2008(E) – 15 –
4.2. QoS Manager
4.2.1. Role
QosManager Interface
QoS Manager
QoS Manager Service
QoS Management Entity
Control Point Interface to QosDevice
Service and QoS Policy Holder Service
Figure 2 – QoS Manager function and interfaces
The QoS Manager function is an essential part of the UPnP QoS architecture. This function is a combination of a
QosManager Service and a QoS Management Entity as shown in Figure 2. The QoS Management Entity provides
Control Point functionality that discovers and controls QosDevice services and the QosPolicyHolder Services
running on the network. The QoS Management Entity is responsible for requesting and releasing the QoS
assigned to various network traffic streams. The interface between the QoS Management Entity and the
QosManager Service is device dependent and not defined by the UPnP QoS specifications.
In the remainder of the document the term “QosManager” may be used to refer to the QosManager Service or the
QoS Management Entity or the collective functionality.
4.2.2. Behavior
When
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...