DVB-H Interface Study (CBMS1 ~ CBMS7)

Interface Further Study in DVB-H (CBMS1 ~ CBMS7)

1). Overall Protocol Stack:

http://docs.google.com/View?id=ddh56dhg_171fd5gqkf2

1.1). Service Access Points on the broadcast network

Solution	Service Access Points on the broadcast network Description	Service Access Points on the broadcast network Description
DVB-H	DVB Signalling	Access point mainly used by tuning and mobility management enablers to obtain relevant configuration information.
Streaming	AV Streaming	Access Point for all Audio/Video streams delivered over the Broadcast network
Download	File/Data Download	Access Point for all data delivered over the Broadcast network via FLUTE (one time or carousel based)
IP MC	IP Multicast	Access point to IP multicast for application specific usage of IP multicast.
UDP MC	UDP Multicast	Access point to UDP multicast for application specific usage of IP multicast datagram services.

1.2). Protocol Stack - Interface Used in DVB-H (CBMS)

http://docs.google.com/View?id=ddh56dhg_205g5bmqbg7

2). Reference Points / Interface and Fucntions:

2.1). Protocols over reference point CBMS-1

Ref Point	End Points	Usage
CBMS-1	From Broadcast network To Terminal	Broadcast network-specific singnalling, PSI/SI signalling in DVB-H.

http://docs.google.com/View?id=ddh56dhg_207gxbf8ghc

§ Reference point CBMS-1 is between broadcast network and terminal.

§ It is used to signal IP streams (TS) with PSI/SI information (or tables) over the broadcast bearer.

§ These protocols are subject of TS 102 470

2.2). Protocols over reference point CBMS-2

Ref Point	End Points	Usage
CBMS-2	From Service Application To Terminal	Content Flow, including: • A/V streams. • Auxiliary data. • Files delivered by a carousel mechanism (clips, software, etc.).

http://docs.google.com/View?id=ddh56dhg_209fmqd9kfh

§ Reference point CBMS-2 is between service application and terminal.

§ It is used for content delivery over the broadcast network.

§ Both Stream Delivery (via RTP/UDP) and File Delivery (via FLUTE/ALC) are considered.

§ The contribution side for streams an encapsulation may be used as part of the head-end interface.

§ An RTP in TCP encapsulation method is defined in RFC 2326

§ These CDP protocols (Content Delivery Protocols) are subject of TS 102 472

2.3). Protocols over reference point CBMS-3

Ref Point	End Points	Usage
CBMS-3	From Service Management To Terminal	Electronic Service Guide (metadata, point-to-multipoint delivery).

http://docs.google.com/View?id=ddh56dhg_211f5jmd2g3

§ Reference point CBMS-3 is between service management and terminal.

§ The ESG is delivered (via FLUTE/ALC) on this reference point.

§ ESGC: Encoded ESG information is transported in ESG fragment containers.

§ L4/L5 protocol levels at the head-end side are subject of further study.

§ The ESG is subject of document “IP Datacast over DVB-H: Electronic Service Guide (ESG)”, the FLUTE/ALC/LCT delivery protocols are subject of TS 102 472

2.4). Protocols over reference point CBMS-4

Ref Point	End Points	Usage
CBMS-4	Between Service Management and Terminal (only for the interactive network)	• Electronic Service Guide (metadata, point-to-point delivery). • Access Control to service applications. • This reference point exists only if the IPDC terminal includes an endpoint for the interactive network and if service management supports this reference point.

http://docs.google.com/View?id=ddh56dhg_213fsrfptgj

§ Reference point CBMS-4 is between service management (Logical ESG Aggregator) and terminal (Service and content description handler) over the interaction channel.

§ This reference point is optional. If available in the Terminal and configured for in the Service Management, it is used for ESG post delivery repair.

§ This reference point may be used e.g. to retrieve ESG information via the interaction channel. The current IP Datacast over DVB-H specification does not yet provide for this.

2.5). Protocols over reference point CBMS-5

Ref Point	End Points	Usage
CBMS-5	Between Service Application and Terminal (only for the interactive network)	• Point-to-point transport services (SMS/MMS, IP connectivity). • This reference point exists only if the IPDC terminal includes an endpoint for the interactive network and if service application supports this reference point. • Service applications may require this reference point.

http://docs.google.com/View?id=ddh56dhg_215fvh5s4hp

§ Reference point CBMS-5 is between service application and terminal via the interaction network.

§ This reference point is optional for terminals.

§ It is used for general interaction between terminal service applications.

§ In IP Datacast only for File Post Delivery Repair (via HTTP) it is defined up the application level.

§ File Post Delivery Repair is subject of TS 102 472

2.6). Protocols over reference point CBMS-6

Ref Point	End Points	Usage
CBMS-6	From Service Management To Broadcast network	Configuration of the DVB-H transport (number of services, allocated bandwidth, etc.).

http://docs.google.com/View?id=ddh56dhg_217cx9rctwv

§ Reference point CBMS-6 is between service management (resource provisioning and scheduling) and broadcast network (DVB-H service handler).

§ CBMS-6 comprises head-end interfaces. Therefore, mention of Muxconfig, SOAP, and SNMP are non-normative.

2.7). Protocols over reference point CBMS-7

Ref Point	End Points	Usage
CBMS-7	Between Service Application and Service Management	• Service Application Declaration. • Service Application Description, including content description/metadata.

http://docs.google.com/View?id=ddh56dhg_2198bpxf7c5

Reference point CBMS-7 is between service application and service management.

§ CBMS-7 comprises head-end interfaces. Therefore, mention of SOAP is non-normative

DVB-H Reference Architecture and Interface

DVB-H - Reference Architecture and Interface Overview

1). DVB-IPDC Reference Architecture:

http://docs.google.com/View?id=ddh56dhg_205g5bmqbg7

2). Reference Points / Interfaces:

Ref Point	End Points	Usage
CBMS-1	From Broadcast network To Terminal	Broadcast network-specific singnalling, PSI/SI signalling in DVB-H.
CBMS-2	From Service Application To Terminal	Content Flow, including: • A/V streams. • Auxiliary data. • Files delivered by a carousel mechanism (clips, software, etc.).
CBMS-3	From Service Management To Terminal	Electronic Service Guide (metadata, point-to-multipoint delivery).
CBMS-4	Between Service Management and Terminal (only for the interactive network)	• Electronic Service Guide (metadata, point-to-point delivery). • Access Control to service applications. • This reference point exists only if the IPDC terminal includes an endpoint for the interactive network and if service management supports this reference point.
CBMS-5	Between Service Application and Terminal (only for the interactive network)	• Point-to-point transport services (SMS/MMS, IP connectivity). • This reference point exists only if the IPDC terminal includes an endpoint for the interactive network and if service application supports this reference point. • Service applications may require this reference point.

Ref Point	End Points	Usage
CBMS-6	From Service Management To Broadcast network	Configuration of the DVB-H transport (number of services, allocated bandwidth, etc.).
CBMS-7	Between Service Application and Service Management	• Service Application Declaration. • Service Application Description, including content description/metadata.

Ref Point	End Points	Usage
X-1	Between Content Creation and Service Application	Provision of content to Service Application, including: • Content essence. • Content description/metadata. • Content control policy,
X-2	Between Interactive Network and Terminal	Interactive network specific interactions (authentication, mobility management, specific services such as voice, etc.).
X-3	Between Service Management and Interactive Network	This reference point may be used to access specific functions available in the interactive network, such as subscriber management or billing functions.

§ CBMS = Convergence of Broadcast and Mobile Services

3). Functional Entity OV:

3.1). Content Creation

§ This is the primary source of content for distribution over IP Datacast. It may provide support for delivery paradigms, such as streaming.

§ Provides base material for content descriptions.

3.2). Service Application

§ Aggregates content from multiple sources and their related metadata in order to provide a particular service application.

§ Provides the head-end application logic.

§ Responsible to provide content encoded in the format understood by the terminal either via streaming or file carousel delivery.

§ Generates service description metadata to be used in the Electronic Service Guide (to be provided at CBMS-7).

§ Interaction end-point for terminals to interact with service application.

§ Service Protection provision.

§ A Service Application entity may exist for each application that is provided in IP Datacast.

3.3). Service Management

§ Consists of four sub-entities, which may be instantiated independently:

1. Service configuration and resource allocation:

§ Registration of service applications that contend for bandwidth of the broadcast bearer (i.e. one DVB-H IP platform in one DVB transport stream).

§ Assignment of services to location (wrt. Broadcast network topology), to bandwidth and schedules services over time.

§ There is one instance of this sub-entity associated with a broadcast bandwidth contention domain.

2. Service Guide Provisioning application:

§ Aggregation of ESG (metadata information) pieces from the service applications.

§ There may be multiple instances of this sub-entity.

3. Security / Service protection provision:

§ Management of user access to service applications.

4. Location services:

§ The service management entity may provide location services to service application(s) in a manner that is independent of the way they are actually obtained (such as interaction bearer network functionality or GPS).

3.4). Broadcast Network

§ Multiplexing of service applications at IP level.

§ Assignment of IP flows on DVB-H time slices (IP Encapsulation).

§ Transmission over DVB-H.

§ Security/Service protection provisioning

3.5). Interactive Network

§ Provision for terminal to interact with service management and/or service application.

§ This entity exists only if the IPDC-DVB-H terminal includes an endpoint for it and if service management and/or service application support the relevant reference points. Service applications may require communication over the interactive network.

§ May provide additional functionalities to Service Application or Service Management, such as Location Services (may require additional reference point)

§ Security/Service protection provisioning

3.6). Terminal

§ The user device.

§ Point of acquisition and consumption for content.

§ Client of network and service resources.