Cause value = 81 Invalid transaction identifier value.

See annex H, subclause H.5.1.

Cause value = 95 Semantically incorrect message.

See annex H, subclause H.5.5.

Cause value = 96 Invalid mandatory information.

See annex H, subclause H.6.1.

Cause value = 97 Message type non-existent or not implemented.

See annex H, subclause H.6.2.

Cause value = 98 Message not compatible with protocol state.

See annex H, subclause H.6.3.

Cause value = 99 Information element non-existent or not implemented.

See annex H, subclause H.6.4.

Cause value = 100 Conditional IE error.

See annex H, subclause H.6.5.

Cause value = 101 Message not compatible with protocol state.

See annex H, subclause H.6.6.

Cause value = 111 Protocol error, unspecified.

See annex H, subclause H.6.8.

I.3   Void

Causes related to nature of request

Cause value = 8 Operator Determined Barring

This cause code is used by the network to indicate that the requested service was rejected by the SGSN due to Operator Determined Barring.

Cause value = 24 MBMS bearer capabilities insufficient for the service

This cause code is used by the network to indicate that an MBMS context activation request was rejected by the network, because the MBMS bearer capabilities are insufficient for the MBMS service.

Cause value = 25 LLC or SNDCP failure (A/Gb mode only)

This cause code is used by the MS indicate that a PDP context is deactivated because of a LLC or SNDCP failure (e.g. if the SM receives a SNSM-STATUS.request message with cause “DM received ” or “ invalid XID response “, see 3GPP TS 44.065 [78])

Cause value = 26 Insufficient resources

This cause code is used by the MS or by the network to indicate that a PDP context activation request, secondary PDP context activation request, PDP context modification request, or MBMS context activation request cannot be accepted due to insufficient resources.

Cause value = 27 Unknown or missing access point name

This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the access point name was not included although required or if the access point name could not be resolved.

Cause value = 28 Unknown PDP address or PDP type

This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the PDP address or type could not be recognised.

Cause value = 29 User authentication failed

This cause code is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication.

Cause value = 30 Activation rejected by GGSN, Serving GW or PDN GW

This cause code is used by the network to indicate that the requested service was rejected by the GGSN, Serving GW or PDN GW.

Cause value = 31 Activation rejected, unspecified

This cause code is used by the network to indicate that the requested service was rejected due to unspecified reasons.

Cause value = 32 Service option not supported

This cause code is used by the network when the MS requests a service which is not supported by the PLMN.

Cause value = 33 Requested service option not subscribed

See Annex G, clause 4.

Cause value = 34 Service option temporarily out of order

See Annex G, clause 4.

Cause value = 35 NSAPI already used

This cause code may be used by a network to indicate that the NSAPI requested by the MS in the PDP context activation request is already used by another active PDP context of this MS.

Never to be sent, but can be received from a R97/R98 network at PDP context activation

Cause value = 36 Regular deactivation

This cause code is used to indicate a regular MS or network initiated PDP context deactivation or a regular network initiated MBMS context deactivation.

Cause value = 37 QoS not accepted

This cause code is used by the MS if the new QoS cannot be accepted that were indicated by the network in the PDP Context Modification procedure.

Cause value = 38 Network failure

This cause code is used by the network to indicate that the PDP context deactivation or the MBMS context deactivation is caused by an error situation in the network.

Cause value = 39 Reactivation requested

This cause code is used by the network to request a PDP context reactivation after a GGSN restart.

Cause value = 40 Feature not supported

This cause code is used by the MS to indicate that the PDP context activation or the MBMS context activation initiated by the network is not supported by the MS.

Cause value = 41 semantic error in the TFT operation.

This cause code is used by the network or the MS to indicate that there is a semantic error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation.

Cause value = 42 syntactical error in the TFT operation.

This cause code is used by the network or the MS to indicate that there is a syntactical error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation.

Cause value = 43 unknown PDP context

This cause code is used by the network or the MS to indicate that the PDP context identified by the Linked TI IE in the secondary PDP context activation request or a network requested secondary PDP context activation is not active.

Cause value = 44 semantic errors in packet filter(s)

This cause code is used by the network or the MS to indicate that there is one or more semantic errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation.

Cause value = 45 syntactical error in packet filter(s)

This cause code is used by the network or the MS to indicate that there is one or more syntactical errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation.

Cause value = 46 PDP context without TFT already activated

This cause code is used by the network or the MS to indicate that it has already activated a PDP context without TFT.

Cause value = 47 Multicast group membership time-out

This cause code is used by the network to indicate that the MBMS context is deactivated because the timer supervising the IGMP group membership interval (see RFC 3376 [107], subclause 8.4) or the MLD multicast listener interval (see RFC 2710 [108], subclause 7.4) expired.

Cause value = 48 Activation rejected, B earerC ontrolMode violation

This cause code is used by the network or the MS to indicate that the requested service was rejected because of Bearer Control Mode violation.

Cause value = 50 PDP type IPv4 only allowed

This cause is used by the network to indicate that the requested PDN connectivity is accepted with the restriction that only PDP type IPv4 is allowed.

Cause value = 51 PDP type IPv6 only allowed

This cause is used by the network to indicate that the requested PDN connectivity is accepted with the restriction that only PDP type IPv6 is allowed.

Cause value = 52 single address bearers only allowed

This cause is used by the network to indicate that the requested PDN connectivity is accepted with the restriction that only single IP version bearers are allowed.

Cause value = 56 Collision with network initiated request.

This cause code is used by the network to indicate that the MS-initiated request was rejected since the network has requested a secondary PDP context activation for the same service using a network-initiated procedure.

Cause value = 112 APN restriction value incompatible with active PDP context.

This cause code is used by the network to indicate that the PDP context(s) or MBMS context(s) have an APN restriction value that is not allowed in combination with a currently active PDP context. Restriction values are defined in 3GPP TS 23.060 [74], subclause 15.4.

H.1   Normal class

H.1.1    Cause No. 1 “unassigned (unallocated) number”

This cause indicates that the destination requested by the mobile station cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated).

H.1.2    Cause No. 3 “no route to destination”

