Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 24.007  Word version:  18.2.0

Top   Top   Up   Prev   Next
1…   4…   5…   6…   6.5…   7…   7.4…   9…   9.4…   10…   11…   A… 
4 Introduction  4.1 General  4.2 Applicability of functional blocks  4.3 Technique of description 
...

 

4  Introduction  p. 16

4.1  General  p. 16

Five models are defined for Layer 3, one model for non-GPRS services, one for GPRS services supporting Class C MSs only, one model for GPRS-services supporting Class A and Class B MSs, one model for EPS services and one model for 5GS services over either 3GPP access or over non-3GPP access. (The third model is a combination of the first two models listed). In the present document GPRS services and EPS services will be used as synonyms.
The layer 3 for non-GPRS services provides the functions necessary:
  • for Radio Resource (RR) management;
  • for Mobility Management (MM); and
  • for the Connection Management (CM) functions, i.e. functions for the control, provision, and support of services offered by the network; among which there are, e.g.:
    • the functions to establish, maintain and terminate circuit-switched connections across a GSM PLMN and other networks to which the GSM PLMN is connected;
    • supporting functions for supplementary services control;
    • supporting functions for short messages service control;
    • supporting functions for location services control (only for a type A LMU).
The layer 3 for non-GPRS services is composed of three sublayers comprising:
  • the Radio Resource Management (RR) functions;
  • the Mobility Management (MM) functions; and
  • the Connection Management (CM) functions.
When CTS services are added to non-GPRS services, the following functions are added:
  • CTS Radio Resource Management (CTS-RR) functions to RR; and
  • CTS Mobility Management (CTS-MM) functions to MM.
The layer 3 for GPRS services is composed of four sublayers comprising:
  • the Radio Resource Management (RR) functions;
  • the Mobility Management (GMM);
  • for the Logical Link Control (LLC);
  • the Connection Management (CM) functions.
The Connection Management (CM) sublayer is composed of functional blocks for:
  • Call Control (CC) for non-GPRS services;
  • Short Message Service Support (SMS) for non-GPRS services;
  • GPRS Short Message Service Support (GSMS) (for GPRS services supporting Class A, B and C MSs);
  • Session Management (SM) (for GPRS services supporting Class A, B and C MSs);
  • Supplementary Services Support (SS) for non-GPRS services;
  • Group Call Control for non-GPRS services;
  • Broadcast Call Control (BCC) for non-GPRS services;
  • Connection Management of Packet Data on Signalling channels for non-GPRS services;
  • Location Services support (LCS) for non-GPRS services (only for a type A LMU).
Within the context of LCS, for GSM LCS, the services defined for an MS are equally applicable to a type A LMU, unless otherwise stated. However, services defined specifically for a type A LMU are not applicable to an MS. The following is a list of services essential for a type A LMU.
The layer 3 for non-GPRS services provides the functions necessary:
  • for Radio Resource (RR) management;
  • for Mobility Management (MM); and
  • supporting functions for location service control.
The layer 3 for non-GPRS services is composed of three sublayers comprising:
  • the Radio Resource Management (RR) functions;
  • the Mobility Management (MM) functions; and
  • the Connection Management (CM) functions.
The Connection Management (CM) sublayer is composed of a functional block for:
  • location services support (LCS) for non-GPRS services.
The present document does not consider the distribution of signalling functions among the different network equipments. The signalling functions are described between two systems which represent the MS side and the network side of the radio interface of layer 3. Only the functions in the network for signalling communication with one MS is considered.
For GPRS services, in addition to the signalling functions also the user data transfer is included in the present document.
The layer 3 for EPS services is composed of three sublayers comprising:
  • the EPS Radio Resource Management (RR) functions;
  • the EPS Mobility Management (EMM) functions; and
  • the Connection Management (CM) functions.
The Connection Management (CM) sublayer is composed of a functional block for:
  • the EPS Session Management (ESM) functions.
The layer 3 for 5GS services is composed of three sublayers comprising:
  • the 5GS radio resource management (5GRR) functions for NAS over 3GPP access or the non-3GPP access functions for NAS over non-3GPP access;
  • the 5GS mobility management (5GMM) functions; and
  • the 5GS connection management (5GCM) functions.
The 5GS mobility management (5GMM) sublayer is composed of a functional block for:
  • the 5GS mobility management (5GMM) functions.
The 5GS connection management (5GCM) sublayer is composed of a functional block for:
  • the 5GS session management (5GSM) functions.
Up

4.2  Applicability of functional blocks  p. 18

Not for all functional blocks listed in clause 4.1, support in the MS or in the network is mandatory:
  • Support of Group Call Control is optional in the MS and in the network.
  • Support of Broadcast Call Control is optional in the MS and in the network.
  • Connection Management of Packet Data on Signalling channels. is optional in the MS and in the network.
  • Support of GPRS services is optional in the MS and in the network.
  • Support of CTS services is optional in the MS. CTS services are not applicable to the network.
  • Support of LCS services is optional in the MS and in the network, but not optional in LMU.
Further conditions and constraints are defined in other Technical Specifications.
Up

4.3  Technique of description  p. 18

Layer 3 and its sub-layers are specified by:
Descriptions in clause 3 to clause 10 are not maintained actively.
Up

4.3.1  Service description  p. 18

The services of signalling layer 3 and its sublayers are described in terms of:
  • services provided to upper (sub-)layers at the service access points;
  • services assumed from lower (sub-)layers at the service access points.
Layer 3 and its supporting lower layers provide the Mobile Network Signalling (MNS) Service and User Data Transfer (UDT) Service (for GPRS services only) to the upper layers.
The service provided/assumed at the service access points are described by means of abstract service primitives and parameters as recommended in ITU-T Recommendation X.200 [18].
Up

4.3.2  Abstract service primitives  p. 18

The abstract service primitives consist of requests, responses, indications and confirmations. The general syntax of a primitive is specified in TR 21.905.

4.3.3  Protocols and peer-to-peer communication  p. 18

By use of the services provided by lower (sub-)layers, peer entities in a (sub-)layer in the MS and the network exchange information. Exchange of information between two peer entities is performed according to the corresponding (sub-)layer protocols. A protocol is a set of rules and formats by which the information (control information and user data) is exchanged between the two peers. The information is exchanged by use of messages which are defined in the protocol. (Therefore, the messages are also called Protocol Data Units, PDUs).
There are several protocols of the RR sublayer, one protocol of the LLC sublayer, three protocols of the MM sublayer, and several protocols of the CM sublayer. For each functional block of the CM sublayer as defined in clause 4.1 there is one protocol. The CM protocols are specified in the Technical Specifications identified in clause 4.3.4.
In the model used in the present document, there are:
  1. for non-GPRS services:
    • one RR sub-layer entity in the MS and one RR sub-layer entity in the network;
    • one MM sub-layer entity in the MS and one MM sub-layer entity in the network;
    • for each functional block of the CM sublayer as defined in clause 4.1 which is supported in the MS (in the network), there are, depending on the protocol, one or more entities in the MS (in the network). Two different entities of the same functional block in the MS (in the network) are called parallel entities. The entities of the same functional block in the MS correspond in a one-to-one relation to the entities of the functional block in the network. The corresponding entities are called peer entities;
  2. for CTS services (in addition to non-GPRS services):
    • one RR sub-layer entity in the MS and one in the CTS fixed part. These RR sub-layers include one CTS-RR sub-entity on each side;
    • one MM sub-layer entity in the MS and one in the CTS fixed part These MM sub-layers include one CTS-MM sub-entity on each side;
    • for each functional block of the CM sublayer as defined in clause 4.1 which is supported in the MS (in the fixed part), there are, depending on the protocol, one or more entities in the MS (in the fixed part). Two different entities of the same functional block in the MS (in the fixed part) are called parallel entities. The entities of the same functional block in the MS correspond in a one-to-one relation to the entities of the functional block in the fixed part. The corresponding entities are called peer entities;
  3. for GPRS services supporting Class C MSs:
    • one RR sublayer entity (RR) in the MS and one RR sublayer entity in the network;
    • six LLC sublayer entities (QoS1-QoS4, signalling, SMS) in the MS and six LLC sublayer entities in the network;
    • one MM sublayer entity (GMM) in the MS and one MM sublayer entity in the network (GMM);
    • one SM entity in the MS's CM sublayer and one SM sublayer entity in the network's CM sublayer;
    • one or more GSMS functional blocks in the CM sublayer if supported;
  4. for non-GPRS and GPRS services supporting Class A and Class B MSs:
    • two RR sublayer entities (RR) in the MS and two RR sublayer entities in the network;
    • six LLC sublayer entities (QoS1-QoS4, signalling, SMS) in the MS and six LLC sublayer entities in the network;
    • two MM sublayer entities (GMM + MM) in the MS and one or two MM sublayer entities in the network (GMM or MM);
    • one SM entity in the MS's CM sublayer and one SM entity in the network's CM sublayer;
    • for each functional block of the CM sublayer as defined in clause 4.1 which is supported in the MS (in the network), there are, depending on the protocol, one or more entities in the MS (in the network). Two different entities of the same functional block in the MS (in the network) are called parallel entities. The entities of the same functional block in the MS correspond in a one-to-one relation to the entities of the functional block in the network. The corresponding entities are called peer entities;
  5. for EPS services:
    • one RR entity in the MS and one RR entity in the network;
    • one EMM entity in the MS and one EMM entity in the network;
    • for each functional block of the CM sublayer as defined in clause 4.1 which is supported in the MS (in the network), there are, depending on the protocol, one or more entities in the MS (in the network). Two different entities of the same functional block in the MS (in the network) are called parallel entities. The entities of the same functional block in the MS correspond in a one-to-one relation to the entities of the functional block in the network. The corresponding entities are called peer entities.
  6. for 5GS services:
    • one 5GRR entity in the MS and one 5GRR entity in the network for NAS over 3GPP access;
    • one non-3GPP access management entity in the MS and one non-3GPP access interworking entity in the N3IWF for the NAS over non-3GPP access;
    • one 5GMM entity in the MS and one 5GMM entity in the network;
    • for each functional block of the 5GCM sublayer as defined in clause 4.1 which is supported in the MS (in the network), there are, depending on the protocol, one or more entities in the MS (in the network). Two different entities of the same functional block in the MS (in the network) are called parallel entities. The entities of the same functional block in the MS correspond in a one-to-one relation to the entities of the functional block in the network. The corresponding entities are called peer entities.
