Information technology -- UPnP Device Architecture

ISO/IEC 29341-4-11:2011(E) describes the service-type which enables modeling of streaming capabilities of A/V devices, and binding of those capabilities between devices. Each device that is able to send or receive a stream according to the UPnP AV Architecture will have 1 instance of the ConnectionManager service. This service provides a mechanism for control points to: a) Perform capability matching between source/server devices and sink/renderer devices, b) Find information about currently ongoing transfers in the network, c) Setup and teardown connections between devices (when required by the streaming protocol). This service definition is compliant with the UPnP Device Architecture version 1.0. This International Standard replaces ISO/IEC 29341-4-11, first edition, published in 2008, and constitutes a technical revision.

Technologies de l'information -- Architecture de dispositif UPnP

General Information

Status
Published
Publication Date
14-Sep-2011
Current Stage
9020 - International Standard under periodical review
Start Date
15-Oct-2021
Ref Project

RELATIONS

Buy Standard

Standard
ISO/IEC 29341-4-11:2011 - Information technology -- UPnP Device Architecture
English language
43 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

ISO/IEC 29341-4-11
Edition 2.0 2011-09
INTERNATIONAL
STANDARD
colour
inside
Information technology – UPnP device architecture
Part 4-11: Audio Video Device Control Protocol – Level 2 – Connection Manager
Service
ISO/IEC 29341-4-11:2011(E)
---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2011 ISO/IEC, Geneva, Switzerland

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
---------------------- Page: 2 ----------------------
ISO/IEC 29341-4-11
Edition 2.0 2011-09
INTERNATIONAL
STANDARD
colour
inside
Information technology – UPnP device architecture
Part 4-11: Audio Video Device Control Protocol – Level 2 – Connection Manager
Service
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
ICS 35.200 ISBN 978-2-88912-681-1
---------------------- Page: 3 ----------------------
29341-4-11 © ISO/IEC:2011(E)
CONTENTS

1  Overview and Scope ....................................................................................................... 3

1.1  Introduction ........................................................................................................... 3

1.2  Notation ................................................................................................................ 3

1.2.1  Data Types ................................................................................................ 4

1.2.2  Strings Embedded in Other Strings ............................................................ 4

1.2.3  Extended Backus-Naur Form ..................................................................... 4

1.3  Derived Data Types ............................................................................................... 5

1.3.1  Comma Separated Value (CSV) Lists ......................................................... 5

1.4  Management of XML Namespaces in Standardized DCPs ...................................... 6

1.4.1  Namespace Prefix Requirements ............................................................... 9

1.4.2  Namespace Names, Namespace Versioning and Schema Versioning ....... 10

1.4.3  Namespace Usage Examples ................................................................... 12

1.5  Vendor-defined Extensions .................................................................................. 13

1.5.1  Vendor-defined Action Names .................................................................. 13

1.5.2  Vendor-defined State Variable Names ...................................................... 13

1.5.3  Vendor-defined XML Elements and attributes ........................................... 13

1.5.4  Vendor-defined Property Names .............................................................. 13

1.6  References .......................................................................................................... 13

2  Service Modeling Definitions ......................................................................................... 17

2.1  ServiceType ........................................................................................................ 17

2.2  State Variables .................................................................................................... 17

2.2.1  SourceProtocolInfo .................................................................................. 18

2.2.2  SinkProtocolInfo ...................................................................................... 18

2.2.3  CurrentConnectionIDs .............................................................................. 18

2.2.4  A_ARG_TYPE_ConnectionStatus ............................................................. 19

2.2.5  A_ARG_TYPE_ConnectionManager ......................................................... 19

2.2.6  A_ARG_TYPE_Direction .......................................................................... 19

2.2.7  A_ARG_TYPE_ProtocolInfo ..................................................................... 19

2.2.8  A_ARG_TYPE_ConnectionID ................................................................... 19

2.2.9  A_ARG_TYPE_AVTransportID ................................................................. 19

2.2.10  A_ARG_TYPE_RcsID .............................................................................. 19

2.3  Eventing and Moderation ..................................................................................... 20

2.4  Actions ................................................................................................................ 20

2.4.1  GetProtocolInfo() ..................................................................................... 20

2.4.2  PrepareForConnection() ........................................................................... 21

2.4.3  ConnectionComplete() ............................................................................. 23

2.4.4  GetCurrentConnectionIDs() ...................................................................... 24

2.4.5  GetCurrentConnectionInfo() ..................................................................... 25

2.4.6  Common Error Codes .............................................................................. 26

2.5  Theory of Operation ............................................................................................. 27

2.5.1  Purpos e ................................................................................................... 27

2.5.2  ProtocolInfo Concept ............................................................................... 27

2.5.3  Typical Control Point Operations .............................................................. 32

2.5.4  Relation to Devices without ConnectionManager s..................................... 33

2.5.5  PrepareForConnection() and ConnectionComplete() ................................. 33

---------------------- Page: 4 ----------------------

