Consumer terminal function for access to IPTV and open internet multimedia services - Part 6: Procedural application environment

IEC 62766-6:2017(E) specifies the procedural application environment (PAE) component of the OIPF terminal function (OITF). It also defines the UNI reference point UNIS-12 of the OIPF functional architecture summarised in Annex B of IEC 62766-1:2017.
The PAE is an application environment for IPTV services based on Java. Like other specifications such as OCAP, ACAP and Blu-ray, which are, or include, GEM terminal specifications, this document follows the structure of ETSI TS 102 728.

General Information

Status
Published
Publication Date
25-Jul-2017
Current Stage
PPUB - Publication issued
Start Date
22-Aug-2017
Completion Date
26-Jul-2017
Ref Project
Standard
IEC 62766-6:2017 - Consumer terminal function for access to IPTV and open internet multimedia services - Part 6: Procedural application environment
English language
57 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


IEC 62766-6 ®
Edition 1.0 2017-07
INTERNATIONAL
STANDARD
colour
inside
Consumer terminal function for access to IPTV and open internet multimedia
services –
Part 6: Procedural application environment
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 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.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing 20 000 terms and definitions in
Technical Specifications, Technical Reports and other English and French, with equivalent terms in 16 additional
documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical
iPad. Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a 65 000 electrotechnical terminology entries in English and
variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of
committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been
and withdrawn publications. collected from earlier publications of IEC TC 37, 77, 86 and

CISPR.
IEC Just Published - webstore.iec.ch/justpublished

Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: csc@iec.ch.
IEC 62766-6 ®
Edition 1.0 2017-07
INTERNATIONAL
STANDARD
colour
inside
Consumer terminal function for access to IPTV and open internet multimedia

services –
Part 6: Procedural application environment

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ISBN 978-2-8322-4616-0
ICS 33.170 35.240.95
– 2 – IEC 62766-6:2017 © IEC 2017
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 8
2 Normative references . 8
3 Terms, definitions and abbreviated terms . 10
3.1 Abbreviated terms . 10
4 General considerations and conventions . 10
4.1 Overview. 10
4.2 Relation between DVB-GEM and PAE definitions . 11
4.2.1 General . 11
4.2.2 DVB-GEM Compliance . 11
4.2.3 Functional equivalents . 12
5 Architecture and deployment options . 13
5.1 Architecture . 13
5.2 Deployment options . 14
5.2.1 Combined IG-AG-OITF STB and OITF TV (“headed configuration”) . 14
5.2.2 Combined AG-IG with multiple OITFs (“headless configuration”) . 15
5.2.3 AG-IG, OITF-IG, multiple OITFs . 16
5.2.4 Combined OITF-AG TV and IG-WAN Gateway (“headed configuration”) . 16
5.3 Remote UI server . 17
6 Protocols . 17
6.1 Broadcast channel protocols . 17
6.2 Interaction channel protocols . 17
6.3 Transport protocols for application loading over the interaction channel . 17
6.4 IPTV protocols . 18
6.4.1 Streaming protocols . 18
6.4.2 Metadata protocols . 18
6.4.3 Content download protocols . 18
6.5 Home network protocols. 18
7 Content formats . 18
7.1 Static formats. 18
7.2 Streaming formats . 18
7.3 Fonts . 19
7.3.1 Resident fonts . 19
7.3.2 Downloadable fonts . 19
8 Void . 19
9 Application model . 19
9.1 Overview. 19
9.2 Broadcast applications . 21
9.3 DVB-J model . 21
9.4 Stored and cached applications . 21
9.5 Unbound applications. 21
10 Application signalling / metadata . 21
10.1 XML AIT . 21
10.2 Stored and cached applications . 22
11 The Java platform . 23