This cause indicates that the called user cannot be reached because the network through which the call has been routed does not serve the destination desired.

H.1.3    Cause No. 6 “channel unacceptable”

This cause indicates the channel most recently identified is not acceptable to the sending entity for use in this call.

H.1.4    Cause No. 8 “operator determined barring”

This cause indicates that the MS has tried to access a service that the MS’s network operator or service provider is not prepared to allow.

H.1.5    Cause No.16 “normal call clearing”

This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared.

Under normal situations, the source of this cause is not the network.

H.1.6    Cause No.17 “user busy”

This cause is used when the called user has indicated the inability to accept another call.

It is noted that the user equipment is compatible with the call.

H.1.7    Cause No. 18 “no user responding”

This cause is used when a user does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated (defined by the expiry of either timer T303 or T310).

H.1.8    Cause No. 19 “user alerting, no answer”

This cause is used when a user has provided an alerting indication but has not provided a connect indication within a prescribed period of time.

H.1.9    Cause No. 21 “call rejected”

This cause indicates that the equipment sending this cause does not wish to accept this call, although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible.

H.1.10    Cause No. 22 “number changed”

This cause is returned to a calling mobile station when the called party number indicated by the calling mobile station is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this capability, cause No. 1 “unassigned (unallocated) number” shall be used.

H.1.11    Cause No. 25 “pre-emption”

This cause is returned to the network when a mobile station clears an active call which is being pre-empted by another call with higher precedence.

H.1.12    Cause No. 26 “non-selected user clearing”

Not supported. Treated as cause no. 31.

H.1.13    Cause No. 27 “destination out of order”

This cause indicates that the destination indicated by the mobile station cannot be reached because the interface to the destination is not functioning correctly. The term “not functioning correctly” indicates that a signalling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc.

H.1.14    Cause No. 28 “invalid number format (incomplete number)”

This cause indicates that the called user cannot be reached because the called party number is not a valid format or is not complete.

H.1.15    Cause No. 29 “facility rejected”

This cause is returned when a facility requested by user can not be provided by the network.

H.1.16    Cause No. 30 “response to STATUS ENQUIRY”

This cause is included in STATUS messages if the message is sent in response to a STATUS ENQUIRY message. See also subclause 5.5.3.

H.1.17    Cause No. 31 “normal, unspecified”

This cause is used to report a normal event only when no other cause in the normal class applies.

H.2   Resource unavailable class

H.2.1    Cause No. 34 “no circuit/channel available”

This cause indicates that there is no appropriate circuit/channel presently available to handle the call.

H.2.2    Cause No. 38 “network out of order”

This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time; e.g., immediately re-attempting the call is not likely to be successful.

H.2.3    Cause No. 41 “temporary failure”

This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time; e.g., the mobile station may wish to try another call attempt almost immediately.

H.2.4    Cause No. 42 “switching equipment congestion”

This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.

H.2.5    Cause No. 43 “access information discarded”

This cause indicates that the network could not deliver access information to the remote user as requested; i.e., a user-to-user information, low layer compatibility, high layer compatibility, or sub-address as indicated in the diagnostic.

It is noted that the particular type of access information discarded is optionally included in the diagnostic.

H.2.6    Cause No. 44 “requested circuit/channel not available”

This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side of the interface.

H.2.7    Cause No. 47 “resource unavailable, unspecified”

This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.

H.3   Service or option not available class

H.3.1    Cause No. 49 “quality of service unavailable”

This cause indicates to the mobile station that the requested quality of service, as defined in ITU-T Recommendation X.213, cannot be provided.

H.3.2    Cause No. 50 “Requested facility not subscribed”

This cause indicates that the requested supplementary service could not be provided by the network because the user has no completed the necessary administrative arrangements with its supporting networks.

H.3.3    Cause No. 55 “Incoming calls barred within the CUG”

This cause indicates that although the called party is a member of the CUG for the incoming CUG call, incoming calls are not allowed within this CUG.

H.3.4    Cause No. 57 “bearer capability not authorized”

This cause indicates that the mobile station has requested a bearer capability which is implemented by the equipment which generated this cause but the mobile station is not authorized to use.

H.3.5    Cause No. 58 “bearer capability not presently available”

This cause indicates that the mobile station has requested a bearer capability which is implemented by the equipment which generated this cause but which is not available at this time.

H.3.6    Cause No. 63 “service or option not available, unspecified”

This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies.

H.3.7    Cause No. 68 “ACM equal to or greater than ACMmax”

This cause is used by the mobile to indicate that call clearing is due to ACM being greater than or equal to ACMmax.

H.4   Service or option not implemented class

H.4.1    Cause No. 65 “bearer service not implemented”

This cause indicates that the equipment sending this cause does not support the bearer capability requested.

H.4.2    Cause No. 69 “Requested facility not implemented”

This cause indicates that the equipment sending this cause does not support the requested supplementary service.

H.4.3    Cause No. 70 “only restricted digital information bearer capability is available”

This cause indicates that one equipment has requested an unrestricted bearer service, but that the equipment sending this cause only supports the restricted version of the requested bearer capability.

H.4.4    Cause No. 79 “service or option not implemented, unspecified”

This cause is used to report a service or option not implemented event only when no other cause in the service or option not implemented class applies.

H.5   Invalid message (e.g., parameter out of range) class

H.5.1    Cause No. 81 “invalid transaction identifier value”

This cause indicates that the equipment sending this cause has received a message with a transaction identifier which is not currently in use on the MS-network interface.

H.5.2    Cause No. 87 “user not member of CUG”

This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG.

H.5.3    Cause No. 88 “incompatible destination”

This cause indicates that the equipment sending this cause has received a request to establish a call which has low layer compatibility, high layer compatibility, or other compatibility attributes (e.g., data rate) which cannot be accommodated.

H.5.4    Cause No. 91 “invalid transit network selection”

For further study. Treated as cause no. 95.

H.5.5    Cause No. 95 “semantically incorrect message”

This cause is used to report receipt of a message with semantically incorrect contents (see subclause 8.8).

H.6   Protocol error (e.g., unknown message) class

