Content for TS 23.078 Word version: 19.0.0

1… 4.2… 4.3… 4.4… 4.5… 4.5.2… 4.5.3… 4.5.4… 4.5.5… 4.5.6… 4.5.7… 4.5.8… 4.6… 4.6.2… 4.6.3… 4.6.7… 4.6.13… 5… 6… 6.5… 6.6… 7… 7.5… 8… 9… 10… 11… 12… A…

7.5 Procedures for CAMEL SMS 7.6 Description of information flows 7.6.1 gsmSSF or gprsSSF to gsmSCF information flows 7.6.2 gsmSCF to gsmSSF or gprsSSF information flows 7.6.3 HLR to VLR or SGSN information flows 7.6.4 VLR or SGSN to HLR information flows 7.6.5 VLR to MSC Information Flows 7.6.6 MSC to VLR Information Flows
...

7.5 Procedures for CAMEL SMS p. 628

7.5.1 Functional architecture for CAMEL MO SMS services p. 628

Copy of original 3GPP image for 3GPP TS 23.078, Fig. 7.4: MO SMS via MSC or SGSN

Figure 7.4: MO SMS via MSC or SGSN
(⇒ copy of original 3GPP image)

7.5.2 Handling of mobile originating SMS p. 628

7.5.2.1 Handling of mobile originating SMS in the originating MSC or SGSN p. 628

The functional behaviour of the originating MSC or SGSN is specified in TS 29.002 and TS 23.060. The procedures specific to CAMEL are specified in this subclause:

Procedure CAMEL_O_SMS_INIT;
Procedure CAMEL_O_SMS_SUBMITTED;
Procedure CAMEL_O_SMS_FAILURE.

A CAMEL Service may be invoked for the following Mobile Originated short message types:

Short Message Submission (TPDU type = SMS-SUBMIT)
Short Message Command (TPDU type = SMS-COMMAND)

Refer to TS 23.040 for a description of the various TPDU types and to TS 24.011 for a description of the protocol elements of the Short Message Relay Layer (RPDUs).

7.5.2.1.1 Actions of the MSC or SGSN on receipt of Int_Error p. 629

The MSC or SGSN checks the default SMS Handling parameter in MO-SMS-CSI.

If the default SMS handling is 'releaseTransaction', a A_RP_ERROR is sent to the MS. The MSC or SGSN then releases all resources and the procedure CAMEL_O_SMS_INIT ends.

If the default SMS handling is 'continueTransaction', the MSC or SGSN continues processing without CAMEL support.

7.5.2.1.2 Actions of the MSC or SGSN on receipt of Int_Continue_SMS p. 629

The MSC or SGSN continues processing with modified SM parameters. The MSC or SGSN shall transparently modify the SMS parameters with the received information. Parameters which are not included in the Int_Continue_SMS signal are unchanged.

7.5.2.1.3 Actions of the MSC or SGSN on receipt of Int_Connect_SMS p. 629

The MSC or SGSN continues processing with modified SM parameters. The MSC or SGSN shall transparently modify the SMS parameters with the received information. Barring is checked with the modified parameters. Parameters which are not included in the Int_Connect_SMS signal are unchanged.

7.5.2.1.4 Actions of the MSC or SGSN on receipt of Int_Release_SMS p. 629

A_RP_ERROR is sent to the MS and the Short Message is deleted. The SMS cause received in the Int_Release_SMS signal is used. The MSC or SGSN then releases all resources and the procedure CAMEL_O_SMS_INIT ends.

7.5.2.1.5 Allocation of SMS Reference Number p. 629

During the CAMEL handling of a Mobile Originated Short Message, the MSC or SGSN shall allocate an SMS Reference Number. This SMS Reference Number shall be placed in the SMS-MO Call Detail Record, together with the MSC Address or SGSN Number. This SMS Reference Number shall also be sent to the gsmSCF in the Initial DP SMS Information Flow, together with the MSC Address or SGSN Number. The combination of SMS Reference Number and MSC Address or SGSN Number forms a globally unique pair. This pair may be used for correlation of CDRs produced in the MSC or SGSN with CDRs produced in the gsmSCF.

An SMS Reference Number shall be generated and placed in the SMS-MO Call Detail Record, for every Short Message, including the case when a Short Message forms part of a set of concatenated Short Messages.

7.5.2.2 Handling of A_MM_Release and A_LLC_Release p. 629

