English Translation

IPTV STANDARD

Overview

IPTVFJ STD-0001 Version 1.1

Created on September 11, 2008 (Version 1.0)

Revised on September 16, 2009 (Version 1.1)

IPTV Forum Japan

IPTVFJ STD-0001

-2-

General Notes to the English Translation of IPTV Standards 1. The copyright of this document is ascribed to the IPTV Forum Japan(IPTVFJ). 2. All rights reserved. No part of this document may be reproduced, stored in a retrieval

system, or transmitted, in any form or by any means, without the prior written permission of IPTVFJ.

3. The IPTV Standards are usually written in Japanese and approved by the IPTVFJ

Technical Committee. This document is a translation into English of the approved document for the purpose of convenience of users. If there are any discrepancies in the content, expressions, etc., between the Japanese original and this translated document, the Japanese original shall prevail.

4. The establishment, revision and abolishment of IPTV Standards are approved at the

IPTVFJ Technical Committee, which meets several times a year. Approved IPTV Standards, in their original language, are made publicly available through web posting, generally in about a few weeks after the date of approval. The original document of this translation may have been further revised and therefore users are encouraged to check the latest version at an appropriate page under the following URL:

http://www.iptvforum.jp/en/

IPTVFJ STD-0001

i

Table of contents

Chapter 1 Introduction .................................................................................................................... 1

Chapter 2 Delivery Service Models Assumed................................................................................. 2

2.1 VOD Service ............................................................................................................................ 2

2.2 Download Service ................................................................................................................... 2

2.3 IP Broadcasting Service ......................................................................................................... 3 2.4 IP Retransmission Service ..................................................................................................... 4

Chapter 3 Assumed Network Environment and Approaches to Delivery Services ..................... 5

3.1 Assumed Network Environment ........................................................................................... 5

3.1.1 Network Configuration for IPTV .................................................................................... 5

3.1.2 CDN Scope ........................................................................................................................ 6 3.1.3 Internet Scope .................................................................................................................. 7

3.2 Approaches to Delivery Services ........................................................................................... 7

3.2.1 Models of Approaches to Delivery Services .................................................................... 7

3.2.2 Network Environment and Service Approach Patterns ............................................... 8

Chapter 4 Overview of Technology Elements Used in the IPTV Standards .............................. 10 4.1 Basic Architecture of IPTV Technology ............................................................................... 10

4.2 Overview of IPTV Technology Elements .............................................................................. 11

4.2.1 Content Encoding ........................................................................................................... 11

4.2.2 Content Transmission Method ...................................................................................... 12

4.2.3 CAS/DRM ....................................................................................................................... 12 4.2.4 System Control ............................................................................................................... 13

4.2.5 Resident-based Content Navigation ............................................................................. 13

4.2.6 Browser-based Content Navigation .............................................................................. 14

4.2.7 Service Discovery ........................................................................................................... 14 4.2.8 Network Connection ...................................................................................................... 15

Chapter 5 Structure of Specifications and Organization of Specification Documents in the

IPTV Standards ................................................................................................................................ 16

IPTVFJ STD-0001

-1-

Chapter 1 Introduction

IPTV Forum Japan (IPTVFJ) was established in May 2008 to standardize technical specifications relating to IPTV receivers and services and to promote the widespread use and enhancement of these specifications, with a view to making available IPTV services that conform to common specifications. It has pressed ahead with its main task of formulating various specifications for IPTV Standards, and released the first set of specifications on September, 2008, the second set on December, 2008, and the third set on September, 2009. The developed specifications are posted on the Forum’s website for anyone to browse or download, in accordance with the Forum’s policy of enabling anyone to use the IPTV Standards and of providing an environment in which anyone can design receivers that conform to these specifications.

Another important policy of the Forum is to build an environment that allows high-definition videos to be circulated and viewable by receivers available on the market. This objective is to enable service providers to provide high-quality content easily, and allow users to access it easily. In developing these specifications, we have assumed that the service will be provided over a network, such as the open Internet and a CDN. We aim at assisting receiver manufacturers so that they can produce a wide variety of receivers. Furthermore, as Japan makes a complete transition to digital broadcasting in 2011, we aim at developing services that organically integrate digital broadcasting and network-based content provision.