H.6.1    Cause No. 96 “invalid mandatory information”

This cause indicates that the equipment sending this cause has received a message with a non-semantical mandatory IE error (see subclause 8.5).

H.6.2    Cause No. 97 “message type non-existent or not implemented”

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this cause.

H.6.3    Cause No. 98 “message type not compatible with protocol state”

This cause indicates that the equipment sending this cause has received a message not compatible with the protocol state (subclause 8.4).

H.6.4    Cause No. 99 “information element non-existent or not implemented”

This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

H.6.5    Cause No. 100 “conditional IE error”

This cause indicates that the equipment sending this cause has received a message with conditional IE errors (see subclause 8.7.2).

H.6.6    Cause No. 101 “message not compatible with protocol state”

This cause indicates that a message has been received which is incompatible with the protocol state or that a STATUS message has been received indicating an incompatible call state.

H.6.7    Cause No. 102 “recovery on timer expiry”

This cause indicates that a procedure has been initiated by the expiry of a timer in association with 3GPP TS 24.008 error handling procedures.

H.6.8    Cause No. 111 “protocol error, unspecified”

This cause is used to report a protocol error event only when no other cause in the protocol error class applies.

H.7   Interworking class

H.7.1    Cause No. 127 “interworking, unspecified”

This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being sent cannot be ascertained.

Causes related to MS identification

Cause value = 2 IMSI unknown in HLR

This cause is sent to the MS if the MS is not known (registered) in the HLR. This cause code does not affect operation of the GPRS service, although is may be used by a GMM procedure.

Cause value = 3 Illegal MS

This cause is sent to the MS when the network refuses service to the MS either because an identity of the MS is not acceptable to the network or because the MS does not pass the authentication check, i.e. the SRES received from the MS is different from that generated by the network. When used by an MM procedure, except the authentication procedure, this cause does not affect operation of the GPRS service.

Cause value = 4 IMSI unknown in VLR

This cause is sent to the MS when the given IMSI is not known at the VLR.

Cause value = 5 IMEI not accepted

This cause is sent to the MS if the network does not accept emergency call establishment using an IMEI or not accept attach procedure for emergency services using an IMEI.

Cause value = 6 Illegal ME

This cause is sent to the MS if the ME used is not acceptable to the network, e.g. blacklisted. When used by an MM procedure, this cause does not affect operation of the GPRS service.

Cause related to subscription options

Cause value = 11 PLMN not allowed

This cause is sent to the MS if it requests location updating in a PLMN where the MS, by subscription or due to operator determined barring is not allowed to operate.

Cause value = 12 Location Area not allowed

This cause is sent to the MS if it requests location updating in a location area where the HPLMN determines that the MS, by subscription, is not allowed to operate.

NOTE:   If cause #12 is sent to a roaming subscriber the subscriber is denied service even if other PLMNs are available on which registration was possible.

Cause value = 13 Roaming not allowed in this location area

This cause is sent to an MS which requests location updating in a location area of a PLMN which by subscription offers roaming to that MS but not  in that Location Area.

Cause value = 15 No Suitable Cells In Location Area

This cause is sent to the MS if it requests location updating in a location area where the MS, by subscription, is not allowed to operate, but when it should find another allowed location area in the same PLMN.

NOTE:     Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the MS to search for another allowed location area on the same PLMN.

Cause value = 25 Not authorized for this CSG

This cause is sent to the MS if it requests access in a CSG cell where the MS either has no subscription to operate or the MS’s subscription has expired and it should find another cell in the same PLMN.

NOTE:     The MS not supporting CSG will not receive cause# 25, as such a MS is not supposed to try to access a CSG cell.

Causes related to PLMN specific network failures and congestion/Authentication Failures

Cause value = 20 MAC failure

This cause is sent to the network if the USIM detects that the MAC in the AUTHENTICATION REQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message is not fresh (see 3GPP TS 33.102 [5a]).

Cause value = 21 Synch failure

This cause is sent to the network if the USIM detects that the SQN in the AUTHENTICATION REQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message is out of range (see 3GPP TS 33.102 [5a]).

Cause value = 17 Network failure

This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, e.g. problems in MAP.

Cause value = 22 Congestion

This cause is sent if the service request cannot be actioned because of congestion (e.g. no channel, facility busy/congested etc.).

Cause value = 23 GSM authentication unacceptable

This cause is sent to the network in Iu mode if a USIM is inserted in the MS and there is no Authentication Parameter AUTN IE present in the AUTHENTICATION REQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message.

Causes related to nature of request

Cause value = 32 Service option not supported

This cause is sent when the MS requests a service/facility in the CM SERVICE REQUEST message which is not supported by the PLMN.

Cause value = 33 Requested service option not subscribed

This cause is sent when the MS requests a service option for which it has no subscription.

Cause value = 34 Service option temporarily out of order

This cause is sent when the MSC cannot service the request because of temporary outage of one or more functions required for supporting the service.

Cause value = 38 Call cannot be identified

This cause is sent when the network cannot identify the call associated with a call re-establishment request.

Causes related to invalid messages

Cause value = 95 Semantically incorrect message.

See annex H, subclause H.5.10.

Cause value = 96 Invalid mandatory information.

See annex H, subclause H.6.1.

Cause value = 97 Message type non-existent or not implemented.

See annex H, subclause H.6.2.

Cause value = 98 Message not compatible with protocol state.

See annex H, subclause H.6.3.

Cause value = 99 Information element non-existent or not implemented.

See annex H, subclause H.6.4.

Cause value = 100 Conditional IE error.

See annex H, subclause H.6.5.

Cause value = 101 Message not compatible with protocol state.

See annex H, subclause H.6.6.

Cause value = 111 Protocol error, unspecified.

See annex H, subclause H.6.8.

Additional cause codes for GMM

Cause value = 7 GPRS services not allowed

This cause is sent to the MS when it is not allowed to operate GPRS services.

Cause value = 8 GPRS services and non-GPRS services not allowed

This cause is sent to the MS when it is not allowed to operate either GPRS or non-GPRS services.

Cause value = 9 MS identity cannot be derived by the network

