7.6 Description of information flows

23.0783GPPCustomised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4Release 17Stage 2TS

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 3GPP TS 29.002 [34], TS 29.078 [36].

7.6.1 gsmSSF or gprsSSF to gsmSCF information flows

7.6.1.1 Event Report SMS

7.6.1.1.1 Description

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

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

7.6.1.2.1 Description

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

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 3GPP TS 23.040 [14] 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 3GPP TS 23.060 [15]. 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 3GPP TS 23.003 [7]) of the ME in use by the served subscriber.

Note: Refer to 3GPP TS 23.040 [14] 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 3GPP TS 23.018 [12]. The following differences apply:

Information element name

MO

MT

Description

Service area ID

C,E

C,E

See 3GPP TS 23.018 [12].

Cell ID

C,E

C,E

See 3GPP TS 23.018 [12].

Location area ID

C,E

C,E

See 3GPP TS 23.018 [12].

VLR number

M

M

See 3GPP TS 23.018 [12].

Age of location information

M

See 3GPP TS 23.018 [12].

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 3GPP TS 23.073 [18].

User CSG Information

C

C

See 3GPP TS 23.060 [15].

E-UTRAN Cell ID

C,E

C,E

See 3GPP TS 23.018 [12].

Tracking area ID

C,E

C,E

See 3GPP TS 23.018 [12].

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 3GPP TS 23.018 [12].

Cell ID

C,E

C,E

See 3GPP TS 23.018 [12].

Location area ID

C,E

C,E

See 3GPP TS 23.018 [12].

Routeing area ID

C

C

See 3GPP TS 23.003 [7].

Geographical information

C

C

See 3GPP TS 23.032 [13].

Geodetic information

Not applicable

Age of location information

Not applicable

Current Location Retrieved

Not applicable

User CSG Information

C

C

See 3GPP TS 23.060 [15].

7.6.2 gsmSCF to gsmSSF or gprsSSF information flows

7.6.2.1 Connect SMS

7.6.2.1.1 Description

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

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

7.6.2.2.1 Description

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

This IF contains no information elements.

7.6.2.3 Furnish Charging Information SMS

7.6.2.3.1 Description

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

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

7.6.2.4.1 Description

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

7.6.2.4.2 Information Elements

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. 3GPP TS 24.011 [31] 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. 3GPP TS 29.002 [34] specifies which RP-Cause values may be sent to the SMSC.

7.6.2.5 Request Report SMS Event

7.6.2.5.1 Description

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

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

7.6.2.6.1 Description

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

7.6.2.6.2 Information Elements

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

7.6.3.1 Delete Subscriber Data

7.6.3.1.1 Description

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

7.6.3.1.2 Information Elements

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

7.6.3.2.1 Description

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

7.6.3.2.2 Information Elements

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

7.6.4.1 Insert Subscriber Data ack

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

7.6.4.2 Update Location

See subclause 4.6.8.3.

7.6.4.3 Update GPRS Location

7.6.4.3.1 Description

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 3GPP TS 29.002 [34].

7.6.4.3.2 Information Elements

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

7.6.5.1 Continue CAMEL SMS Handling

7.6.5.1.1 Description

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

7.6.5.1.2 Information Elements

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

7.6.5.2.1 Description

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

7.6.5.2.2 Information Elements

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

7.6.6.1 Send Info For MT SMS

7.6.6.1.1 Description

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

7.6.6.1.2 Information Elements

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.