IPTV Standards of this Forum consist of 8 parts: CDN Scope Service Approach Specifications, Internet Scope Service Approach Specifications, IP broadcasting Specifications, Operational Specifications for IP Retransmission of Digital Terrestrial Television Broadcasting, Operational Specifications for IP Retransmission of BS Digital Satellite Broadcasting, VOD Specifications, Download Specifications, and Integration with Broadcasting Specifications. The present document, Overview, presents an overview of each part and the relationships among them. It is hoped that this document will assist readers to gain an overall picture of all the IPTV Standards.

IPTVFJ STD-0001

-2-

Chapter 2 Delivery Service Models Assumed

The “IPTV service” is a service that delivers video content over an IP network. Although a variety of delivery methods and service models can be conceived for the delivery of video content, this chapter focuses on the methods for content delivery services that can be provided in accordance with these IPTV Standards.

2.1 VOD Service

In the VOD service, the user directly receives and plays back the content that is delivered by streaming from the server upon the user’s request. In the assumed operation type, contents are streamed from the beginning (or a specified point) from a video content server using unicast in response to the play request that was sent from receiver to the server when the contents were selected by a user from the content list on the screen of the receiver. The delivery network is required to maintain a bandwidth adequate for the playback quality of the requested content. The assumed trick playback in regard to content playback includes variable speed playback with several speed settings (fast-forward playback, fast-rewind playback, etc.), pause, resume (playback from the interrupted point), and other functions such as chapter jump playback that is set in the contents.

Figure 2-1 Conceptual Diagram of the VOD Service

2.2 Download Service

In the download service, the content downloaded from the server is first stored in the storage

ｔ

Playback

Playback ends Selection of content Playback starts

CDN

Video content server

Unicast streaming

Request

Request Receiver

Receiver

Program

IPTVFJ STD-0001

-3-

media of the receiver, and the user views the content in the storage media when he or she wants to. Therefore, this service is available to only those receivers that have built-in storage media. This service is assumed to operate as follows. First, the user selects an item of content from the list of downloadable items of content displayed on the screen of the receiver. The receiver downloads the specified item of content from the server, and holds it in its storage media. Second, the user selects an item of content from the list of already stored items of content displayed on the screen, and the receiver plays back the content from the beginning (or a specified point). The length of download time depends on the size of the content and the bandwidth of the transmission link. Unlike a streaming service, it is not essential to maintain a certain bandwidth for the transmission link in the delivery network. The assumed trick playback in regard to content playback includes variable speed playback with several speed settings (fast-forward playback, fast-rewind playback, etc.), pause, resume (playback from the interrupted point), and other functions such as chapter jump playback that is set in the contents.

Figure 2-2 Conceptual Diagram of the Download Service

2.3 IP Broadcasting Service

The IP broadcasting service is a broadcast-type service based on the concept of channels with programs arranged along the time axis. This service provides a viewing experience similar to those of BS digital satellite broadcasting, CS digital broadcasting, and digital terrestrial

Video content server

CDN Request Receiver

Download

Request Receiver

Selection of content Playback starts Playback ends

Program A

Program A

Download

Content being Stored

Playback

ｔ

Selection of content Download starts

IPTVFJ STD-0001

-4-

broadcasting over an IP network instead of radio waves. This service is assumed to operate as follows. Content providers send, via dedicated lines, etc., service streams to the IP broadcasting servers operated by service providers. The servers then multicast the streams to users. IP broadcasting service providers may produce content on their own and directly multicast it over the CDN from their servers.

Figure 2-3 Conceptual Diagram of the IP Broadcasting Service and IP Retransmission Service

2.4 IP Retransmission Service