This cause is sent to the MS when the network cannot derive the MS’s identity from the P-TMSI in case of inter-SGSN routing area update.

Cause value = 10 Implicitly detached

This cause is sent to the MS either if the network has implicitly detached the MS, e.g. some while after the Mobile reachable timer has expired, or if the GMM context data related to the subscription dose not exist in the SGSN e.g. because of a SGSN restart.

Cause value = 14 GPRS services not allowed in this PLMN

This cause is sent to the MS which requests GPRS service in a PLMN which does not offer roaming for GPRS services to that MS.

Cause value = 16 MSC temporarily not reachable

This cause is sent to the MS if it requests a combined GPRS attach or routing are updating in a PLMN where the MSC is temporarily not reachable via the GPRS part of the network.

Cause value = 40 No PDP context activated

This cause is sent to the MS if the MS requests an establishment of the radio access bearers for all active PDP contexts by sending a SERVICE REQUEST message indicating “data” to the network, but the SGSN does not have any active PDP context(s).

Timers of mobility management

3GPP TS 24.008: Mobility management timers – MS-side

TIMER NUM.	MM STATE	TIME OUT VAL.	CAUSE FOR START	NORMAL STOP	AT THE EXPIRY
T3210	LOCATION UPDATING INITIATED	20s	– LOC_UPD_REQ sent	– LOC_UPD_ACC – LOC_UPD_REJ – AUTH_REJ – Lower layer failure	Start T3211
T3211	MM IDLE,	15s	– LOC_UPD_REJ with cause#17 netw. failure – lower layer failure or RR conn. released after RR conn. abort during loc. updating	– Time out – cell change – request for MM connection establishment – change of LA	Restart the Location update proc.
T3212	MM IDLE	Note 1	– termination of MM service or MM signalling	– initiation of MM service or MM signalling	initiate periodic updating
T3213	LOCATION UPDATING INITIATED	4s	– location updating failure	– expiry – change of BCCH parameter	new random attempt
T3214	LOCATION UPDATING INITIATED WAIT FOR OUTGOING MM CONNECTION IMSI DETACH INITIATED	20s	AUTHENT FAILURE Cause = ‘MAC failure’ or ‘GSM authentication unacceptable’ sent	AUTHENT REQ received	Consider the network as ’false’ (see 4.3.2.6.1)
T3216	LOCATION UPDATING INITIATED WAIT FOR OUTGOING MM CONNECTION IMSI DETACH INITIATED	15s	AUTHENT FAILURE Cause = Synch failure sent	AUTHENT REQ received	Consider the network as ’false’ (see 4.3.2.6.1)
T3218	LOCATION UPDATING INITIATED WAIT FOR OUTGOING MM CONNECTION IMSI DETACH INITIATED	20s	RAND and RES stored as a result of of a UMTS authentication challenge	– Cipher mode setting (A/Gb mode only) –  Security mode setting (Iu mode only) –  CM_SERV_ACCEPT received –  CM SERVICE REJECT received – LOCATION UPDATING ACCEPT received – AUTHENT REJ received – AUTHENT FAIL sent – enter MM IDLE or NULL	Delete the stored RAND and RES
T3220	IMSI DETACH INITIATED	5s	– IMSI DETACH	– release from RM-sublayer	enter Null or Idle, ATTEMPTING TO UPDATE
T3230	WAIT FOR OUTGOING MM CONNECTION WAIT FOR ADDITIONAL OUTGOING MM CONNECTION WAIT FOR REESTABLISH	15s	– CM SERV REQ CM RE-EST REQ	– Cipher mode setting – CM SERV REJ – CM SERV ACC	provide release ind.
T3240	WAIT FOR NETWORK COMMAND LOCATION UPDATE REJECTED	10s	see timer description T3240 below	see timer description T3240 below	abort the RR connection
T3241	RR CONNECTION RELEASE NOT ALLOWED	300s	*Refer timer description T3241 below	*Refer timer description T3241 below	abort the RR connection
T3242	All except NULL	3600s	eCall only MS enters MM IDLE state after an emergency call	– Time Out – Power Off – Removal of eCall only restriction	Perform eCall Inactivity procedure in subclause 4.4.7
T3243	All except NULL	900s	eCall only MS enters MM IDLE state after a test/reconfiguration call	– Time Out – Power Off – Removal of eCall only restriction	Perform eCall Inactivity procedure in subclause 4.4.7

NOTE 1:     The timeout value is broadcasted in a SYSTEM INFORMATION message.

3GPP TS 24.008: Mobility management timers – network-side

TIMER NUM.	MM STATE	TIME OUT VAL.	CAUSE FOR START	NORMAL STOP	AT THE EXPIRY	AT THE SECOND EXPIRY
T3250	TMSI REALLOCATION INITIATED	12s	TMSI-REAL-CMD or LOC UPD ACC with new TMSI sent	TMSI-REALL-COM received	Optionally Release RR connection
T3255		Note	LOC UPD ACC sent with”Follow on Proceed”	CM SERVICE REQUEST	Release RR Connection or use for mobile station terminating call
T3260	AUTHENTICATION INITIATED	12s	AUTHENT-REQUEST sent	AUTHENT-RESPONSE received AUTHENT-FAILURE received	Optionally Release RR connection
T3270	IDENTIFICATION INITIATED	12s	IDENTITY REQUEST sent	IDENTITY RESPONSE received	Optionally Release RR connection

NOTE 2:     The value of this timer is not specified by this recommendation.

Timer T3240 and Timer T3241

Timer T3240 is started in the mobile station when:

–   the mobile station receives a LOCATION UPDATING ACCEPT message completing a location updating procedure in the cases specified in subclauses 4.4.4.6 and 4.4.4.8;

–   the mobile station receives a LOCATION UPDATING REJECT message in the cases specified in subclause 4.4.4.7;

–   the mobile station has sent a CM SERVICE ABORT message as specified in subclause 4.5.1.7;

–   the mobile station has released or aborted all MM connections in the cases specified in 4.3.2.5, 4.3.5.2, 4.5.1.1, and 4.5.3.1.

