Ajay K Shrestha
Newbie level 1
fbus 1e-0c-00-7f-00-02-40
I would highly recommend downloading the GSM 03.40 - Technical realization of the Short Message Service (SMS) Point-to-Point (PP). This specification describes the following SMS fields in detail. Refer to this specification for further information.
Sample frame sent to my Nokia 3310 (showed as a Hex dump) 98 Bytes
Byte: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Data: 1E 00 0C 02 00 59 00 01 00 01 02 00 07 91 16 14 91 09 10 F0 00 00 00 00 15 00 00 00 33 0A 81 40 30 87 00 47
SMS message centre -- Phone number -
Byte: 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71
Data: 00 00 00 00 00 A7 00 00 00 00 00 00 C8 34 28 C8 66 BB 40 54 74 7A 0E 6A 97 E7 F3 F0 B9 0C BA 87 E7 A0 79 D9
Start of Message - Hi All. This message was sent through F-Bus. Cool!!
Byte: 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97
Data: 4D 07 D1 D1 F2 77 FD 8C 06 19 5B C2 FA DC 05 1A BE DF EC 50 08 01 43 00 7A 52
F-Bus Frame Header
Byte 0: F-Bus Frame ID. We are on Cable (0x1E) See Part 1.
Byte 1: Destination address.
Byte 2: Source address.
Byte 3: Message Type or 'command'. 0x02 (SMS Handling).
Byte 4 & 5: Message length. In our case it is 0x0059 bytes long or 89 bytes in decimal.
(SMS) Short Message Service Frame Header
Byte 6 to 8: Start of the SMS Frame Header. 0x00, 0x01, 0x00
Byte 9 to 11: 0x01, 0x02, 0x00 = Send SMS Message
(SMSC) Short Message Service Centre (12 Bytes)
Byte 12: SMS Centre number length. 0x07 is 7 bytes long. This includes SMSC Number Type and SMS Centre Phone Number
Byte 13: SMSC number type e.g. 0x81-unknown 0x91-international 0xa1-national
1XXX IIII : Where I is the Numbering-plan-identification (Refer to GSM 03.40 - 9.1.2.5 Address fields)
1TTT XXXX : Where T is the Type-of-number (Refer to GSM 03.40 - 9.1.2.5 Address fields)
Byte 14 to 23: (Octet format) SMS Centre Phone Number In this case +61 411990010
(TPDU) Transfer Protocol Data Unit
Byte 24: Message Type
XXXX XXX1 = SMS Submit - The short message is transmitted from the Mobile Station (MS) to the Service Centre (SC).
XXXX XXX0 = SMS Deliver - The short message is transmitted from the SC to the MS.
(Refer to GSM 03.40 - 9.2.3 Definition of the TPDU parameters) In our case it is 0x15 = 0001 0101 in binary. The message is SMS Submit, Reject Duplicates, and Validity Indicator present.
Byte 25: Message Reference if SMS Deliver & Validity Indicator used (Not used in this case). Refer GSM 03.40 - 9.2.3.6 TP-Message-Reference (TP-MR)
Byte 26: Protocol ID. Refer to GSM 3.40 - 9.2.3.9 TP-Protocol-Identifier (TP-PID)
Byte 27: Data Coding Scheme. Refer to GSM 03.38 & GSM 3.40 - 9.2.3.10 TP-Data-Coding-Scheme (TP-DCS)
Byte 28: Message Size is 0x33 in hex or 51 bytes long in decimal. This is the size of the unpacked message.
Refer to GSM 03.40 - 9.2.3.16 TP-User-Data-Length (TP-UDL)
Destination's Phone Number (12 Bytes)
Byte 29: Destination's number length. Is this correct?. Byte 30: Number type e.g. 0x81-unknown 0x91-international 0xa1-national
Byte 31 to 40: (Octet format) Destination's Phone Number
Validity Period (VP)
Byte 41: Validity-Period Code. Time period during which the originator considers the short message to be valid.
Byte 42 to 47: Service Centre Time Stamp ?? For SMS-Deliver
The SMS Message (SMS-SUBMIT)
Byte 48 to 92: This is the SMS message packed into 7 bit characters. SMS Point-to-Point Character Packing
Byte 93: Always 0x00
The F-Bus usual ending
Byte 94: Packet Sequence Number
Byte 95: Padding Byte - String is old and requires to be even!
Byte 96 & 97: Odd & even checksum bytes.
If the phone receives a valid frame it should reply with something like this below, to say it got the message.
Reply frame sent from my Nokia 3310 (showed as a Hex dump)
Byte: 00 01 02 03 04 05 06 07 08 09
Data: 1E 0C 00 7F 00 02 02 03 1C 72
This is just like the above Acknowledge command frame. The destination and source addresses are swapped, as this is a frame from the phone to the PC. This message is two bytes long with the first byte representing the message type received (0x02) and the next byte, the sequence number (0x03). The last two bytes are the checksum and should be checked to make sure the data is correct.
After a short time the phone will reply with a 'Message sent' frame shown below.
Byte: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17
Data: 1E 0C 00 02 00 09 01 08 00 02 64 12 00 01 44 00 3F 1E
Byte 03: Message Type = 0x02 - SMS Handing
Byte 04 & 05: Message Length = 0x0009 - 9 Bytes long
Byte 09: 0x02 = Message Sent
Byte 10 to 14: Unsure of what this is?
The PC must then acknowledge the frame. No explanation required here!
Byte: 00 01 02 03 04 05 06 07 08 09
Data: 1E 00 0C 7F 00 02 02 04 10 79
I would highly recommend downloading the GSM 03.40 - Technical realization of the Short Message Service (SMS) Point-to-Point (PP). This specification describes the following SMS fields in detail. Refer to this specification for further information.
Sample frame sent to my Nokia 3310 (showed as a Hex dump) 98 Bytes
Byte: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Data: 1E 00 0C 02 00 59 00 01 00 01 02 00 07 91 16 14 91 09 10 F0 00 00 00 00 15 00 00 00 33 0A 81 40 30 87 00 47
SMS message centre -- Phone number -
Byte: 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71
Data: 00 00 00 00 00 A7 00 00 00 00 00 00 C8 34 28 C8 66 BB 40 54 74 7A 0E 6A 97 E7 F3 F0 B9 0C BA 87 E7 A0 79 D9
Start of Message - Hi All. This message was sent through F-Bus. Cool!!
Byte: 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97
Data: 4D 07 D1 D1 F2 77 FD 8C 06 19 5B C2 FA DC 05 1A BE DF EC 50 08 01 43 00 7A 52
F-Bus Frame Header
Byte 0: F-Bus Frame ID. We are on Cable (0x1E) See Part 1.
Byte 1: Destination address.
Byte 2: Source address.
Byte 3: Message Type or 'command'. 0x02 (SMS Handling).
Byte 4 & 5: Message length. In our case it is 0x0059 bytes long or 89 bytes in decimal.
(SMS) Short Message Service Frame Header
Byte 6 to 8: Start of the SMS Frame Header. 0x00, 0x01, 0x00
Byte 9 to 11: 0x01, 0x02, 0x00 = Send SMS Message
(SMSC) Short Message Service Centre (12 Bytes)
Byte 12: SMS Centre number length. 0x07 is 7 bytes long. This includes SMSC Number Type and SMS Centre Phone Number
Byte 13: SMSC number type e.g. 0x81-unknown 0x91-international 0xa1-national
1XXX IIII : Where I is the Numbering-plan-identification (Refer to GSM 03.40 - 9.1.2.5 Address fields)
1TTT XXXX : Where T is the Type-of-number (Refer to GSM 03.40 - 9.1.2.5 Address fields)
Byte 14 to 23: (Octet format) SMS Centre Phone Number In this case +61 411990010
(TPDU) Transfer Protocol Data Unit
Byte 24: Message Type
XXXX XXX1 = SMS Submit - The short message is transmitted from the Mobile Station (MS) to the Service Centre (SC).
XXXX XXX0 = SMS Deliver - The short message is transmitted from the SC to the MS.
(Refer to GSM 03.40 - 9.2.3 Definition of the TPDU parameters) In our case it is 0x15 = 0001 0101 in binary. The message is SMS Submit, Reject Duplicates, and Validity Indicator present.
Byte 25: Message Reference if SMS Deliver & Validity Indicator used (Not used in this case). Refer GSM 03.40 - 9.2.3.6 TP-Message-Reference (TP-MR)
Byte 26: Protocol ID. Refer to GSM 3.40 - 9.2.3.9 TP-Protocol-Identifier (TP-PID)
Byte 27: Data Coding Scheme. Refer to GSM 03.38 & GSM 3.40 - 9.2.3.10 TP-Data-Coding-Scheme (TP-DCS)
Byte 28: Message Size is 0x33 in hex or 51 bytes long in decimal. This is the size of the unpacked message.
Refer to GSM 03.40 - 9.2.3.16 TP-User-Data-Length (TP-UDL)
Destination's Phone Number (12 Bytes)
Byte 29: Destination's number length. Is this correct?. Byte 30: Number type e.g. 0x81-unknown 0x91-international 0xa1-national
Byte 31 to 40: (Octet format) Destination's Phone Number
Validity Period (VP)
Byte 41: Validity-Period Code. Time period during which the originator considers the short message to be valid.
Byte 42 to 47: Service Centre Time Stamp ?? For SMS-Deliver
The SMS Message (SMS-SUBMIT)
Byte 48 to 92: This is the SMS message packed into 7 bit characters. SMS Point-to-Point Character Packing
Byte 93: Always 0x00
The F-Bus usual ending
Byte 94: Packet Sequence Number
Byte 95: Padding Byte - String is old and requires to be even!
Byte 96 & 97: Odd & even checksum bytes.
If the phone receives a valid frame it should reply with something like this below, to say it got the message.
Reply frame sent from my Nokia 3310 (showed as a Hex dump)
Byte: 00 01 02 03 04 05 06 07 08 09
Data: 1E 0C 00 7F 00 02 02 03 1C 72
This is just like the above Acknowledge command frame. The destination and source addresses are swapped, as this is a frame from the phone to the PC. This message is two bytes long with the first byte representing the message type received (0x02) and the next byte, the sequence number (0x03). The last two bytes are the checksum and should be checked to make sure the data is correct.
After a short time the phone will reply with a 'Message sent' frame shown below.
Byte: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17
Data: 1E 0C 00 02 00 09 01 08 00 02 64 12 00 01 44 00 3F 1E
Byte 03: Message Type = 0x02 - SMS Handing
Byte 04 & 05: Message Length = 0x0009 - 9 Bytes long
Byte 09: 0x02 = Message Sent
Byte 10 to 14: Unsure of what this is?
The PC must then acknowledge the frame. No explanation required here!
Byte: 00 01 02 03 04 05 06 07 08 09
Data: 1E 00 0C 7F 00 02 02 04 10 79