The IP retransmission service is similar to the IP broadcasting service in that it multicasts programs based on the concept of channels. However, its objectives are to complement the digital terrestrial television broadcasting service, which is the core broadcasting service, by providing solutions to areas that cannot be reached by the radio waves of digital terrestrial television broadcasting/BS digital satellite broadcasting, and to broaden the range of programs users can choose from. This service is assumed to operate as follows. The service first receives digital terrestrial television broadcasting/BS digital satellite broadcasting programs, converts the received signals and then multicasts the converted signals. Therefore, it is assumed that users have the same service experience as that of receiving radio-wave-based digital terrestrial television broadcasting programs.

ｔ

ChA

ChB

Program A-1 Program A-2 Program A-3

Program B-1 Program B-2 Program B-3

Receiver

Receiver

Receiver

Multicast streaming

CDN

IP broadcasting & IP retransmission server

IP broadcasting

IP retransmission of digital terrestrial television broadcasting IP retransmission of BS digital satellite broadcasting

Channel selection

Channel selection Playback

Playback

IPTVFJ STD-0001

-5-

Chapter 3 Assumed Network Environment and Approaches to Delivery Services

This chapter describes the network environment in which the various delivery services mentioned in the previous chapter can be provided, and, as a related topic, a model of different approaches taken by the receiver to receive delivery services. In addition, it presents assumed variations of the network environment and approaches to delivery services.

3.1 Assumed Network Environment

3.1.1 Network Configuration for IPTV

The basic network configuration model for the IPTV service is shown in Figure 3-1.

Figure 3-1 Network Configuration Model for IPTV Service

The various entities in this figure are defined below. Delivery network

A delivery network has IPTV servers and connects home gateways in residential homes to these servers to allow provision of IPTV service IPTV server

An IPTV server is used for different types of IPTV service. It is a generic name for a group of servers accessed mainly by IPTV receivers (ex. Video content servers). Home gateway (HGW)

A home gateway is a node that terminates both a delivery network and a home network Home network

A home network connects IPTV receivers to a home gateway in a residential home. This is outside the scope of these specifications. IPTV receiver

An IPTV receiver is a terminal that mainly communicates with an IPTV server to receive IPTV service.

IPTVFJ STD-0001

-6-

The part of the network environment that is subject to these specifications is the delivery network. The delivery network can be classified into two categories in terms of the scope of the network used by IPTV service.

3.1.2 CDN Scope

A content delivery network (CDN) is a single managed network designed to deliver high-quality content, such as video content. If IPTV service is provided only within a single CDN, this network environment is called a CDN Scope.

A conceptual network configuration diagram for IPTV in the CDN Scope is shown in Figure 3-2.

IPTVServer

IPTVServer

CDN

CDN

IPTVReceiver

IPTVReceiver

□ □

IPTVReceiver

IPTVReceiver

□

IPTVReceiver

IPTVReceiver

□

IPTVReceiver

IPTVReceiver

□

IPTVReceiver

□

■

■■ ■ ■

■

AccessNetwork Access

NetworkHGW

Figure 3-2 Network Configuration in the CDN Scope

The CDN Scope has the following features as the network environment for IPTV service:

Only those IPTV receivers that are connected to a specific delivery network (CDN) can receive the service. A certain level of service quality can be guaranteed because the CDN is well managed and

normally provides broadband transmission links for content delivery. Since the service is provided within a single managed network, service can be provided using

multicast. Since the service is provided within one limited and managed scope, and the number of service

providers and the number of IPTV servers are limited, it is possible to operate the service in a well-controlled manner, and receivers can manage the service control.

All types of delivery services can be assumed to fall within the CDN Scope, namely, VOD service, download service, IP broadcasting service, and IP retransmission service.

IPTVFJ STD-0001

-7-

3.1.3 Internet Scope

If all networks that can be accessed using IP and can provide some form of delivery service are used for IPTV service, this network environment is called the Internet Scope. The Internet Scope can include CDNs. A conceptual network configuration diagram for IPTV service in the Internet Scope is shown in Figure 3-3.

■■ ■

■■

IPTVReceiver

IPTVReceiver

IPTVServer

■ ■

□ □

IPTVReceiver

