Content for  TS 23.040  Word version:  18.0.0

This information element is used to indicate the existence of an IETF RFC 5322 Internet electronic mail in the data part of the short message. Both, E-Mail Header and (optional) E-Mail Body shall be parts of the SM's data and shall be compliant with the syntax specified in IETF RFC 5322. The character set used for encoding of E-Mail Header and E-Mail body, however, shall be according to TS 23.038. Encoding of E-Mail Header and E-Mail Body shall be done using the same character set. In compliance with IETF RFC 5322 the E-Mail Header shall always be located at the very beginning of the SM's data part. It shall always be present in the "unfolded" format as it is specified in IETF RFC 5322. Not the <CRLF> character defined in IETF RFC 5322 but the <LF> character according to TS 23.038 shall be used for the separation of different E-Mail Header fields. If an RFC 5322 E-Mail Body exists, it shall immediately follow the E-Mail Header in the SM's data part. In case of an IETF RFC 5322 E-Mail Header exceeding the data part of a single SM, concatenation shall be used. In this case the E-Mail Header starts in the first segment of a concatenated SM and continues in one or several subsequent segments. The IETF RFC 5322 E-Mail Body shall immediately follow the final fraction of the IETF RFC 5322 E-Mail Header and may also be spread over several segments of the concatenated SM. In case where this IEI is to be used in a concatenated SM then the IEI, its associated IEDL, and IED fields shall be contained in the first segment of the concatenated SM and shall also be contained in every subsequent segment of the concatenated SM. The Information-Element-Data octet shall be coded as follows:

The diagram below shows the layout of the IED for 8 bit data.

The diagram below shows the layout of the IED for UCS2 data.

A hyperlink format element shall be structured as follows:

Enhanced Voice Mail Information allows a Voice Mail system to convey to a mobile subscriber, comprehensive information regarding individual voice mail messages and mailbox status. Enhanced Voice Mail Information has two types of Information Element Data

• Enhanced Voice Mail Notification which conveys to the MS information regarding newly deposited Voice Mail messages and Voice Mailbox Status
• Enhanced Voice Mail Delete Confirmation which allows an MS to maintain Voice mailbox status information synchronisation between the MS and the Voice Mailbox in the event of Voice Mail Message deletion.

The first 'bit' of the Enhanced Voice Mail Information Element Data is known as Enhanced Voice Mail PDU Type and discriminates between whether the Enhanced Voice Mail Information PDU is an Enhanced Voice Mail Notification or an Enhanced Voice Mail Delete Confirmation.

  00  profile ID 1
  10  profile ID 2
  01  profile ID 3
  11  profile ID 4

A directory number may, as an optional feature, be identified within the User Data Field. This allows, for example, a receiving entity to automatically identify a string of digits in the User Data Field as being a telephone number in order to facilitate easy call back by user action. This shall be implemented by enclosing the directory number in inverted commas (character 0100010 from the 7 bit default alphabet in TS 23.038 or its equivalent in other character sets). Unspecified address formats or International address formats (using + symbol) may be used for the directory number. Spaces may be included with the directory number inside the inverted commas. E.g. "+1 234 567 8901" The User Data Field displayed to the recipient may contain more than one directory number, in which case it is for the user to select the one required.

This information element is used to indicate which National Language Single Shift Table is used instead of the GSM 7 bit default alphabet extension table specified in TS 23.038. The total length of the IE is 1 octet: The National Language Identifier values and Language tables are defined in TS 23.038. A receiving entity shall ignore (i.e. skip over and commence processing at the next information element) this information element if the value of the National Language Identifier is not described in TS 23.038. If this IE is duplicated within different segments of a concatenated message then a receiving entity shall process each segment individually. If this IE is not included within a segment of a concatenated message then the receiving entity shall use the GSM 7 bit default alphabet extension table for this segment. In the event that this IE is duplicated within one segment of a concatenated message or a single message then a receiving entity shall use the last occurrence of the IE. In the event that this IE is received within a single message or a segment of a concatenated message, in which the DCS has indicated UCS-2 encoding, then the receiving entity shall ignore this IE.

This information element is used to indicate which National Language Locking Shift Table is used instead of the GSM 7 bit default alphabet specified in TS 23.038. This IE is coded in the same way as the National Language Single Shift IE in clause 9.2.3.24.15. A receiving entity shall ignore (i.e. skip over and commence processing at the next information element) this information element if the value of the National Language Identifier is not described in TS 23.038. If this IE is duplicated within different segments of a concatenated message then a receiving entity shall process each segment individually. If this IE is not included within a segment of a concatenated message then the receiving entity shall use the GSM 7 bit default alphabet table for this segment. In the event that this IE is duplicated within one segment of a concatenated message or a single message then a receiving entity shall use the last occurrence of the IE. In the event that this IE is received within a single message or a segment of a concatenated message, in which the DCS has indicated UCS-2 encoding, then the receiving entity shall ignore this IE.

This information element shall be used when there is a requirement to replace IEs in the User Data Header while retaining the original TP-User-Data-Header-Length (UDHL) and TP-User-Data-Length (TP-UDL) values. When the Filler IE is used, the information element data octets shall be set to 0. The length field of the Filler IE shall be set to the same value of the length field of the IE it is replacing. A receiving entity shall ignore (i.e. skip over and commence processing at the next information element) the content of this IE. Multiple occurrences of this IE may occur.