11.1 Fundamentals . 23
11.2 GEM 1.3 . 23
11.3 Extensions and mappings to GEM APIs . 24
11.3.1 Broadcast transport protocol access API (org.dvb.dsmcc). 24
11.3.2 Application listing and launching API (org.dvb.application) . 24
11.3.3 Streaming media APIs . 24
11.3.4 GEM 3D API . 24
11.4 APIs defined by this part . 24
11.4.1 Content and service protection API . 24
11.4.2 User authentication API . 24
11.4.3 UI server API . 24
11.4.4 Content download API . 24
11.4.5 Service API . 25
11.5 PVR APIs . 25
11.6 Content referencing . 25
12 Security . 25
12.1 Authentication of applications . 25
12.2 Permission request file. 26
12.3 Security policy for applications . 26
12.4 Certificate management . 26
13 Graphics reference model . 26
14 System integration aspects . 26
15 Detailed profile definitions . 27
16 PVR . 34
16.1 General . 34
16.2 Mandatory Responsibilities . 34
16.3 Optional responsibilities . 35
16.4 Visibility of recording requests and recordings between applications and
service providers . 36
17 Minimum terminal capabilities . 36
18 HTTP adaptive streaming . 36
18.1 General . 36
18.2 HAS support . 36
Annex A (informative) Headless behaviour of UI-related APIs . 37
A.1 General . 37
A.2 PBP . 37
A.3 JavaTV . 37
Annex B (informative) Void . 39
Annex C (normative) Package org.oipf.download . 40
C.1 Interface ApplicationDownloadRequest . 40
C.2 Class LocatorDownloadSpec . 40
C.3 Class ApplicationDownloadException . 41
C.4 Class ApplicationDownloadSpec . 41
Annex D (normative) Package org.oipf.service – interface ServiceCreator . 43
Annex E (normative) org.oipf.auth . 44
E.1 Class HTTPDigestCredentials . 44
E.2 Class UserAuthenticationPermission . 44
E.3 Class UserAuthenticationManager . 45

– 4 – IEC 62766-6:2017 © IEC 2017
E.4 Class UserCredentials . 46
E.5 Class CookieCredentials . 46
Annex F (normative) org.oipf.uiserver – class UIServerManager . 47
Annex G (normative) org.oipf.drm . 48
G.1 General . 48
G.2 Class DRMAgentEvent . 48
G.3 Class DRMAgentPermission . 49
G.4 Interface DRMAgentListener . 50
G.5 Class DRMAgent. 50
G.6 Class DRMAgentException . 52
G.7 Class DRMRightsErrorEvent . 52
Annex H (normative) org.oipf.pvr . 54
H.1 Class RecordingAccessPermissions . 54
H.2 Class RecordingProperties . 55
Bibliography . 57

Figure 1 – PAE architecture block diagram . 13
Figure 2 – Combined IG-AG-OITF STB and OITF TV (“headed configuration”) . 14
Figure 3 – Combined AG-IG with multiple OITFs (“headless configuration”) . 15
Figure 4 – AG-IG, OITF-IG, multiple OITFs . 16
Figure 5 – Combined OITF-AG TV and IG-WAN Gateway (“headed configuration”) . 16

Table 1 – Status of XML AIT descriptors and elements . 22
Table 2 – Mapping of GEM clauses relating to content referencing . 25
Table 3 – Locators and corresponding text representations. 26
Table 4 – Platform profile definitions . 27
Table 5 – Applicability of GEM specification sections . 28
Table 6 – Summary of functional equivalents (informative) . 31
Table 7 – Responsibilities of GEM recording specifications . 34
Table 8 – Events during normal playback and resulting behaviour . 35
Table 9 – Optional responsibilities of GEM recording specifications . 35

INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
CONSUMER TERMINAL FUNCTION FOR ACCESS
TO IPTV AND OPEN INTERNET MULTIMEDIA SERVICES –

Part 6: Procedural application environment

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 itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
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 62766-6 has been prepared by IEC technical committee 100:
Audio, video and multimedia systems and equipment.
The text of this International Standard is based on the following documents:
CDV Report on voting
100/2550/CDV 100/2664/RVC
Full information on the voting for the approval of this International Standard can be found in
the report on voting indicated in the above table.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.