Timer T3240 is stopped, reset, and started again at receipt of an MM message.

Timer T3240 is stopped and reset (but not started) at receipt of a CM message that initiates establishment of an CM connection (an appropriate SETUP, REGISTER, or CP-DATA message as defined in 3GPP TS 24.008, 3GPP TS 24.010 [21] or 3GPP TS 24.011 [22]).

Timer T3241 is started in the mobile station when entering MM state RR CONNECTION RELEASE NOT ALLOWED.

Timer T3241 is stopped and reset (but not started) when the MM state RR CONNECTION RELEASE NOT ALLOWED is left.

If timer T3241 expires, the MS shall abort the RR connection and enter the MM state MM IDLE.

Timers of GPRS mobility management

3GPP TS 24.008: GPRS Mobility management timers – MS side

TIMER NUM.	TIMER VALUE	STATE	CAUSE OF START	NORMAL STOP	ON THE 1st, 2nd, 3rd, 4th EXPIRY Note 3
T3310	15s	GMM- REG-INIT	ATTACH REQ sent	ATTACH ACCEPT received ATTACH REJECT received	Retransmission of ATTACH REQ
T3311	15s	GMM-DEREG ATTEMPTING TO ATTACH or GMM-REG ATTEMPTING TO UPDATE	ATTACH REJ with other cause values as described in chapter ‘GPRS Attach’ ROUTING AREA UPDATE REJ with other cause values as described in chapter ‘Routing Area Update’ Low layer failure	Change of the routing area	Restart of the Attach or the RAU procedure with updating of the relevant attempt counter
T3316	30s	GMM- REG-INIT GMM-REG GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT (Iu mode only)	RAND and RES stored as a result of a UMTS authentication challenge	Security mode setting (Iu mode only) SERVICE ACCEPT received. (Iu mode only) SERVICE REJECT received (Iu mode only) ROUTING AREA UPDATE ACCEPT received AUTHENTICATION AND CIPHERING REJECT received AUTHENTICATION_AND_CIPHERING FAILURE sent Enter GMM-DEREG or GMM-NULL	Delete the stored RAND and RES
T3318	20s	GMM- REG-INIT GMM-REG GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT (Iu mode only)	AUTHENTICATION & CIPHERING FAILURE (cause=’MAC failure’ or ‘GSM authentication unacceptable’) sent	AUTHENTICATION & CIPHERING REQUEST received	On first expiry, the MS should consider the network as false (see 4.7.7.6.1)
T3320	15s	GMM- REG-INIT GMM-REG GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT (Iu mode only)	AUTHENTICATION & CIPHERING FAILURE (cause=synch failure) sent	AUTHENTICATION & CIPHERING REQUEST received	On first expiry, the MS should consider the network as false (see 4.7.7.6.1)
T3321	15s	GMM- DEREG-INIT	DETACH REQ sent	DETACH ACCEPT received	Retransmission of the DETACH REQ
T3330	15s	GMM-ROUTING-UPDATING-INITIATED	ROUTING AREA UPDATE REQUEST sent	ROUTING AREA UPDATE ACC received ROUTING AREA UPDATE REJ received	Retransmission of the ROUTING AREA UPDATE REQUEST message
T3340 (Iu mode only)	10s	GMM- REG-INIT GMM-DEREG-INIT GMM-RA-UPDATING-INT GMM-SERV-REQ-INIT (Iu mode only) GMM-ATTEMPTING-TO-UPDATE-MM GMM-REG-NORMAL-SERVICE	ATTACH REJ, DETACH REQ, ROUTING AREA UPDATE REJ or SERVICE REJ with any of the causes #11, #12, #13, #15, or #25. ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT is received with “no follow-on proceed“ indication.	PS signalling connection released	Release the PS signalling connection and proceed as described in subclause 4.7.1.9

3GPP TS 24.008: GPRS Mobility management timers – MS side

TIMER NUM.		TIMER VALUE		STATE		CAUSE OF START		NORMAL STOP		ON EXPIRY
T3302		Default 12 min Note 1 Note 5		GMM-DEREG or GMM-REG		At attach failure and the attempt counter is greater than or equal to 5. At routing area updating failure and the attempt counter is greater than or equal to 5.		At successful attach At successful routing area updating		On every expiry, initiation of the GPRS attach procedure or RAU procedure
T3312		Default 54 min Note1		GMM-REG		In A/Gb mode, when READY state is left. In Iu mode, when PMM-CONNECTED mode is left.		When entering state GMM-DEREG		Initiation of the Periodic RAU procedure
T3314 READY (A/Gb mode only)		Default 44 sec Note 2		All except GMM-DEREG		Transmission of a PTP PDU		Forced to Standby		No cell-updates are performed
T3317 (Iu mode only)	15s		GMM-SERVICE-REQUEST-INITIATED		SERVICE REQ sent		Security mode control procedure is completed, SERVICE ACCEPT received, or SERVICE REJECT received		Abort the procedure
T3319 (Iu mode only)	Default 30s Note 1 Note 4		GMM-REG		Completion of the Security Mode Control procedure after sending a SERVICE REQUEST with service type “data”. Reception of a SERVICE ACCEPT message.		When entering PMM-IDLE mode. When the radio access bearer is released for any active PDP context. When entering state GMM-DEREG		SERVICE REQ with service type “data” may be invoked again, if required.
T3323	NOTE 6		GMM-REGISTERED		T3312 expires while the MS is in GMM-REGISTERED.NO-CELL-AVAILABLE and ISR is activated.		When entering state GMM-DEREGISTERED or when entering GMM-CONNECTED mode.		Deactivation of ISR by setting TIN to “GUTI”

NOTE 1:     The value of this timer is used if the network does not indicate another value in a GMM signalling procedure.

NOTE 2:     The default value of this timer is used if neither the MS nor the Network send another value, or if the Network sends this value, in a signalling procedure.

NOTE 3:     Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

NOTE 4:      The purpose of this timer is to prevent the MS from repeating the SERVICE REQUEST message with service type “data” too early in case the request to setup the radio access bearer is queued by the radio access network.

