3GPP TS 24.008

3GPP TS 24.008 V12.1.0 (2013-03)Release 122

3GPP TS 24.008 V12.1.0 (2013-03)Technical Specification

3rd Generation Partnership Project;

Technical Specification Group Core Network and Terminals;

Mobile radio interface Layer 3 specification;

Core network protocols; Stage 3

(Release 12)

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.

The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.

Keywords

UMTS, GSM, radio, layer3, stage3, network, LTE3GPP

Postal address

3GPP support office address

650 Route des Lucioles - Sophia Antipolis

Valbonne - FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet

http://www.3gpp.org

Copyright Notification

No part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.

2013, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).

All rights reserved.

UMTS is a Trade Mark of ETSI registered for the benefit of its members

3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners

GSM and the GSM logo are registered and owned by the GSM Association

Contents

26Foreword

Introduction261Scope271.1Scope of the Technical Specification271.2Application to the interface structures271.3Structure of layer 3 procedures271.4Test procedures281.5Use of logical channels in A/Gb mode281.6Overview of control procedures281.6.1List of procedures281.7Applicability of implementations301.7.1Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS)301.7.2General Packet Radio Service (GPRS)301.7.2.1Packet services in GSM (A/Gb mode only)301.7.2.2Packet services in Iu mode (Iu mode only)311.8Handling of NAS signalling low priority indication311.9Restrictions322References322.1Definitions and abbreviations382.1.1Random values382.1.2Vocabulary383Radio Resource management procedures424Elementary procedures for Mobility Management424.1General424.1.1MM and GMM procedures434.1.1.1Types of MM and GMM procedures434.1.1.1.1Integrity Checking of Signalling Messages in the Mobile Station (Iu mode only)444.1.1.1.1aIntegrity protection for emergency call (Iu mode only)464.1.1.2MM-GMM co-ordination for GPRS MS's474.1.1.2.1GPRS MS operating in mode A or B in a network that operates in mode I474.1.1.2.2GPRS MS operating in mode A or B in a network that operates in mode II484.1.1.2ACoordination between GMM and EMM484.1.1.3Core Network System Information for MM (Iu mode only)484.1.1.4Core Network System Information for GMM (Iu mode only)494.1.1.4.1General494.1.1.4.2Control of Network Mode of Operation I494.1.1.5Access class control494.1.1.6Specific requirements for MS configured to use timer T3245504.1.1.7Handling of NAS level mobility management congestion control504.1.1.8Handling of security related parameters at switch on and switch off514.1.2MM sublayer states514.1.2.1MM sublayer states in the mobile station514.1.2.1.1Main states524.1.2.1.2Substates of the MM IDLE state564.1.2.2The update Status584.1.2.3MM sublayer states on the network side584.1.3GPRS mobility management (GMM) sublayer states604.1.3.1GMM states in the MS604.1.3.1.1Main states604.1.3.1.2Substates of state GMM-DEREGISTERED614.1.3.1.3Substates of state GMM-REGISTERED614.1.3.2GPRS update status644.1.3.3GMM mobility management states on the network side644.1.3.3.1Main States654.1.3.3.2Substates of state GMM-REGISTERED654.2Behaviour of the MS in MM Idle state, GMM-DEREGISTERED state and GMM-REGISTERED state664.2.1Primary Service State selection664.2.1.1Selection of the Service State after Power On.664.2.1.2Other Cases674.2.2Detailed Description of the MS behaviour in MM IDLE State.674.2.2.1Service State, NORMAL SERVICE674.2.2.2Service State, ATTEMPTING TO UPDATE684.2.2.3Service State, LIMITED SERVICE684.2.2.4Service State, NO IMSI694.2.2.5Service State, SEARCH FOR PLMN, NORMAL SERVICE694.2.2.6Service State, SEARCH FOR PLMN704.2.2.7Service State, RECEIVING GROUP CALL (NORMAL SERVICE)704.2.2.8Service State, RECEIVING GROUP CALL (LIMITED SERVICE)704.2.2.9Service State, eCALL INACTIVE714.2.3Service state when back to state MM IDLE from another state714.2.4Behaviour in state GMM-DEREGISTERED724.2.4.1Primary substate selection724.2.4.1.1Selection of the substate after power on or enabling the MS's GPRS capability724.2.4.1.2Other Cases734.2.4.2Detailed description of the MS behaviour in state GMM-DEREGISTERED734.2.4.2.1Substate, NORMAL-SERVICE734.2.4.2.2Substate, ATTEMPTING-TO-ATTACH734.2.4.2.3Substate, LIMITED-SERVICE734.2.4.2.4Substate, NO-IMSI744.2.4.2.5Substate, NO-CELL744.2.4.2.6Substate, PLMN-SEARCH744.2.4.2.7Substate, ATTACH-NEEDED744.2.4.2.8Substate, SUSPENDED (A/Gb mode only)744.2.4.3Substate when back to state GMM-DEREGISTERED from another GMM state744.2.5Behaviour in state GMM-REGISTERED754.2.5.1Detailed description of the MS behaviour in state GMM-REGISTERED754.2.5.1.1Substate, NORMAL-SERVICE754.2.5.1.2Substate, SUSPENDED (A/Gb mode only)754.2.5.1.3Substate, UPDATE-NEEDED754.2.5.1.4Substate, ATTEMPTING-TO-UPDATE764.2.5.1.5Substate, NO-CELL-AVAILABLE764.2.5.1.6Substate, LIMITED-SERVICE764.2.5.1.7Substate, ATTEMPTING-TO-UPDATE-MM764.2.5.1.8Substate, PLMN-SEARCH774.3MM common procedures774.3.1TMSI reallocation procedure774.3.1.1TMSI reallocation initiation by the network774.3.1.2TMSI reallocation completion by the mobile station784.3.1.3TMSI reallocation completion in the network.784.3.1.4Abnormal cases784.3.2Authentication procedure794.3.2aAuthentication procedure used for a UMTS authentication challenge794.3.2bAuthentication Procedure used for a GSM authentication challenge794.3.2.1Authentication request by the network794.3.2.2Authentication response by the mobile station804.3.2.3Authentication processing in the network804.3.2.3a128-bit circuit-switched GSM ciphering key814.3.2.4Ciphering key sequence number814.3.2.5Authentication not accepted by the network824.3.2.5.1Authentication not accepted by the MS824.3.2.6Abnormal cases834.3.2.6.1MS behaviour towards a network that has failed the authentication procedure854.3.2.7Handling of keys at intersystem change from Iu mode to A/Gb mode854.3.2.7aUse of established security contexts864.3.2.8Handling of keys at intersystem change from A/Gb mode to Iu mode874.3.2.9Void884.3.2.10Derivation of keys at SRVCC or vSRVCC handover from S1 mode884.3.2.10.0General884.3.2.10.1PDN connection with integrity protection884.3.2.10.2PDN connection without integrity protection884.3.2.11Derivation of keys at SRVCC handover from Iu mode to Iu mode884.3.2.11.1PDN connection with integrity protection884.3.2.11.2PDN connection without integrity protection894.3.2.12Derivation of keys at SRVCC handover from Iu mode to A/Gb mode904.3.2.12.1PDN connection with integrity protection904.3.2.12.2PDN connection without integrity protection914.3.2.13Derivation of keys at CS to PS SRVCC handover from A/Gb mode to Iu mode914.3.3Identification procedure934.3.3.1Identity request by the network934.3.3.2Identification response by the mobile station934.3.3.3Abnormal cases934.3.4IMSI detach procedure944.3.4.0General944.3.4.1IMSI detach initiation by the mobile station944.3.4.2IMSI detach procedure in the network954.3.4.3IMSI detach completion by the mobile station954.3.4.4Abnormal cases954.3.5Abort procedure954.3.5.1Abort procedure initiation by the network954.3.5.2Abort procedure in the mobile station964.3.6MM information procedure964.3.6.1MM information procedure initiation by the network964.3.6.2MM information procedure in the mobile station964.4MM specific procedures964.4.1Location updating procedure964.4.2Periodic updating984.4.3IMSI attach procedure994.4.4Generic Location Updating procedure1004.4.4.1Location updating initiation by the mobile station1004.4.4.1aNetwork Request for Additional mobile station Capability Information1004.4.4.2Identification request from the network1004.4.4.3Authentication by the network1004.4.4.4Security mode setting by the network1004.4.4.5Attempt Counter1004.4.4.6Location updating accepted by the network1014.4.4.7Location updating not accepted by the network1024.4.4.8Release of RR connection after location updating1044.4.4.9Abnormal cases on the mobile station side1044.4.4.10Abnormal cases on the network side1064.4.5Void1074.4.6Void1074.4.7eCall inactivity procedure1074.5Connection management sublayer service provision1084.5.1MM connection establishment1084.5.1.1MM connection establishment initiated by the mobile station1084.5.1.2Abnormal cases1114.5.1.3MM connection establishment initiated by the network1134.5.1.3.1Mobile Terminating CM Activity1134.5.1.3.2Mobile Originating CM Activity $(CCBS)$1144.5.1.3.3Paging response in Iu mode (Iu mode only)1154.5.1.3.4Paging response for CS fallback1154.5.1.4Abnormal cases1154.5.1.5MM connection establishment for emergency calls1164.5.1.5aMM connection establishment for emergency calls for CS fallback1164.5.1.6Call re-establishment1174.5.1.6.1Call re-establishment, initiation by the mobile station1174.5.1.6.2Abnormal cases1194.5.1.7Forced release during MO MM connection establishment1194.5.1.8MM connection establishment due to SRVCC or vSRVCC handover1204.5.2MM connection information transfer phase1204.5.2.1Sending CM messages1204.5.2.2Receiving CM messages1204.5.2.3Abnormal cases1214.5.3MM connection release1214.5.3.1Release of associated RR connection1214.5.3.2Uplink release in a voice group call1224.6Receiving a MM STATUS message by a MM entity.1224.7Elementary mobility management procedures for GPRS services1224.7.1General1224.7.1.1Lower layer failure1224.7.1.2Ciphering of messages (A/Gb mode only)1224.7.1.3P-TMSI signature1234.7.1.4Radio resource sublayer address handling1234.7.1.4.1Radio resource sublayer address handling (A/Gb mode only)1234.7.1.5P-TMSI handling1244.7.1.5.1P-TMSI handling in A/Gb mode1244.7.1.5.2P-TMSI handling in Iu mode1254.7.1.5.3Void1254.7.1.5.4Void1254.7.1.6Change of network mode of operation1254.7.1.6.1Change of network mode of operation in A/Gb mode (A/Gb mode only)1254.7.1.6.2Change of network mode of operation in Iu mode (Iu mode only)1254.7.1.6.3Change of network mode of operation at Iu mode to A/Gb mode inter-system change1264.7.1.6.4Change of network mode of operation at A/Gb mode to Iu mode inter-system change1264.7.1.7Intersystem change between A/Gb mode and Iu mode1274.7.1.8List of forbidden PLMNs for GPRS service1284.7.1.8aEstablishment of the PS signalling connection (Iu mode only)1284.7.1.9Release of the PS signalling connection (Iu mode only)1294.7.2GPRS Mobility management timers and UMTS PS signalling connection control1294.7.2.1READY timer behaviour1294.7.2.1.1READY timer behaviour (A/Gb mode only)1294.7.2.1.2Handling of READY timer in Iu mode (Iu mode only)1304.7.2.2Periodic routing area updating1304.7.2.3PMM-IDLE mode and PMM-CONNECTED mode (Iu mode only)1324.7.2.4Handling of Force to standby in Iu mode (Iu mode only)1334.7.2.5RA Update procedure for Signalling Connection Re-establishment (Iu mode only)1334.7.2.6Cell Update triggered by low layers1334.7.2.7Handling of timer T33021334.7.3GPRS attach procedure1334.7.3.1GPRS attach procedure for GPRS services1354.7.3.1.1GPRS attach procedure initiation1354.7.3.1.2GMM common procedure initiation1364.7.3.1.3GPRS attach accepted by the network1364.7.3.1.4GPRS attach not accepted by the network1384.7.3.1.4aGPRS attach for emergency bearer services not accepted by the network (UTRAN Iu mode only)1434.7.3.1.4bAttach for initiating a PDN connection for emergency bearer services not accepted by the network (UTRAN Iu mode only)1434.7.3.1.5Abnormal cases in the MS1444.7.3.1.6Abnormal cases on the network side1464.7.3.2Combined GPRS attach procedure for GPRS and non-GPRS services1474.7.3.2.1Combined GPRS attach procedure initiation1484.7.3.2.2GMM Common procedure initiation1484.7.3.2.3Combined GPRS attach accepted by the network1484.7.3.2.4Combined GPRS attach not accepted by the network1504.7.3.2.5Abnormal cases in the MS1534.7.3.2.6Abnormal cases on the network side1544.7.4GPRS detach procedure1544.7.4.0General1544.7.4.1MS initiated GPRS detach procedure1554.7.4.1.1MS initiated GPRS detach procedure initiation1554.7.4.1.2MS initiated GPRS detach procedure completion for GPRS services only1554.7.4.1.3MS initiated combined GPRS detach procedure completion1564.7.4.1.4Abnormal cases in the MS1564.7.4.1.5Abnormal cases on the network side1584.7.4.2Network initiated GPRS detach procedure1594.7.4.2.1Network initiated GPRS detach procedure initiation1594.7.4.2.2Network initiated GPRS detach procedure completion by the MS1594.7.4.2.3Network initiated GPRS detach procedure completion by the network1634.7.4.2.4Abnormal cases on the network side1634.7.5Routing area updating procedure1644.7.5.1Normal and periodic routing area updating procedure1664.7.5.1.1Normal and periodic routing area updating procedure initiation1674.7.5.1.2GMM Common procedure initiation1684.7.5.1.3Normal and periodic routing area updating procedure accepted by the network1684.7.5.1.4Normal and periodic routing area updating procedure not accepted by the network1724.7.5.1.4aRouting area updating procedure for initiating a PDN connection for emergency bearer services not accepted by the network (UTRAN Iu mode only)1774.7.5.1.5Abnormal cases in the MS1774.7.5.1.6Abnormal cases on the network side1804.7.5.2Combined routing area updating procedure1824.7.5.2.0General1824.7.5.2.1Combined routing area updating procedure initiation1824.7.5.2.2GMM Common procedure initiation1844.7.5.2.3Combined routing area updating procedure accepted by the network1844.7.5.2.4Combined routing area updating not accepted by the network1864.7.5.2.5Abnormal cases in the MS1904.7.5.2.6Abnormal cases on the network side1914.7.6P-TMSI reallocation procedure1914.7.6.1P-TMSI reallocation initiation by the network1914.7.6.2P-TMSI reallocation completion by the MS1914.7.6.3P-TMSI reallocation completion by the network1924.7.6.4Abnormal cases on the network side1924.7.7Authentication and ciphering procedure1934.7.7aAuthentication and ciphering procedure used for UMTS authentication challenge.1934.7.7bAuthentication and ciphering procedure used for GSM authentication challenge1944.7.7cChange of the ciphering algorithm at PS Handover1944.7.7.1Authentication and ciphering initiation by the network1944.7.7.2Authentication and ciphering response by the MS1954.7.7.3Authentication and ciphering completion by the network1964.7.7.3a128-bit packet-switched GSM ciphering key1964.7.7.4GPRS ciphering key sequence number1974.7.7.5Authentication not accepted by the network1984.7.7.5.1Authentication not accepted by the MS1984.7.7.6Abnormal cases1994.7.7.6.1MS behaviour towards a network that has failed the authentication procedure2034.7.7.7Use of established security contexts2034.7.7.8Handling of keys at intersystem change from Iu mode to A/Gb mode2044.7.7.9Handling of keys at intersystem change from A/Gb mode to Iu mode2044.7.7.10Handling of keys at intersystem change from S1 mode to Iu mode or A/Gb mode2054.7.8Identification procedure2074.7.8.1Identification initiation by the network2074.7.8.2Identification response by the MS2074.7.8.3Identification completion by the network2074.7.8.3aAbnormal cases in the MS2074.7.8.4Abnormal cases on the network side2084.7.9Paging procedure2094.7.9.1Paging for GPRS services2094.7.9.1.1Paging for GPRS services using P-TMSI2094.7.9.1.2Paging for GPRS services using IMSI2104.7.9.2Paging for non-GPRS services2104.7.10Receiving a GMM STATUS message by a GMM entity2104.7.11Void2114.7.12GMM Information procedure2114.7.12.1GMM information procedure initiation by the network2114.7.12.2GMM information procedure in the mobile station2114.7.13Service Request procedure (Iu mode only)2114.7.13.1Service Request procedure initiation2134.7.13.2GMM common procedure initiation2134.7.13.3Service request procedure accepted by the network2134.7.13.4Service request procedure not accepted by the network2144.7.13.4aService request procedure for initiating a PDN connection for emergency bearer services not accepted by the network2184.7.13.5Abnormal cases in the MS2184.7.13.6Abnormal cases on the network side2204.7.14Void2215Elementary procedures for circuit-switched Call Control2215.1Overview2215.1.1General2215.1.2Call Control States2295.1.2.1Call states at the mobile station side of the interface2295.1.2.1.1Null (State U0)2295.1.2.1.2MM Connection pending (U0.1)2295.1.2.1.2aCC prompt present (U0.2) $(CCBS)$2295.1.2.1.2bWait for network information (U0.3) $(CCBS)$2295.1.2.1.2cCC-Establishment present (U0.4) $(CCBS)$2295.1.2.1.2dCC-Establishment confirmed (U0.5) $(CCBS)$2305.1.2.1.2eRecall present (U0.6) $(CCBS)$2305.1.2.1.3Call initiated (U1)2305.1.2.1.4Mobile originating call proceeding (U3)2305.1.2.1.5Call delivered (U4)2305.1.2.1.6Call present (U6)2305.1.2.1.7Call received (U7)2305.1.2.1.8Connect Request (U8)2305.1.2.1.9Mobile terminating call confirmed (U9)2305.1.2.1.10Active (U10)2305.1.2.1.11Disconnect request (U11)2305.1.2.1.12Disconnect indication (U12)2315.1.2.1.13Release request (U19)2315.1.2.1.14Mobile originating modify (U26)2315.1.2.1.15Mobile terminating modify (U27)2315.1.2.2Network call states2315.1.2.2.1Null (State N0)2315.1.2.2.2MM connection pending (N0.1)2315.1.2.2.2aCC connection pending (N0.2) $(CCBS)$2315.1.2.2.2bNetwork answer pending (N0.3) $(CCBS)$2315.1.2.2.2cCC-Establishment present (N0.4) $(CCBS)$2315.1.2.2.2dCC-Establishment confirmed (N0.5) $(CCBS)$2315.1.2.2.2eRecall present (N0.6) $(CCBS)$2315.1.2.2.3Call initiated (N1)2325.1.2.2.4Mobile originating call proceeding (N3)2325.1.2.2.5Call delivered (N4)2325.1.2.2.6Call present (N6)2325.1.2.2.7Call received (N7)2325.1.2.2.8Connect request (N8)2325.1.2.2.9Mobile terminating call confirmed (N9)2325.1.2.2.10Active (N10)2325.1.2.2.11Not used2325.1.2.2.12Disconnect indication (N12)2325.1.2.2.13Release request (N19)2325.1.2.2.14Mobile originating modify (N26)2325.1.2.2.15Mobile terminating modify (N27)2335.1.2.2.16Connect Indication (N28)2335.2Call establishment procedures2335.2.1Mobile originating call establishment2335.2.1.1Call initiation2345.2.1.2Receipt of a setup message2345.2.1.3Receipt of a CALL PROCEEDING message2365.2.1.4Notification of progressing mobile originated call2365.2.1.4.1Notification of interworking in connection with mobile originated call establishment2375.2.1.4.2Call progress in the PLMN/ISDN environment2375.2.1.5Alerting2375.2.1.6Call connected2385.2.1.7Call rejection2395.2.1.8Transit network selection2395.2.1.9Traffic channel assignment at mobile originating call establishment2395.2.1.10Call queuing at mobile originating call establishment2395.2.1.11Speech Codec Selection2395.2.1.12Cellular Text telephone Modem (CTM) selection2405.2.2Mobile terminating call establishment2415.2.2.1Call indication2415.2.2.2Compatibility checking2415.2.2.3Call confirmation2415.2.2.3.1Response to SETUP2415.2.2.3.2Receipt of CALL CONFIRMED and ALERTING by the network2425.2.2.3.3Call failure procedures2435.2.2.3.4Called mobile station clearing during mobile terminating call establishment2435.2.2.4Notification of interworking in connection with mobile terminating call establishment2435.2.2.5Call accept2445.2.2.6Active indication2445.2.2.7Traffic channel assignment at mobile terminating call establishment2445.2.2.8Call queuing at mobile terminating call establishment2455.2.2.9User connection attachment during a mobile terminating call2455.2.2.10Speech Codec Selection2455.2.2.11Cellular Text telephone Modem (CTM) selection2455.2.3Network initiated MO call $(CCBS)$2455.2.3.1Initiation2455.2.3.2CC-Establishment present2465.2.3.2.1Recall Alignment Procedure2475.2.3.3CC-Establishment confirmation2485.2.3.4Recall present2485.2.3.5Traffic channel assignment during network initiated mobile originating call establishment2495.2.4Call establishment for SRVCC or vSRVCC2495.2.4.1General2495.2.4.2Call activation for SRVCC2495.2.4.2aCall activation for vSRVCC2505.2.4.2bMultimedia CAT and vSRVCC handover2515.2.4.3Traffic channel assignment and user connection attachment2515.2.4.4State verification2525.3Signalling procedures during the "active" state2525.3.1User notification procedure2525.3.2Call rearrangements2525.3.3Codec Change Procedure2525.3.4Support of Dual Services2525.3.4.1Service Description2525.3.4.2Call establishment2535.3.4.2.1Mobile Originating Establishment2535.3.4.2.2Mobile Terminating Establishment2545.3.4.3Changing the Call Mode2545.3.4.3.1Initiation of in-call modification2545.3.4.3.2Successful completion of in-call modification2545.3.4.3.3Change of the channel configuration2565.3.4.3.4Failure of in-call modification2565.3.4.4Abnormal procedures2565.3.5User initiated service level up- and downgrading (A/Gb mode and GERAN Iu mode only)2575.3.5.1Initiation of service level up- and downgrading2575.3.5.2Successful completion of service level up- and downgrading2575.3.5.3Rejection of service level up- and downgrading2585.3.5.4Time-out recovery2585.3.6Support of multimedia calls2585.3.6.1Service description2585.3.6.2Call establishment2585.3.6.2.1Mobile originated multimedia call establishment2585.3.6.2.2Mobile terminating multimedia call2595.3.6.2.2.1Fallback to speech2605.3.6.3In-call modification in the "active" state2605.3.6.3.1Void2615.3.6.3.2Void2615.3.6.3.3Void2615.3.6.4Multimedia CAT during the alerting phase of a mobile originated call2615.3.6.5DTMF transmission during a multimedia call2625.3.6.6vSRVCC handover to a circuit-switched multimedia call2625.4Call clearing2625.4.1Terminology2625.4.2Exception conditions2625.4.3Clearing initiated by the mobile station2635.4.3.1Initiation of call clearing2635.4.3.2Receipt of a DISCONNECT message from the mobile station.2635.4.3.3Receipt of a RELEASE message from the network2635.4.3.4Receipt of a RELEASE COMPLETE message from the mobile station2635.4.3.5Abnormal cases2635.4.4Clearing initiated by the network2645.4.4.1Clearing initiated by the network: mobile does not support "Prolonged Clearing Procedure"2645.4.4.1.1Clearing when tones/announcements provided2645.4.4.1.2Clearing when tones/announcements not provided2645.4.4.1.3Completion of clearing2655.4.4.2Clearing initiated by the network: mobile supports "Prolonged Clearing Procedure"2655.4.4.2.1Clearing when tones/announcements provided and the network does not indicate that "CCBS activation is possible"2655.4.4.2.2Clearing when the network indicates that "CCBS activation is possible"2665.4.4.2.3Clearing when tones/announcements are not provided and the network does not indicate that "CCBS activation is possible"2675.4.4.2.4Receipt of a RELEASE message from the mobile station2675.4.4.2.5Completion of clearing2685.4.5Call clearing for SRVCC from CS to PS2685.5Miscellaneous procedures2685.5.1In-band tones and announcements2685.5.2Call collisions2695.5.3Status procedures2695.5.3.1Status enquiry procedure2695.5.3.2Reception of a STATUS message by a CC entity2705.5.3.2.1STATUS message with incompatible state2705.5.3.2.2STATUS message with compatible state2705.5.4Call re-establishment, mobile station side2705.5.4.1Indication from the mobility management sublayer2705.5.4.2Reaction of call control2705.5.4.3Completion of re-establishment2715.5.4.4Unsuccessful outcome2715.5.5Call re-establishment, network side2715.5.5.1State alignment2715.5.6Progress2715.5.7DTMF protocol control procedure2715.5.7.1Start DTMF request by the mobile station2725.5.7.2Start DTMF response by the network2725.5.7.3Stop DTMF request by the mobile station2725.5.7.4Stop DTMF response by the network2725.5.7.5Sequencing of subsequent start DTMF requests by the mobile station2726Support for packet services2736.1GPRS Session management2736.1.1General2736.1.2Session management states2746.1.2.1Session management states in the MS2746.1.2.1.1PDP-INACTIVE2746.1.2.1.2PDP-ACTIVE-PENDING2746.1.2.1.3PDP-INACTIVE-PENDING2746.1.2.1.4PDP-ACTIVE2746.1.2.1.5PDP-MODIFY_PENDING2746.1.2.1.6MBMS-ACTIVE-PENDING2746.1.2.1.7MBMS-ACTIVE2746.1.2.2Session management states on the network side2766.1.2.2.1PDP-INACTIVE2766.1.2.2.2PDP-ACTIVE-PENDING2766.1.2.2.3PDP-INACTIVE-PENDING2766.1.2.2.4PDP-ACTIVE2766.1.2.2.5PDP-MODIFY-PENDING2766.1.2.2.6MBMS-ACTIVE-PENDING2776.1.2.2.7MBMS-INACTIVE-PENDING2776.1.2.2.8MBMS-ACTIVE2776.1.2APDP address allocation2786.1.2A.1General2786.1.2A.1.1Interworking with PDN based on IP2786.1.2A.1.2Interworking with PDN based on PPP2786.1.2A.2IP address allocation via NAS signalling2796.1.3Session Management procedures2796.1.3.0General2796.1.3.1PDP context activation2796.1.3.1.1Successful PDP context activation initiated by the mobile station2806.1.3.1.2Successful PDP context activation requested by the network2826.1.3.1.3Unsuccessful PDP context activation initiated by the MS2836.1.3.1.3AVoid2856.1.3.1.4Unsuccessful PDP context activation requested by the network2856.1.3.1.5Abnormal cases2856.1.3.1.6Handling Activate PDP context request for MS configured for dual priority2886.1.3.2Secondary PDP Context Activation Procedure2886.1.3.2.1Successful Secondary PDP Context Activation Procedure Initiated by the MS2896.1.3.2.1aSuccessful Secondary PDP Context Activation Procedure Requested by the network2896.1.3.2.2Unsuccessful Secondary PDP Context Activation Procedure initiated by the MS2906.1.3.2.2aUnsuccessful secondary PDP context activation requested by the network2916.1.3.2.3Abnormal cases2926.1.3.3PDP context modification procedure2946.1.3.3.1Network initiated PDP Context Modification2956.1.3.3.2MS initiated PDP Context Modification accepted by the network2966.1.3.3.3MS initiated PDP Context Modification not accepted by the network2966.1.3.3.3aNetwork initiated PDP Context Modification not accepted by the MS2996.1.3.3.4Abnormal cases3006.1.3.4PDP context deactivation procedure3016.1.3.4.1PDP context deactivation initiated by the MS3016.1.3.4.2PDP context deactivation initiated by the network3026.1.3.4.3Abnormal cases3036.1.3.4aVoid3046.1.3.5Void3046.1.3.5aNotification procedure3046.1.3.5a.1General3046.1.3.5a.2Notification procedure initiation by the network3046.1.3.5a.3Notification procedure in the MS3056.1.3.6Receiving a SM STATUS message by a SM entity3056.1.3.7Protocol configuration options3066.1.3.8MBMS context activation3066.1.3.8.1Successful MBMS context activation3066.1.3.8.2Unsuccessful MBMS context activation requested by the MS3076.1.3.8.3Unsuccessful MBMS context activation requested by the network3086.1.3.8.4Abnormal cases3086.1.3.9MBMS context deactivation3096.1.3.9.1MBMS context deactivation initiated by the network3096.1.3.9.2Abnormal cases3096.1.3.10MBMS protocol configuration options3106.1.3.11Handling of APN based congestion control3106.1.3.12Handling session management request for MS configured for dual priority3106.2void3116.3Coordination between SM and GMM for supporting ISR3116.4MSISDN notification procedure3117Examples of structured procedures3118Handling of unknown, unforeseen, and erroneous protocol data3118.1General3118.2Message too short3128.3Unknown or unforeseen transaction identifier3128.3.1Call Control3128.3.2Session Management3138.4Unknown or unforeseen message type3148.5Non-semantical mandatory information element errors3148.5.1Radio resource management3158.5.2Mobility management3158.5.3Call control3158.5.4GMM mobility management3158.5.5Session management3158.6Unknown and unforeseen IEs in the non-imperative message part3168.6.1IEIs unknown in the message3168.6.2Out of sequence IEs3168.6.3Repeated IEs3168.7Non-imperative message part errors3168.7.1Syntactically incorrect optional IEs3178.7.2Conditional IE errors3178.8Messages with semantically incorrect contents3179Message functional definitions and contents3179.1Messages for Radio Resources management3189.2Messages for mobility management3189.2.1Authentication reject3199.2.2Authentication request3209.2.2.1Authentication Parameter AUTN3209.2.3Authentication response3209.2.3.1Authentication Response Parameter3219.2.3.2Authentication Response Parameter (extension)3219.2.3aAuthentication Failure3219.2.3a.1Authentication Failure parameter3219.2.4CM Re-establishment request3229.2.4.1Location area identification3229.2.4.2Mobile Station Classmark3229.2.4.3Device properties3229.2.5CM service accept3229.2.5aCM service prompt $(CCBS)$3239.2.6CM service reject3239.2.6.1T3246 value3249.2.7CM service abort3249.2.8Abort3249.2.9CM service request3259.2.9.1Mobile Station Classmark3259.2.9.2Priority3259.2.9.3Additional update parameters3259.2.9.4Device properties3259.2.10Identity request3269.2.11Identity response3269.2.12IMSI detach indication3269.2.12.1Mobile Station Classmark3279.2.13Location updating accept3279.2.13.1Follow on proceed3279.2.13.2CTS permission3289.2.13.3Equivalent PLMNs3289.2.13.4Emergency Number List3289.2.13.5Per MS T32123289.2.14Location updating reject3289.2.14.1T3246 value3289.2.15Location updating request3289.2.15.1Location area identification3299.2.15.2Mobile Station Classmark3299.2.15.3Mobile Station Classmark for Iu mode3299.2.15.4Additional update parameters3299.2.15.5Device properties3299.2.15.6MS network feature support3299.2.15aMM information3309.2.15a.1Full name for network3309.2.15a.2Short name for network3309.2.15a.3Local time zone3309.2.15a.4Universal time and local time zone3309.2.15a.5LSA Identity3319.2.15a.6Network Daylight Saving Time3319.2.16MM Status3319.2.17TMSI reallocation command3319.2.18TMSI reallocation complete3329.2.19MM Null3329.3Messages for circuit-switched call control3339.3.1Alerting3339.3.1.1Alerting (network to mobile station direction)3339.3.1.1.1Facility3349.3.1.1.2Progress indicator3349.3.1.1.3User-user3349.3.1.2Alerting (mobile station to network direction)3349.3.1.2.1Facility3359.3.1.2.2User-user3359.3.1.2.3SS version3359.3.2Call confirmed3359.3.2.1Repeat indicator3369.3.2.2Bearer capability 1 and bearer capability 23369.3.2.3Cause3379.3.2.4CC Capabilities3379.3.2.5Stream Identifier3379.3.2.6Supported Codecs3379.3.3Call proceeding3379.3.3.1Repeat indicator3379.3.3.2Bearer capability 1 and bearer capability 23389.3.3.3Facility3389.3.3.4Progress Indicator3389.3.3.5Priority granted3389.3.3.6Network Call Control Capabilities3389.3.4Congestion control3389.3.4.1Cause3399.3.5Connect3399.3.5.1Connect (network to mobile station direction)3399.3.5.1.1Facility3399.3.5.1.2Progress indicator3399.3.5.1.3User-user3399.3.5.2Connect (mobile station to network direction)3399.3.5.2.1Facility3409.3.5.2.2User-user3409.3.5.2.3SS version3409.3.5.2.4Stream Identifier3409.3.6Connect acknowledge3409.3.7Disconnect3419.3.7.1Disconnect (network to mobile station direction)3419.3.7.1.1Facility3419.3.7.1.2Progress indicator3419.3.7.1.3User-user3419.3.7.1.4Allowed actions $(CCBS)$3419.3.7.2Disconnect (mobile station to network direction)3429.3.7.2.1Facility3429.3.7.2.2User-user3429.3.7.2.3SS version3429.3.8Emergency setup3429.3.8.1Bearer capability3439.3.8.2Stream Identifier3439.3.8.3Supported Codecs3439.3.8.4Emergency category3439.3.9Facility3439.3.9.1Facility (network to mobile station direction)3439.3.9.2Facility (mobile station to network direction)3449.3.9.2.1SS version3449.3.10Hold3459.3.11Hold Acknowledge3459.3.12Hold Reject3459.3.13Modify3469.3.13.1Low layer compatibility3469.3.13.2High layer compatibility3469.3.13.3Reverse call setup direction3469.3.13.4Void3479.3.13.5Network-initiated Service Upgrade indicator3479.3.14Modify complete3479.3.14.1Low layer compatibility3479.3.14.2High layer compatibility3479.3.14.3Reverse call setup direction3479.3.15Modify reject3479.3.15.1Low layer compatibility3489.3.15.2High layer compatibility3489.3.16Notify3489.3.17Progress3489.3.17.1User-user3499.3.17.2Progress indicator3499.3.17aCC-Establishment $(CCBS)$3499.3.17a.1Void3509.3.17a.2Setup container3509.3.17bCC-Establishment confirmed $(CCBS)$3509.3.17b.1Repeat indicator3509.3.17b.2Bearer capability 1 and bearer capability 23519.3.17b.3Cause3519.3.17b.4Supported Codecs3519.3.18Release3519.3.18.1Release (network to mobile station direction)3519.3.18.1.1Cause3519.3.18.1.2Second cause3519.3.18.1.3Facility3529.3.18.1.4User-user3529.3.18.2Release (mobile station to network direction)3529.3.18.2.1Cause3529.3.18.2.2Second cause3529.3.18.2.3Facility3529.3.18.2.4User-user3539.3.18.2.5SS version3539.3.18aRecall $(CCBS)$3539.3.18a.1Recall Type3539.3.18a.2Facility3539.3.19Release complete3539.3.19.1Release complete (network to mobile station direction)3539.3.19.1.1Cause3549.3.19.1.2Facility3549.3.19.1.3User-user3549.3.19.2Release complete (mobile station to network direction)3549.3.19.2.1Cause3559.3.19.2.2Facility3559.3.19.2.3User-user3559.3.19.2.4SS version.3559.3.20Retrieve3559.3.21Retrieve Acknowledge3569.3.22Retrieve Reject3569.3.23Setup3579.3.23.1Setup (mobile terminated call establishment)3579.3.23.1.1BC repeat indicator3589.3.23.1.2Bearer capability 1 and bearer capability 23599.3.23.1.3Facility3599.3.23.1.4Progress indicator3599.3.23.1.4aCalled party BCD number3599.3.23.1.5Called party subaddress3599.3.23.1.6LLC repeat indicator3599.3.23.1.7Low layer compatibility I3599.3.23.1.8Low layer compatibility II3599.3.23.1.9HLC repeat indicator3599.3.23.1.10High layer compatibility i3599.3.23.1.11High layer compatibility ii3609.3.23.1.12User-user3609.3.23.1.13Redirecting party BCD number3609.3.23.1.14Redirecting party subaddress3609.3.23.1.15Priority3609.3.23.1.16Alert $(Network Indication of Alerting in the MS)$3609.3.23.1.17Network Call Control Capabilities3609.3.23.1.18Cause of No CLI3609.3.23.1.19Backup bearer capability3609.3.23.2Setup (mobile originating call establishment)3609.3.23.2.1BC repeat indicator3619.3.23.2.2Facility3629.3.23.2.3LLC repeat indicator3629.3.23.2.4Low layer compatibility I3629.3.23.2.5Low layer compatibility II3629.3.23.2.6HLC repeat indicator3629.3.23.2.7High layer compatibility i3629.3.23.2.8High layer compatibility ii3629.3.23.2.9User-user3629.3.23.2.10SS version3629.3.23.2.11CLIR suppression3629.3.23.2.12CLIR invocation3639.3.23.2.13CC Capabilities3639.3.23.2.14Stream Identifier3639.3.23.2.15Bearer capability 1 and bearer capability 23639.3.23.2.16Supported Codecs3639.3.23.2.17Redial3639.3.23aStart CC $(CCBS)$3639.3.23a.1CC Capabilities3639.3.24Start DTMF3649.3.25Start DTMF Acknowledge3649.3.25.1Keypad facility3649.3.26Start DTMF reject3649.3.27Status3659.3.27.1Auxiliary states3659.3.28Status enquiry3659.3.29Stop DTMF3669.3.30Stop DTMF acknowledge3669.3.31User information3679.3.31.1User-user3679.3.31.2More data3679.4GPRS Mobility Management Messages3679.4.1Attach request3679.4.1.1Old P-TMSI signature3689.4.1.2Requested READY timer value3699.4.1.3TMSI status3699.4.1.4PS LCS Capability3699.4.1.5UE network capability3699.4.1.6Mobile station classmark 23699.4.1.7Mobile station classmark 33699.4.1.8Supported Codecs3699.4.1.9Additional mobile identity3699.4.1.10Additional old routing area identification3699.4.1.11Voice domain preference and UE's usage setting3699.4.1.12Device properties3699.4.1.13P-TMSI type3699.4.1.14MS network feature support3709.4.1.15Old location area identification3709.4.1.16Additional update type3709.4.1.17TMSI based NRI container3709.4.2Attach accept3709.4.2.1P-TMSI signature3719.4.2.2Negotiated READY timer value3719.4.2.3Allocated P-TMSI3719.4.2.4MS identity3729.4.2.5GMM cause3729.4.2.6T3302 value3729.4.2.7Cell Notification (A/Gb mode only)3729.4.2.8Equivalent PLMNs3729.4.2.9Network feature support3729.4.2.10Emergency Number List3729.4.2.11Requested MS Information3729.4.2.12T3319 value3729.4.2.13T3323 value3729.4.2.14T3312 extended value3729.4.2.15Additional network feature support3729.4.3Attach complete3729.4.3.1Inter RAT handover information3739.4.3.2E-UTRAN inter RAT handover information3739.4.4Attach reject3739.4.4.1T3302 value3749.4.4.2T3346 value3749.4.5Detach request3749.4.5.1Detach request (mobile terminated detach)3749.4.5.1.1GMM cause3749.4.5.2Detach request (mobile originating detach)3749.4.5.2.1P-TMSI3759.4.5.2.2P-TMSI signature3759.4.6Detach accept3759.4.6.1Detach accept (mobile terminated detach)3759.4.6.2Detach accept (mobile originating detach)3759.4.7P-TMSI reallocation command3769.4.7.1P-TMSI signature3769.4.8P-TMSI reallocation complete3769.4.9Authentication and ciphering request3779.4.9.1Authentication Parameter RAND3779.4.9.2GPRS ciphering key sequence number3779.4.9.3Authentication Parameter AUTN3779.4.10Authentication and ciphering response3789.4.10.1Authentication Response Parameter3789.4.10.2IMEISV3789.4.10.3Authentication Response Parameter (extension)3789.4.10aAuthentication and Ciphering Failure3789.4.10a.1Authentication Failure parameter3799.4.11Authentication and ciphering reject3799.4.12Identity request3799.4.13Identity response3809.4.14Routing area update request3809.4.14.1Old P-TMSI signature3829.4.14.2Requested READY timer value3829.4.14.3DRX parameter3829.4.14.4TMSI status3829.4.14.5P-TMSI (Iu mode only)3829.4.14.6MS network capability3829.4.14.7PDP context status3829.4.14.8PS LCS Capability3829.4.14.9MBMS context status3829.4.14.10Additional mobile identity3829.4.14.11Additional old routing area identification3829.4.14.12UE network capability3829.4.14.13Mobile station classmark 23829.4.14.14Mobile station classmark 33829.4.14.15Supported Codecs3839.4.14.16Voice domain preference and UE's usage setting3839.4.14.17P-TMSI type3839.4.14.18Device properties3839.4.14.19MS network feature support3839.4.14.20Old location area identification3839.4.14.21Additional update type3839.4.14.22TMSI based NRI container3839.4.15Routing area update accept3839.4.15.1P-TMSI signature3849.4.15.2Allocated P-TMSI3849.4.15.3MS identity3859.4.15.4List of Receive NPDU Numbers3859.4.15.5Negotiated READY timer value3859.4.15.6GMM cause3859.4.15.7T3302 value3859.4.15.8Cell Notification (A/Gb mode only)3859.4.15.9Equivalent PLMNs3859.4.15.10PDP context status3859.4.15.11Network feature support3859.4.15.12Emergency Number List3859.4.15.13MBMS context status3869.4.15.14Requested MS Information3869.4.15.15T3319 value3869.4.15.16T3323 value3869.4.15.17T3312 extended value3869.4.15.18Additional network feature support3869.4.16Routing area update complete3869.4.16.1List of Receive NPDU Numbers3879.4.16.2Inter RAT handover information3879.4.16.3E-UTRAN inter RAT handover information3879.4.17Routing area update reject3879.4.17.1T3302 value3889.4.17.2T3346 value3889.4.18GMM Status3889.4.19GMM Information3889.4.19.1Full name for network3899.4.19.2Short name for network3899.4.19.3Local time zone3899.4.19.4Universal time and local time zone3899.4.19.5LSA Identity3899.4.19.6Network Daylight Saving Time3899.4.20Service Request (Iu mode only)3909.4.20.1PDP context status3909.4.20.2MBMS context status3909.4.20.3Uplink data status3909.4.20.4Device properties3909.4.21Service Accept (Iu mode only)3909.4.21.1PDP context status3919.4.21.2MBMS context status3919.4.22Service Reject (Iu mode only)3919.4.22.1T3346 value3919.5GPRS Session Management Messages3919.5.1Activate PDP context request3919.5.1.1Access point name3929.5.1.2Protocol configuration options3929.5.1.3Request type3929.5.1.4Device properties3929.5.2Activate PDP context accept3929.5.2.1PDP address3939.5.2.2Protocol configuration options3939.5.2.3Packet Flow Identifier3939.5.2.4SM cause3939.5.2.5Connectivity type3939.5.3Activate PDP context reject3949.5.3.1Protocol configuration options3949.5.3.2T3396 value3949.5.4Activate Secondary PDP Context Request3949.5.4.1TFT3959.5.4.2Protocol configuration options3959.5.4.3Device properties3959.5.5Activate Secondary PDP Context Accept3959.5.5.1Packet Flow Identifier3969.5.5.2Protocol configuration options3969.5.6Activate Secondary PDP Context Reject3969.5.6.1Protocol configuration options3969.5.6.2T3396 value3969.5.7Request PDP context activation3969.5.7.1Protocol configuration options3979.5.8Request PDP context activation reject3979.5.8.1Protocol configuration options3979.5.9Modify PDP context request (Network to MS direction)3979.5.9.1PDP address3989.5.9.2Packet Flow Identifier3989.5.9.3Protocol configuration options3989.5.9.4TFT3989.5.10Modify PDP context request (MS to network direction)3989.5.10.1Requested LLC SAPI3999.5.10.2Requested new QoS3999.5.10.3New TFT3999.5.10.4Protocol configuration options3999.5.10.5Device properties3999.5.11Modify PDP context accept (MS to network direction)3999.5.11.1Protocol configuration options4009.5.12Modify PDP context accept (Network to MS direction)4009.5.12.1Negotiated QoS4009.5.12.2Negotiated LLC SAPI4009.5.12.3New radio priority4009.5.12.4Packet Flow Identifier4019.5.12.5Protocol configuration options4019.5.13Modify PDP Context Reject4019.5.13.1Protocol configuration options4019.5.13.2T3396 value4019.5.14Deactivate PDP context request4019.5.14.1Tear down indicator4029.5.14.2Protocol configuration options4029.5.14.3MBMS protocol configuration options4029.5.14.4T3396 value4029.5.15Deactivate PDP context accept4029.5.15.1Protocol configuration options4039.5.15.2MBMS protocol configuration options4039.5.15aRequest Secondary PDP Context Activation4039.5.15.1aTFT4049.5.15.2aProtocol configuration options4049.5.15bRequest Secondary PDP Context Activation Reject4049.5.15.1bProtocol configuration options4049.5.16Void4049.5.16aNotification4049.5.17Void4059.5.18Void4059.5.19Void4059.5.20Void4059.5.21SM Status4059.5.22Activate MBMS Context Request4059.5.22.1MBMS protocol configuration options4069.5.22.2Device properties4069.5.23Activate MBMS Context Accept4069.5.23.1MBMS protocol configuration options4079.5.24Activate MBMS Context Reject4079.5.24.1MBMS protocol configuration options4079.5.24.2T3396 value4079.5.25Request MBMS Context Activation4079.5.25.1Linked NSAPI4089.5.25.2MBMS protocol configuration options4089.5.26Request MBMS Context Activation Reject4089.5.26.1MBMS protocol configuration options40810General message format and information elements coding40910.1Overview40910.2Protocol Discriminator40910.3Skip indicator and transaction identifier40910.3.1Skip indicator40910.3.2Transaction identifier41110.4Message Type41110.5Other information elements41410.5.1Common information elements.41510.5.1.1Cell identity41510.5.1.2Ciphering Key Sequence Number41610.5.1.3Location Area Identification41610.5.1.4Mobile Identity41810.5.1.5Mobile Station Classmark 142210.5.1.6Mobile Station Classmark 242410.5.1.7Mobile Station Classmark 342710.5.1.8Spare Half Octet44010.5.1.9Descriptive group or broadcast call reference44010.5.1.10Group Cipher Key Number44110.5.1.10aPD and SAPI $(CCBS)$44210.5.1.11Priority Level44310.5.1.12Core Network System Information (Iu mode only)44310.5.1.12.1CN Common GSM-MAP NAS system information44310.5.1.12.2CS domain specific system information44410.5.1.12.3PS domain specific system information44410.5.1.13PLMN list44510.5.1.14NAS container for PS HO44610.5.1.15MS network feature support44710.5.2Radio Resource management information elements.44810.5.3Mobility management information elements.44810.5.3.1Authentication parameter RAND44810.5.3.1.1Authentication Parameter AUTN (UMTS and EPS authentication challenge)44810.5.3.2Authentication Response parameter44910.5.3.2.1Authentication Response Parameter (extension) (UMTS authentication challenge only)45010.5.3.2.2Authentication Failure parameter (UMTS and EPS authentication challenge)45010.5.3.3CM service type45110.5.3.4Identity type45110.5.3.5Location updating type45210.5.3.5aNetwork Name45210.5.3.6Reject cause45410.5.3.7Follow-on Proceed45510.5.3.8Time Zone45510.5.3.9Time Zone and Time45610.5.3.10CTS permission45710.5.3.11LSA Identifier45810.5.3.12Daylight Saving Time45810.5.3.13Emergency Number List45910.5.3.14Additional update parameters46010.5.3.15Void46010.5.3.16MM Timer46010.5.4Call control information elements46110.5.4.1Extensions of codesets46110.5.4.2Locking shift procedure46210.5.4.3Non-locking shift procedure46210.5.4.4Auxiliary states46310.5.4.4aBackup bearer capability46410.5.4.4a.1Static conditions for the backup bearer capability IE contents47310.5.4.5Bearer capability47310.5.4.5.1Static conditions for the bearer capability IE contents48810.5.4.5aCall Control Capabilities48810.5.4.6Call state48910.5.4.7Called party BCD number49010.5.4.8Called party subaddress49210.5.4.9Calling party BCD number49310.5.4.10Calling party subaddress49410.5.4.11Cause49510.5.4.11aCLIR suppression50010.5.4.11bCLIR invocation50110.5.4.12Congestion level50110.5.4.13Connected number50110.5.4.14Connected subaddress50210.5.4.15Facility50210.5.4.16High layer compatibility50310.5.4.16.1Static conditions for the high layer compatibility IE contents50410.5.4.17Keypad facility50410.5.4.18Low layer compatibility50410.5.4.19More data50410.5.4.20Notification indicator50510.5.4.21Progress indicator50510.5.4.21aRecall type $(CCBS)$50610.5.4.21bRedirecting party BCD number50710.5.4.21cRedirecting party subaddress50710.5.4.22Repeat indicator50810.5.4.22aReverse call setup direction50810.5.4.22bSETUP Container $(CCBS)$50910.5.4.23Signal50910.5.4.24SS Version Indicator51010.5.4.25User-user51010.5.4.26Alerting Pattern $(NIA)$51110.5.4.27Allowed actions $(CCBS)$51210.5.4.28Stream Identifier51310.5.4.29Network Call Control Capabilities51310.5.4.30Cause of No CLI51410.5.4.31Void51410.5.4.32Supported codec list51410.5.4.33Service category51510.5.4.34Redial51610.5.4.35Network-initiated Service Upgrade indicator51610.5.5GPRS mobility management information elements51710.5.5.0Additional update type51710.5.5.1Attach result51710.5.5.2Attach type51710.5.5.3Ciphering algorithm51810.5.5.4TMSI status51910.5.5.5Detach type51910.5.5.6DRX parameter52010.5.5.7Force to standby52210.5.5.8P-TMSI signature52210.5.5.8aP-TMSI signature 252310.5.5.9Identity type 252310.5.5.10IMEISV request52410.5.5.11Receive NPDU Numbers list52410.5.5.12MS network capability52510.5.5.12aMS Radio Access capability52910.5.5.13Spare54210.5.5.14GMM cause54210.5.5.15Routing area identification54310.5.5.15aRouting area identification 254510.5.5.16Spare54510.5.5.17Update result54510.5.5.18Update type54610.5.5.19A&C reference number54710.5.5.20Service type54710.5.5.21Cell Notification54810.5.5.22PS LCS Capability54810.5.5.23Network feature support54910.5.5.23AAdditional network feature support55010.5.5.24Inter RAT information container55110.5.5.25Requested MS information55110.5.5.26UE network capability55210.5.5.27E-UTRAN inter RAT information container55210.5.5.28Voice domain preference and UE's usage setting55210.5.5.29P-TMSI type55310.5.5.30Location Area Identification 255410.5.5.31Network resource identifier container55410.5.6Session management information elements55510.5.6.1Access point name55510.5.6.2Network service access point identifier55510.5.6.3Protocol configuration options55610.5.6.4Packet data protocol address56310.5.6.5Quality of service56410.5.6.6SM cause57410.5.6.6ASM cause 257510.5.6.7Linked TI57610.5.6.8Spare57610.5.6.9LLC service access point identifier57610.5.6.10Tear down indicator57710.5.6.11Packet Flow Identifier57710.5.6.12Traffic Flow Template57810.5.6.13Temporary Mobile Group Identity (TMGI)58410.5.6.14MBMS bearer capabilities58410.5.6.15MBMS protocol configuration options58510.5.6.16Enhanced network service access point identifier58610.5.6.17Request type58610.5.6.18Notification indicator58710.5.6.19Connectivity type58710.5.7GPRS Common information elements58810.5.7.1PDP context status58810.5.7.2Radio priority58910.5.7.3GPRS Timer58910.5.7.4GPRS Timer 259010.5.7.4aGPRS Timer 359010.5.7.5Radio priority 259110.5.7.6MBMS context status59110.5.7.7Uplink data status59210.5.7.8Device properties59311List of system parameters59411.1Timers and counters for radio resource management59411.2Timers of mobility management59411.2.1Timer T3240 and Timer T324159611.2.2Timers of GPRS mobility management59811.2.3Timers of GPRS session management60511.3Timers of circuit-switched call control607Annex A (informative):Example of subaddress information element coding609Annex B (normative):Compatibility checking610B.1Introduction610B.2Calling side compatibility checking610B.2.1Compatibility checking of the CM SERVICE REQUEST message610B.2.2Compatibility/Subscription checking of the SETUP message610B.3Called side compatibility checking610B.3.1Compatibility checking with addressing information611B.3.2Network-to-MS compatibility checking611B.3.3User-to-User compatibility checking611B.4High layer compatibility checking611Annex C (normative):Low layer information coding principles612C.1Purpose612C.2Principles612C.2.1Definition of types of information612C.2.2Examination by network612C.2.3Location of type I information613C.2.4Location of types II and III information613C.2.5Relationship between bearer capability and low layer compatibility information elements613Annex D (informative):Examples of bearer capability information element coding614D.1Coding for speech for a full rate support only mobile station614D.1.1Mobile station to network direction614D.1.2Network to mobile station direction614D.2An example of a coding for modem access with V22-bis, 2,4 kbit/s, 8 bit no parity615D.2.1Mobile station to network direction, data compression allowed615D.2.2Network to mobile station direction, data compression possible616D.3An example of a coding for group 3 facsimile (9,6 kbit/s, transparent)617D.3.1Mobile station to network direction617D.3.2Network to mobile station direction618Annex E (informative):Comparison between call control procedures specified in 3GPP TS 24.008 and ITU-T Recommendation Q.931619Annex F (informative):A/Gb modespecific cause values for radio resource management623Annex G (informative):3GPP specific cause values for mobility management624G.1Causes related to MS identification624G.2Cause related to subscription options624G.3Causes related to PLMN specific network failures and congestion/Authentication Failures625G.4Causes related to nature of request625G.5Causes related to invalid messages626G.6Additional cause codes for GMM626Annex H (informative):3GPP specific cause values for call control628H.1Normal class628H.1.1Cause No. 1 "unassigned (unallocated) number"628H.1.2Cause No. 3 "no route to destination"628H.1.3Cause No. 6 "channel unacceptable"628H.1.4Cause No. 8 "operator determined barring"628H.1.5Cause No.16 "normal call clearing"628H.1.6Cause No.17 "user busy"628H.1.7Cause No. 18 "no user responding"628H.1.8Cause No. 19 "user alerting, no answer"628H.1.9Cause No. 21 "call rejected"629H.1.10Cause No. 22 "number changed"629H.1.10a Cause No. 24 "call rejected due to feature at the destination"629H.1.11Cause No. 25 "pre-emption"629H.1.12Cause No. 26 "non-selected user clearing"629H.1.13Cause No. 27 "destination out of order"629H.1.14Cause No. 28 "invalid number format (incomplete number)"629H.1.15Cause No. 29 "facility rejected"629H.1.16Cause No. 30 "response to STATUS ENQUIRY"629H.1.17Cause No. 31 "normal, unspecified"629H.2Resource unavailable class630H.2.1Cause No. 34 "no circuit/channel available"630H.2.2Cause No. 38 "network out of order"630H.2.3Cause No. 41 "temporary failure"630H.2.4Cause No. 42 "switching equipment congestion"630H.2.5Cause No. 43 "access information discarded"630H.2.6Cause No. 44 "requested circuit/channel not available"630H.2.7Cause No. 47 "resource unavailable, unspecified"630H.3Service or option not available class630H.3.1Cause No. 49 "quality of service unavailable"630H.3.2Cause No. 50 "Requested facility not subscribed"630H.3.3Cause No. 55 "Incoming calls barred within the CUG"631H.3.4Cause No. 57 "bearer capability not authorized"631H.3.5Cause No. 58 "bearer capability not presently available"631H.3.6Cause No. 63 "service or option not available, unspecified"631H.3.7Cause No. 68 "ACM equal to or greater than ACMmax"631H.4Service or option not implemented class631H.4.1Cause No. 65 "bearer service not implemented"631H.4.2Cause No. 69 "Requested facility not implemented"631H.4.3Cause No. 70 "only restricted digital information bearer capability is available"631H.4.4Cause No. 79 "service or option not implemented, unspecified"631H.5Invalid message (e.g., parameter out of range) class632H.5.1Cause No. 81 "invalid transaction identifier value"632H.5.2Cause No. 87 "user not member of CUG"632H.5.3Cause No. 88 "incompatible destination"632H.5.4Cause No. 91 "invalid transit network selection"632H.5.5Cause No. 95 "semantically incorrect message"632H.6Protocol error (e.g., unknown message) class632H.6.1Cause No. 96 "invalid mandatory information"632H.6.2Cause No. 97 "message type non-existent or not implemented"632H.6.3Cause No. 98 "message type not compatible with protocol state"632H.6.4Cause No. 99 "information element non-existent or not implemented"633H.6.5Cause No. 100 "conditional IE error"633H.6.6Cause No. 101 "message not compatible with protocol state"633H.6.7Cause No. 102 "recovery on timer expiry"633H.6.8Cause No. 111 "protocol error, unspecified"633H.7Interworking class633H.7.1Cause No. 127 "interworking, unspecified"633Annex I (informative):GPRSspecific cause values for GPRS Session Management634I.1Causes related to nature of request634I.2Causes related to invalid messages636Annex J (informative):Algorithm to encode frequency list information elements638Annex K (informative):Default Codings of Information Elements639K.1Common information elements.639K.2Radio Resource management information elements.639K.3Mobility management information elements.639K.4Call control information elements.640Annex L (normative):Establishment cause (Iu mode only)642L.1Mapping of NAS procedure to RRC establishment cause(Iu mode only)642Annex M (normative):Additional Requirements for backward compatibility with PCS 1900 for NA revision 0 ME645Annex N (normative):Ranking of reject causes for Location Registration (MM and GMM) in a shared network645Annex O (normative):3GPP capability exchange protocol646O.1Scope646O.2User-user protocol contents647O.3Information element identifier647O.4Information elements648O.4.1Personal ME identifier648O.4.2Radio environment capability649O.4.3UE capability version649O.4.4IM Status650O.5Handling of unknown, unforeseen, and erroneous protocol data651O.5.1General651O.5.2Not supported IEs, unknown IEIs651O.5.3Repeated IEs651O.5.4Syntactically incorrect IEs652O.5.5Semantically incorrect IEs652Annex P (normative):Mobility management for IMS voice termination653P.1Introduction653P.2Activation of mobility management for IMS voice termination653P.3Inter-system change between A/Gb mode and Iumode653P.4Inter-system change between A/Gb mode and S1mode654P.5Inter-system change between Iu mode and S1 mode654Annex Q (informative):Change History655

