ISO/IEC 29341-4-10:2008

ISO/IEC 29341-4-10
Edition 1.0 2008-11
INTERNATIONAL
STANDARD
Information technology – UPnP Device Architecture –
Part 4-10: Audio Video Device Control Protocol –
Level 2 – Audio Video Transport 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: 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-4-10
Edition 1.0 2008-11
INTERNATIONAL
STANDARD
Information technology – UPnP Device Architecture –
Part 4-10: Audio Video Device Control Protocol –
Level 2 – Audio Video Transport Service
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
X
ICS 35.200 ISBN 978-2-88910-852-7

– 2 – 29341-4-10 © ISO/IEC:2008(E)
CONTENTS
FOREWORD .7
ORIGINAL UPNP DOCUMENTS (informative) .9
1 Overview and Scope.11
1.1 Introduction.11
1.2 Notation .11
1.2.1 Data Types.11
1.2.2 Strings Embedded in Other Strings.12
1.2.3 Extended Backus-Naur Form.12
1.3 Derived Data Types.13
1.3.1 Comma Separated Value (CSV) Lists .13
1.4 Management of XML Namespaces in Standardized DCPs.14
1.4.1 Namespace Prefix Requirements .17
1.4.2 Namespace Names, Namespace Versioning and Schema Versioning.18
1.4.3 Namespace Usage Examples.19
1.5 Vendor-defined Extensions .19
1.6 References .20
2 Service Modeling Definitions.23
2.1 ServiceType.23
2.2 State Variables .23
2.2.1 TransportState .28
2.2.2 TransportStatus.28
2.2.3 CurrentMediaCategory.28
2.2.4 PlaybackStorageMedium .29
2.2.5 RecordStorageMedium .29
2.2.6 PossiblePlaybackStorageMedia.29
2.2.7 PossibleRecordStorageMedia.29
2.2.8 CurrentPlayMode .29
2.2.9 TransportPlaySpeed .29
2.2.10 RecordMediumWriteStatus .29
2.2.11 CurrentRecordQualityMode .29
2.2.12 PossibleRecordQualityModes.30
2.2.13 NumberOfTracks.30
2.2.14 CurrentTrack .30
2.2.15 CurrentTrackDuration.30
2.2.16 CurrentMediaDuration.31
2.2.17 CurrentTrackMetaData.31
2.2.18 CurrentTrackURI.31
2.2.19 AVTransportURI.31
2.2.20 AVTransportURIMetaData .31
2.2.21 NextAVTransportURI .31
2.2.22 NextAVTransportURIMetaData.32
2.2.23 RelativeTimePosition .32
2.2.24 AbsoluteTimePosition .32
2.2.25 RelativeCounterPosition.32
2.2.26 AbsoluteCounterPosition.33
2.2.27 CurrentTransportActions.33

29341-4-10 © ISO/IEC:2008(E) – 3 –
2.2.28 LastChange.33
2.2.29 DRMState.33
2.2.30 A_ARG_TYPE_SeekMode .34
2.2.31 A_ARG_TYPE_SeekTarget.34
2.2.32 A_ARG_TYPE_InstanceID .34
2.2.33 A_ARG_TYPE_DeviceUDN.34
2.2.34 A_ARG_TYPE_ServiceType.35
2.2.35 A_ARG_TYPE_ServiceID.35
2.2.36 A_ARG_TYPE_StateVariableValuePairs.35
2.2.37 A_ARG_TYPE_StateVariableList .35
2.3 Eventing and Moderation.36
2.3.1 Event Model .37
2.4 Actions.38
2.4.1 SetAVTransportURI().39
2.4.2 SetNextAVTransportURI().41
2.4.3 GetMediaInfo() .43
2.4.4 GetMediaInfo_Ext() .44
2.4.5 GetTransportInfo().45
2.4.6 GetPositionInfo() .46
2.4.7 GetDeviceCapabilities() .47
2.4.8 GetTransportSettings().48
2.4.9 Stop() .49
2.4.10 Play().50
2.4.11 Pause().52
2.4.12 Record() .52
2.4.13 Seek().54
2.4.14 Next() .56
2.4.15 Previous().58
2.4.16 SetPlayMode() .60
2.4.17 SetRecordQualityMode().61
2.4.18 GetCurrentTransportActions().62
2.4.19 GetDRMState() .63
2.4.20 GetStateVariables().64
2.4.21 SetStateVariables() .65
2.4.22 Common Error Codes.66
2.5 Theory of Operation.68
2.5.1 TransportState Control.68
2.5.2 Transport Settings.69
2.5.3 Navigation .69
2.5.4 AVTransportURI Concept .69
2.5.5 AVTransport Abstraction.70
2.5.6 Supporting Multiple Virtual Transports.72
2.5.7 Playlist Playback .73
3 XML Service Description.74
4 Test.89
Annex A (normative) SetAVTransportURI() Protocol Specifics.90
A.1 Application to HTTP Streaming .90
A.1.1 AVTransportURI Definition.90

