Section: 6.1.3.8.2 Unsuccessful MBMS context activation requested by the MS 6.1.3.8.2.1 General
Content: Upon receipt of an ACTIVATE MBMS CONTEXT REQUEST message the network may reject the MS initiated MBMS context activation by sending an ACTIVATE MBMS CONTEXT REJECT message to the MS. The sender of the message shall include the same TI as included in the ACTIVATE MBMS CONTEX REQUEST and an additional cause code that typically indicates one of the following causes: # 8: Operator Determined Barring; # 24: MBMS bearer capabilities insufficient for the service; # 26: insufficient resources; # 27: missing or unknown APN; # 29: user authentication failed; # 30: activation rejected by GGSN, Serving GW or PDN GW; # 31: activation rejected, unspecified; # 32: service option not supported; # 33: requested service option not subscribed; # 34: service option temporarily out of order; or # 95 - # 111: protocol errors. The network may include a Back-off timer value IE in the ACTIVATE MBMS CONTEXT REJECT message. If the Back-off timer value IE is included and the SM cause value is different from #26 "insufficient resources", the network may include the Re-attempt indicator IE to indicate whether the MS is allowed to attempt an MBMS context activation procedure in an equivalent PLMN. Upon receipt of an ACTIVATE MBMS CONTEXT REJECT message, the MS shall stop timer T3380 and enter/remain in state PDP-INACTIVE.