12 Detailed operation procedures for SMS control

29.0783GPPCAMEL Application Part (CAP) specificationCustomised Applications for Mobile network Enhanced Logic (CAMEL) Phase XRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

NOTE: For Short Message processing in a Circuit Switched network, the CAMEL interaction with SMS is done through the MSC/smsSSF.
For Short Message processing in a Packet Switched network, the CAMEL interaction with SMS is done through the SGSN/smsSSF.

Any reference to the smsSSF applies to both the smsSSF co-located with the MSC and the smsSSF co-located with the SGSN.

NOTE Where a parameter for an SMS control Operation is marked OPTIONAL in ASN.1, the reader is referred to the conditions for presence for this parameter, specified in the respective Information Flow in 3GPP TS 23.078 [7].

12.1 ConnectSMS procedure

12.1.1 General description

The gsmSCF uses this operation to request the smsSSF to continue Short Message processing, such as routeing a Short Message to a specific destination or delivering a Short Message to the served subscriber, with modified information.

12.1.1.1 Parameters

– callingPartysNumber:
This parameter allows the gsmSCF to set the Calling Party Number parameter used in the network. It is used for showing the sending party’s id (i.e. the originating address) to the receiving party.

– destinationSubscriberNumber:
This parameter contains the destination address to which the Short Message shall be routed by the SMSC.

– smscAddress:
This parameter contains the Short Message Service Centre address towards which the Short Message shall be routed.

12.1.2 Responding entity (smsSSF)

12.1.2.1 Normal procedure

smsSSF preconditions:

(1) Mobile originating Short Message submission or Mobile terminating Short Message delivery attempt has been initiated.

(2) Short Message processing has been suspended at the DP SMS_Collected_Info or at DP SMS_Delivery_Requested.

(3) The smsSSF FSM is in the state "Waiting_for_Instructions".

smsSSF postconditions:

(1) The smsSSF performs the Short Message processing actions to route the Short Message to the specified destination or to deliver the Short Message to the served subscriber.

On receipt of this operation, the smsSSF performs the following actions:

– if the callingPartysNumber, destinationSubscriberNumber or smscAddress are supplied, then these values shall be used for subsequent processing;

– if no EDPs have been armed, then the smsSSF FSM transits to the state "Idle". Otherwise, the smsSSF FSM transits to the state "Monitoring".

The smsSSF shall not perform any implicit arming or disarming of DPs.

Statistic counter(s) are not affected.

12.1.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

12.2 ContinueSMS procedure

12.2.1 General description

The gsmSCF uses this operation to request the smsSSF to proceed with processing at the DP at which it previously suspended processing to await gsmSCF instructions. The smsSSF continues processing without substituting new data from the gsmSCF.

12.2.1.1 Parameters

None.

12.2.2 Responding entity (smsSSF)

12.2.2.1 Normal procedure

smsSSF preconditions:

(1) processing has been suspended at any DP.

(2) The smsSSF FSM is in the state "Waiting_for_Instructions".

smsSSF postconditions:

(1) processing continues.

(2) The smsSSF FSM is in one of the following states:

– State "Monitoring" because at least one EDP was armed; or

– State "Idle" because no EDPs were armed.

12.2.2.2 Error handling

Operation related error handling is not applicable, due to class 4 operation.

12.3 EventReportSMS procedure

12.3.1 General description

The smsSSF uses this operation to notify the gsmSCF of a short message related event previously requested by the gsmSCF in a RequestReporSMSEvent operation.

12.3.1.1 Parameters

– eventTypeSMS:
This parameter identifies the type of event that is reported.

– eventSpecificInformationSMS:
This parameter contains the Short Message related information specific to the event.

For O_SMS_Failure it shall contain the O-SMSCause, if available.
For T_SMS_Failure it shall contain the T-SMSCause, if available.
For O_SMS_Submitted and for T_SMS_Delivery it shall be empty.

– miscCallInfo:
This parameter contains DP related information.

– messageType:
This parameter indicates whether the message is a request, i.e. resulting from a RequestReportSMSEvent with "monitorMode" = "interrupted", or a notification, i.e. resulting from a RequestReportSMSEvent with "monitorMode" = "notifyAndContinue".

12.3.2 Invoking entity (smsSSF)

12.3.2.1 Normal procedure

smsSSF preconditions:

(1) The smsSSF FSM is in the state "Monitoring";

(2) The smsSSF FSM proceeds to an EDP that is armed.

smsSSF postconditions:

(1) The smsSSF has applied implicit disarming of EDPs.

(2) If message type was notification and there are no more EDPs armed, then the smsSSF FSM transits to the state "Idle". Otherwise, the smsSSF FSM transits to the state "Waiting_for_Instructions".

12.3.2.2 Error handling

Operation related error handling is not applicable, due to class 4 operation.

12.4 FurnishChargingInformationSMS procedure