Foreword

This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:

Version x.y.z

where:

xthe first digit:

1presented to TSG for information;

2presented to TSG for approval;

3or greater indicates TSG approved document under change control.

ythe second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.

zthe third digit is incremented when editorial only changes have been incorporated in the document.

Introduction

The present document includes references to features which are not part of the Phase2+ Release96 of the GSM Technical specifications. All subclauses which were changed as a result of these features contain a marker (see table below) relevant to the particular feature.

The following table lists all features that were introduced after GSM Release96.

FeatureDesignator

BA Range IE handling$(impr-BA-range-handling)$

Advanced Speech Call Item$(ASCI)$

Call Completion Busy Subscriber$(CCBS)$

Mobile Assisted Frequency Allocation$(MAFA)$

Network Indication of Alerting in MS$(NIA)$

1Scope

The present document specifies the procedures used at the radio interface core network protocols within the 3rd generation mobile telecommunications system and the digital cellular telecommunications system.

It specifies the procedures used at the radio interface (Reference Point Um or Uu, see 3GPPTS24.002[15] or 3GPPTS23.002[127]) for Call Control (CC), Mobility Management (MM), and Session Management (SM).

When the notations for "further study" or "FS" or "FFS" are present in this TS they mean that the indicated text is not a normative portion of the present document.

