SIST ETS 300 940 E7:2005
(Main)Digital cellular telecommunications system (Phase 2+) (GSM); Mobile radio interface; Layer 3 specification (GSM 04.08 version 5.13.1 Release 1996)
- Abstract
SUBJECT Clarification of the classmark 3 IE
- Status
- Published
- Publication Date
- 31-Jan-2005
- Technical Committee
- RES - Radio equipment and systems
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Feb-2005
- Due Date
- 01-Feb-2005
- Completion Date
- 01-Feb-2005
SIST ETS 300 940 E7:2005 is the Slovenian standard identical to ETS 300 940 Edition 7 from ETSI. It specifies GSM Layer 3 procedures on the Um radio interface for radio resource management, mobility management, and circuit-switched call control. It is written for implementers and testers of GSM mobile stations and network equipment, including cases that use classmark procedures and the Mobile Station Classmark 3 information element.
What does SIST ETS 300 940 E7:2005 specify?
SIST ETS 300 940 E7:2005 specifies the Layer 3 procedures used at the GSM radio interface reference point Um. Clause 0 says the document covers call control, mobility management, and radio resource management, and that GSM 04.10 and GSM 04.11 cover supplementary services and point-to-point short message services.
The document is organized into clauses 0 to 11, followed by annexes. Clause 3 covers Radio Resource management procedures, clause 4 covers Mobility Management, clause 5 covers circuit-switched Call Control, clause 6 covers support of packet services, clause 7 gives non-normative examples, clause 8 handles unknown and erroneous protocol data, clause 9 defines message contents, clause 10 defines general formats and coding, and clause 11 lists timers and counters.
| Annex | What it covers |
|---|---|
| Annex A | Example of subaddress information element coding |
| Annex B | Compatibility checking |
| Annex C | Low layer information coding principles |
| Annex H | GSM specific cause values for call control |
| Annex K | Default codings of information elements |
| Annex L | Change Record |
What are the key requirements of SIST ETS 300 940 E7:2005?
Clause 0 sets the framework: the Layer 3 procedures apply to the interface structures defined in GSM 04.03, and they use services from layer 2 as defined in GSM 04.05 and GSM 04.06. The document also says it uses a building-block method, with elementary procedures defined for the radio resource management, mobility management, and connection management sublayers. In practice, this means implementers can map each signalling function to a named procedure and verify it against the right lower-layer services.
Radio Resource management
Clause 3 defines how the mobile station and network behave in idle mode, dedicated mode, group receive mode, and group transmit mode. It covers system information broadcasting, paging, RR connection establishment, service request and contention resolution, and the transitions into dedicated or group modes. For a practical implementation, this is the part that drives channel access, paging response, and the handover of signalling between control channels and dedicated channels.
Clause 3 also covers the procedures used once a connection exists, including SACCH measurement reports, channel assignment, handover, frequency redefinition, channel mode modify, ciphering mode setting, additional channel assignment, partial channel release, classmark change, classmark interrogation, configuration change, and mapping of user data substreams onto timeslots in a multislot configuration. It also includes handling of classmark information at band change. These procedures matter because they control how a call or signalling connection is maintained, reconfigured, and recovered when conditions change.
The group transmit and group receive procedures are only applicable to mobile stations that support VGCS talking or VGCS/VBS listening, respectively. That limitation matters in practice because a device should only implement those procedures if it supports the related voice group call or voice broadcast functions.
Mobility Management
Clause 4 defines the MM sublayer states and the behaviour in MM IDLE state. The text distinguishes service states such as NORMAL SERVICE, ATTEMPTING TO UPDATE, LIMITED SERVICE, NO IMSI, SEARCH FOR PLMN, and the group-call reception states. In practice, this is the logic that decides whether the mobile station can offer normal service, only emergency service, or no service at all.
Clause 4 also defines the MM common procedures: TMSI reallocation, authentication, identification, IMSI detach, abort, and MM information. These procedures are central to subscriber identity handling and registration control, so they affect how the network confirms identity, updates temporary identities, and informs the mobile station.
Clause 4.4 adds MM specific procedures, including location updating, periodic updating, IMSI attach, and generic location updating. The generic procedure includes network requests for additional mobile station capability information, identification, authentication, ciphering mode setting, an attempt counter, and accept or reject outcomes. A key rule is that a MM specific procedure can only start when no other MM specific procedure is running or when no MM connection exists, which prevents overlapping registration actions.
Clause 4.5 introduces the concept of an MM connection for carrying CM messages. It covers MM connection establishment initiated by the mobile station or the network, emergency calls, call re-establishment, forced release during MO MM connection establishment, MM connection information transfer, and MM connection release. This matters because it is the bridge between mobility handling and call control signalling.
Call Control and packet services
Clause 5 defines the circuit-switched Call Control state machines on both the mobile station side and the network side. It covers call establishment, mobile originating and mobile terminating call setup, network-initiated MO call for CCBS, active-state signalling, Dual Services, user initiated service level up- and downgrading, call clearing, status procedures, call re-establishment, progress handling, and DTMF protocol control. For implementers, this clause is the core call signalling state machine.
Clause 5 says call establishment consists of both the CC connection and activation of the codec or interworking function. That is important because a call is not complete until signalling and bearer handling are both in place.
Clause 6 says the circuit-switched Call Control procedures of clause 5 also apply to packet services. In practice, that tells the reader that the same CC procedure framework is reused in that case.
Error handling, coding, and timers
Clause 8 defines how to handle messages that are too short, have unknown or unforeseen transaction identifiers, unknown message types, missing or incorrect mandatory information elements, incorrect optional or conditional information elements, or semantically incorrect contents. This clause is the interoperability safety net: it tells implementations when to ignore, reject, or otherwise react to malformed protocol data.
Clauses 9 and 10 define the message functions, contents, general message format, and information element coding for RR, MM, and CC. Clause 11 then lists the timers and counters used by the procedures. Together, these clauses are what implementers use to build, encode, decode, and time the signalling correctly.
What terms does SIST ETS 300 940 E7:2005 define?
- idle mode - The mobile station is not allocated a dedicated channel and listens to the CCCH and BCCH.
- group receive mode - This mode applies to mobile stations that support VGCS listening or VBS listening and are receiving a group call.
- group transmit mode - This mode applies to mobile stations that support VGCS talking and are transmitting in a group call.
- MM IDLE state - No MM procedure is running and no RR connection exists.
- NORMAL SERVICE - Valid subscriber data are available, and the selected cell belongs to the location area where the subscriber is registered.
- LIMITED SERVICE - Valid subscriber data are available, but the mobile station can offer only emergency services.
- NO IMSI - No valid subscriber data are available, so only emergency services are offered.
- TMSI - The temporary identity handled by the TMSI reallocation procedure to support subscriber identity confidentiality.
Who uses SIST ETS 300 940 E7:2005?
SIST ETS 300 940 E7:2005 is used by GSM mobile station designers, network equipment vendors, and protocol engineers who implement Layer 3 signalling at the radio interface. It is also used by test laboratories and acceptance teams that need to verify paging, location updating, handover, call setup, ciphering, and error handling on real implementations.
Quality managers, system integrators, and technical buyers use it to check that a product supports the GSM Phase 2+ procedures it claims to support. It is especially relevant when comparing behaviour for normal service, limited service, group call support, and classmark handling.
What changed in SIST ETS 300 940 E7:2005 from the previous edition?
SIST ETS 300 940 E7:2005 corresponds to ETS 300 940 Edition 7. The document presents itself as the seventh edition and includes a Change Record in Annex L.
Which standards are used with SIST ETS 300 940 E7:2005?
| Standard | What it contributes |
|---|---|
| GSM 04.02 | Reference point Um context |
| GSM 04.03 | Interface structures to which Layer 3 procedures apply |
| GSM 04.05 | Layer 2 functions and services used by Layer 3 |
| GSM 04.06 | Layer 2 functions and services used by Layer 3 |
| GSM 04.07 | General description of Layer 3, procedure description, message format, and error handling |
| GSM 04.10 | Functional procedures for supplementary services |
| GSM 04.11 | Functional procedures for point-to-point short message services |
| GSM 05.02 | Logical control channels |
| GSM 11.10 | GSM radio interface signalling test procedures |
| GSM 11.2x | GSM radio interface signalling test procedures |
| GSM 01.04 | Abbreviations used in the specification |
What does the SIST ETS 300 940 E7:2005 document contain?
The document contains the procedure descriptions that drive GSM Layer 3 signalling on the radio interface, including state behaviour, message sequences, abnormal cases, and interworking between RR, MM, and CC. Section 7 gives worked examples of structured procedures such as paging, immediate assignment, service request and contention resolution, authentication, ciphering mode setting, transaction phase, channel release, location updating, mobile originating and mobile terminating call establishment, call clearing, DTMF protocol control, handover, in-call modification, call re-establishment, and CCBS.
Section 9 contains detailed message definitions for RR, MM, and CC, with tables that identify which information elements each message uses and how they are marked as mandatory, optional, or conditional. Section 10 then gives the general message format and coding rules for protocol discriminator, transaction identifier, message type, and the information elements used across the three sublayers.
The annexes add implementation support rather than new signalling flows. Annex B covers compatibility checking, Annex C gives low layer coding principles, Annex A gives an example of subaddress coding, Annex K lists default codings of information elements, and Annex L records the changes. This makes the document useful both for implementation and for interoperability testing, because it combines procedure logic with coding detail.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST ETS 300 940 E7:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital cellular telecommunications system (Phase 2+) (GSM); Mobile radio interface; Layer 3 specification (GSM 04.08 version 5.13.1 Release 1996)". This standard covers: SUBJECT Clarification of the classmark 3 IE
SUBJECT Clarification of the classmark 3 IE
SIST ETS 300 940 E7:2005 is classified under the following ICS (International Classification for Standards) categories: 33.070.01 - Mobile services in general. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST ETS 300 940 E7:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-februar-2005
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D 9PHVQLN]DPRELOQLUDGLR
6SHFLILNDFLMDWUHWMHSODVWL *60UD]OLþLFDL]GDMD
Digital cellular telecommunications system (Phase 2+) (GSM); Mobile radio interface;
Layer 3 specification (GSM 04.08 version 5.13.1 Release 1996)
Ta slovenski standard je istoveten z: ETS 300 940 Edition 7
ICS:
33.070.01 Mobilni servisi na splošno Mobile services in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 940
TELECOMMUNICATION December 1999
STANDARD Seventh Edition
Source: SMG Reference: RE/SMG-030408QR9
ICS: 33.020
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
R
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
Digital cellular telecommunications system (Phase 2+);
Mobile radio interface;
Layer 3 specification
(GSM 04.08 version 5.13.1 Release 1996)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.org
Tel.:+33492944200- Fax:+33493654716
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 1999. All rights reserved.
Page 2
ETS 300 940 (GSM 04.08 version 5.13.1 Release 1996): December 1999
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.
Page 3
ETS 300 940 (GSM 04.08 version 5.13.1 Release 1996): December 1999
Contents
Intellectual Property Rights.21
Foreword.21
Introduction.22
0 Scope .23
0.1 Scope of the Technical Specification.23
0.2 Application to the interface structures.23
0.3 Structure of layer 3 procedures.23
0.4 Test procedures.23
0.5 Use of logical channels .23
0.6 Overview of control procedures .24
0.6.1 List of procedures.24
0.7 Applicability of implementations.25
1 Normative references.26
2 Definitions and abbreviations .30
2.1 Random values .30
2.2 Vocabulary .30
3 Radio Resource management procedures .32
3.1 Overview/General .32
3.1.1 General.32
3.1.2 Services provided to upper layers .32
3.1.2.1 Idle mode.32
3.1.2.2 Dedicated mode.32
3.1.2.3 Group receive mode .33
3.1.2.4 Group transmit mode.33
3.1.3 Services required from data link and physical layers .33
3.1.4 Change of dedicated channels.33
3.1.4.1 Change of dedicated channels using SAPI = 0 .33
3.1.4.2 Change of dedicated channels using other SAPIs than 0 .34
3.1.4.3 Sequenced message transfer operation.34
3.1.4.3.1 Variables and sequence numbers .34
3.1.4.3.2 Procedures for the initiation, transfer
execution and termination of the
sequenced message transfer
operation .35
3.1.5 Procedure for Service Request and Contention Resolution.35
3.2 Idle mode procedures .36
3.2.1 Mobile Station side .36
3.2.2 Network side.36
3.2.2.1 System information broadcasting .36
3.2.2.2 Paging.37
3.3 RR connection establishment .37
3.3.1 RR connection establishment initiated by the mobile station .37
3.3.1.1 Entering the dedicated mode : immediate assignment
procedure.37
3.3.1.1.1 Permission to access the network .37
3.3.1.1.2 Initiation of the immediate assignment
procedure.38
3.3.1.1.3 Answer from the network .39
3.3.1.1.4 Assignment completion.40
3.3.1.1.5 Abnormal cases .41
Page 4
ETS 300 940 (GSM 04.08 version 5.13.1 Release 1996): December 1999
3.3.1.2 Entering the group transmit mode: uplink access
procedure. 41
3.3.1.2.1 Mobile station side. 41
3.3.1.2.2 Network side. 42
3.3.1.2.3 Abnormal cases . 43
3.3.2 Paging procedure. 43
3.3.2.1 Paging initiation by the network. 43
3.3.2.2 Paging response . 44
3.3.2.3 Abnormal cases . 44
3.3.3 Notification procedure. 45
3.3.3.1 Notification of a call. 45
3.3.3.2 Joining a VGCS or VBS call. 45
3.3.3.3 Reduced NCH monitoring mechanism. 46
3.4 Procedures in dedicated mode and in group transmit mode. 47
3.4.1 SACCH procedures . 47
3.4.1.1 General . 47
3.4.1.2 Measurement report. 48
3.4.1.3 Extended measurement report $(MAFA)$. 48
3.4.2 Transfer of messages and link layer service provision. 48
3.4.3 Channel assignment procedure. 49
3.4.3.1 Channel assignment initiation . 49
3.4.3.2 Assignment completion. 51
3.4.3.3 Abnormal cases . 51
3.4.4 Handover procedure . 52
3.4.4.1 Handover initiation. 52
3.4.4.2 Physical channel establishment . 54
3.4.4.2.1 Finely synchronized cell case. 54
3.4.4.2.2 Non synchronized cell case. 54
3.4.4.2.3 Pseudo-synchronized cell case. 55
3.4.4.2.4 Pre-synchronized cell case . 55
3.4.4.3 Handover completion . 55
3.4.4.4 Abnormal cases . 56
3.4.5 Frequency redefinition procedure . 57
3.4.5.1 Abnormal cases . 57
3.4.6 Channel mode modify procedure. 57
3.4.6.1 Normal channel mode modify procedure. 58
3.4.6.1.1 Initiation of the channel mode modify
procedure . 58
3.4.6.1.2 Completion of channel mode modify
procedure . 58
3.4.6.1.3 Abnormal cases . 58
3.4.6.2 Channel mode modify procedure for a voice group call
talker . 58
3.4.6.2.1 Initiation of the channel mode modify
procedure . 58
3.4.6.2.2 Completion of mode change
procedure . 58
3.4.6.2.3 Abnormal cases . 59
3.4.7 Ciphering mode setting procedure. 59
3.4.7.1 Ciphering mode setting initiation . 59
3.4.7.2 Ciphering mode setting completion. 59
3.4.8 Additional channel assignment procedure. 60
3.4.8.1 Additional assignment procedure initiation. 60
3.4.8.2 Additional assignment procedure completion . 60
3.4.8.3 Abnormal cases . 60
3.4.9 Partial channel release procedure . 61
3.4.9.1 Partial release procedure initiation. 61
3.4.9.2 Abnormal cases . 61
3.4.10 Classmark change procedure. 61
3.4.11 Classmark interrogation procedure . 61
3.4.11.1 Classmark interrogation initiation. 61
3.4.11.2 Classmark interrogation completion. 62
3.4.12 Indication of notifications and paging informations. 62
Page 5
ETS 300 940 (GSM 04.08 version 5.13.1 Release 1996): December 1999
3.4.13 RR connection release procedure.63
3.4.13.1 Normal release procedure .63
3.4.13.1.1 Channel release procedure initiation in
dedicated mode and in group transmit
mode.63
3.4.13.1.2 Abnormal cases .64
3.4.13.2 Radio link failure in dedicated mode.64
3.4.13.2.1 Mobile side.64
3.4.13.2.2 Network side .64
3.4.13.3 RR connection abortion in dedicated mode.64
3.4.13.4 Uplink release procedure in group transmit mode.65
3.4.13.5 Radio link failure in group transmit mode .65
3.4.13.5.1 Mobile side.65
3.4.13.5.2 Network side .65
3.4.14 Receiving a RR STATUS message by a RR entity. .65
3.4.15 Group receive mode procedures.66
3.4.15.1 Mobile station side .66
3.4.15.1.1 Reception of the VGCS or VBS
channel .66
3.4.15.1.2 Monitoring of downlink messages and
related procedures.66
3.4.15.1.3 Uplink reply procedure .67
3.4.15.1.4 Leaving the group receive mode.68
3.4.15.2 Network side.68
3.4.15.2.1 Provision of messages on the VGCS
or VBS channel downlink .68
3.4.15.2.2 Release of the VGCS or VBS
Channels.69
3.4.15.3 Failure cases .69
3.4.16 Configuration change procedure .69
3.4.16.1 Configuration change initiation .70
3.4.16.2 Configuration change completion .70
3.4.16.3 Abnormal cases.70
3.4.17 Mapping of user data substreams onto timeslots in a multislot
configuration.70
3.4.18 Handling of classmark information at band change .71
4 Elementary procedures for Mobility Management.72
4.1 General .72
4.1.1 Type of MM procedures .72
4.1.2 MM sublayer states .73
4.1.2.1 MM sublayer states in the mobile station.73
4.1.2.1.1 Main states.73
4.1.2.1.2 Substates of the MM IDLE state .76
4.1.2.2 The update Status .77
4.1.2.3 MM sublayer states on the network side .78
4.2 Behaviour in MM IDLE State.79
4.2.1 Primary Service State selection.79
4.2.1.1 Selection of the Service State after Power On. .79
4.2.1.2 Other Cases.80
4.2.2 Detailed Description of the MS behaviour in MM IDLE State.80
4.2.2.1 Service State, NORMAL SERVICE .80
4.2.2.2 Service State, ATTEMPTING TO UPDATE .81
4.2.2.3 Service State, LIMITED SERVICE .81
4.2.2.4 Service State, NO IMSI.82
4.2.2.5 Service State, SEARCH FOR PLMN, NORMAL SERVICE.82
4.2.2.6 Service State, SEARCH FOR PLMN.82
4.2.2.7 Service State, RECEIVING GROUP CALL (NORMAL
SERVICE).83
4.2.2.8 Service State, RECEIVING GROUP CALL (LIMITED
SERVICE).83
4.2.3 Service state when back to state MM IDLE from another state .83
4.3 MM common procedures .84
Page 6
ETS 300 940 (GSM 04.08 version 5.13.1 Release 1996): December 1999
4.3.1 TMSI reallocation procedure. 84
4.3.1.1 TMSI reallocation initiation by the network. 85
4.3.1.2 TMSI reallocation completion by the mobile station. 85
4.3.1.3 TMSI reallocation completion in the network. . 85
4.3.1.4 Abnormal cases . 85
4.3.2 Authentication procedure. 87
4.3.2.1 Authentication request by the network . 87
4.3.2.2 Authentication response by the mobile station. 87
4.3.2.3 Authentication processing in the network. 87
4.3.2.4 Ciphering key sequence number . 87
4.3.2.5 Unsuccessful authentication . 88
4.3.2.6 Abnormal cases . 88
4.3.3 Identification procedure . 89
4.3.3.1 Identity request by the network . 89
4.3.3.2 Identification response by the mobile station . 89
4.3.3.3 Abnormal cases . 89
4.3.4 IMSI detach procedure . 89
4.3.4.1 IMSI detach initiation by the mobile station. 89
4.3.4.2 IMSI detach procedure in the network . 90
4.3.4.3 IMSI detach completion by the mobile station. 90
4.3.4.4 Abnormal cases . 90
4.3.5 Abort procedure . 90
4.3.5.1 Abort procedure initiation by the network. 90
4.3.5.2 Abort procedure in the mobile station . 91
4.3.6 MM information procedure. 91
4.3.6.1 MM information procedure initiation by the network. 91
4.3.6.2 MM information procedure in the mobile station . 91
4.4 MM specific procedures . 92
4.4.1 Location updating procedure . 92
4.4.2 Periodic updating . 93
4.4.3 IMSI attach procedure . 93
4.4.4 Generic Location Updating procedure . 94
4.4.4.1 Location updating initiation by the mobile station. 94
4.4.4.1a Network Request for Additional mobile station Capability
Information . 94
4.4.4.2 Identification request from the network . 94
4.4.4.3 Authentication by the network . 94
4.4.4.4 Ciphering mode setting by the network. 94
4.4.4.5 Attempt Counter. 94
4.4.4.6 Location updating accepted by the network. 95
4.4.4.7 Location updating not accepted by the network. 95
4.4.4.8 Release of RR connection after location updating. 96
4.4.4.9 Abnormal cases on the mobile station side . 96
4.4.4.10 Abnormal cases on the network side . 97
4.5 Connection management sublayer service provision. 98
4.5.1 MM connection establishment . 98
4.5.1.1 MM connection establishment initiated by the mobile
station. 98
4.5.1.2 Abnormal cases . 101
4.5.1.3 MM connection establishment initiated by the network. 102
4.5.1.3.1 Mobile Terminating CM Activity. 102
4.5.1.3.2 Mobile Originating CM Activity
$(CCBS)$. 103
4.5.1.4 Abnormal cases . 103
4.5.1.5 MM connection establishment for emergency calls . 103
4.5.1.6 Call re-establishment . 104
4.5.1.6.1 Call re-establishment, initiation by the
mobile station . 105
4.5.1.6.2 Abnormal cases . 106
4.5.1.7 Forced release during MO MM connection establishment 107
4.5.2 MM connection information transfer phase . 107
4.5.2.1 Sending CM messages. 107
4.5.2.2 Receiving CM messages . 108
Page 7
ETS 300 940 (GSM 04.08 version 5.13.1 Release 1996): December 1999
4.5.2.3 Abnormal cases.108
4.5.3 MM connection release .108
4.5.3.1 Release of associated RR connection.108
4.5.3.2 Uplink release in a voice group call .109
4.6 Receiving a MM STATUS message by a MM entity.109
5 Elementary procedures for circuit-switched Call Control.110
5.1 Overview .110
5.1.1 General.110
5.1.2 Call Control States.115
5.1.2.1 Call states at the mobile station side of the interface .115
5.1.2.1.1 Null (State U0) .115
5.1.2.1.2 MM Connection pending (U0.1).115
5.1.2.1.2a CC prompt present (U0.2) $(CCBS)$.115
5.1.2.1.2b Wait for network information (U0.3)
$(CCBS)$.115
5.1.2.1.2c CC-Establishmentpresent (U0.4)
$(CCBS)$.115
5.1.2.1.2d CC-Establishment confirmed (U0.5)
$(CCBS)$.115
5.1.2.1.2e Recall present (U0.6) $(CCBS)$.115
5.1.2.1.3 Call initiated (U1) .115
5.1.2.1.4 Mobile originating call proceeding (U3)115
5.1.2.1.5 Call delivered (U4) .116
5.1.2.1.6 Call present (U6).116
5.1.2.1.7 Call received (U7) .116
5.1.2.1.8 Connect Request (U8) .116
5.1.2.1.9 Mobile terminating call confirmed (U9)116
5.1.2.1.10 Active (U10) .116
5.1.2.1.11 Disconnect request (U11) .116
5.1.2.1.12 Disconnect indication (U12).116
5.1.2.1.13 Release request (U19).116
5.1.2.1.14 Mobile originating modify (U26) .116
5.1.2.1.15 Mobile terminating modify (U27).116
5.1.2.2 Network call states.116
5.1.2.2.1 Null (State N0) .117
5.1.2.2.2 MM connection pending (N0.1).117
5.1.2.2.2a CC connection pending (N0.2)
$(CCBS)$.117
5.1.2.2.2b Network answer pending (N0.3)
$(CCBS)$.117
5.1.2.2.2c CC-Establishment present (N0.4)
$(CCBS)$.117
5.1.2.2.2d CC-Establishment confirmed (N0.5)
$(CCBS)$.117
5.1.2.2.2e Recall present (N0.6) $(CCBS)$.117
5.1.2.2.3 Call initiated (N1) .117
5.1.2.2.4 Mobile originating call proceeding (N3)117
5.1.2.2.5 Call delivered (N4) .117
5.1.2.2.6 Call present (N6).117
5.1.2.2.7 Call received (N7) .117
5.1.2.2.8 Connect request (N8).118
5.1.2.2.9 Mobile terminating call confirmed (N9)118
5.1.2.2.10 Active (N10) .118
5.1.2.2.11 {Not used} .118
5.1.2.2.12 Disconnect indication (N12).118
5.1.2.2.13 Release request (N19).118
5.1.2.2.14 Mobile originating modify (N26) .118
5.1.2.2.15 Mobile terminating modify (N27).118
5.1.2.2.16 Connect Indication (N28) .118
5.2 Call establishment procedures.118
5.2.1 Mobile originating call establishment.119
5.2.1.1 Call initiation.119
Page 8
ETS 300 940 (GSM 04.08 version 5.13.1 Release 1996): December 1999
5.2.1.2 Receipt of a setup message . 120
5.2.1.3 Receipt of a CALL PROCEEDING message. 121
5.2.1.4 Notification of progressing mobile originated call. 121
5.2.1.4.1 Notification of interworking in
connection with mobile originated call
establishment . 121
5.2.1.4.2 Call progress in the PLMN/ISDN
environment. 122
5.2.1.5 Alerting . 122
5.2.1.6 Call connected . 123
5.2.1.7 Call rejection . 123
5.2.1.8 Transit network selection . 123
5.2.1.9 Traffic channel assignment at mobile originating call
establishment. 123
5.2.1.10 Call queuing at mobile originating call establishment . 124
5.2.2 Mobile terminating call establishment. 124
5.2.2.1 Call indication. 124
5.2.2.2 Compatibility checking . 125
5.2.2.3 Call confirmation . 125
5.2.2.3.1 Response to SETUP . 125
5.2.2.3.2 Receipt of CALL CONFIRMED and
ALERTING by the network . 125
5.2.2.3.3 Call failure procedures . 126
5.2.2.3.4 Called mobile station clearing during
mobile terminating call establishment 126
5.2.2.4 Notification of interworking in connection with mobile
terminating call establishment. 126
5.2.2.5 Call accept . 126
5.2.2.6 Active indication . 126
5.2.2.7 Traffic channel assignment at mobile terminating call
establishment. 127
5.2.2.8 Call queuing at mobile terminating call establishment . 127
5.2.2.9 User connection attachment during a mobile terminating
call. 127
5.2.3 Network initiated MO call $(CCBS)$. 127
5.2.3.1 Initiation. 127
5.2.3.2 CC-Establishment present . 128
5.2.3.2.1 Recall Alignment Procedure. 129
5.2.3.3 CC-Establishment confirmation . 130
5.2.3.4 Recall present . 130
5.2.3.5 Traffic channel assignment during network initiated
mobile originating call establishment . 131
5.3 Signalling procedures during the "active" state . 131
5.3.1 User notification procedure. 131
5.3.2 Call rearrangements . 131
5.3.3 Not used. 131
5.3.4 Support of Dual Services . 131
5.3.4.1 Service Description . 132
5.3.4.2 Call establishment. 132
5.3.4.2.1 Mobile Originating Establishment. 132
5.3.4.2.2 Mobile Terminating Establishment . 133
5.3.4.3 Changing the Call Mode. 133
5.3.4.3.1 Initiation of in-call modification . 133
5.3.4.3.2 Successful completion of in-call
modification . 134
5.3.4.3.3 Change of the channel configuration. 134
5.3.4.3.4 Failure of in-call modification. 134
5.3.4.4 Abnormal procedures. 135
5.3.5 User initiated service level up- and downgrading . 136
5.3.5.1 Initiation of service level up- and downgrading . 136
5.3.5.2 Successful completion of service level up- and
downgrading. 136
5.3.5.3 Rejection of service level up- and downgrading. 136
Page 9
ETS 300 940 (GSM 04.08 version 5.13.1 Release 1996): December 1999
5.3.5.4 Time-out recovery.136
5.4 Call clearing .137
5.4.1 Terminology.137
5.4.2 Exception conditions.137
5.4.3 Clearing initiated by the mobile station.138
5.4.3.1 Initiation of call clearing .138
5.4.3.2 Receipt of a DISCONNECT message from the mobile
station. .138
5.4.3.3 Receipt of a RELEASE message from the network .138
5.4.3.4 Receipt of a RELEASE COMPLETE message from the
mobile station.138
5.4.3.5 Abnormal cases.138
5.4.4 Clearing initiated by the network .138
5.4.4.1 Clearing when tones/announcements provided.138
5.4.4.1.1 Receipt of a DISCONNECT message
with progress indicator #8 from the
network .139
5.4.4.1.2 Expiry of timer T306.139
5.4.4.2 Clearing when tones/announcements not provided.139
5.4.4.2.1 Receipt of a DISCONNECT message
without progress indicator or with
progress indicator different from #8
from the network .139
5.4.4.2.2 Receipt of a RELEASE message from
the mobile station.139
5.4.4.2.3 Abnormal cases .139
5.4.4.3 Completion of clearing.140
5.4.4.3.1 Abnormal cases .140
5.4.5 Clear collision .140
5.5 Miscellaneous procedures .140
5.5.1 In-band tones and announcements.140
5.5.2 Call collisions.140
5.5.3 Status procedures .141
5.5.3.1 Status enquiry procedure.141
5.5.3.2 Reception of a STATUS message by a CC entity .141
5.5.3.2.1 STATUS message with incompatible
state .141
5.5.3.2.2 STATUS message with compatible
state .141
5.5.4 Call re-establishment, mobile station side.142
5.5.4.1 Indication from the mobility management sublayer .142
5.5.4.2 Reaction of call control .142
5.5.4.3 Completion of re-establishment.142
5.5.4.4 Unsuccessful outcome .142
5.5.5 Call re-establishment, network side .142
5.5.5.1 State alignment.142
5.5.6 Progress .142
5.5.7 DTMF protocol control procedure.143
5.5.7.1 Start DTMF request by the mobile station .143
5.5.7.2 Start DTMF response by the network .143
5.5.7.3 Stop DTMF request by the mobile station .143
5.5.7.4 Stop DTMF response by the network .143
5.5.7.5 Sequencing of subsequent start DTMF requests by the
mobile station.144
6 Support of packet services.144
7 Examples of structured procedures .145
7.1 General .145
7.1.1 Paging request .146
7.1.2 Immediate assignment .146
7.1.3 Service request and contention resolution .147
7.1.4 Authentication.147
Page 10
ETS 300 940 (GSM 04.08 version 5.13.1 Release 1996): December 1999
7.1.5 Ciphering mode setting. 148
7.1.6 Transaction phase . 148
7.1.6.1 Channel mode modify . 148
7.1.7 Channel release. 149
7.2 Abnormal cases. 149
7.3 Selected examples. 149
7.3.1 Location updating. 150
7.3.2 Mobile originating call establishment . 152
7.3.3 Mobile terminating call establishment. 156
7.3.4 Call clearing . 159
7.3.5 DTMF protocol control . 160
7.3.6 Handover . 161
7.3.7 In-call modification . 163
7.3.8 Call re-establishment . 164
7.3.9 Network initiated mobile originating call $(CCBS)$ . 165
8 Handling of unknown, unforeseen, and erroneous protocol data . 170
8.1 General. 170
8.2 Message too short. 170
8.3 Unknown or unforeseen transaction identifier. 170
8.4 Unknown or unforeseen message type. 171
8.5 Non-semantical mandatory information element errors . 172
8.5.1 Radio resource management . 172
8.5.2 Mobility management. 172
8.5.3 Call control. 172
8.6 Unknown and unforeseen IEs in the non-imperative message part. 173
8.6.1 IEIs unknown in the message. 173
8.6.2 Out of sequence IEs . 173
8.6.3 Repeated IEs . 173
8.7 Non-imperative message part errors. 173
8.7.1 Syntactically incorrect optional IEs. 173
8.7.2 Conditional IE errors . 173
8.8 Messages with semantically incorrect contents . 174
9 Message functional definitions and contents. 174
9.1 Messages for Radio Resources management. 175
9.1.1 Additional assignment. 177
9.1.1.1 Mobile Allocation . 177
9.1.1.2 Starting Time. 177
9.1.2 Assignment command . 178
9.1.2.1 Mode of the First Channel (Channel Set 1) and Mode of
Channel Set "X" (2=
9.1.2.2 Description of the Second Channel. 179
9.1.2.3 Mode of the Second Channel. 179
9.1.2.4 Mobile Allocation and Frequency List, after the starting
time . 179
9.1.2.5 Starting Time. 180
9.1.2.6 Reference cell frequency list. 180
9.1.2.7 Cell Channel Description. 180
9.1.2.8 Cipher Mode Setting . 180
9.1.2.9 VGCS target mode Indication . 181
9.1.2.10 Description of the multislot allocation. 181
9.1.3 Assignment complete . 181
9.1.4 Assignment failure . 182
9.1.5 Channel mode modify. 182
9.1.5.1 Channel Description. 182
9.1.5.2 VGCS target mode Indication . 182
9.1.6 Channel mode modify acknowledge. 183
9.1.7 Channel release. 184
9.1.7.1 Channel description and mobile allocation. 184
9.1.7.2 Group Cipher Key Number. 184
9.1.8 Channel request. 185
9.1.9 Ciphering mode command . 187
Page 11
ETS 300 940 (GSM 04.08 version 5.13.1 Release 1996): December 1999
9.1.10 Ciphering mode complete .
...