| Bit no | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
|---|---|---|---|---|---|---|---|---|
| Name | TP-RP | TP-UDHI | TP-SRR | TP-VPF | TP-VPF | TP-RD | TP-MTI | TP-MTI |
| Fieldname | Meaning |
|---|---|
| TP-RP | Reply path. Parameter indicating that reply path exists. |
| TP-UDHI | User data header indicator. This bit is set to 1 if the User Data field starts with a header |
| TP-SRR | Status report request. This bit is set to 1 if a status report is requested |
| TP-VPF | Validity Period Format. Bit4 and Bit3
specify the TP-VP field according to this table: bit4 bit3 0 0 : TP-VP field not present 1 0 : TP-VP field present. Relative format (one octet) 0 1 : TP-VP field present. Enhanced format (7 octets) 1 1 : TP-VP field present. Absolute format (7 octets) |
| TP-RD | Reject duplicates. Parameter 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-MTI | Message type indicator. Bits no 1 and 0 are set to 0 and 1 respectively to indicate that this PDU is an SMS-SUBMIT |
| Bit no | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
|---|---|---|---|---|---|---|---|---|
| Name | TP-RP | TP-UDHI | TP-SRR | TP-VPF | TP-VPF | TP-RD | TP-MTI | TP-MTI |
| Value | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 |