NAS Impact of MBMS

Multimedia Broadcast/Multicast services

 Agenda

Overview

MBMS Procedures
 MBMS MULTICAST procedures

Subscription

Service announcement
Joining

Session start

MBMS notification

Data transfer

Session Stop
Leaving
 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 Use case with Example

Subscription can be Service join by the

at any time user can be at any
time

UE1  time
events
subscription User  service 
to service1 service  leave
join
subscription
UE2  to service1
events

Idle period Data  Data  Data 

Service 1  of seconds transfer transfer transfer
events
Start Service 1  1st Session  1st session stop  Stop Service 1 
announcement start Service 1 Session 2 announcement
Service 1 session1

Transfer Announcement
of data
Data sent to Data sent to
Data sent UE1 and UE1 and Data sent
to UE1 UE2 UE2 to UE2
 Functionality of Session- Management

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.
 Session Manage States in MS/Network
PDP - Inactive
In this state there is no user data transfer can be possible.

PDP - Active Pending

Activation request is sent and yet received no response to other
side(MS/Nw)

PDP – Active
PDP context has been set up, hence user data transfer is
possible.

PDP – Inactive Pending

De-activation request is sent and yet received no response to
other side(MS/Nw)

PDP – Modify Pending

Modification request is sent and yet received no response to
other side(MS/Nw)
 MBMS States in MS/Network

MBMS - Active pending

This state exists when an activate MBMS context request is sent
out.

MBMS - Active
This 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.
 MT PDP Context Activation Procedure

MS Network

REQUEST- Activate PDP Context

Start
[ PDP type,PDP Address QoS Requested,Access Point,…] T3385

Activate PDP Context Request Stop

Start
T3380 PDP type,PDP Address T3385
QoS Requested,Access Point,…

MS Activate PDP Context Accept

PDP type,PDP Address
Stop
QoS Negotiated,…
T3380
or
MS Activate PDP Context Reject
Reject cause like insufficient resource ’#81’

Initiated by Network
 MBMS Context Activation Procedure

MS Network

REQUEST- Activate MBMS Context

Start
[ TMGI, Address QoS Requested,Access Point,…] T3385

Activate MBMS Context Request Stop

Start
T3380 PDP type,PDP Address T3385
QoS Requested,Access Point,…

Activate MBMS Context Accept

PDP type,PDP Address
Stop
QoS Negotiated,…
T3380
or
Activate MBMS Context Reject
Reject cause like insufficient resource ’#81’
Session management states for MBMS context
DI (REQ. MBMS CONTX. ACTIV) PDP-INACTIVE

DR (ACTIV. MBMS DR (DEACTIV. PDP

CONTX. REQ) CONTX. ACC)

DI (ACTIV. MBMS CONTX. REJ)

DI (DEACTIV. PDP CONTX. REQ)

MBMS-ACTIVE-
PENDING

DI (ACTIV. MBMS CONTX. ACC)

MBMS-ACTIVE

DR: GMMSM-DATA-REQUEST (Message), i.e. message sent by an MS

DI: GMMSM-DATA-INDICATION (Message), i.e. message received by an MS

Figure 6.1a/3GPP TS 24.008: Session management states for MBMS context handling in the MS
UE RAN SGSN GGSN BM-SC

1. PDP Context Activation

2. IGMP Join
3. MBMS Authorization Request
3. MBMS Authorization Response
4a. MBMS Notification Request
4b. MBMS Notification Response
5. Request MBMS Context Activation

6. Activate MBMS Context Request

7. MBMS Notification Reject Request

7. MBMS Notification Reject Response

8. Security Functions

9. Invoke Trace GGSN

10. Create MBMS Context Request

11. MBMS Authorization Request

11. MBMS Authorization Response

12.MBMS Registration Request

12. MBMS Registration Response

13. Create MBMS Context Response

14. MBMS Registration Request

14. MBMS Registration Response

15. Provision of MBMS UE

Context to RAN
16. Invoke Trace
17. Activate MBMS Context Accept
 Synchronize MBMS context

1 1 0 0 0 1 1 1 0 0
Mbms status bitmap Mbms status bitmap

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 active
context 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
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

SGSN

• Different QOS 3G 2G
• IP multicast address
•TMGI

Separate MBMS Bearer Services for 2G and 3G for the same MBMS User Service
Typically with different QoS.
For this purpose two IP multicast addresses and the associated two
TMGIs should be allocated for the same MBMS user service
 MT PDP Context De-activation

MBMS context

MBMS context

General PDP Context

Existing PDP context deactivation procedure is used for deleting the MBMS contexts
In both MS and Network side
UE RAN SGSN GGSN BM-SC

1. IGMP Leave
2. Leave Indication

3. UE Removal Request
4. MBMS UE Context Deactivation Request
4. MBMS UE Context Deactivation Response
5. Deactivate MBMS Context Request

6. Deactivate MBMS Context Response

7. MBMS UE De-Linking Request

7. MBMS UE De-Linking Response

GGSN
8. RAN Resource Release

9. Delete MBMS Context Request

10. Deactivation Indication

10. Deactivation Confirmation

11. MBMS Deregistration Request

11. MBMS Deregistration Response

12. Delete MBMS Context Response
13. Deregistration Request

13. Deregistration Response

 Temporary Mobile Group Identity

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

 OPEN ISSUES

• 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
The Opportunity