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 44.018  Word version:  18.0.0

Top   Top   None   None   Next
1…   2…   3…   3.4   3.5…   9…   10…   A… 
1 Scope  1.1 Scope of the Technical Specification  1.2 Application to the interface structures  1.3 Structure of layer 3 procedures  1.4 Test procedures  1.5 Use of logical channels  1.6 Overview of control procedures  1.7 Applicability of implementations  1.8 Restrictions 
...

 

1  Scope  p. 20

The present document specifies the procedures used at the radio interface (Reference Point Um, see TS 24.002) for Radio Resource (RR) management.
Notation "Reserved sub-clause number" is used to indicate which sub-clauses of the specification were moved from this part of the standard to the other part when this standard was split between RAN and CN parts.
When the notations for "further study" or "FS" or "FFS" are present in this specification they mean that the indicated text is not a normative portion of this standard.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in TS 44.003.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in TS 24.007.
Up

1.1  Scope of the Technical Specification  p. 20

The procedures currently described in the present document are for radio resource management for circuit-switched and GPRS services.
3GPP TS 24.010 contains functional procedures for support of supplementary services.
3GPP TS 24.011 contains functional procedures for support of point-to-point short message services.
3GPP TS 44.012 contains functional description of short message - cell broadcast.
3GPP TS 44.060 contains procedures for radio link control and medium access control (RLC/MAC) of packet data physical channels.
3GPP TS 44.071 contains functional descriptions and procedures for support of location services.
3GPP TS 24.008 contains the procedures for CN protocols.
Up

1.2  Application to the interface structures  p. 20

The layer 3 procedures apply to the interface structures defined in TS 44.003. They use the functions and services provided by layer 2 defined in TS 44.005 and TS 44.006. TS 24.007 gives the general description of layer 3 including procedures, messages format and error handling.
Up

1.3  Structure of layer 3 procedures  p. 20

A building block method is used to describe the layer 3 procedures.
The basic building blocks are "elementary procedures" provided by the protocol control entities of the three sublayers, i.e. radio resource management, mobility management and connection management sublayer.
Complete layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences.

1.4  Test procedures  p. 20

Test procedures of the GSM radio interface signalling are described in TS 51.010-1 and 3GPP TS 51.02x series.

1.5  Use of logical channels  p. 21

The logical control channels are defined in TS 45.002. In the following those control channels are considered which carry signalling information or specific types of user packet information:
  1. Broadcast Control CHannel (BCCH): downlink only, used to broadcast Cell specific information;
  2. Synchronization CHannel (SCH): downlink only, used to broadcast synchronization and BSS identification information;
  3. Paging CHannel (PCH): downlink only, used to send page requests to Mobile Stations (MSs);
  4. Random Access CHannel (RACH): uplink only, used to request a Dedicated Control CHannel;
  5. Access Grant CHannel (AGCH): downlink only, used to allocate a Dedicated Control CHannel;
  6. Standalone Dedicated Control CHannel (SDCCH): bi-directional;
  7. Fast Associated Control CHannel (FACCH): bi-directional, associated with a Traffic CHannel;
  8. Slow Associated Control CHannel (SACCH): bi-directional, associated with a SDCCH or a Traffic CHannel;
  9. Cell Broadcast CHannel (CBCH): downlink only used for general (not point to point) short message information;
  10. Notification CHannel (NCH): downlink only, used to notify mobile stations of VBS (Voice Broadcast Service) calls or VGCS (Voice Group Call Service) calls.
  11. Extended Coverage Broadcast Control CHannel (EC-BCCH): downlink only, used to broadcast Cell specific information in cells that support EC-GSM-IoT;
  12. Extended Coverage Synchronization CHannel (EC-SCH): downlink only, used to broadcast synchronization, BSS identification, EC-BCCH CHANGE MARK, Implicit Reject Status and RACH Access Control in cells that support EC-GSM-IoT;
  13. Extended Coverage Paging CHannel (EC-PCH): downlink only, used to send page requests to EC capable Mobile Stations (MSs) in cells that support EC-GSM-IoT;
  14. Extended Coverage Access Grant CHannel (EC-AGCH): downlink only, used to allocate packet resources to EC capable Mobile Stations (MSs) in cells that support EC-GSM-IoT;
  15. Extended Coverage Random Access CHannel (EC-RACH): uplink only, used to request uplink packet resources by EC capable Mobile Stations (MSs) in cells that support EC-GSM-IoT;
Two service access points are defined on signalling layer 2 which are discriminated by their Service Access Point Identifiers (SAPI) (see TS 44.006):
  1. SAPI 0: supports the transfer of signalling information including user-user information;
  2. 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 TS 44.005 and TS 44.006) as required for each individual message.
Up

1.6  Overview of control procedures  p. 21

1.6.1  List of procedures  p. 21

The following procedures are specified in this Technical Specification:
  1. Clause 3 specifies elementary procedures for Radio Resource management:
    • system information broadcasting (sub-clause 3.2.2);
    • RR connection establishment (sub-clause 3.3):
    • Procedures in dedicated mode and in group transmit mode (sub-clause 3.4):
    • 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 and EC-CCCH related to temporary block flow establishment (sub-clause 3.5):
    • RR procedures on DCCH related to temporary block flow establishment:
    • RR procedure on DCCH related to MBMS:
      • packet paging procedure for MBMS related to dedicated MBMS notification (sub-clause 3.4.27).
    • RR procedures on CCCH related to MBMS:
      • packet paging procedure for MBMS notification using CCCH (sub-clause 3.5.1.3);
      • packet access procedure for MBMS using CCCH (sub-clause 3.5.4).
    • Procedures related to the simultaneous handover of dedicated and packet resources (sub-clause 3.7).
Clause 8 specifies actions to be taken on various error conditions and also provides rules to ensure compatibility with future enhancements of the protocol.
Up

1.7  Applicability of implementations  p. 23

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. For the MS, the Revision level indicating Release 1999 is linked to the full support of the RR protocol and procedures in 3GPP TS 44.018 Release 1999.

1.7.1  Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS)  p. 23

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.
A VGCS capable mobile station shall support USIM-based VGCS ciphering.
The related terms are used in this technical specification, if information on these implementation options is required.
Up

1.7.2  General Packet Radio Service (GPRS)  p. 23

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 TS 23.060:
  • 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.
It should be noted that it is possible that for a GPRS MS, the GMM procedures currently described in the present document do not support combinations of VGCS, VBS and GPRS. The possible interactions are not studied yet.
Up

1.7.3  Multimedia Broadcast/Multicast Service (MBMS) |R6|  p. 23

For mobile stations supporting the Multimedia Broadcast/Multicast Service (MBMS) feature, 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.
The support of dedicated mode MBMS notification is mandatory for mobile stations and optional for networks supporting the Multimedia Broadcast/Multicast Service (MBMS) feature. The dedicated mode MBMS notification consists of the Service Information Sending procedure and the MBMS announcement of mobile stations in dedicated mode.
Up

1.8  Restrictions |R9|  p. 24

Independently of what is stated elsewhere in this and other 3GPP specifications, mobile station support for PBCCH and PCCCH is optional for A/Gb-mode of operation. The network shall never enable PBCCH and PCCCH.

Up   Top   ToC