Section: 6.1.3.8.4 Abnormal cases
Content: The following abnormal cases can be identified: a) Expiry of timers in the mobile station: On the first expiry of the timer T3380, the MS shall resend the ACTIVATE MBMS CONTEXT REQUEST and shall reset and restart timer T3380. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3380, the MS shall release all resources possibly allocated for this invocation and shall abort the procedure; no automatic MBMS context activation re-attempt shall be performed. b) Expiry of timers on the network side: On the first expiry of the timer T3385, the network shall resend the message REQUEST MBMS CONTEXT ACTIVATION and shall reset and restart timer T3385. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3385, the network shall release possibly allocated resources for this activation and shall abort the procedure. c) MBMS context activation request for an already activated MBMS context (on the mobile station side): If the MS receives a REQUEST MBMS CONTEXT ACTIVATION message with the same combination of APN and IP multicast address (i.e. PDP type and PDP address) as an already activated MBMS context, the MS shall deactivate the existing MBMS context locally without notification to the network and proceed with the requested MBMS context activation. d) MBMS context activation request for an already activated MBMS context (on the network side): If the network receives an ACTIVATE MBMS CONTEXT REQUEST message with the same combination of APN and IP multicast address (i.e. PDP type and PDP address) as an already activated MBMS context, the network shall deactivate the existing MBMS context locally without notification to the MS and proceed with the requested MBMS context activation. Figure 6.10/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MBMS context activation procedure