If the radio link with the subscriber is lost during the handling of a CAMEL procedure in the MSC or SGSN, then the MSC or SGSN sends signal A_MM_Release_ind or A_LLC_Release_ind to that procedure. This results in the termination of that CAMEL procedure. (Refer to TS 29.002 for details.)

7.5.2.3 Handling of time-out from SMSC p. 629

If the MSC or SGSN does not receive a confirmation from the SMSC after submission of a Short Message, then the MSC or SGSN calls procedure CAMEL_O_SMS_FAILURE. (Refer to TS 29.002 for details.)

(not reproduced yet)

Figure 7.5-1: Procedure CAMEL_O_SMS_INIT (sheet 1)

(not reproduced yet)

Figure 7.5-2: Procedure CAMEL_O_SMS_INIT (sheet 2)

(not reproduced yet)

Figure 7.5-3: Procedure CAMEL_O_SMS_INIT (sheet 3)

(not reproduced yet)

Figure 7.6-1: Procedure CAMEL_O_SMS_SUBMITTED (sheet 1)

(not reproduced yet)

Figure 7.7-1: Procedure CAMEL_O_SMS_FAILURE (sheet 1)

7.5.2.4 Handling of mobile originating SMS in the VLR p. 634

The functional behaviour of the VLR is specified in TS 29.002 The handling specific to CAMEL is specified in the following procedure:

Procedure CAMEL_MO_SMS_VLR.

(not reproduced yet)

Figure 7.8-1: Procedure CAMEL_MO_SMS_VLR (sheet 1)

7.5.3 Functional architecture for CAMEL MT SMS services p. 636

Copy of original 3GPP image for 3GPP TS 23.078, Fig. 7.9: MT SMS via MSC or SGSN

Figure 7.9: MT SMS via MSC or SGSN
(⇒ copy of original 3GPP image)

7.5.4 Handling of mobile terminating SMS |R5| p. 636

7.5.4.1 Handling of mobile terminating SMS in the terminating MSC or SGSN p. 636

A CAMEL Service may be invoked for the following Mobile Terminated short message types:

Short Message Delivery (TPDU type = SMS-DELIVER)
Short Message Status Report (TPDU type = SMS-STATUS-REPORT)

Refer to TS 23.040 for a description of the various TPDU types and to TS 24.011 for a description of the protocol elements of the Short Message Relay Layer (RPDUs).

The functional behaviour of the terminating MSC or SGSN is specified in TS 29.002. The procedures specific to CAMEL are specified in the following subclauses:

7.5.4.1.1 Procedure CAMEL_T_SMS_INIT; p. 637

This procedure is called when a Short Message delivery attempt is received from the SMS-GMSC. If MT-SMS-CSI is present for the subscriber, then the SMS_SSF shall be invoked. Otherwise, the Short Message delivery attempt proceeds without CAMEL.

When the SMS_SSF is invoked and the SMS_SSF has requested the gsmSCF for instructions, the MSC or SGSN may receive the following responses from the SMS_SSF:

Int_Continue_SMS
The gsmSCF has indicated that SM delivery may proceed. It may have supplied the SMS_SSF with a modified Calling Party Number. This Calling Party Number shall replace the TP-Originating-Address in the SMS-DELIVER TPDU.
Int_Release_SMS
The gsmSCF has force-released SM delivery. The RP Cause received from the gsmSCF shall be conveyed to the SMS-GMSC in the RP-Cause component, in the RP-ERROR RPDU.
Int_Error
A Tssf time-out or an internal SMS_SSF error has occurred; the SM has not been forwarded to the Mobile Station. If Default SMS Handling equals 'Continue', the SM delivery proceeds. Otherwise, SM delivery shall be aborted. In the latter case, the RP-Cause component, in the RP-ERROR RPDU shall be set to EquipmentProtocolError, in accordance with TS 29.002.

7.5.4.1.2 Procedure CAMEL_T_SMS_DELIVERED p. 637

This procedure is called when the MSC or SGSN has detected that delivery of the SM to the Mobile Station has succeeded. No event specific information is sent to the gsmSCF.

When Short Message delivery attempt success has been reported to the gsmSCF, then the MSC or SGSN may receive the following responses from the SMS_SSF:

Int_Continue_SMS
The event was reported to the gsmSCF in interrupt mode. The gsmSCF has concluded CAMEL processing and has terminated the Service Logic.
Int_Continue
The event was not reported to the gsmSCF or was reported in notification mode.
Int_Error
A Tssf time-out has occurred.