These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in 3GPPTS44.003[16] and 3GPPTS25.301[128].

The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPPTS24.007[20].

1.1Scope of the Technical Specification

The procedures currently described in this TS are for the call control of circuit-switched connections, session management for GPRS services, mobility management and radio resource management for circuit-switched and GPRS services.

3GPPTS24.010[21] contains functional procedures for support of supplementary services.

3GPPTS24.011[22] contains functional procedures for support of point-to-point short message services.

3GPPTS24.012[23] contains functional description of short message - cell broadcast.

3GPPTS44.060[76] contains procedures for radio link control and medium access control (RLC/MAC) of packet data physical channels.

3GPPTS44.071[23a] contains functional descriptions and procedures for support of location services.

NOTE:"layer3" includes the functions and protocols described in the present document. The terms "data link layer" and "layer2" are used interchangeably to refer to the layer immediately below layer3.

1.2Application to the interface structures

The procedures defined in the present document apply to the interface structures defined in 3GPPTS44.003[16] and 3GPPTS25.301[128]. They use the functions and services provided by lower layers defined in 3GPPTS44.005[18] and 3GPPTS44.006[19] or 3GPP TS25.331[23c], 3GPPTS25.322[19b] and 3GPPTS25.321[19a]. 3GPPTS24.007[20] gives the general description of layer3 (A/Gb mode) and Non Access Stratum (Iu mode and S1 mode) including procedures, messages format and error handling.

