Information technology - UPnP Device Architecture - Part 4-2: Audio Video Device Control Protocol - Level 2 - Media Renderer Device

ISO/IEC 29341-4-2:2011(E) The MediaRenderer specification defines a general-purpose device template that can be used to instantiate any Consumer Electronics (CE) device that is capable of rendering AV content from the home network. It exposes a set of rendering controls in which a control point can control how the specified AV content is rendered. This includes controlling various rendering features such as brightness, contrast, volume, etc. This device specification is compliant with the Universal Plug and Play Device Architecture version 1.0. It defines a device type referred to herein as MediaRenderer. This International Standard replaces ISO/IEC 29341-4-2, first edition, published in 2008, and constitutes a technical revision.

General Information

Status
Published
Publication Date
14-Sep-2011
Current Stage
PPUB - Publication issued
Start Date
31-Jan-2012
Completion Date
14-Sep-2011
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 29341-4-2:2011 - Information technology - UPnP device architecture - Part 4-2: Audio Video Device Control Protocol - Level 2 - Media Renderer Device
English language
20 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


ISO/IEC 29341-4-2
Edition 2.0 2011-09
INTERNATIONAL
STANDARD
colour
inside
Information technology –UPnP device architecture –
Part 4-2: Audio Video Device Control Protocol – Level 2 – Media Renderer Device

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-2
Edition 2.0 2011-09
INTERNATIONAL
STANDARD
colour
inside
Information technology –UPnP device architecture –
Part 4-2: Audio Video Device Control Protocol – Level 2 – Media Renderer Device

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
K
ICS 35.200 ISBN 978-2-88912-678-1

29341-4-2 XXX: © IEC:2010 © ISO/IEC:2011(E) — 1 —
CONTENTS
1  Overview and Scope . 2
1.1  Introduction . 2
1.2  Notation . 3
1.2.1  Data Types . 3
1.2.2  Strings Embedded in Other Strings . 3
1.2.3  Extended Backus-Naur Form . 4
1.3  Derived Data Types . 4
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  Device Definitions . 17
2.1  Device Type . 17
2.2  Device Model . 17
2.2.1  Description of Device Requireme nts . 17
2.2.2  Relationships Between Services . 18
2.3  Theory of Operation . 18
2.3.1  Device Discovery . 19
2.3.2  Preparing to Transfer the Content . 19
2.3.3  Controlling the Transfer of the Co ntent . 19
2.3.4  Controlling How the Content is Rendered . 19
3  XML Device Description . 20
4  Test . . 21

Figure 1 — MediaRenderer Functional Diagram . 2

Table 1-1 — EBNF Operators . 4
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 — Device Requirem ents . 17

29341-4-2 © ISO/IEC:2011(E)
INFORMATION TECHNOLOGY –
UPNP DEVICE ARCHITECTURE –
Part 4-2: Audio Video Device Control Protocol –
Level 2 – Media Renderer Device
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-2 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-2, 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.
—————————
rd
UPnP Forum Steering committee, UPnP Forum, 3855 SW 153 Drive, Beaverton, Oregon 97006 USA. See also
“Introduction”.
29341-4-2 © 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.

XXX: © IEC:2010 — 2 — 29341-4-2 © ISO/IEC:2011(E)
1 Overview and Scope
1.1 Introduction
This device specification is compliant with the Universal Plug and Play Device Architecture
version 1.0. It defines a device type referred to herein as MediaRenderer.
The MediaRenderer specification defines a general-purpose device template that can be
used to instantiate any Consumer Electronics (CE) device that is capable of rendering AV
content from the home network. It exposes a set of rendering controls in which a control point
can control how the specified AV content is rendered. This includes controlling various
rendering features such as brightness, contrast, volume, etc.
Example instances of a MediaRenderer include traditional devices such as TVs and stereo
systems. Some more contemporary examples include digital devices such as MP3 players
and Electronic Picture Frames (EPFs). Although most of these examples typically render one
specific type of content (for example, a TV typically renders video content), a MediaRenderer
is able to support a number of different data formats and transfer protocols. For example, a
sophisticated implementation of a TV MediaRenderer could also support MP3 data so that its
speakers could be used to play MP3 audio content.
The MediaRenderer device specification is very lightweight and is easy to implement on low-
resource devices such as an MP3 player. However, it can also be used to expose the high-
end capabilities of devices such as a PC.
A full-featured MediaRenderer exposes the following capabilities:
• Control various rendering characteristics
• Expose the supported transfer protocols and data formats
• Control the flow of the content (for example, FF, REW, etc), if appropriate depending on
the transfer protocol.

The MediaRenderer DOES NOT enable control points to:
• Send AV content to another device
• Retrieve any type of meta-data associated with the content
From Network
Content Transfer Format Decoder Rendering
Subsystem Subsystem Hardware
AVTransport ConnectionManager RenderingControl
Service Service Service
(Optional) (Required) (Required)
MediaRenderer
Figure 1 — MediaRenderer Functional Diagram
The un-shaded blocks represent the UPnP services that are contained by a MediaRenderer.
The shaded blocks represent various device-specific modules that the UPnP services might

29341-4-2 XXX: © IEC:2010 © ISO/IEC:2011(E) — 3 —
interact with. However, the internal architecture of a MediaRenderer device is vendor
specific.
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 REQUI
...

Questions, Comments and Discussion

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