Chapter 9
Standard: JT/T 808-2013

Detailed Explanation of Messages

Comprehensive wire-frame field breakdown of all 22 communication messages in JT/T 808-2013.

Detailed Explanation of Messages

9.0 Terminal Configuration Parameters Overview
#

According to the JT/T 808-2013 standard:

0x0001 ~ 0xEFFF: Standard parameters defined in national specification JT/T 808-2013.
0xF000 ~ 0xFFFF: Proprietary user-defined parameters for Jimi VL502 connected vehicle terminals.
Parameter IDData TypeDefault ValueDescription & Requirements
0xF000DWORD0Connected vehicle terminal feature switch bitmask
0xF001WORD10OBD data acquisition frequency while driving (seconds)
0xF002WORD300OBD data acquisition frequency while stationary/flameout (seconds)
0xF003BYTE1High-frequency acceleration sensor collection enable (0: Disable, 1: Enable)
0xF004WORD30Idle timeout alarm threshold (seconds)
0xF005WORD120Rapid acceleration threshold (mg)
0xF006WORD120Rapid deceleration / harsh braking threshold (mg)
0xF007WORD100Harsh sharp turn threshold (mg)
0xF008WORD500Collision / impact alarm threshold (mg)
0xF00DDWORD0x00000000Vehicle brand & engine protocol type ID (See Table 5)
0xF010STRING""FOTA firmware upgrade FTP server address
0xF011WORD21FOTA firmware upgrade FTP server port
0xF020DWORD0Extended telemetry mask flags
QUICK EXPLORER: Explore over 100 hardware configuration parameters (0xF000 ~ 0xFFFF and 0x0001 ~ 0x0074) with complete data types, value ranges, and default values at:

---

9.0.1 Terminal General Response — 0x0001
#

Message ID: 0x0001 | Direction: Uplink

Terminal acknowledgement response to platform commands.

Table: Data Format of Terminal General Response Message Body

Start ByteFieldData TypeDescription and Requirements
0Response Sequence NumberWORDFlow number of the corresponding platform message.
2Response Message IDWORDMessage ID of the corresponding platform command.
4ResultBYTE0: Succeeded/confirm; 1: Failed; 2: Message error; 3: Not support; 4: SE key exchange succeeded; 5: SE key exchange failed.

9.1 Platform General Response — 0x8001
#

Message ID: 0x8001 | Direction: Platform -> Terminal (Downlink)

General response sent by the platform to acknowledge terminal requests or report execution results.

Table: Data Format of Platform General Response Message Body

Start ByteFieldData TypeDescription and Requirements
0Response Flow NumberWORDCorresponding terminal message flow number.
2Response Message IDWORDCorresponding terminal message ID.
4ResultBYTE0: Success / Confirmation; 1: Failure; 2: Message error; 3: Not supported.

9.2 Terminal Heartbeat — 0x0002
#

Message ID: 0x0002 | Direction: Terminal -> Platform (Uplink)

Periodically sent by the terminal to keep the TCP/UDP connection alive. The message body is empty.

Table: Data Format of Terminal Heartbeat Message Body

*This message has an empty message body (0 bytes payload).*

9.3 Terminal Registration — 0x0100
#

Message ID: 0x0100 | Direction: Terminal -> Platform (Uplink)

Sent upon first boot or SIM insertion to register the hardware identity and vehicle metadata with the platform.

Table: Data Format of Terminal Registration Message Body

Start ByteFieldData TypeDescription and Requirements
0Province IDWORDGB/T 2260 administrative division province code.
2City IDWORDGB/T 2260 administrative division city/county code.
4Manufacturer IDSTRING[5]5-byte manufacturer code assigned to Jimi IoT.
9Terminal ModelSTRING[20]Device model, e.g. VL502 (padded with 0x00).
29Terminal IDSTRING[7]7-byte unique terminal serial number.
36License Plate ColorBYTEJT/T 415-2006: 1=Blue, 2=Yellow, 3=Black, 4=White, 5=Green, 9=Other, 0=Unlicensed.
37Vehicle License PlateSTRINGMotor vehicle registration plate string (or VIN if unlicensed).

9.4 Terminal Registration Response — 0x8100
#

Message ID: 0x8100 | Direction: Platform -> Terminal (Downlink)