– 6 – IEC 62766-6:2017 © IEC 2017
A list of all parts in the IEC 62766 series, published under the general title Consumer terminal
function for access to IPTV and open internet multimedia services, can be found on the IEC
website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to
the specific document. At this date, the document 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 document using a
colour printer.
INTRODUCTION
The IEC 62766 series is based on a series of specifications that was originally developed by
the OPEN IPTV FORUM (OIPF). They specify the user-to-network interface (UNI) for
consumer terminals to access IPTV and open internet multimedia services over managed or
non-managed networks as defined by OIPF.

– 8 – IEC 62766-6:2017 © IEC 2017
CONSUMER TERMINAL FUNCTION FOR ACCESS
TO IPTV AND OPEN INTERNET MULTIMEDIA SERVICES –

Part 6: Procedural application environment

1 Scope
This part of IEC 62766 specifies the procedural application environment (PAE) component of
the OIPF terminal function (OITF). It also defines the UNI reference point UNIS-12 of the
OIPF functional architecture summarised in Annex B of IEC 62766-1:2017.
The PAE is an application environment for IPTV services based on Java . Like other
specifications such as OCAP, ACAP and Blu-ray , which are, or include, GEM terminal
specifications, this document follows the structure of ETSI TS 102 728.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 62766-1:2017, Open IPTV Forum (OIPF) consumer terminal function and network
interfaces for access to IPTV and open Internet multimedia services – Part 1: General
IEC 62766-2-1, Open IPTV Forum (OIPF) consumer terminal function and network interfaces
for access to IPTV and open Internet multimedia services – Part 2-1: Media Formats
IEC 62766-2-2, Open IPTV Forum (OIPF) consumer terminal function and network interfaces
for access to IPTV and open Internet multimedia services – Part 2-1: HTTP Adaptive
Streaming
IEC 62766-3:2016, Open IPTV Forum (OIPF) consumer terminal function and network
interfaces for access to IPTV and open Internet multimedia services – Part 3: Content
Metadata
IEC 62766-4-1:2017, Open IPTV Forum (OIPF) consumer terminal function and network
interfaces for access to IPTV and open Internet multimedia services – Part 4-2: Protocols
IEC 62766-5-1:2017, Open IPTV Forum (OIPF) consumer terminal function and network
interfaces for access to IPTV and open Internet multimedia services – Part 5-1: Declarative
Application Environment
ISO/IEC 14496-18, Information technology – Coding of audio-visual objects – Part 18: Font
compression and streaming
___________
1 Javaspript is a programming language that has been standardised by ECMA as ECMAScript® and as
ISO/IEC 16262
Blu-ray is a trademark owned by the Blu-ray Disc Association. This information is given for the convenience of
users of this document and does not constitute an endorsement by IEC of the product named. Equivalent
products may be used if they can be shown to lead to the same results.

