NAS Impact of MBMS
Multimedia Broadcast/Multicast services
Agenda
Overview
MBMS Procedures
Subscription
Joining
Service announcement
Data transfer
Leaving
MBMS notification
Session start
Session Stop
MBMS MULTICAST procedures
Subscription--setting up the connection between user and service provider, and authorizing user to receive relevant MBMS service.
Service announcement--notifying user of services to be provided. For example, the system will rebroadcast-a football match in Beijing at 7:00 p.m.
Joining--indicating that user joins a group, i.e. the user informs the network that he or she is willing to receive this multicast service.
MBMS multicast mode bearer set up--setting up network resources for MBMS data transfer.
MBMS notification--notifying user of MBMS data transfer to be performed immediately.
Data transfer--indicating the process of transferring MBMS service data to user.
MBMS multicast mode bearer release--indicating the releasing of network resources after MBMS service data transfer finishes.
leaving--corresponding to 002 joining, which indicates that a user is leaving a group, i.e. the user doesn't want to receive the data of a certain service any more.
MBMS MULTICAST procedures
MBMS Use case with Example
subscription to service1
User service join
service leave
subscription to service1
UE1 events
Transfer of data
Subscription can be at any time
Start Service 1 announcement
1st Session start
Data transfer
1st session stop Service 1 Session 2
Service 1 events
Service 1 session1
UE2 events
Announcement
time
Stop Service 1 announcement
Idle period of seconds
Data transfer
Data transfer
Service join by the user can be at any time
Data sent to UE1
Data sent to UE1 and UE2
Data sent to UE1 and UE2
Data sent to UE2
Main function of SM is to support • PDP context handling of the user terminal and the network.
• MBMS context handling within the MS and the network, which allows the MS to receive data from a specific MBMS source.
Functionality of Session- Management
Session Manage States in MS/Network
PDP - Inactive In this state there is no user data transfer can be possible.
PDP - Active PendingActivation request is sent and yet received no response to other side(MS/Nw)
PDP – ActivePDP context has been set up, hence user data transfer is possible.
PDP – Inactive PendingDe-activation request is sent and yet received no response to other side(MS/Nw)
PDP – Modify PendingModification request is sent and yet received no response to other side(MS/Nw)
MBMS States in MS/Network
MBMS - Active pendingThis state exists when an activate MBMS context request is sent out.
MBMS - ActiveThis state indicates that the MBMS context is active.
MBMS – Inactive pending This state exists when the network has requested the MS to deactivate an MBMS context.
Activate PDP Context Request
MS Activate PDP Context Accept
PDP type,PDP AddressQoS Requested,Access Point,…
PDP type,PDP AddressQoS Negotiated,…
MS Network
MT PDP Context Activation Procedure
orMS Activate PDP Context Reject
Reject cause like insufficient resource ’#81’
Initiated by Network
REQUEST- Activate PDP Context
[ PDP type,PDP Address QoS Requested,Access Point,…]
Start T3380
Stop T3380
Start T3385
Stop T3385
Activate MBMS Context Request
Activate MBMS Context Accept
PDP type,PDP AddressQoS Requested,Access Point,…
PDP type,PDP AddressQoS Negotiated,…
MS Network
MBMS Context Activation Procedure
or Activate MBMS Context Reject
Reject cause like insufficient resource ’#81’
REQUEST- Activate MBMS Context
[ TMGI, Address QoS Requested,Access Point,…]
Start T3380
Stop T3380
Start T3385
Stop T3385
MBMS-ACTIVE- PENDING
MBMS-ACTIVE
PDP-INACTIVE
DI (ACTIV. MBMS CONTX. REJ)
DR: GMMSM-DATA-REQUEST (Message), i.e. message sent by an MS DI: GMMSM-DATA-INDICATION (Message), i.e. message received by an MS
DI (DEACTIV. PDP CONTX. REQ)
DR (DEACTIV. PDP CONTX. ACC)
DI (ACTIV. MBMS CONTX. ACC)
DI (REQ. MBMS CONTX. ACTIV)
DR (ACTIV. MBMS CONTX. REQ)
Figure 6.1a/3GPP TS 24.008: Session management states for MBMS context handling in the MS
Session management states for MBMS context
6. Activate MBMS Context Request
SGSN RAN
8. Security Functions
UE BM-SC
13. Create MBMS Context Response
5. Request MBMS Context Activation
10. Create MBMS Context Request
4a. MBMS Notification Request
14. MBMS Registration Request
14. MBMS Registration Response
15. Provision of MBMS UE Context to RAN
4b. MBMS Notification Response
1. PDP Context Activation 2. IGMP Join
12. MBMS Registration Response
12.MBMS Registration Request
11. MBMS Authorization Response 11. MBMS Authorization Request
3. MBMS Authorization Request 3. MBMS Authorization Response
7. MBMS Notification Reject Request
7. MBMS Notification Reject Response
17. Activate MBMS Context Accept
GGSN
GGSN
9. Invoke Trace
16. Invoke Trace
Synchronize MBMS context
It is possible that MBMS/PDP contexts might go out of synch between MS and Network.Synchronization of MBMS context is done by RAU / Service request Procedures(UMTS)
The purpose of the MBMS context status information element is to indicate the state of each MBMS context which can be identified by an NSAPI.
MBMS context status IEI is included by the sender entity to communicate the activecontext to the receiving entity.
Receiving entity shall synchronize itself with the sending entity by de-activating the Active MBMS contexts locally which are marked as In-active in MBMS context status information
1 1 0 0 0 1 1 1 0 0Mbms status bitmap Mbms status bitmap
Service Request procedure
Counting the number of mobile stations in a cell which are interested in a specific MBMS service.
Requesting the establishment of a point-to-point Radio Bearer for receiving a MBMS service.
MBMS bearers
Separate MBMS Bearer Services for 2G and 3G for the same MBMS User ServiceTypically with different QoS. For this purpose two IP multicast addresses and the associated two TMGIs should be allocated for the same MBMS user service
3G 2G
SGSN
• Different QOS• IP multicast address•TMGI
MT PDP Context De-activation
General PDP Context
MBMS context
MBMS context
Existing PDP context deactivation procedure is used for deleting the MBMS contextsIn both MS and Network side
GGSN
6. Deactivate MBMS Context Response
5. Deactivate MBMS Context Request
SGSN RAN UE BM-SC
3. UE Removal Request
1. IGMP Leave
4. MBMS UE Context Deactivation Request
13. Deregistration Request
13. Deregistration Response
11. MBMS Deregistration Request
11. MBMS Deregistration Response
8. RAN Resource Release
10. Deactivation Indication
2. Leave Indication
4. MBMS UE Context Deactivation Response
10. Deactivation Confirmation
GGSN
12. Delete MBMS Context Response
7. MBMS UE De-Linking Request
7. MBMS UE De-Linking Response
9. Delete MBMS Context Request
Temporary Mobile Group Identity (TMGI)
Used in paging information for broadcast service in an MBMS mobile communication system
- Received by UE in MBMS notification procedure.
- BM-SC allocates a globally unique TMGI per MBMS bearer service
• MBMS bearer service
Temporary Mobile Group Identity
• Notification of MBMS session during an ongoing CS or PS domain "connection" in GERAN is not supported
• How does GERAN counts the number of users that are interested in a specific MBMS service which are present in a cell
OPEN ISSUES
The Opportunity