7.4 Description of SMS State Models
23.0783GPPCustomised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4Release 17Stage 2TS
7.4.1 General Handling
See subclause 4.4.1.
The State Model for MO SMS handling contains Points in Association (PIA’s) instead of Points in Call (PIC’s).
7.4.2 Mobile Originating SMS State Models
7.4.2.1 Description of MO SMS state model
The MO SMS state model is used to describe the actions in an MSC and in a SGSN during Mobile Originating SMS.
Figure 7.2: MO SMS State Model
Table 7.1: Description of MO SMS DPs in the MSC and SGSN
|
CAMEL Detection Point |
DP Type |
Description |
|
DP SMS_Collected_Info |
TDP‑R |
Indication that the MO‑SMS‑CSI is analysed and a mobile originated short message is received. |
|
DP O_SMS_Failure |
EDP‑N, EDP‑R |
Indication that the SM submission to the Short Message Service Centre failed |
|
DP O_SMS_Submitted |
EDP‑N, EDP‑R |
Indication that the SM has been successfully submitted to the Short Message Service Centre. |
7.4.2.1.1 Description of the MO SMS state model (PIAs)
This subclause describes the state model for originating SMS transfer. For each PIA a description can be found of the entry events, actions and exit events.
7.4.2.1.1.1 SMS Null & Start & Authorize
Entry events:
– Previous MO SMS transfer to the SMSC completed (DP O_SMS_Submitted).
– Exception event is reported.
Actions:
– Interface is idled.
– Authentication.
– Ciphering.
– MO SMS subscription check.
– RP-MO-DATA message containing the User Data and the SMSC address is received from MS.
– The supplementary service "barring of all outgoing calls" is checked and invoked if necessary.
– The ODB category "barring of all outgoing calls" is checked and ODB is invoked if necessary.
Exit events:
– MO‑SMS‑CSI is analysed.
– An exception condition is encountered.
7.4.2.1.1.2 SMS Analyse & Routing
Entry events:
– MO‑SMS‑CSI is analysed (DP SMS_Collected_Info).
Actions:
– Information being analysed and/or translated to determine routeing address of the SMSC.
– Outgoing barring services and ODB categories not already applied are checked and invoked if necessary. If any of the barring services or ODB categories prevents the submission of the MO‑SMS, then the MSC or SGSN shall generate the "O_SMS_Failure" event. The cause code to be used in that case shall be "sM‑DeliveryFailure".
– The short message is sent to the SMSC.
Exit events:
– Acknowledge from the SMSC is received. (DP O_SMS_submitted).
A positive acknowledgement is sent to the MS.
– An exception condition is encountered – this leads to the SMS_Exception PIA.
A negative acknowledgement is sent to the MS.
– Attempt to select the route for the SMS fails (DP O_SMS_Failure).
A negative acknowledgement is sent to the MS.
– Negative acknowledgement from the SMSC is received (DP O_SMS_Failure).
A negative acknowledgement is sent to the MS.
7.4.2.1.1.3 SMS_Exception
Entry events:
– An exception condition is encountered. In addition to specific examples listed above, exception events include any type of failure, which means that the normal exit events for a PIA cannot be met.
Actions:
– Default handling of the exception condition is applied. This includes general actions necessary to ensure that no resources remain inappropriately allocated such as:
– If a relationship exists between the gsmSCF and gsmSSF or gprsSSF send an error information flow closing the relationship and indicating that any outstanding Short Message handling instructions will not run to completion.
– The MSC/gsmSSF or SGSN/gprsSSF shall make use of vendor-specific procedures to ensure release of internal resources.
Exit events:
– Default handling of the exception condition by MSC/gsmSSF or SGSN/gprsSSF completed.
7.4.3 Mobile Terminating SMS State Model
7.4.3.1 Description of MT SMS state model
The MT SMS state model is used to describe the actions in an MSC and in a SGSN during Mobile Terminating SMS.
Figure 7.3: MT SMS State Model
Table 7.2: Description of MT SMS DPs in the MSC and SGSN
|
CAMEL Detection Point |
DP Type |
Description |
|
DP SMS_Delivery_Request |
TDP‑R |
Indication that the MT‑SMS‑CSI is analysed and a mobile terminating short message or status report is received. |
|
DP T_SMS_Failure |
EDP‑N, EDP‑R |
Indication that the SM delivery to the Mobile Station has failed |
|
DP T_SMS_Delivered |
EDP‑N, EDP‑R |
Indication that the SM has been successfully delivered to the Mobile Station. |
7.4.3.1.1 Description of the MT SMS state model (PIAs)
This subclause describes the state model for terminating SMS transfer. For each PIA a description can be found of the entry events, actions and exit events.
7.4.3.1.1.1 SMS Null & Start & Authorize
Entry events:
– MAP-MT-FORWARD-SHORT-MESSAGE message is received from SMS-GMSC.
– Previous MT SMS transfer to the MS completed (DP T_SMS_Delivered).
– Exception event is reported.
Actions:
– Interface is idled.
– MT SMS subscription check.
– MT‑SMS‑CSI is received from the VLR (in the MSC only).
Exit events:
– MT‑SMS‑CSI is analysed.
– An exception condition is encountered.
7.4.3.1.1.2 SMS Delivery
Entry events:
– MT‑SMS‑CSI is analysed. (DP SMS_Delivery_Request).
Actions:
– Subscriber paging is performed, if required.
– The short message is delivered to the MS.
Exit events:
– Acknowledge from the MS is received. (DP T_SMS_Delivered).
A positive acknowledgement is sent to the SMSC.
– An exception condition is encountered – this leads to the SMS_Exception PIA.
A negative acknowledgement is sent to the SMSC.
– Negative acknowledgement from the MS is received (DP T_SMS_Failure).
A negative acknowledgement is sent to the SMSC.
7.4.3.1.1.3 SMS_Exception
Entry events:
– An exception condition is encountered. In addition to specific examples listed above, exception events include any type of failure, which means that the normal exit events for a PIA cannot be met.
Actions:
– Default handling of the exception condition is applied. This includes general actions necessary to ensure that no resources remain inappropriately allocated such as:
– If a relationship exists between the gsmSCF and gsmSSF or gprsSSF send an error information flow closing the relationship and indicating that any outstanding Short Message handling instructions will not run to completion.
– The MSC/gsmSSF or SGSN/gprsSSF shall make use of vendor-specific procedures to ensure release of internal resources.
Exit events:
– Default handling of the exception condition by MSC/gsmSSF or SGSN/gprsSSF completed.