Hint: [RX] (TX)
Field Name Length Note MEM 1 Memory type (SIM/Phone) LOC 1 Memory location (1...) ? 1 most of time 0x04 PID 1 Protocol Identifier DCS 1 Data Coding Scheme SCTS 7 Service Centre Time Stamp UDL 1 User Data Length OA PNUM Originating Address SCA PNUM Service Centre Address TA 1 Type of OA
Request SMS (0x25)
Field Length Description MEM 1 Memory Area LOC 1 Location in specified memory area In successful request, phone sends one SMS Header and one or more SMS Data packets. In failure, phone sends SMS Request Failed packet.
SMS Header [0x2c]
Field Length Description MEM 1 Memory Area LOC 1 Location in specified memory area STATUS 2 0701: Saved, not sent
0501: Sent
0304: Received, unread
0204: Unread
0104: Received, readPID 1 Protocol Identifier DCS 1 Data Coding Scheme SCTS 7 Service Centre Time Stamp UDL 1 User Data Length SCA PNUM Service Centre Address OA PNUM Originating Address TA 1 Type of OA SMS Data [0x27]
Message is received in max of 55 octet blocksSequence number starts from 0x01 and is increased by 1 after each block transmitted.
Field Length Description SEQ 1 Sequence number of block UD 1...55 Block of User Data SMS Request Failed [0x2d]
Field Length Description EID 1 Error Identifier
Field Length Description MEM 1 Memory type LOC 1 Location in memory SMS Deleted [0x2e]
SMS Delete Failed [0x2f]
Field Length Description EID 1 Error Identifier
Sending SMS Header (0x23)
Field Length Description FO 1 "The First Octet" PID 1 Protocol Identification DCS 1 Data Coding Scheme VP 7 Validity Period UDL 1 User Data Length SCA PNUM Service Centre Address DA PNUM Destination Address Sending SMS Message (0x27)
Message is sent in max size of 55 octet blocks
Field Length Description SEQ 1 Sequence number of the block UD 1...55 Block of User Data Message Sent [0x28]
Field Length Description MR 1 Message Reference Try Later [0x29]
Field Length Description E1 1 Error E2 1 Error
Field Length Description ? 1 0x06,0x02 ??? DT TP-SCTS Delivery time SCTS TP-SCTS Report time ? 1 always 0x00 ? MR 1 Message Reference DA PNUM Destination Address SCA PNUM Service Centre Address TA 1 Type of DA
Write SMS Settings to phone (0x3c)
Field Length Description MASK 1 Bit mask, which values are saved to ME PID 1 Send Messages As... UK 1 Unknown VP 1 Validity Period in Relative format RP 1 Reply Path SRR 1 Relivery Reports UA PNUM Unused Address SCA PNUM Service Centre Address TA 1 Type of UA (if 0, phone sets to correct value) PID Values for common SMS formats:
Look TP-PID for more info about PID.
Value SEND MESSAGES AS 00 Text 22 Fax 24 Voice 25 ERMES 26 Paging 2d 31 X.400 SMS Settings Wrote [0x3d]
SMS Settings Write Error [0x3e]
MASK
Bit Allow change to 7 ?? 6 SRR 5 RP 4 SCA 3 UA 2 VP 1 UK 0 PID Read SMS Settings from phone (0x3f)
SMS Settings not available [0x40]
SMS Settings from phone [0x41]
Field Length Description MEM 1 Selected memory SMS's in phone 1 Number of SMS's in Phone Unread -''- 1 Number of Unread SMS's in Phone SMS's in SIM 1 Number of SMS's in SIM Unread -''- 1 Number of Unread SMS's in Phone PID 1 Protocol Identifier UK 1 Unknown VP 1 Validity Period in Relative format RP 1 Reply Path SRR 1 Delivery Reports UA PNUM Unknown Address SCA PNUM Service Centre Address TA 1 Type of UA First five fields are read-only data and can not be modified via FBUS.
In case where bits 7 and 6 both are 0:
Bit 7 Bit 6 Usage 0 0 Assigns bits 0..5 as defined below 0 1 Assigns bits 0..5 as defined below 1 0 Reserved 1 1 Assigns bits 0..5 for SC specific use In the case of telematic interworking, the following five bit patterns in bits 4..0 are used to indicate types of telematic devices:
Bit 5 Description 0 no interworking, but SME-to-SME protocol 1 telematic interworking If bit 5 has value 1 in an SMS-SUBMIT PDU, it indicates that the SME is a telematic device of a type which is indicated in bits 4..0, and requests the SC to convert the SM into a form suited for that device type. If the destination network is ISDN, the SC must also select the proper service indicators for connecting to a device of that type.
Bits 4..0 Description 00000 implicit - device type is specific to this SC, or can be concluded on the basis of the address 00001 telex (or teletex reduced to telex format) 00010 group 3 telefax 00011 group 4 telefax 00100 voice telephone (i.e. conversion to speech) 00101 ERMES (European Radio Messaging System) 00110 National Paging System (known to the SC) 00111 Videotex (T.100/T.101) 01000 teletex, carrier unspecified 01001 teletex, in PSPDN 01010 teletex, in CSPDN 01011 teletex, in analog PSTN 01100 teletex, in digital ISDN 01101 UCI (Universal Computer Interface, ETSI DE/PS 3 01-3) 01110..
..01111(reserved, 2 combinations) 10000 a message handling facility (known to the SC) 10001 any public X.400-based message handling system 10010 Internet Electronic Mail 10011..
..10111(reserved, 5 combinations) 11000..
..11110values specific to each SC, usage based on mutual agreement between the SME and the SC (7 combinations available for each SC) 11111 A GSM mobile station. The SC converts the SM from the received TP-DCS to any data coding scheme supported by that MS (e.g. the default). If bit 5 has value 1 in an SMS-DELIVER PDU, it indicates that the SME is a telematic device of a type which is indicated in bits 4..0.
If bit 5 has value 0 in an SMS-DELIVER PDU, the value in bits 4..0 indicates the SM-AL protocol being used between the SME and the MS.
Note that for the straightforward case of simple MS-to-SC short message transfer the Protocol Identifier is set to the value 0.
In the case where bit 7 = 0, bit 6 = 1, bits 5..0 are used as defined below
Bits 5..0 Description 000000 Short Message Type 0 000001 Replace Short Message Type 1 000010 Replace Short Message Type 2 000011 Replace Short Message Type 3 000100 Replace Short Message Type 4 000101 Replace Short Message Type 5 000110 Replace Short Message Type 6 000111 Replace Short Message Type 7 001000..011110 Reserved 011111 Return Call Message 100000..111100 Reserved 111101 ME Data download 111110 ME De-personalization Short MEssage 111111 SIM Data download A short message type 0 indicates that the ME must acknowledge receipt of the short message but may discard its contents.
The Replace Short Message feature is optional for the ME and the SIM but if implemented it shall be performed as descriped here.
For MT short messages, on receipt of a short message from from the SC, the MS shall check to see if the associated Protocol Identifier contains a Replace Short Message Type code.
If such a code is present, the the MS will check the originating address and replace any existing stored message having the same Protocol Identifier code and originating address with the new short message and other parameter values. If there is no message to be replaced, the MS shall store the message in the normal way. The MS may also check the SC address as well as the Originating Address. However, in a network which has multiple SCs, it is possible for a Replace Message type for a SM to be sent via different SCs and so it is recommended that the SC address should not be checked by the MS unless the application specifically requires such a check.
If a Replace Short Message Type code is not present then the MS will will store the message in the normal way.
In MO short messages the SC reacts similarly but only the address of the originating MS or any other source is checked.
A Return Call Message indicates to the MS to inform the user that a call (e.g. a telephone call) can be established to the address specified within the TP-OA. The RP-OA contains the address of the SC as usual. The message content (if present) gives displayable information (e.g. the number of waiting voice messages). The message is handled in the same way as all other messages of the Replace Short Message Types.
The ME De-personalization Short Message is an ME-specific message which instructs the ME to de-personalities the ME (see GSM 2.22). The TP-DCS shall be set to Uncompressed, Default Alphabet, and Message Class 1 (Me-specific), which corresponds to a bit coding og 00010001. The TP-UD field contains de-personalization information coded according to GSM 02.22. This information shall not be displayed by an ME which supports the scheme. The acknowledgement to this message is a SMS-DELIVER-REPORT for RP-ACK in ehich the TP-User-Data shall be coded according to GSM 02.22.
SIM Data download is a facility whereby the ME must pass the short message in its entirety including all SMS elements contained in the SMS deliver to the SIM using the mechanism descriped in GSM 11.11. The DCS shall be set to 8 bit message class 2 (either bit coding 11110110 or 00010110). The entire user data field is available for SIM Data download.
ME Data download is facility whereby the ME shall process the short message in its entirety including all SMS elements contained in the SMS deliver to the ME. The DCS shall be set to message class 1. The entire user data field is available for ME data download.
Coding Group Bits 7..4 Use of bits 3..0 00xx General Data Coding indication
Bits 5..0 indicate the following:
Bit 5 0 Text is uncompressed 1 Text is compressed
Bit 4 0 Bits 1..0 have no meaning 1 Bits 1..0 indicates message class
Bit 3 Bit 2 Alphabet being used 0 0 Default alphabet 0 1 8 bit data 1 0 UCS2 (16bit) 1 1 Reserved
Bit 1 Bit 0 Message class Description 0 0 Class 0 0 1 Class 1 ME specific 1 0 Class 2 SIM specific 1 1 Class 3 TE specific NOTE: The special case of bits 7..0 being 0000 0000 indicates the Default Alphabet as in Phase 2
0100..1011 Reserved coding groups 1100 Message Waiting Indication Group: Discard Message Bits 3..0 are coded exactly the same as Group 1101, however with bits 7..4 set to 1100 the mobile may discard the contents of the message, and only present the indication to the user.
1101 Message Waiting Indication Group: Store Message This Group allows an indication to be provided to the user about status of types of message waiting on systems connected to the GSM PLMN. The mobile may present this indication as an icon on the screen, or other MMI indication. The mobile may take note of the Origination Address for message in this group and group 1100. For each indication supported, the mobile may provide storage for the Origination Address which is to control the mobile indication.
Text included in the user data is coded in the Default Alphabet.
Ehere 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.
Bit 3 Description 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. The meaning of this indication is intended to be standardized in the future, so Operators should not make use of this indication until the standard for this indication is finalized.
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 alphabet.
1111 Data coding/message class Bit 3 is reserved, set to 0.
Bit 2 Message coding 0 Default alphabet 1 8-bit data
Bit 1 Bit 0 Message Class Description 0 0 Class 0 0 1 Class 1 ME specific 1 0 Class 2 SIM specific 1 1 Class 3 TE specific
Field Length Description RP 1b Reply Path, if 1, answer to SM is send via same SC UDHI 1b User Data Header Identifier, UD starts with UDH SRR 1b Status Report Request VPF 2b Validity Period Format RD 1b Reject Duplicates MTI 2b Message Type Indicator (01 = SUBMIT)
E.g.: 0x99 0x20 0x21 0x50 0x75 0x03 0x12 means 12. Feb 1999 05:57:30 GMT+3
Field Length Description Year 1 These are in "Swapped Nibble" mode Month 1 Day 1 Hour 1 Minute 1 Second 1 Timezone 1 Relation to GMT. One unit is 15min. If MSB=1, value is negative. Swapped Nibble presentation
BCD code where nibbles within octet is swapped. E.g.: 0x31 Represents value of 13
Bit 4 Bit 3 Format 1 0 Relative 1 1 Absolute 0 1 Enhanged
Validity period specifies the time when SM expires. If SM is't delivered before that moment, it is discarded by SC. Validity-Period can be in three different format; Relative, Absolute and Enhanged.Relative:
Time relative to current moment.
TP-VP value Validity period value 0 to 143 (TP-VP + 1) * 5 minutes (i.e. 5 minutes intervals up to 12 hours) 144 to 167 12 hours + ((TP-VP - 143) * 30 minutes) 168 to 196 (TP-VP - 166) * 1 day 197 to 255 (TP-VP - 192) * 1 week Absolute
TP-VP field is 7 octets long, containing TP-SCTS formatted time when SM expires.Enhanged
Too tired to write... RTFETSIM
Value Type of address 0x31 International without leading '+' ??? 0x91 International See ETSI's docs for more info.
UD is sent just like when sending, within 0x27 messages.
Field Length Description MEM 1 Memory area: 2=SIM, 3=ME Status 2 These two are the same as in received SM header. PID 1 Protocol Identifier DCS 1 Data Coding Scheme SCTS 7 Service Centre Time Stamp UDL 1 User Data Length SMSC PNUM SM Service Centre OA PNUM Originating Address TA 1 Type of OA SMS Stored [0x2a]
Field Length Description LOC 1 SMS memory location where stored to BZZZZ [0x2b]
Field Length Description EID 1 Cause of BZZZZ