1.3Structure of layer 3 procedures

A building block method is used to describe the layer3 procedures.

The basic building blocks are "elementary procedures" provided by the protocol control entities of the three sublayers, i.e. radio resource management, mobility management and connection management sublayer.

Complete layer3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences.

1.4Test procedures

Test procedures of the GSMradio interface signalling are described in 3GPPTS51.010[39] and 3GPPTS51.02xseries.

1.5Use of logical channels in A/Gb mode

The logical control channels are defined in 3GPPTS45.002[32]. In the following those control channels are considered which carry signalling information or specific types of user packet information:

i)Broadcast Control CHannel (BCCH): downlink only, used to broadcast Cell specific information;

ii)Synchronization CHannel (SCH): downlink only, used to broadcast synchronization and BSS identification information;

iii)Paging CHannel (PCH): downlink only, used to send page requests to Mobile Stations (MSs);

iv)Random Access CHannel (RACH): uplink only, used to request a Dedicated Control CHannel;

v)Access Grant CHannel (AGCH): downlink only, used to allocate a Dedicated Control CHannel;

vi)Standalone Dedicated Control CHannel (SDCCH): bi-directional;

vii)Fast Associated Control CHannel (FACCH): bi-directional, associated with a Traffic CHannel;

viii)Slow Associated Control CHannel (SACCH): bi-directional, associated with a SDCCH or a Traffic CHannel;

