ISO/IEC 14543-5-6:2012

ISO/IEC 14543-5-6
Edition 1.0 2012-02
INTERNATIONAL
STANDARD
Information technology – Home electronic system (HES) architecture –
Part 5-6: Intelligent grouping and resource sharing for HES Class 2 and Class 3 –
Service type
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 Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland 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.

Useful links:
IEC publications search - www.iec.ch/searchpub Electropedia - www.electropedia.org
The advanced search enables you to find IEC publications The world's leading online dictionary of electronic and
by a variety of criteria (reference number, text, technical electrical terms containing more than 30 000 terms and
committee,…). definitions in English and French, with equivalent terms in
It also gives information on projects, replaced and additional languages. Also known as the International
withdrawn publications. Electrotechnical Vocabulary (IEV) on-line.

IEC Just Published - webstore.iec.ch/justpublished Customer Service Centre - webstore.iec.ch/csc
Stay up to date on all new IEC publications. Just Published If you wish to give us your feedback on this publication
details all new publications released. Available on-line and or need further assistance, please contact the
also once a month by email. Customer Service Centre: csc@iec.ch.

ISO/IEC 14543-5-6
Edition 1.0 2012-02
INTERNATIONAL
STANDARD
Information technology – Home electronic system (HES) architecture –

Part 5-6: Intelligent grouping and resource sharing for HES Class 2 and Class 3 –

Service type
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XC
ICS 35.200 ISBN 978-2-88912-900-3

– 2 – 14543-5-6  ISO/IEC:2012(E)
CONTENTS
FOREWORD . 6
INTRODUCTION . 7
1 Scope . 8
2 Normative references . 8
3 Terms, definitions, abbreviations and conventions . 8
3.1 Terms and definitions . 8
3.2 Abbreviations . 11
3.3 Conventions . 11
4 Conformance . 11
5 IGRS service overview . 12
6 Definition of service type identifier . 12
7 Standard service type list . 13
8 Basic service type specification . 15
8.1 Content index service . 15
8.1.1 Overview . 15
8.1.2 Content index service type . 15
8.1.3 Content index service attribute . 15
8.1.4 Data type of content index service . 15
8.1.5 Invocation interface set of content index service . 17
8.1.6 Content index service error code definition . 26
8.2 Connection management service . 26
8.2.1 Overview . 26
8.2.2 Connection management service type . 26
8.2.3 Reference flow of connection management service interface
invocation . 27
8.2.4 Connection management service attribute . 27
8.2.5 Connection management service data type . 28
8.2.6 Connection management service invocation interface set . 28
8.2.7 Content management service error code definition . 31
8.3 Media server transport management service . 31
8.3.1 Overview . 31
8.3.2 Media server transport management service type . 31
8.3.3 Reference flow of media server transport management service
interface invocation . 31
8.3.4 Media server transport management service attribute . 32
8.3.5 Media server transport management service data type . 32
8.3.6 Media server transport management service invocation interface set . 33
8.3.7 Media server transport management service error code definition . 38
8.4 Media client transport management service . 38
8.4.1 Overview . 38
8.4.2 Media client transport management service type . 39
8.4.3 Reference flow of media client transport management service interface
invocation . 39
8.4.4 Media client transport management service attribute . 39
8.4.5 Media client transport management service data type . 40