12.4.1 General description

The gsmSCF uses this operation to send charging related information to a Logical SMS record. This Logical SMS record is CAMEL specific. The first FurnishChargingInformationSMS operation leads to the generation of a Logical SMS record. Receipt of subsequent FurnishChargingInformationSMS operations shall overwrite or append the contents of the Logical SMS record.

12.4.1.1 Parameters

– fCISMSBillingChargingCharacteristics:
This parameter contains the following parameters;

– fCIBCCCAMELsequence1:
This parameter contains the following parameters;

– freeFormatData:
This parameter contains free-format billing and/or charging characteristics.

– appendFreeFormatData:
This parameter indicates whether previous free-format data shall be appended or overwritten. See 3GPP TS 23.078 [7] for details.

12.4.2 Responding entity (smsSSF)

12.4.2.1 Normal procedure

smsSSF preconditions:

(1) The smsSSF FSM is in the state "Waiting_for_Instructions".

smsSSF postconditions:

(1) No smsSSF FSM state transition.

On receipt of this operation, the smsSSF performs actions to create the Logical SMS record, if a Logical SMS record does not already exist, and writes the free-format information carried in the operation into the Logical SMS record. Subsequent FurnishChargingInformationSMS operations received, by default, will overwrite the free-format data previously written in the Logical SMS record, as specified in 3GPP TS 23.078 [7]. It is also possible to append free format data with subsequent FurnishChargingInformationSMS operations.

The Logical SMS records will be associated for a given Short Message submission or Short Message delivery with one or more physical CDRs, as specified in 3GPP TS 32.250 [13], 3GPP TS 32.251 [14] and 3GPP TS 22.115 [4].

12.4.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

12.5 InitialDPSMS procedure

12.5.1 General description

The smsSSF uses this operation after detection of a TDP-R in the smsSF FSM, to request the gsmSCF for instructions to complete the Short Message submission to the SMSC or the Short Message delivery to the served subscriber.

12.5.1.1 Parameters

– destinationSubscriberNumber:
This parameter carries the ISDN number of the entity receiving the short message or the destination address of the destination subscriber, in an MO-SMS procedure.

– callingPartyNumber:
In an MO-SMS procedure, this parameter carries the MSISDN of the subscriber. In an MT-SMS procedure, this parameter carries the address of the submitter of the short message (i.e. the originating address).

– eventType:
This parameter indicates the armed smSSF FSM DP, resulting in the InitialDPSMS operation.

– iMSI:
IMSI of the mobile subscriber for whom the CAMEL service is invoked.

– locationInformationInMSC:
This parameter indicates the location of the MSC of the served subscriber. This parameter shall be included only if the InitialDP operation is sent from the MSC.

– locationInformationInSGSN:
This parameter indicates the location of the SGSN of the served subscriber. This parameter shall be included only if the InitialDPSMS operation is sent from the SGSN.

– serviceKey:
This parameter indicates to the gsmSCF the requested IN service. It is used to address the required application/SLP within the gsmSCF; it is not for gsmSCF addressing.

– timeAndTimeZone:
This parameter contains the time that the smsSSF was triggered, and the time zone that the invoking smsSSF resides in.

– tPDataCodingScheme:
This parameter indicates the data coding scheme of the TP‑User-Data element within the TPDU. It may indicate a message class. The message class may indicate e.g. the originator of the Short Message.

– tPShortMessageSpecificInfo:
This parameter contains the 1^st octet of the TPDU. Refer to 3GPP TS 23.040 [6] for a description of the various TPDUs.

– tPProtocolIdentifier:
This parameter indicates the protocol used above the SM-Transfer Layer.

– tPValidityPeriod:
This parameter indicates the length of the validity period or the absolute time of the validity period termination.

– sMSCAddress:
This parameter defines the address of the SMSC to which the Short Message is intended to be submitted.

smsReferenceNumber:
This parameter contains the SMS Reference Number assigned to the Short Message by the MSC or SGSN.
mscAddress:
This parameter contains the E.164 address of the MSC. It shall be present if the SMS processing takes place in the MSC; otherwise shall be absent.
sgsn-Number:
This parameter contains the Global Title of the SGSN. It shall be present if the SMS processing takes place in the SGSN; otherwise it shall be absent.

– ms-Classmark2:
This parameter contains the MS Classmark 2 of the mobile subscriber for which the service is invoked.

– gPRSMSClass:
This parameter contains the GPRS MS capabilities of the mobile subscriber for which the CAMEL service is invoked.

– iMEI:
This parameter contains the IMEI (with software version) of the mobile subscriber for which the service is invoked.

calledPartyNumber:
This parameter indicates the served subscriber in an MT-SMS procedure.

12.5.2 Invoking entity (smsSSF)

12.5.2.1 Normal procedure

smsSSF preconditions:

(1) A Short Message submission attempt or a Short Message delivery attempt has been initiated.