ix)Cell Broadcast CHannel (CBCH): downlink only used for general (not point to point) short message information;

x)Notification CHannel (NCH): downlink only, used to notify mobile stations of VBS (Voice Broadcast Service) calls or VGCS (Voice Group Call Service) calls.

Two service access points are defined on signalling layer 2 which are discriminated by their Service Access Point Identifiers (SAPI) (see 3GPPTS44.006[19]):

i)SAPI 0: supports the transfer of signalling information including user-user information;

ii)SAPI 3: supports the transfer of user short messages.

Layer 3 selects the service access point, the logical control channel and the mode of operation of layer2 (acknowledged, unacknowledged or random access, see 3GPPTS44.005[18] and 3GPPTS44.006[19]) as required for each individual message.

1.6Overview of control procedures

1.6.1List of procedures

The following procedures are specified in the present document:

a)Clause 4 specifies elementary procedures for Mobility Management:

-mobility management common procedures (subclause4.3):

-TMSI reallocation procedure (subclause4.3.1);

-authentication procedure (subclause4.3.2);

-identification procedure (subclause4.3.3);

-IMSI detach procedure (subclause4.3.4);

-abort procedure (subclause4.3.5);

-MM information procedure (subclause4.3.6).

-mobility management specific procedures (subclause4.4):