Platform reply to 0x0100 registration request containing authorization token.

Table: Data Format of Terminal Registration Response Message Body

Start ByteFieldData TypeDescription and Requirements
0Response Flow NumberWORDFlow number of the corresponding 0x0100 registration request.
2ResultBYTE0: Success; 1: Vehicle already registered; 2: No such vehicle in database; 3: Terminal already registered; 4: No such terminal in database.
3Authentication CodeSTRINGAuthentication token string issued by platform; required for subsequent 0x0102 logins (only present if Result=0).

9.5 Terminal Logout — 0x0003
#

Message ID: 0x0003 | Direction: Terminal -> Platform (Uplink)

Notifies the platform that the terminal is being uninstalled or powering down. Message body is empty.

Table: Data Format of Terminal Logout Message Body

*This message has an empty message body (0 bytes payload).*

9.6 Terminal Login Authentication — 0x0102
#

Message ID: 0x0102 | Direction: Terminal -> Platform (Uplink)

Sent immediately after establishing TCP connection to authenticate identity using the token received in 0x8100.

Table: Data Format of Terminal Login Authentication Message Body

Start ByteFieldData TypeDescription and Requirements
0Authentication CodeSTRINGAuthentication string assigned during terminal registration.

9.7 Set Parameter for Specific Terminal — 0x8103
#

Message ID: 0x8103 | Direction: Platform -> Terminal (Downlink)

Downlink command configuring one or multiple terminal parameters (0x0001 - 0xFFFF).

Table: Data Format of Set Parameter for Specific Terminal Message Body

Start ByteFieldData TypeDescription and Requirements
0Parameter CountBYTENumber of parameter items included in the command (n).
1Parameter Items ListPARAM_LISTRepeated items: [Param ID (DWORD, 4B) + Param Length (BYTE, 1B) + Param Value (Variable)].

9.8 Query Parameter of Specific Terminal — 0x8106
#

Message ID: 0x8106 | Direction: Platform -> Terminal (Downlink)

Queries current values of designated parameter IDs.

Table: Data Format of Query Parameter of Specific Terminal Message Body

Start ByteFieldData TypeDescription and Requirements
0Parameter CountBYTETotal number of parameter IDs requested (n).
1Parameter ID ListDWORD[n]Array of 4-byte parameter IDs.

9.9 Response to Parameter Query — 0x0104
#

Message ID: 0x0104 | Direction: Terminal -> Platform (Uplink)

Terminal response containing requested parameter values.

Table: Data Format of Response to Parameter Query Message Body

Start ByteFieldData TypeDescription and Requirements
0Response Flow NumberWORDFlow number of corresponding 0x8106 query message.
2Parameter CountBYTENumber of returned parameters.
3Parameter Items ListPARAM_LIST[Param ID (DWORD) + Param Length (BYTE) + Param Value].

9.10 Terminal Control — 0x8105
#

Message ID: 0x8105 | Direction: Platform -> Terminal (Downlink)

Platform remote execution commands for device management (reboot, reset, wireless controls).

Table: Data Format of Terminal Control Message Body

Start ByteFieldData TypeDescription and Requirements
0Command WordBYTE1: Wireless upgrade; 2: Connect specified server; 3: Terminal reboot; 4: Factory reset; 5: Turn off data communication; 6: Turn off all wireless.
1Command ParameterSTRINGCommand arguments (e.g. APN, IP, Port, URL for upgrade).

9.11 Notification of Terminal Upgrade Result — 0x0108
#

Message ID: 0x0108 | Direction: Terminal -> Platform (Uplink)

Reports firmware OTA upgrade completion status.

Table: Data Format of Notification of Terminal Upgrade Result Message Body

Start ByteFieldData TypeDescription and Requirements
0Upgrade TypeBYTE0: Terminal firmware; 12: Card reader; 52: Beidou/GNSS module.
1Upgrade ResultBYTE0: Succeeded; 1: Failed; 2: Canceled.

9.12 Location Information Reporting — 0x0200
#

Message ID: 0x0200 | Direction: Terminal -> Platform (Uplink)

Core periodic tracking packet reporting GNSS position, speed, direction, status flags, and active alarms.

Table: Data Format of Location Information Reporting Message Body