14543-5-6  ISO/IEC:2012(E) – 3 –
8.4.6 Media client transport management service invocation interface set . 42
8.4.7 Media client transport management service error code definition . 49
8.5 Rendering management service . 49
8.5.1 Overview . 49
8.5.2 Rendering management service type . 49
8.5.3 Rendering management service attribute . 49
8.5.4 Rendering management service data type . 49
8.5.5 Rendering management service invocation interface set . 50
8.5.6 Rendering management service error code definition . 58
8.6 File access management service . 58
8.6.1 Overview . 58
8.6.2 File access managemet service type . 58
8.6.3 Reference flow of FAMS interface invocation . 59
8.6.4 File access management service attribute . 60
8.6.5 File access management service data type . 60
8.6.6 File access management service invocation interface set . 61
8.6.7 File access management service error codes definition . 72
8.7 File connection management service . 72
8.7.1 Overview . 72
8.7.2 File connection management service type . 72
8.7.3 Reference flow of file connection management service interface
invocation . 73
8.7.4 File connection management service attribute . 73
8.7.5 File connection management service data type . 74
8.7.6 File connection management service invocation inteface set . 74
8.7.7 File connection management service error codes definition . 76
9 Back channel message TCP service . 76
9.1 Overview of Back channel message . 76
9.2 Interaction flow of back channel message TCP service in audio/video playback
application . 77
9.3 Interaction flow of back channel message TCP service in an audio/video
multicast playback application . 77
9.4 BCM request message format definition . 78
9.4.1 General . 78
9.4.2 Connection management message . 78
9.4.3 Content selection message . 79
9.4.4 Transport control message . 79
9.5 BCM response message format definition . 80
Annex A (normative) Content representation framework of
an IGRS AV content directory . 82
A.1 Overview . 82
A.2 IGRS metadata specification . 83
A.2.1 IGRS metadata definition . 83
A.2.2 Metadata of item object . 84
A.2.3 Metadata of container object . 88
A.2.4 Interface for vendor defined metadata . 92
A.2.5 Extension point for the next version’s metadata definition . 92
Annex B (normative) Specific description of metadata definitions . 94
B.1 Basic metadata of item objects . 94

– 4 – 14543-5-6  ISO/IEC:2012(E)
B.2 Metadata of a specific item object . 99
B.3 Basic metadata of the container object . 109
B.4 Metadata of specific container object . 110
Annex C (normative) Specific description of data type generation rules . 114
C.1 Type_ObjectId . 114
C.2 Type_ContentList . 114
C.3 Type_FilterRule . 115
C.4 Type_SortRule . 115
C.5 Type_URI . 116
C.6 Type_MediaFormat . 116
C.7 Type_UserList . 116
C.8 Type_ProtocolInfo . 116
C.9 Type_MediaFormatList . 117
C.10 Type_StorageMediumName . 117
C.11 Type_TransportURI . 117
C.12 Type_ItemList . 118
C.13 Type_DisplayWindowInfo . 118
C.14 Type_ObjectId in FAMS . 119
C.15 ObjectType . 119
Annex D (normative) Service type message format . 120
D.1 Universal message format for IGRS service invocation . 120
D.2 Content index service . 127
D.3 Connection management service . 139
D.4 Media server transport management service . 143
D.5 Media client transport management service . 154
D.6 Rendering management service . 167
D.7 File access management service . 182
D.8 File connection management service . 194
Annex E (normative) IGRS XML schema files . 197
E.1 igrs-cis-dt.xsd . 197
E.2 igrs-cis-framework.xsd . 197
E.3 igrs-cis-metadata-base.xsd . 198
E.4 igrs-cis-metadata-container.xsd . 200
E.5 igrs-cis-metadata-item.xsd . 203
Annex F (normative) Connection management service description.wsdl . 211
Annex G (normative) Content index service description.wsdl . 217
Annex H (normative) Media client transport management service description.wsdl . 234
Annex I (normative) Media server transport management service description.wsdl . 251
Annex J (normative) Rendering management service description.wsdl . 265
Annex K (informative) XML string example . 285
Bibliography . 286

Figure 1 – Connection establishment and release flow . 27

14543-5-6  ISO/IEC:2012(E) – 5 –
Figure 2 – Transport control flow . 31
Figure 3 – Transport control flow . 39
Figure 4 – File access flow . 59
Figure 5 – Connection establishment and release flow . 73
Figure 6 – Interaction flow of back channel message TCP service in audio/video playback
application . 77
Figure 7 – Basic BCM request message format . 78
Figure A.1 – An illustrative example of the structure of an IGRS content directory . 82