IPTVReceiver

IPTVReceiver

□ □

IPTVReceiver

■ ■

IPTVReceiver

IPTVReceiver

□ □

IPTVReceiver

■ ■

AccessNetwrok

HGW HGW HGW HGW HGW HGW

AccessNetwork

AccessNetwork

Figure 3-3 Conceptual Diagram of Network Configuration in the Internet Scope

The Internet Scope has the following features as the network environment for IPTV service:

In principle, all IPTV receivers connected to IP networks can receive the service. Since this network environment is not managed, the quality of service is normally not

guaranteed. Since this network environment consists of multiple networks managed by different

organizations, it is difficult to use multicast. Since inherently the number of service providers and the number of IPTV servers managed by

them are indefinite, it is normally difficult for the receiver to manage the service control.

Because multicast operation is difficult, delivery services that can be assumed in the Internet Scope are restricted to the VOD service and download service.

3.2 Approaches to Delivery Services

3.2.1 Models of Approaches to Delivery Services

To receive the delivery services mentioned in the previous chapter, the IPTV receiver generally approaches delivery services following the sequence of the phases shown below.

(1) Service entry phase

IPTVFJ STD-0001

-8-

The IPTV receiver makes ready for using the service by establishing an IP connection to the delivery network, and receiving basic information about content navigation and the delivery service, and information needed to access a variety of IPTV servers.

(2) Content navigation phase The IPTV receiver receives content navigation information by accessing the IPTV server that provides information needed to access an individual item of content/program to be delivered by means of the delivery service, and searches for and displays the item of content/program to be provided by the delivery service, and activates the use of the delivery service.

(3) Delivery service receiving phase The IPTV receiver accesses the IPTV server that delivers the desired content, and directly receives the delivery service so that the user can view the content.

3.2.2 Network Environment and Service Approach Patterns

The approach to the delivery service depends on which network environment described in Section 3.1 is used. It can also be conceived that the reception of an IPTV delivery service is initiated in connection with integration with broadcasting. Considering these factors, we classify service approaches into the three patterns described below. Figure 3-4 shows a conceptual diagram that summarizes various flows in these service approaches.

Service approach in the CDN Scope To enter the service, the receiver discovers the service by scanning information about access to the IPTV servers for all services available in the delivery network. This information is called “configuration information”. A portal service is provided as a means of content navigation that is common to all delivery services. The receiver accesses the portal service by selecting the portal based on information on all providers obtained through the service discovery. BML is used for this portal service. Service approach in the Internet Scope

Unlike the CDN Scope, this approach involves no service discovery process. A portal service is provided as a means of content navigation that is common to all delivery services. It is normally assumed that the receiver accesses a particular portal service based on information embedded in the IPTV receiver. HTML is used for this portal service. Service approach in connection with integration with broadcasting

Access to the delivery service is initiated by a transition from the state of receiving a digital broadcasting service, such as digital terrestrial television broadcasting, to a portal service in the CDN Scope or Internet Scope using BML data for data broadcasting. Alternatively, the receiver directly accesses the delivery service by creating a content navigation function using BML data for data broadcasting.

IPTVFJ STD-0001

-9-

Figure 3-4 Conceptual Diagram of the Flows in Different Service Approaches

ポータルサービス （＠

IP 再送信

放送

ポータルサービス （＠

放送

デジタル

(network connection and service discovery)

Service entry Content navigation (authentication and content search, purchase, service activation)

Receiving delivery service

CDN Scope

Internet Scope

Integration with broadcasting

BS digital EPG

Digital terrestrial EPG

EPG IP broadcasting

VOD-ECG

DL-ECG

IP retransmission

service

service

IP broadcasting

service

service

VOD

Portal URL

Portal service (Web service)

(＠BML browser)

Portal service

(＠HTML browser) (Web service)

Service discovery

(getting configuration

information)

Broadcasting (Data broadcasting) (＠BML browser)

Download

IPTVFJ STD-0001

-10-

Chapter 4 Overview of Technology Elements Used in the IPTV Standards

