IEC 62546:2009
(Main)High definition (HD) recording link guidelines
High definition (HD) recording link guidelines
IEC 62546:2009 specifies the communication protocol between a TV receiver and a video recorder which are connected through a digital interface.
Lignes directrices pour les liaisons d'enregistrement haute définition (HD)
IEC 62546:2009 spécifie le protocole de communication entre un récepteur TV et un enregistreur vidéo qui sont connectés par l'intermédiaire d'une interface numérique.
General Information
Standards Content (Sample)
IEC 62546 ®
Edition 1.0 2009-07
INTERNATIONAL
STANDARD
colour
inside
High Definition (HD) recording link guidelines
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 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: 0Hinmail@iec.ch
Web: 1Hwww.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: 2Hwww.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: 3Hwww.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: 4Hwww.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: 5Hwww.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: 6Hcsc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 62546 ®
Edition 1.0 2009-07
INTERNATIONAL
STANDARD
colour
inside
High Definition (HD) recording link guidelines
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
U
ICS 33.160.25; 33.160.40 ISBN 978-2-88910-761-2
– 2 – 62546 © IEC:2009(E)
CONTENTS
FOREWORD.15H4
INTRODUCTION.16H6
1 Scope.17H7
2 Normative references .18H7
3 Terms, definitions and abbreviations .19H7
3.1 Terms and definitions .20H7
3.2 Abbreviations .21H7
4 Use cases .22H8
5 System definition.23H9
5.1 Device model .24H9
5.2 System usage .25H9
6 Guideline terminology and conventions .26H10
7 Guideline requirements .27H10
7.1 Purpose .28H10
7.2 General .29H10
7.3 Networking and connectivity .30H10
7.4 Device discovery and control.31H10
7.5 Media management .32H11
7.5.1 Purpose.33H11
7.5.2 Support for upload operations.34H11
7.5.3 Support for selection of record destination.35H12
7.5.4 Actions .36H12
7.6 Media transport .37H16
7.7 Media format .38H16
7.7.1 Purpose.39H16
7.7.2 General .40H16
7.7.3 Media format profile.41H16
7.8 Content protection.42H16
Annex A (informative) Use cases .43H17
Annex B (informative) Media format profile .44H22
Annex C (informative) Record destination selection .45H23
Annex D (informative) Vendor extension of XML service description .46H26
Bibliography.47H28
Figure 1 – High definition reception and recording .48H6
Figure 2 – Recording system usage interaction model .49H9
Figure A.1 – HD reception and recording device model – triggered by the recorder.50H18
Figure A.2 – HD reception and recording device model – triggered by the receiver .51H19
Table 1 – HDLNK namespace values .52H10
Table 2 – HD Recording Link guidelines version .53H11
Table 3 – element description .54H11
Table 4 – Arguments for X_HDLnkGetRecordDestinations().55H12
Table 5 – Arguments for X_HDLnkGetRecordDestinationInfo() .56H12
62546 © IEC:2009(E) – 3 –
Table 6 – Arguments for X_HDLnkGetRecordContainerID() .57H13
Table 7 – Child elements and attributes of the element. .58H14
Table 8 – Child elements and attributes of the element. .59H15
Table 9 – Eventing and moderation.60H16
Table B.1 – Media format profiles for regions.61H22
– 4 – 62546 © IEC:2009(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
HIGH DEFINITION (HD) RECORDING LINK GUIDELINES
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC 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 National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees 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, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) 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.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62546 has been prepared by technical area 9: Audio, video and
multimedia applications for end-user network, of IEC technical committee 100: Audio, video
and multimedia systems and equipment.
The text of this standard is based on the following documents:
CDV Report on voting
100/1470/CDV 100/1558/RVC
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
62546 © IEC:2009(E) – 5 –
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in
the data related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
A bilingual version of this publication may be issued at a later date.
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.
– 6 – 62546 © IEC:2009(E)
INTRODUCTION
With the global introduction of High definition (HD) TV services, receivers, and consumer
recording equipment, the need has arisen for a universal recording interface to connect
receivers and recorders.
This International Standard presents a comprehensive proposal for this interface including
content protection 62H [2 ]63H [3 ] 0F . The proposal – intended as a guideline – leverages existing
standards IEC 62481-1, and 64H [4] in the field, ensuring interoperability between receivers and
recorders.
*
Recorder
Recording
Receiver
interface
IEC 1338/09
NOTE * HDMI (High-Definition Multimedia Interface)1F is a digital interface for the connection between source
device and monitor provided by HDMI Licensing, LLC.
Figure 1 – High definition reception and recording
The starting point for the proposal is an in-home configuration depicted in 65HFigure 1. The
assumption is that both the receiver (e.g. STB) as well as the recorder (e.g. BD-recorder) are
connected to the display via an HDMI interface 66H [4]. The proposed recording interface
connects the recorder to the receiver and carries compressed signals only. Obviously, the
receiver functionality can be integrated into the display.
The proposed interface recognises the fact that a large amount of content will be made
available in the form of a Pay-TV and thus be protected via a Conditional Access (CA) system.
The required CA functionality is assumed to be contained in the receiver.
___________
Figures in square brackets refer to the Bibliography.
HDMI is the trade name of a product supplied by HDMI Licensing, LLC. This information is given for the
convenience of users of this document and does not consitute an endorsement by IEC of the product named.
62546 © IEC:2009(E) – 7 –
HIGH DEFINITION (HD) RECORDING LINK GUIDELINES
1 Scope
This International Standard specifies the communication protocol between a TV receiver and
a video recorder which are connected through a digital interface.
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.
IEC 62481-1:2007, Digital living network alliance (DLNA) home networked device
interoperability guidelines – Part 1: Architecture and protocols
IEC 62481-2, Digital living network alliance (DLNA) home networked device interoperability
guidelines – Part 2: DNLA media formats
ETSI TR 101 211:2004, Digital Video Broadcasting (DVB); Guidelines on Implementation
and usage of Service Information (SI)-V1.6.1
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1.1
content
video, audio or subtitles data which is intended to be delivered to and consumed by a user
3.1.2
content protection
control of access and usage of content through rules and rights
3.1.3
receiver
device with a digital broadcast reception capability which may have a storage for recording
content, for example STB
3.1.4
recorder
device capable of recording digital content on to a storage medium (removable or non-
removable or both), for example BD-recorder
3.2 Abbreviations
For the purposes of this document, the following abbreviations apply.
CDS Content Directory Service
CEC Consumer Electronics Control
– 8 – 62546 © IEC:2009(E)
CSV Comma Separated Value
DIT Discontinuity Information Table
DLNA Digital Living Network Alliance
DMS Digital Media Server
DTCP Digital Transmission Content Protection
EPG Electronic Program Guide
HDD Hard Disk Drive
HDLNK HD recording LiNK
HDMI High Definition Multimedia Interface
HTTP Hyper Text Transfer Protocol
IRD Integrated Receiver Decoders
MPEG Moving Picture Experts Group
OCM Optional Content Management
PAT Program Association Table
PMT Program Map Table
PVR Personal Video Recorder
RCV Receiver
REC Recorder
SIT Selection Informative Table
SPTS Single Program Transport Stream
STB Set Top Box
STC System Time Clock
TS Transport Stream
SI Service Information
SOAP Simple Object Access Protocol
SCPD Service Controlled Protocol Description
UPnP Universal Plug and Play
XML eXtensible Markup Language
4 Use cases
Annex A shows the following use cases derived from the interconnection depicted in 67HFigure 1.
a) Impulse recording (What You See Is What You Record – WYSIWYR)
b) Scheduled recording
c) Pause TV
d) Archiving
This standard addresses the following two use cases described in 68H A.4.3 and Clause 69H A. 6, but
not others described in 70H An ne x A.
In addition, it should be noted that this guideline implements the scheduled recording use
case without reservation of the storage on the recorder side. Other use cases described in
Annex A may be covered by the future publications.
62546 © IEC:2009(E) – 9 –
5 System definition
5.1 Device model
HD Recording Link guidelines uses the device model described in DLNA (see Clause 5 in
IEC 62481-1). This subclause maps the receiver and the recorder (target devices for the
guidelines) to DLNA device model.
This guideline provides the requirements for the following devices:
a) RCV – receiver is a device that consists of one or more broadcasting tuner(s), an IP-
based home network interface and may have storage for recording content. The storage
functionality of the receiver is not covered by the guidelines;
b) REC – recorder is a device that consists of a storage for recording content (removable or
non-removable or both) and an IP-based home network interface.
5.2 System usage
The system usage describes the device interaction model between devices defined in this
document in order to realise the use cases listed in Clause 71H 4.
The usage covers the use cases addressed in Clause 72H 4 of this document. The recording
system usage has an upload controller device capability in the RCV to instruct the REC to
accept the content for recording.
IEC 1339/09
Figure 2 – Recording system usage interaction model
73HFigure 2 illustrates the device interaction model. The following steps are performed in the
system usage:
invoke UPnP action to select the destination media (HDD, BD, etc.);
invoke UPnP action to create a CDS entry for the content to be recorded;
transport the content to the recorder.
It should be noted that the upload controller device capability is incorporated as part of a valid
DLNA device. In preparation for the next steps of the guidelines it has been decided to host
the upload controller device capability in a DMS. Therefore, the receiver requires adherence
to the DMS device class although the functionality of the DMS is not required to implement
the use cases realised by the current guidelines.
– 10 – 62546 © IEC:2009(E)
6 Guideline terminology and conventions
The HD Recording Link guidelines include references to XML 74H [6 ]75H [7] elements and attributes
without the definition of formal HDLNK XML schema. This allows the HD Recording Link
guidelines to define new XML elements and attributes in the future, without having to define a
new namespace or schema definition. 76HTable 1 lists the namespace values that are used by
HD Recording Link guidelines and the context of their usage.
Table 1 – HDLNK namespace values
Namespace value Usage context
Used for XML elements and attributes defined by HD Recording
urn:schemas-hdlnk-org:device-1-0
Link guidelines for use in UPnP device description files.
7 Guideline requirements
7.1 Purpose
This clause covers the guidelines that enable vendors to build HD receivers and recorders
that together, provide HD Recording Link functionality as defined in the current phase.
7.2 General
The RCV must fulfil all the guidelines for a DMS device class in IEC 62481-1 and upload
controller device capability (+UP+) in IEC 62481-1. The REC must fulfil all guidelines for DMS
device class in IEC 62481-1 and must accept upload operations from the RCV (see following
subclause for details).
7.3 Networking and connectivity
The RCV and REC must support the following connectivity selection of IEC 62481-1.
• Ethernet conformant to all [NC Ethernet:] labeled requirements in the general capability
requirements clause of networking and connectivity.
The RCV and REC may support the following connectivity selection of IEC 62481-1.
• 802.11 conformant to all [NC 802:11:] labeled requirements in the general capability
requirements clause of networking and connectivity2F .
Any of the above selections can be supported via an add-on card, dongle, or equivalent.
7.4 Device discovery and control
The device discovery and control should be performed using UPnP device architecture as
described in 7.3 of IEC 62481-1.
However, the HD Recording Link devices (RCV and REC) must incorporate the following
changes to the device description documents.
a) The RCV and REC must employ the XML element inside the
element of the device description document to indicate adherence to a particular
HDLNK guidelines parts.
b) The value of element is a string as defined below:
___________
It is to be noted that the transmission of an HD signal may require more than 10 Mbps of network bandwidth.
62546 © IEC:2009(E) – 11 –
• hdlnkdoc-value = hdlnk-dev-class”-“hdlnk-version;
• hdlnk-dev-class = “RCV” | “REC”;
• hdlnk-version = major-version”.”minor-version;
• major-version = DIGIT;
• minor-version = DIGIT DIGIT.
The hdlnk-dev-class represents a Device Class of a HDLNK device. The hdlnk-version
represents adherence to specific guidelines parts according to 77HTable 2.
The namespace value in the element of the device description of
RCV and REC devices must be according to Clause 78H 6.
Table 2 – HD Recording Link guidelines version
HD Recording Link guidelines adherence HD Record Link guidelines version
HD Recording Link guidelines (this standard) 1.00
For instance, to indicate adherence to the currently defined specification, the HD Recording
Link devices must include the values as shown in 79HTable 3.
Table 3 – element description
Device class element
RCV
RCV-1.00
REC
REC-1.00
7.5 Media management
7.5.1 Purpose
This subclause covers the guidelines for implementing media management, mainly transfer of
content, using the DLNA and UPnP AV architecture.
7.5.2 Support for upload operations
An RCV must support the DLNA upload controller device capability according to IEC 62481-1,
7.4.1.2.4 with the following exception.
• The support for upload functionality as specified in these guidelines is not determined by
the presence of the capability ID (av-upload) in element of the the
device description. Instead, it must be deduced from adherence of a device to the REC
device class specified by defined in 80H 7.4 .
A REC must support the DLNA upload device option according to IEC 62481-1, 7.4.1.7.1 with
the following additional requirements and exceptions.
• DLNA OCM content upload operation must be supported according to IEC 62481-1
7.4.1.7.12.1.
– 12 – 62546 © IEC:2009(E)
• The DLNA advertisement of the upload AnyContainer operation and OCM upload content
operation is optional 3F . More specifically:
– it is not required to use the capability ID (av-upload) in element of
the device description to indicate support for the upload AnyContainer operation;
– and it is not required to use @dlna:dlnaManaged attribute to indicate support for OCM
upload content operation.
• The support for upload device option as specified in this guidelines must be deduced from
adherence of a device to the REC device class specified by
defined in 81H 7.4 .
7.5.3 Support for selection of record destination
A REC must support the selection of record destination using the following vendor-specific
UPnP actions of the Content Directory service 82H [5 ] :
a) CDS:X_HDLnkGetRecordDestinations()– returns a list of possible record destinations.
This action is used by RCV to acquire the possible record destinations;
b) CDS:X_HDLnkGetRecordDestinationInfo()– returns properties of a given record
destination. This action is used by the RCV to query the
...
IEC 62546 ®
Edition 1.0 2009-07
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
High definition (HD) recording link guidelines
Lignes directrices pour les liaisons d'enregistrement haute définition (HD)
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 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.
Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie
et les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez
les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.
IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
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 corrigendum or an amendment might have been published.
IEC publications search - webstore.iec.ch/advsearchform IEC online collection - oc.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews. With a subscription you will always
committee, …). It also gives information on projects, replaced have access to up to date content tailored to your needs.
and withdrawn publications.
Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
The world's leading online dictionary on electrotechnology,
Stay up to date on all new IEC publications. Just Published
containing more than 22 000 terminological entries in English
details all new publications released. Available online and
and French, with equivalent terms in 18 additional languages.
once a month by email.
Also known as the International Electrotechnical Vocabulary
(IEV) online.
IEC Customer Service Centre - webstore.iec.ch/csc
If you wish to give us your feedback on this publication or
need further assistance, please contact the Customer Service
Centre: sales@iec.ch.
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.
A propos des publications IEC
Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.
Recherche de publications IEC - IEC online collection - oc.iec.ch
webstore.iec.ch/advsearchform Découvrez notre puissant moteur de recherche et consultez
La recherche avancée permet de trouver des publications IEC gratuitement tous les aperçus des publications. Avec un
en utilisant différents critères (numéro de référence, texte, abonnement, vous aurez toujours accès à un contenu à jour
comité d’études, …). Elle donne aussi des informations sur adapté à vos besoins.
les projets et les publications remplacées ou retirées.
Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
Le premier dictionnaire d'électrotechnologie en ligne au
Restez informé sur les nouvelles publications IEC. Just
monde, avec plus de 22 000 articles terminologiques en
Published détaille les nouvelles publications parues.
anglais et en français, ainsi que les termes équivalents dans
Disponible en ligne et une fois par mois par email.
16 langues additionnelles. Egalement appelé Vocabulaire
Electrotechnique International (IEV) en ligne.
Service Clients - webstore.iec.ch/csc
Si vous désirez nous donner des commentaires sur cette
publication ou si vous avez des questions contactez-nous:
sales@iec.ch.
IEC 62546 ®
Edition 1.0 2009-07
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
High definition (HD) recording link guidelines
Lignes directrices pour les liaisons d'enregistrement haute définition (HD)
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 33.160.25; 33.160.40 ISBN 978-2-8322-9334-8
– 2 – IEC 62546:2009 IEC 2009
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms, definitions and abbreviations . 7
3.1 Terms and definitions . 7
3.2 Abbreviations . 7
4 Use cases . 8
5 System definition . 9
5.1 Device model . 9
5.2 System usage . 9
6 Guideline terminology and conventions . 10
7 Guideline requirements . 10
7.1 Purpose . 10
7.2 General . 10
7.3 Networking and connectivity . 10
7.4 Device discovery and control . 10
7.5 Media management . 11
7.5.1 Purpose . 11
7.5.2 Support for upload operations . 11
7.5.3 Support for selection of record destination . 12
7.5.4 Actions . 12
7.6 Media transport . 16
7.7 Media format . 16
7.7.1 Purpose . 16
7.7.2 General . 16
7.7.3 Media format profile . 16
7.8 Content protection . 16
Annex A (informative) Use cases . 17
Annex B (informative) Media format profile . 22
Annex C (informative) Record destination selection . 23
Annex D (informative) Vendor extension of XML service description . 26
Bibliography . 28
Figure 1 – High definition reception and recording . 6
Figure 2 – Recording system usage interaction model . 9
Figure A.1 – HD reception and recording device model – triggered by the recorder . 18
Figure A.2 – HD reception and recording device model – triggered by the receiver . 19
Table 1 – HDLNK namespace values . 10
Table 2 – HD Recording Link guidelines version . 11
Table 3 – element description . 11
Table 4 – Arguments for X_HDLnkGetRecordDestinations() . 12
Table 5 – Arguments for X_HDLnkGetRecordDestinationInfo() . 12
Table 6 – Arguments for X_HDLnkGetRecordContainerID() . 13
Table 7 – Child elements and attributes of the element. . 14
Table 8 – Child elements and attributes of the element. . 15
Table 9 – Eventing and moderation . 16
Table B.1 – Media format profiles for regions . 22
– 4 – IEC 62546:2009 IEC 2009
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
HIGH DEFINITION (HD) RECORDING LINK GUIDELINES
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC 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 National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees 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, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) 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.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62546 has been prepared by technical area 9: Audio, video and
multimedia applications for end-user network, of IEC technical committee 100: Audio, video
and multimedia systems and equipment.
The text of this standard is based on the following documents:
CDV Report on voting
100/1470/CDV 100/1558/RVC
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in
the data related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
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.
– 6 – IEC 62546:2009 IEC 2009
INTRODUCTION
With the global introduction of High definition (HD) TV services, receivers, and consumer
recording equipment, the need has arisen for a universal recording interface to connect
receivers and recorders.
This International Standard presents a comprehensive proposal for this interface including
content protection [2][3] . The proposal – intended as a guideline – leverages existing
standards IEC 62481-1, and [4] in the field, ensuring interoperability between receivers and
recorders.
*
Recording Recorder
Receiver
interface
IEC 1338/09
NOTE * HDMI (High-Definition Multimedia Interface) is a digital interface for the connection between source
device and monitor provided by HDMI Licensing, LLC.
Figure 1 – High definition reception and recording
The starting point for the proposal is an in-home configuration depicted in Figure 1. The
assumption is that both the receiver (e.g. STB) as well as the recorder (e.g. BD-recorder) are
connected to the display via an HDMI interface [4]. The proposed recording interface
connects the recorder to the receiver and carries compressed signals only. Obviously, the
receiver functionality can be integrated into the display.
The proposed interface recognises the fact that a large amount of content will be made
available in the form of a Pay-TV and thus be protected via a Conditional Access (CA) system.
The required CA functionality is assumed to be contained in the receiver.
___________
Figures in square brackets refer to the Bibliography.
HDMI is the trade name of a product supplied by HDMI Licensing, LLC. This information is given for the
convenience of users of this document and does not consitute an endorsement by IEC of the product named.
HIGH DEFINITION (HD) RECORDING LINK GUIDELINES
1 Scope
This International Standard specifies the communication protocol between a TV receiver and
a video recorder which are connected through a digital interface.
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.
IEC 62481-1:2007, Digital living network alliance (DLNA) home networked device
interoperability guidelines – Part 1: Architecture and protocols
IEC 62481-2, Digital living network alliance (DLNA) home networked device interoperability
guidelines – Part 2: DNLA media formats
ETSI TR 101 211:2004, Digital Video Broadcasting (DVB); Guidelines on Implementation
and usage of Service Information (SI)-V1.6.1
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1.1
content
video, audio or subtitles data which is intended to be delivered to and consumed by a user
3.1.2
content protection
control of access and usage of content through rules and rights
3.1.3
receiver
device with a digital broadcast reception capability which may have a storage for recording
content, for example STB
3.1.4
recorder
device capable of recording digital content on to a storage medium (removable or non-
removable or both), for example BD-recorder
3.2 Abbreviations
For the purposes of this document, the following abbreviations apply.
CDS Content Directory Service
CEC Consumer Electronics Control
– 8 – IEC 62546:2009 IEC 2009
CSV Comma Separated Value
DIT Discontinuity Information Table
DLNA Digital Living Network Alliance
DMS Digital Media Server
DTCP Digital Transmission Content Protection
EPG Electronic Program Guide
HDD Hard Disk Drive
HDLNK HD recording LiNK
HDMI High Definition Multimedia Interface
HTTP Hyper Text Transfer Protocol
IRD Integrated Receiver Decoders
MPEG Moving Picture Experts Group
OCM Optional Content Management
PAT Program Association Table
PMT Program Map Table
PVR Personal Video Recorder
RCV Receiver
REC Recorder
SIT Selection Informative Table
SPTS Single Program Transport Stream
STB Set Top Box
STC System Time Clock
TS Transport Stream
SI Service Information
SOAP Simple Object Access Protocol
SCPD Service Controlled Protocol Description
UPnP Universal Plug and Play
XML eXtensible Markup Language
4 Use cases
Annex A shows the following use cases derived from the interconnection depicted in Figure 1.
a) Impulse recording (What You See Is What You Record – WYSIWYR)
b) Scheduled recording
c) Pause TV
d) Archiving
This standard addresses the following two use cases described in A.4.3 and Clause A.6, but
not others described in Annex A.
In addition, it should be noted that this guideline implements the scheduled recording use
case without reservation of the storage on the recorder side. Other use cases described in
Annex A may be covered by the future publications.
5 System definition
5.1 Device model
HD Recording Link guidelines uses the device model described in DLNA (see Clause 5 in
IEC 62481-1). This subclause maps the receiver and the recorder (target devices for the
guidelines) to DLNA device model.
This guideline provides the requirements for the following devices:
a) RCV – receiver is a device that consists of one or more broadcasting tuner(s), an IP-
based home network interface and may have storage for recording content. The storage
functionality of the receiver is not covered by the guidelines;
b) REC – recorder is a device that consists of a storage for recording content (removable or
non-removable or both) and an IP-based home network interface.
5.2 System usage
The system usage describes the device interaction model between devices defined in this
document in order to realise the use cases listed in Clause 4.
The usage covers the use cases addressed in Clause 4 of this document. The recording
system usage has an upload controller device capability in the RCV to instruct the REC to
accept the content for recording.
Receiver Recorder
RCV = Upload controller REC = DMS + upload
⊃ DMS option
MSCP
MSD MSD
(+upload)
UPnP UPnP
UPnP CP
device device
Content Content
Media
Media Media
transport
transport transport
server
client server
(+upload) (+upload)
IP connectivity IP connectivity
Part of DMS requirement, but not required to realize
the use case.
IEC 1339/09
Figure 2 – Recording system usage interaction model
Figure 2 illustrates the device interaction model. The following steps are performed in the
system usage:
invoke UPnP action to select the destination media (HDD, BD, etc.);
invoke UPnP action to create a CDS entry for the content to be recorded;
transport the content to the recorder.
It should be noted that the upload controller device capability is incorporated as part of a valid
DLNA device. In preparation for the next steps of the guidelines it has been decided to host
the upload controller device capability in a DMS. Therefore, the receiver requires adherence
to the DMS device class although the functionality of the DMS is not required to implement
the use cases realised by the current guidelines.
– 10 – IEC 62546:2009 IEC 2009
6 Guideline terminology and conventions
The HD Recording Link guidelines include references to XML [6][7] elements and attributes
without the definition of formal HDLNK XML schema. This allows the HD Recording Link
guidelines to define new XML elements and attributes in the future, without having to define a
new namespace or schema definition. Table 1 lists the namespace values that are used by
HD Recording Link guidelines and the context of their usage.
Table 1 – HDLNK namespace values
Namespace value Usage context
Used for XML elements and attributes defined by HD Recording
urn:schemas-hdlnk-org:device-1-0
Link guidelines for use in UPnP device description files.
7 Guideline requirements
7.1 Purpose
This clause covers the guidelines that enable vendors to build HD receivers and recorders
that together, provide HD Recording Link functionality as defined in the current phase.
7.2 General
The RCV must fulfil all the guidelines for a DMS device class in IEC 62481-1 and upload
controller device capability (+UP+) in IEC 62481-1. The REC must fulfil all guidelines for DMS
device class in IEC 62481-1 and must accept upload operations from the RCV (see following
subclause for details).
7.3 Networking and connectivity
The RCV and REC must support the following connectivity selection of IEC 62481-1.
• Ethernet conformant to all [NC Ethernet:] labeled requirements in the general capability
requirements clause of networking and connectivity.
The RCV and REC may support the following connectivity selection of IEC 62481-1.
• 802.11 conformant to all [NC 802:11:] labeled requirements in the general capability
requirements clause of networking and connectivity .
Any of the above selections can be supported via an add-on card, dongle, or equivalent.
7.4 Device discovery and control
The device discovery and control should be performed using UPnP device architecture as
described in 7.3 of IEC 62481-1.
However, the HD Recording Link devices (RCV and REC) must incorporate the following
changes to the device description documents.
a) The RCV and REC must employ the XML element inside the
element of the device description document to indicate adherence to a particular
HDLNK guidelines parts.
b) The value of element is a string as defined below:
___________
It is to be noted that the transmission of an HD signal may require more than 10 Mbps of network bandwidth.
• hdlnkdoc-value = hdlnk-dev-class”-“hdlnk-version;
• hdlnk-dev-class = “RCV” | “REC”;
• hdlnk-version = major-version”.”minor-version;
• major-version = DIGIT;
• minor-version = DIGIT DIGIT.
The hdlnk-dev-class represents a Device Class of a HDLNK device. The hdlnk-version
represents adherence to specific guidelines parts according to Table 2.
The namespace value in the element of the device description of
RCV and REC devices must be according to Clause 6.
Table 2 – HD Recording Link guidelines version
HD Recording Link guidelines adherence HD Record Link guidelines version
HD Recording Link guidelines (this standard) 1.00
For instance, to indicate adherence to the currently defined specification, the HD Recording
Link devices must include the values as shown in Table 3.
Table 3 – element description
Device class element
RCV
RCV-1.00
REC
REC-1.00
7.5 Media management
7.5.1 Purpose
This subclause covers the guidelines for implementing media management, mainly transfer of
content, using the DLNA and UPnP AV architecture.
7.5.2 Support for upload operations
An RCV must support the DLNA upload controller device capability according to IEC 62481-1,
7.4.1.2.4 with the following exception.
• The support for upload functionality as specified in these guidelines is not determined by
the presence of the capability ID (av-upload) in element of the the
device description. Instead, it must be deduced from adherence of a device to the REC
device class specified by defined in 7.4.
A REC must support the DLNA upload device option according to IEC 62481-1, 7.4.1.7.1 with
the following additional requirements and exceptions.
• DLNA OCM content upload operation must be supported according to IEC 62481-1
7.4.1.7.12.1.
– 12 – IEC 62546:2009 IEC 2009
• The DLNA advertisement of the upload AnyContainer operation and OCM upload content
operation is optional . More specifically:
– it is not required to use the capability ID (av-upload) in element of
the device description to indicate support for the upload AnyContainer operation;
– and it is not required to use @dlna:dlnaManaged attribute to indicate support for OCM
upload content operation.
• The support for upload device option as specified in this guidelines must be deduced from
adherence of a device to the REC device class specified by
defined in 7.4.
7.5.3 Support for selection of record destination
A REC must support the selection of record destination using the following vendor-specific
UPnP actions of the Content Directory service [5]:
a) CDS:X_HDLnkGetRecordDestinations()– returns a list of possible record destinations.
This action is used by RCV to acquire the possible record destinations;
b) CDS:X_HDLnkGetRecordDestinationInfo()– returns properties of a given record
destination. This action is used by the RCV to query the status of a given record
destination (e.g. media type, total capacity, etc.);
c) CDS:X_HDLnkGetRecordContainerID() – returns the CDS container ID associated to a
given record destination. This function is used by the RCV to select a CDS container with
a given record destination. The returned container ID is later used in the execution of the
CreateObject() action of the upload operation.
7.5.4 Actions
7.5.4.1 X_HDLnkGetRecordDestinations()
This action returns a RecordDestination XML document describing the possible record
destinations that a REC device supports, if any. The action is used by the REC to expose the
possible record destinations, see Table 4.
Table 4 – Arguments for X_HDLnkGetRecordDestinations()
Argument Direction Related state variable
RecordDestinationList OUT X_RecordDestinationList
7.5.4.2 X_HDLnkGetRecordDestinationInfo()
This action returns a RecordDestinationInfo XML document describing the properties of a
given record destination, see Table 5.
Table 5 – Arguments for X_HDLnkGetRecordDestinationInfo()
Argument Direction Related State Variable
RecordDestinationID IN X_A_ARG_TYPE_RecordDestinationID
RecordDestinationInfo OUT X_A_ARG_TYPE_RecordDestinationInfo
___________
The advertisement of the DLNA upload functionality is not mandatory in the REC for the following reasons:
A REC is not necessarily fully compliant with DLNA upload device option. Some valid REC implementations may
not be able to support all mandatory upload media profiles as defined in IEC 62481-2.
A REC implementation may want to hide the upload functionality from all DLNA devices that are not aware of this
guidelines. This may be used to avoid possible unmanaged upload operation from other DLNA devices conflicting
with RCV record schedule.
7.5.4.3 X_HDLnkGetRecordContainerID()
This action returns the container ID associated with a given record destination. The container
is later used to create the new object for the upload operation, see Table 6.
Table 6 – Arguments for X_HDLnkGetRecordContainerID()
Argument Direction Related State Variable
RecordDestinationID IN X_ARG_TYPE RecordDestinationID
Elements IN A_ARG_TYPE Result
ContainerID OUT A_ARG_TYPE ObjectID
The state variables A_ARG_TYPE_ObjectID and A_ARG_TYPE_Result are defined in [5].
The argument Elements is identical to the argument Elements of CreateObject (see [5])
except ParentID and is provided to describe the object that will be uploaded later. This way
the REC can refine the selection of the associated container ID. For example, using the same
RecordDestinationID a given REC implementation may expect the upload of audio and video
items in two different containers.
Obviously, the argument Elements cannot include a valid parentID which is the expected
result of the action. Hence, the value of parentID in the argument Elements must be empty
(“ ”) in this action.
7.5.4.4 State variables
7.5.4.4.1 X_A_ARG_TYPE_RecordDestinationID
This state variable is introduced to provide type information for the RecordDestinationID
argument in various actions. The RecordDestinationID argument uniquely identifies individual
record destinations within this vendor-specific extension of the Content Directory service [5].
7.5.4.4.2 X_RecordDestinationList
This state variable enumerates the various record destinations supported by the REC. The
value is a valid RecordDestination XML document:
• the root element of the document is . It contains zero or more
child elements, each of which represents one record
destination that is supported in this REC implementation;
• a element must have the required (R) child value and
atrributes as defined in.Table 7;
• a element may have optional (O) attributes as defined in
Table 7;
• a element may have other attributes.
– 14 – IEC 62546:2009 IEC 2009
Table 7 – Child elements and attributes of the element.
a
Name R/O XML Form Type Description
version R Attribute of xsd:unsignedInt Indicates the RecordDestination
version. MUST be set to “1” for
this version.
destID R Attribute of xsd:string Uniquely identifies the
element.
updateID O Attribute of xsd:unsignedInt Indicates the update count of
the associated
. The
value is incremented by ‘1’ for
every change of properties of
the Record Destination.
Direct child value of The user friendly name of the
- R xsd:string
Record Destination.
a
R – required; O – optional
See [6][7] for detailed description of xsd types (i.e.: xsd:unsignedInt, xsd:string, etc.).
Example (this string must be escaped when transmitted in a SOAP response message):
xmlns=”urn:schemas-hdlnk-org”>
User Friendly Name
User Friendly Name
7.5.4.4.3 X_A_ARG_TYPE _RecordDestinationInfo
This state variable is introduced to provide type information for the RecordDestinationInfo
argument in various actions. It enumerates the properties of a given record destination. The
value is a valid RecordDestinationInfo XML document:
• the root element of the document is ;
• a element must have the required (R) child value and
attributes defined in Table 8;
• a element may have optional (O) attributes defined in
Table 8;
• a element may have other attributes.
Table 8 – Child elements and attributes of the element.
a
Name R/O XML Form Type Description
version R Attribute of xsd:unsignedInt Indicates the RecordDestinationInfo
version. MUST be set to “1” for this
version.
allowedTypes R Attribute of xsd:string Attribute indicates the CSV list for
types of allowed media that are
(CSV)
available for the recording.
Refers to
AVTransport::RecordStorageMedium
[9] state variable for allowed values
[9]
recordable R Attribute of xsd:boolean When set to “1”, the content
represented by this record
destination can be used for
recording purposes.
dtcpSupport R Attribute of xsd:boolean When set to “1”, the content
represented by this record
destination can be used for
recording from DTCP source device.
totalCapacity O Attribute of xsd:unsignedLong Indicates the total capacity of the
record destination expressed in
bytes.
Attribute of Indicates the available capacity of
availableCapacity O xsd:unsignedLong
the record destination expressed in
bytes.
- R Direct child value of xsd:string Indicates the type of media that is to
be used for the recording.
Refers to
AVTransport::RecordStorageMedium
[9] state variable for allowed values
[9].
Note that “NONE” is used to indicate
there is no media now.
a
R – required; O – optional
Example (this string must be escaped when transmitted in a SOAP response message):
xmlns=”urn:schemas-hdlnk-org”
version=”1” allowedTypes=”BD,DVD+RW,DVD-R,NONE” recordable=”0”
availableCapacity=”0”/>
DVD+RW
– 16 – IEC 62546:2009 IEC 2009
7.5.4.5 Eventing and moderation
The eventing and moderation is shown in Table 9.
Table 9 – Eventing and moderation
Minimum
Moderated Maximum Logical
Variable name Evented delta per
a
event event rate combination
b
event
X_RecordDestinationList YES YES 1 s
a
Determined by N, where rate = (event)/(N seconds).
b
(N) × (allowedValueRange step)
The X_RecordDestinationList state variable is evented to allow the REC to notify a change in
the list of available record destinations or if applicable to notify a change in the state of one or
more record destinations (see updateID property).
7.6 Media transport
Media transport should be performed by following mandatory protocols as defined in 7.4 of
IEC 62481-1:
a) HTTP/1.1 (IETF RFC 2616, Hypertext Transfer Protocol);
b) HTTP POST.
7.7 Media format
7.7.1 Purpose
This clause provides a comprehensive list of all media format profiles defined (mandatory and
optional) for this version of the HD Recording Link guidelines.
7.7.2 General
The following list of requirements is applicable for all media format profiles defined in the
guidelines.
• All content objects exchanged according to HD Recording Link guidelines belong to AV
media class as defined in IEC 62481-2.
• All media format profiles defined in these guidelines must adhere to the MPEG TS packet
format described below:
– the transport system stream must be a partial single program transport stream (SPTS).
• Information of the transport stream including PAT, PMT, SI tables, SIT and DIT must be
compliant to partial bitstream described in ETSI TR 101 211 (Section 6 : Storage media)
and the insertion of SIT is mandatory.
• A list of the recommendation of the media format profiles is given in Annex B. All the
media format profiles should be supported by REC and at least one of these media format
profiles is supported by RCV in accordance with the region where those are used.
7.7.3 Media format profile
A REC must support the exposure of the profiles for upload using
CDS:X_GetDLNAUploadProfiles action defined in 7.4.1.7.4.2 of IEC 62481-1.
7.8 Content protection
All content objects exchanged according to HD Recording Link guidelines must be protected
according to DTCP [2][3].
Annex A
(informative)
Use cases
A.1 General
In order to specify the interface between receiver and recorder, use cases are investigated.
This annex introduces the use cases which are investigated. Some of those use cases are
solved by the current standard and some may be solved by the future publications.
A.2 Overview
This annex describes four use cases that form the basis for the HD Recording Link guidelines.
The four use cases are:
a) impulse recording (What You See Is What You Record – WYSIWYR);
b) scheduled recording;
c) pause TV;
d) archiving.
The use cases are described in the form of a stimuli-response sequence. Typically, a key
press on the remote control of a recorder or a receiver is the stimulus and the execution of a
user requested function (such as recording) in the system response. Moreover, each use case
can be triggered either by the receiver or by the recorder.
A.3 Impulse recording (WYSIWYR)
A.3.1 General
The impulse recording use case depicts a functionality to record a currently watched
programme. The functionality can be triggered either from the receiver side or from the
recorder side.
– 18 – IEC 62546:2009 IEC 2009
A.3.2 Triggered by the recorder
Recording Recorder
Receiver
interface
IEC 1340/09
Figure A.1 – HD reception and recording device model – triggered by the recorder
Figure A.1 shows the recording of an actual viewing programme initiated by the recorder. The
sequence of user actions and system responses are as follows:
a) user pushes Rec button on the recorder;
b) Active Source is determined using an appropriate mechanism, for example HDMI/CEC [4]
If the receiver is the Active Source, it sends its content to the recorder;
c) content is continuously transferred until the conclusion of the event (programme).
A.3.3 Triggered by the receiver
Recording Recorder
Receiver
interface
IEC 1341/09
Figure A.2 – HD reception and recording device model – triggered by the receiver
Figure A.2 shows the recording of an actual viewing programme initiated by the receiver. The
sequence of user actions and system responses are as follows:
a) user pushes Rec button on the receiver;
b) Active Source is determined using an appropriate mechanism, for example HDMI/CEC [4];
c) if the receiver is the Active Source, it sends its content to the recorder;
d) content is continuously transferred until the conclusion of the event (programme).
A.4 Scheduled recording
A.4.1 General
The scheduled recording use case depicts a functionality to record a programme that will be
broadcast in the future. A specific programme is selected using an Electronic Programme
Guide (EPG) or other methods (e.g., manual entry of date, time, duration, channel number).
The functionality can be triggered either from the receiver side or from the recorder side.
A.4.2 Initiated by the recorder
Figure A.1 shows the timer-recording of future programme(s) using EPG or other methods
initiated from the recorder. The sequence of user actions and system responses are as
follows:
a) user selects a programme to be recorded using EPG or another method on the recorder;
b) recorder creates a recording schedule on the receiver;
c) recorder internally creates a recording reservation;
d) at the time of the selected event, the receiver sends its content to the recorder;
e) content is continuously transferred until the conclusion of the event (programme).
– 20 – IEC 62546:2009 IEC 2009
A.4.3 Initiated by the receiver
Figure A.2 shows the timer recording of future programme(s) using EPG or other methods
initiated from the receiver. The sequence of user actions and system responses are as follows:
a) user selects a programme to be recorded using EPG or another method on the receiver;
b) receiver creates a recording reservation on the recorder;
c) receiver internally creates a recording schedule;
d) at the time of the selected event, the receiver sends its content to the recorder;
e) content is continuously transferred until the conclusion of the event (programme).
A.5 Pause TV
A.5.1 General
The pause TV use case enables a functionality to pause a live TV programme that is being
broadcast. While in the pause state, the recorder continues to record the content internally,
but outputs the frozen picture at the paused position. When the user resumes the play, the
content is played back from the position where it was paused, while the recorder continues to
record the content internally. This functionality can be triggered either from the receiver side
or from the recorder side.
A.5.2 Triggered by the recorder
Figure A.1 shows the Playback-Pause of a currently viewing programme initiated from the
recorder. The sequence of user actions and system responses are as follow
...










Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...