(2) An event has been detected at a DP.

(3) For MT-SMS, the event fulfilled the criteria for the DP being executed.

smsSSF postconditions:

(1) A control relationship has been established and the smsSSF waits for instructions from the gsmSCF.

The address of the gsmSCF the InitialDPSMS operation shall be sent to, shall be fetched from the MO-SMS-CSI or the MT-SMS-CSI. The smsSSF shall provide all available parameters to the gsmSCF.

A control relationship is established with the gsmSCF. The smsSSF application timer Tssf is laded with the deafult value and is started. It is used to prevent excessive Short Message submission or delivery suspension time.

12.5.2.2 Error handling

If the gsmSCF is not accessible, then the smsSSF instructs the MSC or SGSN to proceed with the Short Message processing in accordance with the Default SMS Handling parameter of the MO-SMS-CSI or MT-SMS-CSI.

If Tssf expires, then the smsSSF aborts the interaction with the gsmSCF by means of an abort to TC and shall instruct the MSC or SGSN to proceed with the Short Message processing in accordance with the Default SMS Handling parameter of the MO-SMS-CSI CSI or MT-SMS-CSI.

In the case of an MO-SMS Service, if the sending mobile party abandons after the sending of InitialDPSMS and before the TC dialogue is established, then the smsSSF shall abort the interaction with the gsmSCF by means of an abort to TC.

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

12.6 ReleaseSMS procedure

12.6.1 General description

The gsmSCF uses this operation to tear down a Short Message submission attempt or Short Message delivery attempt. The operation may be sent within a control relationship only; it is not allowed in a monitor relationship.

12.6.1.1 Parameters

– rPCause:
This parameter gives an indication to the smsSSF about the reason of releasing this specific Short Message. For a MO-SMS Service, the rPCause shall be sent to the served subscriber in the RP-ERROR RPDU. For a MT-SMS Service, the rPCause shall be sent to the SMS-GMSC in the RP-ERROR RPDU.

12.6.2 Responding entity (smsSSF)

12.6.2.1 Normal procedure

smsSSF preconditions:

(1) The smsSSF FSM is in the state "Waiting_for_Instructions".

(2) The FSM is in DP SMS_Collected_Info or in DP SMS_Delivery_Requested.

smsSSF postconditions:

(1) The smsSSF FSM transits to the state "Idle". All armed EDPs shall be disarmed. All resources in the MSC or SGSN related to the Short Message shall be released.

12.6.2.2 Error handling

Operation related error handling is not applicable, due to class 4 operation.

12.7 RequestReportSMSEvent procedure

12.7.1 General description

The gsmSCF uses this operation to request the smsSSF to monitor for a Short Message related event (FSM events such as failure, delivery or submission) and to send a notification to the gsmSCF when the event is detected.

The monitoring of more than one event may be requested with a single RequestReportSMSEvent operation, but each of these requested events will be reported in a separate EventReportSMS operation.

12.7.1.1 Parameters

– smsEvents:
This parameter indicates the event or events of which a report is requested.

– eventTypeSMS:
This parameter indicates the type of event of which a report is requested. Values SMSCollectedInfo and SMSDeliveryRequested are not valid for the RequestReportSMSEvent operation.

– monitorMode:
This parameter indicates how the event shall be reported. When the "monitorMode" is "interrupted", the event shall be reported as a request, if the "monitorMode" is "notifyAndContinue", the event shall be reported as a notification, if the "monitorMode" is "transparent", then the event shall not be reported.

12.7.2 Responding entity (smsSSF)

12.7.2.1 Normal procedure

smsSSF preconditions:

(1) A control relationship exists between the smsSSF and the gsmSCF.

(2) The smsSSF FSM is in the state "Waiting_for_Instructions".

smsSSF postconditions:

(1) The requested EDPs have been armed or disarmed as indicated.

(2) Armed events are monitored until ended by a transparent monitor mode, until the occurance of the event or until the implicit disarming of the event.

(3) No smsSSF FSM state transition.

12.7.2.2 Error handling

Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.

12.8 ResetTimerSMS procedure

12.8.1 General description

The gsmSCF uses this operation to refresh the Tssf application timer, in order to prevent Tssf expiry at the smsSSF.

12.8.1.1 Parameters

– timerID:
This parameter indicates which timer shall be reset. The only permissible value of this parameter is "tssf".

– timerValue:
This parameter defines the value to which the timer shall be set.

12.8.2 Responding entity (smsSSF)

12.8.2.1 Normal procedure

smsSSF preconditions:

(1) Short Message processing has been suspended at a DP.

(2) The smsSSF FSM is in the state "Waiting_for_Instructions".

smsSSF postconditions:

(1) The Tssf timer is loaded with the value received from the gsmSCF and is restarted.

(2) No smsSSF FSM state transition.

12.8.2.2 Error handling

Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14.