-location updating procedure (subclause4.4.1);

-periodic updating (subclause4.4.2);

-IMSI attach procedure (subclause4.4.3);

-generic location updating procedure (subclause4.4).

-connection management sublayer service provision:

-mobility management connection establishment (subclause4.5.1);

-mobility management connection information transfer phase (subclause4.5.2);

-mobility management connection release (subclause4.5.3).

-GPRS specific mobility management procedures (subclause4.7):

-GPRS attach procedure (subclause4.7.3);

-GPRS detach procedure (subclause4.7.4);

-GPRS routing area updating procedure (subclause4.7.5).

-GPRS common mobility management procedures (subclause4.7):

-GPRS P-TMSI reallocation procedure (subclause4.7.6);

-GPRS authentication and ciphering procedure (subclause4.7.7);

-GPRS identification procedure (subclause4.7.8);

-GPRS information procedure (subclause4.7.12).

b)Clause 5 specifies elementary procedures for circuit switched Call Control comprising the following elementary procedures:

-mobile originating call establishment (subclause5.2.1);

-mobile terminating call establishment (subclause5.2.2);

-signalling procedures during the active state (subclause5.3):

-user notification procedure (subclause5.3.1);

-call rearrangements (subclause5.3.2);

-DTMF protocol control procedure (subclause5.5.7);