In all the above cases, the SM processing in the MSC or SGSN continues.

7.5.4.1.3 Procedure CAMEL_T_SMS_FAILURE p. 637

This procedure is called when the MSC or SGSN has detected that delivery of the SM to the Mobile Station has failed. If the delivery failure is due to RP-ERROR RPDU received from the MS, then the MT SMS Cause in the event report to the gsmSCF shall be set to the RP-Cause component in the RP-ERROR-RPDU. Otherwise, if the delivery failure is due to internal failure in the MSC or SGSN, CP-ERROR from MS or time-out from the MS, then the MT SMS Cause in the event report to the gsmSCF shall be set to "Protocol error, unspecified", as defined in TS 24.011.

When Short Message delivery attempt failure has been reported to the gsmSCF, then the MSC or SGSN may receive the following responses from the SMS_SSF:

Int_Continue_SMS
The event was reported to the gsmSCF in interrupt mode. The gsmSCF has concluded CAMEL processing and has terminated the Service Logic.
Int_Continue
The event was not reported to the gsmSCF or was reported in notification mode.
Int_Error
A Tssf time-out has occurred.

In all the above cases, the SM processing in the MSC or SGSN continues.

7.5.4.1.4 Allocation of SMS Reference Number p. 638

During the CAMEL handling of a Mobile Terminating Short Message, the MSC or SGSN shall allocate an SMS Reference Number. This SMS Reference Number shall be placed in the SMS-MT Call Detail Record, together with the MSC Address or SGSN Number. This SMS Reference Number shall also be sent to the gsmSCF in the Initial DP SMS Information Flow, together with the MSC Address or SGSN Number. The combination of SMS Reference Number and MSC Address or SGSN Number forms a globally unique pair. This pair may be used for correlation of CDRs produced in the MSC or SGSN with CDRs produced in the gsmSCF.

An SMS Reference Number shall be generated and placed in the SMS-MT Call Detail Record, for every Short Message, including the case when a Short Message forms part of a set of concatenated Short Messages.

(not reproduced yet)

Figure 7.10-1: Procedure CAMEL_T_SMS_INIT (sheet 1)

(not reproduced yet)

Figure 7.10-2: Procedure CAMEL_T_SMS_INIT (sheet 2)

(not reproduced yet)

Figure 7.11-1: Procedure CAMEL_T_SMS_FAILURE (sheet 1)

(not reproduced yet)

Figure 7.12-1: Procedure CAMEL_T_SMS_DELIVERED (sheet 1)

7.5.4.2 Handling of mobile terminating SMS in the VLR p. 643

The functional behaviour of the VLR is specified in TS 29.002. The handling specific to CAMEL is specified in the following procedure:

Procedure CAMEL_MT_SMS_VLR.

(not reproduced yet)

Figure 7.13-1: Procedure CAMEL_MT_SMS_VLR (sheet 1)

7.5.4.3 CAMEL subscription check for mobile terminating SMS in the SGSN p. 645

The functional behaviour of the SGSN for delivery of MT shrt message is specified in TS 29.002. The procedure for checking CAMEL capability and subscription information is specified in the following procedure:

Procedure CAMEL_MT_SMS_SGSN.

(not reproduced yet)

Figure 7.14-1: Procedure CAMEL_MT_SMS_SGSN (sheet 1)

7.5.5 Handling of mobile originating and mobile terminating SMS in the gsmSSF or gprsSSF |R5| p. 647

7.5.5.1 Process SMS_SSF p. 647

Sheet 1

The Int_Invoke SMS_SSF signal dictates which TDP shall be armed. For a Mobile Originated SMS service, the SMS_Collected_Info TDP shall be armed. For a Mobile Terminated SMS service, the SMS_Delivery_Request TDP shall be armed.

Sheet 2

The Int_SMS_Failure signal may be received only for a MO-SMS service. It is received when a MS detach event occurs before the SMS_SSF is invoked.

Sheet 3

The SMSC Address and Destination Subscriber Number may be received in CAP ConnectSMS only for a MO-SMS service.

Sheet 4:

For a MO-SMS service, the following events may be armed or disarmed: O_SMS_Submission, O_SMS_Failure. For a MT-SMS service, the following events may be armed or disarmed: T_SMS_Delivery, T_SMS_Failure.

