hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.10 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.11 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.12 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.13 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.14 SMREG-PDP-ACTIVATE-REJ-RSP | The network requested PDP context activation failed. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.15 SMREG-PDP-ACTIVATE-SEC-REQ | The MS initiates a secondary PDP context activation. SM is requested to send the ACTIVATE SECONDARY PDP CONTEXT REQUEST message to the network. The PDP context is pending activation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.16 SMREG-PDP-ACTIVATE-SEC-CNF | The MS initiated secondary PDP context activation succeeded. The network confirmed the PDP context activation, i.e. the ACTIVATE SECONDARY PDP CONTEXT ACCEPT message was received from the network. In GSM, this implies that SM has ordered SNDCP to establish the needed LLC link. In the UMTS case, this implies that the RLC link towards the RNC has been established and that the SM has been informed about this from the RABM service entity in the MS. (RABM- RAB Management service entity is FFS and could lead to update of the protocol architecture in figure 5.2 and 5.3) The PDP context connected to the same PDP address as the PDP context identified by the primary NSAPI parameter in SMREG-PDP-ACTIVATE-SEC-REQ is active. ('Primary NSAPI' will point to any one of the other established PDP contexts for a given PDP address). |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.17 SMREG-PDP-ACTIVATE-SEC-REJ | The secondary PDP context activation failed, the PDP context is not activated. One reason for failure is that the network rejected the activation attempt, which means the ACTIVATE SECONDARY PDP CONTEXT REJECT message was received. Another reason is e.g. that it was not possible to establish the needed LLC link in the GSM case. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.18 SMREG-PDP-MODIFY-REQ | An MS initiated PDP context modification is requested. The MODIFY PDP CONTEXT REQUEST message is sent to the network and pending acceptance. Affected PDP context is identified via the NSAPI value included in the primitive. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.19 SMREG-PDP-MODIFY-CNF | An MS initiated PDP context modification has been accepted by the network. The modification is acknowledged from the network via the MODIFY PDP CONTEXT ACCEPT message. The addressed PDP context has been modified. LLC or RLC link is adjusted according to the QoS returned from the network. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.20 SMREG-PDP-MODIFY-REJ | An MS initiated PDP context modification has been rejected by the network. The rejection is signalled from the network via the MODIFY PDP CONTEXT REJECT message with the cause code. The PDP context remains active without change of QoS. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.21 SMREG-MBMS-ACTIVATE-REQ | The MS initiates an MBMS context activation as requested by the network. SM is requested to send the ACTIVATE MBMS CONTEXT REQUEST message to the network. The MBMS context is pending activation waiting for the network confirmation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.22 SMREG-MBMS-ACTIVATE-CNF | The MBMS context activation succeeded. The network confirmed the MBMS context activation, i.e. the ACTIVATE MBMS CONTEXT ACCEPT message was received from the network. The MBMS context is active. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.23 SMREG-MBMS-ACTIVATE-REJ | The MBMS context activation failed, the MBMS context is not activated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.24 SMREG-MBMS-ACTIVATE-REJ-RSP | The network requested MBMS context activation failed. SM is requested to send the REQUEST MBMS CONTEXT ACTIVATION REJECT message to the network. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.25 SMREG-MBMS-ACTIVATE-IND | The network asked for an MBMS context activation. The REQUEST MBMS CONTEXT ACTIVATION message was received from the network. The MS reacts either by initiating the activation of the MBMS context or by rejecting the request from the network.
The Session Management services provided at the service access point SMREG-SAP are illustrated in the state machines of figures 6.4 and 6.5 below. Note, that each state machine describes only one PDP/MBMS context within the SM entity.
Figure 6.4: Session Management service states at the SMREG-SAP for GPRS PDP context handling ‑ MS side
Figure 6.5: Session Management service states at the SMREG-SAP for MBMS context handling ‑ MS side |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.2 Session Management Services for SNSM-SAP (GSM only) | The SNSM-SAP service primitives are defined in 3GPP TS 44.065 [12a]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.3 Session Management Services for RABMSM-SAP (UMTS only) | Table 6.5.3: Service primitives and parameters at RABMSM-SAP - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
Reference
RABMSM-ACTIVATE-IND
NSAPI, QoS
6.5.3.1
RABMSM-ACTIVATE-RSP
NSAPI
6.5.3.2
RABMSM-DEACTIVATE-IND
NSAPIs
6.5.3.3
RABMSM-DEACTIVATE-RSP
NSAPIs
6.5.3.4
RABMSM-DEACTIVATE-REQ
NSAPI
6.5.3.5
RABMSM-MODIFY-IND
NSAPI, QoS
6.5.3.6
RABMSM-MODIFY-RSP
-
6.5.3.7
RABMSM-STATUS-REQ
- Cause
6.5.3.8 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.3.1 RABMSM-ACTIVATE-IND | Indication used by the SM entity to inform the RABM entity that an NSAPI has been activated for data transfer (e.g. an activate PDP Context request has been sent to the network). It also informs the RABM entity about the requested QoS profile for this NSAPI. The indication is sent by SM towards RABM during an ongoing PDP context activation procedure. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.3.2 RABMSM-ACTIVATE-RSP | Response used by the RABM entity to inform the SM entity that the indicated NSAPI is now in use and that a RAB for the indicated NSAPI is established. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.3.3 RABMSM-DEACTIVATE-IND | Indication used by the SM entity to inform the RABM entity that an NSAPIs has been de-allocated and cannot be used by the RABM entity anymore. The request is sent by SM towards RABM during an ongoing MS initiated as well as network initiated PDP context de-activation procedure or during local de-activation of a PDP context. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.3.4 RABMSM-DEACTIVATE-RSP | This message is the response to RABMSM-DEACTIVATE-IND used by the RABM entity to inform the SM entity that the NSAPI indicated is no longer in use. It is either sent immediately when there is no corresponding bearer active or it is sent after reception and processing of RABMAS-RAB-RELEASE-IND from access stratum. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.3.5 RABMSM-DEACTIVATE-REQ | This primitive is used by the RABM entity to inform the SM entity that the RAB for an NSAPI has been released. This primitive is only sent for bearer with a RT-QoS classes. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.3.6 RABMSM-MODIFY-IND | Indication used by the SM entity to indicate the change of the QoS for an NSAPI. The indication is sent by SM towards RABM during an ongoing PDP context modification procedure. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.3.7 RABMSM-MODIFY-RSP | Response used by the RABM entity to inform the SM entity that the indicated NSAPI and QoS profile are now in use and the RAB for the NSAPI is established and/or released, if necessary. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.3.8 RABMSM-STATUS-REQ | This primitive is used by the RABM entity to inform the SM entity that RABM cannot continue its operation due to errors at the lower layer (i.e. Access Stratum) or at the RABM layer. The Cause parameter indicates the cause of the error. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.6 Registration Services for GPRS-Services | The attach/detach procedures comprise the registration services which are provided at the GMMREG-SAP.
It shall be noted, that the registration services for mobiles of class A or B may depend on the service states for GPRS and non-GPRS services. Therefore the internal access points MMCOORD and the GMMCOORD (see figure 5.3) are used by GMM and MM to inform each other about the relevant conditions. No service primitives between the entities within the same sublayer, i.e. the MM sublayer, are defined in the present document. The Mobility Management for class A and B mobiles is further specified in 3GPP TS 24.008 [6]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.6.1 Registration Services for GMMREG-SAP | Table 6.6.1: Service primitives and parameters at GMMREG-SAP - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
GMMREG-ATTACH-REQ
attach-type, READY-timer, STANDBY-timer
6.6.1.1
GMMREG-ATTACH-CNF
PLMNs MT-caps, attach-type.
6.6.1.2
GMMREG-ATTACH-REJ
cause
6.6.1.3
GMMREG-DETACH-REQ
detach-type, power-off/normal-detach
6.6.1.4
GMMREG-DETACH-CNF
detach-type
6.6.1.5
GMMREG-DETACH-IND
detach-type
6.6.1.6 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.6.1.1 GMMREG-ATTACH-REQ | MS initiates the GPRS and/or IMSI attach. GMM is requested to send an ATTACH REQUEST message to the network. The attachment is registration pending in the MS. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.6.1.2 GMMREG-ATTACH-CNF | The attach (either GPRS-attach or IMSI-attach or both) was successful. The network confirmed the attach, i.e. the ATTACH ACCEPT message was received by the MS. The LLC and RR sublayer will be informed by GMM about the TLLI to be used. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.6.1.3 GMMREG-ATTACH-REJ | The attach (either GPRS-attach or IMSI-attach or both) has failed. The network rejected the attach attempt, i.e. the message ATTACH REJECT was received from the network. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.6.1.4 GMMREG-DETACH-REQ | MS initiates GPRS and/or IMSI detach: GMM is requested to send a DETACH REQUEST message, the detach procedure is initiated. In case of MS initiated detach at power-off, the procedure is terminated in the MS after sending the DETACH REQUEST message. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.6.1.5 GMMREG-DETACH-CNF | The MS initiated detach (either GPRS-attach or IMSI-attach or both) has been completed.
The network confirmed the detach, i.e. the message DETACH ACCEPT was received from the network. This finalizes the detach procedure (normal, not at power off). Any PDP context possibly activated before is deactivated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.6.1.6 GMMREG-DETACH-IND | A network initiated detach has been performed. Or the detach has been performed locally due to expiration of the standby timer or a failed routing area update. In the first case the DETACH REQUEST message was from the network. Any PDP context possibly activated before is deactivated.
The registration services provided at the service access point GMMREG-SAP are illustrated in the state machine of figure 6.6 below. Note, that in state registered the MS may be suspended from GPRS mobility management due to an ongoing CS connection. The registration procedure Routing Area Updating, which is not provided at the GMMREG-SAP, is not visible within the diagram.
Figure 6.6: Registration services states at GMMREG-SAP for GPRS attach and detach - MS side |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7 Services provided to SNDCP 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.
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 | 6.7.1 Service state diagram for QoS1-SAP, QoS2-SAP, QoS3-SAP and QoS4-SAP | Figure 6.7: States to establish and release ABM mode operation |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2 Service primitives for QoS1-SAP, QoS2-SAP, QoS3-SAP and QoS4-SAP | Table 6.7.2: Service primitives and parameters at QoS1 to QoS4 - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
LL-ESTABLISH-REQ
TLLI, SNDCP requested parameters (XID)
6.7.2.1
LL-ESTABLISH-CNF
TLLI, SNDCP negotiated parameters (XID)
6.7.2.2
LL-ESTABLISH-IND
TLLI, SNDCP requested parameters (XID), N201
6.7.2.3
LL-ESTABLISH-RSP
TLLI, SNDCP negotiated parameters (XID)
6.7.2.4
LL-RELEASE-REQ
TLLI
6.7.2.5
LL-RELEASE-CFN
TLLI
6.7.2.6
LL-RELEASE-IND
TLLI
6.7.2.7
LL-XID-REQ
TLLI, SNDCP requested parameters (XID)
6.7.2.8
LL-XID-IND
TLLI, SNDCP requested parameters (XID), N201
6.7.2.9
LL-XID-RSP
TLLI, SNDCP negotiated parameters (XID)
6.7.2.10
LL-XID-CNF
TLLI, SNDCP negotiated parameters (XID), N201
6.7.2.11
LL-DATA-REQ
TLLI, N-PDU, local reference
6.7.2.12
LL-DATA-CNF
TLLI, local reference
6.7.2.13
LL-DATA-IND
TLLI, N-PDU
6.7.2.14
LL-UNITDATA-REQ
TLLI, N-PDU, protect, cipher
6.7.2.15
LL-UNITDATA-IND
TLLI, N-PDU
6.7.2.16
LL-STATUS-IND
TLLI, cause
6.7.2.17 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.1 LL-ESTABLISH-REQ | A LLC SABM frame will be sent to establish the LLC ABM mode. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.2 LL-ESTABLISH-CNF | A LLC UA frame is received, the LLC ABM mode has been established. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.3 LL-ESTABLISH-IND | A LLC SABM frame is received. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.4 LL-ESTABLISH-RSP | A LLC UA frame will be sent, the ABM mode is established. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.5 LL-RELEASE-REQ | A LLC DISC frame will be sent to change to LLC ADM mode. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.6 LL-RELEASE-CNF | The LLC link has been disconnected, LLC is in ADM mode. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.7 LL-RELEASE-IND | LLC is in idle mode. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.8 LL-XID-REQ | An LLC XID frame will be sent. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.9 LL-XID-IND | An LLC XID frame has been received. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.10 LL-XID-RSP | An LLC XID frame will be sent as a response to a received XID frame. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.11 LL-XID-CNF | An LLC XID frame has been received as a response to a sent XID frame. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.12 LL-DATA-REQ | An LLC I frame will be sent to the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.13 LL-DATA-CNF | Successful reception of an LLC I frame has been acknowledged by the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.14 LL-DATA-IND | An LLC I frame has been received from the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.15 LL-UNITDATA-REQ | An LLC UI frame will be sent to the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.16 LL-UNITDATA-IND | An LLC UI frame has been received from the peer entity. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.7.2.17 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 | 6.8 Location services at the type A LMU side | The location services (e.g. transfer of timing related measurement information by 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]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.8.1 Service state diagram | The positioning services provided at the service access point MNLCS‑SAP are illustrated in the state diagram of figure 6.8.
STATES:
IDLE ‑ No LCS signalling transaction pending.
CONN ‑ LCS signalling transaction established.
Figure 6.8: Service graph of the Location Services Support entity ‑ type A LMU side |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.8.2 Service primitives | Table 6.8: Primitives and Parameters at MNLCS‑SAP ‑ type A LMU side
PRIMITIVES
PARAMETERS
(Info elements of message)
REFERENCE
MNLCS_BEGIN_REQ
REGISTER
6.8.2.1
MNLCS_BEGIN_IND
REGISTER
6.8.2.2
MNLCS_FACILITY_REQ
FACILITY
6.8.2.3
MNLCS_FACILITY_IND
FACILITY
6.8.2.4
MNLCS_END_REQ
RELEASE COMPLETE
6.8.2.5
MNLCS_END_IND
RELEASE COMPLETE
6.8.2.6 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.8.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 transfer of a location service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.8.2.2 MNLCS_BEGIN_IND | Receipt of a REGISTER message, a signalling transaction is established for the provision of location services after receipt of a REGISTER message. The indication of a location service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.8.2.3 MNLCS_FACILITY_REQ | Request to send a FACILITY message for the provision of a location service invocation. The request for transfer of a location service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.8.2.4 MNLCS_FACILITY_IND | Receipt of a FACILITY message, a location service facility has been requested. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.8.2.5 MNLCS_END_REQ | Request to send a RELEASE COMPLETE message in order to release the signalling transaction. The request for transfer of a location service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.8.2.6 MNLCS_END_IND | Receipt of a RELEASE COMPLETE message, the signalling transaction has been released. The indication of a location service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7 Services provided by signalling layer 3 on the Network side | In this clause, the services provided by signalling layer 3 on the network side are described which belong to the CM sub‑layer functional blocks of CC, SMS, LCS, and SS. The services corresponding to further functional blocks of the CM sublayer are not further described in this clause. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1 Call control services | The Call Control services are provided by multiple CC entities at the service access point MNCC‑SAP.
The Call Control service class consists of the following services:
- call establishment;
- call maintaining;
- call termination;
- call related Supplementary Services Support. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.1 Service state diagram | The Call Control services provided at the service access point MNCC‑SAP are illustrated in figure 7.1.
Figure 7.1: (page 1 of 2) Service graph of Call Control entity ‑ Network side
Figure 7.1: (page 2 of 2) Service graph of Call Control entity ‑ Network side |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2 Service primitives | Table 7.1: Primitives and Parameters at MNCC‑SAP ‑ Network side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
MNCC_SETUP_REQ
SETUP incl. Mobile ID or EMERGENCY SETUP
7.1.2.1
MNCC_SETUP_IND
SETUP
7.1.2.2
MNCC_SETUP_RSP
CONNECT
7.1.2.3
MNCC_SETUP_CNF
CONNECT
7.1.2.4
MNCC_SETUP_COMPL_REQ
CONNECT ACKNOWLEDGE
7.1.2.5
MNCC_SETUP_COMPL_IND
CONNECT ACKNOWLEDGE
7.1.2.6
MNCC_REJ_REQ
RELEASE COMPLETE
7.1.2.7
MNCC_REJ_IND
cause
7.1.2.8
MNCC_CALL_CONF_IND
CALL CONFIRMED
7.1.2.9
MNCC_CALL PROC_REQ
CALL PROCEEDING
7.1.2.10
MNCC_PROGRESS_REQ
PROGRESS
7.1.2.11
MNCC_ALERT_REQ
ALERTING
7.1.2.12
MNCC_ALERT_IND
ALERTING
7.1.2.13
MNCC_NOTIFY_REQ
NOTIFY
7.1.2.14
MNCC_NOTIFY_IND
NOTIFY
7.1.2.15
MNCC_DISC_REQ
DISCONNECT
7.1.2.16
MNCC_DISC_IND
DISCONNECT
7.1.2.17
MNCC_REL_REQ
RELEASE or DISCONNECT
7.1.2.18
MNCC_REL_IND
RELEASE
7.1.2.19
MNCC_REL_CNF
RELEASE or RELEASE COMPLETE
7.1.2.20
MNCC_FACILITY_REQ
facility
7.1.2.21
MNCC_FACILITY_IND
facility
7.1.2.22
MNCC_START_DTMF_IND
START DTMF
7.1.2.23
MNCC_START_DTMF_RSP
START DTMF ACK or START DTMF REJ
7.1.2.24
MNCC_STOP_DTMF_IND
STOP DTMF
7.1.2.25
MNCC_STOP_DTMF_RSP
STOP DTMF ACK
7.1.2.26
MNCC_MODIFY_REQ
MODIFY or BC‑parameter
7.1.2.27
MNCC_MODIFY_IND
BC‑parameter
7.1.2.28
MNCC_MODIFY RES
MODIFY COMPLETE
7.1.2.29
MNCC_MODIFY_CNF
BC‑parameter
7.1.2.30 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.1 MNCC_SETUP_REQ | Request to send a SETUP message to initiate Mobile terminated establishment. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.2 MNCC_SETUP_IND | Receipt of a SETUP or EMERGENCY SETUP message, the Mobile originating call establishment has been initiated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.3 MNCC_SETUP_RSP | Response to send a CONNECT message to indicate call acceptance by the remote user. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.4 MNCC_SETUP_CNF | Receipt of a CONNECT message, the Mobile terminated call has been accepted. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.5 MNCC_SETUP_COMPL_REQ | Request to send a CONNECT ACKNOWLEDGE message, the Mobile terminated call establishment has been completed. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.6 MNCC_SETUP_COMPL_IND | Indication of the receipt of a CONNECT ACKNOWLEDGE message, the Mobile originating call establishment has been completed. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.7 MNCC_REJ_REQ | Reject the Mobile originated call establishment if the call cannot be accepted. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.8 MNCC_REJ_IND | A Mobile terminated call was rejected by the MS, e.g. because of missing compatibility. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.9 MNCC_CALL_CONF_IND | Receipt of a CALL CONFIRMED message, the Mobile terminated call has been confirmed. A bearer capability different from that given in MNCC_SETUP_REQ may be offered to the remote calling user. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.10 MNCC_CALL_PROC_REQ | Request to send a CALL PROCEEDING message to indicate to the Mobile originating user that call establishment has been initiated in the Network and no more call establishment information will be accepted. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.11 MNCC_PROGRESS_REQ | Request to send a PROGRESS message or to piggy‑back a progress IE in a suitable CC message in order to give the Mobile user information about the call, e.g. that the call is progressing in the PLMN/ISDN environment, or that the call has left the PLMN/ISDN environment, or that in‑band tones/announcement are available. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.12 MNCC_ALERT_REQ | Request to send an ALERTING message to indicate to the Mobile originating user that remote called user alerting has been initiated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.13 MNCC_ALERT_IND | Receipt of an ALERTING message from the Mobile terminated user to be sent to the remote calling user to indicate that user alerting has been initiated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.14 MNCC_NOTIFY_REQ | Request to send information pertaining to a call, such as user suspended, to the Mobile originating or the Mobile terminated user. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.15 MNCC_NOTIFY_IND | Indication from the Mobile originating or Mobile terminated user of information pertaining to a call, such as remote user suspended. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.16 MNCC_DISC_REQ | Request to send a DISCONNECT message to the MS in order to clear the end‑to‑end connection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.17 MNCC_DISC_IND | Receipt of a DISCONNECT message, the MS indicates that the end‑to‑end connection is cleared. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.18 MNCC_REL_REQ | Request to send a RELEASE message to inform the MS that the network intends to release the MM connection and the correspondent call reference. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.19 MNCC_REL_IND | Receipt of a RELEASE message, the MS intends to release its MM connection and call reference. The Network is requested to release its call reference and MM connection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.20 MNCC_REL_CNF | The RELEASE COMPLETE message has been received, the MM connection in the MS has been released, the Network itself shall release its MM connection and the corresponding call reference. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.21 MNCC_FACILITY_REQ | Request to transport a facility IE for call related supplementary service invocations. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.22 MNCC_FACILITY_IND | Indication that a facility IE for call related supplementary service invocations has been received. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.23 MNCC_START_DTMF_IND | Indicate the receipt of a START DTMF message in order to start a DTMF control operation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.24 MNCC_START_DTMF_RSP | Request to send a START DTMF ACKNOWLEDGE or START DTMF REJECT message in order to acknowledge or reject the start of a DTMF control operation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.25 MNCC_STOP_DTMF_IND | Indicate the receipt of a STOP DTMF message in order to stop a DTMF control operation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.26 MNCC_STOP_DTMF_RSP | Request to send a STOP DTMF ACKNOWLEDGE message in order to acknowledge the completion of a DTMF control operation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.27 MNCC_MODIFY_REQ | Request to start the Mobile terminating in‑call modification. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.28 MNCC_MODIFY_IND | Receipt of a MODIFY message, the Mobile originating in‑call modification has been initiated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.29 MNCC_MODIFY_RES | Response to send a MODIFY COMPLETE to indicate to the Mobile user that the mobile originating in‑call modification procedure has been completed. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.1.2.30 MNCC_MODIFY_CNF | Confirmation that the Mobile terminating in‑call modification has been completed. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.2 Call independent Supplementary Services Support | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.2.1 Service state diagram | The primitives provided by the call independent Supplementary Services Support entity and the transitions between permitted states are shown in the service graph of figure 7.2 below.
STATES:
IDLE ‑ No SS signalling transaction pending.
CONN ‑ SS signalling transaction established.
Figure 7.2: Service graph of the call independent Supplementary Services Support entity ‑ Network side |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 7.2.2 Service primitives | Table 7.2: Primitives and Parameters at MNSS‑SAP ‑ Network side
PRIMITIVES
PARAMETERS
(Info elements of message)
REFERENCE
MNSS_BEGIN_REQ
REGISTER
7.2.2.1
MNSS_BEGIN_IND
REGISTER
7.2.2.2
MNSS_FACILITY_REQ
FACILITY
7.2.2.3
MNSS_FACILITY_IND
FACILITY
7.2.2.4
MNSS_END_REQ
RELEASE COMPLETE
7.2.2.5
MNSS_END_IND
RELEASE COMPLETE
7.2.2.6 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.