The CBS Data Coding Scheme indicates the intended handling of the message at the MS, the character set/coding, and the language (when applicable). Any reserved codings shall be assumed to be the GSM 7 bit default alphabet (the same as codepoint 00001111) 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:

0000  German
0001  English
0010  Italian
0011  French
0100  Spanish
0101  Dutch
0110  Swedish
0111  Danish
1000  Portuguese
1001  Finnish
1010  Norwegian
1011  Greek
1100  Turkish
1101  Hungarian
1110  Polish
1111  Language unspecified

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)

Bit 3  Bit 2  Character set:
0      0      GSM 7 bit default alphabet
0      1      8 bit data
1      0      UCS2 (16 bit) [10]
1      1      Reserved

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)

Bit 3  Bit 2  Alphabet:
0      0      GSM 7 bit default alphabet
0      1      8 bit data
1      0      UCS2 (16 bit) [10]
1      1      Reserved

Bit 2  Message coding:
0      GSM 7 bit default alphabet
1      8 bit data	

Bit 1  Bit 0  Message Class:
0      0      No message class.
0      1      Class 1  user defined.
1      0      Class 2  user defined.
1      1      Class 3  default meaning: TE specific
                       (see TS 27.005)	

These codings may also be used for USSD and MMI/display purposes. The message length specified in this subclause is not applicable for UTRAN, E-UTRAN, and NG-RAN, but only applicable for GSM. See TS 24.090 for specific coding values applicable to USSD for MS originated USSD messages and MS terminated USSD messages. USSD messages using the default alphabet are coded with the GSM 7-bit default alphabet given in clause 6.2.1. The message can then consist of up to 182 user characters. Cell Broadcast messages using the default alphabet are coded with the GSM 7-bit default alphabet given in clause 6.2.1. The Message Information Page then consists of 93 user characters. 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 usedCell Broadcast Messages Information Page using 8-bit data have user-defined coding, and will each be 82 octets in length. UCS2 character set indicates that the message is coded in UCS2 [10]. 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>. Cell Broadcast Messages Information Page encoded in UCS2 consist of 41 characters each. When a CBS message received by the MS is message class 0 and the MS has the capability of displaying CBS messages, the MS shall display the message immediately. 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 CBS messages or if the immediate display of the message has been disabled through MMI then the ME shall treat the CBS message as though there was no message class, i.e. it will ignore bits 0 and 1 in the TP-DCS but may store the message either on the ME or on the (U)SIM. Class 1 and Class 2 messages may be routed by the ME to user-defined destinations, but the user may override any default meaning and select their own routing. Class 3 messages will normally be selected for transfer to a TE, in cases where a ME supports an SMS/CBS interface to a TE, and the TE requests "TE-specific" cell broadcast messages (see TS 27.005). The user may be able to override the default meaning and select their own routing. Messages with a User Data Header Structure are encoded as described in TS 23.040 for SMS, in subclauses 3.10 and 9.2.3.24. The use of Cell Broadcast DCS values for messages with a User Data Header structure implies that the 82-bytes CB payload has a User Data Header structure. The CBS message information field will contain the IEs as described in TS 23.040. The concatenation IEs will not be used, as CB concatenation will rely in that case on the existing CB mechanism. Note that IEs that cannot be split and that IEs that are too large to fit in one CB segment cannot be transmitted using this mechanism. Also, some IEs as defined for SMS are not applicable for CB: