1. IEEE 802.21 MEDIA INDEPENDENT HANDOVER
DCN: bcst
Title: Broadcast Handover Architecture
Date Submitted: July 10, 2009
Presented at IEEE session #33 in SF
Authors or Source(s):
Hongseok Jeon, Eunah Kim, Hyunho Park, Junghoon Jee, Changmin Park (ETRI)
Abstract: General functional architecture for broadcast handover based on OMA BCAST and IPDC.

2. IEEE 802.21 presentation release statements
This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE
The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws < and in Understanding Patent Issues During IEEE Standards Development

3. Legacy Architecture
802.21b architecture in 21-09/0041r3 raises some questions;
Why WLAN is included in the broadcast network?
Why OMA BCAST has only bidirectional technologies as its bearers?
What is difference between Content Creation and Content Provider?
What is service provider?
We need to generalize and clarify the architecture.
Source: bcst-broadcast-services-use-cases-and-requirements.

4. Our Approach
802.21b is based on a strong trend towards convergence between telecommunication and classical broadcast sectors.
Two standard efforts have been emerged as a result of this convergence;
OMA Mobile Broadcast Service Enabler Suit (BCAST)
DVB Internet Protocol Datacasting (IPDC)
Since OMA BCAST and IPDC will be key users of b, b architecture should be based on them.
This contribution first reviews the functional architecture of BCAST and IPDC, and suggests a general architecture of b with their common functional components.

5. OMA BCAST Architecture (1/2)
Source: Mobile Broadcast Service Architecture, Approved Version 1.0 – 12 Feb. 2009, OMA-AD-BCAST-V1_ A

6. OMA BCAST Architecture (2/2)
Content Creation:
Source of contents (e.g. stream server)
Providing base material for content descriptions (e.g. media type, codec)
BCAST Service Application:
Translating (e.g. encoding.) if a media type and CODEC of the contents are different from those of BCAST standard.
Providing additional information (e.g. user location, user profile) as well as contents descriptions.
Interaction related to BCAST service.
BCAST Service Distribution/Adaptation:
Aggregating and delivering BCAST services.
Determining of a suitable bearer with the given information.
Performing adaptation to the specific bearer.
BCAST Subscription Management:
Service provisioning such as subscription and payment.

7. IPDC Architecture (1/2)
Source: IP Datacast over DVB-H: Architecture - TR v1.1.1

8. IPDC Architecture (2/2) Content Creation: Service Application:
Primary source of content
Service Application:
Aggregating content from multiple sources and their related metadata.
Encoding streaming content for the terminal
Generates service description metadata(e.g. title, genre, and time) for Electronic Service Guide (ESG)
Service Management:
Service configuration and resource allocation
Assignment of services to location, to bandwidth and schedules services over time.
Service Guide Provisioning
Aggregation of ESG from service applications
Security/service protection provision
Management of user access to service applications

9. Common Functional Components
OMA BCAST
IPDC
Content Creation :
Primary source of content
Content Creation
Content Creation
BCAST Service Application
Service Application
Service Provider :
Aggregation and delivery
Determination of a suitable bearer
Adaptation to the specific bearer
BCAST Service Distribution
/Adaptation
BCAST Subscription Management
Service Management
Service Management:
Service provisioning
Service configuration
Resource allocation

10. Proposed General Architecture
MIH IS
MIHF
Content
Creation
Service Provider
Service Management
Broadcast
Network
Mobile
Network
Data Path
Control Path
MIH Path
MIHF
Controlled content
(by BCAST or IPDC)
DVB-H
802.11
802.16
Uncontrolled contents