– 4 – 29341-4-10 © ISO/IEC:2008(E)
A.1.2 Control Point Behavior for SetAVTransportURI().90
A.1.3 Implementation of SetAVTransportURI() .90
A.1.4 Cleanup.90
A.2 Application to RTSP/RTP/UDP Streaming .90
A.2.1 AVTransportURI Definition.90
A.2.2 Control Point behavior for SetAVTransportURI() .91
A.2.3 Implementation of SetAVTransportURI() .91
A.2.4 Cleanup.91
A.2.5 Implementation of Transport Controls.92
A.3 Application to Internal Streaming.92
A.3.1 AVTransportURI Definition.92
A.3.2 Implementation of SetAVTransportURI() .92
A.3.3 Cleanup.92
A.4 Application to IEC61883 Streaming.92
A.4.1 AVTransportURI Definition.92
A.4.2 Implementation of SetAVTransportURI() .92
A.4.3 Cleanup.93
A.5 Application to Vendor-specific Streaming.93
A.5.1 AVTransportURI Definition.93
A.5.2 Implementation of SetAVTransportURI() .93
A.5.3 Cleanup.93

29341-4-10 © ISO/IEC:2008(E) – 5 –
LIST OF TABLES
Table 1-1: EBNF Operators .12
Table 1-2: CSV Examples .14
Table 1-3: Namespace Definitions.16
Table 1-4: Schema-related Information .17
Table 1-5: Default Namespaces for the AV Specifications.18
Table 2-6: State Variables .23
Table 2-7: allowedValueList for TransportState.24
Table 2-8: allowedValueList for CurrentMediaCategory .24
Table 2-9: allowedValueList for PlaybackStorageMedium and RecordStorageMedium.25
Table 2-10: allowedValueList for CurrentPlayMode.26
Table 2-11: allowedValueList for RecordMediumWriteStatus .26
Table 2-12: allowedValueList for CurrentRecordQualityMode.26
Table 2-13: allowedValueRange for NumberOfTracks .26
Table 2-14: allowedValueRange for CurrentTrack .27
Table 2-15: allowedValueList for CurrentTransportActions .27
Table 2-16: allowedValueList for DRMState.27
Table 2-17: allowedValueList for A_ARG_TYPE_SeekMode.28
Table 2-18: Format of A_ARG_TYPE_SeekTarget.34
Table 2-19: Event Moderation.36
Table 2-20: Actions.38
Table 2-21: Arguments for SetAVTransportURI().39
Table 2-22: Error Codes for SetAVTransportURI().40
Table 2-23: Arguments for SetNextAVTransportURI() .41
Table 2-24: Error Codes for SetNextAVTransportURI() .41
Table 2-25: Arguments for GetMediaInfo().43
Table 2-26: Error Codes for GetMediaInfo().43
Table 2-27: Arguments for GetMediaInfo_Ext().44
Table 2-28: Error Codes for GetMediaInfo_Ext().44
Table 2-29: Arguments for GetTransportInfo() .45
Table 2-30: Error Codes for GetTransportInfo() .45
Table 2-31: Arguments for GetPositionInfo().46
Table 2-32: Error Codes for GetPositionInfo().46
Table 2-33: Arguments for GetDeviceCapabilities() .47
Table 2-34: Error Codes for GetDeviceCapabilities() .47
Table 2-35: Arguments for GetTransportSettings() .48
Table 2-36: Error Codes for GetTransportSettings() .48
Table 2-37: Arguments for Stop() .49
Table 2-38: Error Codes for Stop() .49
Table 2-39: Arguments for Play().50