NOTE 5:     In Iu mode, the default value of this timer is used if the network provides a value for this timer in a non-integrity protected Iu mode GMM message.

NOTE 6:     The value of this timer may be provided by the network to the MS in the ATTACH ACCEPT message and ROUTING AREA UPDATE ACCEPT message. The default value of this timer is identical to the value of timer T3312.

3GPP TS 24.008: GPRS Mobility management timers – network side

TIMER NUM.	TIMER VALUE	STATE	CAUSE OF START	NORMAL STOP	ON THE 1st, 2nd, 3rd, 4th EXPIRY Note 3
T3322	6s	GMM- DEREG-INIT	DETACH REQ sent	DETACH ACCEPT received	Retransmission of DETACH REQUEST
T3350	6s	GMM-COMMON-PROC-INIT	ATTACH ACCEPT sent with P-TMSI and/or TMSI RAU ACCEPT sent with P-TMSI and/or TMSI P-TMSI REALLOC COMMAND sent	ATTACH COMPLETE received RAU COMPLETE received P-TMSI REALLOC COMPLETE received	Retransmission of the same message type, i.e. ATTACH ACCEPT, RAU ACCEPT or REALLOC COMMAND
T3360	6s	GMM- COMMON-PROC-INIT	AUTH AND CIPH REQUEST sent	AUTH AND CIPH RESPONSE received AUTHENT-AND CIPHER-FAILURE received	Retransmission of AUTH AND CIPH REQUEST
T3370	6s	GMM-COMMON-PROC-INIT	IDENTITY REQUEST sent	IDENTITY RESPONSE received	Retransmission of IDENTITY REQUEST

3GPP TS 24.008: GPRS Mobility management timers – network side

TIMER NUM.	TIMER VALUE	STATE	CAUSE OF START	NORMAL STOP	ON EXPIRY
T3313	Note 1	GMM_REG	Paging procedure initiated	Paging procedure completed	Network dependent
T3314 READY (A/Gb mode only)	Default 44 sec Note 2	All except GMM-DEREG	Receipt of a PTP PDU	Forced to Standby	The network shall page the MS if a PTP PDU has to be sent to the MS
Mobile Reachable	Default 4 min greater than T3312	All except GMM-DEREG	In A/Gb mode, change from READY to STANDBY state In Iu mode, change from PMM-CONNECTED mode to PMM-IDLE mode.	PTP PDU received	Network dependent but typically paging is halted on 1st expiry
Implicit Detach timer	Default 4 min greater than T3323	All except GMM-DEREG	The Mobile Reachable timer expires while the network is in PMM-IDLE mode or STANDBY state and ISR is activated.	PTP PDU received	Implicitly detach the MS on 1st expiry

NOTE 1:     The value of this timer is network dependent.

NOTE 2:     The default value of this timer is used if neither the MS nor the Network send another value, or if the Network sends this value, in a signalling procedure. The value of this timer should be slightly shorter in the network than in the MS, this is a network implementation issue.

NOTE 3:     Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

Timers of GPRS session management

3GPP TS 24.008: GPRS session management timers – MS side

TIMER NUM.	TIMER VALUE	STATE	CAUSE OF START	NORMAL STOP	ON THE 1st, 2nd, 3rd, 4th EXPIRY
T3380	30s	PDP- ACTIVE-PEND or MBMS ACTIVE-PENDING	ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST sent	ACTIVATE PDP CONTEXT ACCEPT, ACTIVATE SECONDARY PDP CONTEXT ACCEPT or ACTIVATE MBMS CONTEXT ACCEPT received ACTIVATE PDP CONTEXT REJECT, ACTIVATE SECONDARY PDP CONTEXT REJECT or ACTIVATE MBMS CONTEXT REJECT received	Retransmission of ACTIVATE PDP CONTEXT REQ, ACTIVATE SECONDARY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST
T3381	8s	PDP-MODIFY-PENDING	MODIFY PDP CONTEXT REQUEST sent	MODIFY PDP CONTEXT ACCEPT received	Retransmission of MODIFY PDP CONTEXT REQUEST
T3390	8s	PDP- INACT-PEND	DEACTIVATE PDP CONTEXT REQUEST sent	DEACTIVATE PDP CONTEXT ACC received	Retransmission of DEACTIVATE PDP CONTEXT REQUEST

NOTE:     Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

3GPP TS 24.008: GPRS session management timers – network side

TIMER NUM.	TIMER VALUE	STATE	CAUSE OF START	NORMAL STOP	ON THE 1st, 2nd, 3rd, 4th EXPIRY
T3385	8s	PDP- ACT-PEND or MBMS ACTIVE-PENDING	REQUEST PDP CONTEXT ACTIVATION or REQUEST SECONDARY PDP CONTEXT ACTIVATION or REQUEST MBMS CONTEXT ACTIVATION sent	ACTIVATE PDP CONTEXT REQUEST or ACTIVATE SECONDARY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST received	Retransmission of REQUEST PDP CONTEXT ACTIVATION or REQUEST SECONDARY PDP CONTEXT ACTIVATION or REQUEST MBMS CONTEXT ACTIVATION
T3386	8s	PDP- MOD-PEND	MODIFY PDP CONTEXT REQUEST sent	MODIFY PDP CONTEXT ACC received	Retransmission of MODIFY PDP CONTEXT REQ
T3395	8s	PDP- INACT-PEND or MBMS INACTIVE-PENDING	DEACTIVATE PDP CONTEXT REQUEST sent	DEACTIVATE PDP CONTEXT ACC received	Retransmission of DEACTIVATE PDP CONTEXT REQ

NOTE:     Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

Timers of circuit-switched call control

3GPP TS 24.008: Call control timers – MS side

