1. IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-09-0141-00-bcst
Title: b Proposal
Date Submitted: Sept 13, 2009
Presented at IEEE session #34 in Hawaii
Authors or Source(s):
 Catherine Livet (InterDigital), Michelle Perras (InterDigital)
Abstract: This document provides a MIH Proposal for the support of BCAST services. This answers to the call of proposal IEEE /0129r1-bcst
bcst

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
bcst

3. Table of Contents Introduction Assumptions
Considerations for HO with Broadcast Services
Extra Features supported by this proposal
Summary of the impacts on MIH framework
Architecture proposal
Network and Mobile Architecture
Enhancements to SAP and MIH Messages
Examples of new IEs
Questions, Open discussion & Feedback
bcst

4. Table of Contents Introduction Assumptions
Considerations for HO with Broadcast Services
Extra Features supported by this proposal
Summary of the impacts on MIH framework
Architecture proposal
Network and Mobile Architecture
Enhancements to SAP and MIH Messages
Examples of new IEs
Questions, Open discussion & Feedback
bcst

5. Introduction
This proposal responds to the “Call for Technical Proposals on Handovers with Broadcast Networks” ( /0129r1-bcst)
Additions to specification are required to address handovers with Broadcast or Downlink Only (DO) technologies.
bcst

6. Table of Contents Introduction Assumptions
Considerations for HO with Broadcast Services
Extra Features supported by this proposal
Summary of the impacts on MIH framework
Architecture proposal
Network and Mobile Architecture
Enhancements to SAP and MIH Messages
Examples of new IEs
Questions, Open discussion & Feedback
bcst

7. Assumptions (1/2)
Multiple radios may be used simultaneously at the mobile
A Broadcast session can be handed over according to the following scenarios
From (1 DO and 1 Bidirectional) to (1 Bidirectional)
E.g. for a DVB session with the Return channel over 3GPP
The DVB Session is HO from DVB to 3GPP
The return channel remains on 3GPP
From (1 Bidirectional) to (1 DO and 1 Bidirectional)
E.g. for a 3GPP session with Return Channel over 3GPP
The 3GPP session is HO to DVB
The Return channel remains on 3GPP if still available
Return Channel HO only scenario
E.g. for a DVB session with Return Channel over 3GPP
The DVB data remains on DVB
The return channel HO from 3GPP to WLAN
From (1 DO) to (1 Bidirectional) with no return channel
E.g. a DVB session is HO to 3G
bcst

8. Assumptions (2/2)
Service Distribution/Management might be based on different broadcasting services
OMA BCAST, IPDC
Different Distribution Networks are also considered
DVB/NGH, 3GPP MBMS, 3GPP2 BCMCS, MediaFLO, DMB
When the HO is complete, the Service Distribution is responsible for the service redirection to the new technology
The service may have to be initialized on the new interface if not already started
bcst

9. Table of Contents Introduction Assumptions
Considerations for HO with Broadcast Services
Extra Features supported by this proposal
Summary of the impacts on MIH framework
Architecture proposal
Network and Mobile Architecture
Enhancements to SAP and MIH Messages
Examples of new IEs
Questions, Open discussion & Feedback
bcst

10. Considerations for HO with Broadcast Services (from 21-09/41r4 Use cases and requirements)
Service discovery may be needed
Target network selection can be mobile-based or network-based
The target network might provide the program as multicast or unicast
Handover commands and information can be sent over DO network
Information Service can use Push mechanism on DO technology
Information services for DO technologies or enhancements to existing bidirectional technologies may be needed
Information services can be used to identify a program
Event services may be needed for monitoring DO technology behavior
Command services may be needed for setting up the new link
A Return Channel may be required to support interactive services & to provide more granularity in the location information
bcst

11. Considerations for HO with Broadcast Services (from 21-09/41r4 Use cases and requirements)
can be used for candidate network and PoA selection
Means for discovering program availability at the target network to allow for service continuity may be needed
Mobile reporting about the available services; network can provide service availability based on mobile geo-location; initialization of the service in the target network may be required; indexing/bookmarking
The program may or may not be available at the target network
If the service is available on the target network,
Information may be required to perform network-specific actions (e.g. successful frequency tuning)
Security may or may not be needed
Additional information relevant to DO technology streams must be given in the primitives
Means to perform resource management at the target network may be needed
e.g. Determination of the number of listeners and required resources
bcst