XXXX: © IEC:2010 — 2 — — 2 — 29341-4-11 29341-4-11 © ISO/IEC:2011(E)© ISO/IEC:2011(E)

3  XML Service Description .............................................................................................. 36

4  Test .......................................................................................................................... ... 39

Annex A (normative) Protocol Specifics ............................................................................... 40

A.1  Application to HTTP Streaming ............................................................................ 40

A.1.1  ProtocolInfo Defini tion .............................................................................. 40

A.1.2  Implementation of PrepareForConnection() .............................................. 40

A.1.3  Implementation of ConnectionComplete() ................................................. 40

A.1.4  Automatic Connection Cleanup ................................................................ 40

A.2  Application to RTSP/RTP/UDP Streaming ............................................................ 41

A.2.1  ProtocolInfo Defini tion .............................................................................. 41

A.2.2  Implementation of PrepareForConnection() .............................................. 41

A.2.3  Implementation of ConnectionComplete() ................................................. 41

A.2.4  Automatic Connection Cleanup ................................................................ 41

A.3  Application to Device-Internal Streaming .............................................................. 42

A.4  Application to IEC61883 Stream ing ...................................................................... 42

A.4.1  ProtocolInfo Defini tion .............................................................................. 42

A.4.2  Implementation of PrepareForConnection() .............................................. 43

A.4.3  Implementation of ConnectionComplete() ................................................. 44

A.4.4  Automatic Connection Cleanup ................................................................ 44

A.5  Application to Vendor-specific Streaming ............................................................. 45

Table 1-1 — EBNF Operators ............................................................................................... 5

Table 1-2 — CSV Examples .................................................................................................. 6

Table 1-3 — Namespace Definitions ..................................................................................... 8

Table 1-4 — Schema-related Information .............................................................................. 9

Table 1-5 — Default Namespaces for the AV Specifications ................................................ 10

Table 2-6 — State Variables ............................................................................................... 17

Table 2-7 — Event Moderat ion ............................................................................................ 20

Table 2-8 — Actions ........................................................................................................... 20

Table 2-9 — Arguments for GetProtocolInfo() ...................................................................... 20

Table 2-10 — Arguments for PrepareForConnection() ......................................................... 22

Table 2-11 — Error Codes for PrepareForConnection() ....................................................... 23

Table 2-12 — Arguments for ConnectionComplete() ............................................................ 24

Table 2-13 — Error Codes for ConnectionComplete() .......................................................... 24

Table 2-14 — Arguments for GetCurrentConnectionIDs() .................................................... 24

Table 2-15 — Error Codes for GetCurrentConnectionIDs() .................................................. 25

Table 2-16 — Arguments for GetCurrentConnectionInfo() .................................................... 25

Table 2-17 — Error Codes for GetCurrentConnectionInfo() .................................................. 26

Table 2-18 — Common Error Codes ................................................................................... 26

Table 2-19 — Defined Protocols and their associated ProtocolInfo Values ........................... 28

Table A.1 — for Protocol IEC61883 ......................................................... 43

---------------------- Page: 5 ----------------------
29341-4-11 © ISO/IEC:2011(E)
INFORMATION TECHNOLOGY –
UPNP DEVICE ARCHITECTURE –
Part 4-11: Audio Video Device Control Protocol –
Level 2 – Connection 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.

10) Attention is drawn to the possibility that some of the elements of this International Standard may be the subject of

patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.

International Standard ISO/IEC 29341-4-11 was prepared by UPnP Forum Steering
committee , was adopted, under the fast track procedure, by subcommittee 25:

Interconnection of information technology equipment, of ISO/IEC joint technical committee 1:

Information technology.

This International Standard replaces ISO/IEC 29341-4-11, first edition, published in 2008, and

constitutes a technical revision.

The list of all currently available parts of the ISO/IEC 29341 series, under the general title

Information technology – UPnP device 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.
—————————

UPnP Forum Steering committee, UPnP Forum, 3855 SW 153 Drive, Beaverton, Oregon 97006 USA. See also

“Introduction”.
---------------------- Page: 6 ----------------------
29341-4-11 © ISO/IEC:2011(E)

IMPORTANT – The “colour inside” logo on the cover page of this publication indicates

that it contains colours which are considered to be useful for the correct understanding

of its contents. Users should therefore print this publication using a colour printer.

---------------------- Page: 7 ----------------------
29341-4-11 XXXX: © IEC:2010 © ISO/IEC:2011(E) — 3 —
1 Overview and Scope
1.1 Introduction

This service definition is compliant with the UPnP Device Architecture version 1.0.

This service-type enables modeling of streaming capabilities of A/V devices, and binding of

those capabilities between devices. Each device that is able to send or receive a stream

according to the UPnP AV Architecture will have 1 instance of the ConnectionManager

service. This service provides a mechanism for control points to:

a) Perform capability matching between source/server devices and sink/renderer devices,

b) Find information about currently ongoing transfers in the network,