TIM NUM.	TIM VAL	STATE OF CALL	CAUSE OF START	NORMAL STOP	AT FIRST EXPIRY	AT SECOND EXPIRY
T303	30s	Call initiated	CM SER RQ sent	CALL PROC, or REL COMP received	Clear the call	Timer is not restarted
T305	30s	Disconnect Request	DISC sent	REL or DISC received	REL sent.	Timer is not restarted
T308	30s	Release request	REL sent	REL COMP or REL received	Retrans. RELEASE restart T308	Call ref. release
T310 Note 1	30s	Outgoing call Proceeding	CALL PROC received	ALERT,CONN, DISC or PROG rec.	Send DISC	Timer is not restarted
T313	30s	Connect Request	CONN sent	CONNect ACKnowledge received	Send DISC	Timer is not restarted
T323	30s	Modify Request	MOD sent	MOD COMP or MOD REJ received	Clear the call	Timer is not restarted
T324	15s	Modify request	MOD received	MOD COMP or MOD REJ sent	MOD REJ with old bearer capability	Timer is not restarted
T332	30s	Wait for network info	START_CC sent	CC-EST. received	Clear the call	Timer is not restarted
T335	30s	CC-Est. Confirmed	CC-EST CONF.sent	RECALL received	Clear the call	Timer is not restarted
T336	10s		START DTMF sent	START DTMF ACK or START DTMF REJECT received		Timer is not restarted
					The MS considers the DTMF Procedure (for the digit) to be terminated
T337	10s		STOP DTMF sent	STOP DTMF ACK received	The MS considers the DTMF procedure (for the current digit) to be terminated	Timer is not restarted

NOTE 1:     T310 is not started if progress indicator #1, #2, or #64 has been delivered in the CALL PROCEEDING message or in a previous PROGRESS message.

3GPP TS 24.008: Call control timers – network side

TIM NUM.	DFT TIM VAL	STATE OF CALL	CAUSE FOR START	NORMAL STOP	AT FIRST EXPIRY	AT SECOND EXPIRY
T301 Note 1	Min180s	Call received	ALERT received	CONN received	Clear the call	Timer is not restarted
T303	Note 2	Call present	SETUP sent	CALL CONF or REL COMP received	Clear the call	Timer is not restarted
T305	30s	Disconnect Indication	DISC without progress indic. #8 sent or CCBS Possible	REL or DISC received	Network sends RELEASE	Timer is not restarted
T306	30s	Disconnect Indication	DISC with progress indic. #8 sent but no CCBS possible	REL or DISC received	Stop the tone/ announc. Send REL	Timer is not restarted
T308	Note 2	Release request	REL sent	REL COMP or REL received	Retrans. RELEASE restart T308	Release call reference
T310	Note 2	Incoming call proceeding	CALL CONF received	ALERT, CONN or DISC received	Clear the call	Timer is not restarted
T313	Note 2	Connect Indication	CON sent	CON ACK received	Clear the call	Timer is not restarted
T323	30s	Modify request	MOD sent	MOD COMP or MOD REJ received	Clear the call	Timer is not restarted
T331	Note 2	CC Connec. Pending	CM-SERV PROMPT sent	START CC received	Clear the call	Timer is not restarted
T333	Note 2	CC-Est. Present	START CC received	CC-EST.CONF or REL COMP received	Clear the call	Timer is not restarted
T334 Note 3	Min 15s	CC-Est. Confirmed	RECALL sent	SETUP received	Clear the call	Timer is not restarted
T338	Note 2	Disconnect indication	DISC with CCBS possible	REL or DISC received	stop any tone/ announc. Send REL	Timer is not restarted

NOTE 1:     The network may already have applied an internal alerting supervision function; e.g. incorporated within call control. If such a function is known to be operating on the call, then timer T301 is not used.

NOTE 2:     These time values are set by the network operator.

NOTE 3:     When applied to the supplementary service CCBS, the timer T334 can either represent the recall timer T4 or the notification timer T10 (see 3GPP TS 23.093 [88a]). Thus the timer T334 can take two different values. 3GPP TS 23.093 [88a] defines the range of these values.

Message Type

The message type IE used in the Mobility Management protocol, the Call Control protocol, and Session management protocol.

3GPP TS 24.008: Message types for Mobility Management

8	7	6	5	4	3	2	1
x	x	0	0	–	–	–	–		Registration messages:
				0	0	0	1		– IMSI DETACH INDICATION
				0	0	1	0		– LOCATION UPDATING ACCEPT
				0	1	0	0		– LOCATION UPDATING REJECT
				1	0	0	0		– LOCATION UPDATING REQUEST
x	x	0	1	–	–	–	–		Security messages:
				0	0	0	1		– AUTHENTICATION REJECT
				0	0	1	0		– AUTHENTICATION REQUEST
				0	1	0	0		– AUTHENTICATION RESPONSE
				1	1	0	0		– AUTHENTICATION FAILURE…………..
				1	0	0	0		– IDENTITY REQUEST
				1	0	0	1		– IDENTITY RESPONSE
				1	0	1	0		– TMSI REALLOCATION COMMAND
				1	0	1	1		– TMSI REALLOCATION COMPLETE
x	x	1	0	–	–	–	–		Connection management messages:
				0	0	0	1		– CM SERVICE ACCEPT
				0	0	1	0		– CM SERVICE REJECT
				0	0	1	1		– CM SERVICE ABORT
				0	1	0	0		– CM SERVICE REQUEST
				0	1	0	1		– CM SERVICE PROMPT
				0	1	1	0		– Reserved (see NOTE)
				1	0	0	0		– CM RE-ESTABLISHMENT REQUEST
				1	0	0	1		– ABORT
x	x	1	1	–	–	–	–		Miscellaneous messages:
				0	0	0	0		– MM NULL
				0	0	0	1		– MM STATUS
				0	0	1	0		– MM INFORMATION

NOTE:     This value was allocated but never used in earlier phases of the protocol.

When the radio connection started with a core network node of earlier than R99, bit 8 shall be set to 0 and bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a “0”. See 3GPP TS 24.007 [20].

When the radio connection started with a core network node of R’99 or later, bits 7 and 8 are reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a “0”. See 3GPP TS 24.007 [20].

3GPP TS 24.008: Message types for Call Control and call related SS messages

8	7	6	5	4	3	2	1
x	x	0	0	0	0	0	0		escape to nationally specific
									message types; see 1) below