As each sub-layer entity is specified by one and only one protocol, it is also called a protocol entity or protocol control entity.
For GPRS-services supporting Class A and Class B MSs, the MM entities of the MM-sublayer are able to exchange information by means of GMM PDUs as well as MM PDU's. This means if a mobile is GPRS attached, non-GPRS mobility management procedures may make use of GRPS mobility management messages.
When two peer protocol entities exchange PDUs, a transaction is said to be established (or: to be active; or: to exist). It depends from the protocol when exactly a protocol entity considers the transaction to be active, normally this is the case:
  • from the moment when it has passed the first suitable message to lower (sub-) layers or received the first suitable message from its peer entity;
  • up to the moment when it has released the transaction.
Up

4.3.4  Contents of layer 3 related Technical Specifications  p. 20

 
  • The Radio Resource (RR) management protocol is defined in TS 44.018;
  • the Mobility Management (MM) protocol is defined in TS 24.008;
  • the Session Management (SM) protocol is defined in TS 24.008;
  • the Call Control (CC) protocol is defined in TS 24.008;
  • the Supplementary Services (SS) protocol is defined in TS 24.010, 3GPP TS 24.08x, 3GPP TS 24.09x, and TS 24.030;
  • the Short Message Service (SMS) protocol is defined in TS 24.011;
  • the Group Call Control (GCC) protocol is defined in TS 44.068;
  • the Logical Link Control (LLC) protocol is defined in TS 44.064;
  • the GPRS Radio Resource (GRR) protocol is defined in TS 44.060 and TS 24.008;
  • the CTS Radio Resource (CTS-RR) sub-protocol is defined in TS 44.056;
  • the CTS Mobility Management (CTS-MM) sub-protocol is defined in TS 44.056;
  • the CTS additions to the Call Control (CC) protocol are defined in TS 44.056;
  • the Location Services (LCS) protocol for a type A LMU is defined in TS 23.271 and TS 44.071;
  • the EPS Radio Resource (RR) management protocol is defined in TS 36.331;
  • the EPS Mobility Management (EMM) protocol is defined in TS 24.301;
  • the EPS Session Management (ESM) protocol is defined in TS 24.301;
  • the 5GS Radio Resource management (5GRR) protocol is defined in TS 38.331;
  • the 5GS Mobility Management (5GMM) protocol is defined in TS 24.501;
  • the UE policy delivery service is defined in TS 24.501;
  • the 5GS Session Management (5GSM) protocol is defined in TS 24.501;
  • the non-3GPP access management protocol is defined in TS 24.502;
  • the PC5 signalling protocol for V2X communication for 5GS is defined in TS 24.587;
  • the Time-Sensitive Networking (TSN) Application Function (AF) to Device-Side TSN Translator (DS-TT) and Network-Side TSN Translator (NW-TT) protocol is defined in TS 24.519;
  • the Performance Measurement Function (PMF) protocol is defined in TS 24.193;
  • the PC3 and PC5 signalling protocol for Proximity-based Services (ProSe) are defined in TS 24.334;
  • the PC3a and PC5 signalling protocol for 5G Proximity-based Services (ProSe) are defined in TS 24.554;
  • the signalling protocol between the Application Client on the constrained UE and the MSGin5G Client on the MSGin5G Gateway UE for Enabling MSGin5G Service is defined in TS 24.538;
  • the Location Services User Plane (LCS-UP) protocol is defined in TS 24.572;
  • the User Plane Positioning Connection Management (UPP-CM) protocol is defined in TS 24.572;
  • the extended PC5 signalling protocol and supplementary RSPP signalling protocol over PC5-U for ranging and sidelink positioning are defined in TS 24.514; and.
  • the PC5 signalling protocol for aircraft-to-everything (A2X) communication is defined in TS 24.577.
Up

Up   Top   ToC