4.1 Basic Architecture of IPTV Technology

A good part of these IPTV Standards is based on the digital broadcasting technologies defined by ARIB and Dpa, and implemented in BS digital satellite broadcasting, digital terrestrial television broadcasting, etc. In particular, the technical specifications for multicast services, such as IP broadcasting service and IP retransmission service, reuse the architecture of digital broadcasting almost without modification, except for technical differences arising from the fact that an IP network is used for data transmission instead of radio waves. In contrast, the specifications for on-demand services (especially for content layer), such as the VOD service and download service, is based on that of MPEG2-TS-based digital broadcasting. The architecture for an on-demand mechanism is based on that of server-type broadcasting that has been studied by ARIB and the Server P. Consequently, each specification of these IPTV Standards includes many references to the specifications of ARIB and operational rules of TR-B14, TR-B15, etc. However, the IPTV Standards inherently differ from those for digital broadcasting because an IP network is used. They use international Internet standards defined by IETF, etc. in the transmission layer. Figure 4-1 shows the protocol stack used in the IPTV Standards.

IPv4/IPv6UDP

RTSP

HTTP RTP(+FEC)SDP

PESTS

MPEG2H.264Video

AACMPEG1-L2

Audio

subtitle

Contentlayer

Communi-cationlayer

Content playback

control infomation

ECG

metadata

TTS

PSISI

Section

HTMLBML

BML/JPEG/PNGMNG

Content delivery serviceNavigationService

Servicelayer

TLS/SSL (available)HTTP

TCPIGMP/MLD

DataＣarrousel

Muliti-media(BML)

CAS./D

RM

license

DL

control data

IPv4/IPv6UDP

RTSP

HTTP RTP(+FEC)SDP

PESTS

MPEG2H.264Video

AACMPEG1-L2

Audio

subtitle

Contentlayer

Communi-cationlayer

Content playback

control infomation

ECG

metadata

TTS

PSISI

Section

HTMLBML

BML/JPEG/PNGMNG

Content delivery serviceNavigationService

Servicelayer

TLS/SSL (available)HTTP

TCPIGMP/MLD

DataＣarrousel

Muliti-media(BML)

CAS./D

RM

license

DL

control data

Figure 4-1 Protocol Stack used in the IPTV Standards

While the communication layer adopts the standard protocols of the Internet, the structure for video content on MPEG2-TS in the content layer reuses that for digital broadcasting almost

IPTVFJ STD-0001

-11-

without modification.

The technology elements used in the IPTV Standards can be classified as shown in Figure 4-2 according to the service approach phases described in the previous chapter. Each technology element is outlined below.

Service entryphase

・Network connection

・Servicediscovery

Content navigationphase

・Browser-based content navigation

・Resident-basedcontent navigation

Receiving deliveryService phase

・Content encoding

・Content transmission system

・CAS/DRM

・System control

Figure 4-2 Technical Elements in Each Process of the Service Approach

4.2 Overview of IPTV Technology Elements

4.2.1 Content Encoding

The encoding of video content, which is transmitted and viewed, in any delivery service is exactly based on the encoding specification for digital broadcasting.

MPEG2-TS is used for multiplexing. PSI, such as PAT and PMT, is used for control data. What differs from broadcasting is the fact that data is transmitted using TTS, which is a time-stamped TS packet. The reason is that an IP network, unlike broadcasting, is based on asynchronous transmission, and therefore clock synchronization information other than PCR is transmitted to ensure uninterrupted playing of content.

AV encoding is also based on the encoding specification for ISO MPEG just as digital broadcasting is. What currently differs from the encoding specification used in digital terrestrial television broadcasting, etc., is that IPTV also uses H.264/AVC, which is being increasingly

IPTVFJ STD-0001

-12-

adopted worldwide, in parallel to the above, to meet the need for efficient use of transmission bandwidth.

Encoding of subtitle data is also based on the specifications defined by ARIB.

