ETSI EN 300 940: Draft V7.7.0

draft ETSI EN 300 940 V7.7.
0 (2000-04)
European Standard (Telecommunications series)
Digital cellular telecommunications system (Phase 2+);
Mobile radio interface layer 3 specification
(GSM 04.08 version 7.7.0 Release 1998)
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
R
Reference
REN/SMG-030408Q7R3 (8pc03ic0.PDF)
Keywords
Digital cellular telecommunications system,
Global System for Mobile communications (GSM)
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N348 623 562 00017 - NAF 742 C
Association but non lucratif enregistre la
Sous-Prfecture de Grasse (06) N7803/88
Internet
[email protected]
Individual copies of this ETSI deliverable
can be downloaded from
http://www.etsi.org
If you find errors in the present document, send your
comment to: [email protected]
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 2000.
All rights reserved.
ETSI
3 draft ETSI EN 300 940 V7.7.0 (2000-04)
Contents
Intellectual Property Rights ............................................................................................................................. 28
Foreword.......................................................................................................................................................... 28
Introduction...................................................................................................................................................... 29
0 Scope ..................................................................................................................................................... 30
0.1 Scope of the Technical Specification ............................................................................................................... 30
0.2 Application to the interface structures.............................................................................................................. 30
0.3 Structure of layer 3 procedures ........................................................................................................................ 30
0.4 Test procedures ................................................................................................................................................ 30
0.5 Use of logical channels..................................................................................................................................... 31
0.6 Overview of control procedures ....................................................................................................................... 31
0.6.1 List of procedures ....................................................................................................................................... 31
0.7 Applicability of implementations ..................................................................................................................... 33
0.7.1 Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS) .................................................. 34
0.7.2 General Packet Radio Service (GPRS) ....................................................................................................... 34
1 References ............................................................................................................................................. 34
2 Definitions and abbreviations................................................................................................................ 38
2.1 Random values ................................................................................................................................................. 38
2.2 Vocabulary....................................................................................................................................................... 39
3 Radio Resource management procedures.............................................................................................. 40
3.1 Overview/General ............................................................................................................................................ 40
3.1.1 General ....................................................................................................................................................... 40
3.1.2 Services provided to upper layers............................................................................................................... 40
3.1.2.1 Idle mode .............................................................................................................................................. 40
3.1.2.2 Dedicated mode .................................................................................................................................... 41
3.1.2.3 Group receive mode.............................................................................................................................. 41
3.1.2.4 Group transmit mode............................................................................................................................. 41
3.1.2.5 Packet idle mode................................................................................................................................... 42
3.1.2.6 Packet transfer mode............................................................................................................................. 42
3.1.3 Services required from data link and physical layers.................................................................................. 42
3.1.4 Change of dedicated channels..................................................................................................................... 42
3.1.4.1 Change of dedicated channels using SAPI = 0...................................................................................... 42
3.1.4.2 Change of dedicated channels using other SAPIs than 0....................................................................... 42
3.1.4.3 Sequenced message transfer operation.................................................................................................. 43
3.1.4.3.1 Variables and sequence numbers..................................................................................................... 43
3.1.4.3.1.2 Send sequence number N(SD) ................................................................................................... 43
3.1.4.3.2 Procedures for the initiation, transfer execution and termination of the sequenced message
transfer operation............................................................................................................................. 43
3.1.4.3.2.2 Transfer Execution..................................................................................................................... 43
3.1.5 Procedure for Service Request and Contention Resolution ........................................................................ 43
3.1.6 Preemption.................................................................................................................................................. 45
3.2 Idle mode procedures and general procedures in packet idle and packet transfer modes................................. 46
3.2.1 Mobile Station side..................................................................................................................................... 46
3.2.2 Network side............................................................................................................................................... 47
3.2.2.1 System information broadcasting.......................................................................................................... 47
3.2.2.2 Paging ................................................................................................................................................... 48
3.3 RR connection establishment ........................................................................................................................... 48
3.3.1 RR connection establishment initiated by the mobile station...................................................................... 48
3.3.1.1 Entering the dedicated mode : immediate assignment procedure.......................................................... 48
3.3.1.1.1 Permission to access the network .................................................................................................... 48
3.3.1.1.2 Initiation of the immediate assignment procedure........................................................................... 49
3.3.1.1.3 Answer from the network ................................................................................................................ 49
3.3.1.1.3.1 On receipt of a CHANNEL REQUEST message ...................................................................... 49
ETSI
4 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.3.1.1.3.2 Assignment rejection ................................................................................................ ................. 50
3.3.1.1.4 Assignment completion ................................................................................................. .................. 51
3.3.1.1.4.1 Early classmark sending............................................................................................. ................ 51
3.3.1.1.4.2 GPRS suspension procedure........................................................................................... ........... 52
3.3.1.1.5 Abnormal cases ........................................................................................................ ....................... 52
3.3.1.2 Entering the group transmit mode: uplink access procedure............................................................... .. 52
3.3.1.2.1 Mobile station side .......................................................................................................................... 53
3.3.1.2.1.1 Uplink investigation procedure.................................................................................................. 53
3.3.1.2.1.2 Uplink access procedure ............................................................................................................ 53
3.3.1.2.2 Network side.................................................................................................................................... 53
3.3.1.2.3 Abnormal cases ............................................................................................................................... 54
3.3.1.3 Dedicated mode and GPRS................................................................................................................... 54
3.3.2 Paging procedure for RR connection establishment ................................................................................... 54
3.3.2.1 Paging initiation by the network............................................................................................................ 54
3.3.2.1.1 Paging initiation using paging subchannel on CCCH...................................................................... 54
3.3.2.1.2 Paging initiation using paging subchannel on PCCCH.................................................................... 56
3.3.2.1.3 Paging initiation using PACCH....................................................................................................... 56
3.3.2.2 Paging response .................................................................................................................................... 56
3.3.2.3 Abnormal cases ..................................................................................................................................... 56
3.3.3 Notification procedure................................................................................................................................ 57
3.3.3.1 Notification of a call ............................................................................................................................. 57
3.3.3.2 Joining a VGCS or VBS call................................................................................................................. 57
3.3.3.3 Reduced NCH monitoring mechanism.................................................................................................. 57
3.3.3.4 Notification response procedure ........................................................................................................... 58
3.4 Procedures in dedicated mode and in group transmit mode ............................................................................. 59
3.4.1 SACCH procedures .................................................................................................................................... 59
3.4.1.1 General.................................................................................................................................................. 59
3.4.1.2 Measurement report .............................................................................................................................. 60
3.4.1.3 Extended measurement report $(MAFA)$............................................................................................ 60
3.4.2 Transfer of messages and link layer service provision................................................................................ 60
3.4.3 Channel assignment procedure ................................................................................................................... 60
3.4.3.1 Channel assignment initiation ............................................................................................................... 61
3.4.3.2 Assignment completion......................................................................................................................... 62
3.4.3.3 Abnormal cases ..................................................................................................................................... 62
3.4.4 Handover procedure ................................................................................................................................... 63
3.4.4.1 Handover initiation ............................................................................................................................... 64
3.4.4.2 Physical channel establishment ............................................................................................................. 65
3.4.4.2.1 Finely synchronized cell case .......................................................................................................... 65
3.4.4.2.2 Non synchronized cell case ............................................................................................................. 66
3.4.4.2.3 Pseudo-synchronized cell case ........................................................................................................ 66
3.4.4.2.4 Pre-synchronized cell case............................................................................................................... 66
3.4.4.3 Handover completion............................................................................................................................ 67
3.4.4.4 Abnormal cases ..................................................................................................................................... 67
3.4.5 Frequency redefinition procedure............................................................................................................... 68
3.4.5.1 Abnormal cases ..................................................................................................................................... 68
3.4.6 Channel mode modify procedure................................................................................................................ 69
3.4.6.1 Normal channel mode modify procedure .............................................................................................. 69
3.4.6.1.1 Initiation of the channel mode modify procedure............................................................................ 69
3.4.6.1.2 Completion of channel mode modify procedure.............................................................................. 69
3.4.6.1.3 Abnormal cases ............................................................................................................................... 69
3.4.6.2 Channel mode modify procedure for a voice group call talker ............................................................. 70
3.4.6.2.1 Initiation of the channel mode modify procedure............................................................................ 70
3.4.6.2.2 Completion of mode change procedure........................................................................................... 70
3.4.6.2.3 Abnormal cases ............................................................................................................................... 70
3.4.7 Ciphering mode setting procedure.............................................................................................................. 70
3.4.7.1 Ciphering mode setting initiation.......................................................................................................... 70
3.4.7.2 Ciphering mode setting completion....................................................................................................... 71
3.4.8 Additional channel assignment procedure .................................................................................................. 71
3.4.8.1 Additional assignment procedure initiation........................................................................................... 71
3.4.8.2 Additional assignment procedure completion....................................................................................... 72
ETSI
5 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.4.8.3 Abnormal cases.......................................................................................................... ........................... 72
3.4.9 Partial channel release procedure ......................................................................................... ...................... 72
3.4.9.1 Partial release procedure initiation.................................................................................... .................... 72
3.4.9.2 Abnormal cases.......................................................................................................... ........................... 72
3.4.10 Classmark change procedure ............................................................................................... ....................... 72
3.4.11 Classmark interrogation procedure........................................................................................ ..................... 73
3.4.11.1 Classmark interrogation initiation..................................................................................... .................... 73
3.4.11.2 Classmark interrogation completion..................................................................................... ................. 73
3.4.12 Indication of notifications and paging information....................................................................... .............. 73
3.4.13 RR connection release procedure .......................................................................................... ..................... 73
3.4.13.1 Normal release procedure ............................................................................................... ...................... 73
3.4.13.1.1 Channel release procedure initiation in dedicated mode and in group transmit mode..................... 73
3.4.13.1.2 Abnormal cases ....................................................................................................... ........................ 74
3.4.13.2 Radio link failure in dedicated mode ................................................................................... ................. 75
3.4.13.2.1 Mobile side.......................................................................................................... ............................ 75
3.4.13.2.2 Network side......................................................................................................... ........................... 75
3.4.13.3 RR connection abortion in dedicated mode ............................................................................... ........... 76
3.4.13.4 Uplink release procedure in group transmit mode........................................................................ ......... 76
3.4.13.5 Radio link failure in group transmit mode............................................................................................. 76
3.4.13.5.1 Mobile side...................................................................................................................................... 76
3.4.13.5.2 Network side.................................................................................................................................... 76
3.4.14 Receiving a RR STATUS message by a RR entity..................................................................................... 76
3.4.15 Group receive mode procedures ................................................................................................................. 77
3.4.15.1 Mobile station side................................................................................................................................ 77
3.4.15.1.1 Reception of the VGCS or VBS channel......................................................................................... 77
3.4.15.1.2 Monitoring of downlink messages and related procedures.............................................................. 77
3.4.15.1.2.1 Spare.......................................................................................................................................... 77
3.4.15.1.2.2 Spare.......................................................................................................................................... 77
3.4.15.1.2.3 Channel mode modify procedure............................................................................................... 77
3.4.15.1.2.4 Notification and paging information.......................................................................................... 77
3.4.15.1.2.4.1 Use of Reduced NCH monitoring ........................................................................................ 78
3.4.15.1.2.5 Uplink status messages .............................................................................................................. 78
3.4.15.1.2.6 Channel release message............................................................................................................ 78
3.4.15.1.2.7 Information on paging channel restructuring ............................................................................. 78
3.4.15.1.3 Uplink reply procedure.................................................................................................................... 78
3.4.15.1.4 Leaving the group receive mode...................................................................................................... 79
3.4.15.2 Network side ......................................................................................................................................... 79
3.4.15.2.1 Provision of messages on the VGCS or VBS channel downlink..................................................... 79
3.4.15.2.2 Release of the VGCS or VBS Channels .......................................................................................... 80
3.4.15.3 Failure cases.......................................................................................................................................... 80
3.4.16 Configuration change procedure................................................................................................................. 80
3.4.16.1 Configuration change initiation............................................................................................................. 80
3.4.16.2 Configuration change completion ......................................................................................................... 81
3.4.16.3 Abnormal cases ..................................................................................................................................... 81
3.4.17 Mapping of user data substreams onto timeslots in a multislot configuration ............................................ 81
3.4.18 Handling of classmark information at band change.................................................................................... 81
3.4.19 Assignment to a Packet Data channel ......................................................................................................... 82
3.4.19.1 Assignment to PDCH initiation............................................................................................................. 82
3.4.19.2 Completion of the Assignment to PDCH procedure ............................................................................. 83
3.4.19.3 Abnormal cases ..................................................................................................................................... 83
3.4.20 RR-Network Commanded Cell Change Order............................................................................................ 84
3.4.20.1 RR-network commanded cell change order initiation ........................................................................... 84
3.4.20.2 Network controlled cell reselection completion.................................................................................... 85
3.4.20.3 Abnormal cases ..................................................................................................................................... 85
3.4.21 Application Procedures .......................................................................................................................................... 85
3.4.21.1 General.................................................................................................................................................. 85
3.4.21.2 Application Information Transfer ......................................................................................................... 85
3.4.21.2.1 Normal Procedure without Segmentation........................................................................................ 86
3.4.21.2.2 Normal Procedure with Segmentation............................................................................................. 86
3.4.21.2.3 Abnormal Cases............................................................................................................................... 86
ETSI
6 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.5 RR procedures on CCCH related to temporary block flow establishment........................................................ 87
3.5.1 Packet paging procedure using CCCH........................................................................................................ 87
3.5.1.1 Packet paging initiation by the network ................................................................................................ 87
3.5.1.2 On receipt of a packet paging request ................................................................................................... 88
3.5.2 Packet access procedure using CCCH........................................................................................................ 88
3.5.2.1 Entering the packet transfer mode: packet access procedure ................................................................ 88
3.5.2.1.1 Permission to access the network .................................................................................................... 88
3.5.2.1.2 Initiation of the packet access procedure: channel request .............................................................. 88
3.5.2.1.3 Packet immediate assignment .......................................................................................................... 89
3.5.2.1.4 Packet access completion ................................................................................................................ 92
3.5.2.1.5 Abnormal cases ............................................................................................................................... 92
3.5.2.2 Sending an RLC/MAC control message: single block packet access procedure................................... 92
3.5.3 Packet downlink assignment procedure using CCCH................................................................................. 92
3.5.3.1 Entering the packet transfer mode: packet downlink assignment procedure......................................... 92
3.5.3.1.2 Initiation of the packet downlink assignment procedure ................................................................. 93
3.5.3.1.3 Packet downlink assignment completion......................................................................................... 94
3.5.3.1.4 Abnormal cases ............................................................................................................................... 94
3.5.3.2 Sending an RLC/MAC control message: single block packet downlink assignment procedure............ 95
4 Elementary procedures for Mobility Management................................................................................ 95
4.1 General ............................................................................................................................................................. 95
4.1.1 MM and GMM procedures......................................................................................................................... 96
4.1.1.1 Types of MM and GMM procedures .................................................................................................... 96
4.1.1.2 MM-GMM co-ordination for GPRS MSs............................................................................................ 97
4.1.1.2.1 GPRS MS operating in mode A or B in a network that operates in mode I..................................... 97
4.1.1.2.2 GPRS MS operating in mode A or B in a network that operates in mode II or III.......................... 97
4.1.2 MM sublayer states..................................................................................................................................... 98
4.1.2.1 MM sublayer states in the mobile station.............................................................................................. 98
4.1.2.1.1 Main states....................................................................................................................................... 98
4.1.2.1.2 Substates of the MM IDLE state ................................................................................................... 101
4.1.2.2 The update Status................................................................................................................................ 102
4.1.2.3 MM sublayer states on the network side ............................................................................................. 103
4.1.3 GPRS mobility management (GMM) sublayer states ............................................................................... 104
4.1.3.1 GMM states in the MS........................................................................................................................ 104
4.1.3.1.1 Main states..................................................................................................................................... 104
4.1.3.1.1.1 GMM-NULL ........................................................................................................................... 104
4.1.3.1.1.2 GMM-DEREGISTERED........................................................................................................ 104
4.1.3.1.1.3 GMM-REGISTERED-INITIATED ........................................................................................ 104
4.1.3.1.1.4 GMM-REGISTERED.............................................................................................................. 105
4.1.3.1.1.5 GMM-DEREGISTERED-INITIATED................................................................................... 105
4.1.3.1.2.5 GMM-DEREGISTERED.NO-IMSI ........................................................................................ 105
4.1.3.1.2.6 GMM-DEREGISTERED.NO-CELL-AVAILABLE............................................................... 105
4.1.3.1.2.7 GMM-DEREGISTERED.PLMN-SEARCH............................................................................ 105
4.1.3.1.2.8 GMM-DEREGISTERED.SUSPENDED ................................................................................ 106
4.1.3.1.3 Substates of state GMM-REGISTERED....................................................................................... 106
4.1.3.1.3.1 GMM-REGISTERED.NORMAL-SERVICE.......................................................................... 106
4.1.3.1.3.2 GMM-REGISTERED.SUSPENDED...................................................................................... 106
4.1.3.1.3.3 GMM-REGISTERED.UPDATE-NEEDED............................................................................ 106
4.1.3.1.3.4 GMM-REGISTERED.ATTEMPTING-TO-UPDATE............................................................ 106
4.1.3.1.3.5 GMM-REGISTERED.NO-CELL-AVAILABLE.................................................................... 106
4.1.3.1.3.7 GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM................................................... 107
4.1.3.1.3.8 GMM-REGISTERED.IMSI-DETACH-INITIATED.............................................................. 107
4.1.3.2 GPRS update status............................................................................................................................. 107
4.1.3.3 GMM mobility management states on the network side ..................................................................... 108
4.1.3.3.1 Main States.................................................................................................................................... 108
4.1.3.3.1.1 GMM-DEREGISTERED........................................................................................................ 108
4.1.3.3.1.2 GMM-COMMON-PROCEDURE-INITIATED...................................................................... 108
4.1.3.3.1.3 GMM-REGISTERED.............................................................................................................. 108
4.1.3.3.1.4 GMM-DEREGISTERED-INITIATED................................................................................... 108
4.1.3.3.2 Substates of state GMM-REGISTERED....................................................................................... 109
4.1.3.3.2.1 GMM-REGISTERED.NORMAL-SERVICE.......................................................................... 109
ETSI
7 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.1.3.3.2.2 GMM-REGISTERED.SUSPENDED...................................................................................... 109
4.2 Behaviour of the MS in MM Idle state, GMM-DEREGISTERED state and GMM-REGISTERED state .... 109
4.2.1 Primary Service State selection ........................................................................................... ..................... 110
4.2.1.1 Selection of the Service State after Power On........................................................................... .......... 110
4.2.1.2 Other Cases ......................................................................................................................................... 110
4.2.2 Detailed Description of the MS behaviour in MM IDLE State ................................................................ 111
4.2.2.1 Service State, NORMAL SERVICE................................................................................................... 111
4.2.2.2 Service State, ATTEMPTING TO UPDATE.....................................................................................111
4.2.2.3 Service State, LIMITED SERVICE.................................................................................................... 112
4.2.2.4 Service State, NO IMSI ...................................................................................................................... 112
4.2.2.5 Service State, SEARCH FOR PLMN, NORMAL SERVICE............................................................. 113
4.2.2.6 Service State, SEARCH FOR PLMN................................................................................................. 113
4.2.2.7 Service State, RECEIVING GROUP CALL (NORMAL SERVICE) ................................................ 113
4.2.2.8 Service State, RECEIVING GROUP CALL (LIMITED SERVICE) ................................................. 114
4.2.3 Service state when back to state MM IDLE from another state................................................................ 114
4.2.4 Behaviour in state GMM-DEREGISTERED ........................................................................................... 115
4.2.4.1 Primary substate selection................................................................................................................... 115
4.2.4.1.1 Selection of the substate after power on or enabling the MSs GPRS capability .......................... 115
4.2.4.1.2 Other Cases ........................................................................................................... ........................ 116
4.2.4.2 Detailed description of the MS behaviour in state GMM-DEREGISTERED..................................... 116
4.2.4.2.1 Substate, NORMAL-SERVICE .............................................................................................. ...... 116
4.2.4.2.2 Substate, ATTEMPTING-TO-ATTACH...................................................................................... 116
4.2.4.2.3 Substate, LIMITED-SERVICE..................................................................................................... 116
4.2.4.2.4 Substate, NO-IMSI ........................................................................................................................ 116
4.2.4.2.5 Substate, NO-CELL ...................................................................................................................... 117
4.2.4.2.6 Substate, PLMN-SEARCH ........................................................................................................... 117
4.2.4.2.7 Substate, ATTACH-NEEDED...................................................................................................... 117
4.2.4.2.8 Substate, SUSPENDED ................................................................................................................ 117
4.2.4.3 Substate when back to state GMM-DEREGISTERED from another GMM state .............................. 117
4.2.5 Behaviour in state GMM-REGISTERED................................................................................................. 117
4.2.5.1 Detailed description of the MS behaviour in state GMM-REGISTERED.......................................... 118
4.2.5.1.1 Substate, NORMAL-SERVICE .................................................................................................... 118
4.2.5.1.2 Substate, SUSPENDED ................................................................................................................ 118
4.2.5.1.3 Substate, UPDATE-NEEDED ...................................................................................................... 118
4.2.5.1.4 Substate, ATTEMPTING-TO-UPDATE ...................................................................................... 118
4.2.5.1.5 Substate, NO-CELL-AVAILABLE............................................................................................... 119
4.2.5.1.6 Substate, LIMITED-SERVICE..................................................................................................... 119
4.2.5.1.7 Substate, ATTEMPTING-TO-UPDATE-MM.............................................................................. 119
4.3 MM common procedures ............................................................................................................................... 119
4.3.1 TMSI reallocation procedure.................................................................................................................... 119
4.3.1.1 TMSI reallocation initiation by the network ....................................................................................... 120
4.3.1.2 TMSI reallocation completion by the mobile station.......................................................................... 120
4.3.1.3 TMSI reallocation completion in the network..................................................................................... 120
4.3.1.4 Abnormal cases ................................................................................................................................... 120
4.3.2 Authentication procedure.......................................................................................................................... 121
4.3.2.1 Authentication request by the network................................................................................................ 121
4.3.2.2 Authentication response by the mobile station.................................................................................... 121
4.3.2.3 Authentication processing in the network ........................................................................................... 121
4.3.2.4 Ciphering key sequence number ......................................................................................................... 121
4.3.2.5 Unsuccessful authentication................................................................................................................ 122
4.3.2.6 Abnormal cases ................................................................................................................................... 122
4.3.3 Identification procedure............................................................................................................................ 123
4.3.3.1 Identity request by the network........................................................................................................... 123
4.3.3.2 Identification response by the mobile station...................................................................................... 123
4.3.3.3 Abnormal cases ................................................................................................................................... 123
4.3.4 IMSI detach procedure ............................................................................................................................. 123
4.3.4.1 IMSI detach initiation by the mobile station ....................................................................................... 123
4.3.4.2 IMSI detach procedure in the network................................................................................................ 124
4.3.4.3 IMSI detach completion by the mobile station.................................................................................... 124
4.3.4.4 Abnormal cases ................................................................................................................................... 124
ETSI
8 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.3.5 Abort procedure........................................................................................................... ............................. 124
4.3.5.1 Abort procedure initiation by the network ............................................................................... ........... 124
4.3.5.2 Abort procedure in the mobile station................................................................................................. 124
4.3.6 MM information procedure ...................................................................................................................... 125
4.3.6.1 MM information procedure initiation by the network......................................................................... 125
4.3.6.2 MM information procedure in the mobile station ............................................................................... 125
4.4 MM specific procedures................................................................................................................................. 125
4.4.1 Location updating procedure .................................................................................................................... 125
4.4.2 Periodic updating...................................................................................................................................... 126
4.4.3 IMSI attach procedure .............................................................................................................................. 127
4.4.4 Generic Location Updating procedure...................................................................................................... 127
4.4.4.1 Location updating initiation by the mobile station.............................................................................. 127
4.4.4.1a Network Request for Additional mobile station Capability Information............................................. 127
4.4.4.2 Identification request from the network .............................................................................................. 127
4.4.4.3 Authentication by the network ............................................................................................................ 128
4.4.4.4 Ciphering mode setting by the network............................................................................................... 128
4.4.4.5 Attempt Counter.................................................................................................................................. 128
4.4.4.6 Location updating accepted by the network........................................................................................ 128
4.4.4.7 Location updating not accepted by the network.................................................................................. 129
4.4.4.8 Release of RR connection after location updating .............................................................................. 129
4.4.4.9 Abnormal cases on the mobile station side ......................................................................................... 130
4.4.4.10 Abnormal cases on the network side................................................................................................... 131
4.5 Connection management sublayer service provision...................................................................................... 131
4.5.1 MM connection establishment .................................................................................................................. 132
4.5.1.1 MM connection establishment initiated by the mobile station ............................................................ 132
4.5.1.2 Abnormal cases ................................................................................................................................... 134
4.5.1.3 MM connection establishment initiated by the network...................................................................... 135
4.5.1.3.1 Mobile Terminating CM Activity.................................................................................................. 135
4.5.1.3.2 Mobile Originating CM Activity $(CCBS)$ ................................................................................. 135
4.5.1.4 Abnormal cases ................................................................................................................................... 136
4.5.1.5 MM connection establishment for emergency calls ............................................................................ 136
4.5.1.6 Call re-establishment........................................................................................................................... 137
4.5.1.6.1 Call re-establishment, initiation by the mobile station................................................................... 137
4.5.1.6.2 Abnormal cases ............................................................................................................................. 139
4.5.1.7 Forced release during MO MM connection establishment.................................................................. 139
4.5.2 MM connection information transfer phase.............................................................................................. 140
4.5.2.1 Sending CM messages ........................................................................................................................ 140
4.5.2.2 Receiving CM messages ..................................................................................................................... 140
4.5.2.3 Abnormal cases ................................................................................................................................... 140
4.5.3 MM connection release............................................................................................................................. 140
4.5.3.1 Release of associated RR connection.................................................................................................. 141
4.5.3.2 Uplink release in a voice group call .................................................................................................... 141
4.6 Receiving a MM STATUS message by a MM entity..................................................................................... 141
4.7 Elementary mobility management procedures for GPRS services .................................................................141
4.7.1 General ..................................................................................................................................................... 141
4.7.1.1 Lower layer failure.............................................................................................................................. 141
4.7.1.2 Ciphering of messages ........................................................................................................................ 141
4.7.1.3 P-TMSI signature................................................................................................................................ 142
4.7.1.4 Radio resource sublayer address handling .......................................................................................... 142
4.7.1.5 P-TMSI handling ................................................................................................................................ 143
4.7.1.6 Change of network mode of operation................................................................................................ 143
4.7.2 GPRS Mobility management timers ......................................................................................................... 144
4.7.2.1 READY timer behaviour..................................................................................................................... 144
4.7.2.2 Periodic routing area updating ............................................................................................................ 145
4.7.3 GPRS attach procedure............................................................................................................................. 146
4.7.3.1 GPRS attach procedure for GPRS services......................................................................................... 147
4.7.3.1.1 GPRS attach procedure initiation .................................................................................................. 147
4.7.3.1.2 GMM common procedure initiation.............................................................................................. 147
4.7.3.1.3 GPRS attach accepted by the network........................................................................................... 147
4.7.3.1.4 GPRS attach not accepted by the network..................................................................................... 148
ETSI
9 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.7.3.1.5 Abnormal cases in the MS.............................................................................................. ............... 148
4.7.3.1.6 Abnormal cases on the network side ............................................................................................. 149
4.7.3.2 Combined GPRS attach procedure for GPRS and non-GPRS services............................................... 151
4.7.3.2.1 Combined GPRS attach procedure initiation................................................................................. 151
4.7.3.2.2 GMM Common procedure initiation............................................................................................. 151
4.7.3.2.3 Combined GPRS attach accepted by the network ......................................................................... 151
4.7.3.2.3.1 Combined attach successful for GPRS and non-GPRS services .............................................. 152
4.7.3.2.3.2 Combined attach successful for GPRS services only............................................................... 152
4.7.3.2.4 Combined GPRS attach not accepted by the network ................................................................... 153
4.7.3.2.5 Abnormal cases in the MS............................................................................................................. 153
4.7.4 GPRS detach procedure............................................................................................................................ 154
4.7.4.1 MS initiated GPRS detach procedure ................................................................................................. 154
4.7.4.1.1 MS initiated GPRS detach procedure initiation............................................................................. 154
4.7.4.1.2 MS initiated GPRS detach procedure completion for GPRS services only................................... 155
4.7.4.1.3 MS initiated combined GPRS detach procedure completion......................................................... 155
4.7.4.1.4 Abnormal cases in the MS.............................................................................................. ............... 155
4.7.4.2 Network initiated GPRS detach procedure ......................................................................................... 156
4.7.4.2.1 Network initiated GPRS detach procedure initiation..................................................................... 156
4.7.4.2.2 Network initiated GPRS detach procedure completion by the MS................................................ 156
4.7.4.2.3 Network initiated GPRS detach procedure completion by the network ........................................ 158
4.7.5 Routing area updating procedure.............................................................................................................. 159
4.7.5.1 Normal and periodic routing area updating procedure........................................................................ 160
4.7.5.1.1 Normal and periodic routing area updating procedure initiation................................................... 160
4.7.5.1.3 Normal and periodic routing area updating procedure accepted by the network........................... 160
4.7.5.1.4 Normal and periodic routing area updating procedure not accepted by the network..................... 161
4.7.5.2 Combined routing area updating procedure ........................................................................................ 164
4.7.5.2.1 Combined routing area updating procedure initiation ................................................................... 164
4.7.5.2.3 Combined routing area updating procedure accepted by the network........................................... 165
4.7.5.2.3.1 Combined routing area updating successful............................................................................. 165
4.7.5.2.3.2 Combined routing are updating successful for GPRS services only ........................................ 166
4.7.5.2.4 Combined routing area updating not accepted by the network...................................................... 166
4.7.6 P-TMSI reallocation procedure ................................................................................................................ 168
4.7.6.1 P-TMSI reallocation initiation by the network.................................................................................... 168
4.7.6.2 P-TMSI reallocation completion by the MS ....................................................................................... 168
4.7.6.3 P-TMSI reallocation completion by the network ................................................................................ 168
4.7.7 Authentication and ciphering procedure................................................................................................... 170
4.7.7.1 Authentication and ciphering initiation by the network ...................................................................... 170
4.7.7.2 Authentication and ciphering response by the MS.............................................................................. 170
4.7.7.3 Authentication and ciphering completion by the network................................................................... 171
4.7.7.4 GPRS ciphering key sequence number ............................................................................................... 171
4.7.7.5 Unsuccessful authentication and ciphering ......................................................................................... 171
4.7.8 Identification procedure............................................................................................................................ 173
4.7.8.1 Identification initiation by the network ............................................................................................... 173
4.7.8.2 Identification response by the MS....................................................................................................... 173
4.7.8.3 Identification completion by the network............................................................................................ 173
4.7.9 Paging procedure ...................................................................................................................................... 174
4.7.9.1 Paging for GPRS services ................................................................................................................... 174
4.7.9.1.1 Paging for GPRS services using P-TMSI ...................................................................................... 174
4.7.9.1.2 Paging for GPRS services using IMSI........................................................................................... 175
ETSI
10 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.7.9.2 Paging for non-GPRS services............................................................................................................ 175
4.7.10 Receiving a GMM STATUS message by a GMM entity.......................................................................... 175
4.7.11 GMM support for anonymous access ....................................................................................................... 175
4.7.11.1 MS side ............................................................................................................................................... 176
4.7.11.2 Network side ....................................................................................................................................... 176
4.7.12 GMM Information procedure ................................................................................................................... 176
4.7.12.1 GMM information procedure initiation by the network...................................................................... 176
4.7.12.2 GMM information procedure in the mobile station............................................................................. 176
5 Elementary procedures for circuit-switched Call Control................................................................... 176
5.1 Overview........................................................................................................................................................ 176
5.1.1 General ..................................................................................................................................................... 176
5.1.2 Call Control States.................................................................................................................................... 181
5.1.2.1 Call states at the mobile station side of the interface........................................................................... 181
5.1.2.1.1 Null (State U0) .............................................................................................................................. 181
5.1.2.1.2 MM Connection pending (U0.1) ................................................................................................... 181
5.1.2.1.2a CC prompt present (U0.2) $(CCBS)$ ........................................................................................... 182
5.1.2.1.2b Wait for network information (U0.3) $(CCBS)$........................................................................... 182
5.1.2.1.2c CC-Establishment present (U0.4) $(CCBS)$ ................................................................................ 182
5.1.2.1.2d CC-Establishment confirmed (U0.5) $(CCBS)$ ........................................................................... 182
5.1.2.1.2e Recall present (U0.6) $(CCBS)$................................................................................................... 182
5.1.2.1.3 Call initiated (U1).......................................................................................................................... 182
5.1.2.1.4 Mobile originating call proceeding (U3) ....................................................................................... 182
5.1.2.1.5 Call delivered (U4)........................................................................................................................ 182
5.1.2.1.6 Call present (U6) ........................................................................................................................... 182
5.1.2.1.7 Call received (U7) ......................................................................................................................... 182
5.1.2.1.8 Connect Request (U8) ................................................................................................................... 182
5.1.2.1.9 Mobile terminating call confirmed (U9)........................................................................................ 183
5.1.2.1.10 Active (U10).................................................................................................................................. 183
5.1.2.1.11 Disconnect request (U11) .............................................................................................................. 183
5.1.2.1.12 Disconnect indication (U12).......................................................................................................... 183
5.1.2.1.13 Release request (U19) ................................................................................................................... 183
5.1.2.1.14 Mobile originating modify (U26) .................................................................................................. 183
5.1.2.1.15 Mobile terminating modify (U27) ................................................................................................. 183
5.1.2.2 Network call states .............................................................................................................................. 183
5.1.2.2.1 Null (State N0) .............................................................................................................................. 183
5.1.2.2.2 MM connection pending (N0.1) .................................................................................................... 183
5.1.2.2.2a CC connection pending (N0.2) $(CCBS)$ .................................................................................... 183
5.1.2.2.2b Network answer pending (N0.3) $(CCBS)$.................................................................................. 183
5.1.2.2.2c CC-Establishment present (N0.4) $(CCBS)$ ................................................................................ 184
5.1.2.2.2d CC-Establishment confirmed (N0.5) $(CCBS)$ ........................................................................... 184
5.1.2.2.3 Call initiated (N1).......................................................................................................................... 184
5.1.2.2.4 Mobile originating call proceeding (N3) ....................................................................................... 184
5.1.2.2.5 Call delivered (N4)........................................................................................................................ 184
5.1.2.2.6 Call present (N6) ........................................................................................................................... 184
5.1.2.2.7 Call received (N7) ......................................................................................................................... 184
5.1.2.2.8 Connect request (N8)..................................................................................................................... 184
5.1.2.2.9 Mobile terminating call confirmed (N9)........................................................................................ 184
5.1.2.2.10 Active (N10).................................................................................................................................. 184
5.1.2.2.11 Not used ........................................................................................................................................ 184
5.1.2.2.12 Disconnect indication (N12).......................................................................................................... 184
5.1.2.2.13 Release request (N19) ................................................................................................................... 185
5.1.2.2.14 Mobile originating modify (N26) .................................................................................................. 185
5.1.2.2.15 Mobile terminating modify (N27) ................................................................................................. 185
5.1.2.2.16 Connect Indication (N28) .............................................................................................................. 185
5.2 Call establishment procedures........................................................................................................................ 185
5.2.1 Mobile originating call establishment....................................................................................................... 185
5.2.1.1 Call initiation ...................................................................................................................................... 186
5.2.1.2 Receipt of a setup message.................................................................................................................. 186
5.2.1.3 Receipt of a CALL PROCEEDING message...................................................................................... 187
5.2.1.4 Notification of progressing mobile originated call.............................................................................. 188
ETSI
11 draft ETSI EN 300 940 V7.7.0 (2000-04)
5.2.1.4.1 Notification of interworking in connection with mobile originated call establishment ................. 188
5.2.1.4.2 Call progress in the PLMN/ISDN environment............................................................................. 188
5.2.1.5 Alerting ............................................................................................................................................... 188
5.2.1.6 Call connected..................................................................................................................................... 189
5.2.1.7 Call rejection....................................................................................................................................... 190
5.2.1.8 Transit network selection .................................................................................................................... 190
5.2.1.9 Traffic channel assignment at mobile originating call establishment .................................................. 190
5.2.1.10 Call queuing at mobile originating call establishment......................................................................... 190
5.2.2 Mobile terminating call establishment ...................................................................................................... 190
5.2.2.1 Call indication..................................................................................................................................... 190
5.2.2.2 Compatibility checking ....................................................................................................................... 191
5.2.2.3 Call confirmation ................................................................................................................................ 191
5.2.2.3.1 Response to SETUP ...................................................................................................................... 191
5.2.2.3.2 Receipt of CALL CONFIRMED and ALERTING by the network............................................... 192
5.2.2.3.3 Call failure procedures .................................................................................................................. 192
5.2.2.3.4 Called mobile station clearing during mobile terminating call establishment ............................... 192
5.2.2.4 Notification of interworking in connection with mobile terminating call establishment ..................... 192
5.2.2.5 Call accept........................................................................................................................................... 193
5.2.2.6 Active indication................................................................................................................................. 193
5.2.2.7 Traffic channel assignment at mobile terminating call establishment ................................................. 193
5.2.2.8 Call queuing at mobile terminating call establishment........................................................................ 193
5.2.2.9 User connection attachment during a mobile terminating call ............................................................ 194
5.2.3 Network initiated MO call $(CCBS)$ ...................................................................................................... 194
5.2.3.1 Initiation.............................................................................................................................................. 194
5.2.3.2 CC-Establishment present ................................................................................................................... 194
5.2.3.2.1 Recall Alignment Procedure.......................................................................................................... 195
5.2.3.3 CC-Establishment confirmation .......................................................................................................... 196
5.2.3.4 Recall present...................................................................................................................................... 196
5.2.3.5 Traffic channel assignment during network initiated mobile originating call establishment............... 197
5.3 Signalling procedures during the "active" state.............................................................................................. 197
5.3.1 User notification procedure ...................................................................................................................... 197
5.3.2 Call rearrangements .................................................................................................................................. 197
5.3.3 Not used.................................................................................................................................................... 198
5.3.4 Support of Dual Services .......................................................................................................................... 198
5.3.4.1 Service Description............................................................................................................................. 198
5.3.4.2 Call establishment ............................................................................................................................... 198
5.3.4.2.1 Mobile Originating Establishment................................................................................................. 198
5.3.4.2.2 Mobile Terminating Establishment ............................................................................................... 199
5.3.4.3 Changing the Call Mode ..................................................................................................................... 199
5.3.4.3.1 Initiation of in-call modification.................................................................................................... 200
5.3.4.3.2 Successful completion of in-call modification............................................................................... 200
5.3.4.3.3 Change of the channel configuration............................................................................................. 200
5.3.4.3.4 Failure of in-call modification....................................................................................................... 200
5.3.4.3.4.1 Network rejection of in-call modification................................................................................ 200
5.3.4.3.4.2 Mobile station rejection of in-call modification....................................................................... 201
5.3.4.3.4.3 Time-out recovery.................................................................................................................... 201
5.3.4.4 Abnormal procedures.......................................................................................................................... 201
5.3.5 User initiated service level up- and downgrading..................................................................................... 201
5.3.5.1 Initiation of service level up- and downgrading.................................................................................. 202
5.3.5.2 Successful completion of service level up- and downgrading............................................................. 202
5.3.5.3 Rejection of service level up- and downgrading ................................................................................. 202
5.3.5.4 Time-out recovery............................................................................................................................... 202
5.4 Call clearing ................................................................................................................................................... 202
5.4.1 Terminology ............................................................................................................................................. 202
5.4.2 Exception conditions ................................................................................................................................ 203
5.4.3 Clearing initiated by the mobile station .................................................................................................... 203
5.4.3.1 Initiation of call clearing..................................................................................................................... 203
5.4.3.2 Receipt of a DISCONNECT message from the mobile station. .......................................................... 203
5.4.3.3 Receipt of a RELEASE message from the network ............................................................................ 204
5.4.3.4 Receipt of a RELEASE COMPLETE message from the mobile station............................................. 204
ETSI
12 draft ETSI EN 300 940 V7.7.0 (2000-04)
5.4.3.5 Abnormal cases ................................................................................................................................... 204
5.4.4 Clearing initiated by the network.............................................................................................................. 204
5.4.4.1 Clearing initiated by the network: mobile does not support Prolonged Clearing Procedure ........... 204
5.4.4.1.1 Clearing when tones/announcements provided.............................................................................. 204
5.4.4.1.2 Clearing when tones/announcements not provided........................................................................ 205
5.4.4.1.3 Completion of clearing.................................................................................................................. 205
5.4.4.2 Clearing initiated by the network: mobile supports Prolonged Clearing Procedure ........................ 206
5.4.4.2.1 Clearing when tones/announcements provided and the network does not indicate that CCBS
activation is possible.................................................................................................................... 206
5.4.4.2.2 Clearing when the network indicates that CCBS activation is possible ..................................... 206
5.4.4.2.3 Clearing when tones/announcements are not provided and the network does not indicate that
CCBS activation is possible.................................................................................................. ..... 207
5.4.4.2.4 Receipt of a RELEASE message from the mobile station............................................................. 208
5.4.4.2.5 Completion of clearing.................................................................................................................. 208
5.4.5 Clear collision........................................................................................................................................... 209
5.5 Miscellaneous procedures .............................................................................................................................. 209
5.5.1 In-band tones and announcements ............................................................................................................ 209
5.5.2 Call collisions ........................................................................................................................................... 209
5.5.3 Status procedures...................................................................................................................................... 210
5.5.3.1 Status enquiry procedure..................................................................................................................... 210
5.5.3.2 Reception of a STATUS message by a CC entity............................................................................... 210
5.5.3.2.1 STATUS message with incompatible state.................................................................................... 210
5.5.3.2.2 STATUS message with compatible state....................................................................................... 210
5.5.4 Call re-establishment, mobile station side ................................................................................................ 210
5.5.4.1 Indication from the mobility management sublayer ............................................................................ 211
5.5.4.2 Reaction of call control ....................................................................................................................... 211
5.5.4.3 Completion of re-establishment .......................................................................................................... 211
5.5.4.4 Unsuccessful outcome......................................................................................................................... 211
5.5.5 Call re-establishment, network side .......................................................................................................... 211
5.5.5.1 State alignment.................................................................................................................................... 211
5.5.6 Progress .................................................................................................................................................... 211
5.5.7 DTMF protocol control procedure ........................................................................................................... 212
5.5.7.1 Start DTMF request by the mobile station .......................................................................................... 212
5.5.7.2 Start DTMF response by the network ................................................................................................. 212
5.5.7.3 Stop DTMF request by the mobile station .......................................................................................... 212
5.5.7.4 Stop DTMF response by the network.................................................................................................. 212
5.5.7.5 Sequencing of subsequent start DTMF requests by the mobile station............................................... 212
6 Support for packet services ................................................................................................................. 213
6.1 GPRS Session management............................................................................................................................ 213
6.1.1 General ..................................................................................................................................................... 213
6.1.1.1 Radio resource sublayer address handling for anonymous access....................................................... 214
6.1.2 Session management states ....................................................................................................................... 214
6.1.2.1 Session management states in the MS................................................................................................. 214
6.1.2.1.1 PDP-INACTIVE ........................................................................................................................... 214
6.1.2.1.2 PDP-ACTIVE-PENDING............................................................................................................. 214
6.1.2.1.3 PDP-INACTIVE-PENDING......................................................................................................... 214
6.1.2.1.4 PDP-ACTIVE................................................................................................................................ 214
6.1.2.2 Session management states on the network side ................................................................................. 215
6.1.2.2.1 PDP-INACTIVE ........................................................................................................................... 215
6.1.2.2.2 PDP-ACTIVE-PENDING............................................................................................................. 215
6.1.2.2.3 PDP-INACTIVE-PENDING......................................................................................................... 215
6.1.2.2.4 PDP-ACTIVE................................................................................................................................ 215
6.1.2.2.5 PDP-MODIFY-PENDING............................................................................................................ 215
6.1.3 Session Management procedures.............................................................................................................. 216
6.1.3.1 PDP context activation........................................................................................................................ 216
6.1.3.1.1 Successful PDP context activation initiated by the mobile station ................................................ 216
6.1.3.1.2 Successful PDP context activation requested by the network........................................................ 217
6.1.3.1.3 Unsuccessful PDP context activation initiated by the MS............................................................. 217
6.1.3.1.4 Unsuccessful PDP context activation requested by the network ................................................... 217
6.1.3.1.5 Abnormal cases ............................................................................................................................. 217
ETSI
13 draft ETSI EN 300 940 V7.7.0 (2000-04)
6.1.3.2 PDP context modification procedure .................................................................................................. 219
6.1.3.2.1 Abnormal cases ............................................................................................................................. 220
6.1.3.3 PDP context deactivation procedure ................................................................................................... 220
6.1.3.3.1 PDP context deactivation initiated by the MS............................................................................... 220
6.1.3.3.2 PDP context deactivation initiated by the network........................................................................ 220
6.1.3.3.3 Abnormal cases ............................................................................................................................. 220
6.1.3.4 AA PDP context activation ................................................................................................................. 221
6.1.3.4.1 Successful AA PDP context activation initiated by the mobile station.......................................... 221
6.1.3.4.2 Unsuccessful AA PDP context activation...................................................................................... 222
6.1.3.4.3 Abnormal cases ............................................................................................................................. 222
6.1.3.5 AA PDP context deactivation ............................................................................................................. 222
6.1.3.5.1 Implicit AA PDP context deactivation .......................................................................................... 222
6.1.3.5.2 Explicit AA PDP context deactivation .......................................................................................... 223
6.1.3.5.3 Abnormal cases ............................................................................................................................. 223
6.1.3.6 Receiving a SM STATUS message by a SM entity ............................................................................223
7 Examples of structured procedures ..................................................................................................... 223
7.1 General ........................................................................................................................................................... 224
7.1.1 Paging request........................................................................................................................................... 224
7.1.2 Immediate assignment .............................................................................................................................. 224
7.1.3 Service request and contention resolution ................................................................................................ 225
7.1.4 Authentication........................................................................................................................................... 225
7.1.5 Ciphering mode setting............................................................................................................................. 225
7.1.6 Transaction phase ..................................................................................................................................... 226
7.1.6.1 Channel mode modify......................................................................................................................... 226
7.1.7 Channel release......................................................................................................................................... 226
7.2 Abnormal cases .............................................................................................................................................. 226
7.3 Selected examples .......................................................................................................................................... 226
7.3.1 Location updating..................................................................................................................................... 227
7.3.2 Mobile originating call establishment....................................................................................................... 228
7.3.3 Mobile terminating call establishment ...................................................................................................... 232
7.3.4 Call clearing.............................................................................................................................................. 234
7.3.5 DTMF protocol control ............................................................................................................................ 235
7.3.6 Handover .................................................................................................................................................. 236
7.3.7 In-call modification .................................................................................................................................. 237
7.3.8 Call re-establishment ................................................................................................................................ 238
7.3.9 Network initiated mobile originating call $(CCBS)$ ............................................................................... 239
8 Handling of unknown, unforeseen, and erroneous protocol data........................................................ 244
8.1 General ........................................................................................................................................................... 244
8.2 Message too short........................................................................................................................................... 244
8.3 Unknown or unforeseen transaction identifier................................................................................................ 245
8.3.1 Call Control .............................................................................................................................................. 245
8.3.2 Session Management ................................................................................................................................ 245
8.4 Unknown or unforeseen message type ........................................................................................................... 246
8.5 Non-semantical mandatory information element errors.................................................................................. 247
8.5.1 Radio resource management ..................................................................................................................... 247
8.5.2 Mobility management ............................................................................................................................... 247
8.5.3 Call control ............................................................................................................................................... 247
8.5.4 GMM mobility management..................................................................................................................... 248
8.5.5 Session management................................................................................................................................. 248
8.6 Unknown and unforeseen IEs in the non-imperative message part ................................................................ 248
8.6.1 IEIs unknown in the message.................................................................................................................... 248
8.6.2 Out of sequence IEs....................................................................................................... ........................... 248
8.6.3 Repeated IEs.............................................................................................................. ............................... 248
8.7 Non-imperative message part errors.......................................................................................... ..................... 249
8.7.1 Syntactically incorrect optional IEs ...................................................................................... .................... 249
8.7.2 Conditional IE errors ..................................................................................................... ........................... 249
8.8 Messages with semantically incorrect contents ............................................................................... ............... 249
ETSI
14 draft ETSI EN 300 940 V7.7.0 (2000-04)
9 Message functional definitions and contents ...................................................................................... 249
9.1 Messages for Radio Resources management.................................................................................................. 250
9.1.1 Additional assignment .............................................................................................................................. 252
9.1.1.1 Mobile Allocation ............................................................................................................................... 253
9.1.1.2 Starting Time ...................................................................................................................................... 253
9.1.2 Assignment command............................................................................................................................... 253
9.1.2.1 Mode of the First Channel (Channel Set 1) and Mode of Channel Set "X" (2=<X=<8)..................... 254
9.1.2.2 Description of the Second Channel ..................................................................................................... 254
9.1.2.3 Mode of the Second Channel .............................................................................................................. 255
9.1.2.4 Mobile Allocation and Frequency List, after the starting time............................................................ 255
9.1.2.5 Starting Time ...................................................................................................................................... 255
9.1.2.6 Reference cell frequency list ............................................................................................................... 256
9.1.2.7 Cell Channel Description .................................................................................................................... 256
9.1.2.8 Cipher Mode Setting........................................................................................................................... 256
9.1.2.9 VGCS target mode Indication............................................................................................................. 256
9.1.2.10 Description of the multislot allocation ................................................................................................ 256
9.1.2.11 Multi Rate configuration..................................................................................................................... 256
9.1.3 Assignment complete................................................................................................................................ 257
9.1.4 Assignment failure.................................................................................................................................... 257
9.1.5 Channel mode modify............................................................................................................................... 257
9.1.5.1 Channel Description............................................................................................................................ 258
9.1.5.2 VGCS target mode Indication............................................................................................................. 258
9.1.5.3 Multi Rate configuration..................................................................................................................... 258
9.1.6 Channel mode modify acknowledge......................................................................................................... 258
9.1.7 Channel release......................................................................................................................................... 259
9.1.7.1 Channel description and mobile allocation ......................................................................................... 260
9.1.7.2 Group Cipher Key Number ................................................................................................................. 260
9.1.8 Channel request ........................................................................................................................................ 260
9.1.9 Ciphering mode command........................................................................................................................ 262
9.1.10 Ciphering mode complete......................................................................................................................... 263
9.1.10.1 Mobile Equipment Identity ................................................................................................................. 263
9.1.11 Classmark change ..................................................................................................................................... 263
9.1.11.1 Additional Mobile Station Classmark Information ............................................................................. 264
9.1.11.2 Mobile Station Classmark................................................................................................................... 264
9.1.12 Classmark enquiry .................................................................................................................................... 264
9.1.12a Spare......................................................................................................................................................... 264
9.1.12b Configuration change command ............................................................................................................... 264
9.1.12b.1 Description of the multislot allocation ................................................................................................ 265
9.1.12b.2 Mode of Channel Set X ( 1=<X<=8)............................................................................................... 265
9.1.12c Configuration change acknowledge.......................................................................................................... 265
9.1.12d Configuration change reject...................................................................................................................... 266
9.1.13 Frequency redefinition.............................................................................................................................. 266
9.1.13.1 Cell Channel Description .................................................................................................................... 267
9.1.13a PDCH Assignment command ................................................................................................................... 267
9.1.13a.1 Mobile Allocation and Frequency List, after the starting time............................................................ 268
9.1.13a.2 Starting Time ...................................................................................................................................... 269
9.1.13a.3 Reference cell frequency list ............................................................................................................... 269
9.1.13a.4 Cell Channel Description .................................................................................................................... 269
9.1.13a.5 Packet Assignment .............................................................................................................................. 269
9.1.13b GPRS suspension request ......................................................................................................................... 270
9.1.14 Handover access ....................................................................................................................................... 271
9.1.15 Handover command.................................................................................................................................. 271
9.1.15.1 Synchronization Indication ................................................................................................................. 274
9.1.15.2 Mode of the First Channel (Channel Set 1) and Mode of Channel Set "X" (2=<X<=8)..................... 274
9.1.15.3 Description of the Second Channel ..................................................................................................... 274
9.1.15.4 Mode of the Second Channel .............................................................................................................. 274
9.1.15.5 Frequency Channel Sequence, Frequency List, Frequency short list and Mobile Allocation, after
time ..................................................................................................................................................... 275
9.1.15.6 Starting Time ...................................................................................................................................... 275
9.1.15.7 Reference cell frequency list ............................................................................................................... 276
ETSI
15 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.15.8 Real Time Difference.......................................................................................................................... 276
9.1.15.9 Timing Advance.................................................................................................................................. 276
9.1.15.11 VGCS target mode indication ............................................................................................................. 276
9.1.15.12 Description of the multislot allocation ................................................................................................ 276
9.1.15.13 MultiRateconfiguration....................................................................................................................... 277
9.1.16 Handover complete................................................................................................................................... 277
9.1.16.1 Mobile Observed Time Difference ..................................................................................................... 277
9.1.17 Handover failure....................................................................................................................................... 277
9.1.18 Immediate assignment .............................................................................................................................. 278
9.1.18.0a Dedicated mode or TBF...................................................................................................................... 279
9.1.18.0b Channel Description............................................................................................................................ 279
9.1.18.0c Packet Channel Description ................................................................................................................ 280
9.1.18.0d Request Reference............................................................................................................................... 280
9.1.18.0e Timing Advance.................................................................................................................................. 280
9.1.18.2 Starting Time ...................................................................................................................................... 280
9.1.18.3 IA Rest Octets (Frequency parameters, before time) .......................................................................... 280
9.1.18.4 IA Rest Octets (assignment of uplink or downlink TBF) .................................................................... 280
9.1.19 Immediate assignment extended ............................................................................................................... 281
9.1.19.1 Unnecessary IEs.................................................................................................................................. 283
9.1.19.3 Starting Time ...................................................................................................................................... 283
9.1.19.4 Maximum message length................................................................................................................... 283
9.1.19.5 IAX Rest Octets .................................................................................................................................. 283
9.1.20 Immediate assignment reject..................................................................................................................... 283
9.1.20.1 Use of the indexes ............................................................................................................................... 284
9.1.20.2 Filling of the message ......................................................................................................................... 285
9.1.20.3 Wait Indication.................................................................................................................................... 285
9.1.20.4 IAR Rest Octets .................................................................................................................................. 285
9.1.21 Measurement report .................................................................................................................................. 285
9.1.21a Notification/FACCH................................................................................................................................. 286
9.1.21a.1 Spare ................................................................................................................................................... 287
9.1.21a.2 Spare ................................................................................................................................................... 287
9.1.21a.3 Spare ................................................................................................................................................... 287
9.1.21a.4 Spare ................................................................................................................................................... 287
9.1.21b Notification/NCH ..................................................................................................................................... 287
9.1.21b.1 Spare ................................................................................................................................................... 289
9.1.21b.2 Spare ................................................................................................................................................... 289
9.1.21d Notification response................................................................................................................................ 289
9.1.21e RR-Cell Change Order.............................................................................................................................. 290
9.1.22 Paging request type 1................................................................................................................................ 290
9.1.22.1 Unnecessary IE ................................................................................................................................... 291
9.1.22.2 Channels needed for Mobiles 1 and 2 ................................................................................................. 291
9.1.22.3 Mobile Identities ................................................................................................................................. 291
9.1.22.4 P1 Rest Octets..................................................................................................................................... 291
9.1.23.2 Mobile Identity 3................................................................................................................................. 293
9.1.23.3 P2 Rest Octets..................................................................................................................................... 293
9.1.24.2 P3 Rest Octets..................................................................................................................................... 294
9.1.25 Paging response ........................................................................................................................................ 295
9.1.26 Partial release............................................................................................................................................ 296
9.1.27 Partial release complete ............................................................................................................................ 297
9.1.28 Physical information................................................................................................................................. 297
9.1.28.a RR Initialisation Request .......................................................................................................................... 298
ETSI
16 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.29 RR Status .................................................................................................................................................. 298
9.1.30 Synchronization channel information ....................................................................................................... 299
9.1.31 System information Type 1....................................................................................................................... 299
9.1.32 System information type 2 ........................................................................................................................ 300
9.1.33 System information type 2bis ................................................................................................................... 301
9.1.34 System information type 2ter .................................................................................................................... 301
9.1.36.1 CBCH Channel description................................................................................................................. 304
9.1.36.2 CBCH Mobile Allocation ................................................................................................................... 304
9.1.36.3 SI 4 Rest Octets................................................................................................................................... 304
9.1.38 System information type 5bis ................................................................................................................... 305
9.1.39 System information type 5ter .................................................................................................................... 306
9.1.40.1 Cell Identity ........................................................................................................................................ 307
9.1.40.2 Location Area Identification ............................................................................................................... 307
9.1.40.3 Cell Options ........................................................................................................................................ 307
9.1.40.4 NCC permitted.................................................................................................................................... 308
9.1.43 System information Type 9....................................................................................................................... 309
9.1.43a System information Type 13..................................................................................................................... 309
9.1.43b [Spare] ...................................................................................................................................................... 306
9.1.43c [Spare] ...................................................................................................................................................... 307
9.1.43d System information type 16 ...................................................................................................................... 307
9.1.43e System information type 17 ...................................................................................................................... 307
9.1.44 Talker indication....................................................................................................................................... 308
9.1.45 Uplink access............................................................................................................................................ 308
9.1.46 Uplink busy............................................................................................................................................... 309
9.1.47 Uplink free................................................................................................................................................ 309
9.1.48 Uplink release........................................................................................................................................... 310
9.1.49 VGCS uplink grant ................................................................................................................................... 310
9.1.50 System information type 10 $(ASCI)$ ..................................................................................................... 311
9.1.51 EXTENDED MEASUREMENT ORDER............................................................................................... 311
9.1.52 Extended measurement report................................................................................................................... 312
9.1.53 Application Information ........................................................................................................................... 312
9.2 Messages for mobility management ............................................................................................................... 313
9.2.1 Authentication reject................................................................................................................................. 313
9.2.2 Authentication request .............................................................................................................................. 314
9.2.3 Authentication response............................................................................................................................ 314
9.2.4 CM Re-establishment request ................................................................................................................... 315
9.2.4.1 Location area identification................................................................................................................. 316
9.2.5 CM service accept .................................................................................................................................... 316
9.2.5a CM service prompt $(CCBS)$ ................................................................................................................. 316
9.2.6 CM service reject...................................................................................................................................... 317
9.2.7 CM service abort ...................................................................................................................................... 317
9.2.8 Abort......................................................................................................................................................... 318
9.2.9 CM service request ................................................................................................................................... 318
9.2.9.2 Priority ................................................................................................................................................ 319
9.2.10 Identity request ......................................................................................................................................... 319
9.2.11 Identity response....................................................................................................................................... 320
9.2.12 IMSI detach indication ............................................................................................................................. 320
9.2.13 Location updating accept .......................................................................................................................... 321
9.2.13.1 Follow on proceed............................................................................................................................... 322
9.2.13.2 CTS permission................................................................................................................................... 322
9.2.14 Location updating reject ........................................................................................................................... 322
ETSI
17 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.2.15 Location updating request......................................................................................................................... 322
9.2.15.1 Location area identification................................................................................................................. 323
9.2.15a MM information ....................................................................................................................................... 323
9.2.15a.1 Full name for network......................................................................................................................... 324
9.2.15a.2 Short name for network....................................................................................................................... 324
9.2.15a.3 Network time zone .............................................................................................................................. 324
9.2.15a.4 Universal time and time zone.............................................................................................................. 324
9.2.15a.5 LSA Identity........................................................................................................................................ 324
9.2.16 MM Status ................................................................................................................................................ 324
9.2.17 TMSI reallocation command .................................................................................................................... 325
9.2.18 TMSI reallocation complete ..................................................................................................................... 325
9.2.19 MM Null................................................................................................................................................... 326
9.3 Messages for circuit-switched call control ..................................................................................................... 326
9.3.1 Alerting..................................................................................................................................................... 327
9.3.1.1 Alerting (network to mobile station direction) .................................................................................... 327
9.3.1.1.1 Facility........................................................................................................................................... 328
9.3.1.1.2 Progress indicator .......................................................................................................................... 328
9.3.1.1.3 User-user ....................................................................................................................................... 328
9.3.1.2 Alerting (mobile station to network direction) .................................................................................... 328
9.3.1.2.1 Facility........................................................................................................................................... 329
9.3.1.2.2 User-user ....................................................................................................................................... 329
9.3.1.2.3 SS version...................................................................................................................................... 329
9.3.2 Call confirmed .......................................................................................................................................... 329
9.3.2.1 Repeat indicator .................................................................................................................................. 330
9.3.2.2 Bearer capability 1 and bearer capability 2......................................................................................... 330
9.3.2.3 Cause................................................................................................................................................... 330
9.3.2.4 CC Capabilities ................................................................................................................................... 330
9.3.3 Call proceeding......................................................................................................................................... 330
9.3.3.2 Bearer capability 1 and bearer capability 2......................................................................................... 331
9.3.3.3 Facility ................................................................................................................................................ 331
9.3.3.4 Progress Indicator ............................................................................................................................... 331
9.3.3.5 Priority granted ................................................................................................................................... 332
9.3.4 Congestion control.................................................................................................................................... 332
9.3.4.1 Cause................................................................................................................................................... 332
9.3.5 Connect..................................................................................................................................................... 332
9.3.5.1 Connect (network to mobile station direction) .................................................................................... 332
9.3.5.1.1 Facility........................................................................................................................................... 333
9.3.5.1.3 User-user ....................................................................................................................................... 333
9.3.5.2 Connect (mobile station to network direction) .................................................................................... 333
9.3.5.2.1 Facility........................................................................................................................................... 334
9.3.5.2.2 User-user ....................................................................................................................................... 334
9.3.5.2.3 SS version...................................................................................................................................... 334
9.3.6 Connect acknowledge............................................................................................................................... 334
9.3.7 Disconnect ................................................................................................................................................ 335
9.3.7.1 Disconnect (network to mobile station direction) ............................................................................... 335
9.3.7.1.1 Facility........................................................................................................................................... 335
9.3.7.1.3 User-user ....................................................................................................................................... 336
9.3.7.1.4 Allowed actions $(CCBS)$ ........................................................................................................... 336
9.3.7.2 Disconnect (mobile station to network direction) ............................................................................... 336
9.3.7.2.1 Facility........................................................................................................................................... 336
9.3.7.2.2 User-user ....................................................................................................................................... 336
9.3.7.2.3 SS version...................................................................................................................................... 337
9.3.8 Emergency setup....................................................................................................................................... 337
9.3.8.1 Bearer capability................................................................................................................................. 337
9.3.9 Facility...................................................................................................................................................... 337
9.3.9.1 Facility (network to mobile station direction) ..................................................................................... 337
ETSI
18 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.3.9.2 Facility (mobile station to network direction) ..................................................................................... 338
9.3.9.2.1 SS version...................................................................................................................................... 339
9.3.10 Hold.......................................................................................................................................................... 339
9.3.11 Hold Acknowledge ................................................................................................................................... 339
9.3.12 Hold Reject............................................................................................................................................... 340
9.3.13 Modify...................................................................................................................................................... 340
9.3.13.1 Low layer compatibility ...................................................................................................................... 341
9.3.13.2 High layer compatibility...................................................................................................................... 341
9.3.13.3 Reverse call setup direction ................................................................................................................ 341
9.3.14 Modify complete....................................................................................................................................... 341
9.3.14.3 Reverse call setup direction ................................................................................................................ 342
9.3.15 Modify reject ............................................................................................................................................ 342
9.3.16 Notify........................................................................................................................................................ 343
9.3.17 Progress .................................................................................................................................................... 343
9.3.17.1 User-user ............................................................................................................................................. 344
9.3.17a CC-Establishment $(CCBS)$ ................................................................................................................... 344
9.3.17a.2 Setup container.................................................................................................................................... 344
9.3.17b CC-Establishment confirmed $(CCBS)$ .................................................................................................. 344
9.3.17b.1 Repeat indicator .................................................................................................................................. 345
9.3.17b.2 Bearer capability 1 and bearer capability 2......................................................................................... 345
9.3.17b.9 Cause................................................................................................................................................... 345
9.3.18 Release...................................................................................................................................................... 345
9.3.18.1 Release (network to mobile station direction)..................................................................................... 345
9.3.18.1.1 Cause ............................................................................................................................................. 346
9.3.18.1.2 Second cause ................................................................................................................................. 346
9.3.18.1.3 Facility........................................................................................................................................... 346
9.3.18.1.4 User-user ....................................................................................................................................... 346
9.3.18.2 Release (mobile station to network direction)..................................................................................... 346
9.3.18.2.1 Cause ............................................................................................................................................. 347
9.3.18.2.2 Second cause ................................................................................................................................. 347
9.3.18.2.3 Facility........................................................................................................................................... 347
9.3.18.2.4 User-user ....................................................................................................................................... 347
9.3.18.2.5 SS version...................................................................................................................................... 348
9.3.18a Recall $(CCBS)$...................................................................................................................................... 348
9.3.18a.1 Recall Type ......................................................................................................................................... 348
9.3.18a.2 Facility ................................................................................................................................................ 348
9.3.19 Release complete ...................................................................................................................................... 348
9.3.19.1 Release complete (network to mobile station direction) ..................................................................... 348
9.3.19.1.1 Cause ............................................................................................................................................. 349
9.3.19.1.2 Facility........................................................................................................................................... 349
9.3.19.1.3 User-user ....................................................................................................................................... 349
9.3.19.2 Release complete (mobile station to network direction) ..................................................................... 349
9.3.19.2.1 Cause ............................................................................................................................................. 350
9.3.19.2.2 Facility........................................................................................................................................... 350
9.3.19.2.3 User-user ....................................................................................................................................... 350
9.3.19.2.4 SS version...................................................................................................................................... 350
9.3.20 Retrieve..................................................................................................................................................... 350
9.3.21 Retrieve Acknowledge.............................................................................................................................. 351
9.3.22 Retrieve Reject ......................................................................................................................................... 351
9.3.23 Setup......................................................................................................................................................... 352
9.3.23.1 Setup (mobile terminated call establishment) ..................................................................................... 352
9.3.23.1.1 BC repeat indicator........................................................................................................................ 353
9.3.23.1.2 Bearer capability 1 and bearer capability 2 ................................................................................... 354
9.3.23.1.3 Facility........................................................................................................................................... 354
9.3.23.1.4a Called party BCD number ............................................................................................................. 354
ETSI
19 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.3.23.1.5 Called party subaddress................................................................................................................. 354
9.3.23.1.6 LLC repeat indicator ..................................................................................................................... 354
9.3.23.1.7 Low layer compatibility I .............................................................................................................. 354
9.3.23.1.8 Low layer compatibility II ............................................................................................................. 354
9.3.23.1.9 HLC repeat indicator ..................................................................................................................... 354
9.3.23.1.10 High layer compatibility i.............................................................................................................. 354
9.3.23.1.11 High layer compatibility ii............................................................................................................. 355
9.3.23.1.12 User-user ....................................................................................................................................... 355
9.3.23.1.13 Redirecting party BCD number ..................................................................................................... 355
9.3.23.1.14 Redirecting party subaddress......................................................................................................... 355
9.3.23.1.15 Priority........................................................................................................................................... 355
9.3.23.1.16 Alert $(Network Indication of Alerting in the MS )$ .................................................................... 355
9.3.23.2 Setup (mobile originating call establishment) ..................................................................................... 355
9.3.23.2.1 BC repeat indicator........................................................................................................................ 357
9.3.23.2.2 Facility........................................................................................................................................... 357
9.3.23.2.3 LLC repeat indicator ..................................................................................................................... 357
9.3.23.2.4 Low layer compatibility I .............................................................................................................. 357
9.3.23.2.5 Low layer compatibility II ............................................................................................................. 357
9.3.23.2.6 HLC repeat indicator ..................................................................................................................... 357
9.3.23.2.7 High layer compatibility i.............................................................................................................. 357
9.3.23.2.8 High layer compatibility ii............................................................................................................. 357
9.3.23.2.9 User-user ....................................................................................................................................... 357
9.3.23.2.10 SS version...................................................................................................................................... 357
9.3.23.2.11 CLIR suppression.......................................................................................................................... 358
9.3.23.2.12 CLIR invocation............................................................................................................................ 358
9.3.23.2.13 CC Capabilities.............................................................................................................................. 358
9.3.23a Start CC $(CCBS)$ .................................................................................................................................. 358
9.3.23a.1 CC Capabilities ................................................................................................................................... 358
9.3.24 Start DTMF .............................................................................................................................................. 358
9.3.25 Start DTMF Acknowledge........................................................................................................................ 359
9.3.25.1 Keypad facility.................................................................................................................................... 359
9.3.26 Start DTMF reject..................................................................................................................................... 359
9.3.27 Status ........................................................................................................................................................ 360
9.3.27.1 Auxiliary states.................................................................................................................................... 361
9.3.28 Status enquiry ........................................................................................................................................... 361
9.3.29 Stop DTMF............................................................................................................................................... 361
9.3.30 Stop DTMF acknowledge......................................................................................................................... 361
9.3.31 User information....................................................................................................................................... 362
9.3.31.1 User-user ............................................................................................................................................. 362
9.3.31.2 More data ............................................................................................................................................ 363
9.4 GPRS Mobility Management Messages......................................................................................................... 363
9.4.1 Attach request ........................................................................................................................................... 363
9.4.1.1 Old P-TMSI signature......................................................................................................................... 363
9.4.1.2 Requested READY timer value .......................................................................................................... 363
9.4.1.3 TMSI status......................................................................................................................................... 363
9.4.2 Attach accept ............................................................................................................................................ 364
9.4.2.1 P-TMSI signature................................................................................................................................ 364
9.4.2.2 Negotiated READY timer ................................................................................................................... 364
9.4.2.3 Allocated P-TMSI............................................................................................................................... 364
9.4.2.4 MS identity.......................................................................................................................................... 364
9.4.2.5 GMM cause......................................................................................................................................... 365
9.4.3 Attach complete........................................................................................................................................ 365
9.4.4 Attach reject.............................................................................................................................................. 365
9.4.5 Detach request .......................................................................................................................................... 365
9.4.5.1 Detach request (mobile terminated detach)......................................................................................... 365
9.4.5.1.1 GMM cause................................................................................................................................... 366
9.4.5.2 Detach request (mobile originating detach) ........................................................................................ 366
9.4.6 Detach accept............................................................................................................................................ 366
9.4.6.1 Detach accept (mobile terminated detach) .......................................................................................... 366
9.4.6.2 Detach accept (mobile originating detach).......................................................................................... 367
ETSI
20 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.4.7 P-TMSI reallocation command................................................................................................................. 367
9.4.7.1 P-TMSI signature................................................................................................................................ 368
9.4.8 P-TMSI reallocation complete.................................................................................................................. 368
9.4.9 Authentication and ciphering request ....................................................................................................... 368
9.4.9.1 Authentication Parameter RAND........................................................................................................ 369
9.4.9.2 GPRS ciphering key sequence number ............................................................................................... 369
9.4.10 Authentication and ciphering response ..................................................................................................... 369
9.4.10.1 Authentication Parameter SRES ......................................................................................................... 369
9.4.10.2 IMEISV............................................................................................................................................... 370
9.4.11 Authentication and ciphering reject .......................................................................................................... 370
9.4.12 Identity request ......................................................................................................................................... 370
9.4.13 Identity response....................................................................................................................................... 370
9.4.14 Routing area update request...................................................................................................................... 371
9.4.14.1 Old P-TMSI signature......................................................................................................................... 371
9.4.14.2 Requested READY timer value .......................................................................................................... 371
9.4.14.3 DRX parameter ................................................................................................................................... 371
9.4.14.4 TMSI status......................................................................................................................................... 371
9.4.15 Routing area update accept ....................................................................................................................... 372
9.4.15.1 P-TMSI signature................................................................................................................................ 372
9.4.15.2 Allocated P-TMSI............................................................................................................................... 372
9.4.15.3 MS identity.......................................................................................................................................... 372
9.4.15.4 List of Receive N-PDU Numbers........................................................................................................ 372
9.4.15.5 Negotiated READY timer value.......................................................................................................... 372
9.4.15.6 GMM cause......................................................................................................................................... 373
9.4.16 Routing area update complete................................................................................................................... 373
9.4.16.1 List of Receive N-PDU Numbers........................................................................................................ 373
9.4.17 Routing area update reject ........................................................................................................................ 373
9.4.18 GMM Status ............................................................................................................................................. 373
9.4.19 GMM Information .................................................................................................................................... 374
9.4.19.1 Full name for network......................................................................................................................... 374
9.4.19.2 Short name for network....................................................................................................................... 374
9.4.19.3 Network time zone .............................................................................................................................. 374
9.4.19.4 Universal time and time zone.............................................................................................................. 375
9.4.19.5 LSA Identity........................................................................................................................................ 375
9.5 GPRS Session Management Messages........................................................................................................... 375
9.5.1 Activate PDP context request ................................................................................................................... 375
9.5.1.1 Access point name............................................................................................................................... 375
9.5.1.2 Protocol configuration options............................................................................................................ 375
9.5.2 Activate PDP context accept .................................................................................................................... 375
9.5.2.1 PDP address ........................................................................................................................................ 376
9.5.3 Activate PDP context reject...................................................................................................................... 376
9.5.4 Request PDP context activation................................................................................................................ 377
9.5.5 Request PDP context activation reject...................................................................................................... 377
9.5.6 Modify PDP context request..................................................................................................................... 378
9.5.7 Modify PDP context accept ...................................................................................................................... 378
9.5.8 Deactivate PDP context request................................................................................................................ 378
9.5.9 Deactivate PDP context accept ................................................................................................................. 379
9.5.10 Activate AA PDP context request............................................................................................................. 379
9.5.10.1 Access point name............................................................................................................................... 380
9.5.10.3 Requested AA-READY timer value.................................................................................................... 380
9.5.11 Activate AA PDP context accept.............................................................................................................. 380
9.5.11.2 Negotiated AA-Ready timer value ...................................................................................................... 381
9.5.12 Activate AA PDP context reject ............................................................................................................... 381
9.5.13 Deactivate AA PDP context request ......................................................................................................... 382
9.5.14 Deactivate AA PDP context accept .......................................................................................................... 382
ETSI
21 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.5.15 SM Status.................................................................................................................................................. 382
10 General message format and information elements coding ................................................................ 384
10.1 Overview........................................................................................................................................................ 384
10.2 Protocol Discriminator ................................................................................................................................... 385
10.3 Skip indicator and transaction identifier......................................................................................................... 385
10.3.1 Skip indicator............................................................................................................................................ 385
10.3.2 Transaction identifier................................................................................................................................ 385
10.4 Message Type................................................................................................................................................. 385
10.5 Other information elements ............................................................................................................................ 391
10.5.1 Common information elements................................................................................................................. 392
10.5.1.1 Cell identity......................................................................................................................................... 392
10.5.1.2 Ciphering Key Sequence Number ....................................................................................................... 393
10.5.1.3 Location Area Identification ............................................................................................................... 393
10.5.1.4 Mobile Identity.................................................................................................................................... 395
10.5.1.5 Mobile Station Classmark 1................................................................................................................ 397
10.5.1.8 Spare Half Octet.................................................................................................................................. 405
10.5.1.9 Descriptive group or broadcast call reference..................................................................................... 405
10.5.1.10 Group Cipher Key Number ................................................................................................................. 407
10.5.1.10a PD and SAPI $(CCBS)$ ..................................................................................................................... 408
10.5.1.11 Priority Level ...................................................................................................................................... 408
10.5.2 Radio Resource management information elements ................................................................................. 409
10.5.2.1a BA Range............................................................................................................................................ 409
10.5.2.1b Cell Channel Description .................................................................................................................... 411
10.5.2.1b.1 General description........................................................................................................................ 412
10.5.2.1b.2 Bit map 0 format............................................................................................................................ 413
10.5.2.1b.3 Range 1024 format ........................................................................................................................ 414
10.5.2.1b.4 Range 512 format .......................................................................................................................... 415
10.5.2.1b.5 Range 256 format .......................................................................................................................... 416
10.5.2.1b.6 Range 128 format .......................................................................................................................... 417
10.5.2.1b.7 Variable bit map format................................................................................................................. 418
10.5.2.1c BA List Pref ........................................................................................................................................ 419
10.5.2.2 Cell Description .................................................................................................................................. 419
10.5.2.3 Cell Options (BCCH).......................................................................................................................... 420
10.5.2.3a Cell Options (SACCH) ....................................................................................................................... 420
10.5.2.4 Cell Selection Parameters ................................................................................................................... 422
10.5.2.4a MAC Mode and Channel Coding Requested ...................................................................................... 424
10.5.2.5a Channel Description 2......................................................................................................................... 427
10.5.2.6 Channel Mode..................................................................................................................................... 429
10.5.2.7 Channel Mode 2.................................................................................................................................. 430
10.5.2.8 Channel Needed.................................................................................................................................. 431
10.5.2.8a Channel Request Description.............................................................................................................. 431
10.5.2.10 Cipher Response ................................................................................................................................. 434
10.5.2.11 Control Channel Description............................................................................................................... 434
10.5.2.12 Frequency Channel Sequence ............................................................................................................. 436
10.5.2.13 Frequency List..................................................................................................................................... 437
10.5.2.13.1 General description........................................................................................................................ 438
10.5.2.13.2 Bit map 0 format............................................................................................................................ 438
10.5.2.13.3 Range 1024 format ........................................................................................................................ 439
10.5.2.13.4 Range 512 format .......................................................................................................................... 441
10.5.2.13.5 Range 256 format .......................................................................................................................... 444
10.5.2.13.6 Range 128 format .......................................................................................................................... 447
10.5.2.13.7 Variable bit map format................................................................................................................. 450
10.5.2.14 Frequency Short List ........................................................................................................................... 451
10.5.2.14a Frequency Short List 2........................................................................................................................ 451
10.5.2.14b Group Channel Description................................................................................................................. 452
10.5.2.14c GPRS Resumption .............................................................................................................................. 455
ETSI
22 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.15 Handover Reference............................................................................................................................ 455
10.5.2.16 IA Rest Octets ..................................................................................................................................... 455
10.5.2.17 IAR Rest Octets .................................................................................................................................. 460
10.5.2.18 IAX Rest Octets .................................................................................................................................. 460
10.5.2.19 L2 Pseudo Length ............................................................................................................................... 461
10.5.2.20 Measurement Results .......................................................................................................................... 461
10.5.2.20a GPRS Measurement Results ............................................................................................................... 465
10.5.2.21a Mobile Time Difference...................................................................................................................... 467
10.5.2.21aa MultiRate configuration...................................................................................................................... 467
10.5.2.21b Multislot Allocation ............................................................................................................................ 471
10.5.2.21c NC mode ............................................................................................................................................. 473
10.5.2.22 Neighbour Cells Description............................................................................................................... 474
10.5.2.22a Neighbour Cells Description 2............................................................................................................ 475
10.5.2.22c NT/N Rest Octets................................................................................................................................ 476
10.5.2.23 P1 Rest Octets..................................................................................................................................... 476
10.5.2.24 P2 Rest Octets..................................................................................................................................... 477
10.5.2.25 P3 Rest Octets..................................................................................................................................... 478
10.5.2.25a Packet Channel Description ................................................................................................................ 479
10.5.2.25b Dedicated mode or TBF...................................................................................................................... 480
10.5.2.25c RR Packet Uplink Assignment............................................................................................................ 480
10.5.2.25d RR Packet Downlink Assignment ....................................................................................................... 485
10.5.2.26 Page Mode .......................................................................................................................................... 486
10.5.2.26a Spare ................................................................................................................................................... 487
10.5.2.26b Spare ................................................................................................................................................... 487
10.5.2.26c Spare ................................................................................................................................................... 487
10.5.2.26d Spare ................................................................................................................................................... 487
10.5.2.27 NCC Permitted.................................................................................................................................... 487
10.5.2.28 Power Command................................................................................................................................. 488
10.5.2.28a Power Command and access type ....................................................................................................... 488
10.5.2.29 RACH Control Parameters.................................................................................................................. 489
10.5.2.30 Request Reference............................................................................................................................... 490
10.5.2.31 RR Cause ............................................................................................................................................ 491
10.5.2.32 SI 1 Rest Octets................................................................................................................................... 492
10.5.2.33 SI 2bis Rest Octets .............................................................................................................................. 493
10.5.2.33a SI 2ter Rest Octets .............................................................................................................................. 493
10.5.2.34 SI 3 Rest Octets................................................................................................................................... 494
10.5.2.35 SI 4 Rest Octets................................................................................................................................... 496
10.5.2.35a SI 6 Rest Octets................................................................................................................................... 499
10.5.2.36 SI 7 Rest Octets................................................................................................................................... 499
10.5.2.37 SI 8 Rest Octets................................................................................................................................... 499
10.5.2.37a SI 9 Rest Octets................................................................................................................................... 500
10.5.2.37b SI 13 Rest Octets................................................................................................................................. 502
10.5.2.37c [Spare]................................................................................................................................................. 505
10.5.2.37d [Spare]................................................................................................................................................. 506
10.5.2.37e SI 16 Rest Octets................................................................................................................................. 506
10.5.2.37f SI 17 Rest Octets................................................................................................................................. 507
10.5.2.38 Starting Time ...................................................................................................................................... 507
10.5.2.39 Synchronization Indication ................................................................................................................. 508
10.5.2.40 Timing Advance.................................................................................................................................. 508
10.5.2.41 Time Difference .................................................................................................................................. 509
10.5.2.41a TLLI.................................................................................................................................................... 509
10.5.2.42 TMSI/P-TMSI..................................................................................................................................... 510
10.5.2.42a VGCS target mode Indication............................................................................................................. 510
10.5.2.43 Wait Indication.................................................................................................................................... 511
10.5.2.44 SI10 rest octets $(ASCI)$ ................................................................................................................... 511
10.5.2.45 EXTENDED MEASUREMENT RESULTS...................................................................................... 514
10.5.2.46 Extended Measurement Frequency List .............................................................................................. 516
10.5.2.47 Suspension Cause................................................................................................................................ 517
10.5.2.48 APDU ID............................................................................................................................................ 517
ETSI
23 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.49 APDU Flags ........................................................................................................................................ 518
10.5.2.50 APDU Data ..................................................................................................................................................... 518
10.5.3 Mobility management information elements............................................................................................. 519
10.5.3.1 Authentication parameter RAND........................................................................................................ 519
10.5.3.2 Authentication parameter SRES.......................................................................................................... 520
10.5.3.3 CM service type .................................................................................................................................. 520
10.5.3.4 Identity type ........................................................................................................................................ 521
10.5.3.5 Location updating type........................................................................................................................ 521
10.5.3.5a Network Name .................................................................................................................................... 522
10.5.3.6 Reject cause ........................................................................................................................................ 523
10.5.3.7 Follow-on Proceed.............................................................................................................................. 524
10.5.3.8 Time Zone........................................................................................................................................... 524
10.5.3.9 Time Zone and Time........................................................................................................................... 525
10.5.3.10 CTS permission................................................................................................................................... 526
10.5.3.11 LSA Identifier ..................................................................................................................................... 526
10.5.4 Call control information elements............................................................................................................. 527
10.5.4.1 Extensions of codesets ........................................................................................................................ 527
10.5.4.2 Locking shift procedure ...................................................................................................................... 527
10.5.4.3 Non-locking shift procedure................................................................................................................ 528
10.5.4.4 Auxiliary states.................................................................................................................................... 529
10.5.4.5 Bearer capability................................................................................................................................. 530
10.5.4.5.1 Static conditions for the bearer capability IE contents .................................................................. 541
10.5.4.5a Call Control Capabilities..................................................................................................................... 542
10.5.4.6 Call state ............................................................................................................................................. 542
10.5.4.7 Called party BCD number................................................................................................................... 544
10.5.4.8 Called party subaddress ...................................................................................................................... 546
10.5.4.9 Calling party BCD number ................................................................................................................. 547
10.5.4.10 Calling party subaddress ..................................................................................................................... 548
10.5.4.11 Cause................................................................................................................................................... 549
10.5.4.11a CLIR suppression................................................................................................................................ 554
10.5.4.11b CLIR invocation.................................................................................................................................. 555
10.5.4.12 Congestion level.................................................................................................................................. 555
10.5.4.13 Connected number .............................................................................................................................. 555
10.5.4.14 Connected subaddress ......................................................................................................................... 556
10.5.4.15 Facility ................................................................................................................................................ 556
10.5.4.16.1 Static conditions for the high layer compatibility IE contents ....................................................... 558
10.5.4.17 Keypad facility.................................................................................................................................... 558
10.5.4.19 More data ............................................................................................................................................ 559
10.5.4.20 Notification indicator .......................................................................................................................... 559
10.5.4.21 Progress indicator................................................................................................................................ 560
10.5.4.21a Recall type $(CCBS)$......................................................................................................................... 561
10.5.4.21b Redirecting party BCD number........................................................................................................... 562
10.5.4.21c Redirecting party subaddress......................................................................................................... 562
10.5.4.22a Reverse call setup direction ................................................................................................................ 563
10.5.4.22b SETUP Container $(CCBS)$.............................................................................................................. 564
10.5.4.23 Signal .................................................................................................................................................. 564
10.5.4.24 SS Version Indicator ........................................................................................................................... 565
10.5.4.25 User-user ............................................................................................................................................. 565
10.5.4.26 Alerting Pattern $(NIA)$ .................................................................................................................... 566
10.5.4.27 Allowed actions $(CCBS)$................................................................................................................. 567
10.5.5 GPRS mobility management information elements .................................................................................. 568
10.5.5.1 Attach result ........................................................................................................................................ 568
10.5.5.2 Attach type .......................................................................................................................................... 568
10.5.5.3 Ciphering algorithm............................................................................................................................ 569
10.5.5.4 [Spare]TMSI status ............................................................................................................................. 569
10.5.5.5 Detach type ......................................................................................................................................... 569
10.5.5.6 DRX parameter ................................................................................................................................... 570
ETSI
24 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.5.7 Force to standby.................................................................................................................................. 572
10.5.5.8 P-TMSI signature................................................................................................................................ 572
10.5.5.9 Identity type 2 ..................................................................................................................................... 572
10.5.5.10 IMEISV request .................................................................................................................................. 573
10.5.5.11 Receive N-PDU Numbers list ............................................................................................................. 573
10.5.5.12 MS network capability........................................................................................................................ 574
10.5.5.12a MS Radio Access capability ............................................................................................................... 576
10.5.5.13 Spare ................................................................................................................................................... 579
10.5.5.14 GMM cause......................................................................................................................................... 579
10.5.5.15 Routing area identification.................................................................................................................. 580
10.5.5.16 Spare ................................................................................................................................................... 582
10.5.5.17 Update result ....................................................................................................................................... 582
10.5.5.18 Update type ......................................................................................................................................... 583
10.5.5.19 A&C reference number ....................................................................................................................... 583
10.5.6 Session management information elements .............................................................................................. 584
10.5.6.1 Access Point Name ............................................................................................................................. 584
10.5.6.2 Network service access point identifier............................................................................................... 584
10.5.6.4 Packet data protocol address............................................................................................................... 589
10.5.6.5 Quality of service ................................................................................................................................ 591
10.5.6.6 SM cause............................................................................................................................................. 594
10.5.6.7 Spare ................................................................................................................................................... 594
10.5.6.8 AA deactivation cause......................................................................................................................... 595
10.5.6.9 LLC service access point identifier ..................................................................................................... 595
10.5.7 GPRS Common information elements...................................................................................................... 596
10.5.7.1 [Spare]................................................................................................................................................. 596
10.5.7.2 Radio priority...................................................................................................................................... 596
10.5.7.3 GPRS Timer........................................................................................................................................ 596
11 List of system parameters.................................................................................................................... 598
11.1 Timers and counters for radio resource management ..................................................................................... 598
11.1.1 Timers on the mobile station side ............................................................................................................. 598
11.1.2 Timers on the network side....................................................................................................................... 599
11.1.3 Other parameters....................................................................................................................................... 601
11.2 Timers of mobility management..................................................................................................................... 602
11.2.1 Timer T3240............................................................................................................................................. 603
11.2.2 Timers of GPRS mobility management .................................................................................................... 604
11.2.3 Timers of session management ................................................................................................................. 606
11.3 Timers of circuit-switched call control........................................................................................................... 607
Annex A (informative): Example of subaddress information element coding............................... 609
Annex B (normative): Compatibility checking............................................................................... 610
B.1 Introduction ......................................................................................................................................... 610
B.2 Calling side compatibility checking.................................................................................................... 610
B.2.1 Compatibility checking of the CM SERVICE REQUEST message............................................................... 610
B.2.2 Compatibility/Subscription checking of the SETUP message........................................................................ 610
B.3 Called side compatibility checking ..................................................................................................... 610
B.3.1 Compatibility checking with addressing information..................................................................................... 611
B.3.2 Network-to-MS compatibility checking ......................................................................................................... 611
B.3.3 User-to-User compatibility checking.............................................................................................................. 611
B.4 High layer compatibility checking ...................................................................................................... 611
Annex C (normative): Low layer information coding principles ................................................. 612
C.1 Purpose ................................................................................................................................................ 612
C.2 Principles ............................................................................................................................................. 612
C.2.1 Definition of types of information.................................................................................................................. 612
ETSI
25 draft ETSI EN 300 940 V7.7.0 (2000-04)
C.2.2 Examination by network................................................................................................................................. 612
C.2.3 Location of type I information........................................................................................................................ 613
C.2.4 Location of types II and III information......................................................................................................... 613
C.2.5 Relationship between bearer capability and low layer compatibility information elements ........................... 613
Annex D (informative): Examples of bearer capability information element coding................... 614
D.1 Coding for speech for a full rate support only mobile station............................................................. 614
D.1.1 Mobile station to network direction ............................................................................................................... 614
D.1.2 Network to mobile station direction............................................................................................................... 614
D.2 An example of a coding for modem access with V22-bis, 2.4 kbit/s, 8 bit no parity ......................... 615
D.2.1 Mobile station to network direction, data compression allowed .................................................................... 615
D.2.2 Network to mobile station direction, data compression possible.................................................................... 615
D.3 An example of a coding for group 3 facsimile (9.6 kbit/s, transparent).............................................. 617
D.3.1 Mobile station to network direction ............................................................................................................... 617
D.3.2 Network to mobile station direction............................................................................................................... 618
Annex E (informative): Comparison between call control procedures specified in GSM 04.08
and CCITT Recommendation Q.931 ........................................................ 619
Annex F (informative): GSM specific cause values for radio resource management................... 623
Annex G (informative): GSM specific cause values for mobility management ............................. 625
G.1 Causes related to MS identification .................................................................................................... 625
G.2 Cause related to subscription options.................................................................................................. 625
G.3 Causes related to PLMN specific network failures and congestion.................................................... 625
G.4 Causes related to nature of request...................................................................................................... 626
G.5 Causes related to invalid messages ..................................................................................................... 626
G.6 Additional cause codes for GMM....................................................................................................... 627
Annex H (informative): GSM specific cause values for call control ............................................... 628
H.1 Normal class ........................................................................................................................................ 628
H.1.1 Cause No. 1 "unassigned (unallocated) number" ........................................................................................... 628
H.1.2 Cause No. 3 "no route to destination" ............................................................................................................ 628
H.1.3 Cause No. 6 "channel unacceptable".............................................................................................................. 628
H.1.4 Cause No. 8 "operator determined barring" ................................................................................................... 628
H.1.5 Cause No.16 "normal call clearing" ............................................................................................................... 628
H.1.6 Cause No.17 "user busy"................................................................................................................................ 628
H.1.7 Cause No. 18 "no user responding"................................................................................................................ 628
H.1.8 Cause No. 19 "user alerting, no answer" ........................................................................................................ 628
H.1.9 Cause No. 21 "call rejected" .......................................................................................................................... 629
H.1.10 Cause No. 22 "number changed".................................................................................................................... 629
H.1.11 Cause No. 25 pre-emption .......................................................................................................................... 629
H.1.12 Cause No. 26 "non-selected user clearing" .................................................................................................... 629
H.1.13 Cause No. 27 "destination out of order"......................................................................................................... 629
H.1.14 Cause No. 28 "invalid number format (incomplete number)" ........................................................................ 629
H.1.15 Cause No. 29 "facility rejected" ..................................................................................................................... 629
H.1.16 Cause No. 30 "response to STATUS ENQUIRY"......................................................................................... 629
H.1.17 Cause No. 31 "normal, unspecified" .............................................................................................................. 629
H.2 Resource unavailable class.................................................................................................................. 629
H.2.1 Cause No. 34 "no circuit/channel available" .................................................................................................. 629
H.2.2 Cause No. 38 "network out of order" ............................................................................................................. 630
H.2.3 Cause No. 41 "temporary failure" .................................................................................................................. 630
H.2.4 Cause No. 42 "switching equipment congestion"........................................................................................... 630
H.2.5 Cause No. 43 "access information discarded"................................................................................................ 630
ETSI
26 draft ETSI EN 300 940 V7.7.0 (2000-04)
H.2.6 Cause No. 44 "requested circuit/channel not available"................................................................................. 630
H.2.7 Cause No. 47 "resource unavailable, unspecified"......................................................................................... 630
H.3 Service or option not available class ................................................................................................... 630
H.3.1 Cause No. 49 "quality of service unavailable" ............................................................................................... 630
H.3.2 Cause No. 50 "Requested facility not subscribed" ......................................................................................... 630
H.3.3 Cause No. 55 "Incoming calls barred within the CUG" ................................................................................. 630
H.3.4 Cause No. 57 "bearer capability not authorized" ........................................................................................... 630
H.3.5 Cause No. 58 "bearer capability not presently available" .............................................................................. 631
H.3.6 Cause No. 63 "service or option not available, unspecified".......................................................................... 631
H.3.7 Cause No. 68 "ACM equal to or greater than ACMmax" .............................................................................. 631
H.4 Service or option not implemented class............................................................................................. 631
H.4.1 Cause No. 65 "bearer service not implemented" ............................................................................................ 631
H.4.2 Cause No. 69 "Requested facility not implemented"...................................................................................... 631
H.4.3 Cause No. 70 "only restricted digital information bearer capability is available".......................................... 631
H.4.4 Cause No. 79 "service or option not implemented, unspecified" ................................................................... 631
H.5 Invalid message (e.g., parameter out of range) class........................................................................... 631
H.5.1 Cause No. 81 "invalid transaction identifier value" ....................................................................................... 631
H.5.2 Cause No. 87 "user not member of CUG"...................................................................................................... 631
H.5.3 Cause No. 88 "incompatible destination"....................................................................................................... 632
H.5.4 Cause No. 91 "invalid transit network selection" ........................................................................................... 632
H.5.5 Cause No. 95 "semantically incorrect message"............................................................................................. 632
H.6 Protocol error (e.g., unknown message) class ..................................................................................... 632
H.6.1 Cause No. 96 "invalid mandatory information" ............................................................................................. 632
H.6.2 Cause No. 97 "message type non-existent or not implemented" .................................................................... 632
H.6.3 Cause No. 98 "message type not compatible with protocol state".................................................................. 632
H.6.4 Cause No. 99 "information element non-existent or not implemented" ......................................................... 632
H.6.5 Cause No. 100 "conditional IE error" ............................................................................................................ 632
H.6.6 Cause No. 101 "message not compatible with protocol state" ....................................................................... 632
H.6.7 Cause No. 102 "recovery on timer expiry"..................................................................................................... 633
H.6.8 Cause No. 111 "protocol error, unspecified" ................................................................................................. 633
H.7 Interworking class ............................................................................................................................... 633
H.7.1 Cause No. 127 "interworking, unspecified" ................................................................................................... 633
ETSI
27 draft ETSI EN 300 940 V7.7.0 (2000-04)
Annex I (informative): GSM specific cause values for session management................................ 634
I.1 Causes related to nature of request...................................................................................................... 634
I.2 Causes related to invalid messages ..................................................................................................... 635
Annex J (informative): Algorithm to encode frequency list information elements...................... 636
J.1 Introduction ......................................................................................................................................... 636
J.2 General principle ................................................................................................................................. 636
J.3 Performances ....................................................................................................................................... 638
J.4 Encoding algorithm............................................................................................................................. 639
J.5 Decoding.............................................................................................................................................. 641
J.6 A detailed example.............................................................................................................................. 642
Annex K (informative): Default Codings of Information Elements................................................ 644
K.1 Common information elements ........................................................................................................... 644
K.2 Radio Resource management information elements ........................................................................... 644
K.3 Mobility management information elements....................................................................................... 646
K.4 Call control information elements. ...................................................................................................... 646
Annex M (normative): Additional Requirements for backward compatibility with PCS 1900
for NA revision 0 ME.................................................................................. 648
Annex N (informative): Change Record............................................................................................ 649
History ........................................................................................................................................................... 652
ETSI
28 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (http://www.etsi.org/ipr).
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 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 European Standard (Telecommunications series) has been produced by ETSI Technical Committee Special Mobile
Group (SMG), and is now submitted for the ETSI standards One-step Approval Procedure.
The present document specifies the procedures used at the radio interface (Reference Point Um, see GSM 04.02) for
Call Control (CC), Mobility Management (MM) and Radio Resource (RR) management within the digital cellular
telecommunications system.
The contents of the present document are subject to continuing work within SMG and may change following formal
SMG approval. Should SMG modify the contents of the present document it will then be re-submitted for OAP with an
identifying change of release date and an increase in version number as follows:
Version 7.x.y
where:
7 indicates GSM Release 1998 of Phase 2+
x the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,
etc.
y the third digit is incremented when editorial only changes have been incorporated in the specification.
Proposed national transposition dates
Date of latest announcement of this EN (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
ETSI
29 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 Release 96.
Feature Designator
BA Range IE handling $(impr-BA-range-handling)$
Advanced Speech Call Item $(ASCI)$
Call Completion Busy Subscriber $(CCBS)$
Mobile Assisted Frequency Allocation $(MAFA)$
Network Indication of Alerting in MS $(NIA)$
ETSI
30 draft ETSI EN 300 940 V7.7.0 (2000-04)
0 Scope
The present document specifies the procedures used at the radio interface (Reference Point Um, see GSM 04.02) for
Call Control (CC), Mobility Management (MM), Radio Resource (RR) management and Session Management (SM).
When the notations for "further study" or "FS" or "FFS" are present in the present document 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 GSM 04.03.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described
in general terms in GSM 04.07.
0.1 Scope of the Technical Specification
The procedures currently described in the present document 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.
GSM 04.10 contains functional procedures for support of supplementary services.
GSM 04.11 contains functional procedures for support of point-to-point short message services.
GSM 04.12 contains functional description of short message - cell broadcast.
GSM 04.60 contains procedures for radio link control and medium access control (RLC/MAC) of packet data physical
channels.
GSM 04.71 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.
0.2 Application to the interface structures
The layer 3 procedures apply to the interface structures defined in GSM 04.03. They use the functions and services
provided by layer 2 defined in GSM 04.05 and GSM 04.06. GSM 04.07 gives the general description of layer 3
including procedures, messages format and error handling.
0.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.
0.4 Test procedures
Test procedures of the GSM radio interface signalling are described in GSM 11.10 and GSM 11.2x series.
ETSI
31 draft ETSI EN 300 940 V7.7.0 (2000-04)
0.5 Use of logical channels
The logical control channels are defined in GSM 05.02. 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 GSM 04.06):
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 GSM 04.05 and GSM 04.06) as required for each individual message.
0.6 Overview of control procedures
0.6.1 List of procedures
The following procedures are specified in this Technical Specification:
a) Clause 3 specifies elementary procedures for Radio Resource management:
- system information broadcasting (subclause 3.2.2)
- RR connection establishment (subclause 3.3)
- entering the dedicated mode : immediate assignment procedure (subclause 3.3.1.1)
- paging procedure for RR connection establishment (subclause 3.3.2)
- notification procedure (subclause 3.3.3)
- Procedures in dedicated mode and in group transmit mode (subclause 3.4)
- measurement report procedure (subclause 3.4.1.2)
- intracell change of channels (subclause 3.4.3)
- intercell change of channels (subclause 3.4.4)
- frequency redefinition procedure (subclause 3.4.5)
ETSI
32 draft ETSI EN 300 940 V7.7.0 (2000-04)
- channel mode change procedure (subclause 3.4.6)
- ciphering mode setting procedure (subclause 3.4.7)
- additional channel assignment procedure (subclause 3.4.8)
- partial channel release procedure (subclause 3.4.9)
- radio resources connection release (subclause 3.4.13)
- specific RR procedures for voice broadcast channels and voice group call channels (subclause 3.4.15)
- application procedures (subclause 3.4.21)
- RR procedures on CCCH related to temporary block flow establishment (subclause 3.5)
- packet paging procedure using CCCH (subclause 3.5.1)
- packet access procedure using CCCH (subclause 3.5.2)
- packet downlink assignment procedure using CCCH (subclause 3.5.3)
- RR procedures on DCCH related to temporary block flow establishment
- Assignment to Packet Data Channel procedure (subclause 3.4.19)
- Network commanded cell reselection (subclause 3.4.20)
b) 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)
- 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)
ETSI
33 draft ETSI EN 300 940 V7.7.0 (2000-04)
- 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)
c) 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.1)
- PDP context modification (subclause 6.1.2)
- PDP context deactivation (subclause 6.1.3)
- anonymous PDP context activation (subclause 6.1.4)
- anonymous PDP context deactivation (subclause 6.1.5)
The elementary procedures can be combined to form structured procedures. Examples of such structured procedures are
given in clause 7. This part of the Technical Specification 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.
0.7 Applicability of implementations
The applicability of procedures of this technical specification for the mobile station is dependent on the services and
functions which are to be supported by a mobile station.
ETSI
34 draft ETSI EN 300 940 V7.7.0 (2000-04)
0.7.1 Voice Group Call Service (VGCS) and Voice Broadcast Service
(VBS)
For mobile stations supporting the Voice Group Call Service or the Voice Broadcast Service, it is explicitly mentioned
throughout this 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.
For VGCS and VBS, the following possible mobile station implementations exist:
- support of listening to voice broadcast calls (VBS listening)
- support of originating a voice broadcast call (VBS originating)
- support of listening to voice group calls (VGCS listening)
- support of talking in voice group calls (VGCS talking. This always includes the implementation for VGCS
listening)
- support of originating a voice group call (VGCS originating. This always includes the implementation for VGCS
talking)
Apart from the explicitly mentioned combinations, all possible combinations are optional and supported by this
technical specification.
The related terms are used in this technical specification, if information on these implementation options is required.
0.7.2 General Packet Radio Service (GPRS)
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 03.60 [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 MSs capabilities to operate GPRS and other GSM services simultaneously. Mobile
stations that are capable to operate GPRS services are referred to as GPRS MSs.
NOTE: Other GSM technical specifications may refer to the MS operation modes A, B, and C as GPRS 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 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.
ETSI
35 draft ETSI EN 300 940 V7.7.0 (2000-04)
A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 01.02: "Digital cellular telecommunications system (Phase 2+); General description of a
GSM Public Land Mobile Network (PLMN)".
[2] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and
acronyms".
[3] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS)
supported by a GSM Public Land Mobile Network (PLMN)".
[4] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a
GSM Public Land Mobile Network (PLMN)".
[5] GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects".
[6] GSM 02.11: "Digital cellular telecommunications system (Phase 2+); Service accessibility".
[7] GSM 02.17: "Digital cellular telecommunications system (Phase 2+); Subscriber identity modules
Functional characteristics".
[8] GSM 02.40: "Digital cellular telecommunications system (Phase 2+); Procedures for call progress
indications".
[9] GSM 03.01: "Digital cellular telecommunications system (Phase 2+); Network functions".
[10] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and
identification".
[11] GSM 03.13: "Digital cellular telecommunications system (Phase 2+); Discontinuous Reception
(DRX) in the GSM system".
[12] GSM 03.14: "Digital cellular telecommunications system (Phase 2+); Support of Dual Tone Multi-
Frequency signalling (DTMF) via the GSM system".
[12a] GSM 03.71: Digital cellular telecommunications system (Phase 2+); Location Services;
Functional description Stage 2.
[13] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network
functions".
[14] GSM 03.22: "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile
Station (MS) in idle mode".
[15] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile
Network (PLMN) access reference configuration".
[16] GSM 04.03: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base
Station System (MS - BSS) interface Channel structures and access capabilities".
[17] GSM 04.04: "Digital cellular telecommunications system (Phase 2+); layer 1 General
requirements".
[18] GSM 04.05: "Digital cellular telecommunications system (Phase 2+); Data Link (DL) layer
General aspects".
[19] GSM 04.06: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base
Station System (MS - BSS) interface Data Link (DL) layer specification".
[20] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface
signalling layer 3 General aspects".
ETSI
36 draft ETSI EN 300 940 V7.7.0 (2000-04)
[21] GSM 04.10: "Digital cellular telecommunications system ; Mobile radio interface layer 3
Supplementary services specification General aspects".
[22] GSM 04.11: "Digital cellular telecommunications system (Phase 2); Point-to-Point (PP) Short
Message Service (SMS) support on mobile radio interface".
[23] GSM 04.12: "Digital cellular telecommunications system (Phase 2+); Short Message Service Cell
Broadcast (SMSCB) support on the mobile radio interface".
[23a] GSM 04.71: Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer
3 location services specification.
[23b] GSM 04.31 Digital cellular telecommunication system (Phse 2+);Location Services;Mobile
Station (MS) Serving Mobile Location Centre (SMLC); Radio Resource LCS Protocol (RRLP).
[24] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer
3 supplementary services specification Formats and coding".
[25] GSM 04.81: "Digital cellular telecommunications system (Phase 2+); Line identification
supplementary services - Stage 3".
[26] GSM 04.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF)
[27] GSM 04.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call
Hold (HOLD) supplementary services - Stage 3".
[28] GSM 04.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY)
[29] GSM 04.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG)
[30] GSM 04.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC)
[31] GSM 04.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB)
[32] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple
access on the radio path".
[33] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and
reception".
[34] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link
control".
[35] GSM 05.10: "Digital cellular telecommunications system (Phase 2+); Radio subsystem
synchronization".
[36] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal
Adaptation Functions (TAF) for Mobile Stations (MS)".
[37] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part
(MAP) specification".
[38] GSM 09.07: "Digital cellular telecommunications system (Phase 2+); General requirements on
interworking between the Public Land Mobile Network (PLMN) and the Integrated Services
Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
[39] GSM 11.10: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS)
conformity specification".
ETSI
37 draft ETSI EN 300 940 V7.7.0 (2000-04)
[40] GSM 11.21: "Digital cellular telecommunications system (Phase 2); The GSM Base Station
System (BSS) 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 processing systems - Data communications - Network service
definition".
[44] CCITT Recommendation E.163: "Numbering plan for the international telephone service".
[45] CCITT Recommendation E.164: "Numbering plan for the ISDN era".
[46] CCITT Recommendation E.212: "Identification plan for land mobile stations".
[47] ITU-T Recommendation F.69 (1993): "Plan for telex destination codes".
[48] CCITT Recommendation I.330: "ISDN numbering and addressing principles".
[49] CCITT Recommendation I.440 (1989): "ISDN user-network interface data link layer - General
aspects".
[50] CCITT Recommendation I.450 (1989): "ISDN user-network interface layer 3 General aspects".
[51] ITU-T Recommendation I.500 (1993): "General structure of the ISDN interworking
recommendations".
[52] CCITT Recommendation T.50: "International Alphabet No. 5".
[53] CCITT Recommendation Q.931: ISDN user-network interface layer 3 specification for basic
control".
[54] CCITT Recommendation V.21: "300 bits per second duplex modem standardized for use in the
general switched telephone network".
[55] CCITT 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".
[56] CCITT 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] CCITT Recommendation V.23: "600/1200-baud modem standardized for use in the general
switched telephone network".
[58] CCITT 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] CCITT 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] CCITT Recommendation V.110: "Support of data terminal equipments (DTEs) with V-Series
interfaces by an integrated services digital network".
[61] CCITT Recommendation V.120: "Support by an ISDN of data terminal equipment with V-Series
type interfaces with provision for statistical multiplexing".
[62] CCITT Recommendation X.21: "Interface between data terminal equipment (DTE) and data
circuit-terminating equipment (DCE) for synchronous operation on public data networks".
ETSI
38 draft ETSI EN 300 940 V7.7.0 (2000-04)
circuit-terminating equipment (DCE) for terminals operating in the packet mode and connected to
public data networks by dedicated circuit".
[64] CCITT Recommendation X.28: "DTE/DCE interface for a start-stop mode data terminal
equipment accessing the packet assembly/disassembly facility (PAD) in a public data network
situated in the same country".
[65] CCITT 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] CCITT Recommendation X.31: "Support of packet mode terminal equipment by an ISDN".
circuit-terminating equipment (DCE) for terminals operating in the packet mode and accessing a
packet switched public data network through a public switched telephone network or an integrated
services digital network or a circuit switched public data network".
[68] CCITT Recommendation X.75 (1988): "Packet-switched signalling system between public
networks providing data transmission services".
[69] CCITT Recommendation X.121: "International numbering plan for public data networks".
[70] ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network interface layer 3
Specifications for basic call control".
[71] ETS 300 102-2: "Integrated Services Digital Network (ISDN); User-network interface layer 3
Specifications for basic call control".
[72] ISO/IEC10646: Universal Multiple-Octet Coded Character Set (UCS); UCS2, 16 bit coding.
[73] GSM 02.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio
Service (GPRS); Service Description; Stage 1".
Service (GPRS); Service Description; Stage 2".
Service (GPRS); Overall description of the GPRS radio interface; Stage 2".
Service (GPRS); Mobile Station - Base Station System (MS-BSS) interface; Radio Link Control
and Medium Access Control (RLC/MAC) layer specification".
[77] IETF RFC 1034: "Domain names - Concepts and Facilities " (STD 7).
Service (GPRS); Subnetwork Dependent Convergence Protocol (SNDCP)".
2 Definitions and abbreviations
Abbreviations used in this specification are listed in GSM 01.04
2.1 Random values
In a number of places in this Technical Specification, 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
ETSI
39 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 Vocabulary
The following terms are used in this Technical Specification:
- 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
listen to the BCCH of the serving cell as defined in GSM 03.22 and 05.08;
- 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 GSM 04.60.
- 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 0 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 GSM 04.60.
- RLC/MAC block: A RLC/MAC block is the protocol data unit exchanged between RLC/MAC entities, see
GSM 04.60.
- A GMM context is established when a GPRS attach procedure is successfully completed.
ETSI
40 draft ETSI EN 300 940 V7.7.0 (2000-04)
-- Network operation mode
The three different network operation modes I, II, and III are defined in GSM 03.60 [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 GSM 03.60 [74].
- Anonymous access refers to limited service provisioning to an MS whose identity is unknown in the network.
3 Radio Resource management procedures
3.1 Overview/General
3.1.1 General
Radio Resource management procedures include the functions related to the management of the common transmission
resources, e.g. the physical channels and the data link connections on control channels.
The general purpose of Radio Resource procedures is to establish, maintain and release RR connections that allow a
point-to-point dialogue between the network and a mobile station. This includes the cell selection/reselection and the
handover procedures. Moreover, Radio Resource management procedures include the reception of the uni-directional
BCCH and CCCH when no RR connection is established. This permits automatic cell selection/reselection.
If VGCS listening or VBS listening are supported, the radio resource management also includes the functions for the
reception of the voice group call channel or the voice broadcast channel, respectively, and the automatic cell reselection
of the mobile station in Group receive mode.
If VGCS talking is supported, the radio resource management also includes the functions for the seizure and release of
the voice group call channel.
If GPRS point-to-point services are supported, the radio resource management procedures includes functions related to
the management of transmission resources on packet data physical channels. This includes the broadcast of system
information to support a mobile station in packet idle and packet transfer modes, see also GSM 04.60.
NOTE 1: This chapter includes some procedures used for multislot operation and for the TCH/H + TCH/H
configuration which need not be supported by simple mobile stations.
NOTE 2: The procedures and the information content relating to the TCH/H + TCH/H configuration in RR
messages is for further study.
3.1.2 Services provided to upper layers
A RR connection is a physical connection used by the two peer entities to support the upper layers exchange of
information flows.
3.1.2.1 Idle mode
In idle mode no RR connection exists.
The RR procedures include (on the mobile station side) those for automatic cell selection/reselection. The RR entity
indicates to upper layers the unavailability of a BCCH/CCCH and the cell change when decided by the RR entity. Upper
layers are advised of the BCCH broadcast information when a new cell has been selected, or when a relevant part of this
information changes.
In Idle mode, upper layers can require the establishment of an RR connection.
ETSI
41 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.1.2.2 Dedicated mode
In dedicated mode, the RR connection is a physical point-to-point bi-directional connection, and includes a SAPI 0 data
link connection operating in multiframe mode on the main DCCH. If dedicated mode is established, RR procedures
provide the following services:
- establishment/release of multiframe mode on data link layer connections other than SAPI 0, on the main DCCH
or on the SACCH associated with the channel carrying the main signalling link;
- transfer of messages on any data link layer connection;
- indication of temporary unavailability of transmission (suspension, resuming);
- indication of loss of RR connection;
- automatic cell reselection and handover to maintain the RR connection;
- setting/change of the transmission mode on the physical channels, including change of type of channel, change of
the coding/decoding/transcoding mode and setting of ciphering;
- allocation/release of an additional channel (for the TCH/H + TCH/H configuration);
- allocation/release of additional channels for multislot operation;
- release of an RR connection.
3.1.2.3 Group receive mode
Only applicable for mobile stations supporting VGCS listening or VBS listening.
In this mode, the RR procedures on the mobile station side provide the services:
- local connection to the voice broadcast channel or voice group call channel;
- reception of messages in unacknowledged mode;
- automatic cell reselection for the mobile station in Group receive mode;
- local disconnection from the received voice group call or broadcast call channels.
For mobile stations supporting both VGCS listening and VGCS transmit, in addition, the RR procedures on the mobile
station side provide the service
- uplink access procedures to establish the RR connection.
3.1.2.4 Group transmit mode
Only applicable for mobile stations supporting VGCS talking.
In group transmit mode, the RR connection is a physical point-to-point bi-directional connection, and includes a SAPI 0
data link connection operating in multiframe mode on the main DCCH. If the group transmit mode is established, RR
procedures provide the following services:
- transfer of messages on the SAPI 0 of the data link layer connection;
- indication of loss of RR connection;
- automatic cell reselection and handover to maintain the RR connection;
- setting of the transmission mode on the physical channels, change of type of channel and setting of ciphering;
- release of the RR connection..
ETSI
42 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.1.2.5 Packet idle mode
Only applicable for mobile stations supporting GPRS.
In packet idle mode, no temporary block flow exists (see GSM 04.60). Upper layers may require the transfer of a LLC
PDU, which implicitly triggers the establishment of a temporary block flow.
3.1.2.6 Packet transfer mode
Only applicable for mobile stations supporting GPRS.
In packet transfer mode, the mobile station is allocated radio resource providing a temporary block flow on one or more
packet data physical channels. The RR sublayer provides the following services, see also GSM 04.60:
- transfer of LLC PDUs in acknowledged mode;
- transfer of LLC PDUs in unacknowledged mode;
Depending on the GPRS mode of operation (class A or B), the mobile station may leave both packet idle mode and
packet transfer mode before entering dedicated mode, group receive mode or group transmit mode.
Cell reselection in packet idle and packet transfer modes is specified in GSM 05.08. The RR entity on the mobile station
side indicates to the upper layers the availability of a cell and a cell change when decided by the RR sublayer. Upper
layers are advised of system information broadcast in the cell when a new cell has been selected, or when a relevant part
of this information changes.
3.1.3 Services required from data link and physical layers
The RR sublayer uses the services provided by the data link layer as defined in GSM 04.05.
Moreover, the RR sublayer directly uses services provided by the physical layer such as BCCH searching and transfer of
RLC/MAC blocks, as defined in GSM 04.04.
3.1.4 Change of dedicated channels
3.1.4.1 Change of dedicated channels using SAPI = 0
In case a change of dedicated channels is required using a dedicated assignment and handover procedure, respectively,
the RR sublayer will request the data link layer to suspend multiple frame operation before the mobile station leaves the
old channel. When the channel change has been completed, layer 3 will request the data link layer to resume multiple
frame operation again. The layer 2 suspend/resume procedures are described in GSM 04.05 and 04.06.
These procedures are specified in such a way that a loss of a layer 3 message cannot occur on the radio interface.
However, messages sent from the mobile station to the network may be duplicated by the data link layer if a message has
been transmitted but not yet completely acknowledged before the mobile station leaves the old channel (see
GSM 04.06).
As the RR sublayer is controlling the channel change, a duplication of RR messages does not occur. However, there are
some procedures for which a duplication is possible, e.g. DTMF procedures. For all upper layer procedures using the
transport service of the RR sub-layer (e.g., MM and CM procedures), the request messages sent by the mobile station
contain a sequence number in order to allow the network to detect duplicated messages, which are then ignored by the
network. The procedures for sequenced transmission on layer 3 are described in subclause 3.1.4.2.
3.1.4.2 Change of dedicated channels using other SAPIs than 0
For SAPIs other than 0, the data link procedures described in GSM 04.06 do not provide any guarantee against message
loss or duplication.
Therefore, if an application uses a SAPI other than 0 and if this application is sensitive to message loss or duplication,
then it has to define its own protection mechanism. No general protection mechanism is provided by the protocol
defined in this Technical Specification.
ETSI
43 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.1.4.3 Sequenced message transfer operation
Upper layer messages sent using the RR sub-layer transport service from the mobile station to the network can be
duplicated by the data link layer in the following case:
- a channel change of dedicated channels is required (assignment or handover procedure) and the last layer 2 frame
has not been acknowledged by the peer data link layer before the mobile station leaves the old channel.
In this case, the mobile station does not know whether the network has received the message correctly. Therefore, the
mobile station has to send the message again after the new dedicated channel is established (see GSM 04.06).
The network must be able to detect the duplicated received message. Therefore, each concerned upper layer message
must be marked with a send sequence number.
To allow for different termination points in the infrastructure of the messages of different PDs, the sequence numbering
is specific to each PD. For historical reasons, an exception is that messages sent with the CC, SS and MM PDs share the
same sequence numbering. In the following, the phrase upper layer message flow refers to a flow of messages sharing
the same sequence numbering. The different upper layer flows are MM+CC+SS, GCC, BCC, PDSS1 and PDSS2.
3.1.4.3.1 Variables and sequence numbers
3.1.4.3.1.1 Send state variable V(SD)
The RR sublayer of the mobile station shall have one associated send state variable V(SD) ("Send Duplicated") for each
upper layer message flow. The send state variable denotes the sequence number of the next in sequence numbered
message in the flow to be transmitted. The value of the corresponding send state variable shall be incremented by one
with each numbered message transmission. Arithmetic operations on V(SD) are performed modulo 2.
3.1.4.3.1.2 Send sequence number N(SD)
At the time when such a message to be numbered is designated for transmission, the value of N(SD) for the message to
be transferred is set equal to the value of the send state variable V(SD). See GSM 04.07.
3.1.4.3.2 Procedures for the initiation, transfer execution and termination of the sequenced
message transfer operation
3.1.4.3.2.1 Initiation
The sequenced message transfer operation is initiated by establishing a RR connection. The send state variables V(SD)
are set to 0.
3.1.4.3.2.2 Transfer Execution
The network must compare the send sequence numbers of pairs of subsequent messages in the same upper layer
messages flow. In case the send sequence numbers of two subsequent messages in a flow are not identical, no
duplication has occurred. In case the send sequence numbers are identical, the network must ignore the second one of
the received messages.
3.1.4.3.2.3 Termination
The sequenced message transfer operation is terminated by the RR connection release procedure.
3.1.5 Procedure for Service Request and Contention Resolution
Upon seizure of the assigned dedicated channel, the mobile station establishes the main signalling link on this channel
by sending a layer 2 SABM frame containing a layer 3 service request message. The data link layer will store this
message to perform the contention resolution. The service request message will be returned by the network in the UA
frame.
ETSI
44 draft ETSI EN 300 940 V7.7.0 (2000-04)
The data link layer in the mobile station compares the content of the information field (i.e. the layer 3 service request
message) received in the UA frame with the stored message and leaves the channel in case they do not match. This
procedure resolves contentions in the case where several mobile stations have accessed at the same random access slot
and with the same random reference and one has succeeded due to capture. The full description of the procedure is given
in GSM 04.06.
The purpose of the service request message is to indicate to the network which service the mobile station is requesting.
This then allows the network to decide how to proceed (e.g. to authenticate or not).
The service request message must contain the identity of the mobile station and may include further information which
can be sent without encryption.
ETSI
45 draft ETSI EN 300 940 V7.7.0 (2000-04)
The layer 3 service request message is typically one of the following:
- CM SERVICE REQUEST
- LOCATION UPDATING REQUEST
- IMSI DETACH
- PAGING RESPONSE
- CM RE-ESTABLISHMENT REQUEST
- NOTIFICATION RESPONSE
- IMMEDIATE SETUP
- RR INITIALISATION REQUEST
Mobile Station Network
+------------------------------------------+
SABM ("layer 3 service request message")
--------------------------------------->

UA ("layer 3 service request message")
<--------------------------------------
+------------------------------------------+
Figure 3.1/GSM 04.08 Service request and contention resolution
3.1.6 Preemption
The datalink layer provides the capability to assign a priority to any message transferred in dedicated mode on SAPI 0
with multiframe operation. The available message priorities defined in GSM 04.06 are high, normal and low.
Messages assigned a high priority are enabled to preempt, in the data link layer, all preceeding untransmitted and
partially transmitted messages assigned a low priority that are using the same data link connection (same SAPI and
logical channel). Messages or message portions that are preempted are discarded without notification to higher layers
except that the first 2*N201 octets of any partially transmitted message are not discarded. The following priority
assignments are defined for those Radio Resource, Mobility Management and Connection Management messages that
use SAPI 0.
ETSI
46 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 2.1/GSM 04.08: Priority Values of Layer 3 Messages
Priority Messages
Low RR Application Information message
Normal All MM messages
All CM messages
All other RR messages using SAPI 0 not listed
here
High RR Channel Establishment:
RR INITIALISATION REQUEST
ADDITIONAL ASSIGNMENT
IMMEDIATE ASSIGNMENT
IMMEDIATE ASSIGNMENT EXTENDED
IMMEDIATE ASSIGNMENT REJECT
RR Configuration Change:
CONFIGURATION CHANGE COMMAND
CONFIGURATION CHANGE ACK.
CONFIGURATION CHANGE REJECT
RR Handover related
ASSIGNMENT COMMAND
ASSIGNMENT COMPLETE
ASSIGNMENT FAILURE
HANDOVER COMMAND
HANDOVER COMPLETE
HANDOVER FAILURE
PHYSICAL INFORMATION
RR-CELL CHANGE ORDER
PDCH ASSIGNMENT COMMAND
RR Channel release
CHANNEL RELEASE
PARTIAL RELEASE
PARTIAL RELEASE COMPLETE
Use of the preemption capability by layer 3 is not required in a BSS or MS that does not send any low priority
message. In this case, all messages may be treated as having normal priority.
3.2 Idle mode procedures and general procedures in packet
idle and packet transfer modes
3.2.1 Mobile Station side
In idle mode, the MS listens to the BCCH and to the paging sub-channel for the paging group the MS belongs to in idle
mode (cf. GSM 03.13); it measures the radio propagation for connection with other cells.
In packet idle and packet transfer modes (applicable only to a GPRS mobile station), the mobile station listens to either
the PBCCH, if that is present in the cell, or BCCH. The requirements for the monitoring of system information is further
specified in GSM 04.60. Moreover, the mobile station measures the radio propagation for connection with other cells.
In packet idle mode (applicable only to a GPRS mobile station), the mobile station listens to the paging sub-channels on
the PCCCH or CCCH. Paging sub-channels are monitored according to the paging group determined for the mobile
station and its current discontinuous reception (DRX) mode. The determination of paging group for the mobile station is
defined in GSM 05.02. The DRX procedures are defined in GSM 04.60 and GSM 05.02.
Measurements are treated to assess the need of a cell change as specified in GSM 05.08. When the decision to change
cells is made, the mobile station switches to the BCCH or PBCCH of the new cell. The broadcast information is then
checked to verify the allowance to camp on this cell (cf. section 3.2.2). Dependent on the mobile station type and
configuration, the mobile station may be required to try to read further BCCH and PBCCH information. If allowed, the
cell change is confirmed, and the broadcast information is then treated for Mobility Management actions (cf. section 4).
Similarly, physical contexts are updated (list of neighbouring cells frequencies, thresholds for some actions, etc. (cf.
GSM 05.08 and section 3.2.2)).
ETSI
47 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.2.2 Network side
3.2.2.1 System information broadcasting
SYSTEM INFORMATION TYPE 2 to 4 messages, and optionally TYPE 1, 2bis, 2ter, 7, 8, 13, 16 and 17 and further
types are regularly broadcast by the network on the BCCH. Based on this information the mobile station is able to
decide whether and how it may gain access to the system via the current cell. The SYSTEM INFORMATION TYPE
2bis message shall be sent if and only if the EXT-IND bit in the Neighbour Cells Description IE in both the TYPE 2 and
TYPE 2bis messages indicates that each IE only carries part of the BA. SYSTEM INFORMATION TYPE 2ter message
shall be sent if and only if this is indicated in SYSTEM INFORMATION TYPE 3 message.
A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. GSM 05.05) may consider the
EXT-IND bit in the Neighbour Cells Description IE in the SYSTEM INFORMATION TYPE 2 message as a spare bit.
If it does so it shall assume that the information element carries the complete BA and it shall ignore any SYSTEM
INFORMATION TYPE 2bis and 2ter messages.
If the additional cell reselection parameters are broadcast then SYSTEM INFORMATION TYPE 3 message shall
always contain these parameters. In addition to SYSTEM INFORMATION TYPE 3 at least either SYSTEM
INFORMATION TYPE 4 or SYSTEM INFORMATION TYPE 7 and 8 messages shall contain these parameters too.
If additional SoLSA specific parameters are broadcast then SYSTEM INFORMATION TYPE 16 and 17 messages,
shall always contain these parameters. In addition to SYSTEM INFORMATION TYPE 16 and 17 messages at least
either SYSTEM INFORMATION TYPE 4 or SYSTEM INFORMATION TYPE 7 and 8 messages shall contain these
SoLSA specific parameters too.
The support of GPRS shall be indicated in SYSTEM INFORMATION TYPE 3 message. In addition, the support of
GPRS shall be indicated in either SYSTEM INFORMATION TYPE 4 or SYSTEM INFORMATION TYPE 7 and 8
messages. If GPRS is supported, SYSTEM INFORMATION TYPE 13 message shall be sent. SI 13 message shall not
be sent if GPRS is not supported. Additional requirements for the broadcast of system information in a cell supporting
GPRS are specified in GSM 04.60.
NOTE 1: The allowed scheduling of SYSTEM INFORMATION messages on the BCCH are specified in
GSM 05.02.
NOTE 2: The network should take into account limitations of certain mobile stations to understand SYSTEM
INFORMATION TYPE 2bis, TYPE 2ter, the EXT-IND bit in the Neighbour Cells Description, the
indication of 2ter in SYSTEM INFORMATION TYPE 3 and formats used in the Neighbour Cells
Description IE and Cell Channel Description IE used in SYSTEM INFORMATION messages, see this
section, section 10.5.2.1b, and section 10.5.2.22.
NOTE 3: The network should take into account the limitations of earlier version of mobile equipments to
understand the 3-digit MNC format of the location area identification, see section 10.5.1.3.
The information broadcast may be grouped in the following classes:
- information giving unique identification of the current network, location area and cell;
- information used for candidate cell measurements for handover and cell selection procedures;
- information describing the current control channel structure;
- information controlling the random access channel utilization;
- information defining different options supported within the cell; and
- information about the length of the part of the message belonging to the phase 1 protocol.
The network may send to the mobile station BCCH scheduling information as specified below:
1) The BCCH scheduling information may be contained in the SYSTEM INFORMATION TYPE 9 messages. If so,
SYSTEM INFORMATION TYPE 3 specifies where to find SYSTEM INFORMATION TYPE 9 messages
carrying BCCH scheduling information.
ETSI
48 draft ETSI EN 300 940 V7.7.0 (2000-04)
2) If the mobile station has received BCCH scheduling information, it shall assume that this BCCH scheduling
information is valid in the location area until new scheduling information is received. It may store the information
in the ME and assume its validity after switch on in the same location area.
3) The network need not indicate the schedule of all SYSTEM INFORMATION messages in SYSTEM
INFORMATION 9. For any System Information message, the MS shall monitor all blocks specified in GSM
05.02 for that System Information message and all blocks specified in the SYSTEM INFORMATION TYPE 9
message for that System Information message.
4) When the mobile station detects that the BCCH information is not scheduled as defined in the last received SI 9
message, it shall read the SYSTEM INFORMATION TYPE 3 message. If presence of BCCH scheduling
information in SYSTEM INFORMATION TYPE 9 message is indicated, it shall try to read the information and
continue as in 2 above. If presence of BCCH scheduling information in SYSTEM INFORMATION TYPE 9
message is not indicated, it shall assume that there is no valid BCCH scheduling information.
3.2.2.2 Paging
The network is required to send valid layer 3 messages continuously on all paging subchannels on CCCH.
3.3 RR connection establishment
3.3.1 RR connection establishment initiated by the mobile station
The purpose of the immediate assignment procedure is to establish an RR connection between the mobile station and the
network.
3.3.1.1 Entering the dedicated mode : immediate assignment procedure
The immediate assignment procedure can only be initiated by the RR entity of the mobile station. Initiation is triggered
by request from the MM sublayer or LLC layer to enter the dedicated mode or by the RR entity in response to a
PAGING REQUEST message or to initiate a notification response procedure. Upon such a request,
- if access to the network is allowed (as defined in 3.3.1.1.1), the RR entity of the mobile station initiates the
immediate assignment procedure as defined in section 3.3.1.1.2;
- otherwise, it rejects the request.
The request from the MM sublayer to establish an RR connection specifies an establishment cause. Similarly, the
request from the RR entity to establish a RR connection in response to a PAGING REQUEST 1, 2 or 3 message
specifies one of the establishment causes "answer to paging"; the request from the RR entity to establish an RR
connection in order to initiate a notification response procedure specifies one of the establishment causes " procedures
that can be completed with a SDCCH".
3.3.1.1.1 Permission to access the network
All mobile stations with an inserted SIM are members of one out of 10 access classes numbered 0 to 9. The access class
number is stored in the SIM. In addition, mobile stations may be members of one or more out of 5 special access classes
(access classes 11 to 15) (see GSM 02.11), this is also held on the SIM card.
The system information messages on the BCCH broadcast the list of authorized access classes and authorized special
access classes in the system information messages, and whether emergency calls are allowed in the cell to all mobile
stations or only to the members of authorized special access classes.
If the establishment cause for the request of the MM sublayer is not "emergency call", access to the network is allowed
if and only if the mobile station is a member of at least one authorized:
- access class; or
- special access class.
ETSI
49 draft ETSI EN 300 940 V7.7.0 (2000-04)
If the establishment cause for the request of the MM sublayer is "emergency call", access to the network is allowed if
and only if:
- emergency calls are allowed to all mobile stations in the cell; or
- the mobile station is a member of at least one authorized special access class.
3.3.1.1.2 Initiation of the immediate assignment procedure
The RR entity of the mobile station initiates the immediate assignment procedure by scheduling the sending on the
RACH and leaving idle mode (in particular, the mobile station shall ignore PAGING REQUEST messages).
It then sends maximally M + 1 CHANNEL REQUEST messages on the RACH in a way such that:
- the number of slots belonging to the mobile stations RACH between initiation of the immediate assignment
procedure and the first CHANNEL REQUEST message (excluding the slot containing the message itself) is a
random value drawn randomly for each new initial assignment initiation with uniform probability distribution in
the set {0, 1, ..., max (T,8) - 1};
- the number of slots belonging to the mobile stations RACH between two successive CHANNEL REQUEST
messages (excluding the slots containing the messages themselves) is a random value drawn randomly for each
new transmission with uniform probability distribution in the set
{S, S + 1, ..., S + T - 1};
Here, T is the value of the parameter "Tx-integer" broadcast on the BCCH;
M is the value of the parameter "max retrans" broadcast on the BCCH;
S is a parameter depending on the CCCH configuration and on the value of Tx-integer as defined in
table 3.1/GSM 04.08.
The CHANNEL REQUEST messages are sent on the RACH (cf. section 1.5) and contain as parameters:
- an establishment cause which corresponds to the establishment cause given by the MM sublayer and the
broadcast NECI value, or which corresponds to one of the establishment causes "answer to paging" given by the
RR entity in response to a PAGING REQUEST message including the Channel Needed information, or which
corresponds to one of the establishment causes " procedures that can be completed with a SDCCH" given by the
RR entity in order to initiate a notification response procedure;
- a random reference which is drawn randomly from a uniform probability distribution for every new transmission.
After sending the first CHANNEL REQUEST message, the mobile station shall start listening to the BCCH; it shall also
listen to the full downlink CCCH timeslot corresponding to its CCCH group.
Having sent M + 1 CHANNEL REQUEST messages, the RR entity of the mobile station starts timer T3126. At expiry
of timer T3126, the immediate assignment procedure is aborted; if the immediate assignment procedure was triggered by
a request from the MM sublayer, a random access failure is indicated to the MM sublayer.
Table 3.1/GSM 04.08: Values of parameter S
TX-integer non combined CCCH combined CCH/SDCCH
3, 8, 14, 50 55 41
4, 9, 16 76 52
5, 10, 20 109 58
6, 11, 25 163 86
7, 12, 32 217 115
3.3.1.1.3 Answer from the network
3.3.1.1.3.1 On receipt of a CHANNEL REQUEST message
The network may allocate a dedicated channel to the mobile station by sending an IMMEDIATE ASSIGNMENT
message or IMMEDIATE ASSIGNMENT EXTENDED message in unacknowledged mode on the same CCCH timeslot
ETSI
50 draft ETSI EN 300 940 V7.7.0 (2000-04)
on which it has received the CHANNEL REQUEST. There is no further restriction on what part of the downlink CCCH
an IMMEDIATE ASSIGNMENT message or IMMEDIATE ASSIGNMENT EXTENDED message can be sent. The
type of channel allocated (SDCCH or TCH; the channel mode shall be set to signalling only) is a network operator
decision. Timer T3101 is then started on the network side.
NOTE: There are two types of immediate assignment messages:
- IMMEDIATE ASSIGNMENT message, containing assignment information for one mobile station
only;
- IMMEDIATE ASSIGNMENT EXTENDED message, containing assignment information for two
mobile stations at the same time.
The IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED message contains:
- the description of the assigned channel;
- the information field of the CHANNEL REQUEST message and the frame number of the frame in which the
CHANNEL REQUEST message was received;
- the initial timing advance (cf. GSM 04.04);
- optionally, a starting time indication.
If frequency hopping is applied, the mobile station uses the last CA received on the BCCH to decode the Mobile
Allocation.
On receipt of an IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED message corresponding
to one of its 3 last CHANNEL REQUEST messages, the mobile station stops T3126 (if running), stops sending
CHANNEL REQUEST messages, switches to the assigned channels, sets the channel mode to signalling only and
activates the assigned channels. It then establishes the main signalling link with an SABM containing an information
field (see section 3.1.5).
An IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED message may indicate a frequency
change in progress, with a starting time and possibly alternative channel descriptions.
In the case of the reception of an IMMEDIATE ASSIGNMENT EXTENDED message, or of an IMMEDIATE
ASSIGNMENT message which contains only the description of a channel to be used after the starting time, the mobile
station shall wait up to the starting time before accessing the channel. If the starting time has already elapsed, the mobile
shall access the channel as an immediate reaction to the reception of the message (see GSM 05.10 for the timing
constraints).
If the message contains both the description of a channel to be used after the indicated time and of a channel to be used
before, the mobile station accesses a channel as an immediate reaction to the reception of the message. If the moment the
mobile station is ready to access is before the indicated time, the mobile station accesses the channels described for
before the starting time. The mobile station then changes to the channel described for after the starting time at the
indicated time. New parameters can be frequency list and MAIO. Other parameters describing the channel to be used
before the starting time are taken from the description of the channel defined for use after the starting time. If the
moment the mobile station is ready to access is after the starting time, the mobile station accesses the channel described
for after the starting time.
If frequency hopping is applied, the mobile station uses the last CA received on the BCCH.
3.3.1.1.3.2 Assignment rejection
If no channel is available for assignment, the network may send to the mobile station an IMMEDIATE ASSIGNMENT
REJECT message in unacknowledged mode on the same CCCH timeslot on which the channel request message was
received. There is no further restriction on what part of the downlink CCCH timeslot an IMMEDIATE ASSIGNMENT
REJECT message can be sent. This message contains the request reference and a wait indication.
On receipt of an IMMEDIATE ASSIGNMENT REJECT message corresponding to one of its 3 last CHANNEL
REQUEST messages, the mobile station, stops sending CHANNEL REQUEST messages, starts timer T3122 with the
indicated value, ("wait indication" information element), starts T3126 if it has not already been started, and listens to the
downlink CCCH until T3126 expires. During this time, additional IMMEDIATE ASSIGNMENT REJECT messages are
ETSI
51 draft ETSI EN 300 940 V7.7.0 (2000-04)
ignored, but any immediate assignment corresponding to any other of its 3 last CHANNEL REQUEST messages make
the mobile station follow the procedure in section 3.3.1.2. If no such immediate assignment is received, the mobile
station returns to CCCH idle mode (listening to its paging channel).
As an option the mobile station may return to CCCH idle mode as soon as it has received responses from the network on
all, or in case more than 3 were sent the last 3, of its CHANNEL REQUEST messages.
The mobile station is not allowed to make a new attempt to establish a non emergency RR connection in the same cell
until T3122 expires. Provided that an IMMEDIATE ASSIGNMENT REJECT message has not been received for an
emergency RR connection attempt, the mobile station may attempt to enter the dedicated mode for an emergency call in
the same cell before T3122 has expired.
The Wait Indication IE (i.e. T3122) relates to the cell from which it was received.
The mobile station in packet idle mode (only applicable to mobile station supporting GPRS) may initiate packet access
in the same cell before T3122 has expired, see GSM 04.60 and section 3.5.2.1.3.4.
After T3122 expiry, no CHANNEL REQUEST message shall be sent as a response to a page until a PAGING
REQUEST message for the mobile station is received.
3.3.1.1.4 Assignment completion
The immediate assignment procedure is terminated on the network side when the main signalling link is established.
Timer T3101 is stopped and the MM sublayer on the network side is informed that the RR entity has entered the
dedicated mode.
On the mobile station side, the procedure is terminated when the establishment of the main signalling link is confirmed.
The MM sublayer is informed that the RR entity has entered the dedicated mode.
3.3.1.1.4.1 Early classmark sending
Early classmark sending consists in the mobile station sending as early as possible after access a CLASSMARK
CHANGE message to provide the network with additional classmark information.
A mobile station which implements the Controlled Early Classmark Sending option shall perform the early
classmark sending if and only if explicitly accepted by the network, as indicated in the last reception in the accessed cell
of the SYSTEM INFORMATION TYPE 3 message.
A mobile station which implements one or more of the multiple band support options shall also implement the
Controlled Early Classmark Sending option.
A mobile station which implements the multislot capability option shall also implement the Controlled Early
Classmark Sending option.
A mobile station that implements some form of treatment of UCS2 alphabet (see TS GSM 03.38) encoded character
string (e.g., in short message, or in USSD string) may indicate so in the classmark. (An example is a Mobile Equipment
able to display UCS2 encoded character string.) In such a case, it should also implement the Controlled Early
Classmark Sending option. It is the mobile station responsibility to provide the UCS2 support information in due time.
If the network needs this information and the mobile station did not provide it, the network may assume that the Mobile
Equipment does not support UCS2.
A mobile station which implements the R-GSM band (see GSM 05.05) shall also implement the Controlled Early
A mobile station which implements the extended measurement function shall also implement the Controlled Early
A mobile station which implements the GPRS option shall also implement the Controlled Early Classmark Sending
option.
A mobile station which implements the SoLSA option shall also implement the Controlled Early Classmark
Sending option.
ETSI
52 draft ETSI EN 300 940 V7.7.0 (2000-04)
A mobile station which implements the LCS option shall also implement the Controlled Early Classmark Sending
option.
A mobile station which implements the Controlled Early Classmark Sending option shall indicate it in the classmark
(ES IND bit).
3.3.1.1.4.2 GPRS suspension procedure
This procedure enables the network to suspend GPRS services packet flow in the downlink direction.
The GPRS suspension procedure is initiated by the mobile station by sending a GPRS SUSPENSION REQUEST
message. This can be done as early as possible after access but shall be done after sending a CLASSMARK CHANGE
message. The RR sublayer of the mobile station shall indicate a RR GPRS suspend condition to the MM sublayer, see
section 4.
When a mobile station which is IMSI attached for GPRS services (section 4) enters the dedicated mode, and when the
mobile station limitations make it unable to handle both dedicated mode and either packet idle mode or packet transfer
mode simultaneously, the mobile station shall perform the GPRS suspension procedure.
3.3.1.1.5 Abnormal cases
If a lower layer failure occurs on the mobile station side on the new channel before the successful establishment of the
main signalling link, the allocated channels are released; the subsequent behaviour of the mobile station depends on the
type of failure and previous actions.
- If the failure is due to information field mismatch in the contention resolution procedure, see section 3.1.5, and
no repetition as described in this paragraph has been performed, the immediate assignment procedure shall be
repeated.
- If the failure is due to any other reason or if a repetition triggered by a contention resolution failure has been
performed. The mobile station returns to idle mode (RR connection establishment failure), transactions in
progress are aborted and cell reselection then may take place.
If the information available in the mobile station, after the reception of an IMMEDIATE ASSIGNMENT message does
not satisfactorily define a channel, an RR connection establishment failure has occurred.
If the Mobile Allocation IE indexes frequencies in more than one frequency band then a RR connection establishment
failure has occurred.
If an IMMEDIATE ASSIGNMENT message indicates (a) channel(s) in a different frequency band to which the
CHANNEL REQUEST message was sent then, if the frequency band is supported by the mobile station, the mobile
station shall access the indicated channel(s) with the same power control level as used for the CHANNEL REQUEST
message.
If an IMMEDIATE ASSIGNMENT message indicates a channel in non-supported frequency band then a RR
connection establishment failure has occurred.
On the network side, if timer T3101 elapses before the main signalling link is established, the newly allocated channels
are released and the request is forgotten. Note that the network has no means to distinguish repeated attempts from
initial attempts from a mobile station.
3.3.1.2 Entering the group transmit mode: uplink access procedure
Only applicable for mobile stations supporting VGCS transmit .
The purpose of the uplink control procedure is to establish an RR connection on a VGCS channel between a mobile
station which is in group receive mode on that channel and the network.
The mobile station enters the group transmit mode when a successful establishment of the RR connection is indicated.
The channel mode assumed by the mobile station is the one derived from the channel description.
ETSI
53 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.3.1.2.1 Mobile station side
3.3.1.2.1.1 Uplink investigation procedure
The mobile station in group receive mode shall consider the uplink as free if the last message indicating the uplink as
being free was received less than 480 ms ago and if no UPLINK BUSY message has been received since the last
message indicating the uplink as free.
On receipt of a request from the upper layer to access the uplink and if the uplink is not free, the mobile station starts the
timer T3128.
If the uplink is free or becomes free before expiry of timer T3128, then the uplink investigation procedure is terminated,
the mobile station shall stop T3128, and start the uplink access procedure.
NOTE: The start of the uplink access procedure is not subject to the access class of the mobile station.
If the uplink is not indicated free before the timer expires, the mobile station shall remain in the group receive mode and
indicate a reject of the uplink request to the upper layer.
3.3.1.2.1.2 Uplink access procedure
The mobile station shall send UPLINK ACCESS messages on the voice group call channel with the appropriate
establishment cause. The first UPLINK ACCESS message shall be transmitted by the mobile station with a random
delay between 0 and 20ms. The UPLINK ACCESS messages shall be repeated after a further period of 100ms plus a
random delay between 0 and 20ms.
If an uplink identity code (UIC) of the current cell has been provided by the network in the UPLINK FREE message, the
mobile station shall use this UIC IE for the coding of the UPLINK ACCESS messages (see GSM 05.03). If no UIC is
provided, the mobile station shall use the BSIC received from the current cell, for instance from the initial
synchronization.
Having sent the first UPLINK ACCESS message, the mobile station starts timer T3130. At expiry of timer T3130, the
mobile station shall repeat the same procedure if the uplink is free. A maximum of three attempts is allowed and after
that a rejection of the uplink request is indicated to the upper layers.
If no VGCS UPLINK GRANT or UPLINK BUSY message is received by the mobile station 480 ms after having sent
the first UPLINK ACCESS message, the mobile station shall stop sending UPLINK ACCESS messages and wait in
order to receive a VGCS UPLINK GRANT or UPLINK BUSY message.
On receipt of an VGCS UPLINK GRANT message corresponding to one of its UPLINK ACCESS messages, the mobile
station stops T3130, stops sending UPLINK ACCESS messages, and establishes the main signalling link with an SABM
containing the TALKER INDICATION message in the information field. Early classmark sending shall be performed if
applicable. If a UA is received containing the message sent, the mobile station enters the group transmit mode and
indicates the successful seizure of the uplink to the upper layer. If a UA is received with a message different from the
message sent, the mobile station shall remain in the group receive mode and indicate the rejection of the uplink request
to the upper layers.
When receiving an UPLINK BUSY message or a VGCS UPLINK GRANT message aimed to another mobile station
(i.e., not corresponding to one of its UPLINK ACCESS messages), the mobile station stops T3130 and stops sending
UPLINK ACCESS messages. The mobile shall remain in the group receive mode and shall indicate a rejection of the
uplink request to the upper layers.
3.3.1.2.2 Network side
On receipt of an UPLINK ACCESS message the network shall perform, if necessary, contention resolution and grant the
uplink to one mobile station by sending a VGCS UPLINK GRANT message to the mobile station in unacknowledged
mode on the main signalling link. Furthermore, the network shall provide UPLINK BUSY messages on the main
signalling link in all cells of the group call area. After having sent the first message, the network starts T3115. If the
timer expires before the reception of a correctly decoded frame from the MS, the network repeats the VGCS UPLINK
GRANT message to the mobile station. If the VGCS UPLINK GRANT message has been repeated Ny2 times without a
correctly decoded frame being received from the MS, the network shall stop sending VGCS UPLINK GRANT messages
and provide an UPLINK FREE message on the main signalling channel and wait for a new UPLINK ACCESS message.
ETSI
54 draft ETSI EN 300 940 V7.7.0 (2000-04)
The correct decoding of a frame means that the decoding algorithm and the error detection tests, if any, indicate no
error.
After the data link layer is established, the RR entity of the network shall analyse the TALKER INDICATION message
received from the mobile station, adapt the RR procedures to the new classmark if necessary and provide the mobile
subscriber identity to the upper layer.
If a lower link failure has occurred or an indication of the release of the data link layer was provided by the lower layer
and no RR release request was previously received from the upper layer, the network shall provide an UPLINK FREE
message on the main signalling channel and wait for a new UPLINK ACCESS message.
3.3.1.3 Dedicated mode and GPRS
A mobile station whose Channel Request message contained a packet access establishment cause may receive an
Immediate Assignment message to a Channel which is to be used in dedicated mode. A mobile station supporting the
<<GPRS>> option shall obey this command. When establishing the main signalling link the information field in the
SABM shall contain an RR INITIALISATION REQUEST message.
This message contains:
TLLI,
MS Classmark type 2
Ciphering Key Sequence Number
MAC Mode and Channel Coding Requested
Channel Request Description
Following a successful contention resolution procedure, the mobile station shall implement the Early Classmark Sending
option. Then, the upper layers in the mobile station shall wait for commands from the network, eg for the allocation of a
GPRS resource.
While on the dedicated channel the mobile station shall obey the RR management procedures of 04.08, in particular the
mobile station shall send measurement reports on the SACCH.
3.3.2 Paging procedure for RR connection establishment
The network can initiate the establishment of an RR connection by the paging procedure for RR connection
establishment. Such a procedure can only be initiated by the network.
3.3.2.1 Paging initiation by the network
The network initiates the paging procedure to trigger RR connection establishment by broadcasting a paging request
message on the appropriate paging subchannel on CCCH or PCCCH, and starts timer T3113. The paging subchannels
on CCCH and PCCCH are specified in GSM 05.02 and GSM 03.13.
The network may also send paging related information on PACCH to a mobile station in packet transfer mode, see
section 3.3.2.1.3.
The network may also broadcast paging related information on any voice broadcast or voice group call channel
downlink.
3.3.2.1.1 Paging initiation using paging subchannel on CCCH
Paging initiation using the paging subchannel on CCCH is used when sending paging information to a mobile station in
idle mode. It is also used when sending paging information to a mobile station in packet idle mode, if PCCCH is not
present in the cell.
ETSI
55 draft ETSI EN 300 940 V7.7.0 (2000-04)
NOTE 1: There are 3 types of paging messages which may be used on CCCH:
- PAGING REQUEST TYPE 1;
- PAGING REQUEST TYPE 2; and
- PAGING REQUEST TYPE 3.
In a PAGING REQUEST message on CCCH to trigger RR connection establishment, the mobile station shall be
identified by the TMSI (non-GPRS TMSI) or its IMSI. If the mobile station is identified by the TMSI, it shall proceed
as specified in section 3.3.2.2.
If the mobile station in packet idle mode is identified by its IMSI, it shall parse the message for a corresponding Packet
Page Indication field:
- if the Packet Page Indication field indicates a paging procedure for RR connection establishment, or the field
is not present in the message, the mobile station shall proceed as specified in section 3.3.2.2;
- if the Packet Page Indication field indicates a packet paging procedure, the mobile station shall proceed as
specified in section 3.5.1.2.
A PAGING REQUEST message on CCCH includes for each mobile station that is paged to trigger RR connection
establishment an indication which defines how mobiles of different capabilities shall code the establishment cause field
in the CHANNEL REQUEST message. The information received in the CHANNEL REQUEST can be used by the
network to assign a suitable channel.
A PAGING REQUEST message on CCCH may include more than one mobile station identification.
A PAGING REQUEST TYPE 1 message on CCCH may have additionally a notification message coded in the P1 rest
octets information element.
A PAGING REQUEST message on CCCH may also include priority levels related to the mobile station identifications.
A mobile station in group receive mode supporting eMLPP shall take into account this information to decide whether to
respond to this PAGING REQUEST and, if the call is answered, the mobile station shall store the priority level for the
duration of the call. A mobile station not supporting eMLPP shall ignore this information element when received in a
PAGING REQUEST message.
NOTE 2: A mobile station not supporting VGCS or VBS may ignore this information element when received in a
PAGING REQUEST message, since the priority level is also provided in the SETUP message.
If VGCS or VBS is supported by the network and the network supports reduced NCH monitoring, messages sent on the
PCH may also include an indication of the change of the information sent on the NCH (see section 3.3.3.2).
The choice of the message type depends on the number of mobile stations to be paged and of the types of identities that
are used. The maximum number of paged mobile stations per message is 4 when using only TMSIs for identification of
the mobile stations.
The mobile station in idle mode is required to receive and analyse the paging messages and immediate assignment
messages sent on the paging subchannel corresponding to its paging subgroup, as specified in GSM 05.02.
NOTE 3: The possible immediate assignment messages are: the IMMEDIATE ASSIGNMENT, the IMMEDIATE
ASSIGNMENT EXTENDED and the IMMEDIATE ASSIGNMENT REJECT messages.
The paging and immediate assignment type messages contain a page mode information element. This information
element controls possible additional requirements on mobile stations belonging to the paging subgroup corresponding to
the paging subchannel the message was sent on. This implies that a given mobile station shall take into account the page
mode information element of any message sent on its own paging subchannel whatever the nature of this message
(paging messages or immediate assignment messages). This further implies that the mobile station does not take into
account page mode information element of messages sent on paging subchannels other than its own paging subchannel.
The requirements yielded by the page mode information element are as follows:
a) normal paging: no additional requirements;
b) extended paging: the mobile station is required in addition to receive and analyse the next but one message on the
PCH;
ETSI
56 draft ETSI EN 300 940 V7.7.0 (2000-04)
c) paging reorganization: The mobile station shall receive all messages on the CCCH regardless of the BS-AG-
BLKS-RES setting. It is required to receive all BCCH messages. When the mobile station receives the next
message to its (possibly new) paging subgroup the subsequent action is defined in the page mode information
element in that message.
d) same as before: No change of page mode from the previous page mode.
Note that a mobile station takes into account the page mode information only in messages of its own paging subchannel
whatever the currently applied requirements (a, b, c or d).
When the mobile station selects a new PCH, the initial page mode in the mobile station shall be set to paging
reorganization. If a message in the paging subchannel is not received correctly, the message is ignored and the previous
page mode is assumed.
3.3.2.1.2 Paging initiation using paging subchannel on PCCCH
Paging initiation using a paging subchannel on PCCCH, see GSM 04.60, applies when sending paging information to a
mobile station in packet idle mode and PCCCH is provided in the cell.
The paging initiation procedure and the paging request message used on PCCCH are specified in GSM 04.60.
3.3.2.1.3 Paging initiation using PACCH
Paging initiation using PACCH, see GSM 04.60, applies to a mobile station in packet transfer mode.
The paging initiation procedure and the message used to carry paging related information on PACCH are specified in
GSM 04.60.
3.3.2.2 Paging response
Upon receipt of a paging request message, or other message containing information to trigger the establishment of a RR
connection, and if access to the network is allowed, the addressed mobile station shall, when camped on a cell as
specified in GSM 03.22, initiate the immediate assignment procedure as specified in 3.3.1. The establishment of the
main signalling link is then initiated by use of an SABM with information field containing the PAGING RESPONSE
message (see section 3.1.5). The MM sublayer in the mobile station is informed that the RR entity has entered the
dedicated mode.
Upon receipt of the PAGING RESPONSE message the network stops timer T3113. The MM sublayer in the network is
informed that an RR connection exists.
3.3.2.3 Abnormal cases
Lower layer failure occurring during the immediate assignment procedure is treated as specified for that procedure.
If timer T3113 expires and a PAGING RESPONSE message has not been received, the network may repeat the paging
request message and start timer T3113 again. The number of successive paging attempts is a network dependent choice.
mobile station network
PAGING REQUEST
<------------------------- Start T3113
RANDOM ACCESS
------------------------->
IMM ASSIGN
<------------------------- Start T3101
SABM (PAGING RESPONSE)
-------------------------> Stop T3101,
T3113
Figure 3.2/GSM 04.08 Paging sequence
ETSI
57 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.3.3 Notification procedure
The support of notification procedure is mandatory for mobile stations supporting VGCS receive and/or VBS
receive .
The network informs the mobile station of starting or on-going voice broadcast calls and voice group calls with the
notification procedure.
In cases where the mobile station has initiated a VGCS call, if the channel mode modify procedure is applied to turn the
dedicated channel into a VGCS channel and ciphering may be applied for that call, in this case the network should
suspend transmission of notification messages until ciphering with the group cipher key has started on the dedicated
channel.
3.3.3.1 Notification of a call
The mobile station may receive a notification that a voice broadcast call or a voice group call is established.
Notifications may be sent on the NCH, on the PCH, or on the FACCH when in dedicated mode or group receive mode.
The presence of an NCH is indicated on the PCH in the Pi Rest Octets IE. A notification contains the group call
reference and possibly other related information. This notification may be contained:
- in a NOTIFICATION/NCH message sent on the NCH to notify mobile stations of VBS or VGCS calls in the
current cell, possibly together with a description of the related VBS or VGCS channel;
- in a NOTIFICATION/FACCH message sent in unacknowledged mode on the main DCCH to notify mobile
stations in dedicated mode or on the main DCCH of a VGCS or VBS channel, of other VBS or VGCS calls in the
current cell, possibly together with a description of the related VBS or VGCS channel.
- in the rest octets part of a PAGING REQUEST TYPE 1 message.
A mobile station supporting neither VGCS listening nor VBS listening may ignore the notifications sent on the NCH or
PCH. It may also ignore the notifications sent on the main DCCH except that a RR-STATUS message shall be sent to
the network with cause #97, "message not existent or not implemented".
Upon receipt of every notification message a mobile station supporting VGCS listening or VBS listening shall give an
indication containing the notified group call reference(s) to upper layers in the mobile station which may then decide:
- not to react on the notification, or
- join the voice broadcast call or the voice group call, if needed after having stopped on going activities.
3.3.3.2 Joining a VGCS or VBS call
In order to join a VGCS or a VBS call the following procedures apply.
In this subclause, the term notification refers to the notification which has triggered the decision to join a VGCS or
VBS call.
If the notification on the main DCCH concerns a VBS or VGCS in the current cell and does not contain a description of
the VGCS or VBS channel, the mobile station shall read the corresponding notification on the NCH.
If the description of the VGCS or VBS channel was included in the notification for the current cell, RR connection
establishment shall not be initiated, instead, the mobile station shall enter the group receive mode.
If no description for the VGCS or VBS channel is included in the notification, the mobile station shall establish a RR
connection in dedicated mode in order to initiate the notification response procedure.
3.3.3.3 Reduced NCH monitoring mechanism
This section applies to mobile stations which read the NCH in idle mode in order to receive the notification messages for
the voice broadcast call and the voice group call, which read the PCH to receive pagings and which aim at reducing the
reception load.
ETSI
58 draft ETSI EN 300 940 V7.7.0 (2000-04)
A reduced NCH monitoring mechanism may be used on the NCH. When the mobile station in idle mode enters a cell
and deduces from the BCCH that an NCH is present, it shall read the NCH until it has received at least two messages on
the NCH indicating NLN, with the two last received NLN being identical. Then it may stop reading the NCH until it
receives on the PCH an NLN(PCH) different from the last previously received NLN or on the SACCH an
NLN(SACCH) different from the last previously received NLN..
A mobile is able to determine the reduced NCH monitoring is active in the network if it receives an NLN in any
message. Once received, the mobile shall assume that NCH monitoring is active for a certain period of time which is not
specified.
For this, parameters are provided:
- NLN: Notification List Number;
The NLN is a modulo 4 counter which is changed every time a notification for a new VGCS or VBS call is
started on the NCH. If the reduced NCH monitoring is indicated, the NLN provides information on new
notifications provided on the NCH.
- NLN status :
The NLN status is a single bit field which indicates the status of the content of the NOTIFICATION/NCH
messages for a particular NLN value. A change of the NLN status field indicates a change of information on the
NCH which is not related to new calls (e.g. There may have been a release of a previous notified call or change
of priority, etc ...).
If the reduced NCH monitoring is active in the network, the network has to provide both NLN and NLN status
parameters.
These parameters may be provided on the NCH, PCH and SACCH:
- NLN(NCH): Notification List Number (received on the NCH).
- NLN(PCH): Notification List Number (received on the PCH).
- NLN(SACCH): Notification List Number (received on the SACCH).
- NLN status(PCH): NLN status (received on the PCH).
- NLN status(SACCH): NLN status (received on the SACCH).
A mobile station supporting neither VGCS listening nor VBS listening shall ignore the NLN(NCH),NLN(PCH),
NLN(SACCH) and NLN status fields.
If a mobile station (supporting VGCS listening and/or VBS listening) receives a NLN parameters on the NLN(PCH) or
NLN(SACCH) field different from the last received NLN value it shall read the NCH until it has received at least two
messages on the NCH indicating NLN with the two last received NLN being identical.
If a message in the paging subchannel is not received correctly, or if a paging message does not contain the information
on the notification status, the mobile station shall read the NCH until it has received at least two messages on the NCH
indicating NLN, with the two last received NLN being identical
3.3.3.4 Notification response procedure
In order to initiate the notification response procedure, if access to the network is allowed, the mobile station shall, when
camped on a cell as specified in GSM 03.22, initiate the immediate assignment procedure as specified in 3.3.1. The
establishment of the main signalling link is then initiated by use of an SABM with information field containing the
NOTIFICATION RESPONSE message (see section 3.1.5). The MM sublayer in the mobile station is informed that the
RR entity has entered the dedicated mode.
Upon receipt of the NOTIFICATION RESPONSE message the network stops timer T3101. The MM sublayer in the
network may be informed that an RR connection exists; in this case, the MM sublayer may initiate MM common
procedures.
ETSI
59 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.4 Procedures in dedicated mode and in group transmit mode
Procedures described in this section apply to the dedicated mode and/or the group transmit mode.
Those procedures which are specific for group transmit mode or refer to transitions to the group transmit mode are only
applicable for mobile stations supporting VGCS talking.
Direct transition between dedicated mode and group transmit mode is possible in both directions by use of the following
procedures:
- Channel assignment procedure;
- Handover procedure;
- Channel mode modify procedure.
3.4.1 SACCH procedures
3.4.1.1 General
In dedicated mode and group transmit mode, the SACCH is used in signalling layer at least for measurement results
transmission from the mobile station.
The SACCH has the particularity that continuous transmission must occur in both directions at least on the channel
carrying the main signalling link. For that purpose, in the mobile station to network direction, measurement result
messages are sent at each possible occasion when nothing else has to be sent (see section 3.4.1.2). Similarly, SYSTEM
INFORMATION TYPE 5, 6 and optionally 5bis and 5ter messages are sent in the network to mobile station direction in
UI frames when nothing else has to be sent.
In a multislot configuration the SYSTEM INFORMATION TYPE 5, 6 and optionally 5bis and 5ter messages shall be
sent on the SACCH associated with the channel carrying the main signalling link.
In a multislot configuration the mobile station shall ignore all messages received on the SACCH(s) that are not
associated with the channel carrying the main signalling link.
On a VGCS channel, the network may send additional or alternative system information messages for both mobile
stations in group transmit mode and those in group receive mode (see section 3.4.15.2.1).
A mobile station with extended measurement capabilities which receives EXTENDED MEASUREMENT ORDER
(EMO) messages on the SACCH, shall perform and report extended measurements, see section 3.4.1.3.
The SYSTEM INFORMATION TYPE 5bis message shall be sent if and only if the EXT IND bit in the Neighbour Cell
Description information element in both the SYSTEM INFORMATION TYPE 5 and TYPE 5bis messages indicates
that each information element only carries part of the BA.
A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. GSM 05.05) may consider the
EXT-IND bit in the Neighbour Cells Description IE in the SYSTEM INFORMATION TYPE 5 message bit as a spare
bit, assume that the information element carries the complete BA, and ignore any SYSTEM INFORMATION TYPE
5bis messages.
NOTE: The network should take into account limitations of certain mobile stations to understand SYSTEM
INFORMATION TYPE 5ter and TYPE 5bis messages, the EXT-IND bit in the Neighbour Cells
Description, and formats used in the Neighbour Cells Description information element and Cell Channel
Description information element used in SYSTEM INFORMATION messages, see section 10.5.2.1b, and
section 10.5.2.22.
As specified in GSM 05.08, problems occurring in the reception of SACCH frames are interpreted as a loss of
communication means and appropriate procedures are then triggered as specified in section 3.4.13.
ETSI
60 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.4.1.2 Measurement report
When in dedicated mode or group transmit mode, the mobile station regularly sends MEASUREMENT REPORT
messages to the network. These messages contain measurement results about reception characteristics from the current
cell and from neighbour cells. The BA (list) which is the basis for the measurements is derived from information
received on the BCCH in System Information 2 and optionally 2bis and/or 2ter and on the SACCH in System
Information 5 and optionally 5bis and/or 5ter.
When the information is received in more than one message the mobile station shall only combine information from
messages received on the same channel and indicating the same value of the BCCH allocation sequence number without
any message indicating a different value of the BCCH allocation sequence number received in between. If neighbouring
cell information for the serving cell is not available, the mobile station indicates this in the MEASUREMENT REPORT
message. These measurement results are obtained as specified in GSM 05.08.
These messages are sent on the slow ACCH, in unacknowledged mode.
If no other message is scheduled on the SACCH at the instant when a layer 2 frame is due to be sent, then the mobile
station shall send a MEASUREMENT REPORT message or an EXTENDED MEASUREMENT REPORT message
(see section 3.4.1.3) in that frame. The interval between two successive layer 2 frames containing MEASUREMENT
REPORT messages shall not exceed one layer 2 frame.
3.4.1.3 Extended measurement report $(MAFA)$
Only applicable to mobile stations which support extended measurement.
When in dedicated mode or group transmit mode, a mobile station may receive an EXTENDED MEASUREMENT
ORDER (EMO) message, from the network. The mobile station shall then, as defined in GSM 05.08, for one reporting
period perform measurements on the frequencies specified by this EMO message. The mobile station shall thereafter
send an EXTENDED MEASUREMENT REPORT message. This message contains the measurement results as defined
in GSM 05.08.
If the mobile station has not started to send its EXTENDED MEASUREMENT REPORT within 10 seconds after the
reception of the EMO message, no EXTENDED MEASUREMENT REPORT shall be sent. The mobile station shall
after a successful channel change abort any pending measurements or reporting related to an EMO message received on
the old channel.
If a mobile station receives an EMO message indicating the same value of the sequence code as an EMO message
received earlier on the same channel without having received any EMO message indicating a different value of the
sequence code in between, that EMO message shall be ignored. If the mobile station, before the reporting related to an
EMO message has started, receives a new EMO message with a different value of the sequence code, any pending
measurements or reporting related to the earlier EMO message shall be aborted and the new message treated.
The EMO message and the EXTENDED MEASUREMENT REPORT message are sent on the SACCH, in
unacknowledged mode.
3.4.2 Transfer of messages and link layer service provision
When in dedicated mode or in group transmit mode, upper layers can send messages in multiframe or unacknowledged
mode on SAPI 0.
Moreover, but only when in dedicated mode, upper layers have access to the full link layer services for SAPIs other than
0, with the exception of the error indication and local end release that are directly treated by the RR sublayer, as
specified in particular places of section 3.
3.4.3 Channel assignment procedure
In dedicated mode or in group transmit mode, an intracell change of channel can be requested by upper layers for
changing the channel type, or decided by the RR sublayer, e.g. for an internal handover. This change may be performed
through the dedicated channel assignment procedure.
ETSI
61 draft ETSI EN 300 940 V7.7.0 (2000-04)
The purpose of the channel assignment procedure is to completely modify the physical channel configuration of the
mobile station without frequency redefinition or change in synchronization while staying in the same cell.
This procedure shall not be used for changing between dependent configurations, i.e. those sharing Radio Resource for
the main signalling link. An example of dependent channels is a full rate channel and one of the corresponding half rate
channels. In multislot operation however, it is allowed to use the same timeslots before and after the assignment, as long
as the main signalling link has been changed. The only procedures provided for changing between dependent
configurations for the main signalling link are the additional assignment and the partial release procedures.
The channel assignment procedure happens only in dedicated mode and in group transmit mode. This procedure cannot
be used in the idle mode; in this case the immediate assignment procedure is used.
The channel assignment procedure includes:
- the suspension of normal operation except for RR management (layer 3).
- the release of the main signalling link, and of the other data links as defined in section 3.1.4, and the
disconnection of TCHs if any.
- the deactivation of previously assigned channels (layer 1)
- the activation of the new channels and their connection if applicable.
- The triggering of the establishment of the data link connections for SAPI = 0.
The channel assignment procedure is always initiated by the network.
3.4.3.1 Channel assignment initiation
The network initiates the channel assignment procedure by sending an ASSIGNMENT COMMAND message to the
mobile station on the main signalling link. It then starts timer T3107.
NOTE: The network should take into account limitations of certain mobile stations to understand formats used in
the Frequency List IE and Cell Channel Description IE used in the ASSIGNMENT COMMAND
message, see section 10.5.2.13 and section 10.5.2.1b.
When sending this message on the network side, and when receiving it on the mobile station side, all transmission of
signalling layer messages except for those RR messages needed for this procedure and for abnormal cases is suspended
until resumption is indicated. These RR messages can be deduced from sections 3.4.3 and 8.8 Radio Resource
management.
Upon receipt of the ASSIGNMENT COMMAND message, the mobile station initiates a local end release of link layer
connections, disconnects the physical channels, commands the switching to the assigned channels and initiates the
establishment of lower layer connections (this includes the activation of the channels, their connection and the
establishment of the main signalling links).
The ASSIGNMENT COMMAND message contains the description of the new configuration, including for the multislot
configuration and the TCH/H + TCH/H + ACCHs configuration, the exact ACCHs to be used and a power command.
The power level defined in this power command shall be used by the mobile station for the initial power on the new
channel(s). It shall not affect the power used on the old channel(s). The message may also contain definitions of the
channel mode to be applied for one or several channel sets. If a previously undefined channel set is defined by the
ASSIGNMENT COMMAND message, a definition of the channel mode for the new channel set shall be included in the
message.
If the channel mode to be applied corresponds to a multi-rate speech codec, the ASSIGNMENT COMMAND message
may contain the MultiRate Configuration IE, which defines the set of codec modes and related information to use on the
new channel. For an initial assignment of a multi-rate speech codec, the MS shall expect in the ASSIGNMENT
COMMAND the MultiRate Configuration IE. After reception of the ASSIGNMENT COMMAND, the mobile station
shall use the Initial Codec Mode specified in the MultiRate Configuration IE, if present, or apply the implicit rule
defined in GSM 05.09.
An ASSIGNMENT COMMAND message may indicate a frequency change in progress, with a starting time and
possibly alternative channel descriptions.
ETSI
62 draft ETSI EN 300 940 V7.7.0 (2000-04)
In the case of the reception of an ASSIGNMENT COMMAND message which contains only the description of a
channel to be used after the starting time, the mobile station shall wait up to the starting time before accessing the
channel. If the starting time has already elapsed, the mobile shall access the channel as an immediate reaction to the
reception of the message (see GSM 05.10 for the timing constraints).
indicated time. New parameters can be frequency list, MAIO and HSN. Other parameters describing the allocated
channels must be identical to the parameters described for before the starting time. If the moment the mobile station is
ready to access is after the starting time, the mobile station accesses the channel described for after the starting time.
If frequency hopping is applied, the cell allocation if present in the message is used to decode the mobile allocation. If
the cell allocation is not included, the mobile station uses its current cell allocation, the current CA is the last CA
received on the BCCH. Afterward, the current CA may be changed by some messages sent on the main signalling link
containing a CA (the possible messages are: ASSIGNMENT COMMAND, HANDOVER COMMAND and
FREQUENCY REDEFINITION). Note that there are cases in which the current CA is undefined, see section 3.4.3.3.
The ASSIGNMENT COMMAND message may contain a cipher mode setting IE. In that case, this ciphering mode has
to be applied on the new channel. If no such information is present, the ciphering mode is the same as on the previous
channel. In either case the ciphering key shall not be changed. The ASSIGNMENT COMMAND message shall not
contain a cipher mode setting IE that indicates "start ciphering" unless a CIPHERING MODE COMMAND message has
been transmitted earlier in the RR connection: if such an ASSIGNMENT COMMAND message is received it shall be
regarded as erroneous, an ASSIGNMENT FAILURE with cause "Protocol error unspecified" message shall be returned
immediately, and no further action taken.
In a voice group call, the ASSIGNMENT COMMAND message may contain a VGCS target mode information element
defining which RR mode is to be used on the new channel (i.e. dedicated mode or group transmit mode). If this
information element is not present, the mode shall be assumed to be the same as on the previous channel. The VGCS
target mode information element shall also indicate the group cipher key number for the group cipher key to be used on
the new channel or if the new channel is non ciphered. If the information element is not present, the ciphering mode and
group cipher key shall be the same as on the previous channel. Mobile stations not supporting VGCS talking shall ignore
the ASSIGNMENT COMMAND message if the VGCS target mode information element is included in the message and
shall send an RR STATUS message to the network with cause #96. If a VGCS target mode information element and a
cipher mode setting information element is included in the same message, then a mobile station supporting VGCS
talking mobile shall regard the ASSIGNMENT COMMAND message as erroneous, an ASSIGNMENT FAILURE
message with cause "Protocol error unspecified" shall be returned immediately, and no further action taken.
3.4.3.2 Assignment completion
After the main signalling link is successfully established, the mobile station returns an ASSIGNMENT COMPLETE
message, specifying cause "normal event", to the network on the main DCCH.
The sending of this message on the mobile station side and its receipt on the network side allow the resumption of the
transmission of signalling layer messages other than those belonging to RR management.
At the receipt of the ASSIGNMENT COMPLETE message, the network releases the previously allocated resources and
stops timer T3107.
If the mobile station has no current CA and if it needs a CA to analyse the ASSIGNMENT COMMAND message, it
stays on the current channel(s) and sends an ASSIGNMENT FAILURE message with cause "no cell allocation
available".
If the ASSIGNMENT COMMAND message instructs the mobile station to use a Channel Description or Mode that it
does not support, or if the Channel Mode to use is not defined for all channel sets, then the mobile station shall return an
ASSIGNMENT FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the
current channel(s) and uses the old Channel Description or Channel Mode(s).
ETSI
63 draft ETSI EN 300 940 V7.7.0 (2000-04)
If the mobile station receives an ASSIGNMENT COMMAND message containing an inconsistent MultiRate
Configuration IE, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "channel mode
unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or
Channel Mode(s).
If during the initial assignment of the multirate speech the mobile station receives an ASSIGNMENT COMMAND
message and the MultiRate Configuration IE is not present, then the mobile station shall return an ASSIGNMENT
FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the current
channel(s) and uses the old Channel Description or Channel Mode(s).
If the ASSIGNMENT COMMAND message instructs the mobile station to use a frequency that it is not capable of, then
the mobile station shall return an ASSIGNMENT FAILURE message with cause "frequency not implemented", and the
mobile station shall remain on the current channel(s).
If the mobile station receives an ASSIGNMENT COMMAND message with a Frequency List IE indicating frequencies
that are not all in one band, then the mobile station shall stay on the current channel(s) and send an ASSIGNMENT
FAILURE message with cause "frequency not implemented". If the mobile station receives an ASSIGNMENT
COMMAND message with a Mobile Allocation IE indexing frequencies that are not all in one band, then the mobile
station shall stay on the current channel(s) and send an ASSIGNMENT FAILURE message with cause "frequency not
implemented".
NOTE: An ASSIGNMENT COMMAND message sent to a multi band mobile station shall not be considered
invalid because it indicates frequencies that are all in a different frequency band to that of the current
channel.
On the mobile station side, if a lower layer failure happens on the new channel before the ASSIGNMENT COMPLETE
message has been sent, the mobile station deactivates the new channels, reactivates the old channels, reconnects the
TCHs if any and triggers the establishment of the main signalling link. It then sends a ASSIGNMENT FAILURE
message, cause "protocol error unspecified" on the main DCCH and resumes the normal operation, as if no assignment
attempt had occurred. The operational parameters (e.g. ciphering mode) when returning on the old channel are those
applied before the procedure.
When receiving the ASSIGNMENT FAILURE message, the network stops T3107.
If a lower layer failure happens while attempting to connect back to the old channels, the radio link failure procedure is
applied (see section 3.4.13.2 for dedicated mode and 3.4.13.5 for group transmit mode).
On the network side, if timer T3107 elapses before either the ASSIGNMENT COMPLETE message has been received
on the new channels or an ASSIGNMENT FAILURE message is received on the old channels, the old channels and the
new channels are released if they both were dedicated channels and, unless the mobile station has re-established the call,
all contexts related to the connections with that mobile station are cleared. If one of the channels was a VGCS channel, it
shall be maintained and the uplink shall be set free. If both channels were VGCS channels, the network shall maintain
one of the channels and the uplink shall be set free.
On the network side, lower layer failure occurring on the old channels after the sending of the ASSIGNMENT
COMMAND message are ignored. Lower layer failures occurring after the receipt of the SABM Frame on the new main
signalling link are treated following the general rules (cf. section 3.5.2).
3.4.4 Handover procedure
In dedicated mode or group transmit mode, an intercell or intracell change of channel(s) can be requested by the network
RR sublayer. This change may be performed through the handover procedure
NOTE: The decision to do a handover and the choice of the new cell is out of the scope of this technical
specification.
The purpose of the handover procedure is to completely modify the channels allocated to the mobile station e.g. when
the cell is changed. A change in the channel configuration nature is possible. This procedure is used only while in
dedicated mode or group transmit mode.
The handover procedure is also used by Location Services as described in GSM 03.71.
ETSI
64 draft ETSI EN 300 940 V7.7.0 (2000-04)
The handover procedure shall not be used for changing between dependent configurations (see section 3.4.3). ). An
exception to this is when the handover procedure is used by Location Services. In this case the mobile may be
commanded to attempt a handover to the same channel as currently assigned to the MS. The MS shall attempt to
perform a handover to this unchanged channel, which includes the transmission of access bursts.
The handover procedure includes:
- The suspension of normal operation except for RR management (layer 3).
- The disconnection of the main signalling link, and of the other links via local end release (layer 2), and the
disconnection of the TCH(s) if any.
- The disconnection and the deactivation of previously assigned channels and their release (layer 1).
- The activation of the new channels, and their connection if applicable.
- The triggering of the establishment of data link connection for SAPI = 0 on the new channels.
The handover procedure is always initiated by the network.
3.4.4.1 Handover initiation
The network initiates the handover procedure by sending a HANDOVER COMMAND message to the mobile station on
the main DCCH. It then starts timer T3103.
the Frequency List IE, Frequency Short List IE, and Cell Channel Description IE used in the
HANDOVER COMMAND message, see section 10.5.2.13, section 10.5.2.14, and section 10.5.2.1b.
signalling layer messages except for those RR messages needed for this procedure and for abnormal cases, is suspended
until resuming is indicated. These RR messages can be deduced from section 3.4.3 and 8.5.1 "Radio Resource
management".
Upon receipt of the HANDOVER COMMAND message, the mobile station initiates, as described in section 3.1.4, the
release of link layer connections, disconnects the physical channels, commands the switching to the assigned channels
and initiates the establishment of lower layer connections (this includes the activation of the channels, their connection
and the establishment of the data links).
The HANDOVER COMMAND message contains:
- The characteristics of the new channels, including for the multislot configuration and the TCH/H + TCH/H +
ACCHs configuration the exact ACCHs to be used. The message may also contain definitions of the channel
mode to be applied for one or several channel sets. If a previously undefined channel set is defined by the
HANDOVER COMMAND message, a definition of the channel mode for the new channel set shall be included
in the message.
- The characteristics of the new cell that are necessary to successfully communicate (e.g. frequency list in the case
of slow frequency hopping), including the data that allows the mobile station to use the pre-knowledge about
synchronization it acquires by the measurement process (i.e. BSIC + BCCH frequency).
- A power command (cf. GSM 05.08). The power level defined in this power command shall be used by the
mobile station for the initial power on the new channel(s). It shall not affect the power used on the old channel(s).
- An indication of the physical channel establishment procedure to be used.
- A handover reference, used as specified in the following section. The choice of the handover reference by the
network is out of the scope of this specification and left to the manufacturers.
- Optionally a timing advance to be used on the new cell.
- Optionally a cipher mode setting. In that case, this ciphering mode has to be applied on the new channel. If no
such information is present, the ciphering mode is the same as on the previous channel. In either case the
ciphering key shall not be changed. The HANDOVER COMMAND message shall not contain a cipher mode
ETSI
65 draft ETSI EN 300 940 V7.7.0 (2000-04)
setting IE that indicates "start ciphering" unless a CIPHERING MODE COMMAND message has been
transmitted previously in this instance of the dedicated mode: if such a HANDOVER COMMAND message is
received it shall be regarded as erroneous, a HANDOVER FAILURE message with cause "Protocol error
unspecified" shall be returned immediately, and no further action taken.
- Optionally, in a voice group call, a VGCS target mode information element defining which RR mode is to be
used on the new channel (i.e. dedicated mode or group transmit mode). If this information element is not present,
the mode shall be assumed to be the same as on the previous channel. The VGCS target mode information
element shall also indicate the group cipher key number for the group cipher key to be used on the new channel
or if the new channel is non ciphered. If the information element is not present, the ciphering mode and ciphering
key shall be the same as on the previous channel. Mobile stations not supporting VGCS talking shall ignore the
HANDOVER COMMAND message if the VGCS target mode information element is included in the message
and shall send an RR STATUS message to the network with cause #96. If a VGCS target mode information
element and a cipher mode setting information element is included in the same message, then a mobile station
supporting VGCS talking shall regard the HANDOVER COMMAND message as erroneous, an HANDOVER
FAILURE message with cause "Protocol error unspecified" shall be returned immediately, and no further action
taken.
- Optionally, when the channel mode indicates that a multi-rate speech codec must be applied, the
MultiRateconfiguration to be used in the new cell. The MultiRate Configuration IE defines the set of codec mode
and related information to use after the handover. When accessing the new channel, the mobile station shall use
for the Initial Codec Mode the mode specified in the MultiRate Configuration IE, if present, or apply by default
the implicit rule defined in GSM 05.09.
In addition, a HANDOVER COMMAND message may indicate a frequency change in progress, with a starting time and
In the case of the reception of a HANDOVER COMMAND message which contains only the description of a channel to
be used after the starting time, the mobile station shall wait up to the starting time before accessing the channel. If the
starting time has already elapsed, the mobile shall access the channel as an immediate reaction to the reception of the
message (see GSM 05.10 for the timing constraints).
indicated time. New parameters can be frequency list, MAIO and HSN. Other parameters describing the allocated
channels must be identical to the parameters described for before the starting time. If the moment the mobile station is
ready to access is after the starting time, the mobile station accesses the channel described for after the starting time.
If the channel mode indicates that a multi-rate speech codec must be applied, and the MultiRateConfiguration IE is not
included in the HANDOVER COMMAND message, then the mobile station shall assume that the
MultiRateconfiguration has not changed. For the Initial Codec Mode, the mobile station shall use the previously
received Initial Codec Mode, if any, or apply by default the implicit rule defined in GSM 05.09.
3.4.4.2 Physical channel establishment
Four procedures are defined. The support of three of them is mandatory in the mobile station. The pseudo-
synchronization case is optional in the mobile station. A pseudo-synchronized handover can be commanded only to a
mobile station that can support it, as indicated in the classmark.
3.4.4.2.1 Finely synchronized cell case
If the mobile station knows that the timing advance with the new cell is not out of range, i.e. smaller than or equal to the
maximum timing advance that can be coded as specified in GSM 04.04, or if the new cell does accept out of range
timing advance as indicated in the HANDOVER COMMAND message, the mobile station proceeds as follows.
After having switched to the assigned channels, the mobile station sends four times the HANDOVER ACCESS message
in four successive layer 1 frames on the main DCCH. This message is sent in an access burst. Its content is reduced to
the handover reference information element. The transmission of these four messages is optional if so indicated by the
network in the HANDOVER COMMAND message.
ETSI
66 draft ETSI EN 300 940 V7.7.0 (2000-04)
Before completion of the 4 access bursts on the DCCH, additional access bursts may also be sent on the SACCH.
It then activates the channels in sending and receiving mode and connects the channels if need be.
If applicable, ciphering is immediately started . The access bursts are not ciphered.
3.4.4.2.2 Non synchronized cell case
After having switched to the assigned channels, the mobile station starts repeating the HANDOVER ACCESS message
in successive layer 1 frames on the main DCCH and optionally on the SACCH. This message is sent in an access burst.
Its content is reduced to the handover reference information element. The mobile station starts timer T3124 at the start
point of the timeslot in which the HANDOVER ACCESS message is sent the first time on the main DCCH.
The mobile station then activates the channels in receiving mode and connects the channels if need be (only for
reception).
If applicable, deciphering is then immediately started . The access bursts are not ciphered.
When the network has the RF characteristics that are necessary, it sends in unacknowledged mode a PHYSICAL
INFORMATION message to the mobile station on the main DCCH. If applicable, ciphering and deciphering is
immediately started (i.e., before even the reception of a correct access burst), and the message is sent enciphered.
The PHYSICAL INFORMATION message contains various physical layer related information, allowing a proper
transmission by the mobile station.
When sending the PHYSICAL INFORMATION message, the network starts timer T3105. If this timer times out before
the reception of a correctly decoded layer 2 frame in format A or B (see GSM 04.06), or a correctly decoded TCH
frame from the mobile station, the network repeats the PHYSICAL INFORMATION message and restarts timer T3105.
The maximum number of repetitions is Ny1.
The correct decoding of a frame means that the decoding algorithm and the error detection tests, if any, indicate no
error.
When the mobile station receives a PHYSICAL INFORMATION message, it stops timer T3124, stops sending access
bursts, activates the physical channels in sending and receiving mode and connects the channels if need be. If the
allocated channel is an SDCCH (+ SACCH), performance of the mobile station must enable the mobile station to accept
a correct PHYSICAL INFORMATION message sent by the network in any block while T3124 is running.
3.4.4.2.3 Pseudo-synchronized cell case
The details of the use of this procedure are described in GSM 05.10. The mobile station computes the timing advance to
be used with the new cell from the real time difference value given in the HANDOVER COMMAND message. If the
mobile station knows that the timing advance with the new cell is not out of range , i.e. smaller or equal to the maximum
timing advance that can be coded as specified in GSM 04.04, or if the new cell accepts an out of range timing advance
as indicated in the HANDOVER COMMAND message, the mobile station switches to the new channel and proceeds as
follows.
After having switched to the assigned channels, the mobile station sends in four successive slots on the main DCCH a
HANDOVER ACCESS message. This message is sent in random mode and thus does not follow the basic format. Its
content is reduced to the handover reference information element. The transmission of these four messages is optional if
so indicated by the network in the HANDOVER COMMAND message.
The mobile station then activates the channels in sending and receiving mode and connects the channels if need be. The
mobile station may activate the channels in receiving mode and connect the channels while sending access bursts.
If applicable, ciphering is then immediately started. The access bursts are not ciphered.
3.4.4.2.4 Pre-synchronized cell case
The details of the use of this procedure are described in GSM 05.10. The mobile station switches to the new channel and
proceeds as follows.
ETSI
67 draft ETSI EN 300 940 V7.7.0 (2000-04)
After having switched to the assigned channels, the mobile station sends in four successive slots on the main DCCH a
HANDOVER ACCESS message. This message is sent in an access burst and thus does not follow the basic format. Its
content is reduced to the handover reference information element. The transmission of these four messages is optional if
so indicated by the network in the HANDOVER COMMAND message.
The mobile station then activates the channel in sending and receiving mode and connects the channels if need be. The
timing advance value to be used with the new cell is:
- either the value contained in the HANDOVER COMMAND message if the timing advance information element
is present;
- or the default value for pre-synchronized handover as defined in GSM 05.10, if the timing advance information
element is not included in the HANDOVER COMMAND message. The MS may activate the channels in
receiving mode and connect the channels while sending access bursts.
If applicable, ciphering is immediately started. The access bursts are not ciphered.
3.4.4.3 Handover completion
After lower layer connections are successfully established, the mobile station returns a HANDOVER COMPLETE
message, specifying cause "normal event", to the network on the main DCCH.
The sending of this message on the mobile station side and its receipt on the network side allow the resumption of the
transmission of signalling layer messages other than those for RR management.
When receiving the HANDOVER COMPLETE message, the network stops timer T3103 and releases the old channels.
If requested to do so in the HANDOVER COMMAND message, the mobile station includes the observed time
difference it has measured when performing the handover, corrected by half the timing advance, in the HANDOVER
COMPLETE message (detailed specifications are given in GSM 05.10).
In the case of a synchronous or pseudo-synchronous handover, if the mobile station knows that the timing advance with
the new cell is out of range, i.e. is bigger than the maximum timing advance that can be coded as specified in
GSM 04.04, and if the new cell does not accept out of range timing advance as indicated in the HANDOVER
COMMAND message, the mobile station sends a HANDOVER FAILURE message, cause "handover impossible,
timing advance out of range", on the main signalling link and does not attempt that handover.
If the HANDOVER COMMAND message instructs the mobile station to use a Channel Description or Mode that it does
not support, or if the Channel Mode to use is not defined for all channel sets, then the MS shall return a HANDOVER
FAILURE message with cause "channel mode unacceptable", and the MS shall remain on the current channel(s) and
uses the old Channel Description or Mode(s).
If the mobile station receives a HANDOVER COMMAND message containing an inconsistent MultiRateConfiguration
IE, then the mobile station shall return a HANDOVER FAILURE message with cause "channel mode unacceptable",
and the mobile station shall remain on the current channel(s) and uses the old Channel Description or Mode(s).
If the HANDOVER COMMAND message instructs the mobile station to use a frequency that it is not capable of, then
the mobile station shall return a HANDOVER FAILURE message with cause "frequency not implemented", and the
If the mobile station receives a HANDOVER COMMAND message with a Frequency List IE or Frequency Short List
IE indicating frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and
send a HANDOVER FAILURE message with cause "frequency not implemented". If the mobile station receives a
HANDOVER COMMAND message with a Mobile Allocation IE indexing frequencies that are not all in one band, then
the mobile station shall stay on the current channel(s) and send a HANDOVER FAILURE message with cause
"frequency not implemented".
ETSI
68 draft ETSI EN 300 940 V7.7.0 (2000-04)
NOTE: A HANDOVER COMMAND message sent to a multi band mobile station shall not be considered invalid
because it indicates target channel frequencies that are all in a different frequency band to that of the
ARFCN in the Cell Description IE.
On the mobile station side, if timer T3124 times out (only in the non- synchronized case) or if a lower layer failure
happens on the new channel before the HANDOVER COMPLETE message has been sent, the mobile station
deactivates the new channels, reactivates the old channels, reconnects the TCHs if any and triggers the establishment of
the main signalling link. It then sends a HANDOVER FAILURE message on the main signalling link and resumes
normal operation as if no handover attempt had occurred. The operational parameters (e.g. ciphering mode) when
returning on the old channel are those applied before the HANDOVER COMMAND message was received.
When the HANDOVER FAILURE message has been received, the network releases the new channels if they were
dedicated channels and stops timers T3105 and stops T3103 in the non-synchronized case. If the new channels were
VGCS channels, they shall be maintained.
If a lower layer failure happens while attempting to connect back to the old channels, the standard rules are applied (cf.
section 3.4.13.2 for dedicated mode and 3.4.13.5 for group transmit mode).
On the network side, if timer T3103 elapses before either the HANDOVER COMPLETE message is received on the
new channels, or a HANDOVER FAILURE message is received on the old channels, or the mobile station has re-
established the call, the old channels are released if they were dedicated channels and all contexts related to the
connections with that mobile station are cleared. If the old channel was a VGCS channel, it shall be maintained and the
uplink shall be set free.
On the network side, if neither a correctly layer 2 frame in format A or B nor a correctly TCH frame have been received
from the mobile station on the new channel, the newly allocated channels are released if they were dedicated channels. If
the new channels were VGCS channels, they shall be maintained and the uplink shall be set free..
On the network side, lower layer failures occurring on the old channels after the sending of the HANDOVER
COMMAND message are ignored. Lower layer failures occurring after the receipt of the SABM frame on the new main
signalling link are treated following a general scheme (cf. section 3.4.13.2 for dedicated mode and 3.4.13.5 for group
transmit mode).
3.4.5 Frequency redefinition procedure
In dedicated mode and group transmit mode, this procedure is used by the network to change the frequencies and
hopping sequences of the allocated channels. This is meaningful only in the case of frequency hopping.
The network sends to the mobile station a FREQUENCY REDEFINITION message containing the new parameters
together with a starting time indication.
the Cell Channel Description IE used in the FREQUENCY REDEFINITION message, see section
10.5.2.13.
When receiving such a message, the mobile station modifies the frequencies/hopping sequences it uses at the exact
indicated time slot, i.e. the indicated time slot is the first with new parameters. All other functions are not disturbed by
this change. New parameters can be the cell channel description, the mobile allocation and the MAIO. In case of
multislot configuration, the Channel Description IE shall describe the channel carrying the main signalling link, the new
parameters however, shall be used for all assigned timeslots. Other parameters describing the allocated channels must be
identical to the current parameters.
If the mobile station receives a FREQUENCY REDEFINITION message with a Mobile Allocation IE indexing
frequencies that are not all in one band and a Starting Time IE indicating a time that has not elapsed, then the mobile
station shall stay on the current channel(s) and send a RR STATUS message with cause "frequency not implemented".
If the mobile station receives a FREQUENCY REDEFINITION message with a Mobile Allocation IE indexing
frequencies that are not all in one band and a Starting Time IE indicating a time that has elapsed, then the mobile station
shall locally abort the radio connection and, if permitted, attempt Call Re-establishment.
ETSI
69 draft ETSI EN 300 940 V7.7.0 (2000-04)
If the mobile station receives a FREQUENCY REDEFENITION message on a channel for which it has a pending
redefinition (defined by the immediate assignment, assignment or handover procedure or a previous frequency
redefinition procedure) the frequencies, hopping and starting time parameters defined by the new frequency redefinition
procedure supersedes those of the pending one.
NOTE: A FREQUENCY REDEFINITION message sent to a multi band mobile station shall not be considered
invalid because it indicates new frequencies that are all in a different frequency band to that of the
ARFCN of the serving cell.
3.4.6 Channel mode modify procedure
In dedicated mode or group transmit mode, higher layers can request the setting of the channel mode.
The channel mode modify procedure allows the network to request the mobile station to set the channel mode for one
channel or one channel set. The procedure shall not be used if the multislot configuration contains more than one
channel set. The channel mode covers the coding, decoding and transcoding mode used on the indicated channel.
This procedure is always initiated by the network.
NOTE: Direct transitions between full rate speech coder version 1 and full rate speech coder version 2 (and vice
versa) may cause unpleasant audio bursts.
3.4.6.1 Normal channel mode modify procedure
3.4.6.1.1 Initiation of the channel mode modify procedure
The network initiates the procedure by sending a CHANNEL MODE MODIFY message to the mobile station. This
message contains:
- a channel description of the channel(s) on which the mode in the CHANNEL MODE MODIFY message shall be
applied; and
- the mode to be used on that channel, or on all the channels of a channel set in a multislot configuration.
- Optionally, when the channel mode indicates that a multi-rate speech codec must be applied, the
MultiRateconfiguration to be used. The MultiRateConfiguration IE defines the set of codec mode and related
information to use after the mode modify procedure. When initiating the new mode, the mobile station shall use
for the Initial Codec Mode the mode specified in the MultiRateConfiguration IE, if present, or apply by default
the implicit rule defined in GSM 05.09.
3.4.6.1.2 Completion of channel mode modify procedure
When it has received the CHANNEL MODE MODIFY message, the mobile station sets the mode for the indicated
channel, and if that is in a multislot configuration, the whole channel set and then replies by a CHANNEL MODE
MODIFY ACKNOWLEDGE message indicating the ordered channel mode.
This applies whether the mode commanded by the CHANNEL MODE MODIFY is different from the one used by the
mobile station or whether it is already in use.
No specific action for a lower layer failure is specified in this section. If the mobile station does not support the
indicated mode, it shall retain the old mode and return the associated channel mode information in the CHANNEL
MODE MODIFY ACKNOWLEDGE message.
ETSI
70 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.4.6.2 Channel mode modify procedure for a voice group call talker
3.4.6.2.1 Initiation of the channel mode modify procedure
The network initiates the procedure by sending a CHANNEL MODE MODIFY message to the mobile station. This
message contains:
- a channel description of the channel on which the CHANNEL MODE MODIFY message is sent; and
- the new channel mode to be used on the channel; and
- optionally, the VGCS target mode information element defining which RR mode is to be used with the new
channel mode (i.e. dedicated mode or group transmit mode). If this information element is not present, the RR
mode shall be assumed to be the same as with the previous channel mode. The VGCS target mode information
element shall also indicate the group cipher key number for the group cipher key to be used on the new channel
or if the new channel is non ciphered. If the information element is not present, the ciphering mode and ciphering
key shall be the same as with the previous channel mode. Mobile stations not supporting VGCS talking shall
ignore the CHANNEL MODE MODIFY message if the VGCS target mode information element is included in
the message and shall send an RR STATUS message to the network with cause #96.
The start of ciphering with a group cipher key with the new channel mode is only possible when the mode on the old
channel was not ciphered.
If a VGCS target mode information element indicating a group cipher key number is included in the message and the
previous mode is not non ciphered and the group cipher key number is different to the previous cipher key number, the
mobile station shall behave as if it would not support the indicated channel mode.
3.4.6.2.2 Completion of mode change procedure
When it has received the CHANNEL MODE MODIFY message, the mobile station changes the mode for the indicated
channel and then replies by a CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the new channel
mode.
No specific action for a lower layer failure is specified in this section. If the mobile station does not support the
indicated mode, it shall retain the old mode and return the associated channel mode information in the CHANNEL
MODE MODIFY ACKNOWLEDGE message.
3.4.7 Ciphering mode setting procedure
In dedicated mode, the ciphering mode setting procedure is used by the network to set the ciphering mode, i.e. whether
or not the transmission is ciphered, and if so which algorithm to use. The procedure shall only be used to change from
"not ciphered" mode to "ciphered" mode, or vice-versa, or to pass a CIPHERING MODE COMMAND message to the
mobile station while remaining in the "not ciphered" mode. The ciphering mode setting procedure is always triggered by
the network and it only applies to dedicated resources.
The cipher mode setting procedure shall not be applied in group transmit mode.
3.4.7.1 Ciphering mode setting initiation
The network initiates the ciphering mode setting procedure by sending a CIPHERING MODE COMMAND message to
the mobile station on the main signalling link, indicating whether ciphering shall be used or not, and if yes which
algorithm to use.
Additionally, the network may, by the use of the cipher response information element, request the mobile station to
include its IMEISV in the CIPHERING MODE COMPLETE message.
The new mode is applied for reception on the network side after the message has been sent.
ETSI
71 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.4.7.2 Ciphering mode setting completion
Whenever the mobile station receives a valid CIPHERING MODE COMMAND message, it shall, if a SIM is present
and considered valid by the ME and the ciphering key sequence number stored on the SIM indicates that a ciphering key
is available, load the ciphering key stored on the SIM into the ME. A valid CIPHERING MODE COMMAND message
is defined to be one of the following:
- one that indicates "start ciphering" and is received by the mobile station in the "not ciphered" mode;
- one that indicates "no ciphering" and is received by the MS in the "not ciphered" mode; or
- one that indicates "no ciphering" and is received by the mobile station in the "ciphered" mode.
Other CIPHERING MODE COMMAND messages shall be regarded as erroneous, an RR STATUS message with cause
"Protocol error unspecified" shall be returned, and no further action taken.
Upon receipt of the CIPHERING MODE COMMAND message indicating ciphering, the mobile station shall start
transmission and reception in the indicated mode.
When the appropriate action on the CIPHERING MODE COMMAND has been taken, the mobile station sends back a
CIPHERING MODE COMPLETE message. If the "cipher response" field of the cipher response information element in
the CIPHERING MODE COMMAND message specified "IMEI must be included" the mobile station shall include its
IMEISV in the CIPHERING MODE COMPLETE message.
Upon receipt of the CIPHERING MODE COMPLETE message or any other correct layer 2 frame which was sent in the
new mode, the network starts transmission in the new mode.
CIPH MOD CMD
<--------------------------
<------ start reception
start ---> in new mode
transmission and
reception in new mode
CIPH MOD COM
-------------------------->
<------ start trans-
mission in new mode
Figure 3.3/GSM 04.08: Ciphering mode setting sequence
3.4.8 Additional channel assignment procedure
NOTE: In the present state of GSM 04.03, this procedure is only possible for the TCH/H + ACCHs to TCH/H +
TCH/H + ACCHs transition. As a consequence it is not needed for simple mobile stations. The description
of the procedure is in general terms to cope with possible evolution.
In dedicated mode, a change of channel configuration to include an additional channel can be requested by upper layers.
The additional channel assignment procedure shall not be applied in group transmit mode,
The purpose of the additional assignment procedure is to allocate an additional dedicated channel to a mobile station
while keeping the previously allocated channels. In particular the main DCCH and the SACCH are not modified, and
signalling exchanges are not interrupted.
The additional assignment procedure may happen only in dedicated mode. It is used for instance for the transition from
the TCH/H + ACCHs configuration to the TCH/H + TCH/H + ACCHs configuration.
The additional assignment procedure is always initiated by the network.
3.4.8.1 Additional assignment procedure initiation
The network initiates the procedure by sending an ADDITIONAL ASSIGNMENT message to the mobile station on the
main DCCH. The ADDITIONAL ASSIGNMENT message contains the description of the newly assigned channel.
ETSI
72 draft ETSI EN 300 940 V7.7.0 (2000-04)
On receipt of the message, the mobile station activates the new channel.
3.4.8.2 Additional assignment procedure completion
The mobile station sends an ASSIGNMENT COMPLETE message to the network on the channel, on which it receives
the ADDITIONAL ASSIGNMENT message.
A lower layer failure occurring during the procedure is treated according to the general case (see section 3. 4.13.2).
The network considers the channel as allocated from the sending of the ADDITIONAL ASSIGNMENT message. As a
consequence, if a re-establishment occurs, the network will consider the context as if the mobile station has received the
message, and the new configuration allocated after the re-establishment may differ from the one the mobile station had
before the re-establishment.
3.4.9 Partial channel release procedure
In dedicated mode, a change of channel configuration to release one channel can be requested by upper layers.
The partial channel release procedure shall not be applied in group transmit mode.
The purpose of this procedure is to deactivate part of the dedicated channels in use. The channel configuration remains
dedicated.
NOTE: In the present state of GSM 04.03, this procedure is only possible for the TCH/H + TCH/H + ACCHs to
TCH/H + ACCHs transition. As a consequence it is not needed for simple mobile stations.
The partial release procedure is always initiated by the network.
3.4.9.1 Partial release procedure initiation
The network initiates the partial release by sending a PARTIAL RELEASE message to the mobile station on the main
DCCH.
On receipt of the PARTIAL RELEASE message the mobile station:
- Initiates the disconnection of all the link layer connections carried by the channel to be released;
- Simultaneously initiates the connection on remaining channels of the data link layer connections that have been
released;
- Deactivates the physical channels to be released.
- Sends a PARTIAL RELEASE COMPLETE to the network on the (possibly new) main signalling link.
A lower layer failure is treated following the general rules as specified in section 3.4.13.2.
Moreover, on the network side, the channel configuration nature is set from the sending of the PARTIAL RELEASE
message onward. As a consequence, any new assignment after a re-establishment may concern a different channel
configuration nature from the one known by the mobile station before the re-establishment.
3.4.10 Classmark change procedure
In dedicated mode or in group transmit mode, this procedure allows the mobile station to indicate to the network a
change of characteristics reflected in the classmark (e.g. due to addition of power amplification). Furthermore, a mobile
station which implements the controlled early classmark sending option may also send a CLASSMARK CHANGE
message as described in clause 3.3.1.1.4, even if no change of characteristics has occurred.
ETSI
73 draft ETSI EN 300 940 V7.7.0 (2000-04)
The mobile station sends a CLASSMARK CHANGE message to the network. This message contains the new mobile
station classmark 2 information element. It may also contain a Classmark 3 Information Element. There is no
acknowledgement from the network at layer 3.
3.4.11 Classmark interrogation procedure
This procedure allows the network to request additional classmark information from the mobile station (e.g. if the
information initially sent by the mobile station is not sufficient for network decisions).
3.4.11.1 Classmark interrogation initiation
The network initiates the classmark interrogation procedure by sending a CLASSMARK ENQUIRY message to the
mobile station on the main DCCH.
3.4.11.2 Classmark interrogation completion
On receipt of the CLASSMARK ENQUIRY message the mobile station sends a CLASSMARK CHANGE message to
the network on the main DCCH. This message contains the mobile station classmark 2 information element. It may also
contain a Classmark 3 Information Element.
3.4.12 Indication of notifications and paging information
Only applicable for mobile stations supporting VGCS listening or VBS listening:
In dedicated mode or in group transmit mode, the RR entity shall provide indications to the upper layer on all received
notifications for voice group calls or voice broadcast calls according to the VGCS or VBS subscription data stored in
the mobile station. The indication shall include the notified group or broadcast call reference and possibly the related
priority, if provided.
In group transmit mode, if the mobile station has received a paging message with the own mobile station identity on the
PCH or on the voice group call channel downlink, the RR entity shall provide an indication to the upper layers, together
with the related priority, if applicable.
In group transmit mode, if the RR entity receives information on the voice group call channel of the existence of a
paging message in its paging subgroup of the PCH, the RR entity shall pass this information to the upper layers together
with the related priority if provided (see also section 3.3.2 and 3.3.3).
3.4.13 RR connection release procedure
3.4.13.1 Normal release procedure
The release of the RR connection can be requested by upper layers.
The purpose of this procedure is to deactivate all the dedicated channels in use. When the channels are released, the
mobile station returns to the CCCH configuration, idle mode. The channel release procedure can be used in a variety of
cases, including TCH release after a call release, and DCCH release when a dedicated channel allocated for signalling is
released.
In dedicated mode and group transmit mode, the channel release procedure is always initiated by the network.
If the mobile station is IMSI attached for GPRS services (section 4) at release of the RR connection, the mobile station
shall return to packet idle mode, or if a temporary block flow is established, continue in packet transfer mode.
3.4.13.1.1 Channel release procedure initiation in dedicated mode and in group transmit
mode
The network initiates the channel release by sending a CHANNEL RELEASE message to the mobile station on the main
DCCH, starts timer T3109 and deactivates the SACCH.
ETSI
74 draft ETSI EN 300 940 V7.7.0 (2000-04)
On receipt of a CHANNEL RELEASE message the mobile station starts timer T3110 and disconnects the main
signalling link. When T3110 times out, or when the disconnection is confirmed, the mobile station deactivates all
channels, considers the RR connection as released, and returns to CCCH idle mode.
NOTE: Data Links other than the main signalling link are disconnected by local end link release.
If case of dedicated mode, on the network side, when the main signalling link is disconnected, the network stops timer
T3109 and starts timer T3111. When timer T3111 times out, the network deactivates the channels, they are then free to
be allocated to another connection.
NOTE: The sole purpose of timer T3111 is to let some time to acknowledge the disconnection and to protect the
channel in case of loss of the acknowledge frame.
If timer T3109 times out, the network deactivates the channels; they are then free to be allocated to another connection.
The CHANNEL RELEASE message will include an RR cause indication as follows:
#0 if it is a normal release, e.g. at the end of a call or at normal release of a DCCH.
#1 to indicate an unspecified abnormal release.
#2, #3 or #4 to indicate a specific release event.
#5 if the channel is to be assigned for servicing a higher priority call (e.g. an emergency call).
#65 if e.g. a handover procedure is stopped because the call has been cleared.
The CHANNEL RELEASE message may include the information element BA Range which may be used by a mobile
station in its selection algorithm (see GSM 05.08 and GSM 03.22).
Mobile stations not supporting VGCS or VBS listening shall consider Group Channel Description and Group Cipher
Key Number information elements as unnecessary in the message and perform the channel release procedure as normal.
For mobile stations supporting VGCS listening, the following procedures apply:
The CHANNEL RELEASE message may include the information element Group Channel Description. In this case, the
mobile station shall release the layer 2 link, enter the group receive mode and give an indication to the upper layer. If a
CHANNEL RELEASE message with no Group Channel Description is received, the normal behaviour applies.
If ciphering is applied on the VGCS or VBS channel, the network shall provide in the CHANNEL RELEASE message
with the Group Cipher Key Number information element for the group cipher key to be used by the mobile station for
reception of the VGCS or VBS channel. If this information element is not included, no ciphering is applied on the
VGCS or VBS channel.
A mobile station not supporting the GPRS option shall consider the GPRS Resumption information element as an
information element unknown in the message and continue the channel release procedure as normal.
For a mobile station supporting the GPRS option, the following additional procedures also apply:
The CHANNEL RELEASE message may include the information element GPRS Resumption. If the GPRS Resumption
information element indicates that the network has resumed GPRS services, the RR sublayer of the mobile station shall
indicate a RR GPRS resumption complete to the MM sublayer, see section 4. If the GPRS Resumption information
element indicates that the network has not successfully resumed GPRS services, the RR sublayer of the mobile station
shall indicate a RR GPRS resumption failure to the MM sublayer, see section 4.
If the mobile station has performed the GPRS suspension procedure (section 3.3.1.1.4.2) and the GPRS Resumption
information element is not included in the message, the RR sublayer of the mobile station shall indicate a RR GPRS
resumption failure to the MM sublayer, see section 4.
If the mobile station has not performed the GPRS suspension procedure and the GPRS Resumption information element
is not included in the message, the mobile station shall continue the channel release procedure as normal.
Abnormal cases are taken into account in the main part of the description of the procedure.
ETSI
75 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.4.13.2 Radio link failure in dedicated mode
The main part of these procedures concerns the "normal" cases, i.e. those without any occurrence of loss of
communication means. A separate paragraph at the end of the description of each procedure treats the cases of loss of
communication, called a radio link failure. In dedicated mode, in most of the cases the reaction of the mobile station or
the network is the same. Those reactions are described in this section to avoid repetitions.
A radio link failure can be detected by several ways:
1) By analysis of reception at layer 1, as specified in GSM 05.08 and section 3.4.1.1.
2) By a data link layer failure as specified in GSM 04.06, on the main signalling link. A data link failure on any
other data link shall not be considered as a radio link failure.
3) When a lower layer failure happens while the mobile station attempts to connect back to the old channels in a
channel assignment procedure, handover procedure, PDCH assignment procedure or RR-cell change order
procedure.
4) In some cases where timers are started to detect the lack of answer from the other party, as described in section 3.
The two first cases are known by the term "lower layer failure".
3.4.13.2.1 Mobile side
When a radio link failure is detected by the mobile station,
- the MS shall perform a local end release on all signalling links unless otherwise specified;
- the mobile station shall deactivate all channels;
- the RR sublayer of the mobile station shall indicate an RR connection failure to the MM sublayer unless
otherwise specified.
NOTE: Upper layers may decide on a re-establishment (cf. section 5.5.4).
When a mobile station which has performed the GPRS suspension procedure (section 3.3.1.1.4.2) detects a radio link
failure, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see
section 4.
In dedicated mode, the reaction of the network to a lower layer failure depends on the context. Except when otherwise
specified, it is to release the connection either with the channel release procedure as specified in section 3.5.1, or with
the following procedure. The network starts timer T3109 and deactivates the SACCH (and hence to stop transmission on
the SACCH).
When a radio link failure has been detected, an indication is passed to the upper Mobility Management sublayer on the
network side.
When timer T3109 expires, the network can regard the channels as released and free for allocation.
This procedure relies on the fact that if a mobile station does not receive the SACCH for some time, it completely
releases the channels (cf. GSM 05.08).
NOTE: The network should maintain for a while the transaction context in order to allow call re-establishment.
The length of timer is for further study.
When a mobile station which has performed the GPRS suspension procedure (section 3.3.1.1.4.2) detects a radio link
failure, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see
section 4.
ETSI
76 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.4.13.3 RR connection abortion in dedicated mode
The mobile station aborts the RR connection by initiating a normal release of the main signalling link, performing local
end releases on all other signalling links and disconnecting all traffic channels, if any.
When a mobile station which has performed the GPRS suspension procedure (section 3.3.1.1.4.2) aborts the RR
connection, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see
section 4.
3.4.13.4 Uplink release procedure in group transmit mode
If the uplink release is requested by the upper layer the mobile station shall send an UPLINK RELEASE message on the
voice group call channel uplink, perform a release of the main signalling link and go back to the group receive mode.
If the UPLINK RELEASE message is received from the network on the voice group call channel downlink, the MS shall
perform a release of the main signalling link and go back to the group receive mode.
3.4.13.5 Radio link failure in group transmit mode
The main part of these procedures concerns the "normal" cases, i.e. those without any occurrence of loss of
communication means. A separate paragraph at the end of the description of each procedure treats the cases of loss of
communication, called a radio link failure. In group transmit mode, in most of the cases the reaction of the mobile
station or the network is the same. Those reactions are described in this section to avoid repetitions.
A radio link failure can be detected by several ways:
1) By analysis of reception at layer 1, as specified in GSM 05.08 and section 3.4.1.1.
2) By a data link layer failure as specified in GSM 04.06, on the main signalling link. A data link failure on any
other data link shall not be considered as a radio link failure.
3) When a lower layer failure happens while the mobile station attempts to connect back to the old channels in a
channel assignment procedure or handover procedure.
4) In some cases where timers are started to detect the lack of answer from the other party, as described in section 3.
The two first cases are known by the term "lower layer failure".
3.4.13.5.1 Mobile side
When a radio link failure is detected by the mobile station,
- the MS shall perform a local end release on all signalling links;
- the mobile station shall go back to idle mode and, when possible, to group receive mode;
- the RR sublayer of the mobile station shall indicate an RR connection failure to the MM sublayer unless
When the uplink has been allocated and the network detects a lower layer failure, the network shall set the uplink free
and provide an UPLINK FREE message on the main signalling channel, when appropriate.
When a radio link failure has been detected, an indication is passed to the upper Mobility Management sublayer on the
network side.
3.4.14 Receiving a RR STATUS message by a RR entity
If the RR entity of the mobile station receives a RR STATUS message no transition and no specific action shall be taken
as seen from the radio interface, i.e. local actions are possible.
ETSI
77 draft ETSI EN 300 940 V7.7.0 (2000-04)
The actions to be taken on receiving a RR STATUS message in the network are an implementation dependent option see
also section 8.
3.4.15 Group receive mode procedures
Only applicable for support of VGCS listening or VBS listening.
3.4.15.1 Mobile station side
3.4.15.1.1 Reception of the VGCS or VBS channel
In group receive mode, the mobile station receives the downlink of the voice broadcast channel or voice group call
channel for which the channel description was provided within the notification message or in the related command
message. The mobile station should also listen to the CCCH of the serving cell. Moreover, it measures the received
levels on the serving cell and on the neighbour cells to assess the need for a cell reselection as specified in GSM 05.08.
The general cell reselection procedure for the mobile station in group receive mode is described in GSM 03.22.
Information on neighbour cells used for cell reselection and reception of the VGCS or VBS channel in the neighbour
cells may be provided on the downlink messages (see section 3.4.15.1.2). If no such information is provided or
information is missing, the mobile station shall try to read this information on the BCCH and NCH of the neighbour
cells.
3.4.15.1.2 Monitoring of downlink messages and related procedures
Mobile stations in group receive mode shall monitor messages related to the following procedures on the VGCS or VBS
channel downlink and act appropriately in order to be able to keep receiving the VGCS or VBS channel downlink.
All messages for mobile stations in group receive mode shall be sent in UI format on the VGCS or VBS channel
downlink. Mobile stations in group receive mode shall ignore all messages which are not sent in UI format or which are
not related to the following mentioned procedures.
The mobile should also monitor messages on the PCH or NCH of the current cell.
3.4.15.1.2.1 Spare
3.4.15.1.2.2 Spare
3.4.15.1.2.3 Channel mode modify procedure
The mobile station shall receive CHANNEL MODE MODIFY messages. The mobile station shall use the new channel
mode but shall not transmit any response to the network.
3.4.15.1.2.4 Notification and paging information
The mobile station shall monitor messages related to notification and paging procedures.
The RR entity shall provide indications on all received notifications for voice group calls or voice broadcast calls to the
upper layer. The indication shall include the notified group or broadcast call reference and, if provided, and if the
mobile station supports eMLPP the related priority.
On request by the upper layer to join another voice broadcast call or voice group call for which a corresponding
notification has been received on the VGCS or VBS channel downlink, the RR entity shall read the corresponding
notification on the NCH.
If the mobile station has received a paging message with its own mobile station identity on the PCH or on the voice
broadcast channel or voice group call channel downlink, the RR entity shall provide an indication to the upper layers,
together with the related priority, if applicable.
ETSI
78 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.4.15.1.2.4.1 Use of Reduced NCH monitoring
This section applies to mobile stations which are in group receive mode or group transmit mode of dedicated mode and
which in addition want to receive notification messages for other voice broadcast calls or voice group calls and which
aim at reducing the reception load.
If the reduced NCH monitoring mechanism is used on the NCH as defined in section 3.3.3.3, when the MS in group
receive mode or group transmit mode enters a cell, it should read the NCH until it has received at least two messages on
the NCH indicating NLN, with the two last received NLN being identical. Then it should stop reading the NCH until it
receives on the SACCH an NLN(SACCH) different from the last previously received NLN.
For this, a parameter is provided on the SACCH in the SYSTEM INFORMATION TYPE 6 message:
- NLN(SACCH): Notification List Number (received on the SACCH).
If a mobile station receives on the SACCH an NLN(SACCH) different from the last received NLN it may read the NCH
until it has received at least two messages on the NCH indicating NLN with the two last received NLN being identical.
If a message in the SACCH is not received correctly the MS may read the NCH until it has received at least two
messages on the NCH indicating NLN, with the two last received NLN being identical.
NOTE: If the NLN(SACCH) is not provided on the SACCH, the mobile station, depending on its particular
implementation, may either read the NCH while being in group receive mode or group transmit mode or
may not be able to receive notifications for other voice group calls or voice broadcast calls other than
those notifications provided on the FACCH.
3.4.15.1.2.5 Uplink status messages
Mobile stations supporting VGCS talking shall monitor the VGCS uplink control related messages UPLINK FREE and
UPLINK BUSY.
3.4.15.1.2.6 Channel release message
The mobile station shall receive CHANNEL RELEASE messages. On receipt of a CHANNEL RELEASE message, the
RR entity shall go to idle mode and give an indication to the upper layer. (See also section 3.4.15.1.4.1, 4
th
paragraph.)
3.4.15.1.2.7 Information on paging channel restructuring
On receipt of a SYSTEM INFORMATION TYPE 6 message indicating that paging channel restructuring has taken
place, if the mobile station wants to be able to read its paging subchannel while in group receive mode or group transmit
mode, the mobile station should read the related messages on the BCCH to know the position of its paging group.
3.4.15.1.3 Uplink reply procedure
Only applicable for mobile stations supporting VGCS talking .
On receipt of an UPLINK FREE message with an uplink access request indication from the network on the voice group
call channel downlink, the mobile station shall send two UPLINK ACCESS messages on the voice group call channel
with establishment cause Reply on uplink access request and then stop immediately transmitting on the uplink.
The first UPLINK ACCESS message shall be transmitted by the mobile station with a random delay between 0 and
20 ms. The second UPLINK ACCESS messages shall be repeated after a further period of 100 ms plus a random delay
between 0 and 20 ms.
If an uplink identity code (UIC) of the current cell has been provided by the network in the UPLINK FREE message, the
mobile station shall use this UIC for the coding of the UPLINK ACCESS messages. If no UIC is provided, the mobile
station shall use the BSIC received of the serving cell, for instance as received from the initial synchronization.
ETSI
79 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.4.15.1.4 Leaving the group receive mode
3.4.15.1.4.1 Returning to idle mode
If the mobile station enters a new cell in which:
- notifications for the current group or broadcast call are sent; but
- no VGCS or VBS channel description for the current group or broadcast call is provided;
the mobile station shall go to idle mode and give an indication to the upper (sub-)layers.
NOTE: Upper (sub-)layers then can request the establishment of an RR connection in order to be informed about
the channel description by the network.
If the mobile station enters a cell in which notifications for the current group or broadcast call are not sent, the mobile
station shall disconnect locally the TCH, go to idle mode and give an indication to the upper (sub-)layers.
On request by the upper layer in order to respond to a paging message the RR entity shall go to the idle mode in order to
establish a dedicated RR connection.
On receipt of a CHANNEL RELEASE message in UI format from the network the RR entity shall go to idle mode and
give an indication to the upper layer.
If the upper layer requests to abort the group receive mode, the mobile station shall go back to idle mode.
3.4.15.1.4.2 Going to group transmit mode
If the upper layer requests an uplink access, the mobile station shall perform the uplink investigation procedure as
defined in section 3.3.1.2.1.1.
If the uplink investigation procedure is not successful, the mobile station shall give an indication to the upper layers and
remain in group receive mode.
If the uplink investigation procedure is successful, the uplink access procedure is initiated as defined in section
3.3.1.2.1.2.
If the uplink access procedure is successful, the mobile station shall give an indication to the upper layers and enter the
group transmit mode.
If the uplink access procedure is not successful, the mobile station shall give an indication to the upper layers and remain
in group receive mode.
3.4.15.2 Network side
3.4.15.2.1 Provision of messages on the VGCS or VBS channel downlink
3.4.15.2.1.1 General
The network shall provide all messages directed to mobile stations in group receive mode (see section 3.4.15.1.2) in
unacknowledged mode. Those messages which are also sent to the mobile station in group transmit mode in
acknowledged mode have therefore to be repeated in addition as UI messages on the VGCS channel downlink if they
shall also be received by mobile stations in group receive mode.
3.4.15.2.1.2 Provision of general information messages
In the case where the group call area exceeds one cell, the network should provide the SYSTEM INFORMATION
TYPE 6 message on the SACCH related to the voice broadcast channel or voice group call channel.
ETSI
80 draft ETSI EN 300 940 V7.7.0 (2000-04)
In addition, if the group call area exceeds one cell, the network should provide SYSTEM INFORMATION TYPE 5
(possibly together with TYPE 5bis and 5ter) on the SACCH related to the voice broadcast channel or voice group call
channel.
- The SYSTEM INFORMATION TYPE 5, TYPE 5bis and TYPE 5ter messages provide information on the
BCCH frequency of the neighbour cells.
- The SYSTEM INFORMATION TYPE 6 message provides information on the location area of the current cell,
possibly the status of the NCH, and an indication of whether paging channel restructuring has taken place.
- $(ASCI)$ Optional messages of the SYSTEM INFORMATION TYPE 10 message type provide information
improving cell re-selection in group receive mode.
The network may also provide layer 3 messages for notification on the VGCS or VBS channel downlink FACCH.
3.4.15.2.1.3 Provision of messages related to the voice group call uplink channel
Only applicable for the support of VGCS talking.
The network shall provide UPLINK FREE messages on the main signalling link of all voice group call channels when
the uplink is set free. The provision of UPLINK FREE messages shall be repeated as long as no uplink is granted to a
mobile station.
The network shall provide an UPLINK BUSY message on the main signalling link of all voice group call when the
uplink has been granted to a mobile station.
The network may send UPLINK FREE messages containing an uplink access request on the main signalling channel of
the VGCS channels in order to obtain knowledge on whether any listening mobile is present in a cell or not. If there is
no mobile station responding to the uplink access request, the network may decide to clear the VGCS channel in that
cell.
3.4.15.2.2 Release of the VGCS or VBS Channels
If a release request for a voice group call is received from the upper layer, the network, after having released the RR
connection with the mobile station in group transmit mode, shall stop the notification procedures for that voice group
call and clear all related voice group call channels.
If a release request for a voice broadcast call is received from the upper layer, the network shall stop the notification
procedures for that voice broadcast call and locally disconnect any channel related to the voice broadcast call.
3.4.15.3 Failure cases
If the mobile station looses the voice group call channel or voice broadcast channel, the mobile station shall search all
possible channel positions on the current cell and the neighbour cells for which a channel description is known for that
call.
3.4.16 Configuration change procedure
This is only applicable for multislot configuration.
The configuration change procedure is used by the network to change the number of timeslots used in a multislot
configuration. The procedure can also be used to change the channel mode of one or several channels and change their
allocation. The main signalling link however, cannot be changed by the configuration change procedure. If a change of
the main signalling link is needed, the assignment or handover procedures shall be used.
The network shall not initiate a new configuration change procedure before a response to the previous
CONFIGURATION CHANGE COMMAND message has been received from the mobile station.
3.4.16.1 Configuration change initiation
The procedure starts when the network sends a CONFIGURATION CHANGE COMMAND to the mobile station on the
main DCCH. The message indicates:
ETSI
81 draft ETSI EN 300 940 V7.7.0 (2000-04)
- which timeslots to use in uplink;
- which timeslots to use in downlink; and
- which channel set each timeslot belongs to.
The message may also contain definitions of the channel mode to be applied for one or several channel sets. If a
previously undefined channel set is defined by the CONFIGURATION CHANGE COMMAND a definition of the
channel mode for the new channel set shall be included in the message.
3.4.16.2 Configuration change completion
When the mobile station receives the CONFIGURATION CHANGE COMMAND it changes its configuration in
accordance with the message contents and returns a CONFIGURATION CHANGE ACKNOWLEDGE on the same
channel as the command message was received, confirming the new channel configuration. This applies irrespective of
whether the new configuration is different from the one already in use by the mobile station or if it is the same.
If the CONFIGURATION CHANGE COMMAND message instructs the mobile station to use a Channel Configuration
or Mode(s) that it does not support, or if the channel mode to use is not defined for all channel sets, the mobile station
shall return a CONFIGURATION CHANGE REJECT message with cause channel mode unacceptable, and the mobile
station shall remain on the current channel(s) and use the old Channel Configuration and Channel Mode(s).
3.4.17 Mapping of user data substreams onto timeslots in a multislot
configuration
For multislot configurations the following rules for mapping of the user data substreams onto timeslots shall apply for
each channel set:
at initial assignment (using assignment procedure), the lowest numbered user data substream shall be mapped to
the lowest numbered timeslot etc. in ascending order (the user data substreams are numbered 0 to (n-1), where n
is the number of substreams)
at channel changes using handover procedure or assignment procedure (where none of the timeslots are present in
both the old and the new configuration), the lowest numbered user data substream shall be mapped to the lowest
numbered timeslot etc. in ascending order (the user data substreams are numbered 0 to (n-1), where n is the
number of substreams)
at channel changes using assignment procedure (where at least one of the timeslots is the same in both the old and
the new configuration) or configuration change procedure:
user data substream(s) mapped to timeslot(s) that are present in both the old and the new configuration shall
continue to be mapped to the same timeslot(s) as before the channel change; and
possibly added timeslot(s) shall carry the lowest numbered available user data substream so that the lowest
numbered data substream among the added is mapped to the lowest numbered added timeslot and so on in
ascending order.
NOTE: The user data substream number is a number that need not be the same as the inband number used for
transparent services. The user data substream number is only used as a point of reference to a specific user
data substream.
3.4.18 Handling of classmark information at band change
The coding of some fields in the Mobile Station Classmark 1 and in the Mobile Station Classmark 2 information
elements depends on the band in use as described in subclause 10.5.1.5 and subclause 10.5.1.6. When a command to
change the frequency band (GSM 900, DCS 1800) has been received (by, e.g., an IMMEDIATE ASSIGNMENT
message, an ASSIGNMENT COMMAND message, a HANDOVER COMMAND message or a FREQUENCY
REDEFINITION message) the following applies:
ETSI
82 draft ETSI EN 300 940 V7.7.0 (2000-04)
- When an IMMEDIATE ASSIGNMENT message is received, the band used for the purpose of coding the
classmark information in the service request message, see subclause 3.1.5, shall be understood as the band used
for the CHANNEL REQUEST message or (one of) the band(s) indicated by the IMMEDIATE ASSIGNMENT
message.
- For other cases the band used for the purpose of coding the classmark information shall be understood as one
of the bands used or attempted to be used within the 2 seconds preceding the passing of the layer 3 message
containing the classmark information to the layer 2 send queue as described in GSM 04.06.
NOTE: This definition means that when a band change is being done the network must take appropriate actions to
handle possible ambiguities in the frequency band related information in the classmark.
3.4.19 Assignment to a Packet Data channel
This section is only applicable to mobile stations supporting the <<GPRS>> option.
When in dedicated mode or in group transmit mode, the network may wish to change the resources used by a mobile
station that supports the <<GPRS option>>. This change may be performed through the assignment to a Packet Data
Channel procedure.
The purpose of the assignment to PDCH channel procedure is to completely modify the physical channel configuration
of the mobile station without frequency redefinition or change in synchronization while staying in the same cell.
The assignment to PDCH procedure only commences in dedicated mode or in group transmit mode. This procedure
cannot be used in the idle mode.
The assignment to PDCH procedure includes:
- the suspension of normal operation.
- the release of the main signalling link, and of the other data links as defined in section 3.1.4, and the
disconnection of TCHs if any.
- the deactivation of previously assigned channels (layer 1)
- The triggering of the establishment of a Temporary Block Flow .
The assignment to PDCH procedure is always initiated by the network.
3.4.19.1 Assignment to PDCH initiation
The network initiates the assignment to PDCH procedure by sending a PDCH ASSIGNMENT COMMAND message to
the mobile station on the main signalling link. It then starts timer T3117.
the Frequency List IE and Cell Channel Description IE used in the PDCH ASSIGNMENT COMMAND
message, see section 10.5.2.13 and section 10.5.2.1b.
signalling layer messages except for those RR messages needed for this procedure and for abnormal cases is suspended
until resumption is indicated. These RR messages can be deduced from sections 3.4.3 and 8.8 Radio Resource
management.
Upon receipt of the PDCH ASSIGNMENT COMMAND message, the mobile station initiates a local end release of
dedicated mode link layer connections, disconnects the physical channels, commands the switching to the identified
channels and obeys the procedures relevant to the establishment of the Temporary Block Flow. The mobile station starts
timer T3190.
The PDCH ASSIGNMENT COMMAND message contains the description of either the uplink TBF or the downlink
TBF.
The information on the power to be used on the target TBF shall not affect the power used on the old channel(s).
ETSI
83 draft ETSI EN 300 940 V7.7.0 (2000-04)
A PDCH ASSIGNMENT COMMAND message may indicate a frequency change in progress, with a starting time and
In the case of the reception of a PDCH ASSIGNMENT COMMAND message which contains only the description of a
TBF to be used after the starting time, the mobile station shall wait up to the starting time before using the TBF. If the
starting time has already elapsed, the mobile shall use the TBF as an immediate reaction to the reception of the message
(see GSM 05.10 for the timing constraints).
If the message contains both the description of a TBF to be used after the indicated time and of a TBF to be used before,
the mobile station uses the TBF as an immediate reaction to the reception of the message. If the moment the mobile
station is ready to access is before the indicated time, the mobile station uses the TBF described for before the starting
time. The mobile station then changes to the TBF described for after the starting time at the indicated time. New
parameters can be frequency list, MAIO and HSN. Other parameters describing the allocated channels shall be identical
to the parameters described for before the starting time. If the moment the mobile station is ready to access is after the
starting time, the mobile station uses the TBF described for after the starting time.
If frequency hopping is applied, the cell allocation if present in the message is used to decode the mobile allocation. If
the cell allocation is not included, the mobile station uses its current cell allocation, the current CA is the last CA
received on the BCCH. Afterward, the current CA may be changed by some messages sent on the main signalling link
containing a CA (the possible messages are: ASSIGNMENT COMMAND, HANDOVER COMMAND and
FREQUENCY REDEFINITION). Note that there are cases in which the current CA is undefined, see section 3.4.3.3.
The PDCH ASSIGNMENT COMMAND does not contain a cipher mode setting IE. Any RR layer ciphering that may
have been applied in dedicated mode shall not be applied to the target TBF.
3.4.19.2 Completion of the Assignment to PDCH procedure
The network regards the procedure as successfully completed when RLC/MAC blocks are received from the mobile
station on the target TBF. The network then stops timer T3117.
The mobile station regards the procedure as successfully completed when RLC/MAC blocks with any TFI are received
on the new PDCH.
If the mobile station has no current CA and if it needs a CA to analyse the PDCH ASSIGNMENT COMMAND
message, it stays on the current channel(s) and sends an ASSIGNMENT FAILURE message with cause "no cell
allocation available".
If the PDCH ASSIGNMENT COMMAND message instructs the mobile station to use a Coding Scheme that it does not
support then the mobile station shall return an ASSIGNMENT FAILURE message with cause "channel mode
unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or
Channel Mode(s).
If the PDCH ASSIGNMENT COMMAND message instructs the mobile station to use a frequency that it is not capable
of, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "frequency not implemented",
and the mobile station shall remain on the current channel(s).
If the mobile station receives a PDCH ASSIGNMENT COMMAND message with a Frequency List IE indicating
frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send an
ASSIGNMENT FAILURE message with cause "frequency not implemented". If the mobile station receives a PDCH
ASSIGNMENT COMMAND message with a Mobile Allocation IE indexing frequencies that are not all in one band,
then the mobile station shall stay on the current channel(s) and send an ASSIGNMENT FAILURE message with cause
"frequency not implemented".
NOTE: A PDCH ASSIGNMENT COMMAND message sent to a multi band mobile station shall not be
considered invalid because it indicates frequencies that are all in a different frequency band to that of the
current channel.
On the mobile station side, if RLC/MAC blocks are not successfully received within T3190 seconds, the mobile station
reactivates the old channels, reconnects the TCHs if any and triggers the establishment of the main signalling link. It
then sends an ASSIGNMENT FAILURE message, cause "protocol error unspecified" on the main DCCH and resumes
ETSI
84 draft ETSI EN 300 940 V7.7.0 (2000-04)
the normal operation, as if no assignment attempt had occurred. The operational parameters (e.g. ciphering mode) when
returning on the old channel are those applied before the procedure.
When receiving the ASSIGNMENT FAILURE message, the network stops T3117.
If a lower layer failure happens while attempting to connect back to the old channels, the radio link failure procedure is
applied (see section 3.4.13.2).
On the network side, if timer T3117 elapses before either the network receives an RLC/MAC block from the mobile
station on the new channel, or, an ASSIGNMENT FAILURE message is received on the old channels, then the old
channels and the new resources are released, except that, if the old channel was a VGCS channel, the old channel shall
be maintained and the uplink shall be set free.
On the network side, lower layer failure occurring on the old channels after the sending of the PDCH ASSIGNMENT
COMMAND message are ignored.
3.4.20 RR-Network Commanded Cell Change Order
This section is only applicable to mobiles supporting the <<GPRS>> option.
In dedicated mode or in group transmit mode, intracell or intercell change of channel(s) can be requested by the network
RR sublayer. This change may be performed through the RR-network commanded cell change order procedure.
The purpose of the RR-network commanded cell change order procedure is to permit the complete modification of the
channels allocated to the mobile station e.g. when the cell is changed. This procedure only commences while in
dedicated mode or in group transmit mode.
The RR-network commanded cell change order procedure includes:
- The suspension of normal operation except for RR management (layer 3).
- The disconnection of the main signalling link, and of the other links via local end release (layer 2), and the
disconnection of the TCH(s) if any.
- The disconnection and the deactivation of previously assigned channels and their release (layer 1).
The complete acquisition of BCCH or PBCCH messages of the target cell.
- The triggering of the establishment of a Temporary Block Flow.
The RR-network controlled cell change order procedure is always initiated by the network.
3.4.20.1 RR-network commanded cell change order initiation
The network initiates the RR-network controlled cell change order procedure by sending a RR-CELL CHANGE
ORDER message to the mobile station on the main DCCH. The network then starts timer T3119.
When a handover has taken place during dedicated connection, the network shall send a RR-CELL CHANGE ORDER
message to the mobile station in order to establish TBF. In this case the target cell is equal to the old cell.
signalling layer messages except for those RR messages needed for this procedure and for abnormal cases, is suspended
until resuming is indicated. These RR messages can be deduced from section 3.4.3 and 8.5.1 "Radio Resource
management".
Upon receipt of the RR-CELL CHANGE ORDER message, the mobile station starts timer T3134, and initiates, as
described in section 3.1.4, the release of link layer connections, disconnects the physical channels, commands the
switching to the identified cell, performs a complete acquisition of BCCH or PBCCH messages (see GSM 04.60), and
obeys the procedures relevant to the establishment of the Temporary Block Flow. The mobile station shall obey the RR-
CELL CHANGE ORDER irrespective of whether or not the mobile station has any knowledge of the relative
synchronisation of the target cell to the serving cell.
The RR-CELL CHANGE ORDER message contains:
ETSI
85 draft ETSI EN 300 940 V7.7.0 (2000-04)
- The characteristics of the new cell that are necessary to identify it (i.e. BSIC + BCCH frequency);
- the NC mode to be initially applied on the new cell.
The RR-CELL CHANGE ORDER does not contain a cipher mode setting IE. Any RR layer ciphering that may have
been applied in dedicated mode shall not be applied to the target TBF or with the target cell.
3.4.20.2 Network controlled cell reselection completion
The network regards the procedure as successfully completed when it knows that communication has been established
with that mobile station via the new cell (e.g. the network has received a RLC/MAC Block containing the mobile
stations identity). The network then stops timer T3119.
The mobile station regards the procedure as successfully completed when it has received a response to a (PACKET)
CHANNEL REQUEST message on the new cell which allocates it a resource on the new cell.
If the RR-CELL CHANGE ORDER message instructs the mobile station to use a frequency that it is not capable of, then
the mobile station shall return a HANDOVER FAILURE message with cause "frequency not implemented", and the
On the mobile station side, if timer T3134 times out before a response to the (PACKET) CHANNEL REQUEST
message has been received, or, if an IMMEDIATE ASSIGNMENT REJECT message or a PACKET ACCESS REJECT
is received from the new cell, or, if the contention resolution procedure fails on the new cell then the mobile station shall
reactivate the old channels, reconnect the TCHs if any and trigger the establishment of the main signalling link. It then
sends a HANDOVER FAILURE message on the main signalling link and resumes normal operation as if no handover
attempt had occurred. The operational parameters (e.g. ciphering mode) when returning on the old channel are those
applied before the RR-CELL CHANGE ORDER message was received.
When the HANDOVER FAILURE message has been received, the network stops T3119.
If a lower layer failure happens while attempting to connect back to the old channels, the standard rules are applied (cf.
section 3.4.13.2).
On the network side, if timer T3119 elapses before either the mobile station has been recognised on the new cell, or a
HANDOVER FAILURE message is received on the old channels, then the old channels are released, except that, if the
old channel was a VGCS channel, the old channel shall be maintained and the uplink shall be set free.
On the network side, lower layer failures occurring on the old channels after the sending of the RR-CELL CHANGE
ORDER message are ignored.
3.4.21 Application Procedures
3.4.21.1 General
While in dedicated mode, the following applications associated with the Radio Resource management layer may be
supported in the network and MS:
Location Services (LCS)
Common procedures are defined in the Radio Resource management layer to assist these applications.
3.4.21.2 Application Information Transfer
The Application Information Transfer procedure enables an Application on the network side and a peer application in
the MS to exchange Application Protocol Data Units (APDUs).
ETSI
86 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.4.21.2.1 Normal Procedure without Segmentation
The maximum size of an APPLICATION INFORMATION message is 251 octets as defined in GSM 04.06.
Segmentation shall not be used when an APDU fits into a single APPLICATION INFORMATION message of
maximum or smaller size.
APPLICATION INFORMATION [APDU, C/R ]
<--------------------------
APPLICATION INFORMATION [APDU, C/R]
-------------------------->
Figure 3.4/GSM 04.08: Application Information Transfer without segmentation
Either the network or MS may send an APPLICATION INFORMATION message once the MS is in dedicated mode.
The APDU Data in the APPLICATION INFORMATION message shall contain a complete APDU according to the
protocol in use. The APDU ID IE identifies the protocol and associated application. The APDU Flags IE indicates First
or Only Segment, Last or Only Segment and conveys a C/R flag transparently between the communicating
applications. The C/R Flag may be used to distinguish a command from other messages and a final response from a non-
final response. The use of the C/R flag is defined with respect to each application. On receiving an APPLICATION
INFORMATION message, the receiving layer 3 entity shall deliver the message contents to the identified local
application.
3.4.21.2.2 Normal Procedure with Segmentation
Segmentation is applicable when an APDU is too large to fit into a single APPLICATION INFORMATION message.
The procedure is applicable for either direction of transfer.
Mobile Station or Network Network or Mobile Station
APPLICATION INFORMATION [APDU segment, First Segment, not Last Segment]
<--------------------------
APPLICATION INFORMATION [APDU segment, not First Segment, not Last Segment]
<--------------------------
APPLICATION INFORMATION [APDU segment, not First Segment, Last Segment, C/R]
<--------------------------
Figure 3.5/GSM 04.08: Application Information Transfer with segmentation
The sending layer 3 entity shall segment an APDU by dividing it into one or more segments exactly fitting into
maximum sized APPLICATION INFORMATION messages plus a final segment fitting into an APPLICATION
INFORMATION message of maximum size or smaller. Once segmented, the resulting APPLICATION
INFORMATION messages shall be transferred in sequence to the data link layer for transmission, without being
intersperced by other level 3 messages. The first APPLICATION INFORMATION message in the sequence shall
indicate First Segment and Not Last Segment. Subsequent APPLICATION INFORMATION messages except for
the last shall indicate Not First Segment and Not Last Segment. The last APPLICATION INFORMATION message
shall indicate Not First Segment and Last Segment and shall include a C/R flag as provided by the sending
application.
The receiving layer 3 entity shall reassemble any segmented APDU before transfer to the local application. The receiver
may employ a timer to detect possible loss of APDU segments. If employed, the timer shall be started when the first
APDU segment is received and cancelled after the last segment is received.
3.4.21.2.3 Abnormal Cases
APPLICATION INFORMATION messages are sent using low priority at the data link layer. This can lead to message
loss or truncation when preempted by other high priority messages. A receiving layer 3 entity shall detect APDU
truncation if an APPLICATION INFORMATION message is received carrying an APDU or APDU segment that is
shorter than indicated by the length indicator for the APDU Data IE. This test is reliable because preemption in the data
link layer guarantees that at least the first 2*N201 octets of any truncated message will be reliably transferred.
An APPLICATION INFORMATION transfer error shall be detected due to any of the following:
ETSI
87 draft ETSI EN 300 940 V7.7.0 (2000-04)
(a) Receipt of a truncated APDU or APDU segment;
(b) While performing APDU reassembly
- receipt of any other layer 3 message defined to use SAPI 0 on the main DCCH;
- receipt of an APDU or APDU segment indicating First or Only Segment;
- expiration of the reassembly timer (if supported);
(c) While not performing APDU reassembly, receipt of an APDU segment indicating not First or only segment;
(d) Detection of any other error for a received message as defined in clause 8.
If APDU reassembly was in process when the error occurred, the receiving layer 3 entity shall discard the partially
reassembled APDU and reprocess any received APDU or APDU segment that caused the error provided not an error
defined in clause 8. In all other cases, any received APDU or APDU segment shall be discarded.
3.5 RR procedures on CCCH related to temporary block flow
establishment
The establishment of a temporary block flow (TBF) on a packet data physical channel is supported by procedures on
CCCH when PCCCH is not provided in the cell. The procedures for temporary block flow establishment using CCCH
are only applicable to a mobile station supporting GPRS. The procedures are optional for the network.
These procedures constitute a complement to the corresponding procedures for temporary block flow establishment
using PCCCH, defined in GSM 04.60, and include the procedures using CCCH for packet paging (section 3.5.1), packet
access (section 3.5.2) and packet downlink assignment (section 3.5.3).
3.5.1 Packet paging procedure using CCCH
The network can initiate the packet paging procedure in order to cause upper layers in the mobile station to respond, see
section 4. The packet paging procedure can only be initiated by the network.
3.5.1.1 Packet paging initiation by the network
The packet paging procedure is initiated by the RR entity of the network side. It is triggered by a page request from the
MM sublayer, see GSM 04.07.
The network initiates the paging procedure by sending a paging request message on an appropriate paging subchannel
on CCCH or PCCCH. Paging initiation using a paging subchannel on CCCH is used when sending paging information
to a mobile station and PCCCH is not present in the cell.
NOTE 1: There are three types of paging request messages that are applicable:
- PAGING REQUEST TYPE 1;
- PAGING REQUEST TYPE 2; and
- PAGING REQUEST TYPE 3.
In a PAGING REQUEST message used for the packet paging procedure, the mobile station shall be identified by the P-
TMSI (GPRS TMSI) or its IMSI. If the mobile station is identified by the P-TMSI, it shall proceed as specified in
section 3.5.1.2.
If the mobile station identified by its IMSI, it shall parse the message for a corresponding Packet Page Indication field:
- if the Packet Page Indication field indicates a paging procedure for RR connection establishment, or the field
is not present in the message, the mobile station shall proceed as specified in section 3.3.2.2;
- if the Packet Page Indication field indicates a packet paging procedure, the mobile station shall proceed as
A PAGING REQUEST message may include more than one mobile station identification.
ETSI
88 draft ETSI EN 300 940 V7.7.0 (2000-04)
The mobile station in packet idle mode is required to receive and analyse the paging messages and immediate
assignment messages sent on the paging subchannels on CCCH corresponding to the paging groups determined for it in
packet idle mode, as specified in GSM 05.02. These messages contain a page mode information element.
NOTE 2: The possible immediate assignment messages are: the IMMEDIATE ASSIGNMENT, the IMMEDIATE
ASSIGNMENT EXTENDED and the IMMEDIATE ASSIGNMENT REJECT messages.
The treatment of page mode information, including the procedure when the mobile station selects a new PCH, and the
procedure if a message in a paging subchannel is not received correctly are defined in section 3.3.2.1.1.
3.5.1.2 On receipt of a packet paging request
On the receipt of a paging request message, the RR sublayer of addressed mobile station indicates the receipt of a paging
request to the MM sublayer, see GSM 04.07;
3.5.2 Packet access procedure using CCCH
The packet access procedure using CCCH may be used to establish a temporary block flow to support the transfer of
LLC PDUs in the direction from the mobile station to the network. Establishment using one phase and two phase packet
access, see GSM 04.60, are supported. The two phase packet access is supported by means of the single block packet
access option in this procedure, allowing the transfer of a PACKET RESOURCE REQUEST message to the network.
The single block packet access option in this procedure may also be used by a mobile station in packet idle mode to
transfer an RLC/MAC control message other than the PACKET RESOURCE REQUEST message to the network, see
section 3.5.2.2.
3.5.2.1 Entering the packet transfer mode: packet access procedure
The establishment of an uplink temporary block flow may be initiated by the RR entity of the mobile station using the
packet access procedure. The procedure is triggered by a request from upper layers to transfer a LLC PDU, see
GSM 04.07. The request from upper layers specifies radio priority and an RLC mode associated with the packet transfer
or it indicates that the packet to be transferred contains signalling.
Upon such a request,
- if access to the network is allowed (section 3.5.2.1.1), the RR entity of the mobile station initiates the packet
access procedure as defined in section 3.5.2.1.2;
- otherwise, it rejects the request.
If the request from upper layers indicates signalling, the highest radio priority level shall be used at determination if
access to the network is allowed, and the acknowledged RLC mode shall be used.
3.5.2.1.1 Permission to access the network
Access to the network is allowed:
- if the mobile station is a member of at least one authorized access class or special access class as defined in
section 3.3.1.1.1, and
- if packet access is allowed in the cell for the radio priority level associated with the packet transfer, as indicated
by the PRIORITY_ACCESS_THR parameter broadcast in SI 13 message.
- if the cell belongs to one of the allowed LSAs for the mobile station, as indicated on the SIM, in the case where
the mobile station is a LSA only access subscriber.
3.5.2.1.2 Initiation of the packet access procedure: channel request
The mobile station initiates the packet access procedure by scheduling the sending of CHANNEL REQUEST messages
on RACH and leaving the packet idle mode. In particular, the mobile station shall ignore PAGING REQUEST messages
indicating a packet paging procedure.
ETSI
89 draft ETSI EN 300 940 V7.7.0 (2000-04)
A mobile station belonging to GPRS MS class A or B shall continue to monitor its paging subchannel on CCCH for
PAGING REQUEST messages indicating an establishment of RR connection. A mobile station belonging to GPRS MS
class B may abort the packet access procedure at the receipt of a PAGING REQUEST messages indicating an
establishment of RR connection.
The mobile station schedules CHANNEL REQUEST messages on RACH as defined in section 3.3.1.1.2.
The CHANNEL REQUEST messages are sent on RACH and contain the parameters:
- an establishment cause which indicates packet access, and as applicable, a request for one phase packet access or
single block packet access (section 9.1.8);
- a random reference which is drawn randomly from an uniform probability distribution for every new
transmission.
If the requested RLC mode is unacknowledged mode, the mobile station shall request a single block packet access and
attempt a two phase packet access.
If the purpose of the packet access procedure is to send a Page Response, Cell update, for a GPRS Mobility
Management or a GPRS Session Management procedure, (i.e. the access is for Layer 3 signalling only, and not for a
Layer 3 data transfer), the mobile station shall request a one phase packet access.
After sending the first CHANNEL REQUEST message, the mobile station shall start listening to the BCCH; it shall also
listen to the full downlink CCCH timeslot corresponding to its CCCH group.
Having sent the maximum number of CHANNEL REQUEST messages, the mobile station starts timer T3146. At expiry
of timer T3146, the packet access procedure is aborted and a packet access failure is indicated to upper layers.
If the mobile station receives an IMMEDIATE ASSIGNMENT message during the packet access procedure indicating a
packet downlink assignment procedure, the mobile station shall abort the packet access procedure and respond to the
IMMEDIATE ASSIGNMENT message as specified in section 3.5.3.1.2. The mobile station shall then attempt an
establishment of uplink TBF, using the procedure specified in GSM 04.60 which is applicable in packet transfer mode.
3.5.2.1.3 Packet immediate assignment
3.5.2.1.3.1 On receipt of a CHANNEL REQUEST message
On receipt of a CHANNEL REQUEST message indicating a packet access, the network may allocate a temporary flow
identity and assign a packet uplink resource comprising one PDCH for an uplink temporary block flow.
If the establishment cause in the CHANNEL REQUEST message indicates a request for a single block packet access,
the network shall grant only the single block period on the assigned packet uplink resource if the network allocates
resource for the mobile station.
If the establishment cause in the CHANNEL REQUEST message indicates a request for one phase packet access, the
network may grant either a one phase packet access or a single block packet access for the mobile station. If a single
block packet access is granted, it forces the mobile station to perform a two phase packet access.
The packet uplink resource is assigned to the mobile station in an IMMEDIATE ASSIGNMENT message sent in
unacknowledged mode on the same CCCH timeslot on which the network has received the CHANNEL REQUEST
message. There is no further restriction on what part of the downlink CCCH timeslot the IMMEDIATE ASSIGNMENT
message can be sent. Timer T3141 is started on the network side.
The IMMEDIATE ASSIGNMENT message contains:
- the information field of the CHANNEL REQUEST message and the frame number of the frame in which the
CHANNEL REQUEST message was received;
- the packet channel description;
- the initial timing advance;
- the packet uplink assignment construction.
ETSI
90 draft ETSI EN 300 940 V7.7.0 (2000-04)
If frequency hopping is applied, the network may use the indirect encoding or the direct encoding of the frequency
configuration in the Packet Channel Description information element. If the indirect encoding is used, the mobile station
uses information received in system information or stored from a previous assignment to determine the frequency
parameters, see GSM 04.60. If the direct encoding is used, the mobile station uses the cell allocation defined for the cell
to decode the mobile allocation.
If the indirect encoding is used, the IMMEDIATE ASSIGNMENT message may contain a CHANGE_MARK_1 field.
If that is present, the mobile station shall verify the validity of the SI13_CHANGE_MARK associated with the GPRS
mobile allocation to which the message refers, see GSM 04.60. If the CHANGE_MARK_1 field and the
SI13_CHANGE_MARK do not match, the message does not satisfactorily define a PDCH.
If the mobile station receives an IMMEDIATE ASSIGNMENT message and the Dedicated mode or TBF information
element indicates that this is the first message in a two-message assignment, the mobile station shall continue to listen to
the full CCCH. The network may send a second IMMEDIATE ASSIGNMENT message to the mobile station within
two multiframe periods following the first IMMEDIATE ASSIGNMENT message, specifying the packet channel
description and, if required, a mobile allocation for the assignment. The two IMMEDIATE ASSIGNMENT messages in
a two-message assignment shall have the same contents of the Request Reference information elements.
If the mobile station does not receive the second IMMEDIATE ASSIGNMENT messages in a two-message assignment
within two multiframe periods following the first message, the mobile station shall discard the first IMMEDIATE
ASSIGNMENT message received.
On receipt of an IMMEDIATE ASSIGNMENT message or, in case of a two-message assignment, a matching pair of
IMMEDIATE ASSIGNMENT messages corresponding to one of its 3 last CHANNEL REQUEST messages, the mobile
station stops T3146 (if running), stops sending CHANNEL REQUEST messages, and switches to the assigned PDCH.
The content of the packet uplink assignment construction indicates which type of packet access is granted: one phase
packet access or single block packet access
3.5.2.1.3.2 One phase packet access
In the case the one phase packet access is granted, the packet uplink assignment construction contains:
- the temporary flow identity;
- the USF value, if the medium access method is dynamic allocation;
or
the fixed allocation bitmap, if the medium access method is fixed allocation;
- the channel coding scheme for RLC data blocks;
- the power control parameters;
- the polling bit ;- optionally, the timing advance index (see GSM 05.10);
- optionally, the TBF starting time (note: TBF starting time is mandatory if medium access method is fixed
allocation).
The medium access method is dynamic allocation or fixed allocation and the RLC mode is acknowledged mode, see
GSM 04.60.
The mobile station shall start timer T3164 and proceed with the contention resolution at one phase access defined in
GSM 04.60.
If the medium access method is fixed allocation, and the number of blocks allocated in the ALLOCATION_BITMAP is
not sufficient to transfer all the RLC/MAC blocks that the MS has to transmit at the time the packet uplink assignment
construction is received, the MS shall request additional resources by sending a PACKET RESOURCE REQUEST on
one of the allocated blocks.
If the timing advance index (TAI) is included in the packet uplink assignment construction, the mobile station shall use
the continuous update timing advance mechanism, see GSM 05.10, using PTCCH in the same timeslot as the assigned
PDCH. If a timing advance index (TAI) field is not included, the continuous update timing advance mechanism shall not
be used.
ETSI
91 draft ETSI EN 300 940 V7.7.0 (2000-04)
In case the packet uplink assignment construction contains a TBF starting time and the mobile station receives the
message before the TBF starting time has expired, it shall wait until the frame number indicated by the TBF starting time
before accessing the channel. If the mobile station receives the message after the TBF starting time has expired, it shall
ignore the TBF starting time and may immediately access the channel.
If the Polling bit is set to 1, MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message (see 04.60) on
the assigned PDCH, in the uplink block specified by the TBF Starting Time. In this case the TBF Starting Time is used
both to indicate when the assigned PDCH becomes valid and to specify the uplink block. If the TBF Starting Time is not
present or has expired, the MS shall ignore the polling request.
3.5.2.1.3.3 Single block packet access
In the case the single block packet access is granted, the packet uplink resource description contains:
- the power control parameter setting;
- the TBF starting time.
If the mobile station receives the IMMEDIATE ASSIGNMENT message before the TBF starting time has expired, it
shall wait until the block period indicated by the TBF starting time. The network shall use the TBF starting time to
indicate the first frame number belonging to the single block period granted for packet access. The mobile station may
either use the assigned block period to send a PACKET RESOURCE REQUEST message to initiate the two phase
packet access procedure defined in GSM 04.60, or to send an RLC/MAC control message other than the PACKET
RESOURCE REQUEST message to the network, see section 3.5.2.2.
If the mobile station receives the IMMEDIATE ASSIGNMENT message after the TBF starting time has expired, a
failure has occurred.
If a failure occurs and the packet access attempt was due to a request from upper layers to transfer a LLC PDU, a TBF
establishment failure has occurred and the mobile station proceeds as specified in section 3.5.2.1.5. If a failure occurs
and the packet access attempt was due to the sending of an RLC/MAC control message, the packet access is aborted, the
mobile station returns to packet idle mode.
3.5.2.1.3.4 Packet access rejection
The network may send to the mobile station an IMMEDIATE ASSIGNMENT REJECT message in unacknowledged
mode on the same CCCH timeslot on which the channel request message was received. There is no further restriction on
what part of the downlink CCCH timeslot an IMMEDIATE ASSIGNMENT REJECT message can be sent. This
message contains the request reference and a wait indication.
On receipt of an IMMEDIATE ASSIGNMENT REJECT message corresponding to one of its 3 last CHANNEL
REQUEST messages, the mobile station stops sending CHANNEL REQUEST messages, starts timer T3142 with the
indicated value, ("wait indication" information element), starts T3146 if it has not already been started, and listens to the
downlink CCCH until T3146 expires. During this time, additional IMMEDIATE ASSIGNMENT REJECT messages are
ignored, but any immediate assignment corresponding to any other of its 3 last CHANNEL REQUEST messages make
the mobile station follow the procedure in section 3.5.2.1.3.1. If no such immediate assignment is received, the mobile
station returns to packet idle mode and notify higher layers (TBF establishment failure).
If the mobile station has received responses from the network on all, or in case more than 3 were sent the last 3, of its
CHANNEL REQUEST messages, it shall immediately return to packet idle mode and notify higher layers.
The mobile station is not allowed to make a new attempt for packet access in the same cell until T3142 expires, but may
attempt packet access in an other cell after successful cell reselection for radio conditions reasons (see GSM 05.08). The
value of the wait indication (i.e. T3142) relates to the cell from which it was received.
The mobile station may initiate RR connection establishment in the same cell before T3142 has expired, see section
3.3.1.1.3.2.
ETSI
92 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.5.2.1.4 Packet access completion
The one phase packet access procedure is completed at a successful contention resolution. The mobile station has
entered the packet transfer mode. Timer T3141 is stopped on the network side. Timer T3164 is stopped on the mobile
station side.
If a failure occurs on the mobile station side before a successful contention resolution procedure is completed, the
allocated temporary block flow is released; the mobile station returns to packet idle mode, upper layers are notified
(TBF establishment failure), transactions in progress are aborted:
- If a TLLI mismatch has occurred during the contention resolution procedure, and the repetition of the packet
access has been repeated the maximum number of times as defined in GSM 04.60, a TBF establishment failure
has occurred.
- If the information available in the mobile station, after the reception of an IMMEDIATE ASSIGNMENT
message or the second IMMEDIATE ASSIGNMENT message of a two-message assignment, does not
satisfactorily define a PDCH, a TBF establishment failure has occurred.
- If the mobile allocation indexes frequencies in more than one frequency band then a TBF establishment failure
has occurred.
- If an IMMEDIATE ASSIGNMENT message indicates a PDCH in a non-supported frequency band then a TBF
establishment failure has occurred.
On the network side, if timer T3141 elapses before a successful contention resolution procedure is completed, the newly
allocated temporary block flow is released as specified in GSM 04.60 and the packet access is forgotten.
3.5.2.2 Sending an RLC/MAC control message: single block packet access
procedure
The sending of an RLC/MAC control message other than the PACKET RESOURCE REQUEST message from a mobile
station in packet idle mode to the network may be initiated by the RR entity on the mobile station side using the packet
access procedure. If access to the network is allowed (section 3.5.2.1.1), the packet access is done according to the
procedures defined in sections 3.5.2.1.2 and 3.5.2.1.3, using the single block packet access option defined in section
3.5.2.1.3.3.
Further action depends on the RLC/MAC control message sent by the mobile station, see GSM 04.60. Unless otherwise
indicated by the RLC/MAC control message, the mobile station remains in packet idle mode.
3.5.3 Packet downlink assignment procedure using CCCH
The packet downlink assignment procedure using CCCH may be used to establish a temporary block flow to support the
transfer of LLC PDUs in the direction from the network to the mobile station.
This procedure may also be used to assign a single downlink block on a PDCH to support the transfer of an RLC/MAC
control message from the network to a mobile station in packet idle mode, see 3.5.3.2.
3.5.3.1 Entering the packet transfer mode: packet downlink assignment procedure
The establishment of a downlink temporary block flow may be initiated by the RR entity on the network side using the
packet downlink assignment procedure. The procedure is triggered by a request from upper layers to transfer a LLC
PDU, see GSM 04.07. The request from upper layers specifies an optional Priority level, a QoS profile including the
requested RLC mode, optional DRX parameters, an optional IMSI and an optional MS Radio Access Capability
associated with the packet transfer.
Upon such a request, the network shall determine whether the mobile station is in packet idle mode or packet transfer
mode. The packet downlink assignment procedure using CCCH is applicable when the mobile station is in packet idle
mode and when there is no PCCCH present in the cell.
ETSI
93 draft ETSI EN 300 940 V7.7.0 (2000-04)
The network may allocate a temporary flow identity and assign a packet downlink resource comprising one PDCH for a
downlink temporary block flow.
3.5.3.1.2 Initiation of the packet downlink assignment procedure
The network initiates the packet downlink assignment procedure by sending an IMMEDIATE ASSIGNMENT message
in unacknowledged mode on the CCCH timeslot corresponding to CCCH group the mobile station belongs to. The
appropriate CCCH group is calculated from the IMSI, see 05.02. The behaviour of the network when the RR entity does
not receive the IMSI from the upper layers is implementation dependent for the calculation of the CCCH group where
the IMMEDIATE ASSIGNMENT message has to be sent. If the mobile station is in non-DRX mode or if the RR entity
does not receive the IMSI or the DRX parameters from the upper layers, there is no further restriction on what part of
the downlink CCCH timeslot the IMMEDIATE ASSIGNMENT message, or the first part of the IMMEDIATE
ASSIGNMENT message (in the case of a two-message assignment), can be sent. If the mobile station applies DRX, the
IMMEDIATE ASSIGNMENT message, or the first part of the IMMEDIATE ASSIGNMENT message (in the case of a
two-message assignment), shall be sent in a CCCH block corresponding to a paging group determined for the mobile
station in packet idle mode, see GSM 05.02.
The IMMEDIATE ASSIGNMENT message contains:
- the packet channel description;
- the initial timing advance;
- the packet downlink assignment construction
The contents of the packet downlink assignment construction determines the further action. At the establishment of a
downlink temporary block flow, the packet downlink assignment construction shall contain:
- the TLLI;
- the temporary flow identity;
- the RLC mode;
- the power control parameters;
- the polling bit ;
- the initial timing advance validity flag ;
- optionally, the timing advance index (see GSM 05.10);
- optionally, the TBF starting time
If frequency hopping is applied, the network may use the indirect encoding or the direct encoding of the frequency
configuration in the Packet Channel Description information element. If the indirect encoding is used, the mobile station
uses information received in system information or stored from a previous assignment to determine the frequency
parameters, see GSM 04.60. If the direct encoding is used, the mobile station uses the cell allocation defined for the cell
to decode the mobile allocation.
If the indirect encoding is used, the IMMEDIATE ASSIGNMENT message may contain a CHANGE_MARK_1 field.
If that is present, the mobile station shall verify the validity of the SI change mark associated with the GPRS mobile
allocation to which the message refers, see GSM 04.60. If the CHANGE_MARK_1 field and the SI change mark do not
match, the message does not satisfactorily define a PDCH.
If the mobile station receives an IMMEDIATE ASSIGNMENT message and the Dedicated mode or TBF information
element indicates that this is the first message in a two-message assignment, the mobile station shall start listen to the
full CCCH. The network may send a second IMMEDIATE ASSIGNMENT message to the mobile station within two
multiframe periods following the first IMMEDIATE ASSIGNMENT message, specifying the packet channel
description and, if required, a mobile allocation for the assignment. The two IMMEDIATE ASSIGNMENT messages in
a two-message assignment shall have the same contents of the Request Reference information elements.
ETSI
94 draft ETSI EN 300 940 V7.7.0 (2000-04)
If the mobile station was operating in DRX mode when it received the first message of a two-message assignment, the
network shall not send the second IMMEDIATE ASSIGNMENT message within the two block periods immediately
following the first message.
If the mobile station does not receive the second IMMEDIATE ASSIGNMENT messages in a two-message assignment
within two multiframe periods following the first message, the mobile station shall discard the first IMMEDIATE
ASSIGNMENT message received. After the two multiframe periods following the first message, the mobile station may
resume to DRX mode.
On receipt of an IMMEDIATE ASSIGNMENT message or, in case of a two-message assignment, a matching pair of
IMMEDIATE ASSIGNMENT messages, the mobile station stops monitoring downlink CCCH and switches to the
assigned PDCH and starts listening for downlink RLC/MAC blocks identified by the assigned TFI; it starts timer T3190.
The IMMEDIATE ASSIGNMENT message may indicate a TBF starting time. If the mobile station receives the
message before the TBF starting time has expired, it shall wait until the frame number indicated by the TBF starting
time, start timer T3190 and switch to the assigned PDCH. If the mobile station receives the message after the TBF
starting time has expired, it shall ignore the indicated TBF starting time, immediately start timer T3190 and switch to the
assigned PDCH.
If the Polling bit is set to 1, MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message (see 04.60) on
the assigned PDCH, in the uplink block specified by the TBF Starting Time. In this case the TBF Starting Time is used
both to indicate when the assigned PDCH becomes valid and to specify the uplink block. If the TBF Starting Time is not
present or has expired, the MS shall ignore the polling request.
An IMMEDIATE ASSIGNMENT message may indicate a timing advance index (TAI) in the packet timing advance IE.
The mobile station shall then use the continuous update timing advance mechanism, see GSM 05.10, using PTCCH in
the same timeslot as the assigned PDCH. If there is no indication of a timing advance index, the continuous update
timing advance mechanism shall not be used.
The TA_VALID flag indicates if the value of the Timing Advance IE is valid or not.
If the network does not have a valid timing advance value for the mobile station to include in the IMMEDIATE
ASSIGNMENT message, the network shall use the procedures defined in GSM 04.60 on the assigned TBF, or the
polling mechanism defined in the above paragraph if the PACKET CONTROL ACKNOWLEDGEMENT format is set
to four access bursts, to obtain a timing advance value and to update the initially assigned timing advance value before
the mobile station is required to transmit other than access burst on the newly assigned channel.
3.5.3.1.3 Packet downlink assignment completion
After having sent the packet downlink assignment, the network starts sending downlink RLC/MAC blocks on the
assigned packet downlink resource and the packet downlink assignment procedure is completed at the network side.
On the mobile station side, the procedure is completed when the mobile station receives an RLC/MAC block identified
by the assigned temporary flow identity. The mobile station stops timer T3190. The mobile station has entered packet
transfer mode.
If a failure occurs on the mobile station side before the packet downlink assignment procedure is completed (TBF
establishment failure), the temporary block flow is released; the mobile station returns to packet idle mode:
- If the mobile station does not receive a RLC/MAC block on the assigned PDCHs before timer T3190 expires,
then a TBF establishment failure has occurred.
- If the information available in the mobile station, after the reception of an IMMEDIATE ASSIGNMENT
message or the second IMMEDIATE ASSIGNMENT message of a two-message assignment, does not
satisfactorily define a PDCH, then a TBF establishment failure has occurred.
- If the mobile allocation in the frequency parameters indexes frequencies in more than one frequency band, then a
TBF establishment failure has occurred.
If an IMMEDIATE ASSIGNMENT message indicates a PDCH in a non-supported frequency band, then a TBF
establishment failure has occurred.
ETSI
95 draft ETSI EN 300 940 V7.7.0 (2000-04)
3.5.3.2 Sending an RLC/MAC control message: single block packet downlink
assignment procedure
The sending of an RLC/MAC control message to a mobile station in packet idle mode may be initiated by the RR entity
on network side using the packet downlink assignment procedure. The procedure is used to assign a single downlink
block on a PDCH for the transfer of the RLC/MAC control message.
The single downlink block assignment is done according to the procedure defined in 3.5.3.1.2, with the following
exceptions:
The packet downlink assignment construction in the IMMEDIATE ASSIGNMENT message shall contain only:
- the TLLI; and
- the TBF starting time.
If the mobile station receives the IMMEDIATE ASSIGNMENT message before the TBF starting time has expired, it
shall wait until the frame number indicated by the TBF starting time. The network shall use the TBF starting time to
indicate the first frame number belonging to the single block period assigned to the mobile station. The mobile station
shall switch to the assigned PDCH and attempt to decode an RLC/MAC control message in the assigned downlink
block. Further action depends on the RLC/MAC control message sent by the network, see GSM 04.60. Unless otherwise
indicated by the RLC/MAC control message, the mobile station remains in packet idle mode. If the mobile station
remains in packet idle mode, it shall continue to monitor downlink CCCH once the block period indicated by the TBF
starting time has passed.
If the mobile station fails to decode or does not receive an RLC/MAC control message in the assigned downlink block, it
shall remain in packet idle mode and continue to monitor downlink CCCH once the block period indicated by the TBF
starting time has passed.
If the mobile station receives the IMMEDIATE ASSIGNMENT message after the TBF starting time has expired, it shall
ignore the assignment.
If a failure occurs on the mobile station side due to any other reason, the mobile station shall ignore the assignment.
4 Elementary procedures for Mobility Management
4.1 General
This section describes the procedures used for mobility management for non-GPRS services and for GPRS-services at
the radio interface (Reference Point Um).
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 GSM 04.07).
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 and GMM-AA entity of the MM sublayer),
see GSM 04.07 [20].
All the MM procedures described in this section 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 according to the
procedures specified in section 3.3. The GMM procedures described in this section, use services provided by the RR
sublayer without prior RR connection establishment.
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
ETSI
96 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 GSM
03.60.
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 section 4.3.5.
Initiated by the mobile station:
- IMSI detach procedure (with the exceptions specified in section 4.3.4).
ii) 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.
iii) 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, two types of GMM procedures can be distinguished:
i) GMM common procedures:
Initiated by the network when a GMM context has been established:
- P-TMSI (re-) allocation;
- GPRS authentication and ciphering;
- GPRS identification;
- GPRS information.
ETSI
97 draft ETSI EN 300 940 V7.7.0 (2000-04)
ii) 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.
4.1.1.2 MM-GMM co-ordination for GPRS MSs
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 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 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: 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: 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, uses the combined GMM specific procedures
in place of the MM specific procedures, so all conditions describing when to trigger a MM specific procedure listed in
subsections 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) except in some error and abnormal cases. If the MM
timers are already running, the MS should not react on the expiration of the timers.
NOTE: Whenever GMM performs a combined GMM procedure, a GPRS MS enters the MM state MM
LOCATION UPDATING PENDING in order to prevent the MM to perform a location update 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 shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM
is removed. The MS shall abort any GMM procedure and shall enter state GMM-DEREGISTERED.
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 subsections 4.3 and 4.4
and the GMM specific procedures listed in subsections 4.7.3, 4.7.4 and 4.7.5. The applicability of periodic location
updating is further specified in section 4.4.2 and the periodic routing area updating is specified in section 4.7.2.2.
ETSI
98 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM
is removed. The MS shall abort any GMM procedure and shall enter state GMM-DEREGISTERED.
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 section 4.1.2.1.1. The MM IDLE state is subdivided in substates for the description of the
behaviour in idle mode (section 4.1.2.1.2). This behaviour depends on an update status, described in 4.1.2.2. The states
for the network side are described in 4.1.2.3.
4.1.2.1 MM sublayer states in the mobile station
In this section, the possible states for the MM sublayer in the mobile station is described. In figure 4.1/GSM 04.08 an
overview of the MM sublayer protocol is given.
4.1.2.1.1 Main states
0 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.
(
G
S
M

0
4
.
0
8

v
e
r
s
i
o
n

7
.
3
.
0

R
e
l
e
a
s
e

1
9
9
8
)
E
T
S
I
9
9
d
r
a
f
t

E
T
S
I

E
N

3
0
0

9
4
0

V
7
.
7
.
0

(
2
0
0
0
-
0
4
)

Attach or Location
update needed
Attach and Location
update not needed
RR connection
established
Location
update reject
Location update
accept
RR connection released
New LAI, connection request
or T3212/T3211 timeout
MS deactivated
and attach NOT
allowed
MM-connection
request
RR connection
established
First message
received
Last connection
released
Low layer failure
and reestablish
RR connection
established
(paging)
MS deactivated
and attach
allowed
MS deactivated and
attach allowed
RR connection
established
RR connection
released
low layer
failure
Low layer failure
and reestablish
Reestablish
not possible
update SIM
States 6,
20
Send IMSI
detach
Request
RR connection
Send cm
reestablish
request
Indicate
MM connection
Send cm service
request
Confirm
MM connection
Send cm service
request
Request
RRconnection
Update SIM
Store system info
Delete system info
Send location
update request
Request
RR connection
Activate RR
IMSI DETACH
INITIATED
7
WAIT FOR
REESTABLISH
17
MM CONNECTION
ACTIVE
6
WAIT FOR
RR CONNECTION
(IMSI DETACH)
15
WAIT FOR
OUTGOING
MM CONNECTION
5
WAIT FOR
RR CONNECTION
(MM CONNECTION)
14
LOCATION UPDATING
INITIATED
3
LOCATION UPDATE
REJECTED
10
WAIT FOR
RR CONNECTION
(LOCATION UPDATE)
13
WAIT FOR
RR ACTIVE
18
NULL
States 3, 5, 9,
10, 13, 14, 15
CM reestablish-
ment accepted
WAIT FOR NETWORK
COMMAND
9
SIM
inserted
MS
activated
Delete
system
info !!
low layer failure and
no reestablish
CM service
accept
MM-IDLE
19
Ciphering started
or CM service
accept
MM connection
request
WAIT FOR
ADDITIONAL
OUTGOING
MMCONNECTION
20
RR connection
released
.
F
i
g
u
r
e

4
.
1
a

/

G
S
M

0
4
.
0
8
:

O
v
e
r
v
i
e
w

m
o
b
i
l
i
t
y

m
a
n
a
g
e
m
e
n
t

p
r
o
t
o
c
o
l

/

M
S

S
i
d
e
ETSI
100 draft ETSI EN 300 940 V7.7.0 (2000-04)

RR gone to
Group Transmit
mode
21
MM CONNECTION
ACTIVE
(Group TX MODE )
22
WAIT FOR RR
CONNECTION
(Group TX MODE )
RR Connection
established
6
MM CONNECTION
ACTIVE
19
MM-IDLE
5
WAIT FOR
OUTGOING
MM CONNECTION
Send CM service
request
or
Notification Response
RR gone to
Dedicated
mode
Uplink
release
Uplink
access
rejected
Uplink
access
requested
RR connection
released, gone
to group receive
Mode
RR connection
released, gone
to Group Receive
mode
Additions to Figure 4.1.a/GSM 04.08
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.
ETSI
101 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
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 is inserted, or ME plus SIM.). The
service state depends on the update status (see 4.1.2.2) and on the selected cell.
19.1 NORMAL SERVICE
Valid subscriber data are available, update status is U1, 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
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.
ETSI
102 draft ETSI EN 300 940 V7.7.0 (2000-04)
19.4 NO IMSI
No valid subscriber data (no SIM, or the SIM 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 U1 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., in the case of access class blocking.
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 U1, 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 U1, 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 section 4.1.2.1 and which control the MM sublayer protocol, an update
status exists.
The update status pertains to a specific subscriber embodied by a SIM. This status is defined even when the subscriber is
not activated (SIM removed or connected to a switched-off ME). It is stored in a non volatile memory in the SIM. 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, or network initiated GPRS detach procedure.
U1 UPDATED
The last location updating attempt was successful (correct procedure outcome, and the answer was acceptance
from the network). With this status, the SIM contains also the LAI of the LA where the subscriber is
registered, and possibly valid TMSI, ciphering key and ciphering key sequence number. The "Location
update status" stored on the SIM shall be "updated".
ETSI
103 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 does not contain any valid LAI, TMSI, 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 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 does not contain any valid LAI, TMSI, 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 ROAMING NOT ALLOWED. However the presence of other values shall not be considered an error
by the mobile station. The "Location update status" stored on the SIM shall be "Location Area not allowed".
4.1.2.3 MM sublayer states on the network side
1. 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.
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. CIPHERING MODE INITIATED
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.
ETSI
104 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section, the GMM protocol of the MS and the network are described by means of two different state machines. In
section 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 section 4.1.3.2. The states for the network side are described in section 4.1.3.3.
4.1.3.1 GMM states in the MS
In this section, the possible GMM states are described of a GMM entity in the mobile station. Section 4.1.3.1.1
summarises the main states of a GMM entity, see figure 4.1b/GSM 04.08. The substates that have been defined are
described in section 4.1.3.1.2 and section 4.1.3.1.3.
However, it should be noted that this section 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/GSM 04.08 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 section 4.2. Especially, with respect to the behaviour of the MS in abnormal cases it is referred to section 4.7.
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.
ETSI
105 draft ETSI EN 300 940 V7.7.0 (2000-04)
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, 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.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 is inserted, or ME plus SIM). The selection of the appropriate substate depends on the
GPRS update status, see section 4.1.3.2, and on the selected cell.
4.1.3.1.2.1 GMM-DEREGISTERED.NORMAL-SERVICE
Valid subscriber data is available, the GPRS update status is GU1 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 GU1. 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.
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, or the SIM is not considered valid by the ME) and a cell has been
selected.
4.1.3.1.2.6 GMM-DEREGISTERED.NO-CELL-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-SEARCH
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).
ETSI
106 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.1.3.1.2.8 GMM-DEREGISTERED.SUSPENDED
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 is inserted, or ME plus SIM.).
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
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. 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 class
of 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-CELL-AVAILABLE
GPRS coverage has been lost. In this substate, the MS shall not initiate any GMM procedures except of cell (and
PLMN) reselection.
ETSI
107 draft ETSI EN 300 940 V7.7.0 (2000-04)

GMM-NULL
GMM-ROUTING-
AREA-UPDATING-
INITIATED
GMM-
DEREGISTERED
- enable
GPRS mode
- DETACH requested
(not power off)
GMM-
REGISTERED
Any state
GMM-
DEREGISTERED-
INITIATED
- ATTACH
requested
- ATTACH rejected
DETACH requested
(power off)
- Network init. DETACH requested
- Lower layer failure
- ATTACH
accepted
- RAU rejected
- Network init. DETACH requested
-
implicit DETACH
- DETACH accepted
- disable
GPRS mode
- RAU
requested
- RAU accepted
- RAU failed
GMM-
REGISTERED-
INITIATED
Figure 4.1b/GSM 04.08:GMM main states in the MS
4.1.3.1.3.6 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-DETACH-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.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. This status is defined even when the
subscriber is not activated (SIM removed or connected to a switched off ME). It is stored in a non volatile memory in
the SIM. The GPRS update status is changed only after execution of a GPRS attach, network initiated GPRS detach,
authentication procedure, or routing area updating procedure.
ETSI
108 draft ETSI EN 300 940 V7.7.0 (2000-04)
GU1: 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 contains the RAI of the routing area (RA) to which the subscriber
was attached, and possibly a valid P-TMSI, GPRS ciphering 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 may contain the RAI of the routing area (RA) to which the subscriber was attached, and
possibly also a valid P-TMSI, GPRS ciphering 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).
For this status, the SIM does not contain any valid RAI, P-TMSI, GPRS ciphering key or GPRS ciphering key
sequence number. For compatibility reasons, all these fields must be set to the value deleted at the moment the
status is set to ROAMING NOT ALLOWED. 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 subsection, the possible states are described for the GMM on the network side. Section 4.1.3.3.1 summarises the
main states. The corresponding substates are described in section 4.1.3.3.2.
However, it should be noted that this section 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/GSM 04.08 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 section 4.2. Especially, with respect to the behaviour of the MS in abnormal cases it is referred to section 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 section 4.1.1, has been started. The network is awaiting the answer from the
MS.
4.1.3.3.1.3 GMM-REGISTERED
The GMM context has been established 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.
ETSI
109 draft ETSI EN 300 940 V7.7.0 (2000-04)
GMM-
DE-REGISTERED
- Network initiated
DETACH requested
GMM-
REGISTERED
GMM-COMMON-
PROCEDURE-INITIATED
GMM-
DE-REGISTERED-
INITIATED
- COMMON procedure
failed
- ATTACH procedure
successful
- MS initiated
DETACH requested
RAU rejected
implicit DETACH
- DETACH accepted
- COMMON procedure
successful
- ATTACH procedure
successful
- COMMON procedure
requested
- COMMON procedure
requested
Figure 4.1c/GSM 04.08: GMM main states on the network 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-SERVICE
User data and signalling information may be sent and received.
4.1.3.3.2.2 GMM-REGISTERED.SUSPENDED
In this substate, the lower layers shall be prevented of sending user data or signalling information.
4.2 Behaviour of the MS in MM Idle state, GMM-
DEREGISTERED state and GMM-REGISTERED state
In this section, the detailed behaviour of the MS in the main states MM IDLE, GMM-DEREGISTERED and GMM-
REGISTERED is described. Sections 4.2.1 to 4.2.3 refer to the state MM IDLE, whereas section 4.2.4 and section 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.
The specific behaviour in the MM IDLE state depends on the service state of the mobile station as described in section
4.1.2.1.2. The service state depends in particular on the update status which is defined in section 4.1.2.2.
How an appropriate service state is chosen after power on is described in section 4.2.1, and the specific behaviour of the
mobile station in MM IDLE state is described in section 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.):
ETSI
110 draft ETSI EN 300 940 V7.7.0 (2000-04)
- results of procedures on RR connected mode (see section 4.2.3);
- insertion or removal of the SIM;
- cell selection/reselection (see also GSM 03.22);
- 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 sections 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 GSM 03.22 and 05.08, where procedures for power on and selection of
PLMN is described in detail. If the "Location update status" stored on the SIM is different from "updated", then the
mobile shall act as if the "Location update status" stored on the SIM 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:
- if no cell has been found, the state is NO CELL AVAILABLE, until a cell is found;
- if no SIM 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 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;
- 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
as specified in paragraph 4.2.1.1.
ETSI
111 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.2.2 Detailed Description of the MS behaviour in MM IDLE State
In the MM IDLE state the mobile station shall behave according to the service state. In the following sections 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, section 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 T3211 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 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 section 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 section 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;
- 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 section 4.5.1);
- respond to paging (with IMSI).
ETSI
112 draft ETSI EN 300 940 V7.7.0 (2000-04)
- 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;
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;
- 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).
4.2.2.4 Service State, NO IMSI
When in state MM IDLE and service state NO IMSI the mobile station shall (see section 3.2, GSM 03.22 and
GSM 05.08):
- not start any normal location updating attempt;
- 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.
- not indicate notifications to the GCC or BCC layer.
ETSI
113 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 T3211 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;
- support requests from the CM layer;
- listen as far as possible to paging, and respond.
- listen as far as possible to notifications and indicate notifications to the GCC or BCC layer;
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 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)
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 periodic updating at expiration of timer T3212;
- support requests from the GCC or BCC layers;
- indicate notifications or paging information to the GCC or BCC layer;
ETSI
114 draft ETSI EN 300 940 V7.7.0 (2000-04)
- request the RR sublayer to receive another voice group or broadcast call if the GCC or BCC sublayer requests the
by the RR sublayer.
4.2.2.8 Service State, RECEIVING GROUP CALL (LIMITED SERVICE)
When in state MM IDLE and service state RECEIVING GROUP CALL (LIMITED SERVICE), the mobile station
shall:
- 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);
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
GSM 03.22. 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:
- if no cell has been found, the state is NO CELL AVAILABLE, until a cell is found;
- if no SIM is present, or if the inserted SIM 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 paragraph 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);
ETSI
115 draft ETSI EN 300 940 V7.7.0 (2000-04)
- after some abnormal cases occurring during an unsuccessful location updating procedure, as described in
paragraph 4.4.4.9, the state is ATTEMPTING TO UPDATE.
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 section 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 4.7.5).
The selection of the appropriate substate of GMM-DEREGISTERED after switching on is described in section 4.2.4.1.
The specific behaviour of the MS in state GMM-DEREGISTERED is described in section 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
section 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;
- cell selection/reselection (see also GSM 03.22 [14]);
- 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 section 4.7.
4.2.4.1 Primary substate selection
4.2.4.1.1 Selection of the substate after power on or enabling the MSs GPRS capability
When the MS is switched on, the substate shall be PLMN-SEARCH in case the SIM is inserted and valid. See
GSM 03.22 [14] and 05.08 [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 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.
ETSI
116 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 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 (section 4.7.3) have
been performed.
- optionally, when 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 (section 4.7.5) 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 sections, 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 T3311 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 section 4.7.3.1.5 ,
GPRS attach shall be performed when a new cell is entered; and
- if entry into this state was caused by c) or d) with cause different from Retry upon entry into a new cell of
section 4.7.3.1.5, GPRS attach shall not be performed when a new cell is entered.
- 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 T3311 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;
ETSI
117 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.2.4.2.5 Substate, NO-CELL
The MS shall:
- perform cell selection according to GSM 03.22 [14] 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
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 GSM 03.22 [14].
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:
- if no cell has been found, the substate is NO-CELL-AVAILABLE, until a cell is found;
- if no SIM is present or if the inserted SIM 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 GSM 03.22 [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 section 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 GSM 03.22);
- change of RA;
ETSI
118 draft ETSI EN 300 940 V7.7.0 (2000-04)
- loss/regain of coverage.
How various GMM procedures affect the GMM-REGISTERED substates is described in the detailed description of the
procedures in section 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 GSM 03.22 [14];
- 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
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 GSM 03.22 [14]; 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 T3311 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 section
4.7.5.1.5, perform routing area updating when a new cell is entered; and
- shall if entry into this state was caused by c) or d) with cause different from Retry upon entry into a new cell of
section 4.7.5.1.5, not perform routing area updating when a new cell is entered.
ETSI
119 draft ETSI EN 300 940 V7.7.0 (2000-04)
- shall use request from CM layers as triggering the combined routing area update procedure, if the network
operates in network operation mode I. Depending which of the timers T3311 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 GSM 03.22 [14].
4.2.5.1.6 Substate, LIMITED-SERVICE
The MS shall perform cell selection/reselection according to GSM 03.22 [14];
4.2.5.1.7 Substate, ATTEMPTING-TO-UPDATE-MM
The MS shall:
- perform cell selection/reselection according to GSM 03.22 [14];
- 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
T3311 or T3302;
- 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.3 MM common procedures
As described in section 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 GSM 02.09 and 03.20).
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.
The structure of the TMSI is specified in GSM 03.03. 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).
The reallocation of a TMSI can be performed either by a unique procedure defined in this section 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 section 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.
ETSI
120 draft ETSI EN 300 940 V7.7.0 (2000-04)
NOTE 2: Normally the TMSI reallocation will take place in conjunction with another procedure, e.g. at location
updating or at call setup (see GSM 09.02).
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 GSM 03.20).
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. 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. 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 section 3.5).
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;
- 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.
ETSI
121 draft ETSI EN 300 940 V7.7.0 (2000-04)


TMSI REAL CMD
<---------------- Start T3250

TMSI REAL COM
-----------------> Stop T3250

Figure 4.1/GSM 04.08: TMSI reallocation sequence
4.3.2 Authentication procedure
The purpose of the authentication procedure is twofold:
First to permit the network to check whether the identity provided by the mobile station is acceptable or not (see
GSM 03.20);
Second to provide parameters enabling the mobile station to calculate a new ciphering key.
The cases where the authentication procedure should be used are defined in GSM 02.09.
The authentication procedure is always initiated and controlled by the network.
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 GSM 03.20). It also contains the ciphering key sequence number
allocated to the 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. It shall process the challenge information and send back an AUTHENTICATION RESPONSE
message to the network. The new ciphering key calculated from the challenge information shall overwrite the previous
one and be stored on the SIM before the AUTHENTICATION RESPONSE message is transmitted. The ciphering key
stored in the SIM shall be loaded in to the ME when any valid CIPHERING MODE COMMAND is received during an
RR connection (the definition of a valid CIPHERING MODE COMMAND message is given in section 3.4.7.2). The
ciphering key sequence number shall be stored together with the calculated key.
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 GSM 03.20).
4.3.2.4 Ciphering key sequence number
The security parameters for authentication and ciphering are tied together in sets, i.e. from a challenge parameter RAND
both the authentication response SRES and the ciphering key can be computed given the secret key associated to the
IMSI.
In order to allow start of ciphering on a RR connection without authentication, the ciphering key sequence numbers are
introduced. The sequence number is managed by the network in the way that the AUTHENTICATION REQUEST
message contains the sequence number allocated to the key which may be computed from the RAND parameter carried
in that message.
The mobile station stores this number with the key, and indicates to the network in the first message (LOCATION
UPDATING REQUEST, CM SERVICE REQUEST, PAGING RESPONSE, CM RE-ESTABLISHMENT REQUEST)
which sequence number the stored key has. When the deletion of the sequence number is described this also means that
the associated key shall be considered as invalid.
ETSI
122 draft ETSI EN 300 940 V7.7.0 (2000-04)
The network may choose to start ciphering with the stored key (under the restrictions given in GSM 02.09) if the stored
sequence number and the one given from the mobile station are equal.
4.3.2.5 Unsuccessful authentication
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.
If the IMSI 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 section 3.5.
Upon receipt of an AUTHENTICATION REJECT message, the mobile station shall set the update status in the SIM to
U2 ROAMING NOT ALLOWED, delete from the SIM the stored TMSI, LAI and ciphering key sequence number. The
SIM shall be considered as invalid until switching off or the SIM is removed.
If the AUTHENTICATION REJECT message is received in the state IMSI DETACH INITIATED the mobile station
shall follow section 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.
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.
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 any
ongoing MM specific procedure, release all MM connections if any, and initiate the RR connection release
procedure described in section 3.5.

AUT REQ
<------------------ Start T3260
AUT RES
------------------> Stop T3260
(a)
AUT REJ
< - - - - - - - - -
(b)

Figure 4.2/GSM 04.08: Authentication sequence: (a) authentication; (b) authentication rejection
ETSI
123 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 (cf.
GSM 03.03). For the presentation of the IMEI, the requirements of GSM 02.09 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.
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.
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 section 3.5.
ID REQ
<----------------------- Start T3270
ID RES
-----------------------> Stop T3270

Figure 4.3/GSM 04.08: Identification sequence
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 GSM 02.17) is detached from the mobile station. A flag (ATT) broadcast in the 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.
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
ETSI
124 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section
3.5).
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.
If the establishment of an RR connection is unsuccessful, or the RR connection is lost, the IMSI detach is aborted by the
mobile station.
IMSI DET IND
--------------------->

Figure 4.4/GSM 04.08: 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
ETSI
125 draft ETSI EN 300 940 V7.7.0 (2000-04)
delete any TMSI, LAI and ciphering key sequence number stored in the SIM, set the update status to ROAMING NOT
ALLOWED (and store it in the SIM according to section 4.1.2.2) and consider the SIM invalid until switch off or the
SIM 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 section 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.
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 section);
- periodic updating (see section 4.4.2);
- IMSI attach (see section 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
ETSI
126 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 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 card is inserted.
Upon successful location updating the mobile station sets the update status to UPDATED in the SIM, and stores the
received Location Area Identification in the SIM. The attempt counter shall be reset.
The detailed handling of the attempt counter is described in 4.4.4.6 to 4.4.4.9.
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 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.
The cell selection processes in the different states are described in GSM 03.22 and GSM 05.08.
The location updating procedure is always initiated by the mobile station.
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 ciphering 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 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 section 4.2.2.
ETSI
127 draft ETSI EN 300 940 V7.7.0 (2000-04)
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. 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 SYSTEM
INFORMATION TYPE 3 message on the BCCH, in the Control channel description IE, see section 10.5.2.11.
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 t1 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 t1.
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 t1 be the new T3212 timeout value, the new timer shall be started at a value randomly, uniformly drawn
between 0 and t1.
4.4.3 IMSI attach procedure
The IMSI attach procedure is the complement of the IMSI detach procedure (see section 4.3.4). It is used to indicate the
IMSI as active in the network. A flag (ATT) is broadcast in the SYSTEM INFORMATION TYPE 3 message. 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, 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. Otherwise a normal location updating procedure (see section 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 section 3.3.
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.1a Network Request for Additional mobile station Capability Information
The network may initiate the classmark interrogation procedure, for example, to obtain further information on the
mobile stations 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 section 4.3.3).
ETSI
128 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.4.4.3 Authentication by the network
The authentication procedure (see section 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 GSM 02.09).
4.4.4.4 Ciphering mode setting by the network
The ciphering mode setting procedure (see section 3.4.7) may be 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 is specified in section
4.4.4.9.
The attempt counter is reset when:
- the mobile station is powered on;
- a SIM is inserted;
- location update is successfully completed;
- location update completed with cause #11, #12 or #13 (see section 4.4.4.7).
and in case of service state ATTEMPTING to UPDATE:
- 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 T3211.
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 section 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 ACCEPT
message together with the location area identifier LAI. The network shall in this case start the supervision timer T3250
as described in section 4.3.1.
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 to UPDATED. If the
message contains an IMSI, the mobile station is not allocated any TMSI, and shall delete any TMSI in the SIM
accordingly. If the message contains a TMSI, the mobile station is allocated this TMSI, and shall store this TMSI in the
SIM 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 any of the
"forbidden lists" then any such entries shall be deleted.
ETSI
129 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 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: the interaction between CTS and GPRS procedures are not yet defined.
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. 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 according
to section 4.1.2.2), and delete any TMSI, stored LAI and ciphering key sequence number and shall consider the
SIM as invalid until switch-off or the SIM is removed.
# 11: PLMN not allowed;
# 12: Location Area not allowed; or
# 13: Roaming not allowed in this location area.
The mobile station shall delete any LAI, TMSI and ciphering key sequence number stored in the SIM, reset the
attempt counter, set the update status to ROAMING NOT ALLOWED (and store it in the SIM according to
section 4.1.2.2). The mobile station shall store the LAI or the PLMN identity in the suitable forbidden list, i.e. in
the "forbidden PLMN list" for cause #11, in the list of "forbidden location areas for regional provision of
service" for cause #12, and in the list of "forbidden location areas for roaming" for cause #13. In addition, the
MS will memorize if cause #13 was received, so to perform a PLMN selection instead of a cell selection when
back to the MM IDLE state.
Other values are considered as abnormal cases and the specification of the mobile station behaviour in those cases is
given in section 4.4.4.9.
4.4.4.8 Release of RR connection after location updating
When the Location updating procedure is finished (see sections 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 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 section 3.5. 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 section
4.4.4.9.
ETSI
130 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 access class 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
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
Timer T3213 is started. When it expires the procedure is attempted again if still necessary.
NOTE: As specified in GSM 05.08, 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
GSM 05.08), 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.
g) Location updating reject, other causes than those treated in section 4.4.4.7
The MS waits for release of the RR connection as specified in section 4.4.4.8, and then proceeds as specified
below.
In cases d) to g) 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 T3211 when the RR connection is released. When timer T3211
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:
ETSI
131 draft ETSI EN 300 940 V7.7.0 (2000-04)
The mobile station shall delete any LAI, TMSI, ciphering key sequence number stored in the SIM, set the update
status to NOT UPDATED and enter the MM IDLE sub-state ATTEMPTING TO UPDATE when the RR
connection is released (See section 4.2.2.2 for the subsequent actions). 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.10 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
#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 section 3.5).
LOC UPD REQ
Start T3210 ----------------------->
LOC UPD ACC
Stop T3210 <----------------------
LOC UPD REJ
" <- - - - - - - - - - - -

Figure 4.5/GSM 04.08: Location updating sequence
4.5 Connection management sublayer service provision
The concept of MM connection is introduced in this section. 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 section 3.7.2.1.1).)
The Mobility Management (MM) sublayer is providing connection management services to the different entities of the
upper Connection management (CM) sublayer (see GSM 04.07). 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 sections, the procedures for establishing, re-establishing, maintaining, and releasing an MM connection
are described, usually separately for the mobile station and the network side.
ETSI
132 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.5.1 MM 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 or MM connection active but not in MM connection
active (Group call).
An exception from this general rule exists for emergency calls (see section 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 section 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 (this indication implies that the CM SERVICE REQUEST message has been
successfully transferred via the radio interface, see section 2.2), 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, 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).
ETSI
133 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 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.
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 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.
The identification procedure (see section 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 section 4.3.2) depending on the CM service type.
The network decides also if the ciphering mode setting procedure shall be invoked (see section 3.4.7).
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 GSM 03.67.
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. 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 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 section 3.5) when the CM
SERVICE REJECT message is sent.
ETSI
134 draft ETSI EN 300 940 V7.7.0 (2000-04)
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:
- 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, changes the update status to NOT UPDATED (and stores it in the
SIM according to section 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, changes the update status to ROAMING NOT ALLOWED (and
stores it in the SIM according to section 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK
COMMAND. The mobile station shall consider the SIM as invalid until switch-off or the SIM is removed.
a) RR connection failure or IMSI deactivation
If an RR connection failure occurs 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.
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 section 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, #111 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: 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.
Network side:
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
ETSI
135 draft ETSI EN 300 940 V7.7.0 (2000-04)
# 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 section 3.3.2) and the mobile station
shall enter the MM state WAIT FOR NETWORK COMMAND.
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 ciphering mode setting 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 establishment of an RR connection is unsuccessful, or if any of the MM common procedures or the ciphering
mode setting 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 section 3.3.2) and the mobile station
shall enter the MM state WAIT FOR NETWORK COMMAND.
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 ciphering mode setting procedure.
ETSI
136 draft ETSI EN 300 940 V7.7.0 (2000-04)
The network should use the information contained in the Mobile Station Classmark Type 2 IE on the mobile stations
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 the MM sublayer starts timer
T3240 and enter the state WAIT FOR NETWORK COMMAND, expecting the release of the RR connection.
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.
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.
If the establishment of an RR connection is unsuccessful, or if any of the MM common procedures or the ciphering
mode setting 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.
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 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.
ETSI
137 draft ETSI EN 300 940 V7.7.0 (2000-04)
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"
#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 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 section 5.5.4 and, whether or not a cell allowing call re-establishment has been found (as
described in GSM 05.08). 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 stations 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 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 (this indication implies that the CM RE-ESTABLISHMENT REQUEST message has been
successfully transferred via the radio interface, see section 2.2), 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
ETSI
138 draft ETSI EN 300 940 V7.7.0 (2000-04)
- mobile identity according to section 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 (GSM 04.11), Call Independent Supplementary Services
(GSM 04.10) and Location Services (GSM 04.71) 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 identification procedure (see section 4.3.3) may be invoked.
The network may invoke the authentication procedure (see section 4.3.2).
The network decides if the ciphering mode setting procedure shall be invoked (see section 3.4.7).
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. 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 section
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, changes the update status to NOT UPDATED (and stores it in the SIM according to section 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, changes the update status to ROAMING NOT ALLOWED (and stores it in the SIM according to
section 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. The MS shall consider
the SIM as invalid until switch-off or the SIM is removed.
ETSI
139 draft ETSI EN 300 940 V7.7.0 (2000-04)
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
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 section 4.5.3.1.
e) Reject causes #96, #97, #99, #100, #111 received
The mobile station shall perform the same actions as if timer T3230 had expired.
Network side:
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 stations 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 4.5.3 applies after MM connection
establishment.
ETSI
140 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 4.2.3.
4.5.2 MM connection information transfer phase
After the MM connection has been established, it can be used by the CM sublayer entity for information transfer.
According to the protocol architecture described in GSM 04.07, 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 CM 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.
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.
ETSI
141 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.5.3.1 Release of associated RR connection
If all MM connections are released by their CM entities, the mobile station shall set timer T3240 and enter the state
WAIT FOR NETWORK COMMAND, expecting the release of the RR connection.
In the network, if the last MM connection is released by its user, the MM sublayer may decide to release the RR
connection by requesting the RR sublayer according to section 3.5. 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, 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 section 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 MM STATUS message by a MM 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 section describes the basic functions offered by the mobility management (GMM) sublayer at the radio interface
(reference point U
m
). The functionality is described in terms of timers and procedures. During GMM procedures,
session management procedures, see chapter 6, are suspended.
4.7.1.1 Lower layer failure
The LLC sublayer shall indicate a logical link failure or an RR 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
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 REJECT;
ETSI
142 draft ETSI EN 300 940 V7.7.0 (2000-04)
- IDENTITY REQUEST;
- 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 or routing area update procedure. If the MS has no valid P-TMSI it shall
not use the P-TMSI signature in the subsequent attach or routing area update procedure. Upon successful completion of
the subsequent attach or routing area update procedure the used P-TMSI signature shall be deleted.
4.7.1.4 Radio resource sublayer address handling
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. This section 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 GSM 03.03 [10].
Two cases can be distinguished:
- a valid P-TMSI is available in the MS; or
- no valid P-TMSI is available in the MS
NOTE: For anonymous access, the RR address assignment is handled by the SM sublayer as described in section
6.1.1.1.
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; 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 GU1 UPDATED.
Any other GMM message is transmitted using a local TLLI derived from the stored P-TMSI. This includes a
ROUTING AREA UPDATE REQUEST message that is sent within a periodic routing area update procedure.
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:
- 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 assigns a P-TMSI to the MS, 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.
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.

ETSI
143 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.7.1.5 P-TMSI handling
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 RAI as invalid as soon as an LLC frame is received with the local
TLLI derived from the new P-TMSI.
4.7.1.6 Change of network mode of operation
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.
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/GSM 04.08: Mode A or B
Network operation
mode change
Procedure to execute
I II or I III Normal Location Update(*),
followed by a Normal Routing Area Update
II III or III II Normal Location Update (see section 4.2.2),
II I or III I 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/GSM 04.08: Mode B which reverts into mode C in network operation mode III
Network operation
mode change
I II Normal Location Update(*),
I III or II III IMSI Detach (see section 4.3.4),
II I or III I Combined Routing Area Update with IMSI attach
III II IMSI attach (see section 4.4.3),
c) B which reverts to IMSI attached for CS services only in network operation mode III, the MS shall execute:
ETSI
144 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 4.7.1.6.3/GSM 04.08: Mode B which reverts into IMSI attached for CS services only in network
operation mode III
Network operation
mode change
I II Normal Location Update(*),
I III Normal Location Update(*),
followed by a GPRS Detach with type indicating GPRS Detach
II III Normal Location Update (see section 4.2.2),
followed by a GPRS Detach with detach type indicating GPRS Detach
II I Combined Routing Area Update with IMSI attach
III I Combined GPRS Attach
III II Normal Location Update (see section 4.2.2),
followed by a Normal GPRS Attach
(*) Intended to remove the Gs association in the MSC/VLR.
Further details are implementation issues.
4.7.2 GPRS Mobility management timers
4.7.2.1 READY timer behaviour
The READY timer, T3314 is used in the MS and in the network per each assigned P-TMSI 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 GSM 03.22 [14]). If a routing area border is crossed, a routing area updating procedure shall be performed
instead of a cell update.
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 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 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.
ETSI
145 draft ETSI EN 300 940 V7.7.0 (2000-04)
- 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 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.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.
The timer T3312 is reset and started with its the 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 the initial
value .If the initial READY timer value is zero, the timer T3312 is reset and started with its the initial value, when the
ROUTING AREA UPDATE REQUEST message is transmitted.
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. 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.
The Mobile Reachable timer is reset and started with its the 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.
If after a READY timer negotiation the READY timer value is set to zero the Mobile Reachable timer is reset and
started with its the initial value. If the initial READY timer value is zero, the Mobile Reachable is reset and started with
its the initial value, when the ROUTING AREA UPDATE REQUEST message is received.
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:
ETSI
146 draft ETSI EN 300 940 V7.7.0 (2000-04)
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
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" and shall perform the periodic location updating procedure ; or
c) if the MS returns to coverage in a cell that does not support GPRS, then, depending upon the LA of the cell, the
MS shall either perform the periodic location updating procedure or a normal 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 section 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.
Timer T3312 shall not be stopped when a GPRS MS enters state GMM-REGISTERED.SUSPENDED.
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. It
shall also be used by GPRS MSs in MS operation modes A or B if the network operates in network operation
mode II or III .
- 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.
Section 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 section 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 section 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 section 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 is inserted;
- a GPRS attach procedure is successfully completed; or
- a combined GPRS attach procedure is completed for GPRS services only with cause #2, #16, #17 or #22
- a GPRS attach procedure is completed with cause #11, #12 or #13,
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.
ETSI
147 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 4.4.1; the same lists
are used by GMM and MM procedures.
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 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 SI13 or PSI1. 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 GSM 05.02).
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. 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 section 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.
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 GU1 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.
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.
ETSI
148 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 takes one of the following actions depending upon
the reject cause:
# 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 section 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 shall be considered as invalid for GPRS
services until switching off or the SIM is removed.
If the MS is IMSI attached via MM procedures, the MS shall in addition set the update status to U3
ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. The new
MM state is MM IDLE. The SIM shall be considered as invalid also for non-GPRS services until switching
off or the SIM is removed.
# 7 (GPRS services not allowed)
number. The SIM shall be considered as invalid for GPRS services until switching off or the SIM 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 (shall store it according to
section 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 shall be considered as invalid for GPRS and non-GPRS services
until switching off or the SIM is removed.
# 11 (PLMN not allowed)
# 12 (Location area not allowed); or
# 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 stored,
shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to
section 4.1.3.2), shall reset the GPRS attach attempt counter and shall change to state GMM-
DEREGISTERED.
If the MS is IMSI attached via MM procedures, 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 MS shall store the LAI or the PLMN identity in the appropriate forbidden list, i.e. in the forbidden
PLMN list for cause #11, in the list of forbidden location areas for regional provision of service for cause
#12 or in the list of forbidden location areas for roaming for cause #13. If cause #11 or #13 was received,
the MS shall perform a PLMN selection instead of a cell selection.
Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is specified in
section 4.7.3.1.5.
4.7.3.1.5 Abnormal cases in the MS
The following abnormal cases can be identified:
ETSI
149 draft ETSI EN 300 940 V7.7.0 (2000-04)
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. The MS shall proceed as described below.
c) T3310 time-out
On the first expiry of the timer, the MS 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 GPRS
attach procedure shall be aborted and the MS shall proceed as described below.
d) ATTACH REJECT, other causes than those treated in section 4.7.3.1.4
The MS shall proceed as described below.
e) Change of cell within the same RA
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 4.7.4.1).
h) Procedure collision
If the MS receives a DETACH REQUEST message from the network in state GMM-REGISTERED-
INITIATED, the GPRS detach procedure shall be progressed and the GPRS attach procedure shall be aborted. If
the cause IE, in the DETACH REQUEST message, indicated a reattach request, 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 T3311 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, 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 4.2.4.1.2).
4.7.3.1.6 Abnormal cases on the network side
ETSI
150 draft ETSI EN 300 940 V7.7.0 (2000-04)
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
considered as invalid by the network (see section 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
section 4.7.1.5). During this period the network acts as specified for case a.
d.1) ATTACH REQUEST 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 and the new GPRS attach procedure shall be progressed, or
- If no information element differ, then the ATTACH ACCEPT message shall be resent.
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 and PDP 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 section 4.7.5.
ETSI
151 draft ETSI EN 300 940 V7.7.0 (2000-04)
MS Network
ATTACH REQUEST
Start T3310
ATTACH ACCEPT
ATTACH REJECT
Stop T3310
Stop T3310
or
ATTACH COMPLETE
Stop T3350
ATTACH REQUEST
Start T3310
If P-TMSI and/or
TMSI allocated
Start T3350
If P-TMSI and/or
TMSI allocated
Figure 4.7.3/1 GSM 04.08: 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 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.
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.
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.
4.7.3.2.3 Combined GPRS attach accepted by the network
Depending on the value of the attach result IE received in the ATTACH ACCEPT message, two different cases can be
distinguished:
ETSI
152 draft ETSI EN 300 940 V7.7.0 (2000-04)
Case 1) The attach result 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.
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 section 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 section 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 U1 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.
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 attach successful for GPRS services only
The description for IMSI attach for GPRS services as specified in section 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 shall be considered as invalid for
non-GPRS services until switching off or the SIM 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 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 GU1 UPDATED:
- the MS shall keep the GMM update status GU1 UPDATED and changes state to GMM-
REGISTERED.ATTEMPTING-TO-UPDATE-MM. The MS shall start timer T3311. When timer T3311
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.
ETSI
153 draft ETSI EN 300 940 V7.7.0 (2000-04)
The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are
not successful and no new RA is entered. The new MM state is MM IDLE.
Other values 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 section 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
takes one of the following actions depending upon the reject cause:
# 3 (Illegal MS);
# 6 (Illegal ME); or
The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (shall store it according to
section 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 shall be considered as invalid for GPRS and non-GPRS services
The new GMM state is GMM-DEREGISTERED; the MM state is MM IDLE. A GPRS MS operating in MS
operation mode A shall then perform an IMSI attach for non-GPRS services by use of the MM IMSI attach
procedure; a GPRS MS operating in MS operation mode B shall then perform an IMSI attach for non-GPRS
services by use of the MM IMSI attach procedure.
# 11 (PLMN not allowed);
# 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 stored,
shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to
section 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 LAI or the PLMN identity in the appropriate forbidden list, i.e. in the forbidden
PLMN list for cause #11, in the list of forbidden location areas for regional provision of service for cause
#12 or in the list of forbidden location areas for roaming for cause #13. If cause #11 or #13 was received,
the MS shall perform a PLMN selection instead of a cell selection.
Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is specified in
section 4.7.3.2.5.
The abnormal cases specified in section 4.7.3.1.5 apply with the following modification:
If the GPRS attach attempt counter is less than 5, the MM state remains MM LOCATION UPDATING PENDING.
ETSI
154 draft ETSI EN 300 940 V7.7.0 (2000-04)
If the GPRS attach attempt counter is incremented according to section 4.7.3.1.5 the next actions depend on the
Location Area Identities (stored on SIM and the one of the current serving cell) and the value of the attach attempt
counter:
if the update status is U1 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 U1 UPDATED,
the new MM state is MM IDLE substate NORMAL SERVICE; or
if the update status is different from U1 UPDATED, or the stored LAI is different from the one of the current
serving cell, or 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 and set the update status to U2 NOT UPDATED. The
new MM state is MM IDLE substate ATTEMPTING TO UPDATE.
The abnormal cases specified in section 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; 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.
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 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.
If the GPRS detach procedure is performed, the PDP contexts are deactivated locally without peer to peer signalling
between the SM and LLC 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. If the MS is not
switched off, 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 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.
ETSI
155 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 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.
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 and deactivate the logical link(s), if any. The States GMM-DEREGISTERED and MM
NULL are entered in both the MS and the network.
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.
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 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 IMSI/GPRS detach was requested.
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
ETSI
156 draft ETSI EN 300 940 V7.7.0 (2000-04)
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
section 4.7.7 and 4.7.8 respectively.
e) Change of cell within the same RA
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
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.
MS Network
DETACH REQUEST
Start T3321
DETACH ACCEPT
Stop T3321
or at MS power switch off
DETACH REQUEST
Figure 4.7.4/1 GSM 04.08: 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 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 not required or re-
attach required, the MS shall deactivate the PDP 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 if indicated by the network in the
detach type IE.A GPRS MS operating in MS operation mode A or B in network operation mode I, which receives an
ETSI
157 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 contexts. 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, sending a ROUTING AREA UPDATE REQUEST message with Update type IE indicating
"combined RA/LA updating with IMSI attach". An 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, 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.
If the detach type IE indicates "re-attach required", the MS shall perform a new attach procedure. The MS should also
activate PDP context(s) to replace any previously active PDP contexts.
NOTE: In some cases, user interaction may be required and then the MS cannot activate the PDP context(s)
automatically.
If the detach type IE indicates "re-attach required" or "re-attach not required", then, depending on the received cause
code, the MS shall act as follows:
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.
# 6 (Illegal ME)
The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to
section 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 shall be considered as invalid for GPRS services
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. The new MM state is MM
idle. The SIM shall be considered as invalid also for non-GPRS services until switching off or the SIM is
removed.
The SIM shall be considered as invalid for GPRS services until switching off or the SIM is removed. The new
state is GMM-DEREGISTERED.
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.
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 section 4.1.3.2). Furthermore, it shall delete any P-
TMSI, P-TMSI signature, TMSI, RAI, LAI, ciphering key sequence number and GPRS ciphering key sequence
ETSI
158 draft ETSI EN 300 940 V7.7.0 (2000-04)
number and shall consider the SIM as invalid for GPRS and non-GPRS services until switching off or the SIM is
removed.
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 section
4.1.3.2).
A GPRS MS operating in MS operation mode A or B shall in addition 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 store the LAI or the PLMN identity in the appropriate forbidden list, i.e. in the forbidden PLMN
list for cause #11, in the list of forbidden location areas for regional provision of service for cause #12 or in
the list of forbidden location areas for roaming for cause #13. If #11or #13 was received, the MS shall perform
a PLMN selection instead of a cell selection.
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.
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.
d) GPRS detach and GPRS attach procedure collision
If the network receives an ATTACH REQUEST message before the network initiated GPRS detach procedure
has been completed, the network shall ignore the ATTACH REQUEST message, except when the detach type IE
value, sent in the DETACH REQUEST message, indicated that the MS shall perform a GPRS attach procedure.
In this case, the detach procedure is aborted and the GPRS attach procedure shall be progressed after the PDP
contexts have been deleted.
e) GPRS detach and routing area updating procedure collision
GPRS detach containing detach type "re-attach required" or re-attach not required ":
ETSI
159 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
MS Network
DETACH REQUEST
Start T3322
DETACH ACCEPT
Stop T3322
Figure 4.7.4/2 GSM 04.08: 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; or
- 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.
- resuming GPRS services when the RR sublayer indicated a resumption failure after dedicated mode was left, see
section 3.4.13.1.1.
Section 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 section 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 section 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;
ETSI
160 draft ETSI EN 300 940 V7.7.0 (2000-04)
- 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 section 4.4.1.
User data transmission in the MS shall be suspended during the routing area updating procedure; user data reception
shall be possible. User data transmission in the network shall be suspended during the routing area updating procedure,
if a new P-TMSI is assigned.
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 section 4.7.2.2.
The normal routing area updating procedure is initiated when the MS detects a change of the routing area in state GMM-
REGISTERED or when the MS determines that GPRS resumption shall be performed. 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). A normal routing area updating shall abort any
ongoing GMM procedure. Aborted GMM procedures shall 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 normal routing
area 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.
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 AREA
UPDATE ACCEPT message together with the routing area identification. The network shall change to state GMM-
COMMON-PROCEDURE-INITIATED and shall start the supervision timer T3350 as described in section 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.
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 GU1 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.
A ROUTING AREA UPDATE COMPLETE message shall be returned to the network if the ROUTING AREA
UPDATE ACCEPT message contained:
- a P-TMSI; and/or
- Receive N-PDU Numbers (see 04.65 [78]).
ETSI
161 draft ETSI EN 300 940 V7.7.0 (2000-04)
In this case the Receive N-PDU Numbers values valid in the MS, shall be included in the ROUTING AREA UPDATE
COMPLETE message.
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 . The MS shall then
take different actions depending on the received reject cause value:
# 6 (Illegal ME)
section 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 as invalid for GPRS
services until switching off or the SIM is removed.
If the MS is IMSI attached via MM procedures, the MS shall in addition set the update status to U3 ROAMING
NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM
IDLE. The SIM shall be considered as invalid also for non-GPRS services until switching off or the SIM is
removed.
section 4.1.3.2.9) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence
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 section 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.
automatically.
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 section 4.1.3.2)
and enter the state GMM-DEREGISTERED.
If the MS is IMSI attached via MM procedures, 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 list of forbidden location areas for roaming for cause #13. If #11or #13 was received, the MS shall perform
a PLMN selection instead of a cell selection.
ETSI
162 draft ETSI EN 300 940 V7.7.0 (2000-04)
Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in
section 4.7.5.1.5.
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. The MS shall proceed as described below.
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.
d) ROUTING AREA UPDATE REJECT, other causes than those treated in section 4.7.5.1.4
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) 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 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 GU1 UPDATED:
- the MS shall keep the GMM update status to GU1 UPDATED and changes state to GMM-
REGISTERED.NORMAL-SERVICE. The MS shall start timer T3311. When timer T3311 expires the
routing area updating procedure is triggered again.
ETSI
163 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 GU1 UPDATED:
- the MS shall start timer T3311, shall set the GPRS update status to GU2 NOT UPDATED and changes state
to GMM-REGISTERED.ATTEMPTING-TO-UPDATE.
- the MS shall start timer T3302, 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 4.2.4.1.2).
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 section 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 section 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.
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 section 4.7.1.5). During this period the network acts as described for case a above.
ETSI
164 draft ETSI EN 300 940 V7.7.0 (2000-04)
MS Network
ROUTING AREA UPDATE REQUEST
If P-TMSI or
TMSI allocated,
or Receive N-PDU
Number needed
ROUTING AREA UPDATE ACCEPT
ROUTING AREA UPDATE COMPLETE
Stop T3330
Start T3330
Stop T3350
Start T3350
or
ROUTING AREA UPDATE REJECT
Stop T3330
ROUTING AREA UPDATE REQUEST
Start T3330
If P-TMSI or
TMSI allocated,
or Receive N-PDU
Number needed
Figure 4.7.5/1 GSM 04.08: Routing and combined routing area updating procedure
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.
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 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 LA during that non-GPRS service transaction, or
- after a CM SERVICE REJECT message with cause value #4 is received by the mobile station (see section
4.5.1.1), in which case the update type IE shall be set to "Combined RA/LA updating with IMSI attach".
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.
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. 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.
ETSI
165 draft ETSI EN 300 940 V7.7.0 (2000-04)
A GPRS MS in MS operation modes A or 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 GPRS attach 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.
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 contains:
- a P-TMSI and/or a TMSI; and/or
- Receive N-PDU Numbers (see 04.65 [78]).
In the latter case, the Receive N-PDU Numbers that are valid in the MS shall be included in the ROUTING AREA
UPDATE COMPLETE message.
4.7.5.2.3.1 Combined routing area updating successful
The description for normal routing area update as specified in section 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). The
network shall, in this case, change to state GMM-COMMON-PROCEDURE-INITIATED and shall start the timer
T3350 as described in section 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 U1
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, a 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. T3211, 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.
ETSI
166 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.7.5.2.3.2 Combined routing are updating successful for GPRS services only
The description for normal routing area update as specified in section 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:
#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 RAI is equal to the RAI of the current serving cell and the GMM update
status is equal to GU1 UPDATED:
- the MS shall keep the GMM update status GU1 UPDATED and changes state to GMM-
REGISTERED.ATTEMPTING-TO-UPDATE-MM. The MS shall start timer T3311. When timer T3311
expires the combined routing area update procedure indicating combined RA/LA updating with IMSI attach
is triggered again.
- 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 as long as the combined GMM procedures are
not successful and no new RA is entered. The new MM state is IDLE.
Other values 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 section 4.7.5.2.5.
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 and enters
state MM IDLE. 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)
ROAMING NOT ALLOWED (and shall store it according to section 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 as invalid for GPRS and
non GPRS services until switching off or the SIM is removed.
The SIM shall be considered as invalid for GPRS services until switching off or the SIM is removed. The new
ETSI
167 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
# 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 section
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)
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 contexts.
automatically.
ROAMING NOT ALLOWED (and shall store it according to section 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 list of forbidden location areas for roaming for cause #13. If #11 or #13 was received, the MS shall then
perform a PLMN selection instead of a cell selection.
Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in
section 4.7.5.2.5.
The abnormal cases specified in section 4.7.5.1.5 apply with the following modification:
If the GPRS routing area updating counter is less than 5, the MM state remains MM LOCATION UPDATING
PENDING.
If the GPRS routing area updating attempt counter is incremented according to section 4.7.5.1.5 the next actions depend
on the Location Area Identities (stored on SIM and the one of the current serving cell) and the value of the routing area
updating attempt counter.
if the update status is U1 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 U1
UPDATED, the new MM state is MM IDLE substate NORMAL SERVICE, or
if the update status is different from U1 UPDATED, or the stored LAI is different from the one of the current
serving cell, or the routing area updating attempt counter is greater or equal to 5, the mobile station shall delete
ETSI
168 draft ETSI EN 300 940 V7.7.0 (2000-04)
any LAI, TMSI, ciphering key sequence number stored in the SIM and set the update status to U2 NOT
UPDATED. The new MM state is MM IDLE substate ATTEMPTING TO UPDATE.
The abnormal cases specified in section 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.
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 GSM 03.03 [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 GSM 02.09 [5] and 03.20 [34]).
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 section. 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 sections.
NOTE: Normally, the P-TMSI reallocation will take place in conjunction with another GMM procedure, e.g. at
routing area updating (see GSM 09.02 [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 shall not send any 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 the new P-TMSI as valid and the old one as invalid.
The GMM layer shall notify the LLC layer that the P-TMSI has been changed (see GSM 04.64 [76]).
ETSI
169 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 4.7.1.5).
During this period the network:
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 section 4.7.9.1.
- shall consider the new P-TMSI as valid if it is used by the MS (see section 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.
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
Start T3350
P-TMSI REALLOCATION COMPLETE
Stop T3350
Figure 4.7.6/1 GSM 04.08: P-TMSI reallocation procedure
ETSI
170 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.7.7 Authentication and ciphering procedure
The purpose of the authentication and ciphering procedure is threefold:
- to permit the network to check whether the identity provided by the MS is acceptable or not, see GSM 03.20
[13]);
- to provide parameters enabling the MS to calculate a new GPRS ciphering key; and
- to let the network set the ciphering mode (ciphering/no ciphering) and algorithm.
The authentication and ciphering procedure can be used for either:
- authentication only;
- setting of the ciphering mode and the ciphering algorithm only; or
- authentication and the setting of the ciphering mode and the ciphering algorithm.
The cases in which the authentication and ciphering procedure shall be used are defined in GSM 02.09 [5].
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:
- the network cannot decipher a ciphered AUTHENTICATION AND CIPHERING RESPONSE from an
unauthorised MS and put it on the black list; and
- to be able to define a specific point in time from which on a new GPRS ciphering key should be used instead of
the old one.
The network should not send any user data during the authentication and ciphering procedure.
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 GSM 03.20 [13]).
If authentication is requested, then the AUTHENTICATION AND CIPHERING REQUEST message shall contain the
GPRS ciphering key sequence number, allocated to the GPRS ciphering key and the RAND. If authentication is not
requested, then the AUTHENTICATION AND CIPHERING REQUEST message shall contain neither the GPRS
ciphering key sequence number nor the RAND.
If ciphering is requested, then the AUTHENTICATION AND CIPHERING REQUEST message shall indicate the
GPRS 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.
4.7.7.2 Authentication and ciphering response by the MS
An MS that is attached to GPRS shall be ready to respond upon an AUTHENTICATION AND CIPHERING
REQUEST message at any time. 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.The new GPRS ciphering key calculated
from the challenge information shall overwrite the previous one. It shall be stored and shall be loaded into the ME
ETSI
171 draft ETSI EN 300 940 V7.7.0 (2000-04)
before the AUTHENTICATION AND CIPHERING RESPONSE message is transmitted. The GPRS ciphering key
sequence number shall be stored together with the calculated key.
If the AUTHENTICATION AND CIPHERING REQUEST message does not include the authentication parameters
RAND and GPRS CKSN, then upon receipt of the message, the MS replies by sending an AUTHENTICATION AND
CIPHERING RESPONSE message to the network.
The GMM layer shall notify the LLC layer if ciphering shall be used or not and if yes which algorithm and GPRS
ciphering key that shall be used (see GSM 04.64 [76]).
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 GSM 03.20 [13]). 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.
The GMM layer shall notify the LLC sublayer if ciphering shall be used or not and if yes which algorithm and GPRS
ciphering key that shall be used (see GSM 04.64 [76]).
4.7.7.4 GPRS ciphering key sequence number
The security parameters for authentication and ciphering are tied together in sets, i.e. from a challenge parameter RAND
both the authentication response SRES and the GPRS ciphering 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 sequence number is managed by the network such that the AUTHENTICATION AND CIPHERING
REQUEST message contains the sequence number allocated to the key which may be computed from the RAND
parameter carried in that message.
The MS stores this number with the key, and includes the corresponding sequence number in the ROUTING AREA
UPDATE REQUEST and ATTACH REQUEST messages. If the sequence number is deleted, the associated key shall
be considered as invalid.
The network may choose to start ciphering with the stored key (under the restrictions given in GSM 02.09) if the stored
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 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.
The MS starts ciphering after sending the AUTHENTICATION AND CIPHERING RESPONSE message. The SGSN
starts ciphering when a valid AUTHENTICATION AND CIPHERING RESPONSE is received from the MS.
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
SGSN 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.
4.7.7.5 Unsuccessful authentication and ciphering
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
ETSI
172 draft ETSI EN 300 940 V7.7.0 (2000-04)
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, ciphering key sequence number shall be deleted and the
update status shall be set to U3 ROAMING NOT ALLOWED. The SIM shall be considered as invalid until switching
off or the SIM is removed.
If the AUTHENTICATION AND CIPHERING REJECT message is received, the MS shall abort any GMM procedure,
shall stop the timers T3310 and T3330 (if running) and shall enter state GMM-DEREGISTERED.
Upon detection of a lower layer failure before the AUTHENTICATION AND CIPHERING RESPONSE is
received, the network shall abort the procedure.
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:
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
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 section 4.7.4.
ETSI
173 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 GSM 04.08: Authentication and ciphering procedure
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 GSM 03.03). For
the presentation of the IMEI, the requirements of GSM 02.09 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.
Upon detection of a lower layer failure before the IDENTITY RESPONSE is received, the network shall abort
any ongoing GMM procedure.
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
ETSI
174 draft ETSI EN 300 940 V7.7.0 (2000-04)
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:
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
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 section 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.
MS Network
IDENTITY REQUEST
Start T3370
IDENTITY RESPONSE
Stop T3370
Figure 4.7.8/1 GSM 04.08: Identification procedure
4.7.9 Paging procedure
4.7.9.1 Paging for GPRS services
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.
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.
ETSI
175 draft ETSI EN 300 940 V7.7.0 (2000-04)
To initiate the procedure the GMM entity requests the RR sublayer to start paging (see chapter 3 and GSM 04.60 [75])
and starts timer T3313. Upon reception of a paging indication, the MS shall respond to the paging (see GSM 04.07 [20]
and GSM 03.60 [74]).
The network shall stop timer T3313 when a response is received from the MS. When the timer T3313 expires the
network may reinitiate paging.
The network shall stop timer T3313 when a response is received from the MS and shall start the READY timer. When
the timer T3313 expires the network may reinitiate paging.
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.
To initiate the procedure the GMM entity in the network requests the RR sublayer to start paging (see chapter 3 and
GSM 04.60 [75]).
Upon reception of a paging indication for GPRS services using IMSI, the MS shall locally deactivate any active PDP
contexts 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.
After performing the local detach, the MS shall then perform a GPRS attach or combined GPRS attach procedure.
After performing the attach, a MS should activate PDP context(s) to replace any previously active PDP context(s).
automatically.
NOTE: 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: 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. To initiate the procedure the GMM entity requests the RR sublayer to initiate paging (see chapter 3 and GSM
04.60 [75]) 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.10 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 GMM support for anonymous access
The GMM-AA entity within the MM sublayer (see GSM 04.07) supports SM message routing for anonymous PDP
context handling independently of the GMM procedures described throughout section 4.7 as described in section
6.1.1.1. There are no dedicated signalling procedures specified for the GMM-AA entity.
An AA-READY timer is implemented in the GMM-AA entity. This timer is used to supervise the time an anonymous
access may be active without user data transfer.
ETSI
176 draft ETSI EN 300 940 V7.7.0 (2000-04)
4.7.11.1 MS side
The AA-READY timer value shall either be the default value or a value set by the network and sent to the MS by means
of an SM message. The AA-READY timer shall be reset and restarted in the MS when the GMM-AA entity receives an
indication from lower layers that an LLC frame has been transmitted on the radio interface. When the AA-READY timer
expires or a routing area border is crossed, the MS shall deactivate the anonymous access locally, i.e. no signalling
messages are exchanged between the MS and the network.
While the AA-READY timer is running, the MS shall perform cell updates when a new cell is selected within the same
RA.
4.7.11.2 Network side
The AA-READY timer value shall either be the default value or a value received from the MS and possibly modified by
the network and sent to the MS by means of an SM message. The AA-READY timer shall be reset and restarted by the
network when the GMM-AA entity receives an indication from lower layers that an LLC frame has been successfully
received by the network. When the AA-READY timer expires, the network shall deactivate the anonymous access
locally, i.e. no signalling messages are exchanged between the network and the MS.
To account for the LLC frame uplink transmission delay, the AA-READY timer value should be slightly shorter in the
network than in the MS. This is a network implementation issue.
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.
5 Elementary procedures for circuit-switched Call
Control
5.1 Overview
5.1.1 General
This section describes the call control (CC) protocol, which is one of the protocols of the Connection Management
(CM) sublayer (see GSM 04.07).
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 section 5.2.2.2.
ETSI
177 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 this Technical Specification 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 section. 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/GSM 04.08 gives an overview of the main states and transitions on the mobile station side.
The MS side extension figure 5.1a.1/GSM 04.08 shows how for the Network Initiated MO call the MS reaches state
U1.0 from state U0 $(CCBS)$.
Figure 5.1b/GSM 04.08 gives an overview of the main states and transitions on the network side.
The Network side extension figure 5.1b.1/GSM 04.08 shows for Network Initiated MO Calls the Network reaches state
N1.0 from state N0 $(CCBS)$.
ETSI
178 draft ETSI EN 300 940 V7.7.0 (2000-04)
M
N
C
C
-
R
E
L
-
C
N
F
M
M
C
C
-
R
E
L
-
R
E
Q
U
1
9

R
E
L
E
A
S
E

R
E
Q
U
E
S
T
D
R

(
R
E
L
)

D
R

(
R
E
L
)
M
N
C
C
-
D
I
S
C
-
I
N
D
U
1
1

D
I
S
C
O
N
N
E
C
T

R
E
Q
U
E
S
T
U
1
2

D
I
S
C
O
N
N
E
C
T

I
N
D
I
C
A
T
I
O
N
M
N
C
C
-
S
E
T
U
P
-
I
N
D

U
6
C
A
L
L

P
R
E
S
E
N
T
D
R

(
C
A
L
L

C
O
N
F
)
U
9

M
T

C
A
L
L
C
O
N
F
I
R
M
E
D
D
R

(
A
L
E
R
T
)
M
N
C
C
-
S
Y
N
C
-
I
N
D

(
r
e
s
.
a
s
s
)
U
7

C
A
L
L
R
E
C
E
I
V
E
D
D
R

(
C
O
N
N
)
D
R

(
C
O
N
N
)
M
N
C
C
-
D
I
S
C
-
I
N
D
U
8

C
O
N
N
E
C
T

R
E
Q
U
E
S
T
M
N
C
C
-
S
E
T
U
P
C
O
M
P
L
.

I
N
D
D
R

(
D
I
S
C
)

S
T
A
T
E
S
U
3
,
4
,
7
,
8
,
9
,
1
0
M
M
C
C
-
E
S
T
-
R
E
Q
D
R

(
R
E
L
.

C
O
M
)
M
N
C
C
-
R
E
L
-
I
N
D
M
M
C
C
-
R
E
L
-
R
E
Q
D
R

(
S
E
T
U
P
)

U
1
C
A
L
L

I
N
IT
M
N
C
C
-
C
A
L
L
.
P
R
O
C
.
I
N
D
.
M
N
C
C
-
P
R
O
G
R
E
S
S
.

I
N
D
U
3

M
O

C
A
L
L
P
R
O
C
E
E
D
I
N
G
M
N
C
C
-
S
Y
N
C
.

I
N
D
(
r
e
s
.

a
s
s
)
M
N
C
C
-
A
L
E
R
T
-
I
N
D
U
4

C
A
L
L
D
E
L
I
V
E
R
E
D
M
N
C
C
-
S
E
T
U
P
-
C
N
F
D
R

(
C
O
N
N

A
C
K
)
M
N
C
C
-
S
E
T
U
P
-
C
N
F
D
R

(
C
O
N
N

A
C
K
)
U
1
0
A
C
T
I
V
E
M
N
C
C
-
S
E
T
U
P
.
R
E
Q
.
M
M
C
C
.

E
S
T
.

I
N
D

(
S
E
T
U
P
)
M
N
C
C
-
C
A
L
L
.
C
O
N
F
.
R
E
Q
.
M
N
C
C
-
A
L
E
R
T
.
R
E
Q
.

(
*
)
M
M
C
C
.
S
Y
N
C
.
I
N
D
.
(
r
e
s
.
a
s
s
.
)
M
N
C
C
.

S
E
T
U
P
.

R
S
P
.
M
N
C
C
.

S
E
T
U
P
.

R
S
P
D
I

(
C
O
N
N

A
C
K
)
D
I

(
D
I
S
C
)
M
N
C
C
.

R
E
L
.
R
E
Q
.
M
N
C
C
.

D
I
S
C
.
R
E
Q
.
D
I

(
D
I
S
C
)
D
I

(
R
E
L

C
O
M
)
D
I

(
C
A
L
L

P
R
O
C
)
D
I

(
P
R
O
G
R
E
S
S
)
D
I

(
C
O
N
N
)
D
I

(
A
L
E
R
T
)
D
I

(
C
O
N
N
)
M
M
C
C
.
S
Y
N
C
.
I
N
D
(
*
)
(
r
e
s
.

a
s
s
)
(
*
)

e
a
r
l
y

a
s
s
i
g
n
m
e
n
t

U
0
N
U
L
L
U
0
.
1

M
M

C
O
N
-
N
E
C
T
I
O
N

P
E
N
D
I
N
G
D
I

(
C
O
N
N
)
D
I

(
A
L
E
R
T
)
M
N
C
C
.
E
S
T
.
C
N
F
N
O
T
E
:
D
R
(
M
E
S
S
A
G
E
)

=

M
M
C
C
_
D
A
T
A
_
R
E
Q
(
M
E
S
S
A
G
E
)
D
I

(
M
E
S
S
A
G
E
)

=

M
M
C
C
_
D
A
T
A
_
I
N
D

(
M
E
S
S
A
G
E
)
D
I

(
R
E
L
)
.
Figure 5.1a/GSM 04.08:
Overview call control protocol/MS side
ETSI
179 draft ETSI EN 300 940 V7.7.0 (2000-04)
MNCC.PROMPT.IND
U0
NULL
U0.2
PROMPT PRESENT
MMCC.PROMPT.IND
U0.3
WAIT FOR NW INFO
U0.4
CC-EST. PRESENT
DR (START_CC)
DR (CC ESTABLISHMENT CONFIRMED)
MNCC.RECALL.IND
U1
CALL INITIATED
DR (SETUP)
DI (RECALL)
DI (CC ESTABLISHMENT)
MNCC.SETUP.REQ
U0.5
CC_EST. CONFIRMED
U0.6
RECALL_PRESENT
Figure5.1a.1/GSM 04.08:
Overview call control protocol/MS side, extension:
ETSI
180 draft ETSI EN 300 940 V7.7.0 (2000-04)

N
0
N
U
L
L
M
N
C
C
.
S
E
T
U
P
.
I
N
D
.
M
M
C
C
.
E
S
T
.
R
E
Q
.
(
m
o
b
i
le

I
D
)
M
N
C
C
.
R
E
L
.
C
N
F
.
M
M
C
C
.
R
E
L
.
R
E
Q
.
N
0
.
1

M
M
-
C
O
N
-
N
E
C
T
I
O
N

P
E
N
D
I
N
G
D
R

(
S
E
T
U
P
)

N
6
C
A
L
L

P
R
E
S
E
N
T
M
N
C
C
.
C
A
L
L
.
C
O
N
F
.
I
N
D

N
9

M
T

C
A
L
L

C
O
N
F
I
R
M
E
D
M
N
C
C
.
A
L
E
R
T
.
I
N
D
.
M
N
C
C
.
S
E
T
U
P
.
C
N
F
.
N
7

C
A
L
L
R
E
C
E
I
V
E
D
M
N
C
C
.
S
E
T
U
P
.
C
N
F
N
8

C
O
N
N
E
C
T
R
E
Q
U
E
S
T
D
R

(
C
O
N
N

A
C
K
)
N
1
9

R
E
L
E
A
S
E
R
E
Q
U
E
S
T
D
R

(
R
E
L

C
O
M
)
,
M
N
C
C
.
R
E
L
.
I
N
D
,
M
M
C
C
.
R
E
L
.
R
E
Q
.
D
R

(
R
E
L
)
M
N
C
C
.
D
I
S
C
.
I
N
D
N
1
2

D
I
S
C
O
N
-
N
E
C
T

I
N
D
I
C
A
T
I
O
N
D
R

(
D
I
S
C
)

N
1
C
A
L
L

I
N
I
T
N
3

M
O

C
A
L
L
P
R
O
C
E
E
D
I
N
G
D
R

(
P
R
O
G
R
E
S
S
)
D
R

(
A
L
E
R
T
)
D
R

(
C
O
N
N
)
N
4

C
A
L
L
D
E
L
I
V
E
R
E
D
D
R

(
C
O
N
N
)
N
2
8

C
O
N
N
E
C
T
I
N
D
I
C
A
T
I
O
N
M
N
C
C
.

S
E
T
U
P
.
C
O
M
P
L
.

I
N
D
.

N
1
0
A
C
T
I
V
E
D
R

(
C
A
L
L

P
R
O
C
)
M
M
C
C
.
E
S
T
.
I
N
D

(
S
E
T
U
P
)
M
N
C
C
.

S
E
T
U
P

R
E
Q
.
M
M
C
C
.

E
S
T
.

C
N
F
.
D
I

(
C
A
L
L

C
O
N
F
)
D
I

(
A
L
E
R
T
)
D
I
(
C
O
N
N
)
_
D
I

(
C
O
N
N
)
M
N
C
C
.

S
E
T
U
P
.
C
O
M
P
L
.

R
E
Q
.
D
I

(
C
O
N
N

A
C
K
)
M
N
C
C
.

S
E
T
U
P
.

R
S
P
M
N
C
C
.

D
I
S
C
.

R
E
Q
.
D
I

(
D
I
S
C
)
D
I

(
D
I
S
C
)
D
I

(
R
E
L
)
D
I

(
R
E
L

C
O
M
)
M
N
C
C
.

C
A
L
L
.

P
R
O
C
.

R
E
Q
M
N
C
C
.

P
R
O
G
R
E
S
S
.
R
E
Q
.
M
N
C
C
.

S
E
T
U
P
.

R
S
P
D
R

(
R
E
L
)
S
T
A
T
E
S

N
1
,

3
,

4
,
7
,

8
,

9
;

1
0
,

2
8
M
N
C
C

A
L
E
R
T

R
E
Q
N
O
T
E
:
D
R
(
M
E
S
S
A
G
E
)

=

M
M
C
C
_
D
A
T
A
_
R
E
Q
(
M
E
S
S
A
G
E
)
D
I

(
M
E
S
S
A
G
E
)

=

M
M
C
C
_
D
A
T
A
_
I
N
D

(
M
E
S
S
A
G
E
)
.
Figure 5.1b/GSM 04.08: Overview call control protocol/Network side
ETSI
181 draft ETSI EN 300 940 V7.7.0 (2000-04)
MNCC.CC_CONN.REQ
MMCC.CC_CONN.REQ
N0
NULL
N0.2
CC_CONN_PENDING
N0.3
NW_ANSWER_PENDING
DR (CC_ESTABLISH)
N0.4
CC-EST.PESENT
N0.5
CC_EST. CONFIRMED
DR (RECALL)
N0.6
RECALL_PRESENT
N1
CALL_INITIATED
MMCC.EST.IND (START CC)
DI (CC_EST_CONF)
DI (SETUP)
Figure 5.1b.1/GSM 04.08: 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 section.
NOTE: States U0.1, U0.2, U0.3, U0.4, U0.5, U0.6, U26, and U27 are GSM specific. All other states are ITU-T
defined.
5.1.2.1.1 Null (State U0)
No call exists.
5.1.2.1.2 MM Connection pending (U0.1)
This state exists for a mobile originating call, when the mobile station requests the establishment of a MM connection.
ETSI
182 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
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.
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 (U3)
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.
ETSI
183 draft ETSI EN 300 940 V7.7.0 (2000-04)
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
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 (U19)
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 N0.1, N0.2, N0.3, N0.4, N0.5, N0.6, N26, N27, N28, N3a, N4,a, N7a, and N9a are GSM specific.
All other states are CCITT defined.
The call states that may exist on the network side of the radio interface are defined in this section.
5.1.2.2.1 Null (State N0)
No call exists.
5.1.2.2.2 MM connection pending (N0.1)
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 (N0.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 networks action.
ETSI
184 draft ETSI EN 300 940 V7.7.0 (2000-04)
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
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.
ETSI
185 draft ETSI EN 300 940 V7.7.0 (2000-04)
5.1.2.2.13 Release request (N19)
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 GSM 04.08, section 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 U0, "null", is selected to
establish the call. It initiates the establishment by requesting the MM sublayer to establish an MM connection.
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.
For mobile stations supporting eMLPP basic calls may optionally have an associated priority level as defined in
GSM 03.67. This information may also lead to specified qualities of service to be provided by the MM sublayers.
ETSI
186 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 4.5.1.7.
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.
It 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 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 section 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 section 5.2.1.3;
ii) an ALERTING message, it shall proceed as described in section 5.2.1.5;
iii) a CONNECT message, it shall proceed as described in section 5.2.1.6;
iv) a RELEASE COMPLETE message it shall proceed as described in section 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
section 5.4 is performed.
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 section 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.
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 section 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 section 5.4.2 with one
of the following cause values:
# 8 "operator determined barring",
# 57 "bearer capability not authorized",
ETSI
187 draft ETSI EN 300 940 V7.7.0 (2000-04)
# 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 may also contain the priority of the call in the case where eMLPP is applied
and where the network has assigned a different priority to the call than that requested by the user, or where the
user has not requested a priority and the network has assigned a default priority. 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.
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 section 5.2.1.9 (early assignment).
MS Network
+-----------------------------+

(EMERGENCY) SETUP
---------------------->

+-----------------------------+
CALL_PROCEEDING (i)
< - - - - - - - - - - - -
ALERTING (ii)
< - - - - - - - - - - - -
CONNECT (iii)
< - - - - - - - - - - - -
RELEASE COMPLETE (iv)
< - - - - - - - - - - - -
Figure 5.2/GSM 04.08: 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 a 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.
ETSI
188 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 5.4.
MS Network
+---------------------------+

CALL PROCEEDING
<--------------------

+---------------------------+
Figure 5.3/GSM 04.08: Call proceeding sequence at mobile originating call establishment
5.2.1.4 Notification of progressing mobile originated call
In this section, 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.
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 users 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.
This progress indicator 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 sections 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 section 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.
ETSI
189 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 5.4.
MS Network
+---------------------+

ALERTING
<--------------

+---------------------+
Figure 5.4/GSM 04.08: 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 section 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 T310.
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 section 5.4.
ETSI
190 draft ETSI EN 300 940 V7.7.0 (2000-04)
MS Network
+-----------------------------+
CONNECT
<----------------------
CONNECT ACKNOWLEDGE
---------------------->
+-----------------------------+
Figure 5.5/GSM 04.08: 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 section 5.4 using the cause
provided by the terminating network or the called user.
5.2.1.8 Transit network selection
NOTE: For further study.
5.2.1.9 Traffic channel assignment at mobile originating call establishment
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 GSM 04.08, section 3 and GSM 08.08.
The assignment procedure does not affect any call control timer.
5.2.1.10 Call queuing at mobile originating call establishment
The conditions to apply queuing are described in GSM 03.01.
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.2 Mobile terminating call establishment
Before call establishment can be initiated in the mobile station, the MM connection must be established by the network.
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 section 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.
ETSI
191 draft ETSI EN 300 940 V7.7.0 (2000-04)
Upon receipt of a SETUP message, the mobile station shall perform compatibility checking as described in 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 section 5.2.2.3.4.
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 section 5.2.2.3.3 shall apply.
MS Network
+---------------------+

SETUP
<--------------

+---------------------+
CALL_CONFIRMED (i)
- - - - - - - - - - - - >
RELEASE COMPLETE (ii)
- - - - - - - - - - - - >
Figure 5.6/GSM 04.08: 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.
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.
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 GSM 09.07). 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 section 9.3.2.2 shall be followed.
NOTE: The possibility of alternative responses (e.g., in connection with supplementary services) is for further
study.
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 section 5.4.
ETSI
192 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
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 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:
- 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 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 section 5.4.4 using cause #102
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 section 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 GSM 02.40.
5.2.2.3.4 Called mobile station clearing during mobile terminating call establishment
See section 5.4.2.
5.2.2.4 Notification of interworking in connection with mobile terminating call
establishment
In this section, 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.
ETSI
193 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 users 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 section 5.5.1 for further reactions of the mobile station.
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 T313; and
- entering the "connect request" state.
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 section 5.4.3.
MS Network
+------------------------+
CONNECT
--------------------->
CONNECT ACKNOWLEDGE
<--------------------
+------------------------+
Figure 5.7/GSM 04.08: Call acceptance and active indication at mobile terminating call establishment
5.2.2.7 Traffic channel assignment at mobile terminating call establishment
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 section 5.2.1.10 apply accordingly.
NOTE: The interworking to the fixed network has to fulfil the network specific requirements.
ETSI
194 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.3 Network initiated MO call $(CCBS)$
The procedures of section 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
section 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 section 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 T331,
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.
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 section 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 mobiles present capabilities and configuration. The recall
alignment procedure is defined later on in this section.
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,
ETSI
195 draft ETSI EN 300 940 V7.7.0 (2000-04)
- 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.
A mobile station, for which the recall alignment procedure failed, shall respond with a RELEASE COMPLETE message
in accordance with section 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 (s) IE(s) (including Repeat Indicator(s), if there are 2 bearer
capabilities) 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.
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
RELEASE COMPLETE message with cause #102 "recovery on timer expiry" and inform all appropriate entities within
the network, proceeding in accordance with section 5.4.2.
MS Network
+---------------------------+

CC-ESTABLISHMENT
<--------------

CC-ESTABLISHMENTCONFIRMED (i)
- - - - - - - - - - - - >
RELEASE COMPLETE (ii)
- - - - - - - - - - - - >
+---------------------------+
Figure 5.7a/GSM 04.08: Call initiation and possible subsequent responses
5.2.3.2.1 Recall Alignment Procedure
The recall alignment procedure consists of two parts :
- basic service group alignment, and
- facility 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.
ETSI
196 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 coder version(s), the data rate, the radio channel requirement) provided that the basic service
group is not changed. The result shall be that the mobile station has derived Bearer Capability, HLC and LLC
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 IEs. 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 GSM 04.10 also apply.
The Facility IE is encoded as simple recall alignment, advanced recall alignment or recall alignment not essential
(see GSM 04.10). 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.
Further details on Facility handling are given in GSM 04.10
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-establishment confirmed" state.
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.
MS Network
+---------------------+

RECALL
<--------------

+---------------------+
Figure 5.7b/GSM 04.08: 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 section 5.2.1.1.
ETSI
197 draft ETSI EN 300 940 V7.7.0 (2000-04)
The MS shall ensure that the contents of the Bearer Capability IE(s) sent in the SETUP message are the same as the
Bearer Capability IE(s) in the previous CC-ESTABLISHMENT CONFIRMED message related to this Network
Initiated MO Call.
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 section 5.4.2
On receipt of the SETUP message in the recall present state, the network shall stop timer T334 and proceed as
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
--------------------->
RELEASE COMPLETE
-------------------->
+------------------------+
Figure 5.7b/GSM 04.08 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). 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).
ETSI
198 draft ETSI EN 300 940 V7.7.0 (2000-04)
5.3.3 Not used
5.3.4 Support of Dual Services
The behaviour described in this section is used to realize the following required services throughout section 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 section 8.4. If
the mobile station is already prepared to support the procedure in both directions, it shall act as described in this section.
a) Alternate Speech/Data (BS 61 according to GSM 02.02);
b) Speech followed by Data (BS 81 according to GSM 02.02);
c) Alternate Speech/Group 3 fax (Teleservice 61 according to GSM 02.03).
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 section 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; or
mode 1 "and then" 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 II 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.
ETSI
199 draft ETSI EN 300 940 V7.7.0 (2000-04)
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";
- 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 section 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 section 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.
ETSI
200 draft ETSI EN 300 940 V7.7.0 (2000-04)
The in-call modification procedures are completely symmetrical at the radio interface.
NOTE: Considering a possible future evolution, in-call modification is specified as a symmetrical procedure.
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; start timer T323; and enter the "mobile originating modify" state
(mobile station side) or the "mobile terminating modify" state (network side). Any internal resources necessary to
support the next call mode shall be reserved. 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. The MODIFY originating side shall stop sending Bm-channel information; and stop interpreting
received Bm-channel information according to the old call mode.
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 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 not the actual one and can be supported by the destination interface 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 (mobile station or 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.
In case of an alternate speech/data or alternate speech/facsimile group 3 service (refer to section 5.3.4) the old resources
may still be kept reserved, in case of speech followed by data service they may be released.
Upon receipt of the MODIFY COMPLETE message the originating side shall: initiate the alternation to those resources
necessary to support the next call mode; stop timer T323; and enter the "active" state (mobile station or network side).
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.
ETSI
201 draft ETSI EN 300 940 V7.7.0 (2000-04)
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: 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
with cause # 102 "recovery on timer expiry".
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
+-----------------------------------+
MOD
------------------------------->
------------
assignment or channel mode modify
------------
MOD COMP
<------------------------------
MOD REJ
<-- -- -- -- -- -- -- --
+-----------------------------------+
Figure 5.10a/GSM 04.08 In-call modification sequence initiated by MS
MS Network
+-----------------------------------+
MOD
<------------------------------
MOD COMP
------------------------------>
MOD REJ
-- -- -- -- -- -- -- ->
------------
assignment or channel mode modify
------------
+-----------------------------------+
Figure 5.10b/GSM 04.08 In-call modification sequence initiated by network
5.3.5 User initiated service level up- and downgrading
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.
ETSI
202 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
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
5.4 Call clearing
5.4.1 Terminology
The following terms are used in this Technical Specification in the description of clearing procedures:
- A traffic channel (see GSM 04.03) is "connected" when the channel is part of a circuit-switched connection
established according to this Technical Specification.
- 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.
ETSI
203 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 sections 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 section 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.
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 the mobile station
5.4.3.1 Initiation of call clearing
Apart from the exceptions identified in section 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;
- enter the "release request" state.
ETSI
204 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
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.
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 the network
Apart from the exception conditions identified in section 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
sections 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
section 5.4.4.1 and shall ignore section 5.4.4.2. A mobile station that supports the Prolonged Clearing Procedure shall
comply with the requirements of sections 5.4.4.2 and shall ignore section 5.4.4.1.
5.4.4.1 Clearing initiated by the network: mobile does not support Prolonged
Clearing Procedure
Section 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 section 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 the 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 section 5.4.4.1.2.1
without connecting to the in-band tone/announcement;
ETSI
205 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 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 "disconnect 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.
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;
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.
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.
ETSI
206 draft ETSI EN 300 940 V7.7.0 (2000-04)
5.4.4.2 Clearing initiated by the network: mobile supports Prolonged Clearing
Procedure
Section 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 section 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.
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,
- 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:
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 section 8.
ETSI
207 draft ETSI EN 300 940 V7.7.0 (2000-04)
- The call control entity of the MS in the "disconnect request" state, shall, upon receipt of a DISCONNECT
message:
- 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.
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:
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;
If an appropriate speech traffic channel is connected, transmission of this RELEASE message shall not cause it to
be disconnected.
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.
ETSI
208 draft ETSI EN 300 940 V7.7.0 (2000-04)
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:
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:
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:
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:
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.
ETSI
209 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 5.4.3. The behaviour of the MS call control entity receiving a DISCONNECT
message whilst in the "disconnect request" state is defined in section 5.4.4.
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 section 5; if the 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 IEs 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.
ETSI
210 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 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 section 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.
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.
5.5.4 Call re-establishment, mobile station side
This section describes the internal handling in the mobile station as far as call control is concerned.
ETSI
211 draft ETSI EN 300 940 V7.7.0 (2000-04)
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
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 4.5.1.6.
5.5.5 Call re-establishment, network side
This section 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 T310 on receipt of a CALL PROCEEDING message, see section 5.2.1.1.3.
MS Network
PROGRESS
<--------------
Figure 5.11/GSM 04.08: Progress
ETSI
212 draft ETSI EN 300 940 V7.7.0 (2000-04)
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
GSM 03.14.
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: This specification 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.
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.
5.5.7.2 Start DTMF response by the network
Upon receiving the START DTMF message the network will reconvert the received digit back into a DTMF tone which
is applied toward the remote user and returns 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.
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.
5.5.7.4 Stop DTMF response by the network
Upon receiving the STOP DTMF message the network will stop sending the DTMF tone and return a STOP DTMF
ACKNOWLEDGE message to the mobile station.
5.5.7.5 Sequencing of subsequent start DTMF requests by the mobile station
The minimum length of tone generated by the network should be according to CEPT recommendation T/CS 46-02.
The minimum gap between two subsequent tones should be according to CEPT recommendation T/CS 46-02.
There is no defined maximum length to the tone, which will normally cease when a STOP DTMF message is received
from 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 1: 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.
ETSI
213 draft ETSI EN 300 940 V7.7.0 (2000-04)
NOTE 2: The transmission time of the messages over the radio interface on FACCH/F or FACCH/H, see
GSM 05.02, ensures that the minimum length of tones and minimum gap between tones according to T/CS
46-02 are fulfilled.
START DTMF
----------------------------------->
START DTMF ACK
<-----------------------------------
STOP DTMF
----------------------------------->
STOP DTMF ACK
<-----------------------------------
Figure 5.8/GSM 04.08: Single DTMF transmission
START DTMF (x)
----------------------------------->
START DTMF ACK
<-----------------------------------
STOP DTMF
----------------------------------->
STOP DTMF ACK
<-----------------------------------
START DTMF (y)
----------------------------------->
START DTMF ACK
<----------------------------------
.
.
.
Figure 5.9/GSM 04.08: Multiple DTMF transmission
6 Support for packet services
This chapter contains the description of the procedures for the session management of GPRS point-to-point data services
at the radio interface (Reference point U
m
).
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. The SM
comprises procedures for
- identified PDP context activation, deactivation and modification; and
- anonymous PDP context activation and deactivation.
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 GSM 04.07 [20]). Ongoing SM procedures are suspended during GMM procedure execution.
For anonymous access no GMM context is established.
ETSI
214 draft ETSI EN 300 940 V7.7.0 (2000-04)
6.1.1.1 Radio resource sublayer address handling for anonymous access
In the case of anonymous access, no P-TMSI shall be used by the MS or by the network. The MS shall use a randomly
selected random TLLI for transmission of the ACTIVATE AA PDP CONTEXT REQUEST message in order to activate
the AA PDP context.
Upon receipt of the ACTIVATE AA PDP CONTEXT REQUEST message, the network assigns an auxiliary TLLI (A-
TLLI) to the AA PDP context and transmits the assigned A-TLLI to the MS. After receipt of the assigned A-TLLI, the
MS shall use it for further data transmission to the network for the lifetime of the AA PDP context.
6.1.2 Session management states
In this section, the SM states are described for one SM entity (see GSM 04.07 [20]). Each SM entity is associated with
one PDP context. Section 6.1.2.1 describes the SM states in the MS and section 6.1.2.2 describes the SM states on the
network side.
6.1.2.1 Session management states in the MS
In this section, the possible states of an SM entity in the mobile station are described. As illustrated in figure 6.1/GSM
04.08 there are four SM states in the MS.
6.1.2.1.1 PDP-INACTIVE
This state indicates that no PDP context exists.
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.
ETSI
215 draft ETSI EN 300 940 V7.7.0 (2000-04)
PDP-ACTIVE-
PENDING
PDP-ACTIVE
PDP-INACTIVE
PDP-INACTIVE-
PENDING
DR (ACTIV. PDP CONTX. REQ)
DI (ACTIV. PDP CONTX. REJ) DI (DEACTIV. PDP 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
DI (DEACTIV. PDP CONTX. REQ)
DR (DEACTIV. PDP
CONTX. ACC)
DI (DEACTIV. PDP CONTX. ACC)
DR (DEACTIV. PDP
CONTX. ACC)
DI (REQ PDP CONTX. ACTIV)
DR (MOD PDP CONTXT ACC)
DI (ACTIV. PDP CONTX. ACC)
DR (ACTIV. PDP
CONTX. REQ)
DR (DEACTIV. PDP CONTX. REQ)
DI (MOD PDP CONTXT REQ)
Figure 6.1/GSM 04.08: Session management states in the MS (overview)
6.1.2.2 Session management states on the network side
In this section, the possible states of an SM entity on the network side are described. As illustrated in figure 6.2/GSM
04.08 there are five SM states on the network side.
6.1.2.2.1 PDP-INACTIVE
This state indicates that the PDP 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.
ETSI
216 draft ETSI EN 300 940 V7.7.0 (2000-04)
DR: GMMSM-DATA-REQUEST (Message), i.e. message sent by network
DI: GMMSM-DATA-INDICATION (Message), i.e. message received by the network
PDP-INACTIVE-
PEND
DR (DEACTIV. PDP CONTX. REQ) DI (DEACTIV. PDP CONTX. ACC)
DI (DEACTIV. PDP CONTX. REQ)
DR (DEACTIV. PDP
CONTX. ACC)
DI (ACTIV. PDP CONTX. REQ)
DR (ACTIV. PDP
CONTX. ACC)
PDP ACTIVE
PDP-MODIFY-
PEND
DR (MODIFY. PDP CONTX. REQ)
DI (MODIFY. PDP CONTX. ACC)
PDP-ACTIVE-
PEND
DI (REQ PDP CONTX. ACTIV. REJ)
DR (REQ PDP CONTX. ACTIV)
PDP-INACTIVE
DI (ACTIV. PDP CONTX. REQ)
DR (ACTIV. PDP
CONTX. ACC)
DR (ACTIV. PDP CONTX. REJ)
Figure 6.2/GSM 04.08: Session management states 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 establish a PDP context between the MS and the network for a specific QoS on a
specific NSAPI. The PDP context activation may be initiated by the MS or the initiation may be requested by the
network.
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 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.
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 and
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 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 SAPI indicated by the network can not be supported by the
MS, the MS shall initiate the PDP context deactivation procedure.
ETSI
217 draft ETSI EN 300 940 V7.7.0 (2000-04)
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. 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 section or shall reject the activation request by sending a
REQUEST PDP CONTEXT ACTIVATION REJECT message as described in section 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.
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:
# 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; or
# 95 - 111: protocol errors.
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:
# 31: activation rejected, unspecified;
# 40: feature not supported; or
The network shall stop timer T3385 and enter state PDP-INACTIVE.
a) Expiry of timers
In the mobile station:
ETSI
218 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
On the network side:
On the first expiry of the timer T3385, the network shall resent 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 if a REQUEST PDP CONTEXT ACTIVATION message is received from the network after the MS has
sent an ACTIVATE PDP CONTEXT REQUEST message, and the MS has not yet received an ACTIVATE
PDP CONTEXT ACCEPT or ACTIVATE PDP CONTEXT REJECT message.
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. If 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, then the MS shall discard the
REQUEST PDP CONTEXT ACTIVATION message and shall wait for the network response to its
ACTIVATE PDP CONTEXT REQUEST message. If the MS is not 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, then the MS shall send a REQUEST PDP
CONTEXT ACTIVATION REJECT message with the cause insufficient resources to the network, and wait
for an ACTIVATE PDP CONTEXT ACCEPT 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 03.60 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.
ETSI
219 draft ETSI EN 300 940 V7.7.0 (2000-04)
MS Network
ACTIVATE PDP CONTEXT REQUEST
Start T3380
ACTIVATE PDP CONTEXT ACCEPT
ACTIVATE PDP CONTEXT REJECT
Stop T3380
Stop T3380
or
Figure 6.3/GSM 04.08: MS initiated PDP context activation procedure

MS Network
REQUEST PDP CONTEXT
Start T3385
Start T3380
ACTIVATE PDP CONTEXT ACCEPT
Stop T3380
ACTIVATE PDP CONTEXT REQUEST
Stop T3380
ACTIVATE PDP CONTEXT REJECT
Stop T3385
or
or
REQUEST PDP CONTEXT ACTIVATION REJECT
Stop T3385
Figure 6.4/GSM 04.08: Network initiated PDP context activation procedure
6.1.3.2 PDP context modification procedure
The PDP context modification procedure is invoked by the network in order to change the QoS negotiated during the
PDP context activation procedure or at previously performed PDP context modification procedures. The procedure can
be initiated by the network at any time when a PDP context is active.
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 that shall be used by the MS at
the lower layers for the transmission of data related to the PDP context.
Upon receipt of this message the MS shall reply with the MODIFY PDP CONTEXT ACCEPT message, if the MS
accepts the new QoS and the indicated LLC SAPI.
If the MS does not accept the new QoS 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 network shall upon receipt of the MODIFY PDP CONTEXT ACCEPT message stop timer T3386 and 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.
ETSI
220 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
MS Network
MODIFY PDP CONTEXT REQUEST
Start T3386
MODIFY PDP CONTEXT ACCEPT
Stop T3386
Figure 6.5/GSM 04.08: PDP context modification procedure
6.1.3.3 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.
6.1.3.3.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 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;
# 36: regular PDP context 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. Both the MS and the network shall
initiate local release of the logical link if it is not used by another PDP context.
6.1.3.3.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:
# 25: LLC or SNDCP failure;
# 36: regular PDP context 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. Both the MS
and the network shall initiate local release of the logical link if it is not used by another PDP context.
a) Expiry of timers
In the mobile station:
ETSI
221 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
MS Network
DEACTIVATE PDP CONTEXT REQUEST
Start T3390
DEACTIVATE PDP CONTEXT ACCEPT
Stop T3390
Figure 6.6/GSM 04.08: MS initiated PDP context deactivation procedure
MS Network
Start T3395
DEACTIVATE PDP CONTEXT ACCEPT
Stop T3395
DEACTIVATE PDP CONTEXT REQUEST
Figure 6.7/GSM 04.08: Network initiated PDP context deactivation procedure
6.1.3.4 AA PDP context activation
The purpose of this procedure is to anonymously establish a PDP context between the MS and the network for a specific
QoS on a specific NSAPI. The AA PDP context activation shall only be initiated by the MS.
6.1.3.4.1 Successful AA PDP context activation initiated by the mobile station
In order to activate an anonymous PDP context, the MS sends an ACTIVATE AA PDP CONTEXT REQUEST message
to the network, enters the state PDP-ACTIVE-PENDING and starts timer T3380. As long as no auxiliary TLLI is
allocated to the MS, a random TLLI is used for addressing on lower layers.
Upon receipt of an ACTIVATE AA PDP CONTEXT REQUEST message, the network selects a radio priority level
based on the QoS negotiated, assigns a AA-TID to the PDP context and sends an ACTIVATE AA PDP CONTEXT
ACCEPT message to the MS. The message shall contain a the selected radio priority level and negotiated QoS allocated
by the network. If the offered QoS parameters received from the network differ from the QoS requested by the MS, the
MS shall accept the QoS offered by the network. If the LLC SAPI indicated by the network can not be supported by the
MS, the MS shall initiate the implicit AA PDP context deactivation procedure. Upon receipt of the message ACTIVATE
ETSI
222 draft ETSI EN 300 940 V7.7.0 (2000-04)
AA PDP CONTEXT ACCEPT, the MS shall stop timer T3380, shall enter the state PDP-ACTIVE and shall initiate
establishment of the logical link for the LLC SAPI indicated by the network with the negotiated QoS.
6.1.3.4.2 Unsuccessful AA PDP context activation
Upon receipt of the ACTIVATE AA PDP CONTEXT REQUEST message the network may indicate the failure of the
MS initiated AA PDP context activation by sending the ACTIVATE AA PDP CONTEXT REJECT message to the MS.
The message contains a cause code that typically indicates one of the following causes:
# 32: service option not supported;
# 34: service option temporarily out of order;
The MS shall stop the timer T3380.
a) Expiry of timers
On the first expiry of timer T3380, the MS shall retransmit the ACTIVATE AA PDP CONTEXT REQUEST
message 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 indicate the
failure of the AA PDP context activation procedure to the register functions, shall release all resources possibly
allocated for this invocation and shall abort the procedure; no automatic AA PDP context activation re-attempt
shall be performed.
MS Network
ACTIVATE AA PDP CONTEXT REQUEST
Start T3380
ACTIVATE AA PDP CONTEXT ACCEPT
ACTIVATE AA PDP CONTEXT REJECT
Stop T3380
Stop T3380
or
Figure 6.8 GSM 04.08: MS initiated AA PDP context activation procedure
6.1.3.5 AA PDP context deactivation
6.1.3.5.1 Implicit AA PDP context deactivation
The implicit deactivation is performed without signalling message exchange as specified below.
The AA PDP context on the network side shall be deactivated when:
- the AA READY timer expires in the GMM-AA entity.
The AA PDP context in the MS shall be deactivated when:
- the AA READY timer expires in the GMM-AA entity;
- the MS changes the routing area;
ETSI
223 draft ETSI EN 300 940 V7.7.0 (2000-04)
- the LLC SAPI indicated by the network can not be supported by the MS during activation, or
- user requested.
6.1.3.5.2 Explicit AA PDP context deactivation
An explicit AA PDP context deactivation shall only be initiated by the network. The procedure shall be performed when
a misuse of the anonymous PDP context has been detected.
In order to deactivate the AA PDP context, the network sends the message DEACTIVATE AA PDP CONTEXT
REQUEST and starts timer T3397. The message shall contain the transaction identifier in use for the AA PDP context to
be deactivated. After sending the message the network initiates the release of the logical link.
The MS shall, upon receipt of this message, reply with the DEACTIVATE AA PDP CONTEXT ACCEPT message
after the logical link has been released.
Upon receipt of the DEACTIVATE AA PDP CONTEXT ACCEPT message, the network shall stop the timer T3397.
a) Expiry of timers
On the first expiry of timer T3397, the network shall retransmit the message DEACTIVATE AA PDP
CONTEXT REQUEST and shall reset and restart timer T3397.
This retransmission is repeated four times, i.e. on the fifth expiry of timer T3397, the network shall release all
remaining resources allocated for that MS and shall erase the AA PDP context related data for that MS.
MS Network
DEACTIVATE AA PDP CONTEXT REQUEST
Start T3397
DEACTIVATE AA PDP CONTEXT ACCEPT
Stop T3397
Figure 6.9/GSM 04.08: Network initiated AA PDP context deactivation procedure
b) Lower layer failure
If a lower layer failure is indicated before the DEACTIVATE AA PDP CONTEXT ACCEPT message is sent,
the MS shall abort the procedure and shall locally de-allocate the P-TMSI from the LLC sublayer.
If a lower layer failure is indicated before the DEACTIVATE AA PDP CONTEXT ACCEPT message is received,
the network shall abort the procedure and shall locally de-allocate the P-TMSI from the LLC sublayer.
6.1.3.6 Receiving a SM STATUS message by a SM entity
If the SM entity of the MS receives a SM 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 SM STATUS message in the network are an implementation dependent option.
7 Examples of structured procedures
Section 7 is informative.
ETSI
224 draft ETSI EN 300 940 V7.7.0 (2000-04)
7.1 General
Section 7 contains examples of how the network may group together the elementary procedures (i.e. the procedures
defined in sections 3 to 5) in order to provide normal service.
The layer 3 signalling at the radio interface may be divided into so-called structured procedures which consist of specific
combinations of elementary procedures. In section 7.3, selected examples of structured procedures are described. A
structured procedure consists of (not necessarily all) components shown in figure 7.1. These components are
characterized by the purpose of their use in structured procedures and their message flow in the following sections 7.1.1
to 7.1.7.
+- -+
Paging request RR connection
Immediate assignment establishment
+- -+
+- -+
Service request and
Contention resolution
+- -+
+- -+
Authentication
+- -+
+- -+
Ciphering mode setting
+- -+
+- -+
Transaction phase
+- -+
+- -+
Channel release RR connection
+- -+ release
Figure 7.1/GSM 04.08: Components of structured procedures
7.1.1 Paging request
The paging procedure is used to locate a mobile station to which a connection shall be established.
Upon receipt of a PAGING REQUEST message the addressed mobile station initiates the immediate assignment
procedure.
PAGING REQUEST
<-------------------
Figure 7.2/GSM 04.08: Paging request
7.1.2 Immediate assignment
The immediate assignment procedure is always initiated by the mobile station. It may be triggered by a paging request or
by a mobile originating service request.
The mobile station sends a CHANNEL REQUEST message on the Random Access Channel. The network responds
with an IMMEDIATE ASSIGNMENT message which causes the mobile station to seize the indicated dedicated
channel.
CHANNEL REQUEST
------------------------->
<------------------------
Figure 7.3/GSM 04.08: Immediate assignment
ETSI
225 draft ETSI EN 300 940 V7.7.0 (2000-04)
7.1.3 Service request and contention resolution
The initial service request message (a PAGING RESPONSE, LOCATION UPDATING REQUEST, IMSI DETACH,
CM SERVICE REQUEST, or CM RE-ESTABLISHMENT REQUEST message) is sent by the mobile station to the
network piggy-backed in the L2 SABM frames establishing the main signalling link. Its purpose is
- to provide non-confidential information relevant to the service requested for the RR and MM sublayer in the
network;
- in particular to identify the user in the network without jeopardising the confidentiality of the users identity; this
is achieved by using as mobile identity the TMSI, which was never before transmitted un-encrypted over the
radio interface;
- to allow for contention resolution.
- optionally, in the CM SERVICE REQUEST message to inform the network of the priority level associated with
the call.
Contention resolution provides a resolution process when more than one MS try to seize a channel allocated during the
immediate assignment procedure (because they happened to use the same random reference at the same time during
random access). This is achieved by the network including in a L2 UA frame the same information field as that one
received in the L2 SABM frame to which the UA frame responds. By comparing the two information fields the MS can
verify whether it was the originator of the L2 establishment, because the service request contains the mobile identity.
SABM(service request)
------------------------->
UA(service request)
<------------------------
Figure 7.4/GSM 04.08: Service request and contention resolution
7.1.4 Authentication
The purpose of authentication is to validate the identity provided by the mobile station . It is initiated by the network.
The authentication procedure also provides the mobile station with information from which a new ciphering key can be
derived. The network decides whether or not to use authentication. This may depend on the context.
AUTHentication REQuest
<--------------------------
AUTHentication RESponse
--------------------------->
Figure 7.5/GSM 04.08 Authentication
7.1.5 Ciphering mode setting
Ciphering mode setting is initiated by the network. Its purpose is to instruct the mobile station whether or not to use
ciphering and which algorithm to use.
Where ciphering is used, this procedure synchronizes the start of ciphering at the mobile station and in the network.
CIPHer MODE CoMmanD
<----------------------
CIPHer MODe COMplete
----------------------->
Figure 7.6/GSM 04.08: Ciphering mode setting
ETSI
226 draft ETSI EN 300 940 V7.7.0 (2000-04)
7.1.6 Transaction phase
A variety of elementary procedures described in sections 3 to 5 may be performed during the transaction phase. In this
section, only the channel mode modify procedure is characterized.
7.1.6.1 Channel mode modify
The channel mode modify procedure may be used when a traffic channel has been assigned e.g.:
- during the in-call modification procedure in order that the channel mode of the TCH be changed to that one
requested by call control;
- during call establishment with very early assignment in order that the channel mode of the TCH be changed from
signalling only to the mode requested by call control;
- during the active phase of a data call in order that the speed of the data transmission be changed.
The channel mode modify procedure is initiated by the network sending a CHANNEL MODE MODIFY message and
completed by the mobile station changing the mode of the TCH and sending back a CHANNEL MODE MODIFY
ACKNOWLEDGE message.
CHANNEL MODE MODIFY
<-----------------------------------
CHANNEL MODE MODIFY ACKNOWLEDGE
------------------------------------>
Figure 7.7/GSM 04.08: Channel mode change
7.1.7 Channel release
Once the transaction phase has been completed, the channel is released by the channel release procedure. The data link
layer is released explicitly as described in GSM 04.06. After the channel release is completed, the radio resources which
were in use may be reallocated by the network.
CHANNEL RELEASE
<----------------------
Figure 7.8/GSM 04.08: Channel release
7.2 Abnormal cases
Abnormal cases are not described in the examples of section 7. They may arise from:
a) failure at a lower layer (e.g. loss of radio connection);
b) failure of an elementary procedure;
c) errors in an elementary procedure.
7.3 Selected examples
The following examples are considered:
- location updating
- mobile originating call establishment
ETSI
227 draft ETSI EN 300 940 V7.7.0 (2000-04)
a) without OACSU (early assignment)
b) with OACSU
c) with very early assignment
- mobile terminating call establishment
a) without OACSU (early assignment)
b) with OACSU
- call clearing:
a) network initiated
b) mobile initiated
- DTMF protocol control.
- handover:
a) between finely synchronized cells
b) between non-synchronized cells
c) handover failure, where reconnection of the old channel is possible
- in-call modification
- call re-establishment
- network initiated MO call, e.g. CCBS Recall $(CCBS)$:
a) assignment before A party alerting
b) assignment before B party alerting
c) assignment after A and B party alerting
7.3.1 Location updating
The location updating procedure is always initiated by the mobile station e.g. when it finds itself in a different location
area from the one in which it was registered before. The cases where the procedure is triggered are described in
section 4.
The procedure is shown in figure 7.9/GSM 04.08. The network may decide whether to allocate a new TMSI during
location updating, and this option is reflected in this example.
The mobile station initiates immediate assignment, service request using the LOCATION UPDATING REQUEST
message, and contention resolution.
The network requires authentication (this again is an option).
As the network intends to allocate a new TMSI, it should activate ciphering. The network includes the new TMSI in the
LOCATION UPDATING ACCEPT message (it could also use the explicit TMSI reallocation procedure, see section 4).
The mobile station sends a TMSI REALLOCATION COMPLETE message to the network to acknowledge the receipt
of the new TMSI. Upon receipt of the TMSI REALLOCATION COMPLETE message the network initiates the channel
release if no further transactions are scheduled.
ETSI
228 draft ETSI EN 300 940 V7.7.0 (2000-04)
+- -+
CHANNEL REQUEST RR connection
---------------------------------------> establishment
(MO)

<--------------------------------------
+- -+
+- -+

LOCATION UPDATING REQUEST
----------------------------------------> Service request

+- -+
+- -+
AUTHENTICATION REQUEST
<--------------------------------------- Authentication

AUTHENTICATION RESPONSE
---------------------------------------->
+- -+
+- -+

CIPHER MODE COMMAND
<--------------------------------------- Ciphering mode
setting
CIPHER MODE COMPLETE
----------------------------------------->
+- -+
+- -+
LOCATION UPDATING ACCEPT
<---------------------------------------

TMSI REALLOCATION COMPLETE
--------------------------------------->
+- -+
+- -+
CHANNEL RELEASE RR connection
<--------------------------------------- release

+- -+
Figure 7.9/GSM 04.08 Location updating: successful case
7.3.2 Mobile originating call establishment
The mobile station initiates immediate assignment, service request using the CM SERVICE REQUEST message, and
contention resolution. The network may initiate authentication and may start the ciphering mode setting.
After sending the CIPHERING MODE COMPLETE message, the mobile station initiates call establishment by sending
the SETUP message to the network. The network answers with a CALL PROCEEDING message.
a) Non-OACSU option (early assignment)
With this option the network allocates a traffic channel to the mobile station before it initiates call establishment
in the fixed network.
If call queuing is applied, it may cause variable delay in the traffic channel assignment.
When user alerting has been initiated at the called side, an ALERTING message is sent to the mobile station. The
network may optionally instruct the MS to attach the user connection at this stage of the call, by means of the
progress indicator information element set to the value #1 or #8(if the ringing tone will be sent by the remote
end) in the ALERTING message. In that case, an alerting ringing tone has to be generated by the network.
NOTE: The speech codec is transparent for supervisory tones.
ETSI
229 draft ETSI EN 300 940 V7.7.0 (2000-04)
A CONNECT message and its acknowledgement CONNECT ACKNOWLEDGE complete the call establishment
when the called party has answered.
The mobile originating call setup with early assignment is shown in figure 7.10a/GSM 04.08.
b) OACSU option (late assignment)
The network determines when the traffic channel is to be assigned. The assignment may be performed at any time
after call establishment has been initiated in the fixed network. In the following the case is considered where the
network will only allocate a traffic channel after the called party has answered the call (late assignment).
As in a) an ALERTING message is sent to the mobile station when user alerting has been initiated at the called
side. If the ringing tone is needed, it has to be generated locally at the mobile station as no traffic channel is
allocated. When the called party has answered, the network will initiate the channel assignment procedure in
order to allocate a traffic channel to the mobile station. If call queuing is applied, it may cause variable delay in
the traffic channel assignment. Once the channel assignment has been completed the network will send a
CONNECT message to the mobile station. The MS attaches then the user connection. The CONNECT
ACKNOWLEDGE message will complete the call setup.
The mobile originating call setup with late assignment is shown in figure 7.10b/GSM 04.08.
c) Very early assignment
The network assigns the traffic channel at the earliest possible moment, i.e. in the immediate assignment
procedure. The mode of the traffic channel is changed from signalling only to the mode necessary for the call by
means of the channel mode change procedure. An appropriate moment for that change is after the network has
sent the CALL PROCEEDING message, when the call is established towards the called user.
With this option, call queuing is never applied.
The further establishment of the call is as in a).
The mobile originating call setup with very early assignment is shown in figure 7.10c/GSM 04.08.
ETSI
230 draft ETSI EN 300 940 V7.7.0 (2000-04)

+- -+
-------------------------> establishment
IMMEDIATE ASSIGNMENT (MO)
<------------------------
+- -+
+- -+
CM SERVICE REQUEST
-------------------------> Service request

+- -+
+- -+
AUTHENTICATION REQUEST Authentication
<-------------------------
-------------------------->
+- -+
+- -+
CIPHER MODE COMMAND
<------------------------- Ciphering
CIPHER MODE COMPLETE mode setting
-------------------------->
+- -+
+- -+
SETUP
--------------------------> Call initiation
CALL PROCEEDING
<-------------------------
+- -+
+- -+
ASSIGNMENT COMMAND
<-------------------------- Assignment of
ASSIGNMENT COMPLETE a traffic
--------------------------> channel
+- -+
+- -+
ALERTING
<-------------------------- User alerting
+- -+
+- -+
CONNECT
<-------------------------- Call accepted
CONNECT ACKNOWLEDGE
-------------------------->
+- -+
Figure 7.10a/GSM 04.08: Mobile originating call establishment without OACSU (early assignment)
ETSI
231 draft ETSI EN 300 940 V7.7.0 (2000-04)
+- -+
-------------------------> establishment
<------------------------
+- -+
+- -+ Service indication
CM SERVICE REQUEST
------------------------->

+- -+
+- -+
<-------------------------
-------------------------->
+- -+
+- -+
CIPHER MODE COMMAND
<------------------------- Ciphering
-------------------------->
+- -+
+- -+
SETUP
--------------------------> Call initiation
CALL PROCEEDING
<-------------------------
+- -+
+- -+
ALERTING
<-------------------------- User alerting
+- -+
+- -+
ASSIGNMENT COMMAND
<------------------------- Assignment of
--------------------------> channel
+- -+
+- -+
CONNECT
<-------------------------- Call accepted
CONNECT ACKNOWLEDGE
-------------------------->
+- -+
Figure 7.10b/GSM 04.08: Mobile originating call establishment with OACSU (late assignment)
ETSI
232 draft ETSI EN 300 940 V7.7.0 (2000-04)

+- -+
--------------------------> establishment
IMMEDIATE ASSIGNMENT(TCH) (MO)
<-------------------------
+- -+
+- -+
CM SERVICE REQUEST
--------------------------> Service request

+- -+
+- -+
AUTHentication REQuest Authentication
<--------------------------
--------------------------->
+- -+
+- -+
CIPHER MODE COMMAND
<-------------------------- Ciphering
CIPHer MODe COMplete mode setting
--------------------------->
+- -+
+- -+
SETUP
--------------------------> Call initiation
CALL PROCeeding
<--------------------------
+- -+
+- -+
CHANNEL MODE MODIFY
<--------------------------- Transmission
CHANNEL MODE MODIFY ACKNOWLEDGE mode
---------------------------> change
+- -+
+- -+
ALERTING
<---------------------------- User alerting
+- -+
+- -+
CONNect
<--------------------------- Call accepted
CONNect ACKnowledge
--------------------------->
+- -+
Figure 7.10c/GSM 04.08: Mobile originating call establishment with very early assignment
7.3.3 Mobile terminating call establishment
Mobile terminating call establishment is initiated by the network sending a PAGING REQUEST message (see figure
7.11a/GSM 04.08). Upon receiving this message the mobile station initiates the immediate assignment procedure and
responds to the network by sending the PAGING RESPONSE message within a layer 2 SABM frame. The network
returns a layer 2 UA frame containing the same information field as was sent in the SABM frame.
Authentication and ciphering are treated by the network in the same way as defined for the mobile originating call
establishment (section 7.3.2). After ciphering has been started, the network sends a SETUP message to the mobile
station. The capability of the mobile station (at that time) to accept the call is confirmed when the mobile station returns
a CALL CONFIRMED message to the network.
a) Non-OACSU option (early assignment)
With this option the network initiates the assignment of a traffic channel upon receiving the CALL
CONFIRMED message.
The signal IE is not included in the SETUP message, therefore user alerting is initiated only after a traffic
channel has been allocated. An ALERTING message will be sent to the network.
ETSI
233 draft ETSI EN 300 940 V7.7.0 (2000-04)
When the called user answers, the mobile station sends a CONNECT message to the network. Upon receiving the
CONNECT message the network completes the through connection of the communication path and sends a
CONNECT ACK message to the mobile station.
b) OACSU option (late assignment)
In that option, the signalling IE is included in the SETUP message. Consequently, user alerting is initiated as
soon as the MS has accepted the call.
The network determines when the traffic channel is to be assigned. The assignment may be performed at any time
after user alerting has been initiated. In the following the case is considered where the network will only allocate
a traffic channel to the mobile station after having received the CONNECT message sent from the mobile station
(see figure 7.11b).
Upon receiving the ASSIGNMENT COMPLETE message from the mobile station, the network completes the
through connection of the communication path and sends a CONNECT ACKNOWLEDGE message to the
mobile station.
+- -+
PAGING REQUEST
<-------------------------
-------------------------> establishment
IMMEDIATE ASSIGNMENT (MT)
<------------------------
+- -+
+- -+
PAGING RESPONSE
-------------------------> Service request
+- -+
+- -+
<-------------------------
-------------------------->
+- -+
+- -+
CIPHer MODe COMMAND
<------------------------- Ciphering
-------------------------->
+- -+
+- -+
SETUP
<-------------------------- Call initiation
CALL CONFIRMED
-------------------------->
+- -+
+- -+
ASSIGNMENT COMMAND
<-------------------------- Assignment of
--------------------------> channel
+- -+
+- -+
ALERTING
-------------------------> User alerting
+- -+ information
+- -+
CONNECT
--------------------------> Call accepted
CONNECT ACKNOWLEDGE
<--------------------------
+- -+
Figure 7.11a/GSM 04.08: Mobile terminating: call establishment without OACSU (early assignment)
ETSI
234 draft ETSI EN 300 940 V7.7.0 (2000-04)
+- -+
PAGING REQUEST
<-------------------------
-------------------------> establishment
<------------------------
+- -+
+- -+
PAGING RESPONSE
-------------------------> Service request
+- -+
+- -+
<-------------------------
-------------------------->
+- -+
+- -+
CIPHer MODe COMMAND
<------------------------- Ciphering
-------------------------->
+- -+
+- -+
SETUP
<-------------------------- Call initiation
CALL CONFIRMED
-------------------------->
+- -+
+- -+
ALERTING
-------------------------> User alerting
+- -+ information
+- -+
CONNECT
------------------------->
+- -+
+- -+
ASSIGNMENT COMMAND
<-------------------------- Assignment of
--------------------------> channel
+- -+
+- -+
CONNECT ACKNOWLEDGE
<--------------------------
+- -+
Figure 7.11b/GSM 04.08: Mobile terminating: call establishment with OACSU (late assignment)
7.3.4 Call clearing
a) initiated by the network
The network initiates the clearing of a call by sending a DISCONNECT message to the mobile station (see also
section 5.4.4).
Upon receiving the DISCONNECT message from the network the mobile station sends a RELEASE message to
the network.
Upon receiving the RELEASE message from the mobile station, the network sends a RELEASE COMPLETE to
the mobile station and, if the traffic channel is longer needed (e.g. last activity on the traffic channel), performs
the channel release procedure as described in section 7.1.7.
Upon receiving the RELEASE COMPLETE message and if the cleared call was the last activity on the traffic
channel, the mobile station waits for the release of the channel which is always initiated by the network.
Call clearing initiated by the network is shown in figure 7.12a.
ETSI
235 draft ETSI EN 300 940 V7.7.0 (2000-04)
b) initiated by the mobile station
The mobile station initiates the clearing of a call by sending a DISCONNECT message to the network (see also
section 5.4.3).
Upon receiving the DISCONNECT message from the mobile station the network sends a RELEASE message to
the mobile station.
Upon receiving the RELEASE message from the network, the mobile station sends a RELEASE COMPLETE to
the network, which, if the traffic channel is no longer needed (e.g. last activity on the traffic channel), performs
the channel release procedure as described in section 7.1.6.
Call clearing initiated by the mobile station is shown in figure 7.12b.
+- -+
DISCONNECT
<------------------------ Call clearing
RELEASE
----------------------->
RELEASE COMPLETE
<-----------------------
+- -+
+- -+
<------------------------ release
+- -+
a) Call clearing initiated by the network
Figure 7.12a/GSM 04.08: Call clearing
a)
+- -+
DISCONNECT
------------------------> Call clearing
RELEASE
<------------------------
RELEASE COMPLETE
----------------------->
+- -+
+- -+
<------------------------ release
+- -+
b) Call clearing initiated by the MS
Figure 7.12b/GSM 04.08: Call clearing
7.3.5 DTMF protocol control
Figure 7.13 shows the structured procedure for DTMF protocol control.
ETSI
236 draft ETSI EN 300 940 V7.7.0 (2000-04)
+- -+
active call

+- -+
.
+- -+
START DTMF DTMF generation
------------------------------> started
START DTMF ACKNOWLEDGE
<-----------------------------
+- -+
+- -+
STOP DTMF DTMF generation stopped
------------------------------->
STOP DTMF ACKNOWLEDGE
<-------------------------------
+- : -+
:
+- -+
active call

+- -+
Figure 7.13/GSM 04.08: DTMF protocol control
7.3.6 Handover
Figure 7.14 shows the structured procedure for handover to a finely synchronized cell, successful case.
Figure 7.15 shows the structured procedure for handover to a non-synchronized cell, successful case.
Figure 7.16 shows the structured procedure for handover failure, and reconnection to the old traffic channel.
+- -+

RR connection established

+- -+
+- -+ handover
HANDOVER COMMAND old channel,
<------------------------ old cell
- - - - - - - - - - - - - - - -- - - - - - - - - -
HANDOVER ACCESS new channel,
------------------------> new cell

HANDOVER ACCESS
------------------------>

HANDOVER ACCESS
------------------------>

HANDOVER ACCESS
------------------------>

HANDOVER COMPLETE
------------------------>
+- -+
Figure 7.14/GSM 04.08: Handover to a finely synchronized cell, successful case
ETSI
237 draft ETSI EN 300 940 V7.7.0 (2000-04)
+- -+


+- -+
+- -+ handover
<------------------------ old cell
- - - - - - - - - - - - - - - -- - - - - - - - - -
------------------------> new cell
.
.
.
------------------------> new cell

PHYSICAL INFORMATION
<-----------------------
HANDOVER COMPLETE
------------------------>
+- -+
+- -+
.
.
.
+- -+
Figure 7.15/GSM 04.08: Handover to a non-synchronized cell, successful case
+- -+


+- -+
+- -+ handover
<------------------------ old cell
- - - - - - - - - - - - - - - - - - - - - - -
T3124 expiry or new channel,
lower layer failure new cell
- - - - - - - - - - - - - - - - - - - - - - - -
HANDOVER FAILURE old channel,
------------------------> old cell
+- -+
+- -+
.
.
.
+- -+
Figure 7.16/GSM 04.08: Handover failure, reconnection to the old traffic channel
7.3.7 In-call modification
Figure 7.17/GSM 04.08 shows the structured procedure for in-call modification.
ETSI
238 draft ETSI EN 300 940 V7.7.0 (2000-04)
+- -+
active call

+- -+
.
+- -+
MODIFY
------------------------------> in-call modification
e.g. from speech
to data
+- -+ channel
mode modify

+- -+

MODIFY COMPLETE
<-----------------------------
+- -+
+- -+
active call

+- -+
Figure 7.17/GSM 04.08: In-call modification
7.3.8 Call re-establishment
Figure 7.18/GSM 04.08 shows the structured procedure for call re-establishment.
+- -+
active call

+- -+
-------------------------------------- radio link failure
+- -+
-------------------------> establishment
<------------------------
+- -+
+- -+
CM RE-ESTABLISHMENT REQUEST
-------------------------> Service request
+- -+
+- -+
CIPHer MODe COMMAND
<------------------------- Ciphering
------------------------->
+- -+
+- -+
ASSIGNMENT COMMAND
<------------------------- assignment of
ASSIGNMENT COMPLETE a traffic channel
------------------------->
+- -+
+- -+
active call

+- -+
Figure 7.18/GSM 04.08: Call re-establishment
ETSI
239 draft ETSI EN 300 940 V7.7.0 (2000-04)
7.3.9 Network initiated mobile originating call $(CCBS)$
Network initiated mobile originating call establishment (which is used, for example, for CCBS Service) is initiated by
the network sending a PAGING REQUEST message. Upon receiving this message the mobile station initiates the
immediate assignment procedure and responds to the network by sending the PAGING RESPONSE message within a
layer 2 SABM frame. The network returns a layer 2 UA frame containing the same information field as was sent in the
SABM frame.
Authentication and ciphering are treated by the network in the same way as defined for the mobile originating call
establishment (section 7.3.2). After ciphering has been started, the network sends a CM SERVICE PROMPT message,
indicating that the CM protocol is to be started, to the mobile station. The basic capability of the mobile station to accept
any form of recall service is confirmed when the mobile station returns a START CC message to the network.
a) assignment before A party alerting
With this option the network allocates a traffic channel to the mobile station before the mobile station alerts its
user.
The network responds to the START CC message with a CC-ESTABLISHMENT message. The MS answers
with a CC-ESTABLISHMENT CONFIRMED message indicating the wanted channel characteristics. The
network then initiates traffic channel assignment.
When the traffic channel has been assigned, the network indicates a pending recall by sending a RECALL
message.
If the calling user accepts the recall, a SETUP message is sent to the network. The network responds with a
CALL PROCEEDING message and initiates call establishment in the fixed network.
The network initiated mobile originating call establishment with assignment before A part alerting is shown in
figure 7.19/GSM 04.08.
b) assignment before B party alerting
With this option the network allocates a traffic channel to the mobile station after the mobile station has alerted
its user and after its user has accepted the recall but before the network initiates call establishment in the fixed
network.
The network responds to the START CC message with a CC-ESTABLISHMENT message. The MS answers
with a CC-ESTABLISHMENT CONFIRMED message indicating the wanted channel characteristics.
The network indicates a pending recall by sending a RECALL message. If the calling user accepts the recall, a
SETUP message is sent to the network. The network responds with a CALL PROCEEDING message and
initiates traffic channel assignment.
When the traffic channel has been assigned, the network initiates call establishment in the fixed network.
ETSI
240 draft ETSI EN 300 940 V7.7.0 (2000-04)
The network initiated mobile originating call establishment with assignment before B party alerting is shown in
figure 7.20/GSM 04.08.
c) assignment after A and B party alerting
With this option, the network determines when the traffic channel is to be assigned. The assignment may be
performed at any time after call establishment has been initiated in the fixed network. In the following, the case is
considered where the network will only allocate a traffic channel after the called party has answered the call (late
assignment).
The network responds to the START CC message with a CC-ESTABLISHMENT. The MS answers with a CC-
ESTABLISHMENT CONFIRMED message indicating the wanted channel characteristics.
The network indicates a pending recall by sending a RECALL message. If the calling user accepts the recall, a
SETUP message is sent to the network. The network responds with a CALL PROCEEDING message and
initiates call establishment in the fixed network.
As in a) and b) an ALERTING message is sent to the mobile station when user alerting has been initiated at the
called side. If the ringing tone is needed, it has to be generated locally at the mobile station as no traffic channel
is allocated. When the called party has answered, the network will initiate the channel assignment procedure in
order to allocate a traffic channel to the mobile station. Once the channel assignment has been completed the
network will send a CONNECT message to the mobile station. The MS attaches then the user connection. The
CONNECT ACKNOWLEDGE message will complete the call setup.
The network initiated mobile originating call establishment with assignment after A and B party alerting is shown
in figure 7.21/GSM 04.08.
ETSI
241 draft ETSI EN 300 940 V7.7.0 (2000-04)
+- -+
PAGING REQUEST
<-------------------------
-------------------------> establishment
<-------------------------
+- -+
+- -+
PAGING RESPONSE
------------------------->
+- -+
+- -+
<-------------------------
------------------------->
+- -+
+- -+
CIPHer MODe COMMAND
<------------------------- Ciphering
------------------------->
+- -+
+- -+
CM SERVICE PROMPT
<------------------------- Service Request
START CC
------------------------->
+- -+
+- -+
CC-ESTABLISHMENT
<------------------------- Recall initiation
CC-ESTABLISHMENT CONFIRMED
------------------------->
+- -+
+- -+
ASSIGNMENT COMMAND
<------------------------- Assignment of
ASSIGNMENT COMPLETE a traffic channel.
------------------------->
+- -+
+- -+
RECALL
<------------------------- User notified about recall
SETUP
-------------------------> Recall accepted and
CALL PROCEEDING call initiation
<-------------------------
+- -+
+- -+
ALERTING
<------------------------- Called user alerting
+- -+ information
+- -+
CONNECT
<------------------------- Call accepted
CONNECT ACKNOWLEDGE
------------------------->
+- -+
Figure 7.19/GSM 04.08: Network initiated mobile originating call establishment with assignment
before A party alerting
ETSI
242 draft ETSI EN 300 940 V7.7.0 (2000-04)
+- -+
PAGING REQUEST
<-------------------------
-------------------------> establishment
<-------------------------
+- -+
+- -+
PAGING RESPONSE
------------------------->
+- -+
+- -+
<-------------------------
------------------------->
+- -+
+- -+
CIPHer MODe COMMAND
<------------------------- Ciphering
------------------------->
+- -+
+- -+
CM SERVICE PROMPT
<------------------------- Service Request
START CC
------------------------->
+- -+
+- -+
CC-ESTABLISHMENT
------------------------->
+- -+
+- -+
RECALL
SETUP
<-------------------------
+- -+
+- -+
ASSIGNMENT COMMAND
<------------------------- Assignment of
-------------------------> channel
+- -+
+- -+
ALERTING
+- -+ information
+- -+
CONNECT
<------------------------- Call accepted
CONNECT ACKNOWLEDGE
------------------------->
+- -+
Figure 7.20/GSM 04.08: Network initiated mobile originating call establishment with assignment
before B party alerting
ETSI
243 draft ETSI EN 300 940 V7.7.0 (2000-04)
+- -+
PAGING REQUEST
<-------------------------
-------------------------> establishment
<-------------------------
+- -+
+- -+
PAGING RESPONSE
------------------------->
+- -+
+- -+
<-------------------------
------------------------->
+- -+
+- -+
CIPHer MODe COMMAND
<------------------------- Ciphering
------------------------->
+- -+
+- -+
CM SERVICE PROMPT
<------------------------- Service Request
START CC
------------------------->
+- -+
+- -+
CC-ESTABLISHMENT
-------------------------> |
+- -+
+- -+
RECALL
SETUP
<-------------------------
+- -+
+- -+
ALERTING
+- -+ information
+- -+
ASSIGNMENT COMMAND
<------------------------- Assignment of
-------------------------> channel
+- -+
+- -+
CONNECT
<------------------------- Call accepted
CONNECT ACKNOWLEDGE
------------------------->
+- -+
Figure 7.21/GSM 04.08: Network initiated mobile originating call establishment with assignment after
A and B party alerting
ETSI
244 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 Handling of unknown, unforeseen, and erroneous
protocol data
8.1 General
The procedures specified in GSM 04.08 and call-related supplementary service handling in GSM 04.10 apply to those
messages which pass the checks described in this section.
This section 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 this
technical specification. It is defined in GSM 04.10 and the GSM 04.8x series.
Subsections 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 section as mandatory ("shall") and that is indicated as strongly recommended ("should"). Sections 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 sections 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.
In this section the following terminology is used:
- An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved" in
section 10, or if its value part violates rules of section 10. However it is not a syntactical error that a type 4 IE
specifies in its length indicator a greater length than defined in section 10.
- A message is defined to have semantically incorrect contents if it contains information which, possibly dependent
on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part (i.e.
sections 3, 4, 5) of GSM 04.08, GSM 04.10, or relevant GSM 04.8X series.
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. GSM 04.07.
ETSI
245 draft ETSI EN 300 940 V7.7.0 (2000-04)
8.3 Unknown or unforeseen transaction identifier
8.3.1 Call Control
The mobile station and network shall ignore a call control message received with TI value "111". For a call control
message received with TI different from "111", the following procedures shall apply:
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.
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.
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 reject a session management message other than SM-STATUS received with TI
value "111" by immediately sending an SM-STATUS message with TI value 111. For a session management message
received with TI different from "111", the following procedures shall apply:
a) Whenever any session management message except ACTIVATE PDP CONTEXT REQUEST, ACTIVATE AA
PDP CONTEXT REQUEST or SM-STATUS is received by the network specifying a transaction identifier
ETSI
246 draft ETSI EN 300 940 V7.7.0 (2000-04)
which is not recognized as relating to an active context or to a context that is in the process of activation or
deactivation or has been [recently] deactivated, the network should send a SM-STATUS message with cause #81
"invalid transaction identifier value" using the received transaction identifier value and remain in the PDP-
INACTIVE state.
b) Whenever any session management message except REQUEST PDP 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 or has been [recently] deactivated, the
MS shall send a SM-STATUS message with cause #81 "invalid transaction identifier value" using the received
transaction identifier value and remain in the PDP-INACTIVE state.
c) When an ACTIVATE AA PDP CONTEXT REQUEST or REQUEST PDP CONTEXT ACTIVATION message
is received with a transaction identifier flag set to "1", this message shall be ignored.
d) When an ACTIVATE PDP CONTEXT REQUEST message is received specifying a transaction identifier which
is not recognized as relating to a 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 AA PDP CONTEXT REQUEST
message is received by the network specifying a transaction identifier relating to a PDP context not in state PDP-
INACTIVE, the network shall deactivate the old PDP 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.
f) Whenever a REQUEST PDP CONTEXT ACTIVATION message is received by the MS specifying a transaction
identifier relating to a PDP context not in state PDP-INACTIVE, the MS shall locally deactivate the old PDP
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.
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, RR STATUS or 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 RR message or 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, RR 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 GSM 04.07 [20].
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, RR STATUS or 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.
ETSI
247 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section GSM 04.07); or
- an out of sequence IE encoded as "comprehension required" (see section GSM 04.07)
is received,
- the mobile station shall proceed as follows:
If the message is not one of the messages listed in sections 8.5.1, 8.5.2, 8.5.3, 8.5.4 and 8.5.5 a), b) or c), the
mobile station shall ignore the message except for the fact that, if an RR connection exists, it shall return a status
message (STATUS, RR STATUS or 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 section 8.5.3 b), c), d) or e) and 8.5.5 a), b), d) or e),
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, RR STATUS, MM STATUS
(depending on the protocol discriminator), GMM STATUS, or SM STATUS) with cause # 96 "Invalid
mandatory information".
8.5.1 Radio resource management
For the mobile station the following procedures shall apply:
a) If the message is a CHANNEL RELEASE message, the actions taken shall be the same as specified in 3.5 "RR
connection release".
b) If the message is a PARTIAL RELEASE message, the reactions of the MS are for further study.
8.5.2 Mobility 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.
ETSI
248 draft ETSI EN 300 940 V7.7.0 (2000-04)
b) If the message is a DISCONNECT message, a RELEASE message shall be returned with cause value # 96
"invalid mandatory information" and section 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 DEACTIVATE AA PDP CONTEXT REQUEST, a DEACTIVATE AA PDP CONTEXT
ACCEPT message shall be returned. All resources allocated for that context shall be released.
c) If the message is a REQUEST PDP CONTEXT ACTIVATION, a REQUEST PDP CONTEXT REJECT
message with cause # 96 "Invalid mandatory information" shall be returned.
d) If the message is an ACTIVATE PDP CONTEXT REQUEST, an ACTIVATE PDP CONTEXT REJECT
message with cause # 96 "Invalid mandatory information" shall be returned.
If the message is an ACTIVATE AA PDP CONTEXT REQUEST, an ACTIVATE AA PDP CONTEXT
REJECT message with cause # 96 "Invalid mandatory information" shall be returned.
8.6 Unknown and unforeseen IEs in the non-imperative
message part
8.6.1 IEIs unknown in the message
The MS shall ignore all IEs unknown in a message which are not encoded as "comprehension required" (see GSM
04.07).
The network shall take the same approach.
8.6.2 Out of sequence IEs
The MS shall ignore all out of sequence IEs in a message which are not encoded as "comprehension required" (see
GSM 04.07).
The network should take the same approach.
8.6.3 Repeated IEs
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 section 9 of this technical specification, 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
ETSI
249 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 IEs;
- conditional IE errors.
8.7.1 Syntactically incorrect optional IEs
The MS shall treat all optional IEs 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, RR 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, RR 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
GSM 04.08 (i.e. of sections 3, 4, 5) 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, RR STATUS, or MM
STATUS depending on the PD) with cause value # 95 "semantically incorrect message".
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 GSM 04.80) is the subject of the technical
specifications GSM 04.10 and the GSM 04.8x series.
9 Message functional definitions and contents
This section defines the structure of the messages of those layer 3 protocols defined in GSM 04.08. These are standard
L3 messages as defined in GSM 04.07 with the exception of those sent on the SCH, RACH, and the HANDOVER
ACCESS message.
Each definition given in the present section includes:
ETSI
250 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 IEs, which compose the imperative part of the message, occur before T, TV, and TLV formatted IEs
which compose the non-imperative part of the message, cf. GSM 04.07.) 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 N+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 IEI for an information element type; default IEIs of different IE types of the same protocol
are different. If the IEI has half octet length, it is specified by a notation representing the IEI as a hexadecimal
digit followed by a "-" (example: B-).
NOTEThe same IEI may be used for different information element types in different messages of the same
protocol.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 GSM 04.08 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 subsection of section 10 of GSM 04.08 describing the value part of the information
element.
4. the presence requirement indication (M, C, or O) for the IE as defined in GSM 04.07.
5. The format of the information element (T, V, TV, LV, TLV) as defined in GSM 04.07.
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 GSM 04.10. This indication is non-normative.
c) subsections specifying, where appropriate, conditions for IEs with presence requirement C or O in the relevant
message which together with other conditions specified in GSM 04.08 define when the information elements
shall be included or not, what non-presence of such IEs means, and - for IEs with presence requirement C - the
static conditions for presence and/or non-presence of the IEs (cf. GSM 04.07).
9.1 Messages for Radio Resources management
Table 9.1/GSM 04.08 summarizes the messages for Radio Resources management.
ETSI
251 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.1/GSM 04.08: Messages for Radio Resources management
Channel establishment messages: Reference
ADDITIONAL ASSIGNMENT 9.1.1
IMMEDIATE ASSIGNMENT 9.1.18
IMMEDIATE ASSIGNMENT EXTENDED 9.1.19
IMMEDIATE ASSIGNMENT REJECT 9.1.20
Ciphering messages: Reference
CIPHERING MODE COMMAND 9.1.9
CIPHERING MODE COMPLETE 9.1.10
Handover messages: Reference
ASSIGNMENT COMMAND 9.1.2
ASSIGNMENT COMPLETE 9.1.3
ASSIGNMENT FAILURE 9.1.4
PDCH ASSIGNMENT COMMAND 9.1.13a
HANDOVER ACCESS 9.1.14
HANDOVER COMMAND 9.1.15
HANDOVER COMPLETE 9.1.16
HANDOVER FAILURE 9.1.17
RR-CELL CHANGE ORDER 9.1.21e
PHYSICAL INFORMATION 9.1.28
RR INITIALISATION REQUEST 9.1.28a
HANDOVER ACCESS 9.1.14
HANDOVER COMMAND 9.1.15
HANDOVER COMPLETE 9.1.16
HANDOVER FAILURE 9.1.17
PHYSICAL INFORMATION 9.1.28
Channel release messages: Reference
CHANNEL RELEASE 9.1.7
PARTIAL RELEASE 9.1.26
PARTIAL RELEASE COMPLETE 9.1.27
Paging messages: Reference
PAGING REQUEST TYPE 1 9.1.22
PAGING RESPONSE 9.1.25
(continued...)
ETSI
252 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.1/GSM 04.08 (concluded): Messages for Radio Resources management
System information messages: Reference
SYSTEM INFORMATION TYPE 1 9.1.31
SYSTEM INFORMATION TYPE 2bis 9.1.33
SYSTEM INFORMATION TYPE 2ter 9.1.34
SYSTEM INFORMATION TYPE 5bis 9.1.38
SYSTEM INFORMATION TYPE 5ter 9.1.39
SYSTEM INFORMATION TYPE 13 9.1.43a
SYSTEM INFORMATION TYPE 16 9.1.43d
SYSTEM INFORMATION TYPE 17 9.1.43e
Specific messages for VBS/VGCS: Reference
NOTIFICATION/FACCH 9.1.21a
NOTIFICATION/NCH 9.1.21b
NOTIFICATION RESPONSE 9.1.21d
TALKER INDICATION 9.1.44
UPLINK ACCESS 9.1.45
UPLINK BUSY 9.1.46
UPLINK FREE 9.1.47
UPLINK RELEASE 9.1.48
VGCS UPLINK GRANT 9.1.49
..EXTENDED MEASUREMENT ORDER 9.1.51
..EXTENDED MEASUREMENT REPORT 9.1.52
Miscellaneous messages: Reference
CHANNEL MODE MODIFY 9.1.5
CHANNEL MODE MODIFY ACKNOWLEDGE 9.1.6
CHANNEL REQUEST 9.1.8
CLASSMARK CHANGE 9.1.11
CLASSMARK ENQUIRY 9.1.12
FREQUENCY REDEFINITION 9.1.13
MEASUREMENT REPORT 9.1.21
SYNCHRONIZATION CHANNEL INFORMATION 9.1.30
RR STATUS 9.1.29
GPRS SUSPENSION REQUEST 9.1.13b
Configuration Change messages: Reference
CONFIGURATION CHANGE COMMAND 9.1.12b
CONFIGURATION CHANGE ACKNOWLEDGE 9.1.12c
CONFIGURATION CHANGE REJECT 9.1.12d
Application messages: Reference
APPLICATION INFORMATION 9.1.53
9.1.1 Additional assignment
This message is sent on the main DCCH by the network to the mobile station to allocate an additional dedicated channel
while keeping the previously allocated channels. See table 9.2/GSM 04.08.
Message type: ADDITIONAL ASSIGNMENT
Significance: dual
Direction: network to mobile station
ETSI
253 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.2/GSM 04.08: ADDITIONAL ASSIGNMENT message content
IEI Information element Type / Reference Presence Format length
RR management Protocol Discriminator M V
Protocol Discriminator 10.2
Skip Indicator Skip Indicator M V
10.3.1
Additional Assignment Message Type M V 1
Message Type 10.4
Channel Description Channel Description M V 3
10.5.2.5
72 Mobile Allocation Mobile Allocation C TLV 3-10
10.5.2.21
7C Starting Time Starting Time O TV 3
10.5.2.38
9.1.1.1 Mobile Allocation
This information element shall appear if the Channel Description information element indicates frequency hopping.
If the Channel Description IE does not indicate frequency hopping and the information element is present it shall be
considered as an IE unnecessary in the message.
9.1.1.2 Starting Time
This information element appears in particular if e.g., a change of frequency is planned.
9.1.2 Assignment command
This message is sent on the main DCCH by the network to the mobile station to change the channel configuration to
another independent dedicated channel configuration, when no timing adjustment is needed. See table 9.3/GSM 04.08
Message type: ASSIGNMENT COMMAND
Significance: dual
Table 9.3/GSM 04.08: ASSIGNMENT COMMAND message content
RR management Protocol Discriminator M V
Skip Indicator Skip Indicator M V
10.3.1
Assignment command Message Type M V 1
Message Type 10.4
Description of the Channel Description 2 M V 3
First Channel, after time 10.5.2.5a
Power Command Power Command M V 1
10.5.2.28
05 Frequency List, after time Frequency List C TLV 4-132
10.5.2.13
(continued)
ETSI
254 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.3/GSM 04.08 (concluded): ASSIGNMENT COMMAND message content
62 Cell Channel Cell Channel Description O TV 17
Description 10.5.2.1b
10 Description of the Multislot Allocation C TLV 3-12
multislot configuration 10.5.2.21b
63 Mode of the First Channel Mode O TV 2
Channel (Channel Set 1) 10.5.2.6
11 Mode of Channel Set 2 Channel Mode O TV 2
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
64 Description of the Channel Description O TV 4
Second Channel, after time 10.5.2.5
66 Mode of the Second Channel Mode 2 O TV 2
Channel 10.5.2.7
72 Mobile Allocation, Mobile Allocation C TLV 3-10
after time 10.5.2.21
10.5.2.38
19 Frequency List, before time Frequency List C TLV 4-132
10.5.2.13
1C Description of the Channel Description 2 O TV 4
First Channel, before time 10.5.2.5a
1D Description of the Channel Description O TV 4
Second Channel, before time 10.5.2.5
1E Frequency channel sequence Frequency channel
sequence
C TV 10
before time 10.5.2.12
9- Cipher Mode Setting Cipher Mode Setting O TV 1
10.5.2.9
01 VGCS target mode Indication VGCS target mode
Indication
O TLV 3
10.5.2.42a
03 Multi-Rate MultiRate configuration O TLV 4-8
configuration 10.5.2.21aa
9.1.2.1 Mode of the First Channel (Channel Set 1) and Mode of Channel Set "X"
(2=<X=<8)
If this information element is not present the channel mode of the previously allocated channel or channels for Channel
Set X (1=<X<=8) shall be assumed.
If Channel Set X is not defined for the configuration, the Mode of Channel Set X IE shall be considered as an IE
unnecessary in the message.
NOTE: Clause 3.4.3.1 defines cases when one or several Mode of Channel Set X IEs shall be included in the
message.
9.1.2.2 Description of the Second Channel
These information elements appear in the case of an assignment occurring if the mobile station carries two connections
(on two dedicated channels, for the TCH/H + TCH/H configuration).
ETSI
255 draft ETSI EN 300 940 V7.7.0 (2000-04)
The connection using the channel previously defined in the Description of the First Channel IEs of an ASSIGNMENT
COMMAND or HANDOVER COMMAND message shall use the channel defined in the Description of the First
Channel IEs of the ASSIGNMENT COMMAND message defining the new configuration.
The channel described in the Description of the First Channel IEs carries the main DCCH. The SACCH used is the one
associated with that channel.
9.1.2.3 Mode of the Second Channel
If no Description of the Second Channel IE is present but the information element is present it shall be considered as an
IE unnecessary in the message.
This information element appears at least when the channel mode is changed for the channel defined in the second
channel description information elements.
9.1.2.4 Mobile Allocation and Frequency List, after the starting time
If at least one of the channel descriptions for the starting time indicates frequency hopping, one and only one of the
following information elements shall be present and apply to all assigned channels
- Mobile Allocation, after time
- Frequency List, after time.
If neither of the Channel Description IEs for after time indicate frequency hopping, if decoding of Channel Description
IEs for before time does not require a frequency list for after time (see next section), and one or both of the two
information elements are present they shall be considered as IEs unnecessary in the message.
The starting time information element is included when the network wants the mobile station to change the frequency
parameters of the channels more or less at the moment a change of channel occurs. In this case a number of information
elements may be included to give the frequency parameters to be used before the starting time.
If the starting time information element is present and none of the information elements referring to before the starting
time are present, the mobile station waits and accesses the channels at the indicated time.
If the starting time information element is present and at least one of the information elements referring to before the
starting time is present, the mobile station does not wait for the indicated time and accesses the channel using the
frequency parameters for before the starting time.
If the starting time information element is not present and at some of the information elements referring to before the
starting time is present, these information elements shall be considered as IEs unnecessary in the message.
If the description of the first channel, before time IE is not present, the channel description to apply for before the time,
if needed, is given by the description of the first channel, after time IE.
If the description of the second channel, after time IE is present, the description of the second channel, before time IE
not present, and a description of the configuration for before the time needed, the channel configuration before the
starting time is nevertheless of two traffic channels, and the channel description to apply to the second channel before
the starting time is given by the description of the second channel, after time IE.
If the starting time IE is present and at least one of the channel descriptions for before the starting time indicates
frequency hopping, one and only one of the following information elements may be present and applies before the
starting time to all assigned channels
- Mobile Allocation, before time IE;
- Frequency list, before time IE;
- Frequency channel sequence, before time IE.
ETSI
256 draft ETSI EN 300 940 V7.7.0 (2000-04)
frequency hopping, and none of the above mentioned IE is present, a frequency list for after the starting time must be
present (see 9.1.2.4), and this list applies also for the channels before the starting time.
9.1.2.6 Reference cell frequency list
If any of the mobile allocation information elements is present, then the network must ensure that either the mobile
station has received in a previous message the proper reference cell frequency list (CA), or that the cell channel
description IE is present.
If the cell channel description IE is present, it is used to decode the mobile allocation IEs in the message, as well as in
later messages until reception of a new reference cell frequency list or the cell is left.
9.1.2.7 Cell Channel Description
If present, this information element shall be used to decode the Mobile Allocation IE in the same message and in
subsequent messages.
9.1.2.8 Cipher Mode Setting
If this information element is omitted, the mode of ciphering is not changed after the mobile station has switched to the
assigned channel.
9.1.2.9 VGCS target mode Indication
This information element is identified as "comprehension required". Only mobile stations supporting VGCS talking
are required to accept the presence of the element. The presence of the element shall trigger an exception handling if
received by a mobile station not supporting VGCS talking .
This IE indicates which mode is to be used on the new channel (i.e. dedicated mode or group transmit mode). If this
information element is not present, the mode shall be the same as on the previous channel.
The IE also indicates the group cipher key number for the group cipher key to be used on the new channel or if the new
channel is non ciphered. If the information element is not present, the ciphering mode shall be the same as on the
previous channel.
NOTE: A mobile station supporting VGCS talking shall not consider a syntactical error when this IE is present
and the channel mode is not speech.
9.1.2.10 Description of the multislot allocation
This information element is included if so indicated by the channel type and TDMA offset field in the Channel
Description information element and is used to assign channels that do not carry a main signalling link in a multislot
configuration. It indicates how the used timeslots are divided into separate channel sets.
If the Channel Description IE does not require the presence of the information element the Description of the multislot
allocation IE shall be considered as an IE unnecessary in the message.
If multislot configuration is indicated by the Channel Description IE but the Multislot Allocation IE is not present, all
channels in the configuration belong to one channel set, Channel Set 1.
NOTE: As a change of timeslot number cannot occur for the channel described after the starting time, the
Multislot Allocation IE does not have to be included more than once.
9.1.2.11 Multi Rate configuration
This information element appears if the Mode of the First Channel indicates a multi-rate speech codec, and if the
assigned configuration is new, i.e. it is different from the MultiRateconfiguration of a previously allocated channel in the
cell.
ETSI
257 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.3 Assignment complete
This message is sent on the main DCCH from the mobile station to the network to indicate that the mobile station has
established the main signalling link successfully. See table 9.4/GSM 04.08.
Message type: ASSIGNMENT COMPLETE
Significance: dual
Direction: mobile station to network
Table 9.4/GSM 04.08: ASSIGNMENT COMPLETE message content
RR management Protocol Discriminator M V 1/2
Skip Indicator Skip Indicator M V 1/2
10.3.1
Assignment Complete Message Type M V 1
Message Type 10.4
RR Cause RR Cause M V 1
10.5.2.31
9.1.4 Assignment failure
This message is sent on the main DCCH on the old channel from the mobile station to the network to indicate that the
mobile station has failed to seize the new channel. See table 9.5/GSM 04.08
Message type: ASSIGNMENT FAILURE
Significance: dual
Table 9.5/GSM 04.08: ASSIGNMENT FAILURE message content
10.3.1
Assignment Failure Message Type M V 1
Message Type 10.4
RR cause RR Cause M V 1
10.5.2.31
9.1.5 Channel mode modify
This message is sent on the main DCCH by the network to the mobile station to request the setting of the mode for the
indicated channel(s). The message can be used to change the channel mode of a Multislot Configuration which only
contains one channel set. See table 9.6/GSM 04.08.
Message type: CHANNEL MODE MODIFY
Significance: local
ETSI
258 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.6/GSM 04.08: CHANNEL MODE MODIFY message content
10.3.1
Channel Mode Modify Message Type M V 1
Message Type 10.4
Channel Description Channel Description 2 M V 3
10.5.2.5a
Channel Mode Channel Mode M V 1
10.5.2.6
01 VGCS target mode Indication VGCS target mode Indication O TLV 3
10.5.2.42a
9.1.5.1 Channel Description
This is sufficient to identify the channel in the case of a TCH/H + TCH/H configuration. If used for a multislot
configuration, the IE shall describe the present channel configuration with TN indicating the main channel. The IE shall
not indicate a new channel configuration when included in the Channel Mode Modify message.
9.1.5.2 VGCS target mode Indication
This IE indicates which RR mode is to be used with the new channel mode (i.e. dedicated mode or group transmit
mode). If this information element is not present, the RR mode shall be the same as with the previous channel mode.
channel is non ciphered. If the information element is not present, the ciphering mode shall be the same as with the
previous channel mode.
NOTE: A mobile station supporting VGCS Talking shall not consider a syntactical error if this IE is present and
the channel mode is not speech.
9.1.5.3 Multi Rate configuration
This information element appears if the Channel Mode IE indicates a multi-rate speech codec.
9.1.6 Channel mode modify acknowledge
This message is sent on the main DCCH by the mobile station to the network to indicate the successful or unsuccessful
execution of a channel mode modify request. See table 9.7/GSM 04.08.
Message type: CHANNEL MODE MODIFY ACKNOWLEDGE
Significance: local
Table 9.7/GSM 04.08: CHANNEL MODE MODIFY ACKNOWLEDGE message content
ETSI
259 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.3.1
Channel Mode Modify Message Type M V 1
Acknowledge Message Type 10.4
Channel Description Channel Description 2 M V 3
10.5.2.5a
Channel Mode Channel Mode M V 1
10.5.2.6
9.1.7 Channel release
This message is sent on the main DCCH from the network to the mobile station to initiate deactivation of the dedicated
channel used. See table 9.8/GSM 04.08
Message type: CHANNEL RELEASE
Significance: dual
ETSI
260 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.8/GSM 04.08: CHANNEL RELEASE message content
10.3.1
Channel Release Message Type M V 1
Message Type 10.4
10.5.2.31
73 BA Range BA Range O TLV 6 - ?
10.5.2.1a
74 Group Channel Description Group Channel Description O TLV 4-13
10.5.2.14b
8x Group Cipher Key Number Group Cipher Key Number C TV 1
10.5.1.10
Cx GPRS Resumption GPRS Resumption O TV 1
10.5.2.14c
75 BA List Pref BA List Pref O TLV 3-?
10.5.2.1c
9.1.7.1 Channel description and mobile allocation
If a CHANNEL RELEASE is send to a mobile station which is in dedicated mode and which is involved in a voice
group call or has responded to a notification to a voice group call or voice broadcast call, a group channel description
may be included, describing the voice group call channel or voice broadcast channel to which the mobile station shall go
after the channel release procedure.
Mobile stations not supporting VGCS listening or VBS listening shall consider this information element as unnecessary.
9.1.7.2 Group Cipher Key Number
This IE may be present only if the Group channel description IE is provided. The presence of this IE indicates that the
mobile station shall use the Group Cipher Key indicated by the Group Cipher Key Number IE for deciphering on the
VGCS or VBS channel. If this IE is not present, no ciphering is applied on the VGCS or VBS channel.
Mobile stations not supporting VGCS listening or VBS listening shall ignore this information element.
9.1.8 Channel request
This message is sent in random mode on the RACH. It does not follow the basic format. The possible formats are
presented directly below, without reference to information fields. The order of bit transmission is defined in GSM 04.04.
The message is only one octet long, coded as shown in figure 9.1/GSM 4.08 and table 9.9/GSM 04.08.
ETSI
261 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
ESTABLISHMENT RANDOM
+ - - - - - - - - + octet 1
CAUSE REFERENCE
+-----------------------------------------------+
Figure 9.1/GSM 04.08: CHANNEL REQUEST message content
ESTABLISHMENT CAUSE (octet 1)
This information field indicates the reason for requesting the establishment of a connection. This field has a variable
length (from 3 bits up to 6 bits).
RANDOM REFERENCE (octet 1)
This is an unformatted field with variable length (from 5 bits down to 2 bits).
The Channel Request message is coded as follows:
(Random Reference field is filled with "x").
Table 9.9/GSM 04.08: CHANNEL REQUEST message content
MS codes According to Establishment cause:
bits
8 .... 1
101xxxxx Emergency call
110xxxxx Call re-establishment; TCH/F was in use, or
TCH/H was in use but the network does not
set NECI bit to 1
011010xx Call re-establishment; TCH/H was in use and the
network sets NECI bit to 1
011011xx Call re-establishment; TCH/H + TCH/H was in use
and the network sets NECI bit to 1
100xxxxx Answer to paging
0010xxxx
0011xxxx See table 9.9a/GSM 04.08
0001xxxx
111xxxxx Originating call and TCH/F is needed, or originating call
and the network does not set NECI bit to 1, or
procedures that can be completed with a SDCCH and the
network does not set NECI bit to 1. note 1
0100xxxx Originating speech call from dual-rate mobile station when TCH/H
is sufficient and supported by the MS for speech calls and the network sets
NECI bit to 1 note 5
0101xxxx Originating data call from dual-rate mobile station when TCH/H
is sufficient and supported by the MS for data calls and the network sets NECI
bit to 1 note 5
000xxxxx Location updating and the network does not set NECI bit to 1
0000xxxx Location updating and the network sets NECI bit to 1
0001xxxx Other procedures which can be completed with note 1
an SDCCH and the network sets NECI bit to 1
011110xx One phase packet access with request for single timeslot uplink
01111x0x transmission; one PDCH is needed.
01111xx0
ETSI
262 draft ETSI EN 300 940 V7.7.0 (2000-04)
01110xxx Single block packet access; one block period on a PDCH is needed for
two phase packet access or other RR signalling purpose.
01100111 LMU establishment note 2
01100xx0 Reserved for future use
01100x01
01100011 note 2a
01111111 Reserved for future use. note 2b
NOTE 1: Examples of these procedures are: IMSI detach, Short Message Service (SMS), Supplementary Service
management, Location Services.
NOTE 2: If such messages are received by a network, an SDCCH shall be allocated.
NOTE 2a: If such messages are received by a network, an SDCCH may be allocated.
NOTE 2b:This value shall not be used by the mobile station on RACH. If such message is received by the network,
it may be ignored.
Table 9.9a/GSM 04.08: CHANNEL REQUEST message (when answering to paging for RR connection
establishment)
+-------------------------------------------------------+
++ MS Capability
+-------+ Full rate Dual SDCCH
Paging +------+ only rate only
Indication 3) + (note 5)
+----------------+------------+------------+------------
Any channel 100xxxxx 100xxxxx 100xxxxx
+----------------+------------+------------+------------
SDCCH 0001xxxx 0001xxxx 0001xxxx
+----------------+------------+------------+------------
TCH/F 100xxxxx 0010xxxx 0001xxxx
+----------------+------------+------------+------------
TCH/H or TCH/F 100xxxxx 0011xxxx 0001xxxx
+-------------------------------------------------------+
NOTE 3: The Paging Indication is provided by the Channel Needed IE (or the Channel Needed field) associated
with the page which triggered the sending of the CHANNEL REQUEST message.
NOTE 4: In some cases the established connection will be used only to allow a default rejection mechanism to take
place (typically the mobile station will send a RELEASE COMPLETE message with cause #88
"incompatible destination" as an answer to the incoming SETUP message).
NOTE 5: In this section, dual rate capability means that the MS supports both full rate and half-rate channels at
least for the signalling channel mode. In addition, it may support either speech channel mode, or data
channel modes, or both on half-rate channels.
9.1.9 Ciphering mode command
This message is sent on the main DCCH from the network to the mobile station to indicate that the network has started
deciphering and that enciphering and deciphering shall be started in the mobile station, or to indicate that ciphering will
not be performed. See table 9.10/GSM 04.08.
Message type: CIPHERING MODE COMMAND
Significance: dual
ETSI
263 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.10/GSM 04.08: CIPHERING MODE COMMAND message content
10.3.1
Cipher Mode Command Message Type M V 1
Message Type 10.4
Ciphering Mode Setting Cipher Mode Setting M V 1/2
10.5.2.9
Cipher Response Cipher Response M V 1/2
10.5.2.10
9.1.10 Ciphering mode complete
This message is sent on the main DCCH from the mobile station to the network to indicate that enciphering and
deciphering has been started in the MS. See table 9.11/GSM 04.08.
Message type: CIPHERING MODE COMPLETE
Significance: dual
Table 9.11/GSM 04.08: CIPHERING MODE COMPLETE message content
10.3.1
Cipher Mode Complete Message Type M V 1
Message Type 10.4
17 Mobile Equipment Mobile Identity O TLV 3-11
Identity 10.5.1.4
9.1.10.1 Mobile Equipment Identity
This information element is included if and only if the mobile station shall include its IMEISV (see section 3.4.7). This
information element shall only refer to IMEISV.
9.1.11 Classmark change
This message is sent on the main DCCH by the mobile station to the network to indicate a classmark change or as a
response to a classmark enquiry. See table 9.12/GSM 04.08.
Message type: CLASSMARK CHANGE
Significance: dual
ETSI
264 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.12/GSM 04.08: CLASSMARK CHANGE message content
10.3.1
Classmark Change Message Type M V 1
Message Type 10.4
Mobile Station Mobile Station M LV 4
Classmark Classmark 2
10.5.1.6
20 Additional Mobile Mobile Station C TLV 3-14
Station Classmark Classmark 3
Information 10.5.1.7
9.1.11.1 Additional Mobile Station Classmark Information
This IE shall be included if and only if the CM3 bit in the Mobile Station Classmark IE is set to 1.
9.1.11.2 Mobile Station Classmark
This IE shall include for multiband MS the Classmark 2 corresponding to the frequency band in use.
9.1.12 Classmark enquiry
This message is sent on the main DCCH by the network to the mobile station to request classmark information. See table
9.12a/GSM 04.08.
Message type: CLASSMARK ENQUIRY
Significance: dual
Table 9.12a/GSM 04.08: CLASSMARK ENQUIRY message content
10.3.1
Classmark Enquiry Message Type M V 1
Message Type 10.4
9.1.12a Spare
9.1.12b Configuration change command
This message is sent on the main DCCH from the network to the mobile station to change the channel configuration of a
multislot configuration. See table 9.12b/GSM 04.08.
Message type: CONFIGURATION CHANGE COMMAND
ETSI
265 draft ETSI EN 300 940 V7.7.0 (2000-04)
Significance: dual
Table 9.12b/GSM 04.08: CONFIGURATION CHANGE COMMAND message contents
IEI Information element Type/Reference Presence Format length
10.3.1
Configuration change Message Type M V 1
Message Type 10.4
Description of the Multislot Allocation M LV 2-11
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
9.1.12b.1 Description of the multislot allocation
This information element is used to assign channels that do not carry the main signalling link in a multislot
configuration. It indicates if multiple channel sets are used.
9.1.12b.2 Mode of Channel Set X ( 1=<X<=8)
Set X shall be assumed.
message.
9.1.12c Configuration change acknowledge
changed to the ordered channel configuration successfully. See table 9.12c/GSM 04.08.
Message type: CONFIGURATION CHANGE ACKNOWLEDGE
Significance: dual
ETSI
266 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.12c/GSM 04.08: CONFIGURATION CHANGE ACKNOWLEDGE message contents
10.3.1
Configuration Change Message Type M V 1
Acknowledge Message Type 10.4
9.1.12d Configuration change reject
not managed to switch to the channel configuration ordered by the configuration change command and is still using the
previous configuration. See table 9.12d/GSM 04.08.
Message type: CONFIGURATION CHANGE REJECT
Significance: dual
Table 9.12d/GSM 04.08: CONFIGURATION CHANGE REJECT message contents
10.3.1
Configuration Change Message Type M V 1
Reject Message Type 10.4
10.5.2.31
9.1.13 Frequency redefinition
This message is sent on the main DCCH from the network to the MS to indicate that the frequencies and the hopping
sequence of the allocated channels shall be changed. See table 9.13/GSM 04.08
Message type: FREQUENCY REDEFINITION
Significance: dual
Direction: network to MS
ETSI
267 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.13/GSM 04.08: FREQUENCY REDEFINITION message content
10.3.1
Frequency Redefinition Message Type M V 1
Message Type 10.4
10.5.2.5
Mobile Allocation Mobile Allocation M LV 1-9
10.5.2.21
Starting Time Starting Time M V 2
10.5.2.38
9.1.13.1 Cell Channel Description
If it does not appear, the cell channel description is assumed to be unchanged.
9.1.13a PDCH Assignment command
This message is sent on the main DCCH by the network to the mobile station to change the channel configuration to a
PDCH, when no timing adjustment is needed. See table 9.13a/GSM 04.08.
A mobile station that does not support the <<GRPS>> option shall regard this message as an unknown message.
Message type: PDCH ASSIGNMENT COMMAND
Significance: dual
ETSI
268 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.13a/GSM 04.08: PDCH ASSIGNMENT COMMAND message content
10.3.1
PDCH Assignment command Message Type M V 1
Message Type 10.4
Description of the Channel Description M V 3
Channel, after time 10.5.2.5
05 Frequency List, after time Frequency List C TLV 4-132
10.5.2.13
10.5.2.38
19 Frequency List, before time Frequency List C TLV 4-132
10.5.2.13
1C Description of the Channel Description O TV 4
Channel, before time 10.5.2.5
1E Frequency channel sequence Frequency channel
sequence
C TV 10
22 RR Packet Uplink RR Packet Uplink C TLV 3-?
Assignment Assignment
10.5.2.25a
23 RR Packet Downlink RR Packet Downlink C TLV 3-?
Assignment Assignment
10.5.2.25b
9.1.13a.1 Mobile Allocation and Frequency List, after the starting time
If the channel description for after the starting time indicates frequency hopping, one and only one of the following
information elements shall be present
- Mobile Allocation, after time
ETSI
269 draft ETSI EN 300 940 V7.7.0 (2000-04)
- Frequency List, after time.
If the Channel Description IE for after time does not indicate frequency hopping, if decoding of Channel Description IE
for before time does not require a frequency list for after time (see next section), and one or both of the two information
elements are present they shall be considered as IEs unnecessary in the message.
9.1.13a.2 Starting Time
parameters of the channels more or less at the moment the change to a TBF occurs. In this case a number of information
time are present, the mobile station waits and uses the TBFfrom the indicated time.
starting time is present, the mobile station does not wait for the indicated time and uses the TBF using the frequency
parameters for before the starting time.
If the starting time information element is not present and some of the information elements referring to before the
If the description of the channel, before time IE is not present, the channel description to apply for before the time, if
needed, is given by the description of the channel, after time IE.
If the starting time IE is present and the channel description for before the starting time indicates frequency hopping,
one and only one of the following information elements may be present and applies before the starting time
If the starting time IE is present and the channel description for before the starting time indicates frequency hopping,
and none of the above mentioned IE is present, a frequency list for after the starting time must be present (see 9.1.2.4),
and this list applies also for the TBF before the starting time.
9.1.13a.3 Reference cell frequency list
If any of the mobile allocation information elements are present, then the network shall ensure that either the mobile
station has received in a previous message the proper reference cell frequency list (CA), or that the cell channel
description IE is present.
If the cell channel description IE is present, it is used to decode the mobile allocation IEs in the message, as well as in
later dedicated mode messages until reception of a new reference cell frequency list or the cell is left.
9.1.13a.4 Cell Channel Description
If present, this information element shall be used to decode the Mobile Allocation IE in the same message and in
subsequent messages.
9.1.13a.5 Packet Assignment
One and only one of the following information elements shall be present:
- RR Packet Uplink Assignment
- RR Packet Downlink Assignment.
ETSI
270 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.13b GPRS suspension request
This message is sent on the main DCCH by the mobile station to the network to request a suspension of GPRS services.
See table 9.13b/GSM 04.08.
Message type: GPRS SUSPENSION REQUEST
Significance: dual
Table 9.13b/GSM 04.08: GPRS SUSPENSION REQUEST message content
10.3.1
GPRS Suspension Request Message Type M V 1
Message Type 10.4
Temporary Logical Link TLLI M V 4
Identity 10.5.2.41a
Routeing Area Identification Routeing Area Identification M V 6
10.5.5.15
Suspension cause Suspension cause M V 1
10.5.2.47
ETSI
271 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.14 Handover access
This message is sent in random mode on the main DCCH during a handover procedure. It does not follow the basic
format. The format is presented directly below without reference to information elements. The order of bit transmission
is defined in GSM 04.04.
This message is only one octet long, coded as shown in figure 9.2/GSM 04.08 and table 9.14/GSM 04.08.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
handover reference octet 1
+-----------------------------------------------+
Figure 9.2/GSM 04.08: HANDOVER ACCESS message content
Table 9.14/GSM 04.08: HANDOVER ACCESS message content
+----------------------------------------------------------+

HANDOVER REFERENCE
This is an unformatted 8 bit field.
(also described in section 10.5.2.15)

+----------------------------------------------------------+
9.1.15 Handover command
This message is sent on the main DCCH by the network to the mobile station to change the dedicated channel
configuration, timing adjustment needed. See table 9.15/GSM 04.08.
Message type: HANDOVER COMMAND
Significance: dual
ETSI
272 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.15/GSM 04.08: HANDOVER COMMAND message content
10.3.1
Handover Command Message Type M V 1
Message Type 10.4
Cell Description Cell description M V 2
10.5.2.2
Description of the Channel Description 2 M V 3
first channel, after time 10.5.2.5a
Handover Reference Handover Reference M V 1
10.5.2.15
Power Command and Access Power Command and Access M V 1
type type
10.5.2.28a
D- Synchronization Synchronization O TV 1
Indication Indication
10.5.2.39
02 Frequency Short List, Frequency Short List C TV 10
05 Frequency List, Frequency List C TLV 4-131
62 Cell Channel Cell Channel Description C TV 17
10 Description of the Multislot Allocation C TLV 3-12
63 Mode of the First Channel Mode O TV 2
Channel(Channel Set 1)) 10.5.2.6
10.5.2.6
10.5.2.6
(continued)
ETSI
273 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.15/GSM 04.08 (continued): HANDOVER COMMAND message content
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
10.5.2.6
64 Description of the Channel Description O TV 4
Second Channel, after time 10.5.2.5
66 Mode of the Second Channel Mode 2 O TV 2
Channel 10.5.2.7
69 Frequency Channel Frequency Channel C TV 10
Sequence, after time Sequence
10.5.2.12
10.5.2.38
7B Real Time Difference Time Difference C TLV 3
10.5.2.41
7D Timing Advance Timing Advance C TV 2
10.5.2.40
12 Frequency Short List, Frequency Short List C TV 10
19 Frequency List, Frequency List C TLV 4-131
1C Description of the Channel Description 2 O TV 4
First Channel, before time 10.5.2.5a
(continued)
ETSI
274 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.15/GSM 04.08 (concluded): HANDOVER COMMAND message content
1D Description of the Channel Description O TV 4
Second Channel, before time 10.5.2.5
1E Frequency channel sequence Frequency channel sequence C TV 10
9- Cipher Mode Setting Cipher Mode Setting O TV 1
10.5.2.9
01 VGCS target mode Indication VGCS target mode Indication O TLV 3
10.5.2.42a
9.1.15.1 Synchronization Indication
If this information element does not appear, the assumed value is "non-synchronized".
9.1.15.2 Mode of the First Channel (Channel Set 1) and Mode of Channel Set "X"
(2=<X<=8)
Set X (1=<X<=8) shall be assumed.
message.
9.1.15.3 Description of the Second Channel
These information element appear if the mobile station carries two connections (on two dedicated channels, for the
TCH/H+TCH/H configuration).
The connection using the channel previously defined in the Description of the First Channel IE of an ASSIGNMENT
COMMAND or HANDOVER COMMAND message shall use the channel defined in the first channel description IE of
the HANDOVER COMMAND message defining the new configuration.
The channel described in the Description of the First Channel IE carries the main DCCH. The SACCH used is the one
associated with that channel.
9.1.15.4 Mode of the Second Channel
If the Description of the Second Channel IE is not present and the information element is present it shall be considered
as an IE unnecessary in the message.
This element appears at least when the channel mode is changed for the channel defined in the Description of the
Second Channel information element.
ETSI
275 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.15.5 Frequency Channel Sequence, Frequency List, Frequency short list and
Mobile Allocation, after time
If at least one of the channel descriptions for after time indicates frequency hopping, one and only one of the following
information elements shall be present:
- Frequency Channel Sequence, after time;
- Frequency list, after time;
- Frequency Short List, after time;
- Mobile Allocation, after time.
If neither of the Channel Description IEs indicate frequency hopping, if they are not required for the decoding of
Channel Description IEs for before time, and if any of the four information elements are present they shall be considered
as IEs unnecessary in the message.
The Frequency Channel Sequence information element shall not be used unless all the ARFCNs that it indicates are in
the P-GSM band.
parameters of the channels more or less at the moment a change of channel occurs. In this case a number of information
The starting time information element refers to the new cell time.
time are present, the mobile station waits and accesses the channels at the indicated time.
starting time is present, the mobile station does not wait for the indicated time and accesses the channel using the
frequency parameters for before the starting time.
If the starting time information element is not present and some of the information elements referring to before the
If the description of the first channel, before time IE is not present, the channel description to apply for before the time,
if needed, is given by the description of the first channel, after time IE.
If the description of the second channel, after time IE is present, the description of the second channel, before time IE
not present, and a description of the configuration for before the time needed, the channel configuration before the
starting time is nevertheless of two traffic channels, and the channel description to apply to the second channel before
the starting time is given by the description of the second channel, after time IE.
frequency hopping, one and only one of the following information elements may be present and applies before the
starting time to all assigned channels:
- Frequency Short list, before time IE;
ETSI
276 draft ETSI EN 300 940 V7.7.0 (2000-04)
frequency hopping, and none of the above mentioned IE is present, a frequency list for after the starting time must be
present (see 9.1.2.4), and this list applies also for the channels before the starting time.
9.1.15.7 Reference cell frequency list
If any of the mobile allocation information elements is present, then the cell channel description IE must be present. It is
used to decode the mobile allocation IEs in the message.
In addition, if no information elements pertaining to before the starting time is present in the message, the frequency list
defined by the cell channel description IE is used to decode the mobile allocation IEs in later messages received in the
new cell until reception of a new reference cell frequency list or the new cell is left.
9.1.15.8 Real Time Difference
This information element shall appear if the Synchronization Indication information element indicates a pseudo-
synchronous handover otherwise it shall be considered as an unnecessary information element.
9.1.15.9 Timing Advance
This information element shall appear if the "synchronization indication" element indicates a presynchronized handover.
If not included for a presynchronized handover, then the default value as defined in GSM 05.10 shall be used. For other
types of handover it shall be considered as an unnecessary information element.
If this information element is omitted, the mode of ciphering is not changed after the mobile station has switched to the
assigned channel.
Only applicable for mobile stations supporting VGCS talking:
The cipher mode setting IE shall not be included if a HANDOVER COMMAND message is sent on a VGCS channel or
in a HANDOVER COMMAND message on a dedicated channel for a handover to a VGCS channel.
9.1.15.11 VGCS target mode indication
This IE indicates which mode is to be used on the new channel (i.e. dedicated mode or group transmit mode). If this
information element is not present, the mode shall be the same as on the previous channel.
channel is non ciphered. If the information element is not present, the ciphering mode shall be the same as on the
previous channel.
NOTE: A mobile station supporting VGCS Talking shall not consider a syntactical error if this IE is present and
the channel mode is not speech.
9.1.15.12 Description of the multislot allocation
This information element is included if so indicated by the channel type and TDMA offset field in the Channel
Description information element and is used to assign channels that do not carry a main signalling link in a multislot
configuration. It indicates how the used timeslots are divided into separate channel sets.
If the Channel Description IE does not require the presence the information element it shall be considered as an IE
If multislot configuration is indicated by the Channel Description IE but the Multislot Allocation IE is not present, all
channels in the configuration belong to one channel set, Channel Set 1.
ETSI
277 draft ETSI EN 300 940 V7.7.0 (2000-04)
NOTE: As a change of timeslot number cannot occur for the channel described for after the starting time, the
Multislot Allocation IE does not have to be included more than once.
9.1.15.13 MultiRateconfiguration
This information element appears if the Mode of the First Channel indicates a multi-rate speech codec, and if the
assigned configuration is new, i.e. it is different from the MultiRateconfiguration used in the serving cell. If the Mode of
the First Channel indicates a multi-rate speech codec, and this IE is not included, then the mobile station shall assume
that the MultiRateconfiguration has not changed.
9.1.16 Handover complete
established the main signalling link successfully. See table 9.16/GSM 04.08.
Message type: HANDOVER COMPLETE
Significance: dual
Table 9.16/GSM 04.08: HANDOVER COMPLETE message content
10.3.1
Handover Complete Message Type M V 1
Message Type 10.4
10.5.2.31
77 Mobile Observed Time Mobile Time Difference O TLV 5
Difference 10.5.2.21a
9.1.16.1 Mobile Observed Time Difference
This information element is included if and only if the Synchronization Indication IE in the HANDOVER COMMAND
message requests it to be sent.
9.1.17 Handover failure
This message is sent on the main DCCH on the old channel from the mobile station to the network to indicate that the
mobile station has failed to seize the new channel. See table 9.17/GSM 04.08.
Message type: HANDOVER FAILURE
Significance: dual
ETSI
278 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.17/GSM 04.08: HANDOVER FAILURE message content
10.3.1
Handover Failure Message Type M V 1
Message Type 10.4
10.5.2.31
9.1.18 Immediate assignment
This message is sent on the CCCH by the network to the mobile station in idle mode to change the channel configuration
to a dedicated configuration while staying in the same cell or to the mobile station in packet idle mode to change the
channel configuration to either an uplink or a downlink packet data channel configuration in the cell. See
table 9.18/GSM 04.08.
The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the
IA Rest Octets and L2 Pseudo Length information elements.
Message type: IMMEDIATE ASSIGNMENT
Significance: dual
ETSI
279 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.18/GSM 04.08: IMMEDIATE ASSIGNMENT message content
L2 Pseudo Length L2 Pseudo Length M V 1
10.5.2.19
10.3.1
Immediate Assignment Message Type M V 1
Message Type 10.4
Page Mode Page Mode M V 1/2
10.5.2.26
Dedicated mode or TBF Dedicated mode or TBF M V 1/2
10.5.2.25b
Channel Description Channel Description C V 3
10.5.2.5
Packet Channel Description Packet Channel Description C V 3
10.5.2.25a
Request Reference Request Reference M V 3
10.5.2.30
Timing Advance Timing Advance M V 1
10.5.2.40
10.5.2.21
10.5.2.38
IA Rest Octets IA Rest Octets M V 0-11
10.5.2.16
9.1.18.0a Dedicated mode or TBF
A mobile station not supporting GPRS may ignore the contents of this information element and regard it as an
unnecessary IE. Such mobile station shall assume that this message assigns a dedicated mode resource.
9.1.18.0b Channel Description
If the Dedicated mode or TBF IE indicates that the message assigns a dedicated mode resource, the mobile station shall
consider this information element present in the message.
ETSI
280 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.18.0c Packet Channel Description
If the Dedicated mode or TBF IE indicates that the message assigns a Temporary Block Flow (TBF), the mobile station
shall consider this information element present in the message. If the Dedicated mode or TBF IE indicates that this
message is the first of two in a two-message assignment of an uplink or downlink TBF, the mobile station shall ignore
the contents of this information element and regard it as an unnecessary IE.
9.1.18.0d Request Reference
If this message is used in an assignment of a downlink TBF, the network shall code this information element, e.g. by
using a suitably offset frame number, such that the resource reference cannot be confused with any CHANNEL
REQUEST message sent by a mobile station.
If the IA Rest Octets IE indicates that this message is the second message of a two-message assignment of an uplink or
downlink TBF, this information element shall have the same contents as the first message of the assignment.
9.1.18.0e Timing Advance
If the IA Rest Octets IE indicates that this message is the second message of a two-message assignment of an uplink or
downlink TBF, the mobile station shall ignore the contents of this information element and regard it as an unnecessary
IE.
If this message assigns a dedicated mode resource and the Channel Description IE does not indicate frequency hopping ,
the length indicator of this information element shall be set to zero, and the mobile station shall consider the IE as an
unnecessary IE.
If this message assigns a TBF and the Packet Channel Description IE does not indicate frequency hopping or if it uses
indirect encoding of a hopping RF channel configuration, the length indicator of this information element shall be set to
zero, and the mobile station shall consider the IE as an unnecessary IE.
This information element appears if e.g. a frequency change is in progress.
If this message is used in an assignment of an uplink or downlink TBF, the mobile station shall ignore the contents of the
Starting Time information element if included and consider it as an unnecessary IE.
9.1.18.3 IA Rest Octets (Frequency parameters, before time)
The sum of the length of this IE and the L2 Pseudo Length of the message equals 22.
If the starting time IE is present but not the frequency parameters, before time construction, the mobile stations must
wait until the starting time before accessing the channel.
If the starting time IE is present and the Channel Description IE does not indicate frequency hopping the mobile station
shall consider the frequency parameters, before time construction as unnecessary in the message and the mobile must
wait until the starting time before accessing the channel.
If the starting time IE is not present, the mobile station shall consider the frequency parameters, before time
construction as unnecessary in the message.
9.1.18.4 IA Rest Octets (assignment of uplink or downlink TBF)
If the Dedicated mode or TBF IE indicates that this message is used in an assignment of a TBF, this information element
shall contain a Packet Uplink Assignment, Packet Downlink Assignment or Second Part Packet Assignment
construction.
If the Dedicated mode or TBF IE indicates that this message assigns a dedicated mode resource, but not that the mobile
station is identified in the IA Rest Octets IE information element, the mobile station shall consider the Packet Uplink
ETSI
281 draft ETSI EN 300 940 V7.7.0 (2000-04)
Assignment, Packet Downlink Assignment and Second Part Packet Assignment constructions as unnecessary in the
message.
9.1.19 Immediate assignment extended
This message is sent on the CCCH by the network to two mobile stations in idle mode to change their channel
configurations to different dedicated configurations while they stay in the same cell. See table 9.19/GSM 04.08
IAX Rest Octets and L2 Pseudo Length information elements.
Message type: IMMEDIATE ASSIGNMENT EXTENDED
Significance: dual
ETSI
282 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.19/GSM 04.08: IMMEDIATE ASSIGNMENT EXTENDED message content
10.5.2.19
10.3.1
Immediate Assignment Ex Message Type M V 1
tended Message Type 10.4
10.5.2.26
Spare Half Octet Spare Half Octet M V 1/2
10.5.1.8
Channel Description 1 Channel Description M V 3
10.5.2.5
Request Reference 1 Request Reference M V 3
10.5.2.30
Timing Advance 1 Timing Advance M V 1
10.5.2.40
Channel Description 2 Channel Description M V 3
10.5.2.5
10.5.2.30
Timing Advance 2 Timing Advance M V 1
10.5.2.40
10.5.2.21
10.5.2.38
IAX Rest Octets IAX Rest Octets M V 0-4
10.5.2.18
NOTE: Index 1 refers to the first mobile station, index 2 refers to the second mobile station.
ETSI
283 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.19.1 Unnecessary IEs
A mobile station which reacts on the request reference 1 shall consider all information elements as unnecessary IEs
except for Requests Reference 1, Channel Description 1, Timing advance 1, Starting Time and if Channel Description 1
IE indicates frequency hopping mobile allocation.
A mobile station which reacts on the request reference 2 shall consider all information elements as unnecessary IE
except Requests Reference 2, Channel Description 2, Timing advance 2, Starting Time and if channel description 2 IE
indicates frequency hopping mobile allocation.
A mobile station in idle mode shall consider all information elements as unnecessary IEs except for the Page Mode IE.
If both channel description IE do not indicate frequency hopping, the length indicator shall be set to zero.
This information element appears if a frequency change is in progress. If included the starting time is common to the two
referenced mobile stations.
9.1.19.4 Maximum message length
As the maximum length of the resulting layer 3 data cannot exceed 22 octets, it is not possible to use this message type if
the total length of the value part of the Mobile Allocation plus, optionally, the length of the Starting Time IE exceeds 5
octets. In this case it is necessary to use the IMMEDIATE ASSIGNMENT message.
9.1.19.5 IAX Rest Octets
9.1.20 Immediate assignment reject
This message is sent on the CCCH by the network to up to four mobile stations to indicate that no channel is available
for assignment. See table 9.20/GSM 04.08. This message has L2 pseudo length 19.
Message type: IMMEDIATE ASSIGNMENT REJECT
Significance: dual
ETSI
284 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.20/GSM 04.08: IMMEDIATE ASSIGNMENT REJECT message content
10.5.2.19
10.3.1
Immediate Assignment Message Type M V 1
Reject Message Type 10.4
10.5.2.26
10.5.1.8
10.5.2.30
Wait Indication 1 Wait Indication M V 1
10.5.2.43
10.5.2.30
10.5.2.43
10.5.2.30
10.5.2.43
10.5.2.30
10.5.2.43
IAR Rest Octets IAR Rest Octets M V 3
10.5.2.17
NOTE: Index 1 refers to the first mobile station, index 2 refers to the second MS and so on.
9.1.20.1 Use of the indexes
A request reference information element and the following wait indication information element refer to the same mobile
station. So it is possible to reject up to four channel requests with this message.
ETSI
285 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.20.2 Filling of the message
If necessary the request reference information element and the wait indication information element should be duplicated
to fill the message.
9.1.20.3 Wait Indication
When IMMEDIATE ASSIGNMENT REJECT message is for RR connection establisment then this IE contains timeout
value for T3122. If IMMEDIATE ASSIGNMENT REJECT message is for TBF establisment for GPRS MS then this
IE contain timeout value for T3142.
9.1.20.4 IAR Rest Octets
9.1.21 Measurement report
This message is sent on the SACCH by the mobile station to the network to report measurement results about the
dedicated channel and about neighbour cells. See table 9.21/GSM 04.08.
Message type: MEASUREMENT REPORT
Significance: dual
ETSI
286 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.21/GSM 04.08: MEASUREMENT REPORT message content
10.3.1
Measurement Report Message Type M V 1
Message Type 10.4
Measurement Results Measurement Results M V 16
10.5.2.20
9.1.21a Notification/FACCH
The understanding of this message is only required for mobile stations supporting VGCS listening or VBS listening.
This message is sent on the main DCCH, in unacknowledged mode using the RR short protocol discriminator by the
network to notify the mobile stations in dedicated mode or in on-going voice broadcast calls or voice group calls on
other voice broadcast calls or voice group calls in that cell.
Notification/FACCH messages for VBS or VGCS calls are differentiated by a flag in the call reference.
The message shall not exceed a maximum length of 20 octets.
Mobile stations not supporting VGCS listening or VBS listening shall ignore this message.
See table 9.21a/GSM 04.08.
Message type: NOTIFICATION/FACCH
Significance: dual
Table 9.21a/GSM 04.08: NOTIFICATION/FACCH message content
<NOTIFICATION FACCH> ::= <RR short PD : bit> -- See GSM 04.07
<message type : bit(5)> -- See 10.4
<short layer 2 header : bit(2)> -- See GSM 04.06
{0 <Group Call information>
|1 <Paging Information>}
<spare padding> ;
<Group Call information> ::= <Group Call Reference : bit(36)>
{0|1 <Group Channel Description>} ;
<Group Call Reference>
This field is syntactically and semantically equivalent to octets 2-5 and bits 5 to 8 of octet 6 of the Descriptive Group or
Broadcast Call Reference information element.
The <Group Channel Description> field is optionally present. When present only the Channel description is provided in
the case of non hopping channels. In the case where the channel is hopping then either a mobile allocation or a
frequency short list is provided.
ETSI
287 draft ETSI EN 300 940 V7.7.0 (2000-04)
<Group Channel Description> : := <Channel Description : bit(24)>
{0 -- Non hopping case
|1 {0 <Mobile Allocation : <bit string>>
|1 <Frequency Short List : bit(64)>}} ;
<bit string> ::= null | bit <bit string> ;
<Channel Description>
This field is syntactically and semantically equivalent to octets 2-4 of the Channel Description information element. See
10.5.2.5
<Frequency Short List>
This field is syntactically and semantically equivalent to octets 1-8 of the Frequency Short List 2 information element.
See 10.5.2.14a
<Mobile Allocation>
This field is syntactically and semantically equivalent to octet 2 to n+2 of the Mobile Allocation information element.
See 10.5.2.21
The <Paging Information> field may be used to inform the mobile station in Group Receive or in Group Transmit mode
that the corresponding mobile identity is paged in that cell.
<Paging Information> ::= <mobile identity : <bit string>>
<channel first: bit(2)>
{0|1 <eMLPP priority : bit(3)>} ;
<bit string> ::= null | bit <bit string> ;
<mobile identity>
This field is syntactically and semantically equivalent to octet 2-n of the Mobile Identity information element. See
10.5.1.4
<channel first>
This field is syntactically and semantically equivalent to bits 1 and 2 of the Channel Needed information element. See
10.5.2.8
<eMLPP priority>
This field is coded as the <Priority1> field in the P1 Rest Octets information element. See 10.5.2.23
9.1.21a.1 Spare
9.1.21a.2 Spare
9.1.21a.3 Spare
9.1.21a.4 Spare
9.1.21b Notification/NCH
The understanding of this message is only required for mobile stations supporting VGCS listening or VBS listening.
ETSI
288 draft ETSI EN 300 940 V7.7.0 (2000-04)
This message is sent on the NCH by the network to notify mobile stations of VBS or VGCS calls in the current cell. The
VBS or VGCS calls are identified by their broadcast call reference or group call reference, respectively. For each
reference, the corresponding VBS or VGCS call channel may be indicated. See table 9.21b/GSM 04.08.
Notification/NCH messages for VBS or VGCS calls are differentiated by a flag in the call reference.
The L2 pseudo length of this message has a value one
Mobile stations not supporting VGCS listening or VBS listening shall ignore this message.
Message type: NOTIFICATION/NCH
Significance: dual
ETSI
289 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.21b/GSM 04.08: NOTIFICATION/NCH message content
10.5.2.19
10.3.1
Notification/NCH Message Type M V 1
Message Type 10.4
NT/N Rest Octets NT/N Rest Octets M V 1-20
10.5.2.22c
9.1.21b.1 Spare
9.1.21b.2 Spare
9.1.21d Notification response
This message is sent by the mobile station to the network to respond on a notification for a voice group call or voice
broadcast call. See table 9.21d/GSM 04.08.
Message type: NOTIFICATION RESPONSE
Significance: dual
Table 9.21d/GSM 04.08: NOTIFICATION RESPONSE message content
IEI Information element Type / Reference Presence Format Length
RR management Protocol discriminator M V 1/2
Protocol discriminator 10.2
10.3.1
Notification response Message type M V 1
Message type 10.4
Mobile station Mobile station M LV 4
Classmark classmark 2
10.5.1.6
Mobile identity Mobile identity M LV 2-9
10.5.1.4
Group or broadcast Call reference M V 5
ETSI
290 draft ETSI EN 300 940 V7.7.0 (2000-04)
Call reference 10.5.1.9
9.1.21e RR-Cell Change Order
This message is sent on the main DCCH by the network to the mobile station to order it to reselect a cell. See
table 9.21e/GSM 04.08.
A mobile station that does not support the <<GRPS>> option shall regard this message as an unknown message.
Message type: RR-CELL CHANGE ORDER
Significance: dual
Table 9.21e/GSM 04.08: RR-CELL CHANGE ORDER message content
10.3.1
Message Type M V 1
RR-Cell Change Order
Message Type 10.4
Cell Description Cell description M V 2
10.5.2.2
NC mode for target cell NC mode M V 1/2
10.5.2.21c
Spare half octet Spare half octet M V 1/2
10.5.1.8
9.1.22 Paging request type 1
This message is sent on the CCCH by the network to up to two mobile stations. It may be sent to a mobile station in idle
mode to trigger channel access. It may be sent to a mobile station in packet idle mode to transfer MM information (i.e.
trigger of cell update procedure). The mobile stations are identified by their TMSI/P-TMSI or IMSI. See
table 9.22/GSM 04.08.
P1 Rest Octets and L2 Pseudo Length information elements.
Message type: PAGING REQUEST TYPE 1
Significance: dual
ETSI
291 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.22/GSM 04.08: PAGING REQUEST TYPE 1 message content
10.5.2.19
10.3.1
Paging Request Type 1 Message Type M V 1
Message Type 10.4
10.5.2.26
Channels Needed for Channel Needed M V 1/2
Mobiles 1 and 2 10.5.2.8
Mobile Identity 1 Mobile Identity M LV 2-9
10.5.1.4
17 Mobile Identity 2 Mobile Identity O TLV 3-10
10.5.1.4
P1 Rest Octets P1 Rest Octets M V 0-17
10.5.2.23
9.1.22.1 Unnecessary IE
A mobile station in idle mode shall consider all information elements as unnecessary IEs except for the Page Mode IE.
9.1.22.2 Channels needed for Mobiles 1 and 2
The first CHANNEL field of Channel Needed IE is associated with Mobile Identity 1. The second CHANNEL field of
Channel Needed IE is associated with Mobile Identity 2.
If this message is used in the packet paging procedure, the Channel Needed IE associated with the corresponding Mobile
Identity 1 or 2 shall be coded with the value 00 (any channel) by the network. The mobile station receiving a packet
paging request shall treat this information element as unnecessary in the message.
9.1.22.3 Mobile Identities
The Mobile Identity 1 and 2 IEs shall not refer to IMEI.
9.1.22.4 P1 Rest Octets
This IE may contain a notification list number field and/or, referring to each one of the Mobile Identity 1 and 2 IEs, a
Priority 1 and 2 field and/or a Packet Page Indication 1 and 2 field.
ETSI
292 draft ETSI EN 300 940 V7.7.0 (2000-04)
This message is sent on the CCCH by the network to two or three mobile stations. It may be sent to a mobile station in
idle mode to trigger channel access. It may be sent to a mobile station in packet idle mode to transfer MM information
(i.e. trigger of cell update procedure). Two of the mobile stations are identified by their TMSI/P-TMSI while the third is
identified by its TMSI/P-TMSI or IMSI. See table 9.23/GSM 04.08.
P2 Rest Octets and L2 Pseudo Length information elements.
Significance: dual
10.5.2.19
10.3.1
Message Type 10.4
10.5.2.26
Mobile Identity 1 TMSI/P-TMSI M V 4
10.5.2.42
10.5.2.42
17 Mobile Identity 3 Mobile Identity O TLV 3-10
10.5.1.4
P2 Rest Octets P2 Rest Octets M V 1-11
10.5.2.24
ETSI
293 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.23.2 Mobile Identity 3
The Mobile Identity 3 information element shall not refer to IMEI.
This IE contains the channel needed indication related to the paging of Mobile Identity 3. The treatment of this
indication in the case this message is used in a packet paging procedure is specified in section 9.1.23.1.
This IE may further contain a notification list number field and/or, referring to each one of the Mobile Identity 1, 2 and
3 IEs, a Priority 1, 2 and 3 field and/or, referring to the Mobile Identity 3 IE, a Packet Page Indication 3 field.
This message is sent on the CCCH by the network to four mobile stations. It may be sent to a mobile station in idle mode
to trigger channel access. It may be sent to a mobile station in packet idle mode to transfer MM information (i.e. trigger
of cell update procedure). The mobile stations are identified by their TMSIs/P-TMSIs. See table 9.24/GSM 04.08.
This message has a L2 Pseudo Length of 19.
Significance: dual
ETSI
294 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.19
10.3.1
Message Type 10.4
10.5.2.26
10.5.2.42
10.5.2.42
10.5.2.42
10.5.2.42
P3 Rest Octets P3 Rest Octets M V 3
10.5.2.25
This IE contains the channel needed indication related to the paging of Mobile Identity 3 and 4. The treatment of these
indications in the case this message is used in a packet paging procedure is specified in section 9.1.24.1.
This IE may further contain a notification list number field and/or, referring to each one of the Mobile Identity 1, 2, 3
and 4 IEs, a Priority 1, 2, 3 and 4 field.
ETSI
295 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.25 Paging response
This message is sent on the main DCCH by the mobile station to the network in connection with establishment of the
main signalling link as a response to the paging request message. See table 9.25/GSM 04.08.
Message type: PAGING RESPONSE
Significance: dual
ETSI
296 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.25/GSM 04.08: PAGING RESPONSE message content
10.3.1
Paging Response Message Type M V 1
Message Type 10.4
Ciphering Key Sequence Ciphering Key Sequence M V 1/2
Number Number
10.5.1.2
10.5.1.8
10.5.1.6
Mobile Identity Mobile Identity M LV 2-9
10.5.1.4
This IE shall include for multiband mobile station the Classmark 2 corresponding to the frequency band in use.
9.1.26 Partial release
This message is sent on the main DCCH by the network to the mobile station to deactivate part of the dedicated channels
in use. See table 9.26/GSM 04.08.
Message type: PARTIAL RELEASE
Significance: dual
Table 9.26/GSM 04.08: PARTIAL RELEASE message content
10.3.1
Partial Release Message Type M V 1
Message Type 10.4
ETSI
297 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.5
This information element describes the channel to be released.
9.1.27 Partial release complete
This message is sent on the main DCCH by the mobile station to the network to indicate that a part of the dedicated
channels has been deactivated. See table 9.27/GSM 04.08.
Message type: PARTIAL RELEASE COMPLETE
Significance: dual
Table 9.27/GSM 04.08: PARTIAL RELEASE COMPLETE message content
10.3.1
Partial release Message Type M V 1
Complete Message Type 10.4
9.1.28 Physical information
This message is sent on the main DCCH by the network to the mobile station to stop the sending of access bursts from
the mobile station. See table 9.28/GSM 04.08.
Message type: PHYSICAL INFORMATION
Significance: dual
Table 9.28/GSM 04.08: PHYSICAL INFORMATION message content
10.3.1
Physical Information Message Type M V 1
Message Type 10.4
10.5.2.40
ETSI
298 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.28.a RR Initialisation Request
This message is sent on the main DCCH by the mobile station to request establishment of dedicated mode.
Message type: RR Initialisation Request
Significance: local
Table 9.28a/GSM 04.08: RR Initialisation Request message content
10.3.1
RR Initialisation Request Message Type M V 1
Message Type 10.4
Ciphering Key Sequence Ciphering Key sequence M V 1/2
Number Number
10.5.1.2
MAC Mode and Channel Channel Coding Requested M V 1/2
Coding Requested 10.5.2.4a
Mobile station classmark Mobile station classmark 2 M LV 4
10.5.1.6
TLLI TLLI M V 4
10.5.2.41a
Channel Request Description Channel Request Description M V 5
10.5.2.8a
GPRS Measurement Results GPRS Measurement Results M V 2
10.5.2.20a
9.1.29 RR Status
This message is sent by the mobile station or the network at any time to report certain error conditions as described in
section 8. See table 9.28a/GSM 04.08.
Message type: RR STATUS
Significance: local
Direction: both
Table 9.28a/GSM 04.08: RR STATUS message content
ETSI
299 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.3.1
RR Status Message Type M V 1
Message Type 10.4
10.5.2.31
9.1.30 Synchronization channel information
This message is sent on the SCH, which is one of the broadcast channels (ref. GSM 05.02 section 3.3.2). Its purpose is
to support the synchronization of a mobile station to a BSS. It does not follow the basic format. Its length is 25 bits. The
order of bit transmission is defined in GSM 04.04. See figure 9.3/GSM 04.08 and table 9.29/GSM 04.08.
Message type: SYNCHRONIZATION CHANNEL INFORMATION
Significance: dual
8 7 6 5 4 3 2 1
+-----------------------------------------------+
BSIC T1 (high) octet 1
+-----------------------------------------------
T1 (middle) octet 2
+-----------------------------------------------
T1 T2 T3' octet 3
(low) (high)
+-----------------------------------------------
T3'
(low)
+-----+
Figure 9.3/GSM 04.08: Frame synchronization information element
Table 9.29/GSM 04.08: Synchronization channel information message contents
+-------------------------------------------------------+
BSIC, the base station identity code of the base
station

T1, T2 and T3', the 3 parts of the reduced TDMA frame
number (RFN) as specified in TS. GSM05.02 section
3.3.2.
+-------------------------------------------------------+
9.1.31 System information Type 1
This message is sent on the BCCH by the network to all mobile stations within the cell giving information of control of
the RACH and of the cell allocation. See table 9.30/GSM 04.08. Special requirements for the transmission of this
message apply, see GSM 05.02. This message has a L2 Pseudo Length of 21.
Message type: SYSTEM INFORMATION TYPE 1
Significance: dual
ETSI
300 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.30/GSM 04.08: SYSTEM INFORMATION TYPE 1 message content
L2 pseudo length L2 pseudo length M V 1
10.5.2.19
10.3.1
System Information Message Type M V 1
Type 1 Message Type 10.4
Cell Channel Cell Channel Description M V 16
RACH Control Parameter RACH Control Parameters M V 3
10.5.2.29
SI 1 Rest Octets SI 1 Rest Octets M V 1
10.5.2.32
9.1.32 System information type 2
This message is sent on the BCCH by the network to all mobile stations within the cell giving information of control of
the RACH and of the BCCH allocation in the neighbour cells. See table 9.31/GSM 04.08. Special requirements for the
transmission of this message apply, see GSM 05.02. This message has a L2 Pseudo Length of 22.
Significance: dual
10.5.2.19
10.3.1
BCCH Frequency List Neighbour Cell Description M V 16
10.5.2.22
NCC Permitted NCC permitted M V 1
ETSI
301 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.27
RACH Control Parameter RACH Control Parameters
10.5.2.29 M V 3
9.1.33 System information type 2bis
This message is sent optionally on the BCCH by the network to all mobile stations within the cell giving information on
control of the RACH and of the extension of the BCCH allocation in the neighbour cells. See table 9.31a/GSM 04.08.
Special requirements for the transmission of this message apply, see GSM 05.02.
A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. GSM 05.05) may ignore this
message, see section 3.2.2.1.
This message has a L2 pseudo length of 21.
Message type: SYSTEM INFORMATION TYPE 2bis
Significance: dual
Table 9.31a/GSM 04.08: SYSTEM INFORMATION TYPE 2bis message content
10.5.2.19
10.3.1
Type 2bis Message Type 10.4
Extended BCCH Neighbour Cell M V 16
Frequency List Description
10.5.2.22
RACH Control Parameters RACH Control Parameters M V 3
10.5.2.29
SI 2bis Rest Octets SI 2bis Rest Octets M V 1
10.5.2.33
9.1.34 System information type 2ter
This message is sent optionally on the BCCH by the network to all mobile stations within the cell giving information on
the extension of the BCCH allocation in the neighbour cells. See table 9.31b/GSM 04.08. Special requirements for the
transmission of this message apply, see GSM 05.02.
A mobile station that supports either:
only the primary GSM band P-GSM 900 (cf. GSM 05.05), or
ETSI
302 draft ETSI EN 300 940 V7.7.0 (2000-04)
only the DCS 1800 band (cf. GSM 05.05)
may ignore this message, see section 3.2.2.1.
This message has a L2 pseudo length of 18. This message may be sent by the network with either a L2 pseudo length of
18 or some other value. A mobile station that does not ignore this message shall not discard the message due to a
received L2 pseudo length different from 18.
Message type: SYSTEM INFORMATION TYPE 2ter
Significance: dual
Table 9.31b/GSM 04.08: SYSTEM INFORMATION TYPE 2ter message content
10.5.2.19
10.3.1
Type 2ter Message Type 10.4
Frequency List Description 2
10.5.2.22a
SI 2ter Rest Octets SI 2ter Rest Octets M V 4
10.5.2.33a
This message is sent on the BCCH by the network giving information of control on the RACH, the location area
identification, the cell identity and various other information about the cell. See table 9.32/GSM 04.08. Special
requirements for the transmission of this message apply, see GSM 05.02. This message has a L2 Pseudo Length of 18.
Significance: dual
ETSI
303 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.19
10.3.1
Cell Identity Cell Identity M V 2
10.5.1.1
Location Area Location Area M V 5
Identification Identification
10.5.1.3
Control Channel Control Channel M V 3
Description description
10.5.2.11
Cell Options Cell Options (BCCH) M V 1
10.5.2.3
Cell Selection Cell Selection Parameters M V 2
Parameters 10.5.2.4
10.5.2.29
10.5.2.34
This message is sent on the BCCH by the network giving information on control of the RACH, the location area
identification, the cell identity and various other information about the cell. See table 9.33/GSM 04.08. Special
requirements for the transmission of this message apply, see GSM 05.02. The L2 pseudo length of this message is the
sum of lengths of all information elements present in the message except the SI 4 Rest Octets and L2 Pseudo Length
information elements.
Significance: dual
ETSI
304 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.19
10.3.1
Location Area Location Area M V 5
Identification Identification
10.5.1.3
Cell Selection Cell Selection Parameters M V 2
Parameters 10.5.2.4
10.5.2.29
64 CBCH Channel Channel description O TV 4
Description 10.5.2.5
72 CBCH Mobile Allocation Mobile Allocation C TLV 3-6
10.5.2.21
SI 4 Rest Octets SI 4 Rest Octets M V 0-10
10.5.2.35
9.1.36.1 CBCH Channel description
This information element is present if SMSCB is active in the cell and indicates (together with the CBCH Mobile
Allocation IE) where to find the CBCH.
9.1.36.2 CBCH Mobile Allocation
If the CBCH Channel Description Information Element indicates frequency hopping, the CBCH Mobile Allocation IE
shall be present. If the CBCH Channel Description does not indicate frequency hopping, the CBCH Mobile Allocation
IE shall be considered as an unnecessary IE in the message.
9.1.36.3 SI 4 Rest Octets
The sum of the length of this IE and the L2 pseudo length of the message equals 22.
This message is sent on the SACCH by the network to mobile stations within the cell giving information on the BCCH
allocation in the neighbour cells. See table 9.34/GSM 04.08.
When received this information shall be used as the list of BCCH frequencies of the neighbouring cells to be reported
on. Any change in the neighbour cells description must overwrite any old data held by the mobile station. The mobile
station must analyse all correctly received system information type 5 messages. This message has a L2 Pseudo Length of
18.
ETSI
305 draft ETSI EN 300 940 V7.7.0 (2000-04)
Significance: dual
10.5.2.19
10.3.1
BCCH Frequency List Neighbour Cell Description M V 16
10.5.2.22
9.1.38 System information type 5bis
This message is sent optionally on the SACCH by the network to mobile stations within the cell giving information on
the extension of the BCCH allocation in the neighbour cells. See table 9.34a/GSM 04.08.
A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. GSM 05.05) may ignore this
message, see section 3.2.2.1.
When received (and not ignored) this information must be used as the list of neighbouring cells to be reported on. Any
change in the neighbour cells description must overwrite any old data held by the mobile station. The mobile station
must, with the exception stated above, analyse all correctly received system information type 5 messages. This message
has a L2 Pseudo Length of 18.
Message type: SYSTEM INFORMATION TYPE 5bis
Significance: dual
Table 9.34a/GSM 04.08: SYSTEM INFORMATION TYPE 5bis message content
10.5.2.19
10.3.1
Type 5 bis Message Type 10.4
ETSI
306 draft ETSI EN 300 940 V7.7.0 (2000-04)
Extension of the Neighbour Cell M V 16
BCCH Frequency List Description
Description 10.5.2.22
9.1.39 System information type 5ter
This message is sent optionally on the SACCH by the network to mobile stations within the cell giving information on
the extension of the BCCH allocation in the neighbour cells. See table 9.34b/GSM 04.08.
A mobile station that supports either:
only the primary GSM band P-GSM 900 (cf. GSM 05.05), or
only the DCS 1800 band (cf. GSM 05.05)
may ignore this message, see section 3.2.2.1.
When received (and not ignored) this information must be used as part of the list of neighbouring cells to be reported on.
Any change in the neighbour cells description must overwrite this part of any old data held by the mobile station. The
mobile station shall, with the exception stated above, analyse all correctly received system information type 5ter
messages. This message has a L2 Pseudo Length of 18.
Message type: SYSTEM INFORMATION TYPE 5ter
Significance: dual
Table 9.34b/GSM 04.08: SYSTEM INFORMATION TYPE 5ter message content
10.5.2.19
10.3.1
Type 5ter Message Type 10.4
Frequency List Description 2
10.5.2.22a
This message is sent on the SACCH by the network to mobile stations within the cell giving information of location area
identification, of cell identity and various other information. See table 9.35/GSM 04.08. If received correctly by the
mobile station this message is treated as in Sections 9.1.40.1 to 9.1.40.4.
Significance: dual
ETSI
307 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.19
10.3.1
Cell Identity Cell Identity M V 2
10.5.1.1
Location Area Location Area Identification M V 5
Identification 10.5.1.3
Cell Options Cell Options (SACCH) M V 1
10.5.2.3
NCC Permitted NCC Permitted M V 1
10.5.2.27
SI 6 Rest Octets SI6 Rest Octets M V 7
10.5.2.35a
9.1.40.1 Cell Identity
Only applicable for mobile stations supporting SIM Application Toolkit class 2 or higher :
if a new Cell Identity is identified, an indication shall be given to the upper layer together with the new identity.
Other mobile stations may ignore this IE.
9.1.40.2 Location Area Identification
Only applicable for mobile stations supporting VGCS listening and VBS listening or SIM Application Toolkit class 2 or
higher :
if a new Location Area Identification is identified, an indication shall be given to the upper layer together with the
new identification.
Other mobile stations may ignore this IE.
9.1.40.3 Cell Options
When correctly received, this information shall be used as the current Cell Options information. Any change in the Cell
Options shall overwrite any old Cell Options data held by the mobile station.
ETSI
308 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.40.4 NCC permitted
As for BCCH Frequency List in SYSTEM INFORMATION TYPE 5.
This message is sent on the BCCH by the network giving information about cell reselection parameters to be used in that
cell. See table 9.36/GSM 04.08. Special requirements for the transmission of this message apply, see GSM 05.02. The
L2 pseudo length of this message has the value 1.
Significance: dual
10.5.2.19
10.3.1
10.5.2.36
This message is sent on the BCCH by the network giving information about cell reselection parameters to be used in that
cell. See table 9.37/GSM 04.08. Special requirements for the transmission of this message apply, see GSM 05.02. The
L2 Pseudo Length of this message has the value 1.
Significance: dual
10.5.2.19
ETSI
309 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.3.1
10.5.2.37
9.1.43 System information Type 9
This message is sent on the BCCH by the network to all mobile stations within the cell giving some, but not necessarily
all information on the scheduling of information on the BCCH. See table 9.37a/GSM 04.08. Special requirements for the
transmission of this message apply, see subclause 3.2.2.1 and GSM 05.02. This message has a L2 Pseudo Length of 1.
Significance: dual
Table 9.37a/GSM 04.08: SYSTEM INFORMATION TYPE 9 message content
10.5.2.19
10.3.1
RACH Control Parameter RACH Control Parameters M V 3
10.5.2.29
10.5.2.37a
9.1.43a System information Type 13
This message is sent on the BCCH if indicated in at least one of the SYSTEM INFORMATION TYPE 3, 4, 7 or 8
messages. The message is sent by the network to provide information related to GPRS in the cell. See table
9.37b/GSM04.08. Special requirements for the transmission of this message apply, see GSM 05.02.
A mobile station not supporting GPRS shall treat this message as an unknown message type.
The L2 Pseudo Length of this message has the value 0.
Significance: dual
ETSI
310 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.37b/GSM 04.08: SYSTEM INFORMATION TYPE 13 message content
10.5.2.19
10.3.1
10.5.2.37b
ETSI
306 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.43b [Spare]
ETSI
307 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.1.43c [Spare]
9.1.43d System information type 16
This message is sent on the BCCH if indicated in the SYSTEM INFORMATION TYPE 3 message. The message is sent
by the network giving information about cell selection and reselection parameters to be used in that cell. See
table 9.37e/GSM 04.08. Special requirements for the transmission of this message applies, see GSM 05.02.
The L2 pseudo length of this message has the value 1.
Significance: dual
Table 9.37e/GSM 04.08: SYSTEM INFORMATION TYPE 16 message content
10.5.2.19
10.3.1
10.5.2.37e
9.1.43e System information type 17
This message is sent on the BCCH if indicated in the SYSTEM INFORMATION TYPE 3 message. The message is sent
by the network giving information about cell selection and reselection parameters to be used in that cell. See
table 9.37f/GSM 04.08. Special requirements for the transmission of this message applies, see GSM 05.02.
The L2 pseudo length of this message has the value 1.
Significance: dual
Table 9.37f/GSM 04.08: SYSTEM INFORMATION TYPE 17 message content
10.5.2.19
10.3.1
10.5.2.37f
9.1.44 Talker indication
This message is sent on the main DCCH by the mobile station to the network to give the talker information when a new
layer 2 connection is established on a VGCS channel after an uplink access. See table 9.44/GSM 04.08.
Message type: TALKER INDICATION
Significance: dual
Table 9.44/GSM 04.08: TALKER INDICATION message content
10.3.1
Talker Indication Message Type M V 1
Message Type 10.4
10.5.1.6
Mobile Identity Mobile Identity M LV 2-9
10.5.1.4
9.1.45 Uplink access
This message is sent in random mode on the voice group call channel uplink. It does not follow the basic format. The
possible formats are presented directly below, without reference to information fields. The order of bit transmission is
The message is only one octet long, coded as shown in figure 9.4/GSM 04.08 and table 9.45/GSM 04.08.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
ESTABLISHMENT RANDOM REFERENCE
+ - - - - - - - - - - - - - - octet1
CAUSE
+-----------------------------------------------+
Figure 9.4/GSM 04.08: UPLINK ACCESS message content
ESTABLISHMENT CAUSE (octet 1)
This information field indicates the reason for requesting the establishment of a connection. This field has a variable
length (from 3 bits up to 8 bits).
RANDOM REFERENCE (octet 1)
This is an unformatted field with variable length (from 5 bits down to 0 bits).
The Channel Request message is coded as follows:
(Random Reference field is filled with "x").
ETSI
309 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.45/GSM 04.08: UPLINK ACCESS message content
Message Meaning of Establishment Cause
8 . . . . . . 1
110xxxxx Subsequent talker uplink request
00100101 Reply on uplink access request
other values reserved for future use
9.1.46 Uplink busy
The understanding of this message is only required for mobile stations supporting VGCS talking.
This message is broadcasted on the voice group call channel on the main DCCH, SAPI=0, by the network in
unacknowledged mode to inform the mobile station of the uplink status of the voice group call channel. See
table 9.46/GSM 04.08.
Message type: UPLINK BUSY
Significance: dual
Table 9.46/GSM 04.08: UPLINK BUSY message content
10.3.1
Uplink busy Message Type M V 1
Message Type 10.4
9.1.47 Uplink free
This message is sent on the main DCCH, in unacknowledged mode using the RR short protocol discriminator by the
network to inform the mobile station of the uplink status of the voice group call channel. See table 9.47/GSM 04.08. The
message indicates the uplink as free unless the Uplink Access Request field indicates the uplink as not free.
This message may also be used by the network to request the mobile station to perform an uplink reply procedure.
Message type: UPLINK FREE
Significance: dual
Table 9.47/GSM 04.08: UPLINK FREE message content
<UPLINK FREE> ::= <RR short PD : bit> See GSM 04.07
<message type : bit(5)> See 10.4
<short layer 2 header : bit(2) See GSM 04.06
<Uplink Access Request bit>
ETSI
310 draft ETSI EN 300 940 V7.7.0 (2000-04)
{L|H <Uplink Identity Code bit(6)>}
<implicit spare> ;
Uplink Access Request :
L Mobile station shall not perform the uplink reply procedure;
H Mobile station shall perform the uplink reply procedure.
When set to H, this element also indicates the uplink as not free for the uplink access procedure
Uplink Identity Code :
This field is coded as the binary representation of the UIC.
If provided by the network, the Uplink Identity Code shall be used by the mobile for the coding of the UPLINK
ACCESS message
9.1.48 Uplink release
This message is sent on the uplink of the voice group call channel to initiate a deactivation of the group transmit mode
and to set the uplink free or on the downlink of the voice group call channel in order to reject an uplink access which
was already granted by the network. See table 9.48/GSM 04.08
Message type: UPLINK RELEASE
Significance: local
Direction: both
Table 9.48/GSM 04.08: UPLINK RELEASE message content
10.3.1
Uplink Release Message Type M V 1
Message Type 10.4
10.5.2.31
9.1.49 VGCS uplink grant
The understanding of this message is only required for mobile stations supporting VGCS talking.
This message is sent in unacknowledged mode on the main signalling channel by the network to the mobile station to
stop the sending of access bursts from the mobile station and to change the channel configuration to a dedicated
configuration. See table 9.49/GSM 04.08.
Message type: VGCS UPLINK GRANT
Significance: dual
ETSI
311 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.49/GSM 04.08: VGCS UPLINK GRANT message content
10.3.1
VGCS Uplink Grant Message Type M V 1
Message Type 10.4
Request Reference Request Reference M V 3
10.5.2.30
10.5.2.40
9.1.50 System information type 10 $(ASCI)$
The understanding of messages of this message type is only required for mobile stations supporting VGCS listening and
VBS listening. A mobile station not understanding the message shall treat it as unknown message.
Messages of this message type are optionally sent by the network in unacknowledged mode on the SACCH. SYSTEM
INFORMATION TYPE 10 messages contain information about neighbour cells. When sent on the SACCH of a VGCS
or VBS downlink, SYSTEM INFORMATION TYPE 10 messages address all mobile stations receiving that downlink
within the cell. There may be different SYSTEM INFORMATION TYPE 10 messages sent on the same SACCH.
They are not standard layer 3 messages. They shall be transferred using the short header format for SACCH messages
sent in unacknowledged mode specified in GSM 04.07.
Each SYSTEM INFORMATION TYPE 10 message defines a list of cells and may contain further information for cells
of that list, a cell being identified by the pair of ARFCN and BSIC of the BCCH. Newer information about a cell
received in SYSTEM INFORMATION TYPE 10 messages shall replace older information.
Significance: dual
<SYSTEM INFORMATION TYPE 10> ::=

<RR short PD : bit> -- See GSM 04.07
<message type : bit(5)> -- See 10.4
<short layer 2 header : bit(2)> -- See GSM 04.06
<SI10 Rest Octets : bit(160)>; -- See 10.5.2.44
9.1.51 EXTENDED MEASUREMENT ORDER
This message is sent on the SACCH by the network to the mobile station, to order the mobile station to send one
extended measurement report. See table 9.1.51.1/GSM 04.08.
A mobile station which does not support Extended Measurements shall discard this message.
Message type: EXTENDED MEASUREMENT ORDER
Significance: dual
ETSI
312 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.1.51.1/GSM 04.08: EXTENDED MEASUREMENT ORDER message content
10.5.2.19
10.3.1
Extended Measurement Message Type M V 1
Order 10.4
Extended Measurement Extended Measurement M V 16
Frequency List Frequency List
10.5.2.46
9.1.52 Extended measurement report
This message is sent on the SACCH by the mobile station to the network to report extended measurement results about
the signal strength on specified carriers. See table 9.1.52.1/GSM 04.08.
Message type: EXTENDED MEASUREMENT REPORT
Significance: dual
Table 9.1.52.1/GSM 04.08: EXTENDED MEASUREMENT REPORT message content
10.3.1
Extended Measurement Report Message Type M V 1
Message Type 10.4
Extended Measurement Extended Measurement M V 16
Results Results
10.5.2.45
9.1.53 Application Information
This message is sent on the main DCCH by the network or the mobile station to convey an embedded Application
Protocol Data Unit (APDU) or APDU segment between the network and the mobile station. See
table 9.1.53.1/GSM 04.08.
Message type: Application
ETSI
313 draft ETSI EN 300 940 V7.7.0 (2000-04)
Significance: global
Direction: both
Table 9.1.53.1/GSM 04.08: Application Information message content
IEI Information Element Type/Reference Presence Format Length
RR management Protocol
Discriminator
Protocol discriminator
10.2
M V 1/2
Skip Indicator Skip Indicator
10.3.1
M V 1/2
Application Information message
type
Message type
10.4
M V 1
APDU ID APDU ID
0.5.2.48
M V 1/2
APDU Flags APDU Flags
10.5.2.49
M V 1/2
APDU Data APDU Data
10.5.2.50
M LV 2 to N
9.2 Messages for mobility management
Table 9.2.1/GSM 04.08 summarizes the messages for mobility management.
Table 9.2.1/GSM 04.08: 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 REQUEST 9.2.15
Security messages: Reference
AUTHENTICATION REJECT 9.2.1
AUTHENTICATION REQUEST 9.2.2
AUTHENTICATION RESPONSE 9.2.3
IDENTITY REQUEST 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 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/GSM 04.08.
Message type: AUTHENTICATION REJECT
Significance: dual
ETSI
314 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.2.2/GSM 04.08: AUTHENTICATION REJECT message content
Mobility management Protocol discriminator M V 1/2
protocol discriminator 10.2
10.3.1
Authentication Reject Message type M V 1
message type 10.4
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/GSM 04.08.
Message type: AUTHENTICATION REQUEST
Significance: dual
Table 9.2.3/GSM 04.08: AUTHENTICATION REQUEST message content
10.3.1
Authentication Request Message type M V 1
message type 10.4
Ciphering key sequence Ciphering key sequence M V 1/2
number number
10.5.1.2
10.5.1.8
Authentication Auth. parameter RAND M V 16
parameter RAND 10.5.3.1
9.2.3 Authentication 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/GSM 04.08.
Message type: AUTHENTICATION RESPONSE
Significance: dual
ETSI
315 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.2.4/GSM 04.08: AUTHENTICATION RESPONSE message content
10.3.1
Authentication Response Message type M V 1
message type 10.4
Authentication Auth. parameter SRES M V 4
parameter SRES 10.5.3.2
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/GSM 04.08.
Message type: CM RE-ESTABLISHMENT REQUEST
Significance: dual
Table 9.2.5/GSM 04.08: CM RE-ESTABLISHMENT REQUEST message content
10.3.1
CM Re-Establishment Message type M V 1
Request message type 10.4
number number
10.5.1.2
10.5.1.8
classmark classmark 2
10.5.1.6
10.5.1.4
13 Location area Location area C TV 6
ETSI
316 draft ETSI EN 300 940 V7.7.0 (2000-04)
identification identification
10.5.1.3
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.
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/GSM 04.08.
Message type: CM SERVICE ACCEPT
Significance: dual
Table 9.2.6/GSM 04.08: CM SERVICE ACCEPT message content
10.3.1
CM Service Accept Message type M V 1
message type 10.4
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/GSM 04.08.
Message type: CM SERVICE PROMPT
Significance: dual
Table 9.2.7/GSM 04.08: CM SERVICE PROMPT message content
ETSI
317 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.3.1
CM Service Prompt Message type M V 1
message type 10.4
PD and SAPI of CM PD and SAPI M V 1
10.5.1.10a
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/GSM 04.08.
Message type: CM SERVICE REJECT
Significance: dual
Table 9.2.8/GSM 04.08: CM SERVICE REJECT message content
10.3.1
CM Service Reject Message type M V 1
message type 10.4
Reject cause Reject cause M V 1
10.5.3.6
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/GSM 04.08.
Message type: CM SERVICE ABORT
Significance: dual
Table 9.2.9/GSM 04.08: CM SERVICE ABORT message content
10.3.1
CM Service Abort Message type M V 1
message type 10.4
ETSI
318 draft ETSI EN 300 940 V7.7.0 (2000-04)
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/GSM 04.08.
Message type: ABORT
Significance: dual
Table 9.2.10/GSM 04.08: ABORT message content
10.3.1
Abort Message type M V 1
message type 10.4
10.5.3.6
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/GSM 04.08.
Message type: CM SERVICE REQUEST
Significance: dual
ETSI
319 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.2.11/GSM 04.08: CM SERVICE REQUEST message content
10.3.1
CM Service Request Message type M V 1
message type 10.4
CM service type CM service type M V 1/2
10.5.3.3
number number
10.5.1.2
10.5.1.6
10.5.1.4
8- Priority Priority Level O TV 1
10.5.1.11
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/GSM 04.08.
Message type: IDENTITY REQUEST
Significance: dual
ETSI
320 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.2.12/GSM 04.08: IDENTITY REQUEST message content
10.3.1
Identity Request Message type M V 1
message type 10.4
Identity type Identity type M V 1/2
10.5.3.4
10.5.1.8
9.2.11 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/GSM 04.08.
Message type: IDENTITY RESPONSE
Significance: dual
Table 9.2.13/GSM 04.08: IDENTITY RESPONSE message content
10.3.1
Identity Response Message type M V 1
message type 10.4
10.5.1.4
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/GSM 04.08.
Message type: IMSI DETACH INDICATION
Significance: dual
ETSI
321 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.2.14/GSM 04.08: IMSI DETACH INDICATION message content
10.3.1
IMSI Detach Indication Message type M V 1
message type 10.4
Mobile station Mobile station M V 1
10.5.1.5
10.5.1.4
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/GSM 04.08.
Message type: LOCATION UPDATING ACCEPT
Significance: dual
Table 9.2.15/GSM 04.08: LOCATION UPDATING ACCEPT message content
10.3.1
Location Updating Message type M V 1
Accept message type 10.4
Location area Location area M V 5
10.5.1.3
17 Mobile identity Mobile identity O TLV 3-10
10.5.1.4
A1 Follow on proceed Follow on proceed O T 1
ETSI
322 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.3.7
A2 CTS permission CTS permission O T 1
10.5.3.10
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.
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.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/GSM 04.08.
Message type: LOCATION UPDATING REJECT
Significance: dual
Table 9.2.16/GSM 04.08: LOCATION UPDATING REJECT message content
10.3.1
Reject message type 10.4
10.5.3.6
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/GSM 04.08.
Message type: LOCATION UPDATING REQUEST
Significance: dual
Table 9.2.17/GSM 04.08: LOCATION UPDATING REQUEST message content
ETSI
323 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.3.1
Request message type 10.4
Location updating type Location updating type M V 1/2
10.5.3.5
number number
10.5.1.2
10.5.1.3
Mobile station Mobile station M V 1
10.5.1.5
10.5.1.4
9.2.15.1 Location area identification
The location area identification stored in the SIM is used.
This IE shall include for multiband MS the Classmark 1 corresponding to the frequency band in use.
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/GSM 04.08.
Message type: MM INFORMATION
Significance: dual
Table 9.2.18/GSM 04.08 MM INFORMATION message content
10.3.1
MM Information Message type M V 1
message type 10.4
ETSI
324 draft ETSI EN 300 940 V7.7.0 (2000-04)
43 Full name for network Network Name O TLV 3-?
10.5.3.5a
45 Short name for network Network Name O TLV 3-?
10.5.3.5a
46 Universal time zone Time Zone O TV 2
10.5.3.8
47 Network time and time zone Time Zone and Time O TV 8
10.5.3.9
48 LSA Identity LSA Identifier
10.5.3.11
O TLV 2-5
9.2.15a.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.15a.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.15a.3 Network 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.
9.2.15a.4 Universal time and 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.
9.2.15a.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.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 section
8. See table 9.2.19/GSM 04.08.
Message type: MM STATUS
Significance: local
Direction: both
Table 9.2.19/GSM 04.08: MM STATUS message content
ETSI
325 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.3.1
MM Status message Message type M V 1
type 10.4
10.5.3.6
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/GSM 04.08.
Message type: TMSI REALLOCATION COMMAND
Significance: dual
Table 9.2.20/GSM 04.08: TMSI REALLOCATION COMMAND message content
10.3.1
TMSI Reallocation Message type M V 1
Command message type 10.4
10.5.1.3
10.5.1.4
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/GSM 04.08.
Message type: TMSI REALLOCATION COMPLETE
Significance: dual
Table 9.2.21/GSM 04.08: TMSI REALLOCATION COMPLETE message content
ETSI
326 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.3.1
TMSI Reallocation Message type M V 1
Complete message type 10.4
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/GSM 04.08: MM NULL message content
10.3.1
MM Null message Message type M V 1
type 10.4
9.3 Messages for circuit-switched call control
Table 9.54/GSM 04.08 summarizes the messages for circuit-switched call control.
ETSI
327 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.54/GSM 04.08: 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
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
RELEASE COMPLETE 9.3.19
Messages for supplementary service control Reference
FACILITY 9.3.9
HOLD 1) 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 ENQUIRY 9.3.28
STOP DTMF 1) 9.3.29
STOP DTMF ACKNOWLEDGE 1) 9.3.30
NOTE: Not supported by Blue Book CCITT Rec. Q.931.
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/GSM 04.08.
Message type: ALERTING
Table 9.55/GSM 04.08: ALERTING message content (network to mobile station direction)
Call control Protocol discriminator M V 1/2
ETSI
328 draft ETSI EN 300 940 V7.7.0 (2000-04)
Transaction identifier Transaction identifier M V 1/2
10.3.2
Alerting Message type M V 1
message type 10.4
1C Facility Facility O TLV 2-?
10.5.4.15
1E Progress indicator Progress indicator O TLV 4
10.5.4.21
7E User-user User-user O TLV 3-131
10.5.4.25
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.
Message type: ALERTING
Table 9.55a/GSM 04.08: ALERTING message content (mobile station to network direction)
10.3.2
Alerting Message type M V 1
ETSI
329 draft ETSI EN 300 940 V7.7.0 (2000-04)
message type 10.4
10.5.4.15
10.5.4.25
7F SS version SS version indicator O TLV 2-3
10.5.4.24
9.3.1.2.1 Facility
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 GSM 04.10. This information element should not
be transmitted unless explicitly required by GSM 04.10.
9.3.2 Call confirmed
This message is sent by the called mobile station to confirm an incoming call request.
Message type: CALL CONFIRMED
Significance: local
Table 9.56/GSM 04.08: CALL CONFIRMED message content
10.3.2
Call confirmed Message type M V 1
message type 10.4
D- Repeat Indicator Repeat Indicator C TV 1
10.5.4.22
04 Bearer capability 1 Bearer capability O TLV 3-15
10.5.4.5
ETSI
330 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.4.5
08 Cause Cause O TLV 4-32
10.5.4.11
15 CC Capabilities Call Control Capabilities O TLV 3
10.5.4.5a
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 five 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 other speech versions than GSM 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 GSM 07.01, 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 section 10.5.4.22) in cases identified in GSM 07.01.
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.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.
Message type: CALL PROCEEDING
Significance: local
ETSI
331 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.57/GSM 04.08: CALL PROCEEDING message content
10.3.2
Call proceeding Message type M V 1
message type 10.4
10.5.4.22
10.5.4.5
10.5.4.5
10.5.4.15
10.5.4.21
8- Priority granted Priority Level O TV 1
10.5.1.11
This information element is included if and only if bearer capability 1 IE and bearer capability 2 IE are both contained
in the message.
9.3.3.2 Bearer capability 1 and bearer capability 2
The bearer capability 1 information element is included if the network has to specify at least one of the negotiable
parameters described in GSM 07.01, 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 GSM 07.01, if
either bearer capability needs to be included, both shall be included.
9.3.3.3 Facility
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
ETSI
332 draft ETSI EN 300 940 V7.7.0 (2000-04)
- 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 used and the priority assigned by the network is
not the same as that requested by the mobile station.
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.
Message type: CONGESTION CONTROL
Significance: local (note)
Table 9.58/GSM 04.08: CONGESTION CONTROL message content
10.3.2
Congestion control Message type M V 1
message type 10.4
Congestion level Congestion level M V 1/2
10.5.4.12
10.5.1.8
10.5.4.11
NOTE: This message has local significance, but may carry information of global significance.
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.
Message type: CONNECT
ETSI
333 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.59/GSM 04.08: CONNECT message content(network to mobile station direction)
10.3.2
Connect Message type M V 1
message type 10.4
10.5.4.15
10.5.4.21
4C Connected number Connected number O TLV 3-14
10.5.4.13
4D Connected subaddress Connected subaddress O TLV 2-23
10.5.4.14
10.5.4.25
9.3.5.1.1 Facility
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
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.
Message type: CONNECT
ETSI
334 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.59a/GSM 04.08: CONNECT message content (mobile station to network direction)
10.3.2
Connect Message type M V 1
message type 10.4
10.5.4.15
4D Connected subaddress Connected subaddress O TLV 2-23
10.5.4.14
10.5.4.25
10.5.4.24
9.3.5.2.1 Facility
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.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.
Message type: CONNECT ACKNOWLEDGE
Significance: local
Direction: both
ETSI
335 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.60/GSM 04.08: CONNECT ACKNOWLEDGE message content
10.3.2
Connect acknowledge Message type M V 1
message type 10.4
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.
Message type: DISCONNECT
Table 9.61/GSM 04.08: DISCONNECT message content (network to mobile station direction)
10.3.2
Disconnect Message type M V 1
message type 10.4
Cause Cause M LV 3-31
10.5.4.11
10.5.4.15
10.5.4.21
10.5.4.25
7B Allowed actions $(CCBS)$ Allowed actions O TLV 3
10.5.4.26
9.3.7.1.1 Facility
This information element may be used for functional operation of supplementary services, such as the user-user service.
ETSI
336 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 section 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.
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.
Message type: DISCONNECT
Table 9.61a/GSM 04.08: DISCONNECT message content (mobile station to network direction)
10.3.2
Disconnect Message type M V 1
message type 10.4
10.5.4.11
10.5.4.15
10.5.4.25
10.5.4.24
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.
ETSI
337 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.3.8 Emergency setup
This message is sent from the mobile station to initiate emergency call establishment.
Message type: EMERGENCY SETUP
Table 9.62/GSM 04.08: EMERGENCY SETUP message content
10.3.2
Emergency setup Message type M V 1
message type 10.4
04 Bearer capability Bearer capability O TLV 3-9
10.5.4.5
9.3.8.1 Bearer capability
If the element is not included, the network shall by default assume speech and select full rate speech version 1. 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.
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.
Message type: FACILITY
Significance: local (NOTE 1)
Table 9.62a/GSM 04.08: FACILITY message content (network to mobile station direction)
ETSI
338 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.3.2
Facility Message type M V 1
message type 10.4
Facility (note 2) Facility M LV 1-?
10.5.4.15
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 GSM 04.06.
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/GSM 04.08.
Message type: FACILITY
Significance: local (note 1)
Table 9.62b/GSM 04.08: FACILITY message content (mobile station to network direction)
10.3.2
Facility Message type M V 1
message type 10.4
Facility (note 2) Facility M LV 1-?
10.5.4.15
10.5.4.24
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 GSM 04.06.
ETSI
339 draft ETSI EN 300 940 V7.7.0 (2000-04)
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/GSM 04.08 for the content of the HOLD message.
For the use of this message, see GSM 04.10.
Message type: HOLD
Significance: local
Table 9.62c/GSM 04.08: HOLD message content
10.3.2
Hold Message type M V 1
message type 10.4
9.3.11 Hold Acknowledge
This message is sent by the network to indicate that the hold function has been successfully performed.
See table 9.62d/GSM 04.08 for the content of the HOLD ACKNOWLEDGE message.
Message type: HOLD ACKNOWLEDGE
Significance: local
Table 9.62d/GSM 04.08: HOLD ACKNOWLEDGE message content
10.3.2
Hold Acknowledge Message type M V 1
message type 10.4
ETSI
340 draft ETSI EN 300 940 V7.7.0 (2000-04)
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/GSM 04.08 for the content of the HOLD REJECT message.
Message type: HOLD REJECT
Significance: local
Table 9.62e/GSM 04.08: HOLD REJECT message content
10.3.2
Hold Reject Message type M V 1
message type 10.4
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.
Message type: MODIFY
Direction: both
Table 9.63/GSM 04.08: MODIFY message content
10.3.2
Modify Message type M V 1
message type 10.4
Bearer capability Bearer capability M LV 2-14
10.5.4.5
7C Low layer comp. Low layer comp. O TLV 2-15
10.5.4.18
ETSI
341 draft ETSI EN 300 940 V7.7.0 (2000-04)
7D High layer comp. High layer comp. O TLV 2-5
10.5.4.16
A3 Reverse call setup Reverse call setup O T 1
direction direction
10.5.4.22a
9.3.13.1 Low layer compatibility
This information element shall be included if it was included in the initial SETUP message.
9.3.13.2 High layer compatibility
9.3.13.3 Reverse call setup direction
This information element is included or omitted in the mobile to network direction according to the rules defined in
section 5.3.4.3.1.
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.
Message type: MODIFY COMPLETE
Direction: both
Table 9.64/GSM 04.08: MODIFY COMPLETE message content
10.3.2
Modify complete Message type M V 1
message type 10.4
10.5.4.5
10.5.4.18
10.5.4.16
A3 Reverse call setup Reverse call setup O T 1
ETSI
342 draft ETSI EN 300 940 V7.7.0 (2000-04)
direction direction
10.5.4.22a
9.3.14.3 Reverse call setup direction
This information element is included or omitted according to the rules defined in section 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.
Message type: MODIFY REJECT
Direction: both
Table 9.65/GSM 04.08: MODIFY REJECT message content
10.3.2
Modify reject Message type M V 1
message type 10.4
10.5.4.5
10.5.4.11
10.5.4.18
10.5.4.16
ETSI
343 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
Message type: NOTIFY
Significance: access
Direction: both
Table 9.66/GSM 04.08: NOTIFY message content
10.3.2
Notify Message type M V 1
message type 10.4
Notification indicator Notification indicator M V 1
10.5.4.20
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.
Message type: PROGRESS
Table 9.67/GSM 04.08: PROGRESS message content
10.3.2
Progress Message type M V 1
message type 10.4
ETSI
344 draft ETSI EN 300 940 V7.7.0 (2000-04)
Progress indicator Progress indicator M LV 3
10.5.4.21
10.5.4.25
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)$
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/GSM 04.08.
Message type: CC-ESTABLISHMENT
Significance: local
Table 9.67a/GSM 04.08: CC-Establishment message content
10.3.2
CC-Establishment Message type M V 1
message type 10.4
Setup container Container M LV 3-n
10.5.4.22a
* 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.
9.3.17a.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
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.
ETSI
345 draft ETSI EN 300 940 V7.7.0 (2000-04)
See Table 9.67b/GSM 04.08.
Message type: CC-ESTABLISHMENT CONFIRMED
Significance: local
Table 9.67b/GSM 04.08: CC-ESTABLISHMENT CONFIRMED message content
10.3.2
CC-Establishment
confirmed Message type M V 1
message type 10.4
10.5.4.22
04 Bearer capability 1 Bearer capability M TLV 3-10
10.5.4.5
10.5.4.5
10.5.4.11
9.3.17b.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.17b.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.17b.9 Cause
This information element is included if the mobile station is compatible but the user is busy.
9.3.18 Release
9.3.18.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.
ETSI
346 draft ETSI EN 300 940 V7.7.0 (2000-04)
Message type: RELEASE
Table 9.68/GSM 04.08: RELEASE message content (network to mobile station direction)
10.3.2
Release Message type M V 1
message type 10.4
10.5.4.11
08 Second cause Cause O TLV 4-32
10.5.4.11
10.5.4.15
10.5.4.25
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 section 5.4.4.1.2.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.18.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.
ETSI
347 draft ETSI EN 300 940 V7.7.0 (2000-04)
Message type: RELEASE
Direction: mobile station to network direction
Table 9.68a/GSM 04.08: RELEASE message content (mobile station to network direction)
10.3.2
Release Message type M V 1
message type 10.4
10.5.4.11
08 Second cause Cause O TLV 4-32
10.5.4.11
10.5.4.15
10.5.4.25
10.5.4.24
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 section 5.4.3.5 "Abnormal cases" (Clearing
initiated by the mobile station).
9.3.18.2.3 Facility
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.
ETSI
348 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.3.18a Recall $(CCBS)$
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.
Message type: RECALL
Significance: local
Table 9.68b/GSM 04.08: Recall message content
10.3.2
Recall Message type M V 1
message type 10.4
Recall Type Recall Type M V 1
10.5.4.21a
Facility Facility M LV 2-n
10.5.4.15
9.3.18a.1 Recall Type
The purpose of the recall type information element is to describe the reason for the recall.
9.3.18a.2 Facility
The information element shall be included for functional operation of supplementary services.
9.3.19 Release complete
9.3.19.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.
ETSI
349 draft ETSI EN 300 940 V7.7.0 (2000-04)
Message type: RELEASE COMPLETE
Direction: network to mobile station direction
Table 9.69/GSM 04.08: RELEASE COMPLETE message content (network to mobile station direction)
10.3.2
Release complete Message type M V 1
message type 10.4
10.5.4.11
10.5.4.15
10.5.4.25
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 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.19.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.
Message type: RELEASE COMPLETE
Direction: mobile station to network direction
ETSI
350 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.69a/GSM 04.08: RELEASE COMPLETE message content (mobile station to network direction)
10.3.2
Release complete Message type M V 1
message type 10.4
10.5.4.11
10.5.4.15
10.5.4.25
10.5.4.24
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 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.
9.3.20 Retrieve
This message is sent by the mobile user to request the retrieval of a held call.
See table 9.69b/GSM 04.08 for the content of the RETRIEVE message.
Message type: RETRIEVE
ETSI
351 draft ETSI EN 300 940 V7.7.0 (2000-04)
Significance: local
Table 9.69b/GSM 04.08: RETRIEVE message content
10.3.2
Retrieve Message type M V 1
message type 10.4
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/GSM 04.08 for the content of the RETRIEVE ACKNOWLEDGE message.
Message type: RETRIEVE ACKNOWLEDGE
Significance: local
Table 9.69c/GSM 04.08: RETRIEVE ACKNOWLEDGE message content
10.3.2
Retrieve Acknowledge Message type M V 1
message type 10.4
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/GSM 04.08 for the content of the RETRIEVE REJECT message.
Message type: RETRIEVE REJECT
Significance: local
ETSI
352 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.69d/GSM 04.08: RETRIEVE REJECT message content
10.3.2
Retrieve Reject Message type M V 1
message type 10.4
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.
Message type: SETUP
Table 9.70/GSM 04.08: SETUP message content (network to mobile station direction)
10.3.2
Setup Message type M V 1
message type 10.4
D- BC repeat indicator Repeat indicator C TV 1
10.5.4.22
10.5.4.5
10.5.4.5
10.5.4.15
10.5.4.21
34 Signal Signal O TV 2
ETSI
353 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.4.23
5C Calling party BCD Calling party BCD num. O TLV 3-14
number 10.5.4.9
5D Calling party sub- Calling party subaddr. O TLV 2-23
address 10.5.4.10
5E Called party BCD Called party BCD num. O TLV 3-19
number 10.5.4.7
6D Called party sub- Called party subaddr. O TLV 2-23
address 10.5.4.8
74 Redirecting party BCD number Redirecting party BCD num.
10.5.4.21a
O TLV 3-19
75 Redirecting party sub-address Redirecting party subaddress.
10.5.4.21b
O TLV 2-23
D- LLC repeat indicator Repeat indicator O TV 1
10.5.4.22
7C Low layer Low layer comp. O TLV 2-15
compatibility I 10.5.4.18
7C Low layer Low layer comp. C TLV 2-15
compatibility II 10.5.4.18
D- HLC repeat indicator Repeat indicator O TV 1
10.5.4.22
7D High layer High layer comp. O TLV 2-5
compatibility i 10.5.4.16
7D High layer High layer comp. C TLV 2-5
compatibility ii 10.5.4.16
10.5.4.25
8- Priority Priority Level O TV 1
10.5.1.11
19 Alert Alerting Pattern O TLV 3
10.5.4.26
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.
ETSI
354 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.: GSM 09.07). The bearer capability 2 IE is missing at least if the bearer
capability 1 IE is missing.
9.3.23.1.3 Facility
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
9.3.23.1.4a Called party BCD number
For all bands except for PCS1900, 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 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.10 High layer compatibility i
Included in the network-to-mobile station direction if the calling user specified a high layer compatibility.
ETSI
355 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.3.23.1.11 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.13 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.16 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 GSM 02.07.
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.
Message type: SETUP
Table 9.70a/GSM 04.08: SETUP message content (mobile station to network direction)
10.3.2
Setup Message type M V 1
message type 10.4
D- BC repeat indicator Repeat indicator C TV 1
10.5.4.22
04 Bearer capability 1 Bearer capability M TLV 3-16
10.5.4.5
ETSI
356 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.4.5
1C Facility(simple recall alignment) Facility O TLV 2-
10.5.4.15
5D Calling party sub- Calling party subaddr. O TLV 2-23
address 10.5.4.10
5E Called party BCD Called party BCD num. M TLV 3-43
number 10.5.4.7
6D Called party sub- Called party subaddr. O TLV 2-23
address 10.5.4.8
D- LLC repeat indicator Repeat indicator O TV 1
10.5.4.22
compatibility I 10.5.4.18
compatibility II 10.5.4.18
D- HLC repeat indicator Repeat indicator O TV 1
10.5.4.22
compatibility i 10.5.4.16
compatibility ii 10.5.4.16
10.5.4.25
10.5.4.24
A1 CLIR suppression CLIR suppression C T 1
10.5.4.11a
A2 CLIR invocation CLIR invocation C T 1
10.5.4.11b
15 CC capabilities Call Control Capabilities O TLV 3
10.5.4.5a
1D Facility $(CCBS)$ Facility O TLV 2-?
(advanced recall alignment) 10.5.4.15
1B Facility (recall alignment Facility O TLV 2-?
Not essential) $(CCBS)$ 10.5.4.15
ETSI
357 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.
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 04.10.
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 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 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.
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.
ETSI
358 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.3.23.2.11 CLIR suppression
The information element may be included by the MS (see GSM 04.81). If this information element is included the CLIR
invocation IE shall not be included.
9.3.23.2.12 CLIR invocation
The information element may be included by the MS (see GSM 04.81). 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.23a Start CC $(CCBS)$
A Network that does not support the Network initiated MO call option shall treat this message as a message with
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.
Message type: START CC
Significance: local
Table 9.70b/GSM 04.08: START CC message content
10.3.2
Start CC Message type M V 1
message type 10.4
15 CC Capabilities Call Control Capabilities O TLV 3
10.5.4.5a
9.3.23a.1 CC Capabilities
This information element may be included by the mobile station to indicate its call control capabilities
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.
Message type: START DTMF
Significance: local
ETSI
359 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.71/GSM 04.08: START DTMF message content
10.3.2
Start DTMF Message type M V 1
message type 10.4
2C Keypad facility Keypad facility M TV 2
10.5.4.17
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).
Message type: START DTMF ACKNOWLEDGE
Significance: local
Table 9.72/GSM 04.08: START DTMF ACKNOWLEDGE message content
10.3.2
Start DTMF acknowledge Message type M V 1
message type 10.4
2C Keypad facility Keypad facility M TV 2
10.5.4.17
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.
Message type: START DTMF REJECT
ETSI
360 draft ETSI EN 300 940 V7.7.0 (2000-04)
Significance: local
Table 9.73/GSM 04.08: START DTMF REJECT message content
10.3.2
Start DTMF reject Message type M V 1
message type 10.4
10.5.4.11
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 section 8. It shall also be sent in response to a STATUS ENQUIRY message.
Message type: STATUS
Significance: local
Direction: both
Table 9.74/GSM 04.08: STATUS message content
10.3.2
Status Message type M V 1
message type 10.4
10.5.4.11
Call state Call state M V 1
10.5.4.6
24 Auxiliary states Auxiliary states O TLV 3
10.5.4.4
ETSI
361 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 GSM 04.83 and GSM 04.84
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.
Message type: STATUS ENQUIRY
Significance: local
Direction: both
Table 9.75/GSM 04.08: STATUS ENQUIRY message content
10.3.2
Status enquiry Message type M V 1
message type 10.4
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.
Message type: STOP DTMF
Significance: local
Table 9.76/GSM 04.08: STOP DTMF message content
10.3.2
Stop DTMF Message type M V 1
message type 10.4
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.
ETSI
362 draft ETSI EN 300 940 V7.7.0 (2000-04)
Message type: STOP DTMF ACKNOWLEDGE
Significance: local
Table 9.77/GSM 04.08: STOP DTMF ACKNOWLEDGE message content
10.3.2
Stop DTMF acknowledge Message type M V 1
message type 10.4
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 GSM 04.10.
Message type: USER INFORMATION
Significance: access
Direction: both
Table 9.78/GSM 04.08: USER INFORMATION message content
10.3.2
User Information Message type M V 1
message type 10.4
User-user User-user M LV 3-131
10.5.4.25
A0 More data More data O T 1
10.5.4.19
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.
ETSI
363 draft ETSI EN 300 940 V7.7.0 (2000-04)
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 Attach 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/GSM 04.08.
Message type: ATTACH REQUEST
Significance: dual
Direction: MS to network
Table 9.4.1/GSM 04.08: ATTACH REQUEST message content
Protocol discriminator Protocol discriminator
10.2
M V 1/2
Skip indicator Skip indicator
10.3.1
M V
Attach request message identity Message type
10.4
M V 1
MS network capability MS network capability
10.5.5.12
M LV 2
Attach type Attach type
10.5.5.2
M V
GPRS ciphering key sequence
number
Ciphering key sequence number
10.5.1.2
M V
DRX parameter DRX parameter
10.5.5.6
M V 2
P-TMSI or IMSI 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 - 13
19 Old P-TMSI signature P-TMSI signature
10.5.5.8
O TV 4
17 Requested READY timer
value
GPRS Timer
10.5.7.3
O TV 2
9- TMSI status TMSI status
10.5.5.4
O TV 1
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.
ETSI
364 draft ETSI EN 300 940 V7.7.0 (2000-04)
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/GSM 04.08.
Message type: ATTACH ACCEPT
Significance: dual
Table 9.4.2/GSM 04.08: ATTACH ACCEPT message content
10.2
M V 1/2
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
Spare half octet Spare half octet
10.5.1.8
M V 1/2
Routing area identification Routing area identification
10.5.5.15
M V 6
19 P-TMSI signature P-TMSI signature
10.5.5.8
O TV 4
17 Negotiated READY timer
value
GPRS Timer
10.5.7.3
O TV 2
18 Allocated P-TMSI Mobile identity
10.5.1.4
O TLV 7
23 MS identity Mobile identity
10.5.1.4
O TLV 6 - 7
25 GMM cause GMM cause
10.5.5.14
O TV 2
This IE may be included to assign an identity to the MSs 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-TMSI
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.
ETSI
365 draft ETSI EN 300 940 V7.7.0 (2000-04)
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.3 Attach complete
This message is sent by the MS to the network if a P-TMSI and/or a TMSI was included within the attach accept
message. See table 9.4.3/GSM 04.08.
Message type: ATTACH COMPLETE
Significance: dual
Table 9.4.3/GSM 04.08: ATTACH COMPLETE message content
10.2
M V 1/2
10.3.1
M V 1/2
Attach complete message identity Message type
10.4
M V 1
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/GSM 04.08.
Message type: ATTACH REJECT
Significance: dual
Table 9.4.4/GSM 04.08: ATTACH REJECT message content
10.2
M V 1/2
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
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/GSM 04.08.
Message type: DETACH REQUEST
Significance: dual
ETSI
366 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.4.5.1/GSM 04.08: DETACH REQUEST message content
10.2
M V 1/2
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
10.5.5.7
M V 1/2
10.5.5.14
O 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/GSM 04.08.
Message type: DETACH REQUEST
Significance: dual
Table 9.4.5.2/GSM 04.08: DETACH REQUEST message content
10.2
M V 1/2
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
10.5.1.8
M V 1/2
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/GSM 04.08.
Message type: DETACH ACCEPT
Significance: dual
ETSI
367 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.4.6.1/GSM 04.08: DETACH ACCEPT message content
10.2
M V 1/2
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/GSM 04.08.
Message type: DETACH ACCEPT
Significance: dual
Table 9.4.6.2/GSM 04.08: DETACH ACCEPT message content
10.2
M V 1/2
10.3.1
M V 1/2
Detach accept message identity Message type
10.4
M V 1
10.5.5.7
M V 1/2
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/GSM 04.08.
Message type: P-TMSI REALLOCATION COMMAND
Significance: dual
ETSI
368 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.4.7/GSM 04.08: P-TMSI REALLOCATION COMMAND message content
10.2
M V 1/2
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
10.5.5.15
M V 6
10.5.5.7
M V 1/2
10.5.1.8
M V 1/2
10.5.5.8
O TV 4
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/GSM 04.08.
Message type: P-TMSI REALLOCATION COMPLETE
Significance: dual
Table 9.4.8/GSM 04.08: P-TMSI REALLOCATION COMPLETE message content
10.2
M V 1/2
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/GSM 04.08.
Message type: AUTHENTICATION AND CIPHERING REQUEST
Significance: dual
ETSI
369 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.4.9/GSM 04.08: AUTHENTICATION AND CIPHERING REQUEST message content
10.2
M V 1/2
10.3.1
M V 1/2
Authentication 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
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
O TV 17
8 GPRS ciphering key sequence
number
10.5.1.2
C TV 1
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.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/GSM 04.08.
Message type: AUTHENTICATION AND CIPHERING RESPONSE
Significance: dual
Table 9.4.10/GSM 04.08: AUTHENTICATION AND CIPHERING RESPONSE message content
10.2
M V 1/2
10.3.1
M V 1/2
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
10.5.1.8
M V 1/2
22 Authentication parameter SRES Authentication parameter SRES
10.5.3.2
O TV 5
23 IMEISV Mobile identity
10.5.1.4
O TLV 11
9.4.10.1 Authentication Parameter SRES
This IE is included if authentication was requested within the corresponding authentication and ciphering request
message.
ETSI
370 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.4.10.2 IMEISV
This IE is included if requested within the corresponding authentication and ciphering request message.
9.4.11 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/GSM 04.08.
Message type: AUTHENTICATION AND CIPHERING REJECT
Significance: dual
Table 9.4.11/GSM 04.08: AUTHENTICATION AND CIPHERING REJECT message content
10.2
M V 1/2
10.3.1
M V 1/2
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/GSM 04.08.
Message type: IDENTITY REQUEST
Significance: dual
Table 9.4.12/GSM 04.08: IDENTITY REQUEST message content
10.2
M V 1/2
10.3.1
M V 1/2
Identity request message identity Message type
10.4
M V 1
Identity type Identity type 2
10.5.5.9
M V 1/2
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/GSM 04.08.
Message type: IDENTITY RESPONSE
Significance: dual
ETSI
371 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.4.13/GSM 04.08: IDENTITY RESPONSE message content
10.2
M V 1/2
10.3.1
M V 1/2
Identity response message
identity
Message type
10.4
M V 1
Mobile 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/GSM 04.08.
Message type: ROUTING AREA UPDATE REQUEST
Significance: dual
Table 9.4.14/GSM 04.08: ROUTING AREA UPDATE REQUEST message content
10.2
M V 1/2
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 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 - 13
19 Old P-TMSI signature P-TMSI signature
10.5.5.8
O TV 4
17 Requested READY timer value GPRS Timer
10.5.7.3
O TV 2
27 DRX parameter DRX parameter
10.5.5.6
O TV 3
9- TMSI status TMSI status
10.5.5.4
O TV 1
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.14.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 may be included if the MS wants to indicate new DRX parameters.
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.
ETSI
372 draft ETSI EN 300 940 V7.7.0 (2000-04)
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/GSM 04.08.
Message type: ROUTING AREA UPDATE ACCEPT
Significance: dual
Table 9.4.15/GSM 04.08: ROUTING AREA UPDATE ACCEPT message content
10.2
M V 1/2
10.3.1
M V 1/2
Routing area update accept
message identity
Message type
10.4
M V 1
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
10.5.5.15
M V 6
10.5.5.8
O TV 4
18 Allocated P-TMSI Mobile identity
10.5.1.4
O TLV 7
23
MS identity
Mobile identity
10.5.1.4
O TLV 7
26 List of Receive N-PDU Numbers Receive N-PDU Number list
10.5.5.11
O TLV 4 - 19
17 Negotiated READY timer value GPRS Timer
10.5.7.3
O TV 2
10.5.5.14
O TV 2
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.
9.4.15.4 List of Receive N-PDU Numbers
This IE shall be included in case of an inter SGSN routing area updating, if there are PDP contexts that have been
activated in acknowledged transfer mode.
9.4.15.5 Negotiated READY timer value
This IE may be included to indicate a value for the READY timer.
ETSI
373 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.4.15.6 GMM cause
This IE shall be included if IMSI attach was not successful for non-GPRS services during a combined GPRS routing
area updating procedure.
9.4.16 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 a P-TMSI
and/or a TMSI has been assigned and/or if there are established LLC connections. See table 9.4.16/GSM 04.08.
Message type: ROUTING AREA UPDATE COMPLETE
Significance: dual
Table 9.4.16/GSM 04.08: ROUTING AREA UPDATE COMPLETE message content
10.2
M V 1/2
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
O TLV 4 - 19
9.4.16.1 List of Receive N-PDU Numbers
This IE shall be included if the routing area update accept message contained this IE.
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/GSM 04.08.
Message type: ROUTING AREA UPDATE REJECT
Significance: dual
Table 9.4.17/GSM 04.08: ROUTING AREA UPDATE REJECT message content
10.2
M V 1/2
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
10.5.5.7
M V 1/2
10.5.1.8
M V 1/2
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 section 8. See
table 9.4.18/GSM 04.08.
ETSI
374 draft ETSI EN 300 940 V7.7.0 (2000-04)
Message type: GMM STATUS
Significance: local
Direction: both
Table 9.4.18/GSM 04.08: GMM STATUS message content
10.2
M V 1/2
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/GSM 04.08.
Message type: GMM INFORMATION
Significance: local
Table 9.4.19/GSM 04.08: GMM INFORMATION message content
10.2
M V 1/2
10.3.1
M V 1/2
GMM information message
identity
Message type
10.4
M V 1
43 Full name for network Network name
10.5.3.5a
O TLV 3 - ?
45 Short name for network Network name
10.5.3.5a
O TLV 3 - ?
46 Network time zone Time zone
10.5.3.8
O TV 2
47 Universal time and time zone Time zone and time
10.5.3.9
O TV 8
48 LSA Identity LSA Identifier
10.5.3.11
O TLV 2-5
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 Network 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.
ETSI
375 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.4.19.4 Universal time and 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.
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.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.
Message type: ACTIVATE PDP CONTEXT REQUEST
Table 9.5.1/GSM 04.08: ACTIVATE PDP CONTEXT REQUEST message content
10.2
M V 1/2
Transaction identifier Transaction identifier
10.3.2
M V 1/2
Activate PDP context request
message identity
Message 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 4
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
O TLV 3 - 102
27 Protocol configuration options Protocol configuration options
10.5.6.3
O 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 provides protocol configuration options for the external PDN.
9.5.2 Activate PDP context accept
This message is sent by the network to the MS to acknowledge activation of a PDP context.
Message type: ACTIVATE PDP CONTEXT ACCEPT
ETSI
376 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.5.2/GSM 04.08: ACTIVATE PDP CONTEXT ACCEPT message content
10.2
M V 1/2
10.3.2
M V 1/2
Activate PDP context accept
message identity
Message 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 4
Radio priority Radio priority
10.5.7.2
M V 1/2
10.5.1.8
M V 1/2
2B PDP address Packet data protocol address
10.5.6.4
O TLV 4 - 20
10.5.6.3
O TLV 3 - 253
9.5.2.1 PDP address
If the MS did not request a static address in the corresponding ACTIVATE PDP CONTEXT REQUEST message, the
network shall include the PDP address IE in this ACTIVATE PDP CONTEXT ACCEPT message.
If the MS requested a static address in the corresponding ACTIVATE PDP CONTEXT REQUEST message, the
network shall not include the PDP address IE in this ACTIVATE PDP CONTEXT ACCEPT message.
This IE is included in the message when the network wishes to transmit protocol configuration options for the external
PDN.
9.5.3 Activate PDP context reject
This message is sent by the network to the MS to reject activation of a PDP context.
Message type: ACTIVATE PDP CONTEXT REJECT
ETSI
377 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.5.3/GSM 04.08: ACTIVATE PDP CONTEXT REJECT message content
10.2
M V 1/2
10.3.2
M V 1/2
Activate PDP context reject
message identity
Message type
10.4
M V 1
SM cause SM Cause
10.5.6.6
M V 1
10.5.6.3
O TLV 3 - 253
The protocol configuration options IE may only be inserted by the network (see GSM 09.60) if the SM Cause indicates
"activation rejected by GGSN".
9.5.4 Request PDP context activation
This message is sent by the network to the MS to initiate activation of a PDP context.
Message type: REQUEST PDP CONTEXT ACTIVATION
Table 9.5.4/GSM 04.08: REQUEST PDP CONTEXT ACTIVATION message content
10.2
M V 1/2
10.3.2
M V 1/2
Request PDP context activation
message identity
Message type
10.4
M V 1
Offered PDP address Packet data protocol address
10.5.6.4
M LV 3 - 19
10.5.6.1
O TLV 3 102
9.5.5 Request PDP context activation reject
This message is sent by the MS to the network to reject initiation of a PDP context activation.
Message type: REQUEST PDP CONTEXT ACTIVATION REJECT
ETSI
378 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.5.5/GSM 04.08: REQUEST PDP CONTEXT ACTIVATION REJECT message content
10.2
M V 1/2
10.3.2
M V 1/2
Request PDP context act. reject
message identity
Message type
10.4
M V 1
SM cause SM cause
10.5.6.6
M V 1
9.5.6 Modify PDP context request
This message is sent by the network to the MS to request modification of an active PDP context. See
table 9.5.6/GSM 04.08.
Message type: MODIFY PDP CONTEXT REQUEST
Table 9.5.6/GSM 04.08: MODIFY PDP CONTEXT REQUEST message content
10.2
M V 1/2
10.3.2
M V 1/2
Modify PDP context request
message identity
Message type
10.4
M V 1
10.5.7.2
M V 1/2
10.5.1.8
M V 1/2
10.5.6.9
M V 1
New QoS Quality of service
10.5.6.5
M LV 4
9.5.7 Modify PDP context accept
This message is sent by the MS to the network to acknowledge the modification of an active PDP context. See
table 9.5.7/GSM 04.08.
Message type: MODIFY PDP CONTEXT ACCEPT
Table 9.5.7/GSM 04.08: MODIFY PDP CONTEXT ACCEPT message content
10.2
M V 1/2
10.3.2
M V 1/2
Modify PDP context accept
message identity
Message type
10.4
M V 1
9.5.8 Deactivate PDP context request
This message is sent to request deactivation of an active PDP context. See table 9.5.8/GSM 04.08.
ETSI
379 draft ETSI EN 300 940 V7.7.0 (2000-04)
Message type: DEACTIVATE PDP CONTEXT REQUEST
Direction: both
Table 9.5.8/GSM 04.08: DEACTIVATE PDP CONTEXT REQUEST message content
10.2
M V 1/2
10.3.2
M V 1/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.5.9 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.9/GSM 04.08.
Message type: DEACTIVATE PDP CONTEXT ACCEPT
Direction: both
Table 9.5.9/GSM 04.08: DEACTIVATE PDP CONTEXT ACCEPT message content
10.2
M V 1/2
10.3.2
M V 1/2
Deactivate PDP context accept
message identity
Message type
10.4
M V 1
9.5.10 Activate AA PDP context request
This message is sent by the MS to the network to initiate activation of an AA PDP context.
Message type: ACTIVATE AA PDP CONTEXT REQUEST
ETSI
380 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.5.10/GSM 04.08: ACTIVATE AA PDP CONTEXT REQUEST message content
10.2
M V 1/2
10.3.2
M V 1/2
Activate AA PDP context request
message identity
Message type
10.4
M V 1
Requested NSAPI Network service access point
identifier 10.5.6.2
M V 1
10.5.6.9
M V 1
Requested QoS Quality of service
10.5.6. 5
M LV 4
Requested packet data
protocol address
Packet data protocol address
10.5.6.4
M LV 3 - 19
10.5.6.1
O TLV 3 - 102
10.5.6.3
O TLV 3 - 253
29 Requested AA-READY timer
value
GPRS Timer
10.5.7.3
O TV 2
9.5.10.1 Access point name
This IE is included in the message when the MS selects a specific external network to be connected to.
This IE is included in the message when the MS provides protocol configuration options for the external PDN.
9.5.10.3 Requested AA-READY timer value
This IE may be included if the MS wants to indicate a preferred value for the AA-READY timer.
9.5.11 Activate AA PDP context accept
This message is sent by the network to the MS to acknowledge the activation of an AA PDP context. See
table 9.5.11/GSM 04.08.
Message type: ACTIVATE AA PDP CONTEXT ACCEPT
ETSI
381 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.5.11/GSM 04.08: ACTIVATE AA PDP CONTEXT ACCEPT message content
10.2
M V 1/2
10.3.2
M V 1/2
Activate AA PDP context accept
message identity
Message 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 4
Allocated P-TMSI Mobile identity
10.5.1.4
M LV 6
Packet data protocol address Packet data protocol address
10.5.6.4
M LV 3 - 19
10.5.7.2
M V 1/2
10.5.1.8
M V 1/2
10.5.6.3
O TLV 3 - 253
29 Negotiated AA-Ready timer value GPRS Timer
10.5.7.3
O TV 2
This IE may be included if the network wishes to transmit protocol configuration options from the external PDN.
9.5.11.2 Negotiated AA-Ready timer value
This IE may be included if the network wants to indicate a value for the AA-READY timer.
9.5.12 Activate AA PDP context reject
This message is sent by the network to the MS to reject the activation of an AA PDP context. See
table 9.5.12/GSM 04.08.
Message type: ACTIVATE AA PDP CONTEXT REJECT
Table 9.5.12/GSM 04.08: ACTIVATE AA PDP CONTEXT REJECT message content
10.2
M V 1/2
10.3.2
M V 1/2
Activate AA PDP context reject
message identity
Message type
10.4
M V 1
SM Cause SM Cause
10.5.6.6
M V 1
10.5.6.3
O TLV 3 - 253
The protocol configuration options IE may only be inserted by the network (see GSM 09.60) if the SM Cause indicates
"activation rejected by GGSN".
ETSI
382 draft ETSI EN 300 940 V7.7.0 (2000-04)
9.5.13 Deactivate AA PDP context request
This message is sent to request deactivation of an active AA PDP context. See table 9.5.13/GSM 04.08.
Message type: DEACTIVATE AA PDP CONTEXT REQUEST
Table 9.5.13/GSM 04.08: DEACTIVATE AA PDP CONTEXT REQUEST message content
10.2
M V 1/2
10.3.2
M V 1/2
Deactivate AA PDP context
request message identity
Message type
10.4
M V 1
AA deactivation cause AA deactivation cause
10.5.6.8
M V 1/2
10.5.1.8
M V 1/2
9.5.14 Deactivate AA PDP context accept
This message is sent to acknowledge deactivation of an AA PDP context requested by the corresponding Deactivate AA
PDP context request message. See table 9.5.14/GSM 04.08.
Message type: DEACTIVATE AA PDP CONTEXT ACCEPT
Table 9.5.14/GSM 04.08: DEACTIVATE AA PDP CONTEXT ACCEPT message content
10.2
M V 1/2
10.3.2
M V 1/2
Deactivate AA PDP context
accept message identity
Message type
10.4
M V 1
9.5.15 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 section 8). See table 9.5.15/GSM 04.08.
Message type: SM Status
Significance: local
Direction: both
ETSI
383 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 9.5.15/GSM 04.08: SM STATUS message content
10.2
M V 1/2
10.3.2
M V 1/2
SM Status message identity Message type
10.4
M V 1
SM Cause SM Cause
10.5.6.6
M V 1
ETSI
384 draft ETSI EN 300 940 V7.7.0 (2000-04)
10 General message format and information elements
coding
The figures and text in this section describe the Information Elements contents.
10.1 Overview
Within the Layer 3 protocols defined in GSM 04.08, every message with the exception of the messages sent on the
BCCH, downlink CCCH, SCH, RACH, and the HANDOVER ACCESS message, is a standard L3 message as defined
in GSM 04.07 [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.
This organization is illustrated in the example shown in figure 10.1/GSM 04.08.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Transaction identifier Protocol discriminator octet 1
or Skip Indicator
+-----------------------------------------------
Message type octet 2
+-----------------------------------------------
Other information elements as required etc...
+----- - - - - - - - - - - - - - - - - - - -----+
Figure 10.1/GSM 04.08: General message organization example
Unless specified otherwise in the message descriptions of section 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.
ETSI
385 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.2 Protocol Discriminator
The Protocol Discriminator (PD) and its use are defined in GSM 04.07 [20]. GSM 04.08 defines the protocols relating
to the PD values:
bits 4 3 2 1
0 0 1 1 Call Control; call related SS messages
0 1 0 1 Mobility Management messages for non-GPRS services
0 1 1 0 Radio Resource management messages
1 0 0 0 Mobility Management messages for GPRS services
1 0 1 0 Session Management messages
except the call related SS procedures, which are defined in GSM 04.10.
10.3 Skip indicator and transaction identifier
10.3.1 Skip indicator
Bits 5 to 8 of the first octet of every Radio Resource management message and 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 Radio Resource management message or 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 Managementcontain the transaction identifier (TI). The transaction identifier and its use are defined in
GSM 04.07 [20].
10.4 Message Type
The message type IE and its use are defined in GSM 04.07 [20]. Tables 10.3/GSM 04.08, 10.4/GSM 04.08, and
10.4a/GSM 04.08 define the value part of the message type IE used in the Radio Resource management protocol, the
Mobility Management protocol, the Call Control protocol, and Session management protocol.
ETSI
386 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.1/GSM 04.08 (page 1 of 2): Message types for Radio Resource management
+---------------------------------------------------+
8 7 6 5 4 3 2 1

0 0 1 1 1 - - - Channel establishment messages:
1 0 0 - RR INITIALISATION REQUEST
0 1 1 - ADDITIONAL ASSIGNMENT
1 1 1 - IMMEDIATE ASSIGNMENT
0 0 1 - IMMEDIATE ASSIGNMENT EXTENDED
0 1 0 - IMMEDIATE ASSIGNMENT REJECT

0 0 1 1 0 - - - Ciphering messages:
1 0 1 - CIPHERING MODE COMMAND
0 1 0 - CIPHERING MODE COMPLETE

0 0 1 1 0 - - - Configuration change messages:
0 0 0 - CONFIGURATION CHANGE COMMAND
0 0 1 - CONFIGURATION CHANGE ACK.
0 1 1 - CONFIGURATION CHANGE REJECT

0 0 1 0 1 - - - Handover messages:
1 1 0 - ASSIGNMENT COMMAND
0 0 1 - ASSIGNMENT COMPLETE
1 1 1 - ASSIGNMENT FAILURE
0 1 1 - HANDOVER COMMAND
1 0 0 - HANDOVER COMPLETE
0 0 0 - HANDOVER FAILURE
1 0 1 - PHYSICAL INFORMATION

0 0 0 0 1 0 0 0 - RR-CELL CHANGE ORDER
0 0 1 0 0 0 1 1 - PDCH ASSIGNMENT COMMAND

0 0 0 0 1 - - - Channel release messages:
1 0 1 - CHANNEL RELEASE
0 1 0 - PARTIAL RELEASE
1 1 1 - PARTIAL RELEASE COMPLETE

0 0 1 0 0 - - - Paging and Notification messages:
0 0 1 - PAGING REQUEST TYPE 1
1 1 1 - PAGING RESPONSE
0 0 0 - NOTIFICATION/NCH
1 0 1 - NOTIFICATION/FACCH
1 1 0 - NOTIFICATION RESPONSE
0 0 0 0 1 0 1 1 - Reserved (see NOTE)
+---------------------------------------------------+
(continued...)
NOTE: This value was allocated but never used in earlier phases of the protocol.
ETSI
387 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.1/GSM 04.08 (page 2 of 2): Message types for Radio Resource management
+---------------------------------------------------+
8 7 6 5 4 3 2 1

0 0 0 1 1 - - - System information messages:
0 0 0 - SYSTEM INFORMATION TYPE 8

0 1 0 - SYSTEM INFORMATION TYPE 2bis
0 1 1 - SYSTEM INFORMATION TYPE 2ter
1 0 1 - SYSTEM INFORMATION TYPE 5bis
1 1 0 - SYSTEM INFORMATION TYPE 5ter


0 0 0 1 0 - - - Miscellaneous messages:
0 0 0 - CHANNEL MODE MODIFY
0 1 0 - RR STATUS
1 1 1 - CHANNEL MODE MODIFY ACKNOWLEDGE
1 0 0 - FREQUENCY REDEFINITION
1 0 1 - MEASUREMENT REPORT
1 1 0 - CLASSMARK CHANGE
0 1 1 - CLASSMARK ENQUIRY
0 0 1 1 0 1 1 0 - EXTENDED MEASUREMENT REPORT
0 0 1 1 0 1 1 1 - EXTENDED MEASUREMENT ORDER
0 0 1 1 0 1 0 0 - GPRS SUSPENSION REQUEST

VGCS uplink control messages:

0 0 0 0 1 0 0 1 - VGCS UPLINK GRANT
0 0 0 0 1 1 1 0 - UPLINK RELEASE
0 0 0 0 1 1 0 0 - UPLINK FREE
0 0 1 0 1 0 1 0 - UPLINK BUSY
0 0 0 1 0 0 0 1 - TALKER INDICATION

Application messages: |

| 0 0 1 1 1 0 0 0 - Application Information |
+---------------------------------------------------+
Bit 8 is reserved for possible future use as an extension bit, see GSM 04.07.
ETSI
388 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.1a/GSM 04.08: Message types for Radio Resource management messages using the RR
short protocol discriminator
+---------------------------------------------------+
5 4 3 2 1

0 0 0 0 0 SYSTEM INFORMATION TYPE 10
0 0 0 0 1 NOTIFICATION/FACCH
0 0 0 1 0 UPLINK FREE

+---------------------------------------------------+
Table 10.2/GSM 04.08: Message types for Mobility Management
+---------------------------------------------------+

8 7 6 5 4 3 2 1

0 x 0 0 - - - - Registration messages:
0 0 0 1 - IMSI DETACH INDICATION
0 0 1 0 - LOCATION UPDATING ACCEPT
0 1 0 0 - LOCATION UPDATING REJECT
1 0 0 0 - LOCATION UPDATING REQUEST

0 x 0 1 - - - - Security messages:
0 0 0 1 - AUTHENTICATION REJECT
0 0 1 0 - AUTHENTICATION REQUEST
0 1 0 0 - AUTHENTICATION RESPONSE
1 0 0 0 - IDENTITY REQUEST
1 0 0 1 - IDENTITY RESPONSE
1 0 1 0 - TMSI REALLOCATION COMMAND
1 0 1 1 - TMSI REALLOCATION COMPLETE

0 x 1 0 - - - - Connection management messages:
0 0 0 1 - CM SERVICE ACCEPT
0 0 1 0 - CM SERVICE REJECT
0 0 1 1 - CM SERVICE ABORT
0 1 0 0 - CM SERVICE REQUEST
0 1 0 1 - CM SERVICE PROMPT
0 1 1 0 - Reserved (see NOTE)
1 0 0 0 - CM RE-ESTABLISHMENT REQUEST
1 0 0 1 - ABORT

0 x 1 1 - - - - Miscellaneous messages:
0 0 0 0 - MM NULL
0 0 0 1 - MM STATUS
0 0 1 0 - MM INFORMATION
+---------------------------------------------------+
NOTE: This value was allocated but never used in earlier phases of the protocol.
Bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from the
network, bit 7 is coded with a "0". See GSM 04.07.
ETSI
389 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.3/GSM 04.08: Message types for Call Control and call related SS messages
+---------------------------------------------------+
8 7 6 5 4 3 2 1
0 x 0 0 0 0 0 0 escape to nationally specific
message types ; see 1) below

0 x 0 0 - - - - Call establishment messages:
0 0 0 1 - ALERTING
1 0 0 0 - CALL CONFIRMED
0 0 1 0 - CALL PROCEEDING
0 1 1 1 - CONNECT
1 1 1 1 - CONNECT ACKNOWLEDGE
1 1 1 0 - EMERGENCY SETUP
0 0 1 1 - PROGRESS
0 1 0 0 - CC-ESTABLISHMENT
0 1 1 0 - CC-ESTABLISHMENT CONFIRMED
1 0 1 1 - RECALL
1 0 0 1 - START CC
0 1 0 1 - SETUP

0 x 0 1 - - - - Call information phase messages:
0 1 1 1 - MODIFY
1 1 1 1 - MODIFY COMPLETE
0 0 1 1 - MODIFY REJECT
0 0 0 0 - USER INFORMATION
1 0 0 0 - HOLD
1 0 0 1 - HOLD ACKNOWLEDGE
1 0 1 0 - HOLD REJECT
1 1 0 0 - RETRIEVE
1 1 0 1 - RETRIEVE ACKNOWLEDGE
1 1 1 0 - RETRIEVE REJECT

0 x 1 0 - - - - Call clearing messages:
0 1 0 1 - DISCONNECT
1 1 0 1 - RELEASE
1 0 1 0 - RELEASE COMPLETE

0 x 1 1 - - - - Miscellaneous messages:
1 0 0 1 - CONGESTION CONTROL
1 1 1 0 - NOTIFY
1 1 0 1 - STATUS
0 1 0 0 - STATUS ENQUIRY
0 1 0 1 - START DTMF
0 0 0 1 - STOP DTMF
0 0 1 0 - STOP DTMF ACKNOWLEDGE
0 1 1 0 - START DTMF ACKNOWLEDGE
0 1 1 1 - START DTMF REJECT
1 0 1 0 - FACILITY
+---------------------------------------------------+
1): When used, the message type is defined in the following octet(s), according to the national specification.
Bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from the
network, bit 7 is coded with a "0". See GSM 04.07.
ETSI
390 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.4/GSM 04.08: Message types for GPRS mobility management
Bits
8 7 6 5 4 3 2 1
0 0 - - - - - - Mobility management messages
0 0 0 0 0 0 0 1 Attach request
0 0 0 0 0 0 1 0 Attach accept
0 0 0 0 0 0 1 1 Attach complete
0 0 0 0 0 1 0 0 Attach reject
0 0 0 0 0 1 0 1 Detach request
0 0 0 0 0 1 1 0 Detach accept
0 0 0 0 1 0 0 0 Routing area update request
0 0 0 0 1 0 0 1 Routing area update accept
0 0 0 0 1 0 1 0 Routing area update complete
0 0 0 0 1 0 1 1 Routing area update reject
0 0 0 1 0 0 0 0 P-TMSI reallocation command
0 0 0 1 0 0 0 1 P-TMSI reallocation complete
0 0 0 1 0 0 1 0 Authentication and ciphering req
0 0 0 1 0 0 1 1 Authentication and ciphering resp
0 0 0 1 0 1 0 0 Authentication and ciphering rej
0 0 0 1 0 1 0 1 Identity request
0 0 0 1 0 1 1 0 Identity response
0 0 1 0 0 0 0 0 GMM status
0 0 1 0 0 0 0 1 GMM information
Table 10.4a/GSM 04.08: Message types for GPRS session management
Bits
8 7 6 5 4 3 2 1
0 1 - - - - - - Session management messages
0 1 0 0 0 0 0 1 Activate PDP context request
0 1 0 0 0 0 1 0 Activate PDP context accept
0 1 0 0 0 0 1 1 Activate PDP context reject
0 1 0 0 0 1 0 0 Request PDP context activation
0 1 0 0 0 1 0 1 Request PDP context activation rej.
0 1 0 0 0 1 1 0 Deactivate PDP context request
0 1 0 0 0 1 1 1 Deactivate PDP context accept
0 1 0 0 1 0 0 0 Modify PDP context request
0 1 0 0 1 0 0 1 Modify PDP context accept
0 1 0 1 0 0 0 0 Activate AA PDP context request
0 1 0 1 0 0 0 1 Activate AA PDP context accept
0 1 0 1 0 0 1 0 Activate AA PDP context reject
0 1 0 1 0 0 1 1 Deactivate AA PDP context request
0 1 0 1 0 1 0 0 Deactivate AA PDP context accept
0 1 0 1 0 1 0 1 SM Status
ETSI
391 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5 Other information elements
The different formats (V, LV, T, TV, TLV) and the four categories of information elements (type 1, 2, 3, and 4) are
The first octet of an information element in the non-imperative part contains the IEI of the information element. If this
octet does not correspond to an IEI known in the message, the receiver shall determine whether this IE is of type 1 or 2
(i.e. it is an information element of one octet length) or an IE of type 4 (i.e. that the next octet is the length indicator
indicating the length of the remaining of the information element) (see GSM 04.07).
This allows the receiver to jump over unknown information elements and to analyse any following information elements.
The information elements which are common for at least two of the three protocols Radio Resources management,
Mobility Management and Call Control, are listed in section 10.5.1.
The information elements for the protocols Radio Resources management, Mobility Management and Call Control are
listed in sections 10.5.2, 10.5.3 and 10.5.4 respectively. Default information element identifiers are listed in annex K.
NOTE: Different information elements may have the same default information element identifier if they belong to
different protocols.
The descriptions of the information element types in sections 10.5.1, 10.5.2, 10.5.3, and 10.5.4 are organized in
alphabetical order of the IE types. Each IE type is described in one subsection.
The subsection may have an introduction:
- possibly explaining the purpose of the IE;
- possibly describing whether the IE belongs to type 1, 2, 3, 4 or 5;
- possibly indicating the length that the information element has if it is either type 5 or if it is used in format TV
(type 1 and 3) or TLV (type 4).
A figure of the subsection defines the structure of the IE indicating:
- possibly the position and length of the IEI. (However it depends on the message in which the IE occurs whether
the IE contains an IEI.);
- the fields the IE value part is composed of;
- possibly the position and length of the length indicator. (However it depends on the IE type whether the IE
contains a length indicator or not.);
- possibly octet numbers of the octets that compose the IE (see clause a) below).
Finally, the subsection contains tables defining the structure and value range of the fields that compose the IE value part.
The order of appearance for information elements in a message is defined in section 9.
The order of the information elements within the imperative part of messages has been chosen so that information
elements with 1/2 octet of content (type 1) go together in succession. The first type 1 information element 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 N + 1 etc. If the number of type 1
information elements is odd then bits 5 to 8 of the last octet occupied by these information elements contains a spare half
octet IE in format V.
Where the description of information elements in this Technical Specification contains bits defined to be "spare bits",
these bits shall set to the indicated value (0 or 1) by the sending side, and their value shall be ignored by the receiving
side. With few exceptions, spare bits are indicated as being set to "0" in GSM 04.08.
The following rules apply for the coding of type 4 information elements:
a) The octet number of an octet (which is defined in the figure of a subsection) consists of a positive integer,
possibly of an additional letter, and possibly of an additional asterisk, see clause f). The positive integer identifies
one octet or a group of octets.
ETSI
392 draft ETSI EN 300 940 V7.7.0 (2000-04)
b) Each octet group is a self contained entity. The internal structure of an octet group may be defined in alternative
ways.
c) An octet group is formed by using some extension mechanism. The preferred extension mechanism is to extend
an octet (N) through the next octet(s) (Na, Nb, etc.) by using bit 8 in each octet as an extension bit.
The bit value "0" indicates that the octet group continues through to the next octet. The bit value "1" indicates
that this octet is the last octet of the group. If one octet (Nb) is present, the preceding octets (N and Na) shall also
be present.
In the format descriptions appearing in section 10.5.1 to 10.5.4, bit 8 is marked "0/1 ext" if another octet follows.
Bit 8 is marked "1 ext" if this is the last octet in the extension domain.
Additional octets may be defined in later versions of the protocols ("1 ext" changed to "0/1 ext") and equipments
shall be prepared to receive such additional octets; the contents of these octets shall be ignored. However the
length indicated in sections 9 and 10 only takes into account this version of the protocols.
d) In addition to the extension mechanism defined above, an octet (N) may be extended through the next octet(s)
(N+1, N+2 etc.) by indications in bits 7-1 (of octet N).
e) The mechanisms in c) and d) may be combined.
f) Optional octets are marked with asterisks (*).
10.5.1 Common information elements
10.5.1.1 Cell identity
The purpose of the Cell Identity information element is to identify a cell within a location area.
The Cell Identity information element is coded as shown in figure 10.5.1/GSM 04.08 and table 10.5.1/GSM 04.08.
The Cell Identity is a type 3 information element with 3 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Cell Identity IEI octet 1
+-----------------------------------------------

CI value octet 2
+-----------------------------------------------

CI value (continued) octet 3
+-----------------------------------------------+
Figure 10.5.1/GSM 04.08: Cell Identity information element
ETSI
393 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.1/GSM 04.08: Cell Identity information element
+------------------------------------------------------+
CI value, Cell identity value (octet 2 and 3)

In the CI value field bit 8 of octet 2 is the most
significant bit and bit 1 of octet 3 the least
significant bit.

The coding of the cell identity is the
responsibility of each administration. Coding
using full hexadecimal representation may be used.
The cell identity consists of 2 octets.

+------------------------------------------------------+
10.5.1.2 Ciphering Key Sequence Number
The purpose of the Ciphering Key Sequence Number information element is to make it possible for the network to
identify the ciphering key Kc which is stored in the mobile station without invoking the authentication procedure. The
ciphering key sequence number is allocated by the network and sent with the AUTHENTICATION REQUEST message
to the mobile station where it is stored together with the calculated ciphering key Kc.
The Ciphering Key Sequence Number information element is coded as shown in figure 10.5.2/GSM 04.08 and
table 10.5.2/GSM 04.08.
The ciphering key sequence number is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Ciphering Key key sequence octet 1
Sequence Number 0
IEI spare
+-----------------------------------------------+
Figure 10.5.2/GSM 04.08: Ciphering Key Sequence Number information element
Table 10.5.2/GSM 04.08: Ciphering Key Sequence Number information element
+-------------------------------------------------+
Key sequence (octet 1)

Bits
3 2 1

0 0 0
through Possible values for the ciphering key
1 1 0 sequence number

1 1 1 No key is available (MS to network);
Reserved (network to MS)
+-------------------------------------------------+
10.5.1.3 Location Area Identification
The purpose of the Location Area Identification information element is to provide an unambiguous identification of
location areas within the area covered by the GSM system.
The Location Area Identification information element is coded as shown in figure 10.5.3/GSM 04.08 and
table 10.5.3/GSM 04.08.
The Location Area Identification is a type 3 information element with 6 octets length.
ETSI
394 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Location Area Identification IEI octet 1
+-----------------------------------------------

MCC digit 2 MCC digit 1 octet 2
+-----------------------+-----------------------

MNC digit 3 MCC digit 3 octet 3
+-----------------------+-----------------------

MNC digit 2 MNC digit 1 octet 4
+-----------------------------------------------

LAC octet 5
+-----------------------------------------------

LAC (continued) octet 6
+-----------------------------------------------+
Figure 10.5.3/GSM 04.08: Location Area Identification information element
ETSI
395 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.3/GSM 04.08: Location Area Identification information element
MCC, Mobile country code (octet 2 and 3)
The MCC field is coded as in CCITT Rec. E212, Annex A.
If the LAI is deleted the MCC and MNC shall take the
value from the deleted LAI.
In abnormal cases, the MCC stored in the mobile
station can contain elements not in the set
{0, 1 ... 9}. In such cases the mobile station should
transmit the stored values using full hexadecimal
encoding. When receiving such an MCC, the network
shall treat the LAI as deleted.
MNC, Mobile network code (octet 3 bits 5 to 8, octet 4)
The coding of this field is the responsibility of each
administration but BCD coding shall be used. The
MNC shall consist of 2 or 3 digits. For PCS 1900 for
NA, Federal regulation mandates that a 3-digit MNC
shall be used. However a network operator may decide to
use only two digits in the MNC in the LAI over the
radio interface. In this case, bits 5 to 8 of octet 3
shall be coded as "1111". Mobile equipment shall accept
LAI coded in such a way.
Note 1: In earlier versions of this protocol, the
possibility to use a one digit MNC in LAI was provided
on the radio interface. However as this was not used
this possibility has been deleted.
Note 2: In earlier versions of this protocol, bits 5 to
8 of octet 3 were coded as "1111". Mobile equipment
compliant with these earlier versions of the protocol
may be unable to understand the 3-digit MNC format of
the LAI, and therefore unable to register on a network
broadcasting the LAI in this format.
In abnormal cases, the MNC stored in the mobile
station can have
- digit 1 or 2 not in the set {0, 1 ... 9}, or
- digit 3 not in the set {0, 1 ...9, F} hex.
In such cases the mobile station
shall transmit the stored values using full hexadecimal
encoding. When receiving such an MNC, the
network shall treat the LAI as deleted.
The same handling shall apply for the network, if a 3-
digit MNC is sent by the mobile station to a network
using only a 2-digit MNC.
LAC, Location area code (octet 5 and 6)
In the LAC field bit 8 of octet 5 is the most
significant bit and bit 1 of octet 6 the least
significant bit.
The coding of the location area code is the
responsibility of each administration except that
two values are used to mark the LAC, and hence the
LAI, as deleted. Coding using full hexadecimal
representation may be used. The location area code
consists of 2 octets.
If a LAI has to be deleted then all bits of the
location area code shall be set to one with the
exception of the least significant bit which shall be
set to zero. If a SIM is inserted in a Mobile Equipment
with the location area code containing all zeros, then
the Mobile Equipment shall recognise this LAC as part
of a deleted LAI
10.5.1.4 Mobile Identity
ETSI
396 draft ETSI EN 300 940 V7.7.0 (2000-04)
The purpose of the Mobile Identity information element is to provide either the international mobile subscriber identity,
IMSI, the temporary mobile subscriber identity, TMSI/P-TMSI, the international mobile equipment identity, IMEI or
the international mobile equipment identity together with the software version number, IMEISV.
The IMSI shall not exceed 15 digits, the TMSI/P-TMSI is 4 octets long, and the IMEI is composed of 15 digits, the
IMEISV is 16 digits (see GSM 03.03).
For packet paging the network shall select the mobile identity type with the following priority:
1- P-TMSI: The P-TMSI shall be used if it is available.
2- IMSI: The IMSI shall be used in cases where no P-TMSI is available.
For all other transactions except emergency call establishment, emergency call re-establishment, mobile terminated call
establishment, the identification procedure, the GMM identification procedure, the GMM authentication and ciphering
procedure and the ciphering mode setting procedure, the mobile station and the network shall select the mobile identity
type with the following priority:
1- TMSI: The TMSI shall be used if it is available.
2- IMSI: The IMSI shall be used in cases where no TMSI is available.
For mobile terminated call establishment the mobile station shall select the same mobile identity type as received from
the network in the PAGING REQUEST message.
For emergency call establishment and re-establishment the mobile station shall select the mobile identity type with the
following priority:
1- TMSI: The TMSI shall be used if it is available.
2- IMSI: The IMSI shall be used in cases where no TMSI is available.
3- IMEI: The IMEI shall be used in cases where no SIM is available or the SIM is considered as not valid by the
mobile station or no IMSI or TMSI is available.
In the identification procedure and in the GMM identification procedure the mobile station shall select the mobile
identity type which was requested by the network.
In the ciphering mode setting procedure and in the GMM authentication and ciphering procedure the mobile shall select
the IMEISV.
The Mobile Identity information element is coded as shown in figure 10.5.4/GSM 04.08 and table 10.5.4/GSM 04.08.
The Mobile Identity is a type 4 information element with a minimum length of 3 octet and 11 octets length maximal.
Further restriction on the length may be applied, e.g. number plans.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Mobile Identity IEI octet 1
+-----------------------------------------------

Length of mobile identity contents octet 2
+-----------------------------------------------
odd/
Identity digit 1 even Type of identity octet 3
indic
+-----------------------+-----------------------

Identity digit p+1 Identity digit p octet 4*
+-----------------------------------------------+
Figure 10.5.4/GSM 04.08: Mobile Identity information element
ETSI
397 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.4/GSM 04.08: Mobile Identity information element
+--------------------------------------------------------+
Type of identity (octet 3)
Bits
3 2 1
0 0 1 IMSI
0 1 0 IMEI
0 1 1 IMEISV
1 0 0 TMSI/P-TMSI
0 0 0 No Identity note 1)

All other values are reserved.

Odd/even indication (octet 3)
Bit
4
0 even number of identity digits and also when
the TMSI/P-TMSI is used
1 odd number of identity digits

Identity digits (octet 3 etc)
For the IMSI, IMEI and IMEISV this field is coded using
BCD coding. If the number of identity digits is even
then bits 5 to 8 of the last octet shall be filled
with an end mark coded as "1111".

If the mobile identity is the TMSI/P-TMSI then bits 5
to 8 of octet 3 are coded as "1111" and bit 8 of octet
4 is the most significant bit and bit 1 of the last
octet the least significant bit. The coding of the
TMSI/P-TMSI is left open for each administration.
+--------------------------------------------------------+
NOTE 1: This can be used in the case when a fill paging message without any valid identity has to be sent on the
paging subchannel.
10.5.1.5 Mobile Station Classmark 1
The purpose of the Mobile Station Classmark 1 information element is to provide the network with information
concerning aspects of high priority of the mobile station equipment. This affects the manner in which the network
handles the operation of the mobile station. The Mobile Station Classmark information indicates general mobile station
characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the
channel it is sent on.
The Mobile Station Classmark 1 information element is coded as shown in figure 10.5.5/GSM 04.08 and
table 10.5.5/GSM 04.08.
The Mobile Station Classmark 1 is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Mobile Station Classmark 1 IEI octet 1
+-----+-----------------------------------------
0 Revision ES A5/1 RF power
spare level IND capability octet 2
+-----------------------------------------------+
Figure 10.5.5/GSM 04.08: Mobile Station Classmark 1 information element
ETSI
398 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.5/GSM 04.08: Mobile Station Classmark 1 information element
Revision level (octet 2)
Bits
7 6
0 0 Reserved for phase 1
0 1 Used by phase 2 mobile stations
All other values are reserved for future use.
ES IND (octet 2, bit 5) "Controlled Early Classmark Sending" option implementation
0 "Controlled Early Classmark Sending" option is not implemented in the MS
1 "Controlled Early Classmark Sending" option is implemented in the MS
NOTE: The value of the ES IND gives the implementation in the MS. Its value is not dependent
on the broadcast SI 3 Rest Octet <Early Classmark Sending Control> value.
A5/1 algorithm supported (octet 2, bit 4)
0 encryption algorithm A5/1 available
1 encryption algorithm A5/1 not available
RF power capability (octet 2)
When the GSM P, E [or R] 900 MHz band is used (for exceptions see 3.4.18):
Bits
3 2 1
0 0 0 class 1
0 0 1 class 2
0 1 0 class 3
0 1 1 class 4
1 0 0 class 5
When the DCS 1800 or PCS 1900 band is used (for exceptions see 3.4.18):
Bits
3 2 1
0 0 0 class 1
0 0 1 class 2
0 1 0 class 3
concerning aspects of both high and low priority of the mobile station equipment. This affects the manner in which the
network handles the operation of the mobile station. The Mobile Station Classmark information indicates general mobile
station characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band
of the channel it is sent on.
The Mobile Station Classmark 2 information element is coded as shown in figure 10.5.6/GSM 04.08,
table 10.5.6a/GSM 04.08 and table 10.5.6b/GSM 04.08.
The Mobile Station Classmark 2 is a type 4 information element with 5 octets length.
ETSI
399 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Mobile station classmark 2 IEI octet 1
+-----------------------------------------------

Length of mobile station classmark 2 contents octet 2
+-----------------------------------------------
0 Revision ES A5/1 RF power
spare level IND capability octet 3
+-----+-----------------+-----+-----------------
0 PS SS Screen. SM ca VBS VGCS FC
spare capa. Indicator pabi. octet 4
+-----+-----------------+-----+-----+-----+-----
CM3 0 LCSVA 0 SoLSA CMSP A5/3 A5/2
Spare Cap spare octet 5
+-----------------------------------------------+
NOTE: Owing to backward compatibility problems, bit 8 of octet 4 should not be used unless it is also checked
that the bits 8, 7 and 6 of octet 3 are not "0 0 0".
ETSI
400 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.6a/GSM 04.08: Mobile Station Classmark 2 information element
Revision level (octet 3)
Bits
7 6
0 0 Reserved for phase 1
0 1 Used by phase 2 mobile stations
All other values are reserved for future use
ES IND (octet 3, bit 5) "Controlled Early Classmark Sending" option implementation
0 "Controlled Early Classmark Sending" option is not implemented in the MS
1 "Controlled Early Classmark Sending" option is implemented in the MS
NOTE: The value of the ES IND gives the implementation in the MS. Its value is not dependent
on the broadcast SI 3 Rest Octet <Early Classmark Sending Control> value.
RF Power Capability (Octet 3)
When GSM 900 P, E [or R] band is used (for exceptions see 3.4.18):
Bits
3 2 1
0 0 0 class 1
0 0 1 class 2
0 1 0 class 3
0 1 1 class 4
1 0 0 class 5
When the DCS 1800 or PCS 1900 band is used (for exceptions see 3.4.18):
Bits
3 2 1
0 0 0 class 1
0 0 1 class 2
0 1 0 class 3
PS capability (pseudo-synchronization capability) (octet 4)
Bit 7
0 PS capability not present
1 PS capability present
SS Screening Indicator (octet 4)
Bits
6 5
0 0 defined in GSM 04.80
SM capability (MT SMS pt to pt capability) (octet 4)
Bit 4
0 Mobile station does not support mobile terminated point to point SMS
1 Mobile station supports mobile terminated point to point SMS
ETSI
401 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.6b/GSM 04.08: Mobile Station Classmark 2 information element
VBS notification reception (octet 4)
Bit 3
0 no VBS capability or no notifications wanted
1 VBS capability and notifications wanted
VGCS notification reception (octet 4)
Bit 2
0 no VGCS capability or no notifications wanted
1 VGCS capability and notifications wanted
FC Frequency Capability (octet 4)
When a GSM 900 band is used (for exceptions see 3.4.18):
Bit 1
0 The MS does not support the E-GSM or R-GSM band (For definition of frequency bands
see GSM 05.05)
1 The MS does support the E-GSM or R-GSM (For definition of frequency bands see
GSM 05.05)
Note : For mobile station supporting the R-GSM band further information can be found in MS
Classmark 3.
When the DCS 1800 band is used (for exceptions see 3.4.18):
Bit 1
0 Reserved for future use (for definition of frequency bands see GSM 05.05)
Note: This bit conveys no information about support or non support of the E-GSM or R-GSM
band when transmitted on a DCS 1800 channel.
CM3 (octet 5, bit 8)
0 The MS does not support any options that are indicated in CM3
1 The MS supports options that are indicated in classmark 3 IE
LCS VA capability (LCS value added location request notification capability) (octet 5,bit 6)
0 LCS value added location request notification capability not supported
1 LCS value added location request notification capability supported
SoLSA (octet 5, bit 4)
0 The ME does not support SoLSA.
1 The ME supports SoLSA.
CMSP: CM Service Prompt (octet 5, bit 3) $(CCBS)$
0 Network initiated MO CM connection request not supported.
1 Network initiated MO CM connection request supported for at least one CM
protocol.
NOTE: Additional mobile station capability information might be obtained by invoking the classmark
interrogation procedure.
concerning aspects of the mobile station. The contents might affect the manner in which the network handles the
operation of the mobile station. The Mobile Station Classmark information indicates general mobile station
characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the
channel it is sent on.
ETSI
402 draft ETSI EN 300 940 V7.7.0 (2000-04)
The MS Classmark 3 is a type 4 information element with a maximum of 14 octets length.
The value part of a MS Classmark 3 information element is coded as shown in figure 10.5.7/GSM 04.08 and
table 10.5.7/GSM 04.08.
NOTE: The 14 octet limit is so that the CLASSMARK CHANGE message will fit in one layer 2 frame.
SEMANTIC RULE : a multiband mobile station shall provide information about all frequency bands it can support. A
single band mobile station shall not indicate the band it supports in the Multiband Supported field in the MS Classmark
3.
SEMANTIC RULE : a mobile station shall include the MS Measurement Capability field if the Multi Slot Class field
contains a value of 19 or greater (see GSM 05.02).
Typically, the number of spare bits at the end is the minimum to reach an octet boundary. The receiver may add any
number of bits set to "0" at the end of the received string if needed for correct decoding.
<Classmark 3 Value part> ::=
<spare bit>
{ <Multiband supported : {000}>
<A5 bits> |
<Multiband supported : { 101 | 110}>
<A5 bits>
<Associated Radio Capability 2 : bit(4)>
<Associated Radio Capability 1 : bit(4)> |
<Multiband supported : {001 | 010 | 100 }>
<A5 bits>
<spare bit>(4)
<Associated Radio Capability 1 : bit(4)> }
{ 0 | 1 <R Support> }
{ 0 | 1 <Multi Slot Capability>}
<UCS2 treatment: bit>
<Extended Measurement Capability : bit>
{ 0 | 1 <MS measurement capability> }
{ 0 | 1 <MS Positioning Method Capability> }
<spare bit>;
<A5 bits> ::= <A5/7 : bit> <A5/6 : bit> <A5/5 : bit> <A5/4 : bit> ;
<R Support>::=
< R-GSM band Associated Radio Capability : bit(3)>;
<Multi Slot Capability> ::=
<Multi Slot Class : bit(5)> ;
< MS Measurement capability > ::=
< SMS_VALUE : bit (4) >
< SM_VALUE : bit (4) >;
< MS Positioning Method Capability > ::=
< MS Positioning Method : bit(5)>;
ETSI
403 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.7/GSM 04.08: Mobile Station Classmark 3 information element
Multiband Supported (3 bit field)
Band 1 supported (third bit of the field)
0 P-GSM not supported
1 P-GSM supported
Band 2 supported (second bit of the field)
0 E-GSM or R-GSM not supported
1 E-GSM or R-GSM supported
Band 3 supported (first bit of the field)
0 DCS 1800 not supported
1 DCS 1800 supported
The indication of support of P-GSM band or E-GSM or R-GSM band is mutually
exclusive.
When the Band 2 supported bit indicates support of E-GSM or R-GSM, the
presence of the <R Support> field, see below, indicates if the E-GSM or R-GSM
band is supported.
In this version of the protocol, the sender indicates in this field either none
or two of these 3 bands supported. However, if only one band is indicated, the
receiver shall ignore the Associated Radio Capability 2.
For single band mobile station all bits are set to 0.
A5/4
A5/5
A5/6
A5/7
Associated Radio capability 1 and 2
If either of P-GSM or E-GSM or R-GSM is supported, the radio capability 1 field
indicates the radio capability for P-GSM, E-GSM or R-GSM, and the radio
capability 2 field indicates the radio capability for DCS1800 if supported, and
is spare otherwise.
If none of P-GSM or E-GSM or R-GSM are supported, the radio capability 1 field
indicates the radio capability for DCS1800, and the radio capability 2 field is
spare.
The radio capability contains the binary coding of the power class associated
with the band indicated in multiband support bits (see GSM05.05).
R Support
In case where the R-GSM band is supported the R-GSM band assciated radio
capability field contains the binary coding of the power class associated(see
GSM05.05). A mobile station supporting the R-GSM band shall also when
appropriate, see 10.5.1.6, indicate its support in the 'FC' bit in the Mobile
Station Classmark 2 information element.
Note: the coding of the power class for P-GSM, E-GSM, R-GSM and DCS 1800 in
radio capability 1 and/or 2 is different to that used in the Mobile Station
Classmark 1 and Mobile Station Classmark 2 information elements.
(continued...)
ETSI
404 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.1.7/GSM 04.08 (continued): MS Classmark 3 information element
Multi Slot Class (5 bit field)
In case the MS supports the use of multiple timeslots then the Multi Slot Class
field is coded as the binary representation of the multislot class defined in TS
GSM 05.02.
UCS2 treatment
This information field indicates the likely treatment by the mobile station of
UCS2 encoded character strings. If not included, the value 0 shall be assumed by
the receiver.
0 the ME has a preference for the default alphabet (defined in GSM 03.38)
over UCS2.
1 the ME has no preference between the use of the default alphabet and the
use of UCS2.
Extended Measurement Capability
This bit indicates whether the mobile station supports Extended Measurements
or not
0 the MS does not support Extended Measurements
1 the MS supports Extended Measurements
SMS_VALUE (Switch-Measure-Switch) (4 bit field)
The SMS field indicates the time needed for the mobile station to switch from one radio channel to another, perform a
neighbour cell power measurement, and the switch from that radio channel to another radio channel.
Bits
4 3 2 1
0 0 0 0 1/4 timeslot (~144 microseconds)
. . .
SM_VALUE (Switch-Measure) (4 bit field)
The SM field indicates the time needed for the mobile station to switch from one radio channel to another and perform a
neighbour cell power measurement.
Bits
4 3 2 1
. . .
(continued)...
ETSI
405 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.1.7/GSM 04.08 (continued): MS Classmark 3 information element
MS Positioning Method Capability
This bit indicates whether the MS supports Positioning Method or not for the provision of Location Services.
MS Positioning Method (5 bit field)
This field indicates the Positioning Method(s) supported by the mobile station.
MS assisted E-OTD
Bit 5
0: MS assisted E-OTD not supported
1: MS assisted E-OTD supported
MS based E-OTD
Bit 4
0: MS based E-OTD not supported
1: MS based E-OTD supported
MS assisted GPS
Bit 3
0: MS assisted GPS not supported
1: MS assisted GPS supported
MS based GPS
Bit 2
0: MS based GPS not supported
1: MS based GPS supported
MS conventional GPS
Bit 1
0: conventional GPS not supported
1: conventional GPS supported
10.5.1.8 Spare Half Octet
This element is used in the description of messages in section 9 when an odd number of half octet type 1 information
elements are used . This element is filled with spare bits set to zero and is placed in bits 5 to 8 of the octet unless
10.5.1.9 Descriptive group or broadcast call reference
The purpose of the Descriptive Group or Broadcast Call Reference is to provide information describing a voice group
or broadcast call. The IE of the Descriptive Group or Broadcast Call Reference is composed of the group or broadcast
call reference together with a service flag, an acknowledgement flag, the call priority and the group cipher key number.
The Descriptive Group or Broadcast Call Reference information element is coded as shown in figure 10.5.8/GSM 04.08
and Table10.5.8/GSM 04.08
The Descriptive Group or Broadcast Call Reference is a type 3 information element with 6 octets length.
ETSI
406 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Group or broadcast call reference IEI octet 1
+-----------------------------------------------
Binary coding of the group or broadcast
call reference octet 2
+-----------------------------------------------

octet 3
+-----------------------------------------------

octet 4
+-----------------------------------------------

SF AF call priority octet 5
+-----------------------+-----------------------+
Spare
Ciphering information 0 0 0 0 octet 6
+-----------------------+
Figure 10.5.8/GSM 04.08: Descriptive Group or Broadcast Call Reference
ETSI
407 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.8/GSM 04.08: Descriptive Group or Broadcast Call Reference
+-------------------------------------------------------+
Binary code of the group or broadcast call reference
The length of the binary code has 27 bits which is
encoded in the octet 2, 3, 4
and Bits 8,7,6 (octet 5).
The highest bit of the BC is the bit 8 in the octet 2
and the lowest bit is allocated in the bit 6
in the octet 5. (see also GSM03.03)

SF Service flag (octet 5)
Bit
5
0 VBS (broadcast call reference)
1 VGCS (group call reference)

AF Acknowledgement flag (octet 5)
Bit
4
0 acknowledgement is not required
1 acknowledgement is required

Call priority (octet 5)
Bit
3 2 1
0 0 0 no priority applied
0 0 1 call priority level 4
1 1 0 call priority level B
1 1 1 call priority level A

Ciphering information (octet 6)
Bit
8 7 6 5
0 0 0 0 no ciphering
0 0 0 1 ciphering with cipher key number 1
1 0 1 0 ciphering with cipher key number A
1 0 1 1 ciphering with cipher key number B
1 1 0 0 ciphering with cipher key number C
1 1 0 1 ciphering with cipher key number D
1 1 1 0 ciphering with cipher key number E
1 1 1 1 ciphering with cipher key number F

+-------------------------------------------------------+
10.5.1.10 Group Cipher Key Number
The purpose of the Group Cipher Key Number is to provide information on the group cipher key to be used for
ciphering and deciphering by the mobile station.
The Group Cipher Key Number information element is coded as shown in figure 10.5.9/GSM 04.08 and
Table10.5.9/GSM 04.08
The Group Cipher Key Number is a type 1 information element with 1 octet length.
8 7 6 5 4 3 2 1
+------------------------------------------------+
Group cipher key number
IEI Group cipher key number
+------------------------------------------------+
Figure 10.5.9/GSM 04.08: Group Cipher Key Number
ETSI
408 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.9/GSM 04.08: Group Cipher Key Number
+-------------------------------------------------------+
Group cipher key number
Bit
4 3 2 1
0 0 0 0 spare
0 0 0 1 cipher key number 1
1 0 1 0 cipher key number A
1 0 1 1 cipher key number B
1 1 0 0 cipher key number C
1 1 0 1 cipher key number D
1 1 1 0 cipher key number E
1 1 1 1 cipher key number F

+-------------------------------------------------------+
10.5.1.10a PD and SAPI $(CCBS)$
The purpose of the PD and SAPI information element is to provide information concerning Protocol Discriminators and
Service Access Point Identifiers.
The PD and SAPI information element is coded as shown in figure 10.5.10/GSM 04.08 and table 10.5.10/GSM 04.08.
The PD and SAPI is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
PD and SAPI IEI octet 1
+-----+-----------------------------------------
0 0 SAPI PD
spare spare octet 2
+-----------------------------------------------+
Figure10.5.10/GSM 04.08:
PD and SAPI information element
Table 10.5.1.10/GSM 04.08: PD and SAPI information element
SAPI: Service Access Point Identifier (octet 2)
Bits
6 5
0 0 SAPI 0
0 1 reserved
1 0 reserved
1 1 SAPI 3
PD: Protocol Discriminator (octet 2)
bits 4-1
Encoded as specified in section 11.2.1 of 04.07.
10.5.1.11 Priority Level
The purpose of the Priority Level is to provide information defining the priority level requested or applied. The Priority
Level IE may be included in CM_SERVICE_REQUEST, CALL_PROCEEDING and SETUP messages.
The Priority Level information element is coded as shown in figure 10.5.11/GSM 04.08 and table 10.5.11/GSM 04.08.
ETSI
409 draft ETSI EN 300 940 V7.7.0 (2000-04)
The Priority Level is a type 1 information element with 1 octet length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Priority Level 0 call priority
IEI spare octet 1
+-----------------------------------------------+
Figure 10.5.11/GSM 04.08: Priority Level
Table 10.5.11/GSM 04.08: Priority Level
+-------------------------------------------------------+
Call priority (octet 1)
Bit
3 2 1

+-------------------------------------------------------+
10.5.2 Radio Resource management information elements
10.5.2.1a BA Range
The purpose of the BA Range information element is to provide the mobile station with ARFCN range information
which can be used in the cell selection procedure.
The BA Range information element is coded as shown in figure 10.5.12/GSM 04.08 and table 10.5.12/GSM 04.08.
The BA Range is a type 4 information element with a minimum length of 6 octets. No upper length limit is specified
except for that given by the maximum number of octets in a L3 message (see GSM 04.06).
ETSI
410 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
BA RANGE IEI octet 1

+-----------------------------------------------
Length of BA Range contents octet 2

+-----------------------------------------------
Number of Ranges octet 3

+-----------------------------------------------
RANGE1LOWER (high part) octet 4

+-----------------------------------------------
RANGE1LOWER RANGE1HIGHER octet 5
(low part) (high part)
+-----------------------------------------------
RANGE1HIGHER RANGE2LOWER octet 6
+-----------------------------------------------
+-----------------------------------------------
RANGE2HIGHER (low part) octet 8

+-----------------------------------------------
RANGE3LOWER (high part) octet 9

+-----------------------------------------------
+-----------------------------------------------
RANGE3HIGHER RANGE4LOWER octet 11
+-----------------------------------------------
+-----------------------------------------------
RANGE4HIGHER (low part) octet 13

+-----------------------------------------------
: : octet n
+-----------------------------------------------+
Figure 10.5.12/GSM 04.08: BA RANGE information element
ETSI
411 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.12/GSM 04.08: BA Range information element
+------------------------------------------------------+
Number of Ranges parameter
The number of Ranges parameter indicates in binary
the number of ranges to be transmitted in the IE. It
shall have a minimum value of 1.

RANGEi_LOWER

If $(impr-BA-range-handling)$ is not supported:
$begin
The RANGEiLOWER is coded as the binary representa-
tion of the ARFCN used as the lower limit of a range
of frequencies to be used by the mobile station in
cell selection (see GSM05.08 and GSM03.22)
$end

If $(impr-BA-range-handling)$ is supported:
$begin
The RANGEiLOWER is coded as the binary representa-
tion of the ARFCN used as the lower limit of a range
of frequencies which could be used by the mobile
station in cell selection (see GSM05.08 and
GSM03.22)
$end

RANGEiHIGHER
If $(impr-BA-range-handling)$ is not supported:
$begin
The RANGEiHIGHER is coded as the binary representa-
tion of the ARFCN used as the higher limit of a range
of frequencies to be used by the mobile station in
cell selection (see GSM05.08 and GSM03.22)
$end

$begin
The RANGEi HIGHER is coded as the binary representa-
tion of the ARFCN used as the higher limit of a
range of frequencies which could be used by the
mobile station in cell selection (see GSM 05.08 and
GSM 03.22)
$end

If the length of the BA range information element is
greater than the number of octets required to carry
the Number of Ranges given in octet 3, then any
unused octets or parts of octets at the end of the
IE shall be considered as spare.


If a mobile station receives range information
which has ranges or part of the ranges which are not
supported by the mobile station, the mobile station
shall take into account those parts of the ranges
which it does support.

+------------------------------------------------------+
10.5.2.1b Cell Channel Description
The purpose of the Cell Channel Description information element is to provide the reference frequency list to be used to
decode the mobile allocation information element.
The Cell Channel Description is a type 3 information element with 17 octets length.
There are several formats for the Cell Channel Description information element, distinguished by the "format indicator"
subfield. Some formats are frequency bit maps, the others use a special encoding scheme.
NOTE: No more than 64 RF channels should be encoded in the Cell Allocation since this is the maximum number
of RF channels which can be referenced in the Mobile Allocation IE.
ETSI
412 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.1b.1 General description
Figure 10.5.13/04.08 shows only a special bit numbering. The different general format is described in
table 10.5.13/04.08.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Cell Channel Description IEI octet 1
+-----+-----------------------------------------
0 0
Bit Bit spare spare Bit Bit Bit Bit octet 2
128 127 124 123 122 121
+-----+-----+-----+-----+-----+-----+-----+-----

Bit Bit Bit Bit Bit Bit Bit Bit octet 3
120 119 118 117 116 115 114 113
+-----+-----+-----+-----+-----+-----+-----+-----
+-----+-----+-----+-----+-----+-----+-----+-----

008 007 006 005 004 003 002 001
+-----------------------------------------------+
Figure 10.5.13/GSM 04.08: Cell Channel Description information element (general format)
ETSI
413 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.13/GSM 04.08: Cell Channel Description information element, general format
+-----------------------------------------------------+

FORMAT-ID, Format Identifier (Bit 128 and next)

The different formats are distinguished by the bits
of higher number. The possible values are the
following:

Bit Bit Bit Bit Bit format notation
128 127 124 123 122

0 0 X X X bit map 0
1 0 0 X X 1024 range
1 0 1 0 0 512 range
1 0 1 0 1 256 range
1 0 1 1 0 128 range
1 0 1 1 1 variable bit map

All other combinations are reserved for future use.
A GSM900 mobile station which only supports the
primary GSMband P-GSM900 (cf. GSM05.05)
may consider all values except the value for
bit map 0 as reserved.

The significance of the remaining bits depends on
the FORMAT-ID. The different cases are specified in
the next sections.

Mobile stations shall treat all ARFCNs in the set
{0, 1, 2 ... 1023} as valid ARFCN values even if
the mobile station is unable to transmit or receive
on that ARFCN.

+-----------------------------------------------------+
10.5.2.1b.2 Bit map 0 format
8 7 6 5 4 3 2 1
+-----------------------------------------------+
+-----------------------------------------------
0 0 0 0 CA CA CA CA
spare spare ARFCN ARFCN ARFCN ARFCN octet 2
FORMAT-ID 124 123 122 121
+-----------+-----+-----+-----+-----+-----+-----
CA CA CA CA CA CA CA CA
ARFCN ARFCN ARFCN ARFCN ARFCN ARFCN ARFCN ARFCN octet 3
120 119 118 117 116 115 114 113
+-----------------------------------------------
+-----+-----+-----+-----+-----+-----+-----+-----
CA CA CA CA CA CA CA CA
008 007 006 005 004 003 002 001
+-----------------------------------------------+
Figure 10.5.14/GSM 04.08: Cell Channel Description information element, bit map 0 format
ETSI
414 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.14/GSM 04.08: Cell channel Description information element, bit map 0 format
+-----------------------------------------------------+
CA ARFCN N, Cell Allocation Absolute RF Channel
Number N (octet 2 etc.)

For a RF channel with ARFCN = N belonging to the
cell allocation the CA ARFCN N bit is coded with a
"1"; N = 1, 2, .. , 124.

For a RF channel with ARFCN = N not belonging to
the cell allocation the CA ARFCN N bit is coded
with a "0"; N = 1, 2 .. , 124.

+-----------------------------------------------------+
10.5.2.1b.3 Range 1024 format
8 7 6 5 4 3 2 1
+-----------------------------------------------+
+-----------------------------------------------
1 0 0 0 0
FORMAT-ID spare spare FORMA F0 W(1) octet 2
T-ID (high part)
+-----------------------------------------------
W(1) (low part) octet 3
+-----------------------------------------------
W(2) (high part) octet 4
+-----------------------------------------------
W(2) W(3) octet 5
(low) (high part)
+-----------------------------------------------
W(3) W(4) octet 6
+-----------+-----------------------------------
W(4) W(5) octet 7
+-----------+-----------------------------------
W(5) W(6) octet 8
+-----------+-----------------------------------
W(6) W(7) octet 9
+-----------+-----------------------------------
W(7) W(8) octet 10
+-----------------------------------------------
W(8) W(9) octet 11
(low)
+-----------------------------------------------
W(10) W(11) octet 12
high
+-----------------------------------------------
W(11) W(12) octet 13
+-----------------------------------------------
W(12) (low part) W(13) (high part) octet 14
+-----------------------------------------------
+-----------------------------------------------
+-----------------------------------------------
W(15) W(16) octet 17
(low part)
+-----------------------------------------------+
Figure 10.5.15/GSM 04.08: Cell Channel Description information element (1024 range format)
ETSI
415 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.15/GSM 04.08: Cell Channel Description information element, range 1024 format
+---------------------------------------------------------+

F0, frequency 0 indicator (octet 2, bit 3):

0 ARFCN 0 is not a member of the set
1 ARFCN 0 is a member of the set

W(i), i from 1 to 16 (octet 2 to 17):

Each W(i) encodes a non negative integer in binary
format.

If W(k) is null, W(k+1) to W(16) must be null also.

Each non null W(k) allows to compute, together with
some previous W(i) the ARFCN F(k) of a frequency in
the set. The computation formulas are given in section
10.5.2.13.3.
+---------------------------------------------------------+
8 7 6 5 4 3 2 1
+-----------------------------------------------+
+-----------------------------------------------
1 0 0 0 1 0 0 ORIG-
FORMAT-ID spare spare FORMAT-ID ARFCN octet 2
high
+-----------------------------------------------
ORIG-ARFCN (middle part) octet 3
+-----------------------------------------------
ORIG- W(1) octet 4
ARFCN (high part)
low
+-----------------------------------------------
W(1) W(2) octet 5
+-----------+-----------------------------------
W(2) W(3) octet 6
+-----------+-----------------------------------
W(3) W(4) octet 7
+-----------------------------------------------
W(4) W(5) octet 8
low
+-----------------------------------------------
W(6) W(7) octet 9
high
+-----------------------------------------------
W(7) W(8) octet 10
+-----------------------------------------------
+-----------------------------------------------
W(9) W(10) octet 12
(low part)
+-----------------------------------------------
W(11) W(12) octet 13
(high part)
+-----------------------------------------------
+-----------------------------------------------
W(13) W(14) octet 15
(low part)
+-----------------------------------------------
W(15) W(16) octet 16
(high part)
+-----------------------------------------------
W(16) (low part) W(17) octet 17
+-----------------------------------------------+
Figure 10.5.16/GSM 04.08: Cell Channel Description information element (512 range format)
ETSI
416 draft ETSI EN 300 940 V7.7.0 (2000-04)
+---------------------------------------------------------+
ORIG-ARFCN, origin ARFCN (octet 2, 3 and 4)

This field encodes the ARFCN of one frequency
belonging to the set. This value is also used to
decode the rest of the element.


format.


the set. The computation formulas are given in section
10.5.2.13.4.

+---------------------------------------------------------+
8 7 6 5 4 3 2 1
+-----------------------------------------------+
+-----------------------------------------------
1 0 0 0 1 0 1 ORIG-
high
+-----------------------------------------------
+-----------------------------------------------
ORIG- octet 4
ARFCN W(1)
low (high part)
+-----+-----------------------------------------
W(1) W(2) octet 5
low
+-----------------------------------------------
W(3) W(4) octet 6
high
+-----------------------------------------------
+-----------------------------------------------
+-----------------------------------------------
W(6) W(7) W(8) octet 9
low high
+-----------------------------------------------
+-----------------------------------------------
W(9) W(10) W(11) octet 11
low (high part)
+-----------------------------------------------
+-----------------------------------------------
W(13) W(14)(high part) octet 13
+-----------------------------------------------
W(14) W(15) W(16) octet 14
low high
+----------------------------------------+------
W(16) W(17) W(18) octet 15
(low part) high
+----------------+-----------------------+------
W(18) W(19) W(20) octet 16
(low part) high
+----------------+-----------------------+------
W(20) W(21) 0 octet 17
(low part) Spare
+-----------------------------------------------+
Figure 10.5.17/GSM 04.08: Cell Channel Description information element, range 256 format
ETSI
417 draft ETSI EN 300 940 V7.7.0 (2000-04)
+---------------------------------------------------------+



format.


the set. The computation formulas are given in
section 10.5.2.13.5.

+---------------------------------------------------------+
8 7 6 5 4 3 2 1
+-----------------------------------------------+
+-----------------------------------------------
1 0 0 0 1 1 0 ORIG-
high
+-----------------------------------------------
ORIG-ARFCN octet 3
(middle part)
+-----------------------------------------------
ORIG- octet 4
ARFCN W(1)
low
+-----------------------------------------------
W(2) W(3) octet 5
(high part)
+-----------------------------------------------
+-----------------------------------------------
W(4) W(5) W(6) octet 7
low (high part)
+-----------------------------------------------
+-----------------------------------------------
W(8) W(9) octet 9
+-----------------------+-----------------------
W(10) W(11) octet 10
+-----------------------+-----------------------
W(12) W(13) octet 11
+-----------------------+-----------------------
W(14) W(15) octet 12
+-----------------------------------------------
W(16) W(17) W(18) octet 13
(high part)
+-----------------------------------------------
W(18) W(19) W(20) W(21) octet 14
low high
+-----------------------------------------------
W(21) W(22) W(23) octet 15
(low part)
+-----------------------------------------------
W(24) W(25) W(26) octet 16
(high part)
+-----------------------------------------------
W(26) W(27) W(28) 0 octet 17
low spare
+-----------------------------------------------+
Figure 10.5.18/GSM 04.08: Cell Channel Description information element, range 128 format
ETSI
418 draft ETSI EN 300 940 V7.7.0 (2000-04)
+---------------------------------------------------------+



format.


the set. The computation formulas are given in
section 10.5.2.13.6.
+---------------------------------------------------------+
10.5.2.1b.7 Variable bit map format
8 7 6 5 4 3 2 1
+-----------------------------------------------+
+-----------------------------------------------
1 0 0 0 1 1 1 ORIG-
high
+-----------------------------------------------
ORIG-ARFCN octet 3
(middle part)
+-----------------------------------------------
ORIG-
ARFCN RRFCN RRFCN RRFCN RRFCN RRFCN RRFCN RRFCN octet 4
low 1 2 3 4 5 6 7
+-----+-----+-----+-----+-----+-----+-----+-----
+-----+-----+-----+-----+-----+-----+-----+-----

RRFCN RRFCN RRFCN RRFCN RRFCN RRFCN RRFCN RRFCN octet 17
104 105 106 107 108 109 110 111
+-----------------------------------------------+
Figure 10.5.19/GSM 04.08: Cell Channel Description information element, variable bit map format
ETSI
419 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.19/GSM 04.08: Cell Channel Description information element, variable bit map format
+---------------------------------------------------------+

belonging to the set. This value is also used as
origin of the bit map to generate all other frequencies.

RRFCN N, relative radio frequency channel number N
(octet 4 etc.)

For a RF channel with ARFCN = (ORIG-ARFCN + N) mod 1024
belonging to the set, RRFCN N bit is coded with a
"1"; N = 1, 2, .. , 111

not belonging to the set, RRFCN N bit is coded with a
"0"; N = 1, 2, .. , 111
+---------------------------------------------------------+
10.5.2.1c BA List Pref
The purpose of the BA List Pref information element is to provide the mobile station with ARFCN information which
can be used in the cell selection/reselection procedure.
The BA List Pref is a type 4 information element with a minimum length of 3 octets. No upper length limit is specified
<BA List Pref>::=
<01110101>
<LENGTH OF BA LIST PREF : bit (8)>
{1 <RANGE LIMITS >}**0
{1 <BA FREQ : bit (10)>}**0
<spare padding>;
<RANGE LIMITS>::=
<RANGE LOWER : bit (10)>
<RANGE UPPER : bit (10)>;
The RANGE LOWER is coded as the binary representation of the ARFCN used as the lower limit of a range of
frequencies to be used by the mobile station in cell selection and reselection (see GSM 05.08 and GSM 03.22).
The RANGE HIGHER is coded as the binary representation of the ARFCN used as the higher limit of a range of
frequencies to be used by the mobile station in cell selection and reselection (see GSM 05.08 and GSM 03.22).
BA FREQ is coded as the binary representation of the ARFCN indicating a single frequency to be used by the mobile
station in cell selection and reselection (see GSM 05.08 and GSM 03.22).
10.5.2.2 Cell Description
The purpose of the Cell Description information element is to provide a minimum description of a cell, e.g. to allow the
mobile station to use its pre-knowledge about synchronization.
The Cell Description information element is coded as shown in figure 10.5.20/GSM 04.08 and
table 10.5.20/GSM 04.08.
The Cell Description is a type 3 information element with 3 octets length.
ETSI
420 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Cell Description IEI octet 1
+-----------------------------------------------
BCCH ARFCN
(high part) octet 2
NCC BCC
+-----------------------------------------------
octet 3
BCCH ARFCN (low part)
+-----------------------------------------------+
Figure 10.5.20/GSM 04.08: Cell Description information element
Table 10.5.20/GSM 04.08: Cell Description information element
+------------------------------------------------------+

NCC, PLMN colour code (octet 2)
The NCC field is coded as the binary
representation of the PLMN colour code (see TS.
GSM03.03)

BCC, BS colour code (octet 2)
The BCC field is coded as the binary
representation of the BS colour code (see TS.
GSM03.03).

BCCH ARFCN (octet 2, bits 7 and 8, and octet 3)

The BCCH ARFCN number field is coded as the
binary representation of the BCCH carriers
absolute RF channel number.

Range: 0 to 1023

+------------------------------------------------------+
10.5.2.3 Cell Options (BCCH)
The purpose of the Cell Options (BCCH) information element is to provide a variety of information about a cell.
The Cell Options (BCCH) information element is coded as shown in figure 10.5.21/GSM 04.08 and
table 10.5.21/GSM 04.08.
The Cell Options (BCCH) is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Cell Options (BCCH) IEI octet 1
+-----+-----------------------------------------
0 PWRC DTX RADIO-LINK-TIMEOUT
spare octet 2
+-----------------------------------------------+
Figure 10.5.21/GSM 04.08: Cell Options (BCCH) information element
10.5.2.3a Cell Options (SACCH)
The purpose of the Cell Options (SACCH) information element is to provide a variety of information about a cell.
The Cell Options (SACCH) information element is coded as shown in figure 10.5.22 /GSM 04.08 and
table 10.5.22/GSM 04.08.
The Cell Options (SACCH) is a type 3 information element with 2 octets length.
ETSI
421 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Cell Options (SACCH) IEI octet 1
+-----+-----------------------------------------
DTX PWRC DTX RADIO-LINK-TIMEOUT
octet 2
+-----------------------------------------------+
Figure 10.5.22/GSM 04.08: Cell Options (SACCH) information element
Table 10.5.21/GSM 04.08: Cell Options (BCCH) information element
+------------------------------------------------------+
PWRC Power control indicator (octet 2) Note 1
bit 7
0 PWRC is not set
1 PWRC is set

DTX, DTX indicator (octet 2) Note 3
Bit
6 5
0 0 The MSs may use uplink discontinuous
transmission
0 1 The MSs shall use uplink discontinuous
transmission
1 0 The MS shall not use uplink discontinuous
transmission

RADIO-LINKTIMEOUT (octet 2) Note 2
Bits
4 3 2 1
0 0 0 0 4
0 0 0 1 8
0 0 1 0 12
.
.
.
1 1 1 0 60
1 1 1 1 64
+------------------------------------------------------+
NOTE 1: The precise meaning of the PWRC parameter can be found in GSM 05.08.
NOTE 2: The precise meaning of RADIO-LINK-TIMEOUT parameter can be found in GSM 05.08.
NOTE 3: The DTX indicator field is not related to the use of downlink discontinuous transmission.
ETSI
422 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.22/GSM 04.08: Cell Options (SACCH) information element
+------------------------------------------------------+
PWRC Power control indicator (octet 2) Note 1
bit 7
0 PWRC is not set
1 PWRC is set

DTX, DTX indicator (octet 2) Note 3
Bit
8 6 5
0 0 0 The MS may use uplink discontinuous
transmission on a TCH-F. The MS shall not use
uplink discontinuous transmission on TCH-H.

0 0 1 The MS shall use uplink discontinuous

0 1 0 The MS shall not use uplink discontinuous

0 1 1 Note 4: The MS shall use uplink discontinuous
transmission on a TCH-F. The MS may use

1 0 0 The MS may use uplink discontinuous
transmission on a TCH-F. The MS may use

1 0 1 The MS shall use uplink discontinuous
transmission on a TCH-F. The MS shall use

1 1 0 The MS shall not use uplink discontinuous

1 1 1 Note 4: The MS may use uplink discontinuous
RADIO-LINKTIMEOUT (octet 2) Note 2
Bits
4 3 2 1
0 0 0 0 4
0 0 0 1 8
0 0 1 0 12
.
.
.
1 1 1 0 60
1 1 1 1 64
+------------------------------------------------------+
NOTE 1: The precise meaning of the PWRC parameter can be found in GSM 05.08.
NOTE 2: The precise meaning of RADIO-LINK-TIMEOUT parameter can be found in GSM 05.08.
NOTE 3: The DTX indicator field is not related to the use of downlink discontinuous transmission.
NOTE 4: These codes shall not be sent to mobile stations that implement an earlier version of this protocol in which
these codes were not defined.
10.5.2.4 Cell Selection Parameters
The purpose of the Cell Selection Parameters information element is to provide a variety of information about a cell.
The Cell Selection Parameters information element is coded as shown in figure 10.5.23/GSM 04.08 and
table 10.5.23/GSM 04.08.
The Cell Selection Parameters information element is a type 3 information element with 3 octets length.
ETSI
423 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Cell Selection Parameters IEI octet 1
+-----------------------------------------------
CELL-RESELECT MS-TXPWR-MAX-CCH octet 2
HYSTERESIS
+-----------------------------------------------
ACS NECI RXLEV-ACCESS-MIN octet 3

+-----------------------------------------------+
Figure 10.5.23/GSM 04.08: Cell Selection Parameters information element
ETSI
424 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.23/GSM 04.08: Cell Selection Parameters information element
+------------------------------------------------------+
CELL-RESELECT-HYSTERESIS (octet 2)
The usage of this information is defined in GSM
05.08
Bits
8 7 6
0 0 0 0 dB RXLEV hysteresis for LA re-selection

MS-TXPWR-MAX-CCH (octet 2)
The MS-TXPWR-MAX-CCH field is coded as the binary
representation of the "power control level" in TS
GSM05.05 corresponding to the maximum TX power
level an MS may use when accessing on a Control
Channel CCH. This value shall be used by the Mobile
Station according to GSM 05.08.

Range: 0 to 31.

RXLEV-ACCESS-MIN (octet 3)
The RXLEV-ACCESS-MIN field is coded as the binary
representation of the minimum received signal level
at the MS for which it is permitted to access the
system.

Range: 0 to 63. (See TS GSM05.08).

ACS, ADDITIONAL RESELECT PARAM IND (octet 3)
Bit 8:
In System Information type 3 message:
0 The SI 4 rest octets, if present, and SI 7
and SI 8 rest octets, if so indicated in the
SI 4 rest octets shall be used to derive the
value of PI and possibly C2 parameters and/or
other parameters
1 System information type 16 and 17 are
broadcast on the BCCH.
A mobile station which does not support System
information type 16 and 17 may consider this bit
as 0.

In System Information type 4 message:
0 The SI 4 rest octets, if present, shall be
used to derive the value of PI and possibly
C2 parameters and/or other parameters
1 The value of PI and possibly C2 parameters
and/or other parameters in a System
information type 7 or type 8 message shall
be used

NECI: HALF RATE SUPPORT (octet 3)
Bit 7:
0 New establishment causes are not supported
1 New establishment causes are supported
+------------------------------------------------------+
10.5.2.4a MAC Mode and Channel Coding Requested
The purpose of the MAC Mode and Channel Coding Requested information element is for the mobile station to indicate
to the network which channel coding rate the mobile station desires the network to use on the downlink.
The MAC Mode and Channel Coding Requested information element is coded as shown in figure 10.5.24/GSM 04.08
and table 10.5.24/GSM 04.08.
The MAC Mode and Channel Coding Requested is a type 1 information element.
ETSI
425 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+----------------------------------------------+
MAC Mode and MAC 0 octet 1
Chan Cod Req IEI mode CS
+----------------------------------------------+
Figure 10.5.24/GSM 04.08: MAC Mode and Channel Coding Requested information element
Table 10.5.24/GSM 04.08: MAC Mode and Channel Coding Requested information element
+------------------------------------------------------+
CS : Coding Scheme
This field indicates to network the channel coding
scheme (see GSM05.03) that the network should use
on the downlink. The field is encoded according to
the following table:
bits
2 1
0 0 CS 1
0 1 CS 2
1 0 CS 3
1 1 CS 4

MAC Mode (bits 3-4, octet 1)
This field is encoded the same as the MAC_MODE field
in the PACKET RESOURCE REQUEST message described in
GSM 04.60.
+------------------------------------------------------+
The purpose of the Channel Description information element is to provide a description of an allocable channel together
with its SACCH.
The Channel Description information element is coded as shown in figure 10.5.25/GSM 04.08 and
table 10.5.25/GSM 04.08.
The Channel Description is a type 3 information element with 4 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Channel Description IEI octet 1
+-----------------------------------------------
Channel type octet 2
and TDMA offset TN
+-----------------------------------------------
H=1-> MAIO (high part)
TSC +- H -+- - - - - --- - - - - - octet 3
ARFCN
0
H=0-> spare (high part)
+-----------------------------------------------
MAIO HSN
(low part)
+- - - - - --- - - - - - - - - - - - - - - - - - octet 4
ARFCN (low part)
+-----------------------------------------------+
Figure 10.5.25/GSM 04.08: Channel Description information element
ETSI
426 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.25/GSM 04.08: Channel Description information element
+------------------------------------------------------+
Channel type and TDMA offset (octet 2)
Bits
8 7 6 5 4
0 0 0 0 1 TCH/F + ACCHs
0 0 0 1 T TCH/H + ACCHs
0 0 1 T T SDCCH/4 + SACCH/C4 or CBCH (SDCCH/4)
0 1 T T T SDCCH/8 + SACCH/C8 or CBCH (SDCCH/8)

The T bits indicate the subchannel number coded in
binary.


The Channel Type and TDMA offset field shall be
ignored and all bits treated as spare when received
in a PDCH ASSIGNMENT COMMAND message. The sender
set the spare bits to the coding for TCH/F+ACCHs

TN, Timeslot number (octet 2)
The TN field is coded as the binary representation
of the timeslot number as defined in GSM05.10.

Range: 0 to 7.

The Timeslot number field shall be ignored and all
bits treated as spare when received in a PDCH
ASSIGNMENT COMMAND message. The sender sets the spare
bits as 000

TSC, Training Sequence Code (octet 3)
The TSC field is coded as the binary representation
of the Training Sequence code as defined in GSM
05.03
Range: 0 to 7.

H, Hopping channel (octet 3)
Bit
5
0 Single RF channel
1 RF hopping channel

Note: The value of H affects the semantics of the
channel selector field

Channel selector (octet 3 and 4)
H = "0": The channel selector field
consists of the absolute RF channel number

Octet 3
Bits
4 3
0 0 Spare
+------------------------------------------------------+
Continued
ETSI
427 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.25/GSM 04.08 (concluded): Channel Description information element
+------------------------------------------------------+
ARFCN, (octet 3, bits 2 and 1, and
octet 4, bits 8 to 1)
The ARFCN is coded as the binary representa-
tion of the absolute RF channel number

Range: 0 to 1023

H = "1": The channel selector field consists of the
mobile allocation index offset, MAIO, and
the hopping sequence number, HSN.

MAIO, (octet 3 bit 4 to 1 high part and
octet 4 bit 8 to 7 low part)
The MAIO field is coded as the binary rep-
resentation of the mobile allocation index
offset as defined in GSM05.02.

Range: 0 to 63.

HSN, (octet 4 bit 6 to 1)
The HSN field is coded as the binary repres-
entation of the hopping sequence number
as defined in GSM05.02
Range 0 to 63.
+------------------------------------------------------+
10.5.2.5a Channel Description 2
The purpose of the Channel Description 2 information element is to provide a description of an allocable channel
configuration together with its SACCH.
The Channel Description 2 information element is coded as shown in figure 10.5.26 /GSM 04.08 and
table 10.5.26/GSM 04.08.
The Channel Description 2 is a type 3 information element with 4 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Channel Description IEI octet 1
+-----------------------------------------------
and TDMA offset TN
+-----------------------------------------------
TSC +- H -+- - - - - --- - - - - - octet 3
ARFCN
0
+-----------------------------------------------
MAIO HSN
(low part)
+- - - - - --- - - - - - - - - - - - - - - - - - octet 4
ARFCN (low part)
+-----------------------------------------------+
Figure 10.5.26/GSM 04.08: Channel Description 2 information element
ETSI
428 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.26/GSM 04.08: Channel Description 2 information element
+------------------------------------------------------+
Bits
8 7 6 5 4
0 0 0 0 0 TCH/F + FACCH/F and SACCH/M at the
timeslot indicated by TN, and
additional bidirectional or
undirectional TCH/Fs and SACCH/Ms
according to the multislot allocation
information element

0 0 0 0 1 TCH/F + FACCH/F and SACCH/F
0 0 0 1 T TCH/H + ACCHs
0 0 1 T T SDCCH/4 + SACCH/C4 or CBCH (SDCCH/4)
0 1 T T T SDCCH/8 + SACCH/C8 or CBCH (SDCCH/8)

binary.

In the description below "n" is the timeslot number
indicated by TN. The description is valid only if
all the indicated timeslot numbers are in the range
0 to 7.

1 0 X X X TCH/F + FACCH/F and SACCH/M at the
time slot indicated by TN, and additional
bidirectional TCH/Fs and SACCH/Ms at other
timeslots according to the following:

X X X:
0 0 0 no additional timeslots
0 0 1 at timeslot n-1
0 1 0 at timeslot n+1, n-1
0 1 1 at timeslot n+1, n-1 and n-2
1 0 0 at timeslot n+1, n-1, n-2, and n-3
1 0 1 at timeslot n+1, n-1, n-2, n-3 and n-4
1 1 0 at timeslot n+1, n-1, n-2, n-3, n-4
and n-5
1 1 1 at timeslot n+1, n-1, n-2, n-3, n-4, n-5
and n-6

1 1 0 0 1
to
1 1 0 1 1 TCH/F + FACCH/F and SACCH/M at the time
slot indicated by TN and additional
unidirectional TCH/FDs and SACCH/MDs at
other timeslots according to the
following:
1 1 0 0 1 at timeslot n-1
1 1 0 1 0 at timeslot n+1, n-1
1 1 0 1 1 at timeslot n+1, n-1 and n-2

1 1 1 1 0 TCH/F + FACCH/F and SACCH/M at the time
slot indicated by TN and additional
bidirectional TCH/F and SACCH/M at
timeslot n+1 and unidirectional TCH/FD
and SACCH/MD at timeslot n-1


+------------------------------------------------------+
(continued...)
ETSI
429 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.26/GSM 04.08 (concluded): Channel Description information element
+------------------------------------------------------+
of the timeslot number as defined in TS GSM05.10.

Range: 0 to 7.

of the Training Sequence code as defined in TS GSM
05.03
Range: 0 to 7.

Bit
5
0 Single RF channel

Note: The value of H affects the semantics of the


Octet 3
Bits
4 3
0 0 Spare


Range: 0 to 1023


offset as defined in TS GSM05.02.

Range: 0 to 63.

as defined in TS GSM05.02
Range 0 to 63.
+------------------------------------------------------+
10.5.2.6 Channel Mode
The Channel Mode information element gives information of the mode on coding/decoding and transcoding. The exact
mode is determined by the contents of this IE and the channel type.
The Channel Mode information element is coded as shown in figure 10.5.27/GSM 04.08 and table 10.5.27/GSM 04.08.
The Channel Mode is a type 3 information element with 2 octets length.
ETSI
430 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Channel Mode IEI octet 1
+-----------------------------------------------

Mode octet 2
+-----------------------------------------------+
Figure 10.5.27/GSM 04.08: Channel Mode information element
Table 10.5.27/GSM 04.08: Channel Mode information element
+----------------------------------------------------------+
The mode field is encoded as follows:
(octet 2)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 signalling only
0 0 0 0 0 0 0 1 speech full rate or half rate version 1
0 0 0 0 1 1 1 1 data, 14.5 kbit/s radio interface rate

Other values are reserved for future use.

Note 1: The speech full rate or half rate version 3 is
also referred as the adaptive multi-rate full rate
or half rate speech version 1
+----------------------------------------------------------+
10.5.2.7 Channel Mode 2
The Channel Mode 2 information element gives information of the mode of coding/decoding and transcoding.
The Channel Mode 2 information element is coded as shown in figure 10.5.28/GSM 04.08 and
table 10.5.28/GSM 04.08.
The Channel Mode 2 is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Channel Mode 2 IEI octet 1
+-----------------------------------------------

Mode octet 2
+-----------------------------------------------+
Figure 10.5.28/GSM 04.08: Channel Mode 2 information element
ETSI
431 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.28/GSM 04.08: Channel Mode 2 information element
+----------------------------------------------------------+
The mode field is encoded as follows:
(octet 2)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 signalling only
0 0 0 0 0 1 0 1 speech half rate version 1


Note 1: The speech half rate version 3 is
also referred as the adaptive multi-rate
half rate speech version 1
+----------------------------------------------------------+
10.5.2.8 Channel Needed
The purpose of the Channel Needed information element is to indicate to up to two mobile stations which type of
channel is needed (for each mobile station) for the transaction linked to the paging procedure.
The Channel Needed information element is coded as shown in figure 10.5.29/GSM 04.08 and
table 10.5.29/GSM 04.08.
The Channel Needed is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Channel Needed CHANNEL CHANNEL octet 1
IEI (second) (first)
+-----------------------------------------------+
Figure 10.5.29/GSM 04.08: Channel Needed information element
Table 10.5.29/GSM 04.08: Channel Needed information element
+--------------------------------------------------+
CHANNEL (octet 1)
Bits
2/4 1/3
0 0 Any channel.
0 1 SDCCH.
1 0 TCH/F (Full rate).
1 1 TCH/H or TCH/F (Dual rate).

If this information element is used for only one
mobile station, then the first CHANNEL field is
used and the second CHANNEL field is spare.
+--------------------------------------------------+
10.5.2.8a Channel Request Description
The purpose of the Channel Request Description information element is to indicate to the network the type of requested
uplink resources or to indicate the type of paging that is being responded to.
The Channel Request Description information element is coded as shown in figure 10.5.30/GSM 04.08 and
table 10.5.30/GSM 04.08.
The Channel Request Description is a type 3 information element with a length of 6 octets.
ETSI
432 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
Channel Request Description IEI octet 1
0 0 0 0 0 0 0
=0-> spare
MT/MO - - - - - - - - - -- - - - - - - --- - -- - - - - - - - - -- - - - - - - --- - - - - - - - - --- - - octet 2
Spare RLC LLC
=1-> priority mode frame
type
0 0 0 0 0 0 0 0
spare
Requested bandwidth (MSB-Value field) octet 3
0 0 0 0 0 0 0 0
Spare octet 4
Requested bandwidth (LSB-Value field)
0 0 0 0 0 0 0 0
Spare
RLC Octet Count (MSB-Value field) octet 5
0 0 0 0 0 0 0 0
Spare octet 6
RLC Octet Count (LSB-Value field)
Figure 10.5.30/GSM 04.08: Channel Request Description information element
ETSI
433 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.30/GSM 04.08: Channel Request Description information element details
MT/MO (bit 8, octet 2)
1 Mobile originated (MO)
0 Mobile terminated (MT)
PRIORITY (bits 3-4, octet 2)
When MT/MO indicates MO, this field indicates the priority of the requested TBF bit
4 3
0 0 Priority Level 1 (Highest priority)
0 1 Priority Level 2
1 0 Priority Level 3
1 1 Priority Level 4 (Lower priority)
RLC_MODE (bit 2, octet 2)
When MT/MO indicates MO, this field indicates the RLC mode of the requested TBF.
0 RLC acknowledged mode
1 RLC unacknowledged mode
LLC_FRAME_TYPE (bit 1, octet 2)
When MT/MO indicates MO, this field indicates the type of the first LLC frame to be transmitted over the requested
uplink TBF.
0 LLC frame is SACK or NACK
1 LLC frame is not SACK or NACK
REQUESTED_BANDWIDTH (16 bits field, octets 3 and 4) When MT/MO indicates MO, this field indicates the
useful uplink bandwidth requested in bit rate.
The bit rate field is the binary encoding of the rate information expressed in 100 bits/s, starting from 0 x 100 bits/s until
65535 x 100 bits/s.
The throughput granted by BSS may be higher to cope with protocol overhead and retransmissions.
RLC_OCTET_COUNT (16 bits field, octets 5 and 6)
When MT/MO indicates MO, this field indicates the number of octets of RLC data the mobile station wishes to transfer:
see GSM 04.60.
The purpose of the Cipher Mode Setting information element is to indicate whether stream ciphering shall be started or
not and if it is to be started, which algorithm to use.
The Cipher Mode Setting information element is coded as shown in figure 10.5.31/GSM 04.08 and
table 10.5.31/GSM 04.08.
The Cipher Mode Setting is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
algorithm octet 1
Ciph Mod Set IEI identifier SC
+-----------------------------------------------+
Figure 10.5.31/GSM 04.08: Cipher Mode Setting information element
ETSI
434 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.31/GSM 04.08: Cipher Mode Setting information element
+------------------------------------------------------+
algorithm identifier
If SC=1 then:
bits
4 3 2
0 0 0 cipher with algorithm A5/1
1 1 1 reserved

If SC=0 then bits 4, 3 and 2 are spare and set to "0"

SC (octet 1)
Bit
1
0 No ciphering
1 Start ciphering
+------------------------------------------------------+
10.5.2.10 Cipher Response
The Cipher Response information element is used by the network to indicate to the mobile station which information the
mobile station has to include in the CIPHERING MODE COMPLETE message.
The Cipher Response information element is coded as shown in figure 10.5.32/GSM 04.08 and
table 10.5.32/GSM 04.08.
The Cipher Response is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
0 0 0 octet 1
Cipher Resp. IEI Spare CR
+-----------------------------------------------+
Figure 10.5.32/GSM 04.08: Cipher Response information element
Table 10.5.32/GSM 04.08: Cipher Response information element
+------------------------------------------------------+
CR Cipher Response (octet 1)
Bit
1
0 IMEISV shall not be included
1 IMEISV shall be included
+------------------------------------------------------+
10.5.2.11 Control Channel Description
The purpose of the Control Channel Description information element is to provide a variety of information about a cell.
The Control Channel Description information element is coded as shown in figure 10.5.33/GSM 04.08 and
table 10.5.33/GSM 04.08.
The Control Channel Description is a type 3 information element with 4 octets length.
ETSI
435 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Control Channel Description IEI octet 1
+-----+-----------------------------------------
0 ATT octet 2
spare BS-AG-BLKS-RES CCCH-CONF
+-----+-----+-----------------+-----------------
0 0 0 0 0 BS-PA-MFRMS octet 3
spare spare spare spare spare
+-----------------------------------------------
T 3212 octet 4
time-out value
+-----------------------------------------------+
Figure 10.5.33/GSM 04.08: Control Channel Description information element
Table 10.5.33/GSM 04.08: Control Channel Description information element
+----------------------------------------------------------+
ATT, Attach-detach allowed (octet 2)
Bit
7
0 MSs in the cell are not allowed to apply
IMSI attach and detach procedure.
1 MSs in the cell shall apply IMSI attach
and detach procedure.

BS-AG-BLKS-RES (octet 2)
The BS-AG-BLKS-RES field is coded as the binary
representation of the number of blocks reserved for
access grant.

Range 0 to 2 if CCCH-CONF = "001"
0 to 7 for other values of CCCH-CONF

All other values are reserved in the first case

CCCH-CONF (octet 2)
bits
3 2 1
0 0 0 1 basic physical channel used for CCCH,
not combined with SDCCHs
combined with SDCCHs
1 1 0 4 basic physical channels used for CCCH,
all other values are reserved
+----------------------------------------------------------+
(continued....)
ETSI
436 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.33/GSM 04.08 (concluded): Control Channel Description information element
+-----------------------------------------------------+
BS-PA-MFRMS (octet 3)
Bits
3 2 1
0 0 0 2 multiframes period for transmission of
PAGING REQUEST messages to the same
paging subgroup
paging subgroup
. paging subgroup
.
.
paging subgroup

Note: The number of different paging subchannels on
the CCCH is:

MAX(1,(3 - BS-AG-BLKS-RES)) * BS-PA-MFRMS
if CCCH-CONF = "001"
(9 - BS-AG-BLKS-RES) * BS-PA-MFRMS
for other values of CCCH-CONF

T3212 timeout value (octet 4)
The T3212 timeout value field is coded as the
binary representation of the timeout value for
periodic updating in decihours.

Range: 1 to 255

The value 0 is used for infinite timeout value
i.e. periodic updating shall not be used within
the cell.
+-----------------------------------------------------+
10.5.2.12 Frequency Channel Sequence
The purpose of the Frequency Channel Sequence information element is to provide the absolute radio frequency
channel numbers used in the mobile hopping sequence. This information element shall only be used for radio frequency
channels in the primary GSM band (see GSM 05.05).
The Frequency Channel Sequence information element is coded as shown in figure 10.5.34/GSM 04.08 and
table 10.5.34/GSM 04.08.
The Frequency Channel Sequence is a type 3 information element with 10 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Frequency Channel Sequence IEI octet 1
+-----+-----------------------------------------
0 Lowest ARFCN octet 2
spare
+-----------------------------------------------
inc skip of ARFCN 01 inc skip of ARFCN 02 octet 3

+-----------------------+-----------------------
:
:
:
+-----------------------+-----------------------
inc skip of ARFCN 15 inc skip of ARFCN 16 octet 10

+-----------------------------------------------+
Figure 10.5.34/GSM 04.08: Frequency Channel Sequence information element
ETSI
437 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.34/GSM 04.08: Frequency Channel Sequence information element
+------------------------------------------------------+
Lowest ARFCN (octet 2)
The lowest ARFCN field is coded as the binary
representation of the lowest absolute RF channel
number appearing in the sequence of channels used in
the frequency hopping.

Range: 1 to 124


Increment skip ARFCN n (octet 3 to 10)
The increment skip ARFCN n is coded as the binary
representation of the increment of the preceding
absolute RF channel number appearing in the sequence
of channels used in the frequency hopping:
n = 1,...,16.

Range: 0 to 15

The value 0 indicates that the increment value is 15
but the concerned channel is not used and the next
field, i.e. Increment skip ARFCN n+1 (if present)
must be added to the increment to determine the next
absolute RF channel number in the sequence of
channels used in the frequency hopping.
+------------------------------------------------------+
10.5.2.13 Frequency List
The purpose of the Frequency List information element is to provide the list of the absolute radio frequency channel
numbers used in a frequency hopping sequence.
The Frequency List information element is a type 4 information element.
There are several formats for the Frequency List information element, distinguished by the "format indicator" subfield.
Some formats are frequency bit maps, the others use a special encoding scheme.
ETSI
438 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.13.1 General description
Table 10.5.35/GSM 04.08: Frequency List information element, general format
+-----------------------------------------------------+
FORMAT-ID, Format Identifier (part of octet 3)

The different formats are distinguished by the
FORMAT-ID field. The possible values are the
following:

Bit Bit Bit Bit Bit format notation
8 7 4 3 2

0 0 X X X bit map 0
1 0 0 X X 1024 range
1 0 1 0 0 512 range
1 0 1 0 1 256 range
1 0 1 1 0 128 range
1 0 1 1 1 variable bit map

All other combinations are reserved for future use.
A GSM900 mobile station which only supports the
primary GSMband P-GSM900 (cf. GSM05.05)
may consider all values except the value for
bit map 0 as reserved.

The significance of the remaining bits depends on
the FORMAT-ID. The different cases are specified in
the next sections.

+-----------------------------------------------------+
10.5.2.13.2 Bit map 0 format
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Frequency List IEI octet 1
+-----------------------------------------------
0 0 0 1 0 0 0 0 octet 2
Length of frequency list contents
+-----------------------------------------------
0 0 0 0
spare ARFCN ARFCN ARFCN ARFCN octet 3
FORMAT-ID 124 123 122 121
+-----------+-----------+-----+-----+-----+-----

120 119 118 117 116 115 114 113
+-----+-----+-----+-----+-----+-----+-----+-----
+-----+-----+-----+-----+-----+-----+-----+-----

008 007 006 005 004 003 002 001
+-----------------------------------------------+
Figure 10.5.35/GSM 04.08: Frequency List information element, bit map 0 format
ETSI
439 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.36/GSM 04.08: Frequency List information element, bit map 0 format
+-----------------------------------------------------+
ARFCN N, Absolute RF Channel
Number N (octet 3 etc.)

For a RF channel with ARFCN = N belonging to the
frequency list the ARFCN N bit is coded with a
"1"; N = 1, 2, .. , 124.

For a RF channel with ARFCN = N not belonging to
the frequency list the ARFCN N bit is coded
with a "0"; N = 1, 2 .. , 124.

+-----------------------------------------------------+
10.5.2.13.3 Range 1024 format
The information element contains a header, and W(1) to W(M) for some M. If, due to octet boundaries, some bits are
not used at the end of the last octet, these bits must be set to 0.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
+-----------------------------------------------
octet 2
Length of Frequency List contents
+-----------------------------------------------
1 0 0 0 0
FORMAT-ID spare spare FORMA F0 W(1) octet 3
T-ID (high part)
+-----------------------------------------------
W(1) (low part) octet 4
+-----------------------------------------------
W(2) to W(3) are on 9 bits, when present
W(2k) to W(2k+1-1) are on 10-k bits when present
and so on
. .
. .
+-----------------------------------------------+
Figure 10.5.36/GSM 04.08: Frequency List information element (Range 1024 format)
ETSI
440 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.37/GSM 04.08: Frequency List information element, range 1024 format
+---------------------------------------------------------+

F0, frequency 0 indicator (octet 3, bit 3):

0 ARFCN 0 is not a member of the set
1 ARFCN 0 is a member of the set

W(i), i from 1 to M (octet 3 and next):

format.

If W(k) is null, W(i) for i>k must be null also.

the set. The first computation formulas are given
hereafter, with the following conventions:

Wi denotes W(i);
Fi denotes F(i);
+ indicates the natural integer addition;
* indicates the natural integer multiplication;
n mod m indicates the remainder of the euclidian
division of n by m, ie 0 = (n mod m) = m-1 and
there exists k such that n = (k*m) + (n mod m);

n smod m indicates the offset remainder of the
euclidian division of n by m, ie
1 = (n smod m) = m and there exists k such that
n = (k*m) + (n smod m);

F1 = W1
F2 = (W1 - 512 + W2) smod 1023
F3 = (W1 + W3) smod 1023
F4 = (W1 - 512 + (W2 - 256 + W4) smod 511) smod 1023
F5 = (W1 + (W3 - 256 + W5) smod 511) smod 1023
F6 = (W1 - 512 + (W2 + W6) smod 511) smod 1023
F7 = (W1 + (W3 + W7) smod 511) smod 1023
F8 = (W1 - 512 + (W2 - 256 + (W4 - 128 + W8 )
smod 255) smod 511) smod 1023
+---------------------------------------------------------+
(continued...)
ETSI
441 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.37/GSM 04.08 (concluded): Frequency List information element, range 1024 format
+---------------------------------------------------------+
F9 = (W1 + (W3 - 256 + (W5 - 128 + W9 )
F10 = (W1 - 512 + (W2 + (W6 - 128 + W10)
F11 = (W1 + (W3 + (W7 - 128 + W11)
F12 = (W1 - 512 + (W2 - 256 + (W4 + W12)
F13 = (W1 + (W3 - 256 + (W5 + W13)
F14 = (W1 - 512 + (W2 + (W6 + W14)
F15 = (W1 + (W3 + (W7 + W15)
F16 = (W1 - 512 + (W2 - 256 + (W4 - 128 +
(W8 - 64 + W16) smod 127)
+---------------------------------------------------------+
+---------------------------------------------------------+
More generally, the computation of F(K) can be done
with the following program, using ADA language
(declarative parts are skipped and should be obvious):

INDEX := K;
J := GREATESTPOWEROF2LESSEROREQUALTO(INDEX);
N := W(INDEX);
while INDEX>1 loop
if 2*INDEX < 3*J then
INDEX := INDEX - J/2; -- left child
N := (N + W(PARENT) - 1024/J - 1) mod
(2048/J - 1) + 1;
else -- right child
INDEX := INDEX - J;
N := (N + W(PARENT) - 1) mod (2048/J - 1) + 1;
end if;
J := J/2;
end loop;
F(K) := N;
+---------------------------------------------------------+
10.5.2.13.4 Range 512 format
ETSI
442 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
+-----------------------------------------------
octet 2
+-----------------------------------------------
1 0 0 0 1 0 0 ORIG-
high
+-----------------------------------------------
+-----------------------------------------------
ORIG- W(1) octet 5
ARFCN (high part)
low
+-----------------------------------------------
W(1) W(2) octet 6
+-----------+-----------------------------------
and so on
. .
. .
+-----------------------------------------------+
ETSI
443 draft ETSI EN 300 940 V7.7.0 (2000-04)
+---------------------------------------------------------+



format.



Wi denotes W(i); W0 denotes the value of ORIG-ARFCN
Fi denotes F(i);

n = (k*m) + (n smod m);

F1 = (W0 + W1) mod 1024
F2 = (W0 + (W1 - 256 + W2) smod 511) mod 1024
F3 = (W0 + (W1 + W3) smod 511) mod 1024
F4 = (W0 + (W1 - 256 + (W2 - 128 + W4) smod 255)
smod 511) mod 1024
F5 = (W0 + (W1 + (W3 - 128 + W5) smod 255)
smod 511) mod 1024
F6 = (W0 + (W1 - 256 + (W2 + W6) smod 255)
smod 511) mod 1024
F7 = (W0 + (W1 + (W3 + W7) smod 255)
smod 511) mod 1024
F8 = (W0 + (W1 - 256 + (W2 - 128 + (W4 - 64 + W8 )
smod 127) smod 255) smod 511) mod 1024
F9 = (W0 + (W1 + (W3 - 128 + (W5 - 64 + W9 )
+---------------------------------------------------------+
(continued...)
ETSI
444 draft ETSI EN 300 940 V7.7.0 (2000-04)
+---------------------------------------------------------+
F10 = (W0 + (W1 - 256 + (W2 + (W6 - 64 + W10)
F11 = (W0 + (W1 + (W3 + (W7 - 64 + W11)
F12 = (W0 + (W1 - 256 + (W2 - 128 + (W4 + W12)

F13 = (W0 + (W1 + (W3 - 128 + (W5 + W13)
F14 = (W0 + (W1 - 256 + (W2 + (W6 + W14)
F15 = (W0 + (W1 + (W3 + (W7 + W15)
F16 = (W0 + (W1 - 256 + (W2 - 128 + (W4 - 64 +
(W8 - 32 + W16)
smod 63) smod 127) smod 255) smod 511) mod 1024
F17 = (W0 + (W1 + (W3 - 128 + (W5 - 64 +
(W9 - 32 + W17)
+---------------------------------------------------------+
+---------------------------------------------------------+

INDEX := K;
N := W(INDEX);
while INDEX>1 loop
if 2*INDEX < 3*J then -- left child
INDEX := INDEX - J/2;
N := (N + W(PARENT) - 512/J - 1) mod
(1024/J - 1) + 1;
else -- right child
INDEX := INDEX - J;
N := (N + W(INDEX) - 1) mod (1024/J - 1) + 1;
end if;
J := J/2;
end loop;
F(K) := (W(0) + N) mod 1024;
+---------------------------------------------------------+
10.5.2.13.5 Range 256 format
ETSI
445 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
+-----------------------------------------------
octet 2
+-----------------------------------------------
1 0 0 0 1 0 1 ORIG-
high
+-----------------------------------------------
+-----------------------------------------------
ORIG- W(1) octet 5
ARFCN (high part)
low
+-----+-----------------------------------------
W(1) W(2) octet 6
low
+-----------------------------------------------
and so on
. .
. .
+-----------------------------------------------+
ETSI
446 draft ETSI EN 300 940 V7.7.0 (2000-04)
+--------------------------------------------------------------+


This field encodes the ARFCN of one frequency belonging to
the set. This value is also used to decode the rest of the
element.


Each W(i) encodes a non negative integer in binary format.



Fi denotes F(i);

n = (k*m) + (n smod m);

F1 = (W0 + W1) mod 1024
F2 = (W0 + (W1 - 128 + W2) smod 255) mod 1024
F3 = (W0 + (W1 + W3) smod 255) mod 1024
F4 = (W0 + (W1 - 128 + (W2 - 64 + W4) smod 127) smod 255)
mod 1024
F5 = (W0 + (W1 + (W3 - 64 + W5) smod 127) smod 255)
mod 1024
F6 = (W0 + (W1 - 128 + (W2 + W6) smod 127) smod 255)
mod 1024
F7 = (W0 + (W1 + (W3 + W7) smod 127) smod 255)
mod 1024
+--------------------------------------------------------------+
(continued...)
ETSI
447 draft ETSI EN 300 940 V7.7.0 (2000-04)
+--------------------------------------------------------------+

F8 = (W0 + (W1 - 128 + (W2 - 64 + (W4 - 32 + W8 ) smod 63)
smod 127) smod 255) mod 1024
F9 = (W0 + (W1 + (W3 - 64 + (W5 - 32 + W9 ) smod 63)
smod 127) smod 255) mod 1024
F10 = (W0 + (W1 - 128 + (W2 + (W6 - 32 + W10) smod 63)
smod 127) smod 255) mod 1024
F11 = (W0 + (W1 + (W3 + (W7 - 32 + W11) smod 63)
smod 127) smod 255) mod 1024
F12 = (W0 + (W1 - 128 + (W2 - 64 + (W4 + W12) smod 63)
smod 127) smod 255) mod 1024
F13 = (W0 + (W1 + (W3 - 64 + (W5 + W13) smod 63)
smod 127) smod 255) mod 1024
F14 = (W0 + (W1 - 128 + (W2 + (W6 + W14) smod 63)
smod 127) smod 255) mod 1024
F15 = (W0 + (W1 + (W3 + (W7 + W15) smod 63)
smod 127) smod 255) mod 1024
F16 =(W0 + (W1 - 128 + (W2 - 64 + (W4 - 32 + (W8 - 16 + W16)
F17 =(W0 + (W1 + (W3 - 64 + (W5 - 32 + (W9 - 16 + W17)
F18 =(W0 + (W1 - 128 + (W2 + (W6 - 32 + (W10 - 16 + W18)
F19 =(W0 + (W1 + (W3 + (W7 - 32 + (W11 - 16 + W19)
F20 =(W0 + (W1 - 128 + (W2 - 64 + (W4 + (W12 - 16 + W20)
F21 =(W0 + (W1 + (W3 - 64 + (W5 + (W13 - 16 + W21)
+--------------------------------------------------------------+
+--------------------------------------------------------------+

INDEX := K;
N := W(INDEX);
while INDEX>1 loop
N := (N + W(INDEX) - 256/J - 1) mod
(512/J - 1) + 1;
else -- right child
INDEX := INDEX - J;
N := (N + W(INDEX) - 1) mod (512/J - 1) + 1;
end if;
J := J/2;
end loop;
F(K) := (W(0) + N) mod 1024;
+--------------------------------------------------------------+
10.5.2.13.6 Range 128 format
ETSI
448 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
+-----------------------------------------------
octet 2
+-----------------------------------------------
1 0 0 0 1 1 0 ORIG-
high
+-----------------------------------------------
+-----------------------------------------------
ORIG- W(1) octet 5
ARFCN (high part)
low
+-----+-----------------------------------------
and so on
. .
. .
+-----------------------------------------------+
ETSI
449 draft ETSI EN 300 940 V7.7.0 (2000-04)
+--------------------------------------------------------------+


This field encodes the ARFCN of one frequency belonging to
the set. This value is also used to decode the rest of the
element.


Each W(i) encodes a non negative integer in binary format.



Fi denotes F(i);

n = (k*m) + (n smod m);

F1 = (W0 + W1) mod 1024
F2 = (W0 + (W1 - 64 + W2) smod 127) mod 1024
F3 = (W0 + (W1 + W3) smod 127) mod 1024
F4 = (W0 + (W1 - 64 + (W2 - 32 + W4) smod 63) smod 127)
mod 1024
F5 = (W0 + (W1 + (W3 - 32 + W5) smod 63) smod 127)
mod 1024
F6 = (W0 + (W1 - 64 + (W2 + W6) smod 63) smod 127)
mod 1024
F7 = (W0 + (W1 + (W3 + W7) smod 63) smod 127)
mod 1024
+--------------------------------------------------------------+
(continued...)
ETSI
450 draft ETSI EN 300 940 V7.7.0 (2000-04)
+--------------------------------------------------------------+
F8 = (W0 + (W1 - 64 + (W2 - 32 + (W4 - 16 + W8 ) smod 31)
smod 63) smod 127) mod 1024
F9 = (W0 + (W1 + (W3 - 32 + (W5 - 16 + W9 ) smod 31)
F10 = (W0 + (W1 - 64 + (W2 + (W6 - 16 + W10) smod 31)
F11 = (W0 + (W1 + (W3 + (W7 - 16 + W11) smod 31)
F12 = (W0 + (W1 - 64 + (W2 - 32 + (W4 + W12) smod 31)
F13 = (W0 + (W1 + (W3 - 32 + (W5 + W13) smod 31)
F14 = (W0 + (W1 - 64 + (W2 + (W6 + W14) smod 31)
F15 = (W0 + (W1 + (W3 + (W7 + W15) smod 31)
F16 = (W0 + (W1 - 64 + (W2 - 32 + (W4 - 16 + (W8 - 8 + W16)
F17 = (W0 + (W1 + (W3 - 32 + (W5 - 16 + (W9 - 8 + W17)
F18 = (W0 + (W1 - 64 + (W2 + (W6 - 16 + (W10 - 8 + W18)
F19 = (W0 + (W1 + (W3 + (W7 - 16 + (W11 - 8 + W19)
F20 = (W0 + (W1 - 64 + (W2 - 32 + (W4 + (W12 - 8 + W20)
F21 = (W0 + (W1 + (W3 - 32 + (W5 + (W13 - 8 + W21)
F22 = (W0 + (W1 - 64 + (W2 + (W6 + W(14 - 8 + W22)
F23 = (W0 + (W1 + (W3 + (W7 + (W15 - 8 + W23)
F24 = (W0 + (W1 - 64 + (W2 - 32 + (W4 - 16 + (W8 + W24)
F25 = (W0 + (W1 + (W3 - 32 + (W5 - 16 + (W9 + W25)
F26 = (W0 + (W1 - 64 + (W2 + (W6 - 16 + (W10 + W26)
F27 = (W0 + (W1 + (W3 + (W7 - 16 + (W11 + W27)
F28 = (W0 + (W1 - 64 + (W2 - 32 + (W4 + (W12 + W28
F29 = (W0 + (W1 + (W3 - 32 + (W5 + (W13 + W29
+--------------------------------------------------------------+
+--------------------------------------------------------------+


INDEX := K;
N := W(INDEX);
while INDEX>1 loop
N := (N + W(INDEX) - 128/J - 1) mod
(256/J - 1) + 1;
else -- right child
INDEX := INDEX - J;
N := (N + W(INDEX) - 1) mod (256/J - 1) + 1;
end if;
J := J/2;
end loop;
F(K) := (W(0) + N) mod 1024;
+--------------------------------------------------------------+
10.5.2.13.7 Variable bit map format
8 7 6 5 4 3 2 1
+-----------------------------------------------+
ETSI
451 draft ETSI EN 300 940 V7.7.0 (2000-04)
+-----------------------------------------------
octet 2
+-----------------------------------------------
1 0 0 0 1 1 1 ORIG-
(continued) high
+-----------------------------------------------
+-----------------------------------------------
ORIG-
ARFCN RRFCN RRFCN RRFCN RRFCN RRFCN RRFCN RRFCN octet 5
low 1 2 3 4 5 6 7
+-----+-----+-----+-----+-----+-----+-----+-----
+-----+-----+-----+-----+-----+-----+-----+-----

RRFCN RRFCN RRFCN RRFCN RRFCN RRFCN RRFCN RRFCN octet k
8k-40 8k-39 8k-38 8k-37 8k-36 8k-35 8k-34 8k-33
+-----+-----+-----+-----+-----+-----+-----+-----
+-----------------------------------------------+
Figure 10.5.40/GSM 04.08: Frequency List information element, variable bit map format
Table 10.5.41/GSM 04.08: Frequency List information element, variable bit map format
+---------------------------------------------------------+

This field encodes the ARFCN of one frequency belonging
to the set. This value is also used as origin of the
bit map to generate all the other frequencies.

RRFCN N, relative radio frequency channel number N
(octet 5 etc.)

belonging to the set, RRFCN N bit is coded with a
"1"; N = 1, 2, .. , 8M+7 with 1 = M = 127

not belonging to the set, RRFCN N bit is coded with a
"0"; N = 1, 2, .. , 8M+7 with 1 = M = 127
+---------------------------------------------------------+
10.5.2.14 Frequency Short List
The purpose of the Frequency Short List information element is to provide the list of the absolute radio frequency
channel numbers used in a frequency hopping sequence, in a small fixed length information element to obtain when
possible the HANDOVER COMMAND message in a single block.
The Frequency Short List information element is a type 3 information element of 10 octet length.
This element is encoded exactly as the Frequency List information element, except that it has a fixed length instead of a
variable length and does not contain a length indicator and that it shall not be encoded in bitmap 0 format.
10.5.2.14a Frequency Short List 2
The purpose of the Frequency Short List 2 information element is to provide the list of the absolute radio frequency
channel numbers used in a frequency hopping sequence, in a small fixed length information element to obtain the
SYSTEM INFORMATION TYPE 11 and NOTIFICATION FACCH messages in a single block.
The Frequency Short List information element is a type 3 information element of 8 octet length.
This element is encoded exactly as the Frequency List information element, except that it has a fixed length instead of a
variable length and does not contain a length indicator and that it shall not be encoded in bitmap 0 format.
ETSI
452 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.14b Group Channel Description
The purpose of the Group Channel Description information element is to provide a description of an allocable voice
group call or voice broadcast call channel together with its SACCH and that part of the RF channels belonging to the
cell allocation which is used in the mobile hopping sequence if applicable.
The Group Channel Description information element is coded as shown in figure 10.5.41/GSM 04.08 and
table 10.5.42/GSM 04.08.
The Group Channel Description is a type 4 information element with 4 to 13 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Group Channel Description IEI octet 1
+-----------------------------------------------
Length of mobile allocation contents octet 2
+-----------------------------------------------
and TDMA offset TN
+-----------------------------------------------
TSC +- H -+- - - - - --- - - - - - octet 4
ARFCN
0
+-----------------------------------------------
MAIO HSN
(low part)
+- - - - - --- - - - - - - - - - - - - - - - - - octet 5
ARFCN (low part)
+-----------------------------------------------
MA MA MA MA MA MA MA MA
C C C C C C C C octet 6
8n 8n-1 8n-2 8n-3 8n-4 8n-5 8n-6 8n-7
+-----------------------------------------------
+-----+-----+-----+-----+-----+-----+-----+-----
C C C C C C C C octet n+5
008 007 006 005 004 003 002 001
+-----------------------------------------------+
Figure 10.5.41/GSM 04.08: Group Channel Description information element
ETSI
453 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.42/GSM 04.08: Group Channel Description information element
+------------------------------------------------------+
Bits
8 7 6 5 4
0 0 0 0 1 TCH/FS + ACCHs (speech codec version 1)
0 0 0 1 T TCH/HS + ACCHs (speech codec version 1)
0 0 1 T T SDCCH/4 + SACCH/C4
0 1 T T T SDCCH/8 + SACCH/C8

binary.

All other values are reserved for future use.

of the timeslot number as defined in GSM05.10.

Range: 0 to 7.

of the Training Sequence code as defined in GSM
05.03
Range: 0 to 7.

Bit
5
0 Single RF channel

Note 1: The value of H affects the semantics of the

Note 2: If H=0, the information element terminates
with octet 5


Octet 4
Bits
4 3
0 0 Spare

Range: 0 to 1023


offset as defined in GSM05.02.

Range: 0 to 63.

as defined in GSM05.02
Range 0 to 63.

+------------------------------------------------------+
(Continued)
ETSI
454 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.42/GSM 04.08: (concluded) Group Channel Description information element
+------------------------------------------------------+
MA C i, Mobile allocation RF channel i (octet 4
etc.), i = 1, 2,..., NF
The MA C i bit indicates whether or not the Mobile
allocation frequency list includes the i'th
frequency in the cell allocation frequency list.
In the cell allocation frequency list the absolute
RF channel numbers are placed in increasing order of
ARFCN, except that ARFCN 0, if included in the set,
is put in the last position in the list,

For a RF channel belonging to the mobile allocation
the MA C i bit is coded with a "1"; i = 1, 2,...,
NF.

For a RF channel not belonging to the mobile
allocation the MA C i bit is coded with a "0"; i =
1, 2,..., NF.

If NF mod 8 <> 0 then bits NF to 8n in octet 4 must
be coded with a "0" in each.
+------------------------------------------------------+
ETSI
455 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.14c GPRS Resumption
The purpose of the GPRS Resumption information element is to indicate whether the network has successfully resumed
GPRS services or not.
The GPRS Resumption information element is coded as shown in figure 10.5.42/GSM 04.08 and
table 10.5.43/GSM 04.08.
The GPRS Resumption is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
GPRS resumption spare ACK octet 1
IEI 0 0 0
+-----------------------------------------------+
Figure 10.5.42/GSM 04.08: GPRS Resumption information element
Table 10.5.43/GSM 04.08: GPRS Resumption information element
The ACK field (1 bit) is the binary acknowledge of a successful resumption of GPRS services:
0 resumption of GPRS services not successfully acknowledged;
1 resumption of GPRS services successfully acknowledged.
10.5.2.15 Handover Reference
The purpose of the Handover Reference information element is to provide a handover reference value used for access
identification.
The Handover Reference information element is coded as shown in figure 10.5.43/GSM 04.08 and
table 10.5.44/GSM 04.08.
The Handover Reference is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Handover Reference IEI octet 1
+-----------------------------------------------
octet 2
Handover reference value
+-----------------------------------------------+
Figure 10.5.43/GSM 04.08: Handover Reference information element
Table 10.5.44/GSM 04.08: Handover Reference information element
+------------------------------------------------------+
Handover reference value (octet 2)
The handover reference value field is coded using
binary representation.

Range: 0 to 255.
+------------------------------------------------------+
10.5.2.16 IA Rest Octets
The IA Rest Octets information element contains spare bits and possibly either a packet uplink assignment construction,
a packet downlink assignment construction, a second part packet assignment construction or a frequency parameters,
before time construction.
ETSI
456 draft ETSI EN 300 940 V7.7.0 (2000-04)
The frequency parameters, before time construction combines a mobile allocation (see 10.5.2.21) and a MAIO (see the
channel description information element).
The IA Rest Octets information element is coded according to the syntax specified below and described in table
10.5.45/GSM 04.08.
The IA Rest Octets information element is a type 5 information element with 1-12 octets length.
<IA Rest Octets> ::=
{ LL
| LH
| HL
< Length of frequency parameters : bit (6) >
< Frequency Parameters, before time >
| HH
{ 00 < Packet Uplink Assignment >
| 01 < Packet Downlink Assignment >
| 1 < Second Part Packet Assignment : null > }
}
<spare padding>;
< Packet Uplink Assignment > ::=
{ 1
< TFI_ASSIGNMENT : bit (5) >
< POLLING : bit >
{ 0 -- Dynamic Allocation
< USF: bit (3) >
< USF_GRANULARITY : bit >
{ 0 | 1 < P0 : bit (4) >
< PR_MODE : bit (1) > }
| 1 -- Fixed Allocation
< ALLOCATION_BITMAP_LENGTH : bit (5) >
< ALLOCATION_BITMAP : bit (val(ALLOCATION_BITMAP_LENGTH) ) >
{ 0 | 1 < P0 : bit (4) >
< BTS_PWR_CTRL_MODE : bit (1) >
< PR_MODE : bit (1) > }
}
< CHANNEL_CODING_COMMAND : bit (2) >
< TLLI_BLOCK_CHANNEL_CODING : bit >
}
{ 0 | 1 < ALPHA : bit (4) >}
< GAMMA : bit (5) >
{ 0 | 1 < TIMING_ADVANCE_INDEX : bit (4) > }
{ 0 | 1 < TBF_STARTING_TIME : bit (16) > }
| 0 -- Single Block Allocation
{ 0 | 1 < ALPHA : bit (4) >}
< GAMMA : bit (5) >
0 1 -- See Note 1
< TBF_STARTING_TIME : bit (16) >
{ L | H < P0 : bit (4) >
< PR_MODE : bit (1) >}
} ;
< Packet Downlink Assignment > ::=
< TLLI : bit (32) >
{ 0 | 1
< TFI_ASSIGNMENT : bit (5) >
< RLC_MODE : bit >
ETSI
457 draft ETSI EN 300 940 V7.7.0 (2000-04)
{0 | 1 < ALPHA : bit (4) > }
< GAMMA : bit (5) >
< POLLING : bit >
< TA_VALID : bit (1) >
}
{ 0 | 1 < TIMING_ADVANCE_INDEX : bit (4) > }
{ 0 | 1 < TBF_STARTING_TIME : bit (16) > }
{ 0 | 1 < P0 : bit (4) >
< PR_MODE : bit (1) > } :
< Frequency Parameters, before time > ::=
{ null -- Length of frequency parameters = 0
| 0 0
< MAIO : bit (6) >
< Mobile Allocation : octet (val (Length of frequency parameters) 1)
};
NOTE 1: A Timing Advance index shall not be allocated at a Single Block allocation. A TBF Starting Time
shall be allocated at a Single Block allocation. The control bits set to fixed values to specify these
requirements in a way compatible with early GPRS mobile stations in release 97.
ETSI
458 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.45/GSM 04.08: IA Rest Octet information element
Packet Uplink Assignment
The POLLING field (1 bit) indicates if the MS is being polled for a PACKET CONTROL ACKNOWLEDGEMENT.
0 ; no action is required from MS.
1 : MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink block specified by
TBF Starting Time, on the assigned PDCH.
The TFI_ASSIGNMENT field (5 bit) is the binary representation of the Temporary Flow Identity, see GSM 04.60.
Range: 0 to 31.
The USF field (3 bit) is the binary representation of the uplink state flag, see GSM 04.60. Range: 0 to 7.
The USF_GRANULARITY field (1 bit) indicates the USF granularity to be applied by the mobile station when it is
assigned a TBF using Dynamic Allocation, see GSM 04.60:
0 the mobile station shall transmit one RLC/MAC block;
1 the mobile station shall transmit four consecutive RLC/MAC blocks.
The ALLOCATION_BITMAP_LENGTH field (5 bit) specifies the number of bits in the ALLOCATION_BITMAP.
Range 0 to 31.
The ALLOCATION_BITMAP field (variable length field) represents uplink radio blocks, each bit representing one
radio block. Each bit indicates whether the mobile station is permitted to transmit during the corresponding uplink radio
block. The bitmap describes a one dimensional array of block periods, indexed as follows:
block period[z]
z = n for n = 0 to L,
where:
L = number of bits in the ALLOCATION_BITMAP - 1;
z = block period relative to TBF_STARTING_TIME;
n = bit number index into the ALLOCATION_BITMAP, range 0 to L;
TBF_STARTING_TIME indicates the first block period of the assigned allocation
The value of each bit is encoded as:
0 block period[n] is not part of the assigned allocation
1 block period[n] is part of the assigned allocation
The CHANNEL_CODING_COMMAND field (2 bit) indicates the coding scheme to be used for transmission, see
GSM 05.03:
0 0 coding scheme 1, CS-1;
1 1 coding scheme 4, CS-4.
The TLLI_BLOCK_CHANNEL_CODING field (1 bit) indicates the channel coding to be used for RLC data block
comprising TLLI for contention resolution:
0 mobile station shall use CS-1;
1 mobile station shall use coding scheme as specified by the CHANNEL CODING
COMMAND field.
The ALPHA field (4 bit) is the binary representation of the parameter for MS output power control, see GSM 05.08:
0 0 0 0 = 0.0
0 0 0 1 = 0.1
: :
1 0 1 0 = 1.0
ETSI
459 draft ETSI EN 300 940 V7.7.0 (2000-04)
The GAMMA field (5 bit) is the binary representation of the parameter
CH
for MS output power control in units of
2 dB, see GSM 05.08.
The TIMING_ADVANCE_INDEX field (4 bit) is the binary representation of the timing advance index (TAI), see
GSM 05.10 and GSM 04.04. Range: 0 to 15.
The TBF_STARTING_TIME field (16 bit) defines a starting time for the packet uplink assignment. The TBF starting
time is coded using the same coding as the V format of the type 3 information element Starting Time (10.5.2.38).
P0 (4 bit field)
For description and encoding, see the Packet Uplink Assignment message in GSM 04.60.
BTS_PWR_CTRL_MODE (1 bit field)
PR_MODE (1 bit field)
Packet Downlink Assignment
The TLLI field (32 bit) is the binary representation of a TLLI. The coding of TLLI is left open for each administration
using the structure specified in GSM 03.03.
The TFI_ASSIGNMENT field (5 bit) is the binary representation of the Temporary Flow Identity, see GSM 04.60.
Range: 0 to 31.
The RLC_MODE field (1 bit) indicates the RLC mode, see GSM 04.60:
0 RLC acknowledged mode;
1 RLC unacknowledged mode.
The ALPHA field (4 bit) and the GAMMA field (5 bit) are the binary representations of the respective parameters
and
CH
for MS output power control, see Packet Uplink Assignment construction.
The POLLING field (1 bit) indicates if the MS is being polled for a PACKET CONTROL ACKNOWLEDGEMENT.
0 ; no action is required from MS.
1 : MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink block specified by
TBF Starting Time, on the assigned PDCH.
The TA_VALID field (1 bit) indicates the validity of the timing advance value given in the Timing Advance IE.
0 the timing advance value is not valid ;
1 the timing advance value is valid.
The TIMING_ADVANCE_INDEX field (4 bit) is the binary representation of the timing advance index (TAI), see
GSM 05.10 and GSM 04.04. Range: 0 to 15.
The TBF_STARTING_TIME field (16 bit) defines a starting time for the packet downlink assignment. The TBF
starting time is coded using the same coding as the V format of the type 3 information element Starting Time
(10.5.2.38).
P0 (4 bit field)
BTS_PWR_CTRL_MODE (1 bit field)
PR_MODE (1 bit field)
ETSI
460 draft ETSI EN 300 940 V7.7.0 (2000-04)
Second Part Packet Assignment
The presence of the Second Part Packet Assignment is the indication that this message is the second message of two
IMMEDIATE ASSIGNMENT messages in an assignment of an uplink or downlink Temporary Block Flow (TBF).
Frequency parameters, before time
Length of frequency parameters (6 bit field)
This field is coded as the binary representation of the number of octets occupied by the frequency parameters, before
time field. If this length is 0, the frequency parameters, before time is not present.
The MAIO field (6 bit field) is coded as the binary representation of the mobile allocation index offset. Range: 0 to 63.
The Mobile Allocation field (k octet field (k = Length of frequency parameters 1)) contains a bitmap referring to the
Cell Channel Description IE in SI 1 message. The length of the bitmap is 8k, where k = ((NF-1) div 8 + 1) and where
NF denotes the number of ARFCNs contained in the cell channel description. The different bit positions in the mobile
allocation bitmap are assigned indices i = 1 to 8k, starting with i = 8k in the most significant bit position and ending with
i = 1 in the least significant bit position. The bit position with index i corresponds to the i'th frequency in the cell
channel description arranged in ascending order of ARFCN (except that ARFCN = 0, if included, is put last) and
numbered from 1 to NF. Each bit position in the mobile allocation bitmap is coded:
0 RF channel not belonging to mobile allocation;
1 RF channel belonging to mobile allocation.
If NF mod 8 <> 0, then bit positions i = NF+1 to 8k in octet 3 shall each be coded with a "0".
10.5.2.17 IAR Rest Octets
The IAR Rest Octets information element contains only spare bits. Its purpose is to allow the upward compatible
introduction of new information on the AGCH in later phases.
The IAR Rest Octets information element is a type 5 information element with 4 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
IAR Rest Octets IEI octet 1
+-----+-----------------------------------------
0 0 1 0 1 0 1 1 octet 2
spare spare spare spare spare spare spare spare
+-----+-----+-----+-----+-----+-----+-----+-----
0 0 1 0 1 0 1 1 octet 3
+-----+-----+-----+-----+-----+-----+-----+-----
0 0 1 0 1 0 1 1 octet 4
+-----------------------------------------------+
Figure 10.5.44/GSM 04.08: IAR Rest Octets information element
10.5.2.18 IAX Rest Octets
The IAX Rest Octets information element contains only spare bits only. Its purpose is to allow the upward compatible
introduction of new information on the AGCH in later phases.
The IAX Rest Octets information element is a type 5 information element with 1-5 octets length.
ETSI
461 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
IAX Rest Octets IEI octet 1
+-----+-----------------------------------------
0 0 1 0 1 0 1 1 octet 2*
+-----+-----+-----+-----+-----+-----+-----+-----
0 0 1 0 1 0 1 1 octet 3*
+-----+-----+-----+-----+-----+-----+-----+-----
. .
. .
. .
+-----+-----+-----+-----+-----+-----+-----+-----
0 0 1 0 1 0 1 1 octet n*
+-----------------------------------------------+
Figure 10.5.45/GSM 04.08: IAX Rest Octets information element
10.5.2.19 L2 Pseudo Length
The L2 Pseudo Length information element indicates the number of octets following it in the message which are to be
interpreted in the scope of the phase 1 protocol, i.e. the total number of octets (excluding the Rest Octets) for which T,
V, TV, LV, or TLV formatting is used (reference Table 11.1/GSM 04.07).
The L2 Pseudo Length information element is the first part of e.g. SYSTEM INFORMATION messages which are
mentioned as exceptions in section 10.1. It occupies the first octet of such messages.
For any of the SYSTEM INFORMATION messages sent on the BCCH, a mobile station should ignore the contents of
the L2 Pseudo Length value contained in the L2 Pseudo Length information element. For some specific messages,
further requirements are specified in section 9.
The L2 Pseudo Length Information element is an element with 2 octets length:
8 7 6 5 4 3 2 1
+-----------------------------------------------+
L2 Pseudo Length IEI octet 1
+-----------------------------------------------
L2 Pseudo Length value 0 1 octet 2
+-----------------------------------------------+
Figure 10.5.46/GSM 04.08: L2 Pseudo Length information element
Table 10.5.46/GSM 04.08: L2 Pseudo Length information element
+--------------------------------------------------------------+
L2 pseudo length value (octet 2)

The coding of the L2 pseudo length value field is the binary
representation of the L2 pseudo length of the message
in which the L2 pseudo length information element occurs.

+--------------------------------------------------------------+
NOTE: bits 1 and 2 are not spare.
10.5.2.20 Measurement Results
The purpose of the Measurement Results information element is to provide the results of the measurements made by the
mobile station on the serving cell and the neighbour cells.
The Measurement Results information element is coded as shown in figure 10.5.47/GSM 04.08 and
table 10.5.47/GSM 04.08.
The Measurement Results is a type 3 information element with 17 octets length.
ETSI
462 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Measurement Results IEI octet 1
+-----+-----------------------------------------
BA- DTX RXLEV-FULL-SERVING-CELL octet 2
USED USED
+-----+-----+-----------------------------------
0 MEAS- RXLEV-SUB-SERVING-CELL octet 3
spare VALID
+-----+-----------------------------------------
0 NO-
spare NCELL
RXQUAL-FULL RXQUAL-SUB M octet 4
SERVING-CELL SERVING-CELL (high
part)
+-----------------------------------------------
NO-NCELL-M octet 5
(low part) RXLEV-NCELL 1
+-----------------------------------------------
BCCH-FREQ-NCELL 1 BSIC-NCELL 1 octet 6
(high part)
+-----------------------------------------------
BSIC-NCELL 1 RXLEV-NCELL 2 octet 7
+-----------------------------------------------
RXLEV
NCELL BSIC-NCELL octet 8
2 BCCH-FREQ-NCELL 2 2
(low (high part)
part)
+-----+-----------------------------+-----------
(continued..)
Figure 10.5.47/GSM 04.08: Measurement Results information element
+-----------------------+-----------------------
+-----------------------------------------------
RXLEV- BSIC-
NCELL 3 NCELL
BCCH-FREQ-NCELL 3 3 octet 10
(low part) (high
part)
+-----------------------------------------------
+-----------------------------------------------
RXLEV-NCELL 4 BCCH-FREQ-NCELL 4 octet 12
(low part)
+-----------------------------------------------
RXLEV-NCELL
BSIC-NCELL 4 5 octet 13
(high part)
+-----------------------------------------------
+-----------------------------------------------
BCCH- RXLEV
FREQ- NCELL
NCELL BSIC-NCELL 5 6 octet 15
5(low (high
part) part)
+-----------------------------------------------
+-----------------------------------------------
BCCH-FREQ- octet 17
NCELL 6 BSIC-NCELL 6
(low part)
+-----------------------------------------------+
Figure 10.5.47/GSM 04.08: Measurement Results information element (continued)
ETSI
463 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.47/GSM 04.08: Measurement Results information element
BA-USED (octet 2), the value of the BA-IND field of the neighbour cells description
information element or elements defining the BCCH allocation used for the coding of
BCCH-FREQ-NCELL fields. Range 0 to 1.
DTX-USED (octet 2) This bit indicates whether or not the mobile station used DTX during
the previous measurement period.
Bit 7
0 DTX was not used
1 DTX was used
RXLEV-FULL-SERVING-CELL and RXLEV-SUB-SERVING-CELL, (octets 2 and 3)
Received signal strength on serving cell, measured respectively on all slots and on a subset
of slots (see GSM 05.08)
The RXLEV-FULL-SERVING-CELL and RXLEV-SUB-SERVING-CELL fields are coded
as the binary representation of a value N. N corresponds according to the mapping defined
in GSM 05.08 to the received signal strength on the serving cell.
Range: 0 to 63
MEAS-VALID (octet 3)
This bit indicates if the measurement results for the dedicated channel are valid or not
Bit 7
0 The measurement results are valid
1 the measurement results are not valid
RXQUAL-FULL-SERVING-CELL and RXQUAL-SUB-SERVING-CELL (octet 4)
Received signal quality on serving cell, measured respectively on all slots and on a subset of
the slots (see TS. GSM 05.08)
(continued...)
ETSI
464 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.47/GSM 04.08: Measurement Results information element (continued)
CELL fields are coded as the binary representation of the received signal quality on the
serving cell.
Range: 0 to 7 (See GSM 05.08)
NO-NCELL-M, Number of neighbouring cell measurements (octets 4 and 5)
Bits
1 8 7
0 0 0 No neighbour cell measurement result
0 0 1 1 " " " "
0 1 0 2 " " " "
0 1 1 3 " " " "
1 0 0 4 " " " "
1 0 1 5 " " " "
1 1 0 6 " " " "
1 1 1 Neighbour cell information not available for serving cell
RXLEV-NCELL i, Received signal strength on the ith neighbouring cell (octet 5, 7, 8,
9, 10, 11, 12, 13, 14, 15 and 16)
The RXLEV-NCELL field is coded as the binary representation of a value N. N
corresponds according to the mapping defined in TS. GSM 05.08 to the received
signal strength on the ith neighbouring cell. See note 1 & 2.
Range: 0 to 63.
(continued...)
ETSI
465 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.47/GSM 04.08: Measurement Results information element (concluded)
BCCH-FREQ-NCELL i, BCCH carrier of the ith neighbouring cell (octet 6, 8,10, 12, 14,
15, 16 and 17)
The BCCH-FREQ-NCELL i field is coded as the binary representation of the position,
starting with 0, of the ith neighbouring cells BCCH carrier in the BCCH channel list. The
BCCH channel list is composed of one or two BCCH channel sub lists, each sub list is
derived from the set of frequencies defined by reference neighbour cells description
information element or elements. In the latter case the set is the union of the two sets
defined by the two neighbour cells description information elements.
In each BCCH channel sub list the absolute RF channel numbers are placed in increasing
order of ARFCN, except that ARFCN 0, if included in the set, is put in the last position in the
sub list. The BCCH channel list consists either of only the sub list derived from the
neighbour cells description information element(s) in System Information 2/5 (and possible
2bis/5bis) or of that sub list immediately followed by the sub list derived from the neighbour
cells description information element in System Information 2ter/5ter for the case System
Information 2ter/5ter is also received. If the set of ARFCNs defined by the reference
neighbour cells description information element or elements includes frequencies that the
mobile station does not support then these ARFCNs shall be included in the list.
The notation 2/5 etc. means that the rules above apply to the neighbour cells description
information elements received in System Information 2, 2bis and 2ter and to those received
in System Information 5, 5bis and 5ter separately.
See note 1 & 2.
Range: 0 to 31.
BSIC-NCELL i, Base station identity code of the ith neighbouring cell (octet 6, 7, 8, 9, 10,
11, 13, 15 and 17)
The BSIC-NCELL i field is coded as the binary representation of the base station identity
code of the ith neighbouring cell. See note 1 & 2.
Range: 0 to 63.
NOTE 1: If the field extends over two octets the highest numbered bit of the lowest
numbered octet is the most significant and the lowest numbered bit of the highest numbered
octet is the least significant.
NOTE 2: If NO-NCELL-M < 6 the remaining RXLEV-NCELL i, BS-FREQ-NCELL i and
BSIC-NCELL i fields (NO-NCELL-M < i <= 6) shall be coded with a "0" in each bit.
10.5.2.20a GPRS Measurement Results
The purpose of the GPRS Measurement Results information element is to provide the results of the GPRS measurements
made by the GPRS mobile station on the serving cell.
The GPRS Measurement Results information element is coded as shown in figure 10.5.48/GSM 04.08 and
table 10.5.48/GSM 04.08.
The GPRS Measurement Results is a type 3 information element with 3 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
GPRS Measurement Results IEI octet 1
+-----------------------------------------------
CVALUE RXQUAL octet 2
(high part)
+-----------------------------------------------
RXQ-L 0 SIGNVAR octet 3
(low) spare
+-----------------------------------------------+
Figure 10.5.48/GSM 04.08: GPRS Measurement Results information element
ETSI
466 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.48/GSM 04.08: GPRS Measurement Results information element
C_VALUE (octet 1), the value of the C parameter calculated by the GPRS mobile
station (see GSM 05.08). This field is encoded as the binary representation of the C
parameter value defined in GSM 05.08. Range 0 to 63.
RXQUAL (octets 1 and 2), contains the RXQUAL parameter field calculated by the
GPRS mobile station (see GSM 05.08). This field is encoded as defined in
GSM 05.08. Range 0 to 7.
SIGN_VAR (octet 3), contains the signal variance parameter SIGN_VAR calculated
by the mobile station (see GSM 05.08). This field is encoded as defined in GSM
04.60.
The purpose of the Mobile Allocation information element is to provide that part of the RF channels belonging to the
cell allocation (coded with a "1" in the cell channel description information element) which is used in the mobile
hopping sequence.
The Mobile Allocation information element is coded as shown in figure 10.5.49/GSM 04.08 and
table 10.5.49/GSM 04.08.
The Mobile Allocation is a type 4 information element with 3 to 10 octets length except for the cases specified in section
9.1.18.1 and 9.1.19.2.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Mobile Allocation IEI octet 1
+-----------------------------------------------
octet 2
Length of mobile allocation contents
+-----------------------------------------------
C C C C C C C C octet 3
8n 8n-1 8n-2 8n-3 8n-4 8n-5 8n-6 8n-7
+-----------------------------------------------
+-----+-----+-----+-----+-----+-----+-----+-----
C C C C C C C C octet n+2
008 007 006 005 004 003 002 001
+-----------------------------------------------+
Figure 10.5.49/GSM 04.08: Mobile Allocation information element
ETSI
467 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.49/GSM 04.08: Mobile Allocation information element
+------------------------------------------------------+
MA C i, Mobile allocation RF channel i (octet 3
etc.), i = 1, 2,..., NF
The MA C i bit indicates whether or not the Mobile
allocation frequency list includes the i'th
frequency in the cell allocation frequency list.
The cell allocation frequency list is derived from
the set of frequencies defined by the reference cell
channel description information element. NF denotes
the number of frequencies in the cell allocation
frequency list.
In the cell allocation frequency list the absolute
RF channel numbers are placed in increasing order of
ARFCN, except that ARFCN 0, if included in the set,
is put in the last position in the list,

For a RF channel belonging to the mobile allocation
the MA C i bit is coded with a "1"; i = 1, 2,...,
NF.

For a RF channel not belonging to the mobile
allocation the MA C i bit is coded with a "0"; i =
1, 2,..., NF.

If NF mod 8 <> 0 then bits NF to 8n in octet 3 must
be coded with a "0" in each.
+------------------------------------------------------+
10.5.2.21a Mobile Time Difference
A Mobile Time Difference information element encodes a time related to the synchronization difference between the
time bases of two base stations. This type of information is used in conjunction with the HANDOVER COMPLETE
message.
The Mobile Time Difference information element is coded as shown in figure 10.5.50/GSM 04.08 and
table 10.5.50/GSM 04.08.
The Mobile Time Difference information element is a type 4 information element with 5 octets length.
8 7 6 5 4 3 2 1
Mobile Time Difference IEI Octet 1
Length of Mobile Time difference contents Octet 2
Mobile Time Difference value (high) Octet 3
Mobile Time Difference value (contd) Octet 4
Mobile Time Difference value (low) 0
spare
0
spare
0
spare
Octet 5
Figure 10.5.50/GSM 04.08: Mobile Time Difference information element
Table 10.5.50/GSM 04.08: Mobile Time Difference information element
Mobile Time Difference value (octet 3, 4 and 5)
The coding of the Mobile Time Difference value field is the binary representation of the time difference in half bit
periods and modulo 2
21
half bit periods; 1/2 bit period = 24/13 s.
10.5.2.21aa MultiRate configuration
The MultiRate configuration information element gives all parameters related to a multi-rate speechcodec.
The MultiRate configuration information element is coded as shown in figure 10.5.2.47/GSM 04.08 and
table 10.5.2.47/GSM 04.08.
The MultiRate configuration is a type 4 information element with a minimum length of 4 octets and a maximum length
of 8 octets.
ETSI
468 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Multirate speech configuration IEI octet 1
+-----------------------------------------------
Length
octet 2
+-----------------------------------------------

MR version spare ICMI spare Start mode octet 3
+-----------------------------------------------

Parameters for multirate speech octet 4

octet n
+-----------------------------------------------+
Figure 10.5.2.47/GSM 04.08: MultiRate configuration information element
8 7 6 5 4 3 2 1
+-----------------------------------------------+

Set of AMR codec modes octet 4
+-----------------------------------------------+
Figure 10.5.2.47a/GSM 04.08: Parameters for multirate speech field for the MR version 1 when a set
with one codec mode is chosen
8 7 6 5 4 3 2 1
+-----------------------------------------------+

+-----------------------------------------------
Spare
0 0 Threshold 1 octet 5
+-----------------------------------------------
Spare
Hysteresis 1 0 0 0 0 octet 6
+-----------------------------------------------+
Figure 10.5.2.47b/GSM 04.08: Parameters for multirate speech field for the MR version 1 when a set
with two codec modes is chosen
8 7 6 5 4 3 2 1
+-----------------------------------------------+

+-----------------------------------------------
Spare
+-----------------------------------------------

Hysteresis 1 Threshold 2 octet 6
+-----------------------------------------------
Threshold Spare
2 (cont.) Hysteresis 2 0 0 octet 7 +-----------
------------------------------------+
Figure 10.5.2.47c/GSM 04.08: Parameters for multirate speech field for the MR version 1 when a set of
three codec modes is chosen
ETSI
469 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+

+-----------------------------------------------
Spare
+-----------------------------------------------

Hysteresis 1 Threshold 2 octet 6
+-----------------------------------------------
Threshold Threshold 3
2 (cont.) Hysteresis 2 octet 7
+-----------------------------------------------

Threshold (3) Hysteresis 3 octet 8
+-----------------------------------------------+
Figure 10.5.2.47d/GSM 04.08: Parameters for multirate speech field for the MR version 1 when a set of
four modes is chosen
ETSI
470 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.2.47/GSM 04.08: MultiRate configuration information element
Octet 3
Bits
8 7 6 Multirate speech version
0 0 1 Adaptive Multirate speech version 1
Other values reserved
Bit 5
0 Spare
Bit 4 Initial Codec Mode Indicator
0 The initial codec mode is defined by the implicit rule
provided in GSM 05.09
1 The initial codec mode is defined by the Start Mode field
Bit
3
0 Spare
Bits
2 1 Start Mode,
The initial codec mode is coded as in GSM 05.09 section
3.4.1
When Multirate speech version field indicates Adaptive Multirate speech
version 1 then the remaining fields are coded as follows:
THRj (6 bits), is coded as the binary representation of a value N. N
corresponds to the threshold of C/I in dB, as defined in GSM 05.09;
HYSTj (4 bits) is coded as the binary representation of the hysteresis value
associated to THRj, as defined in GSM 05.09.
j = 1 corresponds to the lowest value of threshold in dB, j = 2 to the second
lowest, j = 3 to the highest value.
ETSI
471 draft ETSI EN 300 940 V7.7.0 (2000-04)
Set of adaptive multirate codec modes field (octet 4)
Bit
8
0 12,2 kbit/s codec rate is not part of the subset;
1 12,2 kbit/s codec rate is part of the subset;
Bit
7
Bit
6
Bit
5
Bit
4
Bit
3
Bit
2
Bit
1
10.5.2.21b Multislot Allocation
The purpose of the Multislot Allocation information element is to provide a description of which channels are used in
downlink and uplink respectively, in a multislot configuration. It also groups the channels into channel sets, the channel
mode for each channel set can be defined by a separate information element.
The Multislot Allocation information element is coded as shown in figure 10.5.51/GSM 04.08 and
table 10.5.51/GSM 04.08.
The multislot allocation information element is a type 4 information element with a minimum length of 3 octets and a
maximum length of 12 octets.
ETSI
472 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Multislot alloction IEI octet 1
+-----------------------------------------------

Length of the multislot allocation contents octet 2
+-----+-----+-----+-----+-----+-----+-----+-----
0/1 DA DA DA DA DA DA DA octet 3
ext 7 6 5 4 3 2 1
+-----+-----+-----+-----+-----+-----+-----+-----
1 UA UA UA UA UA UA UA octet 3a*
ext 7 6 5 4 3 2 1
+-----------------------------------------------

Channel set 1 octet 4*
+-----------------------------------------------

+-----------------------------------------------

: :
: :
+-----------------------------------------------+
Figure 10.5.51/GSM 04.08: Multislot Allocation information element
ETSI
473 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.51/GSM 04.08: Multislot allocation information element
+------------------------------------------------------+
DA 1-7, Downlink assignment (octet 3)

Indicates additional downlink channel allocation.
If bit DA n is set to "1" this indicates that
timeslot TN = (n + TNm)mod8 is assigned. If bit DA n
is set to "0" the corresponding timeslot is not
assigned. TNm is the timeslot number of the main
link.

UA 1-7, Uplink assignment (octet 3a)

Indicates additional uplink channel allocation.
If bit UA n is set to "1" this indicates that
timeslot TN = (n + TNm)mod8 is assigned. If bit UA n
is set to "0" the corresponding timeslot is not
assigned. TNm is the timeslot number of the main
link.

If octet 3a is not included the timeslots indicated
by octet 3 are allocated in both downlink and uplink
direction.

Note1: Allocation of timeslots only in uplink is FFS.
Note2: In combination with the channel description
IE, all types of channels can be indicated.
The channel carrying the main signalling link
(indicated by the channel description IE is of
type 1 (see below)), all other channels
allocated both in downlink and uplink are of
type 2 and channels with allocation in only
one direction are of type 3.

Type 1: TCH/F + FACCH/F + SACCH/M bidirectional
Type 2: TCH/F + SACCH/M bidirectional
Type 3: TCH/F + SACCH/M unidirectional

Channel set n (octet 4 to 11 (if included))
If octets 4-11 are omitted, all channels belong
to channel set 1.

If bit m of Channel set n is set to "1" then timeslot
m-1 is included in channel set n.
If bit m of Channel set n is set to "0" then timeslot
m-1 is not included in channel set n.

Each allocated timeslot, including the timeslot
carrying the main signalling link, shall be included
in one (and only one) channel set.
+------------------------------------------------------+
10.5.2.21c NC mode
The purpose of the NC mode information element is for the network to inform the mobile station of the NC mode to be
implemented on the target cell.
The NC mode information element is coded as shown in figure 10.5.52/GSM 04.08 and table 10.5.52/GSM 04.08.
The NC mode is a type 1 information element.
8 7 6 5 4 3 2 1
+----------------------------------------------+
0 0 octet 1
NC mode IEI spare NC mode
+----------------------------------------------+
Figure 10.5.52 /GSM 04.08: NC mode information element
ETSI
474 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.52/GSM 04.08: NC Mode information element
+------------------------------------------------------+
NC mode
This field indicates to the mobile the NC mode for
the target cell (see GSM04.60). The field is encoded
according to the following table:
bits
2 1
0 0 NC 0
0 1 NC 1
1 0 NC 2
1 1 information on NC mode to be gathered from the
target cell
+------------------------------------------------------+
10.5.2.22 Neighbour Cells Description
The purpose of the Neighbour Cells Description information element is to provide the absolute radio frequency channel
numbers of the BCCH carriers to be monitored by the mobile stations in the cell.
The Neighbour Cells Description information element is coded as the Cell Channel Description information element, as
specified in section 10.5.2.1b, with the exception of bits 5 and 6 of octet 2. figure 10.5.53/GSM 04.08 and
table 10.5.53/GSM 04.08 contains the difference of specifications.
The Neighbour Cells Description information element is a type 3 information element with 17 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Neighbour Cells Description IEI octet 1
+-----+-----------------------------------------
EXT- BA-
Bit Bit IND IND Bit Bit Bit Bit octet 2
128 127 124 123 122 121
+-----+-----+-----+-----+-----+-----+-----+-----

120 119 118 117 116 115 114 113
+-----+-----+-----+-----+-----+-----+-----+-----
+-----+-----+-----+-----+-----+-----+-----+-----

008 007 006 005 004 003 002 001
+-----------------------------------------------+
Figure 10.5.53/GSM 04.08: Neighbour Cells Description information element
ETSI
475 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.53/GSM 04.08: Neighbour Cells Description information element
EXT-IND, Extension indication (octet 2, bit 6)
If received in System Information 2, 2bis, 5 or 5bis this bit indicates whether the
information element carries the complete information of a BCCH channel sub list or
whether a complementary information element is sent in another message.
A GSM 900 mobile station which only supports the primary GSM band P-GSM 900
(cf. GSM 05.05) may consider this bit as a spare bit and assume that the information
element carries the complete BA, see section 3.2.2.1.
NOTE: This indicator is set to 1 in the neighbour cells description information
elements in System Information 2 and 2bis and 5 and 5bis respectively when more
than one is needed to describe a BCCH channel sub list.
Bit 6
0 The information element carries the complete BA
1 The information element carries only a part of the BA
BA-IND, BCCH allocation sequence number indication (octet 2). Range 0 to 1
The BA-IND is needed to allow the network to discriminate measurements results
related to different BAs (e.g. BA(BCCH) and BA(SACCH)) sent to the
MS.
10.5.2.22a Neighbour Cells Description 2
The purpose of the Neighbour Cells Description 2 information element is to provide the absolute radio frequency
channel numbers of the BCCH carriers to be monitored by the mobile stations in the cell.
The Neighbour Cells Description 2 information element is coded as the Cell Channel Description information element,
as specified in section 10.5.2.1b, with the exception of bits 5 to 7 of octet 2. figure 10.5.54/GSM 04.08 and
The Neighbour Cells Description 2 information element is a type 3 information element with 17 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Neighbour Cells Description IEI octet 1
+-----+-----------------------------------------
Multiband BA
Bit reporting IND Bit Bit Bit Bit octet 2
128 124 123 122 121
+-----+-----+-----+-----+-----+-----+-----+-----

120 119 118 117 116 115 114 113
+-----+-----+-----+-----+-----+-----+-----+-----
+-----+-----+-----+-----+-----+-----+-----+-----

008 007 006 005 004 003 002 001
+-----------------------------------------------+
Figure 10.5.54/GSM 04.08: Neighbour Cells Description 2 information element
ETSI
476 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.54/GSM 04.08: Neighbour Cells Description 2 information element
Octet 2 bit 8, 4, 3 and 2
FORMAT-ID, Format Identifier (Bit 128 and next)
The different formats are distinguished by the bits of higher number. As an exception to the general format for the
neighbour cell description the format ID is coded as follows :
Bit Bit Bit Bit format notation
128 124 123 122
0 X X X bit map 0
1 0 X X 1024 range
1 1 0 0 512 range
1 1 0 1 256 range
1 1 1 0 128 range
1 1 1 1 variable bit map
Bits 6 and 7 of Octet 2
Multiband reporting
Binary encoding of multiband reporting parameter as specified in GSM 05.08.
Range: 0 to 3
Bit 5 of octet 2
BA-IND, BCCH allocation sequence number indication.
The BA-IND is needed to allow the network to discriminate measurements results related to different BAs (e.g.
BA(BCCH) and BA(SACCH)) sent to the MS.
Range 0 to 1.
10.5.2.22c NT/N Rest Octets
NT/N Rest Octets ::=
{0 I 1<NLN(PCH) : bit (2)>}
<list of Group Call NCH information>
<Spare padding>;
<List of Group Call NCH information> ::=
0 | 1 <Group Call information> <List of Group Call NCH information> ;
NLN(PCH)
This field gives the NLN value to be used as specified in 3.3.3
<Group Call information>
See clause 9.1.21a
The P1 Rest Octets information element contains information about the status of information on an existing NCH,
priority levels and packet page indications applied for mobile station identities and spare bits.
The P1 Rest Octets information element is a type 5 information element with 1-18 octets length.
<P1 Rest Octets> ::=
{L I H <NLN(PCH) : bit (2)> <NLN status : bit>}
{L I H <Priority1 ::= Priority>}
ETSI
477 draft ETSI EN 300 940 V7.7.0 (2000-04)
{L | H <Group Call information>}
< Packet Page Indication 1 : {L | H} >
<spare padding>;
<Priority> ::= <bit (3)>;
<Group Call information>
See clause 9.1.21a
NOTE 1: The value 17h shall not be used as a value of the first octet when this information element is used in the
PAGING REQUEST TYPE 1 message. This will prevent mobile stations misinterpreting this information
as the Mobile Identity IEI.
Table 10.5.55/GSM 04.08: P1 Rest Octets information element
NLN(PCH) Notification List Number
The presence of the NLN(PCH) field indicates that if an NCH is present, reduced NCH monitoring can be used, and
gives the NLN(PCH) value, to be used as specified in 3.3.3.
Priority: Priority i relates to Mobile Station Identity i (i = 1, 2)
The Packet Page Indication i field relates to Mobile Station Identity i (i = 1, 2) and indicates the kind of paging
procedure associated with the mobile station identity. If the identity is not IMSI the Packet Page Indication has no
meaning and is ignored.
L paging procedure for RR connection establishment;
H packet paging procedure.
The P2 Rest Octets information element contains information on the channel needed by the network and information
about the status of information on an existing NCH, priority levels and packet page indications applied for mobile
station identities and spare bits.
The P2 Rest Octets information element is a type 5 information element with 2-12 octets length.
ETSI
478 draft ETSI EN 300 940 V7.7.0 (2000-04)
{L I H <CN3: bit (2)>}
{L I H <NLN : bit (2)> <NLN status : bit>}
<spare padding>;
<Priority> ::= <bit(3)>;
NOTE 1: The value 17h shall not be used as a value of the first octet when this information element is used in the
PAGING REQUEST TYPE 2 message. This will prevent mobile stations misinterpreting this information
as the Mobile Identity IEI.
CN3 Channel Needed for Mobile Identity 3
The values and semantics used in the CN3 field are those of the CHANNEL field of Channel Needed IE (see 10.5.2.8).
The CN3 field is associated with the Mobile Identity 3 IE of the PAGING REQUEST TYPE 2 message.
If the CN3 field is not present, the default value is 00 (any channel).
NLN Notification List Number
See P1 Rest Octets.
Priority: Priority i relates to Mobile Station Identity i (i = 1, 2, 3)
The Packet Page Indication 3 field relates to Mobile Station Identity 3 and indicates the kind of paging procedure
associated with the mobile station identity. If the identity is not IMSI the Packet Page Indication has no meaning and is
ignored.
L paging procedure for RR connection establishment;
H packet paging procedure.
The P3 Rest Octets information element contains information on the channel needed by the network and information
about the status of information on an existing NCH, priority levels applied for mobile station identities and spare bits.
The purpose of the spare bits is to allow the upward compatible introduction of new information on the PCH in later
phases.
The P3 Rest Octets information element is a type 5 information element with 4 octets length.
ETSI
479 draft ETSI EN 300 940 V7.7.0 (2000-04)
{L I H <CN3 : bit (2)> <CN4 : bit (2)>}
{L I H <NLN : bit (2)> <NLN status : bit>}
<spare padding>;
<Priority> ::= <bit(3)>;
+----------------------------------------------------------+
The values and semantics used in the CN3 field are those
of the CHANNEL field of Channel Needed IE (see 10.5.2.8).
The CN3 field is associated with the Mobile Identity 3
IE of the PAGING REQUEST TYPE 3 message.

If the CN3 field is not present, the default value is
00 (any channel)

The values and semantics used in the CN43 field are those
of the CHANNEL field of Channel Needed IE (see 10.5.2.8).
The CN4 field is associated with the Mobile Identity 4
IE of the PAGING REQUEST TYPE 3 message.

If the CN4 field is not present, the default value is
00 (any channel)

NLN Notification List Number
See P1 Rest Octets

Priority: Priority i relates to Mobile Station Identity i
i (i = 1,2,3,4)

+----------------------------------------------------------+
10.5.2.25a Packet Channel Description
The purpose of the Packet Channel Description information element is to provide a description of a packet data physical
channel (PDCH).
The Packet Channel Description information element is coded according to the syntax specified below and described in
table 10.58/GSM 04.08.
The Packet Channel Description is a type 3 information element with 4 octets length.
< Packet Channel Description > ::=
< Channel type : bit (5) >
< TN : bit (3) >
< TSC : bit (3) >
{ 0
{ 0 < spare bit >
< ARFCN : bit (10) > -- non-hopping RF channel configuraion
ETSI
480 draft ETSI EN 300 940 V7.7.0 (2000-04)
| 1 < spare bit >
< MAIO : bit (6) > -- indirect encoding of hopping RF channel configuration
< MA_NUMBER_IND : bit >
{ 0 < spare bits : bit (2) >
| 1 < CHANGE_MARK_1 : bit (2) >
}
}
| 1
< MAIO : bit (6) > -- direct encoding of hopping RF channel configuration
< HSN : bit (6) >
};
Table 10.5.58/GSM 04.08: Packet Channel Description information element
The Channel type field (5 bit) shall be ignored by the receiver and all bits treated as spare. For backward compatibility
reasons, the sender shall set the spare bits to binary 00001.
The TN field (3 bit) is the binary representation of the timeslot number as defined in GSM 05.10. Range: 0 to 7
The TSC field (3 bit) is the binary representation of the training sequence code as defined in GSM 05.02.
Range: 0 to 7.
Non-hopping RF channel configuration
The ARFCN field (10 bit) is the binary representation of the absolute RF channel number, see GSM 05.05.
Range: 0 to 1023.
Indirect encoding of hopping RF channel configuration
The MAIO field (6 bit) is the binary representation of the mobile allocation index offset, see GSM 05.02.
Range: 0 to 63.
The MA_NUMBER_IND field (1 bit) is the binary representation of the MA_NUMBER to use as reference to a GPRS
mobile allocation:
0 MA_NUMBER = 14
1 MA_NUMBER = 15
The CHANGE_MARK_1 field (2 bit) is the binary representation of the allowed value of the SI change mark
associated with the GPRS mobile allocation to which the MA_NUMBER refers. Range: 0 to 3.
If the indirect encoding is used, this information element may contain the CHANGE_MARK_1 field. If that is present,
the mobile station being assigned the TBF shall verify the validity of the SI change mark associated with the GPRS
mobile allocation to which this information element refers, see GSM 04.60. The CHANGE_MARK_1 field shall not be
included in this information element if MA_NUMBER = 15 is used.
Direct encoding of hopping RF channel configuration
The MAIO field (6 bit) is the binary representation of the mobile allocation index offset, see GSM 05.02.
Range: 0 to 63.
The HSN field (6 bit) is the binary representation of the hopping sequence number, see GSM 05.02. Range: 0 to 63.
10.5.2.25b Dedicated mode or TBF
The Dedicated mode or TBF information element is used by the network to indicate to the mobile station whether the
rest of the message shall be decoded as an IMMEDIATE ASSIGNMENT message allocating a channel in dedicated
mode or whether the rest of the message shall be decoded as the allocation of a Temporary Block Flow.
This IE also indicates:
- whether the IMMEDIATE ASSIGNMENT message relates to a downlink TBF for a mobile station in packet idle
mode; and
- whether the IMMEDIATE ASSIGNMENT message is the first message of two IMMEDIATE ASSIGNMENT
messages in a two-message assignment of an uplink or downlink TBF.
The Dedicated mode or TBF information element is coded as shown in figure 10.5.55/GSM 04.08 and
table 10.5.59/GSM 04.08.
The Dedicated mode or TBF is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Dedicated mode spare down- octet 1
or TBF IEI 0 TMA link T/D
+-----------------------------------------------+
Figure 10.5.55/GSM 04.08: Dedicated mode or TBF information element
Table 10.5.59/GSM 04.08: Dedicated mode or TBF information element
T/D : TBF or dedicated mode (octet 1)
Bit
1
0 this message assigns a dedicated mode resource
1 this message assigns a Temporary Block Flow (TBF).
Downlink : Downlink assignment to mobile in packet idle mode
Bit
2
0 No meaning
1 this message assigns a resource to the mobile station identified in the IA rest octets. The type of resource
(either dedicated mode or TBF) is indicated by bit 1.
TMA : Two-message assignment
Bit
3
0 No meaning
1 This message is the first message of two in a two-message assignment of an uplink or downlink TBF.
10.5.2.25c RR Packet Uplink Assignment
The RR Packet Uplink Assignment information element is sent by the network to the mobile station to indicate the
assigned uplink resources.
The RR Packet Uplink Assignment information element is coded as shown in tables 10.5.60/GSM 04.08 and
10.5.61/GSM 04.08.
The RR Packet Uplink Assignment is a type 4 information element.
ETSI
481 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.60: RR PACKET UPLINK ASSIGNMENT information element
< RR Packet Uplink Assignment message content > ::=
< LENGTH_IN_OTECTS : bit (8) >
< CHANNEL_CODING_COMMAND : bit (2) >
< TLLI_BLOCK_CHANNEL_CODING : bit (1) >
< Packet Timing Advance : Packet Timing Advance IE >
{01 <Dynamic Allocation : Dynamic Allocation struct>
| 10 <Single Block Allocation : Single Block Allocation struct>
| 11 <Fixed Allocation : Fixed Allocation struct>
| 00 <Extension>}
< N_SPARE_BITS : bit(N) > ;
<Extension> : := -- Future extension can be done by modifying this structure
null ;
<Dynamic Allocation struct > ::=
< Extended Dynamic Allocation : bit(1)>
{ 0 | 1 < P0 : bit(4) >
< PR_MODE : bit (1) > }
< USF_GRANULARITY : bit (1) >
{ 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > }
{ 0 | 1 < RLC_DATA_BLOCKS_GRANTED : bit (8) > }
{ 0 -- Timeslot Allocation
{ 0 | 1 < USF_TN0 : bit (3) >}
{ 0 | 1 < USF_TN1 : bit (3) >}
{ 0 | 1 < USF_TN2 : bit (3) >}
{ 0 | 1 < USF_TN3 : bit (3) >}
{ 0 | 1 < USF_TN4 : bit (3) >}
{ 0 | 1 < USF_TN5 : bit (3) >}
{ 0 | 1 < USF_TN6 : bit (3) >}
{ 0 | 1 < USF_TN7 : bit (3) >}
| 1 -- Timeslot Allocation with Power Control Parameters
< ALPHA : bit (4) >
{ 0 | 1 < USF_TN0 : bit (3) >
< GAMMA_TN0 : bit (5) > }
{ 0 | 1 < USF_TN1 : bit (3) >
{ 0 | 1 < USF_TN2 : bit (3) >
{ 0 | 1 < USF_TN3 : bit (3) >
{ 0 | 1 < USF_TN4 : bit (3) >
{ 0 | 1 < USF_TN5 : bit (3) >
{ 0 | 1 < USF_TN6 : bit (3) >
< GAMMA_TN6 : bit (5) >
{ 0 | 1 < USF_TN7 : bit (3) >
< GAMMA_TN7 : bit (5) > }};
<Single Block Allocation struct > ::=
< TIMESLOT_NUMBER : bit (3) >
{ 0 | 1 < ALPHA : bit (4) >
< GAMMA_TN : bit (5) >}
{ 0 | 1 < P0 : bit (4) >
< PR_MODE : bit (1) > }
<Fixed Allocation struct > ::=
ETSI
482 draft ETSI EN 300 940 V7.7.0 (2000-04)
{ 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > }
< FINAL_ALLOCATION : bit (1)>
< DOWNLINK_CONTROL_TIMESLOT: bit(3)>
{ 0 | 1 < P0 : bit (4)
< PR_MODE : bit (1) > }
{ 0 < TIMESLOT_ALLOCATION : bit (8) >
| 1 < Power Control Parameters : Power Control Parameters IE > }
< HALF_DUPLEX_MODE : bit (1) >
{ 0 { 0 -- with length of allocation bitmap
< BLOCKS_OR_BLOCK_PERIODS : bit (1) >
< ALLOCATION_BITMAP_LENGTH : bit (7) >
< ALLOCATION_BITMAP : bit (val(ALLOCATION_BITMAP_LENGTH) >
| 1 -- without length of Allocation Bitmap (fills remainder of this IE)
< ALLOCATION_BITMAP : bit ** > }
! < Message escape : 1 bit (*) = <no string> > } ;
Editors note: This IE has a number of differences to the contents of the PACKET UPLINK ASSIGNMENT message
described in GSM 04.60:
- the PAGE_MODE is not included because this IE is sent on a DCCH, not on
the PCH/AGCH;
- the Referenced Address is not included because this IE is sent in a dedicated
mode message and hence has only one intended recipient;
- the CONTENTION_RESOLUTION_TLLI is not included because this IE is
sent after dedicated mode contention resolution;
- the GSM 04.60 Frequency Parameters are not included because the dedicated
mode message(s) carry this information in other information elements
(eg Mobile Allocation);
- the TBF_STARTING_TIME is not included because it duplicates the
information in the Starting Time IE;
- the ALLOCATION_REFERENCE is not included because this IE is in a
message sent in dedicated mode using a reliable data link.
ETSI
483 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.61: RR PACKET UPLINK ASSIGNMENT information element details
LENGTH_IN_OCTETS (8 bit field)
This field encodes (in binary) the number that is equal to one eighth of the number of bits in the RR Packet Uplink
Assignment information element that follow the end of this field.
TIMESLOT_ALLOCATION (8 bit field)
This field is encoded as the TIMESLOT_ALLOCATION field in the PACKET UPLINK ASSIGNMENT message in
GSM 04.60.
CHANNEL_CODING_COMMAND (2 bit field)
This field is encoded as the CHANNEL_CODING_COMMAND field in the PACKET UPLINK ASSIGNMENT
message in GSM 04.60.
TLLI_BLOCK_CHANNEL_CODING (1 bit field)
This field is encoded as the TLLI_BLOCK_CHANNEL_CODING field in the PACKET UPLINK ASSIGNMENT
Packet Timing Advance IE
This field is encoded as the Packet Timing Advance IE in the PACKET UPLINK ASSIGNMENT message in GSM
04.60.
Dynamic Allocation struct
This information element contains parameters necessary to define the radio resources of a dynamic allocation or an
extended dynamic allocation.
Extended Dynamic Allocation (1 bit field)
This information field indicates the medium access mode to be used during the TBF.
0 Dynamic Allocation
1 Extended Dynamic Allocation
UPLINK_TFI_ASSIGNMENT (5 bit field)
If present, this field is encoded as the UPLINK_TFI_ASSIGNMENT information element in the PACKET UPLINK
ASSIGNMENT message in GSM 04.60.
Power Control Parameters IE
If present, this field is encoded as the Power Control Parameters IE in the PACKET UPLINK ASSIGNMENT message
in GSM 04.60.
RLC_DATA_BLOCKS_GRANTED (8 bit field)
If present, this field is encoded as the RLC_DATA_BLOCKS_GRANTED field in the PACKET UPLINK
USF for Timeslot Number 0 (TN0) (3 bit field)
If present, these fields are encoded as the USF for Timeslot Number X field (where 0=<X<8) in the PACKET UPLINK
N_SPARE_BITS (N bit field)
This field contains N spare bits. 0=< N< 8. The sender shall set the spare bits are set to 0. The receiver shall ignore the
value of these bits. N is chosen so that the RR Packet Uplink Assignment IE contains an integer number of octets.
Single Block Allocation struct
This information element contains parameters necessary to define the radio resources of a Single Block allocation. For
example for sending of a PACKET RESOURCE REQUEST message in a two phase access or a Measurement report.
ETSI
484 draft ETSI EN 300 940 V7.7.0 (2000-04)
ALPHA (4 bit field)
The ALPHA Power control parameter field is coded according to the following table:
bits
4 3 2 1
0 0 0 0 = 0.0
0 0 0 1 = 0.1
: : :
1 0 0 1 = 0.9
1 0 1 0 = 1.0
TIMESLOT_NUMBER (3 bit field)
If present, this field is encoded as the TIMESLOT_NUMBER field in the PACKET UPLINK ASSIGNMENT message
in GSM 04.60.
GAMMA_TN (5 bit field)
The GAMMA_TN field is the binary representation of the parameter
CH
for MS output power control in units of 2 dB,
see GSM 05.08.
P0, BTS_PWR_CTRL_MODE and PR_MODE fields
These fields are optional downlink power control parameters and are encoded as in the PACKET UPLINK
Fixed Allocation struct
This information element contains parameters necessary to define the radio resources of a fixed allocation.
FINAL_ALLOCATION (1 bit field)
This field indicates whether this allocation is the last allocation of the TBF.
0 this allocation is not the last allocation of the TBF
1 this allocation is the last allocation of the TBF
DOWNLINK_CONTROL_TIMESLOT (3 bit field)
This information field indicates the downlink timeslot that mobile station operating in fixed allocation mode shall
monitor for downlink PACCH. This field is coded as the binary representation of the timeslot number as defined in
GSM 05.10.
Range 0 to 7
HALF_DUPLEX_MODE (1 bit field)
This information field indicates, for multislot class 19 to 29, whether the mobile station shall operate in half duplex
mode.
Bit
0 the MS shall not operate in half duplex mode
1 the MS shall operate in half duplex mode
BLOCKS_OR_BLOCK_PERIODS (1 bit field)
If present, this field is encoded as the BLOCKS_OR_BLOCK_PERIODS field in the PACKET UPLINK
ALLOCATION_BITMAP_LENGTH (7 bit field)
If present, this field is encoded as the ALLOCATION_BITMAP_LENGTH field in the PACKET UPLINK
ALLOCATION_BITMAP (variable length field)
If present, this field is encoded as the ALLOCATION_BITMAP field in the PACKET UPLINK ASSIGNMENT
Extension and Message escape fields
For mobile stations implemented according to this version of the protocol, those fields shall be considered as reserved
values.
ETSI
485 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.25d RR Packet Downlink Assignment
The RR Packet Downlink Assignment information element is sent by the network to the mobile station to indicate the
assigned downlink resources.
The RR Packet Downlink Assignment information element is coded as shown in tables 10.5.62/GSM 04.08 and
10.5.63/GSM 04.08.
The RR Packet Downlink Assignment is a type 4 information element.
For a mobile station assigned to operate in the fixed allocation MAC mode, the network may assign regularly repeating
intervals during which the mobile station shall measure neighbour cell power levels.
Table 10.5.62: RR PACKET DOWNLINK ASSIGNMENT information element
< RR Packet Downlink Assignment IE > ::=
< LENGTH_IN_OCTETS : bit (8) >
< MAC_MODE : bit (2) >
< RLC_MODE : bit (1) >
< TIMESLOT_ALLOCATION : bit (8) >
< Packet Timing Advance : Packet Timing Advance IE >
{ 0 | 1 < P0 : bit (4) >
< BTS_PWR_CTRL_MODE : bit(1) > }
< PR_MODE : bit (1) > }
{ 0 | 1 < Power Control Parameters : Power Control Parameters IE > }
{ 0 | 1 < DOWNLINK_TFI_ASSIGNMENT: bit (5) > }
{ 0 | 1 < MEASUREMENT_STARTING_TIME : bit (16) >
< MEASUREMENT_INTERVAL : bit (5) >
< MEASUREMENT_BITMAP : bit (8) > }
< N_SPARE_BITS : bit (N) > ;
Editors note: This IE has a number of differences to the contents of the PACKET DOWNLINK ASSIGNMENT
message described in GSM 04.60:
- the PAGE_MODE is not included because this IE is sent on a DCCH not on the
PCH/AGCH;
- Referenced Address is not included because this IE is sent in a dedicated
mode message and hence has only one intended recipient.
- the GSM 04.60 Frequency Parameters are not included because the dedicated
mode message(s) carry this information in other information elements
(eg Mobile Allocation);
- the TBF_STARTING_TIME is not included because it duplicates the
information in the Starting Time IE.
Table 10.5.63: RR PACKET DOWNLINK ASSIGNMENT information element details
LENGTH_IN_OCTETS (8 bit field)
This field encodes (in binary) the number that is equal to one eighth of the number of bits in the RR Packet Downlink
Assignment information element that follow the end of this field.
MAC_MODE (2 bit field)
This field is encoded as the MAC_MODE information field in the PACKET DOWNLINK ASSIGNMENT message in
GSM 04.60.
RLC_MODE (1 bit field)
This field is encoded as the RLC_MODE field in the PACKET DOWNLINK ASSIGNMENT message in GSM 04.60.
ETSI
486 draft ETSI EN 300 940 V7.7.0 (2000-04)
TIMESLOT_ALLOCATION (8 bit field)
This field is encoded as the TIMESLOT_ALLOCATION field in the PACKET DOWNLINK ASSIGNMENT message
in GSM 04.60.
Packet Timing Advance IE
This field is encoded as the Packet Timing Advance IE in the PACKET DOWNLINK ASSIGNMENT message in GSM
04.60.
P0, BTS_PWR_CTRL_MODE and PR_MODE fields
These fields are optional downlink power control parameters and are encoded as in the PACKET UPLINK
Power Control Parameters IE
This field is encoded as the Power Control Parameters IE in the PACKET DOWNLINK ASSIGNMENT message in
GSM 04.60.
DOWNLINK_TFI_ASSIGNMENT (5 bit field)
If present, this field is encoded as the DOWNLINK_TFI_ASSIGNMENT information element in the PACKET
DOWNLINK ASSIGNMENT message in GSM 04.60.
MEAUREMENT_STARTING_TIME (16 bit field)
If present, this field is encoded as the MEASUREMENT_STARTING_TIME field in the PACKET DOWNLINK
MEASUREMENT_BITMAP (8 bit field)
If present, this field is encoded as the MEASUREMENT BITMAP information field in the PACKET DOWNLINK
MEASUREMENT_INTERVAL (5 bit field)
If present, this field is encoded as the MEASUREMENT_INTERVAL field in the PACKET DOWNLINK
N_SPARE_BITS (N bit field)
This field contains N spare bits. 0=< N< 8. The sender shall set the spare bits are set to 0. The receiver shall ignore the
value of these bits. N is chosen so that the RR Packet Downlink Assignment IE contains an integer number of octets.
10.5.2.26 Page Mode
The purpose of the Page Mode information element is to control the action of the mobile station belonging to the paging
subgroup corresponding to the paging subchannel.
The Page Mode information element is coded as shown in figure 10.5.56/GSM 04.08 and table 10.5.64/GSM 04.08.
The Page Mode is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
0 0 octet 1
Page Mode IEI spare spare PM
+-----------------------------------------------+
Figure 10.5.56/GSM 04.08: Page Mode information element
ETSI
487 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.64/GSM 04.08: Page Mode information element
+----------------------------------------------+
PM (octet 1)
Bits
2 1
0 0 Normal paging.
0 1 Extended paging.
1 0 Paging reorganization.
1 1 Same as before.
Note: The value "same as before" has been
defined instead of "reserved" to allow
the use of this coding with another
meaning in an upwards compatible way
in later phases of the GSMsystem.
+----------------------------------------------+
10.5.2.26a Spare
10.5.2.26b Spare
10.5.2.26c Spare
10.5.2.26d Spare
10.5.2.27 NCC Permitted
The purpose of the NCC Permitted information element is to provide a definition of the allowed NCCs on the BCCH
carriers to be reported in the MEASUREMENT REPORT message by the mobile stations in the cell.
The NCC Permitted information element is coded as shown in figure 10.5.57/GSM 04.08 and table 10.5.65/GSM 04.08.
The NCC Permitted is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
NCC Permitted IEI octet 1
+-----------------------------------------------

NCC permitted octet 2
+-----------------------------------------------+
Figure 10.5.57/GSM 04.08: NCC Permitted information element
Table 10.5.65/GSM 04.08: NCC Permitted information element
+------------------------------------------------------+
NCC permitted (octet 2)
The NCC permitted field is coded as a bit map, i.e.
bit N is coded with a "0" if the BCCH carrier with
NCC = N-1 is not permitted for monitoring and with a
"1" if the BCCH carrier with NCC = N-1 is permitted
for monitoring; N = 1,2,..,8.
+------------------------------------------------------+
ETSI
488 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.28 Power Command
The purpose of the Power Command information element is to provide the power level to be used by the mobile station.
The Power Command information element is coded as shown in figure 10.5.58/GSM 04.08 and
table 10.5.66/GSM 04.08.
The Power Command is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Power Command IEI octet 1
+-----+-----------------------------------------
0 0 0 POWER LEVEL
spare spare spare octet 2
+-----------------------------------------------+
Figure 10.5.58/GSM 04.08: Power Command information element
Table 10.5.66/GSM 04.08: Power Command information element
+-------------------------------------------------------+
Power level (octet 2)
The power level field is coded as the binary
representation of the "power control level", see TS
GSM05.05.
This value shall be used by the mobile station
according to GSM05.08.

Range: 0 to 31.
+-------------------------------------------------------+
10.5.2.28a Power Command and access type
The purpose of the Power Command and access type information element is to provide the power level to be used by
the mobile station and the indication that the mobile station can avoid the transmission of handover access.
The Power Command and access type information element is coded as shown in figure 10.5.59/GSM 04.08 and
table 10.5.67/GSM 04.08.
The Power Command and access type is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Power Command and Access Type IEI octet 1
+-----+-----------------------------------------
ATC 0 0 POWER LEVEL
spare spare octet 2
+-----------------------------------------------+
Figure 10.5.59/GSM 04.08: Power Command and access type information element
Table 10.5.67/GSM 04.08: Power Command and access type information element
+-------------------------------------------------------+
ATC (Access Type Control) (octet 2)
bit 8
0 Sending of Handover access is mandatory
1 Sending of Handover access is optional

Power level (octet 2)
The power level field is coded as the binary
representation of the "power control level", see TS
GSM05.05.
This value shall be used by the mobile station
according to GSM05.08.

Range: 0 to 31.
+-------------------------------------------------------+
ETSI
489 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.29 RACH Control Parameters
The purpose of the RACH Control Parameters information element is to provide parameters used to control the RACH
utilization. This information element is broadcast to mobile stations in SYSTEM INFORMATION TYPE 1, 2, 2bis, 3,
and 4 messages.
The RACH Control Parameters information element is coded as shown in figure 10.5.60/GSM 04.08 and
table 10.5.68/GSM 04.08.
The RACH Control Parameters is a type 3 information element with 4 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
RACH Control Parameters IEI octet 1
+-----------------------------------------------

Max retrans Tx-integer CELL RE octet 2
BARR
ACCESS
+-----------+-----------------------------+-----
AC AC AC AC AC EC AC AC
C15 C14 C13 C12 C11 C10 C09 C08 octet 3
+-----+-----+-----+-----+-----+-----+-----+-----
AC AC AC AC AC AC AC AC
C07 C06 C05 C04 C03 C02 C01 C00 octet 4
+-----------------------------------------------+
Figure 10.5.60/GSM 04.08: RACH Control Parameters information element
ETSI
490 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.68/GSM 04.08: RACH Control Parameters information element
+-------------------------------------------------------+
Max retrans, Maximum number of retransmissions
(octet 2)

Bits
8 7
0 0 Maximum 1 retransmission
0 1 Maximum 2 retransmissions

Tx-integer, Number of slots to spread transmission
(octet 2)
Bits
6 5 4 3
0 0 0 0 3 slots used to spread transmission

+-------------------------------------------------------+
Table 10.5.68/GSM 04.08: RACH Control Parameters information element (continued)
+-------------------------------------------------------+
CELLBARACCESS, Cell Barred for Access (octet 2)
Bit
2
0 The cell is not barred, see TS. GSM03.22
1 The cell is barred, see TS. GSM03.22

RE, Call reestablishment allowed (octet 2)
Bit
1
0 Call Reestablishment allowed in the cell
1 Call Reestablishment not allowed in the cell

EC Emergency Call allowed (octet 3 bit 3)
3
0 Emergency call allowed in the cell to all MSs
1 Emergency call not allowed in the cell except
for the MSs that belong to one of the classes
between 11 to 15
AC CN, Access Control Class N (octet 3(except bit 3)
and octet 4)
For a mobile station with AC C = N access is not
barred if the AC CN bit is coded with a "0"; N =
0, 1, .. 9,11, .., 15.
+-------------------------------------------------------+
10.5.2.30 Request Reference
The purpose of the Request Reference information element is to provide the random access information used in the
channel request and the frame number, FN modulo 42432 in which the channel request was received.
The Request Reference information element is coded as shown in figure 10.5.61/GSM 04.08 and
table 10.5.69/GSM 04.08.
The Request Reference is a type 3 information element with 4 octets length.
ETSI
491 draft ETSI EN 300 940 V7.7.0 (2000-04)
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Request Reference IEI octet 1
+-----------------------------------------------

RA octet 2
+-----------------------------------------------
T3
T1' (high part) octet 3
+-----------------------------------------------
T3 octet 4
(low part) T2
+-----------------------------------------------+
Figure 10.5.61/GSM 04.08: Request Reference information element
Table 10.5.69/GSM 04.08: Request Reference information element
+-------------------------------------------------------+
RA, Random Access Information (octet 2)
This is an unformatted 8 bit field. Typically the
contents of this field are coded the same as the
CHANNEL REQUEST message shown in Table 9.9,
section 9.1.8

T1' (octet 2)
The T1' field is coded as the binary representation
of (FN div 1326) mod 32.

T3 (octet 3 and 4)
The T3 field is coded as the binary representation
of FN mod 51. Bit 3 of octet 2 is the most
significant bit and bit 6 of octet 3 is the least
significant bit.

T2 (octet 4)
of FN mod 26.

NOTE 1: The frame number, FN modulo 42432 can be cal-
culated as 51x((T3-T2) mod 26)+T3+51x26xT1'

+-------------------------------------------------------+
10.5.2.31 RR Cause
The purpose of the RR Cause information element is to provide the reason for release or the reason for completion of an
assignment or handover.
The RR Cause information element is coded as shown in figure 10.5.62/GSM 04.08 and table 10.5.70/GSM 04.08.
The RR Cause is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
RR Cause IEI octet 1
+-----------------------------------------------

RR cause value octet 2
+-----------------------------------------------+
Figure 10.5.62/GSM 04.08: RR Cause information element
ETSI
492 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.70/GSM 04.08: RR Cause information element
+--------------------------------------------------------+
RR cause value (octet 2)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 Normal event
0 0 0 0 0 0 0 1 Abnormal release, unspecified
0 0 0 0 0 0 1 0 Abnormal release, channel
unacceptable
0 0 0 0 0 0 1 1 Abnormal release, timer expired
0 0 0 0 0 1 0 0 Abnormal release, no activity on
the radio path
0 0 0 0 0 1 0 1 Preemptive release
0 0 0 0 1 0 0 0 Handover impossible, timing advance
out of range
0 0 0 0 1 0 0 1 Channel mode unacceptable
0 0 0 0 1 0 1 0 Frequency not implemented
0 1 0 0 0 0 0 1 Call already cleared
0 1 0 1 1 1 1 1 Semantically incorrect message
0 1 1 0 0 0 0 0 Invalid mandatory information
0 1 1 0 0 0 0 1 Message type non-existent or not
implemented
0 1 1 0 0 0 1 0 Message type not compatible with
protocol state
0 1 1 0 0 1 0 0 Conditional IE error
0 1 1 0 0 1 0 1 No cell allocation available
0 1 1 0 1 1 1 1 Protocol error unspecified

All other cause values shall be treated as 0000 0000,
'normal event'

The listed RR cause values are defined in Annex F.
+--------------------------------------------------------+
The SI 1 Rest Octets information element contains the position about the NCH and spare bits.
The SI 1 Rest Octets information element is a type 5 information element with 1 octet length.
<SI1 Rest Octets> ::=
{L |H <NCH Position : bit (5)> };
<spare padding> ;
ETSI
493 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.71/GSM 04.08: SI 1 Rest Octets information element
+--------------------------------------------------------+

NCH Position on the CCCH

The values in the NCH Position field indicates the block
number of the CCCH block which is used for the
first NCH block and the number of blocks used
for the NCH. (The block numbering corresponds
to table 5 in section 7 of GSM05.02)

The absence of the NCH position field indicates that
there is no NCH in the cell/on the carrying CCCH slot

The following coding applies if 1 or more basic
physical channels are used for CCCH, not combined with
SDCCHs.
Value No of blocks Number of first block
0 0 0 0 0 1 0
0 0 0 0 1 1 1
0 0 0 1 0 1 2
0 0 0 1 1 1 3
0 0 1 0 0 1 4
0 0 1 0 1 1 5
0 0 1 1 0 1 6
0 0 1 1 1 2 0
0 1 0 0 0 2 1
0 1 0 0 1 2 2
0 1 0 1 0 2 3
0 1 0 1 1 2 4
0 1 1 0 0 2 5
0 1 1 0 1 3 0
0 1 1 1 0 3 1
0 1 1 1 1 3 2
1 0 0 0 0 3 3
1 0 0 0 1 3 4
1 0 0 1 0 4 0
1 0 0 1 1 4 1
1 0 1 0 0 4 2
1 0 1 0 1 4 3
1 0 1 1 0 5 0
1 0 1 1 1 5 1
1 1 0 0 0 5 2
1 1 0 0 1 6 0
1 1 0 1 0 6 1
1 1 0 1 1 7 0

Other values are reserved for future use. A mobile
station receiving a reserved value shall behave as if
the NCH position was not present
+--------------------------------------------------------+
In the case the CCCH configuration is not compatible with the NCH position (e.g., CCCH with combined SDCCH and
the value different from 00001, 00010 or 00111), the mobile station shall behave as if the NCH Position field was not
present.
10.5.2.33 SI 2bis Rest Octets
The SI 2bis Rest Octets information element contains only spare bits. Its purpose is to allow the upward compatible
introduction of new information on the BCCH in later phases.
The SI 2bis Rest Octets information element is a type 5 information element with1 octet length.
<SI2bis Rest Octets> ::=
<spare padding> ;
10.5.2.33a SI 2ter Rest Octets
The SI 2ter Rest Octets information element contains only spare bits. Its purpose is to allow the upward
compatible introduction of new information on the BCCH in later phases.
ETSI
494 draft ETSI EN 300 940 V7.7.0 (2000-04)
The SI 2ter Rest Octets information element is a type 5 information element with 4 octets length.
<SI2ter Rest Octets> ::=
<spare padding> ;
The SI 3 Rest Octets information element is coded according to the syntax specified below and described in tables
10.5.72/GSM 04.08, 10.5.73/GSM 04.08 and 10.5.74/GSM 04.08(See section 10.5.2.35).
The SI 3 Rest Octets information element is a type 5 information element with 5 octets length.
Table 10.5.72/GSM 04.08: SI 3 Rest Octets information element is a type 5 information element
<SI3 Rest Octet> ::= <Optional selection parameters>
<Optional Power offset>
<System Information 2ter Indicator>
<Early Classmark Sending Control>
<Scheduling if and where>
{ L | H <GPRS Indicator> }
<spare padding> :
<Optional Selection Parameters> ::= L | H <Selection Parameters>;
<Selection Parameters> ::=
<CBQ: bit (1)>
<CELL_RESELECT_OFFSET: bit (6)>
<TEMPORARY_OFFSET: bit (3)>
<PENALTY_TIME: bit (5)>;
<Optional Power Offset> ::= L | H <Power Offset: bit (2)>;<System Information 2ter Indicator> ::=
L | H;
<Early Classmark Sending Control> ::= L | H;
<Scheduling if and where>::= L | H <WHERE: bit (3)>;
<GPRS Indicator> ::= < RA COLOUR : bit (3) >
< SI13 POSITION : bit >;
CBQ, CELL_BAR_QUALIFY (1 bit field)
CELL_BAR_QUALIFY is used by the network to control mobile station cell selection and reselection. The use and
coding of this parameter is defined in GSM 05.08.
CELL_RESELECT_OFFSET (6 bit field)
CELL_RESELECT_OFFSET is coded as the binary representation of the "CELL_RESELECT_OFFSET" in
GSM 05.08. It is a value used by the mobile station to apply a positive or negative offset to the value of C2 as defined in
GSM 03.22 and GSM 05.08.
TEMPORARY_OFFSET (3 bit field)
The TEMPORARY_OFFSET field is coded as the binary representation of the "TEMPORARY_OFFSET" in
GSM 05.08. It is used by the mobile station as part of its calculation of C2 for the cell reselection process as described
in GSM 05.08. It is used to apply a negative offset to C2 for the duration of PENALTY_TIME.
PENALTY_TIME (5 bit field)
ETSI
495 draft ETSI EN 300 940 V7.7.0 (2000-04)
The PENALTY_TIME is coded as the binary representation of the "PENALTY_TIME" in GSM 05.08. It defines the
length of time for which TEMPORARY_OFFSET is active. The usage of PENALTY_TIME is described in GSM 03.22
and GSM 05.08.
WHERE (3 bit field)
If the WHERE field is not contained in the information element, this indicates that BCCH scheduling information is not
sent in SYSTEM INFORMATION TYPE 9 on the BCCH.
If the WHERE field is contained in the information element, this indicates that BCCH scheduling information is sent in
SYSTEM INFORMATION TYPE 9 on the BCCH and that SYSTEM INFORMATION TYPE 9 messages are sent in
the blocks of the BCCH norm for which ((FN DIV 51) mod (8) = 4 AND (((FN DIV 51) DIV 8) mod (n+1))= 0), where
n is the value encoded in binary in WHERE.
GPRS Indicator
The GPRS Indicator contains the RA COLOUR field and the SI13_POSITION field. If the GPRS Indicator is
contained in the information element, it indicates that GPRS is supported in the cell.
RA COLOUR (3 bit field)
If the mobile station receives different values of the RA COLOUR field in different cell, the mobile station shall
interpret the cell re-selection information as if the two cells belong to different routeing areas.
SI13_POSITION (1 bit field)
The SI13 POSITION field indicates the minimum schedule for where the SYSTEM INFORMATION TYPE 13
message is sent on BCCH, see GSM 05.02:
0 SYSTEM INFORMATION TYPE 13 message is sent on BCCH Norm;
1 SYSTEM INFORMATION TYPE 13 message is sent on BCCH Ext.
The SI 4 Rest Octets information element includes parameters which are used by the mobile station for cell selection and
reselection purposes. It may also include the POWER OFFSET parameter used by DCS 1800 Class 3 MS.
Its content is described in Table 10.5.73/GSM 04.08 and 10.5.74/GSM 04.08..
NOTE: In the future evolution of this standard the values 64h and 72h shall not be used as values of the first octet
when this information element is used in the SYSTEM INFORMATION TYPE 4 message. This will
prevent mobile stations misinterpreting this inforrmation as the CBCH IEIs .
The SI 4 Rest Octets information element is a type 5 information element with 1 to 11 octets length.
<SI4 Rest Octets> ::= <SI4 Rest Octets_O>
{L<Break indicator>| H<SI Rest Octets_S}
<spare padding> ;
<SI4 Rest Octets_O> ::= <Optional selection parameters>
<Optional Power offset>
{L | H < GPRS Indicator >};
<SI4 Rest Octets_S> ::= {L | H <LSA Parameters>}
{L | H <Cell Identity : bit(16)>}
{L | H <LSA ID information>} ;
<Break Indicator> : := L | H ;
<SI7 Rest Octets> ::= <SI4 Rest Octets_O><SI4 Rest Octets_S> |<SI4 Rest Octets_S>;
<SI8 Rest Octets> ::= <SI4 Rest Octets_O><SI4 Rest Octets_S> |<SI4 Rest Octets_S>;
<Optional Selection Parameters> ::= L | H <Selection Parameters> ;
<Selection Parameters> ::= <CBQ : bit (1)>
<CELL_RESELECT_OFFSET : bit (6)>
<TEMPORARY_OFFSET : bit (3)>
< PENALTY_TIME : bit (5)> ;
<Optional Power Offset> ::= L | H <Power Offset : bit(2)> ;
<GPRS Indicator> ::= < RA COLOUR : bit (3) >
< SI13 POSITION : bit > ;
<LSA Parameters> ::= <PRIO_THR : bit (3)>
<LSA_OFFSET : bit (3)>
{0 | 1 <MCC : bit (12)>
<MNC : bit (12)>} ;
<LSA ID information> ::= <LSA identity>
{0 | 1 <LSA_ID information>} ;
<LSA identity> ::= {0<LSA_ID : bit (24)>
|1<ShortLSA_ID : bit (10)>}
If ACS in the System information type 4 message is set to 1 then the SI 7 and SI 8 rest octets consists of
SI4 Rest Octets_O and SI4 Rest Octets_S, otherwise of only SI4 Rest Octets_S.
ETSI
497 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.73/GSM 04.08
CBQ, CELL_BAR_QUALIFY (1 bit field)
CELL_BAR_QUALIFY is used by the network to control mobile station cell selection and reselection. The use and
coding of this parameter is defined in GSM 05.08.
CELL_RESELECT_OFFSET (6 bit field)
CELL_RESELECT_OFFSET is coded as the binary representation of the "CELL_RESELECT_OFFSET" in
GSM 05.08. It is a value used by the mobile station to apply a positive or negative offset to the value of C2 as defined in
GSM 03.22 and GSM 05.08.
TEMPORARY_OFFSET (3 bit field)
The TEMPORARY_OFFSET field is coded as the binary representation of the "TEMPORARY_OFFSET" in
GSM 05.08. It is used by the mobile station as part of its calculation of C2 for the cell reselection process as described
in GSM 05.08. It is used to apply a negative offset to C2 for the duration of PENALTY_TIME.
PENALTY_TIME (5 bit field)
The PENALTY_TIME is coded as the binary representation of the "PENALTY_TIME" in GSM 05.08. It defines the
length of time for which TEMPORARY_OFFSET is active. The usage of PENALTY_TIME is described in GSM 03.22
and GSM 05.08.
Table 10.5.74/GSM 04.08
POWER OFFSET (2 bit field)
POWER OFFSET is used only by DCS 1800 Class 3 MSs to add a power offset to the value of
MS_TXPWR_MAX_CCH used for its random access attempts. It is also used by the MS in its calculation of C1 and C2
parameters. Its use is defined in GSM 05.08
If this parameter is transmitted on a BCCH carrier within the DCS 1800 band, its meaning shall be described below:
Value Meaning
00 0 dB power offset
If this parameter is transmitted on a BCCH carrier outside the DCS 1800 band, then all bit positions shall be treated as
spare.
ETSI
498 draft ETSI EN 300 940 V7.7.0 (2000-04)
GPRS Indicator
The GPRS Indicator contains the RA COLOUR field and the SI13_POSITION field. If the GPRS Indicator is
contained in the information element, it indicates that GPRS is supported in the cell.
RA COLOUR (3 bit field)
If the mobile station receives different values of the RA COLOUR field in different cell, the mobile station shall
interpret the cell re-selection information as if the two cells belong to different routeing areas.
SI13_POSITION (1 bit field)
The SI13 POSITION field indicates the minimum schedule for where the SYSTEM INFORMATION TYPE 13
message is sent on BCCH, see GSM 05.02:
0 SYSTEM INFORMATION TYPE 13 message is sent on BCCH Norm;
1 SYSTEM INFORMATION TYPE 13 message is sent on BCCH Ext.
Break Indicator
The Break Indicator indicates if parameters in addition to those in SI 4 rest octets are sent in SI7 and SI8.
L Additional parameters are not sent in SYSTEM INFORMATION TYPE 7 and 8.
H Additional parameters, SI4 Rest Octets_S are sent in SYSTEM INFORMATION TYPE 7 and 8.
PRIO_THR (3 bit field)
The PRIO_THR field is a signal threshold used by the mobile station to determine whether prioritised cell re-selection
shall apply. The use and coding of this parameters is defined in GSM 05.08.
LSA_OFFSET (3 bit field)
The LSA_OFFSET field applies an offset for LSA reselection between cells with same LSA priorities. The use and
coding of this parameters is defined in GSM 05.08.
MCC and MNC (24 bit field)
If the escape PLMN is broadcast in SI3 and SI4 the cell is used for SoLSA exclusive access and the MCC and MNC
field shall be included. The MS shall then for all purposes use the MCC and MNC values received in the LSA
Parameters instead of the ones received in the Location Area information element in SI3 and 4, eg when deriving the
PLMN identity, the Location Area Identity and Cell Global Identity broadcast by the cell. The MCC and MNC value
field is coded as specified in Figure 10.5.3/GSM 04.08 and Table 10.5.3/GSM 04.08.
Cell Identity (16 bit field)
The purpose of the Cell Identity is to identify a cell within a location area. The Cell Identity is coded as shown in figure
10.2/GSM 04.08 and table 10.5/GSM 04.08.
LSA_ID (24 bit field)
The purpose of the LSA_ID field is to identify a LSA. The LSA ID value field is specified in GSM 03.03.
Short LSA_ID (10 bit field)
The purpose of the Short LSA_ID field is to identify a LSA. The LSA ID defined by the Short LSA_ID is a LSA_ID as
specified in GSM 03.03 with bit 0 set to 0 bit 1 to 10 set to the value of the Short LSA_ID field (LSB in bit 1, MSB in
bit 10) and bit 11 to 23 set to 0.
10.5.2.35a SI 6 Rest Octets
The SI 6 Rest Octet information element may contain information concerning the paging, notification channels, VBS and
VGCS services of the cell.
Mobile stations not supporting VGCS listening or VBS listening can ignore the information contained in this
information element.
The value part is as shown below:
<SI6 rest octets> ::= {L I H <PCH and NCH info>symbol 125 \f "Symbol" \s 10
{L I H <VBS/VGCS options : bit(2)>}
<implicit spare >;
<PCH and NCH info> ::= <Paging channel restructuring>
<NLN(SACCH) : bit(2)>
symbol 123 \f "Symbol" \s 100 I 1 <Call priority : bit (3)>symbol 125 \f "Symbol" \s 10
<NLN status : bit >;
<paging channel restructuring> ::=
1| -- paging channel is restructured
0 -- paging channel is not restructured
<VBS/VGCS options> ::= <inband notifications>
<inband pagings>;
<inband notifications>::=
0| -- the network does not provide notification on FACCH so that the mobile should
inspect the NCH for notifications
1 -- the mobile shall be notified on incoming high priority VBS/VGCS calls through
NOTIFICATION/FACCH, the mobile need not to inspect the NCH
<inband pagings>::=
0| -- the network does not provide paging information on FACCH so that the mobile
should inspect the PCH for pagings
1 -- the mobile shall be notified on incoming high priority point-to-point calls
through NOTIFICATION/FACCH, the mobile need not to inspect the PCH
Attributes, field contents:
1. For <NLN(SACCH): bit(2)>: see 10.5.2.23.
2. For <call priority>: see 10.5.2.23. Indication of the highest priority associated with VBS/VGCS calls in a cell.
reselection purposes. It may also include the POWER OFFSET parameter used by a DCS 1800 Class 3 MS.
The SI 7 Rest Octets information element is coded as the SI 4 Rest Octets. Its contents is described in Table 10.5.2.35a-
b/GSM 04.08.
reselection purposes. It may also include the POWER OFFSET parameter used by a DCS 1800 Class 3 MS.
ETSI
500 draft ETSI EN 300 940 V7.7.0 (2000-04)
The SI 8 Rest Octets information element is coded as the SI 4 Rest Octets. Its contents is described in Table
10.5.73/GSM 04.08 and 10.5.74/GSM 04.08.
10.5.2.37a SI 9 Rest Octets
The SI 9 Rest Octets information element contains information about scheduling of some or all of the information on the
BCCH.
<SI9 rest octets> ::=
{L | H <Scheduling info>}
<spare padding>;
<Scheduling info> ::= <Info type> <Positions>
{0 | 1 <Scheduling info>};
<Info type> ::= 0 <Info_type_4: bit (4)>
| 1 0 <Info_type_5: bit (5)>
| 1 1 <Info_type_6: bit6)>;
<Positions> ::= <Position> {0 | 1 <Position>}
<Position> ::= <Modulus: bit(4)>
<Relative_position: <bit>> --length depends on modulus
<Bcch_type: bit(1)>;
Attributes
The scheduling info indicates one or more information types (in info type) together with their positions. Here, a position
specifies at which relative position P (specified in relative_position) modulo a position modulus M (specified in
modulus) messages of the given information type are sent, on the BCCH norm or BCCH ext (see GSM 05.02) as
indicated in bcch_type. Precisely, messages of the given information type are sent in the multiframes for which
((frame number) DIV 51) mod (M)) = P.
If the position modulus M equals 0, the information type is not sent.
Field contents
The fields of the SI 9 Rest Octets information element are coded as shown in table 10.75/GSM 04.08.
ETSI
501 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.75/GSM 04.08 SI 9 rest octet information element
Info_type_4_(4 bits)
This field contains a binary encoded non-negative integer number assigned to a type of information sent on the BCCH.
All values indicate unknown, unnecessary information and are reserved for future use.
Info_type_5 (5 bits)
All values except those defined below indicate unknown, unnecessary information and are reserved for future use.
Info_type_5:
0 0000System Information type 1
0 0010System Information type 2bis
0 0011System Information type 2ter
Info_type_6_(6 bits)
All values indicate unknown, unnecessary information and are reserved for future use.
modulus (4 bits)
This field encodes the position modulus, according to the following encoding method. Let N be the integer encoded in
binary in the modulus field; the position modulus is then defined as follows :
If N=0, the position modulus is 0,
if N>0, the position modulus is 2
N+1.
relative position (0 bits if the non-negative integer n contained in the modulus field is 0; n+1 bits, if the non-negative
integer N encoded in the modulus field is > 0.
This field contains the N+1 bit binary encoding of a non-negative integer number < 2
N+1
.
bcch_type (1 bit)
0 BCCH norm(as defined in GSM 05.08)
1 BCCH ext (as defined in GSM 05.08)
ETSI
502 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.37b SI 13 Rest Octets
The SI 13 Rest Octets information element is coded according to the syntax specified below and described in tables
10.5.76/GSM 04.08.
< SI 13 Rest Octets > ::=
{ L | H
< BCCH_CHANGE_MARK : bit (3) >
< SI_CHANGE_FIELD : bit (4) >
{ 0 | 1 < SI13_CHANGE_MARK : bit (2) >
< GPRS Mobile Allocation : GPRS Mobile Allocation IE > } -- Defined in GSM 04.60
{ 0 -- PBCCH not present in cell :
< RAC : bit (8) >
< SPGC_CCCH_SUP : bit >
< PRIORITY_ACCESS_THR : bit (3) >
< NETWORK_CONTROL_ORDER : bit (2) >
< GPRS Cell Options : GPRS Cell Options IE > -- Defined in GSM 04.60
< GPRS Power Control Parameters : GPRS Power Control Parameters struct >
| 1 -- PBCCH present in cell :
< PSI1_REPEAT_PERIOD : bit (4) >
< PBCCH Description : PBCCH Description struct >
}
}
< spare padding > ;
< GPRS Power Control Parameters struct > ::=
< ALPHA : bit (4) >
< T_AVG_W : bit (5) >
< T_AVG_T : bit (5) >
< PC_MEAS_CHAN : bit >
< N_AVG_I : bit (4) >;
< PBCCH Description struct > ::=
<Pb : bit (4)
< TSC : bit (3) >
< TN : bit (3) >
{ 00 -- BCCH carrier
| 01 < ARFCN : bit (10) >
| 1 < MAIO : bit (6) >} ;
ETSI
503 draft ETSI EN 300 940 V7.7.0 (2000-04)
Table 10.5.76/GSM 04.08: SI 13 Rest Octets information element
BCCH_CHANGE_MARK (3 bit field)
This field indicates the status of the information on BCCH. The value of this field may be changed when information on
BCCH is changed, see GSM 04.60.
SI_CHANGE_FIELD (4 bit field)
This field is the binary representation of which information was changed at the last indication in
BCCH_CHANGE_MARK, see GSM 04.60. Range 0 to 15:
0 Update of unspecified SI message or SI messages;
1 Update of SI1 message;
2 Update of SI2, SI2 bis or SI2 ter message;
3 Update of SI3, SI4, SI7 or SI8 message;
4 Update of SI9 message;
All other values shall be interpreted as update of unknown SI message type.
SI13_CHANGE_MARK (2 bit field)
This field is the binary representation of the SI change mark identifying the GPRS Mobile Allocation provided in SI13
and PSI13 messages. Range: 0 to 3.
GPRS Mobile Allocation (information element)
This information element is the representation of the GPRS mobile allocation provided in SI13 and PSI13 messages. It
is identified by MA_NUMBER = 14 when referenced from a packet assignment message. The GPRS Mobile Allocation
information element is defined in GSM 04.60. When used in SI13 or PSI13 message, this information element shall
refer to the cell allocation defined for the cell in SI1 or PSI2.
RAC (8 bit field)
This field is the binary representation of the Routing Area Code, see GSM 03.03.
SPGC_CCCH_SUP (bit field)
This field indicates the support of the parameter SPLIT_PG_CYCLE on CCCH from the network side:
0 SPLIT_PG_CYCLE is not supported on CCCH in this cell;
1 SPLIT_PG_CYCLE is supported on CCCH in this cell.
The PRIORITY_ACCESS_THR field (3 bit) is the binary representation of the parameter
PRIORITY_ACCESS_THR:
0 0 0 packet access is not allowed in the cell;
0 0 1 spare, shall be interpreted as '000' (packet access not allowed);
0 1 0 spare, shall be interpreted as '000' (packet access not allowed);
0 1 1 packet access is allowed for priority level 1;
1 0 0 packet access is allowed for priority level 1 to 2;
1 1 1 spare, shall be interpreted as '110' (packet access allowed).
The NETWORK_CONTROL_ORDER field (2 bit) is the binary representation of the parameter
NETWORK_CONTROL_ORDER, see GSM 04.60:
0 0 NC0: MS controlled cell re-selection, no measurement reporting.
0 1 NC1: MS controlled cell re-selection, MS sends measurement reports.
1 0 NC2: Network controlled cell re-selection, MS sends measurement reports.
1 1 Reserved for future use, interpreted as NC0 by mobile station.
GPRS Cell Options (information element)
The GPRS Cell Option information element is defined in GSM 04.60.
ETSI
504 draft ETSI EN 300 940 V7.7.0 (2000-04)
PSI1_REPEAT_PERIOD (4 bit field)
This field is the representation of the PSI1 repeat period. The field is coded according to the following table:
0000 PSI1 repeat period = 1 multiframe
0001 PSI1 repeat period = 2 multiframes
:
1111 PSI1 repeat period = 16 multiframes
GPRS Power Control Parameters struct
The ALPHA field (4 bit) is the binary representation of the parameter for MS output power control in units of 0.1, see
GSM 05.08: Range: 0 to 10. Values greater than 10 shall be interpreted as 10 by the mobile station.
The T_AVG_W field (5 bit) is the binary representation of the parameter T
AVG_W
for MS output power control, see
The T_AVG_T field (5 bit) is the binary representation of the parameter T
AVG_T
The PC_MEAS_CHAN field (bit) indicates the type of channel which shall be used for downlink measurements for
power control:
0 BCCH;
1 PDCH.
The N_AVG_I field (4 bit) is the binary representation of the parameter N
AVG_I
GSM 05.08: Range: 0 to 15.
PBCCH Description struct
The PBCCH description struct provides the channel description for the PBCCH. The frequency description for the
PBCCH may be specified by an ARFCN (non-hopping radio frequency channel) or a MAIO (hopping radio frequency
channel) field. In case of a hopping radio frequency channel, the PBCCH shall use the GPRS mobile allocation specified
in this message. If none of the ARFCN or MAIO fields are present, the PBCCH shall use the BCCH carrier.
Pb (4bit) (for encoding and description see the Global Power Control Parameters IE)
The TSC field (3 bit) is the binary representation of the training sequence code used for PBCCH and PCCCHs. Range:
0 to 7.
The TN field (3 bit) is the binary representation of the timeslot number for the PBCCH and the corresponding PCCCH.
Range: 0 to 7.
The ARFCN field (10 bit) is the binary representation of the absolute RF channel number. Range: 0 to 1023.
The MAIO field (6 bit) is the binary representation of the mobile allocation index offset. Range: 0 to 63.
ETSI
505 draft ETSI EN 300 940 V7.7.0 (2000-04)
10.5.2.37c [Spare]
ETSI
draft ETSI EN 300 940 V7.7.0 (2000-04) 506 (GSM 04.08 version 7.7.0 Release 1998)
10.5.2.37d [Spare]
10.5.2.37e SI 16 Rest Octets
The SI 16 Rest Octets information element includes parameters which are used by the mobile station for cell selection
and reselection purposes.
The SI 16 Rest Octets information element is coded according to the syntax specified below. Its contents is described in
Table 10.52c/GSM 04.08.
<SI16 Rest Octets> ::= {L | H <LSA Parameters>}
<spare padding> ;
<SI17 Rest Octets> ::= < SI16 Rest Octets> ;
<LSA Parameters> ::= <PRIO_THR : bit (3)>
<LSA_OFFSET : bit (3)>
{0 | 1 <MCC : bit (12)>
<MNC : bit (12)>}
<LSA ID information>;
<LSA ID information> ::= <LSA identity>
{0 | 1 <LSA ID information>} ;
<LSA identity> : := {0 <LSA_ID : bit (24)>
|1 <ShortLSA_ID : bit (10)>} ;
Table 10.52c/GSM 04.08
PRIO_THR (3 bit field)
The PRIO_THR field is a signal threshold used by the mobile station to determine whether prioritised cell re-selection
shall apply. The use and coding of this parameters is defined in GSM 05.08.
LSA_OFFSET (3 bit field)
The LSA_OFFSET field applies an offset for LSA reselection between cells with same LSA priorities. The use and
coding of this parameters is defined in GSM 05.08.
MCC and MNC (24 bit field)
If the escape PLMN is broadcast in SI3 and SI4 the cell is used for SoLSA exclusive access and the MCC and MNC
field shall be included. The MS shall then for all purposes use the MCC and MNC values received in the LSA
Parameters instead of the ones received in the Location Area information element in SI3 and 4, eg when deriving the
PLMN identity, the Location Area Identity and Cell Global Identity broadcast by the cell. The MCC and MNC value
field is coded as specified in Figure 10.5.3/GSM 04.08 and Table 10.5.3/GSM 04.08.
LSA_ID (24 bit field)
The purpose of the LSA_ID field is to identify a LSA. The LSA ID value field is coded as specified in GSM 03.03.
Short LSA_ID (10 bit field)
The purpose of the Short LSA_ID field is to identify a LSA. The LSA ID defined by the Short LSA_ID is a LSA_ID as
specified in GSM 03.03 with bit 0 set to 0 bit 1 to 10 set to the value of the Short LSA_ID field (LSB in bit 1, MSB in
bit 10) and bit 11 to 23 set to 0.
ETSI
10.5.2.37f SI 17 Rest Octets
The SI 17 Rest Octets information element includes parameters, which are used by the mobile station for cell selection
and reselection purposes.
The SI 17 Rest Octets information element is coded as the SI 16 Rest Octets. Its contents is described in Table
10.52c/GSM 04.08.
The purpose of the Starting Time information element is to provide the start TDMA frame number, FN modulo 42432.
The Starting Time information element is coded as shown in figure 10.5.65/GSM 04.08 and table 10.5.79/GSM 04.08.
The Starting Time is a type 3 information element with 3 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Starting Time IEI octet 1
+-----------------------------------------------
T1' T3 octet 2
(high part)
+-----------------------------------------------
T3 T2 octet 3
(low part)
+-----------------------------------------------+
Figure 10.5.65/GSM 04.08: Starting Time information element
Table 10.5.79/GSM 04.08: Starting Time information element
+-------------------------------------------------------+
T1' (octet 2)
The T1' field is coded as the binary representation
of (FN div 1326) mod 32.

T3 (octet 2 and 3)
of FN mod 51. Bit 3 of octet 2 is the most
significant bit and bit 6 of octet 3 is the least
significant bit.

T2 (octet 3)
of FN mod 26.

NOTE 1: The frame number, FN modulo 42432 can be cal-
culated as 51x((T3-T2) mod 26)+T3+51x26xT1'

+-------------------------------------------------------+
The starting time and the times mentioned above are with reference to the frame numbering in the concerned cell. They
are given in units of frames (around 4.615 ms).
The Starting Time IE can encode only an interval of time of 42 432 frames, that is to say around 195.8 seconds. To
remove any ambiguity, the specification for a reception at time T is that the encoded interval is (T-10808, T+31623). In
rigorous terms, if we note ST the starting time:
if 0 <= (ST-T) mod 42432 <= 31623, the indicated time is the next time when FN mod 42432 is equal to ST.
If 32024 <= (ST-T) mod 42432 <= 42431, the indicated time has already elapsed.
The reception time T is not specified here precisely. To allow room for various MS implementations, the limit between
the two behaviours above may be anywhere within the interval defined by
31624 <= (ST-T) mod 42432 <= 32023.
ETSI
10.5.2.39 Synchronization Indication
The purpose of Synchronization Indication information element is to indicate which type of handover is to be
performed.
The Synchronization Indication information element is coded as shown in figure 10.5.66/GSM 04.08 and
table 10.5.80/GSM 04.08.
The Synchronization Indication is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
NCI ROT SI octet 1
Synch. Indic. IEI
+-----------------------------------------------+
Figure 10.5.66/GSM 04.08: Synchronization Indication information element
Table 10.5.80/GSM 04.08: Synchronization Indication information element
+------------------------------------------------------+
ROT: Report Observed Time Difference (Octet1 bit 3)
0 Mobile Time Difference IE shall not be included
in the HANDOVER COMPLETE message

1 Mobile Time Difference IE shall be included in
the HANDOVER COMPLETE message

SI: Synchronization indication (octet 1)
Bit
2 1
0 0 Non-synchronized
0 1 Synchronized
1 0 Pre-synchronised
1 1 Pseudo-synchronised

NCI: Normal cell indication (octet 1, bit 4)
0 Out of range timing advance is ignored
1 Out of range timing advance shall trigger
a handover failure procedure
+------------------------------------------------------+
10.5.2.40 Timing Advance
The purpose of the Timing Advance information element is to provide the timing advance value.
The Timing Advance information element is coded as shown in figure 10.5.67/GSM 04.08 and table 10.5.81/GSM 04.08
The Timing Advance is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Timing Advance IEI octet 1
+-----+-----------------------------------------
0 0 octet 2
spare spare Timing advance value
+-----------------------------------------------+
Figure 10.5.67/GSM 04.08: Timing Advance information element
ETSI
Table 10.5.81/GSM 04.08: Timing Advance information element
+------------------------------------------------------+
Timing advance value (octet 2)
The coding of the timing advance value field is the
binary representation of the timing advance in bit
periods; 1 bit period = 48/13 s.
+------------------------------------------------------+
10.5.2.41 Time Difference
The purpose of the Time Difference information element is to provide information about the synchronization difference
between the time bases of two Base Stations. This type of information element is used in relation with the pseudo-
synchronization scheme, see GSM 05.10.
The Time Difference information element is coded as shown in figure 10.5.68/GSM 04.08 and
table 10.5.82/GSM 04.08.
The Time Difference information element is a type 4 information element with 3 octets length.
8 7 6 5 4 3 2 1
+---------------------------------------------------+
Time Difference IEI octet 1
+---------------------------------------------------
Length of Time Difference contents octet 2
+---------------------------------------------------

Time difference value octet 3
+---------------------------------------------------+
Figure 10.5.68/GSM 04.08: Time Difference information element
Table 10.5.82/GSM 04.08: Time Difference information element
+-------------------------------------------------------------+
Time Difference value (octet 3)
The coding of the time difference value field is the binary
representation of time difference in half bit periods,
modulo 256 half bit periods;
1/2 bit period = 24/13 s.
+-------------------------------------------------------------+
10.5.2.41a TLLI
The purpose of the TLLI information element is to provide the Temporary Logical Link Identifier.
The TLLI information element is coded as shown in figure 10.5.69/GSM 04.08 and table 10.5.83/GSM 04.08.
The TLLI is a type 3 information element with 5 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
TLLI IEI octet 1
+-----------------------------------------------
octet 2
TLLI value
+-----------------------------------------------
octet 3
TLLI value (contd)
+-----------------------------------------------
octet 4
TLLI value (contd)
+-----------------------------------------------
octet 5
TLLI value (contd)
+-----------------------------------------------+
Figure 10.5.69/GSM 04.08: TLLI information element
ETSI
Table 10.5.83/GSM 04.08: TLLI information element
+------------------------------------------------------+
TLLI value (octet 2, 3, 4 and 5)
Bit 8 of octet 2 is the most significant bit and bit
1 of octet 5 is the least significant bit.

The TLLI is encoded as a binary number with a
length of 4 octets. TLLI is defined in GSM 03.03.

+------------------------------------------------------+
10.5.2.42 TMSI/P-TMSI
The purpose of the TMSI/P-TMSI information element is to provide the Temporary Mobile Subscriber Identity for
paging purposes.
The TMSI/P-TMSI information element is coded as shown in figure 10.5.70/GSM 04.08 and table 10.5.84/GSM 04.08.
The TMSI/P-TMSI is a type 3 information element with 5 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
TMSI/P-TMSI IEI octet 1
+-----------------------------------------------
octet 2
TMSI/P-TMSI value
+-----------------------------------------------
octet 3
TMSI/P-TMSI value (contd)
+-----------------------------------------------
octet 4
TMSI/P-TMSI value (contd
+-----------------------------------------------
octet 5
TMSI/P-TMSI value (contd)
+-----------------------------------------------+
Figure 10.5.70/GSM 04.08: TMSI/P-TMSI information element
Table 10.5.84/GSM 04.08: TMSI/P-TMSI information element
TMSI/P-TMSI value (octet 2, 3, 4 and 5)
Bit 8 of octet 2 is the most significant bit and bit 1 of octet 5 is the least significant bit.
The coding of the TMSI/P-TMSI is left open for each administration according to GSM 03.03. The length is 4 octets.
NOTE: For purposes other than paging the TMSI/P-TMSI should be provided using the mobile identity
10.5.2.42a VGCS target mode Indication
The VGCS target mode Indication information element is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
VGCS target mode Indic. IEI octet 1
Length of VGCS target mode Indic. octet 2
Target mode Group cipher key number 1 1 octet 3
spare spare
Figure 10.5.71/GSM 04.08: VGCS target mode Indication information element
ETSI
Table 10.5.85/GSM 04.08: VGCS target mode information element
+-------------------------------------------------------+
Target mode (octet 3)
Bit
8 7
0 0 dedicated mode
0 1 group transmit mode

Group cipher key number (octet 3)
Bit
6 5 4 3
0 0 0 0 no ciphering
1 0 1 0 cipher key number A
1 0 1 1 cipher key number B
1 1 0 0 cipher key number C
1 1 0 1 cipher key number D
1 1 1 0 cipher key number E
1 1 1 1 cipher key number F

+-------------------------------------------------------+
10.5.2.43 Wait Indication
The purpose of the Wait Indication information element is to provide the time the mobile station shall wait before
attempting another channel request.
The Wait Indication information element is coded as shown in figure 10.5.72/GSM 04.08 and table 10.5.86/GSM 04.08.
The Wait Indication is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Wait Indication IEI octet 1
+-----------------------------------------------

T3122/T3142 timeout value octet 2
+-----------------------------------------------+
Figure 10.5.72/GSM 04.08: Wait Indication information element
Table 10.5.86/GSM 04.08: Wait Indication information element
+------------------------------------------------------+
T3122/T3142 timeout value (octet 2)
This field is coded as the binary representation of
the T3122/T3142 timeout value in seconds.
+------------------------------------------------------+
Note1 The timeout value is used for T3122 when received in IMMEDIATE_ASSIGNMENT REJECT message for
RR connection establishment. For GPRS MS the timeout value isused for T3142 when received in
IMMEDIATE ASSIGNMENT REJECT message for TBF establishment.
10.5.2.44 SI10 rest octets $(ASCI)$
The SI 10 rest octets information element contains information for cell re-selection in group receive mode.
The value part is coded as shown below:
ETSI
Static and dynamic conditions:
1. 1) Information from the last received neighbour cells description in SYSTEM INFORMATION TYPE 5/5bis/5ter
is necessary for the mobile station to interpret <neighbour information>. If <BA ind> is different from the last
received BA IND value indicated in SYSTEM INFORMATION TYPE 5/5bis/5ter, <neighbour information> cannot
be interpreted by the mobile station.
2. 2) If the correspondence between neighbour cell frequencies and sets of pairs (BSIC, cell information) cannot be
established following the rules below, or if more than one set of such pairs corresponds to one neighbour cell
frequency, the mobile station shall diagnose an imperative message part error.
Attributes, field contents:
1) <cell info> defines a BSIC given by <bsic : bitstring(6)>. It also defines cell information. If <cell parameters> is
contained in <cell info>, this cell information is the cell information given by <cell parameters>; if
<cell parameters> is not contained in <cell info>, this cell information is empty.
2) <differential cell info> defines a BSIC given by <bsic : bitstring(6)> or by <BCC : bitstring(3)>, see below. It
also defines cell information. If <diff cell pars> is contained in <differential cell info>, this cell information is the
cell information given by <diff cell pars>; if <diff cell pars> is not contained in <differential cell info>, this cell
information is empty.
3) <cell parameters> either indicates a barred cell (by presence of <cell barred>)or specifies cell information given
by <further cell info>.
4) Each occurrence of <diff cell pars> either indicates a barred cell (by presence of <cell barred>)or specifies cell
information given by <further diff cell info>.
<SI10 rest octets> ::= <BA ind : bitstring(1)>
{ L <implicit spare> | H <neighbour information> };
<neighbour information> ::= <first frequency: bitstring(5)> <cell info>
{ H <info field> }* L <implicit spare>;
<cell info> ::= <bsic : bitstring(6)> { H <cell parameters> | L }
<cell parameters> ::= <cell barred> | L <further cell info>
<cell barred> ::= H
<further cell info> ::= <la different>
<ms txpwr max cch : bitstring(5)>
<rxlev access min : bitstring(6)>
<cell reselect offset : bitstring(6)>
<temporary offset : bitstring(3)>
<penalty time : bitstring(5)>
<la different> ::= { H <cell reselect hysteresis : bitstring(3)> | L }
<info field> ::= <next frequency>* L <differential cell info>;
<next frequency> ::= H;
<differential cell info> ::= { H <BCC : bitstring(3)> | L <bsic : bitstring(6)> }
{ H <diff cell pars> | L }
<diff cell pars> ::= <cell barred> | L <further diff cell info>
<further diff cell info> ::= <la different>
{ H <ms txpwr max cch : bitstring(5)> | L }
{ H <rxlev access min : bitstring(6)> | L }
{ H <cell reselect offset : bitstring(6)> | L }
{ H <temporary offset : bitstring(3)> | L }
{ H <penalty time : bitstring(5)> | L }
ETSI
5) <further cell info> specifies cell information given by its components
- <la different>
- <ms txpwr max cch : bitstring(5)>
- <rxlev access min : bitstring(6)>
- <cell reselect offset : bitstring(6)>
- <temporary offset : bitstring(3)>
- <penalty time : bitstring(5)>,
as defined below.
6) For each occurrence of <further diff cell info>, a cell information is defined. This information is given by <la
different> and remaining cell information established as follows:
The remaining cell information defined for the first occurrence of <further diff cell info> consists of the cell
information given by its actual components plus the cell information specified by <further cell info>
corresponding to its missing components.
The remaining cell information defined for a later occurrence of <further diff cell info> consists of the cell
information given by its actual components plus the remaining cell information corresponding to its missing
components which is defined for the previous occurrence of <further diff cell info>.
Here, the
actual components of an occurrence of <further diff cell info> denotes those parameters among
- <penalty time : bitstring(5)>
which are present in that occurrence.
missing components of an occurrence of <differential cell info> denote those parameters among
- <penalty time : bitstring(5)>
which are not present in that occurrence.
7) Each occurrence of <bsic : bitstring(6)> specifies a BSIC by encoding its binary representation.
<BCC : bitstring(3)> specifies a BCC by encoding its binary representation; it specifies the BSIC given by that
BCC and the NCC of the BSIC specified by the previous occurrence of <BCC : bitstring(3)> or
<bsic : bitstring(6)>. All occurrences of <bsic: bitstring(6)> and <BCC : bitstring(3)> establish a list of BSIC.
8) <first frequency : bitstring(5)> is the 5 bit binary coding of an integer n with 0 <= n <= 31. It specifies a first
frequency number n+1.
9) <SI10 rest octets> defines a correspondence between neighbour cell frequencies and sets of pairs (BSIC, cell
information) defining the parameters for cell re-selection of any corresponding neighbour cell with BCCH on that
frequency and having that BSIC:
ETSI
Let a(1),..., a(n) be the list of neighbour cell frequencies, in the order determined by the mobile station. Let i be
the first frequency number specified by <first frequency : bitstring(5)> (see above).
The first BSIC and the cell information specified by <cell info> build a pair belonging to the set corresponding to
a(i).
If an m-th occurrence of <info field> is present (where m >=2), having established the correspondence of the (m-
1)-th BSIC to a neighbour frequency a(k), the m-th BSIC and following <differential cell info>
- belong to a(k), if <next frequency> is not present in the m-th occurrence of <info field>,
- belong to a((smod(k+t)), if <next frequency> is present exactly t times in the m-th occurrence of <info field>.
Here, for an integer j, smod(j) := ((j-1) mod n) + 1.
10)If <la different> contains a <cell reselect hysteresis : bitstring(3)>, this means that the cell is to be considered by
the mobile station to belong to a different location area and that for the cell, the cell reselect hysteresis specified
in <cell reselect hysteresis : bitstring(3)> applies.
If <la different> doesnt contain a <cell reselect hysteresis : bitstring(3)>, this means that the cell is to be
considered by the mobile station to belong to the same location area.
11)<same LA indicator : bitstring(1)> defines whether the location area is the same as the location area of the
serving cell
12)For <cell reselect hysteresis : bitstring(3)>: see 10.5.2.4.
13)For <ms txpwr max cch : bitstring(5)>: see 10.5.2.4.
14)For <rxlev access min : bitstring(6)> see 10.5.2.4.
15)For <cell reselect offset : bitstring(6)>: see 10.5.2.35.
16)For <temporary offset : bitstring(3)>: see 10.5.2.35.
17)For <penalty time : bitstring(5)>: see 10.5.2.35.
10.5.2.45 EXTENDED MEASUREMENT RESULTS
The purpose of the Extended Measurement Results information element is to provide the results of the measurements
made by the mobile station on the carriers specified in the EXTENDED MEASUREMENT ORDER.
The Extended Measurement Results information element is coded as shown in figure 10.5.73/GSM 04.08 and table
10.5.87/GSM 04.08.
The Extended Measurement Results is a type 3 information element with 17 octets length.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Extended Measurement Results IEI octet 1
+-----+-----------------------------------------
SC DTX
USED USED RXLEV carrier 0 octet 2

+-----------------------------------------------
RXLEV
RXLEV carrier 1 carrier 2 octet 3
(high part)
+-----------------------------------------------
RXLEV carrier 2 RXLEV carrier 3 octet 4
+-----------------------------------------------
RXLEV
carrier 3 RXLEV carrier 4 octet 5
(low part)
+-----------------------------------------------
RXLEV
(high part)
+-----------------------------------------------
+-----------------------------------------------
RXLEV
(low part)
+-----------------------------------------------
(continued..)
Figure 10.5.73/GSM 04.08: Extended Measurement Results information element
+-----------------------------------------------
RXLEV
(high part)
+-----------------------------------------------
+-----------------------------------------------
RXLEV
(low part)
+-----------------------------------------------
RXLEV
(high part)
+-----------------------------------------------
+-----------------------------------------------
RXLEV
(low part)
+-----------------------------------------------
RXLEV
(high part)
+-----------------------------------------------
+-----------------------------------------------
RXLEV
(low part)
+-----------------------------------------------+
Figure 10.5.73/GSM 04.08: Extended Measurement Results information element
ETSI
Table 10.5.87/GSM 04.08: Extended Measurement Results information element
SC USED (octet 2), indicates the value of the SEQ-CODE in the extended measurement
frequency list information element used for defining the list of frequencies reported on.
Range: 0 to 1.
DTX USED (octet 2) This bit indicates whether or not the mobile station used DTX during
the previous measurement period.
Bit 7
0 DTX was not used
1 DTX was used
RXLEV carrier N (octets 2 to 17). This field is coded as the binary representation of a value
M. M corresponds according to the mapping defined in TS. GSM 05.08 to the received signal
strength on carrier N. N is the index to the frequency in the sorted list of frequencies defined in
the EXTENDED MEASUREMENT ORDER message. The list is sorted in increasing order of
ARFCN, except that ARFCN 0, if included in th e EXTENDED MEASUREMENT ORDER, is
put in the last position of the sorted list. If the EXTENDED MEASUREMENT ORDER contains
more than 21 carriers, only the signal strength of the carriers 0-20 shall be measured and
reported.
Range: 0 to 63
If the EXTENDED MEASUREMENT ORDER message contains less than 21 carriers, the
fields in the EXTENDED MEASUREMENT REPORT not referring to any specified carrier shall
have RXLEV values set to zero.
10.5.2.46 Extended Measurement Frequency List
The purpose of Extended Measurement Frequency List information element is to provide the absolute radio frequency
channel numbers of carriers to measure signal strength on.
The Extended Measurement Frequency List information element is coded as the Cell Channel Description information
element, as specified in section 10.5.2.1b, with the exception of bit 5 of octet 2. figure 10.5.74/GSM 04.08 and
The Extended Measurement Frequency List information element is a type 3 information element with 17 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Extended Measurement Frequency List IEI octet 1
+-----+-----------------------------------------

Bit Bit 0 SEQ- Bit Bit Bit Bit octet 2
128 127 spare CODE 124 123 122 121

+-----+-----+-----+-----+-----+-----+-----+-----

120 119 118 117 116 115 114 113
+-----+-----+-----+-----+-----+-----+-----+-----
+-----+-----+-----+-----+-----+-----+-----+-----

008 007 006 005 004 003 002 001
+-----------------------------------------------+
Figure 10.5.74/GSM 04.08: Extended Measurement Frequency List information element
Table 10.5.88/GSM 04.08: Extended Measurement Frequency List information element
ETSI
SEQ-CODE, Sequence code (octet 2, bit 5).
Range 0 to 1.
10.5.2.47 Suspension Cause
The purpose of the Suspension Cause information element is to provide the reason for the establishment of the dedicated
circuit which generated the GPRS suspension.
The Suspension Cause information element is coded as shown in figure 10.5.2.47/GSM 04.08 and
table 10.5.2.47/GSM 04.08.
The Suspension Cause is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Suspension Cause IEI octet 1
+-----------------------------------------------

Suspension cause value octet 2
+-----------------------------------------------+
Figure 10.5.2.47/GSM 04.08: Suspension Cause information element
Table 10.5.2.47/GSM 04.08: Suspension Cause information element
+--------------------------------------------------------+
Suspension cause value (octet 2)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 Emergency call, mobile originating
call or call re-establishment
0 0 0 0 0 0 0 1 Location Area Update
0 0 0 0 0 0 1 0 MO Short message service (note 1)
0 0 0 0 0 0 1 1 Other procedure which can be
completed with an SDCCH
0 0 0 0 0 1 0 0 MO Voice broadcast or group call
(note 2)
0 0 0 0 0 1 0 1 Answer to paging

Note 1: As an option, cause value 0000 0011 may be
used for an MO Short message service

Note 2: As an option, cause value 0000 0000 may be
used for an MO Voice broadcast or group call

All other cause values shall be treated as 0000 0000

+--------------------------------------------------------+
10.5.2.48 APDU ID
The APDU ID information element identifies the particular protocol and associated application for an APDU.
The APDU ID information element is coded as shown in figure 10.5.2.48/GSM 04.08 and table 10.5.2.48/GSM 04.08.
The APDU ID is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
octet 1
APDU ID IEI Protocol identifier
+-----------------------------------------------+
Figure 10.5.2.48/GSM 04.08: APDU ID information element
ETSI
Table 10.5.2.48/GSM 04.08: APDU ID information element format
+------------------------------------------------------+
Protocol identifier (octet 1)
Bits Protocol / Application
4 3 2 1
0 0 0 0 RRLP (GSM 04.31)/ LCS
0 0 0 1
to reserved for future use
1 1 1 1
+------------------------------------------------------+
10.5.2.49 APDU Flags
The APDU Flags information element provides segmentation and control information for an associated APDU.
The APDU Flags information element is coded as shown in figure 10.5.2.49/GSM 04.08 and
table 10.5.2.49/GSM 04.08.
The APDU Flags is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
0 |first| last octet 1
APDU Flags IEI spare C/R | seg.| seg.
+-----------------------------------------------+
Figure 10.5.2.49/GSM 04.08: APDU Flags information element
Table 10.5.2.49/GSM 04.08: APDU Flags information element format
+------------------------------------------------------+
Last Segment (octet 1)
bit 1
0 Last or only segment
1 Not last or only segment

First Segment (octet 1)
bit 2
0 First or only segment
1 Not first or only segment

C/R (octet 1)
If last seg. = 0, then:
bit 3
0 Command or Final Response
1 Not Command or Final Response

If last seg. = 1, then bit 3 is spare and set to 0

+------------------------------------------------------+
10.5.2.50 APDU Data
The purpose of the information element is to provide an APDU or APDU segment.
The APDU Data information element is coded as shown in figure 10.5.2.50/GSM 04.08 and
table 10.5.2.50/GSM 04.08.
The APDU Data is a type 4 information element with minimum length of 2 octets. No upper length limit is specified
except for that given by the maximum number of octets in a L3 message (GSM 04.06).
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
APDU IEI octet 1
+-----------------------------------------------

Length of APDU contents octet 2
+-----------------------------------------------

APDU Information octets 3-n
+-----------------------------------------------+
Figure 10.5.2.50/GSM 04.08: APDU Data information element
Table 10.5.2.50/GSM 04.08: APDU Data information element format
+------------------------------------------------------+

APDU Information (octets 3-n)
Contains an APDU message or APDU segment as follows:
Protocol ID APDU Message or Segment
----------- -------------------
RRLP RRLP message in GSM 04.31 (1)

Note 1: messages are segmented on octet boundaries
zero bits are used, where necessary, to pad
out the last segment to an octet boundary

+------------------------------------------------------+
10.5.3 Mobility management information elements
10.5.3.1 Authentication parameter RAND
The purpose of the Authentication Parameter RAND information element is to provide the mobile station with a non-
predictable number to be used to calculate the authentication response signature SRES and the ciphering key Kc.
The Authentication Parameter RAND information element is coded as shown in figure 10.5.75/GSM 04.08 and
table 10.5.89/GSM 04.08.
The Authentication Parameter RAND is a type 3 information element with 17 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Authentication parameter RAND IEI octet 1
+-----------------------------------------------

RAND value octet 2
:
:
octet 17

+-----------------------------------------------+
Figure 10.5.75/GSM 04.08: Authentication Parameter RAND information element
ETSI
Table 10.5.89/GSM 04.08: Authentication Parameter RAND information element
+-----------------------------------------------------+
RAND value (octet 2, 3,... and 17)
The RAND value consists of 128 bits. Bit 8 of octet
2 is the most significant bit while bit 1 of octet
17 is the least significant bit.
+-----------------------------------------------------+
10.5.3.2 Authentication parameter SRES
The purpose of the authentication parameter SRES information element is to provide the network with the
authentication response signature calculated in the mobile station.
The Authentication Parameter SRES information element is coded as shown in figure 10.5.76/GSM 04.08 and
table 10.5.90/GSM 04.08.
The Authentication Parameter SRES is a type 3 information element with 5 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Authentication parameter SRES IEI octet 1
+-----------------------------------------------

SRES value octet 2
:
:
octet 5

+-----------------------------------------------+
Figure 10.5.76/GSM 04.08: Authentication Parameter SRES information element
Table 10.5.90/GSM 04.08: Authentication Parameter SRES information element
+------------------------------------------------------+
SRES value (octet 2, 3, 4 and 5)
The SRES value consists of 32 bits. Bit 8 of octet 2
is the most significant bit while bit 1 of octet 5
is the least significant bit.
+------------------------------------------------------+
10.5.3.3 CM service type
The purpose of the CM Service Type information element is to specify which service is requested from the network.
The CM Service Type information element is coded as shown in figure 10.5.77/GSM 04.08 and
table 10.5.91/GSM 04.08.
The CM Service Type is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
CM service type IEI service type octet 1
+-----------------------------------------------+
Figure 10.5.77/GSM 04.08: CM Service Type information element
ETSI
Table 10.5.91/GSM 04.08: CM Service Type information element
+-----------------------------------------------------+
Service type (octet 1)
Bits
4 3 2 1
0 0 0 1 Mobile originating call establishment
or packet mode connection establishment
0 0 1 0 Emergency call establishment
0 1 0 0 Short message service
1 0 0 0 Supplementary service activation
1 0 0 1 Voice group call establishment
1 0 1 0 Voice broadcast call establishment
1 0 1 1 Location Services

+-----------------------------------------------------+
10.5.3.4 Identity type
The purpose of the Identity Type information element is to specify which identity is requested.
The Identity Type information element is coded as shown in figure 10.5.78/GSM 04.08 and
table 10.5.92/GSM 04.08.
The Identity Type is a type 1 information element .
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Identity type IEI 0 type of identity octet 1
spare
+-----------------------------------------------+
Figure 10.5.78/GSM 04.08: Identity Type information element
Table 10.5.92/GSM 04.08: Identity Type information element
+--------------------------------------------------+
Bits
3 2 1
0 0 1 IMSI
0 1 0 IMEI
0 1 1 IMEISV
1 0 0 TMSI

+--------------------------------------------------+
10.5.3.5 Location updating type
The purpose of the Location Updating Type information element is to indicate whether a normal updating, a periodic
updating or an IMSI attach is wanted. It may also indicate that a follow-on request has been received from the mobile
station CM layer.
The Location Updating Type information element is coded as shown in figure 10.5.79/GSM 04.08 and
table 10.5.93/GSM 04.08.
The Location Updating Type is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Location updating FOR 0 LUT octet 1
type IEI spare
+-----------------------------------------------+
Figure 10.5.79/GSM 04.08: Location Updating Type information element
ETSI
Table 10.5.93/GSM 04.08: Location Updating Type information element
+-----------------------------------------------+
LUT (octet 1)
Bits
2 1
0 0 Normal location updating
0 1 Periodic updating
1 0 IMSI attach
1 1 Reserved

FOR (octet 1)
The Follow-On Request bit (FOR) is coded as
follows:
Bit
4
0 No follow-on request pending
1 Follow-on request pending
+-----------------------------------------------+
10.5.3.5a Network Name
The purpose of this information element is to pass a text string to the mobile station.
The Network Name information element is coded as shown in figure 10.5.80/GSM 04.08 and table 10.5.94/GSM 04.08.
The Network Name is a type 4 information element with a minimum length of 3 octets. No upper length limit is specified
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Network Name IEI octet 1
+-----------------------------------------------

Length of Network Name contents octet 2
+-----------------------------------------------
ext coding scheme Add Number of spare
1 CI bits in last octet octet 3
+-----------------------------------------------

octet 4
Text String

octet n
+-----------------------------------------------+
Figure 10.5.80/GSM 04.08: Network Name information element
ETSI
Table 10.5.94/GSM 04.08: Network Name information element
Number of spare bits in last octet (octet 3, bits 1 to 3)
0 0 1 bit 8 is spare and set to "0" in octet n
0 1 0 bits 7 and 8 are spare and set to "0" in octet n
0 1 1 bits 6 to 8(inclusive) are spare and set to "0" in octet n
0 0 0 this field carries no information about the number of spare bits in octet n
Add CI (octet 3, bit 4)
0 The MS should not add the letters for the Countrys Initials to the text string
1 The MS should add the letters for the Countrys Initials and a separator
(e.g. a space) to the text string
Coding Scheme (octet 3, bits 5-7)
0 0 0 Cell Broadcast data coding scheme defined in GSM 03.38
0 0 1 UCS2 (16 bit) [72]
0 1 0
to reserved
1 1 1
Text String (octet 4 to octet n, inclusive)
Encoded according to the Coding Scheme defined by octet 3, bits 5-7
10.5.3.6 Reject cause
The purpose of the Reject Cause information element is to indicate the reason why a request from the mobile station is
rejected by the network.
The Reject Cause information element is coded as shown in figure 10.5.81/GSM 04.08 and table 10.5.95/GSM 04.08.
The Reject Cause is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Reject cause IEI octet 1
+-----------------------------------------------

reject cause value octet 2
+-----------------------------------------------+
Figure 10.5.81/GSM 04.08: Reject Cause information element
ETSI
Table 10.5.95/GSM 04.08: Reject Cause information element
+-------------------------------------------------------+
Reject cause value (octet 2)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 1 0 IMSI unknown in HLR
0 0 0 0 0 0 1 1 Illegal MS
0 0 0 0 0 1 0 0 IMSI unknown in VLR
0 0 0 0 0 1 0 1 IMEI not accepted
0 0 0 0 0 1 1 0 Illegal ME
0 0 0 0 1 0 1 1 PLMN not allowed
0 0 0 0 1 1 0 0 Location Area not allowed
0 0 0 0 1 1 0 1 Roaming not allowed in this
location area
0 0 0 1 0 0 0 1 Network failure
0 0 0 1 0 1 1 0 Congestion
0 0 1 0 0 0 0 0 Service option not supported
0 0 1 0 0 0 0 1 Requested service option
not subscribed
0 0 1 0 0 0 1 0 Service option temporarily
out of order
0 0 1 0 0 1 1 0 Call cannot be identified
0 0 1 1 0 0 0 0 }
to } retry upon entry into a new cell
0 0 1 1 1 1 1 1 }
0 1 1 0 0 0 0 1 Message type non-existent
or not implemented
the protocol state
0 1 1 0 0 0 1 1 Information element non-existent
or not implemented
0 1 1 0 0 1 0 1 Message not compatible with
the protocol state
0 1 1 0 1 1 1 1 Protocol error, unspecified

Any other value received by the mobile station
shall be treated as 0010 0010, 'Service option
temporarily out of order'. Any other value received
by the network shall be treated as 0110 1111,
'Protocol error, unspecified'.

NOTE: The listed reject cause values are defined in
Annex G.
+-------------------------------------------------------+
10.5.3.7 Follow-on Proceed
The purpose of the Follow-on Proceed information element is to indicate that an MM connection may be established on
an existing RR connection.
The Follow-on Proceed information element is coded as shown in figure 10.5.82/GSM 04.08.
The Follow-on Proceed is a type 2 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Follow-on Proceed IEI octet 1
+-----------------------------------------------+
Figure 10.5.82/GSM 04.08: Follow-on Proceed information element
10.5.3.8 Time Zone
The purpose of this information element is to encode the offset between universal time and local time in steps of 15
minutes.
The Time Zone information element is coded as shown in figure 10.5.83/GSM 04.08 and table 10.5.96/GSM 04.08.
The Time Zone is a type 3 information element with a length of 2 octets.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Time Zone IEI octet 1
+-----------------------------------------------
Time Zone
octet 2
+-----------------------------------------------+
Figure 10.5.83/GSM 04.08: Time Zone information element
Table 10.5.96/GSM 04.08: Time Zone information element
+--------------------------------------------------------------+

Time Zone (octet 2, bits 1-8)
This field uses the same format as the Timezone field used in
the TP-Service-Centre-Time-Stamp, which is defined in GSM
03.40, and its value shall be set as defined in GSM 02.42
.
+--------------------------------------------------------------+
10.5.3.9 Time Zone and Time
The purpose of the timezone part of this information element is to encode the offset between universal time and local
time in steps of 15 minutes.
The purpose of the time part of this information element is to encode the universal time at which this information
element may have been sent by the network.
The Time Zone and Time information element is coded as shown in figure 10.5.84/GSM 04.08 and
table 10.5.97/GSM 04.08.
The Time Zone and Time is a type 3 information element with a length of 8 octets.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Time Zone and Time IEI octet 1
+-----------------------------------------------
Year
octet 2
+-----------------------------------------------
Month
octet 3
+-----------------------------------------------
Day
octet 4
+-----------------------------------------------
Hour
octet 5
+-----------------------------------------------
Minute
octet 6
+-----------------------------------------------
Second
octet 7
+-----------------------------------------------
Time zone
octet 8
+-----------------------------------------------+
Figure 10.5.84/GSM 04.08: Time Zone and Time information element
ETSI
Table 10.5.97/GSM 04.08: Timezone and Time information element
Year (octet 2, bits 1-8)
This field uses the same format as the Year field used in the TP-Service-Centre-Time-Stamp, which is defined in
GSM 03.40, and its value shall be set as defined in GSM 02.42.
Month (octet 3, bits 1-8)
This field uses the same format as the Month field used in the TP-Service-Centre-Time-Stamp, which is defined in
Day (octet 4, bits 1-8)
This field uses the same format as the Day field used in the TP-Service-Centre-Time-Stamp, which is defined in
Hour (octet 5, bits 1-8)
This field uses the same format as the Hour field used in the TP-Service-Centre-Time-Stamp, which is defined in
Minute (octet 6, bits 1-8)
This field uses the same format as the Minute field used in the TP-Service-Centre-Time-Stamp, which is defined in
Second (octet 7, bits 1-8)
This field uses the same format as the Second field used in the TP-Service-Centre-Time-Stamp, which is defined in
Time Zone (octet 8, bits 1-8)
This field uses the same format as the Time Zone field used in the TP-Service-Centre-Time-Stamp, which is defined
in GSM 03.40, and its value shall be set as defined in GSM 02.42.
NOTE: Due to ambiguities in earlier versions of the protocol specifications, some mobile stations may interpret
the received NITZ time as local time. This may result in incorrect time settings in the mobile.
10.5.3.10 CTS permission
The purpose of the CTS permission information element is to indicate that the mobile station is allowed to use GSM-
Cordless Telephony System in the Location Area. The CTS permission information element is coded as shown in
figure 10.5.84a/GSM 04.08.
The CTS permission is a type 2 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
| CTS Permission IEI | octet 1
+-----------------------------------------------+
Figure 10.5.84a/GSM 04.08: CTS permission information element
10.5.3.11 LSA Identifier
This element uniquely identifies a LSA.
The LSA Identifier information element is coded as shown in figure 10.68c/GSM 04.08.
The LSA Identifier is a type 4 information element with a length of 2 or 5 octets.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
LSA Identifier IEI octet 1
+-----------------------------------------------
Length of LSA Identifier contents
octet 2
+-----------------------------------------------
LSA ID
octet 3
+-----------------------------------------------
LSA ID cont.
octet 4
+-----------------------------------------------
LSA ID cont.
octet 5
+-----------------------------------------------
Figure 10.68c/GSM 04.08: LSA Identifier information element
If the Length = 0, then no LSA ID is included. This is used to indicate that the MS has moved to an area
where there is no LSA available for that MS.
Octets 3-5 are coded as specified in GSM 03.03, Identification of Localised Service Area. Bit 8 of octet 3 is
the most significant bit.
10.5.4 Call control information elements
10.5.4.1 Extensions of codesets
There is a certain number of possible information element identifier values using the formatting rules described in
section 10.5: 128 from the type 3 & 4 information element format and at least 8 from the type 1 & 2 information element
format.
One value in the type 1 format is specified for shift operations described below. One other value in both the type 3 & 4
and type 1 format is reserved. This leaves 133 information element identifier values available for assignment.
It is possible to expand this structure to eight codesets of 133 information element identifier values each. One common
value in the type 1 format is employed in each codeset to facilitate shifting from one codeset to another. The contents of
this shift information element identifies the codeset to be used for the next information element or elements. The codeset
in use at any given time is referred to as the "active codeset". By convention, codeset 0 is the initially active codeset.
Two codeset shifting procedures are supported: locking shift and non-locking shift.
Codeset 5 is reserved for information elements reserved for national use.
Codeset 6 is reserved for information elements specific to the local network (either public or private).
Codeset 7 is reserved for user-specific information elements.
The coding rules specified in section 10.5 shall apply for information elements belonging to any active codeset.
Transitions from one active codeset to another (i.e. by means of the locking shift procedure) may only be made to a
codeset with a higher numerical value than the codeset being left.
An information element belonging to codeset 5, 6 or 7 may appear together with information elements belonging to
codeset 0, by using the non-locking shift procedure (see section 10.5.4.3).
A user or network equipment shall have the capability to recognize a shift information element and to determine the
length of the following information element, although the equipment need not be able to interpret and act on the content
of the information element. This enables the equipment to determine the start of the subsequent information element.
10.5.4.2 Locking shift procedure
The locking shift procedure employs an information element to indicate the new active codeset. The specified codeset
remains active until another locking shift information element is encountered which specifies the use of another codeset.
For example, codeset 0 is active at the start of message content analysis. If a locking shift to codeset 5 is encountered,
the next information elements will be interpreted according to the information element identifiers assigned in codeset 5,
ETSI
until another shift information element is encountered. This procedure is used only to shift to a higher order codeset than
the one being left.
The locking shift is valid only within that message which contains the locking shift information element. At the start of
every message content analysis, the active codeset is codeset 0.
The locking shift information element uses the type 1 information element format and coding shown in
figure 10.5.85/GSM 04.08 and table 10.5.98/GSM 04.08.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
0 New codeset octet 1
Shift identifier identification
+-------------------------- --------------------+

"0" in this position indicates locking shift
Figure 10.5.85/GSM 04.08: Locking shift element
Table 10.5.98/GSM 04.08: Locking shift element
+---------------------------------------------------------+
Codeset identification (octet 1):
bits 3 2 1
0 0 0 not applicable
0 0 1
to 1 0 0 reserved
1 0 1 codeset 5: information elements
for national use
1 1 0 codeset 6: information elements specific
to the local network
(either public or private)
1 1 1 codeset 7: user-specific information
elements
+---------------------------------------------------------+
10.5.4.3 Non-locking shift procedure
The non-locking shift procedure provides a temporary shift to the specified lower or higher codeset. The non-locking
shift procedure uses a type 1 information element to indicate the codeset to be used to interpret the next information
element. After the interpretation of the next information element, the active codeset is again used for interpreting any
following information elements. For example, codeset 0 is active at the beginning of message content analysis. If a non-
locking shift to codeset 6 is encountered, only the next information element is interpreted according to the information
element identifiers assigned in codeset 6. After this information element is interpreted, codeset 0 will again be used to
interpret the following information elements. A non-locking shift information element indicating the current codeset
shall not be regarded as an error.
A locking shift information element shall not follow directly a non-locking shift information element. If this combination
is received, it shall be interpreted as though a locking shift information element had been received.
The non-locking shift information element uses the type 1 information format and coding shown in
8 7 6 5 4 3 2 1
+-----------------------------------------------+
1 Temporary codeset octet 1
Shift identifier identification
+-------------------------- --------------------+

"1" in this position indicates non-locking shift
Figure 10.5.86/GSM 04.08: Non-locking shift element
ETSI
Table 10.5.99/GSM 04.08: Non-locking shift element
+---------------------------------------------------------+
Codeset identification (octet 1):
bits 3 2 1
0 0 0 codeset 0 (initially active):
GSM04.08 information elements
0 0 1
to 1 0 0 reserved
for national use
specific to the local network
(either public or private)
1 1 1 codeset 7: user-specific information
elements.
+---------------------------------------------------------+
10.5.4.4 Auxiliary states
The purpose of the auxiliary states information element is to describe the current status of the auxiliary states of a call in
the call control states "active" and "mobile originating modify". (See TSs GSM 04.83 and 04.84)
The auxiliary states information element is coded as shown in figure 10.5.87/GSM 04.08, table 10.5.100/GSM 04.08
and table 10.5.101/GSM 04.08.
The auxiliary states is a type 4 information element with 3 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Auxiliary states IEI octet 1
+-----------------------------------------------

Length of auxiliary states contents octet 2
+-----------------------------------------------
1 0 0 0 hold aux. MPTY aux.
ext spare state state octet 3
+-----------------------------------------------+
Figure 10.5.87/GSM 04.08: Auxiliary states information element
Table 10.5.100/GSM 04.08: Auxiliary states information element
+---------------------------------------------------------+
Hold auxiliary state (octet 3)

Bits
4 3
0 0 idle Note 1
0 1 hold request Note 1
1 0 call held Note 1
1 1 retrieve request Note 1

Note 1: These states are defined in Rec GSM04.83.
+---------------------------------------------------------+
ETSI
Table 10.5.101/GSM 04.08: Auxiliary states information element
+---------------------------------------------------------+
Multi party auxiliary state (octet 3)
Bits
2 1
0 0 idle Note 2
0 1 MPTY request Note 2
1 0 call in MPTY Note 2
1 1 split request Note 2

NOTE 2: These states are defined in Rec GSM04.84.
+---------------------------------------------------------+
10.5.4.5 Bearer capability
The purpose of the bearer capability information element is to describe a bearer service. The use of the bearer capability
information element in relation to compatibility checking is described in annex B.
The bearer capability information element is coded as shown in figure 10.5.88/GSM 04.08 and
tables 10.5.102/GSM 04.08 to 10.5.115/GSM 04.08.
The bearer capability is a type 4 information element with a minimum length of 3 octets and a maximum length of 15
octets.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Bearer capability IEI octet 1
+-----------------------------------------------

Length of the bearer capability contents octet 2
+-----------------------------------------------
0/1 radio co- trans information
ext channel ding fer transfer octet 3
requirement std mode capability
+-----+-----------------+-----------------------
0/1 0 0 0
ext co- spare speech version octet 3a etc*
ding indication
+-----+-----+-----------+-----------------------
1 comp- dupl. confi NIRR esta-
ext ress. structure mode gur. bli. octet 4*
+-----+-----------------------+-----------------
0/1 0 0 rate signalling
ext access id. adaption access protocol octet 5*
+-----+-----------+-----------+-----------------
0/1 Other rate 0 0 0
ext Other ITC adaption Spare octet 5a*
+-----+-----------+-----------+-----------------
1 Hdr/ Multi Mode LLI Assig Inb. 0
ext noHdr frame nor/e neg Spare octet 5b*
+-----+-----------+-----------------------+-----
0/1 0 1 User information sync/
ext layer 1 id. layer 1 protocol async octet 6*
+-----+-----------+-----------------------------
0/1 numb. nego- numb.
ext stop tia- data user rate octet 6a*
bits tion bits
+-----+-----------+-----+-----------------------
0/1 intermed. NIC NIC
ext rate on TX on RX Parity octet 6b*
+-----+-----------+-----------------------------
0/1 connection
ext element modem type octet 6c*

+-----+-----------+-----------------------------
0/1 Other Fixed network user rate octet 6d*
ext modem type
+-----+-----------------------------------------
0/1 Acceptable Maximum number of octet 6e*
ext channel traffic channels
codings
+-----+-----------------------------------------
0/1 UIMI Wanted air interface octet 6f*
ext user rate
+-----+-----------------------------------------
1 1 0 User information
ext layer 2 id. layer 2 protocol octet 7*
+-----------------------------------------------+
Figure 10.5.88/GSM 04.08: Bearer capability information element
NOTE: The coding of the octets of the bearer capability information element is not conforming to TS CCITT
Q.931.
ETSI
Table 10.5.102/GSM 04.08: Bearer capability information element
Radio channel requirement (octet 3), network to MS direction
Bits 6 and 7 are spare bits. The sending side (i.e. the network) shall set bit 7 to value 0 and bit 6
to value 1.
Radio channel requirement (octet 3) MS to network direction
When information transfer capability (octet 3) indicates other values than speech:
Bits
7 6
0 0 reserved
0 1 full rate support only MS
1 0 dual rate support MS/half rate preferred
1 1 dual rate support MS/full rate preferred
When information transfer capability (octet 3) indicates the value speech and no speech version
indication is present in octet 3a etc.:
Bits
7 6
0 0 reserved
0 1 full rate support only MS/fullrate speech version 1 supported
1 0 dual rate support MS/half rate speech version 1 preferred, full rate speech version 1 also
supported
1 1 dual rate support MS/full rate speech version 1 preferred, half rate speech version 1 also
supported
When information transfer capability (octet 3) indicates the value speech and speech version
indication(s) is(are) present in octet 3a etc.:
Bits
7 6
0 0 reserved
0 1 the mobile station supports at least full rate speech version 1 but does not support half rate
speech version 1. The complete voice codec preference is specified in octet(s) 3a etc.
1 0 The mobile station supports at least full rate speech version 1 and half rate speech version
1. The mobile station has a greater preference for half rate speech version 1 than for full
rate speech version 1. The complete voice codec preference is specified in octet(s) 3a etc.
1 1 The mobile station supports at least full rate speech version 1 and half rate speech version
1. The mobile station has a greater preference for full rate speech version 1 than for half
rate speech version 1. The complete voice codec preference is specified in octet(s) 3a etc.
Coding standard (octet 3)
Bit
5
0 GSM standardized coding as described below
1 reserved
(continued...)
ETSI
Table 10.5.102/GSM 04.08: Bearer capability information element (continued)
Transfer mode (octet 3)
Bit
4
0 circuit mode
1 packet mode
Information transfer capability (octet 3)
Bits
3 2 1
0 0 0 speech
0 0 1 unrestricted digital information
0 1 0 3.1 kHz audio, ex PLMN
0 1 1 facsimile group 3
1 0 1 Other ITC (See Octet 5a)
1 1 1 reserved, to be used in the network.
The meaning is: alternate speech/facsimile group 3 - starting with speech.
All other values are reserved
Octet(s) 3a etc. MS to network direction
Coding
Bit
7
0 octet used for extension of information transfer capability
1 octet used for other extension of octet 3
When information transfer capability (octet 3) indicates speech and coding (bit 7 in octet 3a etc.)
is coded as 0, bits 1 through 6 are coded:
Bits 5 and 6 are spare.
Speech version indication (octet(s) 3a etc.)
Bits
4 3 2 1
0 0 0 0GSM full rate speech version 1
0 0 0 1GSM half rate speech version 1
0 1 0 1GSM half rate speech version 3
All other values have the meaning "speech version tbd" and shall be ignored
when received.
If octet 3 is extended with speech version indication(s) (octets 3a etc.), all speech versions
supported shall be indicated and be included in order of preference (the first octet (3a) has the
highest preference and so on).
If information transfer capability (octet 3) indicates speech and coding (bit 7 in octet 3a etc.) is
coded as 1, or the information transfer capability does not indicate speech, then the extension
octet shall be ignored.
Octet(s) 3a etc. network to MS direction
The octet(s) 3a etc. shall be ignored by the MS.
ETSI
Compression (octet 4), network to MS direction:
Bit
7
0 data compression not possible
1 data compression possible
Compression (octet 4), MS to network direction:
Bit
7
0 data compression not allowed
1 data compression allowed
Structure (octet 4)
Bits
6 5
0 0 service data unit integrity
1 1 unstructured
Duplex mode (octet 4)
Bit
4
0 half duplex
1 full duplex
Configuration (octet 4)
Bit
3
0 point-to-point
NIRR (octet 4)
(Negotiation of Intermediate Rate Requested)
Bit
2
0 No meaning is associated with this value.
1 Data up to and including 4.8 kb/s, full rate, non-transparent, 6 kb/s radio interface rate is
requested.
Establishment (octet 4)
Bit
1
0 demand
ETSI
Access identity (octet 5)
Bits
7 6
0 0 octet identifier
Rate adaption (octet 5)
Bits
5 4
0 0 no rate adaption
0 1 V.110/X.30 rate adaptation
1 0 CCITT X.31 flag stuffing
1 1 Other rate adaption (see octet 5a)
Signalling access protocol (octet 5)
Bits
3 2 1
0 0 1 I.440/450
0 1 0 X.21
0 1 1 X.28 - dedicated PAD, individual NUI
1 0 0 X.28 - dedicated PAD, universal NUI
1 0 1 X.28 - non dedicated PAD
1 1 0 X.32
Other ITC (octet 5a)
If the value "Other ITC" is not signalled in the field "ITC" then the contents of this field shall be
ignored.
Bit
7 6
0 0 restricted digital information
Other rate adaption (octet 5a)
If the value " Other rate adaption" is not signalled in the field "Rate adaption" then the contents of
this field shall be ignored.
Bit
5 4
0 0 V.120
ETSI
Rate adaption header/no header (octet 5b)
Bit
7
0 Rate adaption header not included
1 Rate adaption header included
Multiple frame establishment support in data link (octet 5b)
Bit
6
0 Multiple frame establishment not supported, only UI frames allowed
1 Multiple frame establishment supported
Mode of operation (octet 5b)
Bit
5
0 Bit transparent mode of operation
1 Protocol sensitive mode of operation
Logical link identifier negotiation (octet 5b)
Bit
4
0 Default, LLI=256 only
1 Full protocol negotiation, (note: A connection over which protocol negotiation will
be executed is indicated in bit 2 of octet 5b)
Assignor/Assignee (octet 5b)
Bit
3
0 Message originator is "default assignee"
1 Message originator is "assignor only"
In band/Out of band negotiation (octet 5b)
Bit
2
0 Negotiation is done in-band using logical link zero
1 Negotiation is done with USER INFORMATION messages on a temporary
signalling connection
Bit 1 is spare and set to the value "0"
ETSI
Layer 1 identity (octet 6)
Bits
7 6
User information layer 1 protocol (octet 6)
Bits
5 4 3 2
0 0 0 0default layer 1 protocol
All other values reserved.
Synchronous/asynchronous (octet 6)
Bit
1
0 synchronous
1 asynchronous
Number of Stop Bits (octet 6a)
Bit
7
0 1 bit (This value is also used in the case of synchronous mode)
1 2 bits
Negotiation (octet 6a)
Bit
6
0 in-band negotiation not possible
NOTE: See Rec. V.110 and X.30
Number of data bits excluding parity bit if present (octet 6a)
Bit
5
0 7 bits
1 8 bits (this value is also used in the case of bit oriented protocols)
User rate (octet 6a)
Bits
4 3 2 1
0 0 0 10.3 kbit/s Recommendation X.1 and V.110
0 1 1 012.0 kbit/s transparent (non compliance with X.1 and V.110)
0 1 1 11.2 kbit/s/75 bit/s Recommendation V.23, (asymmetric) X.1,V.110.
For facsimile group 3 calls the user rate indicates the first and maximum speed the mobile station
is using.
ETSI
Octet 6b for V.110/X.30 rate adaptation Intermediate rate (octet 6b)
Bits
7 6
0 0 reserved
0 1 reserved
1 0 8 kbit/s
1 1 16 kbit/s
Network independent clock (NIC) on transmission (Tx) (octet 6b) (See Rec. V.110 and X.30)
Bit
5
0 does not require to send data with network independent clock
1 requires to send data with network independent clock
Network independent clock (NIC) on reception (Rx) (octet 6b) (See Rec. V.110 and X.30)
Bit
4
0 cannot accept data with network independent clock (i.e. sender does not support this
optional procedure)
1 can accept data with network independent clock (i.e. sender does support this optional
procedure)
Parity information (octet 6b)
Bits
3 2 1
0 0 0 odd
0 1 0 even
0 1 1 none
1 0 0 forced to 0
1 0 1 forced to 1
ETSI
Connection element (octet 6c)
Bit
7 6
0 0 transparent
0 1 non transparent (RLP)
1 0 both, transparent preferred
1 1 both, non transparent preferred
The requesting end (e.g. the one sending the SETUP message) should use the 4 values
depending on its capabilities to support the different modes. The answering party shall only use
the codings 00 or 01, based on its own capabilities and the proposed choice if any. If both MS and
network support both transparent and non transparent, priority should be given to the MS
preference.
Modem type (octet 6c)
Bits
5 4 3 2 1
0 0 0 0 0 none
0 0 0 0 1 V.21
0 0 0 1 0 V.22
0 0 0 1 1 V.22 bis
0 0 1 0 0 V.23
0 0 1 0 1 V.26 ter
0 0 1 1 0 V.32
0 0 1 1 1 modem for undefined interface
0 1 0 0 0 autobauding type 1
Other modem type (octet 6d)
Bits
7 6
0 0 no other modem type specified in this field
0 1 V.32bis
1 0 V.34
Fixed network user rate (octet 6d)
Bit
5 4 3 2 1
0 0 0 0 0 Fixed network user rate not applicable/No meaning is associated
with this value.
0 0 0 0 1 9.6 kbit/s Recommendation X.1 and V.110
0 0 1 1 0 48.0 kbit/s Recommendation X.1 and V.110(synch)
0 0 1 1 1 56.0 kbit/s Recommendation X.1 and V.110(synch) /bit transparent
0 1 0 0 0 64.0 kbit/s bit transparent
ETSI
Acceptable channel codings (octet 6e), mobile station to network direction:
Bit
7
0 TCH/F14.4 not acceptable
1 TCH/F14.4 acceptable
Bit
6
0 Spare
Bit
5
Bit
4
Acceptable channel codings (octet 6e), network to MS direction:
Bits 4 to 7 are spare and shall be set to "0".
Maximum number of traffic channels (octet 6e), MS to network direction:
Bits
3 2 1
0 0 0 1 TCH
0 0 1 2 TCH
0 1 0 3 TCH
0 1 1 4 TCH
1 0 0 5 TCH
1 0 1 6 TCH
1 1 0 7 TCH
1 1 1 8 TCH
Maximum number of traffic channels (octet 6e), network to MS direction:
Bits 1 to 3 are spare and shall be set to 0.
ETSI
UIMI, User initiated modification indication (octet 6f),
7 6 5
0 0 0 User initiated modification not allowed/required
0 0 1 User initiated modification up to 1 TCH/F allowed/may be requested
All other values shall be interpreted as User initiated modification up to 4 TCH/F may be requested.
Wanted air interface user rate (octet 6f), MS to network direction:
Bits
4 3 2 1
0 0 0 0Air interface user rate not applicable/No meaning associated with this value
0 0 0 19.6 kbit/s
0 0 1 014.4 kbit/s
0 0 1 119.2 kbit/s
0 1 0 128.8 kbit/s
0 1 1 0 38.4 kbit/s
0 1 1 143.2 kbit/s
1 0 0 0 57.6 kbit/s
1 0 0 1interpreted by the network as 38.4 kbit/s in this version of the protocol
Wanted air interface user rate (octet 6f), network to MS direction:
Bits 1 to 4 are spare and shall be set to 0.
Layer 2 identity (octet 7)
Bits
7 6
User information layer 2 protocol (octet 7)
Bits
5 4 3 2 1
0 0 1 1 0 recommendation X.25, link level
0 1 0 0 0 ISO 6429, codeset 0 (DC1/DC3)
0 1 0 0 1 reserved: was allocated but never used in earlier phases of the protocol
0 1 0 1 0 videotex profile 1
0 1 1 0 0 COPnoFlCt (Character oriented Protocol with no Flow Control
mechanism)
0 1 1 0 1 X.75 layer 2 modified (CAPI)
10.5.4.5.1 Static conditions for the bearer capability IE contents
If the information transfer capability field (octet 3) indicates "speech", octets 4, 5, 5a, 5b, 6, 6a, 6b, 6c, 6d, 6e, 6f and 7
shall not be included.
If the information transfer capability field (octet 3) indicates "speech", octet 3a etc. shall be included only if the mobile
station supports at least one speech version other than:
ETSI
- GSM full rate speech version 1; or
- GSM half rate speech version 1.
If the information transfer capability field (octet 3) indicates a value different from "speech", octets 4, 5, 6, 6a, 6b, and
6c shall be included, octets 6d, 6e and 6f are optional. In the network to MS direction in case octet 6d is included, octets
6e and 6f may be included. In the MS to network direction in case octet 6d is included octet 6e shall also be included
and 6f may be included.
If the information transfer capability field (octet 3) indicates "facsimile group 3", the modem type field (octet 6c) shall
indicate "none".
If the information transfer capability field (octet 3) indicates "other ITC" or the rate adaption field (octet 5) indicates
"other rate adaption", octet 5a shall be included.
If the rate adaption field (octet 5) indicates "other rate adaption" and the other rate adaption field (octet 5a) indicates
"V.120", octet 5b shall be included.
The modem type field (octet 6c) shall not indicate "autobauding type 1" unless the connection element field (octet 6c)
indicates "non transparent".
10.5.4.5a Call Control Capabilities
The purpose of the Call Control Capabilities information element is to identify the call control capabilities of the mobile
station.
The Call Control Capabilities information element is coded as shown in figure 10.5.89/GSM 04.08 and
table 10.5.116/GSM 04.08.
The Call Control Capabilities is a type 4 information element with a length of 3 octets.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Call Control Capabilities IEI octet 1
+-----------------------------------------------

Length of Call Control Capabilities contents octet 2
+-----------------------------------------------
0 0 0 0 0 0
spare PCP DTMF octet 3
+-----------------------------------------------+
Figure 10.5.89/GSM 04.08: Call Control Capabilities information element
Table 10.5.116/GSM 04.08: Call Control Capabilities
+--------------------------------------------------------------+
DTMF (octet 3, bit 1)
0 This value is reserved for earlier versions of
the protocol.
1 This value indicates that the mobile station
supports DTMF as specified in section 5.5.7 of
this specification.
PCP (octet 3, bit 2)

does not support the Prolonged Clearing Procedure
supports the Prolonged Clearing Procedure.
|

+--------------------------------------------------------------+
10.5.4.6 Call state
The purpose of the call state information element is to describe the current status of a call, (see section 5.1).
ETSI
The call state information element is coded as shown in figure 10.5.90/GSM 04.08 and table 10.5.117/GSM 04.08.
The call state is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
call state IEI octet 1
+-----------------------------------------------
coding
standard call state value (coded in binary) octet 2
+-----------------------------------------------+
Figure 10.5.90/GSM 04.08: Call state information element
ETSI
Table 10.5.117/GSM 04.08: Call state information element
+--------------------------------------------------------------+
Bits
8 7
0 0 standardized coding as described in
CCITT Rec. Q.931
0 1 reserved for other international
standards
1 0 national standard
1 1 standard defined for the GSMPLMNS
as described below

Coding standards other than "1 1 - Standard defined for the
GSMPLMNS" shall not be used if the call state can be
represented with the GSMstandardized coding.

The mobile station or network need not support any other
coding standard than "1 1 - Standard defined for the GSM
PLMNS".
If a call state IE indicating a coding standard not
supported by the receiver is received, call state "active"
shall be assumed.

Call state value (octet 2)

Bits
6 5 4 3 2 1
0 0 0 0 0 0 UO - null NO - null
0 0 0 0 1 0 U0.1- MM connection N0.1- MM connection
pending pending
1 0 0 0 1 0 U0.2- CC prompt present N0.2- CC connection
pending
1 0 0 0 1 1 U0.3- Wait for network N0.3- Network answer
information pending
1 0 0 1 0 0 U0.4- CC-Establishment N0.4- CC-Establish-
present ment present
1 0 0 1 0 1 U0.5- CC-Establishment N0.5- CC-Establish-
confirmed ment confirmed
1 0 0 1 1 0 U0.6- Recall present N0.6- Recall present
0 0 0 0 0 1 U1 - call initiated N1 - call initiated
0 0 0 0 1 1 U3 - mobile originating N3 - mobile origina-
call proceeding ting call proceeding
0 0 0 1 0 0 U4 - call delivered N4 - call delivered
0 0 0 1 1 0 U6 - call present N6 - call present
0 0 0 1 1 1 U7 - call received N7 - call received
0 0 1 0 0 0 U8 - connect request N8 - connect request
0 0 1 0 0 1 U9 - mobile terminating N9 - mobile termina-
call confirmed ting call confirmed
0 0 1 0 1 0 U10- active N10- active
0 0 1 0 1 1 U11- disconnect request
0 0 1 1 0 0 U12- disconnect indication N12-disconnect
indication
0 1 0 0 1 1 U19- release request N19- release request
0 1 1 0 1 0 U26- mobile originating N26- mobile origina-
modify ting modify
0 1 1 0 1 1 U27- mobile terminating N27- mobile termina-
modify ting modify
0 1 1 1 0 0 N28- connect indication
+--------------------------------------------------------------+
10.5.4.7 Called party BCD number
The purpose of the called party BCD number information element is to identify the called party.
The called party BCD number information element is coded as shown in figure 10.5.91/GSM 04.08 and
table 10.5.118/GSM 04.08.
The called party BCD number is a type 4 information element with a minimum length of 3 octets and a maximum length
of 43 octets. For PCS 1900 the maximum length is 19 octets.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Called party BCD number IEI octet 1
+-----------------------------------------------

Length of called party BCD number contents octet 2
+-----------------------------------------------
1 type of Numbering plan
ext number identification octet 3
+-----------------------+-----------------------

Number digit 2 Number digit 1 octet 4*
+-----------------------+-----------------------

+-----------------------+-----------------------
:
2) :
+-----------------------------------------------+
Figure 10.5.91/GSM 04.08: Called party BCD number information element
NOTE 1: The number digit(s) in octet 4 precedes the digit(s) in octet 5 etc. The number digit which would be
entered first is located in octet 4, bits 1 to 4.
NOTE 2: If the called party BCD number contains an odd number of digits, bits 5 to 8 of the last octet shall be filled
with an end mark coded as "1111".
Since the information element must contain the complete called party BCD number there is no need for an additional
complete indication.
Table 10.5.118/GSM 04.08: Called party BCD number
+-------------------------------------------------------+
Type of number (octet 3) (Note 1)

Bits
7 6 5
0 0 0 unknown (Note 2)
0 0 1 international number (Note 3, Note 5)
0 1 0 national number (Note 3)
0 1 1 network specific number (Note 4)
1 0 0 dedicated access, short code
1 0 1 reserved
1 1 0 reserved
1 1 1 reserved for extension
+-------------------------------------------------------+
NOTE 1: For the definition of "number" see CCITT Recommendation I.330 and GSM 03.03.
NOTE 2: The type of number "unknown" is used when the user or the network has no knowledge of the type of
number, e.g. international number, national number, etc. In this case the number digits field is organized
according to the network dialling plan, e.g. prefix or escape digits might be present.
NOTE 3: Prefix or escape digits shall not be included.
NOTE 4: The type of number "network specific number" is used to indicate administration/service number specific
to the serving network, e.g. used to access an operator.
NOTE 5: The international format shall be accepted by the MSC when the call is destined to a destination in the
same country as the MSC.
ETSI
Table 10.5.118/GSM 04.08: Called party BCD number (continued)
+---------------------------------------------------------+
Numbering plan identification (octet 3)

Number plan (applies for type of number = 000,
001, 010 and 100)
Bits
4 3 2 1
0 0 0 0 unknown
0 0 0 1 ISDN/telephony numbering plan
(Rec. E.164/E.163)
0 0 1 1 data numbering plan (Recommendation X.121)
0 1 0 0 telex numbering plan (Recommendation F.69)
1 0 0 0 national numbering plan
1 0 0 1 private numbering plan
1 0 1 1 reserved for CTS (see GSM 04.56)
1 1 1 1 reserved for extension

+---------------------------------------------------------+
When an MS is the recipient of number information from the network, any incompatibility between the
number digits and the number plan identification shall be ignored and a STATUS message shall not be
sent to the network.
In the case of numbering plan "unknown", the number digits field is organized according to the network
dialling plan; e.g. prefix or escape digits might be present.
Table 10.5.118/GSM 04.08: Called party BCD number (continued)
+---------------------------------------------------------+
Number digits (octets 4, etc.)
Bits Number digit value
4 3 2 1 or
8 7 6 5
0 0 0 0 0
0 0 0 1 1
0 0 1 0 2
0 0 1 1 3
0 1 0 0 4
0 1 0 1 5
0 1 1 0 6
0 1 1 1 7
1 0 0 0 8
1 0 0 1 9

1 0 1 0 *
1 0 1 1 #
1 1 0 0 a
1 1 0 1 b
1 1 1 0 c
1 1 1 1 used as an endmark in the case of an odd
number of number digits
+---------------------------------------------------------+
10.5.4.8 Called party subaddress
The purpose of the Called party subaddress is to identify the subaddress of the called party of a call. For the definition of
a subaddress see Rec. CCITT I.330.
The Called party subaddress information element is coded as shown in figure 10.5.92/GSM 04.08 and Table
10.5.119/GSM 04.08
The called party subaddress is a type 4 information element with a minimum length of 2 octets and a maximum length of
23 octets.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Called party Subaddress IEI octet 1
+-----------------------------------------------

Length of called party subaddress contents octet 2
+-----------------------------------------------
1 type of odd/ev 0 0 0
ext subaddress Indica spare octet 3*
+-----------------------------------------------

Subaddress information octet 4*
: : :
: : : etc.
+-----------------------------------------------+
Figure 10.5.92/GSM 04.08: Called party subaddress
Table 10.5.119/GSM 04.08: Called party subaddress
+-------------------------------------------------------+
Type of subaddress (octet 3)

Bits
7 6 5
0 0 0 NSAP (X.213/ISO 8348 AD2)
0 1 0 User specified

Odd/even indicator (octet 3)
Bit
4
0 even number of address signals
1 odd number of address signals

NOTE: The odd/even indicator is used when the type of
subaddress is "user specified" and the coding is BCD.

Subaddress information (octet 4, etc...)
The NSAP X.213/ISO8348AD2 address shall be formatted
as specified by octet 4 which contains the Authority
and Format Identifier (AFI). The encoding is made ac-
cording to the "preferred binary encoding" as defined
in X.213/ISO8348AD2. For the definition of this type
of subaddress, see Rec. CCITT I.334.

A coding example is given in ANNEX A.

For User-specific subaddress, this field is encoded
according to the user specification, subject to a
maximum length of 20 octets. When interworking with
X.25 networks BCD coding should be applied.

NOTE: It is recommended that users apply NSAP subad-
dress type since this subaddress type allows the use
of decimal, binary and IA5 characters in a standar-
dised manner.
+-------------------------------------------------------+
10.5.4.9 Calling party BCD number
The purpose of the calling party BCD number information element is to identify the origin of a call.
The calling party BCD number information element is coded as shown in figure 10.5.93/GSM 04.08 and
table 10.5.120/GSM 04.08.
The calling party BCD number is a type 4 information element. In the network to mobile station direction it has a
minimum length of 3 octets and a maximum length of 14 octets. (This information element is not used in the mobile
station to network direction.)
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Calling party BCD number IEI octet 1
+-----------------------------------------------

Length of calling party BCD number contents octet 2
+-----------------------------------------------
0/1 type of Numbering plan
ext number identification octet 3
+-----+-----------------------------------------
1 presentat. 0 0 0 screening
ext indicator spare indicator octet 3a*
+-----------------------------------------------

+-----------------------+-----------------------

+-----------------------+-----------------------
:
:
+-----------------------------------------------+
Figure 10.5.93/GSM 04.08: Calling party BCD number information element
The contents of octets 3, 4, etc. are coded as shown in table 10.5.118. The coding of octet 3a is defined in
table 10.5.120 below.
If the calling party BCD number contains an odd number of digits, bits 5 to 8 of the last octet shall be filled with an end
mark coded as "1111".
Table 10.5.120/GSM 04.08: Calling party BCD number
+--------------------------------------------------------+
Presentation indicator (octet 3a)
Bits
7 6
0 0 Presentation allowed
0 1 Presentation restricted
1 0 Number not available due to interworking
1 1 Reserved

If octet 3a is omitted the value "00 - Presentation
allowed" is assumed.

Screening indicator (octet 3a)

Bits
2 1
0 0 User-provided, not screened
0 1 User-provided, verified and passed
1 0 User-provided, verified and failed
1 1 Network provided

If octet 3a is omitted the value "0 0 - User provided,
not screened" is assumed.

+--------------------------------------------------------+
10.5.4.10 Calling party subaddress
The purpose of the Calling party subaddress is to identify a subaddress associated with the origin of a call. For the
definition of a subaddress see Rec. CCITT I.330.
The Calling party subaddress information element is coded as shown in figure 10.5.94/GSM 04.08 and
table 10.5.121/GSM 04.08
The calling party subaddress is a type 4 information element with a minimum length of 2 octets and a maximum length
of 23 octets.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Calling party Subaddress IEI octet 1
+-----------------------------------------------

Length of calling party subaddress contents octet 2
+-----------------------------------------------
1 type of odd/ev 0 0 0
ext subaddress Indica octet 3*
+-----------------------------------------------

: : :
: : : etc.
+-----------------------------------------------+
Figure 10.5.94/GSM 04.08: Calling party subaddress
Table 10.5.121/GSM 04.08: Calling party subaddress
+-------------------------------------------------------+
Type of subaddress (octet 3)

Bits
7 6 5
0 0 0 NSAP (X.213/ISO 8348 AD2)
0 1 0 User specified

Odd/even indicator (octet 3)
Bit
4
0 even number of address signals
1 odd number of address signals

The odd/even indicator is used when the type of
subaddress is "user specified" and the coding is BCD

Subaddress information (octet 4, etc...)
The NSAP X.213/ISO8348AD2 address shall be formatted
as specified by octet 4 which contains the Authority
and Format Identifier (AFI). The encoding is made ac-
cording to the "preferred binary encoding" as defined
in X.213/ISO8348AD2. For the definition of this type
of this type of subaddress, see Rec. CCITT I.332.

A coding example is given in ANNEX A.

For User-specific subaddress, this field is encoded
according to the user specification, subject to a
maximum length of 20 octets. When interworking with
X.25 networks BCD coding should be applied.

NOTE: It is recommended that users apply NSAP subad-
dress type since this subaddress type allows the use
of decimal, binary and IA5 characters in a standar-
dised manner.
+-------------------------------------------------------+
10.5.4.11 Cause
The purpose of the cause information element is to describe the reason for generating certain messages, to provide
diagnostic information in the event of procedural errors and to indicate the location of the cause originator.
The cause information element is coded as shown in figure 10.5.95/GSM 04.08 and tables 10.5.122 and
10.5.123/GSM 04.08.
The cause is a type 4 information element with a minimum length of 4 octets and a maximum length of 32 octets.
The cause information element may be repeated in a message.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Cause IEI octet 1
+-----------------------------------------------

Length of cause contents octet 2
+-----------------------------------------------
0/1 coding 0
ext standard spare location octet 3
+-----+-----------------------------------------
1 octet 3a*
ext recommendation
+-----+-----------------------------------------
1
ext cause value octet 4
+-----------------------------------------------

diagnostic(s) if any octet 5*
: :
: : octet N*
+-----------------------------------------------+
Figure 10.5.95/GSM 04.08: Cause information element
If the default value applies for the recommendation field, octet 3a shall be omitted.
ETSI
Table 10.5.122/GSM 04.08: Cause information element
+-------------------------------------------------------------+
Bits
7 6
0 0 Coding as specified in CCITT Rec. Q.931
0 1 Reserved for other international standards
1 0 National standard
1 1 Standard defined for the GSMPLMNS as described
below and in table 10.86/GSM04.08

Coding standards other than "1 1 - Standard defined for
the GSMPLMNS" shall not be used if the cause can be
represented with the GSMstandardized coding.

PLMNS".
If a cause IE indicating a coding standard not supported by
the receiver is received, cause "interworking, unspecified"
shall be assumed.

Location (octet 3)
Bits
4 3 2 1
0 0 0 0 user
0 0 0 1 private network serving the local user
0 0 1 0 public network serving the local user
0 0 1 1 transit network
0 1 0 0 public network serving the remote user
0 1 0 1 private network serving the remote user
0 1 1 1 international network
1 0 1 0 network beyond interworking point


Recommendation (octet 3a)
Octet 3a shall not be included if the coding standard is
coded as "1 1 - Standard defined for GSMPLMNS".

If the coding standard is different from "1 1 - Standard
defined for GSMPLMNS", the coding of octet 3a, if included,
and octets 4 to N is according to that coding standard.
+-------------------------------------------------------------+
Table 10.5.122/GSM 04.08: Cause information element (continued)
+-------------------------------------------------------------+
Cause value (octet 4)

The cause value is divided in two fields: a class (bits 5
through 7) and a value within the class (bits 1 through 4).

The class indicates the general nature of the event.

Class (000): normal event
Class (001): normal event
Class (010): resource unavailable
Class (011): service or option not available
Class (100): service or option not implemented
Class (101): invalid message (e.g. parameter out of range)
Class (110): protocol error (e.g. unknown message)
Class (111): interworking

The cause values are listed in Table 10.86/GSM04.08 below
and defined in Annex H.

Diagnostic(s) (octet 5)
Diagnostic information is not available for every cause, see
Table 10.86/GSM04.08 below.

When available, the diagnostic(s) is coded in the same way
as the corresponding information element in section 10.

The inclusion of diagnostic(s) is optional.
+-------------------------------------------------------------+
Table 10.5.123/GSM 04.08: Cause information element values
ETSI
Cause value Cause Cause Diag- Remarks
Class Value num. nostic

7 6 5 4 3 2 1

0 0 0 0 0 0 1 1. Unassigned (unallocated) Note 9
number
0 0 0 0 0 1 1 3. No route to destination Note 9
0 0 0 0 1 1 0 6. Channel unacceptable -
0 0 0 1 0 0 0 8. Operator determined barring -
0 0 1 0 0 0 0 16. Normal call clearing Note 9
0 0 1 0 0 0 1 17. User busy Note 1
0 0 1 0 0 1 0 18. No user responding -
0 0 1 0 0 1 1 19. User alerting, no answer -
0 0 1 0 1 0 1 21. Call rejected Note 9 - user
supplied diag-
nostic (note 4)
0 0 1 0 1 1 0 22. Number changed New destination
(note 5)
0 0 1 1 0 0 1 25 Pre-emption
0 0 1 1 0 1 0 26. Non selected user clearing -
0 0 1 1 0 1 1 27. Destination out of order -
0 0 1 1 1 0 0 28. Invalid number format (in- -
complete number)
0 0 1 1 1 0 1 29. Facility rejected Note 1
0 0 1 1 1 1 0 30. Response to STATUS ENQUIRY -
0 0 1 1 1 1 1 31. Normal, unspecified -
0 1 0 0 0 1 0 34. No circuit/channel available Note 1
0 1 0 0 1 1 0 38. Network out of order -
0 1 0 1 0 0 1 41. Temporary failure -
0 1 0 1 0 1 0 42. Switching equipment conges- -
tion
0 1 0 1 0 1 1 43. Access information discarded Discarded info-
mation element
identifiers
(note 6)
0 1 0 1 1 0 0 44. requested circuit/channel -
not available
0 1 0 1 1 1 1 47. Resources unavailable, un- -
specified
0 1 1 0 0 0 1 49. Quality of service Note 9
unavailable
0 1 1 0 0 1 0 50. Requested facility not sub- Note 1
scribed
0 1 1 0 1 1 1 55. Incoming calls barred with- Note 1
in the CUG
0 1 1 1 0 0 1 57. Bearer capability not au- Note 3
thorized
0 1 1 1 0 1 0 58. Bearer capability not pre- Note 3
sently available
0 1 1 1 1 1 1 63. Service or option not -
available, unspecified
1 0 0 0 0 0 1 65. Bearer service not Note 3
implemented
(continued...)
ETSI
Table 10.5.123/GSM 04.08 (concluded): Cause information element values
Cause value Cause Cause Diag- Remarks
Class Value number nostic

7 6 5 4 3 2 1

1 0 0 0 1 0 0 68. ACM equal to or greater
than ACMmax
1 0 0 0 1 0 1 69. Requested facility not Note 1
implemented
1 0 0 0 1 1 0 70. Only restricted digital
information bearer
capability is available
1 0 0 1 1 1 1 79. Service or option not -
implemented, unspecified
1 0 1 0 0 0 1 81. Invalid transaction iden-
tifier value -
1 0 1 0 1 1 1 87. User not member of CUG Note 1

1 0 1 1 0 0 0 88. Incompatible destination Incompatible
parameter
(Note 2)
1 0 1 1 0 1 1 91. Invalid transit network se- -
lection
1 0 1 1 1 1 1 95. Semantically incorrect -
message -
1 1 0 0 0 0 0 96. Invalid mandatory informa- Information
tion element
identifier(s)
1 1 0 0 0 0 1 97. Message type non-existent Message type
or not implemented
1 1 0 0 0 1 0 98. Message type not compatible Message type
with protocol state
1 1 0 0 0 1 1 99. Information element non-ex- Information
istent or not implemented element
identifier(s)
(notes 6,7)
1 1 0 0 1 0 0 100. Conditional IE error Information
element
identifier(s)
(note 6)
1 1 0 0 1 0 1 101. Message not compatible with Message type
protocol state
1 1 0 0 1 1 0 102. Recovery on timer expiry Timer number
(note 8)
1 1 0 1 1 1 1 111. Protocol error, unspecified -
1 1 1 1 1 1 1 127. Interworking, unspecified -
All other values in the range 0 to 31 shall be treated as cause 31.
NOTE 1: Diagnostics for supplementary services are handled as follows:
octet 5, bit 8:
This is an extension bit as defined in the preliminary part of section 10.5. In this version of this protocol,
this bit shall be set to 1. If it is set to zero, the contents of the following octets shall be ignored.
octet 5, bit 7-1:
0000001 - Outgoing calls barred within CUG
0000010 - No CUG selected
ETSI
0000011 - Unknown CUG index
0000100 - CUG index incompatible with requested basic service
0000101 - CUG call failure, unspecified
0000110 - CLIR not subscribed
0000111 - CCBS possible
0001000 - CCBS not possible
All other values shall be ignored.
NOTE 2: The incompatible parameter is composed of the incompatible information element identifier.
NOTE 3: The format of the diagnostic field for cause numbers 57, 58 and 65 is as shown in
figure 10.5.88/GSM 04.08 and tables 10.5.102/GSM 04.08 to 10.5.115/GSM 04.08.
NOTE 4: The user supplied diagnostics field is encoded according to the user specification, subject to the maximum
length of the cause information element. The coding of user supplied diagnostics should be made in such a
way that it does not conflict with the coding described in note 9 below.
NOTE 5: The new destination is formatted as the called party BCD number information element, including
information element identifier.
NOTE 6: Locking and non-locking shift procedures described in sections 10.5.4.2 and 3 are applied. In principle,
information element identifiers are ordered in the same order as the information elements in the received
message.
NOTE 7: When only the locking shift information element is included and no information element identifier
follows, it means that the codeset in the locking shift itself is not implemented.
NOTE 8: The timer number is coded in IA5 characters, e.g., T308 is coded as "3" "0" "8". The following coding is
used in each octet:
bit 8 : spare "0"
bits 7-1 : IA5 character
Octet 5 carries "3", octet 5a carries "0", etc.
NOTE 9: The following coding is used for octet 5:
bit 8 : 1
bits 7-3 : 00000
bits 2-1 : condition as follows:
00 - unknown
01 - permanent
10 - transient
10.5.4.11a CLIR suppression
The CLIR suppression information element may be sent by the mobile station to the network in the SETUP message.
The use is defined in GSM 04.81.
The CLIR suppression information element is coded as shown in figure 10.5.96/GSM 04.08.
The CLIR suppression is a type 2 information element.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
CLIR suppression IEI octet 1
+-----------------------------------------------+
Figure 10.5.96/GSM 04.08: CLIR suppression information element
10.5.4.11b CLIR invocation
The CLIR invocation information element may be sent by the mobile station to the network in the SETUP message. The
use is defined in GSM 04.81.
The CLIR invocation information element is coded as shown in figure 10.5.97/GSM 04.08.
The CLIR invocation is a type 2 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
CLIR invocation IEI octet 1
+-----------------------------------------------+
Figure 10.5.97/GSM 04.08: CLIR invocation information element
10.5.4.12 Congestion level
The purpose of the congestion level information element is to describe the congestion status of the call.
The congestion level information element is coded as shown in figure 10.5.98/GSM 04.08 and
table 10.5.124/GSM 04.08.
The congestion level is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Congestion level octet 1
IEI
+-----------------------------------------------+
Figure 10.5.98/GSM 04.08: Congestion level information element
Table 10.5.124/GSM 04.08: Congestion level information element
+-------------------------------------------------+
Congestion level (octet 1)
bits
4 3 2 1
0 0 0 0 receiver ready
1 1 1 1 receiver not ready

+-------------------------------------------------+
10.5.4.13 Connected number
The purpose of the connected number information element is to identify the connected party of a call.
The connected number information element is coded as shown in figure 10.5.99/GSM 04.08
The connected number is a type 4 information element with a minimum length of 3 octets and a maximum length of 14
octets.
ETSI
8 7 6 5 4 3 2 1
+------------------------------------------------+
Connected number IEI octet 1
+------------------------------------------------
Length of connected number contents octet 2
+------------------------------------------------
0/1 Type of number Number plan octet 3
ext identification note 1)
+------+-----------------------------------------
1 Presentation 0 0 0 Screening octet 3a*
ext indicator Spare indicator note 1)
+------------------------------------------------
+------------------------+----------------------- note 1)
+------------------------+----------------------- note 1)
note 2) :
+------------------------------------------------+ :
Figure 10.5.99/GSM 04.08
The contents of octets 3,4,5, etc. ... are coded as shown in table 10.5.118/GSM 04.08. The coding of octet 3a is defined
in table 10.5.120/GSM 04.08.
If the connected number contains an odd number of digits, bits 5 to 8 of the last octet shall be filled with the end mark
coded as "1111".
10.5.4.14 Connected subaddress
The purpose of the connected subaddress information element is to identify a subaddress associated with the connected
party of a call.
The connected subaddress information element is coded as shown in figure 10.5.100/GSM 04.08
The connected subaddress is a type 4 information element with a minimum length of 2 octets and a maximum length of
23 octets.
8 7 6 5 4 3 2 1
+------------------------------------------------+
Connected subaddress IEI octet 1
+------------------------------------------------
Length of connected subaddress contents octet 2
+------------------------------------------------
1 Type of odd/even 0 0 0 octet 3*
ext subaddress indicator Spare
+------------------------------------------------
: : :
: : : etc.
+------------------------------------------------+
Figure 10.5.100/GSM 04.08
The coding for Type of subaddress, odd/even indicator, and subaddress information is in table 10.5.119/GSM 04.08.
10.5.4.15 Facility
The purpose of the facility information element is to transport supplementary service related information. Within the
scope of GSM 04.08 the content of the Facility information field is an array of octets. The usage of this transportation
mechanism is defined in GSM 04.80.
The facility information element is coded as shown in figure 10.5.101/GSM 04.08
The facility is a type 4 information element with a minimum length of 2 octets. No upper length limit is specified except
for that given by the maximum number of octets in a L3 message (see GSM 04.06).
ETSI
8 7 6 5 4 3 2 1
+------------------------------------------------+
Facility IEI octet 1
+------------------------------------------------
Length of facility contents octet 2
+------------------------------------------------
Facility information (see GSM04.80) octet 3-?*
+------------------------------------------------+
Figure 10.5.101/GSM 04.08
The purpose of the high layer compatibility information element is to provide a means which should be used by the
remote user for compatibility checking. See annex B.
The high layer compatibility information element is coded as shown in figure 10.5.102/GSM 04.08 and
table 10.5.125/GSM 04.08.
The high layer compatibility is a type 4 information element with a minimum length of 2 octets and a maximum length
of 5 octets.
NOTE: The high layer compatibility information element is transported transparently by a PLMN between a call
originating entity (e.g. a calling user) and the addressed entity (e.g. a remote user or a high layer function
network node addressed by the call originating entity). However, if explicitly requested by the user (at
subscription time), a network which provides some capabilities to realize teleservices may interpret this
information to provide a particular service.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
High layer compatibility IEI octet 1
+-----------------------------------------------

Length of high layer compatibility contents octet 2
+-----------------------------------------------
1 coding presentat.
ext standard interpretation method of octet 3*
protocol
profile
+-----+-----------------------------------------
0/1 octet 4*
ext High layer characteristics identification
+-----+-----------------------------------------
1 Extended high layer characteristics octet 4a*
ext identification (note)
+-----------------------------------------------+
Figure 10.5.102/GSM 04.08: High layer compatibility information element
If the value part of the IE is empty, the IE indicates "not applicable".
NOTE: Octet 4a may be present e.g. when octet 4 indicates Maintenance or Management.
ETSI
Table 10.5.125/GSM 04.08: High layer compatibility information element
+------------------------------------------------------+
see CCITT Recommendation Q.931.

Interpretation (octet 3)

Presentation method of protocol profile (octet 3)

High layer characteristics identification (octet 4)

Extended high layer characteristics identification
(octet 4a)
+------------------------------------------------------+
10.5.4.16.1 Static conditions for the high layer compatibility IE contents
Either the value part of the IE is empty, or it contains at least octet 3 and 4.
10.5.4.17 Keypad facility
The purpose of the keypad facility information element is to convey IA5 characters, e.g. entered by means of a terminal
keypad. (Note).
The keypad facility information element is coded as shown in figure 10.5.103/GSM 04.08.
The keypad facility is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Keypad facility IEI octet 1
+-----+-----------------------------------------
Spare
0 Keypad information (IA5 character) octet 2
+-----------------------------------------------+
Figure 10.5.103/GSM 04.08: Keypad facility information element
NOTE: In the GSM system this information element is only used to transfer one DTMF digit (0, 1, ... , 9, A, B, C,
D, *, #) as one IA5 character.
The purpose of the low layer compatibility information element is to provide a means which should be used for
compatibility checking by an addressed entity (e.g., a remote user or an interworking unit or a high layer function
network node addressed by the calling user). The low layer compatibility information element is transferred
transparently by a PLMN between the call originating entity (e.g. the calling user) and the addressed entity.
Except for the information element identifier, the low layer compatibility information element is coded as in ETS 300
102-1.
The low layer compatibility is a type 4 information element with a minimum length of 2 octets and a maximum length of
15 octets.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Low layer compatibility IEI octet 1
+-----------------------------------------------
Length of the low layer compatibility contents octet 2
+-----------------------------------------------
octet 3*
The following octets are coded
as described in ETS 300 102-1 :

:
+-----------------------------------------------+
Figure 10.5.104/GSM 04.08: Low layer compatibility information element
If the value part of the IE is empty, the IE indicates "not applicable".
10.5.4.19 More data
The more data information element is sent by the mobile station to the network or to the network to the mobile station in
a USER INFORMATION message. The presence of the more data information element indicates to the destination
remote user/mobile station that another USER INFORMATION message will follow containing information belonging
to the same block.
The use of the more data information element is not supervised by the network.
The more data information element is coded as shown in figure 10.5.105/GSM 04.08.
The more data is a type 2 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
More data IEI octet 1
+-----------------------------------------------+
Figure 10.5.105/GSM 04.08: More data information element
10.5.4.20 Notification indicator
The purpose of the notification indicator information element is to indicate information pertaining to a call.
The notification indicator element is coded as shown in figure 10.5.106/GSM 04.08 and table 10.5.126/ GSM 04.08.
The notification indicator is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Notification indicator IEI octet 1
+-----+-----------------------------------------
1 octet 2
ext Notification description
+-----------------------------------------------+
Figure 10.5.106/GSM 04.08: Notification indicator information element
ETSI
Table 10.5.126/GSM 04.08: Notification indicator information element
+------------------------------------------+
Notification description (octet 2)
Bits
7 6 5 4 3 2 1
0 0 0 0 0 0 0 User suspended
0 0 0 0 0 0 1 User resumed
0 0 0 0 0 1 0 Bearer change

+------------------------------------------+
10.5.4.21 Progress indicator
The purpose of the progress indicator information element is to describe an event which has occurred during the life of a
call.
The progress indicator information element is coded as shown in figure 10.5.107/GSM 04.08 and
table 10.5.127/GSM 04.08.
The progress indicator is a type 4 information element with a length of 4 octets.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Progress indicator IEI octet 1
+-----------------------------------------------

Length of progress indicator contents octet 2
+-----------------------------------------------
1 coding 0
ext standard spare location octet 3
+-----+-----------------------------------------
1 octet 4
ext progress description
+-----------------------------------------------+
Figure 10.5.107/GSM 04.08: Progress indicator information element
ETSI
Table 10.5.127/GSM 04.08: Progress indicator information element
+-----------------------------------------------------------+
Bits
7 6
0 0 Standardized coding, as described in CCITT Rec.
Q.931
0 1 Reserved for other international standards
1 0 National standard
1 1 Standard defined for the GSMPLMNS as described
below

Coding standards other than "1 1 - Standard defined for
the GSMPLMNS" shall not be used if the progress
description can be represented with the GSMstandardized
coding.

PLMNS".
If a progress indicator IE indicating a coding standard
not supported by the receiver is received, progress
description "Unspecific" shall be assumed.

Location (octet 3)
Bits
4 3 2 1
0 0 0 0 User
0 0 0 1 Private network serving the local user
0 0 1 0 Public network serving the local user
0 1 0 0 Public network serving the remote user
0 1 0 1 Private network serving the remote user
1 0 1 0 Network beyond interworking point


Note: Depending on the location of the users, the local
public network and remote public network may be
the same network.

Progress description (octet 4)
Bits
7 6 5 4 3 2 1 No.
0 0 0 0 0 0 1 1. Call is not end-to-end PLMN/ISDN,
further call progress information may
be available in-band
0 0 0 0 0 1 0 2. Destination address in non-PLMN/ISDN
0 0 0 0 0 1 1 3. Origination address in non-PLMN/ISDN
0 0 0 0 1 0 0 4. Call has returned to the PLMN/ISDN
0 0 0 1 0 0 0 8. In-band information or appropriate
pattern now available
0 1 0 0 0 0 0 32. Call is end-to-end PLMN/ISDN
1 0 0 0 0 0 0 64. Queueing
All other values Unspecific
+-----------------------------------------------------------+
10.5.4.21a Recall type $(CCBS)$
The purpose of the recall type information element is to describe the reason for the recall.
The recall type information element is coded as shown in Figure 10.5.108/GSM 04.08 and Table 10.5.128/GSM 04.08.
The recall type is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
recall type IEI octet 1
+-----------------------------------------------
spare recall type
0 0 0 0 0 octet 2
+-----------------------------------------------+
Figure 10.5.108/GSM 04.08: Recall type information element
ETSI
Table 10.5.128/GSM 04.08: Recall type information element
+--------------------------------------------------------------+
recall type (octet 2, bits 1 to 4)
Bits
3 2 1
0 0 0 - CCBS
0 0 1 }
to }- shall be treated as CCBS (intended for other
1 1 0 } similar types of Recall)
1 1 1 - reserved
+--------------------------------------------------------------+
10.5.4.21b Redirecting party BCD number
The purpose of the redirecting party BCD number information element is to identify the redirecting party.
The redirecting party BCD number information element is coded as shown in Figure 10.88a.
The redirecting party BCD number is a type 4 information element. In the network to mobile station direction it has a
minimum length of 3 octets and a maximum length of 19 octets.
8 7 6 5 4 3 2 1
Redirecting party BCD number IEI octet 1
Length of redirecting party BCD number contents octet 2
0/1
ext
type of
number
Numbering plan
identification
octet 3
(note 1)
1
ext
presentat.
indicator
0 0 0
spare
Screening
indicator
octet 3a*
(note 1)
Number digit 2 Number digit 1
octet 4*
(note 1)
Number digit 4 Number digit 3
octet 5*
(note 1)
:
Note 2) :
Figure 10.88a/GSM 04.08:
Redirecting party BCD number information element
Note 1: The contents of octets 3, 4, etc. are coded as shown in Table 10.81. The coding of octet
3a is defined in Table 10.83.
Note 2: If the redirecting party BCD number contains an odd number of digits, bits 5 to 8 of the last
octet shall be filled with an end mark coded as "1111".
10.5.4.21c Redirecting party subaddress
The purpose of the Redirecting party subaddress is to identify a subaddress associated with the redirecting party. For the
definition of a subaddress see Rec. CCITT I.330.
The Redirecting party subaddress information element is coded as shown in Figure 10.88b and Table 10.84.
The Redirecting party subaddress is a type 4 information element with a minimum length of 2 octets and a maximum
length of 23 octets.
ETSI
8 7 6 5 4 3 2 1
Redirecting party Subaddress IEI octet 1
Length of redirecting party subaddress contents octet 2
1
ext
type of
subaddress
odd/ev
Indica
0 0 0
octet 3*
Subaddress information
:
octet 4*
:
etc.
Figure 10.88b/GSM 04.08:
Redirecting party subaddress information element
The purpose of the repeat indicator information element is to indicate how the associated repeated information elements
shall be interpreted, when included in a message. The repeat indicator information element is included immediately
before the first occurrence of the associated information element which will be repeated in a message. "Mode 1" refers
to the first occurrence of that information element, "mode 2" refers to the second occurrence of that information element
in the same message.
The repeat indicator information element is coded as shown in figure 10.5.109/GSM 04.08 and
table 10.5.129/GSM 04.08.
The repeat indicator is a type 1 information element.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
repeat indicator repeat indication octet 1
IEI
+-----------------------------------------------+
Figure 10.5.109/GSM 04.08: Repeat indicator information element
Table 10.5.129/GSM 04.08: Repeat indicator information element
+----------------------------------------------------------+
Repeat indication (octet 1)
Bits
4 3 2 1
0 0 0 1 Circular for successive selection
"mode 1 alternate mode 2"
0 0 1 1 Sequential for successive selection
"mode 1 and then mode 2"


+----------------------------------------------------------+
10.5.4.22a Reverse call setup direction
This information element may be included in a MODIFY and MODIFY COMPLETE message to indicate that the
direction of the data call to which the MODIFY message relates is opposite to the call setup direction.
The reverse call setup direction information element is coded as shown in figure 10.5.110/GSM 04.08.
The reverse call setup direction is a type 2 information element
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
reverse call setup direction IEI octet 1
+-----------------------------------------------+
Figure 10.5.110/GSM 04.08: Reverse call setup direction information element
10.5.4.22b SETUP Container $(CCBS)$
This information element contains the contents of a SETUP message (Mobile Station to Network). This means that the
Call Control protocol discriminator IE, the Transaction Identifier IE and the Setup message type IE are not included.
The SETUP Container information element is coded as shown in figure 10.5.111/GSM 04.08
The SETUP Container is a type 4 information. No upper length limit is specified except for that given by the maximum
number of octets in a L3 message (see GSM 04.06).
8 7 6 5 4 3 2 1
+------------------------------------------------+
SETUP Container IEI octet 1
+------------------------------------------------
Length of SETUP container contents octet 2
+------------------------------------------------
SETUP message octet 3-n
+------------------------------------------------+
Figure 10.5.111/GSM 04.08: Octet j (j = 3, 4 ... n) is the unchanged octet j of the SETUP message
10.5.4.23 Signal
The purpose of the signal information element is to allow the network to convey information to a user regarding tones
and alerting signals (see sections 5.2.2.3.2 and 7.3.3.).
The signal information element is coded as shown in figure 10.5.112/GSM 04.08 and table 10.5.130/GSM 04.08.
The signal is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Signal IEI octet 1
+-----------------------------------------------

Signal value octet 2
+-----------------------------------------------+
Figure 10.5.112/GSM 04.08: Signal information element
ETSI
Table 10.5.130/GSM 04.08: Signal information element
+------------------------------------------------------+
Signal value (octet 2)
Bits
8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 dial tone on
0 0 0 0 0 0 0 1 ring back tone on
0 0 0 0 0 0 1 0 intercept tone on
0 0 0 0 0 0 1 1 network congestion tone on
0 0 0 0 0 1 0 0 busy tone on
0 0 0 0 0 1 0 1 confirm tone on
0 0 0 0 0 1 1 0 answer tone on
0 0 0 0 0 1 1 1 call waiting tone on
0 0 0 0 1 0 0 0 off-hook warning tone on
0 0 1 1 1 1 1 1 tones off
0 1 0 0 1 1 1 1 alerting off

+------------------------------------------------------+
10.5.4.24 SS Version Indicator
The purpose of the SS version indicator information element is to aid the decoding of the Facility information element as
described in GSM 04.10. Within the scope of GSM 04.08 the contents of the SS Version information field is an array of
one or more octets. The usage of the SS version information field is defined in GSM 04.80.
The SS version indicator information element is coded as shown in figure 10.5.113/GSM 04.08
The SS version indicator is a type 4 information element with a minimum length of 2 octets. No upper length limit is
specified except for that given by the maximum number of octets in a L3 message (see GSM 04.06).
8 7 6 5 4 3 2 1
+------------------------------------------------+
SS version indicator IEI octet 1
+------------------------------------------------
Length of SS version indicator contents octet 2
+------------------------------------------------
SS version information (see GSM04.80) octet 3*

: *

: *
+------------------------------------------------+
Figure 10.5.113/GSM 04.08
NOTE: Usually, this information element has only one octet of content.
10.5.4.25 User-user
The purpose of the user-user information element is to convey information between the mobile station and the remote
ISDN user.
The user-user information element is coded as shown in figure 10.5.114/GSM 04.08 and table 10.5.131/ GSM 04.08.
There are no restrictions on the content of the user-user information field.
The user-user is a type 4 information element with a minimum length of 3 octets and a maximum length of either 35 or
131 octets. In the SETUP message the user-user information element has a maximum size of 35 octets in a GSM PLMN.
In the USER INFORMATION, ALERTING, CONNECT, DISCONNECT, PROGRESS, RELEASE and RELEASE
COMPLETE messages the user-user information element has a maximum size of 131 octets in a GSM PLMN.
In other networks than GSM PLMNs the maximum size of the user-user information element is 35 or 131 octets in the
messages mentioned above. The evolution to a single maximum value is the long term objective; the exact maximum
value is the subject of further study.
NOTE: The user-user information element is transported transparently through a GSM PLMN.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
User-user IEI octet 1
+-----------------------------------------------

Length of user-user contents octet 2
+-----------------------------------------------
User-user protocol discriminator octet 3

+-----------------------------------------------
User-user information octet 4*
: :
: :
octet N*
+-----------------------------------------------+
Figure 10.5.114/GSM 04.08: User-user information element
Table 10.5.131/GSM 04.08: User-user information element
+------------------------------------------------------------+
User-user protocol discriminator (octet 3)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 User specific protocol (Note 1)
0 0 0 0 0 0 0 1 OSI high layer protocols
0 0 0 0 0 0 1 0 X.244 (Note 2)
0 0 0 0 0 0 1 1 Reserved for system management
convergence function
0 0 0 0 0 1 0 0 IA5 characters (Note 3)
0 0 0 0 0 1 1 1 Rec.V.120 rate adaption
0 0 0 0 1 0 0 0 Q.931 (I.451) user-network call control
messages

0 0 0 1 0 0 0 0 Reserved for other network layer or
through layer 3 protocols including Rec.X.25
0 0 1 1 1 1 1 1 (Note 4)

0 1 0 0 0 0 0 0
through National use
0 1 0 0 1 1 1 1

0 1 0 1 0 0 0 0 Reserved for other network
through layer or layer 3 protocols
1 1 1 1 1 1 1 0 including Rec.X.25 (Note 4)


Note 1: The user information is structured according to user
needs.

Note 2: The user information is structured according to
Rec.X.244 which specifies the structure of X.25 call
user data.

Note 3: The user information consists of IA5 characters.

Note 4: These values are reserved to discriminate these
protocol discriminators from the first octet of a
X.25 packet including general format identifier.
+------------------------------------------------------------+
10.5.4.26 Alerting Pattern $(NIA)$
The purpose of the Alerting Pattern information element is to allow the network to convey information related to the
alert to be used by the MS (see GSM 02.07).
The Alerting Pattern information element is coded as shown in figure 10.5.115/GSM 04.08 and
table 10.5.132/GSM 04.08.
The Alerting Pattern IE is a type 4 information element with 3 octet length.
ETSI
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Alerting Pattern IEI octet 1
+-----------------------------------------------
length of alerting pattern content octet 2
+-----------------------------------------------
0 0 0 0 Alerting Pattern
spare value octet 3
+-----------------------------------------------+
Figure 10.5.115/GSM 04.08: Alerting Pattern information element
Table 10.5.132/GSM 04.08: Alerting Pattern information element
+------------------------------------------------------+
Alerting Pattern value (octet 3)
Bits
4 3 2 1

0 0 0 0 alerting pattern 1


all other values are reserved

+------------------------------------------------------+
Alerting pattern 1, 2 and 3 indicate alerting levels 0, 1 and 2.
Alerting pattern 5 to 9 indicate alerting categories 1 to 5
10.5.4.27 Allowed actions $(CCBS)$
The purpose of the Allowed actions information element is to provide the mobile station with information about further
allowed procedures.
The Allowed actions information element is coded as shown in figure 10.5.116/GSM 04.08 and table 10.5.133/GSM
04.08
The Allowed actions is a type 4 information element with 3 octets length
8 7 6 5 4 3 2 1
+-----------------------------------------------+
Allowed Actions IEI octet 1
+-----------------------------------------------

Length of allowed actions contents octet 2
+-----------------------------------------------
CCBS 0 0 0 0 0 0 0
act. spare octet 3
+-----------------------------------------------+
Figure 10.5.116/GSM 04.08: Allowed actions information element
ETSI
Table 10.5.133/GSM 04.08: Allowed actions information element
+---------------------------------------------------------+
CCBS activation (octet 3)

Bit
8
0 Activation of CCBS not possible
1 Activation of CCBS possible
+---------------------------------------------------------+
10.5.5 GPRS mobility management information elements
10.5.5.1 Attach result
The purpose of the attach result information element is to specify the result of a GPRS attach procedure.
The attach result is a type 1 information element.
The attach result information element is coded as shown in figure 10.5.117/GSM 04.08 and table 10.5.134/GSM 04.08.
8 7 6 5 4 3 2 1
Attach result
IEI
0
spare
Result of
attach
octet 1
Figure 10.5.117/GSM 04.08: Attach result information element
Table 10.5.134/GSM 04.08: Attach result information element
Result of attach (octet 1)
Bits
3 2 1
0 0 1 GPRS only attached
0 1 1 Combined GPRS/IMSI attached
10.5.5.2 Attach type
The purpose of the attach type information element is to indicate the type of the requested attach, i.e. whether the MS
wants to perform a GPRS or combined GPRS attach.
The attach type is a type 1 information element.
The attach type information element is coded as shown in figure 10.5.118/GSM 04.08 and table 10.5.135/GSM 04.08.
8 7 6 5 4 3 2 1
Attach type
IEI
0
spare
Type of attach octet 1
Figure 10.5.118/GSM 04.08: Attach type information element
Table 10.5.135/GSM 04.08: Attach type information element
Type of attach (octet 1)
Bits
3 2 1
0 0 1 GPRS attach
0 1 0 GPRS attach while IMSI attached
0 1 1 Combined GPRS/IMSI attach
All other values are interpreted as GPRS
attach in this version of the protocol.
ETSI
10.5.5.3 Ciphering algorithm
The purpose of the ciphering algorithm information element is to specify which ciphering algorithm shall be used.
The ciphering algorithm is a type 1 information element.
The ciphering algorithm information element is coded as shown in figure 10.5.119/GSM 04.08 and
table 10.5.136/GSM 04.08.
8 7 6 5 4 3 2 1
Ciphering algorithm
IEI
0
spare
Type of
algorithm
octet 1
Figure 10.5.119/GSM 04.08: Ciphering algorithm information element
Table 10.5.136/GSM 04.08: Ciphering algorithm information element
Type of ciphering algorithm (octet 1)
Bits
3 2 1
0 0 0 ciphering not used
0 0 1 GPRS Encryption Algorithm GEA/1
All other values are interpreted reserved
by this version of the protocol.
10.5.5.4 [Spare]TMSI status
The purpose of the TMSI status information element is to indicate whether a valid TMSI is available in the MS or not.
The TMSI status is a type 1 information element.
The TMSI status information element is coded as shown in figure 10.5.120/GSM 04.08 and table 10.5.137/GSM 04.08.
8 7 6 5 4 3 2 1
TMSI status
IEI
0 0 0
spare
TMSI
flag
octet 1
Figure 10.5.120/GSM 04.08: TMSI status information element
Table 10.5.137/GSM 04.08: TMSI status information element
TMSI flag (octet 1)
Bit
1
0 no valid TMSI available
1 valid TMSI available
10.5.5.5 Detach type
The purpose of the detach type information element is to indicate which type of detach is requested by the MS. In the
network to MS direction the detach type information element is used to indicate the reason why a detach request is sent.
The detach type is a type 1 information element.
The detach type information element is coded as shown in figure 10.5.121/GSM 04.08 and table 10.5.138/GSM 04.08.
ETSI
8 7 6 5 4 3 2 1
Detach type
IEI
Power
off
Type of detach octet 1
Figure 10.5.121/GSM 04.08: Detach type information element
Table 10.5.138/GSM 04.08: Detach type information element
Type of detach (octet 1)
In the MS to network direction:
Bits
3 2 1
0 0 1 GPRS detach
0 1 0 IMSI detach
0 1 1 Combined GPRS/IMSI detach
All other values are interpreted as
Combined GPRS/IMSI detach by this version
of the protocol.
In the network to MS direction:
Bits
3 2 1
0 0 1 re-attach required
0 1 0 re-attach not required
0 1 1 IMSI detach (after VLR failure)
All other values are interpreted as re-
attach not required by this version of
the protocol.
Power off (octet 1)
In the MS to network direction:
Bit
4
0 normal detach
1 power switched off
In the network to MS direction the Power
off bit shall be spare and set to zero.
10.5.5.6 DRX parameter
The purpose of the DRX parameter information element is to indicate whether the MS uses DRX mode or not.
The DRX parameter is a type 3 information element with a length of 3 octets.
The value part of a DRX parameter information element is coded as shown in table 10.5.139/GSM 04.08.
8 7 6 5 4 3 2 1
DRX parameter IEI octet 1
SPLIT PG CYCLE CODE octet 2
0 0 0 0
spare
SPLIT
on
CCCH
non-DRX
timer octet 3
Figure 10.5.122/GSM 04.08: DRX parameter information element
ETSI
Table 10.5.139/GSM 04.08: DRX parameter information element
SPLIT PG CYCLE CODE, octet 2
The octet contains the binary coded value of the SPLIT PG CYCLE
CODE. The SPLIT PG CYCLE value is derived from the SPLIT PG
CYCLE CODE as follows:
SPLIT PG CYCLE CODE SPLIT PG CYCLE value
0 704 (equivalent to no DRX)
1 to 64 1 to 64, respectively
65 71
66 72
67 74
68 75
69 77
70 79
71 80
72 83
73 86
74 88
75 90
76 92
77 96
78 101
79 103
80 107
81 112
82 116
83 118
84 128
85 141
86 144
87 150
88 160
89 171
90 176
91 192
92 214
93 224
94 235
95 256
96 288
97 320
98 352
All other values are reserved and shall be interpreted as 1 by this version of the protocol.
SPLIT on CCCH, octet 3 (bit 4)
0 Split pg cycle on CCCH is not supported by the mobile station
1 Split pg cycle on CCCH is supported by the mobile station
non-DRX timer, octet 3
bit
3 2 1
0 0 0 no non-DRX mode after transfer state
0 0 1 max. 1 sec non-DRX mode after transfer state
Bits 8 to 5 of octet 3 are spare and shall be coded all zeros.
ETSI
10.5.5.7 Force to standby
The purpose of the force to standby information element is to force the MS to stop the READY timer in order to prevent
the MS to perform cell updates.
The force to standby is a type 1 information element.
The force to standby information element is coded as shown in figure 10.5.123/GSM 04.08 and
table 10.5.140/GSM 04.08.
8 7 6 5 4 3 2 1
Force to standby
IEI
0
spare
Force to
standby value
octet 1
Figure 10.5.123/GSM 04.08: Force to standby information element
Table 10.5.140/GSM 04.08: Force to standby information element
Force to standby value (octet 1)
Bits
3 2 1
0 0 0 Force to standby not indicated
0 0 1 Force to standby indicated
force to standby not indicated by this
version of the protocol.
The purpose of the P-TMSI signature information element is to identify a GMM context of an MS.
The P-TMSI signature is a type 3 information element with 4 octets length.
The P-TMSI signature information element is coded as shown in figure 10.5.124/GSM 04.08 and
table 10.5.141/GSM 04.08.
8 7 6 5 4 3 2 1
P-TMSI signature IEI octet 1
P-TMSI signature value
octet 2
octet 4
Figure 10.5.124/GSM 04.08: P-TMSI signature information element
Table 10.5.141/GSM 04.08: P-TMSI signature information element
P-TMSI signature value
Octets 2, 3 and 4 contain the binary
representation of the P-TMSI signature.
Bit 1 of octet 4 is the least significant
bit and bit 8 of octet 2 is the most
significant bit.
10.5.5.9 Identity type 2
The purpose of the identity type 2 information element is to specify which identity is requested.
The identity type 2 is a type 1 information element.
ETSI
The identity type 2 information element is coded as shown in figure 10.5.125/GSM 04.08 and
table 10.5.142/GSM 04.08.
8 7 6 5 4 3 2 1
Identity type 2
IEI
0
spare
Type of
identity
octet 1
Figure 10.5.125/GSM 04.08: Identity type 2 information element
Table 10.5.142/GSM 04.08: Identity type 2 information element
Bits
3 2 1
0 0 1 IMSI
0 1 0 IMEI
0 1 1 IMEISV
1 0 0 TMSI
IMSI by this version of the protocol.
10.5.5.10 IMEISV request
The purpose of the IMEISV request information element is to indicate that the IMEISV shall be included by the MS in
the authentication and ciphering response message.
The IMEISV request is a type 1 information element.
The IMEISV request information element is coded as shown in figure 10.5.126/GSM 04.08 and
table 10.5.143/GSM 04.08.
8 7 6 5 4 3 2 1
IMEISV request
IEI
0
spare
IMEISV request
value
octet 1
Figure 10.5.126/GSM 04.08: IMEISV request information element
Table 10.5.143/GSM 04.08: IMEISV request information element
IMEISV request value (octet 1)
Bits
3 2 1
0 0 0 IMEISV not requested
0 0 1 IMEISV requested
IMEISV not requested by this version
of the protocol.
10.5.5.11 Receive N-PDU Numbers list
The purpose of the Receive N-PDU Numbers list information element is to specify the current SNDCP Receive N-PDU
Number values.
The Receive N-PDU Number list is a type 4 information element with a length of 4 to 19 octets.
The value part of a Receive N-PDU Number list information element is coded as shown in figure 10.5.127/GSM 04.08
and table 10.5.144/GSM 04.08.
ETSI
8 7 6 5 4 3 2 1
Receive N-PDU Number list IEI octet 1
Length of Receive N-PDU Number list
contents
octet 2
Receive N-PDU Number-list
octet 3
octet 4
octet n*
Figure 10.5.127/GSM 04.08: Receive N-PDU Number list information element
Table 10.5.144/GSM 04.08: Receive N-PDU Number list information element
Receive N-PDU Number -list value ::=
{
< Receive N-PDU Number -list >
< Padding bits>
} ;
< Receive N-PDU Number-list > ::= < sapi : bit-string(4) > < Receive N-PDU
Number-value : bit-string(8) > { < Receive N-PDU Number-list> | < null > } ;
< nsapi > ::=
{ 0101 }; |-- NSAPI 5
{ 0110 }; | -- NSAPI 6
{ 0111 }; | -- NSAPI 7
{ 1000 }; | -- NSAPI 8
{ 1001 }; | -- NSAPI 9
{ 1010 }; | -- NSAPI 10
{ 1011 }; | -- NSAPI 11
{ 1100 }; | -- NSAPI 12
{ 1101 }; | -- NSAPI 13
{ 1110 }; | -- NSAPI 14
{ 1111 }; -- NSAPI 15
< Receive N-PDU Number-value > ::= { 0 | 1} (8) ;
-- Contains the binary coded representation of the receive N-PDU Number value.
-- The first bit in transmission order is the most significant bit.
<Padding bits> ::= null | 0000;
10.5.5.12 MS network capability
The purpose of the MS network capability information element is to provide the network with information concerning
aspects of the mobile station related to GPRS. The contents might affect the manner in which the network handles the
operation of the mobile station. The MS network capability information indicates general mobile station characteristics
and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent
on.
The MS network capability is a type 4 information element with a maximum of 3 octets length.
The value part of a MS network capabilityinformation element is coded as shown in figure 10.5.128/GSM 04.08 and
table 10.5.145/GSM 04.08.
ETSI
8 7 6 5 4 3 2 1
MS network capability IEI octet 1
Length of MS network capability contents octet 2
MS network capability value octet 3
Figure 10.5.128/GSM 04.08: MS network capability information element
Table 10.5.145/GSM 04.08: MS network capability information element
<MS network capability value part> ::=
<GEA bits>
<SM capabilities via dedicated channels: bit>
<SM capabilities via GPRS channels: bit>
<UCS2 support: bit>
<SS Screening Indicator: bit string(2)>
<SoLSA Capability : bit>
<Spare bits>;
<GEA bits> ::= < GEA/1 :bit>;
<Spare bits> ::= null | {<spare bit> < Spare bits >};
SS Screening Indicator
SM capabilities via dedicated channels
0 Mobile station does not support mobile terminated point to point SMS via
dedicated signalling channels
1 Mobile station supports mobile terminated point to point SMS via dedicated
signalling channels
SM capabilities via GPRS channels
0 Mobile station does not support mobile terminated point to point SMS via
GPRS packet data channels
1 Mobile station supports mobile terminated point to point SMS via GPRS
packet data channels
UCS2 support
This information field indicates the likely treatment by the mobile station of UCS2 encoded character strings.
0 the ME has a preference for the default alphabet (defined in GSM 03.38)
over UCS2.
1 the ME has no preference between the use of the default alphabet and the
use of UCS2.
GPRS Encryption Algorithm GEA/1
0 encryption algorithm GEA/1not available
1 encryption algorithm GEA/1 available
SoLSA Capability
0 The ME does not support SoLSA.
1 The ME supports SoLSA.
ETSI
10.5.5.12a MS Radio Access capability
The purpose of the MS RA capability information element is to provide the radio part of the network with information
concerning radio aspects of the mobile station. The contents might affect the manner in which the network handles the
operation of the mobile station.
The MS RA capability is a type 4 information element, with a minimum length of 6 octets and a maximum length of 14
octets.
The value part of a MS RA capability information element is coded a shown table 10.5.146/GSM 04.08.
SEMANTIC RULE : Among the three Access Type Technologies GSM 900-P, GSM 900-E and GSM 900-R
only one shall be present.
Error handling : If a received Access Technology Type is unknown to the receiver, it shall ignore all the
corresponding fields;
If within a known Access Technology Type a receiver recognizes an unknown field it shall ignore it.
See more details about error handling of MS radio access capability in TS GSM 08.18.
- Due to shared radio frequency channel numbers between 1800 and 1900, the mobile should provide MS Radio
Access capability for either 900/1800 band(s) OR 1900 band.
Table 10.5.146/GSM 04.08: Mobile Station Radio Access Capability Information Element
< MS Radio Access capability IE > ::=
<MS Radio Access capability IEI : 00100100 >
<Length of MS RA capability: <octet>> -- length in octets of MS RA capability value part and spare bits
<MS RA capability value part : < MS RA capability value part struct >>
<spare bits>**; -- may be used for future enhancements
<MS RA capability value part struct >::= --recursive structure allows any number of Access technologies
< Access Technology Type: bit (4) >
< Access capabilities : <Access capabilities struct> >
{ 0 | 1 <MS RA capability value part struct> } ;
< Access capabilities struct > ::=
< Length : bit (7) > -- length in bits of Content and spare bits
<Access capabilities : <Content>>
<spare bits>** ; -- expands to the indicated length
-- may be used for future enhancements
< Content > ::=
< RF Power Capability : bit (3) >
{ 0 | 1 <A5 bits : <A5 bits> > } -- zero means that the same values apply for parameters as in the immediately
preceeding Access capabilities field within this IE
-- The presence of the A5 bits is mandatory in the 1
st
Access capabilities struct within this IE.
< ES IND : bit >
< PS : bit >
< VGCS : bit >
< VBS : bit >
{ 0 | 1 < Multislot capability : Multislot capability struct > } ; -- zero means that the same values apply for
multislot parameters as in the immediately preceeding Access capabilities field within this IE.
-- The presence of the Multislot capability struct is mandatory in the 1
st
Access capabilities struct within this IE.
< Multislot capability struct > ::=
{ 0 | 1 < HSCSD multislot class : bit (5) > }
{ 0 | 1 < GPRS multislot class : bit (5) > < GPRS Extended Dynamic Allocation Capability : bit > }
{ 0 | 1 < SMS_VALUE : bit (4) > < SM_VALUE : bit (4) > } ;
ETSI
<A5 bits> ::= < A5/1 : bit> <A5/2 : bit> <A5/3 : bit> <A5/4 : bit> <A5/5 : bit> <A5/6 : bit> <A5/7 : bit>; -- bits for
circuit mode ciphering algorithms
Table 10.5.146/GSM 04.08 (continued): Mobile Station Radio Access Capability Information Element
ETSI
Access Technology Type
This field indicates the access technology type to be associated with the following access capabilities.
Bits
4 3 2 1
0 0 0 0 GSM P
0 0 0 1 GSM E --note that GSM E covers GSM P
0 0 1 0 GSM R --note that GSM R covers GSM E and GSM P
0 0 1 1 GSM 1800
0 1 0 0 GSM 1900
All other values are treated as unknown by the receiver.
RF Power Capability
This field is coded as radio capability in Classmark 3 for the indicated band: it contains the binary coding of he
power class associated (see GSM 05.05 paragraph 4.1 output power and paragraph 4.1.1 Mobile Station).
A5/1
A5/2
A5/3
A5/4
A5/5
A5/6
A5/7
ES IND (Controlled early Classmark Sending)
0 "controlled early Classmark Sending" option is not implemented
1 "controlled early Classmark Sending" option is implemented
PS (Pseudo Synchronisation)
0 PS capability not present
1 PS capability present
VGCS (Voice Group Call Service)
0 no VGCS capability or no notifications wanted
1 VGCS capability and notifications wanted
VBS (Voice Broadcast Service)
0 no VBS capability or no notifications wanted
1 VBS capability and notifications wanted
HSCSD Multi Slot Class
The Multi Slot Class field is coded as the binary representation of the multislot class defined in TS GSM 05.02.
Range 1 to 18, all other values are reserved.
GPRS Multi Slot Class
The GPRS Multi Slot Class field is coded as the binary representation of the multislot class defined in TS GSM
05.02.
ETSI
Table 10.5.146/GSM 04.08 (concluded): Mobile Station Radio Access Capability Information Element
GPRS Extended Dynamic Allocation Capability
0 Extended Dynamic Allocation Capability for GPRS is not implemented
1 Extended Dynamic Allocation Capability for GPRS is implemented
SMS_VALUE (Switch-Measure-Switch) (4 bit field)
The SMS field indicates the time needed for the mobile station to switch from one radio channel to another, perform
a neighbor cell power measurement, and the switch from that radio channel to another radio channel.
Bits
4 3 2 1
. . .
(SM_VALUE) Switch-Measure (4 bit field)
The SM field indicates the time needed for the mobile station to switch from one radio channel to another and
perform a neighbor cell power measurement.
Bits
4 3 2 1
. . .
10.5.5.13 Spare
This is intentionally left spare.
10.5.5.14 GMM cause
The purpose of the GMM cause information element is to indicate the reason why a GMM request from the mobile
station is rejected by the network.
The GMM cause information element is coded as shown in figure 10.5.129/GSM 04.08 and table 10.5.147/GSM 04.08.
The GMM cause is a type 3 information element with 2 octets length.
8 7 6 5 4 3 2 1
GMM cause IEI octet 1
Cause value octet 2
Figure 10.5.129/GSM 04.08: GMM cause information element
ETSI
Table 10.5.147/GSM 04.08: GMM cause information element
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 1 0 IMSI unknown in HLR
0 0 0 0 0 0 1 1 Illegal MS
0 0 0 0 0 1 1 0 Illegal ME
0 0 0 0 0 1 1 1 GPRS services not allowed
0 0 0 0 1 0 0 0 GPRS services and non-GPRS services
not allowed
0 0 0 0 1 0 0 1 MS identity cannot be derived by the
network
0 0 0 0 1 0 1 0 Implicitly detached
0 0 0 0 1 0 1 1 PLMN not allowed
0 0 0 0 1 1 0 0 Location Area not allowed
0 0 0 0 1 1 0 1 Roaming not allowed in this
location area
0 0 0 1 0 0 0 0 MSC temporarily not reachable
0 0 0 1 0 1 1 0 Congestion
0 0 1 1 0 0 0 0 }
to } retry upon entry into a new cell
0 0 1 1 1 1 1 1 }
or not implemented
the protocol state
or not implemented
the protocol state
Any other value received by the mobile station
shall be treated as 0110 1111, 'Protocol error,'
unspecified'. Any other value received
by the network shall be treated as 0110 1111,
'Protocol error, unspecified'.
NOTE: The listed reject cause values are defined in
Annex G.
10.5.5.15 Routing area identification
The purpose of the routing area identification information element is to provide an unambiguous identification of
routing areas within the area covered by the GSM system.
The routing area identification is a type 3 information element with 7 octets length.
The routing area identification information element is coded as shown in figure 10.5.130/GSM 04.08 and
table 10.5.148/GSM 04.08.
ETSI
8 7 6 5 4 3 2 1
Routing Area Identification IEI octet 1
MCC digit 2 MCC digit 1 octet 2
MNC digit 3 MCC digit 3 octet 3
MNC digit 2 MNC digit 1 octet 4
LAC octet 5
LAC contd octet 6
RAC octet 7
Figure 10.5.130/GSM 04.08: Routing area identification information element
ETSI
Table 10.5.148/GSM 04.08: Routing area identification information element
MCC, Mobile country code (octet 2 and 3)
The MCC field is coded as in CCITT Rec. E212, Annex A.
If the RAI is deleted, the MCC and MNC shall take the value from the
deleted RAI.
In abnormal cases, the MCC stored in the mobile station can contain
elements not in the set {0, 1 ... 9}. In such cases the mobile station
should transmit the stored values using full hexadecimal encoding. When
receiving such an MCC, the network shall treat the RAI as deleted.
MNC, Mobile network code (octet 3 bits 5 to 8, octet 4)
The coding of this field is the responsibility of each
administration but BCD coding shall be used. The MNC shall consist of 2 or
3 digits. For PCS 1900 for NA, Federal regulation mandates that a 3-digit
MNC shall be used. However a network operator may decide to use only two
digits in the MNC in the RAI over the radio interface. In this case, bits 5
to 8 of octet 3 shall be coded as "1111". Mobile equipment shall accept RAI
coded in such a way.
Note 1: In earlier versions of this protocol, the possibility to use a one
digit MNC in RAI was provided on the radio interface. However as this was
not used this possibility has been deleted.
Note 2: In earlier versions of this protocol, bits 5 to 8 of octet 3 were
coded as "1111". Mobile equipment compliant with these earlier versions of
the protocol may be unable to understand the 3-digit MNC format of the
RAI, and therefore unable to attach to a network broadcasting the RAI in
this format.
In abnormal cases, the MNC stored in the mobile station can have
- digit 1 or 2 not in the set {0, 1 ... 9} or
- digit 3 not in the set {0, 1 ...9, F} hex.
In such cases the mobile station shall transmit the stored values using
full hexadecimal encoding. When receiving such an MNC, the network shall
treat the RAI as deleted.
The same handling shall apply for the network, if a 3-digit MNC is sent by
the mobile station to a network using only a 2-digit MNC.
LAC, Location area code (octet 5 and 6)
In the LAC field bit 8 of octet 5 is the most significant bit and bit 1 of
octet 6 the least significant bit.
The coding of the location area code is the responsibility of each
administration except that two values are used to mark the LAC, and hence
the RAI, as deleted. Coding using full hexadecimal representation may be
used. The location area code consists of 2 octets.
If a RAI has to be deleted then all bits of the location area code shall
be set to one with the exception of the least significant bit which shall
be set to zero. If a SIM is inserted in a Mobile Equipment with the
location area code containing all zeros, then the Mobile Equipment shall
recognise this LAC as part of a deleted RAI.
RAC, Routing area code (octet 7)
In the RAC field bit 8 of octet 7 is the most significant. The coding of
the routing area code is the responsibility of each administration. Coding
using full hexadecimal representation may be used. The routing area code
consists of 1 octet.
10.5.5.16 Spare
10.5.5.17 Update result
The purpose of the update result information element is to specify the result of the associated updating procedure.
ETSI
The update result is a type 1 information element.
The update result information element is coded as shown in figure 10.5.131/GSM 04.08 and table 10.5.149/GSM 04.08.
8 7 6 5 4 3 2 1
Update result
IEI
0
spare
Update result
value
octet 1
Figure 10.5.131/GSM 04.08: Update result information element
Table 10.5.149/GSM 04.08: Update result information element
Update result value (octet 1)
Bits
3 2 1
0 0 0 RA updated
0 0 1 combined RA/LA updated
10.5.5.18 Update type
The purpose of the update type information element is to specify the area the updating procedure is associated with.
The update type is a type 1 information element.
The update type information element is coded as shown in figure 10.5.132/GSM 04.08 and table 10.5.150/GSM 04.08.
8 7 6 5 4 3 2 1
Update type
IEI
0
spare
Update type
value
octet 1
Figure 10.5.132/GSM 04.08: Update type information element
Table 10.5.150/GSM 04.08: Update type information element
Update type value (octet 1)
Bits
3 2 1
0 0 0 RA updating
0 0 1 combined RA/LA updating
0 1 0 combined RA/LA updating with
IMSI attach
0 1 1 Periodic updating
10.5.5.19 A&C reference number
The purpose of the A&C reference number information element is to indicate to the network in the
AUTHENTICATION AND CIPHERING RESPONSE message which AUTHENTICATION AND CIPHERING
REQUEST message the MS is replying to.
The A&C reference number is a type 1 information element.
The A&C reference number information element is coded as shown in figure 10.5.123/GSM 04.08 and
table 10.5.140/GSM 04.08.
ETSI
8 7 6 5 4 3 2 1
A&C reference number
IEI
A&C reference number
value
octet 1
Figure 10.5.134/GSM 04.08: A&C reference number information element
Table 10.5.152/GSM 04.08: A&C reference number information element
A&C reference number value (octet 1)
Unformatted 4 bit field
10.5.6 Session management information elements
10.5.6.1 Access Point Name
The purpose of the access point name information element is to identify the packet data network to which the GPRS
user wishes to connect and to notify the access point of the packet data network that wishes to connect to the MS.
The Access Point Name is a label or a full qualified domain name according to DNS naming conventions (see GSM
03.03 [10]).
The access point name is a type 4 information element with a minimum length of 3 octets and a maximum length of 102
octets.
The access point name information element is coded as shown in figure 10.5.134/GSM 04.08 and
table 10.5.152/GSM 04.08.
8 7 6 5 4 3 2 1
Access point name IEI octet 1
Length of access point name contents octet 2
Access point name value octet 3
octet n*
Figure 10.5.134/GSM 04.08: Access point name information element
The value part is defined in 03.03 [10].
10.5.6.2 Network service access point identifier
The purpose of the network service access point identifier information element is to identify the service access point that
is used for the GPRS data transfer at layer 3.
The network service access point identifier is a type 3 information element with a length of 2 octets.
The value part of a network service access point identifier information element is coded as shown in
8 7 6 5 4 3 2 1
NSAPI IEI octet 1
0 0 0 0
Spare
NSAPI
value
octet 2
Figure 10.5.135/GSM 04.08: Network service access point identifier information element
ETSI
Table 10.5.153/GSM 04.08: Network service access point identifier information element
NSAPI value (octet 2)
Bit
4 3 2 1
0 0 0 0 reserved
0 0 0 1 reserved
0 0 1 0 reserved
0 0 1 1 reserved
0 1 0 0 reserved
0 1 0 1 NSAPI 5
0 1 1 0 NSAPI 6
0 1 1 1 NSAPI 7
1 0 0 0 NSAPI 8
1 0 0 1 NSAPI 9
1 0 1 0 NSAPI 10
1 0 1 1 NSAPI 11
1 1 0 0 NSAPI 12
1 1 0 1 NSAPI 13
1 1 1 0 NSAPI 14
1 1 1 1 NSAPI 15
The purpose of the protocol configuration options information element is to transfer external network protocol options
associated with a PDP context activation.
The protocol configuration options is a type 4 information element with a minimum length of 2 octets and a maximum
The protocol configuration options information element is coded as shown in figure 10.5.136/GSM 04.08 and
table 10.5.154/GSM 04.08.
ETSI
8 7 6 5 4 3 2 1
Protocol configuration options IEI octet 1
Length of protocol config. options contents octet 2
1
ext
0 0 0 0
Spare
Configuration
protocol
octet 3
Protocol ID 1 octet 4
octet 5
Length of protocol ID 1 contents octet 6
Protocol ID 1 contents
octet 7
octet m
Protocol ID 2 octet m+1
octet m+2
Protocol ID 2 contents
octet m+4
octet n
. . .
octet n+1
octet x
Protocol ID n-1 octet x+1
octet x+2
Length of protocol ID n-1 contents octet x+3
Protocol ID n-1 contents
octet x+4
octet y
Protocol ID n octet y+1
octet y+2
Length of protocol ID n contents octet y+3
Protocol ID n contents
octet y+4
octet z
Figure 10.5.136/GSM 04.08: Protocol configuration options information element
ETSI
Table 10.5.154/GSM 04.08: Protocol configuration options information element
ETSI
Configuration protocol (octet 3)
Bits
3 2 1
0 0 0 PPP for use with IP PDP type
0 0 1 for use with OSP:IHOSS PDP type
NOTE. The OSP:IHOSS PDP type does not have a separately named configuration
protocol analogous to PPP.
All other values are interpreted as PPP in this version of the protocol.
Configuration protocol options list (octets 4 to z)
The configuration protocol options list contains a variable number of logical units,
the may occur in an arbitrary order within the configuration protocol options list.
Each unit is of variable length and consists of a
- protocol identifier (2 octets);
- the length of the protocol identifier contents of the unit (1 octet); and
- the protocol identifier contents itself ( n octets).
The protocol identifier field contains the hexadecimal coding of the configuration
protocol identifier. Bit 8 of the first octet of the protocol identifier field contains
the most significant bit and bit 1 of the second octet of the protocol identifier field
contains the least significant bit.
If the configuration protocol options list contains a protocol identifier that is not
supported by the receiving entity the corresponding unit shall be discarded.
The length of the protocol identifier contents field contains the binary coded
representation of the length of the protocol identifier contents field of a unit. The
first bit in transmission order is the most significant bit.
The protocol identifier contents field of each unit contains information specific to
the configuration protocol specified by the protocol identifier.
PPP
At least the following protocol identifiers (as defined in RFC 1700) shall be
supported in this version of the protocol:
- C021H (LCP;
- C023H (PAP);
- C223H (CHAP);and
- 8021H (IPCP).
The support of other protocol identifiers is implementation dependent and outside
the scope of this specification.
The protocol identifier contents field of each unit corresponds to a Packet as
defined in RFC 1661 that is stripped off the Protocol and the Padding octets.
The detailed coding of the protocol identifier contents field is specified in the RFC
that is associated with the protocol identifier of that unit.
OSP:IHOSS (Octet Stream Protocol for Internet-Hosted Octet Stream Service)
In the logical units described above, OSP:IHOSS uses the term option identifier
rather than protocol identifier.
The currently defined option identifiers, their lengths, and the coding of the option
identifier contents fields are specified in GSM 07.60.
ETSI
10.5.6.4 Packet data protocol address
The purpose of the packet data protocol address information element is to identify an address associated with a PDP.
The packet data protocol address is a type 4 information element with minimum length of 4 octets and a maximum
The packet data protocol address information element is coded as shown in figure 10.5.137/GSM 04.08 and
table 10.5.155/GSM 04.08.
8 7 6 5 4 3 2 1
Packet data protocol address IEI octet 1
Length of PDP address contents octet 2
0 0 0 0
spare
PDP type organisation octet 3
PDP type number octet 4
Address information
octet 5
octet n
Figure 10.5.137/GSM 04.08: Packet data protocol address information element
ETSI
Table 10.5.155/GSM 04.08: Packet data protocol address information element
Length of PDP address contents (octet 2)
If the value of octet 2 equals 0000 0010, then :
- No PDP address is included in this information
element; and
- If the PDP type is IP, dynamic addressing is
applicable.
NOTE : For PPP and OSP:IHOSS, no address is required in this
PDP type organisation (octet 3)
Bits
4 3 2 1
In MS to network direction :
0 0 0 0 ETSI allocated address (e.g. X.121)
0 0 0 1 IETF allocated address
1 1 1 1 Empty PDP type
In network to MS direction :
0 0 0 0 ETSI allocated address (e.g. X.121)
0 0 0 1 IETF allocated address
If bits 4,3,2,1 of octet 3 are coded 0 0 0 0
PDP type number value (octet 4)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 X.121 address
0 0 0 0 0 0 0 1 PDP-type PPP
0 0 0 0 0 0 1 0 PDP-type OSP:IHOSS
All other values shall be interpreted as X.121 address
in this version of the protocol.
Bits
8 7 6 5 4 3 2 1
0 0 1 0 0 0 0 1 IPv4 address
0 1 0 1 0 1 1 1 IPv6 address
All other values shall be interpreted as IPv4 address
in this version of the protocol.
In MS to network direction:
bits 8 to 1 are spare and shall be coded all 0.
Octet 3, bits 7, 6, and 5 are spare and shall be coded
all 0.
If PDP type number indicates X.121, the Address information is coded as follows:
ETSI
8 7 6 5 4 3 2 1
digit 2 digit 1 octet 5
digit 4 digit 3 octet 6
digit m+1 digit m octet n*
Digit 1 contains the first BCD coded digit of the X.121 address. If the X.121 address has an odd number of digits, digit
m+1 shall be padded with HEX(F).
If PDP type number indicates IPv4, the Address information in octet 5 to octet 8 contains the IPv4 address. Bit 8 of
octet 5 represents the most significant bit of the IP address and bit 1 of octet 8 the least significant bit .
If PDP type number indicates IPv6, the Address information in octet 5 to octet 20 contains the IPv6 address. Bit 8 of
octet 5 represents the most significant bit of the IP address and bit 1 of octet 20 the least significant bit.
10.5.6.5 Quality of service
The purpose of the quality of service information element is to specify the QoS parameters for a PDP context.
The quality of service is a type 4 information element with a length of 5 octets.
The quality of service information element is coded as shown in figure 10.5.138/GSM 04.08 and
table 10.5.156/GSM 04.08.
8 7 6 5 4 3 2 1
Quality of service IEI octet 1
Length of quality of service IE Octet 2
0 0
spare
Delay
class
Reliability
class
octet 3
Peak
throughput
0
spare
Precedence
class
octet 4
0 0 0
spare
Mean
throughput
octet 5
Figure 10.5.138/GSM 04.08: Quality of service information element
ETSI
Table 10.5.156/GSM 04.08: Quality of service information element
Reliability class, octet 3 (see GSM 03.60)
Bits
3 2 1
0 0 0 Subscribed reliability class
In network to MS direction:
0 0 0 Reserved
In MS to network direction and in network to MS direction :
0 0 1 Acknowledged GTP, LLC, and RLC; Protected data
0 1 0 Unacknowledged GTP; Acknowledged LLC and RLC, Protected data
0 1 1 Unacknowledged GTP and LLC; Acknowledged RLC, Protected data
1 0 0 Unacknowledged GTP, LLC, and RLC, Protected data
1 0 1 Unacknowledged GTP, LLC, and RLC, Unprotected data
1 1 1 Reserved
All other values are interpreted as Unacknowledged GTP and LLC; Acknowledged RLC, Protected data in this version
of the protocol.
Delay class, octet 3 (see GSM 02.60 and GSM 03.60)
Bits
6 5 4
0 0 0 Subscribed delay class
0 0 0 Reserved
0 0 1 Delay class 1
0 1 0 Delay class 2
0 1 1 Delay class 3
1 0 0 Delay class 4 (best effort)
1 1 1 Reserved
All other values are interpreted as Delay class 4 (best effort) in this version
of the protocol.
Bit 7 and 8 of octet 3 are spare and shall be coded all 0.
Precedence class, octet 4 (see GSM 03.60)
Bits
3 2 1
0 0 0 Subscribed precedence
0 0 0 Reserved
0 0 1 High priority
0 1 0 Normal priority
0 1 1 Low priority
1 1 1 Reserved
ETSI
All other values are interpreted as Normal priority in this version of the protocol.
Bit 4 of octet 4 is spare and shall be coded as 0.
Peak throughput, octet 4
Bits
8 7 6 5
0 0 0 0Subscribed peak throughput
0 0 0 0Reserved
0 0 0 1 Up to 1 000 octet/s
0 0 1 0 Up to 2 000 octet/s
0 0 1 1 Up to 4 000 octet/s
0 1 0 0 Up to 8 000 octet/s
0 1 0 1 Up to 16 000 octet/s
0 1 1 0 Up to 32 000 octet/s
0 1 1 1 Up to 64 000 octet/s
1 0 0 0 Up to 128 000 octet/s
1 0 0 1 Up to 256 000 octet/s
1 1 1 1 Reserved
All other values are interpreted as Up to 1 000 octet/s in this
Mean throughput, octet 5
Bits
5 4 3 2 1
0 0 0 0 0 Subscribed mean throughput
0 0 0 0 0 Reserved
0 0 0 0 1 100 octet/h
0 0 0 1 0 200 octet/h
0 0 0 1 1 500 octet/h
0 0 1 0 0 1 000 octet/h
0 0 1 0 1 2 000 octet/h
0 0 1 1 0 5 000 octet/h
0 0 1 1 1 10 000 octet/h
0 1 0 0 0 20 000 octet/h
0 1 0 0 1 50 000 octet/h
0 1 0 1 0 100 000 octet/h
0 1 0 1 1 200 000 octet/h
0 1 1 0 0 500 000 octet/h
0 1 1 0 1 1 000 000 octet/h
0 1 1 1 0 2 000 000 octet/h
0 1 1 1 1 5 000 000 octet/h
1 0 0 0 0 10 000 000 octet/h
1 0 0 0 1 20 000 000 octet/h
1 0 0 1 0 50 000 000 octet/h
1 1 1 1 0 Reserved
1 1 1 1 1 Best effort
The value Best effort indicates that throughput shall be made available to the MS on a per need and availability basis.
All other values are interpreted as Best effort in this
Bits 8 to 6 of octet 5 are spare and shall be coded all 0.
ETSI
10.5.6.6 SM cause
The purpose of the SM cause information element is to indicate the reason why a session management request is
rejected.
The SM cause is a type 3 information element with 2 octets length.
The SM cause information element is coded as shown in figure 10.5.139/GSM 04.08 and table 10.5.157/GSM 04.08.
8 7 6 5 4 3 2 1
SM cause IEI octet 1
Cause value octet 2
Figure 10.5.139/GSM 04.08: SM cause information element
Table 10.5.157/GSM 04.08: SM cause information element
Bits
8 7 6 5 4 3 2 10 0 0 1 1 0 0 1 LLC or SNDCP failure
0 0 0 1 1 0 1 0 Insufficient resources
0 0 0 1 1 0 1 1 Missing or unknown APN
0 0 0 1 1 1 0 0 Unknown PDP address or PDP type
0 0 0 1 1 1 0 1 User Aauthentication failed
0 0 0 1 1 1 1 0 Activation rejected by GGSN
0 0 0 1 1 1 1 1 Activation rejected, unspecified
0 0 1 0 0 0 0 0 Service option not supported
0 0 1 0 0 0 0 1 Requested service option
not subscribed
0 0 1 0 0 0 1 0 Service option temporarily
out of order
0 0 1 0 0 0 1 1 NSAPI already used
0 0 1 0 0 1 0 0 Regular deactivation
0 0 1 0 0 1 0 1 QoS not accepted
0 0 1 0 0 1 1 1 Reactivation required
0 1 0 1 0 0 0 1 Invalid transaction identifier value
or not implemented
the protocol state
or not implemented
the protocol state
Any other value received by the mobile station shall
be treated as 0010 0010, Service option temporarily
out of order. Any other value received by the network
shall be treated as 0110 1111, Protocol error,
unspecified.
NOTE: The listed cause values are defined in
Annex I
10.5.6.7 Spare
ETSI
10.5.6.8 AA deactivation cause
The purpose of the AA deactivation cause information element is to indicate the reason why a AA PDP context was
deactivated by the network.
The AA deactivation cause information element is coded as shown in figure 10.5.140/GSM 04.08 and
table 10.5.158/GSM 04.08.
The AA deactivation cause is a type 1 information element.
8 7 6 5 4 3 2 1
AA deactivation cause
indicator IEI
0
spare
AA deactivation
cause value
octet 1
Figure 10.5.140/GSM 04.08: AA deactivation cause information element
Table 10.5.158/GSM 04.08: AA deactivation cause information element
AA deactivation cause value (octet 1)
Bits
3 2 1
0 0 0 Normal, unspecified
0 0 1 Server address violation
0 1 0 Network overload
0 1 1 Server not reachable
Normal, unspecified by this version
of the protocol.
10.5.6.9 LLC service access point identifier
The purpose of the LLC service access point identifier information element is to identify the service access point that is
used for the GPRS data transfer at LLC layer.
The LLC service access point identifier is a type 3 information element with a length of 2 octets.
The value part of a LLC service access point identifier information element is coded as shown in
8 7 6 5 4 3 2 1
LLC SAPI IEI octet 1
0 0 0 0
Spare
LLC SAPI
value
octet 2
Figure 10.5.141/GSM 04.08: LLC service access point identifier information element
ETSI
Table 10.5.159/GSM 04.08: LLC service access point identifier information element
LLC SAPI value (octet 2)
Bit
4 3 2 1
0 0 1 1 SAPI 3
0 1 0 1 SAPI 5
1 0 0 1 SAPI 9
1 0 1 1 SAPI 11
10.5.7 GPRS Common information elements
10.5.7.1 [Spare]
10.5.7.2 Radio priority
The purpose of the radio priority information element is to specify the priority level that the MS shall use at the lower
layers for transmission of data related to a PDP context or for mobile originated SMS transmission.
The radio priority information element is coded as shown in figure 10.5.143/GSM 04.08 and
table 10.5.161/GSM 04.08.
The radio priority is a type 1 information element.
8 7 6 5 4 3 2 1
Radio priority IEI 0
spare
Radio priority
level value
octet 1
Figure 10.5.143/GSM 04.08: Radio priority information element
Table 10.5.161/GSM 04.08: Radio priority information element
Radio priority level value (octet 1)
Bits
3 2 1
0 0 1 priority level 1 (highest)
0 1 0 priority level 2
0 1 1 priority level 3
1 0 0 priority level 4 (lowest)
priority level 4 by this version
of the protocol.
10.5.7.3 GPRS Timer
The purpose of the GPRS timer information element is to specify GPRS specific timer values, e.g. for the READY
timer.
The GPRS timer is a type 3 information element with 2 octets length.
The GPRS timer information element is coded as shown in figure 10.5.144/GSM 04.08 and table 10.5.162/GSM 04.08.
8 7 6 5 4 3 2 1
GPRS Timer IEI octet 1
Unit Timer value octet 2
Figure 10.5.144/GSM 04.08: GPRS Timer value information element
ETSI
Table 10.5.162/GSM 04.08: GPRS Timer value information element
Timer value (octet 2)
Bits 5 to 1 represent the binary coded timer
value.
Bits 6 to 8 defines the timer value unit
for the GPRS timer as follows:
Bits
8 7 6
0 0 0 value is incremented in multiples of 2
seconds
0 0 1 value is incremented in multiples of 1
minute
0 1 0 value is incremented in multiples of
decihours
1 1 1 value indicates that the timer is
deactivated.
Other values shall be interpreted as multiples
of 1 minute in this version of the protocol.
ETSI
11 List of system parameters
The description of timers in the following table should be considered a brief summary. The precise details are found in
sections 3 to 6, which should be considered the definitive descriptions.
11.1 Timers and counters for radio resource management
11.1.1 Timers on the mobile station side
T3122: This timer is used during random access, after the receipt of an IMMEDIATE ASSIGN REJECT
message.
Its value is given by the network in the IMMEDIATE ASSIGN REJECT message.
T3124: This timer is used in the seizure procedure during a hand-over, when the two cells are not
synchronized.
Its purpose is to detect the lack of answer from the network to the special signal.
Its value is set to 675 ms if the channel type of the channel allocated in the HANDOVER
COMMAND is an SDCCH (+ SACCH); otherwise its value is set to 320 ms.
T3126: This timer is started either
after sending the maximum allowed number of CHANNEL REQUEST messages during an
immediate assignment procedure.
or
on receipt of an IMMEDIATE ASSIGNMENT REJECT message,
whichever occurs first.
It is stopped at receipt of an IMMEDIATE ASSIGNMENT message, or an IMMEDIATE
ASSIGNMENT EXTENDED message.
At its expiry, the immediate assignment procedure is aborted.
The minimum value of this timer is equal to the time taken by T+2S slots of the mobile stations
RACH. S and T are defined in section 3.3.1.2. The maximum value of this timer is 5 seconds.
T3128: This timer is started when the mobile station starts the uplink investigation procedure and the
uplink is busy.
It is stopped at receipt of the first UPLINK FREE message.
At its expiry, the uplink investigation procedure is aborted.
The value of this timer is set to 1 second.
T3130: This timer is started after sending the first UPLINK ACCESS message during a VGCS uplink
access procedure.
It is stopped at receipt of a VGCS ACCESS GRANT message.
At its expiry, the uplink access procedure is aborted.
The value of this timer is set to 5 seconds.
ETSI
T3110: This timer is used to delay the channel deactivation after the receipt of a (full) CHANNEL
RELEASE. Its purpose is to let some time for disconnection of the main signalling link.
Its value is set to such that the DISC frame is sent twice in case of no answer from the network. (It
should be chosen to obtain a good probability of normal termination (i.e. no time out of T3109) of
the channel release procedure.)
T3134 This timer is used in the seizure procedure during an RR network commanded cell change order
procedure. Its purpose is to detect the lack of answer from the network or the lack of availability of
the target cell.
Its value is set to 5 seconds.
T3142: The timer is used during packet access on CCCH, after the receipt of an IMMEDIATE
ASSIGNMENT REJECT message.
Its value is given by the network in the IMMEDIATE ASSIGNMENT REJECT message.
T3146: This timer is started either
after sending the maximum allowed number of CHANNEL REQUEST messages during a packet
access procedure.
or
on receipt of an IMMEDIATE ASSIGNMENT REJECT message during a packet access
procedure,
whichever occurs first.
It is stopped at receipt of an IMMEDIATE ASSIGNMENT message, or an IMMEDIATE
ASSIGNMENT EXTENDED message.
At its expiry, the packet access procedure is aborted.
The minimum value of this timer is equal to the time taken by T+2S slots of the mobile stations
RACH. S and T are defined in section 3.3.1.2. The maximum value of this timer is 5 seconds.
T3164: This timer is used during packet access using CCCH. It is started at the receipt of an IMMEDIATE
ASSIGNMENT message.
It is stopped at the transmission of a RLC/MAC block on the assigned temporary block flow, see
GSM 04.60.
At expire, the mobile station returns to the packet idle mode.
The value of the timer is 5 seconds.
T3190: The timer is used during packet downlink assignment on CCCH. It is started at the receipt of an
IMMEDIATE ASSIGNMENT message or of an PDCH ASSIGNMENT COMMAND message
when in dedicated mode.
It is stopped at the receipt of a RLC/MAC block on the assigned temporary block flow, see
GSM 04.60.
At expiry, the mobile station returns to the packet idle mode.
The value of the timer is 5 seconds.
11.1.2 Timers on the network side
T3101: This timer is started when a channel is allocated with an IMMEDIATE ASSIGNMENT message. It
is stopped when the MS has correctly seized the channels.
ETSI
Its value is network dependent.
NOTE: It could be higher than the maximum time for a L2 establishment attempt.
T3103: This timer is started by the sending of a HANDOVER message and is normally stopped when the
MS has correctly seized the new channel. Its purpose is to keep the old channels sufficiently long
for the MS to be able to return to the old channels, and to release the channels if the MS is lost.
NOTE: It could be higher than the maximum transmission time of the HANDOVER COMMAND, plus the value
of T3124, plus the maximum duration of an attempt to establish a data link in multiframe mode.)
T3105: This timer is used for the repetition of the PHYSICAL INFORMATION message during the hand-
over procedure.
NOTE: This timer may be set to such a low value that the message is in fact continuously transmitted.
T3107: This timer is started by the sending of an ASSIGNMENT COMMAND message and is normally
stopped when the MS has correctly seized the new channels.
Its purpose is to keep the old channel sufficiently long for the MS to be able to return to the old
channels, and to release the channels if the MS is lost.
NOTE: It could be higher than the maximum transmission time of the ASSIGNMENT COMMAND message plus
twice the maximum duration of an attempt to establish a data link multiframe mode.
T3109: This timer is started when a lower layer failure is detected by the network, when it is not engaged
in a RF procedure. It is also used in the channel release procedure.
Its purpose is to release the channels in case of loss of communication.
NOTE: Its value should be large enough to ensure that the MS detects a radio link failure.
T3111: This timer is used to delay the channel deactivation after disconnection of the main signalling link.
Its purpose is to let some time for possible repetition of the disconnection.
Its value is equal to the value of T3110.
T3113: This timer is started when the network has sent a PAGING REQUEST message and is stopped
when the network has received the PAGING RESPONSE message.
NOTE: The value could allow for repetitions of the Channel Request message and the requirements associated
with T3101.
T3115: This timer is used for the repetition of the VGCS UPLINK GRANT message during the uplink
access procedure.
NOTE: This timer may be set to such a low value that the message is in fact continuously transmitted.
T3117: This timer is started by the sending of a PDCH ASSIGNMENT COMMAND message and is
normally stopped when the MS has correctly accessed the target TBF.
Its purpose is to keep the old channel sufficiently long for the MS to be able to return to the old
channels, and to release the channels if the MS is lost.
ETSI
NOTE: It could be higher than the maximum transmission time of the PDCH ASSIGNMENT COMMAND
message plus T3132 plus the maximum duration of an attempt to establish a data link in multiframe mode.
T3119: This timer is started by the sending of a RR-CELL CHANGE ORDER message and is normally
stopped when the MS has correctly accessed the new cell. Its purpose is to keep the old channels
sufficiently long for the MS to be able to return to the old channels, and to release the channels if
the MS is lost.
NOTE: It could be higher than the maximum transmission time of the RR_CELL CHANGE ORDER, plus T3134,
plus the maximum duration of an attempt to establish a data link in multiframe mode.
T3141: This timer is started when a temporary block flow is allocated with an IMMEDIATE
ASSIGNMENT message during a packet access procedure. It is stopped when the mobile station
has correctly seized the temporary block flow.
11.1.3 Other parameters
Ny1: The maximum number of repetitions for the PHYSICAL INFORMATION message during a
handover (see section 3.4.4.2.2). The value is network dependent.
Ny2: The maximum number of repetitions for the VGCS UPLINK GRANT message during an uplink
access procedure (see section 3.3.1.2.2). The value is network dependent.
ETSI
11.2 Timers of mobility management
Table 11.1/GSM 04.08: Mobility management timers - MS-side
+-----------------------------------------------------+
TIMER MM TIME CAUSE FOR NORMAL STOP AT THE
NUM. ST OUT START EXPIRY
AT VAL.
+-----+--+----+------------+-------------+------------
T3210 3 20s -LOCUPDREQ - LOCUPDACC
sent - LOCUPDREJ
- AUTHREJ Start T3211
- Lower layer
failure
+-----+--+----+------------+-------------+------------
T3211 1 15s -LOCUPDREJ - Time out Restart the
2 with cause - cell change Location up-
#17 netw. - request for date proc.
failure MM connec-
-lower layer tion
failure or establish-
RR conn. ment
released - change of
after LA
RR conn.
abort
during loc.
updating
+-----+--+----+------------+-------------+------------
T3212 1, Note -termination -initiation initiate
2 1 of MM ser- of MM ser- periodic
vice or MM vice or MM updating
signalling signalling
+-----+--+----+------------+-------------+------------
T3213 1 4s -location up - expiry new random
2 dating fai - change of attempt
11 lure BCCH para-
meter
+-----+--+----+------------+-------------+------------
T3220 7 5s -IMSI DETACH - release enter Null
from RM- or Idle, AT-
sublayer TEMPTING TO
UPDATE
+-----+--+----+------------+-------------+------------
T3230 5 15s -CM SERV REQ - Cipher mode provide
setting release ind.
CM REEST REQ - CM SERV REJ
- CM SERV ACC
+-----+--+----+------------+-------------+------------
T3240 9 10s see section see section abort the
10 11.2.1 11.2.1 RR connec-
tion
+-----------------------------------------------------+
NOTE 1: The timeout value is broadcasted in a SYSTEM INFORMATION message
ETSI
Table 11.2/GSM 04.08: Mobility management timers - network-side
+--------------------------------------------------------------+
TIMER MM TIME CAUSE FOR NORMAL STOP AT THE FIRST AT THE
NUM. ST OUT START EXPIRY SECOND
AT VAL. EXPIRY
+-----+--+----+------------+-------------+------------+--------
T3250 6 12s TMSI-REAL- TMSI-REALL- Optionally
CMD or COM received Release
LOC UPD ACC RR connec-
with new tion
TMSI sent
+-----+--+----+------------+-------------+------------+--------
T3255 Note LOC UPD ACC CM SERVICE Release RR
sent with REQUEST Connection
"Follow on or use for
Proceed" mobile sta-
tion termi-
nating call
+-----+--+----+------------+-------------+------------+--------
T3260 5 12s AUTHENT- AUTHENT- Optionally
REQUEST RESPONSE Release
sent received RR connec-
tion
+-----+--+----+------------+-------------+------------+--------
T3270 4 12s IDENTITY IDENTITY Optionally
REQUEST RESPONSE Release
sent received RR connec-
tion
+--------------------------------------------------------------+
NOTE 2: The value of this timer is not specified by this recommendation.
11.2.1 Timer T3240
Timer T3240 is started in the mobile station when:
- the mobile station receives a LOCATION UPDATING ACCEPT message completing a location updating
procedure in the cases specified in section 4.4.4.6 and 4.4.4.8;
- the mobile station receives a LOCATION UPDATING REJECT message in the cases specified in section
4.4.4.7;
- the mobile station has sent a CM SERVICE ABORT message as specified in section 4.5.1.7;
- the mobile station has released or aborted all MM connections in the cases specified in 4.3.2.5, 4.3.5.2, 4.5.1.1,
and 4.5.3.1.
Timer T3240 is stopped, reset, and started again at receipt of an MM message.
Timer T3240 is stopped and reset (but not started) at receipt of a CM message that initiates establishment of an CM
connection (an appropriate SETUP, REGISTER, or CP-DATA message as defined in GSM 04.08, GSM 04.10 or
GSM 04.11).
ETSI
11.2.2 Timers of GPRS mobility management
Table 11.3/GSM 04.08: GPRS Mobility management timers - MS side
TIMER
NUM.
TIMER
VALUE
STATE CAUSE OF START NORMAL STOP ON THE
1
st
, 2
nd
, 3
rd
, 4
th
EXPIRY Note 3
T3310 15s GMM-
REG-INIT
ATTACH REQ sent ATTACH ACCEPT
received
ATTACH REJECT
received
Retransmission of
ATTACH REQ
T3311 15s GMM-DEREG
ATTEMPTING
TO ATTACH or
GMM-REG
ATTEMPTING
TO UPDATE
ATTACH REJ with other cause
values as described in chapter
GPRS Attach
ROUTING AREA UPDATE REJ
with other cause values as
described in chapter Routing
Area Update
Low layer failure
Change of the
routing area
Restart of the
Attach or the RAU
procedure with
updating of the
relevant attempt
counter
T3321 15s GMM-
DEREG-INIT
DETACH REQ sent DETACH ACCEPT
received
Retransmission of
the DETACH REQ
T3330 15s GMM-
ROUTING-
UPDATING-
INITIATED
ROUTING AREA UPDATE
REQUEST sent
ROUTING AREA
UPDATE ACC
received
ROUTING AREA
UPDATE REJ
received
Retransmission of
the ROUTING
AREA UPDATE
REQUEST
message
Table 11.3a/GSM 04.08: GPRS Mobility management timers MS side
TIMER
NUM.
TIMER
VALUE
STATE CAUSE OF START NORMAL STOP ON
EXPIRY
T3302
T3212
Note 4
GMM-DEREG
or
GMM-REG
At attach failure and the attempt
counter is greater than or equal
to 5.
At routing area updating failure
and the attempt counter is greater
than or equal to 5.
At successful attach
At successful
routing area
updating
On every expiry,
initiation of the
GPRS attach
procedure
or
RAU procedure
T3312 Default
54 min
Note1
GMM-REG When READY state is left. When entering state
GMM-DEREG
Initiation of the
Periodic RAU
procedure
T3314
READY
Default
44 sec
Note 2
All except GMM-
DEREG
Transmission of a PTP PDU Forced to Standby No cell-updates are
performed
T3316
AA-
READY
Default
44 sec
Note 2
- Transmission of a PTP PDU - -
NOTE 1: The value of this timer is used if the network does not indicate another value in a GMM signalling
procedure.
NOTE 2: The default value of this timer is used if neither the MS nor the Network send another value, or if the
Network sends this value, in a signalling procedure.
NOTE 3: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in
the corresponding procedure description.
ETSI
NOTE 4: T3302 is loaded with the same value which is used to load T3212.
Table 11.4/GSM 04.08: GPRS Mobility management timers - network side
TIMER
NUM.
TIMER
VALUE
1
st
, 2
nd
, 3
rd
, 4
th
EXPIRY Note 3
T3322 6s GMM-
DEREG-INIT
DETACH REQ sent DETACH ACCEPT
received
Retransmission of
DETACH
REQUEST
T3350 6s GMM-
COMMON-
PROC-INIT
ATTACH ACCEPT
sent with P-TMSI and/or TMSI
RAU ACCEPT sent with P-TMSI
and/or TMSI
P-TMSI REALLOC COMMAND
sent
ATTACH
COMPLETE
received
RAU COMPLETE
received
P-TMSI REALLOC
COMPLETE
received
Retransmission of
the same message
type, i.e. ATTACH
ACCEPT, RAU
ACCEPT or
REALLOC
COMMAND
T3360 6s GMM-
COMMON-
PROC-INIT
AUTH AND CIPH REQUEST
sent
AUTH AND CIPH
RESPONSE
received
Retransmission of
AUTH AND CIPH
REQUEST
T3370 6s GMM-
COMMON-
PROC-INIT
IDENTITY REQUEST sent IDENTITY
RESPONSE
received
Retransmission of
IDENTITY
REQUEST
Table 11.4a/GSM 04.08: GPRS Mobility management timers - network side
TIMER
NUM.
TIMER
VALUE
STATE CAUSE OF START NORMAL STOP ON
EXPIRY
T3313 Note1 GMM_REG Paging procedure initiated Paging procedure
completed
Network dependent
T3314
READY
Default
44 sec
Note 2
All except GMM-
DEREG
Receipt of a PTP PDU Forced to Standby The network shall
page the MS if a
PTP PDU has to be
sent to the MS
T3316 AA-
READY
Default
44 sec
Note 2
- Receipt of a PTP PDU - -
Mobile
Reachable
Default 4
min greater
than T3312
All except GMM-
DEREG
Change from READY to
STANDBY state
PTP PDU received Network dependent
but typically paging
is halted on 1st
expiry
NOTE 1: The value of this timer is network dependent.
NOTE 2: The default value of this timer is used if neither the MS nor the Network send another value, or if the
Network sends this value, in a signalling procedure. The value of this timer should be slightly shorter in
the network than in the MS, this is a network implementation issue.
NOTE 3: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in
the corresponding procedure description.
ETSI
11.2.3 Timers of session management
Table 11.2c/GSM 04.08: Session management timers - MS side
TIMER
NUM.
TIMER
VALUE
1
st
, 2
nd
, 3
rd
, 4
th
EXPIRY
T3380 30s PDP-
ACTIVE-PEND
ACTIVATE PDP CONTEXT
REQUEST sent
ACTIVATE
PDP CONTEXT
ACCEPT received
ACTIVATE
PDP CONTEXT
REJECT received
Retransmission of
ACTIVATE PDP
CONTEXT REQ
T3390 8s PDP-
INACT-PEND
DEACTIVATE PDP CONTEXT
REQUEST sent
DEACTIVATE PDP
CONTEXT ACC
received
Retransmission of
DEACTIVATE
PDP CONTEXT
REQUEST
NOTE: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions
are described in the corresponding procedure description.
Table 11.2d/GSM 04.08: Session management timers - network side
TIMER
NUM.
TIMER
VALUE
1
st
, 2
nd
, 3
rd
, 4
th
EXPIRY
T3385 8s PDP-
ACT-PEND
REQUEST PDP CONTEXT
ACTIVATION sent
ACTIVATE PDP
CONTEXT REQ
received
Retransmission of
REQUEST PDP
CONTEXT
ACTIVATION
T3386 8s PDP-
MOD-PEND
MODIFY PDP CONTEXT
REQUEST sent
MODIFY PDP
CONTEXT ACC
received
Retransmission of
MODIFY PDP
CONTEXT REQ
T3395 8s PDP-
INACT-PEND
DEACTIVATE PDP CONTEXT
REQUEST sent
DEACTIVATE PDP
CONTEXT ACC
received
Retransmission of
DEACTIVATE PDP
CONTEXT REQ
T3397 8s PDP-
INACT-PEND
DEACTIVATE AA PDP
CONTEXT REQUEST sent
DEACTIVATE AA
PDP CONTEXT
ACCEPT received
Retransmission of
DEACTIVATE AA
PDP CONTEXT
REQUEST
NOTE: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions
are described in the corresponding procedure description.
ETSI
11.3 Timers of circuit-switched call control
Table 11.3/GSM 04.08: Call control timers - MS side
+-------------------------------------------------------------+
TIM. TIM STATE OF CAUSE OF NORMAL AT FIRST AT SECOND
NUM. VAL CALL START STOP EXPIRY EXPIRY
+----+---+----------+---------+-----------+---------+---------
T303 30s Call CM SER RQ CALL PROC, Clear the Timer is
initiated sent or REL COMP call not
received restarted

T305 30s Disconnect DISC REL or DISC REL sent. Timer is
Request sent received not
restarted

T308 30s Release REL REL COMP Retrans. Call ref.
request sent or REL RELEASE release
received restart
T308

T310 30s Outgoing CALL ALERT,CONN, Send DISC Timer is
Note call PROC DISC or not
1 Proceeding received PROG rec. restarted

T313 30s Connect CONN CONNect Send DISC Timer is
Request sent ACKnowledge not
received restarted

T323 30s Modify MOD MOD COMP Clear Timer is
Request sent or MOD REJ the call not
received restarted

T332 30s Wait for STARTCC CC-EST. Clear Timer is
network sent received the call not
info. restarted

T335 30s CC-Est. CC-EST RECALL Clear Timer is
Confirmed CONF.sent received the call not
restarted

+-------------------------------------------------------------+
NOTE 1: T310 is not started if progress indicator #1, #2, or #64 has been delivered in the CALL PROCEEDING
message or in a previous PROGRESS message.
ETSI
Table 11.4/GSM 04.08: Call control timers - network side
+------------------------------------------------------------+
TIM. DFT STATE OF CAUSE NORMAL STOP AT FIRST AT SECON
NUM. TIM CALL FOR EXPIRY EXPIRY
VAL START
+----+----+----------+--------+-----------+--------+---------
T301 Min Call ALERT CONN Clear Timer
Note 180s received received received the call is not
1 restarted

T303 Note Call SETUP CALL CONF Clear Timer
2 present sent or REL COMP the call is not
received restarted

T305 30s Disconnect DISC REL or DISC Network Timer
Indication without received sends is not
progress RELEASE restarted
indic.
#8 sent
or CCBS
Possible

T306 30s Disconnect DISC REL or DISC Stop the Timer
Indication with received tone/ is not
progress announc. restarted
indic. Send REL
#8 sent
but no
CCBS
possible

T308 Note Release REL sent REL COMP Retrans. Release
2 request or REL RELEASE call
received restart reference
T308

T310 Note Incoming CALL ALERT, CONN Clear Timer
2 call pro- CONF or DISC the call is not
ceeding received received restarted

T313 Note Connect CON sent CON ACK Clear Timer
2 Indication received the call is not
restarted

T323 30s Modify MOD sent MOD COMP Clear Timer
request or MOD REJ the call is not
received restarted

T331 Note CC CM-SERV START CC Clear Timer
2 Connec. PROMPT received the call is not
Pending sent restarted

T333 Note CC-Est. START CC CC-EST.CONF Clear Timer
2 Present received or REL COMP the call is not
received restarted

T334 Min CC-Est. RECALL SETUP Clear Timer
Note 15s Confirmed sent received the call is not
3 restarted

T338 Note Disconnect DISC REL or DISC stop any Timer
2 indication with received tone/ is not
CCBS announc. restarted
possible Send REL

+------------------------------------------------------------+
NOTE 1: The network may already have applied an internal alerting supervision function; e.g. incorporated within
call control. If such a function is known to be operating on the call, then timer T301 is not used.
NOTE 2: These time values are set by the network operator.
NOTE 3: When applied to the supplementary service CCBS, the timer T334 can either represent the recall timer T4
or the notification timer T10 (see GSM 03.93). Thus the timer T334 can take two different values. GSM
03.93 defines the range of these values.
ETSI
Annex A (informative):
Example of subaddress information element coding
This annex is informative.
This annex gives an example of how the Called Party Subaddress IE is encoded to carry subaddress digits that use IA5
characters. This example is also applicable to the Calling Party Subaddress IE.
8 7 6 5 4 3 2 1 octet
+-----------------------------------------------------+
0 1 1 0 1 1 0 1 1
called party subaddress IEI
+-----------------------------------------------------
0 0 0 0 0 1 1 1 2
Length
+-----------------------------------------------------
1 0 0 0 X 0 0 0 3
not NSAP odd/ev
ext (X.213/ISO 8348 AD2) note 1 note 2
+--------------------------+--------------------------
0 1 0 1 0 0 0 0 4
AFI (note 3)
+--------------------------+--------------------------
IA5 Character (note 4) 5
+--------------------------+--------------------------
IA5 Character (note 4) 6
+--------------------------+--------------------------
. .
. .
+--------------------------+--------------------------
IA5 Character (note 4) 9,
+-----------------------------------------------------+ note 5
NOTE 1: The value of this bit has no significance when the type of subaddress is "NSAP".
NOTE 2: These bits are spare.
NOTE 3: The Authority and Format Identifier code 50 (in BCD) indicates that the subaddress consists of IA5
characters (see ISO standard 8348 AD2).
NOTE 4: IA5 character as defined in CCITT Recommendation T.50/ISO 646 and then encoded into two semi-octets
according to the "preferred binary encoding" defined in X.213/ISO 8348 AD2. (Each character is
converted into a number in the range 32 to 127 using the ISO 646 encoding with zero parity and the parity
bit in the most significant position. This number is then reduced by 32 to give a new number in the range 0
to 95. The new number is then treated as a pair of decimal digits with the value of each digit being
encoded in a semi-octet.)
NOTE 5: the number of IA5 characters in the subaddress may vary, subject to an upper limit of 19 IA5 characters.
ETSI
Annex B (normative):
Compatibility checking
This annex is normative.
B.1 Introduction
This annex describes the various compatibility checks which shall be carried out to ensure that the best matched MS and
network capabilities are achieved on a call between a PLMN and the ISDN.
Three different processes of compatibility checking shall be performed:
i) at the user-to-network interface on the calling side (see B.2);
ii) at the network-user interface on the called side (see B.3.2);
iii) user-to-user (see B 3.3).
NOTE: In this context and throughout this annex the term "called user" is the end point entity which is explicitly
addressed.
For details on the coding of the information required for compatibility checking, see annex C.
B.2 Calling side compatibility checking
B.2.1 Compatibility checking of the CM SERVICE REQUEST
message
The network shall check if the service requested in the CM SERVICE REQUEST message is permitted for that
subscriber.
B.2.2 Compatibility/Subscription checking of the SETUP message
At the calling side the network shall check that the basic service(s) requested by the calling MS in the Bearer Capability
information element(s) match(es) with the basic services provided to that subscriber by the PLMN. If for at least one
bearer capability information element contained in the SETUP message a mismatch is detected, then the network shall
proceed as follows:
- if the SETUP message contained two bearer capability information elements for only one of which a mismatch is
detected, the network shall either:
- under the conditions specified in GSM 07.01 (e.g. TS 61 and TS 62), accept the SETUP message with a
CALL PROCEEDING message containing the, possibly negotiated, bearer capability information element for
which no mismatch is detected, or
- reject the call using one of the causes listed in annex H.
- otherwise the network shall reject the call using one of the causes listed in annex H.
Network services are described in GSM 02.02 and GSM 02.03 as bearer services and teleservices, respectively.
B.3 Called side compatibility checking
In this section, the word "check" means that the MS examines the contents of the specified information element.
ETSI
B.3.1 Compatibility checking with addressing information
If an incoming SETUP message is offered to the MS with addressing information (i.e. sub-address or called party
number) the following shall occur:
a) if the MS has a DDI number or a sub-address, then the information in any Called Party BCD Number or any
Called Party subaddress information elements of the incoming SETUP message shall be checked by the MS
against the corresponding part of the number assigned to the user (e.g. for DDI) or the users own sub-address.
In the cases of a mismatch, the MS shall release the call. In the case of a match, the compatibility checking
described in B.3.2 and B.3.3 shall be performed.
b) if the MS has no DDI number and no sub-address, then the Called Party BCD Number and Called Party Sub-
address information element shall be ignored for the purposes of compatibility checking. The compatibility
checking described in B.3.2 and B.3.3 shall be performed.
NOTE: According to the users requirements, compatibility checking can be performed in various ways from the
viewpoint of execution order and information to be checked, e.g. first DDI number/sub-address and then
bearer capability or vice versa.
B.3.2 Network-to-MS compatibility checking
When the network is providing a basic service at the called side, the MS shall check that the basic service(s) offered by
the network in the Bearer Capability information element(s) match(es) the basic services that the MS is able to support.
If a mismatch is detected, then the MS shall proceed as follows:
- if the SETUP message contained two bearer capability information elements for only one of which a mismatch is
detected, the MS shall either:
- under the conditions specified in GSM 07.01 (e.g. TS 61 and TS 62), accept the SETUP message with a
CALL CONFIRMED message containing the, possibly negotiated, bearer capability information element for
which no mismatch is detected, or
- reject the call using cause No. 88 "incompatible destination".
- otherwise the MS shall reject the offered call using a RELEASE COMPLETE message with cause No. 88
"incompatible destination".
When interworking with existing networks, limitations in network or distant user signalling (e.g. in the case of an
incoming call from a PSTN or a call from an analogue terminal) may restrict the information available to the called MS
in the incoming SETUP message (e.g. missing Bearer Capability Information Element or missing High Layer
Compatibility Information Element). For compatibility checking, and handling of such calls see GSM 07.01.
B.3.3 User-to-User compatibility checking
See GSM 07.01.
B.4 High layer compatibility checking
See GSM 07.01.
ETSI
Annex C (normative):
Low layer information coding principles
This annex is normative.
C.1 Purpose
This annex describes principles that shall be used when the calling MS specifies information during call setup regarding
low layer capabilities required in the network and by the destination terminal. Refer also to GSM 07.01.
NOTE: In this context and throughout this annex the term "called user" is the end point entity which is explicitly
addressed. This may also be an explicitly addressed interworking unit (IWU) (see CCITT I.500-Series
Recommendations and CCITT Recommendation X.31 case a).
C.2 Principles
C.2.1 Definition of types of information
There are three different types of information that the calling PLMN user may specify during call setup to identify low
layer capabilities needed in the network and in the destination terminal:
a) type I information is information about the calling terminal which is only used at the destination end to allow a
decision regarding terminal compatibility. An example would be the user information layer 3 protocol. Type I
information is encoded in octets 5 to 7 of the low layer compatibility information element;
b) type II information is only used by the network (PLMN) to which the calling user is connected for selection of
PLMN specific network resources, e.g. channel type or specific functionality within the interworking function
(IWF, see TS 09.07). This type of information is always present. An example is the connection element. Type II
information is coded in:
i) octet 3 of the bearer capability information element when the information transfer capability required by the
calling user is speech ;
ii) octets 3, 4, 5, and optionally octet 7 of the bearer capability information element when the information
transfer capability required by the calling user is not speech;
c) type III information is required for selection of a basic service from the choice of basic services offered by the
network and together with type II information for selection of an appropriate interworking function (IWF, see
GSM 09.07), as well as for terminal compatibility checking at the destination terminal . An example is the
information transfer capability. Type III information is always present and is encoded in:
i) octet 3 of the bearer capability information element when the information transfer capability required by the
calling user is speech ;
ii) octets 3, 5, 6, 6a, 6b and 6c of the bearer capability information element when the information transfer
capability required by the calling user is not speech;
C.2.2 Examination by network
Type I information is user-to-user (i.e. at the calling side not examined by network) while type II and III information
should be available for examination by the destination user and the network.
NOTE: In the case of a mobile terminated call, if the type II and type III information is not sufficient for the
selection of an appropriate interworking function, the type I information will also examined by the
network.
ETSI
C.2.3 Location of type I information
Type I information (i.e. terminal information only significant to the called user) shall, when used, be included in the low
layer compatibility information element.
C.2.4 Location of types II and III information
Type II information is included in the bearer capability information element. Type III information is also included in the
bearer capability information element. The network may use and modify type III information (e.g. to provide
interworking).
In any case a modification of the bearer capability information element has to be performed when interworking to the
fixed network (e.g. ISDN) is required, where the signalling of the radio interface has to be mapped to fixed network
signalling (e.g. mapping of GSM BCIE to ISDN BCIE, see GSM 09.07).
C.2.5 Relationship between bearer capability and low layer
compatibility information elements
There shall be no contradiction of information between the low layer compatibility and the bearer capability at the
originating side. However, as some bearer capability code points may be modified during the transport of the call (e.g.
by the interworking function), this principle implies that there should be minimal duplication of information between the
bearer capability information element and the low layer compatibility information element.
NOTE: If as a result of duplication, a contradiction occurs at the terminating side between the bearer capability
information element and the low layer compatibility information element at the terminating side, the
receiving entity shall ignore the conflicting information in the low layer compatibility information
element.
ETSI
Annex D (informative):
Examples of bearer capability information element coding
This annex gives examples of the coding of bearer capability information elements for various telecommunication
services. This annex is included for information purposes only. In the case of any inconsistency between this annex and
GSM 07.01 then GSM 07.01 shall take precedence over this annex.
D.1 Coding for speech for a full rate support only mobile
station
D.1.1 Mobile station to network direction
8 7 6 5 4 3 2 1
+-----------------------------------------------+
0 0 0 0 0 1 0 0 octet 1
Bearer capability IEI
+-----------------------------------------------
0 0 0 0 0 0 0 1
+-----------------------------------------------
1 0 1 0 0 0 0 0
not full rate GSM circ. speech octet 3
ext only mode
+-----------------------------------------------+
D.1.2 Network to mobile station direction
8 7 6 5 4 3 2 1
+-----------------------------------------------+
0 0 0 0 0 1 0 0 octet 1
+-----------------------------------------------
0 0 0 0 0 0 0 1
+-----------------------------------------------
1 0 1 0 0 0 0 0
not spare spare GSM circ. speech octet 3
ext mode
+-----------------------------------------------+
ETSI
D.2 An example of a coding for modem access with V22-
bis, 2.4 kbit/s, 8 bit no parity
D.2.1 Mobile station to network direction, data compression
allowed
8 7 6 5 4 3 2 1
+-----------------------------------------------+
0 0 0 0 0 1 0 0 octet 1
+-----------------------------------------------
0 0 0 0 0 1 1 1
+-----------------------------------------------
1 1 0 0 0 0 1 0
not dual, half GSM circ. 3.1 kHz audio octet 3
ext preferred mode ex PLMN
+-----+-----------------+-----+-----------------
1 1 0 0 1 0 0 0
not comp- SDU full pt to no de- octet 4
ext ress. integrity dupl. pt NIRR mand
+-----+-----------------------+-----------------
1 0 0 0 0 0 0 1
not access id. no rate I.440/450 octet 5
ext adaption
+-----+-----------+-----------------------------
0 0 1 0 0 0 0 1
ext layer 1 default layer 1 async octet 6
+-----+-----------+-----------------------------
0 0 0 1 0 0 1 1
ext 1 bit no 8 2.4 kbit/s octet 6a
neg bits
+-----+-----------+-----+-----------------------
0 1 1 0 0 0 1 1
ext 16 kbit/s no no (parity) none octet 6b
inter. rate NICtx NICrx
+-----+-----------+-----------------------------
1 0 1 0 0 0 1 1
not non trans V.22 bis octet 6c
ext (RLP)
+-----------------------------------------------+
D.2.2 Network to mobile station direction, data compression
possible
8 7 6 5 4 3 2 1
+-----------------------------------------------+
0 0 0 0 0 1 0 0 octet 1
+-----------------------------------------------
0 0 0 0 0 1 1 1
+-----------------------------------------------
1 0 1 0 0 0 1 0
not spare spare GSM circ. 3.1 kHz audio octet 3
ext mode ex PLMN
+-----+-----+-----------+-----+-----------------
1 1 0 0 1 0 0 0
not comp- SDU full pt to no de- octet 4
ext ress. integrity dupl. pt NIRR mand
+-----+-----------------------+-----------------
1 0 0 0 0 0 0 1
ext adaption
+-----+-----------+-----------------------------
0 0 1 0 0 0 0 1
ext layer 1 default layer 1 async octet 6
+-----+-----------+-----------------------------
0 0 0 1 0 0 1 1
ext 1 bit no 8 2.4 kbit/s octet 6a
neg bits
ETSI
+-----+-----------+-----+-----------------------
0 1 1 0 0 0 1 1
+-----+-----------+-----------------------------
1 0 1 0 0 0 1 1
not non trans V.22 bis octet 6c
ext (RLP)
+-----------------------------------------------+
ETSI
D.3 An example of a coding for group 3 facsimile (9.6
kbit/s, transparent)
D.3.1 Mobile station to network direction
8 7 6 5 4 3 2 1
+-----------------------------------------------+
0 0 0 0 0 1 0 0 octet 1
+-----------------------------------------------
0 0 0 0 0 1 1 1
+-----------------------------------------------
1 0 1 0 0 0 1 1
not full rate GSM circ. facsimile octet 3
ext only MS mode group 3
+-----+-----------------+-----+-----------------
1 0 1 1 1 0 0 0
not comp- unstruc- full pt to no de- octet 4
ext ress. tured dupl. pt NIRR mand
+-----+-----------------------+-----------------
1 0 0 0 0 0 0 1
ext adaption
+-----+-----------+-----------------------------
0 0 1 0 0 0 0 0
ext layer 1 default layer 1 sync octet 6
+-----+-----------+-----------------------------
0 0 0 1 0 1 0 1
ext (syn) no (syn) 9.6 kbit/s octet 6a
neg
+-----+-----------+-----+-----------------------
0 1 1 0 0 0 1 1
+-----+-----------+-----------------------------
1 0 0 0 0 0 0 0
not transparent none octet 6c
ext (modem type)
+-----------------------------------------------+
ETSI
D.3.2 Network to mobile station direction
8 7 6 5 4 3 2 1
+-----------------------------------------------+
0 0 0 0 0 1 0 0 octet 1
+-----------------------------------------------
0 0 0 0 0 1 1 1
+-----------------------------------------------
1 0 1 0 0 0 1 0
not spare spare GSM circ. 3.1 kHz audio octet 3
ext mode ex PLMN
+-----+-----+-----------+-----+-----------------
1 0 1 1 1 0 0 0
not comp- unstruc- full pt to no de- octet 4
ext ress. tured dupl. pt NIRR mand
+-----+-----------------------+-----------------
1 0 0 0 0 0 0 1
ext adaption
+-----+-----------+-----------------------------
0 0 1 0 0 0 0 0
ext layer 1 default layer 1 sync octet 6
+-----+-----------+-----------------------------
0 0 0 1 0 1 0 1
ext (syn) no (syn) 9.6 kbit/s octet 6a
neg
+-----+-----------+-----+-----------------------
0 1 1 0 0 0 1 1
+-----+-----------+-----------------------------
1 0 0 0 0 0 0 0
not transparent none octet 6c
ext (modem type)
+-----------------------------------------------+
ETSI
Annex E (informative):
Comparison between call control procedures specified in
GSM 04.08 and CCITT Recommendation Q.931
This annex summarizes a comparison of the procedures for call control as specified in CCITT Recommendation Q.931
(blue book) and GSM 04.08.
If no comment is given, it means that the procedures specified in CCITT Recommendation Q.931 and GSM 04.08 are
similar. However, it should be noted that even in such cases the procedures may be described in slightly different ways
in the two documents.
Table E.1/GSM 04.08: Circuit-switched call control procedures
+-------------------------------------------------------------+
Procedure Q.931 GSM04.08
+----------------------+-------------+------------------------
Call establishment at 5.1 5.2.1
the originating
interface

- call request 5.1.1 5.2.1.1.1
en-bloc sending only

- B-channel selection 5.1.2 not applicable
originating

- overlap sending 5.1.3 not supported

- invalid call 5.1.4 5.2.1.1.2
information

- call proceeding, 5.1.5.1 5.2.1.1.3
en-bloc sending

- call proceeding, 5.1.5.2 not supported
overlap sending

- notification of 5.1.6 5.2.1.1.4
interworking at the
originating interf.

- call confirmation 5.1.7 5.2.1.1.5
indication

- call connected 5.1.8 5.2.1.1.6

- call rejection 5.1.9 5.2.1.1.7

- transit network 5.1.10 5.2.1.1.8
selection

+-------------------------------------------------------------+
ETSI
Table E.1/GSM 04.08: Circuit-switched call control procedures (continued)
+-------------------------------------------------------------+
+----------------------+-------------+------------------------
Call establishment at 5.2 5.2.2
the destination
interface

- call indication 5.2.1 5.2.2.1
procedure for multiple
terminal configuration
not required, i.e.
delivery of SETUP
messages on broadcast
data links is not
supported

- compatibility 5.2.2 5.2.2.2
checking equivalent, except that
delivery of SETUP mes-
sages on broadcast data
links is not supported

- B-channel selection 5.2.3 not applicable
destination

- overlap receiving 5.2.4 not supported

- call confirmation 5.2.5 5.2.2.3
information equivalent, except that
delivery of SETUP mes-
sages on broadcast data
links is not supported

- notification of 5.2.6 5.2.2.4
interworking at the
terminating interf.

- call accept 5.2.7 5.2.2.5
indication

- active indication 5.2.8 5.2.2.6
equivalent, except that
SETUP messages are not
sent on broadcast data
links

- non-selected user 5.2.9 not applicable
clearing
+-------------------------------------------------------------+
ETSI
+--------------------------------------------------------------+
+----------------------+------------+--------------------------
Call clearing 5.3 5.4

- terminology 5.3.1 5.4.1
terminology adapted to
GSMapplications

- exception 5.3.2 5.4.2
conditions only case a) of section
5.3.2 of Rec. Q.931 ap-
plies. All other excep-
tions apply to functions
which are not relevant
to GSM

- clearing initiated 5.3.3 5.4.3
by the user/MS

- clearing initiated 5.3.4 5.4.4
by the network

- clearing when 5.3.4.1 5.4.4.1.1 and 5.4.4.2.1
tones/announcements exception: if not already
are provided connected, the traffic
channel is connected in
order to provide the
tone/announcement

- clearing when 5.3.4.2 5.4.4.1.2 and 5.4.4.2.3
tones/announcements
are not provided

- completion of 5.3.4.3 5.4.4.1.3 and 5.4.4.2.5
clearing

Clear collision 5.3.5 5.4.5

+--------------------------------------------------------------+
ETSI
+--------------------------------------------------------------+
+---------------------+-------------+--------------------------
In-band tones and 5.4 5.5.1
announcements

Restart procedure 5.5 not supported

Call rearrangements 5.6 5.3.4
call suspension/call re-
establishment not suppor-
ted on the radio path.
The functions, if requi-
red, are to be supported
locally in the MS. On the
radio interface, the
notification procedure
of Rec. Q.931 (section
5.6.7) applies

Call collisions 5.7 5.5.2
call collisions cannot
occur

Emergency call esta- not specified 5.2.1.2
blishment at the ori- not supported
ginating interface

In-call modification Annex O 5.3.4
Rec. Q.931 is
incomplete
with regard
to in-call
modification
procedures

DTMF protocol control not specified 5.3.3
procedures not supported

Call re-establishment not specified 5.5.4
not supported

Status enquiry 5.8.10, 5.5.3
procedure 5.8.11

User-to-user 7 GSM04.10
signalling

User notification 5.9 5.3.1
procedure

+--------------------------------------------------------------+
ETSI
Annex F (informative):
GSM specific cause values for radio resource management
Cause value = 0 Normal event;
indicates that the channel is released because of a normal event or that an assignment or handover is successfully,
and normally, completed.
Cause value = 1 Abnormal release, unspecified;
indicates that the channel is released because of an abnormal event without specifying further reasons.
Cause value = 2 Abnormal release, channel unacceptable;
indicates that the channel type or channel characteristics are not acceptable.
Cause value = 3 Abnormal release, timer expired;
indicates that the release is caused by a timer expiry.
Cause value = 4 Abnormal release, no activity on the radio path;
indicates that some supervisory function has detected that the channel is not active.
Cause value = 5 Pre-emptive release;
indicates that the channel is released in order to be allocated to a call with priority (e.g. an emergency call).
Cause value = 8 Handover impossible, timing advance out of range;
indicates that a handover is unsuccessful because the target BTS is beyond the normal range and the target BTS
would not accept an out of range timing advance.
Cause value = 9 Channel mode unacceptable
indicates that the MS does not have the capability to handle the requested mode or type of channel.
Cause value = 10 Frequency not implemented
indicates that the MS does not have the capability to operate on (at least one of) the requested frequency(ies).
Cause value = 65 Call already cleared;
indicates that a handover is unsuccessful because the connection has been released by the network or the remote
user.
Cause value = 95 Semantically incorrect message;
See annex H, section H5.10.
Cause value = 96 Invalid mandatory information;
Cause value = 97 Message type non-existent or not implemented;
Cause value = 98 Message type not compatible with protocol state;
See annex H, section H6.3
Cause value = 100 Conditional IE error;
ETSI
See annex H, section H6.5
Cause value = 101 No cell allocation available;
indicates that an assignment or handover is unsuccessful because the MS has no current CA.
Cause value = 111 Protocol error unspecified;
ETSI
Annex G (informative):
GSM specific cause values for mobility management
This annex is informative. It describes the cause values for the mobility management procedures for non-GPRS services
(MM) and GPRS services (GMM). Sections G1 to G5 are valid for both MM and GMM. However, the following codes
are applicable for non-GPRS services only:
#38 Call cannot be identified
Section G.6 applies only for GMM procedures.
G.1 Causes related to MS identification
Cause value = 2 IMSI unknown in HLR
This cause is sent to the MS if the MS is not known (registered) in the HLR. This cause code does not affect
operation of the GPRS service, although is may be used by a GMM procedure.
Cause value = 3 Illegal MS
This cause is sent to the MS when the network refuses service to the MS either because an identity of the MS is
not acceptable to the network or because the MS does not pass the authentication check, i.e. the SRES received
from the MS is different from that generated by the network.
Cause value = 4 IMSI unknown in VLR
This cause is sent to the MS when the given IMSI is not known at the VLR.
Cause value = 5 IMEI not accepted
This cause is sent to the MS if the network does not accept emergency call establishment using an IMEI.
Cause value = 6 Illegal ME
This cause is sent to the MS if the ME used is not acceptable to the network, e.g. blacklisted.
G.2 Cause related to subscription options
Cause value = 11 PLMN not allowed
This cause is sent to the MS if it requests location updating in a PLMN where the MS, by subscription or due to
operator determined barring is not allowed to operate.
Cause value = 12 Location Area not allowed
This cause is sent to the MS if it requests location updating in a location area where the MS, by subscription, is
not allowed to operate.
Cause value = 13 Roaming not allowed in this location area
This cause is sent to an MS which requests location updating in a location area of a PLMN which offers roaming
to that MS in that Location Area, by subscription.
G.3 Causes related to PLMN specific network failures
and congestion
Cause value = 17 Network failure
ETSI
This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, e.g.
problems in MAP.
Cause value = 22 Congestion
This cause is sent if the service request cannot be actioned because of congestion (e.g. no channel, facility
busy/congested etc.)
G.4 Causes related to nature of request
Cause value = 32 Service option not supported
This cause is sent when the MS requests a service/facility in the CM SERVICE REQUEST message which is not
supported by the PLMN.
Cause value = 33 Requested service option not subscribed
This cause is sent when the MS requests a service option for which it has no subscription.
Cause value = 34 Service option temporarily out of order
This cause is sent when the MSC cannot service the request because of temporary outage of one or more
functions required for supporting the service.
Cause value = 38 Call cannot be identified
This cause is sent when the network cannot identify the call associated with a call re-establishment request.
G.5 Causes related to invalid messages
Cause value = 95 Semantically incorrect message.
See annex H, section H.5.10.
Cause value = 96 Invalid mandatory information.
Cause value = 97 Message type non-existent or not implemented.
Cause value = 98 Message not compatible with protocol state.
Cause value = 99 Information element non-existent or not implemented
Cause value = 100 Conditional IE error.
Cause value = 101 Message not compatible with protocol state
Cause value = 111 Protocol error, unspecified
ETSI
G.6 Additional cause codes for GMM
Cause value = 7 GPRS services not allowed
This cause is sent to the MS if it requests an IMSI attach for GPRS services, but is not allowed to operate GPRS
services.
Cause value = 8 GPRS services and non-GPRS services not allowed
This cause is sent to the MS if it requests a combined IMSI attach for GPRS and non-GPRS services, but is not
allowed to operate either of them.
Cause value = 9 MS identity cannot be derived by the network
This cause is sent to the MS when the network cannot derive the MSs identity from the P-TMSI in case of inter-
SGSN routing area update.
Cause value = 10 Implicitly detached
This cause is sent to the MS either if the network has implicitly detached the MS, e.g. some while after the Mobile
reachable timer has expired, or if the GMM context data related to the subscription dose not exist in the SGSN
e.g. because of a SGSN restart.
Cause value = 16 MSC temporarily not reachable
This cause is sent to the MS if it requests a combined GPRS attach or routing are updating in a PLMN where the
MSC is temporarily not reachable via the GPRS part of the GSM network.
ETSI
Annex H (informative):
GSM specific cause values for call control
H.1 Normal class
H.1.1 Cause No. 1 "unassigned (unallocated) number"
This cause indicates that the destination requested by the mobile station cannot be reached because, although the number
is in a valid format, it is not currently assigned (allocated).
H.1.2 Cause No. 3 "no route to destination"
This cause indicates that the called user cannot be reached because the network through which the call has been routed
does not serve the destination desired.
H.1.3 Cause No. 6 "channel unacceptable"
This cause indicates the channel most recently identified is not acceptable to the sending entity for use in this call.
H.1.4 Cause No. 8 "operator determined barring"
This cause indicates that the MS has tried to access a service that the MSs network operator or service provider is not
prepared to allow.
H.1.5 Cause No.16 "normal call clearing"
This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call
be cleared.
Under normal situations, the source of this cause is not the network.
H.1.6 Cause No.17 "user busy"
This cause is used when the called user has indicated the inability to accept another call.
It is noted that the user equipment is compatible with the call.
H.1.7 Cause No. 18 "no user responding"
This cause is used when a user does not respond to a call establishment message with either an alerting or connect
indication within the prescribed period of time allocated (defined by the expiry of either timer T303 or T310).
H.1.8 Cause No. 19 "user alerting, no answer"
This cause is used when a user has provided an alerting indication but has not provided a connect indication within a
prescribed period of time.
ETSI
H.1.9 Cause No. 21 "call rejected"
This cause indicates that the equipment sending this cause does not wish to accept this call, although it could
have accepted the call because the equipment sending this cause is neither busy nor incompatible.
H.1.10 Cause No. 22 "number changed"
This cause is returned to a calling mobile station when the called party number indicated by the calling mobile station is
no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does
not support this capability, cause No. 1 "unassigned (unallocated) number" shall be used.
H.1.11 Cause No. 25 pre-emption
This cause is returned to the network when a mobile station clears an active call which is being pre-empted by another
call with higher precedence.
H.1.12 Cause No. 26 "non-selected user clearing"
Not supported. Treated as cause no. 31.
H.1.13 Cause No. 27 "destination out of order"
This cause indicates that the destination indicated by the mobile station cannot be reached because the interface to the
destination is not functioning correctly. The term "not functioning correctly" indicates that a signalling message was
unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user
equipment off-line, etc.
H.1.14 Cause No. 28 "invalid number format (incomplete number)"
This cause indicates that the called user cannot be reached because the called party number is not a valid format or is not
complete.
H.1.15 Cause No. 29 "facility rejected"
This cause is returned when a facility requested by user can not be provided by the network.
H.1.16 Cause No. 30 "response to STATUS ENQUIRY"
This cause is included in STATUS messages if the message is sent in response to a STATUS ENQUIRY message. See
also section 5.5.3.
H.1.17 Cause No. 31 "normal, unspecified"
This cause is used to report a normal event only when no other cause in the normal class applies.
H.2 Resource unavailable class
H.2.1 Cause No. 34 "no circuit/channel available"
This cause indicates that there is no appropriate circuit/channel presently available to handle the call.
ETSI
H.2.2 Cause No. 38 "network out of order"
This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long
period of time; e.g., immediately re-attempting the call is not likely to be successful.
H.2.3 Cause No. 41 "temporary failure"
This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period
of time; e.g., the mobile station may wish to try another call attempt almost immediately.
H.2.4 Cause No. 42 "switching equipment congestion"
This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.
H.2.5 Cause No. 43 "access information discarded"
This cause indicates that the network could not deliver access information to the remote user as requested; i.e., a user-to-
user information, low layer compatibility, high layer compatibility, or sub-address as indicated in the diagnostic.
It is noted that the particular type of access information discarded is optionally included in the diagnostic.
H.2.6 Cause No. 44 "requested circuit/channel not available"
This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side
of the interface.
H.2.7 Cause No. 47 "resource unavailable, unspecified"
This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class
applies.
H.3 Service or option not available class
H.3.1 Cause No. 49 "quality of service unavailable"
This cause indicates to the mobile station that the requested quality of service, as defined in CCITT Recommendation
X.213, cannot be provided.
H.3.2 Cause No. 50 "Requested facility not subscribed"
This cause indicates that the requested supplementary service could not be provided by the network because the user has
no completed the necessary administrative arrangements with its supporting networks.
H.3.3 Cause No. 55 "Incoming calls barred within the CUG"
This cause indicates that although the called party is a member of the CUG for the incoming CUG call, incoming calls
are not allowed within this CUG.
H.3.4 Cause No. 57 "bearer capability not authorized"
This cause indicates that the mobile station has requested a bearer capability which is implemented by the equipment
which generated this cause but the mobile station is not authorized to use.
ETSI
H.3.5 Cause No. 58 "bearer capability not presently available"
This cause indicates that the mobile station has requested a bearer capability which is implemented by the equipment
which generated this cause but which is not available at this time.
H.3.6 Cause No. 63 "service or option not available, unspecified"
This cause is used to report a service or option not available event only when no other cause in the service or option not
available class applies.
H.3.7 Cause No. 68 "ACM equal to or greater than ACMmax"
This cause is used by the mobile to indicate that call clearing is due to ACM being greater than or equal to ACMmax.
H.4 Service or option not implemented class
H.4.1 Cause No. 65 "bearer service not implemented"
This cause indicates that the equipment sending this cause does not support the bearer capability requested.
H.4.2 Cause No. 69 "Requested facility not implemented"
This cause indicates that the equipment sending this cause does not support the requested supplementary service.
H.4.3 Cause No. 70 "only restricted digital information bearer
capability is available"
This cause indicates that one equipment has requested an unrestricted bearer service, but that the equipment
sending this cause only supports the restricted version of the requested bearer capability.
H.4.4 Cause No. 79 "service or option not implemented,
unspecified"
This cause is used to report a service or option not implemented event only when no other cause in the service or
option not implemented class applies.
H.5 Invalid message (e.g., parameter out of range) class
H.5.1 Cause No. 81 "invalid transaction identifier value"
This cause indicates that the equipment sending this cause has received a message with a transaction identifier
which is not currently in use on the MS-network interface.
H.5.2 Cause No. 87 "user not member of CUG"
This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG.
ETSI
H.5.3 Cause No. 88 "incompatible destination"
This cause indicates that the equipment sending this cause has received a request to establish a call which has low
layer compatibility, high layer compatibility, or other compatibility attributes (e.g., data rate) which cannot be
accommodated.
H.5.4 Cause No. 91 "invalid transit network selection"
For further study. Treated as cause no. 95.
H.5.5 Cause No. 95 "semantically incorrect message"
This cause is used to report receipt of a message with semantically incorrect contents (see section 8.8).
H.6 Protocol error (e.g., unknown message) class
H.6.1 Cause No. 96 "invalid mandatory information"
This cause indicates that the equipment sending this cause has received a message with a non-semantical
mandatory IE error (see section 8.5).
H.6.2 Cause No. 97 "message type non-existent or not
implemented"
This cause indicates that the equipment sending this cause has received a message with a message type it does not
recognize either because this is a message not defined, or defined but not implemented by the equipment sending
this cause.
H.6.3 Cause No. 98 "message type not compatible with protocol
state"
This cause indicates that the equipment sending this cause has received a message not compatible with the
protocol state (section 8.4).
H.6.4 Cause No. 99 "information element non-existent or not
implemented"
This cause indicates that the equipment sending this cause has received a message which includes information
elements not recognized because the information element identifier is not defined or it is defined but not
implemented by the equipment sending the cause. However, the information element is not required to be present
in the message in order for the equipment sending the cause to process the message.
H.6.5 Cause No. 100 "conditional IE error"
This cause indicates that the equipment sending this cause has received a message with conditional IE errors (see
section 8.7.2).
H.6.6 Cause No. 101 "message not compatible with protocol state"
This cause indicates that a message has been received which is incompatible with the protocol state or that a
STATUS message has been received indicating an incompatible call state.
ETSI
H.6.7 Cause No. 102 "recovery on timer expiry"
This cause indicates that a procedure has been initiated by the expiry of a timer in association with TS 04.08
error handling procedures.
H.6.8 Cause No. 111 "protocol error, unspecified"
This cause is used to report a protocol error event only when no other cause in the protocol error class applies.
H.7 Interworking class
H.7.1 Cause No. 127 "interworking, unspecified"
This cause indicates that there has been interworking with a network which does not provide causes for actions it
takes; thus, the precise cause for a message which is being sent cannot be ascertained.
ETSI
Annex I (informative):
GSM specific cause values for session management
I.1 Causes related to nature of request
Cause value = 25 LLC or SNDCP failure
This cause code is used by the MS indicate that a PDP context is deactivated because of a LLC or SNDCP failure
( e.g. if the SM receives a SNSM-STATUS.request message with cause "DM received " or " invalid XID response
", see 04.65 [78])
Cause value = 26 Insufficient resources
This cause code is used by the MS or by the network to indicate that a PDP context activation request or PDP
context modification request cannot be accepted due to insufficient resources.
Cause value = 27 Unknown or missing access point name
This cause code is used by the network to indicate that the requested service was rejected by the external packet
data network because the access point name was not included although required or if the access point name could
not be resolved.
Cause value = 28 Unknown PDP address or PDP type
data network because the PDP address or type could not be recognised.
Cause value = 29 User authentication failed
data network due to a failed user authentication.
Cause value = 30 Activation rejected by GGSN
This cause code is used by the network to indicate that the requested service was rejected by the GGSN..
Cause value = 31 Activation rejected, unspecified
This cause code is used by the network to indicate that the requested service was rejected due to unspecified
reasons.
Cause value = 32 Service option not supported
This cause code is used by the network when the MS requests a service which is not supported by the PLMN.
Cause value = 33 Requested service option not subscribed
See Annex G, section 4.
Cause value = 34 Service option temporarily out of order
See Annex G, section 4.
Cause value = 35 NSAPI already used
This cause code is used by the network to indicate that the NSAPI requested by the MS in the PDP context
activation is already used by another active PDP context of this MS.
Cause value = 36 Regular PDP context deactivation
ETSI
This cause code is used to indicate a regular MS or network initiated PDP context deactivation.
Cause value = 37 QoS not accepted
This cause code is used by the MS if the new QoS cannot be accepted that were indicated by the network in the
PDP Context Modification procedure.
Cause value = 38 Network failure
This cause code is used by the network to indicate that the PDP context deactivation is caused by an error
situation in the network.
Cause value = 39 Reactivation requested
This cause code is used by the network to request a PDP context reactivation after a GGSN restart.
Cause value = 40 Feature not supported
This cause code is used by the MS to indicate that the PDP context activation initiated by the network is not
supported by the MS.
I.2 Causes related to invalid messages
Cause value = 81 Invalid transaction identifier value.
Cause value = 95 Semantically incorrect message.
Cause value = 96 Invalid mandatory information.
Cause value = 97 Message type non-existent or not implemented.
Cause value = 98 Message not compatible with protocol state.
Cause value = 99 Information element non-existent or not implemented
Cause value = 100 Conditional IE error.
Cause value = 101 Message not compatible with protocol state
Cause value = 111 Protocol error, unspecified
ETSI
Annex J (informative):
Algorithm to encode frequency list information elements
J.1 Introduction
Some information elements encode frequency lists with a special method. The main specification specifies the meaning
of the fields and hence the way to decode them, but the corresponding encoding algorithm is difficult to infer from the
decoding algorithm. This annex is intended as an aid for implementers of the encoding algorithm.
It could be shown that any set of frequency with less or the same number of frequencies as the number of words can be
encoded with a careful choice of F1, F2, and so on, i.e. that a set of Wi can be found so that the decoding algorithm
given in the main section will give back the frequency set. The right order is not the order of the frequency values.
J.2 General principle
The encoding algorithm is based on a recursive dichotomy of both the range (i.e. the set of values that are possible) and
the subset (the values to encode).
The dichotomy is best understood if the range is seen as a circle. For instance, for the 1023 range:
1
0
2
3
0
1
2
3
1
0
2
2
5
1
2
5
1
1
Figure J.1: Circular arrangement of 0..1023
The dichotomy consists in finding a value in the subset such that the diameter determined by this value splits the subset
in two equal or nearly equal sub-subsets. In the following case, we see that value 290 is acceptable (the two sub-subsets
have 3 elements), when value 250 is not acceptable (the two sub-subsets have 4 and 2 elements):
ETSI
50
90
250
290
480
600
650
Figure J.2: Example of dichotomy
The pivot value is part of the information field, then the two sub-subsets are renumbered and the same algorithm is
applied again on each of them. Because the range is halved at each step, the number of bits needed to encode a pivot
value is 1 bit less than the number of bits needed to encode the parent pivot value.
The convention is that if the number of values is even, the left sub-subset (that is to say the values that can be expressed
as the pivot value minus some integer between 1 and half the range) will have 1 element more than the right subset.
At each step the subset is numbered from 0 to the range minus 1. The coding in the information field of the pivot value
is its value as renumbered, plus 1. Value 0 is reserved to indicate no element.
The order of appearance in the information field of the successive pivot values is particular. If we present the values as
organized as a tree, with the left child being the pivot of the left sub-subset and the right child the pivot of the right sub-
subset, the order of appearance is given by the following tree:
1
2 3
4
6
5 7
8 12 10 14 9 13 11 15
(and so on)
This order has been chosen so that
a) whatever the number N of elements in the set, the meaningful nodes are the first N and the value for all nodes
from N+1 on are null (if sent),
b) the tree and all subtrees are balanced.
Important properties of these trees are used in the algorithms (with generation 1 corresponding to the root):
Generation g contains 2
g-1
nodes, and their indices are 2
g-1
to 2
g
-1;
For generation g, nodes 2
g-1
to 2
g-1
+2
g-2
-1 are left children, the others are right children;
If node k belongs to generation g, its left child is node k + 2
g-1
, and its right child is k + 2
g
;
ETSI
Reciprocally, if k is a left child from generation g, its parent node is node k - 2
g-2
, and if k is a right child of
generation g, its parent is node k - 2
g-1
.
J.3 Performances
The number of bits needed to encode a given set of values depends on the number of values and on the range they can
span.
For the application on the BCCH and the SACCH (CA and BA information ) 16 octets are available, and the number of
frequencies that can be encoded in one information element is the following:
Range Number
of frequencies
513 to 1024 2 to 16 (17 if frequency 0 is in)
257 to 512 2 to 18
129 to 256 2 to 22
113 to 128 2 to 29
up to 112 any
With two messages (for the BA) the number of frequencies that can be encoded is the following:
Range Number
of frequencies
513 to 1024 2 to 36 (note 1)
257 to 512 2 to 40 (note 2)
225 to 256 2 to 51 (note 3)
up to 224 any
NOTE 1: A 1024 range can be split cyclically in to two 512 ranges each with less than 18 frequencies; each subset
is coded in one message with 512 range format.
NOTE 2: A 512 range can be split in to two consecutive 256 ranges. If both sub-ranges contain 22 frequencies or
less, it is possible to code each of these in a messages using the 256 range format. Otherwise one of the
two ranges contains 23 frequencies or more: 22 of them can be coded in one message using the 256 range
format and the remaining frequencies (numbering less than or equal to 18) can be coded in the other
message using the 512 range format.
NOTE 3: The principles described in notes 1 and 2, above apply in this case.
The frequency short list information element allows the following:
Range Number
of frequencies
513 to 1024 2 to 7 (8 if frequency 0 is in)
257 to 512 2 to 8
129 to 256 2 to 9
57 to 128 2 to 12
up to 56 any
The number of frequencies as a function of the range and the length in octets of the variable length frequency list
information element (including the message type and length fields) is given by the following table:
ETSI
Table J.1/GSM 04.08: Performance of the variable length frequency list information element
Range 513 to 1024 257 to 512 129 to 256 up to
128
variable bit
map
octets
5 1 1 1 1 8
6 2 2 3 3 16
7 3 3 4 4 24
8 4 4 5 6 32
9 5 6 6 8 40
10 6 7 8 10 48
11 7 8 9 12 56
12 9 9 11 14 64
13 10 11 13 16 72
14 11 12 14 18 80
15 12 13 16 21 88
16 13 15 18 24 96
17 14 16 20 26 104
18 16 18 22 29 112
19 17 19 24 32 120
20 18 21 26 -- 128
21 20 22 28 136
22 21 24 30 144
23 22 26 32 152
24 24 27 34 160
25 25 29 37 168
26 26 30 40 176
27 28 32 42 184
28 29 34 45 192
29 30 36 48 200
30 32 38 50 208
31 33 40 53 216
32 35 42 56 224
J.4 Encoding algorithm
The choice is done recursively as given by the following programs, written in ADA:
Let us define the recursive procedure:
procedure ENCODE_SUBTREE(in INDEX : INTEGER;
in SET : SET_OF_VALUE;
in RANGE : INTEGER);
This procedure is given a set of integer values and an index. It chooses one of those values and computes the
corresponding W(INDEX) (considered as a global variable), it splits the set less the value in two equal or nearly equal
subsets, and calls itself recursively for each of those subsets, with suitable INDEX.
Assumption: all values in SET lie (inclusively) between 0 and RANGE-1, and they are all distinct.
As written, the program does not assume special values for the range. With a range such as 2
k
-1, some expressions can
be simplified.
Declarative part:
INDEX_IN_SET : INTEGER;
begin
First the program tests the leaf conditions :
if SETSIZE=0 then
W(INDEX) := 0;
return;
elsif SETSIZE=1 then
W(INDEX) := 1 + SET(1);
return;
end if;
ETSI
The following program finds a value in the set such that exactly (SETSIZE-1)/2 values from the set
are between this value plus 1 and this value plus half the range :
declare
N : INTEGER;
J : INTEGER;
begin
for I in 1..SETSIZE loop
N:=0;
for J in 1..SETSIZE loop
if (SET(J)-SET(I)) mod RANGE <= (RANGE-1)/2 then
N := N+1;
end if;
end loop;
The test compares N-1 because the possible pivot value is counted.
if N-1 = (SETSIZE-1)/2 then
INDEX_IN_SET := I;
exit;
end if;
end loop;
end;
INDEX_IN_SET is then the index in the list of the pivot value.
The following sets W(INDEX)
W(INDEX) := SET(INDEX_IN_SET) + 1;
Then the program does the same thing for the two halves of the range delimited by W(INDEX) and
W(INDEX)+RANGE/2. First the left subset:
declare
SUBSET : SET_OF_VALUE(1..SETSIZE/2);
SUBSET_INDEX : INTEGER;
ORIGIN_VALUE : INTEGER;
begin
ORIGIN_VALUE := (SET(INDEX_IN_SET] + (RANGE-1)/2
+ 1) mod RANGE;
SUBSET_INDEX:=1;
if (SET(I)-ORIGIN_VALUE) mod RANGE) < RANGE/2 then
SUBSET(SUBSET_INDEX) :=
(SET(I) - ORIGIN_VALUE) mod RANGE;
SUBSET_INDEX := SUBSET_INDEX + 1;
end if;
end loop;
ENCODE_SUBTREE(
INDEX := INDEX +
GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX),
SET := SUBSET,
RANGE := RANGE/2);
end;
Then the right subset:
declare
SUBSET : SET_OF_VALUE(1..(SETSIZE-1)/2);
SUBSET_INDEX : INTEGER;
ORIGIN_VALUE : INTEGER;
begin
ORIGIN_VALUE := (SET(INDEX_IN_SET] + 1) mod RANGE;
SUBSET_INDEX:=1;
if (SET(I)-ORIGIN_VALUE) mod RANGE) < RANGE/2 then
SUBSET(SUBSET_INDEX) :=
(SET(I) - ORIGIN_VALUE) mod RANGE;
SUBSET_INDEX := SUBSET_INDEX + 1;
end if;
end loop;
ENCODE_SUBTREE(
INDEX := INDEX +
2*GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX),
SET := SUBSET,
RANGE := (RANGE-1)/2);
end;
end ENCODE_SUBTREE;
The initial call of the procedure depends on the format. Given some set to encode, the first problem is to verify that it
can be encoded, and by so doing to choose the format.
ETSI
First the encoding process must find the minimum range of the set, that is to say the minimum value R such that there
exists one frequency F
0
in the set such that all frequencies in the set can be written (F
0
+ N) mod 1024, with some N, 0
= N = R-1. The choice of the format depends on R and the number of frequencies : the 512 range format can be chosen
only if R512, the 256 range format can be chosen only if R=256, the 128 range format can be chosen only if R128.
If the chosen format is "1024 range", then the program must first check if frequency 0 is in the set. If so the F0 subfield
is set to 1, and frequency 0 is removed from the set. Otherwise, the F0 subfield is set to 0. Then ENCODE_SUBTREE is
called with INDEX := 1, SET set to the set of values equal to the ARFCN of all frequencies minus 1, and RANGE :=
1023.
If the chosen format is "512 range", "256 range" or "128 range", F
0
is chosen as ORIG-ARFCN and
ENCODE_SUBTREE is called with INDEX := 1, SET set to the set of values equal to the ARFCN of all frequencies
except F
0
, minus F
0
+1, and RANGE set respectively to 511, 255 or 127.
J.5 Decoding
The decoding algorithm, as given below, is the inverse transform of the program given in the previous section, for the
specific case where the original range is a power of 2 minus 1. It is given a set of integer values W(i), and an original
range R, and it builds a set of values from 0..R-1.
The program is here written so that the fact that it is the inverse of the encoding program needs no more proof.
procedure DECODE(in W : array <> of INTEGER;
out SET : SET_OF_VALUE;
in ORIGINAL_RANGE : INTEGER);
-- local variables
INDEX : 1..W'SIZE; RANGE : INTEGER;
N : INTEGER;
begin
for K in 1..W'SIZE loop
The next loop follows the tree from child to parent, from the node of index K to the root (index 1). For each iteration the
node of index INDEX is tackled. The corresponding range is RANGE, and N is the value of the element in the range
defined by the node.
The data are set to their initial values :
INDEX := K;
RANGE := ORIGINAL_RANGE / GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX);
N := W(INDEX) - 1;
while INDEX>1 loop
Due to the assumption that the original range is a power of two minus one, the range for the parent node can be easily
computed, and does not depend upon whether the current node is a left or right child :
RANGE := 2*RANGE + 1;
Let us note J := 2
g-1
, g being the generation of node INDEX. We have J =
GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX). The numbering used in the tree is such that the nodes
of index J to J + J/2 - 1 are left children, and the nodes of index J/2 to J+J-1 are right children. Hence an easy test to
distinguish left and right children:
if 2*INDEX <
3*GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX)
then -- left child
The next computation gives the index of the parent node of the node of index INDEX, for a left child :
ETSI
INDEX := INDEX -
GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX)/2;
The next formula is the inverse of the renumbering appearing in the encoding for a left child. It gives the value of the
parent node in the range defined by the grand-parent node:
N := (N + W(INDEX) - 1 + (RANGE-1)/2 + 1)
mod RANGE;
else -- right child
The next computation gives the index of the parent node of the node of index INDEX, for a right child :
INDEX := INDEX - GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX);
The next formula is the inverse of the renumbering appearing in the encoding for a right child:
N := (N + W(INDEX) - 1 + 1) mod RANGE;
end if;
end loop;
F(K) := N;
end loop;
end;
A careful study will show that the programs given in the main part of the Technical Specification are equivalent to the
one presented here. The main difference is the use of different remnant variables to remove most of the calls to the
function giving the greatest power of 2 less than or equal to some integer.
The decoding must be terminated by the correction specific to the format.
J.6 A detailed example
Let us take the following subset of 16 elements of the set [0..1023] : [13, 71, 122, 191, 251, 321, 402, 476, 521, 575,
635, 701, 765, 831, 906, 981]
Range 1024 format will be used. Frequency 0 is not in the set, thus field F0 is set to 0. The set is renumbered, so as to
give a subset of 0..1022 : [12, 70, 121, 190, 250, 320, 401, 475, 520, 574, 634, 700, 764, 830, 905, 980].
For the first node (corresponding to W(1)), the value 121 satisfies the requirements. The opposite value is 121 + 511 =
632. There are 8 values between 633 and 120 (namely the left-hand subset 634, 700, 764, 830, 905, 980, 12 and 70),
and 7 values between 122 and 632 (namely the right-hand subset 190, 250, 320, 401, 475, 520 and 574).
The encoded value W(1) is 121 + 1, i.e. 122.
The second node (corresponding to W(2)) is the left-hand child of the first node. The corresponding subtree has to
encode for the left-hand subset, renumbered beginning at 633. This gives the following 8 element subset of 0..510,
ordered as resulting from the example of algorithm : [402, 460, 1, 67, 131, 197, 272, 347]. Out of these values, 1 splits
the set in 4 and 3, and the encoded value W(2) is 2.
Similarly, the third node (W(3)) is the right-hand child of the first node and then the corresponding subtree encodes for
the right-hand subset, renumbered starting at 122. This gives the following set of 0..510 : [68, 128, 198, 279, 353, 398,
452]. Out of these values, 68 splits the set into 3 and 3, and the encoded value W(3) is 69.
The same method is applied for all nodes, giving the following encoded values per node:
node value node value
1 122 9 83
2 2 10 3
3 69 11 24
4 204 12 67
5 75 13 54
6 66 14 64
ETSI
7 60 15 70
8 70 16 9
The encoding then consists in formatting, in that order :
122 on 10 bits, then 2 and 69 on 9 bits each, then 204, 75, 66 and 60 on 8 bits each, then 70, 83, 3, 24, 67, 54,
64 and 70 on 7 bits each, and finally 9 on 6 bits.
Conversely the decoding can be done easily. For instance for node 2, the original value is:
(122 - 512 + 2) smod 1023 = 635
For node 14, we have as original value:
(122 - 512 + (2 + (66 + 64)smod 255)smod 511)smod 1023 = 765
ETSI
Annex K (informative):
Default Codings of Information Elements
The information in this annex does NOT define the value of any IEI for any particular message. This annex exists to aid
the design of new messages, in particular with regard to backward compatibility with phase 1 mobile stations.
K.1 Common information elements
For the common information elements types listed below, the default coding of information element identifier bits is
summarized in table K.1/GSM 04.08.
Table K.1/GSM 04.08: Default information element identifier coding
for common information elements
Reference
section
8 7 6 5 4 3 2 1

1 : : : - - - - Type 1 info
elements

1 1 1 1 - - - - Note 1

0 : : : : : : : Type 3 & 4 info
elements

0 0 0 1 0 0 0 1 Note 1
0 0 0 1 0 0 1 1 Location Area
Identification 10.5.1.3
0 0 0 1 0 1 1 1 Mobile Identity 10.5.1.4
0 0 0 1 1 0 0 0 Note 1
0 0 0 1 1 1 1 1 Note 1
0 0 1 0 0 0 0 0 Mobile Station 10.5.1.7
classmark 3

Spare Half Octet 10.5.1.8
NOTE 1: These values were allocated but never used in earlier phases of the protocol.
NOTE 2: For GPRS common information elements no default values are defined:
K.2 Radio Resource management information elements
For the Radio Resource management information elements listed below, the default coding of the information element
identifier bits is summarized in table K.2/GSM 04.08.
ETSI
Table K.2/GSM 04.08 (page 1 of 2): Default information element identifier coding for
Radio Resource management information elements
Reference
section

8 7 6 5 4 3 2 1

1 : : : - - - - Type 1 info
elements
1 0 0 1 - - - - Cipher Mode Setting 10.5.2.9
1 0 1 0 - - - - Cipher Response 10.5.2.10
1 0 1 1 - - - - Note
1 1 0 1 - - - - Synchronization 10.5.2.39
Indication
1 1 1 0 - - - - Channel Needed 10.5.2.8
0 : : : : : : : Type 3 & 4 info
elements
0 0 0 0 0 0 1 0 Frequency Short 10.5.2.14
List
0 0 0 0 0 1 0 1 Frequency List 10.5.2.13
0 1 1 0 0 0 0 1 Note
0 1 1 0 0 0 1 0 Cell Channel 10.5.2.1b
Description
0 1 1 0 0 0 1 1 Channel Mode 10.5.2.6
0 1 1 0 0 1 0 0 Channel Descrip- 10.5.2.5
tion
0 1 1 0 0 1 1 0 Channel Mode 2 10.5.2.7
0 1 1 0 1 0 0 0 Note
0 1 1 0 1 0 0 1 Frequency Chan- 10.5.2.12
nel Sequence
0 1 1 0 1 0 1 0 Note
0 1 1 0 1 0 1 1 Note
0 1 1 0 1 1 0 0 Note
Table K.2/GSM 04.08 (page 2 of 2): Default information element identifier coding for Radio Resource
management information elements
Reference
section
8 7 6 5 4 3 2 1
0 1 1 1 0 0 0 1 Note
0 1 1 1 0 0 1 0 Mobile Allocation 10.5.2.21
0 1 1 1 0 0 1 1 BA range 10.5.2.1
0 1 1 1 0 1 0 0 Note
0 1 1 1 0 1 0 1 Note
0 1 1 1 0 1 1 0 Note
0 1 1 1 0 1 1 1 Mobile Time difference 10.5.2.21a
0 1 1 1 1 0 0 0 Note
0 1 1 1 1 0 0 1 Note
0 1 1 1 1 0 1 0 Note
0 1 1 1 1 0 1 1 Time Difference 10.5.2.41
0 1 1 1 1 1 0 0 Starting Time 10.5.2.38
0 1 1 1 1 1 0 1 Timing Advance 10.5.2.40
0 1 1 1 1 1 1 0 TMSI 10.5.2.42
0 1 1 1 1 1 1 1 Note
NOTE: These values were allocated but never used in earlier phases of the protocol.
ETSI
K.3 Mobility management information elements
For the mobility management information elements listed below, the default coding of the information element identifier
bits is summarized in table K.3/GSM 04.08.
Table K.3/GSM 04.08: Default information element identifier coding for mobility management
information elements
Reference
Section
8 7 6 5 4 3 2 1
Type 1 info elements
1 0 0 1 - - - -Note
1 1 0 0 - - - -Note
1 1 1 0 - - - -Note
1 0 1 0 - - - -Type 2 info elements
0 0 0 1Follow-on Proceed 10.5.3.7
0 0 1 0CTS Permission 10.5.3.10
Type 3 & 4 info elements
0 1 0 0 0 0 0 1Note
0 1 0 0 0 0 1 0Note
0 1 0 0 0 1 0 0Note
NOTE: These values were allocated but never used in earlier versions of the protocol
K.4 Call control information elements.
For the call control information elements listed below, the default coding of the information element identifiers is
defined in table K.4/GSM 04.08.
ETSI
Table K.4/GSM 04.08: Default information element identifier coding for call control information
elements
+-------------------------------------------------+
Reference
section

+--------------------------------------+----------
8 7 6 5 4 3 2 1
1 : : : - - - - Type 1 info elements
0 0 1 - - - - shift 10.5.4.2
and .3
0 1 1 - - - - Note
1 0 1 - - - - Repeat indicator 10.5.4.22

1 0 1 0 : : : : Type 2 information
elements
0 0 0 0 More data 10.5.4.19
0 0 0 1 CLIR Suppression 10.5.4.11a
0 0 1 0 CLIR Invocation 10.5.4.11b
0 0 1 1 Reverse call setup 10.5.4.22a
direction

0 : : : : : : : Type 3 & 4 info
elements
0 0 0 0 1 0 0 Bearer capability 10.5.4.5
0 0 0 1 0 0 0 Cause 10.5.4.11
0 0 1 0 1 0 0 Note
0 0 1 0 1 0 1 Call Control 10.5.4.5a
Capabilities
0 0 1 1 1 0 0 Facility 10.5.4.15
0 0 1 1 1 1 0 Progress indicator 10.5.4.21
0 1 0 0 1 0 0 Auxiliary states 10.5.4.4
0 1 0 0 1 1 1 Note
0 1 0 1 1 0 0 Keypad facility 10.5.4.17
0 1 1 0 1 0 0 Signal 10.5.4.23
1 0 0 1 1 0 0 Connected number 10.5.4.13
1 0 0 1 1 0 1 Connected subaddress 10.5.4.14
1 0 1 1 1 0 0 Calling party BCD
number 10.5.4.9
1 0 1 1 1 0 1 Calling party subad 10.5.4.10
1 0 1 1 1 1 0 Called party BCD
number 10.5.4.7
1 1 0 1 1 0 1 Called party subad 10.5.4.8
1 1 1 0 1 0 0 Redirecting Party BCD 10.5.4.21a
1 1 1 1 1 0 1 Redirecting Party
subaddress 10.5.4.21b
1 1 1 1 1 0 0 Low layer compatib. 10.5.4.18
1 1 1 1 1 0 1 High layer compatib. 10.5.4.16
1 1 1 1 1 1 0 User-user 10.5.4.25
1 1 1 1 1 1 1 SS version indicator 10.5.4.24
+-------------------------------------------------+
NOTE: These values were allocated but never used in earlier phases of the protocol.
ETSI
Annex M (normative):
Additional Requirements for backward compatibility with
PCS 1900 for NA revision 0 ME
This annex is normative and provides additional requirements to support network mechanisms for backward
compatibility with PCS 1900 for NA revision 0 mobile equipments (applicable until July 1, 1998).
PCS 1900 for NA revision 0 mobile equipments are defined to understand Mobile Network Codes made of up to 2
digits. However federal regulation mandates that a 3-digit MNC shall be allocated by each administration to network
operators. Therefore each network operator is identified by a 3-digit Mobile Country Code and a 3-digit Mobile
Network Code. An operator whose network code complies to the allocation principle specified for PCS 1900 for NA
and wants to achieve for a transition period of time the backward compatibility with PCS 1900 for NA revision 0 mobile
equipments shall apply the following:
- The network shall send over the air interface the 3-digit Mobile Country Code and only the two most significant
digits of the Mobile Network Code (the value of the digit sent instead of the 3rd digit is specified in GSM
04.08, section 10.5.1.3) (see Note).
When a PCS 1900 for NA (revision greater than 0) mobile equipment recognizes over the air the Mobile Country Code
and the two most significant digits of the Mobile Network Code as being the HPLMN codes of the current IMSI, the
mobile equipment shall take into account the value of the sixth IMSI digit read from the SIM. If this value matches to a
value contained in the limited set of values for the least significant MNC digit assigned by the number administration
bodies for PCS 1900 for NA then the following applies for the mobile equipment:
- The value sent over the air instead of the 3rd MNC digit in the Location Area Identification (for coding see GSM
04.08, section 10.5.1.3) shall be interpreted as the value of the sixth IMSI digit read from the SIM.
NOTE:
It is still a network operator option to apply this requirement after July 1, 1998. However, in this case the
following shall be considered:
1. Network selection considerations for overlapping networks:
Networks overlapping to the HPLMN, identified over the radio interface by an identical combination
MCC1 MCC2 MCC3 MNC1 MNC2 (possible after July 1, 1998) may be selectable by PCS 1900 for NA
mobile equipments revision 0 with the same priority as the HPLMN or presented to the user as the
HPLMN
2. Roaming considerations:
Roamers (SIM) from networks identified by an identical combination MCC1 MCC2 MCC3 MNC1
MNC2 (possible after July 1, 1998) when roaming into the operator network with PCS 1900 for NA
mobile equipments revision 0, may cause these equipments to exhibit an unpredictable behaviour (e.g.
looping in the HPLMN selection and registration procedures).
Home subscribers (SIM) roaming with PCS 1900 for NA mobile equipments revision 0 into networks
identified by an identical combination MCC1 MCC2 MCC3 MNC1 MNC2 (possible after July 1, 1998),
may consider being attached to the HPLMN.
ETSI
Annex N (informative):
Change Record
Creation of v 7.0.1
Based on v6.3.0 including CRs A384, A396r2, A412, A457r1, A427r2, A495, A493
Creation of v 7.1.0
A358 8 Addition of SoLSA functionality
A414 1 Addition of new functionality in the packet access procedure in order to
A419 5 Transfer of the LSA Information to the MS
A460 Cell Channel Description IE incorrectly repeated in the PDCH ASSI
A464 Channel description IE
A466 Radio link failure in dedicated mode
A468 RR-Network command cell change order procedure
A484 Clarification on the RR initialisation request
A486 Correction of message type of PDCH ASSIGNMENT COMMAND
A488 Removal of REL_OR_ABS_FN field for Starting Time encoding by a
A490 P-TMSI is introduced in the Paging request messages and in the Mobile
A494 The Pb parameter is needed in SI13/PSI13 (R98)
A496 Removal of SI15
A498 Increase of SMS_VALUE and SM_VALUE
A502 2 Correction for L2 Pseudo length SI5 & SI6 rest octets
A504 1 Addition of signalling for SoLSA enhancements
A506 Read of system information after CELL CHANGE ORDER message
A534 Correction of VGCS target mode indication IE
A540 P-TMSI is introduced in the Paging request messages and in the Mobile
A542 Clarification of Packet Page Indication
A546 2 Inclusion of SoLSA capability indication in Classmark Ies
A546 2 Inclusion of SoLSA capability indication in Classmark IEs
A548 Wrong application of approved CR on NOTIFICATION/NCH
A552 1 Correction of BTS power output
A558 2 Introduction of LCS in GSM 04.08
A578 AMR IEI
A584 3 MS radio access capability IE
A584 3 MS Radio Access Capability IE
A591 Inconsistency in definition of comprehension required
A594 Role of T3132 and T3190 timers during a TBF release procedure
A598 Alignment 04.60 on 04.08 about single block allocation for a two phase
A600 Clarification on supervision of BCCH_CHANGE_MARK in dedicated
A602 Introduction of P-TMSI in Paging request messages in the MS
A604 Correction of T3142 timeout value
A606 RR Packet Uplink Assignment align with 04.60
A701 1 GPRS Internet Hosted Octet Stream Service (IHOSS).
A751 3 Usage of the combined routing area update procedure
A753 2 Multiple ATTACH REQUEST attempts and GMM-common procedures
A755 2 Network Initiated Detach with ReAttach
A757 2 P-TMSI is introduced in the Paging request messages and in the Mobile
A759 1 Improving the user data loss less inter SGSN RA update
A761 GPRS services not allowedcause in the ATTACH REJECT (combined
A763 1 Clarification to CCBS T334 timer
A765 1 SM-STATUS msg. Response to unknown msg type
A767 2 Cleaning up on text in general, and especially on attempt counters, PDP
A769 4 Correction to the handling of subscribed QoS values
A771 2 Correction of the handling of the Ciphering Key Sequence Number (CKSN)
A773 3 Correction of the SM message collision with equal TI to an active PDP
A775 2 Ready Timer handling in suspend state
ETSI
A777 Deactivation of READY timer
A779 1 Description of cause codes in network initiated detach
A781 1 Clarification of release procedure upon PDP context deactivation
A783 2 New DEREGISTERED suspendedstate
A785 1 Inconsistency in definition of comprehension required IEs
A787 1 Completion of error handling for session management
A789 2 Subsequent GMM substate and attach attempt counter
A791 Usage of GMM cause codes
A793 4 Old P-TMSI/TLLI handling
A797 2 Gs interface failure
A799 1 GPRS services and non-GPRS services not allowed: the behaviour of the
A801 1 Maximum length of Access point name and Protocol configuration
A803 1 Clash between READY time deactivation and Force to Standby Procedure
A805 GMM Mobile station identity
A807 3 Initial synchronisation after READY timer negotiation
A809 2 Usage of GMM update status U2
A811 Conditional IE GPRS CKSN in Authentication and ciphering procedure
A813 Correction of the SM message collision cases through PDP address
A815 4 Paging with IMSI
A817 2 Reactivation of PDP contexts
A819 Correcting mistakes introduced via CRs 385, 415, 425,441 in v6.3.0
A821 1 Editorials, and correcting the A&C REQUEST plus INFORMATION
A823 MS reachable timer
A825 Correction of PDP type
A827 Conditional IE Errors
A829 4 Change of network operation mode
A831 Abnormal case in the MS when changing cell while trying to attach
A833 Definition of the PDP address IE
A835 Deactivation of PDP contexts in case of GPRS detach
A837 Improved SM messages error handling for non-semantically mandatory IE
A839 Usage of cause code #10 implicitly detached
A841 1 TMSI requested by the MSC trough the Gs interface
A371 2 BCIE modifications due to EDGE
Creation of v 7.1.1 Editorial correction to remove unnecessary double Spare Half Octets from section 9.4.9.
Version 7.1.2 Editorial corrections of Table 10.5.144/GSM04.08 the bit-string " Receive N-PDU Number value "
Creation of v 7.2.0
A620 Correction of Mobile Station Classmark 2 in the Talker Indication message
A622 1 Clarification of MCC and MNC in SI 4/16/17 rest octets
A626 1 Alignment on 04.60 of information elements RR Packet Uplink and Downlink Assignment
A632 Length of BA List Pref IE in the Channel Release message
A636 Clarification of DRX
A640 1 Alignment of RLC_OCTET_COUNT in 04.08 with 04.60
A644 System information type 14 and 15
A648 1 Introduction of short LSA ID.
A652 1 New coding of SI 4/7/8 Rest Octets.
A658 Correction to handling of GPRS suspension cause
A662 2 Alignment between 04.08 and 04.60 on the packet access procedure attempt following T3142 or
T3172 attempt
A664 Addition of 3rd MNC digit in Routing Area Identification and correction of LAI
A666 Addition of new SI type in SI 9 Rest Octets.
A670 1 Addition of PR mode in ASSIGNMENT message in 04.08
A843 Addition of 3rd MNC digit in Routing Area Identification and correction of LAI
A847 GMM attempt counters
A851 Cell Change during GPRS Detach procedure
A855 RA change in GMM-ROUTING-AREA-UPDATE-INITIATED
A937 Non power down caused Detach during Attach/ was approve as A859-collision with other CR
A860r1 CM request and combined GMM procedures
ETSI
A863 "Receive N-PDU Number list" IE padding bits
A867r1 TMSI status indication
A875 PDP context deactivation caused by LLC failure
A887 RAU Complete not returned for TMSI deallocation. Some alignments and editorials
A894 Clarification of the Detach Type "re-attach required" or "re-attach not required" in the network
initiated Detach procedure
A901r1 CR clash in sec. 4.7.3.2.6
A905 CR clash in sec. 4.7.3.2.3.2 and 4.7.5.2.3.2
A909r1 T3212 restart after RAU reject
A913 New State GMM-REGISTERED.IMSI-DETACH-INITIATED
A917 Deactivate AA PDP context request message
A921r2 Coding Scheme in Network Name IE
A933 T3212 restart after GPRS detach
A897r1 Addition of Access Point Name in Request PDP Context Activation message
Creation of version 7.3.0
A684 Editorial (misleading reference)
A694 Correction to Packet Access Reject procedure
A939 1 Addition of APN to REQUEST PDP CONTEXT ACTIVATION REJECT message
A676 4 Add enhancements to LCS in GSM 04.08
A version of 7.5.0 have been available in draft format, with severere corruption of tables. This version 7.5.1 replaces
that version.
A612 Immediate assignment
A674 PR_MODE field in assignment message
A676 Intorduction of LCS into GSM 04.08
A688 Channel Request Description IE length and Packet
A706 Clarification of starting timer T3134
A714 Suspension Cause IE
A641r1 Earlier implementation corrected.
Creation of version 7.6.0: Approval at TSGN#7, (changes based on v.7.4.0)
A955 Removal of APN from REQUEST PDP CONTEXT ACTIVATION REJECT message
A951r1 Clarification of NITZ time stamp coding
A959r1 Corrections to SN-PDU IE length in GMM messages
A963r1 Interpretation of CM service reject in MS supporting GPRS services
A975r1 Clarification to the MS handling when receiving detach type IMSI detach
A987 Explanation of octets in MS Classmark 1 IE
A1005 Addition of cause value # 25 Pre-emption
A1007 GPRS detach type corrections
A1013 Moving NOTIFICATION RESPONSE from MM to GSM RR
Createion of version 7.7.0: Approval at SMG#31bis
A722 The break indicator in SI 4 Rest Octets is currently coded as 0 | 1. In order to support the
combination of new mobile stations and old networks, the break indicator has to be coded as L | H.
A720 Moving NOTIFICATION RESPONSE from MM to GSM RR
ETSI
History
Document history
V7.1.2 August 1999 One step Approval Procedure OAP 9954:
V7.2.0 November 1999
V7.3.0 December 1999
V7.4.0 December 1999 Approved at TSGN#6
V7.5.1 March 2000 Implemented CRs approved at SMG31. Corrects corrupted tables in annexes and
includes the CR history table that was originally lost.
V7.6.0 March 2000 TSGN#7 approval of Crs

ETSI EN 300 940: Draft V7.7.0

Uploaded by

Copyright:

Available Formats

ETSI EN 300 940: Draft V7.7.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ETSI EN 300 940: Draft V7.7.0

Uploaded by

Copyright:

Available Formats

draft ETSI EN 300 940 V7.7.

Mobile Station Network

You might also like