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.2.3 SMS-STATUS-REPORT type p. 58
| 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-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-SRQ | TP-Status-Report-Qualifier | M | b | Parameter indicating whether the previously submitted TPDU was an SMS-SUBMIT or an SMS-COMMAND |
| TP-MR | TP-Message-Reference 3) | M | I | Parameter identifying the previously submitted SMS-SUBMIT or SMS-COMMAND |
| TP-RA | TP-Recipient-Address | M | 2-12o | Address of the recipient of the previously submitted mobile originated short message |
| TP-SCTS | TP-Service-Centre-Time-Stamp | M | 7o | Parameter identifying time when the SC received the previously sent SMS-SUBMIT |
| TP-DT | TP-Discharge-Time | M | 7o | Parameter identifying the time associated with a particular TP-ST outcome |
| TP-ST | TP-Status | M | O | Parameter identifying the status of the previously sent mobile originated short message |
| TP-PI | TP-Parameter-Indicator | O (Note 4) | 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-PID of original SMS-SUBMIT |
| 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 | (Note 5) | see clause 9.2.3.24 |
|
NOTE 1:
Provision:
NOTE 2:
Mandatory (M) or Optional (O).
Representation:
NOTE 3:
Integer (I), bit (b), 2 bits (2b), Octet (o), 7 octets (7o), 2-12 octets (2-12o).
Where the SMS-STATUS-REPORT is the result of an SMS-COMMAND and the TP-Command-Type was an Enquiry, the TP-MR returned in the SMS-STATUS-REPORT shall be the TP-MN which was sent in the SMS-COMMAND (i.e. the TP-MR of the previously submitted SM to which the Enquiry refers).
NOTE 4:
Mandatory if any of the optional parameters following TP-PI is present, otherwise optional.
NOTE 5:
TP-UD contains information related to a SMS-DELIVER; can contain information transported in the TP-UD of SMS-DELIVER-REPORT, and information inserted by the SMSC. The length of the TP-UD field is limited and might not be long enough to fit information both from the original receiving terminal (as included into the SMS-DELIVER-REPORT) and information added by the SMSC. In these cases the former information has higher priority, and the latter shall be truncated.
|
||||
9.2.2.4 SMS-COMMAND type p. 60
| Abbr. | Reference | P (Note 1) |
R (Note 2) |
Description |
|---|---|---|---|---|
| TP-MTI | TP-Message-Type-Indicator | M | 2b | Parameter describing the type |
| TP-UDHI | TP-User-Data-Header-Indication | O | b | Parameter indicating that the TP-CD field contains a Header |
| TP-SRR | TP-Status-Report- Request | O | b | Parameter indicating if the SMS Command is requesting a status report. |
| TP-MR | TP-Message Reference | M | I | Parameter identifying the SMS-COMMAND |
| TP-PID | TP-Protocol- Identifier | M | O | Parameter identifying the above layer protocol, if any |
| TP-CT | TP-Command-Type | M | O | Parameter specifying which operation is to be performed on a SM |
| TP-MN | TP-Message-Number | M (Note 3) | O | Parameter indicating which SM in the SC to operate on |
| TP-DA | TP-Destination-Address | M (Note 4) | 2-12o | Parameter indicating the Destination Address to which the TP-Command refers |
| TP-CDL | TP-Command-Data-Length | M | O | Parameter indicating the length of the TP-CD field in octets |
| TP-CD | TP-Command-Data | O | O | Parameter containing user data |
|
NOTE 1:
Provision:
NOTE 2:
Mandatory (M) or Optional (O).
Representation:
NOTE 3:
Integer (I), bit (b), 2bits (2b), octet (o).
For TP-Command-Types which are not for a specific SM this field shall be ignored when received. Its value is of no concern but the field must be present to maintain the structure.
NOTE 4:
For certain TP-Command-Types which operate on a specific SM (e.g. Enquire, Delete etc.) the full TP-DA must be specified. For TP-Command-Types which do not operate on a specific SM, the address length must be set to zero indicating that the Address-Value fields are not present. The Type-of-Address field must be present (see 9.1.2.5) and shall be set to zero and ignored.
|
||||
