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.

MBMS OV - (4) Architecture in MBMS and E-MBMS

1.1. MBMS Architecture in 3G Overview

The MBMS Bearer Service Architecture is defined in 3GPP TS 23.246. The MBMS User Service interfaces to the MBMS system via 3 entities.

- The BM-SC.

- The GGSN.

- The UE.

- A functional entity, the Broadcast Multicast Service Centre (BM-SC) provides a set of functions for MBMS User Services. BM-SC functions for different MBMS User Services may be supported from the same or different physical network elements.

- The BM-SC provides functions for MBMS user service provisioning and delivery to the content provider. It can also serve as an entry point for IP MBMS data traffic from the MBMS User Service source.

- The GGSN serves as an entry point for IP multicast traffic as MBMS data from the BM-SC

Figure: MBMS bearer service architecture

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

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

The existing PS Domain functional entities (GGSN, SGSN, UTRAN, GERAN and UE) are enhanced to provide the MBMS Bearer Service.

1.2. E-MBMS Architecture in LTE EPS Overview

Figure: E-MBMS bearer service architecture

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

MBMS Data Sources and Content Provider to BM-SC

- The reference point from the content provider to the BM-SC is not standardised by 3GPP in this release of the specification

1.3. E-MBMS deployment scenarios in LTE

In terms of deployment scenarios of MBMS in E-UTRAN, the following alternatives can be listed:

- Carrier type: dedicated vs. mixed carrier;

- MBSFN transmission: multi-cell vs. single-cell transmission;

- Radio bearer type: p-t-m vs. p-t-p;

- Counting: yes or no;

- Audience measurement: yes or no;

- ON/OFF control of MBMS service delivery: yes or no;

- PTP / PTM radio bearer switching: yes or no

Table below lists the combinations of the above alternatives that are specifically supported in E-UTRAN:

Scenario	Carrier	Transmission	Radio Bearer Type	Counting	remark
1	Dedicated	Multi-cell	p-t-m	No	From 1 to n cells; Audience Measurement (FFS)
2	Mixed	Multi-cell	p-t-m	No	Audience Measurement (FFS)
3	Mixed	Single-cell	p-t-m	Yes