Table 1 – Basic service type list . 14
Table 2 – Service attribute of content index service . 15
Table 3 – Data type of content index service . 16
Table 4 – Service attribute of connection management service . 27
Table 5 – Data type of connection management service. 28
Table 6 – Service attribute of media server transport management service . 32
Table 7 – Data type of media server transport management service . 33
Table 8 – Service attribute of media client transport management service . 39
Table 9 – Data type of media client transport management service . 41
Table 10 – Service attribute of rendering management service . 49
Table 11 – Data type of rendering management service . 50
Table 12 – Service attribute list of file access management service . 60
Table 13 – Data type of file access management service . 61
Table 14 – Service attribute of file connection management service. 73
Table 15 – Data type of file connection management service . 74
Table 16 – Error definitions . 81
Table D.1 – IGRS service invocation request message . 120
Table D.2 – Service invocation response message . 121
Table D.3 – Content directory object update notification message . 122
Table D.4 – File/directory object update notification message . 124
Table D.5 – Service attribute update notification message . 126

– 6 – 14543-5-6  ISO/IEC:2012(E)
INFORMATION TECHNOLOGY –
HOME ELECTRONIC SYSTEM (HES) ARCHITECTURE –

Part 5-6: Intelligent grouping and resource sharing for HES
Class 2 and Class 3 – Service type

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 14543-5-6 was prepared by subcommittee 25: Interconnection
of information technology equipment, of ISO/IEC joint technical committee 1: Information
technology.
The list of all currently available parts of the ISO/IEC 14543 series, under the general title
Information technology – Home electronic system (HES) 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.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.

14543-5-6  ISO/IEC:2012(E) – 7 –
INTRODUCTION
ISO/IEC 14543-5, Information technology – Home electronic system (HES) architecure –
Part 5: Intelligent Grouping and Resource Sharing for HES (IGRS), consists of six parts:
 IGRS Part 5-1: Core protocol
• Specifies the TCP/IP protocol stack as the basis and the HTTP protocol as the
message-exchanging framework among devices.
• Specifies a series of device and service interaction/invocation standards, including
device and service discovery protocol, device and service description, service
invocation, security mechanisms, etc.
• Specifies core protocols for a type of home network that supports streaming media and
other high-speed data transport within a home.
 IGRS Parts 5-2#: Application profile
• Based on the IGRS Core Protocol.
• Specifies a device and service interaction mechanism, as well as application interfaces
used in IGRS basic applications.
• Multiple application profiles are specified, including:
• Part 5-21: AV profile
• Part 5-22: File profile
• Additional application profiles are planned (part numbers to be assigned)
• Part 5-2w: DVD profile
• Part 5-2x: QoS profile
• Part 5-2y: DMCP profile
• Part 5-2z: Universal control profile
 IGRS Part 5-3: Basic application
• Includes an IGRS basic application list.
• Specifies a basic application framework.
• Specifies operation details (device grouping, service description template, etc.), function
definitions and service invocation interfaces.
 IGRS Part 5-4: Device validation
• Defines a standard method to validate an IGRS-compliant device.
 IGRS Part 5-5: Device type
• Specifies IGRS Device types used in IGRS applications.
 IGRS Part 5-6: Service type
• Specifies basic service types used in IGRS applications.

– 8 – 14543-5-6  ISO/IEC:2012(E)
INFORMATION TECHNOLOGY –
HOME ELECTRONIC SYSTEM (HES) ARCHITECTURE –

Part 5-6: Intelligent grouping and resource sharing for HES
Class 2 and Class 3 – Service type

1 Scope
This part of ISO/IEC 14543-5 specifies the service types that conform to ISO/IEC 14543-5-1.
This part of the ISO/IEC 14543 is applicable to computers, household appliances and
communication devices that implement media or data streaming in a local area network (LAN) or
personal area network (PAN) environment by wired or wireless means.
2 Normative references
The following referenced documents are indispensable for the application of this document. For
dated references, only the edition cited applies. For undated references, the latest edition of the
referenced document, including any amendments, applies.
ISO/IEC 14543-5-1:2010, Information technology – Home electronic system (HES)
architecture – Part 5-1: Intelligent grouping and resource sharing for Class 2 and Class 3 – Core
protocol
ISO/IEC 14543-5-21,— Information technology – Home electronic system (HES) architecture
– Part 5-21: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Application
profile – AV profile
ISO/IEC 14543-5-22:2010, Information technology – Home electronic system (HES)
architecture – Part 5-22: Intelligent grouping and resource sharing for HES Class 2 and Class 3
– Application profile – File profile
ISO/IEC 29341-3-1:2008, Information technology – UPnP Device Architecture – Part 3-1:
Audio Video Device Control Protocol – Audio Video Architecture
IETF RFC 2046, Multipurpose Internet Mail Extensions (MIME) – Part 2: Media Types
3 Terms, definitions, abbreviations and conventions
3.1 Terms and definitions
For the purposes of this document the following terms and defintions apply.
3.1.1
audio/video multicast device group
type of media device group consisting of a media server and media client with multicast
capability for an AV multicast playback application
3.1.2
centralised device group
set of IGRS devices with one IGRS device acting as the master