-in-call modification (subclause5.3.4).

-call clearing initiated by the mobile station (subclause5.4.3);

-call clearing initiated by the network (subclause5.4.4);

-miscellaneous procedures:

-in-band tones and announcements (subclause5.5.1);

-status enquiry procedure (subclause5.5.3);

-call re-establishment procedure (subclause5.5.4).

d)Clause 6 specifies elementary procedures for session management:

-GPRS session management procedures (subclause6.1):

-PDP context activation (subclauses6.1.3.1 and 6.1.3.2);

-PDP context modification (subclause6.1.3.3);

-PDP context deactivation (subclause6.1.3.4).

-MBMS context activation (subclause6.1.3.8);

-MBMS context deactivation (subclause6.1.3.9).

The elementary procedures can be combined to form structured procedures. Examples of such structured procedures are given in clause7. This part of the present document is only provided for guidance to assist implementations.

Clause8 specifies actions to be taken on various error conditions and also provides rules to ensure compatibility with future enhancements of the protocol.

1.7Applicability of implementations

The applicability of procedures of the present document for the mobile station is dependent on the services and functions which are to be supported by a mobile station.

1.7.1Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS)

Voice Group Call Service and Voice Broadcast Service are applicable in A/Gb mode only.

For mobile stations supporting the Voice Group Call Service or the Voice Broadcast Service, it is explicitly mentioned throughout the present document if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave.

For VGCS and VBS, the following possible mobile station implementations exist:

-support of listening to voice broadcast calls (VBS listening);

-support of originating a voice broadcast call (VBS originating);

-support of listening to voice group calls (VGCS listening);

-support of talking in voice group calls (VGCS talking. This always includes the implementation for VGCS listening);

-support of originating a voice group call (VGCS originating. This always includes the implementation for VGCS talking).

Apart from the explicitly mentioned combinations, all possible combinations are optional and supported by the present document.

The related terms are used in the present document, if information on these implementation options is required.

1.7.2General Packet Radio Service (GPRS)

1.7.2.1Packet services in GSM (A/Gb mode only)

For mobile stations supporting the General Packet Radio Service (GPRS), it is explicitly mentioned throughout the technical specification if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave.

A GPRS MS may operate in one of the following MS operation modes, see 3GPPTS23.060[74]:

-MS operation mode A;

-MS operation mode B; or

-MS operation mode C.

The MS operation mode depends on the services that the MS is attached to, i.e., only GPRS or both GPRS and non-GPRS services, and upon the MS's capabilities to operate GPRS and other GSM services simultaneously. Mobile stations that are capable to operate GPRS services are referred to as GPRS MSs.

NOTE: Other GSM technical specifications may refer to the MS operation modes A, B, and C as GPRS classA MS, GPRS classB MS, and GPRS classC MS.

It should be noted that it is possible that for a GPRS MS, the GMM procedures currently described in the ETS do not support combinations of VGCS, VBS and GPRS. The possible interactions are not studied yet.

1.7.2.2Packet services in Iu mode (Iu mode only)

An MS attached to packet switched domain may operate in one of the following MS operation modes, see 3GPPTS23.060[74]:

-PS/CS mode of operation; or

-PS mode of operation.

The terms 'PS/CS mode of operation' and 'PS mode of operation' are not used in the present document with some exceptions. Instead the terms 'MS operation mode A' and 'MS operation mode C' are used.

In network operation mode I and II (see 3GPPTS23.060[74]), an MS in PS/CS mode of operation shall use the sameprocedures as for a GPRS MS operating in MS operation mode A, unless it is explicitly stated for A/Gb mode only orIu mode only.

In network operation mode I and II, an MS in PS mode of operation shall use the same procedures as for a GPRS MS operating in MS operation mode C, unless it is explicitly stated for A/Gb mode only or Iu mode only.

1.8Handling of NAS signalling low priority indicationAn MS configured for NAS signalling low priority (see 3GPPTS24.368[135], 3GPPTS31.102[112]) indicates this by including the Device properties IE in the appropriate NAS message and setting the low priority indicator to "MS is configured to NAS signalling low priority" except for the following cases in which the MS shall set the low priority indicator to "MS is not configured for NAS signalling low priority":-the MS is performing an attach for emergency bearer services;

-the MS has a PDN connection for emergency bearer services established and is performing mobility management procedures, or is establishing a PDN connection for emergency bearer services;

-the MS configured for dual priority is requested by the upper layers to establish a PDN connection with the low priority indicator set to "MS is not configured for NAS signalling low priority";-the MS configured for dual priority is performing EPS session management procedures related to the PDN connection established with low priority indicator set to "MS is not configured for NAS signalling low priority";

-the MS configured for dual priority has a PDN connection established by setting the low priority indicator to "MS is not configured for NAS signalling low priority" and is performing EPS mobility management procedures;

-the MS is accessing the network with access class 11 15; or

-the MS is responding to paging.The network may use the NAS signalling low priority indication for NAS level mobility management congestion control on a per core network node basis and APN based congestion control.

If the NAS signalling low priority indication is provided in an ACTIVATE PDP CONTEXT REQUEST message, the SGSN stores the NAS signalling low priority indication within the default PDP context activated due to this request.1.9RestrictionsIndependently of what is stated elsewhere in this and other 3GPP specifications, mobile station support for PBCCH and PCCCH is optional for A/Gb-mode of operation. The network shall never enable PBCCH and PCCCH. This makes use of network operation mode III obsolete.2References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific.

For a specific reference, subsequent revisions do not apply.

For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]Void.

[2]Void.

[2a]3GPPTR21.905 "Vocabulary for 3GPP Specifications"

[3]3GPPTS22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)".

[4]3GPPTS22.003: "Teleservices supported by a Public Land Mobile Network (PLMN)".

[5]3GPPTS42.009: "Security aspects".

[5a]3GPPTS33.102: "3G security; Security architecture".

[6]Void.

[7]3GPPTS42.017: "Subscriber Identity Modules (SIM); Functional characteristics".

[8]3GPPTS22.101: "Service aspects; Service principles".

[8a]3GPPTS22.001: "Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)".

[8b]3GPPTS23.038: "Alphabets and language-specific information".

[9]3GPPTS23.101: "General UMTS Architecture".

[9a]3GPPTS23.108: "Mobile radio interface layer3 specification core network protocols; Stage2 (structured procedures)".

[10]3GPPTS23.003: "Numbering, addressing and identification".

[11]Void.

[12]3GPPTS23.014: "Support of Dual Tone Multi-Frequency (DTMF) signalling".

[12a]ETSIES201235-2, v1.2.1: "Specification of Dual Tone Multi-Frequency (DTMF); Transmitters and Receivers; Part 2: Transmitters".

[13]3GPPTS43.020: "Security-related network functions".

[14]3GPPTS23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".

[15]3GPPTS24.002: "GSM-UMTSPublic Land Mobile Network (PLMN) access reference configuration".

[16]3GPPTS44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities".

[17]Void.

[18]3GPPTS44.005: "Data Link (DL) layer; General aspects".

[19]3GPPTS44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification".

[19a]3GPPTS25.321: "Medium Access Control (MAC) protocol specification".

[19b]3GPPTS25.322: "Radio Link Control (RLC) protocol specification".

[19c]3GPPTS25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling".

[20]3GPPTS24.007: "Mobile radio interface signalling layer3; General aspects".

[21]3GPPTS24.010: "Mobile radio interface layer3; Supplementary services specification; General aspects".

[22]3GPPTS24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".

[23]3GPPTS24.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface".

[23a]3GPPTS44.071: "Location Services (LCS); Mobile radio interface layer 3 specification."

[23b]3GPPTS44.031 "Location Services LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC); Radio Resource LCS Protocol (RRLP)".

[23c]3GPPTS25.331: "Radio Resource Control (RRC) protocol specification"

[24]3GPPTS24.080: "Mobile radio Layer 3 supplementary service specification; Formats and coding".

[25]3GPPTS24.081: "Line identification supplementary services; Stage3".

[26]Void.

[27]3GPPTS24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage3".

[28]3GPPTS24.084: "MultiParty (MPTY) supplementary services; Stage3".

[29]Void.

[30]Void.

[31]Void.

[32]3GPPTS45.002: "Multiplexing and multiple access on the radio path".

[33]3GPPTS45.005: "Radio transmission and reception".

[34]3GPPTS45.008: "Radio subsystem link control".

[35]Void.

[36]3GPPTS27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".

[36a]3GPPTS27.060: "Mobile Station (MS) supporting Packet Switched Services ".

[37]3GPPTS29.002: "Mobile Application Part (MAP) specification".

[38]3GPPTS29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".

[39]3GPPTS51.010: "Mobile Station (MS) conformance specification".

[40]Void.

[41]ISO/IEC646 (1991): "Information technology - ISO 7-bit coded character set for information interchange".

[42]ISO/IEC6429: "Information technology - Control functions for coded character sets".

[43]ISO8348 (1987): "Information technology -- Open Systems Interconnection -- Network Service Definition".

[44]ITU-TRecommendationE.163: "Numbering plan for the international telephone service".

[45]ITU-TRecommendationE.164: "The international public telecommunication numbering plan".