Sheet 5:

For a MO-SMS service, the gsmSCF may place free-format charging data in the 'MOSMSRecord' CDR (in the MSC) or in the S-SMO-CDR (in the SGSN).

For a MT-SMS service, the gsmSCF may place free-format charging data in the 'MTSMSRecord' (in the MSC) or in the S-SMT-CDR (in the SGSN).

Refer to TS 32.250 and TS 32.251 for a description of these CDR types.

Sheet 6:

The Int_SMS_Failure signal in state Waiting_For_Instructions may be received for a MO-SMS service only. It is received when a MS detach event occurs before the gsmSCF has given instruction to continue SM processing.

Sheet 7:

When the SM submission or failure event occurs, both MO-SMS events shall be disarmed.

When the SM delivery or failure event occurs, both MT-SMS events shall be disarmed.

7.5.5.2 Process Complete_SMS_FCI_Record p. 647

Sheet 1:

For a MO-SMS service, the 'MOSMSRecord' or 'S-SMO-CDR' shall be closed. For a MT-SMS service, the 'MTSMSRecord' or 'S-SMT-CDR' shall be closed.

(not reproduced yet)

Figure 7.15-1: Process SMS_SSF (sheet 1)

(not reproduced yet)

Figure 7.15-2: Process SMS_SSF (sheet 2)

(not reproduced yet)

Figure 7.15-3: Process SMS_SSF (sheet 3)

(not reproduced yet)

Figure 7.15-4: Process SMS_SSF (sheet 4)

(not reproduced yet)

Figure 7.15-5: Process SMS_SSF (sheet 5)

(not reproduced yet)

Figure 7.15-6: Process SMS_SSF (sheet 6)

(not reproduced yet)

Figure 7.15-7: Process SMS_SSF (sheet 7)

(not reproduced yet)

Figure 7.16-1: Procedure Check_Criteria_SMS_Delivery_Request (Sheet 1)

(not reproduced yet)

Figure 7.17-1: Procedure Complete_SMS_FCI_record (sheet 1)

7.6 Description of information flows p. 657

This subclause contains the detailed description of the information flows used by CAMEL for SMS control.

Each Information Element (IE) is marked as Mandatory (M), Conditional (C), Optional (O), Specific conditions (S), mutually Exclusive (E), or not applicable (-) for each different traffic case: Mobile Originating SMS (MO) and Mobile Terminating SMS (MT). If the IEs in one Table apply in both the MO and MT cases, then the IEs are marked in the "Status" column.

An 'M' IE shall always be included. A 'C' IE shall be included if the sending entity has the necessary information to populate the IE. The conditions for the inclusion of an 'S' IE are shown in the 'Description' column of the definition table. When a set of 'E' IEs is shown in the definition of an Information Flow or compound IE, only one of those IEs may be included. An 'O' IE may be included or omitted as required by the service logic. A '-' IE shall always be omitted. This categorization is a functional classification, i.e. it defines the requirements for the stage 2 information. It is not a stage 3 classification to be used for the ASN.1 syntax of the protocol.

The distinction between MO and MT SMS applies only to the Information Flows between the gsmSCF and the gsmSSF or gprsSSF.

Details of errors and exceptions to these rules are specified in TS 29.002, TS 29.078.

7.6.1 gsmSSF or gprsSSF to gsmSCF information flows p. 657

7.6.1.1 Event Report SMS p. 657

7.6.1.1.1 Description p. 657

This IF is used to notify the gsmSCF of an event previously requested by the gsmSCF in a Request Report SMS Event IF.

7.6.1.1.2 Information Elements p. 657

Information element name	MO	MT	Description
Event Type	M	M	This IE specifies the type of event that is reported.
Event Specific Information	C	C	This IE indicates the SMS related information specific to the event.
Misc SMS Info	M	M	This IE indicates the DP type.

If the Event Type IE indicates O_SMS_Failure, then the Event Specific Information contains the following information element:

Information element name	MO	MT	Description
MO_SMS Cause	M	-	This IE indicates the reason of submission failure.

If the Event Type IE indicates T_SMS_Failure, then the Event Specific Information contains the following information elements:

Information element name	MO	MT	Description
MT_SMS Cause	-	M	This IE indicates the reason of delivery failure.

If the Event Type IE indicates O_SMS_Submitted or T_SMS_Delivered, then no Event Specific Information shall be sent to the gsmSCF.

7.6.1.2 Initial DP SMS p. 657

7.6.1.2.1 Description p. 657

This IF is generated by the gsmSSF or gprsSSF when a trigger is detected at a DP in the state model, to request instructions from the gsmSCF.

7.6.1.2.2 Information Elements p. 658

Information element name	MO	MT	Description
Destination Subscriber Number	M	-	This IE contains a number to identify the Destination short message entity. The Destination Subscriber Number shall be retrieved from the TP-Destination-Address in the SMS-SUBMIT TPDU or the SMS-COMMAND TPDU.
Called Party Number	-	M	This IE contains a number to identify the subscriber for whom the Short Message is destined. The Called Party Number shall be the MSISDN of the served subscriber.
Calling Party Number	M	C	For MO SMS: This IE contains a number to identify the subscriber who requests the SM submission. The Calling Party Number shall be the MSISDN of the served subscriber. For MT SMS: This IE contains the address of the submitter of the short message. For SMS-DELIVER TPDU, the Calling Party Number shall be retrieved from the TP-Originating-Address in the SMS-DELIVER TPDU. For SMS-STATUS-REPORT TPDU, this element shall not be included in this IF.
Event Type	M	M	This IE indicates the armed event resulting in the Initial DP SMS IF.
IMSI	M	M	This IE identifies the mobile subscriber.
Location Information In MSC	C	C	This IE is described in a Table below.
Location Information In SGSN	C	C	This IE is described in a Table below.
Service Key	M	M	This IE indicates to the gsmSCF the requested CAMEL Service. It is used to address the required application/SLP within the gsmSCF.
Time And Timezone	M	M	This IE contains the time that the gsmSSF or gprsSSF was triggered, and the time zone the gsmSSF or gprsSSF resides in.
TP Short Message Specific Information	M	M	This IE contains the first octet of the applicable TPDU. For SMS-SUBMIT, the following elements may be included: Message Type Indicator Reject Duplicates Validity Period Format Status Report Request User Data Header Indicator Reply Path For SMS-COMMAND, the following elements may be included: Message Type Indicator User Data Header Indicator Status Report Request For SMS-DELIVER, the following elements may be included: Message Type Indicator More Messages to Send Status Report Indication User Data Header Indicator Reply Path For SMS-STATUS-REPORT, the following elements may be included: Message Type Indicator More Messages to Send Status Report Qualifier User Data Header Indicator Refer to TS 23.040 for an indication of which elements of this 1st octet are Mandatory and which elements are Conditional.
TP Protocol Identifier	M	C	This IE indicates the protocol used above SM-Transfer Layer. The TP Protocol Identifier shall be retrieved from the applicable TPDU. For SMS-STATUS-REPORT, the sending of this IE is Conditional, depending on its presence in the SMS-STATUS-REPORT TPDU.
TP Data Coding Scheme	C	C	This IE indicates the data coding scheme of the TP-User Data field, and may indicate a message class. The message class may indicate e.g. the originator of the Short Message. The TP Data Coding Scheme shall be retrieved from the applicable TPDU. For SMS-COMMAND, this IE shall not be included in this IF.
TP Validity Period	S	-	This IE indicates the length of the validity period or the absolute time of the validity period termination. This IE is used only for the SMS-SUBMIT TPDU. The TP Validity Period, if available, shall be retrieved from the SMS-SUBMIT TPDU. For other TPDU, this IE shall not be included in this IF.
SMSC Address	M	M	For MO SMS: This IE defines the address of the SMSC to which the MO short message is intended to be submitted. It shall be retrieved from the RP-Destination-Address in the RP-MO-DATA RPDU. For MT SMS: This IE identifies the address of the SMSC from which the MT short message is originating. It shall be retrieved from the RP-Originating-Address in the RP-MT-DATA RPDU.
SMS Reference Number	M	M	This IE carries the SMS Reference Number. This Reference Number is allocated by the MSC or SGSN that processes the Short Message. It may be used by the gsmSCF for inclusion in a gsmSCF SMS record.
MSC Address	S	S	This IE carries the E.164 MSC Address. This IE shall be present if the Short Message processing takes place in an MSC. Otherwise shall be absent.
SGSN Number	S	S	This IE carries the Global Title of the SGSN. See TS 23.060. This IE shall be present if the Short Message processing takes place in an SGSN. Otherwise shall be absent.
GPRS MS Class	C	-	This IE contains the MS network and radio access capabilities if the short message is being transferred through an SGSN.
MS Classmark 2	C	-	This IE contains the MS classmark 2 if the short message is being transferred through an MSC.
IMEI (with software version)	C	-	This IE contains the IMEISV (as defined in TS 23.003) of the ME in use by the served subscriber.
NOTE: Refer to TS 23.040 for a description and encoding of the various TP-DUs and RP-DUs.