Detailed specifications differ slightly from one delivery service to another. However, it is natural that at least the IP retransmission service uses a content encoding specification similar to that of TR-B14 and TR-B15 because its main purpose is basically to retransmit the same information as that transmitted by digital terrestrial television broadcasting and BS digital satellite broadcasting although it is necessary to convert some data.

4.2.2 Content Transmission Method

Although content transmission depends on how the delivery service is provided, in principle, Internet standards are used for it.

Two groups of streaming protocols are specified for the VOD service: RTSP and RTP that are suitable for the CDN Scope network environment, and HTTP that is suitable for the Internet Scope network environment.

For the download service, HTTP is specified as the transmission protocol for downloading content.

For the IP broadcasting service and IP retransmission service, the use of IGMP or MLD is specified for channel selection control for multicast services, the use of RTP as the streaming transmission protocol, as in the case of the VOD service.

4.2.3 CAS/DRM

CAS and DRM are specified as the technologies to provide pay delivery services and ensure copyright protection of content. CAS is applied to both the IP broadcasting service and IP retransmission service. It basically adopts the same architecture as the CAS in digital broadcasting, but differs from it in that it obtains a license through communication instead of EMM, which is used in broadcasting. DRM is applied to both the VOD service and download service. The receiver obtains a license for each item of content. The content key contained in the license is used to decrypt the encrypted content. The DRM applied to the VOD service and that applied to the download service are slightly different because of differences in the nature of these delivery services. While CAS and DRM are applied to different services and differ in architecture, they share some common features. Namely, they both obtain licenses from servers using secure communication, use AES for content encryption, and apply encryption to each TS packet. Although these IPTV Standards do not require the use of a specific CAS/DRM system, they assume a system model based on the integrated use of CAS and DRM. They also include

IPTVFJ STD-0001

-13-

reference information about the case where Marlin1

4.2.4 System Control

IPTV-ES is used for CAS and DRM.

Specifications for system control technologies boil down to the service scenario of each delivery service, and the specifications of several items of control information used to control the receiver operation.

In the VOD service, the receiver first obtains control information called content playback control information (metafile). This information contains information about the DRM operation, such as license acquisition; information about playback control, such as trick playback and chapters, in stream reception; and information about display of the playback state.

In the download service, download control information and content playback control information (partially the same as the specification for the VOD service) respectively provide information needed for the receiver operation in the download process and the playback process.

In the IP broadcasting service and IP retransmission service, PSI/SI packets, such as NIT, BIT, PAT and PMT, contained in the content stream, provide information needed for the receiver operations for channel selection and playback as is the case with digital broadcasting.

The specification of these items of control information specific to each delivery service enables the receiver to operate in the optimal manner in order to provide the delivery service properly, and the system, including servers, to operate in the proper sequence.

4.2.5 Resident-based Content Navigation

This technology refers to content navigation technologies implemented in applications resident in the receiver. More specifically, it means technologies related to EPG in multicast services, such as the IP broadcasting and IP retransmission services, and technologies related to ECG in on-demand services, such as the VOD and download services. These are essential for the receiver to provide an efficient and easy-to-understand means of content navigation. (ECG metadata and ECG for the VOD service are optional.)

SI packets, such as EIT and SDT, contained in the stream, are used for EPG in multicast services as is the case with broadcasting. In particular, in the IP retransmission service, SI packets of digital terrestrial television broadcasting and BS digital satellite broadcasting are retransmitted to the IP network without any modification.

ECG metadata is used for ECG in on-demand services. Metadata defined by the TV Anytime 1 Marlin･･･Content control system for home appliances and multimedia services. The technical specifications are available from Marlin Developer Community (MDC).

IPTVFJ STD-0001

-14-

Forum2

4.2.6 Browser-based Content Navigation

and further defined by ARIB in STD-B38 as metadata for server-type broadcasting are applied to this ECG metadata. The receiver obtains metadata from a metadata server as necessary, and provides the user with a content navigation screen based on ECG.

In this content navigation, service providers provide a content navigation screen. The receiver receives a multimedia description document written in HTML or BML from the server and displays a content navigation screen on its browser. In addition to its use for content navigation, this technology plays an even more important role in the promotion of pay services and the sales of content.

