Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.038  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4   5   6…   6.2…   A…   A.3…   B…   C…

 

4  SMS Data Coding Schemep. 8

The TP-Data-Coding-Scheme field, defined in TS 23.040, indicates the data coding scheme of the TP-UD field, and may indicate a message class. Any reserved codings shall be assumed to be the GSM 7 bit default alphabet (the same as codepoint 00000000) by a receiving entity. The octet is used according to a coding group which is indicated in bits 7..4. The octet is then coded as follows:
Coding Group Bits
7..4
Use of bits 3..0
00xx General Data Coding indication Bits 5..0 indicate the following:
Bit 5, if set to 0, indicates the text is uncompressed
Bit 5, if set to 1, indicates the text is compressed using the compression algorithm defined in TS 23.042
Bit 4, if set to 0, indicates that bits 1 to 0 are reserved and have no message class meaning
Bit 4, if set to 1, indicates that bits 1 to 0 have a message class meaning::
Bit 1  Bit 0  Message Class
0      0      Class 0
0      1      Class 1  Default meaning: ME-specific.
1      0      Class 2  (U)SIM specific message
1      1      Class 3  Default meaning: TE specific (see TS 27.005)
Bits 3 and 2 indicate the character set being used, as follows :
Bit 3  Bit 2  Character set:
0      0      GSM 7 bit default alphabet
0      1      8 bit data
1      0      UCS2 (16bit) [10]
1      1      Reserved
01xx Message Marked for Automatic Deletion Group
This group can be used by the SM originator to mark the message ( stored in the ME or (U)SIM ) for deletion after reading irrespective of the message class. The way the ME will process this deletion should be manufacturer specific but shall be done without the intervention of the End User or the targeted application. The mobile manufacturer may optionally provide a means for the user to prevent this automatic deletion.
Bit 5..0 are coded exactly the same as Group 00xx
1000..1011 Reserved coding groups
1100 Message Waiting Indication Group: Discard Message
The specification for this group is exactly the same as for Group 1101, except that:
  • after presenting an indication and storing the status, the ME may discard the contents of the message.
The ME shall be able to receive, process and acknowledge messages in this group, irrespective of memory availability for other types of short message.
1101 Message Waiting Indication Group: Store Message
This Group defines an indication to be provided to the user about the status of types of message waiting on systems connected to the GSM/UMTS PLMN. The ME should present this indication as an icon on the screen, or other MMI indication. The ME shall update the contents of the Message Waiting Indication Status on the SIM (see TS 51.011) or USIM (see TS 31.102) when present or otherwise should store the status in the ME. In case there are multiple records of EFMWIS this information shall be stored within the first record. The contents of the Message Waiting Indication Status should control the ME indicator. For each indication supported, the mobile may provide storage for the Origination Address. The ME may take note of the Origination Address for messages in this group and group 1100.
Text included in the user data is coded in the GSM 7 bit default alphabet. Where a message is received with bits 7..4 set to 1101, the mobile shall store the text of the SMS message in addition to setting the indication. The indication setting should take place irrespective of memory availability to store the short message.
Bit 3 indicates Indication Sense:
Bit 3
0     Set Indication Inactive
1     Set Indication Active
Bit 2 is reserved, and set to 0
Bit 1  Bit 0  Indication Type:
0      0      Voicemail Message Waiting
0      1      Fax Message Waiting
1      0      Electronic Mail Message Waiting
1      1      Other Message Waiting*
* Mobile manufacturers may implement the "Other Message Waiting" indication as an additional indication without specifying the meaning.
1110 Message Waiting Indication Group: Store Message
The coding of bits 3..0 and functionality of this feature are the same as for the Message Waiting Indication Group above, (bits 7..4 set to 1101) with the exception that the text included in the user data is coded in the uncompressed UCS2 character set.
1111 Data coding/message class
Bit 3 is reserved, set to 0.
Bit 2  Message coding:
0      GSM 7 bit default alphabet
1      8-bit data
Bit 1  Bit 0  Message Class:
0      0      Class 0
0      1      Class 1  default meaning: ME-specific.
1      0      Class 2  (U)SIM-specific message.
1      1      Class 3  default meaning: TE specific
                       (see TS 27.005)
GSM 7 bit default alphabet indicates that the TP-UD is coded from the GSM 7 bit default alphabet given in clause 6.2.1. When this character set is used, the characters of the message are packed in octets as shown in clause 6.1.2.1.1, and the message can consist of up to 160 characters. The GSM 7 bit default alphabet shall be supported by all MSs and SCs offering the service. If the GSM 7 bit default alphabet extension mechanism is used then the number of displayable characters will reduce by one for every instance where the GSM 7 bit default alphabet extension table is used. 8-bit data indicates that the TP-UD has user-defined coding, and the message can consist of up to 140 octets.
UCS2 character set indicates that the TP-UD has a UCS2 [10] coded message, and the message can consist of up to 140 octets, i.e. up to 70 UCS2 characters. The General notes specified in clause 6.1.1 override any contrary specification in UCS2, so for example even in UCS2 a <CR> character will cause the MS to return to the beginning of the current line and overwrite any existing text with the characters which follow the <CR>.
When a message is compressed, the TP-UD consists of the GSM 7 bit default alphabet or UCS2 character set compressed message, and the compressed message itself can consist of up to 140 octets in total.
When a mobile terminated message is class 0 and the MS has the capability of displaying short messages, the MS shall display the message immediately and send an acknowledgement to the SC when the message has successfully reached the MS irrespective of whether there is memory available in the (U)SIM or ME. The message shall not be automatically stored in the (U)SIM or ME.
The ME may make provision through MMI for the user to selectively prevent the message from being displayed immediately.
If the ME is incapable of displaying short messages or if the immediate display of the message has been disabled through MMI then the ME shall treat the short message as though there was no message class, i.e. it will ignore bits 0 and 1 in the TP-DCS and normal rules for memory capacity exceeded shall apply.
When a mobile terminated message is Class 1, the MS shall send an acknowledgement to the SC when the message has successfully reached the MS and can be stored. The MS shall normally store the message in the ME by default, if that is possible, but otherwise the message may be stored elsewhere, e.g. in the (U)SIM. The user may be able to override the default meaning and select their own routing.
When a mobile terminated message is Class 2 ((U)SIM-specific), an MS shall ensure that the message has been transferred to the SMS data field in the (U)SIM before sending an acknowledgement to the SC. The MS shall return a "protocol error, unspecified" error message (see TS 24.011) if the short message cannot be stored in the (U)SIM and there is other short message storage available at the MS. If all the short message storage at the MS is already in use, the MS shall return "memory capacity exceeded". This behaviour applies in all cases except for an MS supporting (U)SIM Application Toolkit when the Protocol Identifier (TP-PID) of the mobile terminated message is set to "(U)SIM Data download" (see TS 23.040).
When a mobile terminated message is Class 3, the MS shall send an acknowledgement to the SC when the message has successfully reached the MS and can be stored, irrespectively of whether the MS supports an SMS interface to a TE, and without waiting for the message to be transferred to the TE. Thus the acknowledgement to the SC of a TE-specific message does not imply that the message has reached the TE. Class 3 messages shall normally be transferred to the TE when the TE requests "TE-specific" messages (see TS 27.005). The user may be able to override the default meaning and select their own routing.
The message class codes may also be used for mobile originated messages, to provide an indication to the destination SME of how the message was handled at the MS.
The MS will not interpret reserved or unsupported values but shall store them as received. The SC may reject messages with a Data Coding Scheme containing a reserved value or one which is not supported.
Up

Up   Top   ToC