8.40 MBMS Registration

25.4133GPPRelease 17TSUTRAN Iu interface Radio Access Network Application Part (RANAP) signalling

8.40.1 General

The purpose of the MBMS Registration procedure is to request the CN (PS domain) to register or de-register the RNC for a certain Multicast Service.

The procedure uses connectionless signalling, unless the procedure is used to request CN to de-register the RNC for a Multicast Service which has an existing Iu signalling connection towards the RNC i.e. during a MBMS Session. In this last case, the procedure uses connection oriented signalling.

8.40.2 Successful Operation

Figure 52: MBMS Registration procedure. Successful operation.

The RNC initiates the procedure by sending a MBMS REGISTRATION REQUEST message.

The MBMS REGISTRATION REQUEST message shall contain the following IEs:

– MBMS Registration Request type;

– TMGI;

– The associated IP Multicast Address and the APN corresponding to the MBMS Bearer Service identified by the TMGI, only in the case the MBMS Registration Request type IE is set to "register";

– Global RNC-ID, if connectionless signalling.

If the CN node is capable of processing the request, the RNC shall be informed by the MBMS REGISTRATION RESPONSE message.

In case of connectionless signalling the MBMS REGISTRATION RESPONSE message shall contain the same TMGI as received in the MBMS REGISTRATION REQUEST message.

If the RNC has not sent the MBMS REGISTRATION REQUEST message with the MBMS Registration Request Type IE set to "register", to the default CN node, the MBMS REGISTRATION RESPONSE message shall also include the Global CN-ID IE.

Upon reception of the MBMS REGISTRATION RESPONSE message as a response to a connectionless MBMS REGISTRATION REQUEST message with the MBMS Registration Request Type IE set to "deregister", the RNC shall remove all associated MBMS resources and context(s) corresponding to the MBMS Bearer Service identified by the TMGI included in the MBMS REGISTRATION REQUEST message.

Upon reception of the MBMS REGISTRATION RESPONSE message as a response to a connection oriented MBMS REGISTRATION REQUEST message with the MBMS Registration Request Type IE set to "deregister", the RNC shall release the MBMS Iu signalling connection and the RAB, if any, identified by the TMGI included in the MBMS REGISTRATION REQUEST message.

Transmission and reception of a MBMS REGISTRATION RESPONSE message terminate the procedure in the CN and in the UTRAN respectively.

8.40.3 Unsuccessful Operation

Figure 53: MBMS Registration procedure. Unsuccessful operation.

If the CN node is not capable of correctly processing the request, the RNC shall be informed by the MBMS REGISTRATION FAILURE message.

In case of connectionless signalling, the MBMS REGISTRATION FAILURE message shall contain the same TMGI as received in the MBMS REGISTRATION REQUEST message.

The MBMS REGISTRATION FAILURE message shall inform the RNC about the reason for unsuccessful operation thank to appropriate cause value e.g. "TMGI Unknown", "IP Multicast Address And APN Not Valid", "MBMS De-Registration Rejected Due To Implicit Registration", "MBMS – Request Superseded", "MBMS De-Registration During Session Not Allowed".

In case of connectionless signalling, if the RNC has not sent the MBMS REGISTRATION REQUEST message with the MBMS Registration Request Type IE set to "register", to the default CN node, the MBMS REGISTRATION FAILURE message shall also include the Global CN-ID IE.

Transmission and reception of a MBMS REGISTRATION FAILURE message terminate the procedure in the CN and in the UTRAN respectively.

8.40.4 Abnormal Conditions

Not applicable.