Location Information in MSC is based on the Location Information IE defined in TS 23.018. The following differences apply:

Information element name	MO	MT	Description
Service area ID	C,E	C,E	See TS 23.018.
Cell ID	C,E	C,E	See TS 23.018.
Location area ID	C,E	C,E	See TS 23.018.
VLR number	M	M	See TS 23.018.
Age of location information	-	M	See TS 23.018.
Current Location Retrieved	-	-	Not applicable
Selected LSA Identity	S	S	This IE is applicable only if SoLSA is supported by the MSC. This IE indicates the LSA identity associated with the current position of the MS. It shall be shall be present if the LSA ID in the subscriber data matches the LSA ID of the current cell. In the case of multiple matches the LSA ID with the highest priority shall be present. See TS 43.073.
User CSG Information	C	C	See TS 23.060.
E-UTRAN Cell ID	C,E	C,E	See TS 23.018.
Tracking area ID	C,E	C,E	See TS 23.018.

Location Information in SGSN is based on the Location Information For GPRS IE defined in the subclause 11.3.6.1.2. The following differences and clarifications apply:

Information element name	MO	MT	Description
Service area ID	C,E	C,E	See TS 23.018.
Cell ID	C,E	C,E	See TS 23.018.
Location area ID	C,E	C,E	See TS 23.018.
Routeing area ID	C	C	See TS 23.003.
Geographical information	C	C	See TS 23.032.
Geodetic information	-	-	Not applicable
Age of location information	-	-	Not applicable
Current Location Retrieved	-	-	Not applicable
User CSG Information	C	C	See TS 23.060.

7.6.2 gsmSCF to gsmSSF or gprsSSF information flows p. 660

7.6.2.1 Connect SMS p. 660

7.6.2.1.1 Description p. 660

This IF is used to request the gsmSSF or gprsSSF to perform the actions to route the Short Message to a specific destination (for MO SMS) or to deliver the Short Message to the MS (for MT SMS).

7.6.2.1.2 Information Elements p. 660

Information element name	MO	MT	Description
Calling Partys Number	O	O	This IE indicates the subscriber who sent the SMS; possibly changed by the gsmSCF. If the Short Message type is SMS-SUBMIT or SMS-COMMAND, then this IE, if present, it shall replace the RP-Originating-Address in the RP-MO-DATA RPDU (CHOICE set to MSISDN). If the Short Message type is SMS-DELIVER, then this IE, if present, shall replace the TP-Originating-Address in the SMS-DELIVER TPDU. If the Short Message type is SMS-STATUS-REPORT, then this IE, if present, shall be ignored.
Destination Subscriber Number	O	-	This IE identifies the Destination short message entity; possibly changed by the gsmSCF. This IE, if present, shall replace the TP-Destination-Address in the SMS-SUBMIT TPDU or SMS-COMMAND-TPDU.
SMSC Address	O	-	This IE indicates the SMSC address to which the MO short message shall be submitted; possibly changed by the gsmSCF. This IE, if present, shall replace the RP-Destination-Address in the RP-MO-DATA RPDU (CHOICE set to serviceCentreAddressDA).

7.6.2.2 Continue SMS p. 660

7.6.2.2.1 Description p. 660

This information flow requests the gsmSSF or gprsSSF to proceed normally. The gsmSSF or gprsSSF completes DP processing, and continues with the SMS handling.

7.6.2.2.2 Information Elements p. 660

This IF contains no information elements.

7.6.2.3 Furnish Charging Information SMS p. 660

7.6.2.3.1 Description p. 660

This IF is used to request the gsmSSF or gprsSSF to include information in the CAMEL specific logical MO SMS or MT SMS record.

The logical call record is created when FCI-SMS is received and a logical call record for that short message does not exist. For modelling purposes the logical call record is buffered in the gsmSSF or gprsSSF. The gsmSSF or gprsSSF completes logical call records as defined in the SDLs. Once the logical call record is completed, then its free format data are moved to the corresponding CDR and the logical call record is deleted.