ETSI EN 300 468, Digital Video Broadcasting (DVB); Specification for Service Information (SI)
in DVB systems
ETSI TS 101 211 v1.9.1, Digital Video Broadcasting (DVB); Guidelines on implementation and
usage of Service Information (SI)
ETSI TS 101 600 V1.1.1 (2012-05), Digital Video Broadcasting (DVB); GEM Profile for Plano-
Stereoscopic 3DTV
ETSI TS 102 727 V1.1.1 (2010-01), Digital Video Broadcasting (DVB); Multimedia Home
Platform (MHP) Specification 1.2.2
ETSI TS 102 728 V1.2.1 (2011-09), Digital Video Broadcasting (DVB); Globally Executable
MHP (GEM) Specification 1.3 (including OTT and hybrid broadcast/broadband)
ETSI TS 102 539 V.1.1.1, Digital Video Broadcasting (DVB); Carriage of Broadband Content
Guide (BCG) information over Internet Protocol (IP)
ETSI TS 102 809, Digital Video Broadcasting (DVB); Signalling and carriage of interactive
applications and services in Hybrid broadcast/broadband environments
ETSI, TS 102 816 V1.1.1, Digital Video Broadcasting (DVB); Personal Video Recorder
(PVR)/Personal Data Recorder (PDR) Extension to the Multimedia Home Platform
ETSI TS 102 817 V1.1.1, Digital Video Broadcasting (DVB); Digital Recording Extension to
Globally Executable Multimedia Home Platform (GEM)
3GPP TS 26.234, Transparent end-to-end Packet-switched Streaming Service (PSS)
Protocols and codecs (Release 9)
DAVIC 1.4.1, Specification part 9, Information Representation
Available from
http://docbox.etsi.org/Reference/DAVIC/DAVIC%201.4.1%20Specification%20part%209.pdf
DVB, Blue Book A127, Application Gateway and Media Server Fragment
Available from
http://www.mhp.org/specs/a127.application_gateway_and_media_server_fragment.pdf
Java Community Process, Java Specification Request JSR-217, Personal Basis Profile (PBP)
1.1 (or later)
The latest release of JSR 217 is available at http://www.jcp.org/en/jsr/detail?id=217
Java Community Process, Java Specification Request JSR-218, Connected Device
Configuration (CDC) 1.1 (or later)
The latest release of JSR 218 is available at http://www.jcp.org/en/jsr/detail?id=218
Java Community Process, Java Specification Request JSR-219, Foundation Profile (FP) 1.1
(or later)
The latest release of JSR 219 is available at http://www.jcp.org/en/jsr/detail?id=219
Java Community Process, Java Specification Request JSR-927, Java TV, Version 1.1.1 (or
later)
The latest release of JSR 927 is available at http://www.jcp.org/en/jsr/detail?id=927
Java Community Process, JAR File Specification, part of Java SDK 1.4.2 specification, 1999
Available from http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html

– 10 – IEC 62766-6:2017 © IEC 2017
CableLabs, OpenCable Application Platform (OCAP) Version 1.1.2, September 2009,
Available from https://apps.cablelabs.com/specification/opencable-application-platform-ocap/
3 Terms, definitions and abbreviated terms
No terms and definitions are listed in this document.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1 Abbreviated terms
For the purposes of this document the abbreviated terms given in IEC 62766-1:2017 as well
as the following apply.
DSMCC Digital Storage Media Command and Control
FP Foundation Profile
GEM Globally Extecutable MHP
HAS HTTP Adaptive Streaming
JSSE Java Secure Sockets Extension
MHP Multimedia Home Platform
MPD Media Presentation Description
PBP Personal Basis Profile
4 General considerations and conventions
4.1 Overview
Subclause 4.2 covers general considerations and conventions, in particular the relationship
with DVB-GEM.
Clause 5 explains the relationship between DVB-GEM and the PAE platform, the basic
architecture and positioning of the procedural application environment in the OIPF landscape.
Clause 6 includes details on the supported transport protocols by cross-referencing the OIPF
protocols specification IEC 62766-4-1.
Clause 7 defines static and streaming media formats for the representation of images, sound,
videos, colours and fonts by cross-referencing the OIPF media formats specification
IEC 62766-2-1.
Clause 8 is intentionally void.
Clauses 9 and 10 describe the application model for Java applications for the PAE and
application signalling.
Clause 11 describes features of the Java platform, such as class loading behaviour, event
model and specifies all APIs that are contained in the platform.

