Content for TS 23.040 Word version: 18.0.0

0… 3… 3.3… 4… 8… 9… 9.2… 9.2.2.2… 9.2.2.3… 9.2.3… 9.2.3.12… 9.2.3.24 9.2.3.24.1… 9.2.3.24.10… 9.2.3.24.10.1.12… 9.2.3.24.10.2… 9.2.3.24.11… 9.2.3.25… 9.3… 10… 10.1.1… 10.1.3… 10.1.5… 10.1.7… 10.1.9… 10.1.11… 10.1.13… 10.1.15… 10.1.17… 10.2 10.2.1… 10.2.3… 10.2.5… 10.2.7… 10.3 11… A… C C.1… C.3… C.5… C.7… C.9… C.11… C.13… C.15… D… E… F… G… G.2… G.6 G.7 H… I… J… K…

9.2 Service provided by the SM-TL 9.2.1 General 9.2.2 PDU Type repertoire at SM-TL 9.2.2.1 SMS-DELIVER type 9.2.2.1a SMS-DELIVER-REPORT type
...

9.2 Service provided by the SM-TL p. 49

9.2.1 General p. 49

The Short Message Transfer Layer (SM-TL) provides a service to the Short Message Application Layer (SM-AL). This service enables the SM-AL to transfer short messages to its peer entity, receive short messages from its peer entity and receive reports about earlier requests for short messages to be transferred.

In order to keep track of messages and reports about those messages, primitives between the SM-AL and SM-TL contain a Short Message Identifier (SMI), which is a reference number for the message associated with the primitive. This Short Message Identifier is mapped to and from the Short Message Identifier used between the SM-TL and the Short Message Relay Layer (SM-RL). The Short Message Identifier is not carried between entities and therefore a given message may have different SMIs at the MS and SC sides (see clause 9.3.1 below).

The SM-TL communicates with its peer entity by the protocol described in the following clauses.

9.2.2 PDU Type repertoire at SM-TL p. 49

The SM-TL comprises the following six PDUs:

SMS-DELIVER, conveying a short message from the SC to the MS;

SMS-DELIVER-REPORT, conveying;

a failure cause (if necessary);
information as part of a positive or negative acknowledgement to an SMS-DELIVER or SMS-STATUS-REPORT;

SMS-SUBMIT, conveying a short message from the MS to the SC;

SMS-SUBMIT-REPORT, conveying;

a failure cause (if necessary);
information as part of a positive or negative acknowledgement to an SMS-SUBMIT or SMS-COMMAND;

SMS-STATUS-REPORT, conveying a status report from the SC to the MS;

SMS-COMMAND, conveying a command from the MS to the SC.

9.2.2.1 SMS-DELIVER type p. 50

Table 9.2.2.1-1: Basic elements of the SMS-DELIVER type

Abbr.	Reference	P (Note 1)	R (Note 2)	Description
TP-MTI	TP-Message-Type-Indicator	M	2b	Parameter describing the message type.
TP-MMS	TP-More-Messages-to-Send	M	b	Parameter indicating whether or not there are more messages to send
TP-LP	TP-Loop-Prevention	O	b	Parameter indicating that SMS applications should inhibit forwarding or automatic message generation that could cause infinite looping.
TP-RP	TP-Reply-Path	M	b	Parameter indicating that Reply Path exists.
TP-UDHI	TP-User-Data-Header-Indicator	O	b	Parameter indicating that the TP-UD field contains a Header
TP-SRI	TP-Status-Report-Indication	O	b	Parameter indicating if the SME has requested a status report.
TP-OA	TP-Originating-Address	M	2-12o	Address of the originating SME.
TP-PID	TP-Protocol-Identifier	M	O	Parameter identifying the above layer protocol, if any.
TP-DCS	TP-Data-Coding-Scheme	M	O	Parameter identifying the coding scheme within the TP-User-Data.
TP-SCTS	TP-Service-Centre-Time-Stamp	M	7o	Parameter identifying time when the SC received the message.
TP-UDL	TP-User-Data-Length	M	I	Parameter indicating the length of the TP-User-Data field to follow.
TP-UD	TP-User-Data	O	(Note 3)
NOTE 1: Provision: Mandatory (M) or Optional (O). NOTE 2: Representation: Integer (I), bit (b), 2 bits (2b), Octet (o), 7 octets (7o), 2-12 octets (2-12o). NOTE 3: Dependent on the TP-DCS.

Copy of original 3GPP image for 3GPP TS 23.040, Fig. 9.2.2.1-1: Layout of SMS-DELIVER

Figure 9.2.2.1-1: Layout of SMS-DELIVER
(⇒ copy of original 3GPP image)

9.2.2.1a SMS-DELIVER-REPORT type p. 52

An SMS-DELIVER-REPORT TPDU is carried as a RP-User-Data element within an RP-ERROR PDU and is part of the negative acknowledgement to an SMS-DELIVER or SMS-STATUS-REPORT.

An SMS-DELIVER-REPORT TPDU is also carried as a RP-User-Data element within an RP-ACK PDU and is part of a positive acknowledgement to a SMS-DELIVER or SMS-STATUS REPORT.

(i) SMS-DELIVER-REPORT for RP-ERROR

Table 9.2.2.1a-1: Basic elements of the SMS-DELIVER-REPORT type for RP-ERROR

Abbr.	Reference	P (Note 1)	R (Note 2)	Description
TP-MTI	TP-Message-Type-Indicator	M	2b	Parameter describing the message type
TP-UDHI	TP-User-Data-Header-Indication	O	b	Parameter indicating that the TP-UD field contains a Header
TP-FCS	TP-Failure-Cause	M	I	Parameter indicating the reason for SMS-DELIVER failure
TP-PI	TP-Parameter-Indicator	M	O	Parameter indicating the presence of any of the optional parameters which follow
TP-PID	TP-Protocol-Identifier	O	O	see clause 9.2.3.9
TP-DCS	TP-Data-Coding-Scheme	O	O	see clause 9.2.3.10
TP-UDL	TP-User-Data-Length	O	O	see clause 9.2.3.16
TP-UD	TP-User-Data	O	Notes 3 and 4	see clause 9.2.3.24
NOTE 1: Provision: Mandatory (M) or Optional (O). NOTE 2: Representation: Integer (I), bit (b), 2bits (2b), octet (o). NOTE 3: Dependent upon the TP-DCS. NOTE 4: The TP-User-Data field in the SMS-DELIVER-REPORT is only available for use by the MT.

Copy of original 3GPP image for 3GPP TS 23.040, Fig. 9.2.2.1a-1: Layout of SMS-DELIVER-REPORT for RP-ERROR

Figure 9.2.2.1a-1: Layout of SMS-DELIVER-REPORT for RP-ERROR
(⇒ copy of original 3GPP image)

Bits 7 and 5 - 2 in octet 1 are presently unused and the sender shall set them to zero. If any of these bits is non-zero, the receiver shall not examine the other field and shall treat the TP-Failure-Cause as "Unspecified error cause".

(ii) SMS-DELIVER-REPORT for RP-ACK

Table 9.2.2.1a-2: Basic elements of the SMS-DELIVER-REPORT type for RP-ACK

Abbr.	Reference	P (Note 1)	R (Note 2)	Description
TP-MTI	TP-Message Type Indicator	M	2b	Parameter describing the message type
TP-UDHI	TP-User-Data-Header-Indication	O	b	Parameter indicating that the TP-UD field contains a Header
TP-PI	TP-Parameter-Indicator	M	O	Parameter indicating the presence of any of the optional parameters which follow
TP-PID	TP-Protocol-Identifier	O	O	see clause 9.2.3.9
TP-DCS	TP-Data-Coding-Scheme	O	O	see clause 9.2.3.10
TP-UDL	TP-User-Data-Length	O	O	see clause 9.2.3.16
TP-UD	TP-User-Data	O	Notes 3 and 4	see clause 9.2.3.24
NOTE 1: Provision: Mandatory (M) or Optional (O). NOTE 2: Representation: Integer (I), Bit (b), 2 bits (2b), octet (o). NOTE 3: Dependent upon the TP-DCS. NOTE 4: The TP-User-Data field in the SMS-DELIVER-REPORT is only available for use by the MT.

Copy of original 3GPP image for 3GPP TS 23.040, Fig. 9.2.2.1a-2: Layout of SMS-DELIVER-REPORT for RP-ACK

Figure 9.2.2.1a-2: Layout of SMS-DELIVER-REPORT for RP-ACK
(⇒ copy of original 3GPP image)

Bits 7 and 5 - 2 in octet 1 are presently unused in the SMS-DELIVER-REPORT and the sender shall set them to zero. If any of these bits is non-zero, the receiver shall ignore them.