Start ByteFieldData TypeDescription and Requirements
0Alarm FlagDWORD32-bit alarm bitmap: SOS, speeding, fatigue, geo-fence, low battery, vibration, etc.
4Status FlagDWORD32-bit status bitmap: ACC state (bit 0), GPS fix (bit 1), lat/lon signs, encryption, oil/electric cut.
8LatitudeDWORDLatitude in degrees * 10^6 (accurate to 10^-6 deg).
12LongitudeDWORDLongitude in degrees * 10^6 (accurate to 10^-6 deg).
16AltitudeWORDElevation above sea level in meters.
18SpeedWORDVehicle speed in 1/10 km/h.
20DirectionWORDHeading azimuth 0 - 359 degrees (0 = True North).
22TimeBCD[6]GNSS UTC/local timestamp in YY-MM-DD-HH-MM-SS BCD format.
28Additional Info ItemsEXT_ITEMSOptional TLV items: Mileage (0x01, DWORD), Fuel level (0x02, WORD), Speed sensor (0x03, WORD), etc.

9.12.1 Definition of Location Alarm Flag Bit (Table 19)
#

BitAlarm DefinitionBitAlarm Definition
0SOS emergency alarm (terminal trigger)16VSS vehicle speed sensor abnormal
1Overspeed alarm17Abnormal vehicle oil level
2Fatigue driving alarm18Cumulative driving overspeed
3Danger early warning19Overtime parking alarm
4GNSS module failure20In/Out area geofence breach
5GNSS antenna disconnected21In/Out route breach
6GNSS antenna short circuit22Insufficient / excessive travel time on route
7Terminal main power undervoltage23Route deviation alarm
8Terminal main power disconnected28Illegal vehicle ignition alarm
9Terminal display / LCD failure29Illegal vehicle movement / towing
10TTS speech module failure30Vehicle collision warning
11Camera failure31Vehicle rollover warning

9.12.2 Definition of Status Bit for Location Information (Table 20)
#

BitStatus DefinitionBitStatus Definition
0ACC state (0: ACC OFF, 1: ACC ON)10Vehicle fuel line state (0: Normal, 1: Disconnected)
1Positioning state (0: Unfixed, 1: Fixed)11Vehicle electrical circuit (0: Normal, 1: Cut off)
2Latitude hemisphere (0: North, 1: South)12Vehicle door lock state (0: Unlocked, 1: Locked)
3Longitude hemisphere (0: East, 1: West)18GPS positioning constellation enabled
4Operating state (0: In service, 1: Suspended)19Beidou (BDS) positioning enabled
5Position encryption (0: Plain, 1: Encrypted)20GLONASS positioning enabled

Message ID: 0x8900 | Direction: Platform -> Terminal (Downlink)

Transfers proprietary downstream commands including vehicle remote control (0xF1) and CAN learning parameters.

Table: Data Format of Data Downlink Transparent Transmission Message Body

Start ByteFieldData TypeDescription and Requirements
0Transparent Message TypeBYTE0xF1: Vehicle remote control command.
1Transparent Message ContentBYTESControl payload (door lock/unlock, trunk, remote cut-off).

Message ID: 0x0900 | Direction: Terminal -> Platform (Uplink)

Container for high-level telematics data: OBD-II live telemetry, trouble codes, driving behaviors, trip summaries, and CAN data.

Table: Data Format of Data Uplink Transparent Transmission Message Body

Start ByteFieldData TypeDescription and Requirements
0Transparent Message TypeBYTE0xF0: Telematics uplink data stream.
1Message SubcategoryBYTE0x01: OBD stream; 0x02: Trouble codes; 0x03: Alarms & driving behavior; 0x04: Travel summary; 0x05: Logs; 0x06: CAN learning; 0x0B: VIN; 0x0C: Inspection; 0x0D: Self-test; 0x0F: Function list; 0x15: Emergency event packet.

9.14.1 Transparent Sub-Command Types
#

Sub-Command TypeNamePurpose
0xF0Standard Vehicle Telemetry UploadCarries OBD data streams (Table 25), driving behaviors (Table 28), DTCs, VIN
0xF1Diagnostic Command ResponseReturns result of downlink transparent AT/CAN diagnostic command

9.15 Set Circular Geofence — 0x8600
#