The gsmSCF can send multiple concatenated FCIs per Short Message for completion. The total maximum of free format data is 160 octets per SM. The 160 octets may be sent in one or more FCI IFs. If there are incomplete free format data and new FCI IFs is/are received to overwrite the incomplete data, then the incomplete data are discarded and the gsmSCF can send another 160 octets per SM.

7.6.2.3.2 Information Elements p. 661

Information element name	MO	MT	Description
FCI Billing Charging Characteristics	M	M	This IE is described in a Table below.
FCI Billing Charging Characteristics contains the following information element:

Information element name	MO	MT	Description
FCIBCCCAMEL Sequence 1	M	M	This IE is described in a Table below.

FCIBCCCAMEL Sequence 1 contains the following information elements:

Information element name	MO	MT	Description
Free Format Data	M	M	This IE contains free format data to be inserted in the CAMEL logical call record.
Append Free Format Data	O	O	This IE indicates that the gsmSSF or gprsSSF shall append the free format data to the Logical MO SMS or MT SMS record. If this IE is present indicating "Append", the gsmSSF or gprsSSF shall append the free format data received in this IF to the free format data already present in the Logical MO SMS or MT SMS record. If this IE is absent or indicates "Overwrite", then the gsmSSF shall overwrite all free format data already present in the Logical MO SMS or MT SMS record, by the free format data received in this IF. If no Logical MO SMS or MT SMS record exists yet, then the gsmSSF or gprsSSF shall ignore this IE.

7.6.2.4 Release SMS p. 661

7.6.2.4.1 Description p. 661

This IF is used to tear down by the gsmSCF an existing SMS transfer.

7.6.2.4.2 Information Elements p. 661

Information element name	MO	MT	Description
RP Cause	M	M	SMS Cause. Indicates the SMS specific cause of the release. The cause is reported to the MS (in the case of MO SMS) or SMSC (in the case of MT SMS). For MO SMS, the RP Cause value shall be used to set the RP-Cause in the RP-ERROR RPDU sent to the MS. TS 24.011 specifies which RP-Cause values may be sent to the MS. For MT SMS, the RP Cause value shall be used to set the RP-Cause in the RP-ERROR RPDU sent to the SMSC. TS 29.002 specifies which RP-Cause values may be sent to the SMSC.

7.6.2.5 Request Report SMS Event p. 661

7.6.2.5.1 Description p. 661

This IF is used to request the gsmSSF or gprsSSF to monitor for an event and to send a notification to the gsmSCF when the event is detected (see Event Report SMS IF).

7.6.2.5.2 Information Elements p. 662

Information element name	MO	MT	Description
SMS Event	M	M	This IE specifies the event or events of which a report is requested.

SMS Event contains the following information elements:

Information element name	MO	MT	Description
Event Type	M	M	This IE specifies the type of event of which a report is requested.
Monitor Mode	M	M	This IE indicates how the event shall be reported.

7.6.2.6 Reset Timer SMS p. 662

7.6.2.6.1 Description p. 662

This IF is used to refresh a gsmSSF or gprsSSF timer.

7.6.2.6.2 Information Elements p. 662

Information element name	MO	MT	Description
Timer Value	M	M	This IE specifies the value to which the indicated timer shall be set.
Timer ID	O	O	This IE indicates which timer shall be reset. It shall be set to 'Tssf'.

7.6.3 HLR to VLR or SGSN information flows p. 662

7.6.3.1 Delete Subscriber Data p. 662

7.6.3.1.1 Description p. 662

This IF is used by the HLR to delete CAMEL subscription data from a VLR or SGSN. It is specified in TS 29.002

7.6.3.1.2 Information Elements p. 662

The Delete Subscriber Data IF contains the following CAMEL specific information elements:

Information element name	Status	Description
CAMEL Subscription Info Withdraw	O	This IE identifies that all CSIs shall be deleted from the subscriber data in VLR or SGSN.
Specific CSI Withdraw	O	This IE is used to indicate that only MO-SMS-CSI or MT-SMS-CSI shall be deleted from the VLR or SGSN. This IE should not be present when CAMEL Subscription Info Withdraw is present.

7.6.3.2 Insert Subscriber Data p. 662

7.6.3.2.1 Description p. 662

This IF is used by the HLR to insert subscriber data in the VLR or SGSN. It is specified in TS 29.002.