[46]ITU-TRecommendationE.212: "The international identification plan for mobile terminals and mobile users".

[47]ITU-TRecommendationF.69 (1993): "The international telex service - Service and operational provisions of telex destination codes and telex network identification codes".

[48]ITU-TRecommendationI.330: "ISDN numbering and addressing principles".

[49]ITU-TRecommendationQ.920 (1993): "ISDN user-network interface data link layer - General aspects".

[50]ITU-TRecommendationQ.930 (1993): "ISDN user-network interface layer 3 - General aspects".

[51]ITU-TRecommendationI.500 (1993): "General structure of the ISDN interworking recommendations".

[52]ITU-TRecommendationT.50: "International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information interchange".

[53]ITURecommendationQ.931: "ISDN user-network interface layer 3 specification for basic control".

[54]ITU-TRecommendationV.21: "300 bits per second duplex modem standardized for use in the general switched telephone network".

[55]ITU-TRecommendationV.22: "1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits".

[56]ITU-TRecommendationV.22bis: "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits".

[57]Void.

[58]ITU-TRecommendationV.26ter: "2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits".

[59]ITU-TRecommendationV.32: "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits".

[60]ITU-TRecommendationV.110: "Support by an ISDN of data terminal equipments with V-Series type interfaces".

[61]ITU-TRecommendationV.120: "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing".

[62]ITU-TRecommendationX.21: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for synchronous operation on public data networks".

[63]Void.

[64]Void.

[65]ITU-TRecommendationX.30: "Support of X.21, X.21 bis and X.20 bis based Data Terminal Equipments (DTEs) by an Integrated Services Digital Network (ISDN)".

[66]ITU-TRecommendationX.31: "Support of packet mode terminal equipment by an ISDN".

[67]Void.

[68]Void.

[69]ITU-TRecommendationX.121: "International numbering plan for public data networks".

[70]ETSIETS300102-1: "Integrated Services Digital Network (ISDN); User-network interface layer3; Specifications for basic call control".

[71]Void.

[72]ISO/IEC10646: "Information technology -- Universal Multiple-Octet Coded Character Set (UCS)".

[73]3GPPTS22.060: "General Packet Radio Service (GPRS); Service Description; Stage1".

[74]3GPPTS23.060: "General Packet Radio Service (GPRS); Service Description; Stage2".

[75]Void.

[75a]3GPPTS43.318: "Generic Access Network (GAN); Stage2".

[76]3GPPTS44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".

[76b]3GPPTS44.318: "Generic Access Network (GAN); Mobile GAN interface layer 3 specification; Stage3".

[77]Void.

[78]3GPPTS44.065: "Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP)".

[78a]3GPPTS44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) Layer Specification".

[79]ITURecommendationI.460: "Multiplexing, rate adaption and support of existing interfaces".

[80]3GPPTS26.111: "Codec for Circuit Switched Multimedia Telephony Service; Modifications to H.324".

[81]3GPPTS23.107: "Quality of Service (QoS) concept and architecture".

[82]3GPPTS43.022: "Functions related to Mobile Station (MS) in idle mode and group receive mode".

[83]3GPPTS26.103: "Speech Codec List for GSM and UMTS".

[84]3GPPTS44.018: "Mobile radio interface layer 3 specification, Radio Resource Control Protocol".

[85]3GPPTS48.008: "Mobile-services Switching Centre Base Station System (MSC BSS) interface; layer 3 specification".

[86]3GPPTS48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)".

[87]3GPPTS43.055: "Dual Transfer Mode (DTM); Stage 2".

[88]3GPPTS23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage2".

[88a]3GPPTS23.093: "Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage2".

[89]3GPPTS22.042: "Network Identity and Time Zone (NITZ), Stage1".

[90]3GPPTS23.040: "Technical realization of Short Message Service (SMS)".

[91]3GPPTS44.056: "GSM Cordless Telephony System (CTS), (Phase 1) CTS Radio Interface Layer 3 Specification".

[92]3GPPTS23.226: "Global Text Telephony; Stage2 "

[93]3GPPTS26.226: "Cellular Text Telephone Modem (CTM), General Description"

[94]3GPPTS23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes"

[95]3GPPTS24.229: "IP Multimedia Call Control Protocol based on SIP and SDP"

[96]3GPPTS23.205: "Bearer-independent circuit-switched core network; Stage2".

[97]3GPPTS23.172: "UDI/RDI Fallback and Service Modification; Stage2".

[98]3GPPTS25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode"

[99]IETFRFC4291 (February2006): "Internet Protocol Version 6 (IPv6) Addressing Architecture".

[100]3GPPTS29.207: "Policy control over Go interface".

[101]3GPPTS21.111: "USIM and IC card requirements".

[102]IETFRFC1661 (July 1994): "The Point-to-Point Protocol (PPP)".

[103]IETFRFC3232 (January 2002): "Assigned Numbers: RFC1700 is Replaced by an On-line Database".

[104]3GPPTS23.034: "High Speed Circuit Switched Data (HSCSD) Stage2".

[105]3GPPTS23.271: "Functional stage2 description of Location Services (LCS)".

[106]3GPPTS23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and Functional Description".

[107]IETFRFC3376 (October 2002): "Internet Group Management Protocol, Version 3".[108]IETFRFC2710 (October 1999): "Multicast Listener Discovery (MLD) for IPv6".[109]3GPPTS23.251: "Network Sharing; Architecture and Functional Description".

[110]3GPPTS25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network"[111]3GPPTS44.118: "Radio Resource Control (RRC) protocol; Iu mode".

[112]3GPPTS31.102: "Characteristics of the USIM Application".

[113]3GPPTS43.129: "Packet-switched handover for GERAN A/Gb mode; Stage2".[114]3GPPTS23.009: "Handover procedures".

[115]3GPPTR23.903: "Redial solution for voice-video switching".

[116]3GPPTS24.279: "Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services, stage3" [117]ITU-TRecommendationH.324Amendment1: "New Annex K "Media Oriented Negotiation Acceleration Procedure" and associated changes to Annex".[118]ITU-TRecommendationH.324Amendment2: "New Annex L on text conversation and associated changes; corrections and clarifications to AnnexK".

[119]ITU-TRecommendationH.245: "Control protocol for multimedia communication"

[120]3GPPTS24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage3".

[121]3GPPTS36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".

[122]3GPPTS23.401: "GPRS enhancements for E-UTRAN access".

[123]3GPPTS33.401: "3GPP System Architecture Evolution; Security architecture".

[124]3GPPTS24.303: "Mobility management based on Dual-Stack Mobile IPv6; Stage3".

[125]3GPPTS24.327: "Mobility between 3GPP WLAN Interworking and 3GPP systems; GPRS and 3GPP I-WLAN aspects; Stage3".[126]3GPPTS23.216: "Single Radio Voice Call Continuity (SRVCC); Stage2".[127]3GPPTS23.002: "Network architecture".

[128]3GPPTS25.301: "Radio interface protocol architecture".[129]3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".[130]3GPPTS29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".[131]3GPPTS23.221: "Architectural requirements".[132]3GPPTS23.090: "Unstructured Supplementary Service Data (USSD); Stage2".

[133]3GPPTS23.272: "Circuit Switched Fallback in Evolved Packet System; Stage2".

[134]3GPPTS24.167: "3GPP IMS Management Object (MO); Stage3".[135]3GPPTS24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)".[136]3GPPTS24.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage3".[137]IETFRFC3261 (June2002): "SIP: Session Initiation Protocol".[138]3GPPTS22.011: "Service accessibility".[139]IETFRFC3633 (December2003): "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6".[140]3GPPTS23.012: "Location management procedures".[141]3GPPTS24.022: "Radio Link Protocol (RLP) for circuit switched bearer and teleservices".

[142]ITU-TRecommendationX.1: "International user classes of service in, and categories of access to, public data networks and Integrated Services Digital Networks (ISDNs)".[143]ITU-TRecommendationX.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit".[144]ITU-TRecommendationX.213: "Information technology Open Systems Interconnection Network service definition".[145]ITU-TRecommendationI.334: "Principles relating ISDN numbers/sub-addresses to the OSI reference model network layer addresses".

[146]ITU-TRecommendationH.223: "Multiplexing protocol for low bit rate multimedia communication".

[147]ITU-TRecommendationV.34: "A modem operating at data signalling rates of up to 33 600 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits".

[148]IETFRFC3810 (June2004): "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".[149]3GPPTS29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification".

[150]3GPPTS29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".

2.1Definitions and abbreviations

For the purposes of the present document, the abbreviations defined in 3GPPTR21.905 [2a] and the followings apply:CATCustomized Alerting ToneIP-CANIP-Connectivity Access NetworkHNBHome Node B

Kc64-bit GSM ciphering key

Kc128128-bit GSM ciphering keyL-GWLocal PDN Gateway

LIPALocal IP Access

TMGITemporary Mobile Group IdentityMTUMaximum Transfer Unit

2.1.1Random values

In a number of places in the present document, it is mentioned that some value must take a "random" value, in a given range, or more generally with some statistical distribution. Such cases interest only the Mobile Station.

It is required that there is a low probability that two MSs in the same conditions (including the case of two MSs of the same type from the same manufacturer) will choose the same value. Moreover, it is required that, if it happens that two MSs in similar conditions choose the same value, the probability of their choices being identical at the next occasion is the same as if their first choices had been different.

The meaning of such a specification is that any statistical test for these values, done on a series of similar events, will obtain a result statistically compatible with the specified distribution. This shall hold even in the cases where the tests are conducted with a subset of possible events, with some common parameters. Moreover, basic tests of independence of the values within the series shall pass.

Data against which correlation with the values shall not be found are the protocol state, or the IMSI, or identities or other unrelated information broadcast by the network, or the current TDMA frame number.

2.1.2Vocabulary

For the purposes of the present document, the following terms and definitions apply:

-A GSM security context is established and stored in the MS and the network as a result of a successful execution of a GSM authentication challenge. The GSM security context for the CS domain consists of the GSM ciphering key and the ciphering key sequence number. The GSM security context for the PS domain consists of the GPRS GSM ciphering key and the GPRS ciphering key sequence number.-A UMTS security context is established and stored in the MS and the network as a result of a successful execution of a UMTS authentication challenge. The UMTS security context for the CS domain consists of the UMTS ciphering key, the UMTS integrity key, the GSM ciphering key, the ciphering key sequence number and the GSM Kc128 (if an A5 ciphering algorithm that requires a 128-bit ciphering key is in use). The UMTS security context for the PS domain consists of the GPRS UMTS ciphering key, the GPRS UMTS integrity key, the GPRS GSM ciphering key, the GPRS ciphering key sequence number and the GPRS GSM Kc128 (if a GEA ciphering algorithm that requires a 128-bit ciphering key is in use).-An MS is attached for emergency bearer services if it has successfully completed an attach for emergency bearer services or if it has only a PDN connection for eme