x	x	0	0	–	–	–	–		Call establishment messages:
				0	0	0	1		– ALERTING
				1	0	0	0		– CALL CONFIRMED
				0	0	1	0		– CALL PROCEEDING
				0	1	1	1		– CONNECT
				1	1	1	1		– CONNECT ACKNOWLEDGE
				1	1	1	0		– EMERGENCY SETUP
				0	0	1	1		– PROGRESS
				0	1	0	0		– CC-ESTABLISHMENT
				0	1	1	0		– CC-ESTABLISHMENT CONFIRMED
				1	0	1	1		– RECALL
				1	0	0	1		– START CC
				0	1	0	1		– SETUP
x	x	0	1	–	–	–	–		Call information phase messages:
				0	1	1	1		– MODIFY
				1	1	1	1		– MODIFY COMPLETE
				0	0	1	1		– MODIFY REJECT
				0	0	0	0		– USER INFORMATION
				1	0	0	0		– HOLD
				1	0	0	1		– HOLD ACKNOWLEDGE
				1	0	1	0		– HOLD REJECT
				1	1	0	0		– RETRIEVE
				1	1	0	1		– RETRIEVE ACKNOWLEDGE
				1	1	1	0		– RETRIEVE REJECT
x	x	1	0	–	–	–	–		Call clearing messages:
				0	1	0	1		– DISCONNECT
				1	1	0	1		– RELEASE
				1	0	1	0		– RELEASE COMPLETE
x	x	1	1	–	–	–	–		Miscellaneous messages:
				1	0	0	1		– CONGESTION CONTROL
				1	1	1	0		– NOTIFY
				1	1	0	1		– STATUS
				0	1	0	0		– STATUS ENQUIRY
				0	1	0	1		– START DTMF
				0	0	0	1		– STOP DTMF
				0	0	1	0		– STOP DTMF ACKNOWLEDGE
				0	1	1	0		– START DTMF ACKNOWLEDGE
				0	1	1	1		– START DTMF REJECT
				1	0	1	0		– FACILITY

1):          When used, the message type is defined in the following octet(s), according to the national specification.

When the radio connection started with a core network node of earlier than R99, bit 8 shall be set to 0 and bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a “0”. See 3GPP TS 24.007 [20].

When the radio connection started with a core network node of R’99 or later, bits 7 and 8 are reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a “0”. See 3GPP TS 24.007 [20].

3GPP TS 24.008: Message types for GPRS mobility management

Bits
8	7	6	5	4	3	2	1
0	0	–	–	–	–	–	–		Mobility management messages
0	0	0	0	0	0	0	1		Attach request
0	0	0	0	0	0	1	0		Attach accept
0	0	0	0	0	0	1	1		Attach complete
0	0	0	0	0	1	0	0		Attach reject
0	0	0	0	0	1	0	1		Detach request
0	0	0	0	0	1	1	0		Detach accept
0	0	0	0	1	0	0	0		Routing area update request
0	0	0	0	1	0	0	1		Routing area update accept
0	0	0	0	1	0	1	0		Routing area update complete
0	0	0	0	1	0	1	1		Routing area update reject
0	0	0	0	1	1	0	0		Service Request
0	0	0	0	1	1	0	1		Service Accept
0	0	0	0	1	1	1	0		Service Reject
0	0	0	1	0	0	0	0		P-TMSI reallocation command
0	0	0	1	0	0	0	1		P-TMSI reallocation complete
0	0	0	1	0	0	1	0		Authentication and ciphering req
0	0	0	1	0	0	1	1		Authentication and ciphering resp
0	0	0	1	0	1	0	0		Authentication and ciphering rej
0	0	0	1	1	1	0	0		Authentication and ciphering failure
0	0	0	1	0	1	0	1		Identity request
0	0	0	1	0	1	1	0		Identity response
0	0	1	0	0	0	0	0		GMM status
0	0	1	0	0	0	0	1		GMM information

3GPP TS 24.008: Message types for GPRS session management

Bits
8	7	6	5	4	3	2	1
0	1	–	–	–	–	–	–		Session management messages
0	1	0	0	0	0	0	1		Activate PDP context request
0	1	0	0	0	0	1	0		Activate PDP context accept
0	1	0	0	0	0	1	1		Activate PDP context reject
0	1	0	0	0	1	0	0		Request PDP context activation
0	1	0	0	0	1	0	1		Request PDP context activation rej.
0	1	0	0	0	1	1	0		Deactivate PDP context request
0	1	0	0	0	1	1	1		Deactivate PDP context accept
0	1	0	0	1	0	0	0		Modify PDP context request(Network to MS direction)
0	1	0	0	1	0	0	1		Modify PDP context accept (MS to network direction)
0	1	0	0	1	0	1	0		Modify PDP context request(MS to network direction)
0	1	0	0	1	0	1	1		Modify PDP context accept (Network to MS direction)
0	1	0	0	1	1	0	0		Modify PDP context reject
0	1	0	0	1	1	0	1		Activate secondary PDP context request
0	1	0	0	1	1	1	0		Activate secondary PDP context accept
0	1	0	0	1	1	1	1		Activate secondary PDP context reject
0	1	0	1	0	0	0	0		Reserved: was allocated in earlier phases of the protocol
0	1	0	1	0	0	0	1		Reserved: was allocated in earlier phases of the protocol
0	1	0	1	0	0	1	0		Reserved: was allocated in earlier phases of the protocol
0	1	0	1	0	0	1	1		Reserved: was allocated in earlier phases of the protocol
0	1	0	1	0	1	0	0		Reserved: was allocated in earlier phases of the protocol
0	1	0	1	0	1	0	1		SM Status
0	1	0	1	0	1	1	0		Activate MBMS Context Request
0	1	0	1	0	1	1	1		Activate MBMS Context Accept
0	1	0	1	1	0	0	0		Activate MBMS Context Reject
0	1	0	1	1	0	0	1		Request MBMS Context Activation
0	1	0	1	1	0	1	0		Request MBMS Context Activation Reject
0	1	0	1	1	0	1	1		Request Secondary PDP Context Activation
0	1	0	1	1	1	0	0		Request Secondary PDP Context Activation Reject
0	1	0	1	1	1	0	1		Notification