– 6 – 29341-4-10 © ISO/IEC:2008(E)
Table 2-40: Error Codes for Play().51
Table 2-41: Arguments for Pause() .52
Table 2-42: Error Codes for Pause() .52
Table 2-43: Arguments for Record().53
Table 2-44: Error Codes for Record().53
Table 2-45: Arguments for Seek() .54
Table 2-46: Error Codes for Seek() .55
Table 2-47: Arguments for Next() .56
Table 2-48: Error Codes for Next() .57
Table 2-49: Arguments for Previous() .58
Table 2-50: Error Codes for Previous().59
Table 2-51: Arguments for SetPlayMode() .60
Table 2-52: Error Codes for SetPlayMode() .60
Table 2-53: Arguments for SetRecordQualityMode() .61
Table 2-54: Error Codes for SetRecordQualityMode() .61
Table 2-55: Arguments for GetCurrentTransportActions() .62
Table 2-56: Error Codes for GetCurrentTransportActions() .62
Table 2-57: Arguments for GetDRMState() .63
Table 2-58: Error Codes for GetDRMState() .63
Table 2-59: Arguments for GetStateVariables() .64
Table 2-60: Error Codes for GetStateVariables() .64
Table 2-61: Arguments for SetStateVariables().65
Table 2-62: Error Codes for SetStateVariables().65
Table 2-63: Common Error Codes .66
Table 2-64: Allowed AVTransportURIs.70
Table 2-65: Example mappings of resources type to track sequences.70
Table 2-66: Example seek modes, play modes and transport actions, per resource type.71

LIST OF FIGURES
Figure 1: TransportState Transitions - INFORMATIVE .68

29341-4-10 © ISO/IEC:2008(E) – 7 –
INFORMATION TECHNOLOGY –
UPNP DEVICE ARCHITECTURE –
Part 3-1: Audio Video Device Control Protocol – Level 2 –
Audio Video Transport 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:

– 8 – 29341-4-10 © ISO/IEC:2008(E)
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-4-10 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.

29341-4-10 © ISO/IEC:2008(E) – 9 –
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

– 10 – 29341-4-10 © ISO/IEC:2008(E)
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

29341-4-10 © ISO/IEC:2008(E) – 11 –
1 Overview and Scope
1.1 Introduction
This service definition is compliant with the UPnP Device Architecture version 1.0.
This service type enables control over the transport of audio and video streams. The service type defines a
common model for A/V transport control suitable for a generic user interface. It can be used to control a wide
variety of disc, tape and solid-state based media devices such as CD players, VCRs and MP3 players. A minimal
implementation of this service can be used to control tuners.
The service type is related to the ConnectionManager service type, which describes A/V connection setup
procedures, and the ContentDirectory service, which offers meta-information about the resource stored on the
media. AVTransport also offers an action to retrieve any meta-data embedded in the resource itself.
This service type does not offer scheduled recording.
1.2 Notation
• In this document, features are described as Required, Recommended, or Optional as follows:
The key words “MUST,” “MUST NOT,” “REQUIRED,” “SHALL,” “SHALL NOT,” “SHOULD,”
“SHOULD NOT,” “RECOMMENDED,” “MAY,” and “OPTIONAL” in this specification are to be
interpreted as described in [RFC 2119].
In addition, the following keywords are used in this specification:
PROHIBITED – The definition or behavior is an absolute prohibition of this specification. Opposite of
REQUIRED.
CONDITIONALLY REQUIRED – The definition or behavior depends on a condition. If the specified
condition is met, then the definition or behavior is REQUIRED, otherwise it is PROHIBITED.
CONDITIONALLY OPTIONAL – The definition or behavior depends on a condition. If the specified
condition is met, then the definition or behavior is OPTIONAL, otherwise it is PROHIBITED.
These keywords are thus capitalized when used to unambiguously specify requirements over protocol
and application features and behavior that affect the interoperability and security of implementations.
When these words are not capitalized, they are meant in their natural-language sense.
• Strings that are to be taken literally are enclosed in “double quotes”.
• Words that are emphasized are printed in italic.
• Keywords that are defined by the UPnP AV Working Committee are printed using the forum character
style.
• Keywords that are defined by the UPnP Device Architecture are printed using the arch character style.
• A double colon delimiter, “::”, signifies a hierarchical parent-child (parent::child) relationship between
the two objects separated by the double colon. This delimiter is used in multiple contexts, for example:
Service::Action(), Action()::Argument, parentProperty::childProperty.
1.2.1 Data Types
This specification uses data type definitions from two different sources. The UPnP Device Architecture defined
data types are used to define state variable and action argument data types [DEVICE]. The XML Schema
namespace is used to define property data types [XML SCHEMA-2].
For UPnP Device Architecture defined Boolean data types, it is strongly RECOMMENDED to use the value “0”
for false, and the value “1” for true. However, when used as input arguments, the values “false”, “no”, “true”,
“yes” may also be encountered and MUST be accepted. Nevertheless, it is strongly RECOMMENDED that all
state variables and output arguments be represented as “0” and “1”.
For XML Schema defined Boolean data types, it is strongly RECOMMENDED to use the value “0” for false,
and the value “1” for true. However, when used as input properties, the values “false”, “true” may also be

