SS Training
SS Training
SS Training
NAS SS Training
Qualcomm Proprietary
Page 1
20 August 2019
NAS - SS Training
Simba ASIC Software
SS Functional Description
• Supplementary Services not only modify the calls, but also enable subscriber to inspect and
modify the status or the parameters of their supplementary services any time irrespective of the
Call State.
• The Management of SS functions are executed within the Connection Management (CM) layer.
• All of the SS functions are done between two network entities: the mobile station (MS) and
home location register (HLR).
• SS uses the MAP/I protocol for exchange signaling messages between MS and HLR.
• The MAP/I messages are piggy back on the call control management (CC), RIL3-CC messages,
which are encapsulated in a FACILITY information element (IE), either as a stand-alone
information or as information carried in some other RIL3-CC message such as SETUP or
ALERTING.
SS Protocol Architecture
MAP/I
CM RIL3-CC
RIL3-MM MAP/D
MM
TCAP
Mobile Network
• Mobile Originated SS transaction
• Takes all the MMI supplied call information and decodes the SS request. This is into a form that
can be submitted to the lower layers.
• This information can then be sent to the CM layer as a MNSS_BEGIN_REQ
• The reference mechanism for all this data stored in MN is the INVOKE_ID
• Mobile Terminated SS transaction
• When the indication is received from CM that a SS transaction is pending MN will decode all of
the IEI’s and store the call related data in its database.
• The MMI can then be informed with the signal MMI_MT_SS_IND
• The reference mechanism for all this data stored in MN is the CONNECTION_ID
Summary:
• Mobile Network is not a state machine or controller
• Mobile Network is a database of call information and an interface to the client application
Connection Manager
• Mobile Originated SS transaction
• Takes the MN data and extracts the CONNECTION_ID message type
• Uses this information along with the MN data to prepare a MM request .
• provided other service requests are not pending, then a MMCM_EST_REQ is sent to MM.
• Mobile Terminated SS transaction
• Takes the MM MMCM_EST_IND signal, assigns a CONNECTION_ID and initialises the CM
FSM for this particular transaction
• Uses the layer 3 information carried in the MM message to prepare a MN message
• issues a MNSS_BEGIN_IND
Mobility Manager
• Mobile Originated SS transaction:
• Responsible for the establishment procedure with the peer entity in the network, which gives the
network the opportunity to perform authentication and/or instigate ciphering.
• MM must ensure that the MS is location Updated prior to the service request
• Send the RR_EST_REQ with the establishment cause (SS) and L3 message.
• Mobile Terminated SS transaction:
• The RR_EST_IND will be followed by the networks initiation of ciphering and authentication.
• The arrival of RR_DATA_IND will contain the layer 3 message for CM/MN
• Send the MMCM_EST_IND to CM. This contains the L3 REGISTER command
SS Primitives
• MNSS_BEGIN_REQ
• MNSS_END_REQ
SS Primitives
• MNSS_FACILITY_REQ
• MNSS_BEGIN_IND
Description: Indication of the start of an SS transaction after the receipt of a register message
SS Primitives
• MNSS_END_IND
Description: Indication that the SS transaction has been cleared after receipt of a release complete message.
• MNSS_FACILITY_IND
SS Primitives
• MNSS_REJ_IND
Description: Message from the SS sub-layer to indicate that channel that release has been
requested from the Network, or that the request was not allowed by MM.
MMI_MO_SS_REQ
MNSS_BEGIN_REQ
MMCM_EST_REQ
MMCM_EST_CNF
MMCM_DATA_REQ
(REGISTER)
MMSS_DATA_IND
(FACILITY)
(OPTIONAL
DIALOGUE) MMCM_DATA_REQ
(FACILITY)
MMCM_DATA_IND
(RELEASE_COMPLETE)
MNSS_END_IND
MMI_MO_SS_CONF
IF no more MM connections
MMCM_REL_REQ
MMCM_EST_IND
(REGISTER)
MNSS_BEGIN_IND
MMI_MT_SS_IND
MMI_MT_SS_RES
MNSS_FACILITY_REQ
MMSS_DATA_REQ
(FACILITY)
MMSS_DATA_IND
(RELEASE_COMPLETE)
MNSS_END_IND
IF no more MM connections
MMCM_REL_REQ