0 Scope

04.083GPPMobile radio interface Layer 3 specificationRelease 1998TS

The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 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 3GPP TS 04.03.

The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 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.

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

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

3GPP TS 04.12 contains functional description of short message – cell broadcast.

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

3GPP TS 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 3GPP TS 04.03. They use the functions and services provided by layer 2 defined in 3GPP TS 04.05 and 3GPP TS 04.06. 3GPP TS 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 3GPP TS 11.10 and 3GPP TS 11.2x series.

0.5 Use of logical channels

The logical control channels are defined in 3GPP TS 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 3GPP TS 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 3GPP TS 04.05 and 3GPP TS 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 the present document:

a) Clause 3 specifies elementary procedures for Radio Resource management:

– system information broadcasting (sub-clause 3.2.2);

– RR connection establishment (sub-clause 3.3):

– entering the dedicated mode: immediate assignment procedure (sub-clause 3.3.1.1);

– paging procedure for RR connection establishment (sub-clause 3.3.2);

– notification procedure (sub-clause 3.3.3);

– Procedures in dedicated mode and in group transmit mode (sub-clause 3.4):

– measurement report procedure (sub-clause 3.4.1.2);

– intracell change of channels (sub-clause 3.4.3);

– intercell change of channels (sub-clause 3.4.4);

– frequency redefinition procedure (sub-clause 3.4.5);

– channel mode change procedure (sub-clause 3.4.6);

– ciphering mode setting procedure (sub-clause 3.4.7);

– additional channel assignment procedure (sub-clause 3.4.8);

– partial channel release procedure (sub-clause 3.4.9);

– radio resources connection release (sub-clause 3.4.13);

– specific RR procedures for voice broadcast channels and voice group call channels (sub-clause 3.4.15);

– application procedures (sub-clause 3.4.21);

– RR procedures on CCCH related to temporary block flow establishment (sub-clause 3.5):

– packet paging procedure using CCCH (sub-clause 3.5.1);

– packet access procedure using CCCH (sub-clause 3.5.2);

– packet downlink assignment procedure using CCCH (sub-clause 3.5.3);

– RR procedures on DCCH related to temporary block flow establishment:

– Assignment to Packet Data Channel procedure (sub-clause 3.4.19);

– Network commanded cell reselection (sub-clause 3.4.20).

b) Clause 4 specifies elementary procedures for Mobility Management:

– mobility management common procedures (sub-clause 4.3):

– TMSI reallocation procedure (sub-clause 4.3.1);

– authentication procedure (sub-clause 4.3.2);

– identification procedure (sub-clause 4.3.3);

– IMSI detach procedure (sub-clause 4.3.4);

– abort procedure (sub-clause 4.3.5);

– MM information procedure (sub-clause 4.3.6);

– mobility management specific procedures (sub-clause 4.4):

– location updating procedure (sub-clause 4.4.1);

– periodic updating (sub-clause 4.4.2);

– IMSI attach procedure (sub-clause 4.4.3);

– generic location updating procedure (sub-clause 4.4);

– connection management sublayer service provision:

– mobility management connection establishment (sub-clause 4.5.1);

– mobility management connection information transfer phase (sub-clause 4.5.2);

– mobility management connection release (sub-clause 4.5.3);

– GPRS specific mobility management procedures (sub-clause 4.7):

– GPRS attach procedure (sub-clause 4.7.3);

– GPRS detach procedure (sub-clause 4.7.4);

– GPRS routing area updating procedure (sub-clause 4.7.5);

– GPRS common mobility management procedures (sub-clause 4.7):

– GPRS P-TMSI reallocation procedure (sub-clause 4.7.6);

– GPRS authentication and ciphering procedure (sub-clause 4.7.7);

– GPRS identification procedure (sub-clause 4.7.8);

– GPRS information procedure (sub-clause 4.7.12).

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

– mobile originating call establishment (sub-clause 5.2.1);

– mobile terminating call establishment (sub-clause 5.2.2);

– signalling procedures during the active state (sub-clause 5.3):

– user notification procedure (sub-clause 5.3.1);

– call rearrangements (sub-clause 5.3.2);

– DTMF protocol control procedure (sub-clause 5.5.7);

– in-call modification (sub-clause 5.3.4);

– call clearing initiated by the mobile station (sub-clause 5.4.3);

– call clearing initiated by the network (sub-clause 5.4.4);

– miscellaneous procedures:

– in-band tones and announcements (sub-clause 5.5.1);

– status enquiry procedure (sub-clause 5.5.3);

– call re-establishment procedure (sub-clause 5.5.4).

d) Clause 6 specifies elementary procedures for session management:

– GPRS session management procedures (sub-clause 6.1):

– PDP context activation (sub-clause 6.1.1);

– PDP context modification (sub-clause 6.1.2);

– PDP context deactivation (sub-clause 6.1.3);

– anonymous PDP context activation (sub-clause 6.1.4);

– anonymous PDP context deactivation (sub-clause 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 the present document for the mobile station is dependent on the services and functions which are to be supported by a mobile station.

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 the present document if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave.

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

– support of listening to voice broadcast calls (VBS listening).

– support of originating a voice broadcast call (VBS originating).

– support of listening to voice group calls (VGCS listening).

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

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

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

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

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 MS’s capabilities to operate GPRS and other GSM services simultaneously. Mobile stations that are capable to operate GPRS services are referred to as GPRS MSs.

NOTE: Other GSM technical specifications may refer to the MS operation modes A, B, and C as GPRS 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.