– 12 – 29341-4-10 © ISO/IEC:2008(E)
encountered and MUST be accepted. Nevertheless, it is strongly RECOMMENDED that all properties be
represented as “0” and “1”.
1.2.2 Strings Embedded in Other Strings
Some string variables and arguments described in this document contain substrings that MUST be independently
identifiable and extractable for other processing. This requires the definition of appropriate substring delimiters
and an escaping mechanism so that these delimiters can also appear as ordinary characters in the string and/or its
independent substrings. This document uses embedded strings in two contexts – Comma Separated Value (CSV)
lists (see Section 1.3.1, “Comma Separated Value (CSV) Lists”) and property values in search criteria strings.
Escaping conventions use the backslash character, “\” (character code U+005C), as follows:
a. Backslash (“\”) is represented as “\\” in both contexts.
b. Comma (“,”) is
1. represented as “\,” in individual substring entries in CSV lists
2. not escaped in search strings
c. Double quote (“””) is
1. not escaped in CSV lists
2. not escaped in search strings when it appears as the start or end delimiter of a property value
3. represented as “\”” in search strings when it appears as a character that is part of the property value
1.2.3 Extended Backus-Naur Form
Extended Backus-Naur Form is used in this document for a formal syntax description of certain constructs. The
usage here is according to the reference [EBNF].
1.2.3.1 Typographic conventions for EBNF
Non-terminal symbols are unquoted sequences of characters from the set of English upper and lower case
letters, the digits “0” through “9”, and the hyphen (“-”).  Character sequences between 'single quotes'
are terminal strings and MUST appear literally in valid strings. Character sequences between (*comment
delimiters*) are English language definitions or supplementary explanations of their associated symbols.
White space in the EBNF is used to separate elements of the EBNF, not to represent white space in valid strings.
White space usage in valid strings is described explicitly in the EBNF. Finally, the EBNF uses the following
operators:
Table 1-1: EBNF Operators
Operator Semantics
::=
definition – the non-terminal symbol on the left is defined by one or more alternative
sequences of terminals and/or non-terminals to its right.
|
alternative separator – separates sequences on the right that are independently allowed
definitions for the non-terminal on the left.
*
null repetition – means the expression to its left MAY occur zero or more times.
+
non-null repetition – means the expression to its left MUST occur at least once and MAY
occur more times.
[ ]
optional – the expression between the brackets is optional.
( )
grouping – groups the expressions between the parentheses.
-
character range – represents all characters between the left and right character operands
inclusively.
29341-4-10 © ISO/IEC:2008(E) – 13 –
1.3 Derived Data Types
This section defines a derived data type that is represented as a string data type with special syntax. This
specification uses string data type definitions that originate from two different sources. The UPnP Device
Architecture defined string data type is used to define state variable and action argument string data types. The
XML Schema namespace is used to define property xsd:string data types. The following definition applies to
both string data types.
1.3.1 Comma Separated Value (CSV) Lists
The UPnP AV services use state variables, action arguments and properties that represent lists – or one-
dimensional arrays – of values. The UPnP Device Architecture, Version 1.0 [DEVICE], does not provide for
either an array type or a list type, so a list type is defined here. Lists MAY either be homogeneous (all values are
the same type) or heterogeneous (values of different types are allowed). Lists MAY also consist of repeated
occurrences of homogeneous or heterogeneous subsequences, all of which have the same syntax and semantics
(same number of values, same value types and in the same order). The data type of a homogeneous list is string
or xsd:string and denoted by CSV (x), where x is the type of the individual values. The data t
...