14543-5-6  ISO/IEC:2012(E) – 9 –
NOTE The master is responsible for managing the setup, for dismissing a Device Group and for processing a join
request from other devices. The master device and other IGRS Devices in such a Device Group form a centralised or
master-slave relationship.
3.1.3
client identifier
unique identifier associated with a Client on an IGRS Device to which that Client belongs
3.1.4
content index service device group
type of media device group consisting of multiple media servers for managing content across
multiple media servers in a distributed, collaborative and load-balancing manner
3.1.5
device group
multiple IGRS devices that are organised in a logical group through the device group
management mechanism in the IGRS specification
NOTE Each IGRS device in a Device Group follows common interaction rules. Two types of Device Groups are
defined: peer-to-peer Device Group and centralised (master-slave) Device Group.
3.1.6
device identifier
globally unique device identifier associated with one IGRS Device
3.1.7
device pipe
channel used to transfer device interaction messages
NOTE This channel is set up through the pipe setup mechanism in the IGRS specification.
3.1.8
IGRS client
application that draws upon the services of one or more connected IGRS Devices
NOTE Multiple client instances can exist on a network at the same time.
3.1.9
IGRS device
information device that conforms to the IGRS specification
3.1.10
IGRS dynamic service invocation module
part of the AV application logic to orchestrate the interaction of application services with respect
to the capability of the device or device group involved and to coordinate the service invocation
sequence between the media server and media client
NOTE The IGRS dynamic service invocation module should be implemented on a media server, a media client or a
another separate device.
3.1.11
IGRS service
sharable resource encapsulated in an IGRS Device by implementing application interfaces and
providing services for other IGRS Devices
NOTE An IGRS Service has an invocation interface that meets the requirements of the IGRS specification. These
invocation interfaces are described and announced on the network through the IGRS Service Description
Specification.
– 10 – 14543-5-6  ISO/IEC:2012(E)
3.1.12
IGRS user
owner of an IGRS Device and Client
3.1.13
media client
audio/video device in an IGRS network that possesses multimedia decoding capability
NOTE Examples of a media client device include a TV, set top box, etc. The media client may access content on the
media server as the destination device in an audio/video application.
3.1.14
media device group
embodiment of device group in an audio/video system and a type of centralised device group
defined in ISO/IEC 14543-5-1
NOTE A media device group consists of two classes: content index service device group and audio video multicast
device group.
3.1.15
media server
audio/video device in IGRS network that possesses storage and computing capability
NOTE Examples of a media server device include a PC, network storage server, etc. The media server may provide
a network interface to other audio/video devices to access content managed by the media server as the source device
in an audio/video application.
3.1.16
peer-to-peer device group
set of IGRS Devices where each IGRS Device in this set has a peer-to-peer relationship with one
another
3.1.17
service attribute
variable associated with each service type to record the service status
3.1.18
service identifier
unique identifier assigned to a service provided by a specific IGRS Device
NOTE The same type of service may be provided by multiple IGRS Devices within the same network. Each instance
of a service has a unique service identifier on the IGRS Device providing that service.
3.1.19
service interface
method provided by IGRS service for the IGRS clients to share resources
NOTE The service interface is composed of interface name, parameters provide by IGRS clients, etc.
3.1.20
service type
category of IGRS Service defined according to the set of resources encapsulated
NOTE The Service Type enables service applications in the same category to have common invocation interfaces.

