hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.2.2.1 MNSS_BEGIN_REQ | Request to send a REGISTER message in order to establish a signalling transaction for the provision of call independent supplementary services. The request for a supplementary service invocation may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.2.2.2 MNSS_BEGIN_IND | Receipt of a REGISTER message, a signalling transaction is established for the provision of call independent supplementary services. The indication of a supplementary service invocation may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.2.2.3 MNSS_FACILITY_REQ | Request to send a FACILITY message for the provision of a call independent supplementary service facility. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.2.2.4 MNSS_FACILITY_IND | Receipt of a FACILITY message, a supplementary service facility has been requested. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.2.2.5 MNSS_END_REQ | Request to send a RELEASE COMPLETE message in order to release the signalling transaction by sending a RELEASE COMPLETE message. The request for transfer of a supplementary service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.2.2.6 MNSS_END_IND | Indication that the signalling transaction has been released after receipt of a RELEASE COMPLETE message. The indication of a supplementary service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.3 Short Message Services Support | The service provided by the CM sublayer to support the short message service are defined in 3GPP TS 24.011 [8]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4 Services provided to SNDCP and SMS entities by GPRS Logical Link Control services | This clause is informative, the service primitives are defined in 3GPP TS 44.064 [11a]. They are included here to provide a complete overview of the radio interface protocol architecture.
On the network side, Logical Link Control services are provided at the QoS1-SAP - QoS4 SAP towards the SNDCP and at the LLSMS-SAP towards SMS. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.1 Service state diagram for QoS1-SAP, QoS2-SAP, QoS3-SAP and QoS4-SAP | The service state diagram is identical on the network side is identical to the one shown in figure 6.7 for the mobile side. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2 Service primitives for QoS1-SAP, QoS2-SAP, QoS3-SAP and QoS4-SAP | PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
LL-ESTABLISH-REQ
TLLI, SNDCP requested parameters (XID)
7.4.2.1
LL-ESTABLISH-CNF
TLLI, SNDCP negotiated parameters (XID), N201
7.4.2.2
LL-ESTABLISH-IND
TLLI, SNDCP requested parameters (XID), N201
7.4.2.3
LL-ESTABLISH-RSP
TLLI, SNDCP negotiated parameters (XID)
7.4.2.4
LL-RELEASE-REQ
TLLI
7.4.2.5
LL-RELEASE-CNF
TLLI
7.4.2.6
LL-RELEASE-IND
TLLI
7.4.2.7
LL-XID-REQ
TLLI, SNDCP requested parameters (XID)
7.4.2.8
LL-XID-IND
TLLI, SNDCP requested parameters (XID), N201
7.4.2.9
LL-XID-RSP
TLLI, SNDCP negotiated parameters (XID)
7.4.2.10
LL-XID-CNF
TLLI, SNDCP negotiated parameters (XID), N201
7.4.2.11
LL-DATA-REQ
TLLI, N-PDU, local reference
7.4.2.12
LL-DATASENT-IND
TLLI, local reference, V(S)
7.4.2.13
LL-DATA-CNF
TLLI, local reference
7.4.2.14
LL-DATA-IND
TLLI, N-PDU
7.4.2.15
LL-UNITDATA-REQ
TLLI, N-PDU, protect, cipher
7.4.2.16
LL-UNITDATA-IND
TLLI, N-PDU
7.4.2.17
LL-STATUS-IND
TLLI, cause
7.4.2.18 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.1 LL-ESTABLISH-REQ | A LLC SABM frame will be sent to establish the LLC ABM mode. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.2 LL-ESTABLISH-CNF | A LLC UA frame is received, the LLC ABM mode has been established. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.3 LL-ESTABLISH-IND | A LLC SABM frame is received. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.4 LL-ESTABLISH-RSP | A LLC UA frame will be sent, the ABM mode is established. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.5 LL-RELEASE-REQ | A LLC DISC frame will be sent to change to LLC ADM mode. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.6 LL-RELEASE-CNF | The LLC link has been disconnected, LLC is in ADM mode. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.7 LL-RELEASE-IND | LLC is in idle mode. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.8 LL-XID-REQ | An LLC XID frame will be sent. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.9 LL-XID-IND | An LLC XID frame is received. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.10 LL-XID-RSP | An LLC XID frame will be sent as a reply to a received XID frame. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.11 LL-XID-CNF | An LLC XID frame has been received as a reply to a sent XID frame. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.12 LL-DATA-REQ | An LLC I frame will be sent to the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.13 LL-DATASENT-IND | The sent LLC frame was sent with the V(S) indicated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.14 LL-DATA-CNF | Successful reception of an LLC I frame has been acknowledged by the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.15 LL-DATA-IND | An LLC I frame has been received form the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.16 LL-UNITDATA-REQ | An LLC UI frame will be sent to the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.17 LL-UNITDATA-IND | An LLC UI frame has been received from the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.4.2.18 LL-STATUS-IND | Indication used by LLC to transfer LLC failures to the SNDCP sublayer. The failure may also be caused due to errors at the RLC/MAC layer. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5 Session Management Services for GPRS and MBMS | On the network side Session Management Services are provided at the SNSM-SAP and SMREG-SAP. At the SMREG-SAP, the assumption taken is that the MS initiated primary and secondary PDP context activation, the MS initiated PDP context modification and deactivation, and the MBMS context activation and deactivation are not visible, i.e. the service for these functions on the network side stops in the SM sublayer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.1 Session Management Services for SMREG-SAP | Table 7.5.1: Primitives and Parameters at SMREG-SAP - network side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
SMREG-PDP-ACTIVATE-REQ
PDP address, APN, protocol configuration options
7.5.1.1
SMREG-PDP-ACTIVATE-REJ
Cause, PDP address, APN, protocol configuration options
7.5.1.2
SMREG-PDP-DEACTIVATE-REQ
NSAPI(s), teardown indicator, cause, protocol configuration options, MBMS protocol configuration options
7.5.1.3
SMREG-PDP-DEACTIVATE-CNF
NSAPI(s) , protocol configuration options, MBMS protocol configuration options
7.5.1.4
SMREG-PDP-MODIFY-REQ
QoS, NSAPI, protocol configuration options
7.5.1.5
SMREG PDP-MODIFY-CNF
NSAPI, protocol configuration options
7.5.1.6
SMREG PDP-MODIFY-REJ
NSAPI, protocol configuration options
7.5.1.7
SMREG-MBMS-ACTIVATE-REQ
Multicast address, APN, MBMS protocol configuration options
7.5.1.8
SMREG-MBMS-ACTIVATE-REJ
Cause, multicast address, APN, MBMS protocol configuration options
7.5.1.9 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.1.1 SMREG-PDP-ACTIVATE-REQ | The network initiates a PDP context activation. SM is requested to send the REQUEST PDP CONTEXT ACTIVATION message to the MS. The PDP context is pending activation. The network expects that the MS continues with a normal MS initiated PDP context activation. Therefore, at the SMREG-SAP no confirmation is provided. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.1.2 SMREG-PDP-ACTIVATE-REJ | The network initiated PDP context activation failed. Either the REQUEST PDP CONTEXT ACTIVATION REJECT message was received from the MS, or lower layer failure or timer expiry caused abortion of the PDP context activation procedure. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.1.3 SMREG-PDP-DEACTIVATE-REQ | The network initiates a PDP or MBMS context deactivation. SM is requested to send a DEACTIVATE PDP CONTEXT REQUEST message. The PDP context is pending deactivation. Presence of the teardown indicator will lead to deactivation of all PDP contexts coupled to the identified PDP address. NSAPI(s) to be deallocated from the SNDCP entity via the SNSM-SAP for the GSM case, are included in the primitive. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.1.4 SMREG-PDP-DEACTIVATE-CNF | The network initiated PDP or MBMS context deactivation has been concluded. The MS confirmed the PDP context deactivation, i.e. the DEACTIVATE PDP CONTEXT ACCEPT message was received. Then SM ordered SNDCP to locally release LLC link(s) not further needed for the GSM case. In the UMTS case, release of affected GTP-U tunnel(s) towards the RNC has taken place. The PDP context is deactivated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.1.5 SMREG-PDP-MODIFY-REQ | The network initiates a modification of the PDP context. SM is requested to send a MODIFY PDP CONTEXT REQUEST message to the MS. The PDP context is pending modification. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.1.6 SMREG-PDP-MODIFY-CNF | The PDP context modification has been concluded. The MS confirmed the PDP context modification, i.e. the MODIFY PDP CONTEXT ACCEPT message was received. Then, for the GSM case, SM ordered SNDCP to adjust the affected LLC link as required. For the UMTS case, RAB properties were updated as required. The PDP context is modified. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.1.7 SMREG-PDP-MODIFY-REJ | The PDP context modification has been rejected. Due to timer expiry or lower layer failure the modification procedure has been aborted. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.1.8 SMREG-MBMS-ACTIVATE-REQ | The network initiates an MBMS context activation. SM is requested to send the REQUEST MBMS CONTEXT ACTIVATION message to the MS. The MBMS context is pending activation. The network expects that the MS continues with the MBMS context activation. Therefore, at the SMREG-SAP no confirmation is provided. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.1.9 SMREG-MBMS-ACTIVATE-REJ | The network initiated MBMS context activation failed. Either the REQUEST MBMS CONTEXT REJECT message was received from the MS, or lower layer failure or timer expiry caused abortion of the MBMS context activation procedure. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.5.2 Session Management Services for SNSM-SAP | The SNSM-SAP service primitives are defined in 3GPP TS 44.065 [12a]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.6 Location services at the Network side | The location services (e.g. network initiation of timing related measurements in a type A LMU) are provided at the service access point MNLCS-SAP. The service provided by the CM sublayer to support the location services is defined in 3GPP TS 44.071 [8a] (for communication with a type A LMU only). |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.6.1 Service state diagram | The primitives provided by the call independent Location Services Support entity and the transitions between permitted states are shown in the service graph of figure 7.6 below.
STATES:
IDLE ‑ No LCS signalling transaction pending.
CONN ‑ LCS signalling transaction established.
Figure 7.6: Service graph of the Location Services Support entity ‑ Network side |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.6.2 Service primitives | Table 7.6: Primitives and Parameters at MNLCS‑SAP ‑ Network side
PRIMITIVES
PARAMETERS
(Info elements of message)
REFERENCE
MNLCS_BEGIN_REQ
REGISTER
7.6.2.1
MNLCS_BEGIN_IND
REGISTER
7.6.2.2
MNLCS_FACILITY_REQ
FACILITY
7.6.2.3
MNLCS_FACILITY_IND
FACILITY
7.6.2.4
MNLCS_END_REQ
RELEASE COMPLETE
7.6.2.5
MNLCS_END_IND
RELEASE COMPLETE
7.6.2.6 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.6.2.1 MNLCS_BEGIN_REQ | Request to send a REGISTER message in order to establish a signalling transaction for the provision of location services. The request for a location service invocation may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.6.2.2 MNLCS_BEGIN_IND | Receipt of a REGISTER message, a signalling transaction is established for the provision of location services. The indication of a location service invocation may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.6.2.3 MNLCS_FACILITY_REQ | Request to send a FACILITY message for the provision of a location service facility. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.6.2.4 MNLCS_FACILITY_IND | Receipt of a FACILITY message, a location service facility has been requested. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.6.2.5 MNLCS_END_REQ | Request to send a RELEASE COMPLETE message in order to release the signalling transaction by sending a RELEASE COMPLETE message. The request for transfer of a location service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.6.2.6 MNLCS_END_IND | Indication that the signalling transaction has been released after receipt of a RELEASE COMPLETE message. The indication of a location service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 8 Services assumed from signalling layers 1 and 2 | The services provided by layer 2 are defined in detail in 3GPP TS 44.005 [4]. A short summary is given below.
In addition, layer 1 communicates directly with layer 3 for information transfer related to channel management and to measurement control. See clause 8.5 below. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 8.1 Priority | Messages from layer 3 can be sent with:
- no priority;
i.e. the messages are sent in first‑in‑first‑out order;
- priority;
i.e. a message with this indication is sent as early as possible by layer 2. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 8.2 Unacknowledged information transfer | Transfer of unacknowledged information using the primitives DL_UNIT_DATA_ REQUEST/INDICATION. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 8.3 Acknowledged information transfer | Transfer of information in multiframe acknowledged mode including:
- establishment of data link connection between L3 entities;
- transfer of information in acknowledged mode;
- release of the data link connection.
The primitives associated with acknowledged information transfer are:
- DL_ESTABLISH_REQUEST/INDICATION/CONFIRM for establishment of acknowledged mode;
- DL_DATA_REQUEST/INDICATION for requesting the transmission of a message unit and for indicating the reception of a message unit;
- DL_SUSPEND_REQUEST/DL_RELEASE_CONFIRM for requesting and confirming the suspension of the acknowledged information transfer in the MS upon channel change;
- DL_RESUME_REQUEST/DL_ESTABLISH_CONFIRM for requesting and confirming the resumption of the acknowledged information transfer in the MS after suspension at channel change;
- DL_RELEASE_REQUEST/INDICATION/CONFIRM for the termination of acknowledged mode operation;
- DL_RECONNECT_REQUEST for requesting the re-establishment of acknowledged information transfer in the MS on the old channel after channel change failure. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 8.4 Random access | The transmission/reception of a random access burst is controlled by the primitives DL_RANDOM_ACCESS_REQUEST/INDICATION/CONFIRM. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 8.5 Channel management and measurements | The management of channels, i.e. their activation, deactivation, configuration, deconfiguration, through‑connection and disconnection is controlled by the RR sublayer in layer 3. The measurements performed by the physical layer are also controlled by the RR sublayer of layer 3 and they are reported to layer 3.
These functions use the primitives MPH_INFORMATION_REQUEST/INDICATION/CONFIRMATION. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9 Interlayer service interfaces on the MS side | In addition to the services described in this clause, the RR entity and MM entity also provide services to CM entities which do not 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.1.2 Service primitives | Table 9.1: Primitives and parameters at the RR‑SAP ‑ MS side
PRIMITIVES
PARAMETERS
REFERENCE
RR_EST_REQ
Layer 3 message transferred in the SABM frame, CN domain identity
9.1.2.1
RR_EST_IND
‑
9.1.2.2
RR_EST_CNF
‑
9.1.2.3
RR_REL_IND
cause
9.1.2.4
RR_SYNC_IND
cause (ciphering, res. ass., channel mode modify), list of (RAB ID, NAS Synchronization Indicator, maximum data rate)
9.1.2.5
RR_DATA_REQ
Layer 3 message, local flow identifier CN domain identity
9.1.2.6
RR_DATA_IND
Layer 3 message, CN domain identity
9.1.2.7
RR_UNIT DATA_IND
Layer 3 message
9.1.2.8
RR_ABORT_REQ
cause
9.1.2.9
RR_ABORT_IND
cause
9.1.2.10
RR_ACT_REQ
reselection mode
9.1.2.11 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.1.2.1 RR_EST_REQ | In A/Gb mode it 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.
In Iu mode it is used by the Mobility Management entity to request the establishment of a signalling connection to the CN domain type given in the parameter CN domain identity. The request shall be given only if no signalling connection to the specific CN domain type is established. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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);
- integrity protection has been started (integrity) (UMTS only);
- a traffic channel has been assigned (res. ass. = "resource assigned");
- the channel mode has been modified (channel mode modify).
In Iu mode, in case of a resource assignment or channel mode modification, RR indicates to the Mobility Management entity the list of RAB IDs and, optionally,
- the NAS Synchronization Indicators associated with the assigned or modified radio bearers; or
- the maximum data rate (at RLC layer) associated with the assigned or modified radio bearers, if no NAS Synchronization Indicator is available.
9.1.2.5a Void
9.1.2.5b Void |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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.
For UMTS, RR_DATA_IND is also used to indicate whether control-data has been:
- successfully integrity checked;
- unsuccessfully integrity checked;
- received with no integrity protection.
9.1.2.7a Void |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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
PRIMITIVES
PARAMETERS
REFERENCE
CTS_RR_ALIVE_CHECK_IND
‑
9.1.3.1 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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.
NOTE: The LCS protocol entities for communication between a type A LMU and the network would be included in the figure in the same manner as the protocol entities for CC, SS and SMS.
Figure 9.3: Services provided at the MMCC‑SAP, MMSS‑SAP, MMLCS-SAP, MMSMS‑SAP ‑ MS side |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.2.2 Service primitives | Table 9.2: Primitives and Parameters at MMCC‑SAP, MMSS‑SAP (for type A LMU), MMLCS-SAP or MMSMS‑SAP ‑ MS side
PRIMITIVES
PARAMETERS
REFERENCE
MMXX_EST_REQ (see note 1)
Parameters for the appropriate CM SERVICE REQUEST (if any)
9.2.2.1
MMXX_EST_IND (see note 1)
First CM message
9.2.2.2
MMXX_EST_CNF (see note 1)
‑
9.2.2.3
MMXX_REL_REQ (see note 1)
cause
9.2.2.4
MMXX_REL_IND (see note 1)
cause
9.2.2.5
MMXX_DATA_REQ (see note 1)
Layer 3 message
9.2.2.6
MMXX_DATA_IND (see note 1)
Layer 3 message
9.2.2.7
MMXX_UNIT_DATA_REQ (see note 1)
Layer 3 message
9.2.2.8
MMXX_UNIT_DATA_IND (see note 1)
Layer 3 message
9.2.2.9
MMCC_SYNC_IND (see note 2)
cause: res.ass; list of (RAB ID, NAS Synchronization Indicator, maximum data rate)
9.2.2.10
MMXX_REEST_REQ (see note 1)
9.2.2.11
MMXX_REEST_CNF (see note 1)
9.2.2.12
MMXX_ERR_IND (see note 1)
cause
9.2.2.13
MMXX_PROMPT_IND (see note 1)
-
9.2.2.14
MMXX_PROMPT_REJ (see note 1)
-
9.2.2.15
NOTE 1: MMXX is used as substitution for MMCC, MMSS, MMLCS or MMSMS.
NOTE 2: Only at MMCC‑SAP. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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). |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.2.2.6 MMXX_DATA_REQ | Request used by the CC, SS or SMS entities for acknowledged control‑data transmission. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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).
In Iu mode, MM indicates the list of the RAB IDs and, optionally,
- the NAS Synchronization Indicators associated with the assigned or modified radio bearers; or
- the maximum data rate (at RLC layer) associated with the assigned or modified radio bearers, if no NAS Synchronization Indicator is available.
During a network-initiated in-call modification the CC entity uses the NAS Synchronization Indicator or the maximum data rate to determine whether a suitable channel for the new call mode is available. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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". |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3 Services provided by radio resource management entity for GPRS services | The service primitives for UMTS are defined in the present document. The services provided by the Access Stratum (AS) are specified in 3GPP TS 23.110 [20]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.1 Service primitives for GRR-SAP (GSM only) | The GRR-SAP service primitives are defined in 3GPP TS 44.064 [11a]
[[Table 9.3.1, and chapters 9.3.1.1 - 9.3.1.5 are Void] |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.2 Service primitives for GMMRR-SAP (GSM only) | Table 9.3.2: Primitives and Parameters at GMMRR-SAP - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
GMMRR-ASSIGN-REQ
newTLLI
9.3.2.1
GMMRR-PAGE-IND
TLLI
9.3.2.2 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.2.1 GMMRR-ASSIGN-REQ | A new TLLI is assigned to the RR sublayer. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.2.2 GMMRR-PAGE-IND | A RR-paging message has been received by the RR sublayer. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.3 Service primitives for RABMAS-SAP (UMTS only) | Table 9.3.3: Primitives and parameters at RABMAS-SAP
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
RABMAS-RAB-ESTABLISH-IND
RAB ID list
9.3.3.1
RABMAS-RAB-ESTABLISH-RES
-
9.3.3.2
RABMAS-RAB-ESTABLISH-REJ
9.3.3.3
RABMAS-RAB-RELEASE-IND
RAB ID list
9.3.3.4
RABMAS-RAB-RELEASE-RES
-
9.3.3.5
RABMAS-STATUS-IND
Cause
9.3.3.6 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.3.1 RABMAS-RAB-ESTABLISH-IND | Indication from the Access Stratum layer that radio access bearer setup for the indicated list of RAB IDs (contains NSAPI) has commenced. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.3.2 RABMAS-RAB-ESTABLISH-RES | Response (to RABMAS-RAB-ESTABLISH-IND) used by the RABM entity to inform the Access Stratum sublayer that the indicated NSAPI (in RAB ID) is currently or has been activated by the SM. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.3.3 RABMAS-RAB-ESTABLISH-REJ | Response (to RABMAS-RAB-ESTABLISH-IND) used by the RABM entity to inform the Access Stratum sublayer that all of the NSAPIs, indicated by RAB ID list in the received RABMAS-RAB-ESTABLISH-IND, have not been activated by the SM-layer and the attempt to setup the radio access bearers shall be rejected. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.3.4 RABMAS-RAB-RELEASE-IND | Indication from the Access Stratum layer that a radio access bearer for the indicated NSAPI has been released. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.3.5 RABMAS-RAB-RELEASE-RES | Response used by the RABM entity to inform the Access Stratum sublayer that the indicated RAB ID has been released in the RABM. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.