04.073GPPMobile Radio Interface Signalling Layer 3 - General AspectsTS

In addition to the services described in this clause, the RR entity and MM entity also provide services to CM entities which don’t belong to the functional blocks of CC, SMS, and SS. (For example, the RR entity provides service to Group Call and Broadcast Call entities.) These services are not further described in this clause.

9.1 Services provided by the Radio Resource Management entity

The Radio Resource Management (RR) sublayer provides a service to the Mobility Management entity (MM).

The RR services are used for:

‑ establishing control channel connections;

‑ releasing control channel connections;

‑ control‑data transfer.

The Radio Resource Management services are represented by the RR‑service primitives.

Figure 9.1: Services provided at RR‑SAP ‑ MS side

9.1.1 Service state diagram

The primitives provided by the Radio Resource Management entity and the transition between permitted states are shown in figure 9.2.

Figure 9.2: Service graph of the Radio Resource Management ‑ MS side

9.1.2 Service primitives

Table 9.1: Primitives and parameters at the RR‑SAP ‑ MS side

9.1.2.1 RR_EST_REQ

Is used by the Mobility Management entity to request establishment of a Mobile originated RR connection. The request shall be given only in the IDLE state when the MS listens to the CCCH and the previously selected BCCH.

9.1.2.2 RR_EST_IND

Indicates to the Mobility Management entity the establishment of a Mobile terminated RR connection. By this indication MM is informed that a transparent connection exists and RR is in the dedicated mode.

9.1.2.3 RR_EST_CNF

Is used by RR to indicate the successful completion of a Mobile originated RR connection establishment. RR connection exists and RR is in the dedicated mode.

9.1.2.4 RR_REL_IND

Is used by RR to indicate to the Mobility Management entity the release of a RR connection when RR has received a CHANNEL RELEASE from the Network and has triggered a normal release of the data link layer. It is also used to indicate that a requested RR connection cannot be established. In both cases, RR returns to IDLE mode.

9.1.2.5 RR_SYNC_IND

Is used for synchronizing RR and the Mobility Management entity after the establishment of a Mobile originated or Mobile terminated RR connection. This indication is provided to MM in the following cases:

‑ ciphering has been started (ciphering);

‑ a traffic channel has been assigned (res. ass. = "resource assigned");

‑ the channel mode has been modified (channel mode modify).

9.1.2.6 RR_DATA_REQ

Is used by the Mobility Management entity to send control data to its peer entity on the Network side via an existing RR connection.

9.1.2.7 RR_DATA_IND

Is used by RR to indicate control‑data, which has been received from its peer entity on the Network side via an existing RR connection.

9.1.2.8 RR_UNIT_DATA_IND

Is used by RR to provide MM with system info. The system info is received on the current BCCH if RR is in the IDLE state. If a RR connection has been established, the system info is received on the SACCH.

9.1.2.9 RR_ABORT_REQ

Request to abort an existing RR connection or a RR connection in progress. The data link, if already established, shall be released by a normal release procedure (DISC/UA) initiated by the MS. This is the only way the MS can trigger the release of a RR connection in case of exceptional conditions. The RR returns to the IDLE state.

9.1.2.10 RR_ABORT_IND

Indication that the RR connection has been aborted by a lower layer failure and RR has returned to the IDLE state.

9.1.3 Services provided by the Radio Resource Management entity for CTS

Inside the RR sub-layer, the CTS Radio Resource Management (CTS‑RR) sublayer provides services to the CTS Mobility Management (CTS‑MM) entity.

The CTS-RR services are used for:

‑ alive check.

The CTS Radio Resource Management services are represented by the CTS‑RR‑service primitives.

Table 9.1.3: Primitives and parameters at the RR‑SAP ‑ MS side for CTS

9.1.3.1 CTS_RR_ALIVE_CHECK_IND

Indicates to the CTS Mobility Management entity that an alive check request has been received from the fixed part.

9.2 Services provided by the Mobility Management entity

The Mobility Management (MM) sublayer provides services to the Call Control (CC) entity, the Supplementary Services Support (SS) entity, the Location Services (LCS) entity (only for type A LMU) and the Short Message Service Support (SMS) entity.

The Mobility Management services primitives are discriminated by the MMCC, MMSS, MMLCS and MMSMS prefix.

Figure 9.3: Services provided at the MMCC‑SAP, MMSS‑SAP, MMLCS-SAP, MMSMS‑SAP ‑ MS side

(Note: Figure 9.3 shall be updated to include the LCS PD in the same manner as the other PDs are shown)

9.2.1 Service state diagram

The primitives provided by the Mobility Management entity towards Call Control, call independent Supplementary Service Support, Location Services Support for type A LMU, and towards Short Messages Service Support and the transition between permitted states are illustrated in figure 9.4.

NOTE 1: MMCC‑primitives only at MMCC‑SAP.