c) Setup and teardown connections between devices (when required by the streaming

protocol).

The ConnectionManager service is generic enough to properly abstract different kinds of

streaming mechanisms, such as HTTP-based streaming, RTSP/RTP-based and 1394-based

streaming.

The ConnectionManager enables control points to abstract from physical media interconnect

technology when making connections. The term ‘stream’ used in this service template refers

to both analog and digital data transfer.
1.2 Notation

• In this document, features are described as Required, Recommended, or Optional as

follows:
The keywords “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 prohibited by 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 specification are printed

using the arch character style [DEVICE].

• 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.
---------------------- Page: 8 ----------------------
XXXX: © IEC:2010 — 4 — 29341-4-11 © ISO/IEC:2011(E)
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 boolean 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 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 Clause 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:
---------------------- Page: 9 ----------------------
29341-4-11 XXXX: © IEC:2010 © ISO/IEC:2011(E) — 5 —
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.
1.3 Derived Data Types

This clause 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 type of a heterogeneous list is also string or xsd:string and

denoted by CSV (x, y, z), where x, y and z are the types of the individual values. If the

number of values in the heterogeneous list is too large to show each type individually, that

variable type is represented as CSV (heterogeneous), and the variable description includes

additional information as to the expected sequence of values appearing in the list and their

corresponding types. The data type of a repeated subsequence list is string or xsd:string and

denoted by CSV ({x, y, z}), where x, y and z are the types of the individual values in the

subsequence and the subsequence MAY be repeated zero or more times.

• A list is represented as a string type (for state variables and action arguments) or

xsd:string type (for properties).
• Commas separate values within a list.

• Integer values are represented in CSVs with the same syntax as the integer data type

specified in [DEVICE] (that is: optional leading sign, optional leading zeroes, numeric US-

ASCII)

• Boolean values are represented in state variable and action argument CSVs as either “0”

for false or “1” for true. These values are a subset of the defined boolean data type

values specified in [DEVICE]: 0, false, no, 1, true, yes.

• Boolean values are represented in property CSVs as either “0” for false or “1” for true.

These values are a subset of the defined Boolean data type values specified in [XML

SCHEMA-2]: 0, false, 1, true.

• Escaping conventions for the comma and backslash characters are defined in Clause

1.2.2, “Strings Embedded in Other Strings”.
---------------------- Page: 10 ----------------------
XXXX: © IEC:2010 — 6 — 29341-4-11 © ISO/IEC:2011(E)

• White space before, after, or interior to any numeric data type is not allowed.

• White space before, after, or interior to any other data type is part of the value.

Table 1-2 — CSV Examples
Type refinement of Value Comments
string
CSV (string) or “+artist,-date” List of 2 property sort
CSV (xsd:string) criteria.
CSV (int) or “1,-5,006,0,+7” List of 5 integers.
CSV (xsd:integer)
CSV (boolean) or “0,1,1,0” List of 4 booleans
CSV (xsd:Boolean)
CSV (string) or “Smith\, Fred,Jones\, Davey” List of 2 names,
“Smith, Fred” and
CSV (xsd:string)
“Jones, Davey”
“-29837, string with leading blanks,0” Note that the second value
CSV (i4,string,ui2) or
is “ string with leading
CSV (xsd:int,
xsd:string, blanks”
xsd:unsignedShort)
CSV (i4) or “3, 4” Illegal CSV. White space
CSV (xsd:int) is not allowed as part of
an integer value.
CSV (string) or “,,” List of 3 empty string
CSV (xsd:string) values

CSV (heterogeneous) “Alice,Marketing,5,Sue,R&D,21,Dave,Finance,7” List of unspecified number

of people and associated
attributes. Each person is
described by 3 elements:
a name string, a
department string and
years-of-service ui2 or a
name xsd:string, a
department xsd:string and
years-of-service
xsd:unsignedShort.
1.4 Management of XML Namespaces in Standardized DCPs

UPnP specifications make extensive use of XML namespaces. This allows separate DCPs,

and even separate components of an individual DCP, to be designed independently and still

avoid name collisions when they share XML documents. Every name in an XML document

belongs to exactly one namespace. In documents, XML names appear in one of two forms:

qualified or unqualified. An unqualified name (or no-colon-name) contains no colon (“:”)

characters. An unqualified name belongs to the document’s default namespace. A qualified

name is two no-colon-names separated by one colon character. The no-colon-name before

the colon is the qualified name’s namespace prefix, the no-colon-name after the colon is the

qualified name’s “local” name (meaning local to the namespace identified by the namespace

prefix). Similarly, the unqualified name is a local name in the default namespace.

The formal name of a namespace is a URI. The namespace prefix used in an XML document

is not the name of the namespace. The namespace name is, or should be, globally unique. It

has a single definition that is accessible to anyone who uses the namespace. It has the same

meaning anywhere that it is used, both inside and outside XML documents. The namespace

prefix, however, in formal XML usage,
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.