14543-5-6  ISO/IEC:2012(E) – 11 –
3.1.21
service type identifier
global unique identifier to differentiate IGRS services and identify the operation methods and
eventing mechanism of certain services
3.1.22
user identifier
identifier of an IGRS user
3.2 Abbreviations
BCM Back Channel Message
CIS Content Index Service
CMS Connection Management Service
EPG Electronic Program Guide
FAMS File Access Management Service
FC File Client
FCMS File Connection Management Service
FS File Server
IGRS Intelligent Grouping and Resource Sharing
MAN Mandatory, also refer to message definitions in ISO/IEC 14543-5-1
MCTMS Media Client Transport Management Service
MP Media Player
MR Media Recorder
MS Media Server
MSTMS Media Server Transport Management Service
RMS Rendering Management Service
3.3 Conventions
For the convenience of the implementer, a number of XML schemas specified in this standard
can also be found on the World Wide Web. In case of any differences, the definitions within this
standard shall prevail.
4 Conformance
For conformity to this International Standard the following applies.
• The IGRS generic service model shall meet the general description specification described
in Clause 5.
• The IGRS service type identifier requirements shall meet the specifications described in
Clause 6.
• The list of all standard IGRS service types and their detailed service-related functional
requirements shall conform to meet the specification defined in Clauses 7 and 8 respectively.
• The Back Channel Message TCP Service definitions shall meet the specification defined in
Clause 9.
• The content representation framework requirements for an IGRS AV application shall meet
the specifications described in Annex A.
• The description requirements for metadata used in an IGRS AV application shall meet the
specifications described in Annex B.

– 12 – 14543-5-6  ISO/IEC:2012(E)
• The data type generation requirements for all IGRS services shall meet the specifications
described in Annex C.
• The specific service type message formats for all IGRS services shall meet the specifications
described in Annex D.
• The XML schema files used in the IGRS services shall meet the specifications described in
Annex E.
• The service description wsdl files used in the IGRS services shall meet the specifications
described in Annex F, Annex G, Annex H, Annex I and Annex J, respectively.
5 IGRS service overview
An IGRS service conforms to the Core Protocol and indicates the shared resource provided by
IGRS devices. An IGRS service is published based on the service description template and
mechanism specified by the the Core Protocol and can be invoked by IGRS clients through the
operation mechanism specified by the Core Protocol.
An IGRS service is classified into many types. The service instances implementing the same
service type should provide the same invocation interface and eventing mechanism. The service
type is uniquely defined by the relevant service attribute and interface set.
This standard defines in detail a series of basic service types in the next few clauses. The
description includes the relevant service type identifier, service attribute, service interface set
and service implementation flow.
6 Definition of service type identifier
An IGRS service type can be classified into standard service type and non-standard service
type.
Standard service type identifiers shall conform to the service type identifier definition in the Core
Protocol, see 8.2.3 of ISO/IEC 14543-5-1:2010. According to the service type identifier
definition in the Core Protocol, the syntax of the standard service type identifier shall be as
follows:
::=“urn:”“:”
::=“IGRS:Service:ServiceType”
::=1*
::=
::=|||
::="A" | "B" | "C" | "D" | "E" | "F" | "G" | "H" |"I" | "J" | "K" | "L" | "M" | "N" | "O" | "P"
|"Q" | "R" | "S" | "T" | "U" | "V" | "W" | "X" |"Y" | "Z"
::="a" | "b" | "c" | "d" | "e" | "f" | "g" | "h" |"i" | "j" | "k" | "l" | "m" | "n" | "o" | "p" |"q" | "r" | "s"
| "t" | "u" | "v" | "w" | "x" |"y" | "z"
::="0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" |"8" | "9"
::=“-” | “.” | “_”
The value is case insensitive.
A non-standard service type is a service type not defined by this standard but by the developer
of the product. Non-standard service type identifiers shall conform to the servicetype identifier
syntax definition in the Core Protocol, see 8.2.3 of ISO/IEC 14543-5-1. According to the service
type identifier definition in the Core Protocol, the syntax of the non-standard service type
identifier shall be as follows:
::=“urn:” “:”
::=“IGRS:service:servicetype-p”
::=1*
::=
14543-5-6  ISO/IEC:2012(E) – 13 –
::= | | |
::="A" | "B" | "C" | "D" | "E" | "F" | "G" | "H" |"I" | "J" | "K" | "L" | "M" | "N" | "O" | "P"
|"Q" | "R" | "S" | "T" | "U" | "V" | "W" | "X" |"Y" | "Z"
::="a" | "b" | "c" | "d" | "e" | "f" | "g" | "h" |"i" | "j" | "k" | "l" | "m" | "n" | "o" | "p" |"q" | "r" | "s"
| "t" | "u" | "v" | "w" | "x" |"y" | "z"
::="0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" |"8" | "9"
::= “-” | “.” | “_”
The value is case insensitive.
Unless specified in the document, the word “service type” shall have the meaning of “standard
service type”.
7 Standard service type list
A standard service type includes the following services: Content Index Service, Connection
Management Service, Media Server Transport Management Service, Media Client Transport
Management Service, Rendering Management Service, File Access Management Service and
File Connection Management Service.
Table 1 defines a series of the current basic service types. Clause 8 specifies the details of the
service types listed in Table 1.

