10 Interlayer service interfaces on the Network side

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 Control and Broadcast Call Control entities.) These services are not further described in this clause.

10.1 Services provided by the Radio Resource Management entity

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

The RR services are used for:

‑ establishing control channel connections;

‑ establishing traffic channel connections;

‑ ciphering mode indication;

‑ releasing control channel connections;

‑ control‑data transfer.

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

Figure 10.1: Services provided at RR‑SAP ‑ Network side

10.1.1 Service state diagram

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

STATES:

IDLE ‑ No dedicated channel established.

CONPEND ‑ Connection pending.

DT1 ‑ Data transfer 1, dedicated channel established.

DT2 ‑ Data transfer 2, dedicated channel established, ciphering mode set.

Figure 10.2: Service graph of the Radio Resource Management entity ‑ Network side

10.1.2 Service primitives

Table 10.1: Primitives and Parameters at the RR‑SAP ‑ Network side

PRIMITIVES

PARAMETERS

REFERENCE

RR_EST_REQ

Parameters for the Initial layer 3 message

10.1.2.1

RR_EST_IND

Initial layer 3 message

10.1.2.2

RR_EST_CNF

10.1.2.3

RR_REL_REQ

cause

10.1.2.4

RR_REL_IND

cause

10.1.2.5

RR_SYNC_REQ

cause (resource assign, ciphering)

10.1.2.6

RR_SYNC_CNF

cause (resource assign, ciphering)

10.1.2.7

RR_DATA_REQ

Layer 3 message

10.1.2.8

RR_DATA_IND

Layer 3 message

10.1.2.9

RR_UNIT_DATA_REQ

Layer 3 message

10.1.2.10

RR_UNIT_DATA_IND

Layer 3 message

10.1.2.11

RR_ABORT_REQ

cause

10.1.2.12

RR_ABORT_IND

cause

10.1.2.13

10.1.2.1 RR_EST_REQ

Request used by the Mobility Management entity to request establishment of control channel connections.

10.1.2.2 RR_EST_IND

Indication to the Mobility Management entity that the establishment of control channel connections has been done.

10.1.2.3 RR_EST_CNF

Confirmation used by RR to confirm the establishment of a requested control channel connection.

10.1.2.4 RR_REL_REQ

Request used by the Mobility Management to release a control channel connection.

10.1.2.5 RR_REL_IND

Indication from RR to MM that the main signalling link has been released.

10.1.2.6 RR_SYNC_REQ

Request used by the Mobility Management entity for synchronization with the RR protocol.

10.1.2.7 RR_SYNC_CNF

Confirmation used by RR that the requested synchronization is done.

10.1.2.8 RR_DATA_REQ

Request used by the Mobility Management entity for acknowledged control‑data transmission.

10.1.2.9 RR_DATA_IND

Indication used by RR to transfer received control‑data, which should be acknowledged, to the Mobility Management entity.

10.1.2.10 RR_UNIT_DATA_REQ

Request used by the Mobility Management entity for unacknowledged control‑data transmission.

10.1.2.11 RR_UNIT_DATA_IND

Indication used by RR to transfer received control‑data, which should not be acknowledged, to the Mobility Management entity.

10.1.2.12 RR_ABORT_REQ

Request of the abandon of the RR connection.

10.1.2.13 RR_ABORT_IND

Indication that a radio link failure has occurred.

10.2 Services provided by the Mobility Management entity

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

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

Figure 10.3: Services provided at MMCC‑SAP, MMSS‑SAP, MMLCS-SAP, MMSMS‑SAP ‑ Network side

(Note: Figure 10.3 shall be updated to include the new LCS PD in the same manner as for the other PDs)

10.2.1 Service state diagram

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

NOTE 1: the parameters in RR_SYNC_CNF must correspond to the parameter in RR_SYNC_REQ.

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

NOTE 3: The prefix MMXX is used for substitution of MMCC, MMSS, MMLCS (for type A LMU) or MMSMS.

Figure 10.4: Service graph of the Mobility Management entity, towards Call Control ‑ Network side

10.2.2 Service primitives

Table 10.2: Primitives and Parameters at MMCC‑SAP, MMSS‑SAP, MMSMS‑SAP ‑ Network side

PRIMITIVES

PARAMETERS

REFERENCE

MMXX_EST_REQ (see note 1)

Mobile ID

10.2.2.1

MMXX_EST_IND (see note 1)

First CM message

10.2.2.2

MMXX_EST_CNF (see note 1)

10.2.2.3

MMXX_REL_REQ (see note 1)

cause

10.2.2.4

