Content for  TS 23.040  Word version:  18.0.0

The TP-Discharge-Time field indicates the time at which a previously submitted SMS-SUBMIT was successfully delivered to or attempted to deliver to the recipient SME or disposed of by the SC. In the case of "transaction completed" the time shall be the time of the completion of the transaction. In the case of "SC still trying to transfer SM" the time shall be the time of the last transfer attempt. In the case of "permanent or temporary error - SC not making any more transfer attempts" the time shall be the time of either the last transfer attempt or the time at which the SC disposed of the SM according to the Status outcome in TP-ST. The TP-Discharge-Time is given in semi-octet representation in a format identical to the TP-SCTS.

The TP-Recipient-Address field indicates the address of the SME that was the destination of the previously submitted mobile originated short message being subject to the status report. The field is formatted according to the formatting rules of address fields.

The TP-Status field indicates the status of a previously submitted SMS-SUBMIT and certain SMS COMMANDS for which a Status -Report has been requested. It consists of one octet and the bits in the octet are used as follows. The MS shall interpret any reserved values as "Service Rejected" (01100011) but shall store them exactly as received.

bits	value/usage
7	0	Bits 0..6 as defined below: 6....0 Indicate whether the previously submitted short message was successfully forwarded to the SME, or whether an error condition has been encountered, as follows: Short message transaction completed 0000000 Short message received by the SME 0000001 Short message forwarded by the SC to the SME but the SC is unable to confirm delivery 0000010 Short message replaced by the SC 0000011..0001111 Reserved 0010000..0011111 Values specific to each SC Temporary error, SC still trying to transfer SM 0100000 Congestion 0100001 SME busy 0100010 No response from SME 0100011 Service rejected 0100100 Quality of service not available 0100101 Error in SME 0100110..0101111 Reserved 0110000..0111111 Values specific to each SC Permanent error, SC is not making any more transfer attempts 1000000 Remote procedure error 1000001 Incompatible destination 1000010 Connection rejected by SME 1000011 Not obtainable 1000100 Quality of service not available 1000101 No interworking available 1000110 SM Validity Period Expired 1000111 SM Deleted by originating SME 1001000 SM Deleted by SC Administration 1001001 SM does not exist (The SM may have previously existed in the SC but the SC no longer has knowledge of it or the SM may never have previously existed in the SC) 1001010..1001111 Reserved 1010000..1011111 Values specific to each SC Temporary error, SC is not making any more transfer attempts 1100000 Congestion 1100001 SME busy 1100010 No response from SME 1100011 Service rejected 1100100 Quality of service not available 1100101 Error in SME 1100110..1101001 Reserved 1101010..1101111 Reserved 1110000..1111111 Values specific to each SC
7	1	Bits 0..6  reserved

If the TP-User-Data is coded using the GSM 7 bit default alphabet, the TP-User-Data-Length field gives an integer representation of the number of septets within the TP-User-Data field to follow. If the 7bit default-alphabet extension mechanism is used within the TP-User-Data (see TS 23.038), the actual number of characters in the message shall be less than the number of septets. If a TP-User-Data-Header field is present, then the TP-User-Data-Length value is the sum of the number of septets in the TP-User-Data-Header field (including any padding) and the number of septets in the TP-User-Data field which follows. See Figure 9.2.3.24 (a). If the TP-User-Data is coded using 8-bit data, the TP-User-Data-Length field gives an integer representation of the number of octets within the TP-User-Data field to follow. If a TP-User-Data-Header field is present, then the TP-User-Data-Length value is the sum of the number of octets in the TP-User-Data-Header field and the number of octets in the TP-User-Data field which follows. See Figure 9.2.3.24 (b). If the TP-User-Data is coded using UCS2 [24] data, the TP-User-Data-Length field gives an integer representation of the number of octets within the TP-User-Data field to follow. If a TP-User-Data-Header field is present, then the TP-User-Data-Length value is the sum of the number of octets in the TP-User-Data-Header field and the number of octets in the TP-User-Data field which follows. See Figure 9.2.3.24 (b). If the TP-User-Data is coded using compressed GSM 7 bit default alphabet or compressed 8 bit data or compressed UCS2 [24] data, the TP-User-Data-Length field gives an integer representation of the number of octets after compression within the TP-User-Data field to follow. If a TP-User-Data-Header field is present, then the TP-User-Data-Length value is the sum of the number of uncompressed octets in the TP-User-Data-Header field and the number of octets in the compressed TP-User-Data field which follows. See Figure 9.2.3.24 (c). For other Data Coding Schemes, see TS 23.038. If this field is zero, the TP-User-Data field shall not be present.

The TP-Reply-Path is a 1-bit field, located within bit no 7 of the first octet of both SMS-DELIVER and SMS-SUBMIT, and to be given the following values: Bit no 7: 0 1 Please refer to Annex D for details about the Reply procedures.

The TP-Message-Number is an 8-bit field allowing an MS to refer uniquely to an SM in the SC which that MS has previously submitted. The TP-MN value is the TP-MR value of a previously submitted SM.

The TP-Command-Type is an 8-bit field specifying the type of operation that the SC is to perform. It has the following values:

The SC shall return an RP-Error with an appropriate TP-Failure-Cause for any TP-Command value which is reserved, unsupported or invalid or the actioning of the command has failed. The SC shall return an RP-ACK if the actioning of the Command has succeeded. A successful Enquiry shall result in the SC sending a SMS-STATUS-REPORT for the SM to which the Enquiry refers. In the case where the SC has a number of SMs which have the same TP-MR, the same TP-DA and have come from the same originating address the SC shall send a SMS-STATUS-REPORT for each SM. In the case where a TP-Command is to Delete a previously submitted short message, the SC shall send a Status Report indicating that the SM has been deleted if the original Submit SM request requested a status Report.

The TP-Command-Data-Length field is used to indicate the number of octets contained within the TP-Command-Data-field. If this field is set to zero, the TP-Command-Data field shall not be present.

The TP-Command-Data field contains data relating to the operation requested by the MS which is to be performed at the SC. The maximum length of this field is 157 octets. The usage and provision of the optional TP-Command-Data field shall be determined by the function selected by the TP-Command-Type field.

The TP-Failure-Cause field is used to report the reason for failure to transfer or process a short message. It consists of a single octet used as follows:

The TP-User-Data-Header-Indicator is a 1 bit field within bit 6 of the first octet of the following six PDUs:

• SMS-SUBMIT,
• SMS-SUBMIT-REPORT,
• SMS-DELIVER,
• SMS-DELIVER-REPORT,
• SMS-STATUS-REPORT,
• SMS-COMMAND.

TP-UDHI has the following values.