Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.040  Word version:  18.0.0

Top   Top   Up   Prev   Next
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.2.2 SMS-SUBMIT type  9.2.2.2a SMS-SUBMIT-REPORT type 
...

 

9.2.2.2  SMS-SUBMIT type  p. 54

Abbr. Reference P
(Note 1)		 R
(Note 2)		 Description
TP-MTITP-Message-Type-IndicatorM2bParameter describing the message type.
TP-RDTP-Reject-DuplicatesMbParameter indicating whether or not the SC shall accept an SMS-SUBMIT for an SM still held in the SC which has the same TP-MR and the same TP-DA as a previously submitted SM from the same OA
TP-VPFTP-Validity-Period-FormatM2bParameter indicating whether or not the TP-VP field is present.
TP-RPTP-Reply-PathMbParameter indicating the request for Reply Path.
TP-UDHITP-User-Data-Header-IndicatorObParameter indicating that the TP-UD field contains a Header.
TP-SRRTP-Status-Report-RequestObParameter indicating if the MS is requesting a status report.
TP-MRTP-Message-ReferenceMIParameter identifying the SMS-SUBMIT.
TP-DATP-Destination-AddressM2-12oAddress of the destination SME.
TP-PIDTP-Protocol-IdentifierMOParameter identifying the above layer protocol, if any.
TP-DCSTP-Data-Coding-SchemeMOParameter identifying the coding scheme within the TP-User-Data.
TP-VPTP-Validity-PeriodOo/7oParameter identifying the time from where the message is no longer valid.
TP-UDLTP-User-Data-LengthMIParameter indicating the length of the TP-User-Data field to follow.
TP-UDTP-User-DataO(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.2-1: Layout of SMS-SUBMIT
Figure 9.2.2.2-1: Layout of SMS-SUBMIT
(⇒ copy of original 3GPP image)
Up

9.2.2.2a  SMS-SUBMIT-REPORT type  p. 56

An SMS-SUBMIT-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-SUBMIT or SMS-COMMAND.
An SMS-SUBMIT-REPORT TPDU is also carried as a RP-User-Data element with an RP-ACK PDU and is part of a positive acknowledgement to a SMS-SUBMIT or SMS-COMMAND.
(i) SMS-SUBMIT-REPORT for RP-ERROR
Abbr. Reference P
(Note 1)		 R
(Note 2)		 Description
TP-MTITP-Message-Type-IndicatorM2bParameter describing the message type
TP-UDHITP-User-Data-Header-IndicationObParameter indicating that the TP-UD field contains a Header
TP-FCSTP-Failure-CauseMIParameter indicating the reason for SMS-SUBMIT failure
TP-PITP-Parameter-IndicatorMOParameter indicating the presence of any of the optional parameters which follow
TP-SCTSTP-Service-Centre-Time-StampM7o
(Note 5)		Parameter identifying the time when the SC received the SMS-SUBMIT See clause 9.2.3.11
TP-PIDTP-Protocol-IdentifierOOSee clause 9.2.3.9
TP-DCSTP-Data-Coding-SchemeOOsee clause 9.2.3.10
TP-UDLTP-User-Data-LengthOOsee clause 9.2.3.16
TP-UDTP-User-DataONotes
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-SUBMIT-REPORT is only available for use by the SC.
NOTE 5:
This same time value shall also be carried in the SMS-STATUS-REPORT relating to a particular SM. See clause 9.2.2.3. This shall allow the submitting SME to associate a particular SMS-SUBMIT with a subsequent SMS-STATUS-REPORT by correlating the TP-SCTS values.
Copy of original 3GPP image for 3GPP TS 23.040, Fig. 9.2.2.2a-1: Layout of SMS-SUBMIT-REPORT for RP-ERROR
Figure 9.2.2.2a-1: Layout of SMS-SUBMIT-REPORT for RP-ERROR
(⇒ copy of original 3GPP image)
Up
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-SUBMIT-REPORT for RP-ACK
Abbr. Reference P
(Note 1)		 R
(Note 2)		 Description
TP-MTITP-Message Type-IndicatorM2bParameter describing the message type
TP-UDHITP-User-Data-Header-IndicationObParameter indicating that the TP-UD field contains a Header
TP-PITP-Parameter-IndicatorMOParameter indicating the presence of any of the optional parameters which follow
TP-SCTSTP-Service-Centre-Time-StampM7o
(Note 5)		Parameter identifying the time when the SC received the SMS-SUBMIT See clause 9.2.3.11
TP-PIDTP-Protocol-IdentifierOOSee clause 9.2.3.9
TP-DCSTP-Data-Coding-SchemeOOsee clause 9.2.3.10
TP-UDLTP-User-Data-LengthOOsee clause 9.2.3.16
TP-UDTP-User-DataONotes
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-SUBMIT-REPORT is only available for use by the SC.
NOTE 5:
This same time value shall also be carried in the SMS-STATUS-REPORT relating to a particular SM. See clause 9.2.2.3. This shall allow the submitting SME to associate a particular SMS-SUBMIT with a subsequent SMS-STATUS-REPORT by correlating the TP-SCTS values.
Copy of original 3GPP image for 3GPP TS 23.040, Fig. 9.2.2.2a-2: Layout of SMS-SUBMIT-REPORT for RP-ACK
Figure 9.2.2.2a-2: Layout of SMS-SUBMIT-REPORT for RP-ACK
(⇒ copy of original 3GPP image)
Up
Bits 7 and 5 - 2 in octet 1 are presently unused in the SMS-SUBMIT-REPORT and the sender shall set them to zero. If any of these bits is non-zero, the receiver shall ignore them.

Up   Top   ToC