NOTE 2: The prefix MMXX is used for substitution of MMCC, MMSS, MMLCS or MMSMS.

Figure 9.4: Service graph of the Mobility Management entity ‑ MS side

9.2.2 Service primitives

Table 9.2: Primitives and Parameters at MMCC‑SAP, MMSS‑SAP, MMLCS-SAP (for type A LMU) or MMSMS‑SAP ‑ MS side

9.2.2.1 MMXX_EST_REQ

Request used by CC, SS, LCS (for type A LMU) and SMS respectively, to request establishment of a MM connection. Several MM connections may be provided in parallel to the requesting entities. The primitive may contain parameters which are relevant for the CM SERVICE REQUEST message, e.g. to distinguish a basic call from an emergency call.

9.2.2.2 MMXX_EST_IND

Indication to CC, SS, LCS (for type A LMU) or SMS that a Mobile terminated MM connection has been established and the first message has been received from the respective peer entity. Several MM connections may be provided in parallel. If a MM connection already exists, a new MM connection using the same RR connection is indicated by this primitive if MM detects a message with a new combination of Protocol Discriminator (PD) and Transaction Identifier (TI).

9.2.2.3 MMXX_EST_CNF

Successful confirmation of the MM connection establishment by the MM sublayer to be given to the appropriate entity which has requested the service.

9.2.2.4 MMXX_REL_REQ

Used by CC, SS, LCS (for type A LMU) or SMS respectively, to request release of the MM connection. The corresponding PD/TI will be released and may be used for a new MM connection.

9.2.2.5 MMXX_REL_IND

Indication of the release of an existing MM connection or a MM connection in progress. This primitive is used in exceptional cases to indicate that the MM connection cannot be established or kept any longer and PD/TI have been released.

9.2.2.6 MMXX_DATA_REQ

Request used by the CC, SS or SMS entities for acknowledged control‑data transmission.

9.2.2.7 MMXX_DATA_IND

Indication used by MM to transfer the received acknowledged control‑data to the CC, SS, LCS or SMS entities.

9.2.2.8 MMXX_UNIT_DATA_REQ

Request used by the CC, SS, LCS (for type A LMU) or SMS entities for unacknowledged control‑data transmission.

9.2.2.9 MMXX_UNIT_DATA_IND

Indication used by MM to transfer the received unacknowledged control‑data to the CC, SS, LCS or SMS entities.

9.2.2.10 MMCC_SYNC_IND

Indication that a dedicated channel assignment has been performed and/or the channel mode has been changed (only towards the CC entity).

9.2.2.11 MMXX_REEST_REQ

Request to establish a MM connection which has been interrupted by a lower layer failure. The interruption must have been indicated by MMXX_ERR_IND.

9.2.2.12 MMXX_REEST_CNF

Confirmation of the successful re‑establishment of the MM connection. The MM connection will continue with PD/TI as it had before.

9.2.2.13 MMXX_ERR_IND

Indication of a lower layer failure interrupting the MM connection. The PD/TI are still kept by MM. In case of parallel transactions this indication is passed to all CM entities for which a MM connection has been established. It is left to the decision of the appropriate CM entity to either request the re‑establishment of the MM connection by MMXX_REEST_REQ or to release it by MMXX_REL_REQ.

9.2.2.14 MMXX_PROMPT_IND

Indication given by MM to inform of the completion of the MM connection to the CC, SS, LCS (for type A LMU) or SMS entities for a mobile station which supports "Network Initiated MO CM Connection Request".

9.2.2.15 MMXX_PROMPT_REJ

Response to the MMXX_PROMPT_IND indication to the MM entity in a mobile station which supports "Network Initiated MO CM Connection Request" in case when it is impossible to establish the prompted CM connection e.g. due to lack of free transaction identifiers.

9.3 Services provided by radio resource management entity for GPRS services

This subclause is informative, the service primitives are defined in GSM 04.60 [10]. They are included here to provide a complete overview of the radio interface protocol architecture.

9.3.1 Service primitives for GRR-SAP

Table 9.3.1: Primitives and parameters at GRR-SAP

9.3.1.1 GRR-DATA-REQ

Request used by the LL sublayer for acknowledged data transmission with a certain priority. Cause indicates if the GRR-DATA-REQ was triggered as an implicit page response.

9.3.1.2 GRR-DATA-IND

Indication used by RR to transfer received data to the LL sublayer.

9.3.1.3 GRR-UNITDATA-REQ

Request used by the LL sublayer for unacknowledged data transmission with a certain priority.

9.3.1.4 GRR-UNITDATA-IND

Indication used by RR to transfer received data to the LL sublayer.

9.3.1.5 GRR-STATUS-IND

Indication used by RR to transfer RLC/MAC failures to the LL sublayer.

9.3.2 Service primitives for GMMRR-SAP

Table 9.3.2: Primitives and Parameters at GMMRR-SAP – MS side