– 14 – 14543-5-6  ISO/IEC:2012(E)
Table 1 – Basic service type list
Service type name Service type identifier Field explanation
Content Index Urn:IGRS:Service:ServiceType: The Content Index Service allows the IGRS dynamic
Service ContentIndex:1 service invocation module to discover and list the media
content on a media server so that the IGRS dynamic
service invocation module can retrieve the content
information, including the name, creation date, size,
format, etc. of the media content. This information can be
used by the IGRS dynamic service invocation modules to
determine whether these contents can be played on a
media client. The content directory structure supports
nesting of sub-directories.
Connection Urn:IGRS:Service:ServiceType: The Connection Management Service is used to create
Management ConnectionManagement:1 and manage the connection between media client and
Service media server. The Media server and media client can
support and manage several active connections at any
one time by the Connection Management Service.
Media Server Urn:IGRS:Service:ServiceType: The Media Server Transport Management Service
Transport MediaServerTransportManagem enables IGRS dynamic service invocation modules to
Management ent:1 adjust and to control the media stream transport on the
Service media server, such as play, pause, stop, seek, etc. If this
service exists, it means that the media server initiated
out-of-band transport model is supported. Otherwise, it is
not supported.
Media Client Urn:IGRS:Service:ServiceType: The Media Client Transport Management Service enables
Transport MediaClientTransportManagem an IGRS dynamic service invocation module to adjust and
Management ent:1 to control the transport of media stream on a media client,
Service such as play, pause, stop, seek, etc. If this service exists,
it means that the media client initiated out-of-band
transport model is supported. Otherwise, it is not
supported.
Rendering Urn:IGRS:Service:ServiceType: The Rendering Management Service allows an IGRS
Management RenderingManagement:1 dynamic service invocation module to control media
Service playing, such as volume, contrast, brightness, etc.
Multiple active instances of rendering control can be
supported, such as the "picture-in-picture" function in TV.
The New Rendering Management Service instance is
created by the PrepareForConnection of Connection
Management Service on a media client. This service is
only provided by a media client.
File Access Urn:IGRS:Service:ServiceType: The File Access Management Service provides the
Management FileAccessManagement:1 following functions to a File Client:
Service
it provides authentication for a File Client and thus gives
corresponding file access rights to the File Client;
it allows a File Client to retrieve a sorting/searching
capability supported by a File Server;
it allows a File Client to browse the content directory in the
network provided by the File Server;
it allows a File Client to search a specified file/directory;
it allows a File Client to retrieve and modify attributes of a
file/directory;
it allows a File Client to retrieve and set a browsing filter;
it allows a File Client to subscribe to a file/directory object
update event;
it allows a File Client to subscribe to a File Access
Management Service update event;
it supports a File Client to upload and download the
specified file/directory.
File Connection Urn:IGRS:Service:ServiceType: The File Connection Management Service is used to
Management FileConnectionManagement:1 create and manage the connection between a File Server
Service and a File Client. A File Server can support and manage
multiple active connections at any one time through the
File Connection Management Service.

14543-5-6  ISO/IEC:2012(E) – 15 –
8 Basic service type specification
8.1 Content index service
8.1.1 Overview
A content Index Service allows an IGRS dynamic service invocation module to discover and list
the media content on a media server so that the IGRS dynamic service invocation module ca
...