MMXX_REL_IND (see note 1)

cause

10.2.2.5

MMXX_DATA_REQ (see note 1)

Layer 3 message

10.2.2.6

MMXX_DATA_IND (see note 1)

Layer 3 message

10.2.2.7

MMXX_UNIT_DATA_REQ (see note 1)

Layer 3 message

10.2.2.8

MMXX_UNIT_DATA_IND (see note 1)

Layer 3 message

10.2.2.9

MMCC_SYNC_REQ (see note 2)

cause (resource assign)

10.2.2.10

MMCC_SYNC_CNF (see note 2)

cause (resource assign)

10.2.2.11

NOTE 1: MMXX is used as substitution for MMCC, MMSS, MMLCS (for type A LMU) or MMSMS.

NOTE 2: Only at MMCC‑SAP.

10.2.2.1 MMXX_EST_REQ

Request by CC, SS, LCS (for type A LMU) and SMS respectively, for the establishment of a MM connection.

10.2.2.2 MMXX_EST_IND

Indication by the MM sublayer that a MM connection is established.

10.2.2.3 MMXX_EST_CNF

Confirmation of the MM connection establishment by the MM sublayer.

10.2.2.4 MMXX_REL_REQ

Request by CC, SS, LCS (for type A LMU) or SMS respectively, for the release of the MM connection.

10.2.2.5 MMXX_REL_IND

Indication by the MM sublayer that a MM connection has been released.

10.2.2.6 MMXX_DATA_REQ

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

10.2.2.7 MMXX_DATA_IND

Indication used by MM to transfer the received acknowledged control‑data to the CC, SS, LCS (for type A LMU) or SMS entities.

10.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.

10.2.2.9 MMXX_UNIT_DATA_IND

Indication used by MM to transfer the received unacknowledged control‑data to the CC, SS, LCS (for type A LMU) or SMS entities.

10.2.2.10 MMCC_SYNC_REQ

Request used by the CC entity to synchronize with the MM entity (resource assign).

10.2.2.11 MMCC_SYNC_CNF

Confirmation used by the MM to inform the CC entity that synchronization is completed (resource assign).

10.3 Services provided by radio resource management entity for GPRS services

This section 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.

10.3.1 Service primitives for GRR-SAP

Table 10.3.1 Primitives and Parameters at GRR-SAP – network side

PRIMITIVE

PARAMETER
(message, info elements of message, other parameters)

REFERENCE

GRR-DATA-REQ

LLC PDU, TLLI, CI, DRX, MS CLM, QoS, Priority

10.3.1.1

GRR-DATA-IND

LLC PDU, TLLI, CI

10.3.1.2

GRR-UNITDATA-REQ

LLC PDU, TLLI, CI, DRX, MS CLM, QoS, Priority

10.3.1.3

GRR-UNITDATA-IND

LLC PDU, TLLI, CI

10.3.1.4

GRR-STATUS-IND

TLLI, cause

10.3.1.5

10.3.1.1 GRR-DATA-REQ

Request used by the LLC layer for acknowledged data transmission with a certain priority.

10.3.1.2 GRR-DATA-IND

Indication used by RR to transfer received data, which shall be acknowledged, to the LLC layer.

10.3.1.3 GRR-UNITDATA-REQ

Request used by the LLC layer for unacknowledged data transmission with a certain priority.

10.3.1.4 GRR-UNITDATA-IND

Indication used by RR to transfer received data, which shall not be acknowledged, to the LLC layer

10.3.1.5 GRR-STATUS-IND

Indication to upper layers that an error has occurred on the radio interface. The cause for the failure is indicated

10.3.2 Service primitives for GMMRR-SAP

Table 10.3.2 Primitives and Parameters at GMMRR-SAP – network side

PRIMITIVE

PARAMETER
(message, info elements of message, other parameters)

REFERENCE

GMMRR-PAGE-REQ

TLLI, IMSI, CI or CI-list or RAI, priority

10.3.2.1

10.3.2.1 GMMRR-PAGE-REQ

Request by GMM to send a RR-paging message to the mobile station.

10.4 Services provided by the LLC entity for GPRS services

10.4.1 Service primitives for LLGMM-SAP

Table 10.4.1 Primitives and Parameters at GRR-SAP – network side

PRIMITIVE

PARAMETER
(message, info elements of message, other parameters)

REFERENCE

LLGMM-ASSIGN-REQ

newTLLI, oldTLLI, Kc, Algorithm

10.4.1.1

LLGMM-TRIGGER-IND

TLLI

10.4.1.2

LLGMM-SUSPEND-REQ

TLLI, page

