Chapter 5
Standard: JT/T 808-2013

Protocol Details

TCP/UDP transport, Table 1 primitive data types, Table 2 12/16-byte message header, and XOR BCC checksum.

Protocol Details

5.1 Communication Method
#

The communication protocol adopts TCP or UDP, with the telematics platform serving as the server side and the vehicle terminal operating as the client side.

5.2 Data Type
#

See Table 1 for primitive data types used across all protocol packets:

Table 1: Data Type
Data TypeDescription and RequirementsFormat / Value Range
BYTEUnsigned single-byte integer (single byte, 8 bits)Decimal: 0 ~ 255; Hexadecimal: 0x00 ~ 0xFF
WORDUnsigned double-byte integer (double byte, 16 bits, Big-Endian)Decimal: 0 ~ 65535; Hexadecimal: 0x0000 ~ 0xFFFF
DWORDUnsigned four-byte integer (4-byte double word, 32 bits, Big-Endian)Decimal: 0 ~ 4294967295; Hexadecimal: 0x00000000 ~ 0xFFFFFFFF
BYTE[n]n-byte arraySequential raw byte stream
BCD[n]8421 BCD code, n bytes2 decimal digits per byte (e.g. Phone number, IMEI, Time)
STRINGGBK encoded stringVariable length string; leave blank if there is no data

5.3 Transmission Rules
#

NOTE: When a data value contains negative numbers or fractional decimals, adjust it according to the parameterized algorithm. When data is packed, the physical value should be added with the offset or multiplied by the scaling factor; when unpacked, the raw integer value should be subtracted by the offset or divided by the scaling factor.

The protocol strictly uses Big-Endian network byte order for multi-byte words and double words:

Transmission rules are as follow:

BYTE: Transmitted directly as an 8-bit byte;
WORD: Transmit the upper 8 bits first (MSB), then the lower 8 bits (LSB);
DWORD: Transmit the upper 24 bits first, then the upper 16 bits, the upper 8 bits, and finally the lower 8 bits.

5.4 Message Composition
#

5.4.1 Message Structure
#

Each packet consists of a delimiter identifier, message header, message payload body, and check character:

Fig. 2: Message Structure
text
+---------------+-----------------------+--------------------+----------------+---------------+
|  Identifier   |    Message Header     |    Message Body    | Checksum (BCC) |  Identifier   |
+---------------+-----------------------+--------------------+----------------+---------------+
|  0x7E (1 B)   |    12 or 16 Bytes     |   0 ~ 1023 Bytes   |   XOR (1 B)    |  0x7E (1 B)   |
+---------------+-----------------------+--------------------+----------------+---------------+

5.4.2 Identifier & Escaping Rules
#

This document designates 0x7E as the frame delimiter. If 0x7E or 0x7D appears in the message header, body, or checksum, it must be escaped according to the following rules:

Original Byte in StreamEscaped Byte SequenceMeaning
0x7E0x7D 0x02Delimiter byte escaped
0x7D0x7D 0x01Escape byte escaped

The escape process is as follows:

Sending message: Construct packet โ†’ calculate check character (BCC) โ†’ perform escaping โ†’ wrap with 0x7E head and tail.
Receiving message: Strip 0x7E framing โ†’ perform escape reduction (unescaping) โ†’ verify check character โ†’ parse header and body.

5.4.3 Message Header
#

Example: To send payload data 0x30 0x7E 0x08 0x7D 0x55, the encapsulated wire packet becomes: 0x7E 0x30 0x7D 0x02 0x08 0x7D 0x01 0x55 0x7E.

The content of the standard 12~16 byte message header is shown in Table 2:

Table 2: Message Header
Start ByteFieldData TypeDescription and Requirements
0Message IDWORDUnique packet identifier (e.g. 0x0100, 0x0200, 0x8001)
2Message Body PropertiesWORDBit-mapped attributes: body length, encryption type, packet segmentation (See Fig. 3)
4Terminal SN (Phone/IMEI)BCD[6]6-byte BCD derived from the first 14 digits of the terminal IMEI. E.g. IMEI 123456789012347 โ†’ 0x0B3A73CE2FF2.
10Message Sequence NumberWORDCyclic counter (0~65535) incremented per sent message. Originator increments loop; responder keeps response ID consistent.
12Message Packet Encapsulation ItemStructure*(Optional)* Total sub-packets + packet index. Only present when bit 13 in Message Body Properties is 1.
Fig. 3: Structure Chart of Message Body Attributes Format
text
 Bit:   15   14   13   12   11   10    9   8   7   6   5   4   3   2   1   0
      +----+----+----+----+----+----+----+---+---+---+---+---+---+---+---+---+
      | R  | R  | P  | Data Encrypt |           Message Body Length          |
      +----+----+----+----+----+----+----+---+---+---+---+---+---+---+---+---+

Field Specifications:

Bit 15 ~ 14 (Reserve): Reserved bits, set to 0.
Bit 13 (Sub-packaging / Segment):
0: Single complete packet (no encapsulation item in header).
1: Long message segmented into sub-packets (header includes Table 3 encapsulation item).
NOTE: Considering server and device packet processing, Jimi VL502 strongly recommends bit 13 = 0 (single packet). For multi-packet transfers, refer to specific sub-command specifications.
Bit 12 ~ 10 (Data Encryption):
000: No encryption.
001: Message body encrypted with RSA algorithm.
111: Super encryption (refer to Appendix 10.4).
Others: Reserved.
Bit 9 ~ 0 (Message Body Length):
Length of the message payload in bytes (maximum 1023 bytes).
Table 3: Content of Message Packet Encapsulation Item
Start ByteFieldData TypeDescription and Requirements
0Total Number of PacketsWORDThe total number of packets after segmentation
2Packet NumberWORDCurrent packet sequence number (starts from 1)

5.4.4 Check Character (Checksum)
#

The check character is obtained by applying the bitwise XOR operation from the first byte of the message header to the very last byte prior to the check character:

text
Checksum (BCC) = Byte[0] ^ Byte[1] ^ Byte[2] ^ ... ^ Byte[N-1]

The check character occupies 1 byte and is appended immediately before the ending 0x7E delimiter.