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.requestmessage 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.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
7/28/2019 NAS Messages
http://slidepdf.com/reader/full/nas-messages 1/28
Causes related to nature of requestCause value = 8 Operator Determined Barring
This cause code is used by the network to indicate that the requested service was rejected by theSGSN 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 wasrejected by the network, because the MBMS bearer capabilities are insufficient for the MBMSservice.
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 orSNDCP 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 activationrequest, secondary PDP context activation request, PDP context modification request, or MBMScontext 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 theexternal packet data network because the access point name was not included although required orif 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 theexternal 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 theexternal 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 theGGSN, 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.
7/28/2019 NAS Messages
http://slidepdf.com/reader/full/nas-messages 2/28
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 bythe 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 thePDP 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 aregular 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 thenetwork 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 MBMScontext 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 contextactivation 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 theTFT operation included in a secondary PDP context activation request or an MS-initiated PDPcontext modification or a network requested secondary PDP context activation.
Cause value = 42 syntactical error in the TFT operation.
7/28/2019 NAS Messages
http://slidepdf.com/reader/full/nas-messages 3/28
This cause code is used by the network or the MS to indicate that there is a syntactical error in theTFT operation included in a secondary PDP context activation request or an MS-initiated PDPcontext 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 theLinked TI IE in the secondary PDP context activation request or a network requested secondaryPDP 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 semanticerrors in packet filter(s) of the TFT included in a secondary PDP context activation request or anMS-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 syntacticalerrors in packet filter(s) of the TFT included in a secondary PDP context activation request or anMS-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 PDPcontext 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 becausethe timer supervising the IGMP group membership interval (see RFC 3376 [107], subclause 8.4) orthe 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 wasrejected 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 withthe 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 withthe 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 withthe restriction that only single IP version bearers are allowed.
7/28/2019 NAS Messages
http://slidepdf.com/reader/full/nas-messages 4/28
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 sincethe network has requested a secondary PDP context activation for the same service using anetwork-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 PDPcontext. Restriction values are defined in 3GPP TS 23.060 [74], subclause 15.4.
H.1 Normal classH.1.1 Cause No. 1 “unassigned (unallocated)number” This cause indicates that the destination requested by the mobile station cannot be reachedbecause, 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 thecall 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 foruse 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 orservice 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 hasrequested 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.
7/28/2019 NAS Messages
http://slidepdf.com/reader/full/nas-messages 5/28
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 analerting or connect indication within the prescribed period of time allocated (defined by the expiryof 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 connectindication 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 busynor 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 thecalling mobile station is no longer assigned. The new called party number may optionally beincluded 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 -empt ion”
This cause is returned to the network when a mobile station clears an active call which is beingpre-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 C ause No. 27 “destination out of order”
This cause indicates that the destination indicated by the mobile station cannot be reached becausethe 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 physicallayer 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 nota valid format or is not complete.
7/28/2019 NAS Messages
http://slidepdf.com/reader/full/nas-messages 6/28
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 STATUSENQUIRY”
This cause is included in STATUS messages if the message is sent in response to a STATUSENQUIRY 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 classH.2.1 Cause No. 34 “no circuit/channel available”
This cause indicates that there is no appropriate circuit/channel presently available to handle thecall.
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 tolast a relatively long period of time; e.g., immediately re-attempting the call is not likely to besuccessful.
H.2.3 Cause No. 41 “temporary failure”
This cause indicates that the network is not functioning correctly and that the condition is not likelyto last a long period of time; e.g., the mobile station may wish to try another call attempt almostimmediately.
H.2.4 Cause No. 42 “switching equipmentcongestion”
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 asrequested; i.e., a user-to-user information, low layer compatibility, high layer compatibility, or sub-
address as indicated in the diagnostic.
7/28/2019 NAS Messages
http://slidepdf.com/reader/full/nas-messages 7/28
It is noted that the particular type of access information discarded is optionally included in thediagnostic.
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 beprovided 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 resourceunavailable class applies.
H.3 Service or option not availableclassH.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-TRecommendation X.213, cannot be provided.
H.3.2 Cause No. 50 “Requested facility notsubscribed”
This cause indicates that the requested supplementary service could not be provided by thenetwork because the user has no completed the necessary administrative arrangements with itssupporting networks.
H.3.3 Cause No. 55 “Incoming calls barred withinthe CU G”
This cause indicates that although the called party is a member of the CUG for the incoming CUGcall, incoming calls are not allowed within this CUG.
H.3.4 Cause No. 57 “bearer capability notauthorized”
This cause indicates that the mobile station has requested a bearer capability which is implementedby the equipment which generated this cause but the mobile station is not authorized to use.
7/28/2019 NAS Messages
http://slidepdf.com/reader/full/nas-messages 8/28
7/28/2019 NAS Messages
http://slidepdf.com/reader/full/nas-messages 9/28
This cause is used to report a service or option not implemented event only when no other cause inthe service or option not implemented class applies.
H.5 Invalid message (e.g., parameterout of range) classH.5.1 Cause No. 81 “invalid transacti on identifiervalue”
This cause indicates that the equipment sending this cause has received a message with atransaction 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 specifiedCUG.
H.5.3 Cause No. 88 “incompatible destination”
This cause indicates that the equipment sending this cause has received a request to establish acall 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 networkselection”
For further study. Treated as cause no. 95.
H.5.5 Cause No. 95 “se mantically incorrectmessage”
This cause is used to report receipt of a message with semantically incorrect contents (see
H.6.2 Cause No. 97 “message type non -existent ornot 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 notimplemented by the equipment sending this cause.
H.6.3 Cause No. 98 “message type not compatiblewith protocol state”
This cause indicates that the equipment sending this cause has received a message not compatiblewith 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 includesinformation elements not recognized because the information element identifier is not defined or itis defined but not implemented by the equipment sending the cause. However, the informationelement is not required to be present in the message in order for the equipment sending the causeto 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 withconditional IE errors (see subclause 8.7.2).
H.6.6 Cause No. 101 “message not compatible withprotocol state”
This cause indicates that a message has been received which is incompatible with the protocolstate 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 with3GPP 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 errorclass applies.
This cause indicates that there has been interworking with a network which does not providecauses for actions it takes; thus, the precise cause for a message which is being sent cannot beascertained.
Causes related to MS identificationCause 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 doesnot 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 identityof the MS is not acceptable to the network or because the MS does not pass the authenticationcheck, i.e. the SRES received from the MS is different from that generated by the network. Whenused by an MM procedure, except the authentication procedure, this cause does not affectoperation 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 anIMEI 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. Whenused by an MM procedure, this cause does not affect operation of the GPRS service.
Cause related to subscription optionsCause value = 11 PLMN not allowed
This cause is sent to the MS if it requests location updating in a PLMN where the MS, bysubscription 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 HPLMNdetermines 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 otherPLMNs 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 bysubscription 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, bysubscription, is not allowed to operate, but when it should find another allowed location area in thesame PLMN.
NOTE: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the MS tosearch 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 nosubscription to operate or the MS s subscript ion has expired and it should find another cell in thesame PLMN.
NOTE: The MS not supporting CSG will not receive cause# 25, as such a MS is not supposed totry to access a CSG cell.
Causes related to PLMN specificnetwork failures and
congestion/Authentication FailuresCause value = 20 MAC failure
This cause is sent to the network if the USIM detects that the MAC in the AUTHENTICATIONREQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message is not fresh (see 3GPP TS33.102 [5a]).
Cause value = 21 Synch failure
This cause is sent to the network if the USIM detects that the SQN in the AUTHENTICATIONREQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message is out of range (see 3GPP TS33.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 PLMNfailures, 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,
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 GMMCause 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 incase 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 whileafter the Mobile reachable timer has expired, or if the GMM context data related to the subscriptiondose 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 roamingfor 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 aPLMN 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 allactive PDP contexts by sending a SERVICE REQUEST message indicating “data” to the network, butthe SGSN does not have any active PDP context(s).
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 locationupdating 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 initiatesestablishment 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 RELEASENOT ALLOWED.
Timer T3241 is stopped and reset (but not started) when the MM state RR CONNECTION RELEASENOT 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
At routing area updatingfailure and the attemptcounter is greater than orequal to 5.
At successfulrouting areaupdating
GPRS attachprocedure
or
RAU procedureT3312 Default
54 min
Note1
GMM-REG In A/Gb mode, whenREADY state is left.
In Iu mode, when PMM-CONNECTED mode is left.
When enteringstate GMM-DEREG
Initiation of thePeriodic RAUprocedure
T3314
READY
(A/Gbmodeonly)
Default44 secNote 2
All exceptGMM-DEREG
Transmission of a PTP PDU Forced to Standby No cell-updatesare performed
T3317
(Iu modeonly)
15s GMM-SERVICE-REQUEST-INITIATED
SERVICE REQ sent Security modecontrol procedureis completed,
SERVICE ACCEPTreceived, or
SERVICE REJECTreceived
Abort theprocedure
T3319
(Iu modeonly)
Default30s
Note 1
Note 4
GMM-REG Completion of the SecurityMode Control procedureafter sending a SERVICEREQUEST with service type
“data”.
Reception of a SERVICEACCEPT message.
When enteringPMM-IDLE mode.
When the radioaccess bearer isreleased for anyactive PDPcontext.
When enteringstate GMM-DEREG
SERVICE REQwith service type
“data” may beinvoked again, if required.
T3323 NOTE 6 GMM-REGISTERED
T3312 expires while the MSis in GMM-REGISTERED.NO-CELL-AVAILABLE and ISR isactivated.
When enteringstate GMM-DEREGISTERED orwhen enteringGMM-CONNECTEDmode.
Deactivation of ISR by settingTIN to “GUTI”
NOTE 1: The value of this timer is used if the network does not indicate another value in a GMMsignalling procedure.
NOTE 2: The default value of this timer is used if neither the MS nor the Network send anothervalue, 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 REQUESTmessage with service type “data” too early in case the request to setup the radio access bearer isqueued by the radio access network.
NOTE 5: In Iu mode, the default value of this timer is used if the network provides a value forthis 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 ATTACHACCEPT message and ROUTING AREA UPDATE ACCEPT message. The default value of this timer isidentical to the value of timer T3312.
3GPP TS 24.008: GPRS Mobility management timers – network side
TIMERNUM.
TIMERVALUE
STATE CAUSE OF START NORMAL STOP ON THE1st, 2nd, 3rd,4th EXPIRY Note 3
T3322 6s GMM-
DEREG-INIT
DETACH REQ sent DETACH ACCEPT
received
Retransmission of
DETACH REQUESTT3350 6s GMM-COMMON-PROC-INIT
ATTACH ACCEPTsent with P-TMSI and/orTMSIRAU ACCEPT sent with P-TMSI and/or TMSI
P-TMSI REALLOC COMMANDsent
ATTACHCOMPLETEreceived
RAU COMPLETEreceived
P-TMSI REALLOCCOMPLETEreceived
Retransmission of the same messagetype, i.e. ATTACHACCEPT, RAUACCEPT orREALLOCCOMMAND
T3360 6s GMM-COMMON-PROC-INIT
AUTH AND CIPH REQUESTsent
AUTH AND CIPHRESPONSEreceived
AUTHENT-ANDCIPHER-FAILUREreceived
Retransmission of AUTH AND CIPHREQUEST
T3370 6s GMM-COMMON-PROC-INIT
IDENTITY REQUEST sent IDENTITYRESPONSEreceived
Retransmission of IDENTITYREQUEST
3GPP TS 24.008: GPRS Mobility management timers – network side
TIMER NUM. TIMERVALUE STATE CAUSE OF START NORMAL STOP ON EXPIRYT3313 Note 1 GMM_REG Paging procedure initiated Paging
procedurecompleted
Networkdependent
T3314
READY
(A/Gb modeonly)
Default44 secNote 2
All exceptGMM-DEREG
Receipt of a PTP PDU Forced toStandby
The networkshall page theMS if a PTP PDUhas to be sent tothe MS
MobileReachable
Default 4mingreaterthan
All exceptGMM-DEREG
In A/Gb mode, change fromREADY to STANDBY state
In Iu mode, change from
PTP PDUreceived
Networkdependent buttypically pagingis halted on 1st
The Mobile Reachable timerexpires while the network isin PMM-IDLE mode orSTANDBY state and ISR is
activated.
PTP PDUreceived
Implicitly detachthe MS on 1stexpiry
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 anothervalue, or if the Network sends this value, in a signalling procedure. The value of this timer shouldbe 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 management3GPP TS 24.008: GPRS session management timers – MS side
TIMERNUM.
TIMERVALUE
STATE CAUSE OF START NORMAL STOP ON THE1st, 2nd, 3rd,4th EXPIRY
T3380 30s PDP-ACTIVE-PENDor MBMSACTIVE-PENDING
ACTIVATE PDP CONTEXTREQUEST, ACTIVATESECONDARY PDP CONTEXTREQUEST or ACTIVATEMBMS CONTEXT REQUESTsent
ACTIVATEPDP CONTEXTACCEPT,ACTIVATESECONDARY PDPCONTEXTACCEPT orACTIVATE MBMSCONTEXTACCEPT received
ACTIVATEPDP CONTEXTREJECT,ACTIVATESECONDARY PDPCONTEXTREJECT orACTIVATE MBMSCONTEXTREJECT received
Retransmission of ACTIVATE PDPCONTEXT REQ,ACTIVATESECONDARY PDPCONTEXTREQUEST orACTIVATE MBMSCONTEXTREQUEST
T3381 8s PDP-MODIFY-PENDING
MODIFY PDP CONTEXTREQUEST sent
MODIFY PDPCONTEXTACCEPT received
Retransmission of MODIFY PDPCONTEXTREQUEST
T3390 8s PDP-INACT-PEND
DEACTIVATE PDP CONTEXTREQUEST sent
DEACTIVATEPDP CONTEXTACCreceived
Retransmission of DEACTIVATEPDP CONTEXTREQUEST
NOTE: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptionsare described in the corresponding procedure description.
DEACTIVATE PDP CONTEXTREQUEST sent DEACTIVATEPDP CONTEXTACC received
Retransmission of DEACTIVATE PDPCONTEXT REQ
NOTE: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptionsare described in the corresponding procedure description.
Timers of circuit-switched call control
3GPP TS 24.008: Call control timers – MS side
TIM
NUM.
TIMVAL
STATE OFCALL
CAUSE OFSTART
NORMAL STOP AT FIRSTEXPIRY
AT SECONDEXPIRY
T303 30s Call initiated CM SER RQ sent CALL PROC, or RELCOMP received
Clear the call Timer is notrestarted
T305 30s DisconnectRequest
DISC sent REL or DISCreceived
REL sent. Timer is notrestarted
T308 30s Releaserequest
REL sent REL COMP or RELreceived
Retrans.RELEASErestart 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 ConnectRequest
CONN sent CONNectACKnowledgereceived
Send DISC Timer is notrestarted
T323 30s Modify Request MOD sent MOD COMP orMOD REJ received
Clear the call Timer is notrestarted
T324 15s Modify request MOD received MOD COMP orMOD REJ sent
MOD REJ withold bearercapability
Timer is notrestarted
T332 30s Wait fornetwork info
START_CC sent CC-EST. received Clear the call Timer is notrestarted
T335 30s CC-Est.
Confirmed
CC-EST
CONF.sent
RECALL received Clear the call Timer is not
restartedT336 10s START DTMF START DTMF ACK Timer is not
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 timerT301 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 representthe recall timer T4 or the notification timer T10 (see 3GPP TS 23.093 [88a]). Thus the timer T334can take two different values. 3GPP TS 23.093 [88a] defines the range of these values.
Message Type in IE
Message Type
The message type IE used in the Mobility Management protocol, the Call Control protocol, andSession management protocol.
3GPP TS 24.008: Message types for Mobility Management
x x 1 0 - - - - Connection management messages:0 0 0 1 - CM SERVICE ACCEPT0 0 1 0 - CM SERVICE REJECT0 0 1 1 - CM SERVICE ABORT0 1 0 0 - CM SERVICE REQUEST0 1 0 1 - CM SERVICE PROMPT
0 1 1 0 - Reserved (see NOTE)1 0 0 0 - CM RE-ESTABLISHMENT REQUEST1 0 0 1 - ABORT
x x 1 1 - - - - Miscellaneous messages:0 0 0 0 - MM NULL0 0 0 1 - MM STATUS0 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 setto 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 arereserved for the send sequence number in messages sent from the mobile station. In messagessent from the network, bits 7 and 8 are coded wit h 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 1x x 0 0 0 0 0 0 escape to nationally specific
message types; see 1) belowx x 0 0 - - - - Call establishment messages:
1): When used, the message type is defined in the following octet(s), according to thenational specification.
When the radio connection started with a core network node of earlier than R99, bit 8 shall be setto 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 arereserved for the send sequence number in messages sent from the mobile station. In messagessent 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