Clause 12 deals with security aspects of the platform such as the security framework for
applications, application authentication, secure network connections and certificate
management.
Clause 13 deals with the graphics reference model.
Clause 14 deals with system integration aspects.
Clause 15 defines which parts of the specification are mandatory or optional for the 3 different
device types addressed by this volume.
Clause 16 deals with PVR functionalities.
Clause 17 defines the minimum terminal capabilities.
Clause 18 deals with HTTP Adaptive Streaming support.
The annexes contain API definitions at class and method level and clarifications of referenced
specifications.
4.2 Relation between DVB-GEM and PAE definitions
4.2.1 General
The GEM/MHP notion of "broadcast application" should be interpreted as meaning
applications that are bound to a specific scheduled content service or a content-on-demand
item.
Unbound applications are persistent applications that are not tied to any service.
The GEM term "interaction channel" is the network connection channel of the OIPF
architecture summarised in Annex B of IEC 62766-1:2017.
4.2.2 DVB-GEM Compliance
All mandatory requirements for the GEM IPTV target shall be supported by the PAE.
The following optional parts of the GEM IPTV target shall be supported by the PAE:
• OpenType;
• internet access applications;
• stored applications, stored services and corresponding APIs;
• unbound applications and corresponding APIs;
• content referencing for IPTV;
• service discover and selection for IPTV.
The following optional part of the GEM IPTV target shall be supported by the PAE under
specific circumstances:
• TV-Anytime content referencing and metadata.

– 12 – IEC 62766-6:2017 © IEC 2017
The following optional parts of the GEM IPTV target may be supported by this document:
• file storage API;
• Smart Card API (JSR177);
• providers ;
• privileged applications.
Where a service provider is specifying a device including the PAE, the service provider may
choose to require these optional features.
The following optional parts of the GEM IPTV target should not be supported by the PAE:
• DVB-HTML;
• the MHP functional equivalent called application authentication;
• section filtering API (org.davic.mpeg.sections), tuning API, basic MPEG concepts and
common error reporting;
• MPEG 2 video drips and corresponding APIs;
• MPEG 2 I-frames and corresponding APIs;
• credentials;
• certificate revocation mechanism of ETSI TS 102 727;
• root certificate management mechanism defined in ETSI TS 102 727;
• externally authorized applications.
4.2.3 Functional equivalents
The functional equivalents to GEM-IPTV are listed in Table 6.
The main concepts are as follows:
• DVB Service Discovery and Selection and Broadband Content Guide are used for SI.
• Applications are distributed in JAR files, using HTTP for unicast and FLUTE for multicast.
NOTE FLUTE is conceptually different from DSMCC object carousel and cannot be considered a functional
equivalent.
• Application authentication is based on the signing capabilities for JAR files.

5 Architecture and deployment options
5.1 Architecture
Application
TV Meta TV TV
App.
Media UI
"Core"
specific data exten exten
Lifecycle
App. Data Metadata APIs APIs Security
Java
data format -sions -sions
Java
APIs
Mgmt access APIs - - APIs
APIs
access specific - -
Virtual
-
APIs APIs - javax. java.awt -
-
APIs APIs GEM GEM
Machine
Java TV
- - parts of media from JSSE
CDC
- -
or
GEM parts of javaTV part of PBP
FP
GEM GEM
PBP
java.io java TV
Platform Platform
Platform
Platform Platform
Platform
File System Media
Multi-threading
Metadata Graphics
SSL/TLS
Libraries incl. Presentation
Networking
Library / Library /
Libraries
local file system Library /
..
Libraries Driver
FLUTE Driver
Labraries
IEC
Figure 1 – PAE architecture block diagram
Figure 1 shows a number of the key components of the architecture and indicates their origin
– GEM, JavaTV, PBP or components of PBP (JSSE, CDC or FP). Below is a short summary of
each component ordered from left to right of Figure 1.
• App. Mgmt APIs: these enable one application to obtain lists of other applications and
start or stop other them.
• App. Lifecycle APIs: these are the first APIs to be called by the implementation when
starting an application.
• TV specific data access APIs: these provide access to data in ways which are specific to
TV environments.
• Data access APIs: these provide generic access to data – files, sockets, streams, etc.
• Metadata format specific APIs: these provide access to the details of metadata in a format
dependent way.
• Metadata APIs: these provide access to metadata and are independent of any specific
metadata format.
• TV extensions: these provide control over A/V media in ways which are specific to TV
environments.
• Media APIs: these provide access to and control over A/V media.
• TV extensions: these provide UI features specific to TV environments.
• UI APIs: these provide the basic UI capabilities.
• Security APIs: these provide the basic security capabilities.
• Core Java APIs: these provide the basic capabilities of the Java language.