OBD DATA STREAMS & DIAGNOSTICS:
- Report diagnostic trouble codes (SAE J1939 & OBD-II DTC) in standardized format at Appendix 10.3.

Message ID: 0x8600 | Direction: Platform -> Terminal (Downlink)

Configures a circular boundary with latitude, longitude, radius, and trigger conditions.

Table: Data Format of Set Circular Geofence Message Body

Start ByteFieldData TypeDescription and Requirements
0Setting AttributeBYTE0: Update area; 1: Append area; 2: Modify area.
1Total AreasBYTENumber of circular regions.
2Area IDDWORDUnique identifier for this geofence zone.
6Area AttributeWORDBit flags: enter alarm, exit alarm, speed limit enabled, time range enabled.
8Center LatitudeDWORDCenter latitude in degrees * 10^6.
12Center LongitudeDWORDCenter longitude in degrees * 10^6.
16RadiusDWORDRadius of circular zone in meters.

9.16 Delete Circular Geofence — 0x8601
#

Message ID: 0x8601 | Direction: Platform -> Terminal (Downlink)

Removes designated circular zones from terminal memory.

Table: Data Format of Delete Circular Geofence Message Body

Start ByteFieldData TypeDescription and Requirements
0Area CountBYTENumber of areas to delete (0 = delete all).
1Area ID ListDWORD[n]Array of 4-byte area IDs.

9.17 Set Rectangular Geofence — 0x8602
#

Message ID: 0x8602 | Direction: Platform -> Terminal (Downlink)

Configures rectangular geofence bounding boxes (top-left & bottom-right coordinates).

Table: Data Format of Set Rectangular Geofence Message Body

Start ByteFieldData TypeDescription and Requirements
0Setting AttributeBYTE0: Update area; 1: Append area; 2: Modify area.
1Total AreasBYTENumber of rectangular regions.
2Area IDDWORDUnique zone ID.
6Area AttributeWORDTrigger attributes: enter/exit alarm, speed limit.
8Upper-Left LatitudeDWORDTop-left corner latitude * 10^6.
12Upper-Left LongitudeDWORDTop-left corner longitude * 10^6.
16Lower-Right LatitudeDWORDBottom-right corner latitude * 10^6.
20Lower-Right LongitudeDWORDBottom-right corner longitude * 10^6.

9.18 Delete Rectangular Geofence — 0x8603
#

Message ID: 0x8603 | Direction: Platform -> Terminal (Downlink)

Deletes designated rectangular zones from device memory.

Table: Data Format of Delete Rectangular Geofence Message Body

Start ByteFieldData TypeDescription and Requirements
0Area CountBYTENumber of rectangular areas to delete (0 = delete all).
1Area ID ListDWORD[n]Array of 4-byte area IDs.

9.19 CAN Bus Data Upload — 0x0705
#

Message ID: 0x0705 | Direction: Terminal -> Platform (Uplink)

Raw CAN frame stream upload with high-precision timestamps for vehicle bus diagnostic logging.

Table: Data Format of CAN Bus Data Upload Message Body

Start ByteFieldData TypeDescription and Requirements
0CAN Item CountWORDNumber of CAN frame items included.
2Receive TimeBCD[5]First frame timestamp (hh-mm-ss-ms*10).
7CAN ItemsCAN_FRAME[n]Frame items: CAN Channel (1B) + Frame ID (DWORD, 4B) + Data (BYTE[8]).

9.20 Sending Text Message — 0x8300
#

Message ID: 0x8300 | Direction: Platform -> Terminal (Downlink)

Platform sends text notification or synthesized voice message to vehicle screen/audio terminal.

Table: Data Format of Sending Text Message Message Body

Start ByteFieldData TypeDescription and Requirements
0Text FlagBYTEBit flags: Emergency (bit 0), LCD display (bit 2), TTS voice (bit 3), Advert display (bit 4).
1Text InformationSTRINGGBK/Unicode encoded text message content.

9.21 Response to Text Message Sending — 0x0303
#

Message ID: 0x0303 | Direction: Terminal -> Platform (Uplink)

Terminal acknowledgment for text message display.

Table: Data Format of Response to Text Message Sending Message Body

Start ByteFieldData TypeDescription and Requirements
0Response Flow NumberWORDCorresponding 0x8300 message flow number.