Although the specification of this technology is in principle independent of delivery services, it includes specifications specific to each delivery service, such as delivery service-specific plug-ins and an extended function of ECMAScript. This is because this content navigation technology requires an interface to activate delivery service-specific reception after content has been selected. In addition, general Web security technology is also required. Therefore, the specification includes that for device authentication, which is an efficient alternative to user authentication.

The specification used in the CDN Scope differs from that used in the Internet Scope. The service approach in the CDN Scope is written in BML while that in the Internet Scope is written in HTML. Although the presentation capability of BML and HTML is not so different, BML allows special control in which only a specific range of BML documents are permitted access to a delivery service by . Therefore, BML is suitable for the CDN Scope, in which a specific range of service providers provide delivery services. In contrast, HTML is suitable for the Internet Scope because it has broad applicability, links can be set up without any restriction, and any HTML document can equally have the same functions.

4.2.7 Service Discovery

Service discovery is required at the service entry, which is the first phase in the service approach described in the previous chapter. After a network connection has been established, the receiver needs to obtain information about what service can be received from which service provider and from which IPTV server. In particular, it needs to obtain information about the IPTV server that is required in the next phase, content navigation.

There is no specification about service discovery in the service approach in the Internet Scope. In principle, it is assumed in the Internet Scope that the information embedded in the receiver 2 TV Anytime Forum･･･Organization for standardization established in 1999, which standardizes content metadata, content navigation by metadata, rights management, etc.

IPTVFJ STD-0001

-15-

is used to access a relevant HTML document in a specific, so-called portal site, and thereby start browser-based content navigation.

In contrast, in the CDN Scope, the receiver starts with access to a specific URL, which is the URL of a CDN configuration information server. It then accesses multiple PF configuration information servers to obtain information needed for the approach to delivery services.

4.2.8 Network Connection

Network connection means the process of establishing a communication connection up to the IP layer and making IP addresses and other necessary network parameters available to other applications. Both IPv4 and IPv6 are specified as the IP protocol. Currently, IPv4 is used in the Internet in most cases, but IPv6 has been introduced in some CDNs, and is expected to be introduced in earnest in the future. Therefore, these IPTV Standards assume an environment using a mix of IPv6 and IPv4, and specify how to select one or the other. The IPTV Standards refer to Internet standard protocols for obtaining addresses and other network parameters.

Since the IPTV Standards concern not only delivery networks but also home networks, they show various forms of home networks and provide an operational guideline for home networks.

IPTVFJ STD-0001

-16-

Chapter 5 Structure of Specifications and Organization of Specification Documents in the IPTV Standards

This chapter describes the organization of the specification documents, and the position of each specification document within the IPTV Standards, and gives an overview of each specification document.

The IPTV Standards consist of the present document (overview) and eight specifications, that are five delivery service specification documents (one for each type of delivery service) and three service approach specification documents (one for each type of service approach). The organization of specification documents and the relationships among these documents are shown in Figure 5-1. Figure 5-2 shows mapping of the technology elements described in the previous chapter onto the organization of specification documents.

VODspecifications

Downloadspecifications

IPBroadcastingspecifications

Operationalspecifications

on IPretransmission

of digital

terrestrialtelevision

broadcastingIntegration

with broadcastingspecifications

Internetscope service

approachspecifications

CDNscope service

approachspecifications

Deliveryservicespecifications

Serviceapproachspecifications

Operationalspecifications

on IPretransmission

Of BS

digitalsatellite

broadcasting

* Operational specifications on IP retranmission of digital terrestrial television broadcasting includes the service approach specifications so that it can comletely cover the specifications for IP retranmission. It is related to the CDN scope service approach specifications for the cases where the IP retransmission service is operated with other delivery services.

*

*

Figure 5-1 Organization of Specification Documents

IPTVFJ STD-0001

-17-

Contentencoding

CAS/DRM

Contenttransmissionmethod

System control

Residen-basedcontent navigation