– 14 – IEC 62766-6:2017 © IEC 2017
• Java virtual machine: this provides the basic Java capabilities of the environment.
5.2 Deployment options
5.2.1 Combined IG-AG-OITF STB and OITF TV (“headed configuration”)
Managed
WAN
Gateway
Internet
HNI-INI-AG
OITF
IG - AG –
OITF STB
DLNA device
Legacy TV
IEC
Figure 2 – Combined IG-AG-OITF STB and OITF TV (“headed configuration”)
This deployment as shown in Figure 2 supports both managed and unmanaged services, with
DAE and PAE applications, presented on an OITF TV and a legacy TV. The following devices
are deployed:
• A WAN Gateway.
• Combined IG, AG and OITF STB: a set top box including IG, AG and OITF functionality
that exposes HNI-INI-AG to other OITFs in the residential network. It connects to the
legacy TV using some non-OIPF specified mechanism, such as HDMI.
• OITF TV: this is a TV containing an OITF.
Optionally, the IG-AG-OITF STB or the OITF TV may act as a DLNA DMS to make OIPF
services available to DLNA devices. They may also act as a DLNA DMP to access content
from other DLNA devices on the home network.

5.2.2 Combined AG-IG with multiple OITFs (“headless configuration”)
Managed
WAN
Gateway
Internet
HNI-INI-AG
OITF TV
AG - IG
HNI-INI-AG
OITF STB
Legacy TV
DLNA device
IEC
Figure 3 – Combined AG-IG with multiple OITFs (“headless configuration”)
This deployment as shown in Figure 3 supports both managed and unmanaged services, with
DAE and PAE applications, presented on an OITF TV and a legacy TV. The following devices
are deployed:
• A WAN Gateway.
• Combined AG-IG device: a device including both IG and AG functionality that exposes
HNI-INI-AG to OITFs in the residential network.
• OITF STB: a set-top box containing an OITF. It connects to the legacy TV using some
non-OIPF specified mechanism, such as HDMI or SCART.
• OITF TV: a TV containing an OITF.
Optionally, the OITF STB or the OITF TV may act as a DLNA DMS to make OIPF services
available to DLNA devices. They may also act as a DLNA DMP to access content from other
DLNA devices on the home network.

– 16 – IEC 62766-6:2017 © IEC 2017
5.2.3 AG-IG, OITF-IG, multiple OITFs
Managed
OITF TV
WAN Internet
Gateway
HNI-INI-AG
HNI-INI-AG
AG - IG
DLNA
device
IG – OITF STB
Legacy TV
HNI-INI-AG
OITF STB
IEC
Legacy TV
Figure 4 – AG-IG, OITF-IG, multiple OITFs
This deployment as shown in Figure 4 supports managed and unmanaged services, and DAE
and PAE applications. The following devices are deployed:
• A WAN Gateway.
• Combined AG-IG device: a device including both IG and AG functionality that exposes
HNI-INI-AG to OITFs in the residential network.
• OITF STB: a set-top box containing an OITF. It connects to the legacy TV using some
non-OIF specified mechanism, such as HDMI.
• IG-OITF STB: a set-top box containing both an IG and an OITF.
• OITF TV: a TV containing an OITF.
In this deployment, there are multiple IGs. Only one IG can be active in the residential
network at any point in time. The ISIM application shall always be in the AG-IG in this case.
5.2.4 Combined OITF-AG TV and IG-WAN Gateway (“headed configuration”)
Managed
DLNA device
Internet
OITF + AG IG - WAN Gateway
TV
IEC
Figure 5 – Combined OITF-AG TV and IG-WAN Gateway (“headed configuration”)
This deployment as shown in Figure 5 supports managed and unmanaged services, and DAE
and PAE applications. The following devices are deployed:

• Combined IG-WAN Gateway: a single physical device including an IG and WAN Gateway
functionality.
• Combined AG-OITF TV: a TV including both an OITF and an AG.
Optionally, the OITF-AG TV may act as a DLNA DMS to make OIPF services available to
DLNA devices. It may also act as a DLNA DMP to access content from other DLNA devices
on the home network.
5.3 Remote UI server
NOTE This subclause is given for information only.
PAE applications may offer a CE-HTML remote UI to other devices. The org.oipf.uiserver
package allows applications to register as providing a remote UI. When an application
registers, it provides information about itself in the XML format defined by the CEA-2014-A
remote UI. The PAE implementation listens for UPnP search requests for the schema
“urn:oipf-org:device:ag:1” as defined in IEC 62766-4-1:2017, 11.3.2. When such a request is
received, the implementation combines the remote UI information provided by all currently
registered applications and returns it.
6 Protocols
6.1 Broadcast channel protocols
The broadcast channel protocols defined by Clause 6.2 of ETSI TS 102 728 are not included
in the present document.
6.2 Interaction channel protocols
The following protocols shall be supported with the definition in IEC 62766-4-1 superseding
that in ETSI TS 102 728:
• TCP;
• UDP;
• IP;
• DNS;
• HTTP;
• HTTPS.
6.3 Transport protocols for application loading over the interaction channel
Subclause 6.4.1 of ETSI TS 102 728 need not be supported.
Applications loading over the interaction channel shall be implemented using signed JAR-files
as defined in the JAR file specification.
The FLUTE protocol shall be supported as defined in IEC 62766-4-1.
When the application signalling for an application includes one or more FLUTE transport
protocol descriptors (see Annex AR.2 in ETSI TS 102 728, “Extensions to XML AIT”), the
following shall apply.
• The implementation shall attempt to connect to each specified FLUTE session or sessions
(unless already connected for another application).
• Requests to load files shall be checked against the files available through FLUTE before
fetching them from a unicast network.

– 18 – IEC 62766-6:2017 © IEC 2017
• When a FLUTE session is not used by any running applications, the session shall be
closed. It is implementation-dependent whether this happens immediately or at some later
time when implementation resources used by the closed session may be needed for other
purposes. Closed FLUTE sessions may be subsequently re-used; however, the
implementation shall ensure the contents are current, as if a new session had been
created.
6.4 IPTV protocols
6.4.1 Streaming protocols
The following protocols shall be supported as defined in IEC 62766-4-1:
• RTP;
• IGMP;
• RTSP.
6.4.2 Metadata protocols
The following protocol shall be supported:
• DVB-STP as required by IEC 62766-3.
6.4.3 Content download protocols
The following protocol shall be supported as defined in IEC 62766-4-1:
• HTTP.
6.5 Home network protocols
This is the procedure for AG discovery defined in IEC 62766-4-1.
7 Content formats
7.1 Static formats
Requirements on still image support are defined in referenced specifications. The following is
a summary:
• JPEG support is required by ETSI TS 102 728 and JSR-217 with the precise details
defined in ETSI TS 102 728.
• PNG support is required by ETSI TS 102 728 and JSR-217 with the precise details defined
in ETSI TS 102 728.
• GIF support is required by JSR-217.
The optional MPEG-2 I-frames and video "drips" in ETSI TS 102 728 shall not be used.
7.2 Streaming formats
The following shall be supported for streaming content as defined by IEC 62766-2-1:
• H.264/AVC;
• HE-AAC.
The following shall be supported as monomedia formats for audio clips as defined by
IEC 62766-2-1:
• HE-AAC.
MPEG-1 layer 3 may be supported for streaming content and for audio-clips as defined by
IEC 62766-2-1.
Subtitles shall be supported as defined by IEC 62766-2-1.
OIPF HTTP Adaptive Streaming may be supported as defined by IEC 62766-2-2.
...

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...