4.2.25 EFSMS (Short messages)
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
If service n° 10 is "available", this file shall be present.
This EF contains information in accordance with TS 23.040 [6] comprising short messages (and associated parameters) which have either been received by the UE from the network, or are to be used as an UE originated message.
|
Identifier: ‘6F3C’ |
Structure: linear fixed |
Optional |
||||
|
Record length: 176 bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
Status |
M |
1 byte |
|||
|
2 to 176 |
Remainder |
M |
175 bytes |
|||
‑ Status.
Contents:
Status byte of the record which can be used as a pattern in the SEARCH RECORD command. For UE originating messages sent to the network, the status shall be updated when the UE receives a status report, or sends a successful SMS Command relating to the status report.
Coding:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
|||||||||||||
|
X |
X |
0 |
free space |
|||||||||||||||||
|
X |
X |
1 |
used space |
|||||||||||||||||
|
0 |
0 |
1 |
message received by UE from network; message read |
|||||||||||||||||
|
0 |
1 |
1 |
message received by UE from network; message to be read |
|||||||||||||||||
|
1 |
1 |
1 |
UE originating message; message to be sent |
|||||||||||||||||
|
RFU (see TS 31.101 [11]) |
||||||||||||||||||||
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
||||||||||||
|
X |
X |
1 |
0 |
1 |
UE originating message; message sent to the network: |
||||||||||||||
|
0 |
0 |
1 |
0 |
1 |
Status report not requested |
||||||||||||||
|
0 |
1 |
1 |
0 |
1 |
Status report requested but not (yet) received; |
||||||||||||||
|
1 |
0 |
1 |
0 |
1 |
Status report requested, received but not stored in EF-SMSR; |
||||||||||||||
|
1 |
1 |
1 |
0 |
1 |
Status report requested, received and stored in EF-SMSR; |
||||||||||||||
|
RFU (see TS 31.101 [11]) |
|||||||||||||||||||
‑ Remainder.
Contents:
This data item commences with the TS‑Service‑Centre‑Address as specified in TS 24.011 [10]. The bytes immediately following the TS‑Service‑Centre‑Address contain an appropriate short message TPDU as specified in TS 23.040 [6], with identical coding and ordering of parameters.
Coding:
according to TS 23.040 [6] and TS 24.011 [10]. Any TP‑message reference contained in an UE originated message stored in the USIM, shall have a value as follows:
Value of the TP‑message‑reference:
message to be sent: ‘FF’.
Message sent to the network: the value of TP‑Message‑Reference used in the
message sent to the network.
Any bytes in the record following the TPDU shall be filled with ‘FF’.
It is possible for a TS‑Service‑Centre‑Address of maximum permitted length, e.g. containing more than 18 address digits, to be associated with a maximum length TPDU such that their combined length is 176 bytes. In this case the ME shall store in the USIM the TS‑Service‑Centre‑Address and the TPDU in bytes 2 to 176 without modification, except for the last byte of the TPDU, which shall not be stored.