9.3.2.1 GMMRR-ASSIGN-REQ

A new TLLI is assigned to the RR sublayer.

9.3.2.2 GMMRR-PAGE-IND

A RR-paging message has been received by the RR sublayer.

9.4 Services provided by the LLC entity for GPRS services

This subclause is informative, the service primitives are defined in GSM 04.64 [11]. They are included here to provide a complete overview of the radio interface protocol architecture.

9.4.1 Service primitives for LLGMM-SAP

Table 9.4.1: Primitives and parameters at LLGMM-SAP – MS side

9.4.1.1 LLGMM-ASSIGN-REQ

A new TLLI and/or a ciphering key and/or a ciphering algorithm is assigned to the LLC sublayer.

9.4.1.2 LLGMM-TRIGGER-REQ

Request to send an LLC PDU to the network. Cause indicates if the primitive is sent to trigger an implicit page response.

9.4.1.3 LLGMM-TRIGGER-IND

An LLC frame has been transmitted to the network.

9.4.1.4 LLGMM-SUSPEND-REQ

All LLC links in ABM mode will cease sending PDUs. GMM messages can still be sent and received.

9.4.1.5 LLGMM-RESUME-REQ

Normal LLC frame sending and reception is possible again.

9.4.1.6 LLGMM-WINDOW-REQ

Request for the MS’s actual LLC’s V(R)s.

9.4.1.7 LLGMM-WINDOW-CNF

The actual LLC’s V(R)s for each LLC link in ABM mode are transferred to GMM.

9.4.1.8 LL-UNITDATA-REQ

Request to send a GMM message in unacknowledged mode to the peer entity.

9.4.1.9 LL-UNITDATA-IND

A GMM message in unacknowledged mode has been received from the peer entity.

9.4.1.10 LLGMM-STATUS-IND

Indication used by LLC to transfer LLC failures to the GMM sublayer. The failure may also be caused due to errors at the RLC/MAC layer.

9.4.2 Service primitives for LLSMS-SAP

Table 9.4.2: Service primitives and parameters at LLSMS-SAP – MS side

9.4.2.1 LL-UNITDATA-REQ

An LLC UI frame will be sent to the peer entity

9.4.2.2 LL-UNITDATA-IND

An LLC UI frame has been received from the peer entity

9.5 Registration Services provided for GPRS Services

9.5.1 Service primitives for GMMSM-SAP

Session management services for non-anonymous may request GPRS service registration before activating a PDP context.

Table 9.5.1: Primitives and parameters at GMMSM-SAP – MS side

9.5.1.1 GMMSM-ESTABLISH-REQ

Request from Session Management to send an ATTACH REQUEST message to the network to setup a GMM connection. The request is only performed in case the MS is not already attached. The GPRS attach is then indirectly caused by a requested non-anonymous PDP context activation.

9.5.1.2 GMMSM-ESTABLISH-CNF

The network has send the ATTACH ACCEPT message to the MS, the indirect attach was successful. Now session management can proceed with PDP context activation.

9.5.1.3 GMMSM-ESTABLISH-REJ

The network has rejected the attach. The MS has received the ATTACH REJECT message.

9.5.1.4 GMMSM-RELEASE-IND

The GPRS mobility management informs the session management that the MS has been GPRS detached, e.g. by timer expiry, and therefore the PDP contexts are not valid anymore.

9.5.1.5 GMMSM-UNITDATA-REQ

The GMM is requested to forward a SM PDU to LLC in order to send it in unacknowledged more to the peer entity.

9.5.1.6 GMMSM-UNITDATA-IND

The GMM forwards a SM PDU, which has been received in unacknowledged mode via LLC from the peer entity.

9.5.2 Service primitives for GMMAA-SAP

Session management services for an anonymous PDP require a mobility management entity which does not perform Routing Area Updating, but which requests the termination of the anonymous access in case of change of the RA.

Table 9.5.2: Primitives and parameters at GMMAA-SAP – MS side

9.5.2.1 GMMAA-ESTABLISH-REQ

Request from Session Management to perform timer supervision (standby timer set to zero) and to disable routing area updating for anonymous PDP context(s).

9.5.2.2 GMMAA-RELEASE-IND

The GPRS mobility management informs the session management that the anonymous PDP contexts are deactivated.

9.5.2.3 GMMAA-ESTABLISH-REJ

The GPRS mobility management informs the session management that the anonymous PDP contexts activation was rejected.

9.5.3 Service primitives for GMMSMS-SAP

The Short Message entity may request from the GMM entity the GMM IMSI registration state before an MO SMS transmission is initiated.

Table 9.5.3: Primitives and parameters at GMMSMS-SAP – MS side

9.5.3.1 GMMSMS-REG-STATE-REQ

Request for the current IMSI registration state from the Short Message entity.

9.5.3.2 GMMSM- REG-STATE -RSP

The current IMSI registration state is sent to the Short Message entity.