hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.3.6 RABMAS-STATUS-IND | Indication used by the AS sublayer to transfer failures to the RABM. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4 Service primitives for GMMAS-SAP (UMTS only) | Table 9.3.4: Service primitives and parameters at GMMAS-SAP - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
GMMAS-SECURITY-IND
9.3.4.1
GMMAS-SECURITY-RES
CK, IK
9.3.4.2
GMMAS- ESTABLISH-REQ
Layer 3-PDU, Establishment cause, Priority, CN Domain Identity, MS Identity, LAI/RAI
9.3.4.3
GMMAS- ESTABLISH-CNF
9.3.4.4
GMMAS- ESTABLISH-REJ
9.3.4.5
GMMAS- RELEASE-REQ
CN Domain identity
9.3.4.6
GMMAS- RELEASE-IND
Cause
9.3.4.7
GMMAS- DATA-REQ
Layer 3-PDU, Priority, CN Domain identity
9.3.4.8
GMMAS- DATA-IND
Layer 3-PDU
9.3.4.9
GMMAS-PAGE-IND
MS Identity type, Paging Cause
9.3.4.10
GMMAS-STATUS-IND
Cause
9.3.4.11 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.1 GMMAS-SECURITY-IND | Indication from the AS sublayer that ciphering (and integrity protection) shall be started. The GMM sublayer uses this primitive as an indication of the completion of the service request procedure. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.2 GMMAS-SECURITY-RES | Ciphering and integrity keys are assigned to the AS sublayer to enable ciphering (and integrity protection). |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.3 GMMAS-ESTABLISH-REQ | To establish a signalling connection and to carry the initial Layer 3-PDU over the radio interface. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.4 GMMAS-ESTABLISH-CNF | Confirmation from the AS sublayer that a PS signalling connection has been established. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.5 GMMAS-ESTABLISH-REJ | The attempt to establish a PS signalling connection was rejected by the network. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.6 GMMAS- RELEASE-REQ | Request used by the MM-sublayer to request the release of the PS signalling connection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.7 GMMAS- RELEASE-IND | Indication from the AS sublayer that the PS signalling connection has been released. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.8 GMMAS- DATA-REQ | Request used by the MM-sublayer for transfer of data. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.9 GMMAS- DATA-IND | Indication used by the AS sublayer to transfer received data to MM sublayer. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.10 GMMAS-PAGE-IND | A paging message has been received by the AS sublayer. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.3.4.11 GMMAS-STATUS-IND | Indication used by the AS sublayer to transfer failures to the MM sublayer. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.4 Services provided by the LLC entity for GPRS services (GSM only) | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.4.1 Service primitives for LLGMM-SAP | Table 9.4.1: Primitives and parameters at LLGMM-SAP - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
LLGMM-ASSIGN-REQ
oldTLLI, newTLLI, Kc, RAND, Ciphering Algorithm
9.4.1.1
LLGMM-TRIGGER-REQ
Cause
9.4.1.2
LLGMM-SUSPEND-REQ
TLLI
9.4.1.4
LLGMM-RESUME-REQ
TLLI
9.4.1.5
LL-UNITDATA-REQ
TLLI, GMM-PDU, protect, cipher
9.4.1.8
LL-UNITDATA-IND
TLLI, GMM-PDU, cipher
9.4.1.9
LLGMM-STATUS-IND
TLLI, cause
9.4.1.10 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.4.1.3 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.4.1.5 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.4.1.6 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.4.1.8 LL-UNITDATA-REQ | Request to send a GMM message in unacknowledged mode to the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.4.1.9 LL-UNITDATA-IND | A GMM message in unacknowledged mode has been received from the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.4.2 Service primitives for LLSMS-SAP | Table 9.4.2: Service primitives and parameters at LLSMS-SAP - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
LL-UNITDATA-REQ
TLLI, SMS-CP-PDU, protect, cipher
9.4.2.1
LL-UNITDATA-IND
TLLI, SMS-CP-PDU,
9.4.2.2 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.4.2.1 LL-UNITDATA-REQ | An LLC UI frame will be sent to the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.4.2.2 LL-UNITDATA-IND | An LLC UI frame has been received from the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5 Services provided by the GMM for GPRS services | The GPRS Mobility Management (GMM) sublayer provides services to the Session Management (SM) entity, Supplementary Service (SS) entity and the Short Message Service Support (GSMS) entity for message transfer. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.1 Service primitives for GMMSM-SAP | Session Management services may request GPRS service registration or perform procedures needed to activate a multicast service before activating a PDP or an MBMS context.
Table 9.5.1: Primitives and parameters at GMMSM-SAP - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
GMMSM-ESTABLISH-REQ
-
9.5.1.1
GMMSM-ESTABLISH-CNF
-
9.5.1.2
GMMSM-ESTABLISH-REJ
cause
9.5.1.3
GMMSM-RELEASE-IND
-
9.5.1.4
GMMSM-UNITDATA-REQ
SM-PDU
9.5.1.5
GMMSM-UNITDATA-IND
SM-PDU
9.5.1.6 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 request from Session Management, e.g. a requested PDP context activation or MBMS context activation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 the Session Management request, e.g. the PDP context activation or the MBMS context activation.. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.1.3 GMMSM-ESTABLISH-REJ | The network has rejected the attach. The MS has received the ATTACH REJECT message. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 context(s) and the MBMS context(s), if any, are not valid anymore. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.2 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
GMMSMS-REG-STATE-REQ
-
9.5.3.1
GMMSM- REG-STATE -RSP
Registration state
9.5.3.2 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.3.1 GMMSMS-REG-STATE-REQ | Request for the current IMSI registration state from the Short Message entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.3.2 GMMSM- REG-STATE -RSP | The current IMSI registration state is sent to the Short Message entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.4 Service primitives for PMMSMS-SAP | Table 9.5.4: Primitives and Parameters at PMMSMS‑SAP ‑ MS side
PRIMITIVES
PARAMETERS
(message, info elements of message, other parameters)
REFERENCE
PMMSMS_EST_REQ
Mobile-ID
9.5.4.1
PMMSMS_EST_CNF
-
9.5.4.2
PMMSMS_ERROR_IND
Cause
9.5.4.3
PMMSMS_UNITDATA_REQ
SMS-PDU
9.5.4.4
PMMSMS_UNITDATA_IND
SMS-PDU
9.5.4.5 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.4.1 PMMSMS_EST _REQ | The GMM is requested to establish a PS signalling conection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.4.2 PMMSMS_EST _CNF | The GMM indicates a PS signalling connection is established. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.4.3 PMMSMS_ERROR_IND | The GMM indicates that a PS signalling connection has been released. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.4.4 PMMSMS_UNITDATA_REQ | The GMM is requested to forward a SMS PDU in order to send it to the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.4.5 PMMSMS_UNITDATA_IND | Indication used by GMM to transfer the received data to the GSMS entities. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.5 Service primitives for GMMRABM-SAP (UMTS only) | Table 9.5.5: Service primitives and parameters at GMMRABM-SAP – MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
GMMRABM-REESTABLISH-REQ
9.5.5.1
GMMRABM-REESTABLISH-RSP
9.5.5.2
GMMRABM-REESTABLISH-REJ
Cause
9.5.5.3
NOTE: Confirmation to the RABMGMM-REESTABLISH-REQ is given to the RABM in the form of indications from the AS sublayer that establishment of RABs has commenced or been completed. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.5.1 GMMRABM-REESTABLISH-REQ | This primitive is used by the RABM entity to inform the GMM sublayer that UL user data has been received for an NSAPI without an active RAB. GMM shall initiate a service request procedure to re-establish the RAB for the NSAPI(S). |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.5.2 GMMRABM-REESTABLISH-RSP | This primitive is used by the GMM sublayer to inform the RABM entity that the reception of the Service Request message has been acknowledged by the network. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.5.3 GMMRABM-REESTABLISH-REJ | This primitive is used by the GMM sublayer to inform the RABM entity that the re-establishment of RABs by the service request procedure has failed. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.6 Service primitives for GMMSS-SAP | Supplementary Services may request GPRS service registration before sending SS PDU.
Table 9.5.6: Primitives and parameters at GMMSS-SAP - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
GMMSS-ESTABLISH-REQ
-
9.5.6.1
GMMSS-ESTABLISH-CNF
-
9.5.6.2
GMMSS-ESTABLISH-REJ
cause
9.5.6.3
GMMSS-RELEASE-IND
-
9.5.6.4
GMMSS-UNITDATA-REQ
SS-PDU
9.5.6.5
GMMSS-UNITDATA-IND
SS-PDU
9.5.6.6 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.6.1 GMMSS-ESTABLISH-REQ | Request from Supplementary Services 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 sending of SS PDU. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.6.2 GMMSS-ESTABLISH-CNF | The network has send the ATTACH ACCEPT message to the MS, the indirect attach was successful. Now Supplementary Services can proceed with sending SS PDU. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.6.3 GMMSS-ESTABLISH-REJ | The network has rejected the attach. The MS has received the ATTACH REJECT message. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.6.4 GMMSS-RELEASE-IND | The GPRS mobility management informs the Supplementary Services that the MS has been GPRS detached, e.g. by timer expiry. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.6.5 GMMSS-UNITDATA-REQ | The GMM is requested to forward a SS PDU to lower layer in order to send it to the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.6.6 GMMSS-UNITDATA-IND | The GMM forwards a SS PDU, which has been received from the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.7 Service primitives for GMMSS2-SAP | The Supplementary Service entity may request to the MM and/or GMM entity the MM and/or GMM IMSI registration state before an SS PDU transmission is initiated from the mobile station.
Table 9.5.7: Primitives and parameters at GMMSS2-SAP - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
GMMSS2-REG-STATE-REQ
-
9.5.7.1
GMMSS2- REG-STATE -RSP
Registration state
9.5.7.2 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.7.1 GMMSS2-REG-STATE-REQ | Request for the current IMSI registration state from the Supplementary Services entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 9.5.7.2 GMM SS2- REG-STATE -RSP | The current IMSI registration state is sent to the Supplementary Services entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10 Interlayer service interfaces on the Network 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 Control and Broadcast Call Control entities.) These services are not further described in this clause. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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, channel mode modify), list of (RAB ID, NAS Synchronization Indicator)
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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.1 RR_EST_REQ | Request used by the Mobility Management entity to request establishment of control channel connections. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.2 RR_EST_IND | Indication to the Mobility Management entity that the establishment of control channel connections has been done. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.3 RR_EST_CNF | Confirmation used by RR to confirm the establishment of a requested control channel connection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.4 RR_REL_REQ | Request used by the Mobility Management to release a control channel connection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.5 RR_REL_IND | Indication from RR to MM that the main signalling link has been released. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.6 RR_SYNC_REQ | Request used by the Mobility Management entity for synchronization with the RR protocol.
In Iu mode, in case of resource assignment or channel mode modification, Mobility Management includes the list of the RAB IDs and, optionally, the NAS Synchronization Indicators associated with the radio bearers to be assigned or modified. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.7 RR_SYNC_CNF | Confirmation used by RR that the requested synchronization is done. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.8 RR_DATA_REQ | Request used by the Mobility Management entity for acknowledged control‑data transmission. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.10 RR_UNIT_DATA_REQ | Request used by the Mobility Management entity for unacknowledged control‑data transmission. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.12 RR_ABORT_REQ | Request of the abandon of the RR connection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.1.2.13 RR_ABORT_IND | Indication that a radio link failure has occurred. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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.
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 10.3: Services provided at MMCC‑SAP, MMSS‑SAP, MMLCS-SAP, MMSMS‑SAP ‑ Network side |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.2.1 Service state diagram | The primitives provided by the Mobility Management entity towards Call Control, Short Messages Service Support, Location Services Support (for a 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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.2.2 Service primitives | Table 10.2: Primitives and Parameters at MMCC‑SAP, MMSS‑SAP, MMLCS-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), list of (RAB ID, NAS Synchronization Indicator)
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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.2.2.2 MMXX_EST_IND | Indication by the MM sublayer that a MM connection is established. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.2.2.3 MMXX_EST_CNF | Confirmation of the MM connection establishment by the MM sublayer. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.2.2.5 MMXX_REL_IND | Indication by the MM sublayer that a MM connection has been released. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.2.2.10 MMCC_SYNC_REQ | Request used by the CC entity to synchronize with the MM entity (resource assign).
In Iu mode, the CC entity includes the list of the RAB IDs and, optionally, the NAS Synchronization Indicators associated with the requested radio bearers. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.2.2.11 MMCC_SYNC_CNF | Confirmation used by the MM to inform the CC entity that synchronization is completed (resource assign). |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.3 Services provided by radio resource management entity for GPRS services | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.3.1 Service primitives for GRR-SAP | The GRR-SAP service primitives are defined in 3GPP TS 44.064 [11a]
[Table 10.3.1, and chapters 10.3.1.1 - 10.3.1.5 are Void] |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.3.2.1 GMMRR-PAGE-REQ | Request by GMM to send a RR-paging message to the mobile station. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4 Services provided by the LLC entity for GPRS services | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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-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
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 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 10.4.1.2 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.