12. Table of Contents Introduction Assumptions
Considerations for HO with Broadcast Services
Extra Features supported by this proposal
Summary of the impacts on MIH framework
Architecture proposal
Network and Mobile Architecture
Enhancements to SAP and MIH Messages
Examples of new IEs
Questions, Open discussion & Feedback
bcst

13. Extra Features supported by this proposal
The current proposal provides the means to distribute the new IP address of the Service Management/Distribution
e.g. after a HO, the same service management/distribution with a new IP address or a new service management/distribution might be reached
The new IP address needs to be provided to the broadcast application in the mobile
bcst

14. Table of Contents Introduction Assumptions
Considerations for HO with Broadcast Services
Extra Features supported by this proposal
Summary of the impacts on MIH framework
Architecture proposal
Network and Mobile Architecture
Enhancements to SAP and MIH Messages
Examples of new IEs
Questions, Open discussion & Feedback
bcst

15. Summary of the impacts on MIH
The current framework assumes handover between bi-directional technologies only
The channel direction (Bi or DO) for the current/target networks must be considered before performing a HO
The current framework uses multicast MIH messaging for discovery only
MIH must expand broadcast/multicast to other MIH messages
In the current framework, the MIH Server has no interfaces with others nodes
An new interface with MobileTV service distribution/management is required
In the current framework, there is no application specific information exchanged between the MIHFs
MIH must support the transport of application specific information between MIH Server and MIH Client
The application information must be exchanged between local MIHF and MIH Users
E.g. if the MIH User is a MobileTV Application , the information can be the synchronization on target network, service discovery, service already initialized, etc …
bcst

16. Table of Contents Introduction Assumptions
Considerations for HO with Broadcast Services
Extra Features supported by this proposal
Summary of the impacts on MIH framework
Architecture proposal
Network and Mobile Architecture
Enhancements to SAP and MIH Messages
Examples of new IEs
Questions, Open discussion & Feedback
bcst

17. Generic Hybrid Broadcast and Mobile Architecture
Source : document bcst
bcst

18. Architecture Proposal
MIHF Server can be co-located or not with SD or SM
MIHF needs to interface with SM/SD
MIHF and SD/SM need to be able to exchange information such as number of listeners of the same program, user specific information (program currently viewed, synchronization information, etc…)
MIH Protocol Messages
Need to be updated to relay the SD or SM related information to the MIH Client
Need to be updated to support MIH Multicast messaging
bcst

19. Possible Approach for DVB in 802.21
3GPP /
3GPP2
Network
MIH Function
802 Network
MIH
Users
802 Interface
Mobile Node
DATA
3GPP/
Interface
Higher Layer
Transport
Legend
MIH Message Transport
MIH Local Interface
MGMT
DVB
Network
MIH Function
MIH
Users
Higher Layer
Transport
Interface

20. Mobile Architecture MIH_LINK_SAP MIH_SAP
Need to be updated to support broadcast technology
E.g. need to be able to create a multicast vs unicast link
MIH_LINK_SAP mapping to DVB-H, DMB, MediaFlo primitives are required
MIH_SAP
New IS can be exchanged such as Video Codec Required, QoS bandwidth expected
MIH can trigger OMA BCAST operation

21. Table of Contents Introduction Assumptions
Considerations for HO with Broadcast Services
Extra Features supported by this proposal
Summary of the impacts on MIH framework
Architecture proposal
Network and Mobile Architecture
Enhancements to SAP and MIH Messages
Examples of new IEs
Questions, Open discussion & Feedback
bcst

22. Examples of New IEs Multicast Group
Required by the client to listen to specific multicast messages
IP Address of the Service Management
Required by the Client Application after an HO to be able to interact with the Service Management
Application Specific Information
Required by the MIH Server or by the SM to provide the appropriate program to the user
Required by the Client Application after an HO to synchronize with the new Service Management
Contains information such as program currently tuned, tuning information, schedule for a specific program in this coverage area
Number of listeners of a specific program per network
Required by the MIH Server to take HO decision
bcst

23. Table of Contents Introduction Assumptions
Considerations for HO with Broadcast Services
Extra Features supported by this proposal
Summary of the impacts on MIH framework
Architecture proposal
Network and Mobile Architecture
Enhancements to SAP and MIH Messages
Examples of new IEs
Questions, Open discussion & Feedback
bcst