Skip to main content

Full text of "TS 124 008 - V7.14.0 - Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 (3GPP TS 24.008 version 7.14.0 Release 7)"

See other formats


ETSITS124 008V7.14.0 



(2009-03) 



Technical Specification 

Digital cellular telecommunications system (Phase 2+); 
Universal Mobile Telecommunications System (UMTS); 

LTE; 
Mobile radio interface Layer 3 specification; 

Core network protocols; 

Stage 3 
(3GPP TS 24.008 version 7.14.0 Release 7) 



33i^ 



GS 




® 



GLOBAL SYSTEM FOR 
MOBILE COMMUNICATIONS 





3GPP TS 24.008 version 7.1 4.0 Release 7 1 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 



Reference 



RTS/TSGC-01 24008v7e0 
Keywords 



GSM, UMTS 



ETSI 

650 Route des Lucioles 
F-06921 Sophia Antipolis Cedex - FRANCE 

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

Siret N ° 348 623 562 0001 7 - NAF 742 C 
Association a but non lucratif enregistree a la 
Sous-Prefecture de Grasse (06) N° 7803/88 



Important notice 



Individual copies of the present document can be downloaded from: 
http://www.etsi.orq 

The present document may be made available in more than one electronic version or in print. In any case of existing or 

perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). 

In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive 

within ETSI Secretariat. 

Users of the present document should be aware that the document may be subject to revision or change of status. 

Information on the current status of this and other ETSI documents is available at 

http://portal.etsi.orq/tb/status/status.asp 

If you find errors in the present document, please send your comment to one of the following services: 

http://portal.etsi.orq/chaircor/ETSI support.asp 

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. 

© European Telecommunications Standards Institute 2009. 
All rights reserved. 

DECT™, PLUGTESTS™, UMTS™, TIPHON™, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered 

for the benefit of its Members. 
2QppTM |g g jracle Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. 

LTE™ 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 Trade Marks registered and owned by the GSM Association. 



ETSI 



3GPP TS 24.008 version 7.1 4.0 Release 7 2 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 



Intellectual Property Rights 



IPRs essential or potentially essential to the present document may have been declared to ETSI. The information 
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found 
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in 
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web 
server ( http://webapp.etsi.org/IPR/home.asp ). 

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee 
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web 
server) which are, or may be, or may become, essential to the present document. 



Foreword 

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

The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or 
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. 

The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under 
http://webapp.etsi.org/kev/quervform.asp . 



ETSI 



3GPP TS 24.008 version 7.1 4.0 Release 7 3 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 



Contents 



Intellectual Property Rights 2 

Foreword 2 

Foreword 23 

Introduction 23 

1 Scope 24 

1.1 Scope of the Technical Specification 24 

1.2 Application to the interface structures 24 

1.3 Structure of layer 3 procedures 24 

1.4 Test procedures 24 

1.5 Use of logical channels in A/Gb mode 25 

1.6 Overview of control procedures 25 

1.6.1 List of procedures 25 

1.7 Applicability of implementations 27 

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

1.7.2 General Packet Radio Service (GPRS) 27 

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

1.7.2.2 Packet services in lu mode (lu mode only) 28 

2 References 28 

2.1 Definitions and abbreviations 33 

2.1.1 Random values 33 

2.2.2 Vocabulary 33 

3 Radio Resource management procedures 35 

4 Elementary procedures for Mobility Management 35 

4.1 General 35 

4.1.1 MM and GMM procedures 36 

4.1.1.1 Types of MM and GMM procedures 36 

4.1.1.1.1 Integrity Checking of Signalling Messages in the Mobile Station (lu mode only) 37 

4.1.1.1.1a Integrity protection for emergency call (lu mode only) 38 

4.1.1.2 MM-GMM co-ordination for GPRS MS's 39 

4.1.1.2.1 GPRS MS operating in mode A or B in a network that operates in mode I 39 

4.1.1.2.2 GPRS MS operating in mode A or B in a network that operates in mode II or III 40 

4.1.1.3 Core Network System Information for MM (lu mode only) 40 

4.1.1.4 Core Network System Information for GMM (lu mode only) 40 

4.1.2 MM sublayer states 40 

4.1.2.1 MM sublayer states in the mobile station 41 

4.1.2.1.1 Main states 41 

4.1.2.1.2 Substates of the MM IDLE state 44 

4.1.2.2 The update Status 45 

4.1.2.3 MM sublayer states on the network side 46 

4.1.3 GPRS mobility management (GMM) sublayer states 47 

4.1.3.1 GMM states in the MS 47 

4.1.3.1.1 Main states 48 

4.1.3.1.2 Substates of state GMM-DEREGISTERED 48 

4.1.3.1.3 Substates of state GMM-REGISTERED 49 

4.1.3.2 GPRS update status 51 

4.1.3.3 GMM mobility management states on the network side 51 

4.1.3.3.1 Main States 51 

4.1.3.3.2 Substates of state GMM-REGISTERED 52 

4.2 Behaviour of the MS in MM Idle state, GMM-DEREGISTERED state and GMM-REGISTERED state 52 

4.2.1 Primary Service State selection 53 

4.2.1.1 Selection of the Service State after Power On 53 

4.2.1.2 Other Cases 53 

4.2.2 Detailed Description of the MS behaviour in MM IDLE State 54 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 4 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.2.2.1 Service State, NORMAL SERVICE 54 

4.2.2.2 Service State, ATTEMPTING TO UPDATE 54 

4.2.2.3 Service State, LIMITED SERVICE 55 

4.2.2.4 Service State, NO IMSI 55 

4.2.2.5 Service State, SEARCH FOR PLMN, NORMAL SERVICE 56 

4.2.2.6 Service State, SEARCH FOR PLMN 56 

4.2.2.7 Service State, RECEIVING GROUP CALL (NORMAL SERVICE) 56 

4.2.2.8 Service State, RECEIVING GROUP CALL (LIMITED SERVICE) 57 

4.2.3 Service state when back to state MM IDLE from another state 57 

4.2.4 Behaviour in state GMM-DEREGISTERED 58 

4.2.4.1 Primary substate selection 58 

4.2.4.1.1 Selection of the substate after power on or enabling the MS's GPRS capability 58 

4.2.4.1.2 Other Cases 59 

4.2.4.2 Detailed description of the MS behaviour in state GMM-DEREGISTERED 59 

4.2.4.2.1 Substate, NORMAL-SERVICE 59 

4.2.4.2.2 Substate, ATTEMPTING-TO-ATTACH 59 

4.2.4.2.3 Substate, LIMITED-SERVICE 59 

4.2.4.2.4 Substate, NO-IMSI 59 

4.2.4.2.5 Substate, NO-CELL 60 

4.2.4.2.6 Substate, PLMN-SEARCH 60 

4.2.4.2.7 Substate, ATTACH-NEEDED 60 

4.2.4.2.8 Substate, SUSPENDED (A/Gb mode only) 60 

4.2.4.3 Substate when back to state GMM-DEREGISTERED from another GMM state 60 

4.2.5 Behaviour in state GMM-REGISTERED 60 

4.2.5.1 Detailed description of the MS behaviour in state GMM-REGISTERED 61 

4.2.5.1.1 Substate, NORMAL-SERVICE 61 

4.2.5.1.2 Substate, SUSPENDED (A/Gb mode only) 61 

4.2.5.1.3 Substate, UPDATE-NEEDED 61 

4.2.5.1.4 Substate, ATTEMPTING-TO-UPDATE 61 

4.2.5.1.5 Substate, NO-CELL-AVAILABLE 62 

4.2.5.1.6 Substate, LIMITED-SERVICE 62 

4.2.5.1.7 Substate, ATTEMPTING-TO-UPDATE-MM 62 

4.2.5.1.8 Substate, PLMN-SEARCH 62 

4.3 MM common procedures 62 

4.3.1 TMSI reallocation procedure 62 

4.3.1.1 TMSI reallocation initiation by the network 63 

4.3.1.2 TMSI reallocation completion by the mobile station 63 

4.3.1.3 TMSI reallocation completion in the network 63 

4.3.1.4 Abnormal cases 63 

4.3.2 Authentication procedure 64 

4.3.2a Authentication procedure used for a UMTS authentication challenge 64 

4.3.2b Authentication Procedure used for a GSM authentication challenge 64 

4.3.2.1 Authentication request by the network 65 

4.3.2.2 Authentication response by the mobile station 65 

4.3.2.3 Authentication processing in the network 66 

4.3.2.4 Ciphering key sequence number 66 

4.3.2.5 Authentication not accepted by the network 66 

4.3.2.5.1 Authentication not accepted by the MS 67 

4.3.2.6 Abnormal cases 67 

4.3.2.6.1 MS behaviour towards a network that has failed the authentication procedure 70 

4.3.2.7 Handling of keys at intersystem change fromlu mode to A/Gb mode 70 

4.3.2.7a Use of established security contexts 70 

4.3.2.8 Handling of keys at intersystem change from A/Gb mode to lu mode 71 

4.3.2.9 Void 72 

4.3.3 Identification procedure 72 

4.3.3.1 Identity request by the network 72 

4.3.3.2 Identification response by the mobile station 72 

4.3.3.3 Abnormal cases 72 

4.3.4 IMSI detach procedure 73 

4.3.4.1 IMSI detach initiation by the mobile station 73 

4.3.4.2 IMSI detach procedure in the network 73 

4.3.4.3 IMSI detach completion by the mobile station 73 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 5 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.3.4.4 Abnormal cases 74 

4.3.5 Abort procedure 74 

4.3.5.1 Abort procedure initiation by the network 74 

4.3.5.2 Abort procedure in the mobile station 74 

4.3.6 MM information procedure 74 

4.3.6.1 MM information procedure initiation by the network 74 

4.3.6.2 MM information procedure in the mobile station 75 

4.4 MM specific procedures 75 

4.4.1 Location updating procedure 75 

4.4.2 Periodic updating 76 

4.4.3 IMSI attach procedure 77 

4.4.4 Generic Location Updating procedure 77 

4.4.4.1 Location updating initiation by the mobile station 77 

4.4.4. 1 a Network Request for Additional mobile station Capability Information 78 

4.4.4.2 Identification request from the network 78 

4.4.4.3 Authentication by the network 78 

4.4.4.4 Security mode setting by the network 78 

4.4.4.5 Attempt Counter 78 

4.4.4.6 Location updating accepted by the network 78 

4.4.4.7 Location updating not accepted by the network 80 

4.4.4.8 Release of RR connection after location updating 81 

4.4.4.9 Abnormal cases on the mobile station side 81 

4.4.4.10 Abnormal cases on the network side 82 

4.4.5 Void 83 

4.4.6 Void 83 

4.5 Connection management sublayer service provision 83 

4.5.1 MM connection establishment 83 

4.5.1.1 MM connection establishment initiated by the mobile station 83 

4.5.1.2 Abnormal cases 86 

4.5.1.3 MM connection establishment initiated by the network 87 

4.5.1.3.1 Mobile Terminating CM Activity 87 

4.5.1.3.2 Mobile Originating CM Activity $(CCBS)$ 88 

4.5.1.3.3 Paging response in lu mode (lu mode only) 89 

4.5.1.4 Abnormal cases 89 

4.5.1.5 MM connection establishment for emergency calls 89 

4.5.1.6 Call re-establishment 90 

4.5.1.6.1 Call re-establishment, initiation by the mobile station 90 

4.5.1.6.2 Abnormal cases 91 

4.5.1.7 Forced release during MO MM connection establishment 92 

4.5.2 MM connection information transfer phase 93 

4.5.2.1 Sending CM messages 93 

4.5.2.2 Receiving CM messages 93 

4.5.2.3 Abnormal cases 93 

4.5.3 MM connection release 93 

4.5.3.1 Release of associated RR connection 93 

4.5.3.2 Uplink release in a voice group call 94 

4.6 Receiving a MM STATUS message by a MM entity 94 

4.7 Elementary mobility management procedures for GPRS services 94 

4.7.1 General 94 

4.7.1.1 Lower layer failure 94 

4.7.1.2 Ciphering of messages (A/Gb mode only) 94 

4.7.1.3 P-TMSI signature 95 

4.7.1.4 Radio resource sublayer address handling 95 

4.7.1.4.1 Radio resource sublayer address handling (A/Gb mode only) 95 

4.7.1.5 P-TMSI handling 96 

4.7.1.5.1 P-TMSI handling in A/Gb mode 96 

4.7.1.5.2 P-TMSI handling in lu mode 96 

4.7.1.6 Change of network mode of operation 96 

4.7.1.6.1 Change of network mode of operation in A/Gb mode (A/Gb mode only) 96 

4.7.1.6.2 Change of network mode of operation in lu mode (lu mode only) 97 

4.7.1.6.3 Change of network mode of operation at lu mode to A/Gb mode inter-system change 98 

4.7.1.6.4 Change of network mode of operation at A/Gb mode to lu mode inter-system change 99 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 6 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.1.7 Intersystem change between A/Gb mode and lu mode 100 

4.7.1.8 List of forbidden PLMNs for GPRS service 101 

4.7.1.9 Release of the PS signalling connection (lu mode only) 101 

4.7.2 GPRS Mobility management timers and UMTS PS signalling connection control 101 

4.7.2.1 READY timer behaviour 101 

4.7.2.1.1 READY timer behaviour (A/Gb mode only) 101 

4.7.2.1.2 Handling of READY timer in lu mode (lu mode only) 102 

4.7.2.2 Periodic routing area updating 103 

4.7.2.3 PMM-IDLE mode and PMM-CONNECTED mode (lu mode only) 104 

4.7.2.4 Handling of Force to standby in lu mode (lu mode only) 104 

4.7.2.5 RA Update procedure for Signalling Connection Re-establishment (lu mode only) 104 

4.7.2.6 Cell Update triggered by low layers 104 

4.7.3 GPRS attach procedure 105 

4.7.3.1 GPRS attach procedure for GPRS services 106 

4.7.3.1.1 GPRS attach procedure initiation 106 

4.7.3.1.2 GMM common procedure initiation 106 

4.7.3.1.3 GPRS attach accepted by the network 106 

4.7.3.1.4 GPRS attach not accepted by the network 108 

4.7.3.1.5 Abnormal cases in the MS 110 

4.7.3.1.6 Abnormal cases on the network side Ill 

4.7.3.2 Combined GPRS attach procedure for GPRS and non-GPRS services 113 

4.7.3.2.1 Combined GPRS attach procedure initiation 113 

4.7.3.2.2 GMM Common procedure initiation 113 

4.7.3.2.3 Combined GPRS attach accepted by the network 114 

4.7.3.2.4 Combined GPRS attach not accepted by the network 115 

4.7.3.2.5 Abnormal cases in the MS 117 

4.7.3.2.6 Abnormal cases on the network side 118 

4.7.4 GPRS detach procedure 118 

4.7.4.1 MS initiated GPRS detach procedure 118 

4.7.4.1.1 MS initiated GPRS detach procedure initiation 118 

4.7.4.1.2 MS initiated GPRS detach procedure completion for GPRS services only 119 

4.7.4.1.3 MS initiated combined GPRS detach procedure completion 119 

4.7.4.1.4 Abnormal cases in the MS 119 

4.7.4.2 Network initiated GPRS detach procedure 121 

4.7.4.2.1 Network initiated GPRS detach procedure initiation 121 

4.7.4.2.2 Network initiated GPRS detach procedure completion by the MS 121 

4.7.4.2.3 Network initiated GPRS detach procedure completion by the network 124 

4.7.4.2.4 Abnormal cases on the network side 124 

4.7.5 Routing area updating procedure 125 

4.7.5.1 Normal and periodic routing area updating procedure 127 

4.7.5.1.1 Normal and periodic routing area updating procedure initiation 127 

4.7.5.1.2 GMM Common procedure initiation 127 

4.7.5.1.3 Normal and periodic routing area updating procedure accepted by the network 127 

4.7.5.1.4 Normal and periodic routing area updating procedure not accepted by the network 130 

4.7.5.1.5 Abnormal cases in the MS 132 

4.7.5.1.6 Abnormal cases on the network side 134 

4.7.5.2 Combined routing area updating procedure 135 

4.7.5.2.1 Combined routing area updating procedure initiation 136 

4.7.5.2.2 GMM Common procedure initiation 137 

4.7.5.2.3 Combined routing area updating procedure accepted by the network 137 

4.7.5.2.4 Combined routing area updating not accepted by the network 139 

4.7.5.2.5 Abnormal cases in the MS 141 

4.7.5.2.6 Abnormal cases on the network side 141 

4.7.6 P-TMSl reallocation procedure 142 

4.7.6.1 P-TMSl reallocation initiation by the network 142 

4.7.6.2 P-TMSl reallocation completion by the MS 142 

4.7.6.3 P-TMSl reallocation completion by the network 142 

4.7.6.4 Abnormal cases on the network side 142 

4.7.7 Authentication and ciphering procedure 144 

4.7.7a Authentication and ciphering procedure used for UMTS authentication challenge 144 

4.7.7b Authentication and ciphering procedure used for GSM authentication challenge 144 

4.7.7c Change of the ciphering algorithm at PS Handover 145 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 7 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.7.1 Authentication and ciphering initiation by the network 145 

4.7.7.2 Authentication and ciphering response by the MS 146 

4.7.7.3 Authentication and ciphering completion by the network 147 

4.7.7.4 GPRS ciphering key sequence number 147 

4.7.7.5 Authentication not accepted by the network 148 

4.7.7.5.1 Authentication not accepted by the MS 148 

4.7.7.6 Abnormal cases 149 

4.7.7.6.1 MS behaviour towards a network that has failed the authentication procedure 152 

4.7.7.7 Use of established security contexts 152 

4.7.7.8 Handling of keys at intersystem change from lu mode to A/Gb mode 153 

4.7.7.9 Handling of keys at intersystem change from A/Gb mode to lu mode 153 

4.7.8 Identification procedure 154 

4.7.8.1 Identification initiation by the network 154 

4.7.8.2 Identification response by the MS 154 

4.7.8.3 Identification completion by the network 154 

4.7.8.3a Abnormal cases in the MS 154 

4.7.8.4 Abnormal cases on the network side 154 

4.7.9 Paging procedure 156 

4.7.9.1 Paging for GPRS services 156 

4.7.9.1.1 Paging for GPRS services using P-TMSI 156 

4.7.9.1.2 Paging for GPRS services using IMSI 156 

4.7.9.2 Paging for non-GPRS services 157 

4.7.10 Receiving a GMM STATUS message by a GMM entity 157 

4.7.11 Void 157 

4.7.12 GMM Information procedure 157 

4.7.12.1 GMM information procedure initiation by the network 157 

4.7.12.2 GMM information procedure in the mobile station 157 

4.7.13 Service Request procedure (lu mode only) 157 

4.7.13.1 Service Request procedure initiation 159 

4.7.13.2 GMM common procedure initiation 160 

4.7.13.3 Service request procedure accepted by the network 160 

4.7.13.4 Service request procedure not accepted by the network 160 

4.7.13.5 Abnormal cases in the MS 162 

4.7.13.6 Abnormal cases on the network side 164 

4.7.14 Void 165 

5 Elementary procedures for circuit-switched Call Control 165 

5.1 Overview 165 

5.1.1 General 165 

5.1.2 Call Control States 169 

5.1.2.1 Call states at the mobile station side of the interface 169 

5.1.2.1.1 Null (State UO) 169 

5.1.2.1.2 MM Connection pending (UO.l) 169 

5.1.2.1.2a CC prompt present (U0.2) $(CCBS)$ 170 

5.1.2.1.2b Wait for network information (U0.3)$(CCBS)$ 170 

5.1.2.1.2c CC-EstabUshment present (U0.4) $(CCBS)$ 170 

5.1.2.1.2d CC-Establishment confirmed (U0.5) $(CCBS)$ 170 

5.1.2.1.2e Recall present (U0.6) $(CCBS)$ 170 

5.1.2.1.3 Call initiated (Ul) 170 

5.1.2.1.4 Mobile originating call proceeding (U3) 170 

5.1.2.1.5 Call delivered (U4) 170 

5.1.2.1.6 Call present (U6) 170 

5.1.2.1.7 Call received (U7) 170 

5.1.2.1.8 Connect Request (U8) 170 

5.1.2.1.9 Mobile terminating call confirmed (U9) 171 

5.1.2.1.10 Active (UIO) 171 

5.1.2.1.11 Disconnect request (U 11) 171 

5.1.2.1.12 Disconnect indication (U12) 171 

5.1.2.1.13 Release request (U 19) 171 

5.1.2.1.14 Mobile originating modify (U26) 171 

5.1.2.1.15 Mobile terminating modify (U27) 171 

5.1.2.2 Network call states 171 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 8 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

Null (State NO) 171 

MM connection pending (NO.l) 171 

CC connection pending (N0.2) $(CCBS)$ 171 

Network answer pending (N0.3) $(CCBS)$ 171 

CC-Establishment present (N0.4) $(CCBS)$ 172 

CC-Establishment confirmed (N0.5) $(CCBS)$ 172 

Call initiated (Nl) 172 

Mobile originating call proceeding (N3) 172 

Call delivered (N4) 172 

Call present (N6) 172 

Call received (N7) 172 

Connect request (N8) 172 

Mobile terminating call confirmed (N9) 172 

Active (NIO) 172 

Not used 172 

Disconnect indication (N12) 172 

Release request (N 19) 173 

Mobile originating modify (N26) 173 

Mobile terminating modify (N27) 173 

Connect Indication (N28) 173 

Call establishment procedures 173 

Mobile originating call establishment 173 

Call initiation 174 

Receipt of a setup message 175 

Receipt of a CALL PROCEEDING message 176 

Notification of progressing mobile originated call 177 

Notification of interworking in connection with mobile originated call establishment 177 

Call progress in the PLMN/ISDN environment 177 

Alerting 177 

Call connected 178 

Call rejection 178 

Transit network selection 179 

Traffic channel assignment at mobile originating call establishment 179 

Call queuing at mobile originating call establishment 179 

Speech Codec Selection 179 

Cellular Text telephone Modem (CTM) selection 180 

Mobile terminating call establishment 180 

Call indication 181 

Compatibility checking 181 

Call confirmation 181 

Response to SETUP 181 

Receipt of CALL CONFIRMED and ALERTING by the network 182 

Call failure procedures 183 

Called mobile station clearing during mobile terminating call establishment 183 

Notification of interworking in connection with mobile terminating call establishment 183 

Call accept 184 

Active indication 184 

Traffic channel assignment at mobile terminating call establishment 184 

Call queuing at mobile terminating call establishment 185 

User connection attachment during a mobile terminating call 185 

Speech Codec Selection 185 

Cellular Text telephone Modem (CTM) selection 185 

Network initiated MO call $(CCBS)$ 185 

Initiation 185 

CC-Establishment present 186 

Recall Alignment Procedure 187 

CC-Establishment confirmation 188 

Recall present 188 

Traffic channel assignment during network initiated mobile originating call establishment 189 

Signalling procedures during the "active" state 189 

User notification procedure 189 

Call rearrangements 189 



£75/ 



5.1.2.2.1 


5.1.2.2.2 


5.1.2.2.2a 


5.1.2.2.2b 


5.1.2.2.2c 


5.1.2.2.2d 


5.1.2.2.3 


5.1.2.2.4 


5.1.2.2.5 


5.1.2.2.6 


5.1.2.2.7 


5.1.2.2.8 


5.1.2.2.9 


5.1.2.2.10 


5.1.2.2.11 


5.1.2.2.12 


5.1.2.2.13 


5.1.2.2.14 


5.1.2.2.15 


5.1.2.2.16 


5.2 


5.2.1 


5.2.1.1 


5.2.1.2 


5.2.1.3 


5.2.1.4 


5.2.1.4.1 


5.2.1.4.2 


5.2.1.5 


5.2.1.6 


5.2.1.7 


5.2.1.8 


5.2.1.9 


5.2.1.10 


5.2.1.11 


5.2.1.12 


5.2.2 


5.2.2.1 


5.2.2.2 


5.2.2.3 


5.2.2.3.1 


5.2.2.3.2 


5.2.2.3.3 


5.2.2.3.4 


5.2.2.4 


5.2.2.5 


5.2.2.6 


5.2.2.7 


5.2.2.8 


5.2.2.9 


5.2.2.10 


5.2.2.11 


5.2.3 


5.2.3.1 


5.2.3.2 


5.2.3.2.1 


5.2.3.3 


5.2.3.4 


5.2.3.5 


5.3 


5.3.1 


5.3.2 



3GPP TS 24.008 version 7.1 4.0 Release 7 9 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.3.3 Codec Change Procedure 189 

5.3.4 Support of Dual Services 190 

5.3.4.1 Service Description 190 

5.3.4.2 Call establishment 190 

5.3.4.2.1 Mobile Originating EstabHshment 190 

5.3.4.2.2 Mobile Terminating Establishment 191 

5.3.4.3 Changing the Call Mode 191 

5.3.4.3.1 Initiation of in-call modification 191 

5.3.4.3.2 Successful completion of in-call modification 192 

5.3.4.3.3 Change of the channel configuration 193 

5.3.4.3.4 Failure of in-call modification 193 

5.3.4.4 Abnormal procedures 194 

5.3.5 User initiated service level up- and downgrading (A/Gb mode and GERAN lu mode only) 194 

5.3.5.1 Initiation of service level up- and downgrading 194 

5.3.5.2 Successful completion of service level up- and downgrading 195 

5.3.5.3 Rejection of service level up- and downgrading 195 

5.3.5.4 Time-out recovery 195 

5.3.6 Support of multimedia calls 195 

5.3.6.1 Service description 195 

5.3.6.2 Call establishment 195 

5.3.6.2.1 Mobile originated multimedia call establishment 196 

5.3.6.2.2 Mobile terminating multimedia call 197 

5.3.6.2.2.1 Fallback to speech 197 

5.3.6.3 In-call modification in the "active" state 197 

5.3.6.3.1 Void 198 

5.3.6.3.2 Void 198 

5.3.6.3.3 Void 198 

5.4 Call clearing 198 

5.4.1 Terminology 198 

5.4.2 Exception conditions 198 

5.4.3 Clearing initiated by the mobile station 199 

5.4.3.1 Initiation of call clearing 199 

5.4.3.2 Receipt of a DISCONNECT message from the mobile station 199 

5.4.3.3 Receipt of a RELEASE message from the network 199 

5.4.3.4 Receipt of a RELEASE COMPLETE message from the mobile station 199 

5.4.3.5 Abnormal cases 199 

5.4.4 Clearing initiated by the network 200 

5.4.4.1 Clearing initiated by the network: mobile does not support "Prolonged Clearing Procedure" 200 

5.4.4.1.1 Clearing when tones/announcements provided 200 

5.4.4.1.2 Clearing when tones/announcements not provided 200 

5.4.4.1.3 Completion of clearing 201 

5.4.4.2 Clearing initiated by the network: mobile supports "Prolonged Clearing Procedure" 201 

5.4.4.2. 1 Clearing when tones/announcements provided and the network does not indicate that "CCBS 
activation is possible" 201 

5.4.4.2.2 Clearing when the network indicates that "CCBS activation is possible" 202 

5.4.4.2.3 Clearing when tones/announcements are not provided and the network does not indicate that 
"CCBS activation is possible" 203 

5.4.4.2.4 Receipt of a RELEASE message from the mobile station 204 

5.4.4.2.5 Completion of clearing 204 

5.5 Miscellaneous procedures 205 

5.5.1 In-band tones and announcements 205 

5.5.2 Call colHsions 205 

5.5.3 Status procedures 205 

5.5.3.1 Status enquiry procedure 205 

5.5.3.2 Reception of a STATUS message by a CC entity 206 

5.5.3.2.1 STATUS message with incompatible state 206 

5.5.3.2.2 STATUS message with compatible state 206 

5.5.4 Call re-establishment, mobile station side 206 

5.5.4.1 Indication from the mobility management sublayer 206 

5.5.4.2 Reaction of call control 206 

5.5.4.3 Completion of re-establishment 207 

5.5.4.4 Unsuccessful outcome 207 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.5.5 Call re-establishment, network side 207 

5.5.5.1 State alignment 207 

5.5.6 Progress 207 

5.5.7 DTMF protocol control procedure 207 

5.5.7.1 Start DTMF request by the mobile station 208 

5.5.7.2 Start DTMF response by the network 208 

5.5.7.3 Stop DTMF request by the mobile station 208 

5.5.7.4 Stop DTMF response by the network 208 

5.5.7.5 Sequencing of subsequent start DTMF requests by the mobile station 208 

6 Support for packet services 209 

6.1 GPRS Session management 209 

6.1.1 General 209 

6.1.2 Session management states 210 

6.1.2.1 Session management states in the MS 210 

6.1.2.1.1 PDP-INACTIVE 210 

6.1.2.1.2 PDP-ACTIVE-PENDING 210 

6.1.2.1.3 PDP-INACTIVE-PENDING 210 

6.1.2.1.4 PDP-ACTIVE 210 

6.1.2.1.5 PDP-MODlFY_PENDING 210 

6.1.2.1.6 MBMS-ACTIVE-PENDING 210 

6.1.2.1.7 MBMS-ACTIVE 210 

6.1.2.2 Session management states on the network side 212 

6.1.2.2.1 PDP-INACTIVE 212 

6.1.2.2.2 PDP-ACTlVE-PENDlNG 212 

6.1.2.2.3 PDP-lNACTlVE-PENDlNG 212 

6.1.2.2.4 PDP-ACTIVE 212 

6.1.2.2.5 PDP-MODIFY-PENDING 212 

6.1.2.2.6 MBMS-ACTlVE-PENDlNG 213 

6.1.2.2.7 MBMS-INACTIVE-PENDING 213 

6.1.2.2.8 MBMS-ACTIVE 213 

6.1.3 Session Management procedures 214 

6.1.3.1 PDP context activation 214 

6.1.3.1.1 Successful PDP context activation initiated by the mobile station 214 

6.1.3.1.2 Successful PDP context activation requested by the network 215 

6.1.3.1.3 Unsuccessful PDP context activation initiated by the MS 216 

6.1.3.1.4 Unsuccessful PDP context activation requested by the network 216 

6.1.3.1.5 Abnormal cases 216 

6.1.3.2 Secondary PDP Context Activation Procedure 218 

6.1.3.2.1 Successful Secondary PDP Context Activation Procedure Initiated by the MS 219 

6.1.3.2.1a Successful Secondary PDP Context Activation Procedure Requested by the network 219 

6.1.3.2.2 Unsuccessful Secondary PDP Context Activation Procedure initiated by the MS 220 

6.1.3.2.2a Unsuccessful secondary PDP context activation requested by the network 220 

6.1.3.2.3 Abnormal cases 221 

6.1.3.3 PDP context modification procedure 223 

6.1.3.3.1 Network initiated PDP Context Modification 224 

6.1.3.3.2 MS initiated PDP Context Modification accepted by the network 224 

6.1.3.3.3 MS initiated PDP Context Modification not accepted by the network 225 

6.1.3.3.3a Network initiated PDP Context Modification not accepted by the MS 227 

6.1.3.3.4 Abnormal cases 227 

6.1.3.4 PDP context deactivation procedure 229 

6.1.3.4.1 PDP context deactivation initiated by the MS 229 

6.1.3.4.2 PDP context deactivation initiated by the network 230 

6.1.3.4.3 Abnormal cases 230 

6.1.3.4a Void 231 

6.1.3.5 Void 231 

6.1.3.6 Receiving a SM STATUS message by a SM entity 231 

6.1.3.7 Protocol configuration options 232 

6.1.3.8 MBMS context activation 232 

6.1.3.8.1 Successful MBMS context activation 232 

6.1.3.8.2 Unsuccessful MBMS context activation requested by the MS 233 

6.1.3.8.3 Unsuccessful MBMS context activation requested by the network 233 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 1 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

6.1.3.8.4 Abnormal cases 233 

6.1.3.9 MBMS context deactivation 234 

6.1.3.9.1 MBMS context deactivation initiated by the network 234 

6.1.3.9.2 Abnormal cases 235 

6.1.3.10 MBMS protocol configuration options 235 

6.2 void 235 

7 Examples of structured procedures 235 

8 Handling of unknown, unforeseen, and erroneous protocol data 236 

8.1 General 236 

8.2 Message too short 236 

8.3 Unknown or unforeseen transaction identifier 236 

8.3.1 Call Control 236 

8.3.2 Session Management 237 

8.4 Unknown or unforeseen message type 238 

8.5 Non-semantical mandatory information element errors 239 

8.5.1 Radio resource management 239 

8.5.2 Mobility management 239 

8.5.3 Call control 239 

8.5.4 GMM mobility management 240 

8.5.5 Session management 240 

8.6 Unknown and unforeseen lEs in the non-imperative message part 240 

8.6.1 lEIs unknown in the message 240 

8.6.2 Out of sequence lEs 240 

8.6.3 Repeated IBs 241 

8.7 Non-imperative message part errors 241 

8.7.1 Syntactically incorrect optional IBs 241 

8.7.2 Conditional IB errors 241 

8.8 Messages with semantically incorrect contents 241 

9 Message functional definitions and contents 242 

9.1 Messages for Radio Resources management 243 

9.2 Messages for mobility management 243 

9.2.1 Authentication reject 243 

9.2.2 Authentication request 244 

9.2.2.1 Authentication Parameter AUTN 244 

9.2.3 Authentication response 244 

9.2.3.1 Authentication Response Parameter 245 

9.2.3.2 Authentication Response Parameter (extension) 245 

9.2.3a Authentication Failure 245 

9.2.3a. 1 Authentication Failure parameter 245 

9.2.4 CM Re-estabHshment request 246 

9.2.4.1 Location area identification 246 

9.2.4.2 Mobile Station Classmark 246 

9.2.5 CM service accept 246 

9.2.5a CM service prompt $(CCBS)$ 247 

9.2.6 CM service reject 247 

9.2.7 CM service abort 248 

9.2.8 Abort 248 

9.2.9 CM service request 249 

9.2.9.1 Mobile Station Classmark 249 

9.2.9.2 Priority 249 

9.2.10 Identity request 249 

9.2.11 Identity response 250 

9.2.12 IMSI detach indication 250 

9.2.12.1 Mobile Station Classmark 251 

9.2.13 Location updating accept 251 

9.2.13.1 Follow on proceed 251 

9.2.13.2 CTS permission 252 

9.2.13.3 Bquivalent PLMNs 252 

9.2.13.4 Bmergency Number List 252 

9.2.14 Location updating reject 252 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 2 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.2.15 Location updating request 252 

9.2.15.1 Location area identification 253 

9.2.15.2 Mobile Station Classmark 253 

9.2.15.3 Mobile Station Classmark for lu mode 253 

9.2.15a MM information 253 

9.2.15a. 1 Full name for network 254 

9.2.15a.2 Short name for network 254 

9.2.15a.3 Local time zone 254 

9.2.15a.4 Universal time and local time zone 254 

9.2.15a.5 LSA Identity 254 

9.2.15a.6 Network Daylight Saving Time 255 

9.2.16 MM Status 255 

9.2.17 TMSl reallocation command 255 

9.2.18 TMSl reallocation complete 256 

9.2.19 MM Null 256 

9.3 Messages for circuit-switched call control 257 

9.3.1 Alerting 257 

9.3.1.1 Alerting (network to mobile station direction) 257 

9.3.1.1.1 Facility 258 

9.3.1.1.2 Progress indicator 258 

9.3.1.1.3 User-user 258 

9.3.1.2 Alerting (mobile station to network direction) 258 

9.3.1.2.1 Facility 259 

9.3.1.2.2 User-user 259 

9.3.1.2.3 SS version 259 

9.3.2 Call confirmed 259 

9.3.2.1 Repeat indicator 260 

9.3.2.2 Bearer capability 1 and bearer capability 2 260 

9.3.2.3 Cause 261 

9.3.2.4 CC Capabilities 261 

9.3.2.5 Stream Identifier 261 

9.3.2.6 Supported Codecs 261 

9.3.3 Call proceeding 261 

9.3.3.1 Repeat indicator 261 

9.3.3.2 Bearer capability 1 and bearer capability 2 262 

9.3.3.3 Facility 262 

9.3.3.4 Progress Indicator 262 

9.3.3.5 Priority granted 262 

9.3.3.6 Network Call Control Capabilities 262 

9.3.4 Congestion control 262 

9.3.4.1 Cause 263 

9.3.5 Connect 263 

9.3.5.1 Connect (network to mobile station direction) 263 

9.3.5.1.1 Facility 263 

9.3.5.1.2 Progress indicator 263 

9.3.5.1.3 User-user 263 

9.3.5.2 Connect (mobile station to network direction) 263 

9.3.5.2.1 Facility 264 

9.3.5.2.2 User-user 264 

9.3.5.2.3 SS version 264 

9.3.5.2.4 Stream Identifier 264 

9.3.6 Connect acknowledge 264 

9.3.7 Disconnect 265 

9.3.7.1 Disconnect (network to mobile station direction) 265 

9.3.7.1.1 Facility 265 

9.3.7.1.2 Progress indicator 265 

9.3.7.1.3 User-user 265 

9.3.7.1.4 Allowed actions $(CCBS)$ 265 

9.3.7.2 Disconnect (mobile station to network direction) 266 

9.3.7.2.1 Facility 266 

9.3.7.2.2 User-user 266 

9.3.7.2.3 SS version 266 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 3 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.3.8 Emergency setup 266 

9.3.8.1 Bearer capability 267 

9.3.8.2 Stream Identifier 267 

9.3.8.3 Supported Codecs 267 

9.3.8.4 Emergency category 267 

9.3.9 Facility 267 

9.3.9.1 Facility (network to mobile station direction) 267 

9.3.9.2 Facility (mobile station to network direction) 268 

9.3.9.2.1 SS version 268 

9.3.10 Hold 269 

9.3.11 Hold Acknowledge 269 

9.3.12 Hold Reject 269 

9.3.13 Modify 270 

9.3.13.1 Low layer compatibility 270 

9.3.13.2 High layer compatibility 270 

9.3.13.3 Reverse call setup direction 270 

9.3.13.4 Void 271 

9.3.13.5 Network-initiated Service Upgrade indicator 271 

9.3.14 Modify complete 271 

9.3.14.1 Low layer compatibility 271 

9.3.14.2 High layer compatibility 271 

9.3.14.3 Reverse call setup direction 271 

9.3.15 Modify reject 271 

9.3.15.1 Low layer compatibility 272 

9.3.15.2 High layer compatibility 272 

9.3.16 Notify 272 

9.3.17 Progress 272 

9.3.17.1 User-user 273 

9.3.17a CC-Establishment $(CCBS)$ 273 

9.3.17a.l Void 274 

9.3.17a.2 Setup container 274 

9.3.17b CC-EstabHshment confirmed $(CCBS)$ 274 

9.3. 17b. 1 Repeat indicator 274 

9.3. 17b. 2 Bearer capability 1 and bearer capability 2 274 

9.3.17b.3 Cause 274 

9.3.17b.4 Supported Codecs 274 

9.3.18 Release 275 

9.3.18.1 Release (network to mobile station direction) 275 

9.3.18.1.1 Cause 275 

9.3.18.1.2 Second cause 275 

9.3.18.1.3 Facility 275 

9.3.18.1.4 User-user 275 

9.3.18.2 Release (mobile station to network direction) 275 

9.3.18.2.1 Cause 276 

9.3.18.2.2 Second cause 276 

9.3.18.2.3 Facility 276 

9.3.18.2.4 User-user 276 

9.3.18.2.5 SS version 276 

9.3.18a Recall $(CCBS)$ 276 

9.3.18a.l Recall Type 277 

9.3.18a.2 Facility 277 

9.3.19 Release complete 277 

9.3.19.1 Release complete (network to mobile station direction) 277 

9.3.19.1.1 Cause 278 

9.3.19.1.2 Facility 278 

9.3.19.1.3 User-user 278 

9.3.19.2 Release complete (mobile station to network direction) 278 

9.3.19.2.1 Cause 279 

9.3.19.2.2 Facility 279 

9.3.19.2.3 User-user 279 

9.3.19.2.4 SS version 279 

9.3.20 Retrieve 279 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 4 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.3.21 Retrieve Acknowledge 280 

9.3.22 Retrieve Reject 280 

9.3.23 Setup 281 

9.3.23.1 Setup (mobile terminated call establishment) 281 

9.3.23.1.1 BC repeat indicator 282 

9.3.23.1.2 Bearer capability 1 and bearer capability 2 283 

9.3.23.1.3 Facility 283 

9.3.23.1.4 Progress indicator 283 

9.3.23.1.4a Called party BCD number 283 

9.3.23.1.5 Called party subaddress 283 

9.3.23.1.6 LLC repeat indicator 283 

9.3.23.1.7 Low layer compatibility 1 283 

9.3.23.1.8 Low layer compatibility 11 283 

9.3.23.1.9 HLC repeat indicator 283 

9.3.23.1.10 High layer compatibility i 283 

9.3.23.1.11 High layer compatibility ii 284 

9.3.23.1.12 User-user 284 

9.3.23.1.13 Redirecting party BCD number 284 

9.3.23.1.14 Redirecting party subaddress 284 

9.3.23.1.15 Priority 284 

9.3.23.1.16 Alert $(Network Indication of Alerting in the MS)$ 284 

9.3.23.1.17 Network Call Control Capabilities 284 

9.3.23.1.18 Cause of No CLl 284 

9.3.23.1.19 Backup bearer capability 284 

9.3.23.2 Setup (mobile originating call establishment) 284 

9.3.23.2.1 BC repeat indicator 285 

9.3.23.2.2 Facility 286 

9.3.23.2.3 LLC repeat indicator 286 

9.3.23.2.4 Low layer compatibility 1 286 

9.3.23.2.5 Low layer compatibility 11 286 

9.3.23.2.6 HLC repeat indicator 286 

9.3.23.2.7 High layer compatibility i 286 

9.3.23.2.8 High layer compatibility ii 286 

9.3.23.2.9 User-user 286 

9.3.23.2.10 SS version 286 

9.3.23.2.11 CLIR suppression 286 

9.3.23.2.12 CLIR invocation 287 

9.3.23.2.13 CC Capabilities 287 

9.3.23.2.14 Stream Identifier 287 

9.3.23.2.15 Bearer capability 1 and bearer capability 2 287 

9.3.23.2.16 Supported Codecs 287 

9.3.23.2.17 Redial 287 

9.3.23a Start CC $(CCBS)$ 287 

9.3.23a.l CC Capabilities 287 

9.3.24 Start DTMF 288 

9.3.25 Start DTMF Acknowledge 288 

9.3.25.1 Keypad facility 288 

9.3.26 Start DTMF reject 288 

9.3.27 Status 289 

9.3.27.1 Auxihary states 289 

9.3.28 Status enquiry 289 

9.3.29 Stop DTMF 290 

9.3.30 Stop DTMF acknowledge 290 

9.3.31 User information 291 

9.3.31.1 User-user 291 

9.3.31.2 More data 291 

9.4 GPRS Mobility Management Messages 291 

9.4.1 Attach request 291 

9.4.1.1 Old P-TMSl signature 292 

9.4.1.2 Requested READY timer value 292 

9.4.1.3 TMSl status 292 

9.4.1.4 PS LCS Capability 292 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 5 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.4.2 Attach accept 292 

9.4.2.1 P-TMSI signature 293 

9.4.2.2 Negotiated READY timer 293 

9.4.2.3 Allocated P-TMSI 293 

9.4.2.4 MS identity 293 

9.4.2.5 GMM cause 294 

9.4.2.6 T3302 value 294 

9.4.2.7 Cell Notification (A/Gb mode only) 294 

9.4.2.8 Equivalent PLMNs 294 

9.4.2.9 Network feature support 294 

9.4.2.10 Emergency Number List 294 

9.4.2.11 Requested MS Information 294 

9.4.2.12 T3319 value 294 

9.4.3 Attach complete 294 

9.4.3.1 Inter RAT handover information 295 

9.4.4 Attach reject 295 

9.4.4.1 T3302 value 295 

9.4.5 Detach request 295 

9.4.5.1 Detach request (mobile terminated detach) 295 

9.4.5.1.1 GMM cause 296 

9.4.5.2 Detach request (mobile originating detach) 296 

9.4.5.2.1 P-TMSI 296 

9.4.5.2.2 P-TMSI signature 296 

9.4.6 Detach accept 297 

9.4.6.1 Detach accept (mobile terminated detach) 297 

9.4.6.2 Detach accept (mobile originating detach) 297 

9.4.7 P-TMSI reallocation command 297 

9.4.7.1 P-TMSI signature 298 

9.4.8 P-TMSI reallocation complete 298 

9.4.9 Authentication and ciphering request 298 

9.4.9.1 Authentication Parameter RAND 299 

9.4.9.2 GPRS ciphering key sequence number 299 

9.4.9.3 Authentication Parameter AUTN 299 

9.4.10 Authentication and ciphering response 299 

9.4.10.1 Authentication Response Parameter 300 

9.4.10.2 IMEISV 300 

9.4.10.3 Authentication Response Parameter (extension) 300 

9.4.10a Authentication and Ciphering Failure 300 

9.4. 10a. 1 Authentication Failure parameter 301 

9.4.11 Authentication and ciphering reject 301 

9.4.12 Identity request 301 

9.4.13 Identity response 302 

9.4.14 Routing area update request 302 

9.4.14.1 Old P-TMSI signature 303 

9.4.14.2 Requested READY timer value 303 

9.4.14.3 DRX parameter 303 

9.4.14.4 TMSI status 303 

9.4.14.5 P-TMSI (UMTS only) 303 

9.4.14.6 MS network capability 303 

9.4.14.7 PDP context status 304 

9.4.14.8 PS LCS Capability 304 

9.4.14.9 MBMS context status 304 

9.4.15 Routing area update accept 304 

9.4.15.1 P-TMSI signature 305 

9.4.15.2 Allocated P-TMSI 305 

9.4.15.3 MS identity 305 

9.4.15.4 List of Receive N-PDU Numbers 306 

9.4.15.5 Negotiated READY timer value 306 

9.4.15.6 GMM cause 306 

9.4.15.7 T3302 value 306 

9.4.15.8 Cell Notification (A/Gb mode only) 306 

9.4.15.9 Equivalent PLMNs 306 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 6 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.4.15.10 PDP context status 306 

9.4.15.11 Network feature support 306 

9.4.15.12 Emergency Number List 306 

9.4.15.13 MBMS context status 306 

9.4.15.14 Requested MS Information 306 

9.4.15.15 T3319 value 307 

9.4.16 Routing area update complete 307 

9.4.16.1 List of Receive N-PDU Numbers 307 

9.4.16.2 Inter RAT handover information 307 

9.4.17 Routing area update reject 307 

9.4.17.1 T3302 value 308 

9.4.18 GMM Status 308 

9.4.19 GMM Information 308 

9.4.19.1 Full name for network 309 

9.4.19.2 Short name for network 309 

9.4.19.3 Local time zone 309 

9.4.19.4 Universal time and local time zone 309 

9.4.19.5 LSA Identity 309 

9.4.19.6 Network Daylight Saving Time 309 

9.4.20 Service Request (UMTS only) 310 

9.4.20.1 PDP context status 310 

9.4.20.2 MBMS context status 310 

9.4.20.3 Uplink data status 310 

9.4.21 Service Accept (UMTS only) 310 

9.4.21.1 PDP context status 311 

9.4.21.2 MBMS context status 311 

9.4.22 Service Reject (UMTS only) 311 

9.5 GPRS Session Management Messages 311 

9.5.1 Activate PDP context request 311 

9.5.1.1 Access point name 312 

9.5.1.2 Protocol configuration options 312 

9.5.2 Activate PDP context accept 312 

9.5.2.1 PDP address 313 

9.5.2.2 Protocol configuration options 313 

9.5.2.3 Packet Flow Identifier 313 

9.5.3 Activate PDP context reject 313 

9.5.3.1 Protocol configuration options 314 

9.5.4 Activate Secondary PDP Context Request 314 

9.5.4.1 TFT 314 

9.5.4.2 Protocol configuration options 314 

9.5.5 Activate Secondary PDP Context Accept 315 

9.5.5.1 Packet Flow Identifier 315 

9.5.5.2 Protocol configuration options 315 

9.5.6 Activate Secondary PDP Context Reject 315 

9.5.6.1 Protocol configuration options 316 

9.5.7 Request PDP context activation 316 

9.5.7.1 Protocol configuration options 316 

9.5.8 Request PDP context activation reject 316 

9.5.8.1 Protocol configuration options 317 

9.5.9 Modify PDP context request (Network to MS direction) 317 

9.5.9.1 PDP address 317 

9.5.9.2 Packet Flow Identifier 318 

9.5.9.3 Protocol configuration options 318 

9.5.9.4 TFT 318 

9.5.10 Modify PDP context request (MS to network direction) 318 

9.5.10.1 Requested LLC SAPI 318 

9.5.10.2 Requested new QoS 318 

9.5.10.3 New TFT 319 

9.5.10.4 Protocol configuration options 319 

9.5.11 Modify PDP context accept (MS to network direction) 319 

9.5.11.1 Protocol configuration options 319 

9.5.12 Modify PDP context accept (Network to MS direction) 319 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 7 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.5.12.1 Negotiated QoS 320 

9.5.12.2 Negotiated LLC SAPI 320 

9.5.12.3 New radio priority 320 

9.5.12.4 Packet Flow Identifier 320 

9.5.12.5 Protocol configuration options 320 

9.5.13 Modify PDP Context Reject 320 

9.5.13.1 Protocol configuration options 321 

9.5.14 Deactivate PDP context request 321 

9.5.14.1 Tear down indicator 321 

9.5.14.2 Protocol configuration options 321 

9.5.14.3 MBMS protocol configuration options 322 

9.5.15 Deactivate PDP context accept 322 

9.5.15.1 Protocol configuration options 322 

9.5.15.2 MBMS protocol configuration options 322 

9.5.15a Request Secondary PDP Context Activation 322 

9.5.15.1a TFT 323 

9.5.15.2a Protocol configuration options 323 

9.5.15b Request Secondary PDP Context Activation Reject 323 

9.5.15.1b Protocol configuration options 323 

9.5.16 Void 324 

9.5.17 Void 324 

9.5.18 Void 324 

9.5.19 Void 324 

9.5.20 Void 324 

9.5.21 SM Status 324 

9.5.22 Activate MBMS Context Request 324 

9.5.22.1 MBMS protocol configuration options 325 

9.5.23 Activate MBMS Context Accept 325 

9.5.23.1 MBMS protocol configuration options 325 

9.5.24 Activate MBMS Context Reject 326 

9.5.24.1 MBMS protocol configuration options 326 

9.5.25 Request MBMS Context Activation 326 

9.5.25.1 Linked NSAPl 327 

9.5.25.2 MBMS protocol configuration options 327 

9.5.26 Request MBMS Context Activation Reject 327 

9.5.26.1 MBMS protocol configuration options 327 

10 General message format and information elements coding 327 

10.1 Overview 327 

10.2 Protocol Discriminator 328 

10.3 Skip indicator and transaction identifier 328 

10.3.1 Skip indicator 328 

10.3.2 Transaction identifier 328 

10.4 Message Type 328 

10.5 Other information elements 332 

10.5.1 Common information elements 333 

10.5.1.1 Cell identity 333 

10.5.1.2 Ciphering Key Sequence Number 334 

10.5.1.3 Location Area Identification 334 

10.5.1.4 Mobile Identity 336 

10.5.1.5 Mobile Station Classmark 1 340 

10.5.1.6 Mobile Station Classmark 2 342 

10.5.1.7 Mobile Station Classmark 3 345 

10.5.1.8 Spare Half Octet 356 

10.5.1.9 Descriptive group or broadcast call reference 357 

10.5.1.10 Group Cipher Key Number 358 

10.5.1.10a PD and SAPI $(CCBS)$ 359 

10.5.1.11 Priority Level 360 

10.5.1.12 Core Network System Information (UMTS only) 360 

10.5.1.12.1 CN Common GSM-MAP NAS system information 360 

10.5.1.12.2 CS domain specific system information 361 

10.5.1.12.3 PS domain specific system information 361 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 8 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

10.5.1.13 PLMNlist 362 

10.5.1.14 NAS container for PS HO 363 

10.5.2 Radio Resource management information elements 364 

10.5.3 Mobility management information elements 364 

10.5.3.1 Authentication parameter RAND 364 

10.5.3.1.1 Authentication Parameter AUTN (UMTS authentication challenge only) 364 

10.5.3.2 Authentication Response parameter 365 

10.5.3.2.1 Authentication Response Parameter (extension) (UMTS authentication challenge only) 366 

10.5.3.2.2 Authentication Failure parameter (UMTS authentication challenge only) 366 

10.5.3.3 CM service type 367 

10.5.3.4 Identity type 367 

10.5.3.5 Location updating type 368 

10.5.3.5a Network Name 368 

10.5.3.6 Reject cause 369 

10.5.3.7 Follow-on Proceed 370 

10.5.3.8 Time Zone 371 

10.5.3.9 Time Zone and Time 371 

10.5.3.10 CTS permission 372 

10.5.3.11 LSA Identifier 373 

10.5.3.12 Daylight Saving Time 373 

10.5.3.13 Emergency Number List 374 

10.5.4 Call control information elements 375 

10.5.4.1 Extensions of codesets 375 

10.5.4.2 Locking shift procedure 375 

10.5.4.3 Non-locking shift procedure 376 

10.5.4.4 Auxiliary states 377 

10.5.4.4a Backup bearer capability 378 

10.5.4.4a.l Static conditions for the backup bearer capability IE contents 386 

10.5.4.5 Bearer capability 386 

10.5.4.5.1 Static conditions for the bearer capability IE contents 401 

10.5.4.5a Call Control Capabilities 401 

10.5.4.6 Call state 402 

10.5.4.7 Called party BCD number 403 

10.5.4.8 Called party subaddress 405 

10.5.4.9 Calling party BCD number 406 

10.5.4.10 Calling party subaddress 407 

10.5.4.11 Cause 408 

10.5.4.11a CLIR suppression 413 

10.5.4.11b CLIR invocation 414 

10.5.4.12 Congestion level 414 

10.5.4.13 Connected number 414 

10.5.4.14 Connected subaddress 415 

10.5.4.15 Facility 415 

10.5.4.16 High layer compatibility 416 

10.5.4.16.1 Static conditions for the high layer compatibility IE contents 417 

10.5.4.17 Keypad facility 417 

10.5.4.18 Low layer compatibility 417 

10.5.4.19 More data 417 

10.5.4.20 Notification indicator 418 

10.5.4.21 Progress indicator 418 

10.5.4.21a Recall type $(CCBS)$ 419 

10.5.4.21b Redirecting party BCD number 420 

10.5.4.21c Redirecting party subaddress 420 

10.5.4.22 Repeat indicator 421 

10.5.4.22a Reverse call setup direction 421 

10.5.4.22b SETUP Container $(CCBS)$ 422 

10.5.4.23 Signal 422 

10.5.4.24 SS Version Indicator 423 

10.5.4.25 User-user 423 

10.5.4.26 Alerting Pattern $(NIA)$ 424 

10.5.4.27 Allowed actions $(CCBS)$ 425 

10.5.4.28 Stream Identifier 426 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 9 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

10.5.4.29 Network Call Control Capabilities 426 

10.5.4.30 Cause of No CLl 427 

10.5.4.31 Void 427 

10.5.4.32 Supported codec list 427 

10.5.4.33 Service category 428 

10.5.4.34 Redial 429 

10.5.4.35 Network-initiated Service Upgrade indicator 429 

10.5.5 GPRS mobility management information elements 430 

10.5.5.1 Attach result 430 

10.5.5.2 Attach type 430 

10.5.5.3 Ciphering algorithm 431 

10.5.5.4 TMSl status 432 

10.5.5.5 Detach type 432 

10.5.5.6 DRX parameter 433 

10.5.5.7 Force to standby 435 

10.5.5.8 P-TMSl signature 435 

10.5.5.8a P-TMSI signature 2 436 

10.5.5.9 Identity type 2 436 

10.5.5.10 IMEISV request 437 

10.5.5.11 Receive N-PDU Numbers Hst 437 

10.5.5.12 MS network capability 438 

10.5.5.12a MS Radio Access capability 440 

10.5.5.13 Spare 451 

10.5.5.14 GMM cause 452 

10.5.5.15 Routing area identification 453 

10.5.5.16 Spare 454 

10.5.5.17 Update resuh 454 

10.5.5.18 Update type 455 

10.5.5.19 A&C reference number 456 

10.5.5.20 Service type 456 

10.5.5.21 Cell Notification 457 

10.5.5.22 PS LCS Capability 457 

10.5.5.23 Network feature support 458 

10.5.5.24 Inter RAT information container 459 

10.5.5.25 Requested MS information 460 

10.5.6 Session management information elements 460 

10.5.6.1 Access point name 460 

10.5.6.2 Network service access point identifier 460 

10.5.6.3 Protocol configuration options 461 

10.5.6.4 Packet data protocol address 465 

10.5.6.5 Quality of service 466 

10.5.6.6 SM cause 475 

10.5.6.7 Linked TI 477 

10.5.6.8 Spare 477 

10.5.6.9 LLC service access point identifier 477 

10.5.6.10 Tear down indicator 478 

10.5.6.11 Packet Flow Identifier 478 

10.5.6.12 Traffic Flow Template 479 

10.5.6.13 Temporary Mobile Group Identity (TMGI) 484 

10.5.6.14 MBMS bearer capabilities 484 

10.5.6.15 MBMS protocol configuration options 485 

10.5.6.16 Enhanced network service access point identifier 486 

10.5.7 GPRS Common information elements 486 

10.5.7.1 PDP context status 486 

10.5.7.2 Radio priority 487 

10.5.7.3 GPRS Timer 487 

10.5.7.4 GPRS Timer 2 488 

10.5.7.5 Radio priority 2 488 

10.5.7.6 MBMS context status 489 

10.5.7.7 Uplink data status 490 

11 List of system parameters 491 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 20 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

11.1 Timers and counters for radio resource management 491 

11.2 Timers of mobility management 491 

11.2.1 Timer T3240 and Timer T3241 492 

11.2.2 Timers of GPRS mobility management 493 

11.2.3 Timers of GPRS session management 497 

11.3 Timers of circuit-switched call control 499 

Annex A (informative): Example of subaddress information element coding 501 

Annex B (normative): Compatibility checking 502 

B.l Introduction 502 

B.2 Calling side compatibility checking 502 

B.2.1 Compatibility checking of the CM SERVICE REQUEST message 502 

B.2.2 Compatibility/Subscription checking of the SETUP message 502 

B.3 Called side compatibility checking 502 

B.3.1 Compatibility checking with addressing information 503 

B.3.2 Network-to-MS compatibility checking 503 

B.3. 3 User-to-User compatibility checking 503 

B.4 High layer compatibility checking 503 

Annex C (normative): Low layer information coding principles 504 

C.l Purpose 504 

C.2 Principles 504 

C.2.1 Definition of types of information 504 

C.2. 2 Examination by network 504 

C.2. 3 Location of type I information 505 

C.2.4 Location of types 11 and 111 information 505 

C.2. 5 Relationship between bearer capability and low layer compatibility information elements 505 

Annex D (informative): Examples of bearer capability information element coding 506 

D.l Coding for speech for a full rate support only mobile station 506 

D.1.1 Mobile station to network direction 506 

D.l. 2 Network to mobile station direction 506 

D.2 An example of a coding for modem access with V22-bis, 2,4 kbit/s, 8 bit no parity 507 

D.2.1 Mobile station to network direction, data compression allowed 507 

D.2.2 Network to mobile station direction, data compression possible 508 

D.3 An example of a coding for group 3 facsimile (9,6 kbit/s, transparent) 509 

D.3.1 Mobile station to network direction 509 

D.3.2 Network to mobile station direction 510 

Annex E (informative): Comparison between call control procedures specified in 3GPP TS 

24.008 and ITU-T Recommendation Q.931 511 

Annex F (informative): A/Gb mode specific cause values for radio resource management 515 

Annex G (informative): 3GPP specific cause values for mobility management 516 

G.l Causes related to MS identification 516 

G.2 Cause related to subscription options 516 

G.3 Causes related to PLMN specific network failures and congestion/Authentication Failures 517 

G.4 Causes related to nature of request 517 

G.5 Causes related to invalid messages 517 

G.6 Additional cause codes for GMM 518 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



21 



ETSI TS 124 008 V7.14.0 (2009-03) 



Annex H (informative): 3GPP specific cause values for call control 520 



H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 
H.l 



Normal class 520 

1 Cause No. 1 "unassigned (unallocated) number" 520 

2 Cause No. 3 "no route to destination" 520 

3 Cause No. 6 "channel unacceptable" 520 

4 Cause No. 8 "operator determined barring" 520 

5 Cause No. 16 "normal call clearing" 520 

6 Cause No. 17 "user busy" 520 

7 Cause No. 18 "no user responding" 520 

Cause No. 19 "user alerting, no answer" 520 

9 Cause No. 21 "call rejected" 521 

10 Cause No. 22 "number changed" 521 

11 Cause No. 25 "pre-emption" 521 

12 Cause No. 26 "non-selected user clearing" 521 

13 Cause No. 27 "destination out of order" 521 

14 Cause No. 28 "invalid number format (incomplete number)" 521 

15 Cause No. 29 "facility rejected" 521 

16 Cause No. 30 "response to STATUS ENQUIRY" 521 

17 Cause No. 31 "normal, unspecified" 521 



H.2 Resource unavailable class 521 

H.2.1 Cause No. 34 "no circuit/channel available" 521 

H.2.2 Cause No. 38 "network out of order" 522 

H.2. 3 Cause No. 41 "temporary failure" 522 

H.2.4 Cause No. 42 "switching equipment congestion" 522 

H.2.5 Cause No. 43 "access information discarded" 522 

H.2. 6 Cause No. 44 "requested circuit/channel not available" 522 

H.2. 7 Cause No. 47 "resource unavailable, unspecified" 522 



H.3 Service or option not available class 522 

Cause No. 49 "quality of service unavailable" 522 

Cause No. 50 "Requested facility not subscribed" 522 

Cause No. 55 "Incoming calls barred within the CUG" 522 

Cause No. 57 "bearer capability not authorized" 523 

Cause No. 58 "bearer capability not presently available" 523 

Cause No. 63 "service or option not available, unspecified" 523 

Cause No. 68 "ACM equal to or greater than ACMmax" 523 



H.3.1 
H.3.2 
H.3.3 
H.3.4 
H.3.5 
H.3.6 
H.3.7 

H.4 

H.4.1 
H.4.2 
H.4.3 

H.4.4 



Service or option not implemented class 523 

Cause No. 65 "bearer service not implemented" 523 

Cause No. 69 "Requested facility not implemented" 523 

Cause No. 70 "only restricted digital information bearer capability is available" 523 

Cause No. 79 "service or option not implemented, unspecified" 523 



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

Cause No. 81 "invalid transaction identifier value" 523 

Cause No. 87 "user not member of CUG" 524 

Cause No. 88 "incompatible destination" 524 

Cause No. 91 "invalid transit network selection" 524 

Cause No. 95 "semantically incorrect message" 524 



H.5.1 
H.5.2 
H.5.3 

H.5.4 
H.5.5 

H.6 

H.6.1 

H.6.2 

H.6.3 

H.6.4 

H.6.5 

H.6.6 

H.6.7 

H.6.8 



Protocol error (e.g., unknown message) class 524 

Cause No. 96 "invalid mandatory information" 524 

Cause No. 97 "message type non-existent or not implemented" 524 

Cause No. 98 "message type not compatible with protocol state" 524 

Cause No. 99 "information element non-existent or not implemented" 524 

Cause No. 100 "conditional IE error" 524 

Cause No. 101 "message not compatible with protocol state" 525 

Cause No. 102 "recovery on timer expiry" 525 

Cause No. Ill "protocol error, unspecified" 525 



H.7 Interworking class 525 

H.7.1 Cause No. 127 "interworking, unspecified" 525 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 22 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

Annex I (informative): GPRS specific cause values for GPRS Session Management 526 

1.1 Causes related to nature of request 526 

1.2 Causes related to invalid messages 528 

Annex J (informative): Algorithm to encode frequency list information elements 529 

Annex K (informative): Default Codings of Information Elements 530 

K.l Common information elements 530 

K.2 Radio Resource management information elements 530 

K.3 Mobility management information elements 530 

K.4 Call control information elements 531 

Annex L (normative): Establishment cause (lu mode only) 533 

L.l Mapping of NAS procedure to RRC establishment cause(Iu mode only) 533 

Annex M (normative): Additional Requirements for backward compatibility with PCS 1900 

for NA revision ME 535 

Annex N (normative): Ranking of reject causes for Location Registration (MM and GMM) 

in a shared network 536 

Annex O (normative): 3GPP capability exchange protocol 537 

0.1 Scope 537 

0.2 User-user protocol contents 537 

0.3 Information element identifier 537 

0.4 Information elements 538 

0.4.1 Personal ME identifier 538 

0.4.2 Radio environment capability 539 

0.4.3 UE capability version 539 

0.4.4 IM Status 540 

0.5 Handling of unknown, unforeseen, and erroneous protocol data 541 

0.5.1 General 541 

0.5.2 Not supported lEs, unknown lEIs 541 

0.5.3 Repeated lEs 541 

0.5.4 Syntactically incorrect lEs 542 

0.5.5 Semantically incorrect lEs 542 

Annex P (informative): Change Record 543 

History 551 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



23 



ETSI TS 124 008 V7.14.0 (2009-03) 



Foreword 



This Technical Specification has been produced by the 3' 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: 

X the first digit: 

1 presented to TSG for information; 

2 presented to TSG for approval; 

3 or greater indicates TSG approved document under change control. 

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

z the 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 Phase 2+ Release 96 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 Release 96. 



Feature 


Designator 


BA Range IE handling 


$(impr-BA-range-handling)$ 


Advanced Speech Call Item 


$(ASCI)$ 


Call Completion Busy Subscriber 


${CCBS)$ 


IVIobile Assisted Frequency Allocation 


$(MAFA)$ 


Network Indication of Alerting in MS 


$(NIA)$ 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 24 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 



Scope 



rd 



The present document specifies the procedures used at the radio interface core network protocols within the 3 
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 3GPP TS 24.002 or 3GPP TS 
23.002) for Call Control (CC), Mobihty 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 3GPP TS 44.003 and 3GPP TS 25.301. 

The structured functions and procedures of this protocol and the relationship with other layers and entities are described 
in general terms in 3GPP TS 24.007. 

1.1 Scope 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. 

3GPP TS 24.010 contains functional procedures for support of supplementary services. 

3GPP TS 24.01 1 contains functional procedures for support of point-to-point short message services. 

3GPP TS 24.012 contains functional description of short message - cell broadcast. 

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

3GPP TS 44.071 [23a] contains functional descriptions and procedures for support of location services. 

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

1 .2 Application to the interface structures 

The procedures defined in the present document apply to the interface structures defined in 3GPP TS 44.003 and 
3GPP TS 25.301. They use the functions and services provided by lower layers defined in 3GPP TS 44.005 and 
3GPP TS 44.006 or 3GPP TS 25.331 [23c], 3GPP TS 25.322 and 3GPP TS 25.321. 3GPP TS 24.007 [20] gives the 
general description of layer 3 (A/Gb mode) and Non Access Stratum (lu mode) including procedures, messages format 
and error handling. 

1 .3 Structure of layer 3 procedures 

A building block method is used to describe the layer 3 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 layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" 
is used for these sequences. 

1.4 Test procedures 

Test procedures of the GSM radio interface signalling are described in 3GPP TS 5 1 .010 and 3GPP TS 5 1 .02x series. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 25 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

1 .5 Use of logical channels in A/Gb mode 

The logical control channels are defined in 3GPP TS 45.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 3GPP TS 44.006): 

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 layer 2 
(acknowledged, unacknowledged or random access, see 3GPP TS 44.005 and 3GPP TS 44.006) as required for each 
individual message. 

1 .6 Overview of control procedures 
1.6.1 List of procedures 

The following procedures are specified in the present document: 

a) Clause 4 specifies elementary procedures for Mobility Management: 
mobility management common procedures (subclause 4.3): 
TMSI reallocation procedure (subclause 4.3.1); 
authentication procedure (subclause 4.3.2); 
identification procedure (subclause 4.3.3); 
IMSI detach procedure (subclause 4.3.4); 

- abort procedure (subclause 4.3.5); 

- MM information procedure (subclause 4.3.6). 
mobility management specific procedures (subclause 4.4): 

location updating procedure (subclause 4.4.1); 

- periodic updating (subclause 4.4.2); 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 26 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

IMSI attach procedure (subclause 4.4.3); 

generic location updating procedure (subclause 4.4). 
connection management sublayer service provision: 

mobility management connection establishment (subclause 4.5. 1); 

mobility management connection information transfer phase (subclause 4.5.2); 

mobility management connection release (subclause 4.5.3). 
GPRS specific mobility management procedures (subclause 4.7): 

GPRS attach procedure (subclause 4.7.3); 

GPRS detach procedure (subclause 4.7.4); 

GPRS routing area updating procedure (subclause 4.7.5). 
GPRS common mobility management procedures (subclause 4.7): 

GPRS P-TMSI reallocation procedure (subclause 4.7.6); 

GPRS authentication and ciphering procedure (subclause 4.7.7); 

GPRS identification procedure (subclause 4.7.8); 

GPRS information procedure (subclause 4.7. 12). 

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

mobile originating call establishment (subclause 5.2.1); 

mobile terminating call establishment (subclause 5.2.2); 

signalling procedures during the active state (subclause 5.3): 

user notification procedure (subclause 5.3.1); 

call rearrangements (subclause 5.3.2); 

DTMF protocol control procedure (subclause 5.5.7); 

in-call modification (subclause 5.3.4). 
call clearing initiated by the mobile station (subclause 5.4.3); 
call clearing initiated by the network (subclause 5.4.4); 
miscellaneous procedures: 

in-band tones and announcements (subclause 5.5.1); 

status enquiry procedure (subclause 5.5.3); 

call re-establishment procedure (subclause 5.5.4). 

d) Clause 6 specifies elementary procedures for session management: 

GPRS session management procedures (subclause 6.1): 

PDP context activation (subclause 6.1.3.1 and 6.1.3.2); 

PDP context modification (subclause 6.1.3.3); 

PDP context deactivation (subclause 6.1.3.4). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 27 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- MBMS context activation (subclause 6.1.3.8); 

MBMS context deactivation (subclause 6.1.3.9). 

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

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

1 .7 Applicability 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.1 Voice 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 
Ustening); 

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.2 General Packet Radio Service (GPRS) 

1 .7.2.1 Packet 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 3GPP TS 23.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. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 28 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

NOTE: Other GSM technical specifications may refer to the MS operation modes A, B, and C as GPRS class-A 
MS, GPRS class-B MS, and GPRS class-C 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.2 Packet services in lu mode (lu mode only) 

An MS attached to packet switched domain may operate in one of the following MS operation modes, see 23.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 3GPP TS 23.060 [74]), an MS in PS/CS mode of operation shall use the same 
procedures as for a GPRS MS operating in MS operation mode A, unless it is explicitly stated for A/Gb mode only or 
lu 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 lu mode only. 

NOTE: Network operation mode III is not applicable for lu mode, see 3GPP TS 23.060 [74]. 



References 



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 
non-specific. 

• 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] 3GPP TR 21.905 "Vocabulary for 3GPP Specifications" 

[3] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network 

(PLMN)". 

[4] 3GPP TS 22.003: "Teleservices supported by a Public Land Mobile Network (PLMN)". 

[5] 3GPP TS 42.009: "Security aspects". 

[5a] 3GPP TS 33.102: "3G security; Security architecture". 

[6] 3GPP TS 22.01 1: "Service accessibility". 

[7] 3GPP TS 42.017: "Subscriber Identity Modules (SIM); Functional characteristics". 

[8] 3GPP TS 22.101: "Service aspects; Service principles". 

[8a] 3GPP TS 22.001 : "Principles of circuit telecommunication services supported by a Public Land 

Mobile Network (PLMN)". 



ETSI 



3GPP TS 24.008 version 7.1 4.0 Release 7 29 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

8b] 3GPP TS 23.038: "Alphabets and language-specific information". 

9] 3GPP TS 23.101: "General UMTS Architecture". 

9a] 3GPP TS 23.108: "Mobile radio interface layer 3 specification core network protocols; Stage 2 

(structured procedures)". 

10] 3GPP TS 23.003: "Numbering, addressing and identification". 

1 1 ] 3GPP TS 43 .0 1 3 : "Discontinuous Reception (DRX) in the GSM system" . 

12] 3GPP TS 23.014: "Support of Dual Tone Multi-Frequency (DTMF) signalling". 

12a] ETSI ES 201 235-2, vl .2. 1 : "Specification of Dual Tone Multi-Frequency (DTMF); Transmitters 

and Receivers; Part 2: Transmitters". 

13] 3GPP TS 43.020: "Security-related network functions". 

14] 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode". 

15] 3GPP TS 24.002: "GSM-UMTS PubUc Land Mobile Network (PLMN) access reference 

configuration". 

16] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures 

and access capabilities". 

17] 3GPP TS 44.004: "Layer 1 ; General requirements". 

18] 3GPP TS 44.005: "Data Link (DL) layer; General aspects". 

19] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) 

layer specification". 

19a] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification". 

19b] 3GPP TS 25.322: "Radio Link Control (RLC) protocol specification". 

19c] 3GPP TS 25.413: "UTRAN lu interface RANAP signalling". 

20] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". 

21] 3GPP TS 24.010: "Mobile radio interface layer 3; Supplementary services specification; General 

aspects". 

22] 3GPP TS 24.01 1 : "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio 

interface". 

23] 3GPP TS 24.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio 

interface". 

23a] 3GPP TS 44.071: "Location Services (LCS); Mobile radio interface layer 3 specification." 

23b] 3GPP TS 44.03 1 "Location Services LCS); Mobile Station (MS) - Serving Mobile Location Centre 

(SMLC); Radio Resource LCS Protocol (RRLP)". 

23c] 3GPP TS 25.33 1 : "Radio Resource Control (RRC) protocol specification" 

24] 3GPP TS 24.080: "Mobile radio Layer 3 supplementary service specification; Formats and 

coding". 

25] 3GPP TS 24.081: "Line identification supplementary services; Stage 3". 

26] 3GPP TS 24.082: "Call Forwarding (CF) supplementary services; Stage 3". 

27] 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3". 

28] 3GPP TS 24.084: "MultiParty (MPTY) supplementary services; Stage 3". 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 30 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

[29] 3GPP TS 24.085: "Closed User Group (CUG) supplementary services; Stage 3". 

[30] 3GPP TS 24.086: "Advice of Charge (AoC) supplementary services; Stage 3". 

[31] 3GPP TS 24.088: "Call Barring (CB) supplementary services; Stage 3". 

[32] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". 

[33] 3GPP TS 45.005: "Radio transmission and reception". 

[34] 3GPP TS 45 .008 : "Radio subsystem Hnk control" . 

[35] 3GPP TS 45.010: "Radio subsystem synchronization". 

[36] 3GPP TS 27.001 : "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". 

[36a] 3GPP TS 27.060: "Mobile Station (MS) supporting Packet Switched Services ". 

[37] 3GPP TS 29.002: "Mobile Apphcation Part (MAP) specification". 

[38] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile 

Network (PLMN) and the Integrated Services Digital Network (ISDN) or Pubhc Switched 
Telephone Network (PSTN)". 

[39] 3GPP TS 51.010: "Mobile Station (MS) conformance specification". 

[40] 3GPP TS 51.021: "GSM radio aspects base station system equipment specification". 

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

interchange". 

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

[43] ISO 8348 (1987): "Information technology — Open Systems Interconnection — Network Service 

Definition". 

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

[45] ITU-T Recommendation E. 164: "The international public telecommunication numbering plan". 

[46] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and 

mobile users". 

[47] ITU-T Recommendation F.69 (1993): "The international telex service - Service and operational 

provisions of telex destination codes and telex network identification codes". 

[48] ITU-T Recommendation 1.330: "ISDN numbering and addressing principles". 

[49] ITU-T Recommendation 1.440 (1989): "ISDN user-network interface data link layer - General 

aspects". 

[50] ITU-T Recommendation 1.450 (1989): "ISDN user-network interface layer 3 General aspects". 

[51] ITU-T Recommendation 1.500 (1993): "General structure of the ISDN interworking 

recommendations" . 

[52] ITU-T Recommendation T.50: "International Reference Alphabet (IRA) (Formerly International 

Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information 
interchange". 

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

[54] ITU-T Recommendation V.21: "300 bits per second duplex modem standardized for use in the 

general switched telephone network". 

[55] ITU-T Recommendation V.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". 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 31 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

[56] ITU-T Recommendation V.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-T Recommendation V.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-T Recommendation V.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-T Recommendation V.l 10: "Support by an ISDN of data terminal equipments with V-Series 

type interfaces". 

[61] ITU-T Recommendation V.120: "Support by an ISDN of data terminal equipment with V-Series 

type interfaces with provision for statistical multiplexing". 

[62] ITU-T Recommendation X.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-T Recommendation X.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-T Recommendation X.31: "Support of packet mode terminal equipment by an ISDN". 

[67] Void. 

[68] Void. 

[69] ITU-T Recommendation X. 12 1 : "International numbering plan for public data networks" . 

[70] ETSI ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network interface 

layer 3; Specifications for basic call control". 

[71] ETSI ETS 300 102-2: "Integrated Services Digital Network (ISDN); User-network interface 

layer 3; Specifications for basic call control; Specification Description Language (SDL) 
diagrams". 

[72] ISO/IEC 10646: "Information technology - Universal Multiple-Octet Coded Character Set 

(UCS)". 

[73] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service Description; Stage 1". 

[74] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". 

[75] 3GPP TS 43.064: "General Packet Radio Service (GPRS); Overall description of the GPRS radio 

interface; Stage 2". 

[76] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station 

System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". 

[77] IETF RFC 1034: "Domain names - concepts and facilities". 

[78] 3GPP TS 44.065: "Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork 

Dependent Convergence Protocol (SNDCP)". 

[78a] 3GPP TS 44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link 

Control (LLC) Layer Specification". 

[79] ITU Recommendation 1.460: "Multiplexing, rate adaption and support of existing interfaces". 



ETSI 



3GPP TS 24.008 version 7.1 4.0 Release 7 32 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

[80] 3GPP TS 26. 1 1 1 : "Codec for Circuit Switched Multimedia Telephony Service; Modifications to 

H.324". 

[81] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture". 

[82] 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive 

mode". 

[83] 3GPP TS 26.103: "Speech Codec List for GSM and UMTS". 

[84] 3GPP TS 44.018: "Mobile radio interface layer 3 specification, Radio Resource Control Protocol". 

[85] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) 

interface; layer 3 specification". 

[86] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving 

GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". 

[87] 3GPP TS 43.055: "Dual Transfer Mode (DTM); Stage 2". 

[88] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2". 

[88a] 3GPP TS 23.093: "Technical realization of Completion of Calls to Busy Subscriber (CCBS); 

Stage 2". 

[89] 3GPP TS 22.042: "Network Identity and Time Zone (NITZ), Stage 1 ". 

[90] 3GPP TS 23.040: "Technical reaHzation of Short Message Service (SMS)". 

[91] 3GPP TS 44.056: "GSM Cordless Telephony System (CTS), (Phase 1) CTS Radio Interface Layer 

3 Specification". 

[92] 3GPP TS 23.226: "Global Text Telephony; Stage 2 " 

[93] 3GPP TS 26.226: "Cellular Text Telephone Modem (CTM), General Description " 

[94] 3GPP TS 23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" 

[95] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP" 

[96] 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2". 

[97] 3GPP TS 23.172: "UDI/RDI Fallback and Service Modification; Stage 2". 

[98] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected 

Mode" 

[99] RFC 3513 (April 2003): "Internet Protocol Version 6 (IPv6) Addressing Architecture". 

[100] 3GPP TS 29.207: "Policy control over Go interface". 

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

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

[103] RFC 3232 (January 2002): "Assigned Numbers: RFC 1700 is Replaced by an On-Une Database". 

[ 1 04] 3GPP TS 23 .034: "High Speed Circuit Switched Data (HSCSD) - Stage 2" . 

[105] 3GPP TS 23.271: "Functional stage 2 description of LCS". 

[106] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and Functional 

Description". 

[107] RFC 3376 (October 2002): "Internet Group Management Protocol, Version 3". 

[108] RFC 2710 (October 1999): "Multicast Listener Discovery (MLD) for IPv6". 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 33 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

109] 3GPP TS 23.251: "Network Sharing; Architecture and Functional Description". 

1 10] 3GPP TS 25.346: Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the 

Radio Access Network' 

111] 3GPP TS 44. 1 1 8 : "Radio Resource Control (RRC) protocol; lu mode" . 

112] 3GPPTS 31.102: "Characteristics of the USIM AppHcation". 

113] 3GPP TS 43.129: "Packet-switched handover for GERAN A/Gb mode; Stage 2". 

1 14] 3GPP TS 23.009: "Handover procedures". 

1 15] 3GPP TR 23.903: " Redial solution for voice-video switching". 

1 16] 3GPP TS 24.279: "Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) 

services, stage 3" 

2.1 Definitions and abbreviations 

For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 [2a] and the followings apply: 
TMGI Temporary Mobile Group Identity 

2.1.1 Random 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.2.2 Vocabulary 

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 consists of the GSM ciphering key and 
the 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 consists of the UMTS ciphering key, 
the UMTS integrity key, the GSM ciphering key and the cipher key sequence number. 

idle mode: In this mode, the mobile station is not allocated any dedicated channel; it listens to the CCCH and the 
BCCH; 

group receive mode: (only applicable for mobile stations supporting VGCS listening or VBS listening) In this 
mode, the mobile station is not allocated a dedicated channel with the network; it listens to the downlink of a 
voice broadcast channel or voice group call channel allocated to the cell. Occasionally, the mobile station has to 
Usten to the BCCH of the serving cell as defined in 3GPP TS 43.022 [82] and 3GPP TS 45.008 [34]; 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 34 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

dedicated mode: In this mode, the mobile station is allocated at least two dedicated channels, only one of them 
being a SACCH; 

group transmit mode: (only applicable for mobile stations supporting VGCS talking) In this mode, one mobile 
station of a voice group call is allocated two dedicated channels, one of them being a SACCH. These channels 
can be allocated to one mobile station at a time but to different mobile stations during the voice group call; 

packet idle mode: (only applicable for mobile stations supporting GPRS) In this mode, mobile station is not 
allocated any radio resource on a packet data physical channel; it listens to the PBCCH and PCCCH or, if those 
are not provided by the network, to the BCCH and the CCCH, see 3GPP TS 44.060 [76]. 

packet transfer mode: (only applicable for mobile stations supporting GPRS) In this mode, the mobile station is 
allocated radio resource on one or more packet data physical channels for the transfer of LLC PDUs. 

main DCCH: In Dedicated mode and group transmit mode, only two channels are used as DCCH, one being a 
SACCH, the other being a SDCCH or a FACCH; the SDCCH or FACCH is called here "the main DCCH"; 

A channel is activated if it can be used for transmission, in particular for signalling, at least with UI frames. On 
the SACCH, whenever activated, it must be ensured that a contiguous stream of layer 2 frames is sent; 

A TCH is connected if circuit mode user data can be transferred. A TCH cannot be connected if it is not 
activated. A TCH which is activated but not connected is used only for signalling, i.e. as a DCCH; 

The data link of SAPI on the main DCCH is called the main signalling link. Any message specified to be sent 
on the main signalling link is sent in acknowledged mode except when otherwise specified; 

- The term "to establish" a link is a short form for "to establish the multiframe mode" on that data link. It is 
possible to send UI frames on a data link even if it is not established as soon as the corresponding channel is 
activated. Except when otherwise indicated, a data link layer establishment is done without an information field. 

"channel set" is used to identify TCHs that carry related user information flows, e.g., in a multislot 
configuration used to support circuit switched connection(s), which therefore need to be handled together. 

A temporary block flow (TBF) is a physical connection used by the two RR peer entities to support the uni- 
directional transfer of LLC PDUs on packet data physical channels, see 3GPP TS 44.060 [76]. 

- RLC/MAC block: A RLC/MAC block is the protocol data unit exchanged between RLC/MAC entities, see 
3GPPTS 44.060 [76]. 

A GMM context is established when a GPRS attach procedure is successfully completed. 

- Network operation mode 

The three different network operation modes I, II, and III are defined in 3GPP TS 23.060 [74]. 

The network operation mode shall be indicated as system information. For proper operation, the network 
operation mode should be the same in each cell of one routing area. 

- GPRS MS operation mode 

The three different GPRS MS operation modes A, B, and C are defined in 3GPP TS 23.060 [74]. 

RR connection: A RR connection is a dedicated physical circuit switched domain connection used by the two 
RR or RRC peer entities to support the upper layers' exchange of information flows. 

PS signalling connection is a peer to peer lu mode connection between MS and CN packet domain node. 

Inter-System change is a change of an MS from A/Gb mode to lu mode of operation or vice versa. 

GPRS: Packet Services for systems which operate the Gb or lu-PS interfaces. 

The label (A/Gb mode only) indicates this section or paragraph applies only to a system which operates in A/Gb 
mode, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the 
radio access network and the core network. For multi system case this is determined by the current serving radio 
access network. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 35 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The label (lu mode only) indicates this section or paragraph applies only to a system which operates in lu 
mode. The lu mode includes UTRAN and GERAN lu modes, i.e. with a functional division that is in accordance 
with the use of an lu-CS or lu-PS interface between the radio access network and the core network. For multi 
system case this is determined by the current serving radio access network. 

In A/Gb mode,... Indicates this paragraph applies only to a system which operates in A/Gb mode. For multi 
system case this is determined by the current serving radio access network. 

In lu mode,... Indicates this paragraph applies only to a system which operates in lu mode. The lu mode 
includes both UTRAN lu mode and GERAN lu mode. For multi system case this is determined by the current 
serving radio access network. 

In A/Gb mode and GERAN lu mode,... Indicates this paragraph applies only to a system which operates in 
A/Gb mode or GERAN lu mode. For multi system case this is determined by the current serving radio access 
network. 

In UTRAN lu mode,... Indicates this paragraph applies only to a system which operates in UTRAN lu mode. 
For multi system case this is determined by the current serving radio access network. 

In a shared network,... Indicates this paragraph applies only to a shared network. For the definition of shared 
network see 3GPP TS 23.122 [14]. 

- SIM, Subscriber Identity Module (see 3GPP TS 42.017 [7]). 

- USIM, Universal Subscriber Identity Module (see 3GPP TS 21. Ill [101]). 

MS, Mobile Station. The present document makes no distinction between MS and UE. 

Cell Notification is an (optimised) variant of the Cell Update Procedure which uses the LLC NULL frame for 
cell change notification which does not trigger the restart of the READY timer 

- DTM: dual transfer mode, see 3GPP TS 44.018 [84] and 3GPP TS 43.055 [87] 



3 Radio Resource management procedures 

See 3GPPTS 44.018 [84]. 

4 Elementary procedures for Mobility Management 
4.1 General 

This clause describes the procedures used for mobility management for non-GPRS services and for GPRS -services at 
the radio interface (Reference Point Um and Uu). 

The main function of the Mobility Management sublayer is to support the mobility of user terminals, such as informing 
the network of its present location and providing user identity confidentiality. 

A further function of the MM sublayer is to provide connection management services to the different entities of the 
upper Connection Management (CM) sublayer (see 3GPP TS 24.007). 

There are two sets of procedures defined in this chapter: 

MM procedures for non-GPRS services (performed by the MM entity of the MM sublayer); and 

GMM procedures for GPRS services (performed by the GMM entity of the MM sublayer), see 
3GPPTS 24.007 [20]. 

All the MM procedures described in this clause can only be performed if a RR connection has been established between 
the MS and the network. Else, the MM sublayer has to initiate the establishment of a RR connection (see 3GPP TS 
44.018 [84] clause 3.3 and 3GPP TS 25.331 [23c]). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 36 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

In A/Gb mode, the GMM procedures described in this clause, use services provided by the RR sublayer without prior 
RR connection establishment. 

In lu mode: all the GMM procedures described in this clause can only be performed if a PS signalling connection has 
been established between the MS and the network. Else, the GMM sublayer has to initiate the establishment of a PS 
signalling connection (see 3GPP TS 25.331 [23c]). 

GMM procedures are mandatory and applicable only for GPRS MSs and networks supporting those MSs. For GPRS 
MSs which are IMSI attached for both GPRS and non-GPRS services, some MM procedures are replaced by GMM 
combined procedures provided that the network operates in network operation mode I, i.e. is supporting combined 
GMM procedures. GMM combined procedures are not applicable for the GPRS MS operation mode C but are 
mandatory for the GPRS MS operation modes A and B and networks supporting network operation mode I, see 
3GPPTS 23.060 [74]. 

4.1 .1 MM and GMM procedures 

4.1 .1 .1 Types of MM and GMM procedures 

Depending on how they can be initiated, three types of MM procedures can be distinguished: 

1) MM common procedures: 

A MM common procedure can always be initiated whilst a RR connection exists. The procedures belonging to 
this type are: 

Initiated by the network: 

TMSI reallocation procedure; 

authentication procedure; 

identification procedure; 

- MM information procedure; 

abort procedure. 

However, abort procedure is used only if an MM connection is being established or has already been established i.e. not 
during MM specific procedures or during IMSI detach procedure, see subclause 4.3.5. 

Initiated by the mobile station: 

IMSI detach procedure (with the exceptions specified in subclause 4.3.4). 

2) MM specific procedures: 

A MM specific procedure can only be initiated if no other MM specific procedure is running or no MM 
connection exists. The procedures belonging to this type are: 

normal location updating procedure; 

- periodic updating procedure; 

- IMSI attach procedure. 

3) MM connection management procedures: 

These procedures are used to establish, maintain and release a MM connection between the mobile station and the 
network, over which an entity of the upper CM layer can exchange information with its peer. A MM connection 
establishment can only be performed if no MM specific procedure is running. More than one MM connection may be 

active at the same time. 

Depending on how they can be initiated, three types of GMM procedures can be distinguished: 
1) GMM common procedures: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 37 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

In lu mode, a GMM common procedure can always be initiated whilst a PS signalling connection exists. 
The procedures belonging to this type are: 

Initiated by the network when a GMM context has been established: 

- P-TMSI (re-) allocation; 

GPRS authentication and ciphering; 

- GPRS identification; 
GPRS information. 

2) GMM specific procedures: 

Initiated by the network and used to detach the IMSI in the network for GPRS services and/or non-GPRS 
services and to release a GMM context: 

- GPRS detach. 

Initiated by the MS and used to attach or detach the IMSI in the network for GPRS services and/or non- 
GPRS services and to establish or release a GMM context: 

- GPRS attach and combined GPRS attach; 

- GPRS detach and combined GPRS detach. 

Initiated by the MS when a GMM context has been established: 

normal routing area updating and combined routing area updating; 

- periodic routing area updating. 

3) GMM connection management procedures (lu mode only): 

Initiated by the MS and used to establish a secure connection to the network and/or to request the resource 
reservation for sending data: 

Service Request. 

The Service Request procedure can only be initiated if no MS initiated GMM specific procedure is ongoing. 



4.1 .1 .1 .1 Integrity Checking of Signalling Messages in the Mobile Station (lu mode only) 

In lu mode only, integrity protected signalling is mandatory with one exception regarding emergency calls (see 
subclause 4.1.1.1.1a). In lu mode only, all layer 3 protocols shall use integrity protected signalling once the security 
mode procedure has been successfully activated in the network and the MS. Integrity protection of all layer 3 signalling 
messages is the responsibility of lower layers. It is the network which activates integrity protection. This is done using 
the security mode control procedure (3GPP TS 25.331 [23c] and 3GPP TS 44.118 [111]). 

The supervision that integrity protection is activated shall be the responsibility of the MM and GMM layer in the MS 
(see 3GPP TS 33.102 [5a]). In order to do this, the lower layers shall provide the MM and GMM layer with an 
indication on when the integrity protection is activated in the MS (i.e. one indication to the MM layer when a security 
mode control procedure for the CS domain is processed successfully and one indication to the GMM layer when a 
security mode control procedure for the PS domain is processed successfully). 

The CS and PS domains in the network and the MM and GMM layers in the MS, are not aware of whether integrity 
protection has been started in the lower layers by the other domain. It is mandatory for the network to initiate one 
security mode control procedure for the CS domain and one for the PS domain. 

Except the messages listed below, no layer 3 signalling messages shall be processed by the receiving MM and GMM 
entities or forwarded to the CM entities, unless the security mode control procedure is activated for that domain. 

MM messages: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 38 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- AUTHENTICATION REQUEST 

- AUTHENTICATION REJECT 

- IDENTITY REQUEST 

- LOCATION UPDATING ACCEPT (at periodic location update with no change of location area or 
temporary identity) 

- LOCATION UPDATING REJECT 

- CM SERVICE ACCEPT, if the following two conditions apply: 

no other MM connection is established; and 

- the CM SERVICE ACCEPT is the response to a CM SERVICE REQUEST with CM SERVICE 
TYPE IE set to "emergency call establishment" 

- CM SERVICE REJECT 

- ABORT 
GMM messages: 

- AUTHENTICATION & CIPHERING REQUEST 

- AUTHENTICATION & CIPHERING REJECT 

- IDENTITY REQUEST 

- ATTACH REJECT 

ROUTING AREA UPDATE ACCEPT (at periodic routing area update with no change of routing area or 
temporary identity) 

- ROUTING AREA UPDATE REJECT 

- SERVICE REJECT 

- DETACH ACCEPT (for non power-off) 
CC messages: 

all CC messages, if the following two conditions apply: 
no other MM connection is established; and 

- the MM entity in the MS has received a CM SERVICE ACCEPT message with no ciphering or 
integrity protection applied as response to a CM SERVICE REQUEST message, with CM SERVICE 
TYPE set to "Emergency call establishment" sent to the network. 

The receiving layer 3 entity in the MS shall not process any other layer 3 signalling messages unless they have been 
successfully integrity checked by the lower layers once integrity protection is activated. If any signalling messages, 
having not successfully passed the integrity check, are received, then the lower layers in the MS shall discard that 
message (see 3GPP TS 25.331 [23c] and 3GPP TS 44.118 [111]). If any layer 3 signalling message is received, in either 
PS or CS domains, as not integrity protected even though the integrity protection has been activated in the MS by that 
domain in the network, then the lower layers shall discard this message (see 3GPP TS 25.331 [23c] and 3GPP TS 
44.118 [111]). 

Integrity checking on the network side is performed by the RNC and is described in 3GPP TS 25.331 [23c] and 3GPP 
TS 44.118 [111]. 

4.1.1.1.1a Integrity protection for emergency call (lu mode only) 

The network should initiate the security mode procedure for an emergency call, in the same way as it would for any 
other call except in the cases defined in sub-clause "Security Procedures Not Applied" in 3GPP TS 33.102 [5a]. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 39 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

For the establishment of a MM connection for an emergency call when no other MM connection is established (e.g. for 
an emergency call initiated without a SIM/USIM no other MM connections can exist) the decision on whether or not to 
apply the security procedures shall be made by the network as defined in the sub-clause "Emergency Call Handling" in 
3GPPTS 33.102 [5a]. 

4.1 .1 .2 MM-GMM co-ordination for GPRS MS's 

4.1 .1 .2.1 GPRS MS operating in mode A or B in a network that operates in mode I 

If the network operates in mode I, GPRS MSes that operate in mode A or B and wish to be or are simultaneously IMSI 
attached for GPRS and non-GPRS services, shall use the combined GPRS attach and the combined and periodic routing 
area updating procedures instead of the corresponding MM specific procedures IMSI attach and normal and periodic 
location area updating. 

NOTE 1 : A GPRS MS operating in mode A or B in a network that operates in mode I, shall perform the combined 
GPRS attach or routing area update procedure regardless the value of the ATT flag. 

If a GPRS MS is operating in mode A or B in a network that operates in mode I the IMSI detach shall be performed by 
the GMM using the combined GPRS detach procedure. 

NOTE 2: A GPRS MS operating in mode A or B in a network that operates in mode I, shall perform the combined 
GPRS detach procedure regardless the value of the ATT flag. 

A GPRS MS operating in mode A or B in network that operates in mode I, shall use the combined GMM specific 
procedures in place of the MM specific procedures unless the re-activation of the MM specific procedures is explicitly 
described, so all conditions describing when to trigger an MM specific procedure listed in subclauses 4.3 and 4.4 shall 
not apply. 

A GPRS MS operating in mode A or B in a network that operates in mode I should not use any MM timers relating to 
MM specific procedures, (e.g. T3210, T3211, T3212, T3213) unless the re-activation of the MM specific procedures is 
explicitly described. If the MM timers are already running, the MS should not react on the expiration of the timers. 

NOTE 3: Whenever GMM performs a combined GMM procedure, a GPRS MS enters the MM state MM 

LOCATION UPDATING PENDING in order to prevent the MM from performing a location area 
updating procedure. 

If the authentication procedure is performed by MM and the authentication is rejected by the network (i.e. upon receive 
of AUTHENTICATION REJECT), the MS shall in addition set the GPRS update status to GU3 ROAMING NOT 
ALLOWED and shall, if available, delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number stored. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or 
the SIM/USIM is removed. The MS shall abort any GMM procedure and shall enter state GMM-DEREGISTERED. 

If the PS or CS domain is barred because of domain specific access control, a GPRS MS operating in mode A or B in a 
network that operates in mode I shall act as if in network operation mode II or III (depending on whether a PCCCH is 
present in Gb-mode) and access to the barred domain shall be stopped entirely. If the MS detects that a domain is 
barred, this shall not trigger any MM or GMM specific procedure. 

A GPRS MS operating in mode A or B in a network that operates in mode I shall perform a normal location updating 
procedure (in order to remove the Gs association in the MSC/VLR) when the following conditions are fulfilled: 

the GPRS MS has camped on a cell where the PS domain is barred and the CS domain is unbarred; and 

- T33 12, T33 1 1 , T3302, or T3330 expires; and 

for the last attempt to update the registration of the location area a combined GMM procedure was performed. 

Additionally the MS shall treat the expiry of T33 12 when the PS domain changes from barred to unbarred, analogous to 
the descriptions for the cases when the timer expires out of coverage or in a cell that does not support GPRS (see 
subclause 4.7.2.2). 

If timer T3312 expires and both the PS and CS domain are barred, then a GPRS MS operating in mode A or B in a 
network that operates in mode I shall treat the expiry of T3312 when the GPRS MS detects that the PS or CS domain 
becomes unbarred, analogous to the descriptions for the cases when the timer expires out of coverage (see subclause 
4.7.2.2). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 40 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the PS domain is barred and timer T3312 expires during an ongoing CS connection, then a GPRS MS operating in 
mode A or B in a network that operates in mode I shall treat the expiry of T3312 when the MM state MM -IDLE is 
entered, analogous to the descriptions for the cases when the timer expires out of coverage or in a cell that does not 
support GPRS (see subclause 4.7.2.2), or in a cell where the PS domain is barred. 

A GPRS MS operating in mode A or B in a network that operates in mode I shall perform a combined routing area 
update procedure indicating "combined RA/LA updating with IMSI attach" (in order to establish the Gs association in 
the MSC/VLR) when the following conditions are fulfilled: 

the GPRS MS detects that CS or PS domain or both change from barred to unbarred; 

as a result of the change of the domain specific barring status, both domains are unbarred; and 

for the last attempt to update the registration of the location area an MM specific procedure was performed (see 
subclause 4.7.5.2.1) or for the last attempt to update the registration of the routing area a normal routing area 
update was performed. 

4.1 .1 .2.2 GPRS MS operating in mode A or B in a network that operates in mode II or III 

If the network operates in mode II or III, a GPRS MSs that operate in mode A or B and wish to be or are simultaneously 
IMSI attached for GPRS and non-GPRS services, shall use the MM specific procedures listed in subclauses 4.3 and 4.4 
and the GMM specific procedures listed in subclauses 4.7.3, 4.7.4 and 4.7.5. The applicability of periodic location 
updating is further specified in subclause 4.4.2 and the periodic routing area updating is specified in subclause 4.7.2.2. 

If the authentication procedure is performed by MM and the authentication is rejected by the network (i.e upon receive 
of AUTHENTICATION REJECT), the MS shall in addition set the GPRS update status to GU3 ROAMING NOT 
ALLOWED and shall, if available, delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number stored. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or 
the SIM/USIM is removed. The MS shall abort any GMM procedure and shall enter state GMM-DEREGISTERED. 

If the PS or CS domain is barred because of domain specific access control, a GPRS MS operating in mode A or B in a 
network that operates in mode II or III shall use the MM specific procedures or GMM specific procedures, respectively, 
in the domain which is unbarred. If the MS detects that a domain changes from barred to unbarred, it shall behave as 
specified in subclauses 4.3.4.4, 4.4.4.9, 4.5.1.2, 4.7.3.1.5, 4.7.4.1.4, 4.7.5.1.5, and 4.7.13.5. 

4.1 .1 .3 Core Network System Information for MM (lu mode only) 

In the network broadcast system information some of the system information is used by MM. 

At reception of new system information, the RRC layer in the MS delivers the contents of the CN common system 
information and the CS domain specific system information to the MM layer in the MS. 

The Core Network system information is included in specific information elements within some RRC messages sent to 
MS (see 3GPP TS 25.331 [23c] and 3GPP TS 44.118 [111]). In the Core Network system information the Common 
system information part and the CS domain specific system information part contains settings of parameters controlling 
MM functionality. No MM messages contain the Core Network System Information. 

4.1 .1 .4 Core Network System Information for GMM (lu mode only) 

In the network broadcast system information some of the system information is used by GMM. 

At reception of new system information, the RRC layer in the MS delivers the contents of the CN common system 
information and the PS domain specific system information to the GMM layer in the MS. 

The Core Network system information is included in specific information elements within some RRC messages sent to 
MS (see 3GPP TS 25.331 [23c] and 3GPP TS 44.1 18 [111]). In the Core Network system information the Common 
system information part and the PS domain specific system information part contains settings of parameters controlling 
GMM functionality. No GMM messages contain the Core Network System Information. 



4.1 .2 MM sublayer states 



The description of the states for the MM sublayer is organized as follows. The main states for the MS side, related to 
the procedures, are described in subclause 4.1.2.1.1. The MM IDLE state is subdivided in substates for the description 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 41 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

of the behaviour in idle mode (subclause 4.1.2.1.2). This behaviour depends on an update status, described in 
subclause 4.1.2.2. The states for the network side are described in subclause 4.1.2.3. 

4.1 .2.1 MM sublayer states in the mobile station 

In this subclause, the possible states for the MM sublayer in the mobile station is described. In figure 4. 1 of the present 
document, an overview of the MM sublayer protocol is given. 

4.1.2.1.1 Main States 

NULL 

The mobile station is inactive (e.g. power down). Important parameters are stored. Only manual action by the 
user may transfer the MM sublayer to another state. 

3 LOCATION UPDATING INITIATED 

A location updating procedure has been started and the MM awaits a response from the network. The timer 
T3210 is running. 

5 WAIT FOR OUTGOING MM CONNECTION 

The MM connection establishment has been started, and the MM awaits a response from the network. The 
timer T3230 is running. 

6 MM CONNECTION ACTIVE 

The MM sublayer has a RR connection to its peer entity on the network side. One or more MM connections 
are active. 

7 IMSI DETACH INITIATED 

The IMSI detach procedure has been started. The timer T3220 is running. 

8 PROCESS CM SERVICE PROMPT 

The MM sublayer has a RR connection to its peer entity on the network side. The Mobile Station has 
received a CM SERVICE PROMPT message but has not yet responded $(CCBS)$. 

9 WAIT FOR NETWORK COMMAND 

The MM sublayer has a RR connection to its peer entity in the network, but no MM connection is 
established. The mobile station is passive, awaiting further commands from the network. The timer T3240 
may be running. 

10 LOCATION UPDATE REJECTED 

A location updating procedure has been rejected and RR connection release is awaited. The timer T3240 is 
running. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



42 



ETSI TS 124 008 V7.14.0 (2009-03) 



14 
WAIT FOR 
RR CONNECTION 
(MM CONNECTION) 






Request 
RR connection 




'^v 



RR connection 
established 



states 3, 5, 9, 
10,13,14,15 



Attach or L o catio n 
update needed 



Send cm service 
r e q u e St 



I 



WAIT FOR 
OUTGOING 
MM CONNECTION 



CIph erln g started 

or CM servic e 

accept 



Confi rm 
MM connection 



MM CONNECTION 
ACTIVE 



r^ 



Indicate 
M M connection 




First message 
received 



Figure 4.1a/3GPP TS 24.008: Overview mobility management protocol/MS Side 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



43 



ETSI TS 124 008 V7.14.0 (2009-03) 



21 
MM CONNECTION 
ACTIVE 



(Group TX MODE ) 



RR gone to 
Group Transmit 
mode 



RR Connection 



established 



22 
WAIT FOR RR 
CONNECTION 
(Group TX MODE 




Uplink 

access 

requested 



mode 



19' 
MM-IDLE 



MM CONNECTION 
ACTIVE 



RR connection 

released, gone 

to group receive 

Mode 



RR connection 

released, gone 

to Group Receive 

mode 



WAIT FOR 
OUTGOING 
MM CONNECTION 



Send CM service 
request 

or 

Notification Response 



Additions to Figure 4.1.a/3GPP TS 24.008 

13. WAIT FOR RR CONNECTION (LOCATION UPDATING) 

The MM sublayer has requested RR connection establishment for starting the location updating procedure. 

14. WAIT FOR RR CONNECTION (MM CONNECTION) 

The MM sublayer has requested RR connection establishment for dedicated mode for starting the MM 
connection establishment. 

15. WAIT FOR RR CONNECTION (IMSI DETACH) 

The MM sublayer has requested RR connection establishment for starting the IMSI detach procedure. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 44 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

17. WAIT FOR REESTABLISH 

A lower layer failure has occurred and re-establishment may be performed from the disturbed CM layer 
entities. 

18. WAIT FOR RR ACTIVE 

The MM sublayer has requested activation of the RR sublayer. 

19. MM IDLE 

There is no MM procedure running and no RR connection exists except that a local MM context may exist 
when the RR sublayer is in Group Receive mode. This is a compound state, and the actual behaviour of the 
mobile station to Connection Management requests is determined by the actual substate as described 
hereafter. 

20. WAIT FOR ADDITIONAL OUTGOING MM CONNECTION. 

The MM connection establishment for an additional MM connection has been started, and the MM awaits 
response from the network. 

21. MM CONNECTION ACTIVE (GROUP TRANSMIT MODE) 

(Only applicable for mobile stations supporting VGCS talking:) The MM sublayer has a RR connection on 
the VGCS channel to its peer entity on the network side. Only one MM connection is active. 

22. WAIT FOR RR CONNECTION (GROUP TRANSMIT MODE) 

(Only applicable for mobile stations supporting VGCS talking:) The MM sublayer has requested to perform 
an uplink access on the VGCS channel. 

23. LOCATION UPDATING PENDING 

(Only applicable for GPRS MS operation modes A and B; not shown in figure 4.1a) A location updating has 
been started using the combined GPRS routing area updating procedure. 

24. IMSI DETACH PENDING 

(Only applicable for GPRS MS operation modes A and B; not shown in figure 4.1a) An IMSI detach for non- 
GPRS services has been started using the combined GPRS detach procedure at not switching off. 

25. RR CONNECTION RELEASE NOT ALLOWED 

(Only applicable for mobile stations supporting RRLP procedures (see 3GPP TS 44.031 [23b]) or LCS 
procedures over RRC (see 3GPP TS 25.331 [23c])). All MM connections are released by their CM entities, 
but the RR connection is maintained by the network due to an ongoing RRLP procedure or LCS procedure 
over RRC. 

4.1 .2.1 .2 Substates of the MM IDLE state 

For the description of the behaviour of the MS the MM IDLE state is subdivided in several substates, also called the 
service states. The service state pertains to the whole MS (ME alone if no SIM/USIM is inserted, or ME plus 
SIM/USIM). The service state depends on the update status (see subclause 4.1.2.2) and on the selected cell. 

19.1 NORMAL SERVICE 

Valid subscriber data are available, update status is Ul, a cell is selected that belongs to the LA where the 
subscriber is registered. 

In this state, all requests from the CM layers are treated normally. 

19.2 ATTEMPTING TO UPDATE 

Valid subscriber data are available, update status is U2 and a cell is selected. Requests from upper layers are 
accepted. Emergency call requests are treated normally, otherwise the request triggers first a location 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 45 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

updating attempt in the selected cell, and then triggers the needed procedure only in case of successful 
location updating, otherwise the request is rejected. 

19.3 LIMITED SERVICE 

Valid subscriber data are available, update status is U3, and a cell is selected, which is known not to be able 
to provide normal service. Only emergency services are offered. 

19.4 NO IMSI 

No valid subscriber data (no SIM/USIM, or the SIM/USIM is not considered valid by the ME), and a cell is 
selected. Only emergency services are offered. 

19.5 NO CELL AVAILABLE 

No cell can be selected. This state is entered after a first intensive search failed (state 19.7). Cells are 
searched at a low rhythm. No services are offered. 

19.6 LOCATION UPDATE NEEDED 

Valid subscriber data are available, and for some reason a location updating must be done as soon as possible 
(for instance update status is Ul but the selected cell is not in the registered LA, or the timer has expired, ...). 
This state is usually of no duration, but can last, e.g., if the access class is blocked due to common access 
class control or CS domain specific access control (see subclause 4.1.1.2.1). 

19.7 PLMN SEARCH 

The mobile station is searching for PLMNs, and the conditions for state 19.8 are not met. This state is ended 
when either a cell is selected (the new state is 19.1, 19.3 or 19.6), or when it is concluded that no cell is 
available for the moment (the new state is 19.5). 

19.8 PLMN SEARCH, NORMAL SERVICE 

Valid subscriber data are available, update status is Ul, a cell is selected which belongs to the LA where the 
subscriber is registered, and the mobile station is searching for PLMNs. This state is ended when either a cell 
is selected (the new state is 19.1, 19.3 or 19.6), or when it is concluded that no cell is available for the 
moment (the new state is 19.5). 

19.9 RECEIVING GROUP CALL (NORMAL SERVICE) 

Only applicable for mobile stations supporting VGCS listening or VBS listening. Valid subscriber data are 
available, update status is Ul, a VGCS channel or VBS channel is received in a cell that belongs to the LA 
where the subscriber is registered. 

In this state, only requests from the GCC or BCC layers are treated. 

19.10 RECEIVING GROUP CALL (LIMITED SERVICE) 

Only applicable for mobile stations supporting VGCS listening or VBS listening. Valid subscriber data are 
available, update status is U3, a VGCS channel or VBS channel is received in a cell which is known not to be 
able to provide normal service. 

In this state, only requests from the GCC or BCC layers for the reception of VGCS or VBS calls are treated 
and group call emergency services are offered. 

4.1 .2.2 The update Status 

In parallel with the sublayer states described in subclause 4.1.2.1 and which control the MM sublayer protocol, an 
update status exists. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 46 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The update status pertains to a specific subscriber embodied by a SIM/USIM. This status is defined even when the 
subscriber is not activated (SIM/USIM removed or connected to a switched-off ME). It is stored in a non volatile 
memory in the SIM/USIM. The update status is changed only as a result of a location updating procedure attempt (with 
the exception of an authentication failure and of some cases of CM service rejection). In some cases, the update status is 
changed as a result of a GPRS attach, GPRS routing area update, service request or network initiated GPRS detach 
procedure. 

UI UPDATED 

The last location updating attempt was successful (correct procedure outcome, and the answer was 
acceptance from the network). With this status, the SIM/USIM contains also the LAI of the LA where the 
subscriber is registered, and possibly valid TMSI, GSM ciphering key, UMTS integrity key, UMTS ciphering 
key and ciphering key sequence number. The "Location update status" stored on the SIM/USIM shall be 
"updated". 

U2 NOT UPDATED 

The last location updating attempt made failed procedurally (no significant answer was received from the 
network, including the cases of failures or congestion inside the network). 

For this status, the SIM/USIM does not contain any valid LAI, TMSI, GSM ciphering key, UMTS integrity 
key, UMTS ciphering key or ciphering key sequence number. For compatibility reasons, all these fields must 
be set to the "deleted" value at the moment the status is set to NOT UPDATED. However the presence of 
other values shall not be considered an error by the mobile station. The "Location update status" stored on the 
SIM/USIM shall be "not updated". 

U3 ROAMING NOT ALLOWED 

The last location updating attempt run correctly, but the answer from the network was negative (because of 
roaming or subscription restrictions). 

For this status, the SIM/USIM may contain a vaUd LAI, TMSI, GSM ciphering key, UMTS integrity key, 
UMTS ciphering key or ciphering key sequence number. For compatibility reasons, all these fields must be 
set to the "deleted" value if the LAI is deleted. However the presence of other values shall not be considered 
an error by the mobile station. The "Location update status" stored on the SIM/USIM shall be "Location Area 
not allowed". 

4.1 .2.3 MM sublayer states on the network side 

l.IDLE 

The MM sublayer is not active except possibly when the RR sublayer is in Group Receive mode. 

2. WAIT FOR RR CONNECTION 

The MM sublayer has received a request for MM connection establishment from the CM layer. A RR 
connection to the mobile station is requested from the RR sublayer (i.e. paging is performed). 

3. MM CONNECTION ACTIVE 

The MM sublayer has a RR connection to a mobile station. One or more MM connections are active, or no 
MM connection is active but an RRLP procedure or LCS procedure over RRC is ongoing. 

4. IDENTIFICATION INITIATED 

The identification procedure has been started by the network. The timer T3270 is running. 

5. AUTHENTICATION INITIATED 

The authentication procedure has been started by the network. The timer T3260 is running. 

6. TMSI REALLOCATION INITIATED 

The TMSI reallocation procedure has been started by the network. The timer T3250 is running. 

7. SECURITY MODE INITIATED 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 47 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

In lu mode, the security mode setting procedure has been requested to the RR sublayer. In A/Gb mode, the 
cipher mode setting procedure has been requested to the RR sublayer. 

8a. WAIT FOR MOBILE ORIGINATED MM CONNECTION 

A CM SERVICE REQUEST message is received and processed, and the MM sublayer awaits the "opening 
message" of the MM connection. 

8b. WAIT FOR NETWORK ORIGINATED MM CONNECTION 

A CM SERVICE PROMPT message has been sent by the network and the MM sublayer awaits the "opening 
message" of the MM connection $(CCBS)$. 

9. WAIT FOR REESTABLISHMENT 

The RR connection to a mobile station with one or more active MM connection has been lost. The network 
awaits a possible re-establishment request from the mobile station. 

10. WAIT OF A GROUP CALL 

Only applicable in case for mobile station supporting VGCS talking. The MM sublayer has received a 
request for establishing a VGCS from the GCC sublayer. The request for establishing a VGCS channels is 
given to the RR sublayer. 

11. GROUP CALL ACTIVE 

Only applicable in case of mobile station supporting VGCS talking. A VGCS channel is established by the 
RR sublayer. An RR connection to the talking mobile station can be established by the RR sublayer on the 
VGCS channel. The MM sublayer is active but no sending of MM message between the network and the 
mobile station has occurred. 

12. MM CONNECTION ACTIVE (GROUP CALL) 

Only applicable in case of mobile station supporting VGCS talking. The MM sublayer has a RR connection 
to the talking mobile station on the VGCS channel. Only one MM connection is active. 

13. WAIT FOR BROADCAST CALL 

Only applicable in case of VBS. The MM sublayer has received a request for a VBS establishment from the 
BCC sublayer. The request for establishment of VBS channels is given to the RR sublayer. 

14. BROADCAST CALL ACTIVE 

Only applicable in case of VBS. A VBS channel is established by the RR sublayer. The MM sublayer is 
active but no explicit MM establishment between the Network and the mobile station has occurred. 

4.1 .3 GPRS mobility management (GMM) sublayer states 

In this subclause, the GMM protocol of the MS and the network are described by means of two different state machines. 
In subclause 4.1.3.1, the states of the GMM entity in the MS are introduced. The behaviour of the MS depends on a 
GPRS update status that is described in subclause 4.1.3.2. The states for the network side are described in 
subclause 4.1.3.3. 

4.1.3.1 GMM states in the MS 

In this subclause, the possible GMM states are described of a GMM entity in the mobile station, subclause 4.1.3.1.1 
summarises the main states of a GMM entity, see figure 4.1b of the present document. The substates that have been 
defined are described in subclause 4.1.3.1.2 and subclause 4.1.3.1.3. 

However, it should be noted that this subclause does not include a description of the detailed behaviour of the MS in the 
single states and does not cover abnormal cases. Thus, figure 4.1b of the present document is rather intended to give an 
overview of the state transitions than to be a complete state transition diagram. A detailed description of the behaviour 
of the MS is given in subclause 4.2. Especially, with respect to the behaviour of the MS in abnormal cases it is referred 
to subclause 4.7. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 48 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.1.3.1.1 Main states 

4.1.3.1.1.1 GMM-NULL 

The GPRS capability is disabled in the MS. No GPRS mobility management function shall be performed in this state. 

4.1.3.1.1.2 GMM-DEREGISTERED 

The GPRS capability has been enabled in the MS, but no GMM context has been established. In this state, the MS may 
establish a GMM context by starting the GPRS attach or combined GPRS attach procedure. 

4.1 .3.1 .1 .3 GMM-REGISTERED-INITIATED 

A GPRS attach or combined GPRS attach procedure has been started and the MS is awaiting a response from the 
network. 

4.1.3.1.1.4 GMM-REGISTERED 

A GMM context has been established, i.e. the GPRS attach or combined GPRS attach procedure has been successfully 
performed. In this state, the MS may activate PDP contexts, MBMS contexts, may send and receive user data and 
signalling information and may reply to a page request. Furthermore, cell and routing area updating are performed. 

4.1 .3.1 .1 .5 GMM-DEREGISTERED-INITIATED 

The MS has requested release of the GMM context by starting the GPRS detach or combined GPRS detach procedure. 
This state is only entered if the MS is not being switched off at detach request. 

4.1 .3.1 .1 .6 GMM-ROUTING-AREA-UPDATING-INITIATED 

A routing area updating procedure has been started and the MS is awaiting a response from the network. 

4.1 .3.1 .1 .7 GMM-SERVIGE-REQUEST-INITIATED (UMTS only) 

A service request procedure has been started and the MS is awaiting a response from the network. 

4.1 .3.1 .2 Substates of state GMM-DEREGISTERED 

The GMM-DEREGISTERED state is subdivided into several substates as explained below. The substates pertain to the 
whole MS (ME alone if no SIM/USIM is inserted, or ME plus SIM/USIM). The selection of the appropriate substate 
depends on the GPRS update status, see subclause 4.1.3.2, and on the selected cell. 

4.1 .3.1 .2.1 GMM-DEREGISTERED.NORMAL-SERVIGE 

Valid subscriber data is available, the GPRS update status is GUI or GU2, a cell has been selected. In this state, a 
request for GPRS attach is performed using the stored temporary mobile subscriber identity for GPRS (P-TMSI), 
routing area identification (RAI) and GPRS ciphering key sequence number in case of GUI. If the GPRS update status 
is GU2, the IMSI shall be used to attach for GPRS services. 

4.1 .3.1 .2.2 GMM-DEREGISTERED. LIMITED-SERVICE 

Valid subscriber data is available, GPRS update status is GU3, and a cell is selected, which is known not to be able to 
provide normal service. 

4.1 .3.1 .2.3 GMM-DEREGISTERED.ATTACH-NEEDED 

Valid subscriber data is available and for some reason a GPRS attach must be performed as soon as possible. This state 
is usually of no duration, but can last, e.g. if the access class is blocked due to common access class control or PS 
domain specific access control (see subclause 4.1.1.2.1). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 49 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.1 .3.1 .2.4 GMM-DEREGISTERED.ATTEMPTING-TO-ATTACH 

The GPRS update status is GU2, a cell is selected, a previous GPRS attach was rejected. The execution of further attach 
procedures depends on the GPRS attach attempt counter. No GMM procedure except GPRS attach shall be initiated by 
the MS in this substate. 

4.1 .3.1 .2.5 GMM-DEREGISTERED.NO-IMSI 

No valid subscriber data is available (no SIM/USIM, or the SIM/USIM is not considered valid by the ME) and a cell 
has been selected. 

4.1 .3.1 .2.6 GMM-DEREGISTERED.NO-GELL-AVAILABLE 

No cell can be selected. This substate is entered after a first intensive search failed (substate PLMN SEARCH). Cells 
are searched for at a low rhythm. No services are offered. 

4.1 .3.1 .2.7 GMM-DEREGISTERED.PLMN-SEARGH 

The mobile station is searching for PLMNs. This substate is left either when a cell has been selected (the new substate 
is NORMAL-SERVICE or LIMITED-SERVICE) or when it has been concluded that no cell is available at the moment 
(the new substate is NO-CELL-AVAILABLE). 

4.1 .3.1 .2.8 GMM-DEREGISTERED. SUSPENDED (A/Gb mode only) 

The MS shall enter this substate when entering dedicated mode and the MS limitations make it unable to communicate 
on GPRS channels. The MS shall leave this substate when leaving dedicated mode. 

4.1 .3.1 .3 Substates of state GMM-REGISTERED 

The state GMM-REGISTERED is subdivided into several substate as explained below. The substates pertain to the 
whole MS (ME alone if no SIM/USIM is inserted, or ME plus SIM/USIM). 

4.1 .3.1 .3.1 GMM-REGISTERED.NORMAL-SERVICE 
User data and signalling information may be sent and received. 

4.1 .3.1 .3.2 GMM-REGISTERED. SUSPENDED (A/Gb mode only) 

The MS shall enter this substate when entering dedicated mode and when the MS limitations makes it unable to 
communicate on GPRS channels. In this substate, no user data should be sent and no signalling information shall be 
sent. The MS shall leave this substate when leaving dedicated mode. 

4.1 .3.1 .3.3 GMM-REGISTERED. UPDATE-NEEDED 

The MS has to perform a routing area updating procedure, but its access class is not allowed in the cell due to common 
access class control or PS domain specific access control (see subclause 4.1.1.2.1). The procedure will be initiated as 
soon as access is granted (this might be due to a cell-reselection or due to change of the access classes allowed in the 
current cell). No GMM procedure except routing area updating shall be initiated by the MS in this substate. In this 
substate, no user data and no signalling information shall be sent. 

4.1 .3.1 .3.4 GMM-REGISTERED.ATTEMPTING-TO-UPDATE 

A routing area updating procedure failed due to a missing response from the network. The MS retries the procedure 
controlled by timers and a GPRS attempt counter. No GMM procedure except routing area updating shall be initiated by 
the MS in this substate. No data shall be sent or received. 

4.1 .3.1 .3.5 GMM-REGISTERED. NO-GELL-AVAILABLE 

GPRS coverage has been lost. In this substate, the MS shall not initiate any GMM procedures except of cell (and 
PLMN) reselection. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



50 



ETSI TS 124 008 V7.14.0 (2009-03) 




GMM-ROUTING- 

AREA-UPDATING- 

INrriATED 



enable 
GPRS mode 





DETACH accepted 
Lower layer failure 



RAU accepted 
RAU failed 
RAU rejected 
(#13, #15) 



DETACH requested 
(not power off) 



RAU 
requested 



RAU rejected 

Network init. DETACH requested 

implicit DETACH 



- ATTACH 
requested 



DETACH requested 
(power off) 



ATTACH rejected 

Network init. DETACH requested 

Lower layer failure 





- SR requested 
accepted 



ATTACH 

accepted 



SR accepted 
SR failed 




4.1.3.1.3.6 



Figure 4.1b/3GPP TS 24.008:GMM main states in the IVIS 



GMM-REGISTERED. LIMITED-SERVICE 



A cell is selected, which is known not to be able to provide normal service. The MS will remain in this sub-state until a 
cell is selected which is able to provide normal service. 



4.1.3.1.3.7 



GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM 



A combined routing area updating procedure or a combined GPRS attach procedure was successful for GPRS services 
only. The MS retries the procedure controlled by timers and a GPRS attempt counter. User data and signalling 
information may be sent and received. 



4.1.3.1.3.8 



GMM-REGISTERED.IMSI-DETAGH-INITIATED 



The MS performs a combined GPRS detach procedure for non-GPRS services only (detach type "IMSI Detach"). This 
state is entered if the MS is attached for GPRS and non-GPRS services in a network that operates in network mode I 
and wants to detach for non-GPRS services only. User data and signalling information may be sent and received. 



4.1.3.1.3.9 



GMM-REGISTERED. PLMN-SEARGH 



The mobile station is searching for PLMNs. This substate is left either when a cell has been selected (the new substate 
is NORMAL-SERVICE or LIMITED-SERVICE) or when it has been concluded that no cell is available at the moment 
(the new substate is NO-CELL-AVAILABLE). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 51 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.1 .3.2 GPRS update status 

In addition to the GMM sublayer states described so far, a GPRS update status exists. 

The GPRS update status pertains to a specific subscriber embodied by a SIM/USIM. This status is defined even when 
the subscriber is not activated (SIM/USIM removed or connected to a switched off ME). It is stored in a non volatile 
memory in the SIM/USIM. The GPRS update status is changed only after execution of a GPRS attach, network initiated 
GPRS detach, authentication procedure, or routing area updating procedure. 

GUI: UPDATED 

The last GPRS attach or routing area updating attempt was successful (correct procedure outcome, and the 
answer was accepted by the network). The SIM/USIM contains the RAI of the routing area (RA) to which the 
subscriber was attached, and possibly a valid P-TMSI, GPRS GSM ciphering key, GPRS UMTS ciphering key, 
GPRS UMTS integrity key and GPRS ciphering key sequence number. 

GU2: NOT UPDATED 

The last GPRS attach or routing area updating attempt failed procedurally, i.e. no response was received from 
the network. This includes the cases of failures or congestion inside the network. 

In this case, the SIM/USIM may contain the RAI of the routing area (RA) to which the subscriber was attached, 
and possibly also a valid P-TMSI, GPRS GSM ciphering key, GPRS UMTS ciphering key, GPRS UMTS 
integrity key and GPRS ciphering key sequence number. For compatibility reasons, all these fields shall be set to 
the "deleted" value if the RAI is deleted. However, the presence of other values shall not be considered an error 
by the MS. 

GU3: ROAMING NOT ALLOWED 

The last GPRS attach or routing area updating attempt was correctly performed, but the answer from the network 
was negative (because of roaming or subscription restrictions). 

In this case, the SIM/USIM may contain the RAI of the routing area (RA) to which the subscriber was attached, 
and possibly also a valid P-TMSI, GPRS GSM ciphering key, GPRS UMTS ciphering key, GPRS UMTS 
integrity key or GPRS ciphering key sequence number. For compatibility reasons, all these fields shall be set to 
the value "deleted" if the RAI is deleted. However, the presence of other values shall not be considered an error 
by the MS. 

4.1 .3.3 GMM mobility management states on the network side 

In this subsubclause, the possible states are described for the GMM on the network side. Subclause 4.1.3.3.1 
summarises the main states. The corresponding substates are described in subclause 4.1.3.3.2. 

However, it should be noted that this subclause does not include a description of the detailed behaviour of the network 
in the single states and does not cover abnormal cases. Thus, figure 4.1c/3GPP TS 24.008 is rather intended to give an 
overview of the state transitions than to be a complete state transition diagram. A detailed description of the behaviour 
of the MS is given in subclause 4.2. Especially, with respect to the behaviour of the MS in abnormal cases it is referred 
to subclause 4.7. 

4.1.3.3.1 Main States 

4.1.3.3.1.1 GMM-DEREGISTERED 

The network has no GMM context or the GMM context is marked as detached, the MS is detached. In this state, the 
network may answer to a GPRS attach or combined GPRS attach procedure initiated by the MS. 

4.1 .3.3.1 .2 GMM-COMMON-PROCEDURE-INITIATED 

A common GMM procedure, as defined in subclause 4.1.1, has been started. The network is awaiting the answer from 
the MS. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



52 



ETSI TS 124 008 V7.14.0 (2009-03) 



4.1.3.3.1.3 GMM-REGISTERED 

The GMM context has been estabUshed and the GPRS attach procedure has been successfully performed. 

4.1 .3.3.1 .4 GMM-DEREGISTERED-INITIATED 

The network has started a GPRS detach procedure and is awaiting the answer from the MS. 




GMM- 

DE-REGISTERED 

INITIATED 



DETACH accepted 
Lower layer failure 




Network initiated 
DETACH requested 




GMM 
DE-REGISTERED 




MS initiated 
DETACH requested 
RAU rejected 
implicit DETACH 



COMMON procedure 
requested 




ATTACH procedure 
successful 





- COMMON procedure 
requested 



COMMON procedure 

failed 

Lower layer failure 



T" 




COMMON procedure 
successful 

ATTACH procedure 
successful 



/^GMM-COMMOH^^ / 
WoCEDURE-INITIATEp 

Figure 4.1c/3GPP TS 24.008: GMM main states on the networit side 

4.1 .3.3.2 Substates of state GMM-REGISTERED 

The state GMM-REGISTERED is subdivided into two substates as explained below. 

4.1 .3.3.2.1 GMM-REGISTERED.NORMAL-SERVIGE 
User data and signalling information may be sent and received. 

4.1 .3.3.2.2 GMM-REGISTERED. SUSPENDED (A/Gb mode only) 

In this substate, the lower layers shall be prevented of sending user data or signalling information. 

4.2 Behaviour of the MS in IVIIVI Idle state, GMM- 

DEREGISTERED state and GMM-REGISTERED state 

In this subclause, the detailed behaviour of the MS in the main states MM IDLE, GMM-DEREGISTERED and GMM- 
REGISTERED is described. Subclauses 4.2.1 to 4.2.3 refer to the state MM IDLE, whereas subclauses 4.2.4 and 4.2.5 
refer to the states GMM-DEREGISTERED and GMM-REGISTERED, respectively. 

The MM IDLE state is entered when none of the MM procedures are running and no RR connection exists. It is left 
when one of the MM procedures are triggered or a RR connection is established. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 53 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The specific behaviour in the MM IDLE state depends on the service state of the mobile station as described in 
subclause 4.1.2.1.2. The service state depends in particular on the update status which is defined in subclause 4.1.2.2. 

How an appropriate service state is chosen after power on is described in subclause 4.2.1, and the specific behaviour of 
the mobile station in MM IDLE state is described in subclause 4.2.2. The service state chosen when the MM IDLE state 
is returned to from any state except NULL state is described in 4.2.3. 

It should be noted that transitions between the various MM idle states are caused by (e.g.): 

results of procedures on RR connected mode (see subclause 4.2.3); 

insertion or removal of the SIM/USIM; 

- cell selection/reselection (see also 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98]); 

- PLMN search; 

loss of coverage. 

How various MM procedures affects the service state and the update status is described in the detailed descriptions of 
the procedures in subclauses 4.3 to 4.5. 

4.2.1 Primary Service State selection 

4.2.1 .1 Selection of the Service State after Power On. 

When mobility management is activated after power-on, the service state is 19.7 PLMN SEARCH. The detailed 
processing in this state is described in detail in 3GPP TS 23.122 [14], 3GPP TS 43.022 [82], 3GPP TS 45.008 [34] and 
3GPP TS 25.304 [98], where procedures for power on and selection of PLMN is described in detail. If the "Location 
update status" stored on the SIM/USIM is different from "updated", then the mobile shall act as if the "Location update 
status" stored on the SIM/USIM is "not updated". 

The service state when the PLMN SEARCH state is left depends on the outcome of the search and on the presence of 
the SIM/USIM: 

if no cell has been found, the state is NO CELL AVAILABLE, until a cell is found; 

- if no SIM/USIM is present the state is NO IMSI; 

if the mobile station has been continuously activated since loosing coverage and then returns to coverage, and if 
the selected cell is in the location area where the mobile station is registered and the timer T3212 has not 
expired, then the state is NORMAL SERVICE; 

if the selected cell is in the location area where the mobile station is registered and IMSI ATTACH is not 
required and timer T3212 has not expired, then the state is NORMAL SERVICE; 

if the mobile station is in automatic network selection mode and the selected cell is in a forbidden PLMN or a 
forbidden LA, then the mobile station enters the LIMITED SERVICE state; 

if the mobile station is in manual network selection mode and no cell of the selected PLMN has been found, then 
the mobile station enters the LIMITED SERVICE state; 

- otherwise, the mobile station enters the LOCATION UPDATE NEEDED state. 

4.2.1.2 Other Cases 

The state PLMN SEARCH is also entered in the following cases: 

- in state NO IMSI, a SIM/USIM is inserted; 

- in any state except NO IMSI, NO CELL AVAILABLE, NORMAL SERVICE and RECEIVING GROUP CALL 
(NORMAL SERVICE) after the user has asked for a PLMN selection; 

- in any state except NO IMSI and NO CELL AVAILABLE, coverage is lost; 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 54 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

roaming is denied; 

optionally, when the mobile station is in the ATTEMPTING TO UPDATE state and is in Automatic Network 
Selection mode and location update attempt counter is greater than or equal to 4. 

The service state when the PLMN SEARCH is left depends on the outcome of the search and on the presence of the 
SIM/USIM as specified in subclause 4.2.1.1. 

4.2.2 Detailed Description of tine MS behaviour in MM IDLE State. 

In the MM IDLE state the mobile station shall behave according to the service state. In the following subclauses the 
behaviour is described for the non transient service states. It should be noted that after procedures in RR connected 
mode, e.g. location updating procedures, subclause 4.2.3 applies which specifies the selection of the MM idle state. 
Furthermore when in sub-state NORMAL SERVICE, if a PLMN selection is requested, the MS enters sub-state 
SEARCH FOR PLMN, NORMAL SERVICE. 

4.2.2.1 Service State, NORMAL SERVICE 

When in state MM IDLE and service state NORMAL SERVICE, the mobile station shall: 

perform normal location updating when a new location area is entered; 

perform location updating procedure at expiry of timer T321 1 or T3213; 

perform periodic updating at expiration of timer T3212; 

perform IMSI detach; 

support requests from the CM layer; 

respond to paging. 
In addition, mobile stations supporting VGCS listening or VBS listening shall: 

indicate notifications to the GCC or BCC sublayer; 

respond to notification if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for 
which no channel description has been received in the notification by the RR sublayer; 

request the RR sublayer to receive a voice group or broadcast call if the GCC or BCC sublayer requests the 
reception of a voice group or broadcast call for which a channel description has been received in the notification 
by the RR sublayer and then go to the service state RECEIVING GROUP CALL (NORMAL SERVICE). 

4.2.2.2 Service State, ATTEMPTING TO UPDATE 

When in state MM IDLE and service state ATTEMPTING TO UPDATE the mobile station shall: 

perform location updating procedure at expiry of timer T32 11 or T32 1 3 ; 

perform normal location updating when the location area identification of the serving cell changes; 

if entry into this state was caused by c) or d) or f) (with cause different from "abnormal release, unspecified") or 
g) (with cause "retry upon entry into a new cell") of subclause 4.4.4.9, then location updating shall be performed 
when a new cell is entered; 

if entry into this state was caused by e) or f) (with cause "abnormal release, unspecified") or g) (with cause 
different from "retry upon entry into a new cell") of subclause 4.4.4.9, then location updating shall not be 
performed because a new cell is entered; 

perform normal location updating at expiry of timer T3212; 

not perform IMSI detach; 

support request for emergency calls; 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 55 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

use other request from CM layer as triggering of normal location updating procedure (if the location updating 
procedure is successful, then the request for MM connection is accepted, see subclause 4.5.1); 

respond to paging (with IMSI). 

In addition, mobile stations supporting VGCS listening or VBS listening shall: 

indicate notifications to the GCC or BCC sublayer for which a channel description has been received in the 
notification by the RR sublayer; 

reject requests of the GCC or BCC sublayer to respond to notifications for which no channel description has 
been received in the notification by the RR sublayer; 

request the RR sublayer to receive a voice group or broadcast call if the GCC or BCC sublayer requests the 
reception of a voice group or broadcast call for which a channel description has been received in the notification 
by the RR sublayer and then go to the service state RECEIVING GROUP CALL (LIMITED SERVICE). 

4.2.2.3 Service State, LIMITED SERVICE 

When in state MM IDLE and service state LIMITED SERVICE the mobile station shall: 

not perform periodic updating; 

not perform IMSI detach; 

reject any requests from CM entities for MM connections except for emergency calls; 

perform normal location updating when a cell is entered which may provide normal service (e.g. location area 
not in one of the forbidden LAI lists.); 

- it may respond to paging (with IMSI). 

In addition, mobile stations supporting VGCS listening or VBS listening shall: 

indicate notifications to the GCC or BCC sublayer for which a channel description has been received in the 
notification by the RR sublayer; 

reject requests of the GCC or BCC sublayer to respond to notifications for which no channel description has 
been received in the notification by the RR sublayer; 

request the RR sublayer to receive a voice group or broadcast call if the GCC or BCC sublayer requests the 
reception of a voice group or broadcast call for which a channel description has been received in the notification 
by the RR sublayer and then go to the service state RECEIVING GROUP CALL (LIMITED SERVICE). 

4.2.2.4 Service State, NO IMSI 

When in state MM IDLE and service state NO IMSI the mobile station shall (see subclause 3.2, 3GPP TS 43.022 [82] 
and 3GPP TS 45.008 [34]): 

not start any normal location updating attempt; 

not perform periodic updating; 

not perform IMSI detach if powered down; 

reject any request from CM entities for MM connections except for emergency calls; 

not respond to paging; 

only perform default cell selection. 

In addition, mobile stations supporting VGCS listening or VBS listening shall: 

- not indicate notifications to the GCC or BCC layer. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 56 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.2.2.5 Service State, SEARCH FOR PLMN, NORMAL SERVICE 

When in state MM IDLE and service state SEARCH FOR PLMN, NORMAL SERVICE the mobile station shall: 

if timer T321 1 or T3213 expires in this state perform a location updating procedure at the latest if and when back 
to NORMAL SERVICE state and if the cell is not changed; 

if timer T3212 expires in this state perform a periodic location updating procedure at the latest if and when back 
to NORMAL SERVICE state; 

perform IMSI detach; 

support requests from the CM layer; 

listen as far as possible to paging, and respond. 

In addition, mobile stations supporting VGCS listening or VBS listening shall: 

listen as far as possible to notifications and indicate notifications to the GCC or BCC layer; 

respond to notification if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for 
which no channel description has been received in the notification by the RR sublayer; 

request the RR sublayer to receive a voice group or broadcast call if the GCC or BCC sublayer requests the 
reception of a voice group or broadcast call for which a channel description has been received in the notification 
by the RR sublayer. 

4.2.2.6 Service State, SEARCH FOR PLMN 

When in state MM IDLE and service state SEARCH FOR PLMN the mobile station shall: 
not start any normal location updating attempt; 
not perform periodic updating; 
not perform IMSI detach if powered down; 

reject any request from CM entities for MM connections except emergency calls; 
not respond to paging. 

4.2.2.7 Service State, RECEIVING GROUP CALL (NORMAL SERVICE) 

Only applicable for mobile stations supporting VGCS listening or VBS listening: 

When in state MM IDLE and service state RECEIVING GROUP CALL (NORMAL SERVICE), the mobile station 
shall: 

perform normal location updating when a new location area is entered; 

perform location updating procedure at expiry of timer T32 1 1 or T32 1 3 ; 

perform periodic updating at expiration of timer T3212; 

perform IMSI detach; 

support requests from the GCC or BCC layers; 

indicate notifications or paging information to the GCC or BCC layer; 

respond to notification if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for 
which no channel description has been received in the notification by the RR sublayer; 

request the RR sublayer to receive another voice group or broadcast call if the GCC or BCC sublayer requests 
the reception of a voice group or broadcast call for which a channel description has been received in the 
notification by the RR sublayer. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 57 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.2.2.8 Service State, RECEIVING GROUP CALL (LIMITED SERVICE) 

Only applicable for mobile stations supporting VGCS listening or VBS listening: 

When in state MM IDLE and service state RECEIVING GROUP CALL (LIMITED SERVICE), the mobile station 
shall: 

not perform periodic updating; 

not perform IMSI detach; 

reject any requests from CM entities for MM connections except for emergency calls; 

perform normal location updating when a cell is entered which may provide normal service (e.g. location area 
not in one of the forbidden LAI lists.); 

- it may respond to paging (with IMSI); 

indicate notifications to the GCC or BCC sublayer for which a channel description has been received in the 
notification by the RR sublayer; 

reject requests of the GCC or BCC sublayer to respond to notifications for which no channel description has 
been received in the notification by the RR sublayer; 

request the RR sublayer to receive a voice group or broadcast call if the GCC or BCC sublayer requests the 
reception of a voice group or broadcast call for which a channel description has been received in the notification 
by the RR sublayer and then go to the service state RECEIVING GROUP CALL (LIMITED SERVICE). 

4.2.3 Service state when back to state MM IDLE from another state 

When returning to MM IDLE, e.g., after a location updating procedure, the mobile station selects the cell as specified in 
3GPP TS 43.022 [82] and 3GPP TS 25.304 [98]. With one exception, this is a normal cell selection. 

If this return to idle state is not subsequent to a location updating procedure terminated with reception of cause 
"Roaming not allowed in this location area" the service state depends on the result of the cell selection procedure, on the 
update status of the mobile station, on the location data stored in the mobile station and on the presence of the 
SIM/USIM: 

if no cell has been found, the state is NO CELL AVAILABLE, until a cell is found; 

- if no SIM/USIM is present, or if the inserted SIM/USIM is considered invalid by the MS, the state is NO IMSI; 

if the selected cell is in the location area where the MS is registered, then the state is NORMAL SERVICE; it 
shall be noted that this also includes an abnormal case described in subclause 4.4.4.9; 

(Only applicable for mobile stations supporting VGCS listening or VBS listening.) if the mobile stations was in 
the service state RECEIVING GROUP CALL (NORMAL SERVICE) or RECEIVING GROUP CALL 
(LIMITED SERVICE) before the location updating procedure and the selected cell is in the location area where 
the mobile station is registered, then the state is RECEIVING GROUP CALL (NORMAL SERVICE); 

if the selected cell is in a location area where the mobile station is not registered but in which the MS is allowed 
to attempt a location update, then the state is LOCATION UPDATE NEEDED; 

if the selected cell is in a location area where the mobile station is not allowed to attempt a location update, then 
the state is LIMITED SERVICE; 

(Only applicable for MSs supporting VGCS listening or VBS listening.) if the MSs was in the service state 
RECEIVING GROUP CALL (NORMAL SERVICE) or RECEIVING GROUP CALL (LIMITED SERVICE) 
before the location updating procedure and the selected cell is in the location area where the MS is not allowed 
to attempt a location update, then the state is RECEIVING GROUP CALL (LIMITED SERVICE); 

after some abnormal cases occurring during an unsuccessful location updating procedure, as described in 
subclause 4.4.4.9, the state is ATTEMPTING TO UPDATE. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 58 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

In case of a return from a location updating procedure to which was answered "Roaming not allowed in this location 
area", the service state PLMN SEARCH is entered as specified in subclause 4.2.1.2. 

4.2.4 Behaviour in state GMM-DEREGISTERED 

The state GMM-DEREGISTERED is entered when: 

the MS is switched on; 

the GPRS capability has been enabled in the MS; 

a GPRS detach or combined GPRS detach procedure has been performed; or 

a GMM procedure has failed (except routing area updating, see subclause 4.7.5). 

The selection of the appropriate substate of GMM-DEREGISTERED after switching on is described in 
subclause 4.2.4.1. The specific behaviour of the MS in state GMM-DEREGISTERED is described in subclause 4.2.4.2. 
The substate chosen when the GMM-DEREGISTERED state is returned to from another state except state GMM- 
NULL is described in subclause 4.2.4.3. 

It should be noted that transitions between the various substates of GMM-DEREGISTERED are caused by (e.g.): 

insertion or removal of the SIM/USIM; 

- cell selection/reselection (see also 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98]); 

- PLMN search; 
loss/regain of coverage; or 

- change of RA. 

How various GMM procedures affect the GMM-DEREGISTERED substates and the GPRS update status is described 
in the detailed description of the GMM procedures in subclause 4.7. 

4.2.4.1 Primary substate selection 

4.2.4.1 .1 Selection of the substate after power on or enabling the MS's GPRS capability 

When the MS is switched on, the substate shall be PLMN-SEARCH in case the SIM/USIM is inserted and valid. See 
3GPP TS 23.122 [14] and 3GPP TS 45.008 [34] for further details. 

When the GPRS capability in an activated MS has been enabled, the selection of the GMM-DEREGISTERED substate 
depends on the MM state and the GPRS update status. 

The substate chosen after PLMN-SEARCH, in case of power on or after enabling of the GPRS capability is: 

- if the cell is not supporting GPRS, the substate shall be NO-CELL- AVAILABLE; 

- if no SIM/USIM is present the substate shall be NO-IMSI; 

if a cell supporting GPRS has been found and the PLMN or LA is not in the forbidden list, then the substate shall 
be NORMAL-SERVICE; 

if the selected cell supporting GPRS is in a forbidden PLMN or a forbidden LA, then the MS shall enter the 
substate LIMITED-SERVICE; 

if the MS is in manual network selection mode and no cell supporting GPRS of the selected PLMN has been 
found, the MS shall enter the substate NO-CELL- AVAILABLE. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 59 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.2.4.1.2 Other Cases 

When the MM state is IDLE, the GMM substate PLMN-SEARCH shall also be entered in the following cases: 

- when a SIM/USIM is inserted in substate NO-IMSI; 

- when the user has asked for a PLMN selection in any substate except NO IMSI and NO CELL AVAILABLE ; 

- when coverage is lost in any substate except NO IMSI and NO CELL AVAILABLE ; 

Roaming is denied; 

optionally, when the MS is in automatic network selection mode and the maximum allowed number of 
subsequently unsuccessful attach attempts controlled by the GPRS attach attempt counter (subclause 4.7.3) have 
been performed. 

4.2.4.2 Detailed description of the MS behaviour in state GMM-DEREGISTERED 

In state GMM-DEREGISTERED, the MS shall behave according to the substate. In the following subclauses, the 
behaviour is described for the non transient substates. 

4.2.4.2.1 Substate, NORMAL-SERVICE 
The MS shall: 

perform GPRS attach. 

4.2.4.2.2 Substate, ATTEMPTING-TO-ATTACH 
The MS shall: 

perform GPRS attach on the expiry of timers T33 11 or T3302; 

perform GPRS attach when the routing area of the serving cell has changed and the location area this cell is 
belonging to is not in the list of forbidden LAs; 

if entry into this state was caused by b) or d) with cause "Retry upon entry into a new cell" of 
subclause 4.7.3.1.5, GPRS attach shall be performed when a new cell is entered; 

if entry into this state was caused by c) or d) with cause different from "Retry upon entry into a new cell" of 
subclause 4.7.3.1.5, GPRS attach shall not be performed when a new cell is entered; and 

use requests from CM layers to trigger the combined GPRS attach procedure, if the network operates in network 
operation mode I. Depending on which of the timers T33 1 1 or T3302 is running the MS shall stop the relevant 
timer and act as if the stopped timer has expired. 

4.2.4.2.3 Substate, LIMITED-SERVICE 

The MS shall: 

perform GPRS attach when a cell is entered which may provide normal service (e.g. location area is not in one of 
the forbidden lists). 

4.2.4.2.4 Substate, NO-IMSI 
The MS shall: 

only perform default cell selection. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 60 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.2.4.2.5 Substate, NO-CELL 
The MS shall: 

- perform cell selection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98] and shall choose an 
appropriate substate. 

4.2.4.2.6 Substate, PLMN-SEARCH 

No specific action is required in this substate. 

4.2.4.2.7 Substate, ATTACH-NEEDED 

The MS shall start a GPRS attach procedure if still needed as soon as the access class allows network contact in the 
selected cell. 

4.2.4.2.8 Substate, SUSPENDED (A/Gb mode only) 

The MS: 

shall not send any user data; and 

shall not send any signalling information. 

4.2.4.3 Substate when back to state GMM-DEREGISTERED from another GMM 

state 

When returning to state GMM-DEREGISTERED, the MS shall select a cell as specified in 3GPP TS 43.022 [82] and 
3GPPTS 25.304 [98]. 

The substate depends on the result of the cell selection procedure, the outcome of the previously performed GMM 
specific procedures, on the GPRS update status of the MS, on the location area data stored in the MS and on the 
presence of the SIM/USIM: 

if no cell has been found, the substate is NO-CELL- A VAIL ABLE, until a cell is found; 

- if no SIM/USIM is present or if the inserted SIM/USIM is considered invalid by the MS, the substate shall be 
NO-IMSI; 

if the selected cell is in a location area where the MS is allowed to roam, the substate shall be NORMAL- 
SERVICE; 

if a GPRS attach shall be performed (e.g. network requested reattach), the substate shall be ATTEMPTING-TO- 
ATTACH 

- if a PLMN reselection (according to 3GPP TS 23.122 [14]) is needed, the substate shall be PLMN SEARCH 

if the selected cell is in a location area where the MS is not allowed to roam, the state shall be LIMITED- 
SERVICE. 

4.2.5 Behaviour in state GMM-REGISTERED 

The state GMM-REGISTERED is entered when: 

- a GMM context is established, i.e. the MS is IMSI attached for GPRS services only or for GPRS and non-GPRS 

services. 

The specific behaviour of the MS in state GMM-REGISTERED is described in subclause 4.2.5.1. The primary substate 
when entering the state GMM-REGISTERED is always NORMAL-SERVICE. 

It should be noted that transitions between the various substates of GMM-REGISTERED are caused by (e.g.): 

- cell selection/reselection (see also 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98]); 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 61 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- change of RA; 

loss/regain of coverage. 

How various GMM procedures affect the GMM -REGISTERED substates is described in the detailed description of the 
procedures in subclause 4.7. 

4.2.5.1 Detailed description of the MS behaviour in state GMM-REGISTERED 

In state GMM-REGISTERED, the MS shall behave according to the substate as explained below. 

4.2.5.1.1 Substate, NORMAL-SERVICE 
The MS shall: 

- perform cell selection/reselection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98]; 
perform normal and periodic routing area updating; and 

receive and transmit user data and signalling information. 
GPRS MSs in operation modes C or A shall answer to paging requests. 
GPRS MS in operation mode B may answer to paging requests. 

4.2.5.1 .2 Substate, SUSPENDED (A/Gb mode only) 

The MS: 

shall not send any user data; 

shall not send any signalling information; and 

- shall not perform cell-updates. 

4.2.5.1.3 Substate, UPDATE-NEEDED 

The MS shall: 

not send any user data; 

not send any signalling information; 

- perform cell selection/reselection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98]; and 

chose the appropriate new substate depending on the GPRS update status as soon as the access class allows 
network contact in the selected cell. 

4.2.5.1.4 Substate, ATTEMPTING-TO-UPDATE 

The MS: 

should not send any user data; 

shall perform routing area update on the expiry of timers T33 1 1 or T3302; 

shall perform routing area update when the routing area of the serving cell has changed and the location area this 
cell is belonging to is not in the list of forbidden LAs; 

shall if entry into this state was caused by b) or d) with cause "Retry upon entry into a new cell", of 
subclause 4.7.5.1.5, perform routing area updating when a new cell is entered; 

shall if entry into this state was caused by c) or d) with cause different from "Retry upon entry into a new cell" of 
subclause 4.7.5.1.5, not perform routing area updating when a new cell is entered; and 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 62 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

shall use request from CM layers to trigger the combined routing area update procedure, if the network operates 
in network operation mode I. Depending on which of the timers T33 11 or T3302 is running the MS shall stop the 
relevant timer and act as if the stopped timer has expired. 

4.2.5.1.5 Substate, NO-CELL-AVAILABLE 

The MS shall perform cell selection/reselection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98]. 

4.2.5.1.6 Substate, LIMITED-SERVICE 

The MS shall perform cell selection/reselection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98]; 

4.2.5.1.7 Substate, ATTEMPTING-TO-UPDATE-MM 
The MS shall: 

- perform cell selection/reselection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98]; 

receive and transmit user data and signalling information; 

perform routing area update indicating "combined RA/LA updating with IMSI attach" on the expiry of timers 
T3311orT3302; 

perform routing area update indicating "combined RA/LA updating with IMSI attach" when the routing area of 
the serving cell has changed and the location area this cell is belonging to is not in the list of forbidden LAs. 

GPRS MSs in operation modes C or A shall answer to paging requests. 

GPRS MS in operation mode B may answer to paging requests. 

4.2.5.1.8 Substate, PLMN-SEARCH 

When the MM state is IDLE, the GMM substate PLMN-SEARCH may be entered if the MS is in automatic network 
selection mode and the maximum allowed number of subsequently unsuccessful routing area update attempts controlled 
by the GPRS routing area update attempt counter (clause 4.7.5) have been performed. If a new PLMN is selected the 
MS shall perform the routing area updating procedure. 



4.3 MM common procedures 



As described in subclause 4.1.1, a MM common procedure can be initiated at any time whilst a RR connection exists 
between the network and the mobile station. 



4.3.1 TMSI reallocation procedure 



The purpose of the TMSI reallocation procedure is to provide identity confidentiality, i.e. to protect a user against being 
identified and located by an intruder (see 3GPP TS 42.009, 3GPP TS 43.020 [13] and 3GPP TS 33.102 [5a]). 

If the identity confidentiality service is applied for an IMSI, a Temporary Mobile Subscriber Identity (TMSI) is used for 
identification within the radio interface signalling procedures. 

In a network supporting the feature "Intra domain connection of RAN nodes to multiple CN nodes" a TMSI shall be 
allocated to each IMSI attached mobile station. See 3GPP TS 23.236 [94], chapter 4.3. 

The structure of the TMSI is specified in 3GPP TS 23.003 [10]. The TMSI has significance only within a location area. 
Outside the location area it has to be combined with the Location Area Identifier (LAI) to provide for an unambiguous 
identity. 

Usually the TMSI reallocation is performed at least at each change of a location area. (Such choices are left to the 
network operator). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 63 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The reallocation of a TMSI can be performed either by a unique procedure defined in this subclause or implicitly by a 
location updating procedure using the TMSI. The implicit reallocation of a TMSI is described together with that 
procedure. 

If a TMSI provided by a mobile station is unknown in the network e.g. due to a data base failure, the network may 
require the mobile station to provide its International Mobile Subscriber Identity (IMSI). In this case the identification 
procedure (see subclause 4.3.3) should be used before the TMSI reallocation procedure may be initiated. 

The TMSI reallocation can be initiated by the network at any time whilst a RR connection exists between the network 
and the mobile station. 

NOTE 1 : Usually the TMSI reallocation is performed in ciphered mode. 

NOTE 2: Normally the TMSI reallocation will take place in conjunction with another procedure, e.g. at location 
updating or at call setup (see 3GPP TS 29.002 [37]). 

4.3.1 .1 TMSI reallocation initiation by the network 

The network initiates the TMSI reallocation procedure by sending a TMSI REALLOCATION COMMAND message to 
the mobile station and starts the timer T3250. 

The TMSI REALLOCATION COMMAND message contains a new combination of TMSI and LAI allocated by the 
network or a LAI and the IMSI if the used TMSI shall be deleted. Usually the TMSI-REALLOCATION COMMAND 
message is sent to the mobile station using a RR connection in ciphered mode (see 3GPP TS 43.020 [13] and 
3GPPTS 33.102 [5a]). 

4.3.1 .2 TMSI reallocation completion by the mobile station 

Upon receipt of the TMSI REALLOCATION COMMAND message the mobile station stores the Location Area 
Identifier (LAI) in the SIM/USIM. If the received identity is the IMSI of the relevant mobile station, the mobile station 
deletes any TMSI. If the received identity is a TMSI the mobile station stores the TMSI in the SIM/USIM. In both cases 
the mobile station sends a TMSI REALLOCATION COMPLETE message to the network. 

4.3.1 .3 TMSI reallocation completion in the network. 

Upon receipt of the TMSI REALLOCATION COMPLETE message, the network stops the timer T3250 and either 
considers the new TMSI as valid or, if an IMSI was sent to the mobile station, considers the old TMSI as deleted. 

If the RR connection is no more needed, then the network will request the RR sublayer to release it (see 
3GPP TS 44.018 [84] subclause 3.5 and 3GPP TS 25.331 [23c]). 

4.3.1.4 Abnormal cases 

Mobile station side: 

The mobile station shall consider the new TMSI and new LAI, if any, as valid and the old TMSI and old LAI as 
deleted as soon as a TMSI REALLOCATION COMMAND or another message containing a new TMSI (e.g. 
LOCATION UPDATING ACCEPT) is correctly received. Any RR connection failure at a later stage shall not 
have any impact on the TMSI and LAI storage. 

Network side: 

(a) RR connection failure: 

If the RR connection is lost before the TMSI REALLOCATION COMPLETE message is received, all MM 
connections (if any) shall be released and both the old and the new TMSIs should be considered as occupied 
for a certain recovery time. 

During this period the network may: 

use the IMSI for paging in the case of network originated transactions on the CM layer. Upon response 
from the mobile station the TMSI reallocation is restarted; 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 64 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

consider the new TMSI as valid if it is used by the mobile station in mobile originated requests for RR 
connection; 

- use the Identification procedure followed by a new TMSI reallocation if the mobile station uses the old 
TMSI. 

Other implementations are possible. 

(b) Expiry of timer T3250: 

The TMSI reallocation is supervised by the timer T3250 in the network. At the first expiry of timer T3250 
the network may release the RR connection. In this case, the network shall abort the reallocation procedure 
release all MM connections if any, and follow the rules described for RR connection failure above. 

mobile station network 

TMSI REAL CMD 
< Start T3250 

TMSI REAL COM 

> stop T3250 



Figure 4.1/3GPP TS 24.008: TMSI reallocation sequence 

4.3.2 Authentication procedure 

4.3.2a Authentication procedure used for a UIVITS authentication challenge 

The purpose of the authentication procedure is fourfold (see 3GPP TS 33.102 [5a]): 

First to permit the network to check whether the identity provided by the mobile station is acceptable or not; 

Second to provide parameters enabling the mobile station to calculate a new UMTS ciphering key; 

Third to provide parameters enabling the mobile station to calculate a new UMTS integrity key; 

Fourth to permit the mobile station to authenticate the network. 

The cases where the authentication procedure should be used are defined in 3GPP TS 33.102 [5a]. 

The UMTS authentication procedure is always initiated and controlled by the network. However, there is the possibility 
for the MS to reject the UMTS authentication challenge sent by the network. 

The MS shall support the UMTS authentication challenge, if a USIM is inserted. 

A UMTS security context is established in the MS and the network when a UMTS authentication challenge is 
performed in A/Gb mode or in lu mode. After a successful UMTS authentication, the UMTS ciphering key, the UMTS 
integrity key, the GSM ciphering key and the ciphering key sequence number, are stored both in the network and the 
MS. 

4.3.2b Authentication Procedure used for a GSIVI authentication challenge 

The purpose of the authentication procedure is twofold (see 3GPP TS 43.020 [13]): 

First to permit the network to check whether the identity provided by the mobile station is acceptable or not; 

Second to provide parameters enabling the mobile station to calculate a new GSM ciphering key. 

The cases where the authentication procedure should be used are defined in 3GPP TS 42.009 [5]. 

The authentication procedure is always initiated and controlled by the network. GSM authentication challenge shall be 
supported by a ME supporting GERAN or UTRAN. 

A GSM security context is established in the MS and the network when a GSM authentication challenge is performed in 
A/Gb mode or in lu mode. However, in lu mode the MS shall not accept a GSM authentication challenge, if a USIM is 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 65 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

inserted. After a successful GSM authentication, the GSM ciphering key and the ciphering key sequence number, are 
stored both in the network and the MS. 

4.3.2.1 Authentication request by the network 

The network initiates the authentication procedure by transferring an AUTHENTICATION REQUEST message across 
the radio interface and starts the timer T3260. The AUTHENTICATION REQUEST message contains the parameters 
necessary to calculate the response parameters (see 3GPP TS 43.020 [13] (in case of GSM authentication challenge) 
and 3GPP TS 33.102 [5a] (in case of an UMTS authentication challenge)). In a GSM authentication challenge, the 
AUTHENTICATION REQUEST message also contains the GSM ciphering key sequence number allocated to the key 
which may be computed from the given parameters. In a UMTS authentication challenge, the AUTHENTICATION 
REQUEST message also contains the ciphering key sequence number allocated to the key set of UMTS ciphering key, 
UMTS integrity key and GSM ciphering key which may be computed from the given parameters. 

4.3.2.2 Authentication response by the mobile station 

The mobile station shall be ready to respond upon an AUTHENTICATION REQUEST message at any time whilst a 
RR connection exists. With exception of the cases described in subclause 4.3.2.5.1, it shall process the challenge 
information and send back an AUTHENTICATION RESPONSE message to the network. 

If a SIM is inserted in the MS, the MS shall ignore the Authentication Parameter AUTN IE if included in the 
AUTHENTICATION REQUEST message and shall proceed as in case of a GSM authentication challenge. It shall not 
perform the authentication of the network described in subclause 4.3.2.5.1. 

In a GSM authentication challenge, the new GSM ciphering key calculated from the challenge information shall 
overwrite the previous GSM ciphering key and any previously stored UMTS ciphering key and UMTS integrity key 
shall be deleted. The new GSM ciphering key shall be stored on the SIM/USIM together with the ciphering key 
sequence number. 

In a UMTS authentication challenge, the new UMTS ciphering key, the new GSM ciphering key and the new UMTS 
integrity key calculated from the challenge information shall overwrite the previous UMTS ciphering key, GSM 
ciphering key and UMTS integrity key. The new UMTS ciphering key, GSM ciphering key and UMTS integrity key are 
stored on the USIM together with the ciphering key sequence number. 

The SIM/USIM will provide the mobile station with the authentication response, based upon the authentication 
challenge given from the ME. A UMTS authentication challenge will result in the USIM passing a RES to the ME. A 
GSM authentication challenge will result in the SIM/USIM passing a SRES to the ME. 

A ME supporting UMTS authentication challenge may support the following procedure: 

In order to avoid a synchronisation failure, when the mobile station receives an AUTHENTICATION REQUEST 
message, the mobile station shall store the received RAND together with the RES returned from the USIM in the 
volatile memory and associate it with CS domain. When the MS receives a subsequent AUTHENTICATION 
REQUEST message, if the stored RAND value for the CS domain is equal to the new received value in the 
AUTHENTICATION REQUEST message, then the mobile station shall not pass the RAND to the USIM, but shall 
immediately send the AUTHENTICATION RESPONSE message with the stored RES for the CS domain. If, for the CS 
domain, there is no valid stored RAND in the mobile station or the stored RAND is different from the new received 
value in the AUTHENTICATION REQUEST message, the mobile station shall pass the RAND to the USIM, shall 
override any previously stored RAND and RES with the new ones and start, or reset and restart timer T3218. 

The RAND and RES values stored in the mobile station shall be deleted and timer T3218, if running, shall be stopped: 

- upon receipt of a SECURITY MODE COMMAND (lu mode only), 
CIPHERING MODE COMMAND (A/Gb mode only), 
CM_SERVICE_ACCEPT, 

CM_SERVICE_REJECT, 

LOCATION_UPDATING_ACCEPT 

or AUTHENTICATION REJECT message; 

upon expiry of timer T32 1 8 ; or 

- if the mobile station enters the MM state MM IDLE or NULL. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 66 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.3.2.3 Authentication processing in the network 

Upon receipt of the AUTHENTICATION RESPONSE message, the network stops the timer T3260 and checks the 
validity of the response (see 3GPP TS 43.020 [13] in case of a GSM authentication challenge respective 3GPP TS 
33.102 [5a] in case of an UMTS authentication challenge). 

Upon receipt of the AUTHENTICATION FAILURE message, the network stops the timer T3260. In Synch failure 
case, the core network may renegotiate with the HLR/AuC and provide the MS with new authentication parameters. 

4.3.2.4 Ciphering key sequence number 

The security parameters for authentication and ciphering are tied together in sets. In a GSM authentication challenge, 
from a challenge parameter RAND both the authentication response parameter SRES and the GSM ciphering key can 
be computed given the secret key associated to the IMSI. In a UMTS authentication challenge, from a challenge 
parameter RAND, the authentication response parameter RES and the UMTS ciphering key and the UMTS integrity 
key can be computed given the secret key associated to the IMSI. In addition, a GSM ciphering key can be computed 
from the UMTS ciphering key and the UMTS integrity key by means of an unkeyed conversion function. 

In order to allow start of ciphering on a RR connection without authentication, the ciphering key sequence numbers are 
introduced. The ciphering key sequence number is managed by the network in the way that the AUTHENTICATION 
REQUEST message contains the ciphering key sequence number allocated to the GSM ciphering key (in case of a GSM 
authentication challenge) or the UMTS ciphering key and the UMTS integrity key (in case of a UMTS authentication 
challenge) which may be computed from the RAND parameter carried in that message. 

If an authentication procedure has been completed successfully and a ciphering key sequence number is stored in the 
network, the network shall include a different ciphering key sequence number in the AUTHENTICATION REQUEST 
message when it intiates a new authentication procedure. 

The mobile station stores the ciphering key sequence number with the GSM ciphering key (in case of a GSM 
authentication challenge) and the UMTS ciphering key and the UMTS integrity key (in case of a UMTS authentication 
challenge) and indicates to the network in the first message (LOCATION UPDATING REQUEST, CM SERVICE 
REQUEST, PAGING RESPONSE, CM RE-ESTABLISHMENT REQUEST) which ciphering key sequence number 
the stored GSM ciphering key (in case of a GSM authentication challenge) or set of UMTS ciphering, UMTS integrity 
and derived GSM ciphering keys (in case of a UMTS authentication challenge) has. 

When the deletion of the ciphering key sequence number is described this also means that the associated GSM 
ciphering key, the UMTS ciphering key and the UMTS integrity key shall be considered as invalid (i.e. the established 
GSM security context or the UMTS security context is no longer valid). 

In A/Gb mode, the network may choose to start ciphering with the stored GSM ciphering key (under the restrictions 
given in 3GPP TS 42.009 [5]) if the stored ciphering key sequence number and the one given from the mobile station 
are equal. 

In lu mode, the network may choose to start ciphering and integrity with the stored UMTS ciphering key and UMTS 
integrity key (under the restrictions given in 3GPP TS 42.009 [5] and 3GPP TS 33.102 [5a]) if the stored ciphering key 
sequence number and the one given from the mobile station are equal. 

NOTE: In some specifications the term KSI (Key Set Identifier) might be used instead of the term ciphering key 
sequence number. 

4.3.2.5 Authentication not accepted by the network 

If authentication fails, i.e. if the response is not valid, the network may distinguish between the two different ways of 
identification used by the mobile station: 

- the TMSI was used; 

- the IMSI was used. 

If the TMSI has been used, the network may decide to initiate the identification procedure. If the IMSI given by the 
mobile station then differs from the one the network had associated with the TMSI, the authentication should be 
restarted with the correct parameters. If the IMSI provided by the MS is the expected one (i.e. authentication has really 
failed), the network should proceed as described below. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 67 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the IMS I has been used, or the network decides not to try the identification procedure, an AUTHENTICATION 
REJECT message should be transferred to the mobile station. 

After having sent this message, all MM connections in progress (if any) are released and the network should initiate the 
RR connection release procedure described in subclause 3. 5. of 3GPP TS 44.018 [84] (A/Gb mode only), 
3GPPTS 25.331 [23c] (UTRAN lu mode only), or in 3GPPTS 44.118 [110] (GERAN lu mode only). 

Upon receipt of an AUTHENTICATION REJECT message, the mobile station shall set the update status in the 
SIM/USIM to U3 ROAMING NOT ALLOWED, delete from the SIM/USIM the stored TMSI, LAI and ciphering key 
sequence number. The SIM/USIM shall be considered as invalid until switching off or the SIM/USIM is removed. 

If the AUTHENTICATION REJECT message is received in the state IMSI DETACH INITIATED the mobile station 
shall follow subclause 4.3.4.3. 

If the AUTHENTICATION REJECT message is received in any other state the mobile station shall abort any MM 
specific, MM connection establishment or call re-establishment procedure, stop any of the timers T3210 or T3230 (if 
running), release all MM connections (if any), start timer T3240 and enter the state WAIT FOR NETWORK 
COMMAND, expecting the release of the RR connection. If the RR connection is not released within a given time 
controlled by the timer T3240, the mobile station shall abort the RR connection. In both cases, either after a RR 
connection release triggered from the network side or after a RR connection abort requested by the MS -side, the MS 
enters state MM IDLE, substate NO IMSI. 

4.3.2.5.1 Authentication not accepted by the MS 

In a UMTS authentication challenge, the authentication procedure is extended to allow the MS to check the authenticity 
of the core network. Thus allowing, for instance, detection of false base station. 

Following a UMTS authentication challenge, the MS may reject the core network, on the grounds of an incorrect 
AUTN parameter (see 3GPP TS 33.102 [5a]). This parameter contains two possible causes for authentication failure: 

a) MAC code failure: 

If the MS considers the MAC code (supplied by the core network in the AUTN parameter) to be invalid, it 
shall send an AUTHENTICATION FAILURE message to the network, with the reject cause 'MAC failure'. 
The MS shall then follow the procedure described in subclause 4.3.2.6 (c). 

b) SQN failure: 

If the MS considers the SQN (supplied by the core network in the AUTN parameter) to be out of range, it 
shall send a AUTHENTICATION FAILURE message to the network, with the reject cause 'Synch failure' 
and a re-synchronization token AUTS provided by the USIM (see 3GPP TS 33.102 [5a]). The MS shall then 
follow the procedure described in subclause 4.3.2.6 (d). 

In UMTS, an MS with a USIM inserted shall reject the authentication challenge if no Authentication Parameter AUTN 
IE was present in the AUTHENTICATION REQUEST message (i.e. a GSM authentication challenge has been received 
when the MS expects a UMTS authentication challenge). In such a case, the MS shall send the AUTHENTICATION 
FAILURE message to the network, with the reject cause "GSM authentication unacceptable". The MS shall then follow 
the procedure described in subclause 4.3.2.6 (c). 

If the MS returns an AUTHENTICATION_FAILURE message to the network, the MS shall delete any previously 
stored RAND and RES and shall stop timer T3218, if running. 

4.3.2.6 Abnormal cases 

(a) RR connection failure: 

Upon detection of a RR connection failure before the AUTHENTICATION RESPONSE is received, the 
network shall release all MM connections (if any) and abort any ongoing MM specific procedure. 

(b) Expiry of timer T3260: 

The authentication procedure is supervised on the network side by the timer T3260. At expiry of this timer the 
network may release the RR connection. In this case the network shall abort the authentication procedure and 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 68 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

any ongoing MM specific procedure, release all MM connections if any, and initiate the RR connection release 
procedure described in subclause 3.5. 

(c) Authentication failure (reject cause "MAC failure" or "GSM authentication unacceptable"): 

The MS shall send an AUTHENTICATION FAILURE message, with reject cause "MAC failure" or "GSM 
authentication unacceptable" according to subclause 4.3.2.5.1, to the network and start timer T3214. 
Furthermore, the MS shall stop any of the retransmission timers that are running (e.g. T3210, T3220 or T3230). 
Upon the first receipt of an AUTHENTICATION FAILURE message from the MS with reject cause "MAC 
failure" or "GSM authentication unacceptable", the network may initiate the identification procedure described 
in subclause 4.3.3. This is to allow the network to obtain the IMSI from the MS. The network may then check 
that the TMSI originally used in the authentication challenge corresponded to the correct IMSI. Upon receipt of 
the IDENTITY REQUEST message from the network, the MS shall send the IDENTITY RESPONSE message. 

NOTE: Upon receipt of an AUTHENTICATION FAILURE message from the MS with reject cause "MAC 
failure" or "GSM authentication unacceptable", the network may also terminate the authentication 
procedure (see subclause 4.3.2.5). 

If the TMSI/IMSI mapping in the network was incorrect, the network should respond by sending a new 
AUTHENTICATION REQUEST message to the MS. Upon receiving the new AUTHENTICATION REQUEST 
message from the network, the MS shall stop the timer T3214, if running, and then process the challenge 
information as normal. 

If the network is validated successfully (an AUTHENTICATION REQUEST that contains a valid SQN and 
MAC is received), the MS shall send the AUTHENTICATION RESPONSE message to the network and shall 
start any retransmission timers (e.g. T3210, T3220 or T3230), if they were running and stopped when the MS 
received the first failed AUTHENTICATION REQUEST message. 

If the MS receives the second AUTHENTICATION REQUEST while T3214 is running, and the MAC value 
cannot be resolved or the message contains a GSM authentication challenge, the MS shall follow the procedure 
specified in this subclause (c), starting again from the beginning. If the SQN is invalid, the MS shall proceed as 
specified in (d). 

It can be assumed that the source of the authentication challenge is not genuine (authentication not accepted by 
the MS) if any of the following occur: 

- after sending the AUTHENTICATION FAILURE message with the reject cause "MAC failure" or "GSM 
authentication unacceptable" the timer T3214 expires; 

the MS detects any combination of the authentication failures: "MAC failure", "invalid SQN", and "GSM 
authentication unacceptable", during three consecutive authentication challenges. The authentication 
challenges shall be considered as consecutive only, if the authentication challenges causing the second and 
third authentication failure are received by the MS, while the timer T3214 or T3216 started after the previous 
authentication failure is running. 

When it has been deemed by the MS that the source of the authentication challenge is not genuine (i.e. 
authentication not accepted by the MS), the MS shall behave as described in subclause 4.3.2.6.1. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



69 



ETSI TS 124 008 V7.14.0 (2009-03) 



Start T3214 
StopT3214 


MS 

AUTHENTICATION REQUEST 




Network 


AUTH FAILURE (cause='MAC failure' 
authentication unacceptable') 


or 'GSM 


Start T3260 
.Stop T3260 


IDENTITY REQUEST 

^ ,. , 




Start T3270 


IDENTITY RESPONSE (IMSI) 




Stop T3270 


AUTHENTICATION REQUEST 




Start T3260 


AUTHENTICATION RESPONSE 




Stop T3260 

-- ► 







Figure 4.2/3GPP TS 24.008: Authentication Failure Procedure 
(reject cause "MAC failure" or "GSM authentication unacceptable") 

(d) Authentication failure (reject cause "synch failure"): 

The MS shall send an AUTHENTICATION FAILURE message, with reject cause "synch failure", to the 
network and start the timer T3216. Furthermore, the MS shall stop any of the retransmission timers that are 
running (e.g. T3210, T3220 or T3230). Upon the first receipt of an AUTHENTICATION FAILURE message 
from the MS with the reject cause "synch failure", the network shall use the returned AUTS parameter from the 
authentication failure parameter IE in the AUTHENTICATION FAILURE message, to re-synchronise. The re- 
synchronisation procedure requires the VLR/MSC to delete all unused authentication vectors for that IMSI and 
obtain new vectors from the HLR. When re-synchronisation is complete, the network shall initiate the 
authentication procedure. Upon receipt of the AUTHENTICATION REQUEST message, the MS shall stop the 
timer T3216, if running. 

NOTE: Upon receipt of two consecutive AUTHENTICATION FAILURE messages from the MS with reject 
cause "synch failure", the network may terminate the authentication procedure by sending an 
AUTHENTICATION REJECT message. 

If the network is validated successfully (a new AUTHENTICATION REQUEST is received which contains a 
valid SQN and MAC) while T3216 is running, the MS shall send the AUTHENTICATION RESPONSE 
message to the network and shall start any retransmission timers (e.g. T3210, T3220 or T3230), if they were 
running and stopped when the MS received the first failed AUTHENTICATION REQUEST message. 

If the MS receives the second AUTHENTICATION REQUEST while T3216 is running, and the MAC value 
cannot be resolved or the message contains a GSM authentication challenge, the MS shall proceed as specified in 
(c); if the SQN is invalid, the MS shall follow the procedure specified in this subclause (d), starting again fom 
the beginning. 

The MS shall deem that the network has failed the authentication check and behave as described in subclause 
4.3.2.6.1, if any of the following occurs: 

the timer T3216 expires; 

- the MS detects any combination of the authentication failures: "MAC failure", "invaHd SQN", and "GSM 
authentication unacceptable", during three consecutive authentication challenges. The authentication 
challenges shall be considered as consecutive only, if the authentication challenges causing the second and 
third authentication failure are received by the MS, while the timer T3214 or T3216 started after the previous 
authentication failure is running. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



70 



ETSI TS 124 008 V7.14.0 (2009-03) 



MS 



AUTHENTICATION REQUEST 



Network 

Start T3260 



AUTH FAILURE (cause='Synch failure') Stop T3260 

Start T3216 ^p^^^^^^ 

AUTHENTICATION REQUEST Re-synch 

Stop T3216 ^ with HLR 

AUTHENTICATION RESPONSE 

► 



Figure 4.2a/3GPP TS 24.008: Authentication Failure Procedure (reject cause "Synch failure") 



4.3.2.6.1 



MS behaviour towards a network that has failed the authentication procedure 



If the MS deems that the network has failed the authentication check, then it shall request RR or RRC to release the RR 
connection and the PS signalling connection, if any, and bar the active cell or cells (see 3GPP TS 25.331 and 
3GPP TS 44.018). The MS shall start any retransmission timers (e.g. T3210, T3220 or T3230), if they were running and 
stopped when the MS received the first AUTHENTICATION REQUEST message containing an invalid MAC or 
invalid SQN, or no AUTN when a UMTS authentication challenge was expected. 



4.3.2.7 



Handling of keys at intersystem change from lu mode to A/Gb mode 



At inter-system change from lu mode to A/Gb mode, ciphering may be started (see 3GPP TS 44.018 [86]) without any 
new authentication procedure. Deduction of the appropriate security key for ciphering in A/Gb mode, depends on the 
current GSM/UMTS security context stored in the MS and the network. 

The ME shall handle the GSM ciphering key according to table 4.3.2.7.1. 

Table 4.3.2.7.1/3GPP TS 24.008: Inter-system change from lu mode to A/Gb mode 



Security context established in MS and 
network in lu mode 


At inter-system change to A/Gb mode: 


GSIVI security context 


An ME shall apply the stored GSM cipher key that was received 
from the GSM security context residing in the SIM/USIM during 
the latest successful ciphering mode setting or security mode 
control procedure before the inter-system change. 


UIVITS security context 


An ME shall apply the stored GSM cipher key that was derived 
by the USIM from the UMTS cipher key and the UMTS integrity 
key and provided by the USIM during the latest successful 
ciphering mode setting or security mode control procedure before 
the inter-sytem change. 



NOTE: A USIM with UMTS security context, passes the UMTS cipher key, the UMTS integrity key and the 

derived GSM cipher key to the ME independent on the current radio access being UTRAN or GERAN. 

4.3.2.7a Use of established security contexts 

In A/Gb mode, in the case of an established GSM security context, the GSM ciphering key shall be loaded from the 
SIM/USIM and taken into use by the ME when any vaUd CIPHERING MODE COMMAND is received during an RR 
connection (the definition of a valid CIPHERING MODE COMMAND message is given in 3GPP TS 44.018 [84] 
subclause 3.4.7.2). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 71 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

In A/Gb mode, in the case of an established UMTS security context, the GSM ciphering key shall be loaded from the 
USIM and taken into use by the MS when a valid CIPHERING MODE COMMAND is received during an RR 
connection (the definition of a valid CIPHERING MODE COMMAND message is given in 3GPP TS 44.018 [84] 
subclause 3.4.7.2). The network shall derive a GSM ciphering key from the UMTS ciphering key and the UMTS 
integrity key by using the conversion function named "c3" defined in 3GPP TS 33.102 [5a]. 

In lu mode, in the case of an established GSM security context, the ME shall derive a UMTS ciphering key and a 
UMTS integrity key from the GSM ciphering key by using the conversion functions named "c4" and "c5" defined in 
3GPP TS 33.102 [5a]. The GSM ciphering key shall be loaded from the SIM/USIM and the derived UMTS ciphering 
key and UMTS integrity key shall be taken into use by the MS when a vaUd SECURITY MODE COMMAND 
indicating CS domain is received during an RR connection (the definition of a vahd SECURITY MODE COMMAND 
message is given in 3GPP TS 25.331 [23c] and 3GPP TS 44.1 18 [111]). The network shall derive a UMTS ciphering 
key and a UMTS integrity key from the GSM ciphering key by using the conversion functions named "c4" and "c5" 
defined in 3GPP TS 33.102 [5a]. 

In lu mode, in the case of an established UMTS security context, the UMTS ciphering key and UMTS integrity key 
shall be loaded from the USIM and taken into use by the MS when a valid SECURITY MODE COMMAND indicating 
CS domain is received during a RR connection (the definition of a valid SECURITY MODE COMMAND message is 
given in 3GPPTS 25.331 [23c] and 3GPPTS 44.118 [111]). 

In lu mode and A/Gb mode, if the MS received a valid SECURITY MODE COMMAND indicating CS domain in lu 
mode or a valid CIPHERING MODE COMMAND in A/Gb mode before the network initiates a new Authentication 
procedure and establishes a new GSM/UMTS security context, the new keys are taken into use in the MS when a new 
valid SECURITY MODE COMMAND indicating CS domain in lu mode, or a new vahd CIPHERING MODE 
COMMAND in A/Gb mode, is received during the RR connection. In case of lu mode to lu mode handover, A/Gb 
mode to A/Gb mode handover, or inter-system change to A/Gb mode, the MS and the network shall continue to use the 
key from the old key set until a new valid SECURITY MODE COMMAND indicating CS domain in lu mode, or a new 
valid CIPHERING MODE COMMAND in A/Gb mode, is received during the RR connection. In case of inter-system 
change to lu mode, the MS and the network shall continue to use the keys from the old key set until the second valid 
SECURITY MODE COMMAND indicating CS domain is received during the RR connection. 

NOTE 1 : If the MS received a valid SECURITY MODE COMMAND indicating CS domain in lu mode or a vaUd 
CIPHERING MODE COMMAND in A/Gb mode before the inter-system change to lu mode occurs, the 
first SECURITY MODE COMMAND message after the inter-system change, which indicates CS domain 
and includes only an Integrity protection mode IE, is initiated by the UTRAN without receipt of a 
corresponding RANAP security mode control procedure from the MSC/VLR. The only purpose of this 
SECURITY MODE COMMAND message is to activate the integrity protection, but not to load a new 
key set from the SIM/USIM (see 3GPP TS 25.331 [23c] and 3GPP TS 44.1 18 [111]). 

NOTE 2: If the MS did not receive any valid SECURITY MODE COMMAND indicating CS domain in lu mode 
or any valid CIPHERING MODE COMMAND in A/Gb mode before the inter-system change to lu mode 
occurs, the first SECURITY MODE COMMAND message after the inter-system change, which indicates 
CS domain, is initiated by the UTRAN on receipt of a RANAP security mode control procedure from the 
MSC/VLR. The purpose of this SECURITY MODE COMMAND message is to load a key set from the 
SIM/USIM and to activate either integrity protection or ciphering and integrity protection (see 3GPP TS 
25.331 [23c] and 3GPPTS 44.118 [111]). 

4.3.2.8 Handling of keys at intersystem change from A/Gb mode to lu mode 

At inter-system change from A/Gb mode to lu mode, ciphering and integrity may be started (see 3GPP TS 25.331 
[23c]) without any new authentication procedure. Deduction of the appropriate security keys for ciphering and integrity 
check in lu mode, depends on the current GSM/UMTS security context stored in the MS and the network. 

The ME shall handle the UMTS cipher key and the UMTS integrity key according to table 4.3.2.8. 1. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



72 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 4.3.2.8.1/3GPP TS 24.008: Inter-system change from A/Gb mode to lu mode 



Security context established in MS and 
network in A/Gb mode 


At inter-system change to lu mode: 


GSM security context 


An ME shall derive the UMTS cipher key and the UMTS integrity 
key from the stored GSM cipher key that was provided by the 
SIM/USIM during the latest successful ciphering mode setting or 
security mode control procedure before the inter-system change. 
The conversion functions named "c4" and "c5" in 3GPP TS 
33.102 [5a] are used for this purpose. 


UMTS security context 


An ME shall apply the stored UMTS ciphering key and the stored 
UMTS integrity key that were received from the UMTS security 
context residing in the USIM during the latest successful 
ciphering mode setting or security mode control procedure before 
the inter-system change. 



NOTE: A USIM with UMTS security context, passes the UMTS cipher key, the UMTS integrity key and the 

derived GSM cipher key to the ME independent on the current radio access being UTRAN or GERAN. 



4.3.2.9 



Void 



4.3.3 Identification procedure 



The identification procedure is used by the network to request a mobile station to provide specific identification 
parameters to the network e.g. International Mobile Subscriber Identity, International Mobile Equipment Identity (see 
3GPP TS 23.003 [10]). For the presentation of the IMEI, the requirements of 3GPP TS 42.009 [5] apply. 



4.3.3.1 



Identity request by the network 



The network initiates the identification procedure by transferring an IDENTITY REQUEST message to the mobile 
station and starts the timer T3270. The IDENTITY REQUEST message specifies the requested identification 
parameters in the identity type information element. 



4.3.3.2 



Identification response by the mobile station 



The mobile station shall be ready to respond to an IDENTITY REQUEST message at any time whilst a RR connection 

exists. 

Upon receipt of the IDENTITY REQUEST message the mobile station sends back an IDENTITY RESPONSE 
message. The IDENTITY RESPONSE message contains the identification parameters as requested by the network. 

Upon receipt of the IDENTITY RESPONSE the network shall stop timer T3270. 



4.3.3.3 



Abnormal cases 



(a) RR connection failure: 

Upon detection of a RR connection failure before the IDENTITY RESPONSE is received, the network shall 
release all MM connections (if any) and abort any ongoing MM specific procedure. 

(b) Expiry of timer T3270: 

The identification procedure is supervised by the network by the timer T3270. At expiry of the timer T3270 the 
network may release the RR connection. In this case, the network shall abort the identification procedure and any 
ongoing MM specific procedure, release all MM connections if any, and initiate the RR connection release 
procedure as described in 3GPP TS 44.018 [84] subclause 3.5 and 3GPP TS 25.331 [23c]. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 73 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

motoile station network 

ID REQ 

< Staut T3270 

ID RES 



> Stop T3270 

Figure 4.3/3GPP TS 24.008: Identification sequence 

(c) Requested identity is not available: 

If the MS cannot encode the requested identity in the IDENTITY RESPONSE message, e.g. because no valid 
SIM is available, then it shall encode the identity type as "No identity". 

4.3.4 IMSI detach procedure 

The IMSI detach procedure may be invoked by a mobile station if the mobile station is deactivated or if the Subscriber 
Identity Module (see 3GPP TS 42.017 [7] and 3GPP TS 31.102 [1 12]) is detached from the mobile station. 

In A/Gb mode and GERAN lu mode, a flag (ATT) broadcast in the L3-RR SYSTEM INFORMATION TYPE 3 
message on the BCCH is used by the network to indicate whether the detach procedure is required. The value of the 
ATT flag to be taken into account shall be the one broadcast when the mobile station was in MM idle. 

In UTRAN lu mode, a flag (ATT) in the CS domain specific system information element is used by the network to 
indicate whether the detach procedure is required. The value of the ATT flag to be taken into account shall be the one 
received when the mobile station was in MM idle. 

The procedure causes the mobile station to be indicated as inactive in the network. 

4.3.4.1 IMSI detach initiation by the mobile station 

The IMSI detach procedure consists only of the IMSI DETACH INDICATION message sent from the mobile station to 
the network. The mobile station then starts timer T3220 and enters the MM sublayer state IMSI DETACH INITIATED. 

If no RR connection exists, the MM sublayer within the mobile station will request the RR sublayer to establish a RR 
connection. If establishment of the RR connection is not possible because a suitable cell is not (or not yet) available 
then, the mobile station shall try for a period of at least 5 seconds and for not more than a period of 20 seconds to find a 
suitable cell. If a suitable cell is found during this time then, the mobile station shall request the RR sublayer to establish 
an RR connection, otherwise the IMSI detach is aborted. 

If a RR connection exists, the MM sublayer will release locally any ongoing MM connections before the IMSI 
DETACH INDICATION message is sent. 

The IMSI detach procedure may not be started if a MM specific procedure is active. If possible, the IMSI detach 
procedure is then delayed until the MM specific procedure is finished, else the IMSI detach is omitted. 

4.3.4.2 IMSI detach procedure in the network 

When receiving an IMSI DETACH INDICATION message, the network may set an inactive indication for the IMSI. 
No response is returned to the mobile station. After reception of the IMSI DETACH INDICATION message the 
network shall release locally any ongoing MM connections, and start the normal RR connection release procedure (see 
3GPP TS 44.018 [84] subclause 3.5 and 3GPP TS 25.331 [23c]). 

Only applicable for a network supporting VGCS: If an IMSI DETACH INDICATION message is received from the 
talking mobile station in a group call while the network is in service state MM CONNECTION ACTIVE (GROUP 
TRANSMIT MODE), the network shall release locally the ongoing MM connection and then go to the service state 
GROUP CALL ACTIVE. 

4.3.4.3 IMSI detach completion by the mobile station 

Timer T3220 is stopped when the RR connection is released. The mobile station should, if possible, delay the local 
release of the channel to allow a normal release from the network side until T3220 timeout. If this is not possible (e.g. 
detach at power down) the RR sublayer on the mobile station side should be aborted. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 74 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.3.4.4 Abnormal cases 

The following abnormal cases can be identified: 

a) Lower layer failure 

If the establishment of an RR connection is unsuccessful, or the RR connection is lost, the IMSI detach is aborted by 
the mobile station. 

b) Access barred because of common access class control or CS domain specific access control 

The signalling procedure for IMSI detach shall not be started. The MS starts the signalling procedure as soon as 
possible and if still necessary, i.e. when the barred state is removed or because of a cell change, or performs a 
local detach immediately or after an implementation dependent time. 

niotoile station network 

IMS I DET IND 

> 

Figure 4.4/3GPP TS 24.008: IMSI detach sequence 

4.3.5 Abort procedure 

The abort procedure may be invoked by the network to abort any on-going MM connection establishment or already 
established MM connection. The mobile station shall treat ABORT message as compatible with current protocol state 
only if it is received when at least one MM connection exists or an MM connection is being established. 

4.3.5.1 Abort procedure initiation by the network 

The abort procedure consists only of the ABORT message sent from the network to the mobile station. Before the 
sending of the ABORT message the network shall locally release any ongoing MM connection. After the sending the 
network may start the normal RR connection release procedure. 

The Cause information element indicates the reason for the abortion. The following cause values may apply: 

# 6: Illegal ME 

#17: Network failure 

4.3.5.2 Abort procedure in the mobile station 

At the receipt of the ABORT message the mobile station shall abort any MM connection establishment or call re- 
establishment procedure and release all MM connections (if any). If cause value #6 is received the mobile station shall 
delete any TMSI, LAI and ciphering key sequence number stored in the SIM/USIM, set the update status to ROAMING 
NOT ALLOWED (and store it in the SIM/USIM according to subclause 4.1.2.2) and consider the SIM/USIM invalid 
until switch off or the SIM/USIM is removed. As a consequence the mobile station enters state MM IDLE, substate NO 
IMSI after the release of the RR connection. 

The mobile station shall then wait for the network to release the RR connection - see subclause 4.5.3.1. 

4.3.6 MM information procedure 

The MM information message support is optional in the network. 

The MM information procedure may be invoked by the network at any time during an RR connection. 

4.3.6.1 MM information procedure initiation by the network 

The MM information procedure consists only of the MM INFORMATION message sent from the network to the 
mobile station. During an RR connection, the network shall send none, one, or more MM INFORMATION messages to 
the mobile station. If more than one MM INFORMATION message is sent, the messages need not have the same 
content. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 75 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

NOTE: The network may be able to select particular instants where it can send the MM INFORMATION 

message without adding delay to, or interrupting, any CM layer transaction, e.g. immediately after the 
AUTHENTICATION REQUEST message. 

4.3.6.2 MM information procedure in the mobile station 

When the mobile station (supporting the MM information message) receives an MM INFORMATION message, it shall 
accept the message and optionally use the contents to update appropriate information stored within the mobile station. 

If the mobile station does not support the MM information message the mobile station shall ignore the contents of the 
message and return an MM STATUS message with cause #97. 



4.4 MM specific procedures 



A MM specific procedure can only be started if no other MM specific procedure is running or no MM connection exists 
between the network and the mobile station. The end of the running MM specific procedure or the release of all MM 
connections have to be awaited before a new MM specific procedure can be started. 

During the lifetime of a MM specific procedure, if a MM connection establishment is requested by a CM entity, this 
request will either be rejected or be delayed until the running MM specific procedure is terminated (this depends on the 
implementation). 

Any MM common procedure (except IMSI detach) may be initiated during a MM specific procedure. 

Unless it has specific permission from the network (follow-on proceed) the mobile station side should await the release 
of the RR connection used for a MM specific procedure before a new MM specific procedure or MM connection 
establishment is started. 

NOTE: The network side may use the same RR connection for MM connection management. 

4.4.1 Location updating procedure 

The location updating procedure is a general procedure which is used for the following purposes: 

normal location updating (described in this subclause); 

periodic updating (see subclause 4.4.2); 

- IMSI attach (see subclause 4.4.3). 

The normal location updating procedure is used to update the registration of the actual Location Area of a mobile 
station in the network. The location updating type information element in the LOCATION UPDATING REQUEST 
message shall indicate normal location updating. The conditions under which the normal location updating procedure is 
used by a mobile station in the MM IDLE state are defined for each service state in subclause 4.2.2. 

Only applicable for mobile stations supporting VGCS listening or VBS listening: A mobile station in RR group receive 
mode is in the MM IDLE state, substate RECEIVING GROUP CALL (NORMAL SERVICE) or RECEIVING GROUP 
CALL (LIMITED SERVICE). To perform a location updating, the MS in RR group receive mode shall leave the group 
receive mode, establish an independent dedicated RR connection to perform the location updating as described above 
and return to the RR group receive mode afterwards. 

The normal location updating procedure shall also be started if the network indicates that the mobile station is unknown 
in the VLR as a response to MM connection establishment request. 

To limit the number of location updating attempts made, where location updating is unsuccessful, an attempt counter is 
used. The attempt counter is reset when a mobile station is switched on or a SIM/USIM card is inserted. 

Upon successful location updating the mobile station sets the update status to UPDATED in the SIM/USIM, and stores 
the Location Area Identification received in the LOCATION UPDATING ACCEPT message in the SIM/USIM. The 
attempt counter shall be reset. 

The detailed handling of the attempt counter is described in subclauses 4.4.4.6 to 4.4.4.9. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 76 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The Mobile Equipment shall contain a list of "forbidden location areas for roaming", as well as a list of "forbidden 
location areas for regional provision of service". These lists shall be erased when the MS is switched off or when the 
SIM/USIM is removed, and periodically (with period in the range 12 to 24 hours). The location area identification 
received on the BCCH that triggered the location updating request shall be added to the suitable list whenever a location 
update reject message is received with the cause "Roaming not allowed in this location area" or with the cause 
"Location Area not allowed". The lists shall accommodate each 10 or more location area identifications. When the list is 
full and a new entry has to be inserted, the oldest entry shall be deleted. 

In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 23.122 [14]. The MS 
shall construct the Location Area Identification of the cell from this chosen PLMN identity and the LAC received on the 
BCCH. If the constructed LAI is different from the stored LAI, the MS shall initiate the location updating procedure. 
The chosen PLMN identity shall be indicated to the RAN in the RRC INITIAL DIRECT TRANSFER message (see 
3GPP TS 25.331 [23c]). Whenever a LOCATION UPDATING REJECT message with the cause "PLMN not allowed" 
is received by the MS, the PLMN identity used to construct the LAI which triggered the location updating procedure 
shall be stored in the "forbidden PLMN list". Whenever a LOCATION UPDATING REJECT message is received by 
the MS with the cause "Roaming not allowed in this location area", "Location Area not allowed", or "No suitable cells 
in Location Area", the constructed LAI which triggered the location updating procedure shall be stored in the suitable 
list. 

The Mobile Equipment shall store a list of "equivalent PLMNs". This list is replaced or deleted at the end of each 
location update procedure, routing area update procedure and GPRS attach procedure. The stored list consists of a list of 
equivalent PLMNs as downloaded by the network plus the PLMN code of the registeredPLMN that downloaded the 
list. The stored list shall not be deleted when the MS is switched off The stored list shall be deleted if the SIM/USIM is 
removed. The maximum number of possible entries in the stored list is 16. 

The cell selection processes in the different states are described in 3GPP TS 43.022 [82] and 3GPP TS 45.008 [34]. 

The location updating procedure is always initiated by the mobile station. 

In the case that the mobile station is initiating an emergency call but, due to cell re-selection or redirection by the 
network, it moves to a different LAI then the mobile station may delay the location updating procedure in the new LA 
until after the emergency call is completed. 



4.4.2 Periodic updating 



Periodic updating may be used to notify periodically the availability of the mobile station to the network. Periodic 
updating is performed by using the location updating procedure. The location updating type information element in the 
LOCATION UPDATING REQUEST message shall indicate periodic updating. 

The procedure is controlled by the timer T3212 in the mobile station. If the timer is not already started, the timer is 
started each time the mobile station enters the MM IDLE substate NORMAL SERVICE or ATTEMPTing TO 
UPDATE. When the MS leaves the MM Idle State the timer T3212 shall continue running until explicitly stopped. 

The timer is stopped (shall be set to its initial value for the next start) when: 

- a LOCATION UPDATING ACCEPT or LOCATION UPDATING REJECT message is received; 

- an AUTHENTICATION REJECT message is received; 

the first MM message is received, or security mode setting is completed in the case of MM connection 
establishment, except when the most recent service state is LIMITED SERVICE; 

the mobile station has responded to paging and thereafter has received the first correct layer 3 message except 
RR message; 

the mobile station is deactivated (i.e. equipment powered down or SIM/USIM removed). 

When the timer T3212 expires, the location updating procedure is started and the timer shall be set to its initial value for 
the next start. If the mobile station is in other state than MM Idle when the timer expires the location updating 
procedure is delayed until the MM Idle State is entered. 

The conditions under which the periodic location updating procedure is used by a mobile station in the MM IDLE state 
are defined for each service state in subclause 4.2.2. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 77 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the mobile station is in service state NO CELL AVAILABLE, LIMITED SERVICE, PLMN SEARCH or PLMN 
SEARCH-NORMAL SERVICE when the timer expires the location updating procedure is delayed until this service 
state is left. 

In A/Gb mode and GERAN lu mode, the (periodic) location updating procedure is not started if the BCCH information 
at the time the procedure is triggered indicates that periodic location shall not be used. The timeout value is broadcasted 
in the L3-RR SYSTEM INFORMATION TYPE 3 message on the BCCH, in the Control channel description IE, see 
3GPPTS 44.018 [84] subclause 10.5.2.11. 

In UTRAN lu mode, the (periodic) location updating procedure is not started if the information on BCCH or in the last 
received dedicated system information at the time the procedure is triggered indicates that periodic location shall not be 
used. The timeout value is included in the CS domain specific system information element. 

The T3212 timeout value shall not be changed in the NO CELL AVAILABLE, LIMITED SERVICE, PLMN SEARCH 
and PLMN SEARCH-NORMAL SERVICE states. 

When a change of the T3212 timeout value has to be taken into account and the timer is running (at change of the 
serving cell or, change of the broadcast value of T3212), the MS shall behave as follows: 

Let tl be the new T3212 timeout value and let t be the current timer value at the moment of the change to the 
new T3212 timeout value; then the timer shall be restarted with the value t modulo tl. 

When the mobile station is activated, or when a change of the T3212 timeout value has to be taken into account and the 
timer is not running, the mobile station shall behave as follows: 

Let tl be the new T3212 timeout value, the new timer shall be started at a value randomly, uniformly drawn 
between and tl. 



4.4.3 IMSI attach procedure 



The IMSI attach procedure is the complement of the IMSI detach procedure (see subclause 4.3.4). It is used to indicate 
the IMSI as active in the network. 

In A/Gb mode and GERAN lu mode, a flag (ATT) is broadcast in the L3-RR SYSTEM INFORMATION TYPE 3 
message. It indicates whether the attach and detach procedures are required to be used or not. 

In UTRANmode, a flag (ATT) is included in the CS domain specific system information element. It indicates whether 
the attach and detach procedures are required to be used or not. 

The IMSI attach procedure is invoked if the detach/attach procedures are required by the network and an IMSI is 
activated in a mobile station (i.e. activation of a mobile station with plug-in SIM/USIM, insertion of a card in a card- 
operated mobile station etc.) within coverage area from the network or a mobile station with an IMSI activated outside 
the coverage area enters the coverage area. The IMSI attach procedure is used only if the update status is UPDATED 
and if the stored Location Area Identification is the same as the one which is actually broadcasted on the BCCH of the 
current serving cell. In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 
23.122 [14]. The MS shall use the IMSI attach procedure only if the update status is UPDATED and the stored Location 
Area Identification is equal to the combination of the chosen PLMN identity and the LAC received on the BCCH. 
Otherwise a normal location updating procedure (see subclause 4.4.1) is invoked independently of the ATT flag 
indication. 

IMSI attach is performed by using the location updating procedure. The location updating type information element in 
the LOCATION UPDATING REQUEST message shall in this case indicate IMSI attach. 

4.4.4 Generic Location Updating procedure 
4.4.4.1 Location updating initiation by the mobile station 

Any timer used for triggering the location updating procedure (e.g. T3211, T3212) is stopped if running. 

As no RR connection exists at the time when the location updating procedure has to be started, the MM sublayer within 
the mobile station will request the RR sublayer to establish a RR connection and enter state WAIT FOR RR 
CONNECTION (LOCATION UPDATE). The procedure for establishing an RR connection is described in 
3GPP TS 44.018 [84] subclause 3.3 and 3GPP TS 25.331 [23c]. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 78 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The mobile station initiates the location updating procedure by sending a LOCATION UPDATING REQUEST 
message to the network, starts the timer T3210 and enters state LOCATION UPDATING INITIATED. The location 
updating type information element shall indicate what kind of updating is requested. 

4.4.4.1 a Network Request for Additional mobile station Capability Information 

In A/Gb mode, the network may initiate the classmark interrogation procedure, for example, to obtain further 
information on the mobile station's encryption capabilities. 

4.4.4.2 Identification request from the network 

The network may initiate the identification procedure, e.g. if the network is unable to get the IMSI based on the TMSI 
and LAI used as identification by the mobile station (see subclause 4.3.3). 

4.4.4.3 Authentication by the network 

The authentication procedure (see subclause 4.3.2) may be initiated by the network upon receipt of the LOCATION 
UPDATING REQUEST message from the mobile station. (See the cases defined in 3GPP TS 42.009 [5]). 

4.4.4.4 Security mode setting by the network 

In A/Gb mode, the security mode setting procedure (see 3GPP TS 44.018 [84] subclause 3.4.7) may be initiated by the 
network, e.g., if a new TMSI has to be allocated. 

In lu mode, the security mode control procedure (see 3GPPTS 25.331 [23c] and 3GPPTS 44.118 [111]) maybe 
initiated by the network, e.g., if a new TMSI has to be allocated. 

4.4.4.5 Attempt Counter 

To limit the number of location updating attempts made, where location updating is unsuccessful, an attempt counter is 
used. It counts the number of consecutive unsuccessful location update attempts. 

The attempt counter is incremented when a location update procedure fails. The specific situations are specified in 

subclause 4.4.4.9. 

The attempt counter is reset when: 

the mobile station is powered on; 
- a SIM/USIM is inserted; 

location update is successfully completed; 

location update completed with cause #11, #12,#13 or #15 (see subclause 4.4.4.7). 
and in case of service state ATTEMPTING to UPDATE: 

a MS detects that a new location area is entered; 

expiry of timer T3212; 

location update is triggered by CM sublayer requests. 
The attempt counter is used when deciding whether to re-attempt a location update after timeout of timer T321 1 . 

4.4.4.6 Location updating accepted by the network 

If the location updating is accepted by the network a LOCATION UPDATING ACCEPT message is transferred to the 
mobile station. 

In case the identity confidentiality service is active (see subclauses 4.3.1 and 4.4.4.4), the TMSI reallocation may be 
part of the location updating procedure. The TMSI allocated is then contained in the LOCATION UPDATING 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 79 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

ACCEPT message together with the location area identifier LAI. The network shall in this case start the supervision 
timer T3250 as described in subclause 4.3.1. 

In a shared network, the network shall indicate in the LAI the PLMN identity of the CN operator that has accepted the 
location updating (see 3GPP TS 23.251 [109]). 

If the network wishes to prolong the RR connection to allow the mobile station to initiate MM connection establishment 
(for example if the mobile station has indicated in the LOCATION UPDATING REQUEST that it has a follow-on 
request pending) the network shall send "follow on proceed" in the LOCATION UPDATING ACCEPT and start timer 
T3255. 

The mobile station receiving a LOCATION UPDATING ACCEPT message shall store the received location area 
identification LAI, stop timer T3210, reset the attempt counter and set the update status in the SIM/USIM to 
UPDATED. If the message contains an IMSI, the mobile station is not allocated any TMSI, and shall delete any TMSI 
in the SIM/USIM accordingly. If the message contains a TMSI, the mobile station is allocated this TMSI, and shall 
store this TMSI in the SIM/USIM and a TMSI REALLOCATION COMPLETE shall be returned to the network. If 
neither IMSI nor TMSI is received in the LOCATION UPDATING ACCEPT message, the old TMSI if any available 
shall be kept. 

If the LAI or PLMN identity contained in the LOCATION UPDATING ACCEPT message is a member of the list of 
"forbidden location areas for regional provision of service", the list of "forbidden location areas for roaming" or the 
"forbidden PLMN list" then such entries shall be deleted. 

The network may also send a list of "equivalent PLMNs" in the LOCATION UPDATING ACCEPT message. Each 
entry of the list contains a PLMN code (MCC+MNC). The mobile station shall store the list, as provided by the 
network, except that any PLMN code that is already in the "forbidden PLMN list" shall be removed from the 
"equivalent PLMNs" list before it is stored by the mobile station. In addition the mobile station shall add to the stored 
list the PLMN code of the registered PLMN that sent the list. All PLMNs in the stored Ust shall be regarded as 
equivalent to each other for PLMN selection, cell selection/re-selection and handover. The stored list in the mobile 
station shall be replaced on each occurrence of the LOCATION UPDATING ACCEPT message. If no list is contained 
in the message, then the stored list in the mobile station shall be deleted. The list shall be stored in the mobile station 
while switched off so that it can be used for PLMN selection after switch on. 

After that, the mobile station shall act according to the presence of the "Follow-on proceed" information element in the 
LOCATION UPDATING ACCEPT; if this element is present and the mobile station has a CM application request 
pending, it shall send a CM SERVICE REQUEST to the network and proceed as in subclause 4.5.1.1. Otherwise, it 
shall start timer T3240 and enter state WAIT FOR NETWORK COMMAND. 

Furthermore, the network may grant authorisation for the mobile station to use GSM-Cordless Telephony System (CTS) 
in the Location Area and its immediate neighbourhood. The mobile should memorise this permission in non-volatile 
memory. If the "CTS permission" IE is not present in the message, the mobile is not authorised to use GSM-CTS, and 
shall accordingly delete any memorised permission. 

NOTE 1 : the interaction between CTS and GPRS procedures are not yet defined. 

The network may also send a list of local emergency numbers in the LOCATION UPDATING ACCEPT, by including 
the Emergency Number List IE. The mobile equipment shall store the list, as provided by the network, except that any 
emergency number that is already stored in the SIM/USIM shall be removed from the list before it is stored by the 
mobile equipment. If there are no emergency numbers stored on the SIM/USIM, then before storing the received list the 
mobile equipment shall remove from it any emergency number stored permanently in the ME for use in this case (see 
3GPP TS 22.101 [8]). The list stored in the mobile equipment shall be replaced on each receipt of a new Emergency 
Number List IE. 

The emergency number(s) received in the Emergency Number List IE are valid only in networks with the same MCC as 
in the cell on which this IE is received. If no list is contained in the LOCATION UPDATING ACCEPT message, then 
the stored list in the mobile equipment shall be kept, except if the mobile equipment has successfully registered to a 
PLMN with an MCC different from that of the last registered PLMN. 

The mobile equipment shall use the stored list of emergency numbers received from the network in addition to the 
emergency numbers stored on the SIM/USIM or ME to detect that the number dialled is an emergency number. 

NOTE 2: The mobile equipment may use the emergency numbers list to assist the end user in determining whether 
the dialled number is intended for an emergency service or for another destination, e.g. a local directory 
service. The possible interactions with the end user are implementation specific. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 80 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The list of emergency numbers shall be deleted at switch off and removal of the SIM/USIM. The mobile equipment 
shall be able to store up to ten local emergency numbers received from the network. 

4.4.4.7 Location updating not accepted by the network 

If the location updating cannot be accepted the network sends a LOCATION UPDATING REJECT message to the 
mobile station. The mobile station receiving a LOCATION UPDATING REJECT message shall stop the timer T3210, 
store the reject cause, start T3240, enter state LOCATION UPDATING REJECTED await the release of the RR 
connection triggered by the network, and for all causes except #12, #14 and #15 deletes the list of "equivalent PLMNs". 

Upon the release of the RR connection the mobile station shall take the following actions depending on the stored reject 

cause: 

# 2: (IMSI unknown in HLR); 
#3: (Illegal MS); or 

# 6: (Illegal ME). 

The mobile station shall set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM 
according to subclause 4.1.2.2), and delete any TMSI, stored LAI and ciphering key sequence number and shall 
consider the SIM/USIM as invalid for non-GPRS services until switch-off or the SIM/USIM is removed. 

#11: (PLMN not allowed); 

The mobile station shall delete any LAI, TMSI and ciphering key sequence number stored in the SIM/USIM, 
reset the attempt counter, set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM 
according to subclause 4.1.2.2). The mobile station shall store the PLMN identity in the "forbidden PLMN list". 

The MS shall perform a PLMN selection when back to the MM IDLE state according to 3GPP TS 23.122 [14]. 

#12: (Location Area not allowed); 

The mobile station shall delete any LAI, TMSI and ciphering key sequence number stored in the SIM/USIM, 
reset the attempt counter, set the update status to ROAMING NOT ALLOWED (and store it in the SIM/USIM 
according to subclause 4.1.2.2). 

The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service". 

The MS shall perform a cell selection when back to the MM IDLE state according to 3GPP TS 43.022 [82] and 
3GPPTS 25.304. 

# 13: (Roaming not allowed in this location area). 

The mobile station shall reset the attempt counter, set the update status to ROAMING NOT ALLOWED (and 
store it in the SIM/USIM according to clause 4.1.2.2). 

The mobile station shall store the LAI in the list of "forbidden location areas for roaming". 

The mobile station shall perform a PLMN selection instead of a cell selection when back to the MM IDLE state 
according to 3GPP TS 23.122 [14]. 

# 15: (No Suitable Cells In Location Area). 

The mobile station shall reset the attempt counter, set the update status to ROAMING NOT ALLOWED (and 
store it in the SIM/USIM according to clause 4.1.2.2). 

The mobile station shall store the LAI in the list of "forbidden location areas for roaming". 

The mobile station shall search for a suitable cell in another location area in the same PLMN according to 
3GPP TS 43.022 [82] and 3GPP TS 25.304. 

Other values are considered as abnormal cases and the specification of the mobile station behaviour in those cases is 
given in subclause 4.4.4.9. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 81 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.4.4.8 Release of RR connection after location updating 

When the Location updating procedure is finished (see subclause s 4.4.4.6 and 4.4.4.7) the mobile station shall (except 
in the case where the mobile has a follow-on CM application request pending and has received the follow-on proceed 
indication, see subclause 4.4.4.6) set timer T3240 and enter the state WAIT FOR NETWORK COMMAND, expecting 
the release of the RR connection. The network may decide to keep the RR connection for network initiated 
establishment of a MM connection, or to allow for mobile initiated MM connection establishment. 

Any release of the RR connection shall be initiated by the network according to subclause 3.5 in 3GPP TS 44.018 [84], 
and 3GPP TS 25.331 [23c]. If the RR connection is not released within a given time controlled by the timer T3240, the 
mobile station shall abort the RR connection. In both cases, either after a RR connection release triggered from the 
network side or after a RR connection abort requested by the MS-side, the MS shall return to state MM IDLE. 

At transition to state MM IDLE, substates NORMAL SERVICE or RECEIVING GROUP CALL (NORMAL 
SERVICE) or ATTEMPTING TO UPDATE either timer T3212 or timer T3211 is started as described in 
subclause 4.4.4.9. 

4.4.4.9 Abnormal cases on the mobile station side 

The different abnormal cases that can be identified are the following: 

a) Access barred because of common access class control or CS domain specific access control 

The location updating procedure is not started. The mobile station stays in the current serving cell and applies 
normal cell reselection process. The procedure is started as soon as possible and if still necessary (when the 
barred state is ended or because of a cell change). 

b) The answer to random access is an IMMEDIATE ASSIGNMENT REJECT message (A/Gb mode only) 

The location updating is not started. The mobile station stays in the chosen cell and applies normal cell selection 
process. The waiting timer T3122 is reset when a cell change occurs. The procedure is started as soon as possible 
after T3122 timeout if still necessary. 

c) Random access failure (A/Gb mode only) 

Timer T3213 is started. When it expires the procedure is attempted again if still necessary. 

NOTE 1: As specified in 3GPP TS 45.008 [34], a cell reselection then takes place, with return to the cell inhibited 
for 5 seconds if there is at least one other suitable cell. Typically the selection process will take the 
mobile station back to the cell where the random access failed after 5 seconds. 

If at the expiry of timer T3213 a new cell has not been selected due to the lack of valid information (see 
3GPP TS 45.008 [34]), the mobile station may as an option delay the repeated attempt for up to 8 seconds to 
allow cell re-selection to take place. In this case the procedure is attempted as soon as a new cell has been 
selected or the mobile station has concluded that no other cell can be selected. 

If random access failure occurs for two successive random access attempts for location updating the mobile 
station proceeds as specified below. 

d) RR connection failure 

The procedure is aborted and the mobile station proceeds as specified below. 

e) T3210 timeout 

The procedure is aborted, the RR connection is aborted and the MS proceeds as specified below. 

f) RR release before the normal end of procedure 

The procedure is aborted and the mobile station proceeds as specified below, except in the following 
implementation option case f . 1 . 

f.l)RR release in lu mode (i.e. RRC connection release) with, for example, cause "Normal", "User inactivity" or 
"Directed signalling connection re-estabhshment" (see 3GPP TS 25.331 [32c] and 3GPP TS 44.118 [111]) 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 82 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The location updating procedure shall be initiated again, if the following conditions apply: 

i) The original location updating procedure was initiated over an existing RRC connection; and 

ii) No SECURITY MODE COMMAND message and no Non- Access Stratum (NAS) messages relating to 
the CS signalling connection (e.g. CS authentication procedures, see subclause 4.3.2), were received after the 
LOCATION UPDATING REQUEST message was transmitted. 

NOTE 2: The RRC connection release cause that triggers the re-initiation of the location updating procedure is 
implementation specific. 

g) Location updating reject, other causes than those treated in subclause 4.4.4.7 

Upon reception of the cause codes # 95, # 96, # 97, # 99 and #111 the MS should set the attempt counter to 4. 
The MS waits for release of the RR connection as specified in subclause 4.4.4.8, and then proceeds as specified 
below. 

h) RR connection establishment failure (lu mode only) 

The procedure is aborted and the mobile station proceeds as specified below. 

NOTE 3: Case h) covers all cases when the signalling connection cannot be established, including random access 
failure and access reject. As the RRC protocol has error specific retransmission mechanisms (see 
3GPP TS 25.331 [23c]), there is no need to distinguish between the different error cases within MM. 

In cases d) to h) (except in the case f.l) above and for repeated failures as defined in c) above the mobile station 
proceeds as follows. Timer T3210 is stopped if still running. The RR Connection is aborted in case of timer T3210 
timeout. The attempt counter is incremented. The next actions depend on the Location Area Identities (stored and 
received from the BCCH of the current serving cell) and the value of the attempt counter. 

- the update status is UPDATED, and the stored LAI is equal to the one received on the BCCH from the current 
serving cell and the attempt counter is smaller than 4: 

The mobile station shall keep the update status to UPDATED, the MM IDLE sub-state after the RR connection 
release is NORMAL SERVICE. The mobile station shall memorize the location updating type used in the 
location updating procedure. It shall start timer T321 1 when the RR connection is released. When timer T321 1 
expires the location updating procedure is triggered again with the memorized location updating type; 

- either the update status is different from UPDATED, or the stored LAI is different from the one received on the 
BCCH from the current serving cell, or the attempt counter is greater or equal to 4: 

When the RR connection is released the mobile station shall delete any LAI, TMSI, ciphering key sequence 
number stored in the SIM/USIM, and list of equivalent PLMNs, set the update status to NOT UPDATED and 
enter the MM IDLE sub-state ATTEMPTING TO UPDATE (see subclause 4.2.2.2 for the subsequent actions) 
or optionally the MM IDLE sub-state PLMN SEARCH (see subclause 4.2.1.2) in order to perform a PLMN 
selection according to 3GPP TS 23.122 [14]. If the attempt counter is smaller than 4, the mobile station shall 
memorize that timer T3211 is to be started when the RR connection is released, otherwise it shall memorize that 
timer T3212 is to be started when the RR connection is released. 

4.4.4.1 Abnormal cases on the network side 

a) RR connection failure 

If a RR connection failure occurs during a common procedure integrated with the location updating procedure, the 
behaviour of the network should be according to the description of that common procedure. 

If a RR connection failure occurs when a common procedure does not exist, the location updating procedure towards 
the mobile station should be aborted. 

b) protocol error 

If the LOCATION UPDATING REQUEST message is received with a protocol error, the network should, if possible, 
return a LOCATION UPDATING REJECT message with one of the following Reject causes: 

#96: Mandatory information element error 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 83 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

#99: Information element non-existent or not implemented 
#100: Conditional IE error 
#111: Protocol error, unspecified 
Having sent the response, the network should start the channel release procedure (see subclause 3.5). 

mobile station network 

LOG UPD REQ 
Start T3210 > 

LOG UPD AGC 
Stop T32 10 < 

LOG UPD REJ 

Figure 4.5/3GPP TS 24.008: Location updating sequence 

4.4.5 Void 

4.4.6 Void 

4.5 Connection management sublayer service provision 

The concept of MM connection is introduced in this subclause. This concept is mainly a descriptive tool: The 
establishment of an MM connection by the network can be local (i.e. it is achieved by the transmission of the first CM 
layer message and without the transmission of any MM layer messages) or can be achieved by the transmission of a CM 
SERVICE PROMPT message (eg. in the case of certain ring back services). The release of an MM connection by the 
network or by the mobile station is always local, i.e. these purposes can be achieved without sending any MM messages 
over the radio interface. (On the contrary, establishment of an MM connection by the mobile station requires the 
sending of MM messages over the radio interface. An exception is VGCS, where an MM connection will be established 
as result of an uplink access procedure (see subclause 3.7.2.1.1in 3GPP TS 44.018 [84]).) 

The Mobility Management (MM) sublayer is providing connection management services to the different entities of the 
upper Connection management (CM) sublayer (see 3GPP TS 24.007 [20]). It offers to a CM entity the possibility to use 
an MM connection for the exchange of information with its peer entity. An MM connection is established and released 
on request from a CM entity. Different CM entities communicate with their peer entity using different MM connections. 
Several MM connections may be active at the same time. 

An MM connection requires an RR connection. All simultaneous MM connections for a given mobile station use the 
same RR connection. 

In the following subclause s, the procedures for establishing, re-establishing, maintaining, and releasing an MM 
connection are described, usually separately for the mobile station and the network side. 

4.5.1 IVIIVI connection establishment 

4.5.1 .1 MM connection establishment initiated by the mobile station 

Upon request of a CM entity to establish an MM connection the MM sublayer first decides whether to accept, delay, or 
reject this request: 

An MM connection establishment may only be initiated by the mobile station when the following conditions are 
fulfilled: 

- Its update status is UPDATED. 

- The MM sublayer is in one of the states MM IDLE, RR CONNECTION RELEASE NOT ALLOWED or 
MM connection active but not in MM connection active (Group call). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 84 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

An exception from this general rule exists for emergency calls (see subclause 4.5.1.5). A further exception is 
defined in the following clause. 

If an MM specific procedure is running at the time the request from the CM sublayer is received, and the 
LOCATION UPDATING REQUEST message has been sent, the request will either be rejected or delayed, 
depending on implementation, until the MM specific procedure is finished and, provided that the network has 
not sent a "follow-on proceed" indication, the RR connection is released. If the LOCATION UPDATING 
REQUEST message has not been sent, the mobile station may include a "follow-on request" indicator in the 
message. The mobile station shall then delay the request until the MM specific procedure is completed, when it 
may be given the opportunity by the network to use the RR connection: see subclause 4.4.4.6. 

In order to establish an MM connection, the mobile station proceeds as follows: 

a) If no RR connection exists, the MM sublayer requests the RR sublayer to establish an RR connection and enters 
MM sublayer state WAIT FOR RR CONNECTION (MM CONNECTION). This request contains an 
establishment cause and a CM SERVICE REQUEST message. When the establishment of an RR connection is 
indicated by the RR sublayer, the MM sublayer of the mobile station starts timer T3230, gives an indication to 
the CM entity that requested the MM connection establishment, and enters MM sublayer state WAIT FOR 
OUTGOING MM CONNECTION. 

b) If an RR connection is available, the MM sublayer of the mobile station sends a CM SERVICE REQUEST 
message to the network, starts timer T3230, stops and resets timer T3241, gives an indication to the CM entity 
that requested the MM connection establishment, and enters: 

- MM sublayer state WAIT FOR OUTGOING MM CONNECTION, if no MM connection is active; 

- MM sublayer state WAIT FOR ADDITIONAL OUTGOING MM CONNECTION, if at least one MM 
connection is active; 

- If an RR connection exists but the mobile station is in the state WAIT FOR NETWORK COMMAND then 
any requests from the CM layer that are received will either be rejected or delayed until this state is left. 

c) Only applicable for mobile stations supporting VGCS talking: 

If a mobile station which is in the MM sublayer state MM IDLE, service state RECEIVING GROUP CALL 

(NORMAL SERVICE), receives a request from the GCC sublayer to perform an uplink access, the MM sublayer 
requests the RR sublayer to perform an uplink access procedure and enters MM sublayer state WAIT FOR RR 
CONNECTION (GROUP TRANSMIT MODE). 

When a successful uplink access is indicated by the RR sublayer, the MM sublayer of the mobile station gives an 
indication to the GCC sublayer and enters MM sublayer state MM CONNECTION ACTIVE (GROUP 
TRANSMIT MODE). 

When an uplink access reject is indicated by the RR sublayer, the MM sublayer of the mobile station gives an 
indication to the GCC sublayer and enters the MM sublayer state MM IDLE, service state RECEIVING GROUP 
CALL (NORMAL SERVICE). 

In the network, if an uplink access procedure is performed, the RR sublayer in the network provides an 
indication to the MM sublayer together with the mobile subscriber identity received in the TALKER 
INDICATION message. The network shall then enter the MM sublayer state MM CONNECTION ACTIVE 
(GROUP TRANSMIT MODE). 

The CM SERVICE REQUEST message contains the: 

mobile identity according to subclause 10.5.1.4; 

mobile station classmark 2; 

- ciphering key sequence number; and 

CM service type identifying the requested type of transaction (e.g. mobile originating call establishment, 
emergency call establishment, short message service, supplementary service activation, location services). 

A MS supporting eMLPP may optionally include a priority level in the CM SERVICE REQUEST message. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 85 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

A collision may occur when a CM layer message is received by the mobile station in MM sublayer state WAIT FOR 
OUTGOING MM CONNECTION or in WAIT FOR ADDITIONAL OUTGOING MM CONNECTION. In this case 
the MM sublayer in the MS shall establish a new MM connection for the incoming CM message as specified in 
subclause 4.5.1.3. 

Upon receiving a CM SERVICE REQUEST message, the network shall analyse its content. The type of semantic 
analysis may depend on other on going MM connection(s). Depending on the type of request and the current status of 
the RR connection, the network may start any of the MM common procedures and RR procedures. 

In A/Gb mode, the network may initiate the classmark interrogation procedure, for example, to obtain further 
information on the mobile station's encryption capabilities. 

The identification procedure (see subclause 4.3.3) may be invoked for instance if a TMSI provided by the mobile 
station is not recognized. 

The network may invoke the authentication procedure (see subclause 4.3.2) depending on the CM service type. 

In A/Gb mode, the network decides also if the ciphering mode setting procedure shall be invoked (see subclause 3.4.7 
in 3GPPTS 44.018 [84]). 

In lu mode, the network decides also if the security mode control procedure shall be invoked (see 3GPP TS 25.331 
[23c] and 3GPPTS 44.118 [111]). 

NOTE: If the CM_SERVICE_REQUEST message contains a priority level the network may use this to perform 
queuing and pre-emption as defined in 3GPP TS 23.067 [88]. 

In A/Gb mode, an indication from the RR sublayer that the ciphering mode setting procedure is completed, or reception 
of a CM SERVICE ACCEPT message, shall be treated as a service acceptance indication by the mobile station. 

In lu mode, an indication from the RR sublayer that the security mode control procedure is completed, or reception of a 
CM SERVICE ACCEPT message, shall be treated as a service acceptance indication by the mobile station. The 
procedures in subclause 4.1.1.1.1 shall always have precedence over this subclause. 

In lu mode, during a MM connection establishment for all services, except for emergency call (see subclause 4.1.1.1.1), 
the security mode control procedure with activation of integrity protection shall be invoked by the network unless 
integrity protection is already started (see subclause 4.1.1.1.1). 

The MM connection establishment is completed, timer T3230 shall be stopped, the CM entity that requested the MM 
connection shall be informed, and MM sublayer state MM CONNECTION ACTIVE is entered. The MM connection is 
considered to be active. 

If the service request cannot be accepted, the network returns a CM SERVICE REJECT message to the mobile station. 

The reject cause information element (see subclause 10.5.3.6 and annex G) indicates the reason for rejection. The 
following cause values may apply: 

#4: IMSI unknown in VLR 

#6: Illegal ME 

#17: Network failure 

#22: Congestion 

#32: Service option not supported 

#33: Requested service option not subscribed 

#34: Service option temporarily out of order 

If no other MM connection is active, the network may start the RR connection release (see subclause 3.5) when the CM 
SERVICE REJECT message is sent. 

If a CM SERVICE REJECT message is received by the mobile station, timer T3230 shall be stopped, the requesting 
CM sublayer entity informed. Then the mobile station shall proceed as follows: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 86 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the cause value is not #4 or #6 the MM sublayer returns to the previous state (the state where the request was 
received). Other MM connections shall not be affected by the CM SERVICE REJECT message. 

If cause value #4 is received, the mobile station aborts any MM connection, deletes any TMSI, LAI and 
ciphering key sequence number in the SIM/USIM, changes the update status to NOT UPDATED (and stores it in 
the SIM/USIM according to subclause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK 
COMMAND. If subsequently the RR connection is released or aborted, this will force the mobile station to 
initiate a normal location updating). Whether the CM request shall be memorized during the location updating 
procedure, is a choice of implementation. 

If cause value #6 is received, the mobile station aborts any MM connection, deletes any TMSI, LAI and 
ciphering key sequence number in the SIM/USIM, changes the update status to ROAMING NOT ALLOWED 
(and stores it in the SIM/USIM according to subclause 4.1.2.2), and enters the MM sublayer state WAIT FOR 
NETWORK COMMAND. The mobile station shall consider the SIM/USIM as invalid for non-GPRS services 
until switch-off or the SIM/USIM is removed. 

4.5.1.2 Abnormal cases 

Mobile station side: 

a) RR connection failure or IMSI deactivation 

If an RR connection failure occurs, except in the following implementation option case a. 1, or the IMSI is 
deactivated during the establishment of an MM connection, the MM connection establishment is aborted, timers 
T3230 is stopped, and an indication is given to the CM entity that requested the MM connection establishment. 
This shall be treated as a rejection for establishment of the new MM connection, and the MM sublayer shall 
release all active MM connections. 

a.l) RR connection failure in lu mode (i.e. RRC connection release) with, for example, cause "Normal", "User 
inactivity" or "Directed signalling connection re-establishment" (see 3GPP TS 25.331 [32c] and 3GPP 
TS 44.118 [111]) 

The MM connection establishment procedure shall be initiated again, if the following conditions apply: 

i) The original MM connection establishment was initiated over an existing RRC connection; and 

ii) No SECURITY MODE COMMAND message and no Non- Access Stratum (NAS) messages relating to 
the CS signalling connection (e.g. CS authentication procedures, see subclause 4.3.2), were received after the 
CM SERVICE REQUEST message was transmitted. 

NOTE 1 : The RRC connection release cause that triggers the re-initiation of the MM connection establishment 
procedure is implementation specific. 

b) T3230 expiry 

If T3230 expires (i.e. no response is given but a RR connection is available) the MM connection establishment is 
aborted and the requesting CM sublayer is informed. If no other MM connection exists then the mobile station 
shall proceed as described in subclause 4.5.3.1 for release of the RR connection. Otherwise the mobile station 
shall return to the MM sublayer state where the request of an MM connection was received, i.e. to MM sublayer 
state MM connection active. Other ongoing MM connections (if any) shall not be affected. 

c) Reject cause values #95, #96, #97, #99, #100, #1 1 1 received 

The same actions as on timer expiry shall be taken by the mobile station. 

d) Random access failure or RR connection establishment failure 

If the mobile station detects a random access failure or RR connection establishment failure during the 
establishment of an MM connection, it aborts the MM connection establishment and gives an indication to the 
CM entity that requested the MM connection establishment. 

NOTE 2: Further actions of the mobile station depend on the RR procedures and MM specific procedures during 
which the abnormal situation has occurred and are described together with those procedures. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 87 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

e) Access barred because of CS domain specific access control 

The MM connection establishment shall not be initiated. The MS stays in the current serving cell and applies 
normal cell reselection process. The MM connection establishment may be initiated by CM layer if it is still 
necessary, i.e. when access is granted or because of a cell change. 

Network side: 

a) RR connection failure 

The actions to be taken upon RR connection failure within a MM common procedure are described together with 
that procedure. A RR connection failure occurring outside such MM common procedures, shall trigger the 
release of all active MM connections if any. 

b) Invalid message or message content 

Upon reception of an invalid initial message or a CM SERVICE REQUEST message with invalid content, a CM 
SERVICE REJECT message shall be returned with one of the following appropriate Reject cause indications: 

# 95: Semantically incorrect message 

# 96: Mandatory information element error 

# 97: Message type non-existent or not implemented 

# 99: Information element non-existent or not implemented 

# 100: Conditional IE error 

#111: Protocol error, unspecified 

When the CM SERVICE REJECT message has been sent, the network may start RR connection release if no 
other MM connections exist or if the abnormal condition also has influence on the other MM connections. 

4.5.1 .3 MM connection establishment initiated by the network 

4.5.1 .3.1 Mobile Terminating CM Activity 

When a CM sublayer entity in the network requests the MM sublayer to establish a MM connection, the MM sublayer 
will request the establishment of an RR connection to the RR sublayer if no RR connection to the desired mobile station 
exists. The MM sublayer is informed when the paging procedure is finished (see 3GPP TS 44.018 [84] subclause 3.3.2 
and 3GPP TS 25.331 [23c]) and the mobile station shall enter the MM state WAIT FOR NETWORK COMMAND. 

In A/Gb mode, when an RR connection is established (or if it already exists at the time the request is received), the MM 
sublayer may initiate any of the MM common procedures (except IMSI detach); it may request the RR sublayer to 
perform the RR classmark interrogation procedure, and/or the security mode setting procedure. 

In lu mode, when an RR connection is established (or if it already exists at the time the request is received), the MM 
sublayer may initiate any of the MM common procedures (except IMSI detach); it may request the RR sublayer to 
perform the security mode control procedure. 

When all MM and RR procedures are successfully completed which the network considers necessary, the MM sublayer 
will inform the requesting mobile terminating CM sublayer entity on the success of the MM connection establishment. 

If an RR connection already exists and no MM specific procedure is running, the network may also establish a new 
mobile terminating MM connection by sending a CM message with a new PD/TI combination. 

If the MS receives the first CM message in the MM states WAIT FOR NETWORK COMMAND or RR 
CONNECTION RELEASE NOT ALLOWED, the MS shall stop and reset the timers T3240 and T3241 and shall enter 
the MM state MM CONNECTION ACTIVE. 

In A/Gb mode, if the establishment of an RR connection is unsuccessful, or if any of the MM common procedures or 
the security mode setting fail, this is indicated to the CM layer with an appropriate error cause. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 88 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

In lu mode, if the establishment of an RR connection is unsuccessful, or if any of the MM common procedures or the 
security mode control fail, this is indicated to the CM layer with an appropriate error cause. 

If an RR connection used for a MM specific procedure exists to the mobile station, the CM request may be rejected or 
delayed depending on implementation. When the MM specific procedure has been completed, the network may use the 
same RR connection for the delayed CM request. 

Only applicable in case of VGCS talking: 

In the MM CONNECTION ACTIVE (GROUP TRANSMIT MODE) the mobile station is in RR Group transmit mode. 
There shall be only one MM connection active. 

When in MM CONNECTION ACTIVE (GROUP TRANSMIT MODE) state, the MM sublayer in the network shall 
reject the request for the establishment of another MM connection by any CM layer. 

If the RR sublayer in the network indicates a request to perform a transfer of the mobile station from RR connected 
mode to RR Group transmit mode which will result in a transition from MM CONNECTION ACTIVE state to MM 
CONNECTION ACTIVE (GROUP TRANSMIT MODE) state in the MM sublayer, the MM sublayer shall not allow 
the transition if more than one MM connection is active with the mobile station. 

4.5.1 .3.2 Mobile Originating CM Activity $(CCBS)$ 

When a CM sublayer entity in the network requests the MM sublayer to establish a MM connection, the MM sublayer 
will request the establishment of an RR connection to the RR sublayer if no RR connection to the desired mobile station 
exists. The MM sublayer is informed when the paging procedure is finished (see 3GPP TS 44.018 [84] subclause 3.3.2 
and 3GPP TS 25.331 [23c]) and the mobile station shall enter the MM state WAIT FOR NETWORK COMMAND. 

In A/Gb mode, when an RR connection is established (or if it already exists at the time the request is received), the MM 
sublayer may initiate any of the MM common procedures (except IMSI detach), it may request the RR sublayer to 
perform the RR classmark interrogation procedure and/or the security mode setting procedure. 

In lu mode, when an RR connection is established (or if it already exists at the time the request is received), the MM 
sublayer may initiate any of the MM common procedures (except IMSI detach), it may request the RR sublayer to 
perform the security mode control procedure. 

The network should use the information contained in the Mobile Station Classmark Type 2 IE on the mobile station's 
support for "Network Initiated MO CM Connection Request" to determine whether to: 

not start this procedure (eg if an RR connection already exists), or, 

to continue this procedure, or, 

to release the newly established RR connection. 

In the case of a "Network Initiated MO CM Connection Request" the network shall use the established RR connection 
to send a CM SERVICE PROMPT message to the mobile station. 

If the mobile station supports "Network Initiated MO CM Connection Request", the MM sublayer of the MS gives an 
indication to the CM entity identified by the CM SERVICE PROMPT message and enters the MM sublayer state 
PROCESS CM SERVICE PROMPT. In the state PROCESS CM SERVICE PROMPT the MM sublayer waits for 
either the rejection or confirmation of the recall by the identified CM entity. Any other requests from the CM entities 
shall either be rejected or delayed until this state is left. 

When the identified CM entity informs the MM sublayer, that it has send the first CM message in order to start the CM 
recall procedure the MM sublayer enters the state MM CONNECTION ACTIVE. 

If the identified CM entity indicates that it will not perform the CM recall procedure and all MM connections are 
released by their CM entities the MS shall proceed according to subclause 4.5.3.1. 

If the CM SERVICE PROMPT message is received by the MS in MM sublayer states WAIT FOR OUTGOING MM 
CONNECTION or in WAIT FOR ADDITIONAL OUTGOING MM CONNECTION then the mobile station shall send 
an MM STATUS message with cause " Message not compatible with protocol state". 

A mobile that does not support "Network Initiated MO CM Connection Request" shall return an MM STATUS message 
with cause #97 "message type non-existent or not implemented" to the network. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 89 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the mobile station supports "Network Initiated MO CM Connection Request" but the identified CM entity in the 
mobile station does not provide the associated support, then the mobile station shall send an MM STATUS message 
with cause "Service option not supported". In the case of a temporary CM problem (eg lack of transaction identifiers) 
then the mobile station shall send an MM STATUS message with cause "Service option temporarily out of order". 

If an RR connection already exists and no MM specific procedure is running, the network may use it to send the CM 
SERVICE PROMPT message. 

In A/Gb mode, if the establishment of an RR connection is unsuccessful, or if any of the MM common procedures or 
the security mode setting fail, this is indicated to the CM layer in the network with an appropriate error cause. 

In lu mode, if the establishment of an RR connection is unsuccessful, or if any of the MM common procedures or the 
security mode control fail, this is indicated to the CM layer in the network with an appropriate error cause. 

If an RR connection used for a MM specific procedure exists to the mobile station, the "Network Initiated MO CM 
Connection Request" may be rejected or delayed depending on implementation. When the MM specific procedure has 
been completed, the network may use the same RR connection for the delayed "Network Initiated MO CM Connection 
Request". 

4.5.1 .3.3 Paging response in lu mode (lu mode only) 

The network may initiate the paging procedure for CS services when the MS is IMSI attached for CS services. To 
initiate the procedure, the MM entity requests the RR sublayer to initiate paging (see 3GPP TS 25.331 [23c], 
3GPP TS 25.413and 3GPP TS 44.1 18 [111]) for CS services. 

At reception of a paging message, the RR sublayer in the MS shall deliver a paging indication to the MM sublayer if the 
paging was initiated by the MM entity in the network (see 3GPPTS 25.331 [23c] and 3GPP TS 44.118 [111]). The MS 
shall respond with the PAGING RESPONSE message defined in 3GPP TS 44.018 [84], subclause 9.1.25. For reasons 
of backward compatibility the paging response shall use the RR protocol discriminator. 

If the MS receives a paging request for CS services during an ongoing MM procedure, and the MS has already 
requested the establishment of a radio connection, the MS shall ignore the paging request and the MS and the network 
shall continue the MM procedure. 

4.5.1.4 Abnormal cases 

The behaviour upon abnormal events is described together with the relevant RR procedure or MM common procedure. 

4.5.1 .5 MM connection establishment for emergency calls 

A MM connection for an emergency call may be established in all states of the mobility management sublayer which 
allow MM connection establishment for a normal originating call. In addition, establishment may be attempted in all 
service states where a cell is selected (see subclause 4.2.2) but not in the MM CONNECTION ACTIVE state (GROUP 
TRANSMIT MODE) state. However, as a network dependent option, a MM connection establishment for emergency 
call may be rejected in some of the states. 

When a user requests an emergency call establishment the mobile station will send a CM SERVICE REQUEST 
message to the network with a CM service type information element indicating emergency call establishment. If the 
network does not accept the emergency call request, e.g., because IMEI was used as identification and this capability is 
not supported by the network, the network will reject the request by returning a CM SERVICE REJECT message to the 
mobile station. 

The reject cause information element indicates the reason for rejection. The following cause values may apply: 

#3 "Illegal MS" 

#4 "IMSI unknown in VLR" 

#5 "IMEI not accepted" 

#6 "Illegal ME" 

#17 "Network failure" 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 90 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

#22 "Congestion" 

#32 "Service option not supported" 

#34 "Service option temporarily out of order" 

With the above defined exceptions, the procedures described for MM connection establishment in subclauses 4.5.1.1 
and 4.5.1.2 shall be followed. 

NOTE: Normally, the mobile station will be identified by an IMSI or a TMSI. However, if none of these 

identifiers is available in the mobile station, then the mobile station shall use the IMEI for identification 
purposes. The network may in that case reject the request by returning a CM SERVICE REJECT message 
with reject cause: #5 "IMEI not accepted". 

4.5.1.6 Call re-establishment 

The re-establishment procedure allows a MS to resume a connection in progress after a radio link failure, possibly in a 
new cell and possibly in a new location area. The conditions in which to attempt call re-establishment or not depend on 
the call control state, see subclause 5.5.4 and, whether or not a cell allowing call re-establishment has been found (as 
described in 3GPP TS 45.008 [34]). MM connections are identified by their protocol discriminators and transaction 
identifiers: these shall not be changed during call re-establishment. 

The re-establishment takes place when a lower layer failure occurs and at least one MM connection is active (i.e.. the 
mobile station's MM sublayer is either in state 6 "MM CONNECTION ACTIVE" or state 20 "WAIT FOR 
ADDITIONAL OUTGOING MM CONNECTION"). 

NOTE: During a re-establishment attempt the mobile station does not return to the MM IDLE state; thus no 

location updating is performed even if the mobile is not updated in the location area of the selected cell. 

No call re-establishment shall be performed for voice group and broadcast calls. 

4.5.1 .6.1 Call re-establishment, initiation by the mobile station 

NOTE: The network is unable to initiate call re-establishment. 

If at least one request to re-establish an MM connection is received from a CM entity as a response to the indication that 
the MM connection is interrupted (see subclause 4.5.2.3.) the mobile station initiates the call re-establishment 
procedure. If several CM entities request re-establishment only one re-establishment procedure is initiated. If any CM 
entity requests re-establishment, then re-establishment of all transactions belonging to all Protocol Discriminators that 
permit Call Re-establishment shall be attempted. 

Upon request of a CM entity to re-establish an MM connection the MM sublayer requests the RR sublayer to establish 
an RR connection and enters MM sublayer state WAIT FOR REESTABLISH. This request contains an establishment 
cause and a CM RE-ESTABLISHMENT REQUEST message. When the establishment of an RR connection is 
indicated by the RR sublayer, the MM sublayer of the mobile station starts timer T3230, gives an indication to all CM 
entities that are being re-established, and remains in the MM sublayer state WAIT FOR REESTABLISH. 

The CM RE-ESTABLISHMENT REQUEST message contains the 

mobile identity according to subclause 10.5.1.4; 

mobile station classmark 2; 

ciphering key sequence number. 

NOTE: Whether or not a CM entity can request re-establishment depends upon the Protocol Discriminator. The 
specifications for Short Message Service (3GPP TS 24.01 1), Call Independent Supplementary Services 
(3GPP TS 24.010 [21]) and Location Services (3GPP TS 44.071 [23a]) do not currently specify any re- 
establishment procedures. 

Upon receiving a CM RE-ESTABLISHMENT REQUEST message, the network shall analyse its content. Depending 
on the type of request, the network may start any of the MM common procedures and RR procedures. 

The network may initiate the classmark interrogation procedure, for example, to obtain further information on the 
mobile station's encryption capabilities. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 91 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The identification procedure (see subclause 4.3.3) may be invoked. 

The network may invoke the authentication procedure (see subclause 4.3.2). 

In A/Gb mode, the network decides if the security mode setting procedure shall be invoked (see 3GPP TS 44.018 [84] 
subclause 3.4.7). 

An indication from the RR sublayer that the security mode setting procedure is completed, or reception of a CM 
SERVICE ACCEPT message, shall be treated as a service acceptance indication by the mobile station. 

In lu mode, the network decides if the security mode control procedure shall be invoked (see 3GPP TS 25.331 [23c] and 
3GPP TS 44. 118 [111]). An indication from the RR sublayer that the security mode control procedure is completed, or 
reception of a CM SERVICE ACCEPT message, shall be treated as a service acceptance indication by the mobile 
station. 

The MM connection re-establishment is completed, timer T3230 shall be stopped, all CM entities associated with the 
re-establishment shall be informed, and MM sublayer state MM CONNECTION ACTIVE is re-entered. All the MM 
connections are considered to be active. 

If the network cannot associate the re-establishment request with any existing call for that mobile station, a CM 
SERVICE REJECT message is returned with the reject cause: 

#38 "call cannot be identified" 

If call re-establishment cannot be performed for other reasons, a CM SERVICE REJECT is returned, the appropriate 
reject cause may be any of the following (see annex G): 

# 4 "IMSI unknown in VLR" ; 

# 6 "illegal ME"; 
#17 "network failure"; 
#22 "congestion"; 

#32 "service option not supported"; 

#34 "service option temporarily out of order". 

Whatever the reject cause a mobile station receiving a CM SERVICE REJECT as a response to the CM RE- 
ESTABLISHMENT REQUEST shall stop T3230, release all MM connections and proceed as described in 
subclause 4.5.3.1. In addition: 

if cause value #4 is received, the mobile station deletes any TMSI, LAI and ciphering key sequence number in 
the SIM/USIM, changes the update status to NOT UPDATED (and stores it in the SIM/USIM according to 
subclause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. If subsequently the 
RR connection is released or aborted, this will force the mobile station to initiate a normal location updating). 
The CM re-establishment request shall not be memorized during the location updating procedure. 

if cause value #6 is received, the mobile station deletes any TMSI, LAI and ciphering key sequence number in 
the SIM/USIM, changes the update status to ROAMING NOT ALLOWED (and stores it in the SIM/USIM 
according to subclause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. The 
MS shall consider the SIM/USIM as invalid for non-GPRS services until switch-off or the SIM/USIM is 
removed. 

4.5.1.6.2 Abnormal cases 

Mobile station side: 

a) Random access failure or RR connection establishment failure 

If the mobile station detects a random access failure or RR connection establishment failure during the re- 
establishment of an MM connection, the re-establishment is aborted and all MM connections are released. 

b) RR connection failure 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 92 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If a RR connection failure occurs, timer T3230 is stopped, the re-establishment is aborted and all active MM 
connections are released. 

c) IMSI deactivation 

If the IMSI deactivated during the re-establishment attempt then timer T3230 is stopped, the re-establishment is 
aborted and all MM connections are released. 

d) T3230 expires 

If T3230 expires (i.e. no response is given but a RR connection is available) the re-establishment is aborted, all 
active MM connections are released and the mobile station proceeds as described in subclause 4.5.3.1. 

e) Reject causes #96, #97, #99, #100, #1 1 1 received 

The mobile station shall perform the same actions as if timer T3230 had expired. 
Network side: 

a) RR connection failure 

If a RR connection failure occurs after receipt of the CM RE-ESTABLISHMENT REQUEST the network shall 
release all MM connections. 

b) Invalid message content 

Upon reception an invalid initial of message or a CM RE-ESTABLISHMENT REQUEST message with invalid 
content, a CM SERVICE REJECT message shall be returned with one of the following appropriate Reject cause 
indications: 

#96: Mandatory information element error 

#99: Information element non-existent or not implemented 

#100: Conditional IE error 

#111: Protocol error, unspecified 

When the CM SERVICE REJECT message has been sent, the network shall release the RR connection. 

4.5.1 .7 Forced release during MO MM connection establishment 

If the mobile station's CM layer initiated the MM connection establishment but the CM layer wishes to abort the 
establishment prior to the completion of the establishment phase, the mobile station shall send a CM SERVICE 
ABORT message any time after the completion of the RR connection and not after the first CM message (e.g. SETUP) 
is sent. 

If the first CM message has already been sent, the normal release procedure defined by the appropriate CM protocol 
applies and the CM SERVICE ABORT shall not be sent. 

Sending of the CM SERVICE ABORT message is only allowed during the establishment of the first MM connection, 
where no other MM connection exists in parallel. If parallel MM connections exist already, a new connection 
establishment cannot be aborted and normal MM connection release according to subclause 4.5.3 applies after MM 
connection establishment. 

Upon transmission of the CM SERVICE ABORT message the mobile station shall set timer T3240 and enter the state 
WAIT FOR NETWORK COMMAND, expecting the release of the RR connection. 

Upon receipt of the CM SERVICE ABORT message the network shall abort ongoing processes, release the appropriate 
resources, and unless another MM connection establishment is pending, initiate a normal release of the RR connection. 

If the RR connection is not released within a given time controlled by timer T3240, the mobile station shall abort the 
RR connection. In both cases, either after a RR connection release triggered from the network side or after a RR 
connection abort requested by the mobile station side the mobile station shall return to state MM IDLE; the service state 
depending upon the current update status as specified in subclause 4.2.3. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 93 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.5.2 MM connection information transfer pinase 

After the MM connection has been estabHshed, it can be used by the CM sublayer entity for information transfer. 
According to the protocol architecture described in 3GPP TS 24.007 [20], each CM entity will have its own MM 
connection. These different MM connections are identified by the protocol discriminator PD and, additionally, by the 
transaction identifier TI. 

All MM common procedures may be initiated at any time while MM connections are active. Except for Short Message 
Control which uses a separate layer 2 low priority data link, no priority mechanism is defined between the CM, MM 
and RR sublayer messages. 

4.5.2.1 Sending CM messages 

A CM sublayer entity, after having been advised that a MM connection has been established, can request the transfer of 
CM messages. The CM messages passed to the MM sublayer are then sent to the other side of the interface with the PD 
and TI set according to the source entity. 

4.5.2.2 Receiving CIVI messages 

Upon receiving a CM message, the MM sublayer will distribute it to the relevant CM entity according to the PD value 
and TI value. However, if the received CM message is the first for the MM connection (identified by PD and TI), the 
MM sublayer will in addition indicate to the CM entity that a new MM connection has been established. 

4.5.2.3 Abnormal cases 

RR connection failure: 

If the RR connection failure occurs during a RR or MM common procedure, the consequent actions are 
described together with that procedure. 

In other cases, the following applies: 

- Mobile station: 

The MM sublayer shall indicate to all CM entities associated with active MM connections that the MM 
connection is interrupted, the subsequent action of the MM sublayer (call re-establishment, see 4.5.1.6, or 
local release) will then depend on the decisions by the CM entities. 

Network: 

The MM sublayer shall locally release all active MM connections. As an option the network may delay the 
release of all or some of the MM connections to allow the mobile station to initiate call re-establishment. 

4.5.3 MM connection release 

An established MM connection can be released by the local CM entity. The release of the CM connection will then be 
done locally in the MM sublayer, i.e. no MM message are sent over the radio interface for this purpose. 

4.5.3.1 Release of associated RR connection 

If all MM connections are released by their CM entities, and no RRLP procedure (see 3GPP TS 44.031 [23b]) and no 
LCS procedure over RRC (see 3GPP TS 25.331 [23c]) is ongoing, the mobile station shall set timer T3240 and enter the 
state WAIT FOR NETWORK COMMAND, expecting the release of the RR connection. 

If all MM connections are released by their CM entities and an RRLP procedure or LCS procedure over RRC is 
ongoing, the MS shall start the timer T3241 and enter the state RR CONNECTION RELEASE NOT ALLOWED. 

If the MS is expecting the release of the RR connection in MM state WAIT FOR NETWORK COMMAND and an 
RRLP procedure or LCS procedure over RRC is started, the MS shall stop the timer T3240, start the timer T3241 and 
enter the state RR CONNECTION RELEASE NOT ALLOWED. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 94 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the MS is in MM state RR CONNECTION RELEASE NOT ALLOWED and the ongoing RRLP procedure or LCS 
procedure over RRC is finished, the MS shall stop the timer T3241, reset and start the timer T3240 and shall enter the 
state WAIT FOR NETWORK COMMAND. 

In the network, if the last MM connection is released by its user, the MM sublayer may decide to release the RR 
connection. The RR connection may be maintained by the network, e.g. in order to establish another MM connection. 

If the RR connection is not released within a given time controlled by the timer T3240 or T3241, the mobile station 
shall abort the RR connection. In both cases, either after a RR connection release triggered from the network side or 
after a RR connection abort requested by the MS-side, the MS shall return to MM IDLE state; the service state 
depending upon the current update status as specified in subclause 4.2.3. 

4.5.3.2 Uplink release in a voice group call 

(Only applicable for mobile stations supporting VGCS talking:) 

If a mobile station which is in the MM sublayer state MM CONNECTION ACTIVE (GROUP TRANSMIT MODE) 
receives a request from the GCC sublayer to perform an uplink release, the MM sublayer requests the RR sublayer to 
perform an uplink release procedure and enters the MM sublayer state RECEIVING GROUP CALL (NORMAL 
SERVICE). 

4.6 Receiving a IVIIVI STATUS message by a iVIIVI entity. 

If the MM entity of the mobile station receives a MM STATUS message no state transition and no specific action shall 
be taken as seen from the radio interface, i.e. local actions are possible. 

With the exceptions described for the responses to the CM SERVICE PROMPT message, the actions to be taken on 
receiving a MM STATUS message in the network are an implementation dependent option. 

4.7 Elementary mobility management procedures for GPRS 
services 

4.7.1 General 

This subclause describes the basic functions offered by the mobility management (GMM) sublayer at the radio interface 
(reference point l]^/U\]). The functionality is described in terms of timers and procedures. During GMM procedures, 
procedures of CM layer services via the PS domain, e.g. SM, SMS, and SS, are suspended. 

4.7.1 .1 Lower layer failure 

The lower layers shall indicate a logical link failure or an RR sublayer failure or an RRC sublayer failure to the GMM 
sublayer. The failure indicates an error that cannot be corrected by the lower layers. 

4.7.1 .2 Ciphering of messages (A/Gb mode only) 

If ciphering is to be applied on a GMM context, all GMM messages shall be ciphered except the following messages: 

- ATTACH REQUEST; 

- ATTACH REJECT; 

- AUTHENTICATION AND CIPHERING REQUEST; 

- AUTHENTICATION AND CIPHERING RESPONSE; 

- AUTHENTICATION AND CIPHERING FAILURE; 

- AUTHENTICATION AND CIPHERING REJECT; 

- IDENTITY REQUEST; 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 95 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- IDENTITY RESPONSE; 

- ROUTING AREA UPDATE REQUEST; and 

- ROUTING AREA UPDATE REJECT. 

4.7.1.3 P-TMSI signature 

The network may assign a P-TMSI signature to an MS in an attach, routing area update, or P-TMSI reallocation 
procedure. Only in combination with a valid P-TMSI, this P-TMSI signature is used by the MS for authentication and 
identification purposes in the subsequent attach, routing area update or detach procedure. If the MS has no valid P- 
TMSI it shall not use the P-TMSI signature in the subsequent attach, routing area update or detach procedure. Upon 
successful completion of the subsequent attach or routing area update procedure, the used P-TMSI signature shall be 
deleted. Upon completion of an MS initiated detach procedure, the used P-TMSI signature shall be deleted. Upon 
completion of a network initiated detach procedure the P-TMSI signature shall be kept, unless explicitly specified 
otherwise in subclause 4.7.4.2.2. 

4.7.1 .4 Radio resource sublayer address handling 

In A/Gb mode, while a packet TMSI (P-TMSI) is used in the GMM sublayer for identification of an MS, a temporary 
logical link identity (TLLI) is used for addressing purposes at the RR sublayer. 

In lu mode a Radio Network Temporary Identity (RNTI) identifies a user between the MS and the UTRAN or GERAN. 
The relationship between RNTI and IMSI is known only in the MS and in the UTRAN, see 3GPP TS 25.301 [10]. 

4.7.1 .4.1 Radio resource sublayer address handling (A/Gb mode only) 

This subclause describes how the RR addressing is managed by GMM. For the detailed coding of the different TLLI 
types and how a TLLI can be derived from a P-TMSI, see 3GPP TS 23.003 [10]. 

Two cases can be distinguished: 

- a valid P-TMSI is available in the MS; or 

- no vaHd P-TMSI is available in the MS. 

i) valid P-TMSI available 

If the MS has stored a valid P-TMSI, the MS shall derive a foreign TLLI from that P-TMSI and shall use it for 
transmission of the: 

ATTACH REQUEST message of any GPRS combined/non-combined attach procedure; other GMM 
messages sent during this procedure shall be transmitted using the same foreign TLLI until the ATTACH 
ACCEPT message or the ATTACH REJECT message is received; and 

- ROUTING AREA UPDATE REQUEST message of a combined/non-combined RAU procedure if the MS 
has entered a new routing area, or if the GPRS update status is not equal to GUI UPDATED. Other GMM 
messages sent during this procedure shall be transmitted using the same foreign TLLI, until the ROUTING 
AREA UPDATE ACCEPT message or the ROUTING AREA UPDATE REJECT message is received. 

After a successful GPRS attach or routing area update procedure, independent whether a new P-TMSI is 
assigned, if the MS has stored a valid P-TMSI then the MS shall derive a local TLLI from the stored P-TMSI 
and shall use it for addressing at lower layers. 

NOTE: Although the MS derives a local TLLI for addressing at lower layers, the network should not assume that 
it will receive only LLC frames using a local TLLI. Immediately after the successful GPRS attach or 
routing area update procedure, the network must be prepared to continue accepting LLC frames from the 
MS still using the foreign TLLI. 

ii) no valid P-TMSI available 

When the MS has not stored a valid P-TMSI, i.e. the MS is not attached to GPRS, the MS shall use a randomly 
selected random TLLI for transmission of the: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 96 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

ATTACH REQUEST message of any combined/non-combined GPRS attach procedure. 

The same randomly selected random TLLI value shall be used for all message retransmission attempts and for 
the cell updates within one attach attempt. 

Upon receipt of an ATTACH REQUEST message, the network shall assign a P-TMSI to the MS. The network 
derives a local TLLI from the assigned P-TMSI, and transmits the assigned P-TMSI to the MS. 

Upon receipt of the assigned P-TMSI, the MS shall derive the local TLLI from this P-TMSI and shall use it for 
addressing at lower layers. 

NOTE: Although the MS derives a local TLLI for addressing at lower layers, the network should not assume that 
it will receive only LLC frames using a local TLLI. Immediately after the successful GPRS attach, the 
network must be prepared to continue accepting LLC frames from the MS still using the random TLLI. 

In both cases, the MS shall acknowledge the reception of the assigned P-TMSI to the network. After receipt of the 
acknowledgement, the network shall use the local TLLI for addressing at lower layers. 

4.7.1.5 P-TMSI handling 

4.7.1 .5.1 P-TMSI handling in A/Gb mode 

If a new P-TMSI is assigned by the network the MS and the network shall handle the old and the new P-TMSI as 
follows: 

Upon receipt of a GMM message containing a new P-TMSI the MS shall consider the new P-TMSI and new RAI and 
also the old P-TMSI and old RAI as valid in order to react to paging requests and downlink transmission of LLC 
frames. For uplink transmission of LLC frames the new P-TMSI shall be used. 

The MS shall consider the old P-TMSI and old RAI as invalid as soon as an LLC frame is received with the local TLLI 
derived from the new P-TMSI. 

Upon the transmission of a GMM message containing a new P-TMSI the network shall consider the new P-TMSI and 
new RAI and also the old P-TMSI and old RAI as valid in order to be able to receive LLC frames from the MS. 

The network shall consider the old P-TMSI and old RAJ as invalid as soon as an LLC frame is received with the local 
TLLI derived from the new P-TMSI. 

4.7.1 .5.2 P-TMSI handling in lu mode 

If a new P-TMSI is assigned by the network the MS and the network shall handle the old and the new P-TMSI as 
follows: 

Upon receipt of a GMM message containing a new P-TMSI the MS shall consider the new P-TMSI and new RAI as 
valid. Old P-TMSI and old RAI are regarded as invalid. 

The network shall consider the old P-TMSI and old RAI as invalid as soon as an acknowledge message (e.g. ATTACH 
COMPLETE, ROUTING AREA UPDATE COMPLETE and P-TMSI REALLOCATION COMPLETE) is received. 

4.7.1 .6 Change of network mode of operation 

In the following tables below the abbreviations 'A/Gb mode I', 'A/Gb mode 11' and 'A/Gb mode III' are used for network 
operation mode I, II and III in A/Gb mode. 

In the following tables below the abbreviations 'lu mode I' and 'lu mode 11' are used for network operation modes I and 
II in lu mode. 

4.7.1 .6.1 Change of network mode of operation in A/Gb mode (A/Gb mode only) 

Whenever an MS moves to a new RA, the procedures executed by the MS depend on the network mode of operation in 
the old and new routing area. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



97 



ETSI TS 124 008 V7.14.0 (2009-03) 



In case the MS is in state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED and is in 
operation mode: 

a) A or B (with the exceptions in b and c below), the MS shall execute: 

Table 4.7.1. 6.1/3GPP TS 24.008: Mode A or B 



Network operation 
mode change 


Procedure to execute 


1^ II origin 


Normal Location Update(*), 

followed by a Normal Routing Area Update 


II ^111 or III ^11 


Normal Location Update (see subclause 4.2.2) if a new LA is entered, 
followed by a Normal Routing Area Update 


II ^ lor III ^1 


Combined Routing Area Update with IMSI attach(**) 



b) B which reverts to operation mode C in network operation mode III, the MS shall execute: 
Table 4.7.1. 6.2/3GPP TS 24.008: Mode B which reverts into mode C in network operation mode 



Network operation 
mode change 


Procedure to execute 


l^ll 


Normal Location Update(*), 

followed by a Normal Routing Area Update 


1^ III or II ^111 


IIVISI Detach (see subclause 4.3.4), 
followed by a Normal Routing Area Update 


II ^ lor III ^1 


Combined Routing Area Update with IMSI attach(**) 


III ^11 


IIVISI attach (see subclause 4.4.3), 
followed by a Normal Routing Area Update 



c) B which reverts to IMSI attached for CS services only in network operation mode III, the MS shall execute: 

Table 4.7.1. 6.3/3GPP TS 24.008: Mode B which reverts into IMSI attached for CS services only in 

network operation mode III 



Network operation 
mode change 


Procedure to execute 


l^ll 


Normal Location Update(*), 

followed by a Normal Routing Area Update 


l^lll 


Normal Location Update(*), 

followed by a GPRS Detach with type indicating "GPRS Detach" 


II ^111 


Normal Location Update (see subclause 4.2.2) if a new LA is entered, 
followed by a GPRS Detach with detach type indicating "GPRS Detach" 


II ^1 


Combined Routing Area Update with IMSI attach(**) 


lll^l 


Combined GPRS Attach(**) 


III ^11 


Normal Location Update (see subclause 4.2.2) if a new LA is entered, 
followed by a Normal GPRS Attach 



(*) Intended to remove the Gs association in the MSC/VLR. 

(**) Intended to establish the Gs association in the MSC/VLR. 

Further details are implementation issues. 



4.7.1.6.2 



Change of network mode of operation in lu mode (lu mode only) 



Whenever an MS moves to a new RA, the procedures executed by the MS depend on the network mode of operation in 
the old and new routing area. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



98 



ETSI TS 124 008 V7.14.0 (2009-03) 



In case the MS is in state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED and is in 
operation mode A, the MS shall execute: 

Table 4.7.1 .6.4/3GPP TS 24.008: Mode A 



Network operation 
mode change 


Procedure to execute 


l^ll 


Normal Location Update(*), 

followed by a Normal Routing Area Update 


II ^1 


Combined Routing Area Update with IMSI attachf*) 



(*) Intended to remove the Gs association in the MSC/VLR. 

(**) Intended to establish the Gs association in the MSC/VLR. 

Further details are implementation issues. 

4.7.1 .6.3 Change of network mode of operation at lu mode to A/Gb mode inter-system 

change 

Whenever an MS moves to a new RA supporting the A/Gb mode radio interface, the procedures executed by the MS 
depend on the network mode of operation in the old and new routing area. 

In case the MS is in state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED and is in 
operation mode: 

a) A in lu mode, an MS that changes to GPRS operation mode A or B in A/Gb mode shall execute: 
Table 4.7.1. 6.5/3GPP TS 24.008: Mode A in lu mode changing to GPRS mode A or B in A/Gb mode 



Network operation 
mode change 


Procedure to execute 


lu mode 1 -^ /VGb mode 1 


Combined Routing Area Update 


lu mode II -^ A/Gb mode 1 


Combined Routing Area Update with IMSI attachf*) 


lu mode 1 -^ /VGb mode II 

or 

lu mode 1 -^ /VGb mode 

III 


Normal Location Update(*), 

followed by a Normal Routing Area Update 



b) A in lu mode, an MS that changes due to MS specific characteristics to GPRS operation mode C in network 
operation mode III in A/Gb mode shall execute: 

Table 4.7.1 .6.6/3GPP TS 24.008: Mode A in lu mode changing to GPRS mode C in A/Gb mode 



Network operation 
mode change 


Procedure to execute 


lu mode 1 -^ /VGb mode 

III or 

lu mode II -^ A/Gb mode 

III 


IIVISI detach (see subclause 4.3.4), 
followed by a Normal Routing Area Update 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



99 



ETSI TS 124 008 V7.14.0 (2009-03) 



c) A in lu mode, an MS that changes due to MS specific characteristics to IMSI attached for CS services only in 
network operation mode III in A/Gb mode shall execute: 

Table 4.7.1. 6.7/3GPP TS 24.008: Mode A in lu mode changing to IMSI attached for CS services only in 

A/Gb mode 



Network operation 
mode change 


Procedure to execute 


lu mode 1 -^ A/Gb mode 
III 


Normal Location Update (see subclause 4.4.1 )(*), 

followed by a GPRS Detach with detach type indicating "GPRS Detach" 


lu mode II -^ A/Gb mode 
III 


Normal Location Update (see subclause 4.4.1) if a new LA is entered, 
followed by a GPRS Detach with detach type indicating "GPRS Detach" 



d) C in lu mode, the MS shall change to GPRS operation mode C in A/Gb mode and shall execute the normal 
Routing Area Update procedure. 

e) CS in lu mode, the MS shall execute the normal Location Update procedure. 
(*) Intended to remove the Gs association in the MSC/VLR. 

(**) Intended to establish the Gs association in the MSC/VLR. 

Further details are implementation issues. 

4.7.1 .6.4 Change of network mode of operation at A/Gb mode to lu mode inter-system 

change 

Whenever an MS moves to a new RA supporting the lu mode radio interface, the procedures executed by the MS 
depend on the network mode of operation in the old and new routing area. 

In case the MS is in state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED and is in 
operation mode: 

a) A or B in A/Gb mode, the MS shall change to operation mode A in lu mode and shall execute: 
Table 4.7.1 .6.8/3GPP TS 24.008: Mode A or B in A/Gb mode changing to mode A in lu mode 



Network operation mode 
change 


Procedure to execute 


A/Gb mode 1 -^ lu mode 1 


Combined Routing Area Update 


A/Gb mode II -^ lu mode 1 


Combined Routing Area Update with IIVISI attach(**) 


A/Gb mode 1 -^ lu mode II 


Normal Location Update(*), 

followed by a Normal Routing Area Update 


A/Gb mode II -> lu mode II 

or 

A/Gb mode III -> lu mode II 


Normal Location Update if a new LA is entered, 
followed by a Normal Routing Area Update 



b) C in A/Gb mode, an MS that changes to operation mode C in lu mode shall execute a Normal Routing Area 
Update. 

c) C in A/Gb mode, an MS that, due to MS specific characteristics operated in GPRS operation mode C in 
network operation mode III in A/Gb mode changes to operation mode A in lu mode shall execute: 

Table 4.7.1 .6.9/3GPP TS 24.008: Mode C changing to mode A in lu mode 



Network operation 
mode change 


Procedure to execute 


/VGb mode III -^ lu mode 
1 


Combined Routing Area Update with IMSI attach(**) 


A/Gb mode III -^ lu mode 
II 


IIVISI attach (see subclause 4.4.3), 
followed by a Normal Routing Area Update 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



100 



ETSI TS 124 008 V7.14.0 (2009-03) 



d) IMSI attached for non-GPRS services only, an MS that, due to MS specific characteristics, operated in 
network operation mode III in A/Gb mode and changes to operation mode A in lu mode shall execute: 

Table 4.7.1. 6.1 0/3GPP TS 24.008: IMSI attached for non-GPRS services only changing to mode A in lu 

mode 



Network operation 
mode change 


Procedure to execute 


A/Gb mode III ^ lu mode 

1 


Combined GPRS Attach for GPRS and non-GPRS services(**) 


A/Gb mode III -> lu mode 
II 


GPRS Attach 



(*) Intended to remove the Gs association in the MSC/VLR. 

(**) Intended to establish the Gs association in the MSC/VLR. 

Further details are implementation issues. 



4.7.1.7 



Intersystem change between A/Gb mode and lu mode 



For the lu mode to A/Gb mode and A/Gb mode to lu mode intersystem change the following cases can be 
distinguished: 

a) Intersystem change between cells belonging to different RA's: 

The procedures executed by the MS depends on the network mode of operation in the old and new RA. If a 
change of the network operation mode has occurred in the new RA, then the MS shall behave as specified in 
subclause 4.7.1.6. If no change of the network operation mode has occurred in the new RA, then the MS shall 
initiate the normal or combined RA update procedure depending on the network operation mode in the current 
RA. 

b) Intersystem change between cells belonging to the same RA: 

If the READY timer is running in the MS in A/Gb mode or the MS is in PMM-CONNECTED mode in lu mode, 
then the MS shall perform a normal or combined RA update procedure depending on the network mode of 
operation in the current RA. 

If the READY timer is not running in the MS in A/Gb mode or the MS is in PMM-IDLE mode in lu mode, then 
the MS shall not perform a RA update procedure (as long as the MS stays within the same RA) until up-link user 
data or signalling information needs to be sent from the MS to the network, except case c) is applicable. 

If the MS is in the same access network, A/Gb mode or lu mode, as when it last sent user data or signalling 
messages, the procedures defined for that access system shall be followed. This shall be sending of an LLC 
PDU in a A/Gb mode cell or initiating the SERVICE REQUEST procedure in an lu mode cell. 

If the MS is in a different access network, A/Gb mode or lu mode, as when it last sent user data or signalling 
messages, the normal or combined RA update procedure shall be performed depending on the network 
operation mode in the current RA, before the sending of user data or signalling messages. If the signalling 
message is a DETACH REQUEST containing cause "power off", the RA update procedure need not to be 
performed. 

If the periodic routing area update timer expires the MS shall initiate the periodic RA update procedure. 

If the READY timer is not running in the network in A/Gb mode or the network is in PMM-IDLE mode in lu 
mode, then the network shall page the MS if down-link user data or signalling information needs to be sent from 
the network to the MS. This shall include both A/Gb mode and lu mode cells. 

If the MS receives the paging indication in the same access network, A/Gb mode or lu mode, as when it last 
sent user data or signalling information, the MS shall send any LLC PDU in a A/Gb mode cell or shall 
initiate the SERVICE REQUEST procedure indicating service type "paging response" in an lu mode cell. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 01 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the MS receives the paging indication in a different access network, A/Gb mode or lu mode, as when it last 
sent user data or signalling information, the normal or combined RA update procedure shall be performed 
depending on the network operation mode in the current RA. 

c) Intersystem handover from A/Gb mode to lu mode during a CS connection: 

After the successful completion of the handover from an A/Gb mode cell to an lu mode cell, an MS which has 
performed the GPRS suspension procedure in Gb mode (see 3GPP TS 44.018 [84]) (i.e. an MS in MS operation 
mode B or an DTM MS in a A/Gb mode cell that does not support DTM) shall perform a normal RA update 
procedure in the lu mode cell in order to resume the GPRS services in the network, before sending any other 
signalling messages or user data. 

4.7.1 .8 List of forbidden PLMNs for GPRS service 

The Mobile Equipment shall contain a list of "forbidden PLMNs for GPRS service". This lists shall be erased when the 
MS is switched off or when the SIM/USIM is removed. The PLMN identification received on the BCCH shall be added 
to the list whenever a GPRS attach or routing area update is rejected by the network with the cause "GPRS services not 
allowed in this PLMN" or whenever a GPRS detach is initiated by the network with the cause "GPRS services not 
allowed in this PLMN". 

In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 23.122 [14]. The PLMN 
identity chosen for a GPRS attach procedure, or the PLMN identity used to construct the RAI that triggered the routing 
area updating procedure shall be added to the list of "forbidden PLMNs for GPRS service" whenever such a procedure 
is rejected by the network with the cause "GPRS services not allowed in this PLMN". Whenever a GPRS detach is 
initiated by the network with the cause "GPRS services not allowed in this PLMN", the chosen PLMN identity shall be 
added to the list of "forbidden PLMNs for GPRS service". 

The maximum number of possible entries in this list is implementation dependent, but must be at least one entry. When 
the list is full and a new entry has to be inserted, the oldest entry shall be deleted. 

4.7.1 .9 Release of the PS signalling connection (lu mode only) 

In lu mode, to allow the network to release the PS signalling connection (see 3GPP TS 25.331 [23c] and 
3GPP TS 44.1 18 [110]) the MS shall start the timer T3340 in the following cases: 

a) the MS receives any of the reject cause values #11, #12, #13 or #15; or 

b) the network indicates "no follow-on proceed" in the ROUTING AREA UPDATE ACCEPT or ATTACH 
ACCEPT message. 

Upon expiry of T3340, the MS shall release the established PS signalling connection (see 3GPP TS 25.331 [23c] and 
3GPPTS 44.118 [110]). 

In case b, if the MS has signalling pending, then it shall request a new PS signalling connection for further signalling. 

4.7.2 GPRS Mobility management timers and UMTS PS signalling 
connection control 

4.7.2.1 READY timer behaviour 

4.7.2.1 .1 READY timer behaviour (A/Gb mode only) 

The READY timer, T3314 is used in the MS and in the network per each assigned P-TMSl to control the cell updating 
procedure. 

When the READY timer is running or has been deactivated the MS shall perform cell update each time a new cell is 
selected (see 3GPP TS 43.022 [82]). If a routing area border is crossed, a routing area updating procedure shall be 
performed instead of a cell update. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 02 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

When the READY timer has expired the MS shall: 

perform the routing area updating procedure when a routing area border is crossed; 

not perform a cell update when a new cell is selected. 

All other GMM procedures are not affected by the READY timer. 

The READY timer is started: 

in the MS when the GMM entity receives an indication from lower layers that an LLC frame other than LLC 
NULL frame has been transmitted on the radio interface; and 

in the network when the GMM entity receives an indication from lower layers that an LLC frame other than LLC 
NULL frame has been successfully received by the network. 

Within GMM signalling procedures the network includes a "force to standby" information element, in order to indicate 
whether or not the READY timer shall be stopped when returning to the GMM -REGISTERED state. If the "force to 
standby" information element is received within more than one message during a ongoing GMM specific procedure, the 
last one received shall apply. If the READY timer is deactivated and the network indicates "force to standby" with the 
"force to standby" information element, this shall not cause a modification of the READY timer. 

The READY timer is not affected by state transitions to and from the GMM-REGISTERED.SUSPENDED sub-state. 

The value of the READY timer may be negotiated between the MS and the network using the GPRS attach or GPRS 
routing area updating procedure. 

If the MS wishes to indicate its preference for a READY timer value it shall include the preferred values into the 
ATTACH REQUEST and/or ROUTING AREA UPDATE REQUEST messages. The preferred values may be 
smaller, equal to or greater than the default values or may be equal to the value requesting the READY Timer 
function to be deactivated. 

Regardless of whether or not a timer value has been received by the network in the ATTACH REQUEST or 
ROUTING AREA UPDATE REQUEST messages, the network may include a timer value for the READY timer 
(different or not from the default value) into the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT 
messages, respectively. If the READY Timer value was included, it shall be applied for the GMM context by the 
network and by the MS. 

When the MS proposes a READY Timer value and the Network does not include any READY Timer Value in 
its answer, then the value proposed by the MS shall be applied for the GMM context by the Network and by the 
MS. 

- When neither the MS nor the Network proposes a READY Timer value into the ATTACH ACCEPT or 
ROUTING AREA UPDATE ACCEPT message, then the default value shall be used. 

If the negotiated READY timer value indicates that the ready timer function is deactivated, the READY timer shall 
always run without expiry. If the negotiated READY timer value indicates that the ready timer function is deactivated, 
and within the same procedure the network indicates "force to standby" with the "force to standby" information 
element, the READY timer shall always run without expiry. If the negotiated READY timer value is set to zero, 
READY timer shall be stopped immediately. 

To account for the LLC frame uplink transmission delay, the READY timer value should be slightly shorter in the 
network than in the MS. This is a network implementation issue. 

If a new READY timer value is negotiated, the MS shall upon the reception of the ATTACH ACCEPT or ROUTING 
AREA UPDATE ACCEPT message perform a initial cell update (either by transmitting a LLC frame or, if required, a 
ATTACH COMPLETE or ROUTING AREA UPDATE COMPLETE message), in order to apply the new READY 
timer value immediately. If both the network and the MS supports the Cell Notification, the initial cell update shall use 
any LLC frame except the LLC NULL frame. If the new READY timer value is set to zero or if the network indicates 
"force to standby" with the "force to standby" IE, the initial cell update should not be done. 

4.7.2.1 .2 Handling of READY timer in lu mode (lu mode only) 

The READY timer is not applicable for lu mode. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 03 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

An MS may indicate a READY timer value to the network in the ATTACH REQUEST and the ROUTING AREA 
UPDATE REQUEST messages. 

If a READY timer value is received by an MS capable of both lu mode and A/Gb mode in the ATTACH ACCEPT or 
the ROUTING AREA UPDATE ACCEPT messages, then the received value shall be stored by the MS in order to be 
used at an intersystem change from lu mode to A/Gb mode. 

4.7.2.2 Periodic routing area updating 

Periodic routing area updating is used to periodically notify the availability of the MS to the network. The procedure is 
controlled in the MS by the periodic RA update timer, T3312. The value of timer T3312 is sent by the network to the 
MS in the messages ATTACH ACCEPT and ROUTING AREA UPDATE ACCEPT. The value of the timer T3312 
shall be unique within a RA. 

If the T33 12 received by the MS in A/Gb mode or received in lu mode in a message with integrity protection contains 
an indication that the timer is deactivated or the timer value is zero, then the periodic routing area update timer is 
deactivated and the MS shall not perform periodic routing area updating. 

In lu mode, if the value of timer T33 12 is received in a message without integrity protection and the indicated value is 
larger than the last received value, or the indicated value is "deactivated" or zero, the MS shall use the last received 
value. 

In A/Gb mode, the timer T3312 is reset and started with its initial value, when the READY timer is stopped or expires. 
The timer T3312 is stopped and shall be set to its initial value for the next start when the READY timer is started. If 
after a READY timer negotiation the READY timer value is set to zero, timer T3312 is reset and started with its initial 
value. If the initial READY timer value is zero, the timer T3312 is reset and started with its initial value, when the 
ROUTING AREA UPDATE REQUEST message is transmitted. 

In lu mode, the timer T3312 is reset and started with its initial value, when the MS goes from PMM-CONNECTED to 
PMM-IDLE mode. The timer T3312 is stopped when the MS enters PMM-CONNECTED mode. 

When timer T3312 expires, the periodic routing area updating procedure shall be started and the timer shall be set to its 
initial value for the next start. 

If the MS is in other state than GMM-REGISTERED.NORMAL-SERVICE when the timer expires the periodic routing 
area updating procedure is delayed until the MS returns to GMM-REGISTERED.NORMAL-SERVICE. 

In A/Gb mode, if the MS in MS operation mode B is in the state GMM-REGISTERED.SUSPENDED when the timer 
expires the periodic routing area updating procedure is delayed until the state is left. 

The network supervises the periodic routing area updating procedure by means of the Mobile Reachable timer. The 
Mobile Reachable timer shall be longer than the periodic RA update timer. When the Mobile Reachable timer expires, 
typically the network stops sending paging messages to the mobile and may take other appropriate actions. 

In A/Gb mode, the Mobile Reachable timer is reset and started with its initial value, when the READY timer is stopped 
or expires. The Mobile Reachable timer is stopped and shall be set to its initial value for the next start when the 
READY timer is started. 

In A/Gb mode, if after a READY timer negotiation the READY timer value is set to zero the Mobile Reachable timer is 
reset and started with its initial value. If the initial READY timer value is zero, the Mobile Reachable is reset and 
started with its initial value, when the ROUTING AREA UPDATE REQUEST message is received. 

In lu mode, the Mobile Reachable timer is reset and started with its initial value, when the MS goes from PMM- 
CONNECTED to PMM-IDLE mode. The Mobile Reachable timer is stopped when the MS enters PMM-CONNECTED 
mode. 

If the MS is both IMSI attached for GPRS and non-GPRS services, and if the MS lost coverage of the registered PLMN 
and timer T3312 expires, then: 

a) if the MS returns to coverage in a cell that supports GPRS and that indicates that the network is in network 
operation mode I, then the MS shall either perform the combined routing area update procedure indicating 
"combined RA/LA updating with IMSI attach"; or 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 04 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

b) if the MS returns to coverage in a cell in the same RA that supports GPRS and that indicates that the network is 
in network operation mode II or III, then the MS shall perform the periodic routing area updating procedure 
indicating "Periodic updating"; or 

c) if the MS was both IMSI attached for GPRS and non-GPRS services in network operation mode I and the MS 
returns to coverage in a cell in the same LA that does not support GPRS, then the MS shall perform the periodic 
location updating procedure. In addition, the MS shall perform a combined routing area update procedure 
indicating "combined RA/LA updating with IMSI attach" when the MS enters a cell that supports GPRS and that 
indicates that the network is in network operation mode I; or 

d) if the MS returns to coverage in a new RA the description given in subclause 4.7.5 applies. 

If the MS is both IMSI attached for GPRS and non-GPRS services in a network that operates in network operation 
mode I, and if the MS has camped on a cell that does not support GPRS, and timer T3312 expires, then the MS shall 
start an MM location updating procedure. In addition, the MS shall perform a combined routing area update procedure 
indicating "combined RA/LA updating with IMSI attach" when the MS enters a cell that supports GPRS and indicates 
that the network is in operation mode I. 

If timer T3312 expires during an ongoing CS connection, then a MS operating in MS operation mode B shall treat the 
expiry of T3312 when the MM state MM-IDLE is entered, analogous to the descriptions for the cases when the timer 
expires out of coverage or in a cell that does not support GPRS. 

In A/Gb mode, timer T3312 shall not be stopped when a GPRS MS enters state GMM-REGISTERED.SUSPENDED. 

4.7.2.3 PMM-IDLE mode and PMM-CONNECTED mode (lu mode only) 

An MS shall enter PMM-CONNECTED mode when a PS signalling connection for packet switched domain is 
established between the MS and the network. The MS shall not perform periodic routing area update in PMM- 
CONNECTED mode. 

An MS shall enter PMM-IDLE mode when the PS signalling connection for packet switched domain between the MS 
and the network has been released. The MS shall perform periodic routing area update in PMM-IDLE mode. 

4.7.2.4 Handling of Force to standby \r\ lu mode (lu mode only) 

Force to standby is not applicable for lu mode. 

The network shall always indicate Force to standby not indicated in the Force to standby information element. 

The Force to standby information element shall be ignored by the MS. 

4.7.2.5 RA Update procedure for Signalling Connection Re-establishment (lu mode 
only) 

When the MS receives an indication from the lower layers that the RRC connection has been released with cause 
"Directed signalHng connection re-establishment", see 3GPP TS 25.331 [23c] and 3GPP TS 44.118 [111], then the MS 
shall enter PMM-IDLE mode and initiate immediately a normal routing area update procedure (the use of normal or 
combined procedure depends on the network operation mode in the current serving cell) regardless whether the routing 
area has been changed since the last update or not. This routing area update procedure shall also be performed or 
continued if the MS has performed an inter-system change towards GSM, irrespective whether the READY timer is 
running or the MS is in PMM-IDLE or PMM-CONNECTED mode. 

4.7.2.6 Cell Update triggered by low layers 

A Cell Update may be requested by the low layers, see 3GPP TS 44.060. In this case the Cell Update shall be performed 
even if the READY timer is not running. If both the network and the MS support the Cell Notification, then the MS 
shall use the LLC NULL frame to perform the Cell Update. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 05 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.3 GPRS attach procedure 

The GPRS attach procedure is used for two purposes: 

- normal GPRS attach, performed by the MS to IMSI attach for GPRS services only. The normal GPRS attach 
procedure shall be used: 

- by GPRS MSs in MS operation mode C, independent of the network operation mode; 

- by GPRS MSs in MS operation modes A or B if the network operates in network operation mode II or III; 
and 

by GPRS MSs in MS operation mode A, independent of the network operation mode, if a circuit-switched 
transaction is ongoing; 

combined GPRS attach procedure, used by GPRS MSs in MS operation modes A or B to attach the IMSI for 
GPRS and non-GPRS services provided that the network operates in network operation mode I. 

With a successful GPRS attach procedure a GMM context is established. 

Subclause 4.7.3.1 describes the GPRS attach procedure to attach the IMSI only for GPRS services. The combined 
GPRS attach procedure used to attach the IMSI for both GPRS and non-GPRS services is described in 
subclause 4.7.3.2. 

If an IMSI attach for non-GPRS services is requested and a GMM context exists, the routing area updating procedure 
shall be used as described in subclause 4.7.5.2. 

To limit the number of subsequently rejected attach attempts, a GPRS attach attempt counter is introduced. The GPRS 
attach attempt counter shall be incremented as specified in subclause 4.7.3.1.5. Depending on the value of the GPRS 
attempt counter, specific actions shall be performed. The GPRS attach attempt counter shall be reset when: 

the MS is powered on; 

- a SIM/USIM is inserted; 

a GPRS attach procedure is successfully completed; 

a combined GPRS attach procedure is completed for GPRS services only with cause #2, #16, #17 or #22; or 

a GPRS attach procedure is completed with cause #1 1, #12, #13 or #15, 

and additionally when the MS is in substate ATTEMPTING-TO-ATTACH: 

expiry of timer T3302; 

a new routing area is entered; or 

an attach is triggered by CM sublayer requests. 

The mobile equipment shall contain a list of "forbidden location areas for roaming", as well as a list of "forbidden 
location areas for regional provision of service". The handling of these lists is described in subclause 4.4.1; the same 
lists are used by GMM and MM procedures. 

The Mobile Equipment shall contain a list of "equivalent PLMNs". The handling of this list is described in 
subclause 4.4.1, the same list is used by GMM and MM procedures. 

In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 23.122 [14]. The MS 
shall construct the Routing Area Identification of the cell from this chosen PLMN identity, and the LAC and the RAC 
received on the BCCH. The chosen PLMN identity shall be indicated to the RAN in the RRC INITIAL DIRECT 
TRANSFER message (see 3GPP TS 25.331 [23c]). Whenever an ATTACH REJECT message with the cause "PLMN 
not allowed" is received by the MS, the chosen PLMN indentity shall be stored in the "forbidden PLMN list". 
Whenever an ATTACH REJECT message is received by the MS with the cause "Roaming not allowed in this location 
area", "Location Area not allowed", or "No suitable cells in Location Area", the LAI that is part of the constructed RAI 
shall be stored in the suitable list. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 06 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The network informs the MS about the support of specific features, such as LCS-MOLR or MBMS, in the "Network 
feature support" Information Element. The information is either explicitly given by sending the "Network feature 
support" IE or implicitly by not sending it. The handling in the network is described in subclause 9.4.2.9. The MS may 
use the indication to inform the user about the availability of the appropriate services and it shall not request services 
that have not been indicated as available. The indication for MBMS is defined in subclause "MBMS feature support 
indication" in 3GPP TS 23.246 [106]. 

4.7.3.1 GPRS attach procedure for GPRS services 

The GPRS attach procedure is a GMM procedure used by GPRS MSs to IMSI attach for GPRS services. 
The attach type information element shall indicate "GPRS attach". 

4.7.3.1 .1 GPRS attach procedure initiation 

In state GMM-DEREGISTERED, the MS initiates the GPRS attach procedure by sending an ATTACH REQUEST 
message to the network, starts timer T3310 and enters state GMM-REGISTERED-INITIATED. 

The MS capable of both lu mode and A/Gb mode or only of A/Gb mode shall include a valid P-TMSI, if any is 
available, the P-TMSI signature associated with the P-TMSI and the routing area identity associated with the P-TMSI in 
the ATTACH REQUEST message. If there is no valid P-TMSI available, the IMSI shall be included instead of the P- 
TMSI and P-TMSI signature. 

The MS shall also indicate within the DRX parameters whether it supports the split pg cycle option on CCCH. The 
optional support of the split pg cycle on CCCH by the network is indicated in SI 13 or PSII. Split pg cycle on CCCH is 
applied by both the network and the MS when the split pg cycle option is supported by both (see 3GPP TS 45.002 [32]). 

In lu mode, if the MS wishes to prolong the established PS signalling connection after the GPRS attach procedure (for 
example, the MS has any CM application request pending), it may set a follow-on request pending indicator on (see 
subclause 4.7.13). 

4.7.3.1 .2 GMM common procedure initiation 

The network may initiate GMM common procedures, e.g. the GMM identification and GMM authentication and 
ciphering procedure, depending on the received information such as IMSI, CKSN, old RAI, P-TMSI and P-TMSI 

signature. 

4.7.3.1 .3 GPRS attach accepted by the network 

If the GPRS attach request is accepted by the network, an ATTACH ACCEPT message is sent to the MS. 

The P-TMSI reallocation may be part of the GPRS attach procedure. When the ATTACH REQUEST includes the 
IMSI, the SGSN shall allocate the P-TMSI. The P-TMSI that shall be allocated is then included in the ATTACH 
ACCEPT message together with the routing area identifier. The network shall, in this case, change to state GMM- 
COMMON-PROCEDURE-INITIATED and shall start timer T3350 as described in subclause 4.7.6. Furthermore, the 
network may assign a P-TMSI signature for the GMM context which is then also included in the ATTACH ACCEPT 
message. If the LAI or PLMN identity that has been transmitted in the ATTACH ACCEPT message is a member of any 
of the "forbidden" lists, any such entry shall be deleted. Additionally, the network shall include the radio priority level 
to be used by the MS for mobile originated SMS transfer in the ATTACH ACCEPT message. In a shared network, the 
network shall indicate the PLMN identity of the CN operator that has accepted the GPRS attach request in the RAJ 
contained in the ATTACH ACCEPT message (see 3GPP TS 23.251 [109]). 

If the MS has indicated in the ATTACH REQUEST message that it supports PS inter-RAT handover to UTRAN lu 
mode, the network may include in the ATTACH ACCEPT message a request to provide the Inter RAT information 
container. 

In A/Gb mode, the Cell Notification information element shall be included in the ATTACH ACCEPT message by the 
network which indicates that the Cell Notification is supported by the network. 

In lu mode, the network should prolong the PS signalling connection if the mobile station has indicated a follow-on 
request pending in ATTACH REQUEST. The network may also prolong the PS signalling connection without any 
indication from the mobile terminal. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 07 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The MS, receiving an ATTACH ACCEPT message, stores the received routing area identification, stops timer T3310, 
reset the GPRS attach attempt counter, reset the routing area updating attempt counter, enters state GMM- 
REGISTERED and sets the GPRS update status to GUI UPDATED. 

If the message contains a P-TMSI, the MS shall use this P-TMSI as the new temporary identity for GPRS services. In 
this case, an ATTACH COMPLETE message is returned to the network. The MS shall delete its old P-TMSI and shall 
store the new one. If no P-TMSI has been included by the network in the ATTACH ACCEPT message, the old P-TMSI, 
if any available, shall be kept. 

If the message contains a P-TMSI signature, the MS shall use this P-TMSI signature as the new temporary signature for 
the GMM context. The MS shall delete its old P-TMSI signature, if any is available, and shall store the new one. If the 
message contains no P-TMSI signature, the old P-TMSI signature, if available, shall be deleted. 

If the network has requested the provision of the Inter RAT information container the MS shall return an ATTACH 
COMPLETE message including the Inter RAT information container IE to the network. 

The network may also send a list of "equivalent PLMNs" in the ATTACH ACCEPT message. Each entry of the list 
contains a PLMN code (MCCh-MNC). The mobile station shall store the list, as provided by the network, except that 
any PLMN code that is already in the "forbidden PLMN" list shall be removed from the "equivalent PLMNs" list before 
it is stored by the mobile station. In addition the mobile station shall add to the stored list the PLMN code of the 
registered PLMN that sent the Ust. All PLMNs in the stored list shall be regarded as equivalent to each other for PLMN 
selection, cell selection/re-selection and handover. The stored list in the mobile station shall be replaced on each 
occurrence of the ATTACH ACCEPT message. If no list is contained in the message, then the stored list in the mobile 
station shall be deleted. The list shall be stored in the mobile station while switched off so that it can be used for PLMN 
selection after switch on. 

In lu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has 
indicated "follow-on request pending" in ATTACH REQUEST message) the network shall indicate the "follow-on 
proceed" in the ATTACH ACCEPT message. If the network wishes to release the PS signalling connection, the 
network shall indicate "no follow-on proceed" in the ATTACH ACCEPT message. 

After that in lu mode, the mobile station shall act according to the follow-on proceed flag included in the Attach result 
information element in the ATTACH ACCEPT message (see subclause 4.7.13). 

In A/Gb mode, if the ATTACH ACCEPT message contains the Cell Notification information element, then the MS 
shall start to use the LLC NULL frame to perform cell updates. The network receiving an ATTACH COMPLETE 
message stops timer T3350, changes to GMM-REGISTERED state and considers the P-TMSI sent in the ATTACH 
ACCEPT message as valid. 

The network may also send a list of local emergency numbers in the ATTACH ACCEPT, by including the Emergency 
Number List IE. The mobile equipment shall store the list, as provided by the network, except that any emergency 
number that is already stored in the SIM/USIM shall be removed from the list before it is stored by the mobile 
equipment. If there are no emergency numbers stored on the SIM/USIM, then before storing the received list the mobile 
equipment shall remove from it any emergency number stored permanently in the ME for use in this case (see 3GPP TS 
22.101 [8]). The list stored in the mobile equipment shall be replaced on each receipt of a new Emergency Number List 
IE. 

The emergency number(s) received in the Emergency Number List IE are valid only in networks with the same MCC as 
in the cell on which this IE is received. If no list is contained in the ATTACH ACCEPT message, then the stored list in 
the mobile equipment shall be kept, except if the mobile equipment has successfully registered to a PLMN with an 
MCC different from that of the last registered PLMN. 

The mobile equipment shall use the stored list of emergency numbers received from the network in addition to the 
emergency numbers stored on the SIM/USIM or ME to detect that the number dialled is an emergency number. 

NOTE: The mobile equipment may use the emergency numbers list to assist the end user in determining whether 
the dialled number is intended for an emergency service or for another destination, e.g. a local directory 
service. The possible interactions with the end user are implementation specific. 

The list of emergency numbers shall be deleted at switch off and removal of the SIM/USIM. The mobile equipment 
shall be able to store up to ten local emergency numbers received from the network. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 08 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.3.1 .4 GPRS attach not accepted by the network 

If the attach request cannot be accepted by the network, an ATTACH REJECT message is transferred to the MS. The 
MS receiving the ATTACH REJECT message, stops timer T3310 and for all causes except #12, #14 and #15 deletes the 
list of "equivalent PLMNs". 

The MS shall then take one of the following actions depending upon the reject cause: 

# 3 (Illegal MS); 

# 6 (Illegal ME); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number. The new GMM state is GMM-DEREGISTERED. The SIM/USIM shall be considered as invalid for 
GPRS services until switching off or the SIM/USIM is removed. 

If the MS is IMSI attached, the MS shall in addition set the update status to U3 ROAMING NOT ALLOWED, 
shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A 
and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The 
SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the SIM/USIM is 
removed. 

# 7 (GPRS services not allowed); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM 
is removed. The new state is GMM-DEREGISTERED. 

# 8 (GPRS services and non-GPRS services not allowed); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number. The new GMM state is GMM-DEREGISTERED. 

The MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and 
ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, 
the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered 
as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed. 

# 1 1 (PLMN not allowed); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, 
shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2), shall reset the GPRS attach attempt counter and shall change to state GMM- 
DEREGISTERED. 

The MS shall store the PLMN identity in the "forbidden PLMN list". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall 
delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt 
counter. The new MM state is MM IDLE. 

- The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 

# 12 (Location area not allowed); 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 09 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2) and 
shall reset the attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. 

The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall 
delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt 
counter. The new MM state is MM IDLE. 

- The MS shall perform a cell selection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304. 

#13 (Roaming not allowed in this location area); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2) and 
shall reset the attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE or 
optionally to GMM-DEREGISTERED.PLMN-SEARCH. 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall 
delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt 
counter. The new MM state is MM IDLE. 

- The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 

# 14 (GPRS services not allowed in this PLMN); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, 
shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall change to state GMM-DEREGISTERED. 

The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list. A GPRS MS operating 
in MS operation mode C shall perform a PLMN selection instead of a cell selection. 

A GPRS MS operating in MS operation mode A or B in network operation mode II or III, is still IMSI attached 
for CS services in the network. 

As an implementation option, a GPRS MS operating in operation mode A or B may perform the following 
additional action. If no RR connection exists the MS may perform the action immediately. If the MS is operating 
in MS operation mode A and an RR connection exists, the MS may only perform the action when the RR 
connection is subsequently released: 

- The MS may perform a PLMN selection according to 3GPP TS 23. 122 [14]. 

The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause 
is: 

On the "User Controlled PLMN Selector with Access Technology " list or. 

On the "Operator Controlled PLMN Selector with Access Technology " list or, 

A PLMN identified as equivalent to any PLMN, with the same MCC, contained in the lists above. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 110 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

# 15 (No Suitable Cells In Location Area); 

The MS shall delete any RAI, P-TMSl, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and 
shall reset the attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall 
delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt 
counter. The new MM state is MM IDLE. 

The MS shall search for a suitable cell in another location area in the same PLMN according to 3GPP 
TS 43.022 [82] and 3GPP TS 25.304. 

Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is specified in 
subclause 4.7.3.1.5. 

4.7.3.1 .5 Abnormal cases in the MS 

The following abnormal cases can be identified: 

a) Access barred because of common access class control or PS domain specific access control 

The GPRS attach procedure shall not be started. The MS stays in the current serving cell and applies normal cell 
reselection process. The GPRS attach procedure is started as soon as possible, i.e. when access is granted or 
because of a cell change. 

b) Lower layer failure before the ATTACH ACCEPT or ATTACH REJECT message is received 

The procedure shall be aborted and the MS shall proceed as described below, except in the following 
implementation option cases b.l and b.2. 

b. 1) Release of PS signalling connection in lu mode before the completion of the GPRS attach procedure 

If the release of the PS signalling connection occurs before completion of the GPRS attach procedure, then the 
GPRS attach procedure shall be initiated again, if the following conditions apply: 

i) The original GPRS attach procedure was initiated over an existing PS signalling connection; and 

ii) The GPRS attach procedure was not due to timer T3310 expiry; and 

iii) No SECURITY MODE COMMAND message and no Non- Access Startum (NAS) messages relating to 
the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the 
ATTACH REQUEST message was transmitted. 

b.2) RR release in lu mode (i.e. RRC connection release) with, for example, cause "Normal", or "User inactivity" 
(see 3GPPTS 25.331 [32c] and 3GPP TS 44.118 [111]) 

The GPRS attach procedure shall be initiated again, if the following conditions apply: 

i) The original GPRS attach procedure was initiated over an existing RRC connection; and 

ii) The GPRS attach procedure was not due to timer T3310 expiry; and 

iii) No SECURITY MODE COMMAND message and no Non- Access Stratum (NAS) messages relating to 
the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the 
ATTACH REQUEST message was transmitted. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 111 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

NOTE: The RRC connection release cause that triggers the re-initiation of the GPRS attach procedure is 
implementation specific. 

c) T33 10 time-out 

On the first expiry of the timer, the MS shall reset and restart timer T3310 and shall retransmit the ATTACH 
REQUEST message. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3310, the MS 
shall abort the GPRS attach procedure and, in lu mode, release the PS signalling connection (see 
3GPP TS 25.331 [23c]). The MS shall proceed as described below. 

d) ATTACH REJECT, other causes than those treated in subclause 4.7.3.1.4 

Upon reception of the cause codes # 95, # 96, # 97, # 99 and # HI the MS should set the GPRS attach attempt 
counter to 5. The MS shall proceed as described below. 

e) Change of cell within the same RA (A/Gb mode only) 

If a cell change occurs within the same RA when the MS is in state GMM-REGISTERED-INITIATED, then the 
cell update procedure shall be performed before completion of the attach procedure. 

f) Change of cell into a new routing area 

If a cell change into a new routing area occurs before an ATTACH ACCEPT or ATTACH REJECT message has 
been received, the GPRS attach procedure shall be aborted and re-initiated immediately. If a routing area border 
is crossed when the ATTACH ACCEPT message is received but before an ATTACH COMPLETE message is 
sent, the GPRS attach procedure shall be aborted and the routing area updating procedure shall be initiated. If a 
P-TMSI was allocated during the GPRS attach procedure, this P-TMSI shall be used in the routing area updating 
procedure. If a P-TMSI signature was allocated together with the P-TMSI during the GPRS attach procedure, 
this P-TMSI signature shall be used in the routing area updating procedure. 

g) Mobile originated detach required 

If the MS is in state GMM-REGISTERED-INITIATED, the GPRS attach procedure shall be aborted and the 
GPRS detach procedure shall be performed (see subclause 4.7.4.1). 

h) Procedure collision 

If the MS receives a DETACH REQUEST message from the network in state GMM-REGISTERED- 
INITIATED with type of detach 're-attach not required, the GPRS detach procedure shall be progressed and the 
GPRS attach procedure shall be aborted. Otherwise the GPRS attach procedure shall be progressed and the 
DETACH REQUEST message shall be ignored. 

In cases b, c and d the MS shall proceed as follows. Timer T3310 shall be stopped if still running. The GPRS attach 
attempt counter shall be incremented. 

If the GPRS attach attempt counter is less than 5: 

- timer T33 1 1 is started and the state is changed to GMM-DEREGISTERED.ATTEMPTING-TO- ATTACH. 
If the GPRS attach attempt counter is greater than or equal to 5: 

- the MS shall delete any RAI, P-TMSI, P-TMSI signature, list of equivalent PLMNs, and GPRS ciphering key 
sequence number, shall set the GPRS update status to GU2 NOT UPDATED, shall start timer T3302. The state 
is changed to GMM-DEREGISTERED. ATTEMPTING-TO-ATTACH or optionally to GMM- 
DEREGISTERED.PLMN-SEARCH (see subclause 4.2.4.1.2) in order to perform a PLMN selection according 
to 3GPPTS 23.122 [14]. 

4.7.3.1 .6 Abnormal cases on the network side 

The following abnormal cases can be identified: 

a) Lower layer failure 

If a low layer failure occurs before the message ATTACH COMPLETE has been received from the MS and a 
new P-TMSI (or a new P-TMSI and a new P-TMSI signature) has been assigned, the network shall consider both 
the old and new P-TMSI each with its corresponding P-TMSI-signature as valid until the old P-TMSI can be 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 112 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

considered as invalid by the network (see subclause 4.7.1.5) and shall not resent the message ATTACH 
ACCEPT. During this period the network may: 

use the identification procedure followed by a P-TMSI reallocation procedure if the old P-TMSI is used by 
the MS in a subsequent message. 

b) Protocol error 

If the ATTACH REQUEST message is received with a protocol error, the network shall return an ATTACH 
REJECT message with one of the following reject causes: 

#96: Mandatory information element error; 

#99: Information element non-existent or not implemented; 

#100: Conditional IE error; 

#111: Protocol error, unspecified. 

c) T3350 time-out 

On the first expiry of the timer, the network shall retransmit the ATTACH ACCEPT message and shall reset and 
restart timer T3350. 

This retransmission is repeated four times, i.e. on the fifth expiry of timer T3350, the GPRS attach procedure 
shall be aborted. If a new P-TMSI or a new P-TMSI together with a new P-TMSI signature were allocated in the 
ATTACH ACCEPT message, the network shall consider both the old and new P-TMSI each together with the 
corresponding P-TMSI signatures as valid until the old P-TMSI can be considered as invalid by the network (see 
subclause 4.7.1.5). During this period the network acts as specified for case a. 

d. 1) ATTACH REQUEST received after the ATTACH ACCEPT message has been sent and before the ATTACH 
COMPLETE message is received 

If one or more of the information elements in the ATTACH REQUEST message differ from the ones received 
within the previous ATTACH REQUEST message, the previously initiated GPRS attach procedure shall be 
aborted if the ATTACH COMPLETE message has not been received and the new GPRS attach procedure shall 
be progressed, or 

If the information elements do not differ, then the ATTACH ACCEPT message shall be resent and the timer 
T3350 shall be restarted if an ATTACH COMPLETE message is expected. In that case, the retransmission 
counter related to T3350 is not incremented. 

d.2) More than one ATTACH REQUEST received and no ATTACH ACCEPT or ATTACH REJECT message 
has been sent 

If one or more of the information elements in the ATTACH REQUEST message differs from the ones received 
within the previous ATTACH REQUEST message, the previously initiated GPRS attach procedure shall be 
aborted and the new GPRS attach procedure shall be progressed; 

If the information elements do not differ, then the network shall continue with the previous attach procedure and 
shall not treat any further this ATTACH REQUEST message. 

e) ATTACH REQUEST received in state GMM-REGISTERED 

If an ATTACH REQUEST message is received in state GMM-REGISTERED the network may initiate the 
GMM common procedures; if it turned out that the ATTACH REQUEST message was send by an MS that has 
already been attached, the GMM context, PDP contexts and MBMS contexts, if any, are deleted and the new 
ATTACH REQUEST is progressed. 

f) ROUTING AREA UPDATE REQUEST message received before ATTACH COMPLETE message. 

Timer T3350 shall be stopped. The allocated P-TMSI shall be considered as valid and the routing area updating 
procedure shall be progressed as described in subclause 4.7.5. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



113 



ETSI TS 124 008 V7.14.0 (2009-03) 



MS 


ATTACH REQUEST 


Network 


SlarlT3310 






StopT3310 


ATTACH ACCEPT 


If P-TMSI and/or 






Start T3350 


If P-TMSI and/or 


ATTACH COMPLETE 


_i» Qtr*r» T'^'i^n 


TMSI allocated 














ATTACH REQUEST 




Start T3310 






StopT3310 


ATTACH REJECT 







Figure 4.7.3/1 3GPP TS 24.008: GPRS attach procedure and combined GPRS attach procedure 



4.7.3.2 



Combined GPRS attach procedure for GPRS and non-GPRS services 



The combined GPRS attach procedure is a GMM procedure used by a GPRS MS operating in MS operation modes A or 
B for IMSI attach for GPRS and non-GPRS services if the network operates in network operation mode I. 

If a GPRS MS operating in MS operation modes A or B is already attached for non-GPRS services by use of the MM 
specific IMSI attach procedure, but additionally wishes to perform an IMSI attach for GPRS services, the combined 
GPRS attach procedure shall also be used. 

The attach type information element shall indicate "combined GPRS/IMSI attach". In this case, the messages ATTACH 
ACCEPT, ATTACH COMPLETE, and ATTACH REJECT used by the combined GPRS attach procedure carry 
information for both the GPRS and the non-GPRS services. 

A GPRS MS in MS operation mode A shall perform the normal GPRS/IMSI attach procedure during an ongoing 
circuit-switched transaction. 



4.7.3.2.1 



Combined GPRS attach procedure initiation 



If the MS is in GMM state GMM-DEREGISTERED and in MM state MM IDLE, the MS initiates the combined GPRS 
attach procedure by sending an ATTACH REQUEST message to the network, starts timer T3310 and enters state 
GMM-REGISTERED-INITIATED and MM LOCATION UPDATING PENDING. 

The MS shall include a valid P-TMSI, if available, the P-TMSI signature associated with the P-TMSI and the routing 
area identity associated with the P-TMSI in the ATTACH REQUEST message. If there is no valid P-TMSI available, 
the IMSI shall be included instead of the P-TMSI and P-TMSI signature. Furthermore the MS shall include the TMSI 
status IE if no valid TMSI is available. 

In lu mode, if the MS wishes to prolong the established PS signalling connection after the GPRS attach (for example, 
the MS has any CM application request pending), it may set a follow-on request pending indicator on (see subclause 
4.7.13). 



4.7.3.2.2 



GMM Common procedure initiation 



The network may initiate GMM common procedures, e.g. the GMM identification and GMM authentication and 
ciphering procedure, depending on the received information such as IMSI, CKSN, old RAI, P-TMSI and P-TMSI 
signature. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 114 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.3.2.3 Combined GPRS attach accepted by the network 

Depending on the value of the attach resuh IE received in the ATTACH ACCEPT message, two different cases can be 
distinguished: 

Case 1) The attach resuh IE value indicates "combined GPRS attach": IMSI attach for GPRS and non-GPRS 
services have been successful. 

Case 2) The attach result IE value indicates "GPRS only": IMSI attach for GPRS services has been successful but 
IMSI attach for non-GPRS services has not been successful. 

In lu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has 
indicated "follow-on request pending" in ATTACH REQUEST message) the network shall indicate the "follow-on 
proceed" in the ATTACH ACCEPT message. If the network wishes to release the PS signalling connection, the 
network shall indicate "no follow-on proceed" in the ATTACH ACCEPT message. 

After that in lu mode, the mobile station shall act according to the follow-on proceed flag included in the Attach result 
information element in the ATTACH ACCEPT message (see subclause 4.7.13). 



4.7.3.2.3.1 Combined attach successful for GPRS and non-GPRS services 

The description for IMSI attach for GPRS services as specified in subclause 4.7.3.1.3 shall be followed. In addition, the 
following description for IMSI attach for non-GPRS services applies. 

The TMSI reallocation may be part of the combined GPRS attach procedure. The TMSI allocated is then included in the 
ATTACH ACCEPT message together with the location area identification (LAI). The network shall, in this case, 
change to state GMM-COMMON-PROCEDURE-INITIATED and shall start timer T3350 as described in 
subclause 4.7.6. 

The MS, receiving an ATTACH ACCEPT message, stores the received location area identification, stops timer T3310, 
reset the location update attempt counter and sets the update status to Ul UPDATED. If the message contains an IMSI, 
the mobile station is not allocated any TMSI, and shall delete any TMSI accordingly. If the message contains a TMSI, 
the MS shall use this TMSI as the new temporary identity. The MS shall delete its old TMSI and shall store the new 
TMSI. In this case, an ATTACH COMPLETE message is returned to the network. If neither a TMSI nor an IMSI has 
been included by the network in the ATTACH ACCEPT message, the old TMSI, if any available, shall be kept. The 
new MM state is MM IDLE, the new GMM state is GMM-REGISTERED. 

If the network has requested the provision of the Inter RAT information container the MS shall return an ATTACH 
COMPLETE message including the Inter RAT information container IE to the network. 

Any timer used for triggering the location update procedure (e.g T3211, T3212) shall be stopped if running. 

The network receiving an ATTACH COMPLETE message stops timer T3350, changes to state GMM-REGISTERED 
and considers the new TMSI as valid. 

4.7.3.2.3.2 Combined attacin successful for GPRS services only 

The description for IMSI attach for GPRS services as specified in subclause 4.7.3.1.3 shall be followed. In addition, the 
following description for IMSI attach for non-GPRS services applies. 

The MS receiving the ATTACH ACCEPT message takes one of the following actions depending on the reject cause: 

# 2 (IMSI unknown in HLR) 

The MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and 
ciphering key sequence number. The new MM state is MM IDLE. The SIM/USIM shall be considered as 
invalid for non-GPRS services until switching off or the SIM/USIM is removed. 

#16 (MSC temporarily not reachable) 

#17 (Network failure); or 

# 22 (Congestion) 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 115 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The MS shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. Timer T3310 shall 
be stopped if still running. The routing area updating attempt counter shall be incremented. 

If the routing area updating attempt counter is less than 5, and the stored RAI is equal to the RAI of the 
current serving cell and the GMM update status is equal to GUI UPDATED: 

- the MS shall keep the GMM update status GUI UPDATED and changes state to GMM- 
REGISTERED.ATTEMPTING-TO-UPDATE-MM. The MS shall start timer T3311. When timer T331 1 
expires the combined routing area update procedure indicating "combined RA/LA updating with IMSI 
attach" is triggered again. 

If the routing area updating attempt counter is greater than or equal to 5: 

- the MS shall start timer T3302 and shall change to state GMM-REGISTERED.ATTEMPTING-TO- 
UPDATE-MM; 

a GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific 
procedure; a GPRS MS operating in MS operation mode B may then proceed with appropriate MM 
specific procedures. The MM sublayer shall act as in network operation mode II or III (depending 
whether a PCCCH is present) as long as the combined GMM procedures are not successful and no new 
RA is entered. The new MM state is MM IDLE. 

Other reject cause values and the case that no GMM cause IE was received are considered as abnormal cases. The 
combined attach procedure shall be considered as failed for GPRS and non-GPRS services. The behaviour of the MS in 
those cases is specified in subclause 4.7.3.2.5. 

4.7.3.2.4 Combined GPRS attach not accepted by the network 

If the attach request can neither be accepted by the network for GPRS nor for non-GPRS services, an ATTACH 
REJECT message is transferred to the MS. The MS receiving the ATTACH REJECT message stops timer T3310, and 
for all causes except #12, #14 and #15 deletes the list of "equivalent PLMNs". 

The MS shall then take one of the following actions depending upon the reject cause: 

# 3 (Illegal MS); 

# 6 (Illegal ME), or 

# 8 (GPRS services and non-GPRS services not allowed); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (shall store it according to 
subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number. The new GMM state is GMM-DEREGISTERED. The new MM state is MM IDLE. 

The MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and 
ciphering key sequence number. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS 
services until switching off or the SIM/USIM is removed. 

# 7 (GPRS services not allowed); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM 
is removed. The new GMM state is GMM-DEREGISTERED; the MM state is MM IDLE. 

A GPRS MS operating in MS operation mode A or B which is not yet IMSI attached for CS services in the 
network shall then perform an IMSI attach for non-GPRS services according to the conditions for the MM IMSI 
attach procedure (see 4.4.3). 

A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the 
network is still IMSI attached for CS services in the network and shall then proceed with the appropriate MM 
specific procedure according to the MM service state. 

# 1 1 (PLMN not allowed); 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 116 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number stored, 
shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2), shall reset the routing area updating attempt counter and reset the GPRS attach attempt 
counter and changes to state GMM-DEREGISTERED. 

The MS shall set the update status to U3 ROAMING NOT ALLOWED, reset the location update attempt 
counter and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. 

The MS shall store the PLMN identity in the "forbidden PLMN list". 

The MS shall start timer T3340 as described in subclause 4.7. L9. 

The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 

# 12 (Location area not allowed); 

The MS shall delete any RAJ, P-TMSI, P-TMSI signature GPRS ciphering key sequence number, shall set the 
GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and 
shall reset the attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. 

The MS shall set the update status to U3 ROAMING NOT ALLOWED, reset the location update attempt 
counter and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. 

The MS shall store the LAI in the list of "forbidden location areas for regional provision of service". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

The MS shall perform a cell selection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304. 

#13 (Roaming not allowed in this location area); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and 
shall reset the attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE or 
optionally to GMM-DEREGISTERED.PLMN-SEARCH. 

The MS shall set the update status to U3 ROAMING NOT ALLOWED, reset the location update attempt 
counter and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. 

The mobile station shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 

# 14 (GPRS services not allowed in this PLMN); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, 
shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall change to state GMM-DEREGISTERED. 

The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list. 

As an implementation option, a GPRS MS operating in operation mode A or B may perform a PLMN selection 
according to 3GPP TS 23.122 [14]. 

The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause 
is: 

On the "User Controlled PLMN Selector with Access Technology " or. 

On the "Operator Controlled PLMN Selector with Access Technology " list or, 

- A PLMN identified as equivalent to any PLMN, with the same MCC, contained in the lists above. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 117 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the MS does not perform a PLMN selection then a GPRS MS operating in MS operation mode A or B which 
is not yet IMSI attached for CS services in the network shall then perform an IMSI attach for non-GPRS services 
according to the conditions for the MM IMSI attach procedure (see 4.4.3). 

A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the 
network is still IMSI attached for CS services in the network and shall then proceed with the appropriate MM 
specific procedure according to the MM service state. 

# 15 (No Suitable Cells In Location Area); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and 
shall reset the attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. 

The MS shall set the update status to U3 ROAMING NOT ALLOWED, reset the location update attempt 
counter and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

The MS shall search for a suitable cell in another location area in the same PLMN according to 3GPP TS 43.022 
[82] and 3GPP TS 25.304. 

Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is specified in 
subclause 4.7.3.2.5. 

4.7.3.2.5 Abnormal cases in the MS 

The MS shall proceed as follows: 

If the combined attach was successful for GPRS services only and the ATTACH ACCEPT message contained a 
cause value not treated in subclause 4.7.3.2.3.2 or the GMM Cause IE is not included in the message, the MS 
shall follow the procedure specified in subclause 4.7.3.1.5 step d), with the following modification; 

Otherwise, the abnormal cases specified in subclause 4.7.3.1.5 apply with the following modification. 

If the GPRS attach attempt counter is incremented according to subclause 4.7.3.1.5 the next actions depend on the 
Location Area Identities (stored on SIM/USIM and the one of the current serving cell) and the value of the attach 
attempt counter: 

if the update status is Ul UPDATED, and the stored LAI is equal to the one of the current serving cell and the 
attach attempt counter is smaller than 5, then the mobile station shall keep the update status to Ul UPDATED, 
the new MM state is MM IDLE substate NORMAL SERVICE; 

if the attach attempt counter is smaller than 5 and, additionally, the update status is different from Ul 
UPDATED or the stored LAI is different from the one of the current serving cell, then the mobile station shall 
delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM and list of equivalent PLMNs 
and set the update status to U2 NOT UPDATED. The MM state remains MM LOCATION UPDATING 
PENDING; or 

if the attach attempt counter is greater or equal to 5, then the mobile station shall delete any LAI, TMSI, 
ciphering key sequence number stored in the SIM/USIM and list of equivalent PLMNs and set the update status 
to U2 NOT UPDATED. 

A GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a 
GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures. 
The MM sublayer shall act as in network operation mode II or III (depending whether a PCCCH is present) as 
long as the combined GMM procedures are not successful and no new RA is entered. The new MM state is MM 
IDLE substate ATTEMPTING TO UPDATE or optionally MM IDLE substate PLMN SEARCH in order to 
perform a PLMN selection according to 3GPP TS 23.122 [14].. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 118 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.3.2.6 Abnormal cases on the network side 

The abnormal cases specified in subclause 4.7.3.1.6 apply with the exceptions for cases a and c in which in addition to 
the P-TMSI and P-TMSI signature the old TMSI shall be considered occupied until the new TMSI is used by the MS in 
a subsequent message. 

4.7.4 GPRS detach procedure 

The GPRS detach procedure is used: 

to detach the IMSI for GPRS services only. Independent of the network operation mode, this procedure is used 
by all kind of GPRS MSs; 

as a combined GPRS detach procedure used by GPRS MSs operating in MS operation mode A or B to detach the 
IMSI for GPRS and non-GPRS services or for non-GPRS services only, if the network operates in network 
operation mode I and no circuit-switched transaction is ongoing; or 

in the case of a network failure condition to indicate to the MS that a re-attach with successive activation of 
previously active PDP contexts shall be performed. In this case, the MS may also perform the procedures needed 
in order to activate any previously active multicast service(s). 

After completion of a GPRS detach procedure or combined GPRS detach procedure for GPRS and non-GPRS services 
the GMM context is released. 

The GPRS detach procedure shall be invoked by the MS if the MS is switched off, the SIM/USIM card is removed from 
the MS or if the GPRS or non-GPRS capability of the MS is disabled. The procedure may be invoked by the network to 
detach the IMSI for GPRS services. The GPRS detach procedure causes the MS to be marked as inactive in the network 
for GPRS services, non-GPRS services or both services. 

In A/Gb mode, if the GPRS detach procedure is performed, the PDP contexts and the MBMS contexts, if any, are 
deactivated locally without peer to peer signalling between the SM and LLC entities in the MS and the network. 

In lu mode, if the GPRS detach procedure is performed, the PDP contexts and the MBMS contexts, if any, are 
deactivated locally without peer to peer signalling between the SM entities in the MS and the network. 

4.7.4.1 MS initiated GPRS detach procedure 

4.7.4.1 .1 MS initiated GPRS detach procedure initiation 

The GPRS detach procedure is initiated by the MS by sending a DETACH REQUEST message. The detach type 
information element may indicate "GPRS detach with switching off, "GPRS detach without switching off", "IMSI 
detach", "GPRS/IMSI detach with switching off or "GPRS/IMSI detach without switching off. 

The MS shall include the P-TMSI in the DETACH REQUEST message. The MS shall also include a valid P-TMSI 
signature, if available. 

If the MS is not switched off and the MS is in the state GMM_REGISTERED, timer T3321 shall be started after the 
DETACH REQUEST message has been sent. If the detach type information element value indicates "IMSI Detach" the 
MS shall enter GMM-REGISTERED.IMSI-DETACH_INITIATED, otherwise the MS shall enter the state GMM- 
DEREGISTERED-INITIATED. If the detach type information element value indicates "IMSI Detach" or "GPRS/IMSI 
Detach", state MM IMSI DETACH PENDING is entered. If the MS is to be switched off, the MS shall try for a period 
of 5 seconds to send the DETACH REQUEST message. If the MS is able to send the DETACH REQUEST message 
during this time the MS may be switched off. 

If the detach type information element value indicates "GPRS detach without switching off " and the MS is attached for 
GPRS and non-GPRS services and the network operates in network operation mode I, then if in the MS the timer T3212 
is not already running, the timer T3212 shall be set to its initial value and restarted after the DETACH REQUEST 
message has been sent. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 119 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.4.1 .2 MS initiated GPRS detach procedure completion for GPRS services only 

When the DETACH REQUEST message is received by the network, the network shall send a DETACH ACCEPT 
message to the MS, if the detach type IE value indicates that the detach request has not been sent due to switching off. If 
switching off was indicated, the procedure is completed when the network receives the DETACH REQUEST message. 
The network and the MS shall deactivate the PDP contexts, the MBMS contexts and deactivate the logical link(s), if 
any. 

The MS is marked as inactive in the network for GPRS services; state GMM-DEREGISTERED is entered in the MS 
and the network. 

In lu mode, if the detach has been sent due to switching off, then the network shall release the resources in the lower 
layers for this MS (see 3GPP TS 25.331 [23c]). 

NOTE: When the DETACH REQUEST message is received by the network, and if the detach type IE value 

indicates that the detach is not due to power off, the authentication and ciphering procedure as well as the 
identification procedure may be performed. 

4.7.4.1 .3 MS initiated combined GPRS detach procedure completion 

When the DETACH REQUEST message is received by the network, a DETACH ACCEPT message shall be sent to the 
MS, if the detach type IE value indicates that the detach request has not been sent due to switching off. Depending on 
the value of the detach type IE the following applies: 

GPRS/IMSI detach: 

The MS is marked as inactive in the network for GPRS and for non-GPRS services. The network and the MS shall 
deactivate the PDP contexts, the MBMS contexts and deactivate the logical link(s), if any. The States GMM- 
DEREGISTERED and MM NULL are entered in both the MS and the network. 

In lu mode, if the detach has been sent due to switching off, then the network shall release the resources in the lower 
layers for this MS (see 3GPP TS 25.331 [23c]). 

IMSI detach: 

The MS is marked as inactive in the network for non-GPRS services. State MM NULL is entered in the MS and the 

network. 

4.7.4.1 .4 Abnormal cases in the MS 

The following abnormal cases can be identified: 

a) T3321 time-out 

On the first expiry of the timer, the MS shall retransmit the DETACH REQUEST message and shall reset and 
restart timer T3321. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3321, the GPRS 
detach procedure shall be aborted, the MS shall change to state: 

- MM-NULL if "IMSI detach" was requested; 

- GMM-REGISTERED.NORMAL-SERVICE if "IMSI Detach" was requested; 

- GMM-DEREGISTERED if "GPRS detach" was requested; 

- GMM-DEREGISTERED and MM-NULL if "GPRS/IMSI" detach was requested. 

b) Lower layer failure before reception of DETACH ACCEPT message 

The detach procedure is aborted and the MS shall change to one of the following states, except in the following 
implementation option cases b.l, b.2 and b3: 

- MM-NULL if "IMSI detach" was requested; 

- GMM-REGISTERED.NORMAL-SERVICE if "IMSI Detach" was requested; 

- GMM-DEREGISTERED if "GPRS detach" was requested; 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 20 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- GMM-DEREGISTERED and MM-NULL if "IMSI/GPRS" detach was requested. 

b. 1) Release of PS signalling connection before the completion of the GPRS detach procedure 

The release of the PS signalling connection before completion of the GPRS detach procedure shall result in the 
GPRS detach procedure being initiated again, if the following conditions apply: 

i) The original GPRS detach procedure was initiated over an existing PS signalling connection; and 

ii) No SECURITY MODE COMMAND message and no Non- Access Stratum (NAS) messages relating to 
the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the 
DETACH REQUEST message was transmitted. 

b.2) RR release in lu mode (i.e. RRC connection release) with cause different than "Directed signalling 

connection re-establishment", for example, "Normal", or"User inactivity" (see 3GPP TS 25.331 [32c] and 3GPP 
TS 44.118 [111]) 

The GPRS detach procedure shall be initiated again, if the following conditions apply: 

i) The original GPRS detach procedure was initiated over an exisiting RRC connection; and 

ii) No SECURITY MODE COMMAND message and no Non- Access Stratum (NAS) messages relating to 
the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the 
DETACH REQUEST message was transmitted. 

NOTE: The RRC connection release cause different than "Directed signalling connection re-establishment" that 
triggers the re-initiation of the GPRS detach procedure is implementation specific. 

b.3) RR release in lu mode (i.e. RRC connection release) with cause "Directed signalling connection re- 
establishment" (see 3GPP TS 25.331 [32c] and 3GPPTS 44.118 [111]) 

The routing area updating procedure shall be initiated followed by completion of the GPRS detach procedure if 
the following conditions apply: 

i) The original GPRS detach procedure was not due to SIM removal; and 

ii) The original GPRS detach procedure was not due to a rerun of the procedure due to "Directed signalling 
connection reestablishment". 

c) Detach procedure collision 

If the MS receives a DETACH REQUEST message before the MS initiated GPRS detach procedure has been 
completed, a DETACH ACCEPT message shall be sent to the network. 

d) Detach and GMM common procedure collision 

GPRS detach containing cause "power off: 

If the MS receives a message used in a GMM common procedure before the GPRS detach procedure has 
been completed, this message shall be ignored and the GPRS detach procedure shall continue. 

GPRS detach containing other causes than "power off": 

- If the MS receives a P-TMSI REALLOCATION COMMAND, a GMM STATUS, or a GMM 
INFORMATION message before the GPRS detach procedure has been completed, this message shall be 
ignored and the GPRS detach procedure shall continue. 

- If the MS receives an AUTHENTICATION AND CIPHERING REQUEST or IDENTITY REQUEST 
message, before the GPRS detach procedure has been completed, the MS shall respond to it as described in 
subclause 4.7.7 and 4.7.8 respectively. 

e) Change of cell within the same RA (A/Gb mode only) 

If a cell change occurs within the same RA before a DETACH ACCEPT message has been received, then the 
cell update procedure shall be performed before completion of the detach procedure. 

f) Change of cell into a new routing area 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



121 



ETSI TS 124 008 V7.14.0 (2009-03) 



If a cell change into a new routing area occurs before a DETACH ACCEPT message has been received, the 
GPRS detach procedure shall be aborted and re-initiated after successfully performing a routing area updating 
procedure. If the detach procedure is performed due to the removal of the SIM/USIM the MS shall abort the 
detach procedure and enter the state GMM-DEREGISTERED. 

g) Access barred because of common access class control or PS domain specific access control 

The signalling procedure for GPRS detach shall not be started. The MS starts the signalling procedure as soon as 
possible and if still necessary, i.e. when the barred state is removed or because of a cell change, or performs a 
local detach immediately or after an implementation dependent time. 





MS 




Network 


Start T3321 




DETACH REQUEST 










StopT3321 




DETACH ACCEPT 






















DETACH REQUEST 













Figure 4.7.4/1 3GPP TS 24.008: MS initiated GPRS detach procedure 



4.7.4.2 



Network initiated GPRS detach procedure 



4.7.4.2.1 



Network initiated GPRS detach procedure initiation 



The network initiates the GPRS detach procedure by sending a DETACH REQUEST message to the MS. The 
DETACH REQUEST message shall include a detach type IE. In addition, the network may include a cause IE to 
specify the reason for the detach request. The network shall start timer T3322. If the detach type IE indicates "re-attach 
not required" or "re-attach required", the network shall deactivate the PDP contexts, the MBMS contexts and deactivate 
the logical link(s), if any, and shall change to state GMM-DEREGISTERED-INITIATED. 



4.7.4.2.2 



Network initiated GPRS detach procedure completion by the MS 



When receiving the DETACH REQUEST message and the detach type IE indicates "re-attach required", the MS shall 
deactivate the PDP contexts, the MBMS contexts and deactivate the logical link(s), if any. The MS shall then send a 
DETACH ACCEPT message to the network and shall change state to GMM-DEREGISTERED. The MS shall, after the 
completion of the GPRS detach procedure, initiate a GPRS attach procedure. The MS should also activate PDP 
context(s) to replace any previously active PDP context(s). The MS should also perform the procedures needed in order 
to activate any previously active multicast service(s). 

NOTE: In some cases, user interaction may be required and then the MS cannot activate the PDP/MBMS 
context(s) automatically. 

A GPRS MS operating in MS operation mode A or B in network operation mode I, which receives an DETACH 
REQUEST message with detach type indicating "re-attach required" or "re-attach not required" and no cause code, is 
only detached for GPRS services in the network. 

When receiving the DETACH REQUEST message and the detach type IE indicates "IMSI detach", the MS shall not 
deactivate the PDP/MBMS contexts. The MS shall set the MM update status to U2 NOT UPDATED. A MS in 
operation mode A or B in network operation mode I may send a DETACH ACCEPT message to the network, and shall 
re-attach to non-GPRS service by performing the combined routing area updating procedure according to subclause 
4.7.5.2, sending a ROUTING AREA UPDATE REQUEST message with Update type IE indicating "combined RA/LA 
updating with IMSI attach". A MS in operation mode A that is in an ongoing circuit-switched transaction shall initiate 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 22 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

the combined routing area updating after the circuit-switched transaction has been released. A MS in operation mode C, 
or in MS operation mode A or B in network operation mode II or III, shall send a DETACH ACCEPT message to the 
network. 

If the detach type IE indicates "IMSI detach", or "re-attach required" then the MS shall ignore the cause code if 
received. 

If the detach type information element value indicates "re-attach required" or "re-attach not required" and the MS is 
attached for GPRS and non-GPRS services and the network operates in network operation mode I, then if in the MS the 
timer T3212 is not already running, the timer T3212 shall be set to its initial value and restarted. 

When receiving the DETACH REQUEST message and the detach type IE indicates "re-attach not required" and the 
cause code is not "#2 (IMSI unknown in HLR)", the MS shall deactivate the PDP contexts, the MBMS contexts and 
deactivate the logical link(s), if any. The MS shall then send a DETACH ACCEPT message to the network and shall 
change state to GMM-DEREGISTERED. 

If the detach type IE indicates "re-attach not required", then, depending on the received cause code, the MS shall act as 
follows: 

# 2 (IMSI unknown in HLR); 

The MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and 
ciphering key sequence number. The new MM state is MM IDLE. The SIM/USIM shall be considered as invalid 
for non-GPRS services until switching off or the SIM/USIM is removed. 

A GPRS MS operating in MS operation mode A or B in network operation mode I, is still IMSI attached for 
GPRS services in the network. 

# 3 (Illegal MS); 

# 6 (Illegal ME); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number. The new GMM state is GMM-DEREGISTERED. The SIM/USIM shall be considered as invalid for 
GPRS services until switching off or the SIM/USIM is removed. 

A GPRS MS operating in MS operation mode A or B shall in addition set the update status to U3 ROAMING 
NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in 
MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency 
call is ongoing. The SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or 
the SIM/USIM is removed. 

# 7 (GPRS services not allowed); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.L3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM 
is removed. The new state is GMM-DEREGISTERED. 

A GPRS MS operating in MS operation mode A or B in network operation mode I shall set the timer T3212 to 
its initial value and restart it, if it is not already running. 

A GPRS MS operating in MS operation mode A or B in network operation mode I, is still IMSI attached for CS 
services in the network. 

# 8 (GPRS services and non-GPRS services not allowed); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number. The new GMM state is GMM-DEREGISTERED. 

The MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and 
ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, 
the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered 
as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 23 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

# 1 1 (PLMN not allowed); 

The MS shall delete any RAI or LAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, 
shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2). The new GMM state is GMM-DEREGISTERED. 

The MS shall store the PLMN identity in the "forbidden PLMN list". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- A GPRS MS operating in MS operation mode A or B shall set the update status to U3 ROAMING NOT 
ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM 
IDLE. 

- The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 

# 12 (Location area not allowed); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature GPRS ciphering key sequence number, shall set the 
GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and 
shall reset the attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. 

The MS shall store the LAI in the list of "forbidden location areas for regional provision of service". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall 
delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt 
counter. The new MM state is MM IDLE. 

- The MS shall perform a cell selection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304. 

#13 (Roaming not allowed in this location area); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2) and 
shall reset the attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE or 
optionally to GMM-DEREGISTERED.PLMN-SEARCH. 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall 
delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt 
counter. The new MM state is MM IDLE. 

- The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 24 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

# 14 (GPRS services not allowed in this PLMN); 

The MS shall delete any RAI, P-TMSI, P-TMSl signature, and GPRS ciphering key sequence number stored, 
shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall change to state GMM-DEREGISTERED. 

The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list. 

A GPRS MS operating in MS operation mode A or B in network operation mode 1 shall set the timer T3212 to 
its initial value and restart it, if it is not already running. 

A GPRS MS operating in MS operation mode A or B, is still IMSl attached for CS services in the network. 

# 15 (No Suitable Cells In Location Area); 

The MS shall delete any RAI, P-TMSl, P-TMSl signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and 
shall reset the attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall 
delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt 
counter. The new MM state is MM IDLE. 

The MS shall search for a suitable cell in another location area in the same PLMN according to 3GPP 
TS 43.022 [82] and 3GPP TS 25.304. 

Other cause values shall not impact the update status. Further actions of the MS are implementation dependent. 

4.7.4.2.3 Network initiated GPRS detach procedure completion by the network 

The network shall, upon receipt of the DETACH ACCEPT message, stop timer T3322 and shall change state to GMM- 
DEREGISTERED. 

4.7.4.2.4 Abnormal cases on the network side 

The following abnormal cases can be identified: 

a) T3322 time-out 

On the first expiry of the timer, the network shall retransmit the DETACH REQUEST message and shall start 
timer T3322. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3322, the GPRS detach 
procedure shall be aborted and the network changes to state GMM-DEREGISTERED. 

b) Low layer failure 

The GPRS detach procedure is aborted and the network changes to state GMM-DEREGISTERED. 

c) GPRS detach procedure collision 

If the network receives a DETACH REQUEST message with "switching off indicated, before the network 
initiated GPRS detach procedure has been completed, both procedures shall be considered completed. 

If the network receives a DETACH REQUEST message without "switching off indicated, before the network 
initiated GPRS detach procedure has been completed, the network shall send a DETACH ACCEPT message to 
the MS. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



125 



ETSI TS 124 008 V7.14.0 (2009-03) 



d) GPRS detach and GPRS attach procedure collision 

If the network receives an ATTACH REQUEST message before the network initiated GPRS detach procedure 
with type of detach 're-attach not required' has been completed, the network shall ignore the ATTACH 
REQUEST message. If the detach type IE value, sent in the DETACH REQUEST message, indicates "re-attach 
required" the detach procedure is aborted and the GPRS attach procedure shall be progressed after the PDP 
contexts and MBMS contexts, if any, have been deleted. If the detach type IE value, sent in the DETACH 
REQUEST message, indicates "IMSI detach" the detach procedure is aborted and the GPRS attach procedure 
shall be progressed. 

e) GPRS detach and routing area updating procedure collision 

GPRS detach containing detach type "re-attach required" or "re-attach not required": 

If the network receives a ROUTING AREA UPDATE REQUEST message before the network initiated 
GPRS detach procedure has been completed, the detach procedure shall be progressed, i.e. the ROUTING 
AREA UPDATE REQUEST message shall be ignored. 

GPRS detach containing detach type "IMSI detach": 

If the network receives a ROUTING AREA UPDATE REQUEST message before the network initiated 
GPRS detach procedure has been completed, the network shall abort the detach procedure, shall stop T3322 
and shall progress the routing area update procedure. 

f) GPRS detach and service request procedure collision 

If the network receives a SERVICE REQUEST message before the network initiated GPRS detach procedure 
has been completed, the network shall ignore the SERVICE REQUEST message. 



MS 


DETACH REQUEST 


Network 

Ttni-t TTTT^ 




DETACH ACCEPT 


StopT3322 





Figure 4.7.4/2 3GPP TS 24.008: Network initiated GPRS detach procedure 

4.7.5 Routing area updating procedure 

This procedure is used for: 

normal routing area updating to update the registration of the actual routing area of an MS in the network. This 
procedure is used by GPRS MSs in MS operation mode C and by GPRS MSs in MS operation modes A or B that 
are IMSI attached for GPRS and non-GPRS services if the network operates in network operation mode II or III; 

combined routing area updating to update the registration of the actual routing and location area of an MS in the 
network. This procedure is used by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS 
and non-GPRS services provided that the network operates in network operation mode I; 

periodic routing area updating. This procedure is used by GPRS MSs in MS operation mode C and by GPRS 
MSs in MS operation modes A or B that are IMSI attached for GPRS or for GPRS and non-GPRS services 
independent of the network operation mode; 

IMSI attach for non-GPRS services when the MS is IMSI attached for GPRS services. This procedure is used by 
GPRS MSs in MS operation modes A or B, if the network operates in network operation mode I; 

in A/Gb mode, resuming GPRS services when the RR sublayer indicated a resumption failure after dedicated 
mode was left, see 3GPP TS 44.018 [84]; 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 26 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

in A/Gb mode, updating the network with the new MS Radio Access Capability IE when the content of the IE 
has changed; 

updating the network with the new DRX parameter IE when the content of the IE has changed; 

NOTE 1: Such changes can be used e.g. when the MS activates a PDP context with service requirements that 
cannot be met with the current DRX parameter. As PDP context(s) are activated and deactivated, the 
GMM context will be updated with an appropriate DRX parameter; 

- re-negotiation of the READY timer value; 

lu mode to A/Gb mode and for A/Gb mode to lu mode intersystem change, see subclause 4.7.1.7; or 

in lu mode, to re-synchronize the PMM mode of MS and network after RRC connection release with cause 
"Directed signalling connection re-establishment", see subclause 4.7.2.5. 

The routing area updating procedure shall also be used by a MS which is attached for GPRS services if a new PLMN is 
entered (see 3GPP TS 23.122 [14]). 

Subclause 4.7.5.1 describes the routing area updating procedures for updating the routing area only. The combined 
routing area updating procedure used to update both the routing and location area is described in subclause 4.7.5.2. 

The routing area updating procedure is always initiated by the MS. It is only invoked in state GMM-REGISTERED. 

To limit the number of subsequently rejected routing area update attempts, a routing area updating attempt counter is 
introduced. The routing area updating attempt counter shall be incremented as specified in subclause 4.7.5.1.5. 
Depending on the value of the routing area updating attempt counter, specific actions shall be performed. The routing 
area updating attempt counter shall be reset when: 

a GPRS attach procedure is successfully completed; or 

a routing area updating procedure is successfully completed; 

and additionally when the MS is in substate ATTEMPTING-TO-UPDATE: 

a new routing area is entered; 

expiry of timer T3302; or 

at request from registration function. 

The mobile equipment shall contain a list of "forbidden location areas for roaming", as well as a list of "forbidden 
location areas for regional provision of service". The handling of these lists is described in subclause 4.4.1. 

The Mobile Equipment shall contain a list of "equivalent PLMNs". The handling of this list is described in 
subclause 4.4.1. 

In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 23.122 [14]. The MS 
shall construct the Routing Area Identification of the cell from this chosen PLMN identity, and the LAC and the RAC 
received on the BCCH. If the constructed RAI is different from the stored RAI, the MS shall initiate the routing area 
updating procedure. The chosen PLMN identity shall be indicated to the RAN in the RRC INITIAL DIRECT 
TRANSFER message (see 3GPP TS 25.331 [23c]). Whenever a ROUTING AREA UPDATING REJECT message with 
the cause "PLMN not allowed" is received by the MS, the chosen PLMN identity shall be stored in the "forbidden 
PLMN list". Whenever a ROUTING AREA UPDATING REJECT message is received by the MS with the cause 
"Roaming not allowed in this location area", "Location Area not allowed", or "No suitable cells in Location Area", the 
LAI that is part of the constructed RAI which triggered the routing area updating procedure shall be stored in the 
suitable list. 

In A/Gb mode, user data transmission in the MS shall be suspended during the routing area updating procedure, except 
if the routing area updating procedure is triggered by a PS handover procedure as described in 3GPP TS 43.129 [113]; 
user data reception shall be possible. User data transmission in the network may be suspended during the routing area 
updating procedure. 

In lu mode, user data transmission and reception in the MS shall not be suspended during the routing area updating 
procedure. User data transmission in the network shall not be suspended during the routing area updating procedure. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 27 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

In lu mode, when a ROUTING AREA UPDATE REQUEST is received by the SGSN over a new PS signalling 
connection while there is an ongoing PS signalling connection (network is already in mode PMM-CONNECTED) for 
this UE, the network shall progress the routing area update procedure as normal and release the previous PS signalling 
connection when the routing area update procedure has been accepted by the network. 

NOTE 2: The re-establishment of the radio bearers of active PDP contexts is done as described in subclause 
"Service Request procedure". 

The network informs the MS about the support of specific features, such as LCS-MOLR or MBMS, in the "Network 
feature support" Information Element. The information is either explicitly given by sending the "Network feature 
support" IE or implicitly by not sending it. The handling in the network is described in subclause 9.4.15.1 1. The MS 
may use the indication to inform the user about the availability of the appropriate services and it shall not request 
services that have not been indicated as available. The indication for MBMS is defined in subclause "MBMS feature 
support indication" in 3GPP TS 23.246 [106]. 

4.7.5.1 Normal and periodic routing area updating procedure 

Periodic routing area updating is used to periodically notify the availability of the MS to the network. The value of the 
update type IE in the ROUTING AREA UPDATE REQUEST message shall indicate "periodic updating". The 
procedure is controlled in the MS by timer T3312. When timer T3312 expires, the periodic routing area updating 
procedure is started. Start and reset of timer T3312 is described in subclause 4.7.2.2. 

In A/Gb mode, the normal routing area updating procedure is initiated: 

- when the MS detects a change of the routing area in state GMM-REGISTERED; 

when the MS determines that GPRS resumption shall be performed; 

when the MS needs to update the network with the new MS Radio Access Capability IE; or 

when the MS needs to update the network with the new DRX parameter IE. 

The ROUTING AREA UPDATE REQUEST message shall always be the first data sent by the MS when a routing area 
border is crossed. The routing area identification is broadcast on the broadcast channel(s). 

In lu mode, the normal routing area updating procedure is initiated when the MS detects a change of the routing area in 
state GMM-REGISTERED. The ROUTING AREA UPDATE REQUEST message shall always be the first GMM 
message sent by the MS when a routing area border is crossed. 

A normal routing area updating shall abort any ongoing GMM procedure. Aborted GMM procedures may be repeated 
after the normal routing area updating procedure has been successfully performed. The value of the update type IE 
included in the message shall indicate" RA updating". 

4.7.5.1 .1 Normal and periodic routing area updating procedure initiation 

To initiate the normal routing area updating procedure, the MS sends the message ROUTING AREA UPDATE 
REQUEST to the network, starts timer T3330 and changes to state GMM-ROUTING-AREA-UPDATING- 
INITIATED. The message ROUTING AREA UPDATE REQUEST shall contain the P-TMSI signature when received 
within a previous ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message. 

In lu mode, if the MS wishes to prolong the established PS signalling connection after the normal routing area updating 
procedure (for example, the MS has any CM application request pending), it may set a follow-on request pending 
indicator on (see subclause 4.7.13). 

4.7.5.1 .2 GMM Common procedure initiation 

The network may initiate GMM common procedures, e.g. the GMM authentication and ciphering procedure. 

4.7.5.1 .3 Normal and periodic routing area updating procedure accepted by the network 

If the routing area updating request has been accepted by the network, a ROUTING AREA UPDATE ACCEPT 
message shall be sent to the MS. The network may assign a new P-TMSI and/or a new P-TMSI signature for the MS. If 
a new P-TMSI and/or P-TMSI signature have been assigned to the MS, it/they shall be included in the ROUTING 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 28 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

AREA UPDATE ACCEPT message together with the routing area identification. In a shared network the network shall 
indicate the PLMN identity of the CN operator that has accepted the routing area updating request in the RAI contained 
in the ROUTING AREA UPDATE ACCEPT message (see 3GPP TS 23.251 [109]). 

If a new DRX parameter was included in the ROUTING AREA UPDATE REQUEST message, the network shall store 
the new DRX parameter and use it for the downlink transfer of signalling and user data. 

If the MS has indicated in the ROUTING AREA UPDATE REQUEST message that it supports PS inter-RAT handover 
to UTRAN lu mode, the network may include in the ROUTING AREA UPDATE ACCEPT message a request to 
provide the Inter RAT information container. 

In A/Gb mode the Cell Notification information element shall be included in the ROUTING AREA UPDATE ACCEPT 
message in order to indicate the ability of the network to support the Cell Notification. 

The network shall change to state GMM-COMMON -PROCEDURE-INITIATED and shall start the supervision timer 
T3350 as described in subclause 4.7.6. 

If the LAI or PLMN identity contained in the ROUTING AREA UPDATE ACCEPT message is a member of any of 
the "forbidden" lists then any such entry shall be deleted. 

In lu mode, the network should prolong the PS signalling connection if the mobile station has indicated a follow-on 
request pending in ROUTING AREA UPDATE REQUEST. The network may also prolong the PS signalling 
connection without any indication from the mobile terminal. 

If the PDP context status information element is included in ROUTING AREA UPDATE REQUEST message, then the 
network shall deactivate all those PDP contexts locally (without peer to peer signalling between the MS and the 
network), which are not in SM state PDP-INACTIVE on network side but are indicated by the MS as being in state 
PDP-INACTIVE. 

If the MBMS context status information element is included in the ROUTING AREA UPDATE REQUEST message, 
then the network shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and 
network) which are not in SM state PDP-INACTIVE on the network side, but are indicated by the MS as being in state 
PDP-INACTIVE. If no MBMS context status information element is included, then the network shall deactivate all 
MBMS contexts locally which are not in SM state PDP-INACTIVE on the network side. 

Upon receipt of a ROUTING AREA UPDATE ACCEPT message, the MS stores the received routing area 
identification, stops timer T3330, shall reset the routing area updating attempt counter and sets the GPRS update status 
to GUI UPDATED. If the message contains a P-TMSI, the MS shall use this P-TMSI as new temporary identity for 
GPRS services and shall store the new P-TMSI. If no P-TMSI was included by the network in the ROUTING AREA 
UPDATING ACCEPT message, the old P-TMSI shall be kept. Furthermore, the MS shall store the P-TMSI signature if 
received in the ROUTING AREA UPDATING ACCEPT message. If no P-TMSI signature was included in the 
message, the old P-TMSI signature, if available, shall be deleted. 

If the ROUTING AREA UPDATE REQUEST message was used to update the network with a new DRX parameter IE, 
the MS shall start using the new DRX parameter upon receipt of the ROUTING AREA UPDATE ACCEPT message. 

If the PDP context status information element is included in ROUTING AREA UPDATE ACCEPT message, then the 
MS shall deactivate all those PDP contexts locally (without peer to peer signalling between the MS and network), which 
are not in SM state PDP-INACTIVE in the MS but are indicated by the network as being in state PDP-INACTIVE. 

If the MBMS context status information element is included in the ROUTING AREA UPDATE ACCEPT message, 
then the MS shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and 
network) which are not in SM state PDP-INACTIVE in the MS, but are indicated by the network as being in state PDP- 
INACTIVE. If no MBMS context status information element is included, then the MS shall deactivate all those MBMS 
contexts locally which are not in SM state PDP-INACTIVE in the MS. 

In A/Gb mode, if the ROUTING AREA UPDATE ACCEPT message contains the Cell Notification information 
element, then the MS shall start to use the LLC NULL frame to perform cell updates. 

The network may also send a list of "equivalent PLMNs" in the ROUTING AREA UPDATE ACCEPT message. Each 
entry of the list contains a PLMN code (MCCh-MNC). The mobile station shall store the list, as provided by the 
network, except that any PLMN code that is already in the "forbidden PLMN" list shall be removed from the 
"equivalent PLMNs" list before it is stored by the mobile station. In addition the mobile station shall add to the stored 
list the PLMN code of the registered PLMN that sent the list. All PLMNs in the stored list shall be regarded as 
equivalent to each other for PLMN selection, cell selection/re-selection and handover. The stored list in the mobile 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 29 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

station shall be replaced on each occurrence of the ROUTING AREA UPDATE ACCEPT message. If no list is 
contained in the message, then the stored list in the mobile station shall be deleted. The list shall be stored in the mobile 
station while switched off so that it can be used for PLMN selection after switch on. 

A ROUTING AREA UPDATE COMPLETE message shall be returned to the network if the ROUTING AREA 
UPDATE ACCEPT message contained any of: 

- a P-TMSI; 

- Receive N-PDU Numbers (see 3GPP TS 44.065 [78] and 3GPP TS 25.322); or 

a request for the provision of the Inter RAT information container. 

If Receive N-PDU Numbers were included, the Receive N-PDU Numbers values valid in the MS, shall be included in 
the ROUTING AREA UPDATE COMPLETE message. 

If the network has requested the provision of the Inter RAT information container the MS shall return a ROUTING 
AREA UPDATE COMPLETE message including the Inter RAT information container IE to the network. 

NOTE 1 : In lu mode, after a routing area updating procedure, the mobile station can initiate Service Request 
procedure to request the resource reservation for the active PDP contexts if the resources have been 
released by the network or send upper layer message (e.g. ACTIVATE PDP CONTEXT REQUEST) to 
the network via the existing PS signaling connection. 

In lu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has 
indicated "follow-on request pending" in ROUTING AREA UPDATE REQUEST message) the network shall indicate 
the "follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message. If the network wishes to release the PS 
signalling connection, the network shall indicate "no follow-on proceed" in the ROUTING AREA UPDATE ACCEPT 

message. 

After that in lu mode, the mobile station shall act according to the follow-on proceed flag included in the Update result 
information element in the ROUTING AREA UPDATE ACCEPT message (see subclause 4.7.13). 

The network may also send a list of local emergency numbers in the ROUTING AREA UPDATE ACCEPT, by 
including the Emergency Number List IE. The mobile equipment shall store the list, as provided by the network, except 
that any emergency number that is already stored in the SIM/USIM shall be removed from the list before it is stored by 
the mobile equipment. If there are no emergency numbers stored on the SIM/USIM, then before storing the received list 
the mobile equipment shall remove from it any emergency number stored permanently in the ME for use in this case 
(see 3GPP TS 22.101 [8]). The list stored in the mobile equipment shall be replaced on each receipt of a new 
Emergency Number List IE. 

The emergency number(s) received in the Emergency Number List IE are valid only in networks with the same MCC as 
in the cell on which this IE is received. If no list is contained in the ROUTING AREA UPDATE ACCEPT message, 
then the stored list in the mobile equipment shall be kept, except if the mobile equipment has successfully registered to 
a PLMN with an MCC different from that of the last registered PLMN. 

The mobile equipment shall use the stored list of emergency numbers received from the network in addition to the 
emergency numbers stored on the SIM/USIM or ME to detect that the number dialled is an emergency number. 

NOTE 2: The mobile equipment may use the emergency numbers list to assist the end user in determining whether 
the dialled number is intended for an emergency service or for another destination, e.g. a local directory 
service. The possible interactions with the end user are implementation specific. 

The list of emergency numbers shall be deleted at switch off and removal of the SIM/USIM. The mobile equipment 
shall be able to store up to ten local emergency numbers received from the network. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 30 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.5.1 .4 Normal and periodic routing area updating procedure not accepted by the 

network 

If the routing area updating cannot be accepted, the network sends a ROUTING AREA UPDATE REJECT message to 
the MS. An MS that receives a ROUTING AREA UPDATE REJECT message, stops timer T3330, and for all causes 
except #12, #14 and #15 deletes the list of "equivalent PLMNs". If a ROUTING AREA UPDATE REJECT message is 
received, the MS shall stop any ongoing transmission of user data. 

The MS shall then take different actions depending on the received reject cause value: 

# 3 (Illegal MS); 

# 6 (Illegal ME); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and enter the state GMM-DEREGISTERED. Furthermore, it shall delete any P-TMSI, P- 
TMSI signature, RAI and GPRS ciphering key sequence number and shall consider the SIM/USIM as invalid for 
GPRS services until switching off or the SIM/USIM is removed. 

If the MS is IMSI attached, the MS shall in addition set the update status to U3 ROAMING NOT ALLOWED, 
shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A 
and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The 
SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the SIM/USIM is 
removed. 

# 7 (GPRS services not allowed); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2.9) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM 
is removed. The new state is GMM-DEREGISTERED. 

If the update type is "periodic updating" a GPRS MS operating in MS operation mode A or B in 
networkoperation mode I shall set the timer T3212 to its initial value and restart it, if it is not already running. 

# 9 (MS identity cannot be derived by the network); 

The MS shall set the GPRS update status to GU2 NOT UPDATED (and shall store it according to 
subclause 4.1.3.2), enter the state GMM-DEREGISTERED, and shall delete any P-TMSI, P-TMSI signature, 
RAI and GPRS ciphering key sequence number. Subsequently, the MS may automatically initiate the GPRS 
attach procedure. 

# 10 (Implicitly detached); 

The MS shall change to state GMM-DEREGISTERED.NORMAL-SERVICE. The MS shall then perform a new 
attach procedure. The MS should also activate PDP context(s) to replace any previously active PDP contexts. 
The MS should also perform the procedures needed in order to activate any previously active multicast 
service(s). 

NOTE: In some cases, user interaction may be required and then the MS cannot activate the PDP and MBMS 
context(s) automatically. 

# 1 1 (PLMN not allowed); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) 
and enter the state GMM-DEREGISTERED. 

The MS shall store the PLMN identity in the "forbidden PLMN list". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 31 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall 
delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt 
counter. The new MM state is MM IDLE. 

- The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 

# 12 (Location area not allowed); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2), 
shall reset the routing area updating attempt counter and shall change to state GMM- 
DEREGISTERED.LIMITED-SERVICE. 

The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall 
delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt 
counter. The new MM state is MM IDLE. 

- The MS shall perform a cell selection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304. 

#13 (Roaming not allowed in this location area); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
clause 4.1.3.2) shall reset the routing area updating attempt counter and shall change to state GMM- 
REGISTERED.LIMITED-SERVICE. 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall 
reset the location update attempt counter. The new MM state is MM IDLE. 

- The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 

# 14 (GPRS services not allowed in this PLMN); 

The MS shall delete any RAJ, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, 
shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall change to state GMM-DEREGISTERED. 

The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list. A GPRS MS operating 
in MS operation mode C shall perform a PLMN selection instead of a cell selection. 

If the update type is "periodic updating" a GPRS MS operating in MS operation mode A or B in network 
operation mode I shall set the timer T3212 to its initial value and restart it, if it is not already running. 

A GPRS MS operating in MS operation mode A or B in network operation mode II or III, is still IMSI attached 
for CS services in the network. 

As an implementation option, a GPRS MS operating in operation mode A or B may perform the following 
additional action. If no RR connection exists the MS may perform the action immediately. If the MS is operating 
in MS operation mode A and an RR connection exists, the MS may only perform the action when the RR 
connection is subsequently released: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 32 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- The MS may perform a PLMN selection according to 3GPP TS 23. 122 [14]. 

The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause 
is: 

On the "User Controlled PLMN Selector with Access Technology " or, 

On the "Operator Controlled PLMN Selector with Access Technology " list or, 

A PLMN identified as equivalent to any PLMN, with the same MCC, contained in the lists above. 

# 15 (No Suitable Cells In Location Area); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
clause 4.1.3.2) shall reset the routing area updating attempt counter and shall change to state GMM- 
REGISTERED.LIMITED-SERVICE. 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall 
reset the location update attempt counter. The new MM state is MM IDLE. 

The MS shall search for a suitable cell in another location area in the same PLMN according to 3GPP 
TS 43.022 [82] and 3GPP TS 25.304. 

Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in 
subclause 4.7.5.1.5. 

4.7.5.1 .5 Abnormal cases in the MS 

The following abnormal cases can be identified: 

a) Access barred because of common access class control or PS domain specific access control 

The routing area updating procedure shall not be started. The MS stays in the current serving cell and applies the 
normal cell reselection process. The procedure is started as soon as possible and if still necessary, i.e. when the 
barred state is removed or because of a cell change. 

b) Lower layer failure before the ROUTING AREA UPDATE ACCEPT or ROUTING AREA UPDATE REJECT 
message is received 

The procedure shall be aborted and the MS shall proceed as described below, except in the 
followingimplementat ion option cases b.l and b.2. 

b. 1) Release of PS signalling connection before the completion of the routing area updating procedure 

The routing area updating procedure shall be initiated again, if the following conditions apply: 

i) The original routing area update procedure was initiated over an existing PS signalling connection; and 

ii) The routing area update procedure was not due to timer T3330 expiry; and 

iii) No SECURITY MODE COMMAND message and no Non- Access Stratum (NAS) messages relating to 
the PS signalling connection were (e.g. PS authentication procedure, see subclause 4.7.7) received after the 
ROUTING AREA UPDATE REQUEST message was transmitted. 

b.2) RR release in lu mode (i.e. RRC connection release) with, for example, cause "Normal", or "User inactivity" 
or "Direct signalHng connection re-establishment" (see 3GPP TS 25.331 [32c] and 3GPP TS 44.118 [111]) 

The routing area updating procedure shall be initiated again, if the following conditions apply: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 33 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

i) The original routing area update procedure was initiated over an existing RRC connection; and 

ii) The routing area update procedure was not due to timer T3330 expiry; and 

iii) No SECURITY MODE COMMAND message and no Non- Access Stratum (NAS) messages relating to 
the PS signalling connection (e.g. PS authentication procedure, see subclause 4.7.7) were received after the 
ROUTING AREA UPDATE REQUEST message was transmitted. 

NOTE: The RRC connection release cause that triggers the re-initiation of the routing area update procedure is 
implementation specific. 

c) T3330 time-out 

The procedure is restarted four times, i.e. on the fifth expiry of timer T3330, the MS shall abort the procedure 
and, in lu mode, release the PS signalling connection (see 3GPP TS 25.331 [23c]). The MS shall proceed as 
described below. 

d) ROUTING AREA UPDATE REJECT, other causes than those treated in subclause 4.7.5.1.4 

Upon reception of the cause codes # 95, # 96, # 97, # 99 and #111 the MS should set the routing area updating 
attempt counter to 5. The MS shall proceed as described below. 

e) If a routing area border is crossed, when the MS is in state GMM-ROUTING-AREA-UPDATE-INITIATED, the 
routing area updating procedure shall be aborted and re-initiated immediately. The MS shall set the GPRS update 
status to GU2 NOT UPDATED. 

f) In A/Gb mode, if a cell change occurs within the same RA, when the MS is in state GMM -ROUTING- AREA- 
UPDATE-INITIATED, the cell update procedure is performed, before completion of the routing area updating 
procedure. 

g) Routing area updating and detach procedure collision 

GPRS detach containing detach type"re-attach required" or "re-attach not required": 

If the MS receives a DETACH REQUEST message before the routing area updating procedure has been 
completed, the routing area updating procedure shall be aborted and the GPRS detach procedure shall be 
progressed. 

GPRS detach containing detach type "IMSI detach": 

If the MS receives a DETACH REQUEST message before the routing area updating procedure has been 
completed, the routing area updating procedure shall be progressed, i.e. the DETACH REQUEST message 
shall be ignored. 

h) Routing area updating and P-TMSI reallocation procedure collision 

If the MS receives a P-TMSI REALLOCATION REQUEST message before the routing area updating procedure 
has been completed, the P-TMSI reallocation procedure shall be aborted and the routing area updating procedure 
shall be progressed. 

In cases b, c, d, e, and g with detach type "re-attach required" or "re-attach not required", the MS shall stop any ongoing 
transmission of user data. 

In cases b, c and d the MS shall proceed as follows: 

Timer T3330 shall be stopped if still running. The routing area updating attempt counter shall be incremented. 

If the routing area updating attempt counter is less than 5, and the stored RAI is equal to the RAI of the current 
serving cell and the GMM update status is equal to GUI UPDATED: 

- the MS shall keep the GMM update status to GUI UPDATED and changes state to GMM- 

REGISTERED.NORMAL-SERVICE. The MS shall start timer T331 1. When timer T331 1 expires the 
routing area updating procedure is triggered again. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 34 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the routing area updating attempt counter is less than 5, and the stored RAI is different to the RAI of the 
current serving cell or the GMM update status is different to GUI UPDATED: 

- the MS shall start timer T331 1, shall set the GPRS update status to GU2 NOT UPDATED and changes state 
toGMM-REGISTERED.ATTEMPTING-TO-UPDATE. 

If the routing area updating attempt counter is greater than or equal to 5: 

- the MS shall start timer T3302, shall delete the list of equivalent PLMNs, shall set the GPRS update status to 
GU2 NOT UPDATED and shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE or 
optionally to GMM-REGISTERED.PLMN-SEARCH(see subclause 4.2.5.1.8) in order to perform a PLMN 
selection according to 3GPP TS 23.122 [14]. 

4.7.5.1 .6 Abnormal cases on the network side 

The following abnormal cases can be identified: 

a) If a lower layer failure occurs before the message ROUTING AREA UPDATE COMPLETE has been received 
from the MS and a P-TMSI and/or PTMSI signature has been assigned, the network shall abort the procedure 
and shall consider both, the old and new P-TMSI and the corresponding P-TMSI signatures as valid until the old 
P-TMSI can be considered as invalid by the network (see subclause 4.7.1.5). During this period the network may 
use the identification procedure followed by a P-TMSI reallocation procedure if the old P-TMSI is used by the 
MS in a subsequent message. 

NOTE: Optionally, paging with IMSI may be used if paging with old and new P-TMSI fails. Paging with IMSI 
causes the MS to re-attach as described in subclause 4.7.9.1. 

b) Protocol error 

If the ROUTING AREA UPDATE REQUEST message has been received with a protocol error, the network 
shall return a ROUTING AREA UPDATE REJECT message with one of the following reject causes: 

#96: Mandatory information element error; 

#99: Information element non-existent or not implemented; 

#100: Conditional IE error; 

#111: Protocol error, unspecified. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



135 



ETSI TS 124 008 V7.14.0 (2009-03) 



c) T3350 time-out 

On the first expiry of the timer, the network shall retransmit the ROUTING AREA UPDATE ACCEPT message 
and shall reset and restart timer T3350. The retransmission is performed four times, i.e. on the fifth expiry of 
timer T3350, the routing area updating procedure is aborted. Both, the old and the new P-TMSI and the 
corresponding P-TMSI signatures shall be considered as valid until the old P-TMSI can be considered as invalid 
by the network(see subclause 4.7.1.5). During this period the network acts as described for case a above. 





MS 


Network 




Start T3330 




ROUTING AREA UPDATE REQUEST 




If P-TMSI or 
















TMSI allocated. 


Stop T3330 




ROUTING AREA UPDATE ACCEPT 




or Receive N-PDU 
Number needed 








If P-TMSI or 








Start T3350 


TMSI allocated. 




ROUTING AREA UPDATE COMPLETE 






or Receive N-PDU 






--► 


Stop T3350 






Number needed 














ROUTING AREA UPDATE REQUEST 






Start T3330 




















ROUTING AREA UPDATE REJECT 






Stop T3330 

















Figure 4.7.5/1 3GPP TS 24.008: Routing and combined routing area updating procedure 

d. 1) ROUTING AREA UPDATE REQUEST received after the ROUTING AREA UPDATE ACCEPT message 
has been sent and before the ROUTING AREA UPDATE COMPLETE message is received 

If one or more of the information elements in the ROUTING AREA UPDATE REQUEST message differ from 
the ones received within the previous ROUTING AREA UPDATE REQUEST message, the previously initiated 
routing area updating procedure shall be aborted if the ROUTING AREA UPDATE COMPLETE message has 
not been received and the new routing area updating procedure shall be progressed, or 

- If the information elements do not differ, then the ROUTING AREA UPDATE ACCEPT message shall be 
resent and the timer T3350 shall be restarted if an ROUTING AREA UPDATE COMPLETE message is 
expected. In that case, the retransmission counter related to T3350 is not incremented. 

d.2) More than one ROUTING AREA UPDATE REQUEST received and no ROUTING AREA UPDATE 
ACCEPT or ROUTING AREA UPDATE REJECT message has been sent 

If one or more of the information elements in the ROUTING AREA UPDATE REQUEST message differs from 
the ones received within the previous ROUTING AREA UPDATE REQUEST message, the previously initiated 
routing area updating procedure shall be aborted and the new routing area updating procedure shall be 
progressed; 

If the information elements do not differ, then the network shall continue with the previous routing area updating 
procedure and shall not treat any further this ROUTING AREA UPDATE REQUEST message. 



4.7.5.2 



Combined routing area updating procedure 



Within a combined routing area updating procedure the messages ROUTING AREA UPDATE ACCEPT and 
ROUTING AREA UPDATE COMPLETE carry information for the routing area updating and the location area 
updating. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 36 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.5.2.1 Combined routing area updating procedure initiation 

The combined routing area updating procedure is initiated only by a GPRS MS operating in MS operation modes A or 
B, if the MS is in state GMM-REGISTERED and MM-IDLE, and if the network operates in network operation mode I: 

when a GPRS MS that is IMSI attached for GPRS and non-GPRS services detects a change of the routing area in 
state GMM-REGISTERED and MM-IDLE; 

when a GPRS MS that is IMSI attached for GPRS services wants to perform an IMSI attach for non-GPRS 

services; 

after termination of a non-GPRS service via non-GPRS channels to update the association if the MS has changed 
the RA during that non-GPRS service transaction; 

after termination of a non-GPRS service via non-GPRS channels to update the association if GPRS services were 
suspended during the non-GPRS service but no resume is received. See 3GPP TS 23.060 subclause 16.2.1; 

after termination of a non-GPRS service via non-GPRS channels to update the association, if the GPRS MS in 
MS operation mode A performed a normal GPRS attach or a normal routing area updating procedure during the 
circuit-switched transaction; 

after a CM SERVICE REJECT message with cause value #4 is received by the mobile station (see 

subclause 4.5.1.1); in this case the update type IE shall be set to "Combined RA/LA updating with IMSI attach"; 

when a GPRS MS needs to update the network with the new MS Radio Access Capability IE; 

when a GPRS MS needs to update the network with a new DRX parameter IE; or 

in lu mode, to re-synchronize the PMM mode of MS and network after RRC connection release with cause 
"Directed signalUng connection re-establishment", see subclause 4.7.2.5. 

In A/Gb mode, the routing and location area identification are broadcast on the broadcast channel(s). A combined 
routing area updating procedure shall abort any ongoing GMM procedure. Aborted GMM procedures shall be repeated 
after the combined routing area updating procedure has been successfully performed. The ROUTING AREA UPDATE 
REQUEST message shall always be the first message sent from the MS in the new routing area after routing area 
change. 

In lu mode, the routing and location area identification are broadcast on the broadcast channel(s) or sent to the MS via 
the PS signalling connection. A combined routing area updating procedure shall abort any ongoing GMM procedure. 
Aborted GMM procedures may be repeated after the combined routing area updating procedure has been successfully 
performed. The ROUTING AREA UPDATE REQUEST message shall always be the first GMM message sent from the 
MS in the new routing area after routing area change. 

To initiate a combined routing area updating procedure the MS sends the message ROUTING AREA UPDATE 
REQUEST to the network, starts timer T3330 and changes to state GMM-ROUTING-UPDATING-INITIATED and 
MM LOCATION UPDATING PENDING. The value of the Update type IE in the message shall indicate "combined 
RA/LA updating" unless explicitly specified otherwise. If for the last attempt to update the registration of the location 
area a MM specific procedure was performed, the value of the Update type IE in the ROUTING AREA UPDATE 
REQUEST message shall indicate "combined RA/LA updating with IMSI attach". Furthermore the MS shall include 
the TMSI status IE if no valid TMSI is available. 

A GPRS MS in MS operation modes B that is in an ongoing circuit-switched transaction, shall initiate the combined 
routing area updating procedure after the circuit-switched transaction has been released, if the MS has changed the RA 
during the circuit-switched transaction and if the network operates in network operation mode I. 

A GPRS MS in MS operation mode A shall initiate the combined routing area updating procedure with IMSI attach 
after the circuit-switched transaction has been released, if a normal GPRS attach or a normal routing area updating 
procedure was performed during the circuit-switched transaction and provided that the network operates in network 
operation mode I. 

A GPRS MS in MS operation mode A shall perform the normal routing area update procedure during an ongoing 
circuit-switched transaction. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 37 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

In lu mode, if the MS wishes to prolong the established PS signalling connection after the normal routing area updating 
procedure (for example, the MS has any CM application request pending), it may set a follow-on request pending 
indicator on (see subclause 4.7.13). 

In lu mode, when a ROUTING AREA UPDATE REQUEST is received by the SGSN over a new PS signalling 
connection while there is an ongoing PS signalling connection (network is already in mode PMM-CONNECTED) for 
this UE, the network shall progress the routing area update procedure as normal and release the previous PS signalling 
connection when the routing area update procedure has been accepted by the network. 

NOTE: The re-establishment of the radio bearers of active PDP contexts is done as described in subclause 
"Service Request procedure". 

4.7.5.2.2 GMM Common procedure initiation 

The network may initiate GMM common procedures, e.g. the GMM authentication and ciphering procedure. 

4.7.5.2.3 Combined routing area updating procedure accepted by the network 

Depending on the value of the update result IE received in the ROUTING AREA UPDATE ACCEPT message, two 
different cases can be distinguished: 

Case 1) The update result IE value indicates "combined RA/LA": Routing and location area updating is 
successful; 

Case 2) The update result IE value indicates "RA only": Routing area updating is successful, but location area 
updating is not successful. 

A ROUTING AREA UPDATE COMPLETE message shall be returned to the network if the ROUTING AREA 
UPDATE ACCEPT message containsany of: 

- a P-TMSI and/or a TMSI; 

- Receive N-PDU Numbers (see 3GPP TS 44.065 [78] and 3GPP TS 25.322); or 

a request for the provision of the Inter RAT information container. 

If Receive N-PDU Numbers were included, the Receive N-PDU Numbers that are valid in the MS shall be included in 
the ROUTING AREA UPDATE COMPLETE message. 

If the network has requested the provision of the Inter RAT information container the MS shall return a ROUTING 
AREA UPDATE COMPLETE message including the Inter RAT information container IE to the network. 

In lu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has 
indicated "follow-on request pending" in ROUTING AREA UPDATE REQUEST message) the network shall indicate 
the "follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message. If the network wishes to release the PS 
signalling connection, the network shall indicate "no follow-on proceed" in the ROUTING AREA UPDATE ACCEPT 

message. 

After that in lu mode, the mobile station shall act according to the follow-on proceed flag included in the Update result 
information element in the ROUTING AREA UPDATE ACCEPT message (see subclause 4.7.13). 



4.7.5.2.3.1 Combined routing area updating successful 

The description for normal routing area update as specified in subclause 4.7.5.1.3 shall be followed. In addition, the 
following description for location area updating applies. 

The handling at the receipt of the ROUTING AREA UPDATE ACCEPT depends on the value received in the update 
result IE as specified below. 

The TMSI reallocation may be part of the combined routing area updating procedure. The TMSI allocated is then 
included in the ROUTING AREA UPDATE ACCEPT message together with the location area identification (LAI). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 38 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The network shall, in this case, change to state GMM-COMMON-PROCEDURE-INITIATED and shall start the timer 
T3350 as described in subclause 4.7.6. 

The MS, receiving a ROUTING AREA UPDATE ACCEPT message, stores the received location area identification, 
stops timer T3330, enters state MM IDLE, reset the location update attempt counter and sets the update status to Ul 
UPDATED. If the ROUTING AREA UPDATE ACCEPT message contains an IMSI, the mobile station is not allocated 
any TMSI, and shall delete any TMSI accordingly. If the ROUTING AREA UPDATE ACCEPT message contains a 
TMSI, the MS shall use this TMSI as new temporary identity. The MS shall delete its old TMSI and shall store the new 
TMSI. In this case, an ROUTING AREA UPDATE COMPLETE message is returned to the network. If neither a TMSI 
nor an IMSI has been included by the network in the ROUTING AREA UPDATE ACCEPT message, the old TMSI, if 
any is available, shall be kept. 

Any timer used for triggering the location updating procedure (e.g. T321 1, T3212) shall be stopped if running. 

The network receiving a ROUTING AREA UPDATE COMPLETE message stops timer T3350, changes to GMM- 
REGISTERED state and considers the new TMSI as valid. 

4.7.5.2.3.2 Combined routing area updating successful for GPRS services only 

The description for normal routing area update as specified in subclause 4.7.5.1.3 shall be followed. In addition, the 
following description for location area updating applies. 

The MS receiving the ROUTING AREA UPDATE ACCEPT message takes one of the following actions depending on 
the reject cause: 

#2 (IMSI unknown in HLR); 

The MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering 
key sequence number. The new MM state is MM IDLE. The SIM/USIM shall be considered as invalid for non-GPRS 
services until switching off or the SIM/USIM is removed. 

#16 (MSC temporarily not reachable); 

#17 (Network failure); or 

#22 (Congestion). 

The MS shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. Timer T3330 shall be 
stopped if still running. The routing area updating attempt counter shall be incremented. If the routing area 
updating attempt counter is less than 5, and the stored RAJ is equal to the RAJ of the current serving cell and the 
GMM update status is equal to GUI UPDATED: 

- the MS shall keep the GMM update status GUI UPDATED and changes state to GMM- 
REGISTERED.ATTEMPTING-TO-UPDATE-MM. The MS shall start timer T3311. When timer T331 1 
expires the combined routing area update procedure indicating "combined RA/LA updating with IMSI 
attach" is triggered again. 

If the routing area updating attempt counter is greater than or equal to 5: 

- the MS shall start timer T3302 and shall change to state GMM-REGISTERED.ATTEMPTING-TO- 
UPDATE-MM; 

a GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; 
a GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures. 
The MM sublayer shall act as in network operation mode II or III (depending whether a PCCCH is present) 
as long as the combined GMM procedures are not successful and no new RA is entered. The new MM state 
is MM IDLE. 

Other reject cause values and the case that no GMM cause IE was received are considered as abnormal cases. The 
combined routing area updating shall be considered as failed for GPRS and non-GPRS services. The specification of the 
MS behaviour in those cases is specified in subclause 4.7.5.2.5. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 39 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.5.2.4 Combined routing area updating not accepted by the network 

If the combined routing area updating cannot be accepted, the network sends a ROUTING AREA UPDATE REJECT 
message to the MS. An MS that receives a ROUTING AREA UPDATE REJECT message stops timer T3330, enters 
state MM IDLE, and for all causes except #12, #14 and #15 deletes the list of "equivalent PLMNs". If a ROUTING 
AREA UPDATE REJECT message is received, the MS shall stop any ongoing transmission of user data. 

The MS shall then take different actions depending on the received reject cause: 

# 3 (Illegal MS); 

# 6 (Illegal ME), or 

# 8 (GPRS services and non GPRS services not allowed); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED and the update status to U3 
ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and enter the state GMM- 
DEREGISTERED. Furthermore, it shall delete any P-TMSI, P-TMSI signature, TMSI, RAI, LAI, ciphering key 
sequence number and GPRS ciphering key sequence number and shall consider the SIM/USIM as invalid for 
GPRS and non GPRS services until switching off or the SIM/USIM is removed. 

# 7 (GPRS services not allowed); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAJ and GPRS ciphering key sequence 
number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM 
is removed. The new state is GMM-DEREGISTERED. If in the MS the timer T3212 is not already running, the 
timer shall be set to its initial value and restarted. 

A GPRS MS operating in MS operation mode A or B in network operation mode I, is still IMSI attached for CS 
services in the network, and shall then proceed with the appropriate MM specific procedure according to the 

MM service state. 

# 9 (MS identity cannot be derived by the network); 

The MS shall set the GPRS update status to GU2 NOT UPDATED (and shall store it according to 
subclause 4.1.3.2), enter the state GMM-DEREGISTERED, and shall delete any P-TMSI, P-TMSI signature, 
RAI and GPRS ciphering key sequence number. Subsequently, the MS may automatically initiate the GPRS 
attach procedure. 

A GPRS MS operating in MS operation mode A or B in network operation mode I, is still IMSI attached for CS 
services in the network. 

# 10 (Implicidy detached); 

A GPRS MS operating in MS operation mode A or B in network operation mode I, is IMSI detached for both 
GPRS and CS services in the network. 

The MS shall change to state GMM-DEREGISTERED.NORMAL-SERVICE. The MS shall then perform a new 
attach procedure. The MS should also activate PDP context(s) to replace any previously active PDP context(s). 
The MS should also perform the procedures needed in order to activate any previously active multicast 
service(s). 

NOTE: In some cases, user interaction may be required and then the MS cannot activate the PDP/MBMS 
context(s) automatically. 

# 1 1 (PLMN not allowed); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED and the update status to U3 
ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and enter the state GMM- 
DEREGISTERED. Furthermore, it shall delete any P-TMSI, P-TMSI signature, TMSI, RAI, LAI, ciphering key 
sequence number GPRS ciphering key sequence number, and reset the location update attempt counter. 

The MS shall store the PLMN identity in the "forbidden PLMN list". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 40 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The MS shall then perform a PLMN selection according to 3GPP TS 23.122 [14]. 

# 12 (Location area not allowed); 

The MS shall delete any RAJ, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2), 
shall reset the routing area updating attempt counter and shall change to state GMM- 
DEREGISTERED.LIMITED-SERVICE. 

The MS shall in addition set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI 
and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is 
MM IDLE. 

The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

The MS shall perform a cell selection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304. 

#13 (Roaming not allowed in this location area); 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
clause 4.1.3.2), shall reset the routing area updating attempt counter and shall change to state GMM- 
REGISTERED.LIMITED-SERVICE. 

The MS shall in addition set the update status to U3 ROAMING NOT ALLOWED and shall reset the location 
update attempt counter. The new MM state is MM IDLE. 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 

The MS shall indicate the Update type IE "combined RA/LA updating with IMSI attach" when performing the 
routing area updating procedure following the PLMN selection. 

# 14 (GPRS services not allowed in this PLMN); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, 
shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall change to state GMM-DEREGISTERED. If in the MS the timer T3212 is not 
already running, the timer shall be set to its initial value and restarted. 

The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list. 

A GPRS MS operating in MS operation mode A or B in network operation mode I, is still IMSI attached for CS 
services in the network and shall then proceed with the appropriate MM specific procedure according to the MM 
service state. 

As an implementation option, a GPRS MS operating in operation mode A or B may perform a PLMN selection 
according to 3GPP TS 23.122 [14]. 

The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause 
is: 

On the "User Controlled PLMN Selector with Access Technology " or. 

On the "Operator Controlled PLMN Selector with Access Technology " list or, 

A PLMN identified as equivalent to any PLMN, with the same MCC, contained in the lists above. 



# 15 (No Suitable Cells In Location Area); 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 41 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
clause 4.1.3.2), shall reset the routing area updating attempt counter and shall change to state GMM- 
REGISTERED.LIMITED-SERVICE. 

The MS shall in addition set the update status to U3 ROAMING NOT ALLOWED and shall reset the location 
update attempt counter. The new MM state is MM IDLE. 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

The MS shall search for a suitable cell in another location area in the same PLMN according to 3GPP TS 43.022 
[82] and 3GPP TS 25.304. 

The MS shall indicate the Update type IE "combined RA/LA updating with IMSI attach" when performing the 
routing area updating procedure. 

Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in 
subclause 4.7.5.2.5. 

4.7.5.2.5 Abnormal cases in the MS 

The MS shall proceed as follows: 

If the combined routing area update was successful for GPRS services only and the ROUTING AREA UPDATE 
ACCEPT message contained a cause value not treated in subclause 4.7.5.2.3.2 or the GMM Cause IE is not 
included in the message, the MS shall follow the procedure specified in subclause 4.7.5.1.5 step d) with the 
following modification; 

otherwise, the abnormal cases specified in subclause 4.7.5.1.5 apply with the following modification. 

If the GPRS routing area updating attempt counter is incremented according to subclause 4.7.5.1.5 the next actions 
depend on the Location Area Identities (stored on SIM/USIM and the one of the current serving cell) and the value of 
the routing area updating attempt counter. 

if the update status is Ul UPDATED, and the stored LAI is equal to the one of the current serving cell and the 
routing area updating attempt counter is smaller than 5, then the mobile station shall keep the update status to Ul 
UPDATED, the new MM state is MM IDLE substate NORMAL SERVICE; 

if the routing area updating attempt counter is smaller than 5 and, additionally, the update status is different from 
Ul UPDATED or the stored LAI is different from the one of the current serving cell, the mobile station shall 
delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM and list of equivalent PLMNs 
and set the update status to U2 NOT UPDATED. The MM state remains MM LOCATION UPDATING 
PENDING; or 

if the routing area updating attempt counter is greater or equal to 5, the mobile station shall delete any LAI, 
TMSI, ciphering key sequence number stored in the SIM/USIM and list of equivalent PLMNs and set the update 
status to U2 NOT UPDATED. 

A GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a 
GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures. 
The MM sublayer shall act as in network operation mode II or III (depending whether a PCCCH is present) as 
long as the combined GMM procedures are not successful and no new RA is entered. The new MM state is MM 
IDLE substate ATTEMPTING TO UPDATE or optionally MM IDLE substate PLMN SEARCH in order to 
perform a PLMN selection according to 3GPP TS 23.122 [14]. 

4.7.5.2.6 Abnormal cases on the network side 

The abnormal cases specified in subclause 4.7.5.1.6 apply with the exceptions for cases a and c in which in addition to 
the P-TMSI and P-TMSI signature the old TMSI shall be considered occupied until the new TMSI is used by the MS in 
a subsequent message. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 42 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 



4.7.6 P-TMSI reallocation procedure 



A temporary mobile station identity for GPRS services, the Packet-TMSI (P-TMSI), is used for identification within the 
radio interface signalling procedures. The structure of the P-TMSI is specified in 3GPP TS 23.003 [10]. The P-TMSI 
has significance only within a routing area. Outside the routing area it has to be combined with the routing area 
identification (RAI) to provide for an unambiguous identity. 

The purpose of the P-TMSI reallocation procedure is to provide identity confidentiality, i.e. to protect a user against 
being identified and located by an intruder (see 3GPP TS 42.009 [5] and 43.020 [13]). 

Usually, P-TMSI reallocation is performed at least at each change of a routing area. (Such choices are left to the 
network operator). 

The reallocation of a P-TMSI is performed by the unique procedure defined in this subclause. This procedure can only 
be initiated by the network in state GMM -REGISTERED. 

P-TMSI can also be implicitly reallocated in the attach or routing area updating procedures. The implicit reallocation of 
a P-TMSI is described in the corresponding subclause s. 

NOTE: Normally, the P-TMSI reallocation will take place in conjunction with another GMM procedure, e.g. at 
routing area updating (see 3GPP TS 29.002 [37]). 

4.7.6.1 P-TMSI reallocation initiation by the network 

The network initiates the P-TMSI reallocation procedure by sending a P-TMSI REALLOCATION COMMAND 

message to the MS and starts the timer T3350. 

The P-TMSI REALLOCATION COMMAND message contains a new combination of P-TMSI, RAI and optionally a 
P-TMSI signature allocated by the network. 

The network may suspend the transmission of user data during the P-TMSI reallocation procedure. 

4.7.6.2 P-TMSI reallocation completion by the MS 

Upon receipt of the P-TMSI REALLOCATION COMMAND message, the MS stores the Routing Area Identifier 
(RAI) and the P-TMSI and sends a P-TMSI REALLOCATION COMPLETE message to the network. 

If a P-TMSI signature is present in the P-TMSI REALLOCATION COMMAND message, the MS shall store the new 
P-TMSI signature and shall if available delete the old P-TMSI signature. If no P-TMSI signature is present in the P- 
TMSI REALLOCATION COMMAND message, the old P-TMSI signature, if available, shall be kept. 

4.7.6.3 P-TMSI reallocation completion by the network 

Upon receipt of the P-TMSI REALLOCATION COMPLETE message, the network stops the timer T3350 and 
considers both the old and the new P-TMSI and the corresponding P-TMSI signatures as valid until the old P-TMSI can 
be considered as invalid by the network (see subclause 4.7.1.5). 

In A/Gb mode, the GMM layer shall notify the LLC layer that the P-TMSI has been changed (see 3GPP TS 44.064 

[78a]). 

4.7.6.4 Abnormal cases on the network side 

The following abnormal cases can be identified: 

a) Lower layer failure 

If a lower layer failure is detected before the P-TMSI REALLOCATION COMPLETE message is received, the 
old and the new P-TMSI shall be considered as occupied until the old P-TMSI can be considered as invalid by 
the network (see subclause 4.7.1.5). 

During this period the network: 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



143 



ETSI TS 124 008 V7.14.0 (2009-03) 



may first use the old P-TMSI for paging for an implementation dependent number of paging attempts in the 
case of network originated transactions. Upon response from the MS, the network may re-initiate the P-TMSI 
reallocation. If no response is received to the paging attempts, the network may use the new P-TMSI for 
paging for an implementation dependent number of paging attempts. Upon response from the MS the 
network shall consider the new P-TMSI as valid and the old P-TMSI as invalid. If no response is received to 
the paging attempts, the network may use the IMSI for paging, for an implementation dependent number of 
paging attempts; 

NOTE: Paging with IMSI causes the MS to re-attach as described in subclause 4.7.9. 1. 

shall consider the new P-TMSI as valid if it is used by the MS (see subclause 4.7. 1 .5); or 

may use the identification procedure followed by a new P-TMSI reallocation if the MS uses the old P-TMSI. 

b) Expiry of timer T3350 

The P-TMSI reallocation procedure is supervised by the timer T3350. The network shall, on the first expiry of 
timer T3350, reset and restart timer T3350 and shall retransmit the P-TMSI REALLOCATION COMMAND. 
This retransmission is repeated four times, i.e. on the fifth expiry of timer T3350, the network shall abort the 
reallocation procedure and shall follow the rules for case a as described above. 

c) P-TMSI reallocation and GPRS attach procedure collision 

If the network receives an ATTACH REQUEST message before the ongoing P-TMSI reallocation procedure has 
been completed the network shall proceed with the GPRS attach procedure after deletion of the GMM context. 

d) P-TMSI reallocation and an MS initiated GPRS detach procedure collision 

If the network receives a DETACH REQUEST message before the ongoing P-TMSI reallocation procedure has 
been completed, the network shall abort the P-TMSI reallocation procedure and shall progress the GPRS detach 
procedure. 

e) P-TMSI reallocation and a routing area updating procedure collision 

If the network receives a ROUTING AREA UPDATE REQUEST message before the ongoing P-TMSI 
reallocation procedure has been completed, the network shall abort the P-TMSI reallocation procedure and shall 
progress the routing area updating procedure. The network may then perform a new P-TMSI reallocation. 

f) P-TMSI reallocation and a service request procedure collision 

If the network receives a SERVICE REQUEST message before the ongoing P-TMSI reallocation procedure 
procedure has been completed, the network shall progress both procedures. 

If there are different new P-TMSI included in subsequent P-TMSI REALLOCATION COMMAND messages, due to 
an aborted or repeated P-TMSI reallocation procedure, the MS always regards the newest and its existing P-TMSI as 
valid for the recovery time. 



MS Network 

P-TMSI REALLOCATION COMMAND 



P-TMSI REALLOCATION COMPLETE 



Start T3350 
Stop T3350 



Figure 4.7.6/1 3GPP TS 24.008: P-TMSI reallocation procedure 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 44 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.7 Authentication and cipinering procedure 

4.7.7a Authentication and ciphering procedure used for UMTS authentication 

challenge. 

The purpose of the authentication and ciphering procedure is fourfold (see 3GPP TS 33.102 [5a]): 

to permit the network to check whether the identity provided by the MS is acceptable or not; 

to provide parameters enabling the MS to calculate a new GPRS UMTS ciphering key and a new GPRS UMTS 
integrity key; 

to let the network set the GSM ciphering mode (ciphering /no ciphering) and GSM ciphering algorithm; and 

to permit the mobile station to authenticate the network. 

In lu mode, and in the case of a UMTS authentication challenge, the authentication and ciphering procedure can be used 
for authentication only. 

The cases in which the authentication and ciphering procedure shall be used are defined in 3GPP TS 33.102 [5a] and 
3GPPTS 42.009 [5]. 

The authentication and ciphering procedure is always initiated and controlled by the network. However, in the case of a 
UMTS authentication challenge, there is the possibility for the MS to reject the network. 

The MS shall support the UMTS authentication challenge, if a USIM is inserted. 

The authentication and ciphering procedure can be used for either: 
authentication only; 

setting of the GSM ciphering mode and the GSM ciphering algorithm only; or 
authentication and the setting of the GSM ciphering mode and the GSM ciphering algorithm. 

In A/Gb mode, the network should not send any user data during the authentication and ciphering procedure. 

A UMTS security context is established in the MS and the network when a UMTS authentication challenge is 
performed in A/Gb mode or in lu mode. After a successful UMTS authentication, the GPRS UMTS ciphering key, the 
GPRS UMTS integrity key, the GPRS GSM ciphering key and the GPRS ciphering key sequence number, are stored 
both in the network and the MS. 

4.7.7b Authentication and ciphering procedure used for GSM authentication 

challenge 

The purpose of the authentication and ciphering procedure is threefold (see 3GPP TS 43.020 [13]): 
to permit the network to check whether the identity provided by the MS is acceptable or not; 
- to provide parameters enabling the MS to calculate a new GPRS GSM ciphering key; and 

to let the network set the GSM ciphering mode (ciphering/no ciphering) and GSM ciphering algorithm. 

The authentication and ciphering procedure can be used for either: 
authentication only; 

setting of the GSM ciphering mode and the GSM ciphering algorithm only; or 
authentication and the setting of the GSM ciphering mode and the GSM ciphering algorithm. 

The cases in which the authentication and ciphering procedure shall be used are defined in 3GPP TS 42.009 [5]. 

In A/Gb mode, the authentication and ciphering procedure is always initiated and controlled by the network. It shall be 
performed in a non ciphered mode because of the following reasons: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 45 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- the network cannot decipher a ciphered AUTHENTICATION_AND_CIPHERING RESPONSE from an 
unauthorised MS and put it on the black hst; and 

to be able to define a specific point in time from which on a new GPRS GSM ciphering key should be used 
instead of the old one. 

GSM authentication challenge shall be supported by a ME supporting GERAN or UTRAN. 

In A/Gb mode, the network should not send any user data during the authentication and ciphering procedure. 

A GSM security context is established in the MS and the network when a GSM authentication challenge is performed in 
A/Gb mode or in lu mode. However, in lu mode the MS shall not accept a GSM authentication challenge, if a USIM is 
inserted. After a successful GSM authentication challenge, the GPRS GSM ciphering key and the GPRS ciphering key 
sequence number, are stored both in the network and the MS. 

4.7.7c Change of the ciphering algorithm at PS Handover 

For PS handover to A/Gb mode (see subclause 10.5.1.14 and 3GPP TS 44.060 [76]) the network shall either assign a 
GSM ciphering algorithm to be used in the target cell or deactivate ciphering in the target cell. The MS shall start to use 
the new GSM ciphering algorithm or deactivate ciphering upon an indication from the lower layers that the PS 
handover procedure has been successfully completed (see 3GPP TS 44.060 [76]) 

After PS handover to lu mode (see 3GPP TS 25.331 [23c] and 3GPP TS 44.118 [1 11]) the network shall activate 
integrity protection and shall either assign a ciphering algorithm to be used in the target cell or deactivate ciphering in 
the target cell, using the security mode control procedure (3GPP TS 25.331 [23c] and 3GPP TS 44.1 18 [111]). 

If the GSM ciphering algorithm is changed at PS handover and the routing area updating procedure triggered by the PS 
handover procedure is not accepted by the network, the MS shall delete any GPRS ciphering key sequence number and 
proceed as specified in subclauses 4.7.5.1.4 and 4.7.5.2.4. If the routing area updating procedure fails, because the radio 
resources assigned in the new cell are released before the MS receives a ROUTING AREA UPDATE ACCEPT 
message, the MS shall delete any GPRS ciphering key sequence number and proceed as specified in subclauses 
4.7.5.1.5 itemb and 4.7.5.2.5, respectively. 

4.7.7.1 Authentication and ciphering initiation by the network 

The network initiates the authentication and ciphering procedure by transferring an 

AUTHENTICATION_AND_CIPHERING REQUEST message across the radio interface and starts timer T3360. The 
AUTHENTICATION_AND_CIPHERING REQUEST message shall contain all parameters necessary to calculate the 
response parameters when authentication is performed (see 3GPP TS 43.020 [13] and 3GPP TS 33.102 [5a]). 

If authentication is requested, then the AUTHENTICATION. AND_CIPHERING REQUEST message shall contain 
either: 

In a GSM authentication challenge, the GPRS ciphering key sequence number, allocated to the GPRS GSM 
ciphering key and the RAND, or 

In a UMTS authentication challenge, the GPRS ciphering key sequence number, allocated to the GPRS UMTS 
ciphering and GPRS UMTS integrity keys, the RAND and the AUTN. 

In A/Gb mode, if authentication is not requested, then the AUTHENTICATION_AND_CIPHERING REQUEST 
message shall not contain neither the GPRS ciphering key sequence number, the RAND nor the AUTN. 

In A/Gb mode, if ciphering is requested, in a GSM authentication challenge or in a UMTS authentication challenge, 
then the AUTHENTICATION_AND_CIPHERING REQUEST message shall indicate the GPRS GSM ciphering 
algorithm. 

The network includes the A&C reference number information element in the 

AUTHENTICATION_AND_CIPHERING REQUEST message. Its value is chosen in order to link an 
AUTHENTICATION_AND_CIPHERING REQUEST in a RA with its RESPONSE. The A&C reference number value 
might be based on the RA Colour Code value. 

Additionally, the network may request the MS to include its IMEISV in the AUTHENTICATION_AND_CIPHERING 
RESPONSE message. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 46 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.7.2 Authentication and ciphering response by the MS 

In A/Gb mode, a MS that is attached to GPRS shall be ready to respond upon an 
AUTHENTICATION_AND_CIPHERING REQUEST message at any time. 

In UMTS, an MS that is attached to GPRS shall be ready to respond upon an 
AUTHENTICATION_AND_CIPHERING REQUEST message at any time whilst a PS signalUng connection exists. 

If a SIM is inserted in the MS, the MS shall ignore the Authentication Parameter AUTN IE if included in the 
AUTHENTICATION_AND_CIPHERING REQUEST message and perform the GSM authentication challenge. It shall 
not perform the authentication of the network described in 4.7.7.5.1. 

In a GSM authentication challenge, if the AUTHENTICATION_AND_CIPHERING REQUEST message includes the 
authentication parameters RAND and GPRS CKSN, then upon receipt of the message, the MS processes the challenge 
information and sends an AUTHENTICATION_AND_CIPHERING RESPONSE message to the network. The value of 
the received A&C reference number information element shall be copied into the A&C reference number information 
element in the AUTHENTICATION_AND_CIPHERING RESPONSE message. A GSM authentication challenge will 
result in the SIM/USIM passing a SRES and a GPRS GSM ciphering key to the ME. The new GPRS GSM ciphering 
key calculated from the challenge information shall overwrite the previous one and any previously stored GPRS UMTS 
ciphering and GPRS UMTS integrity keys shall be deleted. The calculated GSM ciphering key shall be stored on the 
SIM/USIM together with the GPRS ciphering key sequence number before the 
AUTHENTICATION_AND_CIPHERING RESPONSE message is transmitted. 

In a UMTS authentication challenge, if the AUTHENTICATION_AND_CIPHERING REQUEST message includes the 
UMTS authentication parameters GPRS CKSN, RAND and AUTN, then upon receipt of the message, the MS verifies 
the AUTN parameter and if this is accepted, the MS processes the challenge information and sends an 
AUTHENTICATION_AND_CIPHERING RESPONSE message to the network. The value of the received A&C 
reference number information element shall be copied into the A&C reference number information element in the 
AUTHENTICATION_AND_CIPHERING RESPONSE message. A UMTS authentication challenge will result in the 
USIM passing a RES, a GPRS UMTS ciphering key, a GPRS UMTS integrity key and a GPRS GSM ciphering key to 
the ME. The new GPRS UMTS ciphering key, GPRS UMTS integrity key and GPRS GSM ciphering key calculated 
from the challenge information shall overwrite the previous ones. The new GPRS UMTS ciphering key, GPRS UMTS 
integrity key and GPRS GSM ciphering key shall be stored on the USIM together with the GPRS ciphering key 
sequence number before the AUTHENTICATION_AND_CIPHERING RESPONSE message is transmitted. 

In lu mode, an MS capable of UMTS only shall ignore the Ciphering Algorithm IE in the 

AUTHENTICATION_AND_CIPHERING REQUEST message. An MS capable of both lu mode and A/Gb mode shall 
store the received value in the Ciphering Algorithm IE in the AUTHENTICATION_AND_CIPHERING REQUEST 
message in order to use it at an inter system change from lu mode to A/Gb mode. 

If the AUTHENTICATION_AND_CIPHERING REQUEST message does not include neither the GSM authentication 
parameters (RAND and GPRS CKSN) nor the UMTS authentication parameters (RAND, AUTN and GPRS CKSN), 
then upon receipt of the message, the MS replies by sending an AUTHENTICATION_AND_CIPHERING RESPONSE 
message to the network. 

In A/Gb mode, the GMM layer shall notify the LLC layer if ciphering shall be used or not and if yes which GSM 
ciphering algorithm and GPRS GSM ciphering key that shall be used (see 3GPP TS 44.064 [78a]). 

A ME supporting UMTS authentication challenge shall support the following procedure: 

In order to avoid a synchronisation failure, when the mobile station receives an 

AUTHENTICATION_AND_CIPHERING REQUEST message, the mobile station shall store the received RAND 
together with the RES returned from the USIM in the volatile memory and associate it with the PS domain. When the 
MS receives a subsequent AUTHENTICATION_AND_CIPHERING REQUEST message, if the stored RAND value 
for the PS domain is equal to the new received value in the AUTHENTICATION_AND_CIPHERING REQUEST 
message, then the mobile station shall not pass the RAND to the USIM, but shall immediately send the 
AUTHENTICATION_AND_CIPHERING RESPONSE message with the stored RES for the PS domain. If, for the PS 
domain, there is no valid stored RAND in the mobile station or the stored RAND is different from the new received 
value in the AUTHENTICATION_AND_CIPHERING REQUEST message, the mobile station shall pass the RAND to 
the USIM, shall override any previously stored RAND and RES with the new ones and start, or reset and restart timer 
T3316. 

The RAND and RES values stored in the mobile station shall be deleted and timer T3316, if running, shall be stopped; 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 47 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- upon receipt of a SECURITY MODE COMMAND (lu mode only), 
SERVICE_ACCEPT (lu mode only), 
SERVICE_REJECT (lu mode only), 
ROUTING_AREA_UPDATE_ACCEPT 

or AUTHENTICATION_AND_CIPHERING REJECT message; 

upon expiry of timer T33 16; or 

- if the mobile station enters the GMM states GMM-DEREGISTERED or GMM-NULL. 

4.7.7.3 Authentication and ciphering completion by the network 

Upon receipt of the AUTHENTICATION AND CIPHERING RESPONSE message, the network stops the timer T3360 
and checks the validity of the response (see 3GPP TS 43.020 [13] and 3GPP TS 33.102 [5a]). For this, it may use the 
A&C reference number information element within the AUTHENTICATION AND CIPHERING RESPONSE message 
to determine whether the response is correlating to the last request that was sent. 

In A/Gb mode, the GMM layer shall notify the LLC sublayer if ciphering shall be used or not and if yes which 
algorithm and GPRS GSM ciphering key that shall be used (see 3GPP TS 44.064 [78a]). 

Upon receipt of the AUTHENTICATION AND CIPHERING FAILURE message, the network stops the timer T3360. 
In Synch failure case, the core network may renegotiate with the HLR/AuC and provide the MS with new 
authentication parameters. 

4.7.7.4 GPRS ciphering key sequence number 

The security parameters for authentication and ciphering are tied together in sets. In a GSM authentication challenge, 
from a challenge parameter RAND both the authentication response parameter SRES and the GPRS GSM ciphering key 
can be computed given the secret key associated to the IMSI. In a UMTS authentication challenge, from a challenge 
parameter RAND, the authentication response parameter RES and the GPRS UMTS ciphering key and the GPRS 
UMTS integrity key can be computed given the secret key associated to the IMSI. 

In order to allow start of ciphering on a logical link without authentication, GPRS ciphering key sequence numbers are 
introduced. 

The GPRS ciphering key sequence number is managed by the network such that the AUTHENTICATION 
AND CIPHERING REQUEST message contains the GPRS ciphering key sequence number allocated to the GPRS 
GSM ciphering key (in case of a GSM authentication challenge) or the GPRS UMTS ciphering key and the GPRS 
UMTS integrity key (in case of a UMTS authentication challenge) which may be computed from the RAND parameter 
carried in that message. 

If an authentication and ciphering procedure has been completed successfully and a GPRS ciphering key sequence 
number is stored in the network, the network shall include a different GPRS ciphering key sequence number in the 
AUTHENTICATION AND CIPHERING REQUEST message when it intiates a new authentication and ciphering 
procedure. 

The MS stores the GPRS ciphering key sequence number with the GPRS GSM ciphering key (in case of a GSM 
authentication challenge) and the GPRS UMTS ciphering key and the GPRS UMTS integrity key (in case of a UMTS 
authentication challenge), and includes the corresponding GPRS ciphering key sequence number in the ROUTING 
AREA UPDATE REQUEST, SERVICE REQUEST and ATTACH REQUEST messages. 

If the GPRS ciphering key sequence number is deleted, the associated GPRS GSM ciphering key, GPRS UMTS 
ciphering key and GPRS UMTS integrity key shall be deleted (i.e. the established GSM security context or the UMTS 
security context is no longer valid). 

In lu mode, the network may choose to start ciphering and integrity checking with the stored GPRS UMTS ciphering 
key and the stored GPRS UMTS integrity key (under the restrictions given in 3GPP TS 42.009 [5] and 3GPP TS 33.102 
[5a]) if the stored GPRS ciphering key sequence number and the one given from the MS are equal. 

In A/Gb mode, the network may choose to start ciphering with the stored GPRS GSM ciphering key (under the 
restrictions given in 3GPP TS 42.009 [5]) if the stored GPRS ciphering key sequence number and the one given from 
the MS are equal and the previously negotiated ciphering algorithm is known and supported in the network. When 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 48 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

ciphering is requested at GPRS attach, the authentication and ciphering procedure shall be performed since the MS does 
not store the ciphering algorithm at detach. 

Upon GPRS attach, if ciphering is to be used, an AUTHENTICATION AND CIPHERING REQUEST message shall 
be sent to the MS to start ciphering. 

If the GPRS ciphering key sequence number stored in the network does not match the GPRS ciphering key sequence 
number received from the MS in the ATTACH REQUEST message, then the network should authenticate the MS. 

In A/Gb mode, the MS starts ciphering after sending the AUTHENTICATION AND CIPHERING RESPONSE 
message. The network starts ciphering when a valid AUTHENTICATION AND CIPHERING RESPONSE is received 
from the MS. 

In lu mode, the MS starts ciphering and integrity checking according to the conditions specified in specification 3GPP 
TS 25.331 [23c]. 

In A/Gb mode, as an option, the network may decide to continue ciphering without sending an AUTHENTICATION 
AND CIPHERING REQUEST message after receiving a ROUTING AREA UPDATE REQUEST message with a valid 
GPRS ciphering key sequence number. Both the MS and the network shall use the latest ciphering parameters. The 
network starts ciphering when sending the ciphered ROUTING AREA UPDATE ACCEPT message to the MS. The MS 
starts ciphering after receiving a valid ciphered ROUTING AREA UPDATE ACCEPT message from the network. 

NOTE: In some specifications the term KSI (Key Set Identifier) is used instead of the term GPRS ciphering key 
sequence number. 

4.7.7.5 Authentication not accepted by the network 

If authentication and ciphering fails, i.e. if the response is not valid, the network considers whether the MS has used the 
P-TMSI or the IMSI for identification. 

If the P-TMSI has been used, the network may decide to initiate the identification procedure. If the IMSI given 
by the MS differs from the one the network had associated with the P-TMSI, the authentication should be 
restarted with the correct parameters. If the IMSI provided by the MS is the expected one (i.e. authentication has 
really failed), the network should proceed as described below. 

If the IMSI has been used, or the network decides not to try the identification procedure, an 
AUTHENTICATION AND CIPHERING REJECT message should be transferred to the MS. 

Upon receipt of an AUTHENTICATION AND CIPHERING REJECT message, the MS shall set the GPRS update 
status to GU3 ROAMING NOT ALLOWED and shall delete the P-TMSI, P-TMSI signature, RAI and GPRS 
ciphering key sequence number stored. If available, also the TMSI, LAI and ciphering key sequence number shall be 
deleted and the update status shall be set to U3 ROAMING NOT ALLOWED. The SIM/USIM shall be considered 
as invalid until switching off or the SIM/USIM is removed. 

If the AUTHENTICATION AND CIPHERING REJECT message is received, the MS shall abort any GMM 
procedure, shall stop the timers T3310, T3317 and T3330 (if running) and shall enter state GMM- 
DEREGISTERED. 

4.7.7.5.1 Authentication not accepted by the MS 

In a UMTS authentication challenge, the authentication procedure is extended to allow the MS to check the authenticity 
of the core network. Thus allowing, for instance, detection of false base station. 

Following a UMTS authentication challenge, the MS may reject the core network, on the grounds of an incorrect 
AUTN parameter (see 3GPP TS 33.102 [5a]). This parameter contains two possible causes for authentication failure: 

a) MAC code failure 

If the MS considers the MAC code (supplied by the core network in the AUTN parameter) to be invalid, it shall send a 
AUTHENTICATION AND CIPHERING FAILURE message to the network, with the GMM cause 'MAC failure'. The 
MS shall then follow the procedure described in subclause 4.7.7.6 (f). 

b) SQN failure 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 49 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the MS considers the SQN (supplied by the core network in the AUTN parameter) to be out of range, it shall 
send a AUTHENTICATION AND CIPHERING FAILURE message to the network, with the GMM cause 
'Synch failure' and the re-synchronization token AUTS provided by the USIM (see 3GPP TS 33.102 [5a]). 
The MS shall then follow the procedure described in subclause 4.7.7.6 (g). 

In lu mode, an MS with a USIM inserted shall reject the authentication challenge if no Authentication Parameter AUTN 
IE was present in the AUTHENTICATION REQUEST message (i.e. a GSM authentication challenge has been received 
when the MS expects a UMTS authentication challenge). In such a case, the MS shall send the AUTHENTICATION 
AND CIPHERING FAILURE message to the network, with the GMM cause "GSM authentication unacceptable". The 
MS shall then follow the procedure described in subclause 4.7.7.6 (f). 

If the MS returns an AUTHENTICATION_AND_CIPHERING_FAILURE message to the network, the MS shall 
delete any previously stored RAND and RES and shall stop timer T3316, if running. 

4.7.7.6 Abnormal cases 

The following abnormal cases can be identified: 

a) Lower layer failure 

Upon detection of a lower layer failure before the AUTHENTICATION AND CIPHERING RESPONSE is 
received, the network shall abort the procedure. 

b) Expiry of timer T3360 

The network shall, on the first expiry of the timer T3360, retransmit the AUTHENTICATION AND 
CIPHERING REQUEST and shall reset and start timer T3360. This retransmission is repeated four times, i.e. on 
the fifth expiry of timer T3360, the procedure shall be aborted. 

c) Collision of an authentication and ciphering procedure with a GPRS attach procedure 

If the network receives an ATTACH REQUEST message before the ongoing authentication procedure has been 
completed and no GPRS attach procedure is pending on the network (i.e. no ATTACH ACCEPT/REJECT 
message has to be sent as an answer to an ATTACH REQUEST message), the network shall abort the 
authentication and ciphering procedure and proceed with the new GPRS attach procedure. 

d) Collision of an authentication and ciphering procedure with a GPRS attach procedure when the authentication 
and ciphering procedure has been caused by a previous GPRS attach procedure 

If the network receives an ATTACH REQUEST message before the ongoing authentication procedure has been 
completed and a GPRS attach procedure is pending (i.e. an ATTACH ACCEPT/REJECT message has still to be 
sent as an answer to an earlier ATTACH REQUEST message), then: 

If one or more of the information elements in the ATTACH REQUEST message differs from the ones 
received within the previous ATTACH REQUEST message, the network shall not treat the authentication 
any further and proceed with the GPRS attach procedure; or 

If the information elements do not differ, then the network shall not treat any further this new ATTACH 
REQUEST. 

Collision of an authentication and ciphering procedure with a GPRS detach procedure 

GPRS detach containing cause "power off: 

If the network receives a DETACH REQUEST message before the ongoing authentication and ciphering 
procedure has been completed, the network shall abort the authentication and ciphering procedure and shall 
progress the GPRS detach procedure. 

GPRS detach containing other causes than "power off": 

If the network receives a DETACH REQUEST message before the ongoing authentication and ciphering 
procedure has been completed, the network shall complete the authentication and ciphering procedure and 
shall respond to the GPRS detach procedure as described in subclause 4.7.4. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



150 



ETSI TS 124 008 V7.14.0 (2009-03) 



e) Collision of an authentication and ciphering procedure with a routing area updating procedure 

If the network receives a ROUTING AREA UPDATE REQUEST message before the ongoing authentication 
procedure has been completed, the network shall progress both procedures. 



MS Network 

AUTHENTICATION AND CIPHERING REQUEST 

< Start T3360 



AUTHENTICATION AND CIPHERING RESPONSE 



Stop T3360 



AUTHENTICATION AND CIPHERING REJECT 



Figure 4.7.7/1 3GPP TS 24.008: Authentication and ciphiering procedure 

(f) Authentication failure (GMM cause "MAC failure" or "GSM authentication unacceptable") 

The MS shall send an AUTHENTICATION & CIPHERING FAILURE message, with GMM cause "MAC 
failure" or "GSM authentication unacceptable" according to subclause 4.7.7.5.1, to the network and start timer 
T3318. Furthermore, the MS shall stop any of the retransmission timers that are running (e.g. T3310, T3321, 
T3330 or T33 17). Upon the first receipt of an AUTHENTICATION & CIPHERING FAILURE message from 
the MS with GMM cause "MAC failure" or "GSM authentication unacceptable" the network may initiate the 
identification procedure described in subclause 4.7.8. This is to allow the network to obtain the IMSI from the 
MS. The network may then check that the P-TMSI originally used in the authentication challenge corresponded 
to the correct IMSI. Upon receipt of the IDENTITY REQUEST message from the network, the MS shall send 
the IDENTITY RESPONSE message. 

NOTE: Upon receipt of an AUTHENTICATION & CIPHERING FAILURE message from the MS with reject 
cause "MAC failure" or "GSM authentication unacceptable", the network may also terminate the 
authentication procedure (see subclause 4.7.7.5). 

If the P-TMSI/IMSI mapping in the network was incorrect, the network should respond by sending a new 
AUTHENTICATION & CIPHERING REQUEST message to the MS. Upon receiving the new 
AUTHENTICATION & CIPHERING REQUEST message from the network, the MS shall stop timer T3318, if 
running, and then process the challenge information as normal. 

If the network is validated successfully (an AUTHENTICATION & CIPHERING REQUEST message that 
contains a valid SQN and MAC is received), the MS shall send the AUTHENTICATION & CIPHERING 
RESPONSE message to the network and shall start any retransmission timers (e.g. T3310, T3321, T3330 or 
T3317), if they were running and stopped when the MS received the first failed AUTHENTICATION AND 
CIPHERING REQUEST message. 

If the MS receives the second AUTHENTICATION AND CIPHERING REQUEST while T3318 is running and 

the MAC value cannot be resolved; or 

the message was received in UMTS and contains a GSM authentication challenge, 

the MS shall follow the procedure specified in this subclause (f), starting again from the beginning. If the SQN is 
invalid, the MS shall proceed as specified in (g). 

It can be assumed that the source of the authentication challenge is not genuine (authentication not accepted by 
the MS) if any of the following occurs: 

- after sending the AUTHENTICATION & CIPHERING FAILURE message with GMM cause "MAC failure" 
or "GSM authentication unacceptable" the timer T3318 expires; 

the MS detects any combination of the authentication failures: "MAC failure", "invalid SQN", and "GSM 
authentication unacceptable", during three consecutive authentication challenges. The authentication 
challenges shall be considered as consecutive only, if the authentication challenges causing the second and 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



151 



ETSI TS 124 008 V7.14.0 (2009-03) 



third authentication failure are received by the MS, while the timer T3318 or T3320 started after the previous 
authentication failure is running. 

When it has been deemed by the MS that the source of the authentication challenge is not genuine 
(authentication not accepted by the MS), the MS shall behave as described in subclause 4.7.7.6.1. 



Start T33 18 
StopT3318 


MS Network 
AUTHENTICATION & CIPHERING REQUEST 


^ Start T3360 

AUTH & CIPH FAILURE (cause='MAC failure' or 

'GSM authentication unacceptable') ^Stop T3360 


IDENTITY REQUEST ^^^^^^33^^ 


IDENTITY RESPONSE (IMSI) ^^^ ^33^^ 


AUTHENTICATION & CIPHERING REQUEST g^^^.^ ^jg^Q 


AUTHENTICATION & CIPHERING RESPONSE Stop T3360 





Figure 4.7.7a/1 3GPP TS 24.008: Authentication failure cause "MAC failure" or "GSM authentication 

unacceptable" 

(g) Authentication failure (GMM cause "Synch failure"): 

The MS shall send an AUTHENTICATION & CIPHERING FAILURE message, with the GMM cause "Synch 
failure", to the network and start the timer T3320. Furthermore, the MS shall stop any of the retransmission 
timers that are running (e.g. T3310, T3321, T3330 or T3317). Upon the first receipt of an AUTHENTICATION 
& CIPHERING message from the MS with the GMM cause "synch failure", the network shall use the returned 
AUTS parameter from the authentication & ciphering failure parameter IE in the AUTHENTICATION & 
CIPHERING FAILURE message, to re-synchronise. The re-synchronisation procedure requires the SGSN to 
delete all unused authentication vectors for that IMSI and obtain new vectors from the HLR. When re- 
synchronisation is complete, the network shall initiate the authentication & ciphering procedure. Upon receipt of 
the AUTHENTICATION & CIPHERING REQUEST message, the MS shall stop timer T3320, if running. 

NOTE: Upon receipt of two consecutive AUTHENTICATION & CIPHERING FAILURE messages from the 

MS with reject cause "synch failure", the network may terminate the authentication procedure by sending 
an AUTHENTICATION & CIPHERING REJECT message. 

If the network is validated successfully (a new AUTHENTICATION & CIPHERING REQUEST message is 
received which contains a valid SQN and MAC) while T3320 is running, the MS shall send the 
AUTHENTICATION & CIPHERING RESPONSE message to the network and shall start any retransmission 
timers (i.e. T3310, T3321, T3330 or T3317), if they were running and stopped when the MS received the first 
failed AUTHENTICATION AND CIPHERING REQUEST message. 

If the MS receives the second AUTHENTICATION & CIPHERING REQUEST while T3320 is running and 

the MAC value cannot be resolved; or 

the message was received in lu mode and contains a GSM authentication challenge, 

the MS shall proceed as specified in (f). If the SQN is invalid, the MS shall follow the procedure specified in this 
subclause (g), starting again fom the beginning. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



152 



ETSI TS 124 008 V7.14.0 (2009-03) 



The MS shall deem that the network has failed the authentication check and behave as described in subclause 
4.7.7.6.1, if any of the following occurs; 

the timer T3320 expires; 

- the MS detects any combination of the authentication failures: "MAC failure", "invalid SQN", and "GSM 
authentication unacceptable", during three consecutive authentication challenges. The authentication 
challenges shall be considered as consecutive only, if the authentication challenges causing the second and 
third authentication failure are received by the MS, while the timer T3318 or T3320 started after the previous 
authentication failure is running. 



MS Network 

AUTHENTICATION & CIPHERING REQUEST ^^^ ^^360 



AUTH & CIPH FAILURE (cause='Synch failure') Stop T3360 
Start T3320 ^p^^^^^^ 

AUTHENTICATION & CIPHERING REQUEST Re-synch 

Stop T3320 ^ with HLR 

AUTHENTICATION & CIPHERING RESPONSE 

► 



4.7.7.6.1 



Figure 4.7.7b/1 3GPP TS 24.008: Authentication failure cause "Synch failure" 

MS behaviour towards a network that has failed the authentication procedure 



If the MS deems that the network has failed the authentication check, then it shall request RR or RRC to release the RR 
connection and the PS signalling connection, if any, and bar the active cell or cells (see 3GPP TS 25.331 and 
3GPP TS 44.018). The MS shall start any retransmission timers (i.e. T3310, T3321, T3330 or T3317), if they were 
running and stopped when the MS received the first AUTHENTICATION AND CIPHERING REQUEST message 
containing an invalid MAC or invalid SQN, or no AUTN when a UMTS authentication challenge was expected. 



4.7.7.7 



Use of established security contexts 



In A/Gb mode, in the case of an established GSM security context, the GPRS GSM ciphering key shall be taken into 
use by the MS before the AUTHENTICATION AND CIPHERING RESPONSE message is transmitted. 

In A/Gb mode, in the case of an established UMTS security context, the GPRS GSM ciphering key shall be taken into 
use by the MS before the AUTHENTICATION AND CIPHERING RESPONSE message is transmitted. The network 
shall derive a GPRS GSM ciphering key from the GPRS UMTS ciphering key and the GPRS UMTS integrity key, by 
using the conversion function named "c3" defined in 3GPP TS 33.102 [5a]. 

In A/Gb mode, if during an ongoing, already ciphering protected RR connection, the network initiates a new 
Authentication and ciphering procedure, the new GPRS GSM ciphering key shall be taken into use by the MS before 
the AUTHENTICATION AND CIPHERING RESPONSE message is transmitted. In case of inter-system change to lu 
mode after receipt of the AUTHENTICATION AND CIPHERING REQUEST message, the MS and the network shall 
take the new keys into use immediately after the inter-system change. 

In lu mode, in the case of an established GSM security context, the ME shall derive a GPRS UMTS ciphering key and a 
GPRS UMTS integrity key from the GPRS GSM ciphering key by using the conversion functions named "c4" and "c5" 
defined in 3GPP TS 33.102 [5a]. The derived GPRS UMTS ciphering key and GPRS UMTS integrity key shall be 
taken into use by the MS when a valid SECURITY MODE COMMAND indicating PS domain is received during an 
RR connection (the definition of a vahd SECURITY MODE COMMAND message is given in 3GPP TS 25.331 [23c]). 
The network shall derive a GPRS UMTS ciphering key and a GPRS UMTS integrity key from the GPRS GSM 
ciphering key by using the conversion functions named "c4" and "c5" defined in 3GPP TS 33.102 [5a]. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



153 



ETSI TS 124 008 V7.14.0 (2009-03) 



In lu mode, in the case of an established UMTS security context, the GPRS UMTS ciphering key and the GPRS UMTS 
integrity key shall be taken into use by the MS when a vahd SECURITY MODE COMMAND indicating PS domain is 
received during an PS signalling connection (the definition of a valid SECURITY MODE COMMAND message is 
given in 3GPP TS 25.331 [23c]). 

In lu mode, if the MS received a vaUd SECURITY MODE COMMAND indicating PS domain in lu mode or a vaUd 
AUTHENTICATION AND CIPHERING REQUEST in A/Gb mode before the network initiates a new Authentication 
and ciphering procedure and establishes a new GSM/UMTS security context, the new GPRS UMTS ciphering key and 
GPRS UMTS integrity key are taken into use by the MS, when a new valid SECURITY MODE COMMAND 
indicating PS domain is received during the PS signalling connection. In case of inter-system change to A/Gb mode, the 
MS and the network shall take the new keys into use immediately after the inter-system change. 



4.7.7.8 



Handling of keys at intersystem change from lu mode to A/Gb mode 



At an inter-system change from lu mode to A/Gb mode, ciphering may be started (see 3GPP TS 44.064 [78a]) without 
any new authentication and ciphering procedure. Deduction of the appropriate security key for ciphering in A/Gb mode, 
depends on the current GSM/UMTS security context stored in the MS and the network. 

The ME shall handle the GPRS GSM ciphering key according to table 4.7.7.8.1. 

Before any initial GMM message is sent in the new cell in A/Gb mode, the GMM layer in the MS shall notify the LLC 
layer if ciphering shall be used or not. If yes, the GPRS GSM ciphering key and the applicable ciphering algorithm 
according to the stored Ciphering Algorithm IE in the MS shall also be indicated to the LLC layer (see 3GPP TS 44.064 
[78a]). 

Table 4.7.7.8.1/3GPP TS 24.008: Inter-system change from lu mode to A/Gb mode 



Security context established in IVIS and 
networl< in lu mode 


At inter-system change to /VGb mode: 


GSIVl security context 


An ME shall apply the GPRS GSM cipher key that was received 
from the GSM security context created in the SIM/USIM during 
the latest successful authentication procedure. 


UIVITS security context 


An ME shall apply the GPRS GSM cipher key that was derived 
by the USIM from the GPRS UMTS cipher key and the GPRS 
UMTS integrity key during the latest successful authentication 
procedure. 



NOTE: A USIM with UMTS security context, passes the GPRS UMTS ciphering key, the GPRS UMTS integrity 
key and the derived GPRS GSM ciphering key to the ME independent on the current radio access being 
UTRAN or GERAN. 



4.7.7.9 



Handling of keys at intersystem change from A/Gb mode to lu mode 



At an inter-system change from A/Gb mode to lu mode, ciphering and integrity may be started (see 3GPP TS 25.331) 
without any new authentication and ciphering procedure. Deduction of the appropriate security keys for ciphering and 
integrity check in lu mode, depend on the current GSM/UMTS security context stored in the MS and the network. 

The ME shall handle the GPRS UMTS cipher key and the GPRS UMTS integrity key according to table 4.7.7.9. L 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



154 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 4.7.7.9. 1/3GPP TS 24.008: Inter-system change from A/Gb mode to lu mode 



Security context established in MS and 
network in A/Gb mode 


At inter-system change to lu mode: 


GSM security context 


An ME shall derive the GPRS UMTS cipher key and the GPRS 
UMTS integrity key from the GPRS GSM cipher key that was 
provided by the SIM/USIM during the latest successful 
authentication procedure. The conversion functions named "c4" 
and "c5" in 3GPP TS 33.102 [5a] are used for this purpose. 


UMTS security context 


An ME shall apply the GPRS UMTS ciphering key and the GPRS 
UMTS integrity key that were received from the UMTS security 
context created in the USIM during the latest successful 
authentication procedure. 



NOTE: A USIM with UMTS security context, passes the GPRS UMTS ciphering key, the GPRS UMTS integrity 
key and the derived GPRS GSM ciphering key to the ME independent on the current radio access being 
UTRAN or GERAN. 



4.7.8 Identification procedure 



The identification procedure is used by the network to request an MS to provide specific identification parameters to the 
network e.g. International Mobile Subscriber Identity, International Mobile Equipment Identity (see 
3GPP TS 23.003 [10]). For the presentation of the IMEI, the requirements of 3GPP TS 42.009 [5] apply. 



4.7.8.1 



Identification initiation by the network 



The network initiates the identification procedure by transferring an IDENTITY REQUEST message to the MS and 
starts the timer T3370. The IDENTITY REQUEST message specifies the requested identification parameters in the 
identity type information element. 

4.7.8.2 Identification response by the MS 

An MS that has been attached to GPRS shall be ready to respond to an IDENTITY REQUEST message at any time. 

Upon receipt of the IDENTITY REQUEST message the MS sends back an IDENTITY RESPONSE message. The 
IDENTITY RESPONSE message shall contain the identification parameters as requested by the network. 

4.7.8.3 Identification completion by the network 

Upon receipt of the IDENTITY RESPONSE the network shall stop timer T3370. 

4.7.8.3a Abnormal cases In the MS 

(a) Requested identity is not available: 

If the MS cannot encode the requested identity in the IDENTITY RESPONSE message, e.g. because no valid 
SIM is available, then it shall encode the identity type as "No identity". 

4.7.8.4 Abnormal cases on the network side 

The following abnormal cases can be identified: 

a) Lower layer failure 

Upon detection of a lower layer failure before the IDENTITY RESPONSE is received, the network shall abort 
any ongoing GMM procedure. 

b) Expiry of timer T3370 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



155 



ETSI TS 124 008 V7.14.0 (2009-03) 



The identification procedure is supervised by the network by the timer T3370. The network shall, on the first 
expiry of the timer T3370, retransmit the IDENTITY REQUEST message and reset and restart the timer T3370. 
This retransmission is repeated four times, i.e. on the fifth expiry of timer T3370, the network shall abort the 
identification procedure and any ongoing GMM procedure. 

c) Collision of an identification procedure with a GPRS attach procedure 

If the network receives an ATTACH REQUEST message before the ongoing identification procedure has been 
completed and no GPRS attach procedure is pending on the network (i.e. no ATTACH ACCEPT/REJECT 
message has still to be sent as an answer to an ATTACH REQUEST message), the network shall proceed with 
the GPRS attach procedure. 

d) Collision of an identification procedure with a GPRS attach procedure when the identification procedure has 
been caused by a GPRS attach procedure 

If the network receives an ATTACH REQUEST message before the ongoing identification procedure has been 
completed and a GPRS attach procedure is pending (i.e. an ATTACH ACCEPT/REJECT message has to be sent 
as an answer to an earlier ATTACH REQUEST message), then: 

If one or more of the information elements in the ATTACH REQUEST message differs from the ones 
received within the previous ATTACH REQUEST message, the network shall proceed with the GPRS attach 
procedure; or 

If the information elements do not differ, then the network shall not treat any further this new ATTACH 
REQUEST. 

Collision of an identification procedure with an MS initiated GPRS detach procedure 

GPRS detach containing cause "power off: 

If the network receives a DETACH REQUEST message before the ongoing identification procedure has been 
completed, the network shall abort the identification procedure and shall progress the GPRS detach 
procedure. 

GPRS detach containing other causes than "power off": 

If the network receives a DETACH REQUEST message before the ongoing identification procedure has been 
completed, the network shall complete the identification procedure and shall respond to the GPRS detach 
procedure as described in subclause 4.7.4. 

e) Collision of an identification procedure with a routing area updating procedure 

If the network receives a ROUTING AREA UPDATE REQUEST message before the ongoing identification 
procedure has been completed, the network shall progress both procedures. 

f) Collision of an identification procedure with a service request procedure 

If the network receives a SERVICE REQUEST message before the ongoing identification procedure has been 
completed, the network shall progress both procedures. 



MS 



IDENTITY REQUEST 



IDENTITY RESPONSE 



Network 
- Start T3370 



-> Stop T3370 



Figure 4.7.8/1 3GPP TS 24.008: Identification procedure 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 56 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.9 Paging procedure 
4.7.9.1 Paging for GPRS services 

In A/Gb mode, paging is used by the network to identify the cell the MS has currently selected, or to prompt the mobile 
to re-attach if necessary as a result of network failure. If the MS is not GPRS attached when it receives a paging for 
GPRS services, the MS shall ignore the paging. 

In lu mode, paging is used by the network to request the establishment of PS signalling connection or to prompt the 
mobile to re-attach if necessary as a result of network failure. If the MS is not GPRS attached when it receives a paging 
for GPRS services, the MS shall ignore the paging. 

4.7.9.1 .1 Paging for GPRS services using P-TMSI 

The network shall initiate the paging procedure for GPRS services using P-TMSI when GMM signalling messages or 
user data is pending to be sent to the MS while the Mobile Reachable timer is running. The network may page only 
GPRS MSs which are GMM-REGISTERED and identified by a local P-TMSI. 

In lu mode, to initiate the procedure the GMM entity in the network requests the lower layer to start paging (see 
3GPP TS 25.331 [23c] and 3GPP TS 25.413) and starts timer T3313. Upon reception of a paging indication, the MS 
shall respond to the paging with a SERVICE REQUEST message with service type "paging response" (see 
3GPP TS 24.007 [20], 3GPP TS 23.060 [74], 3GPP TS 25.331 [23c] and 3GPP TS 25.413). If the paging request for 
GPRS services was received during an ongoing MS initiated GMM specific procedure, then the MS shall progress the 
GMM specific procedure, and the network shall proceed with the GMM specific procedure. 

In A/Gb mode, to initiate the procedure the GMM entity requests the RR sublayer to start paging (see 3GPP TS 44.018 
[84], 3GPP TS 44.060 [76], and starts timer T3313). Upon reception of a paging indication, the MS shall respond to the 
paging with any LLC frame (see 3GPP 3GPP TS 44.064 [78a], TS 24.007 [20], 3GPP TS 23.060 [74]). 

At intersystem change, an MS not having the READY timer running in A/Gb mode or an MS in PMM-IDLE mode in 
lu mode, being paged in a different access network as when it last sent user data or signalling message, uses ROUTING 
AREA UPDATE REQUEST message as paging response, i.e. the RA update procedure shall be performed instead 
according to the selective routing area update procedure. 

The network shall stop timer T3313 when a response is received from the MS. When the timer T3313 expires the 
network may reinitiate paging. 

In lu mode, when a response is received from the MS, the network shall change from PMM-IDLE mode to PMM- 
CONNECTED mode. 

In A/Gb mode, when a response different from an LLC NULL frame is received from the MS, the network shall start 
the READY timer. 

4.7.9.1 .2 Paging for GPRS services using IMSI 

Paging for GPRS services using IMSI is an abnormal procedure used for error recovery in the network. 

The network may initiate paging using IMSI if the P-TMSI is not available due to a network failure. 

In lu mode, to initiate the procedure the GMM entity in the network requests the lower layer to start paging (see 
3GPP TS 25.331 [23c] and 3GPP TS 25.413). 

In A/Gb mode, to initiate the procedure the GMM entity in the network requests the RR sublayer to start paging (see 
3GPP TS 44.018 [84], 3GPP TS 44.060 [76]). 

Upon reception of a paging indication for GPRS services using IMSI, the MS shall locally deactivate any active PDP 
context(s), MBMS context(s) and locally detach from GPRS. The local detach includes deleting any RAI, P-TMSI, P- 
TMSI signature and GPRS ciphering key sequence number stored, setting the GPRS update status to GU2 NOT 
UPDATED and changing state to GMM-DEREGISTERED. 

In lu mode, when an MS receives a paging request for GPRS services using the IMSI from the network before an MS 
initiated GMM specific procedure has been completed, then the MS shall abort the GMM specific procedure, and the 
MS shall proceed according to the description in this clause. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 57 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

After performing the local detach, the MS shall then perform a GPRS attach or combined GPRS attach procedure. 

After performing the attach, the MS should activate PDP context(s) to replace any previously active PDP context(s). 
The MS should also perform the procedures needed in order to activate any previously active multicast service(s). 

NOTE 1 : In some cases, user interaction may be required and then the MS cannot activate the PDP and MBMS 
context(s) automatically. 

NOTE 2: The MS does not respond to the paging except with the Attach Request. Hence timer T3313 in the 
network is not used when paging with IMSI. 

NOTE 3: Paging without DRX parameters may require a considerable extension of the paging duration. 

4.7.9.2 Paging for non-GPRS services 

The network may initiate the paging procedure for non-GPRS services when the MS is IMSI attached for non-GPRS 
services. 

In lu mode, to initiate the procedure the GMM entity requests the lower layer to start paging (see 3GPP TS 25.331 [23c] 
and 3GPP TS 25.413) for non-GPRS services. 

In A/Gb mode, to initiate the procedure the GMM entity requests the RR sublayer to start paging (see 3GPP TS 44.018 
[84] and 3GPP TS 44.060 [76] for non-GPRS services). 

The MS identity used for paging shall be the allocated TMSI if acknowledged by the MS, otherwise the IMSI. 

4.7.1 Receiving a GMM STATUS message by a GMM entity 

If the MS receives a GMM STATUS message no state transition and no specific action shall be taken as seen from the 
radio interface, i.e. local actions are possible. The actions to be taken on receiving a GMM STATUS message in the 
network are an implementation dependent option. 

4.7.11 Void 

4.7.12 GMM Information procedure 

The GMM information message support is optional in the network. The MM information procedure may be invoked by 
the network at any time during an established GMM context. 

4.7.12.1 GMM information procedure initiation by the network 

The GMM information procedure consists only of the GMM INFORMATION message sent from the network to the 
mobile station. During an established GMM context, the network may send none, one, or more GMM INFORMATION 
messages to the mobile station. If more than one GMM INFORMATION message is sent, the messages need not have 
the same content. 

4.7.12.2 GMM information procedure in the mobile station 

When the mobile station (supporting the GMM information message) receives an GMM INFORMATION message, it 
shall accept the message and optionally use the contents to update appropriate information stored within the mobile 
station. 

If the mobile station does not support the GMM information message the mobile station shall ignore the contents of the 
message and return an GMM STATUS message with cause #97. 

4.7.13 Service Request procedure (lu mode only) 

The purpose of this procedure is to transfer the PMM mode from PMM-IDLE to PMM-CONNECTED mode, and/or to 
assign radio access bearer in case of PDP contexts are activated without radio access bearer assigned. In latter case, the 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 58 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

PMM mode may be PMM-IDLE mode or may alternatively be the PMM-CONNECTED mode if the MS requires radio 
access bearer re-establishment. This procedure is used for; 

the initiation of CM layer service (e.g. SM or SMS) procedure from the MS in PMM-IDLE mode, 

the network to transfer down link signalling, 

- uplink (in PMM-IDLE or PMM CONNECTED) and downhnk (only in PMM-IDLE) user data, 

counting the number of mobile stations in a cell which are interested in a specific MBMS service. 

requesting the establishment of a point-to-point Radio Bearer for receiving a MBMS service. 

For downlink transfer of signalling or user data in PMM-IDLE mode, the trigger is given from the network by the 
paging request procedure, which is out of scope of the present document. 

For pending downlink user data in PMM-CONNECTED mode, the re -establishment of radio access bearers for all 
active PDP contexts is done without paging. 

For counting the number of mobile stations in PMM-IDLE mode interested in a specific MBMS service, the trigger is 
given from the network by the MBMS notification procedure (see 3GPP TS 25.331 [23c]). 

For establishing a point-to-point radio bearer to allow MBMS service, the trigger is given from the RRC determining 
this need from the MBMS control parameters broadcasted by the network (see 3GPP TS 25.331 [23c]). 

Service type can take either of the following values; "signalling", "data", "paging response", "MBMS multicast service 
reception" or "MBMS broadcast service reception". Each of the values shall be selected according to the criteria to 
initiate the Service request procedure. 

If the UE is triggered to send a Service Request message for both MBMS multicast service and MBMS broadcast 
service simultaneously, the UE shall include a Service Type indicating "MBMS multicast service reception". 

The criteria to invoke the Service request procedure are when; 

a) the MS has any signalling messages except GMM messages (e.g. for SM or SMS) to be sent to the network in 
PMM-IDLE mode (i.e., no secure PS signalling connection has been established). In this case, the service type 
shall be set to "signalling". 

b) the MS, either in PMM-IDLE or PMM-CONNECTED mode, has pending user data to be sent, no radio access 
bearer is established for the corresponding PDP context, and timer T3319 (see subclause 4.7.13.3) is not running 
or, optionally, if timer T33 19 is running and the flag in the Uplink data status IE for this PDP context has not 
been set in the last Service Request. The procedure is initiated by an indication from the lower layers (see 3GPP 
TS 24.007 [20]). In this case, the service type shall be set to "data". 

c) the MS receives a paging request for PS domain from the network in PMM-IDLE mode. In this case, the service 
type shall be set to "paging response". 

d) the MS is in PMM-IDLE mode or PMM-CONNECTED, receives an MBMS notification for an MBMS 
multicast service for which the MS has activated an MBMS context or for an MBMS broadcast service which 
has been selected for reception locally by upper layers in the MS, and is prompted by the contents of the 
notification to establish a PS signalling connection (see 3GPP TS 25.346 [1 10]). In this case, the service type 
shall be set to "MBMS multicast service reception" or "MBMS broadcast service reception", respectively. 

e) the MS in PMM-IDLE mode or PMM-CONNECTED, determines from the broadcast MBMS control parameters 
that there is a need to establish a point-to-point Radio Bearer to enable MBMS reception (see 3GPP TS 25.346 

[1 10]). In this case, the service type shall be set to "MBMS multicast service reception" or "MBMS broadcast 
service reception", respectively. 

If one of the above criteria to invoke the Service request procedure is fulfilled, then the Service request procedure may 
only be initiated by the MS when the following conditions are fulfilled: 

- its GPRS update status is GUI UPDATED; and 

no GMM specific procedure is ongoing (see subclause 4.1.1.1). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 59 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If a GMM specific procedure is ongoing at the time a request from CM sublayer, the RRC or the RABM (see 3GPP TS 
24.007 [20]) is received and the ATTACH REQUEST or ROUTING AREA UPDATE REQUEST message has been 
sent, then, depending on implementation, the MS shall abort the received request or delay it until the GMM specific 
procedure is completed. If the ATTACH REQUEST or ROUTING AREA UPDATE REQUEST message has not been 
sent, the MS may indicate "follow-on request pending" in the message (i.e. the MS wishes to prolong the established PS 
signalling connection after the GMM specific procedure). Then, the MS shall delay the Service request procedure until 
the GMM specific procedure is completed. 

If the network indicates "follow-on proceed" in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT 

message and the MS has a service request pending, the MS shall react depending on the service type. If the service type 
is: 

"signalling": the MS shall abort the Service request procedure and send the pending signalling messages 
immediately; 

"data": the MS shall immediately perform the pending Service request procedure using the current PS signalling 
connection; 

"paging response": the MS shall abort the Service request procedure. No further specific action is required from 
the MS. 

If the network indicates "follow-on proceed" and the MS has no service request pending, then no specific action is 
required from the MS. 

If the network indicates "no follow-on proceed" in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT 
message, the MS shall not initiate the pending Service request procedure until the current PS signalling connection is 
released. 

NOTE: The "follow-on proceed" indication was not defined in earlier versions of the protocol. A network that is 
compliant with the earlier versions of the protocol will always encode the respective bit as zero, i.e. as 
"follow-on proceed", even if it does not prolong the PS signalling connection. 

After completion of a Service request procedure but before re-establishment of radio access bearer, if the PDP and 
MBMS context status information elements are included, then the network shall deactivate all those PDP and MBMS 
contexts locally (without peer to peer signalling between the MS and the network), which are not in SM state PDP- 
INACTIVE on network side but are indicated by the MS as being in state PDP-INACTIVE. 

After completion of a Service request procedure, the pending service is resumed and uses then the connection 
established by the procedure. If the service type is indicating "data", then the radio access bearers for all activated PDP 
contexts are re-established by the network, except for those activated PDP contexts having maximum bit rate value set 
to kbit/s for both uplink and downlink and as an option those which have no pending user data. The re -establishment 
of radio access bearers for those PDP contexts is specified in subclause 6.1.3.3. 

4.7.13.1 Service Request procedure initiation 

The MS initiates the Service request procedure by sending a SERVICE REQUEST message. The timer T3317 shall be 
started after the SERVICE REQUEST message has been sent and state GMM-SER VICE-REQUEST-INITIATED is 
entered. The message SERVICE REQUEST shall contain the P-TMSI and the Service type shall indicate either "data", 
"signalling", "paging response", "MBMS multicast service reception" or "MBMS broadcast service reception". The MS 
shall not issue another Service request when the MS is in state GMM-SER VICE-REQUEST-INITIATED 

If the PDP context status information element is included in the SERVICE REQUEST message, then the network shall 
deactivate all those PDP contexts locally (without peer to peer signalling between the MS and the network) which are 
not in SM state PDP-INACTIVE on the network side, but are indicated by the MS as being in state PDP-INACTIVE. 

If the MBMS context status information element is included in the SERVICE REQUEST message, then the network 
shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and network) which 
are not in SM state PDP-INACTIVE on the network side, but are indicated by the MS as being in state PDP- 
INACTIVE. If no MBMS context status information element is included, then the network shall deactivate all MBMS 
contexts locally which are not in SM state PDP-INACTIVE on the network side. 

For a Service Request of type "data", the MS may include the Uplink data status information element in the SERVICE 
REQUEST message. The Uplink data status information indicates which preserved PDP contexts have pending uplink 
data to be sent. If the Uplink data status information element is included in the SERVICE REQUEST message with 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 60 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

service type "data", the network may use this information to determine which of the RABs for the preserved PDP 
contexts to re-estabhsh. 

4.7.13.2 GMM common procedure initiation 

The network may initiate GMM common procedures, e.g. the GMM identification or the GMM authentication and 
ciphering procedure, depending on the received information such as GPRS ciphering key sequence number and P- 
TMSI. 

4.7.1 3.3 Service request procedure accepted by the network 

If the SERVICE REQUEST message was sent in PMM-IDLE mode, the indication from the lower layers that the 
security mode control procedure is completed shall be treated as a successful completion of the procedure. The timer 
T3317 shall be stopped, and the MS enters GMM-REGISTERED state and PMM-CONNECTED mode. 

If the SERVICE REQUEST message was sent in PMM-CONNECTED mode, then the reception of the SERVICE 
ACCEPT message shall be treated as a successful completion of the procedure. The timer T3317 shall be stopped and 
the MS remains in PMM-CONNECTED mode. 

At successful completion of a service request procedure with Service type "data", the MS shall start timer T3319. The 
timer T3319 shall be stopped when the MS returns to PMM-IDLE mode or when the network releases the radio access 
bearer of any active PDP context. The MS shall not issue another Service Request with service type "data" while timer 
T3319 is running unless the Service request is being generated from a PDP context for which the flag in the Uplink data 
status IE has not been set in the last Service Request. 

The network may indicate a value for timer T3319 in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT 
messages. The last provided value of T3319 shall be used by the MS. If the information element T3319 value is not 
included in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT messages, the default value shall be 
used. If the T3319 value received by the MS contains an indication that the timer is deactivated or the timer value is 
zero, then the MS shall use the default value. 

If the PDP context status information element is included in the Service Accept, then the MS shall deactivate locally 
(without peer to peer signalling between the MS and the network) all that PDP contexts which are not in SM state PDP- 
INACTIVE on MS side but are indicated by the Network as being in state PDP-INACTIVE. 

If the MBMS context status information element is included in the SERVICE ACCEPT message, then the MS shall 
deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and network) which are 
not in SM state PDP-INACTIVE in the MS, but are indicated by the network as being in state PDP-INACTIVE. If no 
MBMS context status information element is included, then the MS shall deactivate all those MBMS contexts locally 
which are not in SM state PDP-INACTIVE in the MS. 

4.7.1 3.4 Service request procedure not accepted by the network 

If the Service request cannot be accepted, the network returns a SERVICE REJECT message to the mobile station. An 
MS that receives a SERVICE REJECT message stops timer T3317. The MS shall then take different actions depending 
on the received reject cause value: 

# 3 (Illegal MS); or 

# 6 (Illegal ME); 

- The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and enter the state GMM-DEREGISTERED. Furthermore, it shall delete any P-TMSI, P- 
TMSI signature, RAJ and GPRS ciphering key sequence number and shall consider the SIM/USIM as invalid for 
GPRS services until switching off or the SIM/USIM is removed. 

- A GPRS MS operating in MS operation mode A shall in addition set the update status to U3 ROAMING NOT 
ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS 
operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call 
is ongoing. The SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the 
SIM/USIM is removed. 

# 7 (GPRS services not allowed); 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 61 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2.9) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence 
number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM 
is removed. The new state is GMM-DEREGISTERED. 

# 9 (MS identity cannot be derived by the network); 

- The MS shall set the GPRS update status to GU2 NOT UPDATED (and shall store it according to subclause 
4.1.3.2), enter the state GMM-DEREGISTERED, and shall delete any P-TMSI, P-TMSI signature, RAI and 
GPRS ciphering key sequence number. Subsequently, the MS may automatically initiate the GPRS attach 
procedure. 

# 10 (Implicitly detached); 

- The MS shall change to state GMM-DEREGISTERED.NORMAL-SERVICE. The MS shall then perform a new 
attach procedure. The MS should also activate PDP context(s) to replace any previously active PDP contexts. 
The MS should also perform the procedures needed in order to activate any previously active multicast 
service(s). 

NOTE: In some cases, user interaction may be required and then the MS cannot activate the PDP and MBMS 
context(s) automatically. 

# 1 1 (PLMN not allowed); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) 
and enter the state GMM-DEREGISTERED. 

- The MS shall store the PLMN identity in the "forbidden PLMN list". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- A GPRS MS operating in MS operation mode A shall set the update status to U3 ROAMING NOT 
ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM 
IDLE. 

- The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 

# 12 (Location area not allowed); 

The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set 
the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) 
and shall change to state GMM-DEREGISTERED.LIMITED-SERVICE. 

The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall 
delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt 
counter. The new MM state is MM IDLE. 

- The MS shall perform a cell selection according to 3GPP TS 43.022 [82] and 3GPP TS 25.304. 
#13 (Roaming not allowed in this location area); 

- The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall change to state GMM-REGISTERED.LIMITED-SERVICE. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 62 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall 
reset the location update attempt counter. The new MM state is MM IDLE. 

- The MS shall perform a PLMN selection according to 3GPP TS 23.122 [14]. 

# 15 (No Suitable Cells In Location Area); 

- The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to 
subclause 4.1.3.2) and shall change to state GMM-REGISTERED.LIMITED-SERVICE. 

The MS shall store the LAI in the list of "forbidden location areas for roaming". 

The MS shall start timer T3340 as described in subclause 4.7.1.9. 

If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is 
operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the 
RR connection is subsequently released: 

- If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall 
reset the location update attempt counter. The new MM state is MM IDLE. 

The MS shall search for a suitable cell in another location area in the same PLMN according to 3GPP 
TS 43.022 [82] and 3GPP TS 25.304. 

# 40 (No PDP context activated) 

The MS shall deactivate locally all active PDP and MBMS contexts and the MS shall enter the state GMM- 
REGISTERED.NORMAL-SERVICE. The MS may also activate PDP context(s) to replace any previously 
active PDP contexts. The MS may also perform the procedures needed in order to activate any previously active 
multicast service(s). 

NOTE: In some cases, user interaction may be required and then the MS cannot activate the PDP and MBMS 
context(s) automatically. 

Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in 
subclause 4.7.13.5. 

4.7.1 3.5 Abnormal cases in the MS 

The following abnormal cases can be identified: 

a) Access barred because of common access class control or PS domain specific access control 

The Service request procedure shall not be started. The MS stays in the current serving cell and applies normal 
cell reselection process. The Service request procedure may be started by CM layer if it is still necessary, i.e. 
when access is granted or because of a cell change. 

b) Lower layer failure before the security mode control procedure is completed, SERVICE ACCEPT or SERVICE 
REJECT message is received 

The procedure shall be aborted except in the following implementation option cases b.l, b.2 and b.3. 

b. 1) Release of PS signalling connection in lu mode (i.e. RRC connection release) before the completion of the 
service request procedure 

The service request procedure shall be initiated again, if the following conditions apply: 

i) The original service request procedure was initiated over an existing PS signalling connection; and 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 63 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to 
the PS signalling connection were received after the SERVICE REQUEST message was transmitted. 

b.2) RR release in lu mode (i.e. RRC connection release) with cause different than "Directed signalling 

connection re -establishment", for example, "Normal", or "User inactivity" (see 3GPP TS 25.331 [32c] and 3GPP 
TS 44.118 [111]) 

The service request procedure shall be initiated again, if the following conditions apply: 

i) The original service request procedure was initiated over an existing RRC connection and, 

ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to 
the PS signalling connection were received after the SERVICE REQUEST messge was transmitted. 

NOTE: The RRC connection release cause different than "Directed signalling connection re-establishment" that 
triggers the re-initiation of the service request procedure is implementation specific. 

b.3) RR release in lu mode (i.e. RRC connection release) with cause "Directed signalling connection re- 
establishment" (see 3GPPTS 25.331 [32c] and 3GPPTS 44.118 [111]) 

The routing area updating procedure shall be initiated followed by a rerun of the service request procedure if the 
following condition applies: 

i) The service request procedure was not due to a rerun of the procedure due to "Directed signalling 
connection re-establishment". 

c) T33 17 expired 

The MS shall enter GMM-REGISTERED state. 

If the MS is in PMM-IDLE mode then the procedure shall be aborted and the MS shall release locally any 
resources allocated for the service request procedure. 

If the MS is in PMM-CONNECTED mode, then the procedure shall be aborted. 

d) SERVICE REJECT received, other causes than those treated in subclause 4.7.13.4 
The procedure shall be aborted. 

e) Routing area update procedure is triggered 

If a cell change into a new routing area occurs and the necessity of routing area update procedure is determined 
before the security mode control procedure is completed, a SERVICE ACCEPT or SERVICE REJECT message 
has been received, the Service request procedure shall be aborted and the routing area updating procedure is 
started immediately. Follow-on request pending may be indicated in the ROUTING AREA UPDATE 
REQUEST for the service, which was the trigger of the aborted Service request procedure, to restart the pending 
service itself or the Service request procedure after the completion of the routing area updating procedure. If the 
Service type of the aborted SERVICE REQUEST was indicating "data", then the routing area update procedure 
may be followed by a re-initiated Service request procedure indicating "data", if it is still necessary. If the 
Service type was indicating "MBMS multicast service reception", or "MBMS broadcast service reception" the 
Service request procedure shall be aborted. 

f) Power off 

If the MS is in state GMM-SER VICE-REQUEST-INITIATED at power off, the GPRS detach procedure shall be 
performed. 

g) Procedure collision 

If the MS receives a DETACH REQUEST message from the network in state GMM-SER VICE-REQUEST- 
INITIATED, the GPRS detach procedure shall be progressed and the Service request procedure shall be aborted. 
If the cause IE, in the DETACH REQUEST message, indicated a "reattach request", the GPRS attach procedure 
shall be performed. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 64 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.1 3.6 Abnormal cases on the network side 

The following abnormal cases can be identified: 

a) Lower layer failure 

If a low layer failure occurs before the security mode control procedure is completed, a SERVICE ACCEPT or 
SERVICE REJECT message has been sent to the MS, the network enters/stays in PMM-IDLE. 

b) Protocol error 

If the SERVICE REQUEST message is received with a protocol error, the network shall return a SERVICE 
REJECT message with one of the following reject causes: 

#96: Mandatory information element error; 

#99: Information element non-existent or not implemented; 

#100: Conditional IE error; 

#111: Protocol error, unspecified. 

The network stays in PMM-IDLE mode. 

c) More than one SERVICE REQUEST received and the procedure has not been completed (i.e., the security 
mode control procedure has not been completed or SERVICE ACCEPT, SERVICE REJECT message has not 
been sent) 

If one or more of the information elements in the SERVICE REQUEST message differs from the ones 
received within the previous SERVICE REQUEST message, the previously initiated Service request 
procedure shall be aborted and the new Service request procedure shall be progressed; 

If the information elements do not differ, then the network shall continue with the previous Service request 
procedure and shall not treat any further this SERVICE REQUEST message. 

d) ATTACH REQUEST received before the security mode control procedure has been completed or an SERVICE 
ACCEPT or an SERVICE REJECT message has been sent 

If an ATTACH REQUEST message is received and the security mode control procedure has not been completed 
or an SERVICE ACCEPT or an SERVICE REJECT message has not been sent, the network may initiate the 
GMM common procedures, e.g. the GMM authentication and ciphering procedure. The network may e.g. after a 
succesful GMM authentication and ciphering procedure execution, abort the Service request procedure, the 
GMM context, PDP contexts and MBMS contexts, if any, are deleted and the new ATTACH REQUEST is 
progressed. 

e) ROUTING AREA UPDATE REQUEST message received before the security mode control procedure has been 
completed or an SERVICE ACCEPT or an SERVICE REJECT message has been sent 

If an ROUTING AREA UPDATE REQUEST message is received and the security mode control procedure has 
not been completed or an SERVICE ACCEPT or an SERVICE REJECT message has not been sent, the network 
may initiate the GMM common procedures, e.g. the GMM authentication and ciphering procedure. The network 
may e.g. after a successful GMM authentication and ciphering procedure execution, abort the Service request 
procedure and progress the routing area update procedure. 

f) If the Service Type indicates "data" and the network fails to re-establish some or all RAB(s) then the SGSN may 
determine if PDP Context Modification or PDP Context Deactivation should be initiated. 

The appropriate action is an operator choice and depends on the QoS profile of the PDP Context, and the UpUnk 
data status. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 65 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

4.7.14 Void 

5 Elementary procedures for circuit-switched Call 

Control 

5.1 Overview 
5.1.1 General 

This subclause describes the call control (CC) protocol, which is one of the protocols of the Connection Management 
(CM) sublayer (see 3GPP TS 24.007 [20]). 

Every mobile station must support the call control protocol. If a mobile station does not support any bearer capability at 
all then it shall respond to a SETUP message with a RELEASE COMPLETE message as specified in subclause 5.2.2.2. 

In lu mode only, integrity protected signalling (see subclause 4.1.1.1.1 of the present document and in general, see 
3GPP TS 33.102 [5a]) is mandatory. In lu mode only, all protocols shall use integrity protected signalling. Integrity 
protection of all CC signalling messages is the responsibility of lower layers. It is the network which activates integrity 
protection. This is done using the security mode control procedure (3GPP TS 25.331 [23c] and 3GPP TS 44.1 18 [111]). 

In the call control protocol, more than one CC entity are defined. Each CC entity is independent from each other and 
shall communicate with the correspondent peer entity using its own MM connection. Different CC entities use different 
transaction identifiers. 

With a few exceptions the present document describes the call control protocol only with regard to two peer entities. 
The call control entities are described as communicating finite state machines which exchange messages across the 
radio interface and communicate internally with other protocol (sub)layers. This description is only normative as far as 
the consequential externally observable behaviour is concerned. 

Certain sequences of actions of the two peer entities compose "elementary procedures" which are used as a basis for the 
description in this subclause. These elementary procedures may be grouped into the following classes: 

call establishment procedures; 

call clearing procedures; 

- call information phase procedures; 

- miscellaneous procedures. 

The terms "mobile originating" or "mobile originated" (MO) are used to describe a call initiated by the mobile station. 
The terms "mobile terminating" or "mobile terminated" (MT) are used to describe a call initiated by the network. 

Figure 5.1a/3GPP TS 24.008 gives an overview of the main states and transitions on the mobile station side. 

The MS side extension figure 5.1a.l/3GPP TS 24.008 shows how for the Network Initiated MO call the MS reaches 
state Ul.O from state UO $(CCBS)$. 

Figure 5.1b/3GPP TS 24.008 gives an overview of the main states and transitions on the network side. 

The Network side extension figure 5.1b. 1/3GPP TS 24.008 shows for Network Initiated MO Calls the Network reaches 
state Nl.O from state NO $(CCBS)$. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



166 



ETSI TS 124 008 V7.14.0 (2009-03) 



/UO. 1 MM CON- 
I NECTIONPENDINI 

-' MNCC.EST.CNF 



Dl (PROGRESS) 

\mcc- ' 

PROGRESS. IND fU3 MO CALL 
PROCEEDING 

A Dl 



MMCC.SYNC.IND/ 
(res. ass) 



MNCC-SETUP.REQ. 

^^ '~ """"^-- 

MMCC-EST-REC! 



Dl (CONNK 



UO 
NULL 



z: 



MMCC. EST. IND (SETUP) 



MNCC-REL-CNF 
MMCC-REL-REQ 



DR (REL. COM) 
MNCC-REL-IND 
MMCC-REL-REQ 



MNCC-SETUP-INI) 




Ad|(REL COM) 



I CALL PRESENT; 



U19 RELEASE 
REQUEST 



MNCC-CALL.CONF.REQ. 



DR (CALLCONF) 



DR (REL) 
MNCC-DISC-IND 




DISC.REQ. 




DR (REL) 




A 

Dl (DISC) 






T MNC 


C. RELREQ 


1 DSCONNECT 
vREQUEST J 

h 


U12 DISCONNEC 
VINDICATION ^ 






MNCC-DISC-IND 






DR (DISC) 












Amncc 


/ 



MNCC-ALERT.REQ, 



U9 MT CALL 
CONFIRMED 



MMCC. SYNC. IND. 
(res. ass.) 



U7 CALL 
RECEIVED 



-V V 



STATES |/DI(DISC) 

U3, 4,7 ,8,9, 10 



MNOO-SETUP-ONF 
DR (CONNACK) 




MNCC-SYNC-IND 
/^ (res. ass) 



: MNCC. SETUP. RSP. 



DR (CONN) 



MNCC-SETUP-CNF- 
DR (CONNACK) 



<J 



10 
ACTIVE 



,'DI (CONNACK) 



MNCC-SETUP 
COMPL. IND 



(*) early asslgnmenl 

NOTE: 

DR(MESSAGE)= MMCC_DATA_REQ(MESSAGE) 

Dl (MESSAGE) = MMCC_DATA_IND (MESSAGE) 



Figure 5.1a/3GPP TS 24.008: Overview call control protocol/MS side 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



167 



ETSI TS 124 008 V7.14.0 (2009-03) 



U 
Nil 



MMCC.PROM 



MNCC.PROM 



UO. 
PROMPT 



DR 



UO. 
WAIT FOR 



DI(CC 



UO. 



CC-EST. 



DR (CC ESTABLISHMENT 



UO. 



CC_EST. 



DI 



MNCC.RECA 



UO. 
RECALL_PR 



MNCC.SETU 



DR 



U 



CALL 



Figures. 1a.1/3GPP TS 24.008: Overview call control protocol/MS side, extension: 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



168 



ETSI TS 124 008 V7.14.0 (2009-03) 



MMCC.EST.IND(SETUF 



MNCC. SETUP REQ. 




NOTE: 

DR(MESSAGE)= MMCC_DATA_REQ(MESSAGE) 

Dl (MESSAGE) = MMCC_DATAJND (MESSAGE) 



Figure 5.1b/3GPP TS 24.008 Overview call control protocol/Network side 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



169 



ETSI TS 124 008 V7.14.0 (2009-03) 



NO 
NULL 



MNCC.CC CONN.REQ 



MMCC.CC CONN.REQ 



N0.2 
CC CONN PENDING 



,, MMCC.EST.IND (START CC) 



NO. 3 
NW ANSWER PENDING! 



DR (CC_ESTABLISH) 



i 



N0.4 
CC-EST.PESENT 



Dl (CC_EST_CONF) 



NO. 5 
CC EST. CONFIRMED 



DR (RECALL) 



1 



NO. 6 
RECALL PRESENT 



Dl (SETUP) 



N1 
CALL INITIATED 



Figure 5.1b.1/3GPP TS 24.008 Overview call control protocol/Network side, extension 

5.1.2 Call Control States 

5.1 .2.1 Call states at the mobile station side of the interface 

The states which may exist on the mobile station side of the radio interface are defined in this subclause. 

NOTE: States UO.l, U0.2, U0.3, U0.4, U0.5, U0.6, U26, and U27 are 3GPP specific. All other states are ITU-T 
defined. 



5.1.2.1.1 
No call exists. 



Null (State UO) 



5.1 .2.1 .2 MM Connection pending (UO.l ) 

This state exists for a mobile originating call, when the mobile station requests the establishment of a MM connection. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 70 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.1 .2.1 .2a CC prompt present (U0.2) $(CCBS)$ 

This state exists for a mobile originating call when the network has prompted the mobile station to establish a CC 
connection but the mobile station has not yet responded. 

NOTE: This state is transient. 

5.1 .2.1 .2b Wait for network information (U0.3) $(CCBS)$ 

This state exists for a mobile originating call when the mobile station has responded to the prompt from the network to 
establish a CC connection and the mobile station is waiting for further information from the network. 

5.1 .2.1 .2c CC-Establishment present (U0.4) $(CCBS)$ 

This state exists for a mobile originating call when the mobile station has received a CC-establishment request but has 
not yet responded. 

NOTE: This state is transient. 

5.1 .2.1 .2d CC-Establishment confirmed (U0.5) $(CCBS)$ 

This state exists for a mobile originating call when the mobile station has sent the acknowledgement that the mobile 
station has received all the CC information that is needed. 

5.1 .2.1 .2e Recall present (U0.6) $(CCBS)$ 

This state exists for a mobile originating call when the mobile station has received a recall request but has not yet 
responded. 

NOTE: This state is transient. 

5.1.2.1.3 Call initiated (U1) 

This state exists for a mobile originating call, when the MS requests call establishment from the network. 

5.1 .2.1 .4 Mobile originating call proceeding (US) 

This state exists for a mobile originating call when the mobile station has received acknowledgement that the network 
has received all call information necessary to effect call establishment. 

5.1.2.1.5 Call delivered (U4) 

This state exists for a mobile originating call, when the calling mobile station has received an indication that remote 
user alerting has been initiated. 

5.1.2.1.6 Call present (U6) 

This state exists for a mobile terminating call when the mobile station has received a call establishment request but has 
not yet responded. 

5.1.2.1.7 Call received (U7) 

This state exists for a mobile terminating call when the mobile station has indicated alerting but has not yet answered. 

5.1.2.1.8 Connect Request (U8) 

This state exists for a mobile terminating call, when the mobile station has answered the call and is waiting to be 
awarded the call. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 71 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.1 .2.1 .9 Mobile terminating call confirmed (U9) 

This state exists for a mobile terminating call when the mobile station has sent acknowledgement that the mobile station 
has received all call information necessary to effect call establishment. 

5.1.2.1.10 Active (U10) 

This state exists for a mobile terminating call when the MS has answered the call. This state exists for a mobile 
originating call when the MS has received an indication that the remote user has answered the call. 

5.1.2.1.11 Disconnect request (U11) 

This state exists when the mobile station has requested the network to clear the end-to-end connection (if any) and is 
waiting for a response. 

5.1.2.1.12 Disconnect indication (U12) 

This state exists when the mobile station has received an invitation to disconnect because the network has disconnected 
the end-to-end connection (if any). 

5.1.2.1.13 Release request (U 19) 

This state exists when the MS has requested the network to release and is waiting for a response. 

5.1.2.1.14 Mobile originating modify (U26) 

This state exists when the mobile station has sent a request to the network for a new mode but has not yet received an 
answer. 

5.1.2.1.15 Mobile terminating modify (U27) 

This state exists when the mobile station has received a request from the network for a new mode and has not yet sent a 
response to this request. 

5.1.2.2 Network call states 

NOTE: States NO.l, N0.2, N0.3, N0.4, N0.5, N0.6, N26, N27, N28, N3a, N4,a, N7a, and N9a are 3GPP specific. 
All other states are ITU-T defined. 

The call states that may exist on the network side of the radio interface are defined in this subclause. 

5.1.2.2.1 Null (State NO) 

No call exists. 

5.1 .2.2.2 MM connection pending (NO.l ) 

This state exists for a mobile terminating call, when the network requests the establishment of a MM connection. 

5.1 .2.2.2a CC connection pending (N0.2) $(CCBS)$ 

This state exists for a mobile originating call when the network has requested the mobile station to establish a CC 
connection. 

5.1 .2.2.2b Network answer pending (NO. 3) $(CCBS)$ 

This state exists for a mobile originating call when the mobile station has established a CC connection upon the request 
of the network, but the network has not yet informed the mobile station of the reason for the network's action. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 72 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.1 .2.2.2c CC-Establishment present (N0.4) $(CCBS)$ 

This state exists for a mobile originating call when the network has sent a CC establishment request but has not yet 
received a satisfactory response. 

5.1 .2.2.2d CC-Establishment confirmed (N0.5) $(CCBS)$ 

This state exists for a mobile originating call when the network has received acknowledgement that the mobile station 
has received all call information necessary to effect call establishment. 5. 1.2.2.2e Recall present (N0.6) $(CCBS)$ 

This state exists for a mobile originating call when the network has sent a recall request but has not yet received a 
satisfactory response. 

5.1.2.2.3 Call initiated (N1) 

This state exists for a mobile originating call when the network has received a call establishment request but has not yet 
responded. 

5.1 .2.2.4 Mobile originating call proceeding (N3) 

This state exists for a mobile originating call when the network has sent acknowledgement that the network has 
received all call information necessary to effect call establishment. 

5.1.2.2.5 Call delivered (N4) 

This state exists for a mobile originating call when the network has indicated that remote user alerting has been 
initiated. 

5.1.2.2.6 Call present (N6) 

This state exists for a mobile terminating call when the network has sent a call establishment request but has not yet 
received a satisfactory response. 

5.1.2.2.7 Call received (N7) 

This state exists for a mobile terminating call when the network has received an indication that the mobile station is 
alerting but has not yet received an answer. 

5.1.2.2.8 Connect request (N8) 

This state exists for a mobile terminating call when the network has received an answer but the network has not yet 
awarded the call. 

5.1 .2.2.9 Mobile terminating call confirmed (N9) 

This state exists for a mobile terminating call when the network has received acknowledgement that the mobile station 
has received all call information necessary to effect call establishment. 

5.1.2.2.10 Active (N10) 

This state exists for a mobile terminating call when the network has awarded the call to the called mobile station. This 
state exists for a mobile originating call when the network has indicated that the remote user has answered the call. 

5.1.2.2.11 Not used 

5.1.2.2.12 Disconnect indication (N12) 

This state exists when the network has disconnected the end- to-end connection (if any) and has sent an invitation to 
disconnect the mobile station to network connection. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 73 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.1.2.2.13 Release request (N 19) 

This state exists when the network has requested the MS to release and is waiting for a response. 

5.1 .2.2.14 Mobile originating modify (N26) 

This state exists when the network has received a request from the mobile station for a new mode but has not yet sent a 
response. 

5.1.2.2.15 Mobile terminating modify (N27) 

This state exists when the network has sent a request to the mobile station for a new mode but has not yet received an 
answer. 

5.1.2.2.16 Connect Indication (N28) 

This state exists for a mobile originating call when the network has indicated that the remote user has answered the call 
and the network is waiting for acknowledgement by the mobile station. 

5.2 Call establishment procedures 

Establishment of a call is initiated by request of upper layer in either the mobile station or the network; it consists of: 

the establishment of a CC connection between the mobile station and the network; 

the activation of the codec or interworking function. 

Whenever it is specified in the present document clause 5 that the mobile station shall attach the user connection, this 
means that the mobile station shall activate the codec or interworking function as soon as an appropriate channel is 
available. The mobile station shall de-activate the codec or interworking function whenever an appropriate channel is no 
longer available. As soon as an appropriate channel is (again) available, the codec or interworking function shall be re- 
activated. If a new order to attach the user connection is received, the new order shall supersede the previous one. 

A channel shall be considered as appropriate if it is consistent with the possibly negotiated bearer capability applicable 
for the actual phase of the call. The mobile station shall not consider a channel as not appropriate because the type of 
the channel (full rate/half rate) is not the preferred one. If; 

the user connection has to be attached but no appropriate channel is available for a contiguous time of 30 
seconds; or if 

the codec or interworking function is de-activated for a contiguous time of 30 seconds; 

then the mobile station may initiate call clearing. 

Upon request of upper layers to establish a call, restricting conditions for the establishment of the call are examined. 
These restricting conditions concern the states of parallel CC entities and are defined elsewhere. If these restricting 
conditions are fulfilled, the call establishment is rejected. Otherwise a CC entity in state UO, "null", is selected to 
establish the call. It initiates the establishment by requesting the MM sublayer to establish an MM connection. 

In lu mode, if the lower layers indicate the release of a radio access bearer, whereas the corresponding call is still active, 
the MS shall not automatically initiate the release of that call. 



5.2.1 Mobile originating call establishment 



The call control entity of the mobile station initiates establishment of a CC connection by requesting the MM sublayer 
to establish a mobile originating MM connection and entering the "MM connection pending" state. There are two kinds 
of a mobile originating call: basic call and emergency call. The request to establish an MM connection shall contain a 
parameter to specify whether the call is a basic or an emergency call. This information may lead to specific qualities of 
services to be provided by the MM sublayers. Timer T303 is started when the CM SERVICE REQUEST message is 
sent. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 74 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

For mobile stations supporting eMLPP basic calls may optionally have an associated priority level as defined in 
3GPP TS 23.067 [88]. This information may also lead to specified qualities of service to be provided by the MM 
sublayers. 

While being in the "MM connection pending" state, the call entity of the mobile station may cancel the call prior to 
sending the first call control message according to the rules given in subclause 4.5.1.7. 

The mobile station supporting multicall that is initiating an emergency call shall release one or more existing call to 
ensure the emergency call can be established if the multicall supported information stored in the mobile station 
described in subclauses 5.2.1.2 and 5.2.2.1 indicates the network does not support multicall and some ongoing calls 

exists. 

Having entered the "MM connection pending" state, upon MM connection establishment, the call control entity of the 
mobile station sends a setup message to its peer entity. This setup message is 

a SETUP message, if the call to be established is a basic call, and 

an EMERGENCY SETUP message, if the call to be established is an emergency call. 

The mobile station then enters the "call initiated" state. Timer T303 is not stopped. 

The setup message shall contain all the information required by the network to process the call. In particular, the 
SETUP message shall contain the called party address information. 

If the mobile station supports multicall, it shall include the Stream Identifier (SI) information element. For the first call 
i.e. when there are no other ongoing calls the SI value shall be 1. 

For speech calls the mobile station shall indicate all codecs that it supports for UTRAN in the Supported Codec List 
information element. Codecs for GERAN shall be indicated in the Bearer Capability information element, if this 
information element is included. Additionally, if the mobile station supports codecs for GERAN and UTRAN, it shall 
indicate the codecs for GERAN also in the Supported Codec List information element. 

If the call is a redial attempt to switch from speech to multimedia or vice-versa, the SETUP message shall include the 
Redial information element. 

NOTE: Redial attempt is defined in 3GPP TR 23.903: "Redial solution for voice-video switching" [1 15]. 

If the MS supports the enhanced network-initiated in-call modification procedure as specified in subclause 5.3.4.3, the 
MS shall indicate this in the Call Control Capabilities IE in the SETUP message. 

If timer T303 elapses in the "MM connection pending" state, the MM connection in progress shall be aborted and the 
user shall be informed about the rejection of the call. 

5.2.1.1 Call initiation 

The "call initiated" state is supervised by timer T303.For normal MO calls, this timer will have already been started 
after entering the "MM connection pending" state. For network-initiated MO calls this timer will be started in the recall 
present state as defined in subclause 5.2.3.4 

When the call control entity of the mobile station is in the "call initiated" state and if it receives: 

i) a CALL PROCEEDING message, it shall proceed as described in subclause 5.2.1.3; 

ii) an ALERTING message, it shall proceed as described in subclause 5.2.1.5; 

iii) a CONNECT message, it shall proceed as described in subclause 5.2.1.6; 

iv) a RELEASE COMPLETE message it shall proceed as described in subclause 5.2.1.2. 

Abnormal case: 

- If timer T303 elapses in the "call initiated" state before any of the CALL PROCEEDING, ALERTING, 
CONNECT or RELEASE COMPLETE messages has been received, the clearing procedure described in 
subclause 5.4 is performed. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 75 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.2.1.2 Receipt of a setup message 

In the "null" or "recall present" states, upon receipt of a setup message (a SETUP message or an EMERGENCY SETUP 
message, see subclause 5.2.1.1), the call control entity of the network enters the "call initiated" state. It shall then 
analyse the call information contained in the setup message. 

In lu mode, network shall include the SI received in the SETUP message into the RABid and send it back to the mobile 
station. For RABid see 3GPP TS 25.413 and 3GPP TS 44.1 18 [1 1 1]. If the network receives the SETUP message with 
no SI, the network shall set the SI value to 1 . 

i) If, following the receipt of the setup message, the call control entity of the network determines that the call 
information received from the mobile station is invalid (e.g. invalid number), then the network shall initiate call 
clearing as defined in subclause 5.4 with one of the following cause values; 

# 1 "unassigned (unallocated) number", 

# 3 "no route to destination", 

# 22 "number changed", 

# 28 "invalid number format (incomplete number)". 

ii) If, following the receipt of the setup message, the call control entity of the network determines that a requested 
service is not authorized or is not available, it shall initiate call clearing in accordance with subclause 5.4.2 with 
one of the following cause values: 

# 8 "operator determined barring", 

# 57 "bearer capability not authorized", 

# 58 "bearer capability not presently available", 

# 63 "service or option not available, unspecified", or 

# 65 "bearer service not implemented". 

iii) Otherwise, the call control entity of the network shall either: 

send a CALL PROCEEDING message to its peer entity to indicate that the call is being processed; and enter 
the "mobile originating call proceeding" state; 

or: send an ALERTING message to its peer entity to indicate that alerting has been started at the called user 
side; and enter the "call received" state; 

or: send a CONNECT message to its peer entity to indicate that the call has been accepted at the called user 
side; and enter the "connect request" state. 

The call control entity of the network may insert bearer capability information element(s) in the CALL 
PROCEEDING message to select options presented by the mobile station in the Bearer Capability information 
element(s) of the SETUP message. The bearer capability information element(s) shall contain the same 
parameters as received in the SETUP except those presenting a choice. Where choices were offered, appropriate 
parameters indicating the results of those choices shall be included. 

The CALL_PROCEEDING message shall also contain the priority of the call in the case where the network 
supports eMLPP. Mobile stations supporting eMLPP shall indicate this priority level to higher sublayers and 
store this information for the duration of the call for further action. Mobile stations not supporting eMLPP shall 
ignore this information element if provided in a CALL PROCEEDING message. 

NOTE: If the network supports only R98 or older versions of this protocol and the priority is not included in the 
CALL PROCEEDING message, this does not imply that the network does not support eMLPP. 

The CALL_PROCEEDING message shall contain the multicall supported information in the network call 
control capabilities in the case where the network supports multicall and there are no other ongoing calls to the 
MS. Mobile stations supporting multicall shall store this information until the call control state for all calls 
returns to null. Mobile stations not supporting multicall shall ignore this information if provided in a CALL 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



176 



ETSI TS 124 008 V7.14.0 (2009-03) 



PROCEEDING message. If the multicall supported information is not sent in the CALL_PROCEEDING 
message, the mobile station supporting multicall shall regard that the network doesn't support multicall. 

The call control entity of the network having entered the "mobile originating call proceeding" state, the network may 
initiate the assignment of a traffic channel according to subclause 5.2.1.9 (early assignment). 

For speech calls, if the SETUP message or EMERGENCY SETUP message contains a Supported Codec List 
information element, the network shall use this list to select the codec for UTRAN. If no Supported Codec List 
information element is received, then for UTRAN the network shall select the default UMTS speech codec according to 

subclause 5.2.1.11. 

Codecs for GERAN shall be selected from the codecs indicated in the Supported Codec List information element or in 
the Bearer Capability information element. If neither a Supported Codec List information element nor a Bearer 
Capability information element is received, then for GERAN the network shall select GSM full rate speech version 1. 

Codec information that does not apply to the currently serving radio access shall be used by the network if an inter- 
system change occurs. 



Network 




CALL PROCEEDING 

ALERTING 

CONNECT 
RELEASE COMPLETE 



(i) 
(ii) 
(iii) 

(iv) 



Figure 5.2/3GPP TS 24.008 Mobile originated call initiation and possible subsequent responses. 



5.2.1.3 



Receipt of a CALL PROCEEDING message 



Having entered the "call initiated" state, when the call control entity of the mobile station receives a CALL 
PROCEEDING message, it shall stop timer T303; start timer T310 unless 

- the CALL PROCEEDING message contains ?k progress indicator IE specifying progress description #1, #2, or 
#64; or 

it has received a PROGRESS message containing a progress indicator IE specifying progress description #1, #2, 
or #64 prior to the CALL PROCEEDING message 

and enter the "mobile originating call proceeding" state. 

Abnormal case: 

If timer T310 elapses before any of the ALERTING, CONNECT or DISCONNECT messages has been received, 
the mobile station shall perform the clearing procedure described in subclause 5.4. 



Network 




Figure 5.3/3GPP TS 24.008 Call proceeding sequence at mobile originating call establishment 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 77 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.2.1 .4 Notification of progressing mobile originated call 

In this subclause, the term "inter working" is used only in the meaning of interworking with a network other than PLMN 
or ISDN, not as interworking between PLMN and ISDN since this is the normal case. In this sense, PLMN and ISDN 
are seen within the same environment, called the PLMN/ISDN environment. 

5.2.1 .4.1 Notification of interworking in connection with mobile originated call establishment 

During call establishment, the call may leave a PLMN/ISDN environment; e.g., because of interworking with another 
network, with a non-PLMN/ISDN user, or with non-PLMN/ISDN equipment within the called user's premises; the call 
may also return to a PLMN/ISDN environment. When such situations occur, the network may send a progress indicator 
information element to the calling mobile station either: 

a) in an appropriate call control message, if a state change is required (e.g. ALERTING or CONNECT); or, 

b) in the PROGRESS message, if no state change is appropriate. 

Th\s, progress /«(i/cflfor information element shall contain one of the following progress description values: 

a) #1 "call is not end-to-end PLMN/ISDN; further call progress information may be available in-band". 

b) #2 "destination address is non-PLMN/ISDN". 

c) #4 "call has returned to PLMN/ISDN. 

See also subclauses 5.5.1 and 5.5.6 for further reactions of the mobile station. 

5.2.1 .4.2 Call progress in the PLMN/ISDN environment 

In order to inform the mobile station that the call is progressing in the PLMN/ISDN environment the network may send 
a progress indicator information element to the calling mobile station either: 

a) in an appropriate call control message, if a state change is required (e.g., ALERTING or CONNECT); or 

b) in the PROGRESS message, if no state change is appropriate. 

This progress indicator information element shall contain progress description value #32 "Call is end-to-end 
ISDN/PLMN". See also subclause 5.5.6 for further reactions of the mobile station. 

5.2.1.5 Alerting 

Having entered the "mobile originating call proceeding" state, upon receiving an indication that user alerting has been 
initiated at the called address, the call control entity of the network shall: send an ALERTING message to its peer entity 
at the calling mobile station and enter the "call delivered" state. 

When the call control entity of the mobile station in the "call initiated" state or "mobile originating call proceeding" 
state receives an ALERTING message then, the call control entity of the mobile station shall stop timer T303 and T310 
(if running) and shall enter the "call delivered" state. In this state, for speech calls: 

an alerting indication should be given to the user. If the mobile station has not attached the user connection then 
the mobile station shall internally generate an alerting indication. If the mobile station has attached the user 
connection then the network is responsible for generating the alerting indication and the mobile station need not 
generate one. 

Abnormal cases: 

On the mobile station side, if timer T310 expires, the call control entity of the mobile station shall initiate call 
clearing as described in subclause 5.4. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 78 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 



Network 

+ 



Figure 5.4/3GPP TS 24.008 Call confirmation at mobile originating call establishment 

5.2.1.6 Call connected 

Upon receiving an indication that the call has been accepted, the call control entity of the network shall: through 
connect the traffic channel (including the connection of an interworking function, if required) and send a CONNECT 
message to its peer entity at the calling mobile station; start timer T313 and enter the "connect indication" state. 

This message indicates to the call control entity of the calling mobile station that a connection has been established 
through the network. 

The call control entity of the mobile station in the "call initiated" state, in the "mobile originating call proceeding" state 
or in the "call delivered" state, shall, upon receipt of a CONNECT message: 

attach the user connection; 

- return a CONNECT ACKNOWLEDGE message; 

- stop any locally generated alerting indication (if applied); 
stop timer T303 and T310 (if running); 

enter the "active" state. 

Abnormal cases: 

On the mobile station side, if timer T303 or T310 expires, the call control entity of the mobile station shall 
initiate call clearing as described in subclause 5.4. 

NOTE: The mobile station may have applied an additional internal alerting supervision which causes initiation of 
call clearing prior to the expiry of T303 or T3 10. 

The call control of the network in the "connect indication" state, shall, upon receipt of a CONNECT ACKNOWLEDGE 

message: 

stop timer T313 and enter the "active" state. 

Abnormal cases: 

On the network side, if timer T313 elapses before a CONNECT ACKNOWLEDGE message has been received, 
the network shall perform the clearing procedure as described in subclause 5.4. 

MS Network 

+ + 

CONNECT 
< 

CONNECT ACKNO¥LEDGE 
> 

+ + 

Figure 5.5/3GPP TS 24.008 Call acceptance sequence at mobile originating call establishment 

5.2.1.7 Call rejection 

Upon receiving an indication that the network or the called user is unable to accept the call, the network shall initiate 
call clearing at the radio interface to the mobile which originated the call, as described in subclause 5.4 using the cause 
provided by the terminating network or the called user. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 79 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.2.1 .8 Transit network selection 

NOTE: For further study. 

5.2.1 .9 Traffic channel assignment at mobile originating call establishment 

The mobile station supporting muhicall includes the Stream Identifier (SI) in the SETUP message. The multicall 
supporting network shall interprets the SI value as follows: 

a) Mobile station generates a new SI value at the initiation of an originating call, then a new traffic channel shall be 
assigned to the mobile originating call. 

b) Mobile station indicates an existing SI value, then the indicated traffic channel shall be used for the mobile 
originating call. 

Mobile station supporting multicall shall never send an additional SETUP with indication that a new traffic channel is 
requested to a network that does not support multicall. 

It is a network dependent decision when to initiate the assignment of an appropriate traffic channel during the mobile 
originating call establishment phase. Initiation of a suitable RR procedure to assign an appropriate traffic channel does 
neither change the state of a call control entity nor affect any call control timer. 

NOTE: During certain phases of such an RR procedure, transmission of CC and MM messages may be 
suspended, see 3GPP TS 44.018 [84], clause 3 and 3GPP TS 48.008 [85]. 

The assignment procedure does not affect any call control timer. 

5.2.1 .10 Call queuing at mobile originating call establishment 

If an idle traffic channel is not available at the assignment instant, the network may place the traffic channel request in a 
queue. Calls arriving when all positions in the queue are occupied shall be cleared by the network using the cause #34 
"no circuit/channel available". 

The maximum queuing interval is supervised by the network. The limit is a network dependent choice. In case the 
network is not able to allocate a traffic channel within the queuing limit, the network will release the call using cause 
#34 "no circuit/channel available". 

Optionally, e.g. if eMLPP is used, the network may decide to pre-empt existing calls or to place the traffic channel 
request at some preferential position within the queue. 

Specific indications provided in the network to the remote user are a network dependent choice. 

5.2.1 .1 1 Speech Codec Selection 

For speech calls, a mobile station implementing this version of the protocol shall indicate all codecs that it supports for 
UTRAN in the Supported Codec List information element. Codecs for GERAN shall be indicated in the Bearer 
Capability information element, if this information element is included. Additionally, if the mobile station supports 
codecs for GERAN and UTRAN, it shall indicate the codecs for GERAN also in the Supported Codec List information 
element. 

If the network does not receive a Supported Codec List information element then for speech calls in UTRAN it shall 
select the default UMTS speech codec. 

For speech calls in GERAN, if the network does not receive a Supported Codec List information element nor a Bearer 
Capability information element, the network shall select GSM full rate speech version 1. 

The network shall determine the default UMTS speech codec by the following: 

i) If no GSM Speech Version codepoints are received in the Supported Codec List IE or in octet 3a etc. of 

the Bearer Capabilities IE then a "UMTS only" terminal is assumed and the default UMTS speech codec 
shall be UMTS_AMR. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 80 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

ii) If at least one GSM Speech Version codepoint is received in the Supported Codec List IE or in octet 3a 

etc. of the Bearer Capabilities IE then the ME supports GSM and UMTS and the default UMTS speech 
codec shall be UMTS_AMR_2. 

NOTE 1 : In case (ii), if the call is set up in A/Gb or GERAN lu mode by a R99 ME, call control in the core 

network may treat the ME as a "GSM only" ME. The default UMTS speech codec will only become 
relevant when an intersystem handover to UTRAN lu mode is initiated by the radio access network, and 
can be determined when this procedure is started. 

If the Supported Codec List IE is received, then the network shall use this list to select the codec for lu mode and 
indicate the selected codec to the ME via RANAP and RRC protocol in the NAS Synchronisation Indicator IE. See 
3GPPTS 25.413, 3GPPTS 25.331 [32c] and 3GPPTS 44.118 [111]. 

The NAS Synchronisation Indicator IE shall be coded as the 4 least significant bits of the selected codec type (CoID) 
defined in 3GPP TS 26.103 [83] , subclause 6.3. 

The network shall determine the preference for the selected codec type; codec type prioritisation is not provided by the 
ME. 

The ME shall activate the codec type received in the NAS Synchrorusation Indicator IE. 

If the mobile station does not receive the NAS Synchronisation Indicator IE (RRC protocol) 

during setup of a speech call; 

during inter-system handover of a speech call from A/Gb or GERAN lu mode to UTRAN lu mode; or 

during an in-call modification from data to speech, 

then it shall select the UMTS_AMR_2 speech codec. 

NOTE 2: If the network does not support UMTS_AMR_2, it may activate the UMTS_AMR codec and indicate to 
the mobile station that it shall select UMTS_AMR_2. According to 3GPP TS 26.103 [83], subclause 5.4, 
no interworking problem will occur in this case. 

If the mobile station has selected a speech codec for UTRAN lu mode, it shall keep this codec until 

a new codec is requested by the network by sending a NAS Synchronisation Indicator IE (RRC protocol); 

a new codec is requested by the network during inter-system handover from UTRAN lu mode to A/Gb or 
GERAN lu mode; or 

an in-call modification from speech to data is performed. 

For adaptive multirate codec types no indication of subsets of modes is supported in this protocol, from the mobile 
station or to the mobile station. It is a pre-condition that the support of such codec types by the mobile station implicitly 
includes all modes defined for that codec type. 

5.2.1 .12 Cellular Text telephone Modem (CTM) selection 

The mobile station can send a CTM support indication in the Bearer Capability IE in call establishment messages to 
inform the network of the use of CTM text in the call. 

When the mobile station indicates speech and support of CTM text telephony, the network shall select a speech codec 
and additionally CTM text telephony detection/conversion functions as specified in 3GPP TS 23.226 [92] and 3GPP TS 
26.226 [93], if such functions are available. 

NOTE: If CTM support is indicated by the mobile station, then it supports CTM text telephony together with any 
supported speech codec and for any supported radio access. 

5.2.2 Mobile terminating call establishment 

Before call establishment can be initiated in the mobile station, the MM connection must be established by the network. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 81 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.2.2.1 Call indication 

After the arrival of a call from a remote user, the corresponding call control entity in the network shall: initiate the MM 
connection establishment according to clause 4 and enter the "MM connection pending" state. The request to establish 
the MM connection is passed from the CM sublayer to the MM sublayer. It contains the necessary routing information 
derived from the SETUP message. 

Upon completion of the MM connection, the call control entity of the network shall: send the SETUP message to its 
peer entity at the mobile station, start timer T303 and enter the "call present" state. 

The SETUP message shall contain the multicall supported information in the network call control capabilities in the 
case where the network supports multicall and there are no other ongoing calls to the MS. Mobile stations supporting 
multicall shall store this information until the call control state for all calls returns to null. Mobile stations not 
supporting multicall shall ignore this information if provided in a SETUP message. If the multicall supported 
information is not sent in the SETUP message, the mobile station supporting multicall shall regard that the network 
does not support multicall. 

Upon receipt of a SETUP message, the mobile station shall perform compatibility checking as described in 
subclause 5.2.2.2. If the result of the compatibility checking was compatibility, the call control entity of the mobile 
station shall enter the "call present" state. An incompatible mobile station shall respond with a RELEASE COMPLETE 
message in accordance with subclause 5.2.2.3.4. 

If there are no bearer capability lEs in the SETUP message, the network may provide information about the requested 
service in the backup bearer capability IE. 

If no response to the SETUP message is received by the call control entity of the network before the expiry of timer 
T303, the procedures described in subclause 5.2.2.3.3 shall apply. 

HS Network 
+ + 

SETUP 
< 

+ + 

CALL CONFIRMED (i) 

RELEASE COMPLETE (ii) 



Figure 5.6/3GPP TS 24.008 Mobile terminating call initiation and possible subsequent responses. 

5.2.2.2 Compatibility checking 

The mobile station receiving a SETUP message shall perform compatibility checking before responding to that SETUP 
message. Annex B defines compatibility checking to be performed by the mobile station upon receiving a SETUP 
message. For a backup bearer capability IE received with a SETUP message the mobile station shall not perform 
compatibility checking as described in annex B. 

5.2.2.3 Call confirmation 
5.2.2.3.1 Response to SETUP 

Having entered the "call present state" the call control entity of the mobile station shall - with the exception of the cases 
described below - acknowledge the SETUP message by a CALL CONFIRMED message, and enter the "mobile 
terminating call confirmed" state. 

If the mobile station supports multicall, it shall include the Stream Identifier (SI) information element in the CALL 
CONFIRMED message. 

If the mobile station is located in the network supporting multicall, it shall never include the SI that is in use and 
shall include with either of the following two values: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 82 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

- SI="no bearer"; 

SI=new value (not used by any of the existing bearers). 

If the mobile station supporting multicall is located in the network not supporting multicall, it shall include the SI with 
value 1. 

The call control entity of the mobile station may include in the CALL CONFIRMED message to the network one or 
two bearer capability information elements to the network, either preselected in the mobile station or corresponding to a 
service dependent directory number (see 3GPP TS 29.007 [38]). The mobile station may also use the backup bearer 
capability IE, if provided by the network, to deduce the requested service (see 3GPP TS 27.001, subclause 8.3.3.1). The 
mobile station may also include one or two bearer capabilities in the CALL CONFIRMED message to define the radio 
channel requirements. In any case the rules specified in subclause 9.3.2.2 shall be followed. 

NOTE: The possibility of alternative responses (e.g., in connection with supplementary services) is for further 
study. 

For speech calls the mobile station shall indicate all codecs that it supports for UTRAN in the Supported Codec List 
information element. Codecs for GERAN shall be indicated in the Bearer Capability information element, if this 
information element is included. Additionally, if the mobile station supports codecs for GERAN and UTRAN, it shall 
indicate the codecs for GERAN also in the Supported Codec List information element. 

If the MS supports the enhanced network-initiated in-call modification procedure as specified in subclause 5.3.4.3, the 
MS shall indicate this in the Call Control Capabilities IE in the CALL CONFIRMED message. 

A busy MS which satisfies the compatibility requirements indicated in the SETUP message shall respond either with a 
CALL CONFIRMED message if the call setup is allowed to continue or a RELEASE COMPLETE message if the call 
setup is not allowed to continue, both with cause #17 "user busy". 

If the mobile user wishes to refuse the call, a RELEASE COMPLETE message shall be sent with the cause #21 "call 
rejected". 

In the cases where the mobile station responds to a SETUP message with RELEASE COMPLETE message the mobile 
station shall release the MM connection and enter the "null" state after sending the RELEASE COMPLETE message. 

The network shall process the RELEASE COMPLETE message in accordance with subclause 5.4. 

5.2.2.3.2 Receipt of CALL CONFIRMED and ALERTING by the network 

The call control entity of the network in the "call present" state, shall, upon receipt of a CALL CONFIRMED message; 
stop timer T303, start timer T310 and enter the "mobile terminating call confirmed" state. 

In lu mode, network shall include the SI received in the CALL CONFIRMED message into the RABid and send it back 
to the mobile station. For RABid see 3GPP TS 25.413 and 3GPP TS 44.1 18 [1 1 1]. If the network receives the CALL 
CONFIRMED message with no SI, the network shall set the SI value to 1 . 

For speech calls, if the CALL CONFIRMED message contains a Supported Codec List information element, the 
network shall use this list to select the codec for UTRAN. If no Supported Codec List information element is received, 
then for UTRAN the network shall select the default UMTS speech codec according to subclause 5.2.1.1 1. 

Codecs for GERAN shall be selected from the codecs indicated in the Supported Codec List information element or in 
the Bearer Capability information element. If neither a Supported Codec List information element nor a Bearer 
Capability information element is received, then for GERAN the network shall select GSM full rate speech version 1. 

Codec information that does not apply to the currently serving radio access shall be used by the network if an inter- 
system change occurs. 

The call control entity of the mobile station having entered the "mobile terminating call confirmed" state, if the call is 
accepted at the called user side, the mobile station proceeds as described in subclause 5.2.2.5. Otherwise, if the signal 
information element was present in the SETUP message user alerting is initiated at the mobile station side; if the signal 
information element was not present in the SETUP message, user alerting is initiated when an appropriate channel is 
available. 

Here, initiation of user alerting means: 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 183 ETSI TS 124 008 V7.14.0 (2009-03) 

the generation of an appropriate tone or indication at the mobile station; and 

sending of an ALERTING message by the call control entity of the MS to its peer entity in the network and 
entering the "call received" state. 

The call control entity of the network in the "mobile terminated call confirmed" state shall, upon receipt of an 
ALERTING message: send a corresponding ALERTING indication to the calling user; stop timer T310; start timer 
T301, and enter the "call received" state. 

In the "mobile terminating call confirmed" state or the "call received" state, if the user of a mobile station is User 
Determined User Busy then a DISCONNECT message shall be sent with cause #17 "user busy". In the "mobile 
terminating call confirmed" state, if the user of a mobile station wishes to reject the call then a DISCONNECT message 
shall be sent with cause #21 "call rejected". 

5.2.2.3.3 Call failure procedures 

In case of abnormal behaviour the following call failure procedures apply: 

i. If the network does not receive any response to the SETUP message prior to the expiration of timer T303, then 
the network shall: initiate clearing procedures towards the calling user with cause #18 "no user responding"; and 
initiate clearing procedures towards the called mobile station in accordance with subclause 5.4.4 using cause 
#102 "recovery on timer expiry". 

ii. If the network has received a CALL CONFIRMED message, but does not receive an ALERTING, CONNECT 
or DISCONNECT message prior to the expiration of timer T310, then the network shall: 

initiate clearing procedures towards the calling user with cause #18 "no user responding"; and 

initiate clearing procedures towards the called MS in accordance with subclause 5.4.4 using cause #102 
"recovery on timer expiry" . 

iii. If the network has received an ALERTING message, but does not receive a CONNECT or DISCONNECT 

message prior to the expiry of timer T301 (or a corresponding internal alerting supervision timing function), then 
the network shall: initiate clearing procedures towards the calling user with cause #19 "user alerting, no answer"; 
and initiate clearing procedures towards the called mobile station in accordance with subclause 5.4.4, using 
cause #102 "recovery on timer expiry" or using cause #31 "normal, unspecified". 

NOTE: The choice between cause #31 and cause #102 may have consequences on indications generated by the 
mobile station, see 3GPP TS 22.001 [8a]. 

5.2.2.3.4 Called mobile station clearing during mobile terminating call establishment 

See subclause 5.4.2. 

5.2.2.4 Notification of interworking in connection with mobile terminating call 

establishment 

In this subclause, the term "interworking" is used only in the meaning of interworking with a network other than PLMN 
or ISDN, not as interworking between PLMN and ISDN since this is the normal case. In this sense, PLMN and ISDN 
are seen within the same environment, called the PLMN/ISDN environment. 

During call establishment the call may enter an PLMN/ISDN environment, e.g., because of interworking with another 
network, with a non-PLMN/ISDN user, or with non-PLMN/ISDN equipment within the calling or called user's 
premises. When this occurs, the network may include a progress indicator information element to be included in the 
SETUP message to be sent to the called mobile station specifying progress description value: 

a) #1 "call is not end-to-end PLMN/ISDN; further call progress information may be available in-band" or 

b) #3 "origination address is non-PLMN/ISDN". 

See also subclause 5.5.1 for further reactions of the mobile station. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 84 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.2.2.5 Call accept 

In the "mobile terminating call confirmed" state or the "call received" state, the call control entity in the mobile station 
indicates acceptance of a mobile terminating call by: 

sending a CONNECT message to its peer entity in the network; 

starting Timer T3 1 3 ; and 

entering the "connect request" state. 

If the call control entity of the mobile station has indicated "No Bearer" as the SI value in the CALL CONFIRMED 
message, it shall assign the SI value and include the SI information element in the CONNECT message. Otherwise the 
SI information element shall not be included in the CONNECT message. 

5.2.2.6 Active indication 

In the "mobile terminated call confirmed" state or in the "call received" state, the call control entity of the network shall, 
upon receipt of a CONNECT message: through connect the traffic channel (including the connection of an interworking 
function, if required), stop timers T310, T303 or T301 (if running); send a CONNECT ACKNOWLEDGE message to 
its peer entity at the mobile station of the called user; initiate procedures to send a CONNECT message towards the 
calling user and enter the "active" state. 

In the "connect request" state, the call control entity of the mobile station shall, upon receipt of a CONNECT 
ACKNOWLEDGE message: stop timer T313 and enter the "active" state. 

When timer T313 expires prior to the receipt of a CONNECT ACKNOWLEDGE message, the mobile station shall 
initiate clearing in accordance with subclause 5.4.3. 

US Network 

+ + 

CONNECT 
> 

CONNECT ACKNOWLEDGE 

< 

+ + 

Figure 5.7/3GPP TS 24.008 Call acceptance and active indication at mobile terminating call 

establishment 

5.2.2.7 Traffic channel assignment at mobile terminating call establishment 

After receiving the SETUP message, the mobile station supporting multicall may either require a new traffic channel or 
reuse an existing traffic channel. 

If a mobile station in the network supporting multicall requires a new traffic channel, it shall: 

send a CALL CONFIRMED message including the SI indicating a new value, not used by any of the existing 
traffic channels. 

If a mobile station in the network supporting multicall does not require a new traffic channel, it shall: 

send a CALL CONFIRMED message including the SI equal to "no bearer". 

After the mobile station has send the CALL CONFIRMED with SI="no bearer", the SI value in the CONNECT 
message will tell to the network if a user requests a new traffic channel or one of the existing ones will be re-uesd. 

If a new traffic channel is requested by the user, the mobile station in the network supporting multicall shall: 

send a CONNECT message containing the SI with a new value, not used by any existing traffic channel. 

If the user decides that an existing traffic channel will be reused, the mobile station in the network supporting multicall 
shall: 

send a CONNECT message with an SI indicating an existing value used by an existing traffic channel. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 85 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

It is a network dependent decision when to initiate the assignment of a traffic channel during the mobile terminating call 
establishment phase. 

Initiation of the assignment phase does not directly change the state of a CC entity nor affect any call control timer, but 
may have some secondary effects (see e.g. clause 5.2.2.3.2). 

5.2.2.8 Call queuing at mobile terminating call establishment 

The principles described in subclause 5.2.1.10 apply accordingly. 

NOTE: The interworking to the fixed network has to fulfil the network specific requirements. 

5.2.2.9 User connection attachment during a mobile terminating call 

For speech calls: 

The mobile station shall attach the user connection at latest when sending the connect message. 

For data calls: 

The mobile station shall attach the user connection when receiving the CONNECT ACKNOWLEDGE message 
from the network. 

5.2.2.1 Speech Codec Selection 

The principles described in section 5.2.1.11 apply accordingly. 

5.2.2.1 1 Cellular Text telephone Modem (CTM) selection 

The principles described in subclause 5.2.1.12 apply accordingly. 

5.2.3 Network initiated MO call $(CCBS)$ 

The procedures of subclause 5.2.3 are mandatory for mobile stations supporting "Network initiated MO call". 

NOTE: The behaviour of a mobile station that does not support "Network initiated MO call" is described in 
clause 4. 

5.2.3.1 Initiation 

Before call establishment can be initiated in the mobile station, the MM connection shall be established by the network. 

After the arrival of an appropriate stimulus (for example a Remote User Free Indication), the corresponding call control 
entity in the network shall initiate the MM connection establishment according to clause 4, enter the "CC connection 
pending" state and start timer T331. The request to establish the MM connection is passed from the CM sublayer to the 
MM sublayer. It contains the necessary routing information derived from the received stimulus. 

Upon completion of the MM connection, the call control entity of the mobile station shall send a START CC message 
to its peer entity in the network. The mobile station shall then enter the "Wait for network information" state and start 
timer T332. 

If the network receives a START CC message while in the "CC connection pending" state, the network stops T33 1 , 
sends the CC-ESTABLISHMENT message, starts timer T333 and enters the "CC -establishment present" state. 

The MM connection establishment may be unsuccessful for a variety of reasons, in which case the MM sublayer in the 
network will inform the CC entity in the network with an indication of the reason for the failure. The CC entity shall 
then stop all running timers, enter the "Null" state and inform all appropriate entities within the network. 

If timer T331 expires, the network shall abort the MM connection establishment attempt, stop all running CC timers, 
enter the "Null" state and inform all appropriate entities within the network. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 86 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.2.3.2 CC-Establishment present 

In the "CC establishment present" state, the mobile station, upon receipt of the CC-ESTABLISHMENT message, shall 
stop timer T332. 

The CC-ESTABLISHMENT message contains information which the mobile station shall use for the subsequent 
SETUP message (if any) related to this CC-ESTABLISHMENT. 

The CC-ESTABLISHMENT message shall contain the Setup Container IE. 

If no CC-ESTABLISHMENT message is received by the call control entity of the mobile station before the expiry of 
timer T332, then the mobile station shall initiate clearing procedures towards the network using a RELEASE 
COMPLETE message with cause #102 "recovery on timer expiry" and proceed in accordance with subclause 5.4.2. 

Upon receipt of a CC-ESTABLISHMENT message the mobile station shall perform checks on the Setup Container IE 
in order to align the contained information with the mobile's present capabilities and configuration. The "recall 
alignment procedure" is defined later on in this subclause. 

If the recall alignment procedure has succeeded, the call control entity of the Mobile Station shall: 
form and store the SETUP message for sending later in the "Recall present" state, 
- acknowledge the CC-ESTABLISHMENT message with a CC-ESTABLISHMENT CONFIRMED message, 
start timer T335, and 
enter the "CC-establishment confirmed" state. 

Exception: 

A busy mobile station which has successfully performed the recall alignment procedure shall respond with a CC- 
ESTABLISHMENT CONFIRMED message with cause #17 "user busy", and proceed as stated above. 

For speech calls the mobile station shall indicate all codecs that it supports for UTRAN in the Supported Codec List 
information element of the CC-ESTABLISHMENT CONFIRMED message. Codecs for GERAN shall be indicated in 
the Bearer Capability information element. Additionally, if the mobile station supports codecs for GERAN and 
UTRAN, it shall indicate the codecs for GERAN also in the Supported Codec List information element. 

A mobile station, for which the recall alignment procedure failed, shall respond with a RELEASE COMPLETE 
message in accordance with subclause 5.4.2 with the appropriate cause code as indicated in the description of the recall 
alignment procedure. 

The SETUP message is constructed from the Setup Container IE received in the CC ESTABLISHMENT MESSAGE. 
The mobile station shall assume that the Setup Container IE contains an entire SETUP message with the exception of 
the Protocol Discriminator, Transaction ID and Message Type elements. The mobile station may assume that the 
contents of the Setup Container IE are the same as were sent from the subscriber in a previous SETUP message of the 
mobile originating call establishment attempt. The mobile station shall copy the Setup Container to the SETUP message 
and not modify the contents except as defined in the recall alignment procedure and as defined in exceptions below. The 
mobile station shall not add other Information Elements to the end of the SETUP message. 

Exceptions: 

Bearer Capability IE(s), HLC IE(s) and LLC IE(s) (including Repeat Indicator(s), if there are 2 bearer 
capabilities), and the Supported Codec List IE require handling as described in the recall alignment procedure 
below. 

If the CC Capabilities in the Setup Container IE is different to that supported by the mobile station, the mobile 
station shall modify the CC Capabilities in the SETUP message to indicate the true capabilities of the mobile 
station. 

Facility IE(s) and SS Version IE(s) require handling as described in the recall alignment procedure. 

Stream Identifier IE requires handling as described in the recall alignment procedure. 

If no response to the CC-ESTABLISHMENT message is received by the call control entity of the network before the 
expiry of timer T333, then the network shall initiate clearing procedures towards the called mobile station using a 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 87 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

RELEASE COMPLETE message with cause #102 "recovery on timer expiry" and inform all appropriate entities within 
the network, proceeding in accordance with subclause 5.4.2. 

MS Network 
+ + 

CC-E3TABLISHHENT 
< 

CC-ESTABLI3HHENT CONFIRMED (i) 

RELEASE COHPLETE (n) 

+ + 

Figure 5.7a/3GPP TS 24.008 Call initiation and possible subsequent responses. 

5.2.3.2.1 Recall Alignment Procedure 

The recall alignment procedure consists of three parts: 

basic service group alignment, 

facility alignment, and 

stream identifier alignment. 

Basic service group alignment: 

The mobile station shall check that the Bearer Capability, HLC and LLC and Repeat Indicator fields, which are 
embedded in the Setup Container IE, match a basic service group supported by the mobile station. 

If this check fails, then the recall alignment procedure has failed. The mobile station shall use the cause #88 
"incompatible destination" afterwards. 

Otherwise, the mobile station is allowed to alter the content within the Bearer Capability, HLC and LLC Information 
Elements (e.g. the speech codec version(s), the data rate, the radio channel requirement) provided that the basic service 
group is not changed. Furthermore, for speech calls the mobile station is allowed to add or remove the Supported Codec 
List Information Element, or to alter the contents of this information element dependent on the codecs supported by the 
mobile station. The result shall be that the mobile station has derived Bearer Capability, HLC, LLC, and Supported 
Codec List Information Elements, which it can use for a later call setup according to its configuration and capabilities. 

Facility alignment: 

This only applies if the Setup Container contains 1 or more Facility IBs. Each Facility IE within the Setup 
Container will be associated with the common SS Version IE, if present. The handling for each Facility IE is 
defined below. The mobile station shall align each facility IE contained in the Setup Container. The rules defined 
in 3GPP TS 24.010 also apply. 

The Facility IE is encoded as 'simple recall alignment', 'advanced recall alignment' or 'recall alignment not essential' 
(see 3GPP TS 24.010). If the encoding indicates, that 

a simple recall alignment is required, the mobile station shall copy the Facility IE and the common SS version IE 
from the Setup Container to the SETUP message without modifying the content. 

an advanced recall alignment is required, the mobile station must recognise and support the operation defined in 
the facility. If the mobile station does not recognise or support the operation, then the recall alignment procedure 
has failed and the mobile station shall use the cause #29 "facility rejected" in the subsequent rejection of the CC 
establishment request. 

the recall alignment is not essential, then the facility operation is not an essential part of the SETUP. If the MS 
does not recognise the operation then the SS Version IE and Facility IE are discarded, and NOT copied into the 
SETUP message. 

NOTE: A mobile station may include a Facility IE without an associated SS Version IE. This would indicate that 
the SS operation is encoded using Phase 1 protocols. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 88 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

Further details on Facility handling are given in 3GPP TS 24.010. 

Stream identifier alignment: 

The mobile station shall check whether the Stream Identifier field is contained in the Setup Container or nof. 

If the Stream Identifier is contained in the Setup Container, the mobile station shall behave as one of the following. 

the mobile station re-assign the Stream Identifier value, and modify the Stream Identifier field. 

the mobile station remove the Stream Identifier field. 
If the Stream Identifier is not contained in the Setup Container, the mobile station may behave as follows. 

the mobile station assign the Stream Identifier value, and add the Stream Identifier IE to the end of the SETUP 

message. 

5.2.3.3 CC-Establishment confirmation 

The call control entity of the network in the "CC -establishment present" state, shall, upon receipt of a CC- 
ESTABLISHMENT CONFIRMED message, stop timer T333 and enter the "CC-estabhshment confirmed" state. 

For speech calls, if the ESTABLISHMENT CONFIRMED message contains a Supported Codec List information 
element, the network shall use this list to select the codec for UMTS. If no Supported Codec List information element is 
received, then for UMTS the network shall select the default UMTS speech codec according to subclause 5. 2. 1.11. 

Codecs for GERAN shall be selected from the codecs indicated in the Supported Codec List information element or in 
the Bearer Capability information element. If neither a Supported Codec List information element nor a Bearer 
Capability information element is received, then for GERAN the network shall select GSM full rate speech version 1. 

Codec information that does not apply to the currently serving radio access shall be used by the network if an inter- 
system change occurs. 

In the "CC-establishment confirmed" state, the network sends a RECALL message. This message initiates user alerting 
and also shall include the Facility IE (providing additional information to be presented to the user for notification). The 
network starts timer T334 and enters the 'recall present' state. 

Upon reception of the RECALL message the Mobile station stops T335 and enters the "recall present" state. 



Network 

+ 



Figure 5.7b/3GPP TS 24.008 Recall 



5.2.3.4 Recall present 



In the "recall present" state, the call control entity in the mobile station waits for acceptance of the Recall by the user. 
Once confirmation is received, the mobile station indicates acceptance of a recall by 

sending a SETUP message to its peer entity in the network; 

starting Timer T303; and 

entering the "call initiated" state and proceeding as described in subclause 5.2.1.1. 

The MS shall ensure that the contents of the Bearer Capability IE(s) and Supported Codec List IE sent in the SETUP 
message are the same as the Bearer Capability IE(s) and Supported Codec List IE in the previous CC- 
ESTABLISHMENT CONFIRMED message related to this Network Initiated MO Call. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 89 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

In the "recall-present" state, if the user of a mobile station is User Determined User Busy then a RELEASE 
COMPLETE message shall be sent with cause #17 "user busy" In the "recall-present" state. If the user of a mobile 
station wishes to reject the recall then a RELEASE COMPLETE message shall be sent with cause #21 "call rejected". 

In either case, the mobile shall release the connection in accordance with subclause 5.4.2 

On receipt of the SETUP message in the "recall present" state, the network shall stop timer T334 and proceed as 
specified in subclause 5.2.1.2. 

If the call control entity of the network does not receive a SETUP message before the expiry of timer T334, then the 
network shall send a RELEASE COMPLETE message to the mobile using cause #102 "recovery on timer expiry", 
release the MM connection, enter the "null" state and shall inform all appropriate entities within the network. 

MS Network 
+ + 

SETUP I 
> 



RELEASE COMPLETE 
> I 



- + 
Figure 5.7b/3GPP TS 24.008 Recall acceptance or rejection by user 

5.2.3.5 Traffic channel assignment during network initiated mobile originating call 

establishment 

It is a network dependent decision whether or not to initiate the assignment of a traffic channel during the "CC- 
establishment confirmed" state. 

5.3 Signalling procedures during the "active" state 

5.3.1 User notification procedure 

The mobile terminating user notification procedure allows the network to notify a mobile station of any appropriate 
call-related event during the "active" state of a call. The procedure consists in the network sending a NOTIFY message 
to the mobile station. No state change occurs at any of the interface sides following the sending or the receipt of this 
message (but an appropriate indication may optionally be generated in the mobile station). 

The mobile originating notification procedure allows the mobile station to notify the remote user of any appropriate 
call-related event during the "active" state of a call by sending a NOTIFY message containing a notification indicator to 
the network; upon receipt of this message, the network sends a NOTIFY message containing the same notify indicator 
to the other user involved in the call. No state change occurs at any of the interface sides following the sending or the 
receipt of this message. 

5.3.2 Call rearrangements 

Call rearrangements on the radio interface are not supported by explicit messages (e.g. SUSPEND and RESUME 
messages as defined in ETS 300 102-1 [70]). However if a remote non-PLMN user initiates call rearrangements, the 
network shall inform the mobile station by means of a NOTIFY message. In a similar way the mobile station can inform 
the network about rearrangements by sending a NOTIFY message (e.g. change of user equipment connected to the 
mobile station). 

5.3.3 Codec Change Procedure 

During a speech call in UMTS, if a mobile station supports more than one UMTS codec, the network can change the 
UMTS codec via RRC procedures. In order to request the mobile station to change the codec, the network shall send the 
new selected codec type in the NAS Synchronisation Indicator IE (RRC protocol), see subclause 5.2.1.11. 



ETSI 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 90 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 



5.3.4 Support of Dual Services 



The behaviour described in this subclause is used to reahze the following required services throughout subclause 5.3.4. 
The mobile station is not obliged to support the network originated in-call modification procedure. In that case, the 
mobile station shall, when receiving a MODIFY message, treat the message as unknown and react as described in 
subclause 8.4. If the mobile station is already prepared to support the procedure in both directions, it shall act as 
described in this subclause. 

Alternate Speech/Group 3 fax (Teleservice 61 according to 3GPP TS 22.003 [4]). 

5.3.4.1 Service Description 

This circuit switched service allows the two users on a point-to-point connection to use the connection between them 
for different information transfer during the same call, but not at the same time. 

If the negotiation during call establishment leads to the recognition of the above mentioned services, the in-call 
modification procedure is allowed to be executed within the current call by changing from one call mode to the other. 

In some cases the in-call modification procedure makes it necessary to change the channel configuration by allocating a 
new channel and in other cases to change channel configuration parameters while keeping the previously allocated 
channel. This change is determined by the network, which initiates either the channel assignment procedure, handover 
procedure or channel mode modify procedure (see clause 3). 

The capability and the initial mode desired must be identified by the mobile station by identifying each mode of 
operation with a separate information element during call establishment. Further the type of change between the modes 
must be identified by means of the repeat indicator: 

mode 1 "alternate" mode 2. 

5.3.4.2 Call establishment 

For both mobile originating and mobile terminating calls, the normal call establishment procedures apply. 

5.3.4.2.1 Mobile Originating Establishment 

The service is requested by the originating mobile station by transferring a SETUP message to the network containing 
the BC repeat indicator IE, the bearer capability 1 information element, and the bearer capability 2 information 
element. The first mode of operation ("call mode") shall be indicated by the bearer capability 1 information element 
and the second call mode by the bearer capability 2 information element. 

A low layer compatibility may optionally be specified for each call mode in a low layer compatibility I and low layer 
compatibility //information element. In that case: 

the SETUP message shall contain the LLC repeat indicator IE and both low layer compatibility I and low layer 
compatibility II information elements. The low layer compatibility I information element then corresponds to the 
bearer capability 1 information element and the low layer compatibility II information element to the bearer 
capability 2 information element; 

if no low layer compatibility specification applies for one of the two call modes, the corresponding low layer 
compatibility IE {low layer compatibility I or low layer compatibility II) shall indicate "not applicable"; 

the LLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE. 

Similarly, a high layer compatibility may optionally be specified for each call mode in a high layer compatibility i and 
high layer compatibility ii information element. In that case: 

the SETUP message shall contain the HLC repeat indicator IE and both high layer compatibility i and high layer 
compatibility ii information elements. The high layer compatibility i information element then corresponds to the 
bearer capability 1 information element and the high layer compatibility ii information element to the bearer 
capability 2 information element; 

if no high layer compatibility specification applies for one of the two call modes, the corresponding high layer 
compatibility IE {high layer compatibility i or high layer compatibility ii) shall indicate "not applicable"; 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 91 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

the HLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE. 

The receiving entity shall ignore whether the LLC repeat indicator IE or HLC repeat indicator are contained in the 
message or not; it shall also ignore the repeat indication of an LLC repeat indicator IE or HLC repeat indicator IE. If 
the low layer compatibility II IE is not contained in the message and the low layer compatibility I IE is contained in the 
message, the receiving entity shall relate it to a call mode indicated in the message that does not specify speech (if any). 
If the high layer compatibility ii IE is not contained in the message and the high layer compatibility i IE is contained in 
the message, the receiving entity shall relate it to a call mode indicated in the message that does not specify speech (if 
any). 

The specific part of the network which is sensitive to the call mode shall examine each mode described in the bearer 
capabilities included in the SETUP message by performing compatibility checking as defined in Annex B. If as a result 
of this compatibility checking the network decides to reject the call, then the network shall initiate call clearing as 
specified in subclause 5.4 with the following causes: 

a) #57 "bearer capability not authorized"; 

b) #58 "bearer capability not presently available"; 

c) #65 "bearer service not implemented"; 

d) #70 "only restricted digital information bearer capability is available". 

5.3.4.2.2 Mobile Terminating Establishment 

The service is indicated to the called mobile station by a SETUP message coded in the same manner as in the mobile 
originating call establishment. As specified for normal terminating call establishment, the service may be indicated by 
the called mobile station in the CALL CONFIRMED message. 

The destination mobile station shall perform the compatibility checking as defined in Annex B for both required modes 
if indicated in the SETUP message. If as a result of compatibility checking the mobile station decides to reject the call, 
the mobile station shall initiate call clearing according to the procedures of subclause 5.4 with one of the following 

causes: 

a) #57 "bearer capability not authorized"; 

b) #58 "bearer capability not presently available"; 

c) #65 "bearer service not implemented"; 

d) #88 "incompatible destination". 

The mobile station may accept the call if the first mode indicated is free irrespective of whether the other mode is free 
or busy. 

5.3.4.3 Changing the Call Mode 

In order to change the call mode, the following in-call modification procedures shall be used. 

Either side of the radio interface may act as the requesting user to invoke the in-call modification. 

Upon each successful completion of the in-call modification procedure, the call changes to the next mode negotiated 
and agreed during the establishment phase of the call. 

The in-call modification procedures are completely symmetrical at the radio interface. 

5.3.4.3.1 Initiation of in-call modification 

The procedure is initiated by the requesting originating side in the "active" state of the call. It shall send a MODIFY 
message including the new mode to be changed to. The requesting originating side shall also start timer T323 and enter 
the "mobile originating modify" state (mobile station side) or the "mobile terminating modify" state (network side). The 
new mode given in the MODIFY message shall be one of those already negotiated and agreed during the establishment 
phase of the call. If the data call direction is different from the direction of the call setup a reverse call setup direction IE 
shall be included in the MODIFY message; otherwise this IE shall not be included. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 92 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the in-call modification is originated by the mobile station, the mobile station shall reserve any internal resources 
necessary to support the next call mode, stop sending Bm-channel information; and stop interpreting received Bm- 
channel information according to the old call mode. 

If the in-call modification is originated by the network, the network may reserve any internal resources necessary to 
support the next call mode. The network shall stop sending Bm-channel information and stop interpreting received Bm- 
channel information according to the old call mode at the latest when it changes the channel configuration. 

Upon receipt of the MODIFY message, the destination side shall check to ensure that the requested call mode can still 
be supported and if so, it shall initiate the reservation of any resources necessary to support the next call mode; start 
T324 (mobile station side only) if the in-call modification procedure is triggered as a result of a service change from 
speech to UDI/RDI multimedia modes; and enter the "mobile originating modify" (network side) or "mobile terminating 
modify" state (mobile station side). 

5.3.4.3.2 Successful completion of in-call modification 

If the destination network/mobile station receives a MODIFY message with a new mode which is already the actual one 
of the call the network/mobile station shall remain in the "active" state; send a MODIFY COMPLETE message with the 
actual mode; and shall not initiate anything else. 

If the requested mode is speech and if during call establishment the network received a Supported Codec List IE, the 
network shall use this list to select the codec for UTRAN. If no Supported Codec List information element is received, 
then for UTRAN the network shall select the default UMTS speech codec according to subclause 5. 2. 1.11. 

Codecs for GERAN shall be selected from the codecs indicated in the Supported Codec List information element or in 
the Bearer Capability information element. If neither a Supported Codec List information element nor a Bearer 
Capability information element is received, then for GERAN the network shall select GSM full rate speech version 1. 

If the Supported Codec List IE is received, then the network shall indicate the codec selected for lu mode to the mobile 
station via RANAP and RRC protocol in the NAS Synchronisation Indicator IE (see subclause 5. 2. 1.11). 

If the in-call modification was originated by the mobile station, the mobile station and the network shall proceed as 
follows: 

If the requested mode is not the actual one and can be supported by the network it shall change the channel 
configuration, if required, and step on to any internal resources necessary to support the next call mode. If the 
requested mode is a data or facsimile mode, it shall also perform the appropriate means to take the direction of 
the data call into account. After successful change of the channel configuration it shall start sending user 
information according to the next call mode and start interpreting received user channel information according to 
the next call mode; send a MODIFY COMPLETE message with the new call mode included and enter the 
"active" state (network side). If the MODIFY message had contained a reverse call setup direction IE, the same 
IE shall be included in the MODIFY COMPLETE message. 

Upon receipt of the MODIFY COMPLETE message the mobile station shall: initiate the alternation to those 
resources necessary to support the next call mode; stop timer T323; and enter the "active" state (mobile station 
side). 

If the in-call modification was originated by the network, the mobile station and the network shall proceed as follows: 

If the requested mode is not the actual one and can be supported by the mobile station it shall reserve any 
internal resources necessary to support the next call mode. 

NOTE: For a change from speech to a different call mode, user interaction may be required, before the mobile 
decides that the requested mode can be supported. 

If the requested mode is a data or facsimile mode, it shall also perform the appropriate means to take the 
direction of the data call into account. The mobile station shall send a MODIFY COMPLETE message with the 
new call mode included, stop timer T324 and enter the "active" state (mobile station side). If the MODIFY 
message had contained a reverse call setup direction IE, the same IE shall be included in the MODIFY 
COMPLETE message. If the old call mode is speech, the mobile station shall continue sending Bm-channel 
information and interpreting received Bm-channel information for speech until the network modifies its channel 
configuration. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 93 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

After receipt of the MODIFY COMPLETE message the network shall: reserve any internal resources necessary 
to support the next call mode, stop sending Bm-channel information, and stop interpreting received Bm-channel 
information according to the old call mode, unless these actions were already performed earlier. Furthermore, the 
network shall change the channel configuration, if required; after successful change of the channel configuration 
initiate the alternation to those resources necessary to support the next call mode; stop timer T323; and enter the 
"active" state (network side). 

The mobile station shall start sending user information according to the next call mode and start interpreting 
received user channel information according to the next call mode as soon as a suitable channel for the new 
mode is available. 

In both cases: 

For an alternate speech/facsimile group 3 service (refer to subclause 5.3.4) the old resources may still be kept 
reserved. 

The reaction of the originating side if it had included a reverse call setup direction IE in the MODIFY message, 
but the destination side did not include the IE in the MODIFY COMPLETE message is implementation 
dependent. 

5.3.4.3.3 Change of the channel configuration 

In case the requested bearer capability cannot be supported by the current channel configuration the network shall 
initiate the assignment procedure and change the channel configuration accordingly. 

5.3.4.3.4 Failure of in-call modification 

5.3.4.3.4.1 Network rejection of in-call modification 

If the network cannot support the change to the requested call mode or if the change of the channel configuration fails 
the network shall: release the resources which had been reserved for the alternation: send a MODIFY REJECT message 
with the old bearer capability and with cause # 58 "bearer capability not presently available" to the initiating mobile 
station; and enter the "active" state. If the change of the channel configuration fails, the network shall return to the 
internal resources required for the old call mode. 

Upon receipt of the MODIFY REJECT message with the old bearer capability the initiating mobile station shall: stop 
timer T323; release any resources which had been reserved for the alternation; resume sending user channel information 
according to the present call mode; resume interpreting received user channel information according to the present call 
mode; and enter the "active" state. 

5.3.4.3.4.2 Mobile station rejection of in-call modification 

If the mobile station cannot support the change to the requested call mode, the mobile station shall: stop timer T324; 
release any resources which had been reserved for the alternation; send a MODIFY REJECT message with the old 
bearer capability and cause # 58 "bearer capability not presently available", and enter the "active" state. 

Upon receipt of the MODIFY REJECT message the network shall: stop timer T323, release any resources which had 
been reserved for the alternation. 

5.3.4.3.4.3 Time-out recovery 

Upon expiration of T323 in either the mobile station or the network the procedures for call clearing shall be initiated 
(see subclause 5.4) with cause #102 "recovery on timer expiry". 

Upon expiration of T324 the mobile station shall: release any resources which had been reserved for the alternation; 
send a MODIFY REJECT message with the old bearer capability and cause #58 "bearer capability not presently 
available"; and enter the "active" state. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



194 



ETSI TS 124 008 V7.14.0 (2009-03) 



5.3.4.4 



Abnormal procedures 



If a MODIFY, MODIFY COMPLETE or MODIFY REJECT message is received in the "disconnect indication", 
"disconnect request" (mobile station side only) or "release request" state then the received message shall be discarded 
and no action shall be taken. 

If a MODIFY COMPLETE message indicating a call mode which does not correspond to the requested one is received 
or if a MODIFY REJECT message indicating a call mode which does not correspond to the actual one is received then 
the received message shall be discarded and no action shall be taken. 

If a MODIFY message indicating a call mode which does not belong to those negotiated and agreed during the 
establishment phase of the call, is received, then a MODIFY REJECT message with the actual call mode and with cause 
# 57 "bearer capability not authorized" shall be sent back. 



MS 



Network 

+ 



+ 

HOD 
> 



assignment or channel mode modify 
HOD COHP 
HOD RE J 



- + 



Figure 5.10a/3GPP TS 24.008 In-call modification sequence initiated by lUIS 



HS 



Network 



HOD 

HOD COHP 

HOD RE J 



< 

> 

-> 



assignment or channel mode modify 
+ 



5.3.5 



Figure 5.10b/3GPP TS 24.008 In-call modification sequence initiated by network 

User initiated service level up- and downgrading (A/Gb mode and 
GERAN lu mode only) 



The user initiated service level up- and downgrading is applicable for non-transparent multislot data services, only. By 
means of this procedure the user can request a change of the "maximum number of traffic channels" and/or "wanted air 
interface user rate" parameters, to be assigned by the network. 

5.3.5.1 Initiation of service level up- and downgrading 

The procedure is initiated by the mobile station in the "active" state of the call. It shall: 

send a MODIFY message including the wanted value of the "maximum number of traffic channels" and/or the 
"wanted air interface user rate" parameters; 

not change any of the other, possibly negotiated, parameters of the bearer capability information element; 

start timer T323; and 

enter the "mobile originating modify" state. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 95 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

Any internal resources necessary to support the next service parameters shall be reserved. If a dual service was 
negotiated at call setup, the mobile station shall initiate the service level up- or down-grading only during the data phase 
of the dual service. 

Upon receipt of the MODIFY message, the network shall check if the indicated maximum number of traffic channels 
can be supported and enter the "mobile originating modify" state. 

5.3.5.2 Successful completion of service level up- and downgrading 

The network may upon reception of the MODIFY message initiate a change of the channel configuration assigned to 
the mobile station. 

As a response to the MODIFY message the network sends a MODIFY COMPLETE message including the bearer 
capability negotiated at call setup and enters the "active" state. 

Upon receipt of the MODIFY COMPLETE message the mobile station shall stop timer T323 and enter the "active" 
state. 

5.3.5.3 Rejection of service level up- and downgrading 

If a change of bearer service is requested together with a change of the "maximum number of traffic channels" and/or 
the "wanted air interface user rate", or if the current used service is not a data service where up- and downgrading is 
applicable, or if the receiver chooses not to grant the request, the network shall: 

send a MODIFY REJECT message with bearer capability negotiated at call setup and with cause #58 "bearer 
capability not presently available"; 

enter the "active" state. 

Upon receipt of the MODIFY REJECT message with the bearer capability negotiated at call setup, the mobile station 
shall: stop timer T323 and enter the "active" state. 

5.3.5.4 Time-out recovery 

Upon expiration of T323 in the mobile station the procedures for call clearing shall be initiated with cause #102 
"recovery on timer expiry". 

5.3.6 Support of multimedia calls 

5.3.6.1 Service description 

The 3GPP circuit-switched multimedia call is based on the 3G-324M [26. Ill], which is a 3GPP-variant of the ITU-T 
H.324 recommendation. CS Multimedia telephony is a Bearer Service, which utilizes the Synchronous Transparent 
Data service (BS30) [3]. 

At the multimedia call setup the required call type, 3G-324M, is indicated, for the network to be able to invoke 
appropriate interworking functionality. In the peer end the H.324 information is used to invoke the terminal application. 
In addition to H.324 indication the terminal must select Information Transfer Capability (ITC) for the multimedia call. 
The 'correct' ITC depends on the peer end and the transporting networks; an all-ISDN call is a UDI/RDI call, and a call, 
which involves PSTN, is an analog "3.1 kHz audio" call. 

For the case when the setup of a multimedia call is not successful, fallback to speech is specified. 

Users may also request a service change between UDI/RDI multimedia and speech modes during a call (see 3GPP TS 
23.172 [97]). 

5.3.6.2 Call establishment 

For both mobile originating and mobile terminating calls, the normal call establishment procedures apply, with the 
exceptions specified in the following subclauses. 

For further description of the function of MSC/IWF in the following clauses, see 3GPP TS 29.007 [38]. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 96 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.3.6.2.1 Mobile originated multimedia call establishment 

At call setup the required call type, 3G-324M, is indicated by the originating MS in the SETUP message, with the 
bearer capability IE parameter Other Rate Adaptation set to "H.223 and H.245". 

For analogue multimedia, the support of a fallback to speech is requested by including two bearer capability lEs, 
multimedia first and speech as the second BC in the SETUP message. The MS shall indicate fallback to speech by these 
two BC lEs and the associated Repeat Indicator set to "support of fallback". 

For UDI/RDI multimedia, the support of a fallback and service change is requested by including two bearer capability 
IBs, with the first BC as the preferred service in the SETUP message. The MS shall indicate service change and fallback 
by these two BC lEs and the associated Repeat Indicator set to "support of service change and fallback". 

If the bearer capability IE is received from the MS either in A/Gb or GERAN lu mode and indicates no A/Gb mode 
support for the requested bearer service, the network shall consider it as a request to perform an inter-system handover 
to UTRAN lu mode, as described in TS 23.009 [1 14] subclause 14.2. 

The bearer compatibility checking in the network is according to 5.3.4.2. 1. 

If the MS requested for an analogue multimedia call with fallback to speech, or for a UDI/RDI multimedia call with 
fallback and service change, and the network accepts the call, the network has the following options for the inclusion of 
bearer capability IBs in the CALL PROCEEDING message: 

if the network accepts the requested analogue multimedia call and supports fallback to speech, both multimedia 
and speech bearer capability IBs shall be included; 

if the network accepts the requested UDI/RDI multimedia call and supports fallback and service change, both 
multimedia and speech bearer capability IBs shall be included. The order of the bearer capability lEs determines 
the preferred service, and the network may reverse the order of these lEs (see 3GPP TS 23.172 [97], 
subclause 4.2.1); 

if the network accepts a multimedia (only) call, a multimedia bearer capability IB shall be included; 

if the network accepts a speech (only) call, a speech bearer capability IB shall be included; 

for a UDI/RDI multimedia call, if the network accepts the requested speech call and supports service change, 
both multimedia and speech bearer capability IBs shall be included. The order of the bearer capability lEs 
determines the preferred service, and the network may reverse the order of these lEs (see 3GPP TS 23.172 [97], 
subclause 4.2.1); 

if the network received a UDI/RDI multimedia bearer capability IE with FNUR equal to 32kbit/s and a speech 
bearer capability IE in the SETUP message, the network shall not release the call, but shall reply with one 
bearer capability IE only, as specified in 3GPP TS 23.172 [97]. 

NOTE: Service change and fallback for UDI/RDI multimedia calls is not supported with Fixed Network User 
Rate set to 32 kbit/s (see 3GPP TS 23.172 [97]). 

If the MS requested for a multimedia call only, and the network accepts the call, the network shall always include a 
single multimedia bearer capability IB in the CALL PROCEEDING message. 

The originating user shall determine (possibly by pre -configuration of the terminal) whether a digital connection is 
required or if the call will be an analog modem call. If the call is expected to be digital the multimedia bearer capability 
IE parameter ITC is set to UDI/RDI. In an analog call the multimedia bearer capability IE parameter ITC is set to 
"3,1 kHz audio ex PLMN". Additionally required modem type is indicated (Other Modem Type = V.34). 

5.3.6.2.1.1 Fallback 

If the network, during the setup of an H.324-call, detects that the transit network or the called end does not support an 
H.324 call (e.g. because of a failure in the modem handshaking in case of an analogue multimedia call), then the 
network initiates the in-call modification procedure (see subclause 5.3.4.3) towards the MS to modify the call mode to 
speech, if the MS had included a speech bearer capability IB in the SETUP message. 

In case of a UDI/RDI multimedia call with service change and fallback, if the network detects that the called end does 
not support speech, then it initiates an in-call modification procedure towards the MS to modify the call mode to 
multimedia, if the first bearer capability IB was for a speech call. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 97 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.3.6.2.2 Mobile terminating multimedia call 

At call setup the required call type, 3G-324M, is indicated by the network in the SETUP message, with the bearer 
capability /£ parameter. Other Rate Adaptation set to 'H.223 and H.245'. ITC is either '3,1 kHz audio ex PLMN' or 
'UDI/RDI'. 

For analogue multimedia, if the network supports fallback to speech and the subscriber has subscription to speech, two 
bearer capability lEs, multimedia first and speech as the second BC are included in the SETUP message. The network 
shall indicate fallback to speech by these two BC lEs and the associated Repeat Indicator set to "support of fallback". 

For UDI/RDI multimedia, if the network supports fallback and service change, and the subscriber has subscription to 
speech, two bearer capability lEs, with the first BC as the preferred service are included in the SETUP message. The 
network shall indicate service change and fallback by these two BC lEs and the associated Repeat Indicator set to 
"service change and fallback". 

If the bearer capability IE is received from the MS either in A/Gb or GERAN lu mode and indicates no A/Gb mode 
support for the requested bearer service, the network shall consider it as a request to perform an inter-system handover 
to UTRAN lu mode, as described in TS 23.009 [1 14] subclause 14.2. 

The bearer capability IE(s) may (in the case of the single numbering scheme) be missing from the SETUP message. 

The bearer compatibility checking in the MS is according to 5.3.4.2.2. 

The MS shall indicate the supported call type(s) in the CALL CONFIRMED message, which is the acknowledgement 
to SETUP. If the network offered an analogue multimedia call with fallback to speech, or a UDI/RDI multimedia call 
with fallback and service change, the MS has the following options for the inclusion of bearer capability lEs in the 
CALL CONFIRMED message: 

if the MS/user accepts the offered analogue multimedia call and supports fallback to speech, both multimedia 
and speech bearer capability lEs shall be included; 

if the MS/user accepts the offered UDI/RDI multimedia call, and supports fallback and service change, both 
multimedia and speech bearer capability lEs shall be included. The order of the BC lEs determines the preferred 
service, and the MS/user may reverse the order of these lEs; 

if the MS/user accepts the offered multimedia call, but does not support fallback or service change, only a 
multimedia bearer capability IE shall be included; 

if the MS/user wishes a speech (only) call a speech bearer capability IE is included; 

for a UDI/RDI multimedia call, if the MS/user accepts the offered speech call and supports service change, both 
speech and multimedia bearer capability lEs shall be included. The order of the BC lEs determines the preferred 
service, and the MS/user may reverse the order of these lEs. 

If the network offered a multimedia call only, and the MS/user accepts the call, the MS shall always include a single 
multimedia bearer capability IE in the CALL CONFIRMED message. 

If the SETUP contained no bearer capability IE the network shall perform compatibility checking of the CALL 
CONFIRMED message in the same way as the compatibility checking of the SETUP message in the mobile originating 
call case, described in subclause 5.3.6.2.1. 

5.3.6.2.2.1 Fallback to speech 

If modem handshaking fails (in a modem call), the call mode will be modified to speech if a speech bearer capability IE 
was included. The modem signalling is inband, so the call must have reached the active state, when these conclusions 
about the presence of modems can be done. The call modifications are realized through the in-call modification 
procedure, by which the network requests the MS to modify the call mode (see subclause 5.3.4.3). 

NOTE: Fallback from digital (UDI) H.324-call to speech after call setup is not a valid case at the terminating 
side. 

5.3.6.3 In-call modification in the "active" state 

The in-call modification procedure as described in chapter 5.3.4.3 shall be used to: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 98 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

trigger a service change between speech and UDI/RDI multimedia modes, when service change has been agreed 
at call setup; 

trigger a network-initiated service upgrade from speech to UDI/RDI multimedia modes (see 3GPP TS 23.172 
[97]). The network shall initiate this procedure only if the mobile station indicated support of the enhanced 
network-initiated in-call modification procedure in the Call Control Capabilities IE at call establishment. In this 
case, the MODIFY message shall include the Network-initiated Service Upgrade indicator IE; or 

modify the multimedia bearer capability for an analogue multimedia call (restricted to the network initiated in- 
call modification only). In this case, the network shall send a MODIFY message including the new Bearer 
Capability to be changed to. The following bearer capability parameters can be modified with the procedure (see 
3GPP TS 29.007 [38]): 

Fixed Network User Rate (analogue multimedia calls only). 

5.3.6.3.1 Void 

5.3.6.3.2 Void 

5.3.6.3.3 Void 

5.3.6.3.3.1 Void 

5.3.6.3.3.2 Void 

5.4 Call clearing 

5.4.1 Terminology 

The following terms are used in the present document in the description of clearing procedures: 

A traffic channel (see 3GPP TS 44.003 [16]) is "connected" when the channel is part of a circuit-switched 
connection established according to the present document. 

A traffic channel is "disconnected" when the channel is no longer part of a circuit-switched connection, but is not 
yet available for use in a new connection. 

5.4.2 Exception conditions 

Under normal conditions, the call control entity of the mobile station or of the network initiates call clearing by sending 
a DISCONNECT message to its peer entity; then both entities follow the procedures defined in subclauses 5.4.3 and 
5.4.4 respectively. 

As an exception to the above rule, the call control entity of the mobile station or of the network, in response to a SETUP 
or START CC or CC-ESTABLISHMENT CC-ESTABLISHMENT CONFIRMED or RECALL message, can reject a 
call by stopping all running call control timers, responding with a RELEASE COMPLETE message, releasing the MM 
connection, and returning to the "null" state, provided no other response has previously been sent. 

As a further exception, the call control entity of the network may initiate call clearing by stopping all running call 
control timers, sending a RELEASE message, starting timer T308, and entering the "release request" state. 

NOTE: This way to initiate call clearing by sending a RELEASE message should not be used by the network: 

if in-band tones/announcements are provided and the network decides to use the procedure described 

in subclause 5.4.4.1.1.1 or 5.4.4.2.1; 

if the network wants to have the opportunity to respond to information sent by the mobile station 
during call clearing, e.g. when the network indicates that "CCBS activation is possible". 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 1 99 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

A call control entity shall accept an incoming RELEASE COMPLETE message used to initiate the call clearing even 
though the cause information element is not included. 

A control entity shall accept an incoming RELEASE message used to initiate the call clearing even though the cause 
information element is not included. 

Furthermore, a call control entity shall regard an incoming RELEASE COMPLETE message as consistent with any of 
its states; a call control entity shall regard an incoming RELEASE message as consistent with any of its states except 
the null state: a call control entity of the mobile station shall regard an incoming DISCONNECT message as consistent 
with any of its call control states except the "null" state, the "release request" state, and the "disconnect indication" state; 
a call control entity of the network shall regard an incoming DISCONNECT message as consistent with any of its call 
control states except the "null" state and the "release request" state. 

NOTE: This allows the introduction of shorter call clearing procedures in the future. 

5.4.3 Clearing initiated by tine mobile station 

5.4.3.1 Initiation of call clearing 

Apart from the exceptions identified in subclause 5.4.2, the call control entity of the mobile station shall initiate clearing 
by: stopping all running call control timers, sending a DISCONNECT message; starting timer T305; and entering the 
"disconnect request" state. 

5.4.3.2 Receipt of a DISCONNECT message from the mobile station. 

The call control entity in the network in any state except the "null" state and the "release request" state shall, upon 
receipt of a DISCONNECT message: 

Stop all running call control timers; 

initiate procedures to clear the network connection and the call to the remote user; 

send a RELEASE message to its peer entity; 

start timer T308; and 

enter the "release request" state. 

NOTE: The RELEASE message has only local significance and does not imply an acknowledgement of clearing 
from the remote user. 

5.4.3.3 Receipt of a RELEASE message from the network 

The call control entity of the mobile station in any state except the "null" state and the "release request" state, shall, 
upon receipt of a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE message; 
release the MM connection; and return to the "null" state. 

5.4.3.4 Receipt of a RELEASE COMPLETE message from the mobile station 

A call control entity of the network in any call control state shall, upon receipt of a RELEASE COMPLETE message 
from its peer entity in the mobile station: stop all running call control timers; release the MM connection; and return to 
the "null" state. 

5.4.3.5 Abnormal cases 

The call control entity of the mobile station in the "disconnect request" state, shall upon expiry of timer T305: send a 
RELEASE message to the network with the cause number originally contained in the DISCONNECT message and 
optionally, a second cause information element with cause #102 "recovery on timer expiry", start timer T308, and enter 
the "release request" state. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 200 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

The call control entity of the network in the "release request" state, shall, at first expiry of timer T308, retransmit the 
RELEASE message, start timer T308, and stay in the "release request" state. At second expiry of timer T308, the call 
control entity of the network shall: release the MM connection; and return to the "null" state. 

5.4.4 Clearing initiated by tine network 

Apart from the exception conditions identified in subclause 5.4.2, the call control entity of the network shall initiate 
clearing by: sending a DISCONNECT message; and entering the "disconnect indication" state. The DISCONNECT 
message is a local invitation to clear the call. 

NOTE: When the network initiates clearing by sending a RELEASE message, the procedures described in 
subclauses 5.4.3., 5.4.3.4 and 5.4.3.5 are followed. 

A mobile station that does not support the "Prolonged Clearing Procedure" shall comply with the requirements of 
subclause 5.4.4.1 and shall ignore subclause 5.4.4.2. A mobile station that supports the "Prolonged Clearing Procedure" 
shall comply with the requirements of subclauses 5.4.4.2 and shall ignore subclause 5.4.4.1. 

5.4.4.1 Clearing initiated by the networl<: mobile does not support "Prolonged 

Clearing Procedure" 

Sublause 5.4.4.1 only applies to mobile stations that do not support the "Prolonged Clearing Procedure" option. 

5.4.4.1 .1 Clearing when tones/announcements provided 

When in-band tones/announcements are provided (see subclause 5.5.1), the call control entity of the network may 
initiate clearing by sending a DISCONNECT message containing progress indicator #8 "in-band information or 
appropriate pattern now available", starting timer T306, and entering the "disconnect indication" state. 

5.4.4.1 .1 .1 Receipt of a DISCONNECT message with progress indicator #8 from tine network 

The call control entity of the MS in any state except the "null" state, the "disconnect indication" state, and the "release 
request" state, shall, upon receipt of a DISCONNECT message with progress indicator #8: 

i) if an appropriate speech traffic channel is not connected, continue clearing as defined in subclause 5.4.4.1.2.1 
without connecting to the in-band tone/announcement; 

ii) if an appropriate speech traffic channel is connected, attach the user connection for speech if it is not yet attached 
and enter the "disconnect indication" state. In that state, if upper layers request the clearing of the call, the call 
control entity of the MS shall proceed as defined in subclause 5.4.4.1.2.1. 

5.4.4.1.1.2 Expiry of timer T306 

The call control entity of the network, having entered the "discormect indication" state after sending a disconnect 
message with the progress indicator #8, shall, upon expiry of timer T306, continue clearing by sending a RELEASE 
message with the cause number originally contained in the DISCONNECT message; starting timer T308; and entering 
the "release request" state. 

5.4.4.1 .2 Clearing when tones/announcements not provided 

When in-band tones and announcements are not provided, the call control entity of the network shall initiate call 
clearing by stopping all running call control timers, sending a DISCONNECT message without progress indicator, 
starting timer T305 and entering the "disconnect indication" state. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 201 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.4.4.1 .2.1 Receipt of a DISCONNECT message without progress indicator or with progress 
indicator different from #8 from the network 

The call control entity of the mobile station in any state except the "null" state, the "disconnect indication" state, and the 
"release request" state, shall, upon the receipt of a DISCONNECT message without progress indicator information 
element or with progress indicator different from #8: 

stop all running call control timers; 

send a RELEASE message; 

start timer T308; and 

enter the "release request" state. 

5.4.4.1 .2.2 Receipt of a RELEASE message from the mobile station 

The call control entity of the network in any state except the "null" state and the "release request" state, shall, upon 
receipt of a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE message; release 
the MM connection; and return to the "null" state. 

5.4.4.1.2.3 Abnormal cases 

The call control entity of the network, having entered the "disconnect indication" state after sending a DISCONNECT 
message without progress indicator or with progress indicator different from #8, shall upon expiry of timer T305: send a 
RELEASE message to the mobile station with the cause number originally contained in the DISCONNECT message; 
start timer T308; and enter the "release request" state. In addition to the original clearing cause, the RELEASE message 
may contain a second cause information element with cause #102 "recovery on timer expiry". 

5.4.4.1 .3 Completion of clearing 

A call control entity of the mobile station in any call control state shall, upon receipt of a RELEASE COMPLETE 
message from its peer entity in the network: stop all running call control timers; release the MM connection; and return 
to the "null" state. 

5.4.4.1 .3.1 Abnormal cases 

The call control entity of the mobile station in the "release request" state shall at first expiry of timer T308 retransmit 
the RELEASE message and restart timer T308. At second expiry of timer T308, the call control entity of the mobile 
station shall: release the MM connection; and return to the "null" state. 

5.4.4.2 Clearing Initiated by the network: mobile supports "Prolonged Clearing 

Procedure" 

Sublause 5.4.4.2 only applies to mobile stations that support the "Prolonged Clearing Procedure" option. 

5.4.4.2.1 Clearing when tones/announcements provided and the network does not indicate 

that "CCBS activation is possible" 

When in-band tones/announcements are provided (see subclause 5.5.1) and CCBS is not applicable, the call control 
entity of the network may initiate clearing by sending a DISCONNECT message containing progress indicator #8 "in- 
band information or appropriate pattern now available", either not containing an Allowed Actions IE or containing an 
Allowed Actions IE indicating "CCBS activation is not possible", starting timer T306, and entering the "disconnect 
indication" state. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 202 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.4.4.2.1 .1 Receipt of a DISCONNECT message 

The call control entity of the MS in any state except the "null" state, the "disconnect indication" state, and the "release 
request" state, shall, upon receipt of a DISCONNECT message with progress indicator #8 and, either not containing an 
Allowed Actions IE or containing an Allowed Actions IE indicating "CCBS activation is not possible"; 

i) if an appropriate speech traffic channel is not connected, 

stop all running call control timers; 

send a RELEASE message; 

start timer T308; 

enter the "release request" state; and 

not connect to the in-band tone/announcement. 

ii) if an appropriate speech traffic channel is connected, attach the user connection for speech if it is not yet attached 
and enter the "disconnect indication" state. In that state, if upper layers request the clearing of the call, the call 
control entity of the MS shall; 

stop all running call control timers; 

send a RELEASE message; 

start timer T308; and 

enter the "release request" state. 

5.4.4.2.1.2 Expiry of timer T306 

The call control entity of the network, having entered the "disconnect indication, shall, upon expiry of timer T306, 
continue clearing by sending a RELEASE message with the cause number originally contained in the DISCONNECT 
message; starting timer T308; and entering the "release request" state. 

5.4.4.2.2 Clearing when the network indicates that "CCBS activation is possible" 

When Activation of CCBS is possible, the call control entity of the network may initiate clearing by sending a 
DISCONNECT message containing the Allowed Actions IE with an indication that "Activation of CCBS is possible" 
and starting T338. Optionally, progress indicator #8 "in-band information or appropriate pattern now available" may 
also be contained in the DISCONNECT message (in which case, T338 shall not be greater than T306). 

5.4.4.2.2.1 Receipt of a DISCONNECT 

Relative to the current state the following procedures apply; 

The call control entity of the MS in the "null" state, the "disconnect indication" state and the "release request" 
state, shall, upon receipt of a DISCONNECT message react as described in clause 8. 

The call control entity of the MS in the "disconnect request" state, shall, upon receipt of a DISCONNECT 
message; 

stop all running call control timers; 

send a RELEASE message; 

start timer T308; and 

enter the "release request" state. 

The call control entity of the MS in any other states, shall, upon receipt of a DISCONNECT message with an 
Allowed Actions IE indicating "Activation of CCBS is possible" pass the "Activation of CCBS is possible" 
indication to the upper layer, enter the "disconnect indication" state, stop all running call control timers and await 
a response from the upper layers. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 203 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the DISCONNECT message contained the progress indicator #8 "in-band information or appropriate pattern now 
available" and an appropriate speech traffic channel is connected, then the MS shall attach the user connection for 
speech if it is not yet attached. If the DISCONNECT message did not contain the progress indicator #8 "in-band 
information or appropriate pattern now available" any connected speech traffic channel shall be disconnected. 

Response from the upper layers: 

i) If the upper layers request the clearing of the call, the call control entity of the MS shall: 

stop all running call control timers; 

send a RELEASE message; 

start timer T308; and 

enter the "release request" state, 
ii) If the upper layers request that the "CCBS activation is to be attempted" then the MS shall 

send a RELEASE message containing a Facility IE including an 

Invoke=CCBSRequest to the network; 

stop all running call control timers; 

start timer T308; and 

enter the "release request" state. 

If an appropriate speech traffic channel is connected, transmission of this RELEASE message shall not cause it 
to be disconnected. 

5.4.4.2.2.2 Expiry of timer T338 

The call control entity of the network, having entered the "disconnect indication" state after sending a DISCONNECT 
message with an Allowed Actions IE indicating "Activation of CCBS is possible" shall, upon expiry of timer T338, 
continue clearing by sending a RELEASE message with the cause number originally contained in the DISCONNECT 
message; starting timer T308; and entering the "release request" state. 

5.4.4.2.3 Clearing when tones/announcements are not provided and the network does not 

indicate that "CCBS activation is possible" 

When in-band tones and announcements are not provided, and, the network does not wish to indicate in the Allowed 
Actions IE that "CCBS is possible", the call control entity of the network shall initiate call clearing by stopping all 
running call control timers, sending a DISCONNECT message without progress indicator, either without the Allowed 
Actions IE or with the Allowed Actions IE indicating that "CCBS is not possible", starting timer T305 and entering the 
"disconnect indication" state. 

5.4.4.2.3.1 Receipt of a DISCONNECT message 

The call control entity of the mobile station in any state except the "null" state, the "disconnect indication" state, and the 
"release request" state, shall, upon the receipt of a DISCONNECT message either without progress indicator 
information element or with progress indicator different from #8, and, either without the Allowed Actions IE or with the 
Allowed Actions IE indicating that "CCBS is not possible": 

stop all running call control timers; 

send a RELEASE message; 

start timer T308; and 

enter the "release request" state. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 204 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

5.4.4.2.3.2 Abnormal cases 

The call control entity of the network, having entered the "disconnect indication", shall upon expiry of timer T305: send 
a RELEASE message to the mobile station with the cause number originally contained in the DISCONNECT message; 
start timer T308; and enter the "release request" state. 

5.4.4.2.4 Receipt of a RELEASE message from the mobile station 

5.4.4.2.4.1 Release, CCBS not requested 

For a network that does not support the "CCBS activation" option: 

The call control entity of the network in any state except the "null" state and the "release request" state, shall, 
upon receipt of a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE 
message; release the MM connection; and return to the "null" state. 

For a network that does support the "CCBS activation" option: 

The call control entity of the network in any state except the "null" state and the "release request" state, shall, 
upon receipt of a RELEASE message without a Facility IE including an Invoke=CCBSRequest: stop all running 
call control timers; send a RELEASE COMPLETE message; release the MM connection; and return to the "null" 

state. 

5.4.4.2.4.2 Release, CCBS Requested 

For a network that does not support the "CCBS activation" option: 

The call control entity of the network in any state except the "null" state and the "release request" state, shall, 
upon receipt of a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE 
message; release the MM connection; and return to the "null" state. 

For a network that does support the "CCBS activation" option: 

The call control entity of the network in any state except the "null" state and the "release request" state, shall, 
upon receipt of a RELEASE message containing a Facility IE including an Invoke=CCBSRequest: stop all 
running call control timers; then attempt to activate the recall; then send a RELEASE COMPLETE message 
indicating the success or failure of the recall activation attempt; release the MM connection; and return to the 
"null" state. 

5.4.4.2.5 Completion of clearing 

A call control entity of the mobile station in any call control state shall, upon receipt of a RELEASE COMPLETE 
message from its peer entity in the network: stop all running call control timers; release the MM connection; and return 
to the "null" state. 

5.4.4.2.5.1 Abnormal cases 

The call control entity of the mobile station in the "release request" state shall at first expiry of timer T308 retransmit 
the RELEASE message and restart timer T308. At second expiry of timer T308, the call control entity of the mobile 
station shall: release the MM connection; and return to the "null" state. 

The retransmitted RELEASE message need not contain the Facility IE including an Invoke=CCBSRequest, even if the 
original RELEASE message did contain this IE.5 .4.5 Clear collision 

Clear collision occurs when both the mobile station and the network simultaneously transfer DISCONNECT messages 
specifying the same call. 

The behaviour of the network call control entity receiving a DISCONNECT message whilst in the "disconnect 
indication" state is specified in subclause 5.4.3. The behaviour of the MS call control entity receiving a DISCONNECT 
message whilst in the "disconnect request" state is defined in subclause 5.4.4. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 205 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

Clear collision can also occur when both sides simultaneously transfer RELEASE messages related to the same call. 
The entity receiving such a RELEASE message whilst within the "release request" state shall: stop timer T308; release 
the MM connection; and enter the "null" state (without sending a RELEASE COMPLETE message). 

5.5 Miscellaneous procedures 

5.5.1 In-band tones and announcements 

When the network wants to make the mobile station attach the user connection (e.g. in order to provide in-band 
tones/announcement) before the mobile station has reached the "active" state of a call, the network may include a 
progress indicator IE indicating user attachment in a suitable CC message: 

- Either it includes the IE in a SETUP, CALL PROCEEDING, ALERTING, or CONNECT message that is send 
during call establishment 

it sends a PROGRESS message containing the IE. 

A progress indicator IE indicates user attachment if it specifies a progress description in the set { 1 , 2, 3 } or in the set 
{6, 7, 8, ...,20}. 

On reception of a SETUP, CALL PROCEEDING, ALERTING, CONNECT, or PROGRESS message the mobile 
station shall proceed as specified elsewhere in clause 5; \f\hc progress indicator IE indicated user attachment and a 
speech mode traffic channel is appropriate for the call the mobile station shall in addition: attach the user connection for 
speech as soon as an appropriate channel in speech mode is available. (If a new order to attach the user connection is 
received before the attachment has been performed, the new order shall supersede the previous one.) 

Under certain conditions the MS will have to attach the user connection before the CONNECT message. It is up to the 
network to ensure that no undesired end-to-end through connection takes place during the establishment of a MT call. 

NOTE: This allows the use of progress indicator lEs independently from the channel modes appropriate for the 
call. 

5.5.2 Call collisions 

Call collisions as such cannot occur at the network. Any simultaneous mobile originating or mobile terminating calls 
are dealt with separately assigned and different transaction identifiers. 

5.5.3 Status procedures 
5.5.3.1 Status enquiry procedure 

Whenever a call control entity wishes to check the call state of its peer entity, it may initiate the status enquiry 
procedure. 

NOTE: This may, in particular, apply to procedural error conditions described in clause 8. 

A call control entity initiates the status enquiry procedure by sending the STATUS ENQUIRY message and starting 
timer T322. While timer T322 is running, the call control entity shall not send further STATUS ENQUIRY messages. 

Upon receipt of a STATUS ENQUIRY message, the receiver shall respond with a STATUS message, reporting the 
current call state and cause value #30 "response to STATUS ENQUIRY". Receipt of the STATUS ENQUIRY shall not 
result in a state change relating to any protocol and connection of the receiver. 

If a STATUS message is received that contains cause value #30 "response to status enquiry", timer T322 shall be 
stopped and further appropriate actions taken, based on the information in that STATUS message, relative to the current 
state of the receiver of the STATUS message. These further "appropriate actions" are implementation dependent. 
However, the actions prescribed in subclause 5.5.3.2 shall apply. 

If a clearing message is received while timer T322 is running, timer T322 shall be stopped, and call clearing shall 
continue. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 206 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If timer T322 expires, the STATUS ENQUIRY message may be retransmitted maximally once. If T322 expires after 
the STATUS ENQUIRY has been transmitted the maximum number of times, clearing of the call shall be initiated with 
cause value #41, "temporary failure", in the first call clearing message. 

5.5.3.2 Reception of a STATUS message by a CC entity 

5.5.3.2.1 STATUS message with incompatible state 

On receipt of a STATUS message reporting an incompatible call control state, the receiving entity shall clear the call by 
sending a RELEASE COMPLETE message with cause # 101 "message not compatible with protocol state". The 
reported call control state is incompatible if the combination of call control states at the sender and receiver side cannot 
occur, do not match or cannot be aligned by actions of the receiver; the exact definition is implementation dependent. 

5.5.3.2.2 STATUS message with compatible state 

A STATUS message may be received indicating a compatible call state but containing one of the following causes: 

# 95 "semantically incorrect message"; or 

# 96 "invalid mandatory information"; or 

# 97 "message type non-existent or not implemented"; or 

# 98 "message type not compatible with protocol state"; or 

# 99 "information element non-existent or not implemented"; or 

# 100 "conditional IE error". 

This indicates that the transmitter of the STATUS message was unable to accept some information sent by the recipient 
of the STATUS message. This allow the recipient to retransmit some or all of the information. Other actions are 
possible and are implementation dependent; they may include releasing the call. 

In the case the MS receives a STATUS message with the cause #100 due to the presence of a Repeat Indicator with the 
value 'service change and fallback' in a SETUP message, it may then resend a new SETUP message with a single BC-IE 
(no Repeat Indicator is included). The actual behaviour is dependent on the implementation. 

In the case the network receives a STATUS message with the cause #100 due to the presence of a Repeat Indicator with 
the value 'service change and fallback' in a SETUP message, it shall then resend a new SETUP message, with either the 
BC-IE of the preferred service or the speech BC-IE (fallback to speech) as the only BC (no Repeat Indicator is 
included). The preferred behaviour is decided by configuration. 

5.5.4 Call re-establishment, mobile station side 

This subclause describes the internal handling in the mobile station as far as call control is concerned. 

5.5.4.1 Indication from the mobility management sublayer 

When a MM connection is active, an indication may be given by the MM sublayer to the call control entity to announce 
that the current MM connection has been interrupted but might be re-established on request of call control. 

5.5.4.2 Reaction of call control 

Depending whether call re -establishment is allowed or not and on its actual state, call control shall decide to either 
request re-establishment or to release the MM connection. 

a) Re -establishment not required 

If the call is in the call establishment or call clearing phase, i.e. any state other than the "active" state or the 
"mobile originating modify" state, call control shall release the MM connection 

b) Re-establishment required 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 207 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the call is in the "active" state or "mobile originating modify" state, the indication from MM that re- 
establishment is possible shall cause call control to request re -establishment from the MM connection, 
suspend any further message to be sent and await the completion of the re-establishment procedure. 

5.5.4.3 Completion of re-establishment 

Call Control is notified when the MM connection is re-established and shall then resume the transmission of possibly 
suspended messages and resume user data exchange when an appropriate channel is available. 

5.5.4.4 Unsuccessful outcome 

If the attempt to re-establish the connection was unsuccessful, the MM connection will be released and a release 
indication will be given to call control, see subclause 4.5.1.6. 

5.5.5 Call re-establishment, network side 

This subclause describes the handling in the network as far as call control is concerned. 

5.5.5.1 State alignment 

After a successful call re-establishment it is a network responsibility to identify (e.g. by using the status enquiry 
procedure, if needed, and resolve, if possible, any call state or auxiliary state mismatch between the network and the 
mobile station. 

5.5.6 Progress 

At any time during the establishment or release of a call and during an active call the network may send a PROGRESS 
message to the mobile station. 

On receipt of a PROGRESS message during the establishment or release of a call the mobile station shall stop all call 
control timers related to that call. 

NOTE: If the PROGRESS has been received before the receipt of a CALL PROCEEDING message, the mobile 
station will not start timer T3 10 on receipt of a CALL PROCEEDING message, see subclause 5.2. 1 . 1 .3. 

H3 Network 

PROGRESS 
< 

Figure 5.11/3GPP TS 24.008 Progress 

5.5.7 DTMF protocol control procedure 

Dual Tone Multi Frequency (DTMF) is an inband one out of four plus one out of four signalling system primarily used 
from terminal instruments in telecommunication networks. The support of DTMF in the network is described in 
3GPPTS 23.014 [12]. 

The mobile station shall be capable of transmitting DTMF messages if and only if the mobile station has the user 
connection for speech attached and an appropriate channel is available. 

The transaction identifier used by the DTMF messages shall be that of the attached speech call. 

NOTE 1 : The present document means that DTMF messages can generally be sent in the active state of a call in 
speech transmission mode or when a traffic channel is available during setup or release and the progress 
indicator IE has been received. 

NOTE 2: Since the DTMF protocol messages are sent in a store and forward mode on the signalling channels the 
control of the device at the far end may be delayed dependent on the load or quality of the channels. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 208 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

NOTE 3: The procedures described in this paragraph support DTMF only in the direction mobile station to 
network. 

5.5.7.1 Start DTMF request by the mobile station 

A user may cause a DTMF tone to be generated e.g. by depression of a key in the mobile station. The relevant action is 
interpreted by the mobile station as a requirement for a DTMF digit to be sent in a START DTMF message on an 
established FACCH. This message contains the value of the digit to be transmitted (0, 1, ..., 9, A, B, C, D, *, #). 

Only a single digit will be transferred in each START DTMF message. 

On sending a START DTMF message the MS shall start timer T336. 

Where a previous START DTMF message has been sent, another START DTMF message shall only be sent by the MS 
following receipt of its STOP DTMF ACKNOWLEDGE message (see subclause 5.5.7.4) or a START DTMF REJECT 
message from the network (see subclause 5.5.7.2) or following the expiry of timers T336 and T337. 

If timer T336 expires, the MS shall terminate the ongoing DTMF procedure without any retransmissions, and is free to 
begin another DTMF procedure (e.g. another START DTMF message). 

5.5.7.2 Start DTMF response by the network 

Upon receiving the START DTMF message the network shall either: 

convert the received digit into a DTMF tone which is applied toward the remote user, or 

- send the DTMF digit as an out-of-band message (see 3GPP TS 23.205 [96]) 

and return a START DTMF ACKNOWLEDGE message to the mobile station. This acknowledgement may be used in 
the mobile station to generate an indication as a feedback for a successful transmission. 

If the network cannot accept the START DTMF message a START DTMF REJECT message will be sent to the mobile 
station. Upon receipt of a START DTMF ACK message or a START DTMF REJECT message, the MS shall stop timer 
T336. 

5.5.7.3 Stop DTMF request by the mobile station 

When the user indicates that the DTMF sending should cease e.g. by releasing the key the mobile station will send a 
STOP DTMF message to the network. 

On sending a STOP DTMF message the MS shall start timer T337. 

The MS shall only send a STOP DTMF message if a START DTMF ACKNOWLEDGE message has been received 
from the network (see subclause 5.5.7.2). 

If timer T337 expires, the MS shall terminate the ongoing DTMF procedure without any retransmissions, and is free to 
begin another DTMF procedure, (e.g. another START DTMF message). 

5.5.7.4 Stop DTMF response by the network 

Upon receiving the STOP DTMF message the network shall either: 

stop sending the DTMF tone if applied by the network, or 

initiate a suitable out-of-band message (see 3GPP TS 23.205 [96]) 

and return a STOP DTMF ACKNOWLEDGE message to the mobile station. Upon receipt of a STOP DTMF 
ACKNOWLEDGE message, the MS shall stop timer T337. 

5.5.7.5 Sequencing of subsequent start DTMF requests by the mobile station 

If the network is generating DTMF tones it shall ensure that the minimum length of tone and the minimum gap between 
two subsequent tones (according to ETSI ES 201 235-2 [12a]) is achieved. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 209 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

NOTE 1: In ETSI ES 201 235-2 [12a] the minimum duration of a DTMF tone is 65ms. 

NOTE 2: In ETSI ES 201 235-2 [12a] the minimum gap between DTMF tones is 65ms. 

There is no defined maximum length to the tone, which will normally cease when a STOP DTMF message is received 
fi-om the MS. However, the operator may choose to put a pre-defined time limit on the duration of tones sent. 

The appropriate sequencing of DTMF control messages is shown in figures 5.8 and 5.9. 

NOTE 3: The network may implement the time limit option where the DTMF tone duration is controlled by the 
network irrespective of the receipt of a STOP DTMF message from the mobile station. 

Mobile Station Network 

START DTHF 
> 

START DTHF ACK 

< 

STOP DTHF 
> 

STOP DTHF ACK 
< 

Figure 5.8/3GPP TS 24.008 Single DTMF transmission 

Hotoile Station Network 

START DTHF (x) 
> 

START DTHF ACK 

< 

STOP DTHF 
> 

STOP DTHF ACK 
< 

START DTHF (y) 
> 

START DTHF ACK 
< 



Figure 5.9/3GPP TS 24.008 Multiple DTMF transmission 



Support for packet services 



This chapter contains the description of the procedures for the session management of GPRS point-to-point data 
services and MBMS point-to-point and point-to-multipoint data services at the radio interface (Reference point Uu and 
Um). 

6.1 GPRS Session management 
6.1.1 General 

The main function of the session management (SM) is to support PDP context handling of the user terminal. 
Furthermore, the SM supports the MBMS context handling within the MS and the network, which allows the MS to 
receive data from a specific MBMS source. 

The SM comprises procedures for 

- identified PDP context activation, deactivation and modification; and 

- identified MBMS context activation and deactivation. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 210 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

SM procedures for identified access can only be performed if a GMM context has been established between the MS and 
the network. If no GMM context has been established, the MM sublayer has to initiate the establishment of a GMM 
context by use of the GMM procedures as described in chapter 4. After GMM context establishment, SM uses services 
offered by GMM (see 3GPP TS 24.007 [20]). Ongoing SM procedures are suspended during GMM procedure 
execution. 

The SM procedures for identified MBMS context activation and deactivation can only be performed, if in addition to 
the GMM context the MS has a PDP context activated. 

In lu mode only, integrity protected signalling (see subclause 4.1.1.1.1 of the present document and in general, see 
3GPP TS 33.102 [5a]) is mandatory. In lu mode only, all protocols shall use integrity protected signalling. Integrity 
protection of all SM signalling messages is the responsibility of lower layers. It is the network which activates integrity 
protection. This is done using the security mode control procedure (3GPP TS 25.331 [23c] and 3GPP TS 44.1 18 [111]). 

For the session management protocol, the extended TI mechanism may be used (see 3GPP TS 24.007 [20]). 



6.1 .2 Session management states 



In this subclause, the SM states are described for one SM entity (see 3GPP TS 24.007 [20]). Each SM entity is 
associated with one PDP context or MBMS context. Subclause 6.1.2.1 describes the SM states in the MS and subclause 
6.1.2.2 describes the SM states on the network side. 

6.1 .2.1 Session management states in the MS 

In this subclause, the possible states of an SM entity in the mobile station are described. As illustrated in figure 
6.1/3GPP TS 24.008 and 6.1a/3GPP TS 24.008 there are seven SM states in the MS. 

6.1.2.1.1 PDP-INACTIVE 

This state indicates that neither PDP context nor MBMS context exist. 

6.1.2.1.2 PDP-ACTIVE-PENDING 

This state exists when PDP context activation was requested by the MS. 

6.1.2.1.3 PDP-INACTIVE-PENDING 

This state exists when deactivation of the PDP contexts was requested by the MS. 

6.1.2.1.4 PDP-ACTIVE 

This state indicates that the PDP context is active. 

6.1.2.1.5 PDP-MODIFY_PENDING 

This state exists when modification of the PDP context was requested by the MS. 

6.1.2.1.6 MBMS-ACTIVE-PENDING 

This state exists when the MS has requested the network to activate an MBMS context. 

6.1.2.1.7 MBMS-ACTIVE 

This state indicates that the MBMS context is active. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



211 



ETSI TS 124 008 V7.14.0 (2009-03) 




DR (DEACTIV. PDF 
CONTX. REQ) 



DR: GMMSM-DATA-REQUEST (Message), i.e. message sent by an MS 

DI: GMMSM-DATA-INDICATION (Message), i.e. message received by an MS 



DR (MOD PDF CONTXT REJ) 



Figure 6.1/3GPP TS 24.008: Session management states for PDP context handling in the MS 

(overview) 

It shall be noted, that Figure 6.1/3GPP TS 24.008 applies to both the PDP context activation procedure and the 
secondary PDP context activation procedure, though the distinction in messages regarding the activation of PDP 
contexts is not shown here for simplicity. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



212 



ETSI TS 124 008 V7.14.0 (2009-03) 



DI (REQ. MBMS CONTX. ACTIV) •«■ 




DR (ACTIV. MBMS 
CONTX. REQ) 



DR (DEACTIV. PDF 
CONTX. ACC) 




DI (ACTIV. MBMS CONTX. REJ) 



DI (DEACTIV. PDF CONTX. REQ) 



DI (ACTIV. MBMS CONTX. ACC) 




DR: GMMSM-DATA-REQUEST (Mrasage), i.e. message sent by an MS 

DI: GMMSM-DATA-INDICATION (Mes.sage), i.e. message received by an MS 

Figure 6.1a/3GPP TS 24.008: Session management states for lUIBIUIS context hiandling in thie lUIS 

(overview) 

6.1 .2.2 Session management states on the network side 

In this subclause, the possible states of an SM entity on the network side are described. As illustrated in figures 
6.2/3GPP TS 24.008 and 6.2a/3GPP TS 24.008 there are eight SM states on the network side. 

6.1.2.2.1 PDP-INACTIVE 

This state indicates that the PDP context or MBMS context is not active. 

6.1.2.2.2 PDP-ACTIVE-PENDING 

This state exists when the PDP context activation was initiated by the network. 

6.1.2.2.3 PDP-INACTIVE-PENDING 

This state exists when deactivation of the PDP context was requested by the network. 

6.1.2.2.4 PDP-ACTIVE 

This state indicates that the PDP context is active. 

6.1.2.2.5 PDP-MODIFY-PENDING 

This state exists when modification of the PDP context was requested by the network. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



213 



ETSI TS 124 008 V7.14.0 (2009-03) 



6.1.2.2.6 MBMS-ACTIVE-PENDING 

This state exists when the network has initiated MBMS context activation. 

6.1.2.2.7 MBMS-INACTIVE-PENDING 

This state exists when the network has requested the MS to deactivate an MBMS context. 

6.1.2.2.8 MBMS-ACTIVE 

This state indicates that the MBMS context is active. 



(REQ PDF CONTX. ACTIV) 




DR: GMMSM-DATA-REQUEST (Message), i.e. message .sent by network 

DI: GMMSM-DATA-INDICATION (Message), i.e. message received by llie nelwoA 

Figure 6.2/3GPP TS 24.008: Session management states for PDP context handling on the network 

side (overview) 

It shall be noted, that figure 6.2/3GPP TS 24.008 applies to both the PDP context activation procedure and the 
secondary PDP context activation procedure, though the distinction in messages regarding the activation of PDP 
contexts is not shown here for simplicity. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



214 



ETSI TS 124 008 V7.14.0 (2009-03) 




DR: GMMSM-DATA-REQUEST (Message), i.e. message sent by network 

DI: GMMSM-DATA-INDICATION (Message), i.e. message received by the network 



Figure 6.2a/3GPP TS 24.008: Session management states for IVIBIUIS context handling on the network 

side (overview) 

6.1 .3 Session Management procedures 



6.1.3.1 



PDP context activation 



The purpose of this procedure is to estabHsh a PDP context between the MS and the network for a specific QoS on a 
specific NS API. The PDP context activation may be initiated by the MS or the initiation may be requested by the 
network. 

Each PDP address may be described by one or more PDP contexts in the MS or the network. The PDP Context 
Activation procedure is used to activate the first PDP context for a given PDP address and APN, whereas all additional 
contexts associated to the same PDP address and APN are activated with the secondary PDP context activation 
procedure. When more than one PDP context is associated to a PDP address, there shall be a Traffic Flow Template 
(TFT), including one or more packet filters, for each or all but one context. The downlink and uplink packet filters are 
considered separately. If present, the TFT shall be sent transparently either from the MS via the SGSN to the GGSN to 
enable packet classification and policing for downlink data transfer in the GGSN or from the GGSN via the SGSN to 
the MS to be used in a network requested secondary PDP context activation procedure (see subclause 6.1.3.2) and 
enable packet classification and policing for uplink data transfer in the MS (see 3GPP TS 23.060 [74]). 



6.1.3.1.1 



Successful PDP context activation initiated by the mobile station 



In order to request a PDP context activation, the MS sends an ACTIVATE PDP CONTEXT REQUEST message to the 
network, enters the state PDP-ACTIVE-PENDING and starts timer T3380. The message contains the selected NSAPI, 
PDP type, requested QoS and, if the MS requests a static address, the PDP address. The MS shall ensure that the 
selected NSAPI is not currently being used by another Session Management entity in the MS. The MS may indicate the 
support of Network Requested Bearer Control procedures in the protocol configuration options information element in 
the protocol configuration options information element (see 3GPP TS 23.060) [74]). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 215 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message, the network selects a radio priority level based 
on the QoS negotiated and may reply with an ACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of the 
message ACTIVATE PDP CONTEXT ACCEPT the MS shall stop timer T3380, shall enter the state PDP-ACTIVE. If 
the protocol configuration options information element is present, the network may indicate the Bearer Control Mode 
that shall be used. If the protocol configuration options information element is not present, the MS shall apply Bearer 
Control Mode 'MS only' for all active PDP contexts sharing the same PDP Address and APN. If the offered QoS 
parameters received from the network differ from the QoS requested by the MS, the MS shall either accept the 
negotiated QoS or initiate the PDP context deactivation procedure. 

NOTE 1 : If the MS requested a value for a QoS parameter that is not within the range specified by 3GPP TS 
23.107, the network should negotiate the parameter to a value that lies within the specified range. 

In A/Gb mode, the MS shall initiate establishment of the logical link for the LLC S API indicated by the network with 
the offered QoS and selected radio priority level if no logical link has been already established for that S API. If the 
offered QoS parameters received from the network differ from the QoS requested by the MS, the MS shall either accept 
the negotiated QoS or initiate the PDP context deactivation procedure. If the LLC S API indicated by the network can 
not be supported by the MS, the MS shall initiate the PDP context deactivation procedure. 

In lu mode, both the network and the MS shall store the LLC S API and the radio priority in the PDP context. If a lu 
mode to A/Gb mode system change is performed, the new SGSN shall initiate establishment of the logical link using 
the negotiated QoS profile, the negotiated LLC SAPI, and selected radio priority level stored in the PDP context as in a 
A/Gb mode to A/Gb mode Routing Area Update. 

An MS, which is capable of operating in both A/Gb mode and lu mode, shall use a valid LLC SAPI, while an MS 
which is capable of operating only in lu mode shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order 
to avoid unnecessary value range checking and any other possible confusion in the network. When the MS uses a valid 
LLC SAPI, the network shall return a valid LLC SAPI. The network shall return the "LLC SAPI not assigned" value 
only when the MS uses the "LLC SAPI not assigned" value. 

NOTE 2: The radio priority level and the LLC SAPI parameters, though not used in lu mode, shall be included in 
the messages, in order to support handover between lu mode and A/Gb mode networks. 

6.1 .3.1 .2 Successful PDP context activation requested by the network 

In order to request a PDP context activation, the network sends a REQUEST PDP CONTEXT ACTIVATION message 
to the MS and starts timer T3385. The message contains an offered PDP address. If available, the APN shall be included 
in the REQUEST PDP CONTEXT ACTIVATION message. 

Upon receipt of a REQUEST PDP CONTEXT ACTIVATION message, the MS shall than either initiate the PDP 
context activation procedure as described in the previous subclause or shall reject the activation request by sending a 
REQUEST PDP CONTEXT ACTIVATION REJECT message as described in subclause 6.1.3.1.4. The value of the 
reject cause IE of the REQUEST PDP CONTEXT ACTIVATION REJECT message shall indicate the reason for 
rejection, e.g. "insufficient resources to activate another context". 

The ACTIVATE PDP CONTEXT REQUEST message sent by the MS in order to initiate the PDP context activation 
procedure shall contain the PDP address, PDP Type and APN requested by the network in the REQUEST PDP 
CONTEXT ACTIVATION message. 

Upon receipt of the ACTIVATE PDP CONTEXT REQUEST message, the network shall stop timer T3385. 

The same procedures then apply as described for MS initiated PDP context activation. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 216 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

6.1 .3.1 .3 Unsuccessful PDP context activation initiated by the MS 

Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message the network may reject the MS initiated PDP 
context activation by sending an ACTIVATE PDP CONTEXT REJECT message to the MS. The message shall contain 
a cause code that typically indicates one of the following causes: 

# 8: Operator Determined Barring; 

# 26: insufficient resources; 

# 27: missing or unknown APN; 

#28: unknown PDP address or PDP type; 

# 29: user authentication failed; 

# 30: activation rejected by GGSN; 
#31: activation rejected, unspecified; 

# 32: service option not supported; 

# 33: requested service option not subscribed; 

# 34: service option temporarily out of order; 

# 35: NSAPI already used. The network shall not send this cause code (see note 1); or 

# 95 - 111 : protocol errors. 

#1 12: APN restriction value incompatible with active PDP context. 

NOTE 1: Pre-R99 network may send this cause code. 

Upon receipt of an ACTIVATE PDP CONTEXT REJECT message, the MS shall stop timer T3380 and enter/remain in 
state PDP-INACTIVE. 

6.1 .3.1 .4 Unsuccessful PDP context activation requested by the network 

Upon receipt of the REQUEST PDP CONTEXT ACTIVATION message, the MS may reject the network requested 
PDP context activation by sending the REQUEST PDP CONTEXT ACTIVATION REJECT message to the network. 
The message contains the same TI as included in the REQUEST PDP CONTEXT ACTIVATION and an additional 
cause code that typically indicates one of the following causes: 

# 26: insufficient resources; 

#31: activation rejected, unspecified; 

# 40: feature not supported; or 
#95 - 111: protocol errors. 

The network shall stop timer T3385 and enter state PDP-INACTIVE. 

6.1.3.1.5 Abnormal cases 

The following abnormal cases can be identified: 

a) Expiry of timers 

In the mobile station: 

On the first expiry of the timer T3380, the MS shall resend the ACTIVATE PDP CONTEXT REQUEST and 
shall reset and restart timer T3380. This retransmission is repeated four times, i.e. on the fifth expiry of timer 
T3380, the MS shall release all resources possibly allocated for this invocation and shall abort the procedure; 
no automatic PDP context activation re-attempt shall be performed. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 217 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

On the network side: 

On the first expiry of the timer T3385, the network shall resend the message REQUEST PDP CONTEXT 
ACTIVATION and shall reset and restart timer T3385. This retransmission is repeated four times, i.e. on the 
fifth expiry of timer T3385, the network shall release possibly allocated resources for this activation and shall 
abort the procedure. 

b) Collision of MS initiated and network requested PDP context activation 

Dynamic PDP address collision case: 

If the MS uses dynamic PDP addressing that turns out to collide with the network requested PDP address, then 
there is no detection of collision specified but left for network implementation. 

Static PDP address collision detected within the mobile station: 

A collision of an MS initiated and a network requested PDP context activation procedure is identified by the 
MS when a REQUEST PDP CONTEXT ACTIVATION message is received from the network after the MS 
has sent an ACTIVATE PDP CONTEXT REQUEST message, the MS has not yet received an ACTIVATE 
PDP CONTEXT ACCEPT or ACTIVATE PDP CONTEXT REJECT message, and 

i) the MS is able to compare the PDP type, PDP address and APN requested in the ACTIVATE PDP 

CONTEXT REQUEST message with those requested in the REQUEST PDP CONTEXT ACTIVATION 
message and these parameters are equal; or 

ii) the MS is unable to compare these parameters in the two messages. 

NOTE: In general, the MS is unable to test if the PDP type, PDP address and APN in the REQUEST PDP 
CONTEXT ACTIVATION message are the same as those for the PDN to which it is attempting to 
activate a context. This is because the MS may have omitted one or more of the parameters in the 
ACTIVATE PDP CONTEXT REQUEST message, since it is relying on default values to be provided by 
the network. 

In the case of such a collision, the MS initiated PDP context activation shall take precedence over the 
network requested PDP context activation. In case (i) the MS shall discard the REQUEST PDP CONTEXT 
ACTIVATION message and shall wait for the network response to its ACTIVATE PDP CONTEXT 
REQUEST message. In case (ii) the MS shall send a REQUEST PDP CONTEXT ACTIVATION REJECT 
message with the cause 'insufficient resources' to the network, and wait for the network response to its 
ACTIVATE PDP CONTEXT REQUEST message. 

Static PDP address collision detected on the network side: 

A collision is detected by the network in the case where the PDP address, PDP type and APN derived 
(according to 23.060 annex A) from the ACTIVATE PDP CONTEXT REQUEST message received from the 
MS match those in the REQUEST PDP CONTEXT ACTIVATION message sent to the MS. 

In the case of such a collision, the MS initiated PDP context activation shall take precedence over the 
network requested PDP context activation. The network shall terminate the network requested PDP context 
activation procedure, and proceed with the MS initiated PDP context activation procedure. 

c) MS initiated PDP context activation request for an already activated PDP context (on the network side) 

i) If the network receives a ACTIVATE PDP CONTEXT REQUEST message with the same combination 
of APN, PDP type and PDP address as an already activated PDP context, the network shall deactivate the 
existing PDP context and, if any, all the linked PDP contexts (matching the combination of APN, PDP 
type and PDP address), locally without notification to the MS and proceed with the requested PDP 
context activation. 

ii) Alternatively (different combination of APN, PDP type and PDP address), if the NS API matches that of 
an already activated PDP context, then the network shall deactivate only the existing PDP context locally 
without notification to the MS and proceed with the requested PDP context activation. 

It is an implementation option if the parameters used for comparison described in clause i) and ii) are the 
parameters provided in the (current and previous) ACTIVATE PDP CONTEXT REQUESTS or the parameters 
which are the result of the application of the selection rules defined in TS23.060 Annex A. 2. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



218 



ETSI TS 124 008 V7.14.0 (2009-03) 



The parameter provided in the current ACTIVATE PDP CONTEXT REQUEST can not be compared to the 
actually used parameters (result of application of selection rules defined in TS23.060 Annex A. 2) of the 
previously activated PDP contexts. 

d) Network initiated PDP context activation request for an already activated PDP context (on the mobile station 
side) 

If the MS receives a REQUEST PDP CONTEXT ACTIVATION message with the same combination of 
APN, PDP type and PDP address as an already activated PDP context, the MS shall deactivate the existing 
PDP context and, if any, all the linked PDP contexts (matching the combination of APN, PDP type and PDP 
address) locally without notification to the network and proceed with the requested PDP context activation. 



Start 
Stop 



Stop 



MS Networ 

ACTIVATE PDP CONTEXT 



ACTIVATE PDP CONTEXT 



or 



ACTIVATE PDP CONTEXT 



Figure 6.3/3GPP TS 24.008: MS initiated PDP context activation procedure 





MS Network 




REQUEST PDP CONTEXT ACTIVATION 




* Start T3385 




ACTIVATE PDP CONTEXT REQUEST 


1 Start T3380 


* Stop T3385 1 




ACTIVATE PDP CONTEXT ACCEPT 


] StopT3380 






or 1 




ACTIVATE PDP CONTEXT REJECT ] 


1 StopT3380 




L 


J 




or 




REQUEST PDP CONTEXT ACTIVATION REJECT ^ ^,,,, 

_^ Stop T3385 





6.1.3.2 



Figure 6.4/3GPP TS 24.008: Networit initiated PDP context activation procedure 



Secondary PDP Context Activation Procedure 



The purpose of this procedure is to establish an additional PDP context between the MS and the network for a specific 
Traffic Flow Template (TFT) and QoS profile on a specific NSAPI, when one or more PDP contexts has/have already 
been established for the particular PDP address and APN. The MS shall include a request for a TFT if a PDP context 
without a TFT is presently active for the particular PDP address, or the BCM is 'MS/NW. Depending on the selected 
Bearer Control Mode being 'MS only' or 'MS/NW, the secondary PDP context activation procedure may either be 
initiated by the MS or by either the MS or the network, respectively. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 219 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

6.1 .3.2.1 Successful Secondary PDP Context Activation Procedure Initiated by the MS 

In order to request a PDP context activation with the same PDP address and APN as an already active PDP context, the 
MS shall send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message to the network, enter the state 
PDP-ACTIVE-PENDING and start timer T3380. The message shall contain the selected NSAPI. The MS shall ensure 
that the selected NSAPI is not currently being used by another Session Management entity in the MS. The message 
shall also include a QoS profile, a requested LLC SAPI and the Linked TI. The QoS profile is the requested QoS. If 
present, the TFT shall be sent transparently through the SGSN to the GGSN to enable packet classification and policing 
for downlink data transfer. 

Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST, the network shall validate the message by 
verifying the TI given in the Linked TI IE to be any of the active PDP context(s). The same GGSN address shall be 
used by the SGSN as for the already established PDP context(s) for that PDP address. The network shall select a radio 
priority level based on the QoS negotiated and shall reply with an ACTIVATE SECONDARY PDP CONTEXT 
ACCEPT message, if the request can be accepted. 

NOTE 1: If the MS requested a value for a QoS parameter that is not within the range specified by 3GPP TS 23.107 
[81], the network should negotiate the parameter to a value that lies within the specified range. 

Upon receipt of the message ACTIVATE SECONDARY PDP CONTEXT ACCEPT, the MS shall stop timer T3380 
and enter the state PDP-ACTIVE. If the offered QoS parameters received from the network differ from the QoS 
requested by the MS, the MS shall either accept the negotiated QoS or initiate the PDP context deactivation procedure. 

In A/Gb mode the MS shall initiate establishment of the logical link for the LLC SAPI indicated by the network with 
the offered QoS and selected radio priority level if no logical link has been already established for that SAPI. If the LLC 
SAPI indicated by the network can not be supported by the MS, the MS shall initiate the PDP context deactivation 
procedure. 

In lu mode, both SGSN and MS shall store the LLC SAPI and the radio priority in the PDP context. If an lu mode to 
A/Gb mode Routing Area Update is performed, the new SGSN shall initiate establishment of the logical link using the 
negotiated LLC SAPI, the negotiated QoS profile and selected radio priority level stored in the PDP context as in an 
A/Gb mode to A/Gb mode Routing Area Update. 

An MS, which is capable of operating in both A/Gb mode and lu mode, shall use a valid LLC SAPI, while an MS 
which is capable of operating only in lu mode shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order 
to avoid unnecessary value range checking and any other possible confusion in the network. When the MS uses a valid 
LLC SAPI, the network shall return a valid LLC SAPI. The network shall return the 'LLC SAPI not assigned' value 
only when the MS uses the 'LLC SAPI not assigned' value. 

NOTE 2: The radio priority level and the LLC SAPI parameters, though not used in lu mode, shall be included in 
the messages, in order to support handover between lu mode and A/Gb mode networks. 

6.1 .3.2.1a Successful Secondary PDP Context Activation Procedure Requested by the 

network 

In order to request a PDP context activation with the same PDP address and APN as an already active PDP context, the 
network shall send a REQUEST SECONDARY PDP CONTEXT ACTIVATION message to the MS and start timer 
T3385. The message contains the required QoS, Linked TI, and optionally protocol configuration options and a TFT. If 
present, the TFT shall be sent transparently through the SGSN to the MS to enable packet classification and policing for 
uplink and downlink data transfer. 

Upon receipt of a REQUEST SECONDARY PDP CONTEXT ACTIVATION message, the MS shall then either 
initiate the secondary PDP context activation procedure as described in the subclause 6.1.3.2.1 or shall reject the 
activation request by sending a REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message as 
described in subclause 6.1.3.2.2a. The value of the reject cause IE of the REQUEST SECONDARY PDP CONTEXT 
ACTIVATION REJECT message shall indicate the reason for rejection, e.g. "insufficient resources to activate another 
context" . 

The ACTIVATE SECONDARY PDP CONTEXT REQUEST message sent by the MS in order to initiate the secondary 
PDP context activation procedure shall contain the QoS and Linked TI required in the REQUEST SECONDARY PDP 
CONTEXT ACTIVATION message. The MS shall also include a TFT with the downlink packet filters as specified in 
the REQUEST SECONDARY PDP CONTEXT ACTIVATION message. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 220 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

Upon receipt of the ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the network shall stop timer 
T3385. 

The same procedures then apply as described for MS initiated secondary PDP context activation. 

6.1 .3.2.2 Unsuccessful Secondary PDP Context Activation Procedure initiated by the MS 

Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the network may reject the MS 
initiated PDP context activation by sending an ACTIVATE SECONDARY PDP CONTEXT REJECT message to the 
MS. The message shall contain a cause code that typically indicates one of the following: 

# 26: insufficient resources; 

# 30: activation rejected by GGSN; 
#31: activation rejected, unspecified; 

# 32: service option not supported; 

# 33: requested service option not subscribed; 

# 34: service option temporarily out of order; 

# 41 : semantic error in the TFT operation; 

# 42: syntactical error in the TFT operation; 
#43: unknown PDP context; 

# 44: semantic errors in packet filter(s); 

# 45: syntactical errors in packet filter(s); 

# 46: PDP context without TFT already activated; 

# 48: activation rejected. Bearer Control Mode violation; or 

#95: 111: protocol errors. 

Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REJECT message, the MS shall stop timer T3380 and 
enter the state PDP-INACTIVE. 

6.1 .3.2.2a Unsuccessful secondary PDP context activation requested by the network 

Upon receipt of the REQUEST SECONDARY PDP CONTEXT ACTIVATION message, the MS may reject the 
network requested secondary PDP context activation by sending the REQUEST SECONDARY PDP CONTEXT 
ACTIVATION REJECT message to the network. The message contains the same TI as included in the REQUEST 
SECONDARY PDP CONTEXT ACTIVATION and an additional cause code that typically indicates one of the 
following causes: 

# 26: insufficient resources; 

#31: activation rejected, unspecified; 

# 40: feature not supported; 

# 41 : semantic error in the TFT operation; 

# 42: syntactical error in the TFT operation; 

# 43: unknown PDP context; 

# 44: semantic errors in packet filter(s); 

# 45: syntactical errors in packet filter(s); 

# 46: PDP context without TFT already activated; 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 221 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

# 48: activation rejected, Bearer Control Mode violation; or 
#95 - 111: protocol errors. 
The network shall stop timer T3385 and enter state PDP-INACTIVE. 

6.1.3.2.3 Abnormal cases 

The following abnormal cases can be identified: 

a) Expiry of timers 

In the mobile station: 

On the first expiry of the timer T3380, the MS shall resend the ACTIVATE SECONDARY PDP 
CONTEXT REQUEST and shall reset and restart timer T3380. This retransmission is repeated four 
times, i.e. on the fifth expiry of timer T3380, the MS shall release all resources possibly allocated for this 
invocation and shall abort the procedure; no automatic PDP context activation re-attempt shall be 
performed. 

On the network side: 

On the first expiry of the timer T3385, the network shall resend the message REQUEST SECONDARY 
PDP CONTEXT ACTIVATION and shall reset and restart timer T3385. This retransmission is repeated 
four times, i.e. on the fifth expiry of timer T3385, the network shall release possibly allocated resources 
for this activation and shall abort the procedure. 

b) MS initiated secondary PDP context activation procedure for an already activated PDP context (On the network 
side) 

If the NS API matches that of an already activated PDP context, the network shall deactivate the existing PDP 
context locally without notification to the MS and proceed with the requested PDP context activation. The case 
of a TI match is described in subclause 8.3.2. 

c) no PDP context with linked TI activated (on the network side) 

The network shall then check whether there is an activated PDP context for the TI given in the Linked TI IE 
in the ACTIVATE SECONDARY PDP CONTEXT REQUEST message. If there is no active PDP context 
for the specified TI, the network shall reply with an ACTIVATE SECONDARY PDP CONTEXT REJECT 
message, cause code indicating "unknown PDP context". 

d) no PDP context with Linked TI activated (on the mobile station side) 

The MS shall check whether there is an activated PDP context for the TI given in the Linked TI IE in the 
REQUEST SECONDARY PDP CONTEXT ACTIVATION message. If there is no active PDP context for 
the specified TI, the MS shall reply with a REQUEST SECONDARY PDP CONTEXT ACTIVATION 
REJECT message, cause code indicating "unknown PDP context". 

If there exists a PDP context for the TI given in the Linked TI IE, then the TFT in the request message is checked for 
different types of TFT IE errors as follows: 

a) Semantic errors in TFT operations: 

1) When the TFT operation is an operation other than "Create a new TFT" or "No TFT operation". 
The network shall reject the activation request with cause "semantic error in the TFT operation". 
The MS shall reject the activation request with cause "semantic error in the TFT operation". 

b) Syntactical errors in TFT operations: 

1) When the TFT operation = "Create a new TFT" and the packet filter list in the TFT IE is empty. 

2) When the TFT operation = "No TFT operation" with a non-empty packet filter list in the TFT IE. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



222 



ETSI TS 124 008 V7.14.0 (2009-03) 



3) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch 
between the number of packet fihers subfield, and the number of packet fihers in the packet filter list. 

The network shall reject the activation request with cause "syntactical error in the TFT operation". 

The MS shall reject the activation request with cause "syntactical error in the TFT operation". 

c) Semantic errors in packet filters: 

1) When a packet filter consists of conflicting packet filter components which would render the packet 
filter ineffective, i.e. no IP packet will ever fit this packet filter. How the network determines a 
semantic error in a packet filter is outside the scope of the present document. 

The network shall reject the activation request with cause "semantic errors in packet filter(s)". 

The MS shall reject the activation request with cause "semantic errors in packet filter(s)". 

d) Syntactical errors in packet filters: 

1) When the TFT operation = "Create a new TFT" and two or more packet filters in the resultant TFT 
would have identical packet filter identifiers. 

2) When the TFT operation = "Create a new TFT" and two or more packet filters in all TFTs associated 
with this PDP address and APN would have identical packet filter precedence values. 

3) When there are other types of syntactical errors in the coding of packet filters, such as the use of a 
reserved value for a packet filter component identifier. 

In case 2) the network shall not diagnose an error, further process the new activation request and, if it was 
processed successfully, delete the old packet filters which have identical filter precedence values. 
Furthermore, by means of explicit peer-to-peer signalling between the MS and the network, the network shall 
deactivate the PDP context(s) for which it has deleted the packet filters. 

In cases 1) and 3) the network shall reject the activation request with cause "syntactical errors in packet 
filter(s)". 

In case 2) the MS shall not diagnose an error, further process the new activation request and, if it was 
processed successfully, delete the old packet filters which have identical filter precedence values. 
Furthermore, by means of explicit peer-to-peer signalling between the network and the MS, the MS shall 
deactivate the PDP context(s) for which it has deleted the packet filters. 

In cases 1) and 3) the MS shall reject the activation request with cause "syntactical errors in packet filter(s)". 

Otherwise, the network shall accept the activation request by replying to the MS with an ACTIVATE SECONDARY 
PDP CONTEXT ACCEPT message. In case of network requested secondary PDP context activation procedure the MS 
shall accept the activation request by replying to the network with an ACTIVATE SECONDARY PDP CONTEXT 
REQUEST message. 



Start T3380 
Stop T3380 

Stop T3380 


MS Network 
ACTIVATE SECONDARY PDP CONTEXT REQUEST 


ACTIVATE SECONDARY PDP CONTEXT ACCEPT 


or 
ACTIVATE SECONDARY PDP CONTEXT REJECT 





Figure 6.5/3GPP TS 24.008: MS initiated secondary PDP context activation procedure 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



223 



ETSI TS 124 008 V7.14.0 (2009-03) 



Stai1:T3380' 



Stop-T3J80' 



Stop-T33S0' 



MS" 



Network 



REQUEST- SECOND ARY-PDP- C ONTEXT- ACTIVATIONH 
•< StaitTJJS?' 



ACTIVATE- SECOND ARY-PDP- C ONTEXT- REQUESTIT 
► Stop-T33S? 



ACTIVATE- SECONDARY-PDP-C ONTEXT- ACCEPTIJ 



or 



ACTIVATE- SECONDARY-PDP-C ONTEXT- REJECTIJ 



I J 

or 

REQUEST- SECONDARY-PDP-C ONTEXT- ACTIVATION-REJECT^ 

► Stop-T3 J8?' 



Figure 6.5a/3GPP TS 24.008: Network requested secondary PDP context activation procedure 



6.1.3.3 



PDP context modification procedure 



The PDP context modification procedure is invoked by the network or by the MS, in order to change the QoS 
negotiated, the Radio priority level, or the TFT, negotiated during the PDP context activation procedure, the secondary 
PDP context activation procedure or at previously performed PDP context modification procedures. Depending on the 
selected Bearer Control Mode, the MS or the network may also create and delete a TFT in an active PDP context. The 
procedure can be initiated by the network or the MS at any time when a PDP context is active. Only the network may 
modify or delete a TFT packet filter that the network has created and conversely only the MS may modify or delete a 
TFT packet filter that the MS has created. 

The PDP context modification procedure may also be invoked by the MS, in order to upgrade the maximum bit rate and 
to trigger the re-establishment of the radio access bearer for an activated PDP context which is preserved in the MS with 
maximum bit rate values of Okbit/s for both uplink and downlink (see 3GPP TS 23.060 [74]). If 

the PDP Context Modification request is accepted by the network but the radio access bearer is not established; 
or 

the PDP Context Modification request is rejected with cause "insufficient resources" (see subclause 6.1.3.3.3), 

then the MS is not required to start a new PDP Context Modification procedure or to start a Service Request procedure 
in order to trigger the re-establishment of the radio access bearer. 

The network requested PDP context modification procedure may also be used to update the PDP address when external 
PDN address allocation is performed, in which case the MS receives the PDP address in the MODIFY PDP CONTEXT 
REQUEST (Network to MS direction) message. 

NOTE: The procedure may be initiated by the network due to an inter-SGSN Routing Area Updating when a PDP 
context is active. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 224 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

6.1 .3.3.1 Network initiated PDP Context Modification 

In order to initiate the procedure, the network sends the MODIFY PDP CONTEXT REQUEST message to the MS and 
starts timer T3386. The message shall contain the new QoS and the radio priority level and LLC SAPI that shall be used 
by the MS in A/Gb mode at the lower layers for the transmission of data related to the PDP context. The MODIFY PDP 
CONTEXT REQUEST message may also contain modified packet filters in the TFT information element that shall be 
applied to that specific PDP context. 

The network informs the MS about the Bearer Control Mode to be applied for all active PDP contexts sharing the same 
PDP Address and APN by including the selected Bearer Control Mode parameter in the protocol configuration options 
information element. This information is either explicitly given in the MODIFY PDP CONTEXT REQUEST message 
or implicitly given by not being present. The MS shall act according to the presence of the protocol configuration 
options information element and the value of the selected Bearer Control Mode parameter in the MODIFY PDP 
CONTEXT REQUEST message: 

if the protocol configuration options information element is not present, the MS shall apply Bearer Control Mode 
'MS only' for all active PDP contexts sharing the same PDP Address and APN. 

if the selected Bearer Control Mode parameter is not present in the protocol configuration options information 
element, the MS shall apply Bearer Control Mode 'MS only' for all active PDP contexts sharing the same PDP 
Address and APN. 

if the selected Bearer Control Mode parameter is present in the protocol configuration options information 
element, the MS shall apply Bearer Control Mode according to the value of this parameter for all active PDP 
contexts sharing the same PDP Address and APN. 

Upon receipt of the MODIFY PDP CONTEXT REQUEST message the MS shall reply with the MODIFY PDP 
CONTEXT ACCEPT message, if the MS accepts the new QoS and the indicated LLC SAPI. 

The network shall upon receipt of the MODIFY PDP CONTEXT ACCEPT message stop timer T3386. 

In A/Gb mode, the network shall establish, reconfigure or continue using the logical link with the new QoS for the LLC 
SAPI indicated in the MODIFY PDP CONTEXT REQUEST message. 

In lu mode, if the Radio Access Bearer supporting the PDP context is active, then the network shall reconfigure and 
continue using the Radio Access Bearer with the new QoS indicated in the MODIFY PDP CONTEXT REQUEST 
message; if the PDP context is preserved, then the network may re-establish a Radio Access Bearer with the new QoS 
indicated in the MODIFY PDP CONTEXT REQUEST message. 

6.1 .3.3.2 MS initiated PDP Context Modification accepted by the network 

In order to initiate the procedure, the MS sends the MODIFY PDP CONTEXT REQUEST message to the network, 
enters the state PDP-MODIFY-PENDING and starts timer T338L The message may contain the requested new QoS 
and/or the TFT and the requested LLC SAPI (used in A/Gb mode). If the selected Bearer Control Mode is 'MS/NW and 
the MS wants to modify the QoS, it shall include a TFT with packet filter(s), or if no packet filters are proposed to be 
either added, replaced or deleted, it shall include packet filter identifier(s) to indicate which packet filter(s) in the TFT is 
associated with the QoS change. If a PDP context is associated with a TFT containing packet filters established by both 
the MS and the network, the only parameters in the QoS profile of that PDP context the MS is allowed to modify are the 
bitrate parameters. 

Upon receipt of the MODIFY PDP CONTEXT REQUEST message, the network may reply with the MODIFY PDP 
CONTEXT ACCEPT message in order to accept the context modification. The reply message may contain the 
negotiated QoS and the radio priority level based on the new QoS profile and the negotiated LLC SAPI that shall be 
used in A/Gb mode by the logical link. 

Upon receipt of the MODIFY PDP CONTEXT ACCEPT message, the MS shall stop the timer T338L If the offered 
QoS parameters received from the network differs from the QoS requested by the MS, the MS shall either accept the 
negotiated QoS or initiate the PDP context deactivation procedure. 

If a modification of QoS is requested by the MS, which the network can not accept, being unable to provide the 
requested QoS, it should maintain the QoS negotiated as previously negotiated or propose a new QoS. That means that 
the network should not reject the MS initiated PDP context modification request due to the unavailability of the QoS. If 
the MS requested a value for a QoS parameter that is not within the range specified by 3GPP TS 23.107[81], the 
network should negotiate the parameter to a value that lies within the specified range. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 225 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

6.1 .3.3.3 MS initiated PDP Context Modification not accepted by the network 

Upon receipt of a MODIFY PDP CONTEXT REQUEST message, the network may reject the MS initiated PDP 
context modification request by sending a MODIFY PDP CONTEXT REJECT message to the MS. The message shall 
contain a cause code that typically indicates one of the following: 

# 26: insufficient resources; 

# 32: Service option not supported; 

# 41 : semantic error in the TFT operation; 

# 42: syntactical error in the TFT operation; 

# 44: semantic errors in packet filter(s); 

# 45: syntactical errors in packet filter(s); 

# 48: request rejected, Bearer Control Mode violation; or 

# 95 - 111 : protocol errors. 

If upon the reception of a MODIFY PDP CONTEXT REQUEST message the network fails to re-establish the radio 
access bearer for a PDP context whose maximum bit rate in uplink and downlink is set to Okbit/s, the network shall 
reply with MODIFY PDP CONTEXT REJECT with cause "insufficient resources". 

If a TFT modification was requested and the requested new TFT is not available, then MODIFY PDP CONTEXT 
REJECT shall be sent. 

The network shall reply with MODIFY PDP CONTEXT REJECT with cause "request rejected. Bearer Control Mode 
violation", if 

the selected Bearer Control Mode is 'MS/NW and the MS requests to create a TFT for a PDP context that was 
established without TFT; 

the selected Bearer Control Mode is 'MS/NW and the MS requests to upgrade the QoS of a PDP context without 
downlink packet filters, unless uplink packet filters already exist for the PDP context and the MS requests with 
the same MODIFY PDP CONTEXT REQUEST message to create downlink packet filters ; 

the selected Bearer Control Mode is 'MS/NW and the MS requests to modify the QoS, but does not include a 
TFT with at least apacket filter identifier to indicate which packet filter in the TFT that is associated with the 
QoS change; or 

the selected Bearer Control Mode is 'MS/NW and the MS requests to modify the QoS for a PDP context 
associated with a TFT containing packet filters established by both the MS and the network and the MS tries to 
modify other parameters than the bitrate parameters in the QoS profile of that PDP context. 



The TFT in the request message is checked by the receiver for different types of TFT IE errors as follows: 
a) Semantic errors in TFT operations: 

1) TFT operation = "Create a new TFT" when there is already an existing TFT for the PDP context. 

2) When the TFT operation is an operation other than "Create a new TFT" and there is no TFT for the PDP 
context. 

3) TFT operation = "Delete existing TFT" when there is already another PDP context with the same PDP 
address and APN without a TFT. 

4) TFT operation = "Delete packet filters from existing TFT" when it would render the TFT empty. 

In these cases the receiver shall not diagnose an error and perform the following actions to resolve the 
inconsistency: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 226 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

In case 1) the receiver shall further process the new activation request and, if it was processed successfully, 
delete the old TFT. 

In case 2) the receiver shall: 

further process the new request and, if no error according to list items b), c), and d) was detected, consider 
the TFT as successfully deleted, if the TFT operation is "Delete existing TFT" or "Delete packet filters from 
existing TFT" ; 

process the new request as an activation request, if the TFT operation is "Add packet filters in existing TFT" 
or "Replace packet filters in existing TFT". 

In case 3) the receiver shall process the new deletion request and, after successful deletion of the TFT, deactivate 
the old PDF context with the same PDF address and APN without a TFT by explicit peer-to-peer signalling 
between the MS and the network. 

In case 4) the receiver shall further process the new request and, if no error according to list items b), c), and d) 
was detected, delete the existing TFT. After successful deletion of the TFT, if there was already another PDP 
context with the same PDP address and APN without a TFT, the receiver shall deactivate this old PDP context 
without a TFT by explicit peer-to-peer signalling between the MS and the network. 

b) Syntactical errors in TFT operations: 

1) When the TFT operation is an operation other than "Delete existing TFT" or "No TFT operation" and the 
packet filter list in the TFT IE is empty. 

2) TFT operation = "Delete existing TFT" or "No TFT operation" with a non-empty packet filter list in the TFT 
IE. 

3) TFT operation = "Replace packet filters in existing TFT" when a to be replaced packet filter does not exist in 
the original TFT. 

4) TFT operation = "Delete packet filters from existing TFT" when a to be deleted packet filter does not exist in 
the original TFT. 

5) TFT operation = "Delete packet filters from existing TFT" with a packet filter list also including packet 
filters in addition to the packet filter identifiers. 

6) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the 
number of packet filters subfield, and the number of packet filters in the packet filter list. 

In case 3) the receiver shall not diagnose an error, further process the replace request and, if no error according 
to list items c) and d) was detected, include the packet filters received to the existing TFT. 

In case 4) the receiver shall not diagnose an error, further process the deletion request and, if no error according 
to list items c) and d) was detected, consider the respective packet filter as successfully deleted. 

Otherwise the receiver shall reject the modification request with cause "syntactical error in the TFT operation". 

c) Semantic errors in packet filters: 

When a packet filter consists of conflicting packet filter components which would render the packet filter 
ineffective, i.e. no IP packet will ever fit this packet filter. How the receiver determines a semantic error in a 
packet filter is outside the scope of the present document. 

The receiver shall reject the modification request with cause "semantic errors in packet filter(s)". 

d) Syntactical errors in packet filters: 

1) When the TFT operation = "Create a new TFT" or "Add packet filters to existing TFT" and two or more 
packet filters in the resultant TFT would have identical packet filter identifiers. 

2) When the TFT operation = "Create a new TFT" or "Add packet filters to existing TFT" or "Replace packet 
filters in existing TFT" and two or more packet filters in all TFTs associated with this PDP address and APN 
would have identical packet filter precedence values. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 227 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

3) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved 
value for a packet filter component identifier. 

In case 1), if two or more packet filters with identical packet filter identifiers are contained in the new request, 
the receiver shall reject the modification request with cause "syntactical errors in packet filter(s)". Otherwise, the 
receiver shall not diagnose an error, further process the new request and, if it was processed successfully, delete 
the old packet filters which have the identical packet filter identifiers. 

In case 2) the receiver shall not diagnose an error, further process the new request and, if it was processed 
successfully, delete the old packet filters which have identical filter precedence values. Furthermore, by means 
of explicit peer-to-peer signalling between the MS and the network, the receiver shall deactivate the PDP 
context(s) for which it has deleted the packet filters. 

Otherwise the receiver shall reject the modification request with cause "syntactical errors in packet filter(s)". 

Upon receipt of a MODIFY PDP CONTEXT REJECT message, the MS shall stop timer T3381 and enter the state 
PDP-ACTIVE. 

6.1 .3.3.3a Network initiated PDP Context Modification not accepted by the MS 

Upon receipt of a MODIFY PDP CONTEXT REQUEST message, if the MS does not accept the new QoS due to 
resource reasons or the indicated LLC SAPI, the MS shall initiate the PDP context deactivation procedure for the PDP 
context - the reject cause IE value of the DEACTIVATE PDP CONTEXT REQUEST message shall indicate "QoS not 
accepted". 

The MS may reject the network initiated PDP context modification request by sending a MODIFY PDP CONTEXT 
REJECT message to the network. The message shall contain a cause code that typically indicates one of the following: 

# 41 : semantic error in the TFT operation; 

# 42: syntactical error in the TFT operation; 

# 44: semantic errors in packet filter(s); 

# 45: syntactical errors in packet filter(s); 

# 48: request rejected. Bearer Control Mode violation; or 

# 95 - 1 1 1 : protocol errors. 

The MS shall reply with MODIFY PDP CONTEXT REJECT with cause "request rejected. Bearer Control Mode 
violation", if the selected Bearer Control Mode is 'MS only' and the network requests to modify or delete a TFT 

The TFT in the request message is checked by the receiver for different types of TFT IE errors as specified in subclause 
6.L3.3.3. 

Upon receipt of a MODIFY PDP CONTEXT REJECT message, the network shall stop timer T3381 and enter the state 
PDP-ACTIVE. 

6.1.3.3.4 Abnormal cases 

a) Expiry of timers 

On the network side: 

On the first expiry of timer T3386, the network shall resend the MODIFY PDP CONTEXT REQUEST 
message reset and restart timer T3386. This retransmission is repeated four times, i.e. on the fifth expiry of 
timer T3386, the network may continue to use the previously negotiated QoS or it may initiate the PDP 
context deactivation procedure. 

In the MS: 

On the first expiry of timer T3381, the MS shall resend the MODIFY PDP CONTEXT REQUEST message 
reset and restart timer T338L This retransmission is repeated four times, i.e. on the fifth expiry of timer 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



228 



ETSI TS 124 008 V7.14.0 (2009-03) 



T3381, the MS may continue to use the previously negotiated QoS or it may initiate the PDP context 
deactivation procedure. 

b) Collision of MS and Network initiated PDP Context Modification Procedures 

A collision of a MS and network initiated PDP context modification procedures is identified by the MS if a 
MODIFY PDP CONTEXT REQUEST message is received from the network after the MS has sent a MODIFY 
PDP CONTEXT REQUEST message itself, and both messages contain the same TI and the MS has not yet 
received a MODIFY PDP CONTEXT ACCEPT message from the network. 

A collision is detected by the network in case a MODIFY PDP CONTEXT REQUEST message is received from 
the MS with the same TI as the MODIFY PDP CONTEXT REQUEST message sent to the MS. 

In the case of such a collision, the network initiated PDP context modification shall take precedence over the MS 
initiated PDP context modification. The MS shall terminate internally the MS initiated PDP context modification 
procedure, enter the state PDP- Active and proceed with the network initiated PDP context modification 
procedure by sending a MODIFY PDP CONTEXT ACCEPT message. The network shall ignore the MODIFY 
PDP CONTEXT REQUEST message received in the state PDP-MODIFY-PENDING. The network shall 
proceed with the network initiated PDP context modification procedure as if no MODIFY PDP CONTEXT 
REQUEST message was received from the MS. 

c) Collision of MS initiated PDP Context Modification Procedures and Network initiated Deactivate PDP Context 

Request Procedures 

A collision of a MS initiated PDP context modification procedures and a network initiated PDP context 
deactivation procedures is identified by the MS if a DEACTIVATE PDP CONTEXT REQUEST message is 
received from the network after the MS has sent a MODIFY PDP CONTEXT REQUEST message, and the MS 
has not yet received a MODIFY PDP CONTEXT ACCEPT message from the network. 

In the case of such a collision, the network initiated PDP context deactivation shall take precedence over the MS 
initiated PDP context modification. The MS shall terminate internally the MS initiated PDP context modification 
procedure, and proceed with the network initiated PDP context deactivation procedure by sending a 
DEACTIVATE PDP CONTEXT ACCEPT, enter the state PDP-INACTIVE. The network shall ignore the 
MODIFY PDP CONTEXT REQUEST message received in the state PDP-INACTIVE-PENDING. The network 
shall proceed with he network initiated PDP context deactivation procedure as if no MODIFY PDP CONTEXT 
REQUEST message was received from the MS. 



MS 


Network 
MODIFY PDP CONTEXT REQUEST 


Start T3386 
Stop T3386 




MODIFY PDP CONTEXT ACCEPT 







Figure 6.6/3GPP TS 24.008: Network initiated PDP context modification procedure 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



229 



ETSI TS 124 008 V7.14.0 (2009-03) 



MS 



Network 



MODIFY PDP CONTEXT 



Start T3381 



StopT3381 



StopT3381 



MODIFY PDP CONTEXT 



MODIFY PDP CONTEXT 



6.1.3.4 



Figure 6.7/3GPP TS 24.008: MS initiated PDP context modification procedure 



PDP context deactivation procedure 



The purpose of this procedure is to deactivate an existing PDP context between the MS and the network. The PDP 
context deactivation may be initiated by the MS or by the network. The tear down indicator information element may 
be included in the DEACTIVATE PDP CONTEXT REQUEST message in order to indicate whether only the PDP 
context associated with this specific TI or all active PDP contexts sharing the same PDP address and APN as the PDP 
context associated with this specific TI shall be deactivated. If the tear down is requested, all other active PDP contexts 
sharing the same PDP address and APN as the PDP context associated with this specific TI shall be deactivated locally 
without peer-to-peer signalling. If the tear down indicator information element is not included in the DEACTIVATE 
PDP CONTEXT REQUEST message, only the PDP context associated with this specific TI shall be deactivated. 

After successful PDP context deactivation, the associated NSAPI and TI values are released and can be reassigned to 
another PDP context. 

If one or more MBMS contexts are linked to a PDP context that has been deactivated, the MS shall deactivate all those 
MBMS contexts locally (without peer to peer signalling between the MS and the network). 



6.1.3.4.1 



PDP context deactivation initiated by the MS 



In order to deactivate a PDP context, the MS sends a DEACTIVATE PDP CONTEXT REQUEST message to the 
network, enters the state PDP-INACTIVE-PENDING and starts timer T3390. The message contains the transaction 
identifier (TI) in use for the PDP context to be deactivated and a cause code that typically indicates one of the following 

causes: 

# 25: LLC or SNDCP failure (A/Gb mode only); 

# 26: insufficient resources; 

# 36: regular deactivation; or 

# 37: QoS not accepted. 

The network shall reply with the DEACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of the 
DEACTIVATE PDP CONTEXT ACCEPT message, the MS shall stop timer T3390. 

In A/Gb mode, both the MS and the network shall initiate local release of the logical link if it is not used by another 
PDP context. 

In lu mode, the network shall initiate the release of Radio Access Bearer associated with this PDP context. 

If the selected Bearer Control Mode is 'MS/NW the MS should not deactivate a PDP context, if it is the only PDP 
context without TFT within a group of active PDP contexts sharing the same PDP address and APN. 

NOTE 1 : A configuration with more than one PDP context without TFT within a group of active PDP contexts 

sharing the same PDP address and APN can occur during a network initiated PDP context modification 
due to asynchronous TFT states in the MS and in the network (see e.g. subclause 6.1.3.3.3 bullet a.3). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 230 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

NOTE 2: If the MS deactivates the last PDP context without TFT within a group of active PDP contexts sharing the 
same PDP address and APN, the network will initiate the re-establishment of this PDP context using the 
network requested secondary PDP context activation procedure. 



6.1 .3.4.2 PDP context deactivation initiated by the network 

In order to deactivate a PDP context, the network sends a DEACTIVATE PDP CONTEXT REQUEST message to the 
MS and starts timer T3395. The message contains the transaction identifier in use for the PDP context to be deactivated 
and a cause code that typically indicates one of the following causes: 

# 8: Operator Determined Barring; 

# 25: LLC or SNDCP failure (A/Gb mode only); 

# 36: regular deactivation; 

# 38: network failure; or 

# 39: reactivation requested. 

The MS shall, upon receipt of this message, reply with a DEACTIVATE PDP CONTEXT ACCEPT message. Upon 
receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the network shall stop the timer T3395. 

In A/Gb mode, both the MS and the network shall initiate local release of the logical link if it is not used by another 
PDP context. 

In lu mode, the network shall initiate the release of Radio Access Bearer associated with this PDP context. 

6.1.3.4.3 Abnormal cases 

The following abnormal cases can be identified: 

a) Expiry of timers 

In the mobile station: 

On the first expiry of timer T3390, the MS shall resent the message DEACTIVATE PDP CONTEXT 
REQUEST and shall reset and restart the timer T3390. This retransmission is repeated four times, i.e. on the 
fifth expiry of timer T3390, the MS shall release all resources allocated and shall erase the PDP context 
related data. 

On the network side: 

On the first expiry of timer T3395, the network shall resent the message DEACTIVATE PDP CONTEXT 
REQUEST and shall reset and restart timer T3395. This retransmission is repeated four times, i.e. on the fifth 
expiry of timer T3395, the network shall erase the PDP context related data for that MS. 

b) Collision of MS and network initiated PDP context deactivation requests 

If the MS and the network initiated PDP context deactivation requests collide, the MS and the network shall each 
reply with the messages DEACTIVATE PDP CONTEXT ACCEPT and shall stop timer T3390 and T3395, 
respectively. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



231 



ETSI TS 124 008 V7.14.0 (2009-03) 





MS 


Network 
DEACTIVATE PDP CONTEXT REQUEST 


Start T3390 










Stop T3390 




DEACTIVATE PDP CONTEXT ACCEPT 







Figure 6.8/3GPP TS 24.008: MS initiated PDP context deactivation procedure 



MS Network 

DEACTIVATE PDP CONTEXT REQUEST 



DEACTIVATE PDP CONTEXT ACCEPT 



Start T3395 



-► Stop T3395 



Figure 6.9/3GPP TS 24.008: Networit initiated PDP context deactivation procedure 



6.1.3.4a 



Void 



6.1.3.5 



Void 



6.1.3.6 



Receiving a SM STATUS message by a SM entity 



If the SM entity of the MS receives an SM STATUS message the MS shall take different actions depending on the 
received SM cause value: 

#8 1 Invalid transaction identifier value 

The MS shall abort any ongoing SM procedure related to the received transaction identifier value, stop any 
related timer, and deactivate the corresponding PDP or MBMS context locally (without peer to peer signalling 
between the MS and the network). 

If one or more MBMS contexts are linked to a PDP context that has been deactivated, the MS shall deactivate all 
those MBMS Contexts locally (without peer to peer signalling between the MS and the network). 

#97 Message type non-existent or not implemented 

The MS shall abort any ongoing SM procedure related to the received transaction identifier value and stop any 
related timer. 

If the SM entity of the MS receives a SM STATUS message with any other SM cause value no state transition and no 
specific action shall be taken as seen from the radio interface, i.e. local actions are possible. 

If the SM entity of the network receives an SM STATUS message the network shall take different actions depending on 
the received SM cause value: 

#8 1 Invalid transaction identifier value 

The network shall abort any ongoing SM procedure related to the received transaction identifier value, stop any 
related timer, and deactivate the corresponding PDP or MBMS context locally (without peer to peer signalling 
between the MS and the network). 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 232 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If one or more MBMS contexts are linked to a PDP context that has been deactivated, the MS shall deactivate all 
those MBMS Contexts locally (without peer to peer signalling between the MS and the network). 

#97 Message type non-existent or not implemented 

The network shall abort any ongoing SM procedure related to the received transaction identifier value and stop 
any related timer. 

The actions to be taken in the network on receiving a SM STATUS message with any other SM cause value are an 
implementation dependent option. 

6.1 .3.7 Protocol configuration options 

The MS and the GGSN may communicate parameters by means of the protocol configuration options information 
element when activating, modifying or deactivating a PDP context. Such parameters can e.g. be used to convey 
information from external protocols between the MS and the GGSN. An overview of how the protocol configuration 
options information element is used is specified in 3GPP TS 27.060 [36a]. 

The protocol configuration options information element is transparent to the SGSN. 

6.1 .3.8 MBMS context activation 

The purpose of this procedure is to establish an MBMS context in the MS and in the network for a specific IP Multicast 
Address using a specific NSAPI for MBMS user plane transmission. The MS shall only initiate the MBMS context 
activation when requested by the network. However, the trigger for the activation request by the network is initiated by 
the MS at the appHcation layer (see 3GPP TS 23.246 [106]). 

6.1 .3.8.1 Successful MBMS context activation 

In order to request an MBMS context activation, the network sends a REQUEST MBMS CONTEXT ACTIVATION 
message to the MS, enters the state MBMS-ACTIVE-PENDING and starts timer T3385. The message shall contain the 
IP multicast address, the APN and the Linked NSAPI. 

Upon receipt of a REQUEST MBMS CONTEXT ACTIVATION message, the MS shall validate the message by 
verifying the NSAPI given in the Linked NSAPI IE to be one of the active PDP context(s), and send an ACTIVATE 
MBMS CONTEXT REQUEST, enter state MBMS-ACTIVE-PENDING and start timer T3380. The message shall 
contain an IP multicast address and an APN, which shall be the same as the IP multicast address and the APN requested 
by the network in the REQUEST MBMS CONTEXT ACTIVATION message. Furthermore, the MS shall include the 
Supported MBMS bearer capabilities, i.e. the maximum downlink bit rate the MS can handle. 

Upon receipt of the ACTIVATE MBMS CONTEXT REQUEST message, the network shall stop timer T3385. If the 
network accepts the request, it shall reply with an ACTIVATE MBMS CONTEXT ACCEPT message. 

Upon receipt of the message ACTIVATE MBMS CONTEXT ACCEPT the MS shall stop timer T3380 and shall enter 
the state MBMS -ACTIVE. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 233 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

6.1 .3.8.2 Unsuccessful MBMS context activation requested by the MS 

Upon receipt of an ACTIVATE MBMS CONTEXT REQUEST message the network may reject the MS initiated 
MBMS context activation by sending an ACTIVATE MBMS CONTEXT REJECT message to the MS. The sender of 
the message shall include the same TI as included in the ACTIVATE MBMS CONTEX REQUEST and an additional 
cause code that typically indicates one of the following causes: 

#8: Operator Determined Barring; 

# 24: MBMS bearer capabilities insufficient for the service; 

# 26: insufficient resources; 

# 27: missing or unknown APN; 

# 29: user authentication failed; 

# 30: activation rejected by GGSN; 
#31: activation rejected, unspecified; 

# 32: service option not supported; 

# 33: requested service option not subscribed; 

# 34: service option temporarily out of order; or 

# 95 - # 111 : protocol errors. 

Upon receipt of an ACTIVATE MBMS CONTEXT REJECT message, the MS shall stop timer T3380 and enter/remain 
in state PDP-INACTIVE. 

6.1 .3.8.3 Unsuccessful MBMS context activation requested by the network 

Upon receipt of the REQUEST MBMS CONTEXT ACTIVATION message, the MS may reject the network requested 
MBMS context activation by sending the REQUEST MBMS CONTEXT ACTIVATION REJECT message to the 
network. The sender of the message shall include the same TI as included in the REQUEST MBMS CONTEXT 
ACTIVATION and an additional cause code that typically indicates one of the following causes: 

# 26: insufficient resources; 

#31: activation rejected, unspecified; 

# 40: feature not supported; or 

# 95 - # 1 11 : protocol errors. 

The network shall stop timer T3385 and enter in state PDP-INACTIVE. 

6.1.3.8.4 Abnormal cases 

The following abnormal cases can be identified: 

a) Expiry of timers in the mobile station: On the first expiry of the timer T3380, the MS shall resend the 
ACTIVATE MBMS CONTEXT REQUEST and shall reset and restart timer T3380. This retransmission is 
repeated four times, i.e. on the fifth expiry of timer T3380, the MS shall release all resources possibly allocated 
for this invocation and shall abort the procedure; no automatic MBMS context activation re-attempt shall be 
performed. 

b) Expiry of timers on the network side: On the first expiry of the timer T3385, the network shall resend the 
message REQUEST MBMS CONTEXT ACTIVATION and shall reset and restart timer T3385. This 
retransmission is repeated four times, i.e. on the fifth expiry of timer T3385, the network shall release possibly 
allocated resources for this activation and shall abort the procedure. 

c) MBMS context activation request for an already activated MBMS context (on the mobile station side): If the 
MS receives a REQUEST MBMS CONTEXT ACTIVATION message with the same combination of APN and 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



234 



ETSI TS 124 008 V7.14.0 (2009-03) 



IP multicast address (i.e. PDP type and PDP address) as an already activated MBMS context, the MS shall 
deactivate the existing MBMS context locally without notification to the network and proceed with the requested 
MBMS context activation. 

d) MBMS context activation request for an already activated MBMS context (on the network side): If the network 
receives an ACTIVATE MBMS CONTEXT REQUEST message with the same combination of APN and IP 
multicast address (i.e. PDP type and PDP address) as an already activated MBMS context, the network shall 
deactivate the existing MBMS context locally without notification to the MS and proceed with the requested 
MBMS context activation. 



MS 



Network 



Start T3380 



REQUEST MBMS CONTEXT ACTIVATION 

*• Start T3385 

1 

ACTIVATE MBMS CONTEXT REQUEST 

*' StopT3385l 



Stop T3380 *" 



Stop T3380 



ACTIVATE MBMS CONTEXT ACCEPT 



or 



ACTIVATE MBMS CONTEXT REJECT 



or 
REQUEST MBMS CONTEXT ACTIVATION REJECT 



Stop T3385 



Figure 6.10/3GPP TS 24.008: MBMS context activation procedure 



6.1.3.9 



MBMS context deactivation 



The purpose of this procedure is to deactivate an existing MBMS context in the MS and the network. The MS shall only 
initiate the MBMS context deactivation when requested by the network, however the trigger for the deactivation request 
by the network may be initiated by the MS at application layer or by the network, see 3GPP TS 23.246 [106]. 

After a successful MBMS context deactivation, the associated MBMS NSAPI and TI values shall be released in both 
the MS and the network and can be reassigned to another MBMS context. 

The MBMS context deactivation procedure makes use of the messaging and signalling of the PDP context deactivation 
procedure as described in the subclauses 6.1.3.9.1 and 6.1.3.9.2. 



6.1.3.9.1 



MBMS context deactivation initiated by the network 



In order to request an MBMS context deactivation, the network sends a DEACTIVATE PDP CONTEXT REQUEST 
message to the MS, enters the state MBMS -INACTIVE-PENDING and starts timer T3395. The message contains the 
transaction identifier (TI) in use for the MBMS context to be deactivated and a cause code that typically indicates one 
of the following causes: 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



235 



ETSI TS 124 008 V7.14.0 (2009-03) 



# 36: regular deactivation; 

# 38: network failure; 

# 47: multicast group membership time-out. 

The MS shall reply with a DEACTIVATE PDP CONTEXT ACCEPT message and enter the state PDP-INACTIVE. 
Upon receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the network shall stop the timer T3395 and 
enter the state PDP-INACTIVE. 

6.1.3.9.2 Abnormal cases 

The following abnormal cases can be identified: 

a) Expiry of timers: 

On the first expiry of the timer T3395, the network shall resend the message DEACTIVATE PDP 
CONTEXT REQUEST and shall reset and restart the timer T3395. This retransmission is repeated, i.e. on the 
fifth expiry of the timer T3395, the network shall erase the MBMS context related data for that MS. 



MS Network 

DEACTIVATE PDP CONTEXT REQUEST 



DEACTIVATE PDP CONTEXT ACCEPT 



Start T3395 



-+ Stop T3395 



Figure 6.11/3GPP TS 24.008: MBMS context deactivation procedure 



6.1 .3.10 MBMS protocol configuration options 

The MS and the GGSN may communicate parameters related to the MBMS bearer by means of the MBMS protocol 
configuration options information element when activating or deactivating an MBMS context. For example, such 
parameters can be used to convey information between the MS and the GGSN. 

The MBMS protocol configuration options information element is transparent to the SGSN. 



6.2 



void 



Examples of structured procedures 



See 3GPPTS 23.108 [9a]. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 236 ETSI TS 124 008 V7.14.0 (2009-03) 

8 Handling of unknown, unforeseen, and erroneous 

protocol data 

8.1 General 

The procedures specified in 3GPP TS 24.008 and call-related supplementary service handling in 3GPP TS 24.010 [21] 
apply to those messages which pass the checks described in this subclause. 

This subclause also specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the 
receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery 
mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. 

Error handling concerning the value part of the Facility IE and of the SS Version Indicator IE are not in the scope of the 
present document. It is defined in 3GPP TS 24.010 [21] and the 3GPP TS 24.08x series. 

Sub subclauses 8.1 to 8.8 shall be applied in order of precedence. 

Most error handling procedures are mandatory for the mobile station. 

Detailed error handling procedures in the network are implementation dependent and may vary from PLMN to PLMN. 
However, when extensions of this protocol are developed, networks will be assumed to have the error handling that is 
indicated in this subclause as mandatory ("shall") and that is indicated as strongly recommended ("should"). 
Subclauses 8.2, 8.3, 8.4, 8.5 and 8.7.2 do not apply to the error handling in the network applied to the receipt of initial 
layer 3 message: If the network diagnoses an error described in one of these subclause s in the initial layer 3 message 
received from the mobile station, it shall either: 

try to recognize the classmark and then take further implementation dependent actions; or 

release the RR-connection. 

Also, the error handling of the network is only considered as mandatory or strongly recommended when certain 
thresholds for errors are not reached during a dedicated connection. 

For definition of semantical and syntactical errors see 3GPP TS 24.007 [20], subclause 11.4.2. 

8.2 Message too short 

When a message is received that is too short to contain a complete message type information element, that message 
shall be ignored, cf 3GPP TS 24.007 [20]. 

8.3 Unknown or unforeseen transaction identifier 
8.3.1 Call Control 

The mobile station and the network shall ignore a Call Control message received with TI EXT bit = 0. Otherwise, if the 
TI EXT bit =1 or no extension is used, the behaviour described below shall be followed. 

The mobile station and network shall reject a SETUP, EMERGENCY SETUP or START CC message received with 
octet 1 part of the TI value coded as " 1 1 1 " by sending RELEASE COMPLETE with cause #8 1 "Invalid transaction 
identifier value" The TI value in RELEASE COMPLETE shall be the complete TI value including the extension octet 
from the message that caused the rejection. 

Any message other than SETUP, EMERGENCY SETUP or START CC received with octet 1 part of the TI value 
coded as "111" shall be ignored. 

For a call control message received with octet 1 part of the TI value not coded as "111", the following procedures shall 
apply: 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 237 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

a) For a network that does not support the "Network initiated MO call" option and for all mobile stations: 

Whenever any call control message except EMERGENCY SETUP, SETUP or RELEASE COMPLETE is 
received specifying a transaction identifier which is not recognized as relating to an active call or to a call in 
progress, the receiving entity shall send a RELEASE COMPLETE message with cause #81 "invalid transaction 
identifier value" using the received transaction identifier value and remain in the Null state. 

For a network that does support the "Network initiated MO call" option $(CCBS)$: 

Whenever any call control message except EMERGENCY SETUP, SETUP, START CC or RELEASE 
COMPLETE is received specifying a transaction identifier which is not recognized as relating to an active call or 
to a call in progress, the receiving entity shall send a RELEASE COMPLETE message with cause #81 "invalid 
transaction identifier value" using the received transaction identifier value and remain in the Null state. 

b) When a RELEASE COMPLETE message is received specifying a transaction identifier which is not recognized 
as relating to an active call or to a call in progress, the MM connection associated with that transaction identifier 
shall be released. 

c) For a network that does not support the "Network initiated MO call" option and for all mobile stations: 

When an EMERGENCY SETUP or, a SETUP message is received specifying a transaction identifier which is 
not recognized as relating to an active call or to a call in progress, and with a transaction identifier flag 
incorrectly set to " 1 ", this message shall be ignored. 

For a network that does support the "Network initiated MO call" option $(CCBS)$: 

When an EMERGENCY SETUP, a START CC or, a SETUP message is received specifying a transaction 
identifier which is not recognised as relating to an active call or to a call in progress, and with a transaction 
identifier flag incorrectly set to "1", this message shall be ignored. 

d) When a SETUP message is received by the mobile station specifying a transaction identifier which is recognized 
as relating to an active call or to a call in progress, this SETUP message shall be ignored. 

e) For a network that does not support the "Network initiated MO call" option: 

When an EMERGENCY SETUP message or a SETUP message is received by the network specifying a 
transaction identifier which is recognized as relating to an active call or to a call in progress, this message need 
not be treated and the network may perform other actions. 

For a network that does support the "Network initiated MO call" option $(CCBS)$: 

When an EMERGENCY SETUP message or a START CC message is received by the network specifying a 
transaction identifier which is recognised as relating to an active call or to a call in progress, this message need 
not be treated and the network may perform other actions. 

The same applies to a SETUP message unless the transaction has been established by a START_CC message 
and the network is in the "recall present" state (N0.6). 



8.3.2 Session Management 



The mobile station and network shall ignore a session management message with TI EXT bit = 0. Otherwise, the 
following procedures shall apply: 

a) Whenever any session management message except ACTIVATE PDP CONTEXT REQUEST, ACTIVATE 
SECONDARY PDP CONTEXT REQUEST, or SM-STATUS is received by the network specifying a 
transaction identifier which is not recognized as relating to an active PDP context or MBMS context,or to a PDP 
context or MBMS context that is in the process of activation or deactivation, the network shall send a SM- 
STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier 
value including the extension octet and remain in the PDP-IN ACTIVE state. 

b) Whenever any session management message except REQUEST PDP CONTEXT ACTIVATION, REQUEST 
SECONDARY PDP CONTEXT ACTIVATION, REQUEST MBMS CONTEXT ACTIVATION, or SM- 
STATUS is received by the MS specifying a transaction identifier which is not recognized as relating to an 
active context or to a context that is in the process of activation or deactivation, the MS shall send a SM- 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 238 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier 
value including the extension octet and remain in the PDP-INACTIVE state. 

c) When a REQUEST PDP CONTEXT ACTIVATION message, REQUEST SECONDARY PDP CONTEXT 
ACTIVATION message or REQUEST MBMS CONTEXT ACTIVATION message is received by the MS with 
a transaction identifier flag set to "1", this message shall be ignored. 

d) When an ACTIVATE PDP CONTEXT REQUEST message is received by the network specifying a transaction 
identifier which is not recognized as relating to a PDP context that is in the process of activation, and with a 
transaction identifier flag set to "1", this message shall be ignored. 

e) Whenever an ACTIVATE PDP CONTEXT REQUEST or ACTIVATE SECONDARY PDP CONTEXT 
REQUEST message is received by the network specifying a transaction identifier relating to a PDP context or 
MBMS context not in state PDP-INACTIVE, the network shall deactivate the old PDP context or MBMS 
context relating to the received transaction identifier without notifying the MS. Furthermore, the network shall 
continue with the activation procedure of a new PDP context as indicated in the received message. Whenever an 
ACTIVATE MBMS CONTEXT REQUEST message is received by the network specifying a transaction 
identifier relating to an MBMS context not in state PDP-INACTIVE, the network shall deactivate the old MBMS 
context relating to the received transaction identifier without notifying the MS. Furthermore, the network shall 
continue with the activation procedure of a new MBMS context as indicated in the received message. 

f) Whenever a REQUEST PDP CONTEXT ACTIVATION message or REQUEST SECONDARY PDP 
CONTEXT ACTIVATION message is received by the MS specifying a transaction identifier relating to a PDP 
context or MBMS context not in state PDP-INACTIVE, the MS shall locally deactivate the old PDP context or 
MBMS context relating to the received transaction identifier. Furthermore, the MS shall continue with the 
activation procedure of a new PDP context as indicated in the received message. 

Whenever a REQUEST MBMS CONTEXT ACTIVATION message is received by the MS specifying a 
transaction identifier relating to a PDP context or MBMS context not in state PDP-INACTIVE, the MS shall 
locally deactivate the old PDP context or MBMS context relating to the received transaction identifier. 
Furthermore, the MS shall continue with the activation procedure of a new MBMS context as indicated in the 
received message. 

g) When an ACTIVATE SECONDARY PDP CONTEXT REQUEST message is received by the network 
specifying a transaction identifier which is not recognized as relating to a PDP context that is in the process of 
activation and with a transaction identifier flag set to "1", this message shall be ignored. 

8.4 Unknown or unforeseen message type 

If a mobile station receives an RR, MM or CC message with message type not defined for the PD or not implemented 
by the receiver in unacknowledged mode, it shall ignore the message. 

If a mobile station receives an RR, MM or CC message with message type not defined for the PD or not implemented 
by the receiver in acknowledged mode, it shall return a status message (STATUS, MM STATUS depending on the 
protocol discriminator) with cause # 97 "message type non-existent or not implemented". 

If a mobile station receives a GMM message or SM message with message type not defined for the PD or not 
implemented by the receiver, it shall return a status message (GMM STATUS or SM STATUS depending on the 
protocol discriminator) with cause # 97 "message type non-existent or not implemented". 

If the network receives an MM message with message type not defined for the PD or not implemented by the receiver in 
a protocol state where reception of an unsolicited message with the given PD from the mobile station is not foreseen in 
the protocol, the network actions are implementation dependent. Otherwise, if the network receives a message with 
message type not defined for the PD or not implemented by the receiver, it shall ignore the message except that it 
should return a status message (STATUS, MM STATUS, GMM STATUS or SM STATUS depending on the protocol 
discriminator) with cause #97 "message type non-existent or not implemented". 

NOTE: A message type not defined for the PD in the given direction is regarded by the receiver as a message 
type not defined for the PD, see 3GPP TS 24.007 [20]. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 239 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

If the mobile station receives a message not compatible with the protocol state, the mobile station shall ignore the 
message except for the fact that, if an RR connection exists, it returns a status message (STATUS, MM STATUS 
depending on the protocol discriminator) with cause #98 "Message type not compatible with protocol state". When the 
message was a GMM message the GMM-STATUS message with cause #98 "Message type not compatible with 
protocol state" shall be returned. When the message was a SM message the SM-STATUS message with cause #98 
"Message type not compatible with protocol state" shall be returned. 

If the network receives a message not compatible with the protocol state, the network actions are implementation 
dependent. 

NOTE: The use by GMM and SM of unacknowledged LLC may lead to messages "not compatible with the 
protocol state". 

8.5 Non-semantical mandatory information element errors 

When on receipt of a message, 

an "imperative message part" error; or 

a "missing mandatory IE" error; 
is diagnosed or when a message containing: 

a syntactically incorrect mandatory IE; or 

an IE unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.007); or 

an out of sequence IE encoded as "comprehension required" (see 3GPP TS 24.007) is received, 

the mobile station shall proceed as follows: 

If the message is not one of the messages listed in subclauses 8.5.1, 8.5.2, 8.5.3, 8.5.4 and 8.5.5 a), b) or f), the 
mobile station shall ignore the message except for the fact that, if an RR connection exists, it shall return a status 
message (STATUS, MM STATUS depending on the protocol discriminator) with cause # 96 "Invalid mandatory 
information". If the message was a GMM message the GMM-STATUS message with cause #96 " Invalid 
mandatory information" shall be returned. If the message was an SM message the SM-STATUS message with 
cause # 96 "invalid mandatory information" shall be returned. 

the network shall proceed as follows: 

When the message is not one of the messages listed in subclause 8.5.3 b), c), d) or e) and 8.5.5 a), c), d), e) or 
g), the network shall either: 

try to treat the message (the exact further actions are implementation dependent), or 

ignore the message except that it should return a status message (STATUS, or MM STATUS (depending 
on the protocol discriminator), GMM STATUS, or SM STATUS) with cause # 96 "Invalid mandatory 
information". 

8.5.1 Radio resource management 

See 3GPPTS 44.018 [84]. 

8.5.2 IVIobility management 

No exceptional cases are described for mobility management messages. 

8.5.3 Call control 

a) If the message is a SETUP message, a RELEASE COMPLETE message with cause # 96 "invalid mandatory 
information" shall be returned. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 240 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

b) If the message is a DISCONNECT message, a RELEASE message shall be returned with cause value # 96 
"invalid mandatory information" and subclause 5.4. "call clearing" applies as normal. 

c) If the message is a RELEASE message, a RELEASE COMPLETE message shall be returned with cause value # 
96 "invalid mandatory information". 

d) If the message is a RELEASE COMPLETE message, it shall be treated as a normal RELEASE COMPLETE 

message. 

e) If the message is a HOLD REJECT or RETRIEVE REJECT message, it shall be treated as a normal HOLD 
REJECT or RETRIEVE REJECT message. 

f) If the message is a STATUS message and received by the network, a RELEASE COMPLETE message may be 
returned with cause value # 96 "invalid mandatory information". 

8.5.4 GMM mobility management 

No exceptional cases are described for mobility management messages. 

8.5.5 Session management 

a) If the message is a DEACTIVATE PDP CONTEXT REQUEST, a DEACTIVATE PDP CONTEXT ACCEPT 
message shall be returned. All resources allocated for that context shall be released. 

b) If the message is a REQUEST PDP CONTEXT ACTIVATION, a REQUEST PDP CONTEXT ACTIVATION 
REJECT message with cause # 96 "Invalid mandatory information" shall be returned. 

c) If the message is an ACTIVATE PDP CONTEXT REQUEST, an ACTIVATE PDP CONTEXT REJECT 
message with cause # 96 "Invalid mandatory information" shall be returned. 

d) If the message is an ACTIVATE SECONDARY PDP CONTEXT REQUEST, an ACTIVATE SECONDARY 
PDP CONTEXT REJECT message with cause # 96 "Invalid mandatory information" shall be returned. 

e) If the message is a MODIFY PDP CONTEXT REQUEST, a MODIFY PDP CONTEXT REJECT message with 
cause # 96 "Invalid mandatory information" shall be returned. 

f) If the message is a REQUEST MBMS CONTEXT ACTIVATION, a REQUEST MBMS CONTEXT 
ACTIVATION REJECT message with cause # 96 "Invalid mandatory information" shall be returned. 

g) If the message is an ACTIVATE MBMS CONTEXT REQUEST, an ACTIVATE MBMS CONTEXT REJECT 
message with cause # 96 "Invalid mandatory information" shall be returned. 

h) If the message is a REQUEST SECONDARY PDP CONTEXT ACTIVATION, a REQUEST SECONDARY 
PDP CONTEXT ACTIVATION REJECT message with cause # 96 "Invalid mandatory information" shall be 
returned. 

8.6 Unknown and unforeseen lEs in tine non-imperative 
message part 

8.6.1 lEIs unknown in tine message 

The MS shall ignore all lEs unknown in a message which are not encoded as "comprehension required" (see 
3GPP TS 24.007). 

The network shall take the same approach. 

8.6.2 Out of sequence lEs 

The MS shall ignore all out of sequence lEs in a message which are not encoded as "comprehension required" (see 
3GPP TS 24.007). 

The network should take the same approach. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 241 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

8.6.3 Repeated lEs 

If an information element with format T, TV, or TLV is repeated in a message in which repetition of the information 
element is not specified in clause 9 of the present document, only the contents of the information element appearing 
first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of 
information elements is specified, only the contents of specified repeated information elements shall be handled. If the 
limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the 
limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. 

The network should follow the same procedures. 

8.7 Non-imperative message part errors 

This category includes: 

syntactically incorrect optional lEs; 
conditional IE errors. 

8.7.1 Syntactically incorrect optional lEs 

The MS shall treat all optional IBs that are syntactically incorrect in a message as not present in the message. 
The network shall take the same approach. 

8.7.2 Conditional IE errors 

When the MS upon receipt of an RR, MM or CC message diagnoses a "missing conditional IE" error or an "unexpected 
conditional IE" error or when it receives an RR, MM or CC message containing at least one syntactically incorrect 
conditional IE, it shall ignore the message except for the fact that, if an RR connection exists, it shall return a status 
message (STATUS, or MM STATUS depending on the PD) with cause value # 100 "conditional IE error". 

When the MS upon receipt of a GMM or SM message diagnoses a "missing conditional IE" error or an "unexpected 
conditional IE" error or when it receives a GMM or SM message containing at least one syntactically incorrect 
conditional IE, it shall ignore the message and it shall return a status message (GMM STATUS or SM STATUS 
depending on the PD) with cause value # 100 "conditional IE error". 

When the network receives a message and diagnose a "missing conditional IE" error or an "unexpected conditional IE" 
error or when it receives a message containing at least one syntactically incorrect conditional IE, the network shall 
either 

try to treat the message (the exact further actions are implementation dependent), or 

- ignore the message except that it should return a status message (STATUS, MM STATUS, GMM STATUS or 
SM STATUS depending on the protocol discriminator) with cause #100 "conditional IE error". 

8.8 Messages with semantically incorrect contents 

When a message with semantically incorrect contents is received, the foreseen reactions of the procedural part of 3GPP 
TS 24.008 (i.e. of clauses 3, 4, 5, 6) are performed. If however no such reactions are specified, the MS shall ignore the 
message except for the fact that, if an RR connection exists, it returns a status message (STATUS, or MM STATUS 
depending on the PD) with cause value # 95 "semantically incorrect message". If the message was a GMM message the 
GMM-STATUS message with cause #95 "semantically incorrect message" shall be returned. If the message was an SM 
message the SM-STATUS message with cause # 95 "semantically incorrect message" shall be returned. 

The network should follow the same procedure except that a status message is not normally transmitted. 

Semantic checking of the Facility information element value part (defined in 3GPP TS 24.080 [24]) is the subject of the 
technical specifications 3GPP TS 24.010 [21] and the 3GPP TS 24.08x series. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 242 ETSI TS 124 008 V7.14.0 (2009-03) 

9 Message functional definitions and contents 

This clause defines the structure of the messages of those layer 3 protocols defined in 3GPP TS 24.008. These are 
standard L3 messages as defined in 3GPP TS 24.007 [20]. 

Each definition given in the present clause includes: 

a) a brief description of the message direction and use, including whether the message has: 

1. Local significance, i.e. relevant only on the originating or terminating access; 

2. Access significance, i.e. relevant in the originating and terminating access, but not in the network; 

3. Dual significance, i.e. relevant in either the originating or terminating access and in the network; or 

4. Global significance, i.e. relevant in the originating and terminating access and in the network. 

b) a table listing the information elements known in the message and their order of their appearance in the message. 
In messages for circuit-switched call control also a shift information element shall be considered as known even 
if not included in the table. All information elements that may be repeated are explicitly indicated. (V and LV 
formatted lEs, which compose the imperative part of the message, occur before T, TV, and TLV formatted IBs 
which compose the non-imperative part of the message, cf. 3GPP TS 24.007.) In a (maximal) sequence of 
consecutive information elements with half octet length, the first information element with half octet length 
occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet Nh-1 etc. Such a 
sequence always has an even number of elements. 

For each information element the table indicates: 

1 . the information element identifier, in hexadecimal notation, if the IE has format T, TV, or TLV. Usually, 
there is a default lEI for an information element type; default lEIs of different IE types of the same protocol 
are different. If the lEI has half octet length, it is specified by a notation representing the lEI as a 
hexadecimal digit followed by a "-" (example: B-). 

NOTE 1: The same lEI may be used for different information element types in different messages of the same 
protocol.. 

NOTE 2: In the CC protocol the lEI of the locking shift and non-locking shift information elements is the same in 
all messages and is not used for any other information elements. 

2. the name of the information element (which may give an idea of the semantics of the element). The name of 
the information element (usually written in italics) followed by "IE" or "information element" is used in 
3GPP TS 24.008 as reference to the information element within a message. 

3. the name of the type of the information element (which indicates the coding of the value part of the IE), and 
generally, the referenced subclause of clause 10 of 3GPP TS 24.008 describing the value part of the 
information element. 

4. the presence requirement indication (M, C, or O) for the IE as defined in 3GPP TS 24.007 [20]. 

5. The format of the information element (T, V, TV, LV, TLV) as defined in 3GPP TS 24.007 [20]. 

6. The length of the information element (or permissible range of lengths), in octets, in the message, where "?" 
means that the maximum length of the IE is only constrained by link layer protocol, and in the case of the 
Facility IE by possible further conditions specified in 3GPP TS 24.010 [21]. This indication is non- 
normative. 

c.) subclauses specifying, where appropriate, conditions for lEs with presence requirement C or O in the relevant 
message which together with other conditions specified in 3GPP TS 24.008 define when the information 
elements shall be included or not, what non-presence of such lEs means, and - for lEs with presence requirement 
C - the static conditions for presence and/or non-presence of the lEs (see 3GPP TS 24.007 [20]). 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



243 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.1 Messages for Radio Resources management 



See 3GPPTS 44.018 [84]. 



9.2 Messages for mobility management 

Table 9.2.1/3GPP TS 24.008 summarizes the messages for mobility management. 

Table 9.2.1/3GPP TS 24.008: Messages for mobility management 



Registration messages: 


Reference 


IMSI DETACH INDICATION 


9.2.12 


LOCATION UPDATING ACCEPT 


9.2.13 


LOCATION UPDATING REJECT 


9.2.14 


LOCATION UPDATING REOUEST 


9.2.15 


Security messages: 


Reference 


AUTHENTICATION REJECT 


9.2.1 


AUTHENTICATION REQUEST 


9.2.2 


AUTHENTICATION RESPONSE 


9.2.3 


AUTHENTICATION FAILURE 


9.2.3a 


IDENTITY REOUEST 


9.2.10 


IDENTITY RESPONSE 


9.2.11 


TMSI REALLOCATION COMMAND 


9.2.17 


TMSI REALLOCATION COMPLETE 


9.2.18 


Connection management messages: 


Reference 


CM SERVICE ACCEPT 


9.2.5 


CM SERVICE PROMPT 


9.2.5a 


CM SERVICE REJECT 


9.2.6 


CM SERVICE ABORT 


9.2.7 


CM SERVICE REQUEST 


9.2.9 


CM RE-ESTABLISHMENT REQUEST 


9.2.4 


ABORT 


9.2.8 


Miscellaneous message: 


Reference 


MM INFORMATION 


9.2.15a 


MM STATUS 


9.2.16 


MM NULL 


9.2.19 



9.2.1 Authentication reject 



This message is sent by the network to the mobile station to indicate that authentication has failed (and that the 
receiving mobile station shall abort all activities). See table 9.2.2/3GPP TS 24.008. 

Message type: AUTHENTICATION REJECT 

Significance: dual 

Direction: network to mobile station 

Table 9.2.2/3GPP TS 24.008: AUTHENTICATION REJECT message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip Indicator 


Sl<ip Indicator 
10.3.1 


M 


V 


1/2 




Autlientication Reject 
message type 


Message type 
10.4 


M 


V 


1 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



244 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.2.2 Authentication request 



This message is sent by the network to the mobile station to initiate authentication of the mobile station identity. See 
table 9.2.3/3GPP TS 24.008. 

Message type: AUTHENTICATION REQUEST 

Significance: dual 

Direction: network to mobile station 

Table 9.2.3/3GPP TS 24.008: AUTHENTICATION REQUEST message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




Authentication Request 
message type 


Message type 
10.4 


M 


V 


1 




Ciphering key sequence 
number 


Ciphering key sequence 

number 

10.5.1.2 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 




Authentication 
parameter RAND (UMTS 
challenge or GSM challenge) 


Auth. parameter RAND 
10.5.3.1 


M 


V 


16 


20 


Authentication 
Parameter AUTN 


Auth. parameter AUTN 
10.5.3.1.1 





TLV 


18 



9.2.2.1 



Authentication Parameter AUTN 



This IE shall be present if and only if the authentication challenge is a UMTS authentication challenge. The presence or 
absence of this IE defines- in the case of its absence- a GSM authentication challenge or- in the case of its presence- a 
UMTS authentication challenge. 

The MS shall ignore the IE if a SIM is inserted in the MS. 

In UMTS, the MS shall reject the AUTHENTICATION REQUEST message as specified in subclause 4.3.2.5.1 if this 
IE is not present and a USIM is inserted in the MS. 

9.2.3 Autinentication response 

This message is sent by the mobile station to the network to deliver a calculated response to the network. See 
table 9.2.4/3GPP TS 24.008. 

Message type: AUTHENTICATION RESPONSE 

Significance: dual 

Direction: mobile station to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



245 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.2.4/3GPP TS 24.008: AUTHENTICATION RESPONSE message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




Authentication Response 
message type 


IVIessage type 
10.4 


M 


V 


1 




Authentication Response 
parameter 


Auth. Response parameter 
10.5.3.2 


M 


V 


4 


21 


Authentication Response 
Parameter (extension) 


Auth. Response parameter 
10.5.3.2.1 





TLV 


3-14 



9.2.3.1 



Authentication Response Parameter 



This IE contains the SRES, if it was a GSM authentication challenge, or the RES (all or just the 4 most significant 
octets of) if it was a UMTS authentication challenge (see also subclause 9.2.3.2). 



9.2.3.2 



Authentication Response Parameter (extension) 



This IE shall be included if and only if the authentication challenge was a UMTS authentication challenge and the RES 
parameter is greater than 4 octets in length. It shall contain the least significant remaining bits of the RES (the four most 
significant octets shall be sent in the Authentication Response Parameter IE (see subclause 9.2.3.1)) 

This IE shall not be included if a SIM is inserted in the MS. 

9.2.3a Authentication Failure 

This message is sent by the mobile station to the network to indicate that authentication of the network has failed. See 
table 9.2.4a/3GPP TS 24.008. 

Message type: AUTHENTICATION FAILURE 

Significance: dual 

Direction: mobile station to network 

Table 9.2.4a/3GPP TS 24.008: AUTHENTICATION FAILURE message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




Authentication Failure 
Message type 


Message type 
10.4 


M 


V 


1 




Reject Cause 


Reject Cause 
10.5.3.6 


M 


V 


1 


22 


Authentication Failure parameter 


Authentication Failure parameter 
10.5.3.2.2 





TLV 


16 



9.2.3a.1 Authentication Failure parameter 

This IE shall be sent if and only if the reject cause was "Synch failure". It shall include the response to the 
authentication challenge from the USIM, which is made up of the AUTS parameter (see 3GPP TS 33.102 [5a]). 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



246 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.2.4 CM Re-establishment request 



This message is sent by the mobile station to the network to request re-establishment of a connection if the previous one 
has failed. See table 9.2.5/3GPP TS 24.008. 

Message type: CM RE-ESTABLISHMENT REQUEST 

Significance: dual 

Direction: mobile station to network 

Table 9.2.5/3GPP TS 24.008: CM RE-ESTABLISHMENT REQUEST message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




IVIobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


y2 




CM Re-Establishment 
Request message type 


Message type 
10.4 


M 


V 


1 




Ciphering key sequence 
number 


Ciphering key sequence 

number 

10.5.1.2 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 




Mobile station 
classmark 


Mobile station 
classmark 2 
10.5.1.6 


M 


LV 


4 




Mobile identity 


Mobile identity 
10.5.1.4 


M 


LV 


2-9 


13 


Location area 
identification 


Location area 

identification 

10.5.1.3 


C 


TV 


6 



9.2.4.1 



Location area identification 



The location area identification information element shall appear when a TMSI is used as mobile identity, to render that 
mobile identity non-ambiguous. This is the LAI stored in the SIM/USIM. 

9.2.4.2 Mobile Station Classmark 

This IE shall include for multiband mobile station the Classmark 2 corresponding to the frequency band in use. 



9.2.5 CM service accept 



This message is sent by the network to the mobile station to indicate that the requested service has been accepted. See 
table 9.2.6/3GPP TS 24.008. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



247 



ETSI TS 124 008 V7.14.0 (2009-03) 



Message type: CM SERVICE ACCEPT 

Significance: dual 

Direction: network to mobile station 



Table 9.2.6/3GPP TS 24.008: CM SERVICE ACCEPT message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




CM Service Accept 
message type 


Message type 
10.4 


M 


V 


1 



9.2.5a CM service prompt $(CCBS)$ 



A mobile station that does not support the "Network initiated MO call" option shall treat this message as a message with 
message type not defined for the PD. 

This message is sent by the network to the mobile station to request the mobile to establish a service for the specified 
CM protocol using the specified SAPI, e.g. circuit switched connection establishment on SAPI 0, supplementary 
services activation on SAPI 0, or short message transfer on SAPI 3. See Table 9.2.7/3GPP TS 24.008. 

Message type: CM SERVICE PROMPT 

Significance: dual 

Direction: network to mobile station 

Table 9.2.7/3GPP TS 24.008: CM SERVICE PROMPT message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




CM Service Prompt 
message type 


Message type 
10.4 


M 


V 


1 




PD and SAPI of CM 


PD and SAPI 
10.5.1.10a 


M 


V 


1 



9.2.6 CM service reject 



This message is sent by the network to the mobile station to indicate that the requested service cannot be provided. See 
table 9.2.8/3GPP TS 24.008. 

Message type: CM SERVICE REJECT 

Significance: dual 

Direction: network to mobile station 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



248 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.2.8/3GPP TS 24.008: CM SERVICE REJECT message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




CIV! Service Reject 
message type 


IVIessage type 
10.4 


M 


V 


1 




Reject cause 


Reject cause 
10.5.3.6 


M 


V 


1 



9.2.7 CM service abort 

This message is sent by the mobile station to the network to request the abortion of the first MM connection 
establishment in progress and the release of the RR connection. See table 9.2.9/3GPP TS 24.008. 

Message type: CM SERVICE ABORT 

Significance: dual 

Direction: mobile station to network 

Table 9.2.9/3GPP TS 24.008: CM SERVICE ABORT message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




CM Service Abort 
message type 


Message type 
10.4 


M 


V 


1 



9.2.8 Abort 

This message is sent by the network to the mobile station to initiate the abortion of all MM connections and to indicate 
the reason for the abortion. See table 9.2.10/3GPP TS 24.008. 

Message type: ABORT 

Significance: dual 

Direction: network to mobile station 

Table 9.2.1 0/3GPP TS 24.008: ABORT message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




Abort 
message type 


Message type 
10.4 


M 


V 


1 




Reject cause 


Reject cause 
10.5.3.6 


M 


V 


1 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 249 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.2.9 CM service request 

This message is sent by the mobile station to the network to request a service for the connection management sublayer 
entities, e.g. circuit switched connection establishment, supplementary services activation, short message transfer, 
location services. See table 9.2.11/3GPP TS 24.008. 

Message type: CM SERVICE REQUEST 

Significance: dual 

Direction: mobile station to network 

Table 9.2.1 1/3GPP TS 24.008: CM SERVICE REQUEST message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




IVIobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


yi 




CM Service Request 
message type 


Message type 
10.4 


M 


V 


1 




CM service type 


CM service type 
10.5.3.3 


M 


V 


yi 




Ciphering key sequence 
number 


Ciphering key sequence 

number 

10.5.1.2 


M 


V 


V2 




Mobile station 
classmark 


Mobile station 
classmark 2 
10.5.1.6 


M 


LV 


4 




Mobile identity 


Mobile identity 
10.5.1.4 


M 


LV 


2-9 


8- 


Priority 


Priority Level 
10.5.1.11 





TV 


1 



9.2.9.1 Mobile Station Classmark 

This IE shall include for multiband mobile station the Classmark 2 corresponding to the frequency band in use. 

9.2.9.2 Priority 

May be included by mobile station supporting eMLPP to indicate the priority requested. 
This information element is only meaningful when the CM service type is: 

Mobile originating call establishment; 

Emergency call establishment; 

Voice group call establishment; 

Voice broadcast call establishment. 

9.2.10 Identity request 

This message is sent by the network to the mobile station to request a mobile station to submit the specified identity to 
the network. See table 9.2.12/3GPP TS 24.008. 

Message type: IDENTITY REQUEST 

Significance: dual 

Direction: network to mobile station 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



250 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.2.1 2/3GPP TS 24.008: IDENTITY REQUEST message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




Identity Request 
message type 


IVIessage type 
10.4 


M 


V 


1 




Identity type 


Identity type 
10.5.3.4 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 



9.2.1 1 Identity response 



This message is sent by the mobile station to the network in response to an IDENTITY REQUEST message providing 
the requested identity. See table 9.2.13/3GPP TS 24.008. 

Message type: IDENTITY RESPONSE 

Significance: dual 

Direction: mobile station to network 

Table 9.2.1 3/3GPP TS 24.008: IDENTITY RESPONSE message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




Identity Response 
message type 


Message type 
10.4 


M 


V 


1 




Mobile identity 


Mobile identity 
10.5.1.4 


M 


LV 


2-10 



9.2.12 IMSI detach indication 



This message is sent by the mobile station to the network to set a deactivation indication in the network. See 
table 9.2.14/3GPP TS 24.008. 

Message type: IMSI DETACH INDICATION 

Significance: dual 

Direction: mobile station to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



251 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.2.1 4/3GPP TS 24.008: IMSI DETACH INDICATION message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




IVIobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




IIVISI Detach Indication 
message type 


Message type 
10.4 


M 


V 


1 




Mobile station 
classmark 


Mobile station 
classmark 1 
10.5.1.5 


M 


V 


1 




Mobile identity 


Mobile identity 
10.5.1.4 


M 


LV 


2-9 



9.2.1 2.1 Mobile Station Classmark 

This IE shall include for multiband mobile station the Classmark 1 corresponding to the frequency band in use. 

9.2.13 Location updating accept 

This message is sent by the network to the mobile station to indicate that updating or IMSI attach in the network has 
been completed. See table 9.2.15/3GPP TS 24.008. 

Message type: LOCATION UPDATING ACCEPT 

Significance: dual 

Direction: network to mobile station 

Table 9.2.1 5/3GPP TS 24.008: LOCATION UPDATING ACCEPT message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




Location Updating 
Accept message type 


Message type 
10.4 


M 


V 


1 




Location area 
identification 


Location area 

identification 

10.5.1.3 


M 


V 


5 


17 


Mobile identity 


Mobile identity 
10.5.1.4 





TLV 


3-10 


A1 


Follow on proceed 


Follow on proceed 
10.5.3.7 





T 


1 


A2 


CIS permission 


CTS permission 
10.5.3.10 





T 


1 


4A 


Equivalent PLMNs 


PLMN list 
10.5.1.13 





TLV 


5-47 


34 


Emergency Number List 


Emergency Number List 
10.5.3.13 





TLV 


5-50 



9.2.13.1 Follow on proceed 

The follow on /proceed/ information element appears if the network wishes to indicate that the mobile station may 
attempt an MM connection establishment using the same RR connection. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



252 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.2.13.2 CTS permission 

The CTS permission information element appears if the network wishes to allow the mobile station to use GSM- 
Cordless Telephony System in the Location Area. 

9.2.13.3 Equivalent PLMNs 

The Equivalent PLMNs information element is included if the network wants to inform the mobile station of equivalent 
PLMNs. 

9.2.13.4 Emergency Number List 

This IE may be sent by the network. If this IE is sent, the contents of this IE indicates a list of emergency numbers valid 
within the same MCC as in the cell on which this IE is received. 

9.2.14 Location updating reject 

This message is sent by the network to the mobile station to indicate that updating or IMSI attach has failed. See 
table 9.2.16/3GPP TS 24.008. 

Message type: LOCATION UPDATING REJECT 

Significance: dual 

Direction: network to mobile station 

Table 9.2.16/3GPP TS 24.008: LOCATION UPDATING REJECT message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




Location Updating 
Reject message type 


IVIessage type 
10.4 


M 


V 


1 




Reject cause 


Reject cause 
10.5.3.6 


M 


V 


1 



9.2.15 Location updating request 

This message is sent by the mobile station to the network either to request update of its location file (normal updating or 
periodic updating) or to request IMSI attach. See table 9.2.17/3GPP TS 24.008. 

Message type: LOCATION UPDATING REQUEST 

Significance: dual 

Direction: mobile station to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



253 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.2.1 7/3GPP TS 24.008: LOCATION UPDATING REQUEST message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




IVIobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




Location Updating 
Request message type 


Message type 
10.4 


M 


V 


1 




Location updating type 


Location updating type 
10.5.3.5 


M 


V 


1/2 




Ciphering key sequence 
number 


Ciphering key sequence 

number 

10.5.1.2 


M 


V 


1/2 




Location area 
identification 


Location area 

identification 

10.5.1.3 


M 


V 


5 




IVIobile station 
classmark 


Mobile station 
classmark 1 
10.5.1.5 


M 


V 


1 




IVIobile identity 


Mobile identity 
10.5.1.4 


M 


LV 


2-9 


33 


IVIobile station 
classmark for UMTS 


Mobile station 
classmark 2 
10.5.1.6 





TLV 


5 



9.2.15.1 Location area identification 

The location area identification stored in the SIM/USIM is used. 

9.2.1 5.2 Mobile Station Classmark 

This IE shall include for multiband MS the Classmark 1 corresponding to the frequency band in use. 



9.2.15.3 



Mobile Station Classmark for lu mode 



This IE shall be included when the mobile station is in lu mode network. The IE shall not be included when the mobile 
station is in A/Gb mode network. 

9.2.15a MM information 

This message is sent by the network to the mobile station to provide the mobile station with subscriber specific 
information. See table 9.2.18/3GPP TS 24.008. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



254 



ETSI TS 124 008 V7.14.0 (2009-03) 



Message type: MM INFORMATION 

Significance: dual 

Direction: network to mobile station 



Table 9.2.1 8/3GPP TS 24.008 MM INFORMATION message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




MM Information 
message type 


Message type 
10.4 


M 


V 


1 


43 


Full name for network 


Network Name 
10.5.3.5a 





TLV 


3-? 


45 


Short name for network 


Network Name 
10.5.3.5a 





TLV 


3-? 


46 


Local time zone 


Time Zone 
10.5.3.8 





TV 


2 


47 


Universal time and local time 
zone 


Time Zone and Time 
10.5.3.9 





TV 


8 


48 


LSA Identity 


LSA Identifier 
10.5.3.11 





TLV 


2-5 


49 


Network Daylight Saving Time 


Daylight Saving Time 
10.5.3.12 





TLV 


3 



9.2.1 5a.1 Full name for network 

This IE may be sent by the network. If this IE is sent, the contents of this IE indicate the "full length name of the 
network" that the network wishes the mobile station to associate with the MCC and MNC contained in the Location 
Area Identification of the cell to which the mobile station sent its Channel Request message. 

9.2.1 5a.2 Short name for network 

This IE may be sent by the network. If this IE is sent, the contents of this IE indicate the "abbreviated name of the 
network" that the network wishes the mobile station to associate with the MCC and MNC contained in the Location 
Area Identification of the cell to which the mobile station sent its Channel Request message. 

9.2.1 5a.3 Local time zone 

This IE may be sent by the network. The mobile station should assume that this time zone applies to the Location Area 
of the cell to which the Channel Request message was sent. 

If the local time zone has been adjusted for Daylight Saving Time, the network shall indicate this by including the IE 
Network Daylight Saving Time. 

9.2.1 5a.4 Universal time and local time zone 

This IE may be sent by the network. The mobile station should assume that this time zone applies to the Location Area 
of the cell to which the Channel Request message was sent. The mobile station shall not assume that the time 
information is accurate. 

If the local time zone has been adjusted for Daylight Saving Time, the network shall indicate this by including the IE 
Network Daylight Saving Time. 

9.2.1 5a.5 LSA Identity 

This IE may be sent by the network. The contents of this IE indicate the LSA identity of the serving cell. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



255 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.2.1 5a.6 Network Daylight Saving Time 

This IE may be sent by the network. If this IE is sent, the contents of this IE indicates the value that has been used to 
adjust the local time zone. 

9.2.16 MM Status 

This message is sent by the mobile station or the network at any time to report certain error conditions listed in clause i 
See table 9.2.19/3GPP TS 24.008. 

Message type: MM STATUS 

Significance: local 

Direction: both 

Table 9.2.1 9/3GPP TS 24.008: MM STATUS message content 



IE! 


information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




MM Status message 
type 


Message type 
10.4 


M 


V 


1 




Reject cause 


Reject cause 
10.5.3.6 


M 


V 


1 



9.2.17 TMSI reallocation command 

This message is sent by the network to the mobile station to reallocate or delete a TMSI. See table 9.2.20/3GPP TS 
24.008. 

Message type: TMSI REALLOCATION COMMAND 

Significance: dual 

Direction: network to mobile station 

Table 9.2.20/3GPP TS 24.008: TMSI REALLOCATION COMMAND message content 



lEi 


information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




TMSI Reallocation 
Command message type 


Message type 
10.4 


M 


V 


1 




Location area 
identification 


Location area 

identification 

10.5.1.3 


M 


V 


5 




Mobile identity 


Mobile identity 
10.5.1.4 


M 


LV 


2-9 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



256 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.2.18 TMSI reallocation complete 

This message is sent by the mobile station to the network to indicate that reallocation or deletion of a TMSI has taken 
place. See table 9.2.21/3GPP TS 24.008. 

Message type: TMSI REALLOCATION COMPLETE 

Significance: dual 

Direction: mobile station to network 

Table 9.2.21/3GPP TS 24.008: TMSI REALLOCATION COMPLETE message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




TMSI Reallocation 
Complete message type 


Message type 
10.4 


M 


V 


1 



9.2.19 MM Null 

This message is sent in mobile to network direction. 

This message is not used on the radio interface. When received by the network it shall be ignored. 

The introduction of this message solves interworking issues. 

Message type: MM NULL 

Table 9.2.22/3GPP TS 24.008 MM NULL message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




MM Null message 
type 


Message type 
10.4 


M 


V 


1 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



257 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3 Messages for circuit-switched call control 

Table 9.54/3GPP TS 24.008 summarizes the messages for circuit-switched call control. 

Table 9.54/3GPP TS 24.008: Messages for circuit-mode connections call control. 



Call establishment messages: 


Reference 


ALERTING 


9.3.1 


CALL CONFIRMED 1) 


9.3.2 


CALL PROCEEDING 


9.3.3 


CONNECT 


9.3.5 


CONNECT ACKNOWLEDGE 


9.3.6 


EMERGENCY SETUP 1) 


9.3.8 


PROGRESS 


9.3.17 


CC-ESTABLISHMENT 


9.3.17a 


CC-ESTABLISHMENT CONFIRMED 


9.3.17b 


START CC 


9.3.23a 


SETUP 


9.3.23 


Call information phase messages: 


Reference 


MODIFY 1) 


9.3.13 


MODIFY COMPLETE 1) 


9.3.14 


MODIFY REJECT 1) 


9.3.15 


USER INFORMATION 


9.3.31 


Call clearing messages: 


Reference 


DISCONNECT 


9.3.7 


RELEASE 


9.3.18 


RECALL 


9.3.18a 


RELEASE COMPLETE 


9.3.19 


Messages for supplementary service control 


Reference 


FACILITY 


9.3.9 


H0LD1) 


9.3.10 


HOLD ACKNOWLEDGE 1) 


9.3.11 


HOLD REJECT 1) 


9.3.12 


RETRIEVE 1) 


9.3.20 


RETRIEVE ACKNOWLEDGE 1) 


9.3.21 


RETRIEVE REJECT 1) 


9.3.22 


Miscellaneous messages 


Reference 


CONGESTION CONTROL 


9.3.4 


NOTIFY 


9.3.16 


START DTMF 1 ) 


9.3.24 


START DTMF ACKNOWLEDGE 1) 


9.3.25 


START DTMF REJECT 1) 


9.3.26 


STATUS 


9.3.27 


STATUS ENOUIRY 


9.3.28 


STOP DTMF 1) 


9.3.29 


STOP DTMF ACKNOWLEDGE 1) 


9.3.30 



NOTE: Not supported by Blue Book ITU-T Rec. Q.93 1 . 

9.3.1 Alerting 

9.3.1 .1 Alerting (network to mobile station direction) 

This message is sent by the network to the calling mobile station to indicate that the called user alerting has been 
initiated. 

See table 9.55/3GPP TS 24.008. 

Message type: ALERTING 

Significance: global 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



258 



ETSI TS 124 008 V7.14.0 (2009-03) 



Direction: network to mobile station 

Table 9.55/3GPP TS 24.008: ALERTING message content (network to mobile station direction) 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Alerting 
message type 


Message type 
10.4 


M 


V 


1 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


IE 


Progress indicator 


Progress indicator 
10.5.4.21 





TLV 


4 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 



9.3.1.1.1 Facility 

This information element may be used for functional operation of supplementary services. 

9.3.1.1.2 Progress indicator 

This information element may be included by the network: 

in order to pass information about the call in progress, e.g., in the event of interworking; and/or 
to make the mobile station attach the user connection for speech. 

9.3.1.1.3 User-user 

This information element may be included by the network if the called remote user included a user-user information 
element in the ALERTING message. 



9.3.1.2 



Alerting (mobile station to network direction) 



This message is sent by the called mobile station to the network, to indicate that the called user alerting has been 
initiated. 

See table 9.55a/3GPP TS 24.008. 

Message type: ALERTING 

Significance: global 

Direction: mobile station to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



259 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.55a/3GPP TS 24.008: ALERTING message content (mobile station to network direction) 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Alerting 
message type 


IVIessage type 
10.4 


M 


V 


1 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 


7F 


SS version 


SS version indicator 
10.5.4.24 





TLV 


2-3 



9.3.1.2.1 Facility 

This information element may be used for functional operation of supplementary services. 

9.3.1.2.2 User-user 

This information element may be included when the called mobile station wants to return information to the calling 
remote user. 

9.3.1.2.3 SS version 

This information element shall not be included if the facility information element is not present in this message. 

This information element shall be included or excluded as defined in 3GPP TS 24.010. This information element should 
not be transmitted unless explicitly required by 3GPP TS 24.010. 

9.3.2 Call confirmed 

This message is sent by the called mobile station to confirm an incoming call request. 
See table 9.56/3GPP TS 24.008. 

Message type: CALL CONFIRMED 

Significance: local 

Direction: mobile station to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



260 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.56/3GPP TS 24.008: CALL CONFIRMED message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Call confirmed 
message type 


Message type 
10.4 


M 


V 


1 


D- 


Repeat Indicator 


Repeat Indicator 
10.5.4.22 


C 


TV 


1 


04 


Bearer capability 1 


Bearer capability 
10.5.4.5 





TLV 


3-16 


04 


Bearer capability 2 


Bearer capability 
10.5.4.5 





TLV 


3-16 


08 


Cause 


Cause 
10.5.4.11 





TLV 


4-32 


15 


CC Capabilities 


Call Control Capabilities 
10.5.4.5a 





TLV 


4 


2D 


Stream Identifier 


Stream Identifier 
10.5.4.28 





TLV 


3 


40 


Supported Codecs 


Supported Codec List 
10.5.4.32 





TLV 


5-n 



9.3.2.1 



Repeat indicator 



The repeat indicator information element shall be included if bearer capability 1 information element and bearer 
capability 2 IE are both included in the message. 



9.3.2.2 



Bearer capability 1 and bearer capability 2 



The bearer capability 1 information element shall be included if and only if at least one of the following six cases 
holds: 

the mobile station wishes another bearer capability than that given by the bearer capability 1 information 
element of the incoming SETUP message; 

the bearer capability 1 information element is missing or not fully specified in the SETUP message; 

the bearer capability 1 information element received in the SETUP message is accepted and the "radio channel 
requirement" of the mobile station is other than "full rate support only mobile station"; 

the bearer capability 1 information element received in the SETUP message indicates speech and is accepted 
and the mobile station supports CTM text telephony; 

the bearer capability 1 information element received in the SETUP message indicates speech and is accepted 
and the mobile station supports other codecs for GERAN than GSM speech version 1 ; 

the bearer capability 1 information element received in the SETUP message included the "fixed network user 
rate" parameter. 

When the bearer capability 1 information element is followed by the bearer capability 2 IE in the SETUP, the above 
rules apply to both bearer capability 1 IE and bearer capability 2 IE. Except those cases identified in 3GPP TS 27.001, 
if either bearer capability needs to be included, both shall be included. 

Furthermore, both bearer capability information elements may be present if the mobile station wishes to reverse the 
order of occurrence of the bearer capability information elements (which is referred to in the repeat indicator 
information element, see subclause 10.5.4.22) in cases identified in 3GPP TS 27.001 [36]. 

If the mobile station wishes to indicate capability for an alternative call mode, which can be entered during the call 
through in-call modification, this is indicated by adding a bearer capability information element (bearer capability 2 
information element, see subclause 5.3.6). 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



261 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.2.3 Cause 

This information element is included if the mobile station is compatible but the user is busy. 

9.3.2.4 CC Capabilities 

This information element may be included by the mobile station to indicate its call control capabilities. 

9.3.2.5 Stream Identifier 

This information element shall be included by the mobile station supporting multicall. 

9.3.2.6 Supported Codecs 

This information element shall be included for speech calls, if the mobile station supports UMTS radio access. 

9.3.3 Call proceeding 

This message is sent by the network to the calling mobile station to indicate that the requested call establishment 
information has been received, and no more call establishment information will be accepted. 

See table 9.57/3GPP TS 24.008. 

Message type: CALL PROCEEDING 

Significance: local 

Direction: network to mobile station 

Table 9.57/3GPP TS 24.008: CALL PROCEEDING message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Call proceeding 
message type 


IVIessage type 
10.4 


M 


V 


1 


D- 


Repeat Indicator 


Repeat Indicator 
10.5.4.22 


C 


TV 


1 


04 


Bearer capability 1 


Bearer capability 
10.5.4.5 





TLV 


3-16 


04 


Bearer capability 2 


Bearer capability 
10.5.4.5 





TLV 


3-16 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


IE 


Progress indicator 


Progress indicator 
10.5.4.21 





TLV 


4 


8- 


Priority granted 


Priority Level 
10.5.1.11 





TV 


1 


2F 


Network Call Control 
Capabilities 


Network Call Control cap. 
10.5.4.29 





TLV 


3 



9.3.3.1 



Repeat indicator 



This information element is included if and only if bearer capability 1 IE and bearer capability 2 IE are both contained 
in the message. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



262 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.3.2 



Bearer capability 1 and bearer capability 2 



The bearer capability 1 information element shall be included if the network has to specify at least one of the 
negotiable parameters described in 3GPP TS 27.001, or if the bearer capability 1 information element received in the 
SETUP message included the "fixed network user rate" parameter. 

When the bearer capability 1 information element is followed by the bearer capability 2 IE in the SETUP, the above 
rule applies to both bearer capability 1 IE and bearer capability 2 IE. Except those cases identified in 
3GPP TS 27.001 [36], if either bearer capability needs to be included, both shall be included. 

9.3.3.3 Facility 

This information element may be used for functional operation of supplementary services. 

9.3.3.4 Progress Indicator 

This information element may be included: 

in order to pass information about the call in progress e.g. in the event of interworking; and/or 
to make the MS attach the user connection for speech. 

9.3.3.5 Priority granted 

The priority field is provided by the network in the case that eMLPP is supported. 

9.3.3.6 Network Call Control Capabilities 

This information shall be included by the network to indicate its call control capabilities if the network supports 
multicall.and there are no other ongoing calls to the MS. 

9.3.4 Congestion control 

This message is sent by the network to indicate the establishment or termination of flow control on the transmission of 
USER INFORMATION messages. 

See table 9.58/3GPP TS 24.008. 

Message type: CONGESTION CONTROL 

Significance: local (note) 

Direction: network to mobile station 

Table 9.58/3GPP TS 24.008: CONGESTION CONTROL message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Congestion control 
message type 


IVIessage type 
10.4 


M 


V 


1 




Congestion level 


Congestion level 
10.5.4.12 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 


08 


Cause 


Cause 
10.5.4.11 





TLV 


4-32 



NOTE: This message has local significance, but may carry information of global significance. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



263 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.4.1 



Cause 



This information element is included if the user to user information has been discarded as a result of the congestion 
situation. 

9.3.5 Connect 

9.3.5.1 Connect (network to mobile station direction) 

This message is sent by the network to the calling mobile station to indicate call acceptance by the called user. 
See table 9.59/3GPP TS 24.008. 

Message type: CONNECT 

Significance: global 

Direction: network to mobile station 

Table 9.59/3GPP TS 24.008: CONNECT message content(network to mobile station direction) 



IE! 


information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Connect 
message type 


IVIessage type 
10.4 


M 


V 


1 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


IE 


Progress indicator 


Progress indicator 
10.5.4.21 





TLV 


4 


4C 


Connected number 


Connected number 
10.5.4.13 





TLV 


3-14 


4D 


Connected subaddress 


Connected subaddress 
10.5.4.14 





TLV 


2-23 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 



9.3.5.1.1 Facility 

This information element may be used for functional operation of supplementary services. 

9.3.5.1 .2 Progress indicator 

This information element may be included by the network: 

in order to pass information about the call in progress e.g. in the event of interworking; and/or 
to make the MS attach the user connection for speech. 

9.3.5.1.3 User-user 

This information element may be included by the network if the remote user awarded the call included a user- user 
information element in the CONNECT message. 

9.3.5.2 Connect (mobile station to network direction) 

This message is sent by the called mobile station to the network to indicate call acceptance by the called user. 
See table 9.59a/3GPP TS 24.008. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 264 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

Message type: CONNECT 

Significance: global 

Direction: mobile station to network 

Table 9.59a/3GPP TS 24.008: CONNECT message content (mobile station to network direction) 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Connect 
message type 


IVIessage type 
10.4 


M 


V 


1 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


4D 


Connected subaddress 


Connected subaddress 
10.5.4.14 





TLV 


2-23 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 


7F 


SS version 


SS version indicator 
10.5.4.24 





TLV 


2-3 


2D 


Stream Identifier 


Stream Identifier 
10.5.4.28 





TLV 


3 



9.3.5.2.1 Facility 

This information element may be used for functional operation of supplementary services. 

9.3.5.2.2 User-user 

This information element is included when the answering mobile station wants to return user information to the calling 
remote user. 

9.3.5.2.3 SS version 

This information element shall not be included if the facility information element is not present in this message. 

This information element shall be included or excluded as defined in 3GPP TS 24.010. This information element should 
not be transmitted unless explicitly required by 3GPP TS 24.010. 



9.3.5.2.4 



Stream Identifier 



This information element shall be included by a mobile station that supports multicall when a mobile station has 
indicated "No Bearer" as the SI value in the CALL CONFIRMED message. 



9.3.6 Connect acknowledge 



This message is sent by the network to the called mobile station to indicate that the mobile station has been awarded the 
call. It shall also be sent by the calling mobile station to the network to acknowledge the offered connection. 

See table 9.60/3GPP TS 24.008. 

Message type: CONNECT ACKNOWLEDGE 

Significance: local 

Direction: both 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



265 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.60/3GPP TS 24.008: CONNECT ACKNOWLEDGE message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Connect acknowledge 
message type 


IVIessage type 
10.4 


M 


V 


1 



9.3.7 Disconnect 

9.3.7.1 Disconnect (network to mobile station direction) 

This message is sent by the network to indicate that the end-to-end connection is cleared. 
See table 9.61/3GPP TS 24.008. 

Message type: DISCONNECT 

Significance: global 

Direction: network to mobile station 

Table 9.61/3GPP TS 24.008: DISCONNECT message content (network to mobile station direction) 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Disconnect 
message type 


IVIessage type 
10.4 


M 


V 


1 




Cause 


Cause 
10.5.4.11 


M 


LV 


3-31 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


IE 


Progress indicator 


Progress indicator 
10.5.4.21 





TLV 


4 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 


7B 


Allowed actions $(CCBS)$ 


Allowed actions 
10.5.4.27 





TLV 


3 



9.3.7.1.1 Facility 

This information element may be used for functional operation of supplementary services, such as the user-user service. 

9.3.7.1 .2 Progress indicator 

This information element is included by the network to make the MS attach the user connection for speech and react in 
a specific way during call clearing (see subclause 5.4.4). 



9.3.7.1.3 



User-user 



This information element may be included by the network when the remote user initiates call clearing and included a 
user-user information element in the DISCONNECT message. 

9.3.7.1 .4 Allowed actions $(CCBS)$ 

This information element may be included by the network to inform the MS about further possible reactions. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



266 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.7.2 Disconnect (mobile station to network direction) 

This message is sent by the mobile station to request the network to clear an end-to-end connection. 
See table 9.61a/3GPP TS 24.008. 

Message type: DISCONNECT 

Significance: global 

Direction: mobile station to network 

Table 9.61a/3GPP TS 24.008: DISCONNECT message content (mobile station to network direction) 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Disconnect 
message type 


IVIessage type 
10.4 


M 


V 


1 




Cause 


Cause 
10.5.4.11 


M 


LV 


3-31 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 


7F 


SS version 


SS version indicator 
10.5.4.24 





TLV 


2-3 



9.3.7.2.1 Facility 

This information element may be used for functional operation of supplementary services, such as the user-user service. 

9.3.7.2.2 User-user 

This information element is included when the mobile station initiates call clearing and wants to pass user information 
to the remote user at call clearing time. 

9.3.7.2.3 SS version 

This information element shall not be included if the/ac/Z/fy information element is not present in this message. 

This information element shall be included or excluded as defined in 3GPP TS 24.010 [21]. This information element 
should not be transmitted unless explicitly required by 3GPP TS 24.010 [21]. 



9.3.8 Emergency setup 



This message is sent from the mobile station to initiate emergency call establishment. 
See table 9.62/3GPP TS 24.008. 

Message type: EMERGENCY SETUP 

Significance: global 

Direction: mobile station to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



267 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.62/3GPP TS 24.008: EMERGENCY SETUP message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Emergency setup 
message type 


Message type 
10.4 


M 


V 


1 


04 


Bearer capability 


Bearer capability 
10.5.4.5 





TLV 


3-11 


2D 


Stream Identifier 


Stream Identifier 
10.5.4.28 





TLV 


3 


40 


Supported Codecs 


Supported Codec List 
10.5.4.32 





TLV 


5-n 


2E 


Emergency category 


Service category 
10.5.4.33 


O 


TLV 


3 



9.3.8.1 



Bearer capability 



If the element is not included, the network shall by default assume speech and select the speech codec according to 
subclauses 5.2.1.2 and 5.2.1.11. If this information element is included, it shall indicate speech, the appropriate speech 
version(s) and have the appropriate value of radio channel requirement field. 

This information element shall be included by an ME supporting CTM text telephony or supporting at least one speech 
version for GERAN other than GSM FR speech version 1. 

9.3.8.2 Stream Identifier 

This information element shall be included by the mobile station supporting multicall. 

9.3.8.3 Supported Codecs 

This information element shall be included if the mobile station supports UMTS radio access. 

9.3.8.4 Emergency category 

This information element shall be included if the emergency category is available from the SIM/USIM or the mobile 
station. 

If this information element is included, it shall indicate the selected emergency call category. 

If the element is not included, the network shall by default assume a non-specific emergency call. 



9.3.9 Facility 



9.3.9.1 



Facility (network to mobile station direction) 



This message is sent by the network to the mobile station to request or acknowledge a supplementary service. The 
supplementary service to be invoked and its associated parameters are specified in the facility information element. 

See table 9.62a/3GPP TS 24.008. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



268 



ETSI TS 124 008 V7.14.0 (2009-03) 



Message type: FACILITY 
Significance: local (NOTE 1) 
Direction: network to mobile station 

Table 9.62a/3GPP TS 24.008: FACILITY message content (network to mobile station direction) 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Facility 
message type 


IVlessage type 
10.4 


M 


V 


1 




Facility (note 2) 


Facility 
10.5.4.15 


M 


LV 


1-? 



NOTE 1 : This message has local significance; however, it may carry information of global significance. 

NOTE 2: The facility information element has no upper length limit except that given by the maximum number of 
octets in a L3 message, see 3GPP TS 44.006 [19]. 



9.3.9.2 



Facility (mobile station to network direction) 



This message is sent by the mobile station to the network to request or acknowledge a supplementary service. The 
supplementary service to be invoked and its associated parameters are specified in the facility information element. 

See table 9.62b/3GPP TS 24.008. 

Message type: FACILITY 

Significance: local (note 1) 

Direction: mobile station to network 

Table 9.62b/3GPP TS 24.008: FACILITY message content (mobile station to network direction) 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Facility 
message type 


IVlessage type 
10.4 


M 


V 


1 




Facility (note 2) 


Facility 
10.5.4.15 


M 


LV 


1-? 


7F 


SS version 


SS version indicator 
10.5.4.24 





TLV 


2-3 



NOTE 1 : This message has local significance; however, it may carry information of global significance. 

NOTE 2: The facility information element has no upper length limit except that given by the maximum number of 
octets in a L3 message, see 3GPP TS 44.006. 



9.3.9.2.1 



SS version 



This information element shall be included or excluded as defined in 3GPP TS 24.010 [21]. This information element 
should not be transmitted unless explicitly required by 3GPP TS 24.010 [21]. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



269 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.10 Hold 

This message is sent by the mobile user to request the hold function for an existing call. 
See table 9.62c/3GPP TS 24.008 for the content of the HOLD message. 
For the use of this message, see 3GPP TS 24.010. 

Message type: HOLD 

Significance: local 

Direction: mobile station to network 

Table 9.62c/3GPP TS 24.008: HOLD message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Hold 
message type 


Message type 
10.4 


M 


V 


1 



9.3.1 1 Hold Acknowledge 



This message is sent by the network to indicate that the hold function has been successfully performed. 
See table 9.62d/3GPP TS 24.008 for the content of the HOLD ACKNOWLEDGE message. 
For the use of this message, see 3GPP TS 24.010. 

Message type: HOLD ACKNOWLEDGE 

Significance: local 

Direction: network to mobile station 

Table 9.62d/3GPP TS 24.008: HOLD ACKNOWLEDGE message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Hold Acknowledge 
message type 


IVIessage type 
10.4 


M 


V 


1 



9.3.12 Hold Reject 



This message is sent by the network to indicate the denial of a request to hold a call. 
See table 9.62e/3GPP TS 24.008 for the content of the HOLD REJECT message. 
For the use of this message, see 3GPP TS 24.010. 

Message type: HOLD REJECT 

Significance: local 

Direction: network to mobile station 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



270 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.62e/3GPP TS 24.008: HOLD REJECT message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Hold Reject 
message type 


IVIessage type 
10.4 


M 


V 


1 




Cause 


10.5.4.11 


M 


LV 


3-31 



9.3.13 Modify 



This message is sent by the mobile station to the network or by the network to the mobile station to request a change in 
bearer capability for a call. 

See table 9.63/3GPP TS 24.008. 

Message type: MODIFY 

Significance: global 

Direction: both 

Table 9.63/3GPP TS 24.008: MODIFY message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




IVIodify 
message type 


IVIessage type 
10.4 


M 


V 


1 




Bearer capability 


Bearer capability 
10.5.4.5 


M 


LV 


2-15 


7C 


Low layer comp. 


Low layer comp. 
10.5.4.18 





TLV 


2-18 


7D 


High layer comp. 


High layer comp. 
10.5.4.16 





TLV 


2-5 


A3 


Reverse call setup 
direction 


Reverse call setup 

direction 

10.5.4.22a 





T 


1 


A4 


Network-initiated Service 
Upgrade indicator 


Network-initiated Service 
Upgrade indicator 
10.5.4.3X 





T 


1 



9.3.1 3.1 Low layer compatibility 

This information element shall be included if it was included in the initial SETUP message. 

9.3.1 3.2 High layer compatibility 

This information element shall be included if it was included in the initial SETUP message. 

9.3.1 3.3 Reverse call setup direction 

This information element is included or omitted in the mobile to network direction according to the rules defined in 

subclause 5.3.4.3.1. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



271 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.13.4 



Void 



9.3.13.5 Network-initiated Service Upgrade indicator 

This information element shall be included only if the MODIFY message was sent by the network to switch from 
speech to UDI/RDI multimedia due to a network-initiated service upgrade. 

9.3.14 Modify complete 

This message is sent by the mobile station to the network or by the network to the mobile station to indicate completion 
of a request to change bearer capability for a call. 

See table 9.64/3GPP TS 24.008. 

Message type: MODIFY COMPLETE 

Significance: global 

Direction: both 

Table 9.64/3GPP TS 24.008: MODIFY COMPLETE message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




IVIodify complete 
message type 


Message type 
10.4 


M 


V 


1 




Bearer capability 


Bearer capability 
10.5.4.5 


M 


LV 


2-15 


7C 


Low layer comp. 


Low layer comp. 
10.5.4.18 





TLV 


2-18 


7D 


High layer comp. 


High layer comp. 
10.5.4.16 





TLV 


2-5 


A3 


Reverse call setup 
direction 


Reverse call setup 

direction 

10.5.4.22a 





T 


1 



9.3.14.1 Low layer compatibility 

This information element shall be included if it was included in the initial SETUP message. 

9.3.14.2 High layer compatibility 

This information element shall be included if it was included in the initial SETUP message. 

9.3.1 4.3 Reverse call setup direction 

This information element is included or omitted according to the rules defined in subclause 5.3.4.3.2. 

9.3.15 Modify reject 

This message is sent by the mobile station to the network or by the network to the mobile station to indicate failure of a 
request to change the bearer capability for a call. 

See table 9.65/3GPP TS 24.008. 

Message type: MODIFY REJECT 

Significance: global 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



272 



ETSI TS 124 008 V7.14.0 (2009-03) 



Direction: both 

Table 9.65/3GPP TS 24.008: MODIFY REJECT message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




IVIodify reject 
message type 


Message type 
10.4 


M 


V 


1 




Bearer capability 


Bearer capability 
10.5.4.5 


M 


LV 


2-15 




Cause 


Cause 
10.5.4.11 


M 


LV 


3-31 


7C 


Low layer comp. 


Low layer comp. 
10.5.4.18 





TLV 


2-18 


7D 


High layer comp. 


High layer comp. 
10.5.4.16 





TLV 


2-5 



9.3.1 5.1 Low layer compatibility 

This information element shall be included if it was included in the initial SETUP message. 

9.3.15.2 High layer compatibility 

This information element shall be included if it was included in the initial SETUP message. 

9.3.16 Notify 

This message is sent either from the mobile station or from the network to indicate information pertaining to a call, such 
as user suspended. 

See table 9.66/3GPP TS 24.008. 

Message type: NOTIFY 

Significance: access 

Direction: both 

Table 9.66/3GPP TS 24.008: NOTIFY message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Notify 
message type 


IVIessage type 
10.4 


M 


V 


1 




Notification indicator 


Notification indicator 
10.5.4.20 


M 


V 


1 



9.3.17 Progress 



This message is sent from the network to the mobile station to indicate the progress of a call in the event of 
interworking or in connection with the provision of in-band information/patterns. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



273 



ETSI TS 124 008 V7.14.0 (2009-03) 



See table 9.67/3GPP TS 24.008. 
Message type: PROGRESS 
Significance: global 
Direction: network to mobile station 



Table 9.67/3GPP TS 24.008: PROGRESS message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Progress 
message type 


IVIessage type 
10.4 


M 


V 


1 




Progress indicator 


Progress indicator 
10.5.4.21 


M 


LV 


3 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 



9.3.17.1 



User-user 



This information element is included when the PROGRESS message is sent by the network when the call has been 
cleared by the remote user before it reached the active state to indicate that the remote user wants to pass user 
information at call clearing time. 

9.3.17a CC-Establishment $(CCBS)$ 

A mobile station that does not support the "Network initiated MO call" option shall treat this message as a message with 
message type not defined for the PD. 

This message is sent from the network to the mobile station to provide information on the call that the mobile station 
should attempt to establish. 

See Table 9.67a/3GPP TS 24.008. 

Message type: CC-ESTABLISHMENT 

Significance: local 

Direction: network to mobile station 

Table 9.67a/3GPP TS 24.008: CC-Establishment message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




CC-Establishment 
message type 


IVIessage type 
10.4 


M 


V 


1 




Setup container 


Container 
10.5.4.22a 


M 


LV 


3-n 



* From the 4th IE onwards the message is coded in the same way as the SETUP message in MS to network 
direction from the 4th IE onwards. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



274 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.17a.1 



Void 



9.3.1 7a.2 Setup container 

This information element contains the contents of a SETUP message (Mobile Station to Network). 

9.3.17b CC-Establishment confirmed $(CCBS)$ 

A Network that does not support the "Network initiated MO call" option shall treat this message as a message with 
message type not defined for the PD. 

This message is sent by the mobile station to the network to indicate the requested channel characteristics for the call 
which may be initiated by the mobile station. 

See Table 9.67b/3GPP TS 24.008. 

Message type: CC-ESTABLISHMENT CONFIRMED 

Significance: local 

Direction: mobile station to network 

Table 9.67b/3GPP TS 24.008: CC-ESTABLISHMENT CONFIRMED message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




CC-Establishment 
confirmed 
message type 


IVIessage type 
10.4 


M 


V 


1 


D- 


Repeat Indicator 


Repeat Indicator 
10.5.4.22 


C 


TV 


1 


04 


Bearer capability 1 


Bearer capability 
10.5.4.5 


M 


TLV 


3-10 


04 


Bearer capability 2 


Bearer capability 
10.5.4.5 





TLV 


3-10 


08 


Cause 


Cause 
10.5.4.11 





TLV 


4-32 


40 


Supported Codecs 


Supported Codec List 
10.5.4.32 





TLV 


5-n 



9.3.1 7b.1 Repeat indicator 

The repeat indicator information element shall be included if bearer capability 1 information element and bearer 
capability 2 IE are both included in the message. 

9.3.1 7b. 2 Bearer capability 1 and bearer capability 2 

If, in any subsequent SETUP message to be sent on this transaction the bearer capability 1 information element is to be 
followed by the bearer capability 2 IE, then the bearer capability 2 IE shall be included in this message. 

9.3.1 7b.3 Cause 

This information element is included if the mobile station is compatible but the user is busy. 

9.3.1 7b.4 Supported Codecs 

This information element shall be included for speech calls, if the mobile station supports UMTS radio access. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



275 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.18 Release 

9.3.1 8.1 Release (network to mobile station direction) 

This message is sent, from the network to the mobile station to indicate that the network intends to release the 
transaction identifier, and that the receiving equipment shall release the transaction identifier after sending RELEASE 
COMPLETE. 

See table 9.68/3GPP TS 24.008. 

Message type: RELEASE 

Significance: local (note) 

Direction: network to mobile station 

Table 9.68/3GPP TS 24.008: RELEASE message content (network to mobile station direction) 



IE! 


information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Release 
message type 


IVIessage type 
10.4 


M 


V 


1 


08 


Cause 


Cause 
10.5.4.11 





TLV 


4-32 


08 


Second cause 


Cause 
10.5.4.11 





TLV 


4-32 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 



NOTE: This message has local significance; however, it may carry information of global significance when used 
as the first call clearing message. 

9.3.18.1.1 Cause 

This information element shall be included if this message is used to initiate call clearing. 



9.3.18.1.2 



Second cause 



This information element may be included under the conditions described in subclause 5.4.4. L2. 3 "Abnormal cases" 
(Clearing initiated by the network). 

9.3.18.1.3 Facility 

This information element may be included for functional operation of supplementary services. 



9.3.18.1.4 



User-user 



This information element may be included in the network to mobile station direction, when the RELEASE message is 
used to initiate call clearing, in order to transport user-user information from the remote user. 

9.3.1 8.2 Release (mobile station to network direction) 

This message is sent from the mobile station to the network to indicate that the mobile station intends to release the 
transaction identifier, and that the receiving equipment shall release the transaction identifier after sending RELEASE 
COMPLETE. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 276 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

See table 9.68a/3GPP TS 24.008. 
Message type: RELEASE 
Significance: local (note) 
Direction: mobile station to network direction 

Table 9.68a/3GPP TS 24.008: RELEASE message content (mobile station to network direction) 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Release 
message type 


IVIessage type 
10.4 


M 


V 


1 


08 


Cause 


Cause 
10.5.4.11 





TLV 


4-32 


08 


Second cause 


Cause 
10.5.4.11 





TLV 


4-32 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 


7F 


SS version 


SS version indicator 
10.5.4.24 





TLV 


2-3 



NOTE: This message has local significance; however, it may carry information of global significance when used 
as the first call clearing message. 

9.3.18.2.1 Cause 

This information element shall be included if this message is used to initiate call clearing. 



9.3.18.2.2 



Second cause 



This information element may be included under the conditions described in subclause 5.4.3.5 "Abnormal cases" 
(Clearing initiated by the mobile station). 

9.3.18.2.3 Facility 

This information element may be included for functional operation of supplementary services. 

9.3.18.2.4 User-user 

This information element is included when the RELEASE message is used to initiate call clearing and the mobile 
station wants to pass user information to the remote user at call clearing time. 

9.3.18.2.5 SS version 

This information element shall not be included if iho facility information element is not present in this message. 

This information element shall be included or excluded as defined in 3GPP TS 24.010 [21]. This information element 
should not be transmitted unless explicitly required by 3GPP TS 24.010. 



9.3.18a Recall $(CCBS)$ 



A mobile station that does not support the "Network initiated MO call" option shall treat this message as a message with 
message type not defined for the PD. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



277 



ETSI TS 124 008 V7.14.0 (2009-03) 



This message is sent from the network to the mobile station to initiate the sending of the SETUP message. In addition it 
provides information for user notification. 

See Table 9.68b/3GPP TS 24.008. 

Message type: RECALL 
Significance: local 

Direction: network to mobile station 

Table 9.68b/3GPP TS 24.008: Recall message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Recall 
message type 


IVIessage type 
10.4 


M 


V 


1 




Recall Type 


Recall Type 
10.5.4.21a 


M 


V 


1 




Facility 


Facility 
10.5.4.15 


M 


LV 


2-n 



9.3.1 8a. 1 Recall Type 

The purpose of the recall type information element is to describe the reason for the recall. 

9.3.1 8a.2 Facility 

The information element shall be included for functional operation of supplementary services. 

9.3.19 Release complete 

9.3.1 9.1 Release complete (network to mobile station direction) 

This message is sent from the network to the mobile station to indicate that the network has released the transaction 
identifier and that the mobile station shall release the transaction identifier. 

See table 9.69/3GPP TS 24.008. 

Message type: RELEASE COMPLETE 

Significance: local (note) 

Direction: network to mobile station direction 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



278 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.69/3GPP TS 24.008: RELEASE COMPLETE message content (network to mobile station 

direction) 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Release complete 
message type 


Message type 
10.4 


M 


V 


1 


08 


Cause 


Cause 
10.5.4.11 





TLV 


4-32 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 



NOTE: This message has local significance; however, it may carry information of global significance when used 
as the first call clearing message. 

9.3.19.1.1 Cause 

This information element shall be included if the message is used to initiate call clearing. 

9.3.19.1.2 Facility 

This information element may be included for functional operation of supplementary services. 



9.3.19.1.3 



User-user 



This information element is included in the network to mobile station direction, when the RELEASE COMPLETE 
message is used to initiate call clearing, in order to transport user-user information from the remote user. 

9.3.1 9.2 Release complete (mobile station to network direction) 

This message is sent from the mobile station to the network to indicate that the mobile station has released the 
transaction identifier and that the network shall release the transaction identifier. 

See table 9.69a/3GPP TS 24.008. 

Message type: RELEASE COMPLETE 

Significance: local (note) 

Direction: mobile station to network direction 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



279 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.69a/3GPP TS 24.008: RELEASE COMPLETE message content (mobile station to network 

direction) 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Release complete 
message type 


Message type 
10.4 


M 


V 


1 


08 


Cause 


Cause 
10.5.4.11 





TLV 


4-32 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-131 


7F 


SS version 


SS version indicator 
10.5.4.24 





TLV 


2-3 



NOTE: This message has local significance; however, it may carry information of global significance when used 
as the first call clearing message. 

9.3.19.2.1 Cause 

This information element shall be included if the message is used to initiate call clearing. 

9.3.19.2.2 Facility 

This information element may be included for functional operation of supplementary services. 



9.3.19.2.3 



User-user 



This information element is included in the mobile station to network direction when the RELEASE COMPLETE 
message is used to initiate call clearing and the mobile station wants to pass user information to the remote user at call 
clearing time. 

9.3.19.2.4 SS version. 

This information element shall not be included if the facility information element is not present in this message. 

This information element shall be included or excluded as defined in 3GPP TS 24.010 [21]. This information element 
should not be transmitted unless explicitly required by 3GPP TS 24.010. 

9.3.20 Retrieve 

This message is sent by the mobile user to request the retrieval of a held call. 
See table 9.69b/3GPP TS 24.008 for the content of the RETRIEVE message. 
For the use of this message, see 3GPP TS 24.010 [21]. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 

Message type: RETRIEVE 

Significance: local 

Direction: mobile station to network 



280 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.69b/3GPP TS 24.008: RETRIEVE message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Retrieve 
message type 


IVlessage type 
10.4 


M 


V 


1 



9.3.21 Retrieve Acknowledge 

This message is sent by the network to indicate that the retrieve function has been successfully performed. 
See table 9.69c/3GPP TS 24.008 for the content of the RETRIEVE ACKNOWLEDGE message. 
For the use of this message, see 3GPP TS 24.010. 

Message type: RETRIEVE ACKNOWLEDGE 

Significance: local 

Direction: network to mobile station 

Table 9.69c/3GPP TS 24.008: RETRIEVE ACKNOWLEDGE message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Retrieve Acknowledge 
message type 


IVlessage type 
10.4 


M 


V 


1 



9.3.22 Retrieve Reject 



This message is sent by the network to indicate the inability to perform the requested retrieve function. 
See table 9.69d/3GPP TS 24.008 for the content of the RETRIEVE REJECT message. 
For the use of this message, see 3GPP TS 24.010. 

Message type: RETRIEVE REJECT 

Significance: local 

Direction: network to mobile station 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



281 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.69d/3GPP TS 24.008: RETRIEVE REJECT message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Retrieve Reject 
IVIessage type 


Message type 
10.4 


M 


V 


1 




Cause 


10.5.4.11 


M 


LV 


3-31 



9.3.23 Setup 



9.3.23.1 Setup (mobile terminated call establishment) 

This message is sent by the network to the mobile station to initiate a mobile terminated call establishment. 
See table 9.70/3GPP TS 24.008. 

Message type: SETUP 

Significance: global 

Direction: network to mobile station 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



282 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.70/3GPP TS 24.008: SETUP message content (network to mobile station direction) 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Setup 
IVIessage type 


Message type 
10.4 


M 


V 


1 


D- 


BC repeat indicator 


Repeat indicator 
10.5.4.22 


C 


TV 


1 


04 


Bearer capability 1 


Bearer capability 
10.5.4.5 





TLV 


3-16 


04 


Bearer capability 2 


Bearer capability 
10.5.4.5 





TLV 


3-16 


1C 


Facility 


Facility 
10.5.4.15 





TLV 


2-? 


IE 


Progress indicator 


Progress indicator 
10.5.4.21 





TLV 


4 


34 


Signal 


Signal 
10.5.4.23 





TV 


2 


5C 


Calling party BCD 
Number 


Calling party BCD num. 
10.5.4.9 





TLV 


3-14 


5D 


Calling party sub- 
Address 


Calling party subaddr. 
10.5.4.10 





TLV 


2-23 


5E 


Called party BCD 
Number 


Called party BCD num. 
10.5.4.7 





TLV 


3-19 


6D 


Called party sub- 
Address 


Called party subaddr. 
10.5.4.8 





TLV 


2-23 


74 


Redirecting party BCD number 


Redirecting party BCD num. 
10.5.4.21b 





TLV 


3-19 


75 


Redirecting party sub-address 


Redirecting party subaddress. 
10.5.4.21c 





TLV 


2-23 


D- 


LLC repeat indicator 


Repeat indicator 
10.5.4.22 





TV 


1 


7C 


Low layer 
Compatibility 1 


Low layer comp. 
10.5.4.18 





TLV 


2-18 


7C 


Low layer 
Compatibility II 


Low layer comp. 
10.5.4.18 


C 


TLV 


2-18 


D- 


HLC repeat indicator 


Repeat indicator 
10.5.4.22 





TV 


1 


7D 


High layer 
Compatibility i 


High layer comp. 
10.5.4.16 





TLV 


2-5 


7D 


High layer 
Compatibility 11 


High layer comp. 
10.5.4.16 


c 


TLV 


2-5 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-35 


8- 


Priority 


Priority Level 
10.5.1.11 





TV 


1 


19 


Alert 


Alerting Pattern 
10.5.4.26 





TLV 


3 


2F 


Network Call Control 
Capabilities 


Network Call Control cap. 
10.5.4.29 





TLV 


3 


3A 


Cause of No CLI 


Cause of No CLI 
10.5.4.30 





TLV 


3 


41 


Backup bearer capability 


Backup bearer capability 
10.5.4.4a 





TLV 


3-15 



9.3.23.1.1 



BC repeat indicator 



The BC repeat indicator information element is included if and only if bearer capability 1 information element and 
bearer capability 2 IE are both present in the message. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 283 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.3.23.1 .2 Bearer capability 1 and bearer capability 2 

The bearer capability 1 information element may be omitted in the case where the mobile subscriber is allocated only 
one directory number for all services (ref.: 3GPP TS 29.007 [38]). The bearer capability 2 IE is missing at least if the 
bearer capability 1 IE is missing. 

If the MSC wishes to indicate capability for an altenative call mode, which can be entered through fallback, this is 
indicated by adding a bearer capability information element (bearer capability) 2 element (see subclause 5.3.6). 

9.3.23.1.3 Facility 

This information element may be included for functional operation of supplementary services. 

9.3.23.1.4 Progress indicator 

This information element is included by the network 

in order to pass information about the call in progress e.g. in the event of interworking and/or 
to make the MS attach the user connection for speech. 

9.3.23.1 .4a Called party BCD number 

For all bands except for PCS 1900, the maximum length of this IE sent by the network shall be 13 octets 

9.3.23.1 .5 Called party subaddress 

Included in the Network-to-mobile station direction if the calling user includes a called party subaddress information 
element in the SETUP message. 

9.3.23.1 .6 LLC repeat indicator 

The LLC repeat indicator information element is included if and only if both following conditions hold: 

The BC repeat indicator IE is contained in the message. 

The low layer compatibility I IE is contained in the message. 
If included, the LLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE. 

9.3.23.1 .7 Low layer compatibility I 

Included in the network-to-mobile station direction if the calling user specified a low layer compatibility. 

9.3.23.1 .8 Low layer compatibility II 

Included if and only if the LLC repeat indicator information element is contained in the message. 

9.3.23.1 .9 HLC repeat indicator 

The HLC repeat indicator information element is included if and only both following conditions hold: 

The BC repeat indicator IE is contained in the message. 

The high layer compatibility i IE is contained in the message. 
If included, the HLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE. 

9.3.23.1 .1 High layer compatibility i 

Included in the network-to-mobile station direction if the calling user specified a high layer compatibility. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 284 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.3.23.1 .1 1 High layer compatibility ii 

Included if and only if the HLC repeat indicator information element is contained in the message. 

9.3.23.1.12 User-user 

May be included in the network to called mobile station direction when the calling remote user included a user-user 
information element in the SETUP message. 

9.3.23.1 .1 3 Redirecting party BCD number 

May be included in the network to called mobile station direction when the call has been redirected. 

9.3.23.1.14 Redirecting party subaddress 

May be included in the network to called mobile station direction when the calling remote user included a called party 
subaddress in the SETUP message and the call has been redirected 

9.3.23.1.15 Priority 

May be included by the network to indicate the priority of the incoming call if eMLPP is used. 

9.3.23.1 .1 6 Alert $(Network Indication of Alerting in the MS)$ 

May be included by the network to give some indication about alerting (category or level). If supported in the MS, this 
optional indication is to be used by the MS as specified in 3GPP TS 22.101 [8]. 

9.3.23. 1 . 1 7 Network Call Control Capabilities 

This information shall be included by the network to indicate its call control capabilities if the network supports 
multicall.and there are no other ongoing calls to the MS. 

9.3.23.1.18 Cause of No CLI 

This IE may be included by the network as defined by 3GPP TS 24.081 [25]. 

When both Calling Party BCD number IE and Cause of No CLI IE are included in SETUP message then the Cause of 
No CLI IE provides additional information on why the number digits are not present. 

9.3.23.1 .1 9 Backup bearer capability 

The backup bearer capability IE may be included by the network only if there are no bearer capability lEs contained in 
the message. 

NOTE: The MSC may use the backup bearer capability IE if it is not able to provide a complete bearer 
capability IE. 



9.3.23.2 Setup (mobile originating call establishment) 

This message is sent from the mobile station to the network to initiate a mobile originating call establishment. 
See table 9.70a/3GPP TS 24.008. 

Message type: SETUP 

Significance: global 

Direction: mobile station to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



285 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.70a/3GPP TS 24.008: SETUP message content (mobile station to network direction) 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Setup 
message type 


Message type 
10.4 


M 


V 


1 


D- 


BC repeat indicator 


Repeat indicator 
10.5.4.22 


C 


TV 


1 


04 


Bearer capability 1 


Bearer capability 
10.5.4.5 


M 


TLV 


3-16 


04 


Bearer capability 2 


Bearer capability 
10.5.4.5 





TLV 


3-16 


1C 


Facility(simple recall alignment) 


Facility 
10.5.4.15 





TLV 


2- 


5D 


Calling party sub- 
address 


Calling party subaddr. 
10.5.4.10 





TLV 


2-23 


5E 


Called party BCD 
number 


Called party BCD num. 
10.5.4.7 


M 


TLV 


3-43 


6D 


Called party sub- 
address 


Called party subaddr. 
10.5.4.8 





TLV 


2-23 


D- 


LLC repeat indicator 


Repeat indicator 
10.5.4.22 





TV 


1 


7C 


Low layer 
compatibility 1 


Low layer comp. 
10.5.4.18 





TLV 


2-18 


7C 


Low layer 
compatibility II 


Low layer comp. 
10.5.4.18 





TLV 


2-18 


D- 


HLC repeat indicator 


Repeat indicator 
10.5.4.22 





TV 


1 


7D 


High layer 
compatibility i 


High layer comp. 
10.5.4.16 





TLV 


2-5 


7D 


High layer 
compatibility ii 


High layer comp. 
10.5.4.16 





TLV 


2-5 


7E 


User-user 


User-user 
10.5.4.25 





TLV 


3-35 


7F 


SS version 


SS version indicator 
10.5.4.24 





TLV 


2-3 


A1 


CLIR suppression 


CLIR suppression 
10.5.4.11a 


c 


T 


1 


A2 


CLIR invocation 


CLIR invocation 
10.5.4.11b 


c 


T 


1 


15 


CC capabilities 


Call Control Capabilities 
10.5.4.5a 





TLV 


4 


1D 


Facility $(CCBS)$ 
(advanced recall alignment) 


Facility 
10.5.4.15 





TLV 


2-? 


1B 


Facility (recall alignment 
Not essential) $(CCBS)$ 


Facility 
10.5.4.15 





TLV 


2-? 


2D 


Stream Identifier 


Stream Identifier 
10.5.4.28 





TLV 


3 


40 


Supported Codecs 


Supported Codec List 
10.5.4.32 





TLV 


5-n 


A3 


Redial 


Redial 
10.5.4.34 





T 


1 



9.3.23.2.1 



BC repeat indicator 



The BC repeat indicator information element is included if and only if bearer capability 1 IE and bearer capability 2 IE 
are both present in the message. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 286 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.3.23.2.2 Facility 

The information element may be included for functional operation of supplementary services. 
Three different codings of this IE exist, for further details see 3GPP TS 24.010. 

9.3.23.2.3 LLC repeat indicator 

The LLC repeat indicator information element is included if and only if both following conditions hold: 
- The BC repeat indicator IE is contained in the message. 
The low layer compatibility I IE is contained in the message. 
If included, the LLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE. 

9.3.23.2.4 Low layer compatibility I 

The information element is included in the MS-to-network direction when the calling MS wants to pass low layer 
compatibility information to the called user. 

9.3.23.2.5 Low layer compatibility II 

Included if and only if the LLC repeat indicator information element is contained in the message. 

9.3.23.2.6 HLC repeat indicator 

The HLC repeat indicator information element is included if and only if both following conditions hold: 

The BC repeat indicator IE is contained in the message. 

The high layer compatibility i IE is contained in the message. 
If included, the HLC repeat indicator shall specify the same repeat indication as the BC repeat indicator IE. 

9.3.23.2.7 High layer compatibility i 

The information element is included when the calling MS wants to pass high layer compatibility information to the 
called user. 

9.3.23.2.8 High layer compatibility ii 

Included if and only if the HLC repeat indicator information element is contained in the message. 

9.3.23.2.9 User-user 

The information element is included in the calling mobile station to network direction when the calling mobile station 
wants to pass user information to the called remote user. 

9.3.23.2.10 SS version 

This information element shall not be included if ih& facility information element is not present in this message. 

This information element shall be included or excluded as defined in 3GPP TS 24.010 [21]. This information element 
should not be transmitted unless explicitly required by 3GPP TS 24.010. 

9.3.23.2.11 CLIP suppression 

The information element may be included by the MS (see 3GPP TS 24.081 [25]). If this information element is included 
the CLIR invocation IE shall not be included. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



287 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.23.2.12 



CLIP invocation 



The information element may be included by the MS (see 3GPP TS 24.081). If this information element is included the 
CLIR suppression IE shall not be included. 

9.3.23.2.13 CC Capabilities 

This information element may be included by the mobile station to indicate its call control capabilities. 

9.3.23.2.14 Stream Identifier 

This information element shall be included by the mobile station supporting multicall. 

9.3.23.2.1 5 Bearer capability 1 and bearer capability 2 

If the mobile station wishes to indicate capability for an altenative call mode, which can be entered throughfallback, this 
is indicated by adding a bearer capability information element (bearer capability) 2 element (see subclause 5.3.6). 

9.3.23.2.16 Supported Codecs 

This information element shall be included for speech calls, if the mobile station supports UMTS radio access. 



9.3.23.2.17 



Redial 



This information element shall be included if the mobile station is attempting to set up a call to switch from speech to 
multimedia or vice-versa. 

9.3.23a Start CC $(CCBS)$ 

A Network that does not support the "Network initiated MO call" option shall treat this message as a message with 
message type not defined for the PD. 

This message is sent by the mobile station to the network to open a Call Control transaction which the network has 
requested the mobile station to open. 

See Table 9.70b/3GPP TS 24.008. 

Message type: START CC 

Significance: local 

Direction: mobile station to network 

Table 9.70b/3GPP TS 24.008: START CC message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Start CC 
message type 


Message type 
10.4 


M 


V 


1 


15 


CC Capabilities 


Call Control Capabilities 
10.5.4.5a 





TLV 


4 



9.3.23a.1 CC Capabilities 

This information element may be included by the mobile station to indicate its call control capabilities 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



288 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.24 Start DTMF 

This message is sent by the mobile station to the network and contains the digit the network should reconvert back into 
a DTMF tone which is then applied towards the remote user. 

See table 9.71/3GPP TS 24.008. 

Message type: START DTMF 

Significance: local 

Direction: mobile station to network 

Table 9.71/3GPP TS 24.008: START DTMF message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Start DTMF 
message type 


Message type 
10.4 


M 


V 


1 


2C 


Keypad facility 


Keypad facility 
10.5.4.17 


M 


TV 


2 



9.3.25 Start DTMF Acknowledge 

This message is sent by the network to the mobile station to indicate the successful initiation of the action requested by 
the START DTMF message (conversion of the digit contained in this message into a DTMF tone). 

See table 9.72/3GPP TS 24.008. 

Message type: START DTMF ACKNOWLEDGE 

Significance: local 

Direction: network to mobile station 

Table 9.72/3GPP TS 24.008: START DTMF ACKNOWLEDGE message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Start DTMF acknowledge 
message type 


Message type 
10.4 


M 


V 


1 


2C 


Keypad facility 


Keypad facility 
10.5.4.17 


M 


TV 


2 



9.3.25.1 Keypad facility 



This information element contains the digit corresponding to the DTMF tone that the network applies towards the 
remote user. 



9.3.26 Start DTMF reject 



This message is sent by the network to the mobile station, if the network can not accept the START DTMF message. 
See table 9.73/3GPP TS 24.008. 

Message type: START DTMF REJECT 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



289 



ETSI TS 124 008 V7.14.0 (2009-03) 



Significance: local 

Direction: network to mobile station 



Table 9.73/3GPP TS 24.008: START DTMF REJECT message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Start DTIVIF reject 
message type 


IVIessage type 
10.4 


M 


V 


1 




Cause 


Cause 
10.5.4.11 


M 


LV 


3-31 



9.3.27 Status 

This message is sent by the mobile station or the network at any time during a call to report certain error conditions 
listed in clause 8. It shall also be sent in response to a STATUS ENQUIRY message. 

See table 9.74/3GPP TS 24.008. 

Message type: STATUS 

Significance: local 

Direction: both 

Table 9.74/3GPP TS 24.008: STATUS message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Status 
message type 


IVIessage type 
10.4 


M 


V 


1 




Cause 


Cause 
10.5.4.11 


M 


LV 


3-31 




Call state 


Call state 
10.5.4.6 


M 


V 


1 


24 


Auxiliary states 


Auxiliary states 
10.5.4.4 





TLV 


3 



9.3.27.1 Auxiliary states 

The information element is included if and only if the call state is "active" or "mobile originating modify" and any 
auxiliary state is different from "idle". For the definition of the auxiliary states see 3GPP TS 24.083 and 3GPP TS 
24.084 

9.3.28 Status enquiry 

This message is sent by the mobile station or the network at any time to solicit a STATUS message from the peer layer 
3 entity. Sending of STATUS message in response to a STATUS ENQUIRY message is mandatory. 

See table 9.75/3GPP TS 24.008. 

Message type: STATUS ENQUIRY 

Significance: local 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



290 



ETSI TS 124 008 V7.14.0 (2009-03) 



Direction: both 

Table 9.75/3GPP TS 24.008: STATUS ENQUIRY message content 



IE! 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Status enquiry 
message type 


Message type 
10.4 


M 


V 


1 



9.3.29 Stop DTMF 



This message is sent by a mobile station to the network and is used to stop the DTMF tone sent towards the remote user. 
See table 9.76/3GPP TS 24.008. 

Message type: STOP DTMF 

Significance: local 

Direction: mobile station to network 

Table 9.76/3GPP TS 24.008: STOP DTMF message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Stop DTMF 
message type 


Message type 
10.4 


M 


V 


1 



9.3.30 Stop DTMF acknowledge 

This message is sent by the network to the mobile station to indicate that the sending of the DTMF tone has been 
stopped. 

See table 9.77/3GPP TS 24.008. 

Message type: STOP DTMF ACKNOWLEDGE 

Significance: local 

Direction: network to mobile station 

Table 9.77/3GPP TS 24.008: STOP DTMF ACKNOWLEDGE message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




Stop DTMF acknowledge 
message type 


Message type 
10.4 


M 


V 


1 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



291 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.3.31 User information 

This message is sent by the mobile station to the network to transfer information to the remote user. This message is 
also sent by the network to the mobile station to deliver information transferred from the remote user. This message is 
used if the user-to-user transfer is part of an allowed information transfer as defined in 3GPP TS 24.010. 

See table 9.78/3GPP TS 24.008. 

Message type: USER INFORMATION 

Significance: access 

Direction: both 

Table 9.78/3GPP TS 24.008: USER INFORMATION message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Call control 

protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2 




User Information 
message type 


IVIessage type 
10.4 


M 


V 


1 




User-user 


User-user 
10.5.4.25 


M 


LV 


2-130 


AO 


IVIore data 


More data 
10.5.4.19 





T 


1 



9.3.31.1 



User-user 



Some networks may only support a maximum length of 35 octets. Procedures for interworking are not currently defined 
and are for further study. 

R98 and earlier versions of this protocol specified a minimum length of 3 octets for this information element (not 
counting the lEI). To avoid interworking problems with mobile stations supporting only R98 or earlier versions of the 
protocol, the network shall deliver the User information message to these mobile stations only if the length of the User- 
user IE is greater or equal to 3 octets (not counting the lEI). 



9.3.31.2 



More data 



The information element is included by the sending user to indicate that another USER INFORMATION message 
pertaining to the same message block will follow. 

9.4 GPRS Mobility Management Messages 
9.4.1 Attacin request 

This message is sent by the MS to the network in order to perform a GPRS or combined GPRS attach. See 
table 9.4.1/3GPP TS 24.008. 

Message type: ATTACH REQUEST 

Significance: dual 

Direction: MS to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



292 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.1/3GPP TS 24.008: ATTACH REQUEST message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Sl<ip indicator 
10.3.1 


M 


V 


1/2 




Attacti request message identity 


Message type 
10.4 


M 


V 


1 




IVIS networl< capability 


MS network capability 
10.5.5.12 


M 


LV 


3-9 




Attacli type 


Attach type 
10.5.5.2 


M 


V 


'h 




GPRS cipliering l<ey sequence 
number 


Ciphering key sequence number 
10.5.1.2 


M 


V 


V2 




DRX parameter 


DRX parameter 
10.5.5.6 


M 


V 


2 




P-TMSI or IMS! 


Mobile identity 
10.5.1.4 


M 


LV 


6-9 




Old routing area identification 


Routing area identification 
10.5.5.15 


M 


V 


6 




MS Radio Access capability 


MS Radio Access capability 
10.5.5.12a 


M 


LV 


6-52 


19 


Old P-TMSI signature 


P-TMSI signature 
10.5.5.8 





TV 


4 


17 


Requested READY timer 
value 


GPRS Timer 
10.5.7.3 





TV 


2 


9- 


TMSI status 


TMSI status 
10.5.5.4 





TV 


1 


33 


PS LCS Capability 


PS LCS Capability 
10.5.5.22 





TLV 


3 



9.4.1 .1 Old P-TMSI signature 

This IE is included if a valid P-TMSI and P-TMSI signature are stored in the MS. 

9.4.1 .2 Requested READY timer value 

This IE may be included if the MS wants to indicate a preferred value for the READY timer. 

9.4.1.3 TMSI status 

This IE shall be included if the MS performs a combined GPRS attach and no valid TMSI is available. 

9.4.1.4 PS LCS Capability 

This IE shall be included if the MS supports at least one positioning method for the provision of location services (LCS) 
via the PS domain in Gb-mode. 



9.4.2 Attach accept 



This message is sent by the network to the MS to indicate that the corresponding attach request has been accepted. See 
table 9.4.2/3GPP TS 24.008. 

Message type: ATTACH ACCEPT 

Significance: dual 

Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



293 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.2/3GPP TS 24.008: ATTACH ACCEPT message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Sl<ip indicator 
10.3.1 


M 


V 


1/2 




Attach accept message identity 


Message type 
10.4 


M 


V 


1 




Attach result 


Attach result 
10.5.5.1 


M 


V 


1/2 




Force to standby 


Force to standby 
10.5.5.7 


M 


V 


1/2 




Periodic RA update timer 


GPRS Timer 
10.5.7.3 


M 


V 


1 




Radio priority for SMS 


Radio priority 
10.5.7.2 


M 


V 


1/2 




Radio priority for TOIVIS 


Radio priority 2 
10.5.7.5 


M 


V 


1/2 




Routing area identification 


Routing area identification 
10.5.5.15 


M 


V 


6 


19 


P-TIVISI signature 


P-TMSI signature 
10.5.5.8 





TV 


4 


17 


Negotiated READY timer 
value 


GPRS Timer 
10.5.7.3 





TV 


2 


18 


Allocated P-TMSI 


Mobile identity 
10.5.1.4 





TLV 


7 


23 


IVIS identity 


Mobile identity 
10.5.1.4 





TLV 


7-10 


25 


GMM cause 


GMM cause 
10.5.5.14 





TV 


2 


2A 


T3302 value 


GPRS Timer 2 
10.5.7.4 





TLV 


3 


8C 


Cell Notification 


Cell Notification 
10.5.5.21 





T 


1 


4A 


Equivalent PLMNs 


PLMN List 
10.5.1.13 





TLV 


5-47 


B- 


Network feature support 


Network feature support 
10.5.5.23 





TV 


1 


34 


Emergency Number List 


Emergency Number List 
10.5.3.13 





TLV 


5-50 


A- 


Requested IVIS Information 


Requested MS Information 
10.5.5.25 





TV 


1 


37 


T33 19 value 


GPRS Timer 2 
10.5.7.4 





TLV 


3 



9.4.2.1 P-TMSI signature 

This IE may be included to assign an identity to the MS's GMM context. 

9.4.2.2 Negotiated READY timer 

This IE may be included to indicate a value for the READY timer. 

9.4.2.3 Allocated P-TIVISI 

This IE may be included to assign a P-TMSI to an MS in case of a GPRS or combined GPRS attach. 

9.4.2.4 MS identity 

This IE may be included to assign or unassign a TMSI to an MS in case of a combined GPRS attach. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 294 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.4.2.5 GMM cause 

This IE shall be included when IMSI attach for non-GPRS services was not successful during a combined GPRS attach 
procedure. 

9.4.2.6 T3302 value 

This IE may be included to indicate a value for the T3302 timer. 

9.4.2.7 Cell Notification (A/Gb mode only) 

In A/Gb mode, this IE shall be included by the SGSN in order to indicate the ability to support the Cell Notification. 

9.4.2.8 Equivalent PLMNs 

The Equivalent PLMNs information element is included if the network wants to inform the mobile station of equivalent 
PLMNs. 

9.4.2.9 Network feature support 

This IE may be included to inform the MS of the support of certain features. If this IE is not included then the 
respective features are not supported. 

9.4.2.10 Emergency Number List 

This IE may be sent by the network. If this IE is sent, the contents of this IE indicates a list of emergency numbers valid 
within the same MCC as in the cell on which this IE is received. 

9.4.2.11 Requested MS Information 

This IE may be sent by the network to request the MS to provide feature-related information. 

9.4.2.12 T3319value 

This IE may be included to indicate a value for the T3319 timer. 

9.4.3 Attach complete 

This message is sent by the MS to the network if at least one of the following conditions is fulfilled: 
a P-TMSI and/or a TMSI was included within the attach accept message; or 
the network has requested the MS to provide feature-related information. 
See table 9.4.3/3GPP TS 24.008. 

Message type: ATTACH COMPLETE 
Significance: dual 
Direction: MS to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



295 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.3/3GPP TS 24.008: ATTACH COMPLETE message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Attach complete message identity 


Message type 
10.4 


M 


V 


1 


27 


Inter RAT handover information 


Inter RAT information container 
10.5.5.24 





TLV 


3-250 



9.4.3.1 Inter RAT handover information 

This IE shall be included if the network has requested this information in the routing area update accept message. 

9.4.4 Attach reject 

This message is sent by the network to the MS to indicate that the corresponding attach request has been rejected. See 
table 9.4.4/3GPP TS 24.008. 

Message type: ATTACH REJECT 

Significance: dual 

Direction: network to MS 

Table 9.4.4/3GPP TS 24.008: ATTACH REJECT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Attach reject message identity 


Message type 
10.4 


M 


V 


1 




GMM cause 


GMM cause 
10.5.5.14 


M 


V 


1 


2A 


T3302 value 


GPRS Timer 2 
10.5.7.4 





TLV 


3 



9.4.4.1 T3302 value 

This IE may be included to indicate a value for the T3302 timer. 

In lu mode, the network shall not include this IE if this message is to be sent non-integrity protected. 

In lu mode, the MS shall ignore the contents of this IE if this message is received without integrity protection. 

If this IE is not included or if in lu mode the message is not integrity protected, the MS shall use the default value. 



9.4.5 Detach request 



9.4.5.1 Detach request (mobile terminated detach) 

This message is sent by the network to request the release of a GMM context. See table 9.4.5. 1/3GPP TS 24.008. 
Message type: DETACH REQUEST 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 

Significance: dual 
Direction: network to MS 



296 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.5.1/3GPP TS 24.008:DETACH REQUEST message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Detach request message identity 


Message type 
10.4 


M 


V 


1 




Detach type 


Detach type 
10.5.5.5 


M 


V 


1/2 




Force to standby 


Force to standby 
10.5.5.7 


M 


V 


1/2 


25 


GIVIIVI cause 


GIVIM cause 
10.5.5.14 





TV 


2 



9.4.5.1.1 GMM cause 

This IE shall be included in case the detach reason has to be indicated to the MS, e.g. due to a failed IMEI check. 

9.4.5.2 Detach request (mobile originating detach) 

This message is sent by the MS to request the release of a GMM context. See table 9.4.5. 2/3GPP TS 24.008. 
Message type: DETACH REQUEST 
Significance: dual 
Direction: MS to network 

Table 9.4.5.2/3GPP TS 24.008:DETACH REQUEST message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Detach request message identity 


Message type 
10.4 


M 


V 


1 




Detach type 


Detach type 
10.5.5.5 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 


18 


P-TMSI 


Mobile identity 
10.5.1.4 





TLV 


7 


19 


P-TMSI signature 


P-TMSI signature 2 
10.5.5.8a 





TLV 


5 



9.4.5.2.1 P-TMSI 
This IE shall be included by the MS. 

9.4.5.2.2 P-TMSI signature 

This IE shall be included if the MS has a valid P-TMSI signature. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



297 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.4.6 Detach accept 



9.4.6.1 



Detach accept (mobile terminated detach) 



This message is sent by the MS to indicate that the detach procedure has been completed. See table 9.4.6. 1/3GPP TS 
24.008. 

Message type: DETACH ACCEPT 

Significance: dual 

Direction: MS to network 

Table 9.4.6.1/3GPP TS 24.008:DETACH ACCEPT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Detach accept message identity 


Message type 
10.4 


M 


V 


1 



9.4.6.2 



Detach accept (mobile originating detach) 



This message is sent by the network to indicate that the detach procedure has been completed. See table 9.4.6. 2/3GPP 
TS 24.008. 

Message type: DETACH ACCEPT 

Significance: dual 

Direction: network to MS 

Table 9.4.6.2/3GPP TS 24.008:DETACH ACCEPT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Detach accept message identity 


Message type 
10.4 


M 


V 


1 




Force to standby 


Force to standby 
10.5.5.7 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 



9.4.7 P-TMSI reallocation command 

This message is sent by the network to the MS to reallocate a P-TMSI. See table 9.4.7/3GPP TS 24.008. 
Message type: P-TMSI REALLOCATION COMMAND 
Significance: dual 
Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



298 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.7/3GPP TS 24.008: P-TMS! REALLOCATION COMMAND message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




P-TMSI reallocation command 
message identity 


Message type 
10.4 


M 


V 


1 




Allocated P-TMSI 


Mobile identity 
10.5.1.4 


M 


LV 


6 




Routing area identification 


Routing area identification 
10.5.5.15 


M 


V 


6 




Force to standby 


Force to standby 
10.5.5.7 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 


19 


P-TMSI signature 


P-TMSI signature 
10.5.5.8 





TV 


4 



9.4.7.1 P-TMSI signature 

This IE may be included to assign an identity to the MS's GMM context. 

9.4.8 P-TMSI reallocation complete 

This message is sent by the MS to the network to indicate that reallocation of a P-TMSI has taken place. See 
table 9.4.8/3GPP TS 24.008. 

Message type: P-TMSI REALLOCATION COMPLETE 

Significance: dual 

Direction: MS to network 

Table 9.4.8/3GPP TS 24.008: P-TMSI REALLOCATION COMPLETE message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




P-TMSI reallocation complete 
message identity 


Message type 
10.4 


M 


V 


1 



9.4.9 Authentication and ciphering request 

This message is sent by the network to the MS to initiate authentication of the MS identity. Additionally, the ciphering 
mode is set, indicating whether ciphering will be performed or not. See table 9.4.9/3GPP TS 24.008. 

Message type: AUTHENTICATION AND CIPHERING REQUEST 

Significance: dual 

Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



299 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.9/TS 24.008: AUTHENTICATION AND CIPHERING REQUEST message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Autlientication and ciphering 
request message identity 


Message type 
10.4 


M 


V 


1 




Ciphering algorithm 


Ciphering algorithm 
10.5.5.3 


M 


V 


1/2 




IMEISV request 


IMEISV request 
10.5.5.10 


M 


V 


1/2 




Force to standby 


Force to standby 
10.5.5.7 


M 


V 


1/2 




A&C reference number 


A&C reference number 
10.5.5.19 


M 


V 


1/2 


21 


Authentication parameter RAND 


Authentication parameter RAND 
10.5.3.1 





TV 


17 


8- 


GPRS ciphering key sequence 
number 


Ciphering key sequence number 
10.5.1.2 


C 


TV 


1 


28 


Authentication parameter 
AUTN 


Authentication parameter AUTN 
10.5.3.1.1 





TLV 


18 



9.4.9.1 Authentication Parameter RAND 

This IE shall only be included if authentication shall be performed. 

9.4.9.2 GPRS ciphering key sequence number 

This IE is included if and only if the Authentication parameter RAND is contained in the message. 



9.4.9.3 



Authentication Parameter AUTN 



This IE shall be present if and only if the authentication challenge is a UMTS authentication challenge. The presence or 
absence of this IE defines- in the case of its absence- a GSM authentication challenge or- in the case of its presence- a 
UMTS authentication challenge. 

The MS shall ignore the IE if a SIM is inserted in the MS. 

In UMTS, the MS shall reject the AUTHENTICATION & CIPHERING REQUEST message as specified in 
subclause 4.7.7.5.1 if this IE is not present and a USIM is inserted in the MS. 

9.4.10 Authentication and ciphering response 

This message is sent by the MS to the network in response to an Authentication and ciphering request message. See 
table 9.4.10/3GPP TS 24.008. 

Message type: AUTHENTICATION AND CIPHERING RESPONSE 

Significance: dual 

Direction: MS to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



300 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.1 0/3GPP TS 24.008: AUTHENTICATION AND CIPHERING RESPONSE message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Authentication and ciphering 
response message identity 


GPRS message type 
10.4 


M 


V 


1 




A&C reference number 


A&C reference number 
10.5.5.19 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 


22 


Authentication parameter 
Response 


Authentication Response parameter 
10.5.3.2 





TV 


5 


23 


IMEISV 


IVIobile identity 
10.5.1.4 





TLV 


11 


29 


Authentication Response 
parameter (extension) 


Authentication Response parameter 
10.5.3.2.1 





TLV 


3-14 



9.4.10.1 Authentication Response Parameter 

This IE is included if authentication was requested within the corresponding authentication and ciphering request 
message. This IE contains the SRES, if the authentication challenge was for GSM or the RES (all or just the 4 most 
significant octets of) if it is a UMTS authentication challenge (see also subclause 9.4.10.2) 

9.4.10.2 IMEISV 

This IE is included if requested within the corresponding authentication and ciphering request message. 

9.4.10.3 Authentication Response Parameter (extension) 

This IE shall be included if and only if the authentication challenge was a UMTS authentication challenge and the RES 
parameter is greater than 4 octets in length. It shall contain the least significant remaining bits of the RES (the four most 
significant octets shall be sent in the Authentication Response Parameter IE (see subclause 9.2.3.1)) 

This IE shall not be included if a SIM is inserted in the MS. 

9.4.10a Authentication and Ciphering Failure 

This message is sent by the mobile station to the network to indicate that authentication of the network has failed. See 
table 9.4.10a/3GPP TS 24.008. 

Message type: AUTHENTICATION AND CIPHERING FAILURE 

Significance: dual 

Direction: mobile station to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



301 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.1 0a/3GPP TS 24.008: AUTHENTICATION AND CIPHERING FAILURE message content 



lEI 


Information element 


Type/Reference 


Presence 


Format 


Length 




Mobility management 
Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip Indicator 


Skip Indicator 
10.3.1 


M 


V 


1/2 




Authentication and Ciphering 

Failure 

Message type 


Message type 
10.4 


M 


V 


1 




GMM Cause 


GMM Cause 
10.5.5.14 


M 


V 


1 


30 


Authentication Failure parameter 


Authentication Failure parameter 
10.5.3.2.2 





TLV 


16 



9.4.1 Oa.1 Authentication Failure parameter 

This IE shall be sent if and only if the GMM cause was "Synch failure". It shall include the response to the 
authentication challenge from the USIM, which is made up of the AUTS parameter (see 3GPP TS 33.102 [5a]). 

9.4.1 1 Authentication and ciphering reject 

This message is sent by the network to the MS to indicate that authentication has failed (and that the receiving MS shall 
abort all activities). See table 9.4.11/3GPP TS 24.008. 

Message type: AUTHENTICATION AND CIPHERING REJECT 

Significance: dual 
Direction: network to MS 

Table 9.4.1 1/3GPP TS 24.008: AUTHENTICATION AND CIPHERING REJECT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Authentication and ciphering 
reject message identity 


Message type 
10.4 


M 


V 


1 



9.4.12 Identity request 



This message is sent by the network to the MS to request submission of the MS identity according to the specified 
identity type. See table 9.4.12/3GPP TS 24.008. 

Message type: IDENTITY REQUEST 

Significance: dual 

Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



302 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.1 2/3GPP TS 24.008: IDENTITY REQUEST message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Identity request message identity 


IVIessage type 
10.4 


IVI 


V 


1 




Identity type 


Identity type 2 
10.5.5.9 


M 


V 


1/2 




Force to standby 


Force to standby 
10.5.5.7 


M 


V 


1/2 



9.4.13 Identity response 



This message is sent by the MS to the network in response to an identity request message providing the requested 
identity. See table 9.4.13/3GPP TS 24.008. 

Message type: IDENTITY RESPONSE 

Significance: dual 

Direction: MS to network 

Table 9.4.1 3/3GPP TS 24.008: IDENTITY RESPONSE message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Identity response message 
identity 


IVIessage type 
10.4 


M 


V 


1 




IVIobile identity 


Mobile identity 
10.5.1.4 


M 


LV 


4-10 



9.4.14 Routing area update request 



This message is sent by the MS to the network either to request an update of its location file or to request an IMSI 
attach for non-GPRS services. See table 9.4.14/3GPP TS 24.008. 

Message type: ROUTING AREA UPDATE REQUEST 

Significance: dual 

Direction: MS to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



303 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.1 4/3GPP TS 24.008: ROUTING AREA UPDATE REQUEST message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Routing area update request 
message identity 


Message type 
10.4 


M 


V 


1 




Update type 


Update type 
10.5.5.18 


M 


V 


1/2 




GPRS cipliering key sequence 
number 


Ciphering key sequence number 
10.5.1.2 


M 


V 


1/2 




Old routing area identification 


Routing area identification 
10.5.5.15 


M 


V 


6 




MS Radio Access capability 


MS Radio Access capability 
10.5.5.12a 


M 


LV 


6-52 


19 


Old P-TMSI signature 


P-TMSI signature 
10.5.5.8 





TV 


4 


17 


Requested READY timer value 


GPRS Timer 
10.5.7.3 





TV 


2 


27 


DRX parameter 


DRX parameter 
10.5.5.6 





TV 


3 


9- 


TMSI status 


TMSI status 
10.5.5.4 





TV 


1 


18 


P-TMSI 


Mobile identity 
10.5.1.4 





TLV 


7 


31 


MS network capability 


MS network capability 
10.5.5.12 





TLV 


4-10 


32 


PDP context status 


PDP context status 
10.5.7.1 





TLV 


4 


33 


PS LCS Capability 


PS LCS Capability 
10.5.5.22 





TLV 


3 


35 


MBMS context status 


MBMS context status 
10.5.7.6 





TLV 


2-18 



9.4.14.1 Old P-TMSI signature 

This IE is included by the MS if it was received from the network in an ATTACH ACCEPT or ROUTING AREA 
UPDATE ACCEPT message. 

9.4.1 4.2 Requested READY timer value 

This IE may be included if the MS wants to indicate a preferred value for the READY timer. 

9.4.14.3 DRX parameter 

This IE shall be included if the MS changes the access network from GSM to UMTS, or the MS wants to indicate new 
DRX parameters to the network. 

9.4.14.4 TMSI status 

This IE shall be included if the MS performs a combined routing area update and no valid TMSI is available. 

9.4.14.5 P-TMSI (UMTS only) 

This IE shall be included by the MS. 

9.4.1 4.6 MS network capability 

This IE shall be included by the MS to indicate it"s capabilities to the network. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 304 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.4.1 4.7 PDP context status 

This IE shall be included by the MS. 

9.4.14.8 PS LCS Capability 

This IE shall be included if the MS supports at least one positioning method for the provision of location services (LCS) 
via the PS domain in Gb-mode. 

9.4.1 4.9 MBMS context status 

This IE shall be included by the MS, if it has MBMS contexts with an SM state different from PDP-INACTIVE. 

9.4.15 Routing area update accept 

This message is sent by the network to the MS to provide the MS with GPRS mobility management related data in 
response to a routing area update request message. See table 9.4.15/3GPP TS 24.008. 

Message type: ROUTING AREA UPDATE ACCEPT 

Significance: dual 

Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



305 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.1 5/3GPP TS 24.008: ROUTING AREA UPDATE ACCEPT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Routing area update accept 
message identity 


IVIessage type 
10.4 


M 


V 


1 




Force to standby 


Force to standby 
10.5.5.7 


M 


V 


1/2 




Update result 


Update result 
10.5.5.17 


M 


V 


1/2 




Periodic RA update timer 


GPRS Timer 
10.5.7.3 


M 


V 


1 




Routing area identification 


Routing area identification 
10.5.5.15 


M 


V 


6 


19 


P-TMSI signature 


P-TMSI signature 
10.5.5.8 





TV 


4 


18 


Allocated P-TMSI 


Mobile identity 
10.5.1.4 





TLV 


7 


23 


MS identity 


Mobile identity 
10.5.1.4 





TLV 


7-10 


26 


List of Receive N-PDU Numbers 


Receive N-PDU Number list 
10.5.5.11 





TLV 


4- 19 


17 


Negotiated READY timer value 


GPRS Timer 
10.5.7.3 





TV 


2 


25 


GIVIM cause 


GMM cause 
10.5.5.14 





TV 


2 


2A 


T3302 value 


GPRS Timer 2 
10.5.7.4 





TLV 


3 


8C 


Cell Notification 


Cell Notification 
10.5.5.21 





T 


1 


4A 


Equivalent PLMNs 


PLMN List 
10.5.1.13 





TLV 


5-47 


32 


PDP context status 


PDP context status 
10.5.7.1 





TLV 


4 


B- 


Network feature support 


Network feature support 
10.5.5.23 





TV 


1 


34 


Emergency Number List 


Emergency Number List 
10.5.3.13 





TLV 


5-50 


35 


IVIBMS context status 


MBMS context status 
10.5.7.6 





TLV 


2-18 


A- 


Requested IVIS Information 


Requested MS Information 
10.5.5.25 





TV 


1 


37 


T3319 value 


GPRS Timer 2 
10.5.7.4 





TLV 


3 



9.4.15.1 P-TMSI signature 

This IE may be included to assign an identity to the MS's GMM context. 

9.4.15.2 Allocated P-TMSI 

This IE may be included to assign a P-TMSI to an MS in case of a GPRS or combined routing area updating procedure. 

9.4.15.3 MS Identity 

This IE may be included to assign or unassign a TMSI to a MS in case of a combined routing area updating procedure. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 306 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

9.4.15.4 List of Receive N-PDU Numbers 

This IE shall be included in case of an inter SGSN routing area updating from A/Gb mode to A/Gb mode, or inter 
SGSN routing area updating from lu mode to A/Gb mode, or intra SGSN routing area updating from lu mode to A/Gb 
mode, if there are PDP contexts that have been activated in LLC acknowledged transfer mode. 

9.4.1 5.5 Negotiated READY timer value 

This IE may be included to indicate a value for the READY timer. 

9.4.15.6 G MM cause 

This IE shall be included if the combined GPRS routing area updating procedure was successful for GPRS services 
only. 

9.4.15.7 T3302 value 

This IE may be included to indicate a value for the T3302 timer. 

In lu mode, the network shall not include this IE if this message is to be sent non-integrity protected. 

In lu mode, if this message is received without integrity protection the MS shall ignore the contents of this IE and use 
the last received value if available. If there is no last received value, the MS shall use the default value. 

If this IE is not included in the message in A/Gb mode or if in lu mode this IE is not included in an integrity protected 
message, the MS shall use the default value. 

9.4.1 5.8 Cell Notification (A/Gb mode only) 

In A/Gb mode, this IE shall be included if by the SGSN in order to indicate the ability to support the Cell Notification. 

9.4.15.9 Equivalent PLMNs 

The Equivalent PLMNs information element is included if the network wants to inform the mobile station of equivalent 
PLMNs. 

9.4.1 5.1 PDP context status 

This IE shall be included by the NW. 

9.4.1 5.1 1 Network feature support 

This IE may be included to inform the MS of the support of certain features. If this IE is not included then the 
respective features are not supported. 

9.4.1 5.1 2 Emergency Number List 

This IE may be sent by the network. If this IE is sent, the contents of this IE indicates a list of emergency numbers valid 
within the same MCC as in the cell on which this IE is received. 

9.4.1 5.1 3 MBMS context status 

This IE shall be included by the network, if it has MBMS contexts for the MS with an SM state different from PDP- 
INACTIVE. 

9.4.15.14 Requested MS Information 

This IE may be sent by the network to request the MS to provide feature-related information. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



307 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.4.15.15 T3319value 

This IE may be included to indicate a value for the T3319 timer. 

9.4.1 6 Routing area update complete 



This message shall be sent by the MS to the network in response to a routing area update accept message if at least one 
of the following conditions is fulfilled: 

a P-TMSI and/or a TMSI has been assigned; 

there are established LLC connections; or 

the network has requested the MS to provide feature-related information. 

See table 9.4.16/3GPP TS 24.008. 

Message type: ROUTING AREA UPDATE COMPLETE 

Significance: dual 

Direction: MS to network 

Table 9.4.1 6/3GPP TS 24.008: ROUTING AREA UPDATE COMPLETE message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Routing area update complete 
message identity 


Message type 
10.4 


M 


V 


1 


26 


List of Receive N-PDU Numbers 


Receive N-PDU Number list 
10.5.5.11 





TLV 


4-19 


27 


Inter RAT handover information 


Inter RAT information container 
10.5.5.24 





TLV 


3-250 



9.4.1 6.1 List of Receive N-PDU Numbers 

This IE shall be included if the routing area update accept message contained this IE. 

9.4.1 6.2 Inter RAT handover information 

This IE shall be included if the network has requested this information in the routing area update accept message. 



9.4.17 Routing area update reject 



This message is sent by the network to the MS in order to reject the routing area update procedure. See 
table 9.4.17/3GPP TS 24.008. 

Message type: ROUTING AREA UPDATE REJECT 

Significance: dual 

Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



308 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.1 7/3GPP TS 24.008: ROUTING AREA UPDATE REJECT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Routing area update reject 
message identity 


Message type 
10.4 


M 


V 


1 




GMM cause 


GMM cause 
10.5.5.14 


M 


V 


1 




Force to standby 


Force to standby 
10.5.5.7 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 


2A 


T3302 value 


GPRS Timer 2 
10.5.7.4 





TLV 


3 



9.4.17.1 T3302 value 

This IE may be included to indicate a value for the T3302 timer. 

In lu mode, the network shall not include this IE if this message is to be sent non-integrity protected. 

In lu mode, the MS shall ignore the contents of this IE if this message is received without integrity protection. 

If this IE is not included or if in lu mode the message is not integrity protected, the MS shall use the default value. 

9.4.18 GMM Status 

This message is sent by the MS or by the network at any time to report certain error conditions listed in clause 8. See 
table 9.4.18/3GPP TS 24.008. 

Message type: GMM STATUS 

Significance: local 

Direction: both 

Table 9.4.1 8/3GPP TS 24.008: GMM STATUS message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




GMM Status message identity 


Message type 
10.4 


M 


V 


1 




GMM cause 


GMM cause 
10.5.5.14 


M 


V 


1 



9.4.19 GMM Information 

This message is sent by the network at any time to sent certain information to the MS. 
See table 9.4.19/3GPP TS 24.008. 

Message type: GMM INFORMATION 

Significance: local 

Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



309 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.1 9/3GPP TS 24.008: GMM INFORMATION message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




GIVIIVI Information message 
identity 


Message type 
10.4 


M 


V 


1 


43 


Full name for network 


Network name 
10.5.3.5a 





TLV 


3-? 


45 


Short name for network 


Network name 
10.5.3.5a 





TLV 


3-? 


46 


Local time zone 


Time zone 
10.5.3.8 





TV 


2 


47 


Universal time and local time zone 


Time zone and time 
10.5.3.9 





TV 


8 


48 


LSA Identity 


LSA Identifier 
10.5.3.11 





TLV 


2-5 


49 


Network Daylight Saving Time 


Daylight Saving Time 
10.5.3.12 





TLV 


3 



9.4.19.1 



Full name for network 



This IE may be sent by the network. If this IE is sent, the contents of this IE indicate the "full length name of the 
network" that the network wishes the mobile station to associate with the MCC and MNC contained in the routing area 
identification of the current cell. 



9.4.19.2 



Short name for network 



This IE may be sent by the network. If this IE is sent, the contents of this IE indicate the "abbreviated name of the 
network" that the network wishes the mobile station to associate with the MCC and MNC contained in the routing area 
identification of the cell the MS is currently in. 



9.4.19.3 



Local time zone 



This IE may be sent by the network. The mobile station should assume that this time zone applies to the routing area of 
the cell the MS is currently in. 

If the local time zone has been adjusted for Daylight Saving Time, the network shall indicate this by including the IE 
Network Daylight Saving Time. 



9.4.19.4 



Universal time and local time zone 



This IE may be sent by the network. The mobile station should assume that this time zone applies to the routing area the 
MS is currently in. The mobile station shall not assume that the time information is accurate. 

If the local time zone has been adjusted for Daylight Saving Time, the network shall indicate this by including the IE 
Network Daylight Saving Time. 

9.4.19.5 LSA Identity 

This IE may be sent by the network. The contents of this IE indicate the LSA identity of the serving cell. 

9.4.1 9.6 Network Daylight Saving Time 

This IE may be sent by the network. If this IE is sent, the contents of this IE indicates the value that has been used to 
adjust the local time zone. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



310 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.4.20 Service Request (UMTS only) 



This message is sent by the MS to transfer to establish logical association between the MS and the network. See 
table 9.4.20/3GPP TS 24.008. 

Message type: Service Request 

Significance: dual 

Direction: MS to network 

Table 9.4.20/3GPP TS 24.008: Contents of Service Request message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Service Request 


IVIessage type 
10.4 


M 


V 


1 




Ciphering l<ey sequence number 


Ciphering key sequence number 
10.5.1.2 


M 


V 


1/2 




Service type 


Service type 
10.5.5.20 


M 


V 


1/2 




P-TMSI 


IVIobile station identity 
10.5.1.4 


M 


LV 


6 


32 


PDP context status 


PDP context status 
10.5.7.1 





TLV 


4 


35 


MBIVIS context status 


MBIVIS context status 
10.5.7.6 





TLV 


2-18 


36 


Uplink data status 


Uplink data status 
10.5.7.7 





TLV 


4 



9.4.20.1 PDP context status 

This IE shall be included by the MS. 

9.4.20.2 MBMS context status 

This IE shall be included by the MS, if it has MBMS contexts with an SM state different from PDP-INACTIVE. 

9.4.20.3 Uplink data status 

This IE may be included by the MS when the Service Type is set to "data". 



9.4.21 Service Accept (UMTS only) 



This message is sent by the network in response to a Service Request message. See table 9.4.21/3GPP TS 24.008. 
Message type: Service Accept 
Significance: dual 
Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



311 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.4.21/3GPP TS 24.008: Contents of Service Accept message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Sl<ip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Service Accept 


Message type 
10.4 


M 


V 


1 


32 


PDP context status 


PDP context status 
10.5.7.1 





TLV 


4 


35 


IVIBIVIS context status 


MBMS context status 
10.5.7.6 





TLV 


2-18 



9.4.21 .1 PDP context status 

This IE shall be included by the NW. 

9.4.21 .2 MBMS context status 

This IE shall be included by the network, if it has MBMS contexts for the MS with an SM state different from PDP- 
INACTIVE. 



9.4.22 Service Reject (UMTS only) 



This message is sent by the network to the UE in order to reject the Service request procedure. See table 9.4.22/3GPP 
TS 24.008. 

Message type: Service Reject 

Significance: dual 

Direction: network to MS 

Table 9.4.22/3GPP TS 24.008: Contents of Service Reject message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Skip indicator 


Skip indicator 
10.3.1 


M 


V 


1/2 




Service Reject 


Message type 
10.4 


M 


V 


1 




GIVIM cause 


GMM cause 
10.5.5.14 


M 


V 


1 



9.5 GPRS Session Management Messages 
9.5.1 Activate PDP context request 

This message is sent by the MS to the network to request activation of a PDP context. 
See table 9.5.1/3GPP TS 24.008. 

Message type: ACTIVATE PDP CONTEXT REQUEST 

Significance: global 

Direction: MS to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



312 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.5.1/3GPP TS 24.008: ACTIVATE PDP CONTEXT REQUEST message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Activate PDP context request 
message identity 


IVIessage type 
10.4 


M 


V 


1 




Requested NSAPI 


Network service access point identifier 
10.5.6.2 


M 


V 


1 




Requested LLC SAPI 


LLC service access point identifier 
10.5.6.9 


M 


V 


1 




Requested QoS 


Quality of service 
10.5.6.5 


M 


LV 


13-17 




Requested PDP address 


Packet data protocol address 
10.5.6.4 


M 


LV 


3- 19 


28 


Access point name 


Access point name 
10.5.6.1 





TLV 


3-102 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.1 .1 Access point name 

This IE is included in the message when the MS selects a specific external network to be connected to. 



9.5.1.2 



Protocol configuration options 



This IE is included in the message when the MS wishes to transmit (protocol) data (e.g. configuration parameters, error 
codes or messages/events) to the network. 

This IE shall be included if the MS supports Network Requested Bearer Control procedures. 

9.5.2 Activate PDP context accept 

This message is sent by the network to the MS to acknowledge activation of a PDP context. 
See table 9.5.2/3GPP TS 24.008. 

Message type: ACTIVATE PDP CONTEXT ACCEPT 

Significance: global 

Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



313 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.5.2/3GPP TS 24.008: ACTIVATE PDP CONTEXT ACCEPT message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction Identifier 
10.3.2 


M 


V 


1/2-3/2 




Activate PDP context accept 
message identity 


IVIessage type 
10.4 


M 


V 


1 




Negotiated LLC SAPI 


LLC service access point identifier 
10.5.6.9 


M 


V 


1 




Negotiated QoS 


Quality of service 
10.5.6.5 


M 


LV 


13-17 




Radio priority 


Radio priority 
10.5.7.2 


M 


V 


1/2 




Spare lialf octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 


2B 


PDP address 


Packet data protocol address 
10.5.6.4 





TLV 


4-20 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 


34 


Packet Flow Identifier 


Packet Flow Identifier 
10.5.6.11 





TLV 


3 



9.5.2.1 



PDP address 



This IE shall be included by the network if the MS has requested the activation of a PDP context with the PDP type 
IPv4 or IPv6 and dynamic addressing. 



9.5.2.2 



Protocol configuration options 



This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, 
error codes or messages/events) to the MS. This IE is also included to indicate the selected Bearer Control Mode to be 
applied for all active PDP contexts sharing the same PDP Address and APN. 



9.5.2.3 



Packet Flow Identifier 



This IE may be included if the network wants to indicate the Packet Flow Identifier associated to the PDP context. The 
network shall not include this IE if the MS has not indicated PEC procedure support in PEC feature mode field of MS 
Network Capability IE. 

If the MS has not indicated PEC procedure support, then it shall ignore this IE, if received. 

9.5.3 Activate PDP context reject 

This message is sent by the network to the MS to reject activation of a PDP context. 
See table 9.5.3/3GPP TS 24.008. 

Message type: ACTIVATE PDP CONTEXT REJECT 

Significance: global 

Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



314 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.5.3/3GPP TS 24.008: ACTIVATE PDP CONTEXT REJECT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction Identifier 
10.3.2 


M 


V 


1/2-3/2 




Activate PDP context reject 
message identity 


IVIessage type 
10.4 


M 


V 


1 




SIVI cause 


SM Cause 
10.5.6.6 


M 


V 


1 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.3.1 



Protocol configuration options 



This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, 
error codes or messages/events) to the MS. 

9.5.4 Activate Secondary PDP Context Request 

This message is sent by the MS to the network to request activation of an additional PDP context associated with the 
same PDP address and APN as an already active PDP context. See Table 9.5.4/3GPP TS 24.008. 

Message type: ACTIVATE SECONDARY PDP CONTEXT REQUEST 

Significance: global 

Direction: MS to network 

Table 9.5.4/3GPP TS 24.008: ACTIVATE SECONDARY PDP CONTEXT REQUEST message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


y^ 3/2 




Activate secondary PDP context 
request message identity 


IVIessage type 
10.4 


M 


V 


1 




Requested NSAPI 


Network service access point identifier 
10.5.6.2 


M 


V 


1 




Requested LLC SAPI 


LLC service access point identifier 
10.5.6.9 


M 


V 


1 




Requested QoS 


Quality of service 
10.5.6.5 


M 


LV 


13-17 




Linked Tl 


Linked Tl 
10.5.6.7 


M 


LV 


2-3 


36 


TFT 


Traffic Flow Template 
10.5.6.12 





TLV 


3-257 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.4.1 TFT 

This IE shall be included if a linked PDP context without TFT has already been activated. 



9.5.4.2 



Protocol configuration options 



This IE is included in the message when the MS wishes to transmit (protocol) data (e.g. configuration parameters, error 
codes or messages/events) to the network. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



315 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.5.5 Activate Secondary PDP Context Accept 

This message is sent by the network to the MS to acknowledge activation of an additional PDP context associated with 
the same PDP address and APN as an already active PDP context. See Table 9.5.5/3GPP TS 24.008. 

Message type: ACTIVATE SECONDARY PDP CONTEXT ACCEPT 

Significance: global 

Direction: network to MS 

Table 9.5.5/3GPP TS 24.008: ACTIVATE SECONDARY PDP CONTEXT ACCEPT message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Activate secondary PDP context 
accept message identity 


IVlessage type 
10.4 


M 


V 


1 




Negotiated LLC SARI 


LLC service access point identifier 
10.5.6.9 


M 


V 


1 




Negotiated QoS 


Quality of service 
10.5.6.5 


M 


LV 


13-17 




Radio priority 


Radio priority 
10.5.7.2 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 


34 


Packet Flow Identifier 


Packet Flow Identifier 
10.5.6.11 





TLV 


3 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.5.1 



Packet Flow Identifier 



This IE may be included if the network wants to indicate the Packet Flow Identifier associated to the PDP context. The 
network shall not include this IE if the MS has not indicated PEC procedure support in PEC feature mode field of MS 
Network Capability IE. 

If the MS has not indicated PEC procedure support, then it shall ignore this IE, if received. 



9.5.5.2 



Protocol configuration options 



This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, 
error codes or messages/events) to the MS. 

9.5.6 Activate Secondary PDP Context Reject 

This message is sent by the network to the UE to reject activation of an additional PDP context associated with the same 
PDP address and APN as an already active PDP context. See Table 9.5.6/3GPP TS 24.008. 

Message type: ACTIVATE SECONDARY PDP CONTEXT REJECT 

Significance: global 
Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



316 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.5.6/3GPP TS 24.008: ACTIVATE SECONDARY PDP CONTEXT REJECT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Activate secondary PDP context 
reject message identity 


IVIessage type 
10.4 


M 


V 


1 




SIVI cause 


SM Cause 
10.5.6.6 


M 


V 


1 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.6.1 



Protocol configuration options 



This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, 
error codes or messages/events) to the MS. 

9.5.7 Request PDP context activation 

This message is sent by the network to the MS to initiate activation of a PDP context. 
See table 9.5.7/3GPP TS 24.008. 

Message type: REQUEST PDP CONTEXT ACTIVATION 

Significance: global 

Direction: network to MS 

Table 9.5.7/3GPP TS 24.008: REQUEST PDP CONTEXT ACTIVATION message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Request PDP context activation 
message identity 


IVIessage type 
10.4 


M 


V 


1 




Offered PDP address 


Packet data protocol address 
10.5.6.4 


M 


LV 


3- 19 


28 


Access point name 


Access point name 
10.5.6.1 





TLV 


3-102 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.7.1 



Protocol configuration options 



This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, 
error codes or messages/events) to the MS. 

9.5.8 Request PDP context activation reject 

This message is sent by the MS to the network to reject initiation of a PDP context activation. 
See table 9.5.8/3GPP TS 24.008. 

Message type: REQUEST PDP CONTEXT ACTIVATION REJECT 

Significance: global 

Direction: MS to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



317 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.5.8/3GPP TS 24.008: REQUEST PDP CONTEXT ACTIVATION REJECT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Request PDP context act. reject 
message identity 


IVIessage type 
10.4 


M 


V 


1 




SIVI cause 


SM cause 
10.5.6.6 


M 


V 


1 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.8.1 



Protocol configuration options 



This IE is included in the message when the MS wishes to transmit (protocol) data (e.g. configuration parameters, error 
codes or messages/events) to the network. 

9.5.9 Modify PDP context request (Network to MS direction) 

This message is sent by the network to the MS to request modification of an active PDP context. See table 9.5.9/3GPP 
TS 24.008. 

Message type: MODIFY PDP CONTEXT REQUEST (NETWORK TO MS DIRECTION) 

Significance: global 

Direction: network to MS 

Table 9.5.9/3GPP TS 24.008: MODIFY PDP CONTEXT REQUEST (Network to MS direction) message 

content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




IVIodify PDP context request 
message identity 


IVIessage type 
10.4 


M 


V 


1 




Radio priority 


Radio priority 
10.5.7.2 


M 


V 


1/2 




Spare half octet 


Spare half octet 
10.5.1.8 


M 


V 


1/2 




Requested LLC SAPI 


LLC service access point identifier 
10.5.6.9 


M 


V 


1 




New QoS 


Quality of service 
10.5.6.5 


M 


LV 


13-17 


2B 


PDP address 


Packet data protocol address 
10.5.6.4 





TLV 


4-20 


34 


Packet Flow Identifier 


Packet Flow Identifier 
10.5.6.11 





TLV 


3 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 


36 


TFT 


Traffic Flow Template 
10.5.6.12 





TLV 


3-257 



9.5.9.1 



PDP address 



If the MS requested external PDN address allocation at PDP context activation via an APN and this was confirmed by 
the network in the ACTIVATE PDP CONTEXT ACCEPT message, then the network shall include the PDP address IE 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



318 



ETSI TS 124 008 V7.14.0 (2009-03) 



in the MODIFY PDP CONTEXT REQUEST message once the address has been actually allocated, in order to update 
the PDP context in the MS. 



9.5.9.2 



Packet Flow Identifier 



This IE may be included if the network wants to indicate the Packet Flow Identifier associated to the PDP context. The 
network shall not include this IE if the MS has not indicated PEC procedure support in PEC feature mode field of MS 
Network Capability IE. 

If this IE is not included, the MS shall keep the old Packet Elow Identifier value. If the MS has not indicated PEC 
procedure support, then it shall ignore this IE, if received. 



9.5.9.3 



Protocol configuration options 



This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, 
error codes or messages/events) to the MS. This IE is also included to indicate the selected Bearer Control Mode to be 
apphed. 



9.5.9.4 



TFT 



This IE is included in the message to provide the MS with uplink and downlink packet filters when the protocol 
configuration options information element indicates the selected Bearer Control Mode 'MS/NW. 

9.5.1 Modify PDP context request (MS to network direction) 

This message is sent by the MS to the network to request modification of an active PDP context. See table 9.5. 10/3GPP 
TS 24.008. 

Message type: MODIFY PDP CONTEXT REQUEST (MS TO NETWORK DIRECTION) 

Significance: global 
Direction: MS to network 

Table 9.5.1 0/3GPP TS 24.008: MODIFY PDP CONTEXT REQUEST (MS to network direction) message 

content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction Identifier 
10.3.2 


M 


V 


1/2-3/2 




IVIodify PDP context request 
message identity 


Message type 
10.4 


M 


V 


1 


32 


Requested LLC SAPI 


LLC service access point identifier 
10.5.6.9 





TV 


2 


30 


Requested new QoS 


Quality of service 
10.5.6.5 





TLV 


14-18 


31 


New TFT 


Traffic Flow Template 
10.5.6.12 





TLV 


3-257 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.1 0.1 Requested LLC SAPI 

This IE may be included in the message to request a new LLC SAPI if a new QoS is requested. 

9.5.1 0.2 Requested new QoS 

This IE may be included in the message to request a modification of the QoS. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



319 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.5.10.3 



New TFT 



This IE may be included in the message to request a new TFT or modification of an existing TFT or transfer extra 
parameters to the network (e.g. the Authorization Token; see 3GPP TS 24.229). 

9.5.10.4 Protocol configuration options 

This IE is included in the message when the MS wishes to transmit (protocol) data (e.g. configuration parameters, error 
codes or messages/events) to the network. 

9.5.1 1 Modify PDP context accept (MS to network direction) 

This message is sent by the MS to the network to acknowledge the modification of an active PDP context. See 
table 9.5.11/3GPP TS 24.008. 

Message type: MODIFY PDP CONTEXT ACCEPT (MS TO NETWORK DIRECTION) 

Significance: global 

Direction: MS to network 

Table 9.5.1 1/3GPP TS 24.008: MODIFY PDP CONTEXT ACCEPT (MS TO NETWORK DIRECTION) 

message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




IVlodify PDP context accept 
message identity 


IVIessage type 
10.4 


M 


V 


1 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.11.1 



Protocol configuration options 



This IE is included in the message when the MS wishes to transmit (protocol) data (e.g. configuration parameters, error 
codes or messages/events) to the network. 

9.5.12 Modify PDP context accept (Networl< to MS direction) 

This message is sent by the network to the MS to acknowledge the modification of an active PDP context. See 
table 9.5.12/3GPP TS 24.008. 

Message type: MODIFY PDP CONTEXT ACCEPT (NETWORK TO MS DIRECTION) 

Significance: global 

Direction: Network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



320 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.5.1 2/3GPP TS 24.008: MODIFY PDP CONTEXT ACCEPT (NETWORK to MS direction) message 

content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


y^ 3/2 




IVIodify PDP context accept 
message identity 


Message type 
10.4 


M 


V 


1 


30 


Negotiated QoS 


Quality of service 
10.5.6.5 





TLV 


14-18 


32 


Negotiated LLC SAPI 


LLC service access point identifier 
10.5.6.9 





TV 


2 


8 


New radio priority 


Radio priority 
10.5.7.2 





TV 


1 


34 


Packet Flow Identifier 


Packet Flow Identifier 
10.5.6.11 





TLV 


3 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.12.1 Negotiated QoS 

This IE is included in the message if the network assigns a new QoS. 

9.5.1 2.2 Negotiated LLC SAPI 

This IE is included in the message if the network assigns a new LLC SAPI. 

9.5.1 2.3 New radio priority 

This IE is included in the message only if the network modifies the radio priority. 



9.5.12.4 



Packet Flow Identifier 



This IE may be included if the network wants to indicate the Packet Flow Identifier associated to the PDP context. The 
network shall not include this IE if the MS has not indicated PEC procedure support in PEC feature mode field of MS 
Network Capability IE. 

If this IE is not included, the MS shall keep the old Packet Flow Identifier value. If the MS has not indicated PEC 
procedure support, then it shall ignore this IE, if received. 

9.5.12.5 Protocol configuration options 

This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, 
error codes or messages/events) to the MS. 

9.5.13 Modify PDP Context Reject 

This message is sent by the network or the MS to reject a modification of an active PDP context. See Table 
9.5.13/3GPPTS 24.008. 

Message type: MODIFY PDP CONTEXT REJECT 

Significance: global 

Direction: both 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



321 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.5.1 3/3GPP TS 24.008: MODIFY PDP CONTEXT REJECT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




IVIodify PDP Context Reject 


Message type 
10.4 


M 


V 


1 




SIVI cause 


SM Cause 
10.5.6.6 


M 


V 


1 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.13.1 



Protocol configuration options 



This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, 
error codes or messages/events) to the MS. 

9.5.14 Deactivate PDP context request 

This message is sent to request deactivation of an active PDP context or an active MBMS context. See 
table 9.5.14/3GPP TS 24.008. 

Message type: DEACTIVATE PDP CONTEXT REQUEST 

Significance: global 

Direction: both 

Table 9.5.1 4/3GPP TS 24.008: DEACTIVATE PDP CONTEXT REQUEST message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Deactivate PDP context request 
message identity 


Message type 
10.4 


M 


V 


1 




SM cause 


SM cause 
10.5.6.6 


M 


V 


1 


9- 


Tear down indicator 


Tear down indicator 
10.5.6.10 





TV 


1 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 


35 


MBMS protocol configuration 
options 


MBMS protocol configuration options 
10.5.6.15 





TLV 


3-253 



9.5.14.1 



Tear down indicator 



This IE is included in the message in order to indicate whether only the PDP context associated with this specific TI or 
all active PDP contexts sharing the same PDP address and APN as the PDP context associated with this specific TI shall 
be deactivated. 

If this IE is received for an MBMS context, it shall be ignored by the receiver. 

9.5.14.2 Protocol configuration options 

This IE is included in the message when the MS or the network wishes to transmit (protocol) data (e.g. configuration 
parameters, error codes or messages/events) to the peer entity. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



322 



ETSI TS 124 008 V7.14.0 (2009-03) 



If this IE is received for an MBMS context, it shall be ignored by the receiver. 

9.5.14.3 MBMS protocol configuration options 

This IE is included in the message when the MS or the network wishes to transmit MBMS bearer related (protocol) data 
(e.g. configuration parameters, error codes or messages/events) to the peer entity for an MBMS context. 

If the IE is received for a PDP context, it shall be ignored by the receiver. 

9.5.15 Deactivate PDP context accept 

This message is sent to acknowledge deactivation of the PDP context requested in the corresponding Deactivate PDP 
context request message. See table 9.5.15/3GPP TS 24.008. 

Message type: DEACTIVATE PDP CONTEXT ACCEPT 

Significance: global 

Direction: both 

Table 9.5.1 5/3GPP TS 24.008: DEACTIVATE PDP CONTEXT ACCEPT message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Deactivate PDP context accept 
message identity 


IVIessage type 
10.4 


M 


V 


1 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 


35 


IVIBMS protocol configuration 
options 


IVIBMS protocol configuration options 
10.5.6.15 





TLV 


3-253 



9.5.15.1 Protocol configuration options 

This IE is included in the message when the MS or the network wishes to transmit (protocol) data (e.g. configuration 
parameters, error codes or messages/events) to the peer entity. 

If this IE is received for an MBMS context, it shall be ignored by the receiver. 

9.5.15.2 MBMS protocol configuration options 

This IE is included in the message when the MS or the network wishes to transmit MBMS bearer related (protocol) data 
(e.g. configuration parameters, error codes or messages/events) to the peer entity for an MBMS context. 

If the IE is received for a PDP context, it shall be ignored by the receiver. 

9.5.15a Request Secondary PDP Context Activation 

This message is sent by the network to the MS to request activation of a secondary PDP context. 
See table 9.5.15a/3GPP TS 24.008. 

Message type: REQUEST SECONDARY PDP CONTEXT ACTIVATION 

Significance: global 

Direction: network to MS 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



323 



ETSI TS 124 008 V7.14.0 (2009-03) 



Table 9.5.1 5a/3GPP TS 24.008: REQUEST SECONDARY PDP CONTEXT ACTIVATION message 

content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Request secondary PDP context 
activation message identity 


IVIessage type 
10.4 


M 


V 


1 




Required QoS 


Quality of service 
10.5.6.5 


M 


LV 


13-17 




Linl<ed Tl 


Linked Tl 
10.5.6.7 


M 


LV 


2-3 


36 


TFT 


Traffic Flow Template 
10.5.6.12 





TLV 


3-257 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.15.1a TFT 

This IE shall be included if a linked PDP context without TFT has already been activated. This IE provides the MS with 
uplink and downlink packet filters. 

9.5.15.2a Protocol configuration options 

This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, 
error codes or messages/events) to the MS. 

9.5.15b Request Secondary PDP Context Activation Reject 

This message is sent by the MS to the network to reject the request of a secondary PDP context activation. 
See table 9.5.15b/3GPP TS 24.008. 

Message type: REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT 

Significance: global 

Direction: MS to network 

Table 9.5.1 5b/3GPP TS 24.008: REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT 

message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Request secondary PDP context 
activation reject message identity 


IVIessage type 
10.4 


M 


V 


1 




SIVI cause 


SM cause 
10.5.6.6 


M 


V 


1 


27 


Protocol configuration options 


Protocol configuration options 
10.5.6.3 





TLV 


3-253 



9.5.1 5.1 b Protocol configuration options 

This IE is included in the message when the MS wishes to transmit (protocol) data (e.g. configuration parameters, error 
codes or messages/events) to the network. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



324 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.5.16 Void 

9.5.17 Void 

9.5.18 Void 

9.5.19 Void 

9.5.20 Void 

9.5.21 SM Status 

This message is sent by the network or the MS to pass information on the status of the indicated context and report 
certain error conditions (eg. as listed in clause 8). See table 9.5.21/3GPP TS 24.008. 

Message type: SM Status 

Significance: local 

Direction: both 

Table 9.5.21/3GPP TS 24.008: SM STATUS message content 



IE! 


information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




SIVI Status message identity 


IVIessage type 
10.4 


M 


V 


1 




SIVI Cause 


SM Cause 
10.5.6.6 


M 


V 


1 



9.5.22 Activate MBMS Context Request 



This message is sent by the MS to the network as an explicit response to a Request MBMS Context Activation message 
See table 9.5.22/3GPP TS 24.008. 

Message type: ACTIVATE MBMS CONTEXT REQUEST 

Significance: global 

Direction: MS to network 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



325 



ETSI TS 124 008 V7.14.0 (2009-03) 



TABLE 9.5.22 : ACTIVATE MBMS CONTEXT REQUEST message content 



lEI 


Information Element 


Type/ 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction Identifier 
10.3.2 


M 


V 


1/2-3/2 




Activate IVIBIVIS context request 
message identity 


IVIessage type 
10.4 


M 


V 


1 




Requested IVIBIVIS NSAPI 


Enhanced Network service access 
point identifier 10.5.6.16 


M 


V 


1 




Requested LLC SARI 


LLC service access point identifier 
10.5.6.9 


M 


V 


1 




Supported IVIBMS bearer 
capabilities 


IVIBMS bearer capabilities 
10.5.6.14 


M 


LV 


2-3 




Requested multicast address 


Packet data protocol address 
10.5.6.4 


M 


LV 


3- 19 




Access point name 


Access point name 
10.5.6.1 


M 


LV 


2-101 


35 


IVIBMS protocol configuration 
options 


MBMS protocol configuration options 
10.5.6.15 





TLV 


3-253 



NOTE: The MBMS NSAPI will be used in lu mode when the network chooses a point-to-point MBMS bearer for 
the transfer of MBMS data in the user plane. 

9.5.22.1 MBMS protocol configuration options 

This IE is included in the message when the MS wishes to transmit MBMS bearer related (protocol) data (e.g. 
configuration parameters, error codes or messages/events) to the peer entity for an MBMS context. 

9.5.23 Activate MBMS Context Accept 

This message is sent by the network to the MS to acknowledge activation of an MBMS context. 
See table 9.5.23/3GPP TS 24.008. 

Message type: ACTIVATE MBMS CONTEXT ACCEPT 

Significance: global 

Direction: network to MS 

TABLE 9.5.23 : ACTIVATE MBMS CONTEXT ACCEPT message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Activate MBMS context accept 
message identity 


Message type 
10.4 


M 


V 


1 




Temporary Mobile Group Identity 


Temporary Mobile Group Identity 
10.5.6.13 


M 


LV 


4-7 




Negotiated LLC SAPI 


LLC service access point identifier 
10.5.6.9 


M 


V 


1 


35 


MBMS protocol configuration 
options 


MBMS protocol configuration options 
10.5.6.15 





TLV 


3-253 



9.5.23.1 MBMS protocol configuration options 

This IE is included in the message when the network wishes to transmit MBMS bearer related (protocol) data (e.g. 
configuration parameters, error codes or messages/events) to the peer entity for an MBMS context. 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



326 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.5.24 Activate MBMS Context Reject 

This message is sent by the network to the MS to reject activation of a MBMS context. 
See table 9.5.24/3GPP TS 24.008. 

Message type: ACTIVATE MBMS CONTEXT REJECT 

Significance: global 

Direction: network to MS 

TABLE 9.5.24 : ACTIVATE MBMS CONTEXT REJECT message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction Identifier 
10.3.2 


M 


V 


1/2-3/2 




Activate MBMS context reject 
message identity 


Message type 
10.4 


M 


V 


1 




SM cause 


SM Cause 
10.5.6.6 


M 


V 


1 


35 


MBMS protocol configuration 
options 


MBMS protocol configuration options 
10.5.6.15 





TLV 


3-253 



9.5.24.1 MBMS protocol configuration options 

This IE is included in the message when the network wishes to transmit MBMS bearer related (protocol) data (e.j 
configuration parameters, error codes or messages/events) to the peer entity for an MBMS context. 

9.5.25 Request MBMS Context Activation 

This message is sent by the network to the MS to initiate activation of an MBMS context. 
See table 9.5.25/3GPP TS 24.008. 

Message type: REQUEST MBMS CONTEXT ACTIVATION 

Significance: global 

Direction: network to MS 

TABLE 9.5.25 : REQUEST MBMS CONTEXT ACTIVATION message content 



lEI 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction Identifier 


Transaction Identifier 
10.3.2 


M 


V 


1/2-3/2 




Request MBMS context activation 
message identity 


Message type 
10.4 


M 


V 


1 




Linked NSAPI 


Network service access point Identifier 
10.5.6.2 


M 


V 


1 




Offered Multicast address 


Packet data protocol address 
10.5.6.4 


M 


LV 


3- 19 




Access point name 


Access point name 
10.5.6.1 


M 


LV 


2-101 


35 


MBMS protocol configuration 
options 


MBMS protocol configuration options 
10.5.6.15 





TLV 


3-253 



£75/ 



3GPP TS 24.008 version 7.14.0 Release 7 



327 



ETSI TS 124 008 V7.14.0 (2009-03) 



9.5.25.1 



Linked NSAPI 



This IE is included in the message to allow the UE to associate the MBMS context with the PDP context over which the 
IGMP/MLD join message was sent. 

9.5.25.2 MBMS protocol configuration options 

This IE is included in the message when the network wishes to transmit MBMS bearer related (protocol) data (e.g. 
configuration parameters, error codes or messages/events) to the peer entity for an MBMS context. 

9.5.26 Request MBMS Context Activation Reject 

This message is sent by the MS to the network to reject initiation of an MBMS context activation. 
See table 9.5.26/3GPP TS 24.008. 

Message type: REQUEST MBMS CONTEXT ACTIVATION REJECT 

Significance: global 

Direction: MS to network 

TABLE 9.5.26 : REQUEST MBMS CONTEXT ACTIVATION REJECT message content 



IE! 


Information Element 


Type/Reference 


Presence 


Format 


Length 




Protocol discriminator 


Protocol discriminator 
10.2 


M 


V 


1/2 




Transaction identifier 


Transaction identifier 
10.3.2 


M 


V 


1/2-3/2 




Request IVIBIVIS context act. reject 
message identity 


IVIessage type 
10.4 


M 


V 


1 




Sl\/1 cause 


SM Cause 
10.5.6.6 


M 


V 


1 


35 


IVIBIVIS protocol configuration 
options 


IVIBMS protocol configuration options 
10.5.6.15 





TLV 


3-253 



9.5.26.1 MBMS protocol configuration options 

This IE is included in the message when the MS wishes to transmit MBMS bearer related (protocol) data (e.g. 
configuration parameters, error codes or messages/events) to the peer entity for an MBMS context. 



10 General message format and information elements 
coding 

The figures and text in this clause describe the Information Elements contents. 

10.1 Overview 

Within the Layer 3 protocols defined in 3GPP TS 24.008, every message is a standard L3 message as defined in 3GPP 
TS 24.007 [20]. This means that the message consists of the following parts: 

a) protocol discriminator; 

b) transaction identifier; 

c) message type; 

d) other information elements, as required. 



£75/ 



3GPP TS 24.008 version 7.1 4.0 Release 7 328 ETSI TS 1 24 008 V7.1 4.0 (2009-03) 

This organization is illustrated in the example shown in figure 10.1/3GPP TS 24.008. 



87654321 

+ + 

Transaction identifier Protocol discriminator 
or Skip Indicator 

+ 

I Message type 

+ 

I Other information elements as required 

+ __________________ 



octet 1 

octet 2 
etc . . . 



Figure 10.1/3GPP TS 24.008 General message organization example 

Unless specified otherwise in the message descriptions of clause 9, a particular information element shall not be present 
more than once in a given message. 

The term "default" implies that the value defined shall be used in the absence of any assignment, or that this value 
allows negotiation of alternative values in between the two peer entities. 

When a field extends over more than one octet, the order of bit values progressively decreases as the octet number 
increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet 
of the field. 

10.2 Protocol Discriminator 

The Protocol Discriminator (PD) and its use are defined in 3GPP TS 24.007 [20]. 

1 0.3 Skip indicator and transaction identifier 

10.3.1 Skip indicator 

Bits 5 to 8 of the first octet of every Mobility Management message and GPRS MobilityManagement message contains 
the skip indicator. A message received with skip indicator different from 0000 shall be ignored. A message received 
with skip indicator encoded as 0000 shall not be ignored (unless it is ignored for other reasons). A protocol entity 
sending a Mobility Management message or a GPRS Mobility Management message shall encode the skip indicator 
as 0000. 

10.3.2 Transaction identifier 

Bits 5 to 8 of the first octet of every message belonging to the protocols "Call Control; call related SS messages" and 
"Session Management"contain the transaction identifier (TI). The transaction identifier and its use are defined in 3GPP 
TS 24.007 [20]. 

For the session management protocol, the extended TI mechanism may be used (see 3GPP TS 24.007 [20]). 

For the call control protocol, the extended TI mechanism shall be supported for the purpose of protocol error handling 
as specified in subclause 8.3.1 



10.4 IVI ess age Type 



The message type IE and its use are defined in 3GPP TS 24.007 [20]. Tables 10.3/3GPP TS 24.008, 

10.4/3GPP TS