Browser-basedcontent navigation

Servicediscovery

Networkconnection

VOD Download IP broadcasting IP retransmission

CDN scopeservice approach

Internet scopeservice approach

Integration withbroadcasting

AV encoding/Subtitle encodingMultiplexing

DRM CAS

RTSP/RTPHTTP

streaming

Downloadprotocol

RTP streaming,multicast

Content playback control infomationDL control information

PSI/SI

BML for IPTV HTML for IPTVBML for broadcasting

(extended)

Configuration information

IPv4/v6 connection

Deliveryservice

specifications

Serviceapproch

specifications

Data broadcasting

encoding

ECG metadata

Figure 5-2 Mapping of the Technology Elements onto the Organization of Specification Documents

Each delivery service specification (VOD Specifications, Download Specifications and IP Broadcasting Specifications) specifies all technical information needed for each delivery service. Therefore, the service approach model described in Section 3.2 includes not only the delivery service receiving phase but also a resident-based content navigation specification specific to delivery services. (However, ECG metadata in the VOD service is included in the CDN Scope Service Approach Specifications because it is currently used only in the CDN Scope.) Each delivery service specification does not specify any specific operation. Rather, it covers technology elements used in all currently assumed operations so that it can be referenced as a library. However, it is not meant to ensure unlimited flexibility. With the above discussion taken into consideration, each delivery service specification defines as detailed specification as possible and provides as detailed guideline as possible for items that can be made specific and for operations that can be restricted.

As shown in Figure 5-2, each service approach specification (CDN Scope, Internet Scope, and Integration with Broadcasting) specifies all technical information needed for each service approach type (namely, network connection, service discovery, and browser-based content navigation). (However, ECG metadata for the VOD service is included in the CDN Scope Service

IPTVFJ STD-0001

-18-

Approach Specifications although it is used for resident-based content navigation, as mentioned earlier.) Although not shown in Figure 5-2, another role is assumed for the service approach specification. That is, each service approach specification serves as the IPTV service operation specifications for each approach to delivery services. For example, the CDN Scope Service Approach Specifications defines detailed operational specifications of delivery services, such as the VOD and IP broadcasting services, so that it can serve as IPTV service operation specifications for this service approach. The reason for giving two roles to service approach specifications is that the current service demands allow only one set of operation rules to be applied to each type of service approach.

The IP retransmission specifications (Operational Specifications for IP Retransmission of Digital Terrestrial Television Broadcasting and Operational Specifications for IP Retransmission of BS Digital Satellite Broadcasting) can be considered delivery service specifications in that these are specific to delivery services. The IP retransmission specifications are related to the CDN scope service approach specifications for the cases where the IP retransmission service is operated with other delivery services (ex. IP broadcasting services). Further, Operational Specifications for IP Retransmission of Digital Terrestrial Television Broadcasting includes the service approach specifications so that it can completely cover the specifications for IP retransmission.

Except for the IP retransmission specifications, it is necessary to refer to at least one service approach specification and one delivery service specification, whether a service provider operates an IPTV service in a specific manner or a manufacturer designs an IPTV receiver with a specific profile.

Since the VOD Specifications, the Download Specifications, and the Internet Scope Service Approach Specifications include references to the specifications defined by the Digital TV Informatization Research Group3

3 Digital TV Informatization Research Group･･･Organization for standardization established in 2003, which develops and releases specifications of the communication interface and the browser for Digital TV. It also develops and releases guidelines on authoring content which is compliant with its specifications.

, it is necessary to refer to the specifications by this Research Group when reading the above specifications.

IPTVFJ STD-0001

-19-

IPTV Standard

Overview IPTVFJ STD-0001 Version 1.1

September 11, 2008 Version 1.0 Issued September 30, 2009 Version 1.1 Issued

IPTV Forum Japan

3F, Futaba Akasaka Bldg. 8-5-43 Akasaka, Minato-ku, Tokyo 107-0052, Japan

Phone: 03-5858-6685 FAX: 03-5858-6675

e-mail: sec@iptvforum.jp