10.4.1.3

LLGMM-RESUME-REQ

TLLI

10.4.1.4

LLGMM-PAGE-IND

TLLI

10.4.1.5

LLGMM-PAGE-RESP-IND

TLLI

10.4.1.6

LLGMM-WINDOW-REQ

TLLI

10.4.1.7

LLGMM-WINDOW-CNF

actual LLC’s N(R) per SAP

10.4.1.8

LL-UNITDATA-REQ

TLLI, SMM-PDU, protect, cipher

10.4.1.9

LL-UNITDATA-IND

TLLI, SMM-PDU, cipher

10.4.1.10

LLGMM-STATUS-IND

TLLI, cause

10.4.1.11

10.4.1.1 LLGMM-ASSIGN-REQ

A new TLLI and/or a ciphering key and/or a ciphering algorithm is assigned to the LL sublayer. Also an old TLLI can be unassigned.

10.4.1.2 LLGMM-TRIGGER-IND

An LLC frame has been received from the mobile station.

10.4.1.3 LLGMM-SUSPEND-REQ

All LLC links will cease sending PDUs. The parameter page indicates that data shall be sent if available and therefore paging shall be needed. Or the cause indicates that data shall not be sent until a RESUME-REQ is received.

10.4.1.4 LLGMM-RESUME-REQ

Normal LLC frame sending and reception is possible again.

10.4.1.5 LLGMM-WINDOW-REQ

Request for the actual LLC’s N(R)s.

10.4.1.6 LLGMM-WINDOW-CNF

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

10.4.1.7 LLGMM-PAGE-IND

Requires to send a paging message to the mobile station.

10.4.1.8 LLGMM-PAGE-RESP-IND

A paging response has been received from the mobile

10.4.1.9 LL-UNITDATA-REQ

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

10.4.1.10 LL-UNITDATA-IND

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

10.4.1.11 LLGMM-STATUS-IND

Indication used by LLC to transfer lower layer failures to the GMM sublayer.

10.4.2 Service primitives for LLSMS-SAP

Table 10.4.2; Primitives and Parameters at LLSMS-SAP – network side

PRIMITIVE

PARAMETER
(message, info elements of message, other parameters)

REFERENCE

LL-UNITDATA-REQ

TLLI, SMS-CP-PDU, protect, cipher

10.4.2.1

LL-UNITDATA-IND

TLLI, SMS-CP-PDU

10.4.2.2

10.4.2.1 LL-UNITDATA-REQ

An LLC UI frame will be sent to the peer entity.

10.4.2.2 LL-UNITDATA-IND

An LLC UI frame has been received from the peer entity.

10.5 Services provided by the GMM for GPRS services

10.5.1 Service primitives for GMMSM-SAP

Table 10.5.1: Primitives and Parameters at GMMSM-SAP – network side

PRIMITIVE

PARAMETER
(message, info elements of message, other parameters)

REFERENCE

GMMSM-RELEASE-IND

10.5.1.1

GMMSM-UNITDATA-REQ

SM-PDU

10.5.1.2

GMMSM-UNITDATA-IND

SM-PDU

10.5.1.3

10.5.1.1 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.

10.5.1.2 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.

10.5.1.3 GMMSM-UNITDATA-IND

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

10.6 Services provided by the Radio Resource Management entity for CTS on the fixed part

In addition to services described in 10.1, the CTS Radio Resource Management (CTS‑RR) inside the RR sublayer provides services to the CTS Mobility Management entity (CTS‑MM).

The CTS‑RR services are used for:

‑ alive check;

– hunting;

– group alerting.

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

10.6.1 Service primitives

Table 10.6: Primitives and Parameters at the RR‑SAP – Fixed part side

PRIMITIVES

PARAMETERS

REFERENCE

RR_CTS_ALIVE_CHECK_REQ

CTSMSI

10.6.1.1

RR_ CTS_ALIVE_CHECK_IND

Cause

10.6.1.2

RR_ CTS_HUNTING_REQ

10.6.1.3

RR_ CTS_GROUP_ALERTING_REQ

CTSMSI, display

10.6.1.4

10.6.1.1 RR_ CTS_ALIVE_CHECK_REQ

Request used by the CTS Mobility Management entity to request an alive check.

10.6.1.2 RR_ CTS_ALIVE_CHECK_IND

Indication to the CTS Mobility Management entity on the results of the alive check.

10.6.1.3 RR_ CTS_HUNTING_REQ

Request to hunt the mobiles.

10.6.1.4 RR_ CTS_GROUP_ALERTING_REQ

Request to alert a group of mobiles.