7.6.3.2.2 Information Elements p. 662

The Insert Subscriber Data contains the following CAMEL specific information elements:

Information element name	Status	Description
MO-SMS-CSI	O	This IE identifies the subscriber as having MO SMS CAMEL services.
MT-SMS-CSI	O	This IE identifies the subscriber as having MT SMS CAMEL services.

MO-SMS-CSI contains the following information elements:

Information element name	Status	Description
gsmSCF Address	M	See subclause 7.3.1.1.
Service Key	M	See subclause 7.3.1.2.
Default SMS Handling	M	See subclause 7.3.1.3.
CAMEL Capability Handling	M	See subclause 7.3.1.5.
SMS Triggers	M	See subclause 7.3.1.4. It includes the following trigger: SMS_Collected_Info

MT-SMS-CSI contains the following information elements:

Information element name	Status	Description
gsmSCF Address	M	See subclause 7.3.2.1.
Service Key	M	See subclause 7.3.2.2.
Default SMS Handling	M	See subclause 7.3.2.3.
CAMEL Capability Handling	M	See subclause 7.3.2.6.
SMS Triggers	M	See subclause 7.3.2.4. It includes the following trigger: SMS_Delivery_Request.
SMS Trigger Criteria	C	See subclause 7.3.2.5.

7.6.4 VLR or SGSN to HLR information flows p. 663

7.6.4.1 Insert Subscriber Data ack p. 663

See subclause 4.6.8.1. This information flow is sent by the VLR.

7.6.4.2 Update Location p. 663

See subclause 4.6.8.3.

7.6.4.3 Update GPRS Location p. 663

7.6.4.3.1 Description |R5| p. 663

This IF is used by the SGSN to indicate to the HLR the CAMEL phases and CAMEL phase 4 CSIs offered by the SGSN. It is specified in TS 29.002.

7.6.4.3.2 Information Elements |R5| p. 663

Update GPRS location contains the following CAMEL specific information element:

Information element name	Status	Description
Supported CAMEL Phases	S	This IE indicates which CAMEL phases are supported by the SGSN. The SGSN may indicate support of CAMEL phase 3 or higher. It shall be present when the SGSN supports CAMEL.
Offered CAMEL4 CSIs	S	This IE indicates the CAMEL phase 4 CSIs offered in the SGSN. It shall be present if the "Supported CAMEL Phases" IE contains support of CAMEL phase 4.

Offered CAMEL4 CSIs contains the following information elements:

Information element name	Status	Description
MT-SMS-CSI	S	This IE indicates the offer of CAMEL phase 4 MT-SMS-CSI.

7.6.5 VLR to MSC Information Flows p. 664

7.6.5.1 Continue CAMEL SMS Handling p. 664

7.6.5.1.1 Description p. 664

This IF is used to instruct the MSC to continue the CAMEL specific handling.

7.6.5.1.2 Information Elements |R5| p. 664

Information element name	Status	Description
MT-SMS-CSI	M	This IE contains the CAMEL Subscription Information for MT SMS.
IMSI	M	IMSI of the served subscriber.
MSISDN	M	MSISDN of the served subscriber.

7.6.5.2 Send Info For MO SMS ack |R5| p. 664

7.6.5.2.1 Description p. 664

This IF is used to transport MO SMS related subscription data from the VLR to the MSC. It is specified in TS 29.002.

7.6.5.2.2 Information Elements p. 664

Information element name	Status	Description
MO-SMS-CSI	C	This IE contains the CAMEL Subscription Information for MO SMS.
ODB Data	C	This IE contains ODB data. This information is used to apply ODB for a reconnected Short Message, if needed.
CB SS Data	C	This IE contains CB SS data. This information is used to apply CB for a reconnected Short Message, if needed.

7.6.6 MSC to VLR Information Flows |R5| p. 664

7.6.6.1 Send Info For MT SMS p. 664

7.6.6.1.1 Description p. 664

This IF is described in TS 29.002; it is used to request the VLR to provide information to handle an MT SMS.

7.6.6.1.2 Information Elements p. 664

Send Info For MT SMS contains the following CAMEL specific information element:

Information element name	Status	Description
Suppress MT-SMS-CSI	S	This IE indicates to the VLR that it shall not return MT-SMS-CSI to the MSC. This IE shall not be present in the first interrogation; it shall be present in the second interrogation.