General Specifications for The Communication Protocol

and Data Format

JT808 Protocol
1. Terms & Definitions, Abbreviations

1.1 Terms & Definitions

The following terms and definitions apply to this document.

1.1.1 Abnormal data communication link

The wireless communication link is disconnected, or temporarily suspended

(eg, during a call).

1.1.2 Register

The terminal sends a message to the platform that it is installed on a certain

vehicle.

1.1.3 Unregister

The terminal sends a message to the platform for removal from the mounted

vehicle.

1.1.4 Authentication

When the terminal connects to the platform, it sends a message to the

platform so that the platform can verify its identity.

1.1.5 Location reporting strategy

Timed, distanced reporting or a combination of both.

1.1.6 Location reporting program

Rules for determining the interval for periodic reporting based on relevant

conditions.

1.1.7 Additional points report while turning

The terminal sends a position information report message when judging that

the vehicle turns. The sampling frequency is not less than 1Hz, and the change

rate of the vehicle azimuth angle is not less than 15°/s, and it lasts for at least

3s.

1.1.8 Answering strategy

Rules for the terminal to answer incoming calls automatically or manually.

1.1.9 SMS text alarm

When the terminal alarms, text information is sent by SMS.

1.1.10 Event item

The event item is preset by the platform to the terminal, and consists of the

event code and the event name. When the driver encounters the

corresponding event, he operates the terminal and triggers the event report

to be sent to the platform.

1.2 Abbreviations

The following abbreviations apply to this document.

APN —— Access Point Name

GZIP —— A file compression program for GNU free software ( GUNzip )

LCD —— Liquid Crystal Display

RSA —— An asymmetric cryptographic algorithm ( developed by Ron Rivest,

Adi Shamirh, Len Adleman, named after the three )

SMS —— Short Message Service

TCP —— Transmission Control Protocol

TTS —— Text to Speech

UDP —— User Datagram Protocol

VSS —— Vehicle Speed Sensor

2. Protocol Basics

2.1 Way of Communication

The communication method adopted by the protocol should comply with the

relevant regulations in JT/T 794. The communication protocol adopts TCP or

UDP, the platform is the server side, and the terminal is the client side. When

the data communication link is abnormal, the terminal can communicate by

SMS message.

2.2 Type of Data

The data types used in protocol messages are shown in Table 1:

Table 1 Type of Data

Type of Data Description & Requirements

BYTE Unsigned Single-Byte Integer ( Byte, 8-bit )

WORD Unsigned Double Byte Integer ( Word, 16-bit )

DWORD Unsigned Four-Byte Integer ( Double Word, 32 bits )

BYTE[n] n bytes
 BCD[n] 8421 code, n bytes

STRING GBK encoding, empty if there is no data

2.3 Rules of Transmission

The protocol uses big-endian network byte order to pass words and double

words.

The agreement is as follows:

—— Byte (BYTE) transmission convention: according to the way of byte

stream transmission;

—— The transmission convention of word (WORD): first transmit the upper

eight bits, and then transmit the lower eight bits;

—— The transmission convention of double word (DWORD): first transmit

the high 24 bits, then transmit the high 16 bits, then transmit the high eight

bits, and finally transmit the low eight bits.

2.4 Composition of The Message

2.4.1 Message Structure

Each message consists of an identification bit, a message header, a message

body and a check code. The message structure diagram is shown in Figure 1:
Message
Identification bit Message Boday Check Code Identification bit
Header
Figure 1 Message Structure
2.4.2 Identification bit

0x7e is used to indicate that if 0x7e appears in the check code, message

header and message body, it needs to be escaped. The escape rules are

defined as follows:

0x7e <————> 0x7d followed by a 0x02

0x7d <————> 0x7d followed by a 0x01

The escape process is as follows:

When sending a message: message encapsulation ——> calculate and fill

check code ——> escape;

When receiving a message: escape and restore ——> verify the check code

——> parse the message.

Example:

Send a packet with the content of 0x30 0x7e 0x08 0x7d 0x55, and encapsulate

it as follows: 0x7e 0x30 7d 0x02 0x08 0x7d 0x01 0x55 0x7e.

2.4.3 Message Header

The content of the message header is shown in Table 2:

Table 2 Content of Message Header

Description &
Start Byte Field Type of Data
Requirements
0 Message ID WORD
The structure
diagram of the
Message Body
2 WORD message body
Properties
attribute format is
shown in Figure 2
 Terminal Phone
4 BCD[6]
Number
Circular
Message Serial accumulation
10 WORD
Number starting from 0 in
the sending order
If the relevant flag
bit in the message
body attribute
determines the
Message Packet
12 packet processing
Encapsulation Item
of the message,
then the item has
content, otherwise
there is no item

The structure of the message body attribute format is shown in Figure 2:

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Data
Reserve Subpackage Encryption Message Body Length
Method
Figure 2: Message Body Attribute Format Structure Diagram

Data encryption method:

—— bit10 ~ bit12 are the data encryption identification bits;

—— When these three bits are all 0, it means that the message body is not

encrypted;

—— When the 10th bit is 1, it means that the message body is encrypted by

the RSA algorithm;

—— The rest are reserved.

Subpackage:
When the 13th bit in the message body attribute is 1, it means that the

message body is a long message, and it is processed by sub-package sending.

The specific sub-package information is determined by the message package

encapsulation item; If bit 13 is 0, there is no packet encapsulation field in the

message header.

Contents of the message package encapsulation items are shown in Table 3:

Table 3: Contents of the message package encapsulation items

Start Byte Field Type of Data Description

The total number
total number of of packets after the
0 WORD
message packets message is
sub-packaged
package serial
2 WORD Starts from 1
number

2.4.4 Check Code

The check code refers to starting from the message header, XORing with the

next byte until the previous byte of the check code, occupying one byte.

3. Communication Connection

3.1 Connection Establishment

The daily data connection between the terminal and the platform can use TCP

or UDP. After the terminal is reset, it should establish a connection with the

platform as soon as possible, and immediately send a terminal authentication

message to the platform for authentication after the connection is

established.

3.2 Connection Maintenance

After the connection is established and the terminal authentication is

successful, in the absence of normal data packet transmission, the terminal

should periodically send a terminal heartbeat message to the platform. After

receiving it, the platform sends a platform general response message to the

terminal. The sending period is specified by the terminal parameters.

3.3 Disconnection

Both the platform and the terminal can actively disconnect according to the

TCP protocol, and both parties should actively determine whether the TCP

connection is disconnected.

The platform determines the method of TCP connection disconnection:

—— According to the TCP protocol, it is judged that the terminal is actively

disconnected;

—— A terminal with the same identity establishes a new connection,

indicating that the original connection has been disconnected;

—— The message sent by the terminal, such as the heartbeat of the terminal,

is not received within a certain period of time.

The terminal determines the method of TCP connection disconnection:

—— According to the TCP protocol, it is judged that the platform is actively

disconnected;

—— The data communication link is disconnected;

—— The data communication link is normal, and no response is received after

the number of retransmissions is reached.

4. Message Processing

4.1 TCP & UDP Message Processing

4.1.1 Message from the main platform

All messages sent by the platform require the terminal to respond. The

responses are divided into general responses and special responses, which are

determined by each specific functional protocol. After the sender waits for the

response to time out, it should resend the message. The response timeout

time and the number of retransmissions are specified by the platform

parameters. The calculation formula of the response timeout time after each

retransmission is shown in formula (1):

TN+1=TN × ( N+1 ) .......................................Formula (1)

TN+1 —— The response timeout after each retransmission;

TN —— The previous response timeout;

N —— Number of retransmissions.
4.1.2 Message Sent by The Terminal

4.1.2.1 The data communication link is normal

When the data communication link is normal, all messages sent by the

terminal require the platform to respond. The responses are divided into

general responses and special responses, which are determined by each

specific functional protocol. After the terminal waits for the response timeout,

it should retransmit the message. The response timeout time and the number

of retransmissions are specified by the terminal parameters, and the response

timeout time after each retransmission is calculated according to formula (1).

For the key alarm message sent by the terminal, if no response is received

after the number of retransmissions, it should be saved. The saved critical

alarm messages are sent in the future before other messages are sent.

4.1.2.2 Abnormal data communication link

When the data communication link is abnormal, the terminal should save the

location information report message to be sent. The saved message is sent as

soon as the data communication link returns to normal.

4.2 SMS Message Processing

When the terminal communication mode is switched to the SMS message

mode of the GSM network, the PDU eight-bit encoding mode is used. For
messages longer than 140 bytes, they should be subcontracted in accordance

with the SMS service specification of the GSM network GSM 03.40.

The response, retransmission and saving mechanisms of SMS messages are

the same as in 6.1, but the response timeout time and the number of

retransmissions should be handled according to the relevant setting values of

parameters ID0x0006 and 0x0007 in Table 10.

5. Protocol Classification

5.1 Overview

The protocols are described below by functional classification. Unless

otherwise specified, the TCP communication mode is adopted by default. See

Appendix A for the communication protocol between the vehicle terminal and

the external device. See Appendix B for the message comparison table of

message name and message ID in the protocol.

5.2 Terminal Management Protocol

5.2.1 Terminal Registration / De-registration

When the terminal is not registered, it should be registered first. After the

registration is successful, the terminal will obtain the authentication code and

save it. The authentication code is used when the terminal logs in. Before the

vehicle needs to remove or replace the terminal, the terminal should perform
a logout operation to cancel the corresponding relationship between the

terminal and the vehicle.

If the terminal chooses to send the terminal registration and terminal

deregistration messages by SMS, the platform shall reply to the terminal

registration by sending the terminal registration response by SMS, and reply

to the terminal cancellation by sending the platform general response by SMS.

5.2.2 Terminal Authentication

After the terminal is registered, it should be authenticated immediately after

establishing a connection with the platform. The terminal shall not send other

messages until the authentication is successful.

The terminal performs authentication by sending a terminal authentication

message, and the platform replies with a platform general response message.

5.2.3 Set / Query Terminal Parameters

The platform sets terminal parameters by sending a set terminal parameter

message, and the terminal replies with a terminal general response message.

The platform queries terminal parameters by sending a query terminal

parameter message, and the terminal replies with a query terminal parameter

response message. Terminals under different network standards should

support some unique parameters of their respective networks.

5.2.4 Terminal Control

The platform controls the terminal by sending terminal control messages, and

the terminal replies to the terminal general response message.

5.3 Location and Alarm Protocols

5.3.1 Location Information Report

The terminal periodically sends the location information report message

according to the parameter setting.

According to the parameter control, the terminal can send a position

information report message when it judges that the vehicle turns.

5.3.2 Location Information Query

The platform queries the current location information of the designated

vehicle terminal by sending a location information query message, and the

terminal replies with a location information query response message.

5.3.3 Temporary Position Tracking Control

The platform starts/stops location tracking by sending a temporary location

tracking control message. Location tracking requires the terminal to report

periodically before stopping, and report at the time interval specified by the

message. The terminal replies with a terminal general response message.

5.3.4 Terminal Alarm

When the terminal judges that the alarm condition is met, it sends a location

information report message, and sets the corresponding alarm flag in the

location report message. The platform can perform alarm processing by

replying to the platform general response message.

For each alarm type, see the description in the message body of the location

information report. The alarm flag is maintained until the alarm condition is

released. After the alarm condition is released, a position information report

message should be sent immediately to clear the corresponding alarm flag.

5.4 Information Protocol

5.4.1 Text Message Delivery

The platform sends messages by sending text messages to notify drivers in a

specified way. The terminal replies with a terminal general response message.

5.4.2 Event Setup and Reporting

The platform sends the event list to the terminal for storage by sending the

event setting message. After encountering the corresponding event, the driver

can enter the event list interface to select, and the terminal sends an event

report message to the platform after selection.

The event setting message requires the terminal to reply to the terminal

general response message.

The event report message requires the platform to reply to the platform

general response message.

5.4.3 Questioning

The platform sends the question with the candidate answer to the terminal by

sending the question delivery message, and the terminal displays it

immediately. After the driver selects, the terminal sends the question

answering message to the platform.

To ask a question to deliver a message, the terminal needs to reply to the

terminal general response message.

5.4.4 Information on Demand

The platform sends the information-on-demand menu setting message to the

terminal for storage. The driver can select on-demand/cancel the

corresponding information service through the menu, and the terminal sends

the information on-demand/cancel message to the platform after selection.

After the information service is on-demand, it will regularly receive

information service messages from the platform, such as news, weather

forecast, etc.

The information on demand menu setting message requires the terminal to

reply to the terminal general response message.

Information on demand/cancellation message requires the platform to reply

to the platform's general response message.

The information service message requires the terminal to reply to the terminal

general response message.

5.5 Telephone Protocol

5.5.1 Call Back

By sending a call-back message, the platform asks the terminal to call back

according to the specified phone number, and specifies whether to use the

monitoring mode (the terminal does not turn on the speaker).

The phone call back message requires the terminal to reply to the terminal

general answer message.

5.5.2 Set up Phone book

The platform sets the phone book for the terminal by sending the message of

setting the phone book, which requires the terminal to reply to the terminal

general answer message

5.6 Vehicle Control Protocol

By sending vehicle control messages, the platform requires the terminal to

control the vehicle according to the specified operation. The terminal will

reply the terminal general response message immediately after receiving it.
Afterwards, the terminal controls the vehicle, and replies to the vehicle

control response message according to the result.

5.7 Vehicle Management Protocol

The platform performs area and line settings for the terminal by sending

messages such as setting circular area, setting rectangular area, setting

polygon area, and setting route. The terminal judges whether the alarm

conditions are met according to the attributes of the area and the line. The

alarm includes overspeed alarm, entry and exit area/route alarm, and

insufficient/too long travel time in the road section. The corresponding

additional location information should be included in the location information

report message.

The value range of the area or route ID is 1~0XFFFFFFFF. If the set ID is the

same as an existing area or route ID of the same type in the terminal, the

existing one will be updated.

The platform can also delete the areas and routes saved on the terminal

through messages such as deleting circular areas, deleting rectangular areas,

deleting polygonal areas, and deleting routes.

Setting/deleting area and route messages requires the terminal to reply to the

terminal general response message.

5.8 Information Collection Protocol

5.8.1 Collect Driver Identification Data

When the driver starts to drive, insert the IC card qualification certificate into

the card reader module of the terminal. After the card reader module detects

the entry of the card through the induction switch, it sends the authentication

request to the terminal through the interface, and the terminal sends the

authentication request through the transparent transmission instruction. The

data is forwarded to the IC card certification center of the road transport

permit, and the certification result returned by the certification center is

transparently transmitted to the card reader module. The card reader module

reads the IC card qualification certificate information according to the

authentication result and uploads the result information to the authentication

center (success and failure information) and the home monitoring center (only

the successful information is read) through the terminal.

When the driver finishes driving, he pulls out the IC card. After the card reader

module detects the departure of the card through the induction switch, the

relevant information is uploaded to the authentication center and the home

monitoring center through the terminal.

5.8.2 Collect Electronic Waybill Data

The terminal collects the electronic waybill data upload platform.

5.8.3 Collect Driving Record Data

The platform requests the terminal to upload the specified data by sending

the command message of the data collection of the driving record, and the

message requires the terminal to reply to the message of uploading the data

of the driving record.

5.8.4 Download Driving Record Parameters

The platform requests the terminal to upload the specified data by sending

the driving record parameter download command message, which requires

the terminal to reply to the terminal general response message.

5.9 Multimedia Protocol

5.9.1 Multimedia Event Information Upload

When the terminal takes the initiative to shoot or record due to a specific

event, it should actively upload a multimedia event message after the event

occurs, which requires the platform to reply with a general response message.

5.9.2 Multimedia Data Upload

The terminal sends a multimedia data upload message to upload the

multimedia data. Each complete multimedia data needs to be attached with

the location information report message body during recording, which is

called location multimedia data. The platform determines the receiving

timeout period according to the total number of packets. After receiving all
the data packets or reaching the timeout period, the platform sends a

multimedia data upload response message to the terminal, which confirms

the receipt of all the data packets or requests the terminal to retransmit the

specified data packets.

5.9.3 The Camera Shoots Immediately

The platform issues a shooting command to the terminal by sending the

camera immediate shooting command message, which requires the terminal

to reply to the terminal general response message. If real-time upload is

specified, the terminal will upload the camera image/video after shooting,

otherwise, the image/video will be stored.

5.9.4 Recording Starts

The platform issues a recording command to the terminal by sending a

recording start command message, which requires the terminal to reply to the

terminal general response message. If real-time upload is specified, the

terminal will upload the audio data after recording, otherwise, the audio data

will be stored.

5.9.5 Retrieval Terminal for Storing and Extracting Multimedia Data

The platform obtains the situation of the terminal storing the multimedia data

by sending the stored multimedia data retrieval message, which requires the

terminal to reply to the stored multimedia data retrieval response message.

According to the retrieval result, the platform can request the terminal to

upload the specified multimedia data by sending a stored multimedia data

upload message, which requires the terminal to reply to the terminal general

response message.

5.10 Generic Data Transmission Protocol

The messages that are not defined in the protocol but need to be transmitted

in actual use can use data uplink transparent transmission messages and data

downlink transparent transmission messages to exchange uplink and downlink

data.

The terminal can use the GZIP compression algorithm to compress longer

messages, and use data compression to report messages for upload.

5.11 Encryption Protocol

If encrypted communication is required between the platform and the

terminal, the RSA public key cryptosystem can be used. The platform informs

the terminal of its own RSA public key by sending the platform RSA public key

message, and the terminal replies to the terminal RSA public key message,

and vice versa.

5.12 Subpackage Message

When the message is sent by sub-package, the sub-package message should

use the serial number that increases continuously.

Response to packetized messages, if there is no special response command,

the receiver can use a general response to all packetized messages, or use a

general response to each packetized message, and use the result field

(success/failure) to inform Whether the sender receives all packetized

messages correctly. When all the subpackage messages are not received

correctly, the receiver can use the supplementary subpackage request

command to request the sender to retransmit the missing subpackage

messages. The sender should use the original message to retransmit the

sub-packets in the retransmission ID list once, and the retransmitted

sub-packets are exactly the same as the original sub-packet message.

6. Data Format

6.1 Terminal General Response

Message ID: 0x0001.

The data format of the terminal general response message body is shown in

Table 4.

Table 4: The data format of the terminal general response message body
 Start Byte Field Type of Data Description
The serial number of
0 Reply serial number WORD the corresponding
platform message
The ID of the
2 Answering ID WORD corresponding
platform message
0:
success/confirmation;
4 Result BYTE
1: failure; 2: message
error; 3: not supported

6.2 Platform General Response

Message ID: 0x8001.

The data format of the platform general response message body is shown in

Table 5.

Table 5: The data format of the terminal general response message body

Start Byte Field Type of Data Description

The serial number of
0 Reply serial number WORD the corresponding
terminal message
The ID of the
2 Answering ID WORD corresponding terminal
message
0:
success/confirmation;
1: failure; 2: message
4 Result BYTE error; 3: not
supported; 4: Alarm
processing
confirmation;

6.3 Terminal Heartbeat

Message ID: 0x0002.

The message body of the terminal heartbeat data is empty.

6.4 Retransmission Subpackage Request

Message ID: 0x8003.

See Table 6 for the data format of the message body of the retransmission

subpackage request.
Table 6: the data format of the message body of the retransmission subpackage request.

Start Byte Field Type of Data Description

Corresponds to the message
serial number of the first
0 Original Message Serial Number WORD packet of the original
message that requires
retransmission
Total number of retransmitted
4 BYTE n
packets
The sequence numbers of the
retransmission packets are
5 List of retransmitted packet IDs BYTE[2*n] arranged in order, such as
"packet ID1 packet
ID2...packet IDn".

Note: The response to this message should use the original message to

retransmit the subpackage in the retransmission ID list once, which is exactly

the same as the original subpackage message.

6.5 Terminal Registration

Message ID: 0x0100.

The data format of the terminal registration message body is shown in Table

7.

Table 7: The data format of the terminal registration message body

Start Byte Field Type of Data Description
Indicates the province where
the terminal installation
vehicle is located, 0 is
reserved, and the platform
0 State ID WORD takes the default value. The
provincial ID adopts the first
two digits of the six digits of
the administrative division
code specified in GB/T 2260.
Indicates the city and county
where the terminal
installation vehicle is located,
0 is reserved, and the
platform takes the default
2 City ID WORD
value. The city and county ID
adopts the last four digits of
the six digits of the
administrative division code
stipulated in GB/T 2260.
5 bytes, terminal
4 Manufacturer ID BYTE[5]
manufacturer code
20 bytes, the terminal model
is defined by the
9 Terminal Model BYTE[20] manufacturer, if the number
of digits is insufficient, "0X00"
will be added afterward.
7 bytes, consisting of
uppercase letters and
numbers, this terminal ID is
defined by the system
29 Terminal ID BYTE[7] It is defined by the
manufacturer. When the
number of digits is
insufficient, "0X00" will be
added later.
License plate color, according
to 5.4.12 of JT/T415-2006.
36 Color of Car Plate BYTE
When the card is not played,
the value is 0.
When the color of the license
plate is 0, it means the
37 Vehicle Identification STRING
vehicle VIN; otherwise, it
means the motor vehicle
 number plate issued by the
public security traffic
management department.

6.6 Terminal Registration Response

Message ID: 0x8100.

The data format of the terminal registration response message body is shown

in Table 8.

Table 8: The data format of the terminal registration response message body

Start Byte Field Type of Data Description

The serial number of
0 Reply serial number WORD the corresponding
terminal message
0: successful; 1: the
vehicle has been
registered; 2: the
vehicle is not in the
2 Result BYTE database; 3: the
terminal has been
registered; 4: the
terminal is not in the
database
This field is only
3 Authentication Code STRING
available after success

6.7 Terminal Logout

Message ID: 0x0003.

The terminal logout message body is empty.

6.8 Terminal Authentication

Message ID: 0x0102.

The data format of the terminal authentication message body is shown in

Table 9.

Table 9: The data format of the terminal authentication message body

Start Byte Field Type of Data Description

After the terminal
0 Authentication code STRING reconnects, report the
authentication code

6.9 Set Terminal Parameters

Message ID: 0x8103.

See Table 10 for the message body data format for setting terminal

parameters.

Table 10: The message body data format for setting terminal parameters.
Start Byte Field Type of Data Description
Total number of
0 BYTE
parameters
The format of the
1 parameter list parameter item is
shown in Table 11

Table 11: Terminal parameter item data format

Field Type of Data Description
For the definition and
Parameter ID DWORD description of parameter ID, see
Table 12
Parameter Length BYTE
If it is a multi-value parameter,
multiple parameter items with
Parameter Value the same ID are used in the
message, such as the phone
number of the dispatch center
 Table 12: Terminal parameter setting Definition and description of each parameter item
Parameter ID Type of Data Description
0x0001 DWORD Terminal heartbeat sending interval, in seconds (s)
0x0002 DWORD TCP message response timeout, in seconds (s)
0x0003 DWORD Number of TCP message retransmissions
0x0004 DWORD UDP message response timeout, in seconds (s)
0x0005 DWORD UDP message retransmission times
0x0006 DWORD SMS message response timeout, in seconds (s)
0x0007 DWORD SMS message retransmissions
0x0008-0x000F Reserve
Primary server APN, dial-up access point for wireless
0x0010 STRING communication. If the network standard is CDMA,
this is the PPP dial-up number
Primary server wireless communication dial-up user
0x0011 STRING
name
Main server wireless communication dial-up
0x0012 STRING
password
0x0013 STRING Primary server address, IP or domain name
Backup server APN, dial-up access point for wireless
0x0014 STRING
communication
Backup server wireless communication dial-up user
0x0015 STRING
name
Backup server wireless communication dial-up
0x0016 STRING
password
0x0017 STRING Backup server address, IP or domain name
0x0018 DWORD Server TCP port
0x0019 DWORD Server UDP port
Road transport certificate IC card authentication
0x001A STRING
main server IP address or domain name
Road Transport Permit IC Card Authentication Main
0x001B DWORD
Server TCP Port
Road Transport Permit IC Card Authentication Main
0x001C DWORD
Server UDP Port
Road transport certificate IC card authentication
0x001D STRING backup server IP address or domain name, the port
is the same as the main server
0x001E-0x001F Reserve
Location reporting strategy, 0: regular reporting; 1:
0x0020 DWORD fixed-distance reporting; 2: regular and
fixed-distance reporting
Location reporting scheme, 0: according to ACC
0x0021 DWORD status; 1: according to login status and ACC status,
first judge login status, if logged in, then according
 to ACC status
The time interval for reporting that the driver is not
0x0022 DWORD
logged in, in seconds (s), >0
0x0023-0x0026 DWORD Reserve
Report time interval when sleeping, the unit is
0x0027 DWORD
second (s), > 0
The time interval for reporting emergency alarm,
0x0028 DWORD
the unit is second (s), >0
0x0029 DWORD Default time reporting interval, in seconds (s), >0
0x002A-0x002B DWORD Reserve
0x002C DWORD Default distance reporting interval, in meters (m), >0
The driver does not log in to report the distance
0x002D DWORD
interval, the unit is meters (m), > 0
Report distance interval when sleeping, the unit is
0x002E DWORD
meters (m), > 0
Report distance interval during emergency alarm,
0x002F DWORD
the unit is meters (m), > 0
0x0030 DWORD Inflection point supplementary pass angle, <180
The radius of the electronic fence (the illegal
0x0031 WORD
displacement threshold), in meters
0x00032-0x003F Reserve
0x0040 STRING Monitoring platform phone number
Reset phone number, you can use this phone
0x0041 STRING
number to call the terminal to reset the terminal
Factory reset phone number, you can use this phone
0x0042 STRING number to call the terminal to restore the factory
settings
0x0043 STRING Monitoring platform SMS phone number
0x0044 STRING Receiving terminal SMS text alarm number
Terminal phone answering strategy, 0: automatic
0x0045 DWORD answering; 1: automatic answering when ACC is ON,
manual answering when it is OFF
The longest call time each time, in seconds (s), 0
0x0046 DWORD
means no call allowed, 0xFFFFFFFF means no limit
The longest talk time in the current month, the unit
0x0047 DWORD is seconds (s), 0 means no call is allowed,
0xFFFFFFFF means no limit
0x0048 STRING Monitor phone number
0x0049 STRING Supervision platform privileged SMS number
0x004A-0x004F Reserve
Alarm mask word, corresponding to the alarm flag in
0x0050 DWORD the location information report message, if the
corresponding bit is 1, the corresponding alarm is
 masked
Alarm sending text SMS switch, corresponding to
the alarm flag in the location information report
0x0051 DWORD message, when the corresponding bit is 1, the text
SMS will be sent when the corresponding alarm
occurs
The alarm shooting switch corresponds to the alarm
flag in the location information report message, and
0x0052 DWORD
the corresponding bit is
1 camera shooting when the corresponding alarm
The alarm shooting storage flag corresponds to the
alarm flag in the location information report
0x0053 DWORD message. If the corresponding bit is 1, the photos
taken during the corresponding alarm will be stored,
otherwise, they will be uploaded in real time.
The key flag corresponds to the alarm flag in the
location information report message. When the
0x0054 DWORD
corresponding bit is 1, the corresponding alarm is a
key alarm.
0x0055 DWORD Maximum speed in kilometers per hour (km/h)
0x0056 DWORD Overspeed duration, in seconds (s)
0x0057 DWORD Continuous driving time threshold, in seconds (s)
The cumulative driving time threshold of the day, in
0x0058 DWORD
seconds (s)
0x0059 DWORD Minimum rest time, in seconds (s)
0x005A DWORD Maximum parking time, in seconds (s)
Overspeed alarm warning difference, the unit is
0x005B WORD
1/10Km/h
Fatigue driving warning difference, the unit is
0x005C WORD
second (s), >0
Collision alarm parameter settings:
b7-b0: Collision time, unit 4ms;
0x005D WORD
b15-b8: Collision acceleration, the unit is 0.1g, the
setting range is: 0-79, the default is 10.
Rollover alarm parameter settings:
0x005E WORD Rollover angle, the unit is 1 degree, the default is 30
degrees.
0x005F-0x0063 Reserve
0x0064 DWORD Timing photo control, see Table 13
0x0065 DWORD Fixed distance photo control, see Table 14
0x0066-0x006F Reserve
0x0070 DWORD Image/video quality, 1-10, 1 is best
0x0071 DWORD Brightness, 0-255
0x0072 DWORD Contrast, 0-127
 0x0073 DWORD Saturation, 0-127
0x0074 DWORD Chroma, 0-255
0x0075-0x007F Reserve
0x0080 DWORD Vehicle odometer reading, 1/10km
0x0081 WORD The ID of the State where the vehicle is located
0x0082 WORD The ID of the city where the vehicle is located
Motor vehicle license plate issued by public security
0x0083 STRING
traffic management department
License plate color, according to 5.4.12 of
0x0084 BYTE
JT/T415-2006
GNSS positioning mode, defined as follows:
bit0, 0: disable GPS positioning, 1: enable GPS
positioning;
bit1, 0: disable Beidou positioning, 1: enable Beidou
0x0090 BYTE positioning;
bit2, 0: disable GLONASS positioning, 1: enable
GLONASS positioning;
bit3, 0: Disable Galileo positioning, 1: Enable Galileo
positioning.
GNSS baud rate, defined as follows:
0x00: 4800; 0x01: 9600;
0x0091 BYTE
0x02: 19200; 0x03: 38400;
0x04: 57600; 0x05: 115200.
The detailed positioning data output frequency of
the GNSS module is defined as follows:
0x0092 BYTE 0x00: 500ms; 0x01: 1000ms (default);
0x02: 2000ms; 0x03: 3000ms;
0x04: 4000ms.
The frequency of GNSS module detailed positioning
0x0093 DWORD
data collection, the unit is second, the default is 1.
GNSS module detailed positioning data upload
method:
0x00, local storage, do not upload (default);
0x01, upload by time interval;
0x02, upload by distance interval;
0x0B, upload according to the accumulated time,
and automatically stop uploading when the
0x0094 BYTE
transmission time is reached;
0x0C, upload according to the accumulated
distance, and automatically stop uploading when
the distance is reached;
0x0D, upload according to the cumulative number
of records, and automatically stop uploading when
the number of uploaded records is reached.
 GNSS module detailed positioning data upload
settings:
When the upload method is 0x01, the unit is
seconds;
When the upload method is 0x02, the unit is meters;
0x0095 DWORD
When the upload method is 0x0B, the unit is
seconds;
When the upload method is 0x0C, the unit is
meters;
When the upload method is 0x0D, the unit is PC.
CAN bus channel 1 acquisition time interval (ms), 0
0x0100 DWORD
means no acquisition
CAN bus channel 1 upload time interval (s), 0 means
0x0101 WORD
no upload
CAN bus channel 2 acquisition time interval (ms), 0
0x0102 DWORD
means no acquisition
CAN bus channel 2 upload time interval (s), 0 means
0x0103 WORD
no upload
CAN bus ID individual acquisition settings:
bit63-bit32 indicates the ID collection time interval
(ms), 0 indicates no collection;
bit31 represents the CAN channel number, 0: CAN1,
1: CAN2;
0x0110 BYTE[8]
bit30 indicates the frame type, 0: standard frame, 1:
extended frame;
bit29 indicates the data collection method, 0: raw
data, 1: calculated value of the collection interval;
bit28-bit0 represent CAN bus ID.
0x0111-0x01FF BYTE[8] Separate acquisition setup for other CAN bus IDs
0xF000-0xFFFF Custom

Table 13: Timing photo control bit definition

Bit Definition Description
0 Camera channel 1 timing photo switch mark 0: not allowed; 1: allowed
1 Camera channel 2 timing photo switch mark 0: not allowed; 1: allowed
2 Camera channel 3 timing photo switch mark 0: not allowed; 1: allowed
3 Camera channel 4 timing photo switch mark 0: not allowed; 1: allowed
4 Camera channel 5 timing photo switch mark 0: not allowed; 1: allowed
5-7 Reserve
8 Camera channel 1 timing photo storage mark 0: Store; 1: Upload
9 Camera channel 2 timing photo storage mark 0: Store; 1: Upload
10 Camera channel 3 timing photo storage mark 0: Store; 1: Upload
11 Camera channel 4 timing photo storage mark 0: Store; 1: Upload
 12 Camera channel 5 timing photo storage mark 0: Store; 1: Upload
13-15 Reserve
16 0: Second, when the value is less than 5
seconds, the terminal will process it as 5
Timing time unit
seconds;
1: Minute
17-31 Execute after receiving parameter
Time interval
settings or restarting

Table 14: Definition of fixed-distance camera control bits

Bit Definition Description
0 Camera channel 1 fixed-distance photo switch mark 0: not allowed; 1: allowed
1 Camera channel 2 fixed-distance photo switch mark 0: not allowed; 1: allowed
2 Camera channel 3 fixed-distance photo switch mark 0: not allowed; 1: allowed
3 Camera channel 4 fixed-distance photo switch mark 0: not allowed; 1: allowed
4 Camera channel 5 fixed-distance photo switch mark 0: not allowed; 1: allowed
5-7 Reserve
8 Camera channel 1 fixed-distance photo storage mark 0: Store; 1: Upload
9 Camera channel 2 fixed-distance photo storage mark 0: Store; 1: Upload
10 Camera channel 3 fixed-distance photo storage mark 0: Store; 1: Upload
11 Camera channel 4 fixed-distance photo storage mark 0: Store; 1: Upload
12 Camera channel 5 fixed-distance photo storage mark 0: Store; 1: Upload
13-15 Reserve
16 0: meters, when the value is less
than 100 meters, the terminal will
distance unit be treated as 100 meters; 16 fixed
distance distance unit
1: km.
17-31 Execute after receiving parameter
fixed distance interval
settings or restarting

6.10 Query Terminal Parameters

Message ID: 0x8104.

The message body of query terminal parameters is empty.

6.11 Query The Specified Terminal Parameters

Message ID: 0x8106.

See Table 15 for the data format of the message body for querying the

specified terminal parameters, and the terminal responds with the 0x0104

command.
Table 15: the data format of the message body for querying the specified terminal parameters
Start Byte Field Type of Data Description
The total number of
0 Total number of parameters BYTE[]
parameters is n
Arrange the parameters
in order, such as
1 List of parameter IDs BYTE[4*n] "parameter ID1
parameter
ID2...parameter IDn"

6.12 Query Terminal Parameter Response

Message ID: 0x0104.

See Table 16 for the body data format of the query terminal parameter

response message.
Table 16: the body data format of the query terminal parameter response message

Start Byte Field Type of Data Description

The serial number of
the corresponding
0 Reply serial number WORD
terminal parameter
query message
number of response
2 BYTE 0: successful; 1: the
parameters
The format and
definition of parameter
3 parameter list
items are shown in
Table 10

6.13 Terminal Control

Message ID: 0x8105.

The data format of the terminal control message body is shown in Table 17.
Table 17: The data format of the terminal control message body

Start Byte Field Type of Data Description

For the description of
terminal control
0 Command word BYTE
command words, see
Table 18
The command
parameter format is
described later. Each
field is separated by a
1 Command Parameter STRING half-width ";". Each
STRING field is first
processed by GBK
encoding and then
formed into a message.

Table 18: Terminal control command word description

Command Word Command Parameter Description
Wireless upgrades. Parameters are
separated by semicolons. The
instructions are as follows: "URL
address; dial-up point name; dial-up
See Table 19 for the user name; dial-up password; address;
1
command parameter format TCP port; UDP port; manufacturer ID;
hardware version; firmware version;
time limit to connect to the specified
server", If a parameter has no value, it
will be empty
The control terminal connects to the
specified server. Parameters are
separated by semicolons. The control
commands are as follows:
See Table 19 for the
2 "Connection control; supervision
command parameter format
platform authentication code; dial-up
point name; dial-up user name; dial-up
password; address; TCP port; If it is 1,
there is no subsequent parameter
3 No Terminal shutdown
4 No Terminal reset
 5 No Terminal reset to factory settings
6 No Turn off data communication
7 No Turn off all wireless communications

Table 19: Command parameter format

Field Type of Data Description
0: Switch to the designated monitoring
platform server. After connecting to the
server, it will enter an emergency state. In
this state, only the monitoring platform that
Connection Control BYTE issued control commands can send control
commands including short messages; 1:
Switch back to the original default
monitoring platform server and return to
normal.
Generally, it is the server APN, the wireless
communication dial-up access point. If the
Dial Point Name STRING
network standard is CDMA, the value is the
PPP connection dial-up number.
Server wireless communication dial-up
Dial-up Username STRING
username
Server wireless communication dial-up
Dial-up Password STRING
password
Address STRING Server address, IP or domain name
TCP Port WORD Server TCP port
UDP Port WORD Server UDP port
Manufacturer ID BYTE[5] Terminal Manufacturer Code
The authentication code issued by the
supervision platform is only used for
authentication after the terminal is
Regulatory platform
STRING connected to the supervision platform. The
authentication code
terminal is connected back to the original
monitoring platform and the original
authentication code is used.
The hardware version number of the
Hardware Version STRING
terminal, determined by the manufacturer
The firmware version number of the
Firmware Version STRING terminal, which is determined by the
manufacturer
URL Address STRING Full URL address
Unit: minutes (min), a value other than 0
Connect to the
means that the terminal should connect
specified server time WORD
back to the original address before the
limit
expiration of the validity period after the
 terminal receives the instruction to upgrade
or connect to the designated server. If the
value is 0, it means that the specified server
is always connected

6.14 Query Terminal Properties

Message ID: 0x8107.

The message body of the query terminal attribute is empty.

6.15 Query Terminal Properties Reply

Message ID: 0x0107.

See Table 20 for the data format of the message body of the query terminal

attribute response message.

Table 20: the data format of the message body of the query terminal attribute response message.
Start Byte Field Type of Data Description
bit0, 0: not applicable to passenger
vehicles, 1: applicable to passenger
vehicles;
bit1, 0: not applicable to dangerous
goods vehicles, 1: applicable to
dangerous goods vehicles;
bit2, 0: not applicable to ordinary
freight vehicles, 1: applicable to
0 Type of Terminal WORD ordinary freight vehicles;
bit3, 0: not applicable to rental
vehicles, 1: applicable to rental
vehicles;
bit6, 0: does not support hard disk
video recording, 1: supports hard disk
video recording;
bit7, 0: All-in-one machine, 1: Split
machine.
2 Manufacturer ID BYTE[5] 5 bytes, terminal manufacturer code.
20 bytes, the terminal model is defined
7 Terminal Model BYTE[20]
by the manufacturer, if the number of
 digits is insufficient, "0X00" will be
added afterward.
7 bytes, consisting of uppercase letters
and numbers, the terminal ID is
27 Terminal ID BYTE[7] defined by the manufacturer, if the
number of digits is insufficient, "0X00"
is appended.
Terminal SIM card
42 BYTE[10] Terminal SIM card ICCID
ICCID
Terminal hardware
52 version number BYTE n
length
Terminal hardware
53 STRING
version number
Terminal firmware
53+n version number BYTE m
length
Terminal firmware
54+n STRING
version number
bit0, 0: GPS positioning is not
supported, 1: GPS positioning is
supported;
bit1, 0: do not support Beidou
positioning, 1: support Beidou
GNSS module positioning;
54+n+m BYTE
properties bit2, 0: GLONASS positioning is not
supported, 1: GLONASS positioning is
supported;
bit3, 0: Galileo positioning is not
supported, 1: Galileo positioning is
supported.
bit0, 0: does not support GPRS
communication, 1: supports GPRS
communication;
bit1, 0: does not support CDMA
communication, 1: supports CDMA
communication;
Communication
55+n+m BYTE bit2, 0: does not support TD-SCDMA
Module Properties
communication, 1: supports
TD-SCDMA communication;
bit3, 0: does not support WCDMA
communication, 1: supports WCDMA
communication;
bit4, 0: does not support CDMA2000
 communication, 1: supports
CDMA2000 communication.
bit5, 0: does not support TD-LTE
communication, 1: supports TD-LTE
communication;
bit7, 0: Other communication methods
are not supported, 1: Other
communication methods are
supported.

6.16 Issue The Terminal Upgrade Package

Message ID: 0x8108.

See Table 21 for the data format of the message body of the delivered

terminal upgrade package. Use the generic reply to the command terminal to

confirm whether the upgrade package data is received correctly.

Table 21: The data format of the message body of the delivered terminal upgrade package
Start Byte Field Type of Data Description
0: Terminal, 12: IC card reader for road
0 Type of Upgrade BYTE transport certificate, 52: Beidou
satellite positioning module
1 Manufacturer ID BYTE[5] 5 bytes, terminal manufacturer code.
Version Number
6 BYTE n
Length
7 Version Number STRING
Upgrade packet
7+n DWORD Unit is: BYTE
length
11+n Upgrade package

6.17 Terminal Upgrade Result Notification

Message ID: 0x0108.

The terminal uses this command to notify the monitoring center after the

upgrade is completed and reconnected. See Table 22 for the data format of
the terminal upgrade result notification message body.

Table 22: The data format of the terminal upgrade result notification message body.
Start Byte Field Type of Data Description
0: Terminal, 12: IC card reader for road
0 Type of Upgrade BYTE transport certificate, 52: Beidou
satellite positioning module
1 Upgrade Result BYTE 0: success, 1: failure, 2: cancel

6.18 Location Information Report

Message ID: 0x0200.

The location information report message body consists of a list of location

basic information and location additional information items. The message

structure diagram is shown in Figure 3:

Basic location information List of location extension items

Figure 3: Location report message structure diagram

The list of location additional information items is a combination of each

location additional information item, or may not, and is determined according

to the length field in the message header.

See Table 23 for the data format of the basic location information.

Table 23: The data format of the basic location information

Start Byte Field Type of Data Description
Refer to Table 24 for the definition of
0 Alarm Sign DWORD
alarm flags
For the definition of status bits, see
4 Status DWORD
Table 25
Latitude value in degrees multiplied by
8 Latitude DWORD
10 to the 6th power to the nearest
 millionth of a degree
Longitude value in degrees multiplied
12 Longitude DWORD by 10 to the 6th power to the nearest
millionth of a degree
16 Height WORD Altitude, in meters (m)
18 Speed WORD 1/10km/h
20 Direction WORD 0-359, true north is 0, clockwise
YY-MM-DD-hh-mm-ss (GMT+8 time,
21 Time BCD[6] the time involved in this standard is in
this time zone)

Table 24: Definition of alarm bit

Bit Definition Processing Instructions
1: Emergency alarm, trigger after
0 Cleared after receiving response
touching the alarm switch
The flag is maintained until the alarm
1 1: Overspeed alarm
condition is released
The flag is maintained until the alarm
2 1: Fatigue driving
condition is released
3 1: Danger warning Cleared after receiving response
The flag is maintained until the alarm
4 1: GNSS module failure
condition is released
1: GNSS antenna not connected or The flag is maintained until the alarm
5
cut off condition is released
The flag is maintained until the alarm
6 1: GNSS antenna short circuit
condition is released
1: Undervoltage of the terminal main The flag is maintained until the alarm
7
power supply condition is released
1: The main power supply of the The flag is maintained until the alarm
8
terminal is powered off condition is released
The flag is maintained until the alarm
9 1: Terminal LCD or display failure
condition is released
The flag is maintained until the alarm
10 1: TTS module failure
condition is released
The flag is maintained until the alarm
11 1: Camera failure
condition is released
1: The IC card module of the road The flag is maintained until the alarm
12
transport certificate is faulty condition is released
The flag is maintained until the alarm
13 1: Overspeed warning
condition is released
The flag is maintained until the alarm
14 1: Fatigue driving warning
condition is released
15-17 Reserve
 1: Cumulative driving overtime on The flag is maintained until the alarm
18
the day condition is released
The flag is maintained until the alarm
19 1: Overtime parking
condition is released
20 1: In and out of the area Cleared after receiving response
21 1: In and out route Cleared after receiving response
1: Insufficient/too long driving time
22 Cleared after receiving response
on the road section
The flag is maintained until the alarm
23 1: Route deviation alarm
condition is released
The flag is maintained until the alarm
24 1: Vehicle VSS failure
condition is released
The flag is maintained until the alarm
25 1: The vehicle oil level is abnormal
condition is released
1: Vehicle stolen (via vehicle The flag is maintained until the alarm
26
immobilizer) condition is released
27 1: Illegal ignition of the vehicle Cleared after receiving response
28 1: Illegal displacement of the vehicle Cleared after receiving response
The flag is maintained until the alarm
29 1: Collision warning
condition is released
The flag is maintained until the alarm
30 1: Rollover warning
condition is released
1: Illegal door opening alarm (when
31 the terminal does not set an area, it Cleared after receiving response
will not judge illegal door opening)

Note: The location information must be reported immediately when an alarm or

warning occurs.

Table 25: Status Bit Definitions

Bit Status
0 0: ACC off; 1: ACC on
1 0: not positioned; 1: positioned
2 0: north latitude; 1: south latitude
3 0: East longitude; 1: West longitude
4 0: Operation status; 1: Out of service status
0: The latitude and longitude are not encrypted by the security plugin; 1: The
5
latitude and longitude have been encrypted by the security plugin
6-7 Reserve
00: Empty; 01: Half-loaded; 10: Reserved; 11: Full-load
8-9 (It can be used to indicate the empty and full load status of passenger cars, heavy
vehicles and trucks, manual input or sensor acquisition)
10 0: The vehicle oil circuit is normal; 1: The vehicle oil circuit is disconnected
 11 0: The vehicle oil circuit is normal; 1: The vehicle oil circuit is disconnected
12 0: Door unlocked; 1: Door locked
13 0: Door 1 closed; 1: Door 1 open (front door)
14 0: Door 2 closed; 1: Door 2 open (middle door)
15 0: Door 3 closed; 1: Door 3 open (back door)
16 0: Door 4 closed; 1: Door 4 open (driver's door)
17 0: Door 5 closed; 1: Door 5 open (custom)
0: GPS satellites are not used for positioning; 1: GPS satellites are used for
18
positioning
0: BD satellites are not used for positioning; 1: BD satellites are used for
19
positioning
0: GLONASS satellites are not used for positioning; 1: GLONASS satellites are used
20
for positioning
0: Galileo satellites are not used for positioning; 1: Galileo satellites are used for
21
positioning
22-31 Reserve

Note: If the status changes, the location information must be reported immediately.

The format of the location additional information item is shown in Table 26.
Table 26: Location extension item format
Field Type of Data Description
Additional Information ID BYTE 1-255
Additional Information
BYTE
Length
Additional information is defined in
Additional Information
Table 27

Table 27: Additional Information Definition

Additional Info ID Length Description
Mileage, DWORD, 1/10km, corresponding to the
0x01 4
reading on the odometer
Fuel quantity, WORD, 1/10L, corresponding to the
0x02 2
reading of the fuel gauge on the vehicle
The speed obtained by the driving record function,
0x03 2
WORD, 1/10km/h
The ID of the alarm event that needs to be manually
0x04 2
confirmed, WORD, counts from 1
0x05 - 0x10 Reserve
See Table 28 for additional information on
0x11 1 or 5
overspeed alarms
0x12 6 See Table 29 for additional information on entry and
 exit zone/route alarms
Refer to Table 30 for additional information on the
0x13 7 warning of insufficient/too long driving time on the
road section
0x14 - 0x24 Reserve
Extended vehicle signal status bits, see Table 31 for
0x25 4
definitions
0x2A 2 I0 status bits, see Table 32 for definitions
0x2B 4 Analog, bit0-15, AD0; bit16-31, AD1.
BYTE, wireless communication network signal
0x30 1
strength
0x31 1 BYTE, the number of GNSS positioning satellites
Follow-up message
0xE0 Subsequent custom message length
length
0xE1 - 0xFF Custom Area

Table 28: Overspeed alarm additional information message body data format
Start Byte Field Type of Data Description
0: no specific location;
1: circular area;
0 Location Type BYTE 2: Rectangular area;
3: polygon area;
4: Road Section
If the location type is 0, this field is
1 Area or segment ID DWORD
empty

Table 29: Entry and exit area/route alarm additional information message body data format
Start Byte Field Type of Data Description
1: circular area;
2: Rectangular area;
0 Location Type BYTE
3: polygon area;
4: Route
1 Area or segment ID DWORD
0: In;
5 Direction BYTE
1: Out

Table 30: Route travel time is insufficient/too long alarm additional information message
body data format
Start Byte Field Type of Data Description
0 Segment ID DWORD
Road segment travel
4 WORD The unit is second (s)
time
6 Result BYTE 0: not enough; 1: too long
 Table 31: Extended Vehicle Signal Status Bits
Bit Status
0 1: Low beam signal
1 1: High beam signal
2 1: Right turn signal signal
3 1: Left turn signal signal
4 1: Brake signal
5 1: Reverse gear signal
6 1: Fog light signal
7 1: Position light
8 1: Speaker signal
9 1: Air conditioner status
10 1: Neutral signal
11 1: The retarder works
12 1: ABS works
13 1: The heater works
14 1: clutch status
15-31 Reserve

Table 32: IO status bits

Bit Status
0 1: Deep sleep state
1 1: Sleep state
2 -15 Reserve

6.19 Location Information Query

Message ID: 0x8201.

The location information query message body is empty.

6.20 Location Information Query Response

Message ID: 0x0201.

The data format of the location information query response message body is

shown in Table 33.

Table 33: The data format of the location information query response message body
Start Byte Field Type of Data Description
The serial number of the
0 Reply serial number WORD corresponding location information
query message
location information For location information reporting see
2
report 6.12

6.21 Temporary Position Tracking Control

Message ID: 0x8202.

See Table 34 for the data format of the temporary location tracking control

message body.
Table 34: The data format of the temporary location tracking control message body.
Start Byte Field Type of Data Description
The unit is seconds (s), 0 stops
0 Time Interval WORD tracking. Stop tracking without a
successor field
The unit is seconds (s). After receiving
the location tracking control message,
Location Tracking the terminal sends the location report
2 DWORD
Validity Period according to the time interval in the
message before the expiration time of
the validity period.

6.22 Manual Acknowledgment of Alarm Messages

Message ID: 0x8203.

See Table 35 for the manual confirmation alarm message body data format.
Table 35: The manual confirmation alarm message body data format
Start Byte Field Type of Data Description
Serial number of alarm messages that
Alarm message serial
0 WORD need manual confirmation, 0 means all
number
messages of this alarm type
Manual
2 acknowledgment of DWORD See Table 36 for definitions
alarm types
 Table 36: Definition for manual acknowledgment of alarm types
Bit Status
0 1: Confirm emergency alarm;
1 -2 Reserve
3 1: Confirm the danger warning;
4 -19 Reserve
20 1: Confirm the alarm in and out of the area;
21 1: Confirm the incoming and outgoing route alarm;
22 1: Confirm that the driving time of the road section is insufficient/too long;
23 - 26 Reserve
27 1: Confirm the illegal ignition of the vehicle and alarm;
28 1: Confirm the illegal displacement of the vehicle and alarm;
29 -31 Reserve

6.23 Text Message Delivery

Message ID: 0x8300.

See Table 37 for the data format of the text message delivery message body.
Table 37: The data format of the text message delivery message body
Start Byte Field Type of Data Description
See Table 38 for the meaning of the
0 Sign BYTE
text information flags
1 Text Message STRING Up to 1024 bytes, GBK encoded

Table 38: The meaning of the text information bits

Bit Mark
0 1: Emergency
1 Reserve
2 1: Display on the terminal monitor
3 1: Terminal TTS broadcast and read
4 1: Advertising screen display
5 0: center navigation information, 1: CAN fault code information
6-7 Reserve

6.24 Event Settings

Message ID: 0x8301.

The event setting message body data format is shown in Table 39.
 Table 39: The event setting message body data format
Start Byte Field Type of Data Description
0: Delete all existing events of the
terminal, without subsequent bytes
after this command;
1: update event;
0 Setting Type BYTE 2: Append event;
3: Modify the event;
4: Delete certain events, after which
there is no need to include event
content in event items
Total Numbers of
1 BYTE
Setting
See Table 40 for the data format of
2 Event item list
event item composition

Table 40: The data format of event item composition

Start Byte Field Type of Data Description
If the terminal already has an event
0 Event ID BYTE
with the same ID, it will be overwritten
Event Content Subsequent event content field byte
1 BYTE
Length length
2 Event Content STRING Event content, GBK encoded

6.25 Event Report

Message ID: 0x0301.

The event report message body data format is shown in Table 41.
Table 41: The event report message body data format
Start Byte Field Type of Data Description
0 Event ID BYTE

6.26 Issue A Question

Message ID: 0x8302.

The data format of the message body for question delivery is shown in Table

42.
 Table 42: The data format of the message body for question delivery
Start Byte Field Type of Data Description
See Table 43 for the definition of the
0 Sign BYTE
question issuing flag.
Question content
1 BYTE Question field byte length
length
2 Question STRING Question text, GBK encoded, length N
Candidate answer The composition of the candidate
2+N
list answer message is shown in Table 44

Table 43: The definition of the question issuing flag

Bit Mark
0 1: Emergency
1 Reserve
2 Reserve
3 1: Terminal TTS broadcast and read
4 1: Advertising screen display
5-7 Reserve

Table 44: The composition of the candidate answer message

Start Byte Field Type of Data Description
0 Answer ID BYTE
Answer content
1 WORD Answer field byte length
length
3 Answer Content STRING Answer text, GBK encoded

6.27 Question Response

Message ID: 0x0302.

See Table 45 for the data format of the question-response message body.
Table45: The data format of the question response message body
Start Byte Field Type of Data Description
Response serial The serial number of the message
0 WORD
number issued by the corresponding question
The answer ID attached to the
2 Answer ID BYTE
question distribution

6.28 Information on Demand Menu Settings

Message ID: 0x8303.

See Table 46 for the message body data format set in the information on

demand menu.
Table 46: The message body data format set in the information on demand menu
Start Byte Field Type of Data Description
0: delete all terminal information
items;
0 Type of Setting BYTE 1: Update menu;
2: Additional menu;
3: Modify the menu
Total number of
1 BYTE
information items
See Table 47 for the composition data
list of information
2 format of information on demand
items
information items

Table 47: The composition data format of information on demand information items
Start Byte Field Type of Data Description
If the terminal already has an
0 Type of message BYTE information item of the same type, it
will be overwritten
message name
1 WORD Message name field byte length
length
3 Message name STRING Processed by GBK encoding

6.29 Information on Demand / Cancellation

Message ID: 0x0303.

See Table 48 for the message body data format for message

on-demand/cancellation.
Table 48: The message body data format for message on demand/cancellation
Start Byte Field Type of Data Description
0 Type of message BYTE
On-demand/cancel
1 BYTE 0: Cancel; 1: On-demand
flag
6.30 Information Service

Message ID: 0x8304.

See Table 49 for the information service message body data format.
Table 49: The information service message body data format
Start Byte Field Type of Data Description
0 Type of message BYTE
1 message length WORD
3 Message content STRING Processed by GBK encoding

6.31 Call Back

Message ID: 0x8400.

See Table 50 for the data format of the phone callback message body.
Table 50: The data format of the phone callback message body
Start Byte Field Type of Data Description
0 Sign BYTE 0: Normal call; 1: Monitor
1 Phone number BYTE Up to 20 bytes

6.32 Setting Phone Book

Message ID: 0x8401.

See Table 51 for setting the phone book message body data format.
Table 51: Setting the phone book message body data format
Start Byte Field Type of Data Description
0: delete all stored contacts on the
terminal;
1: means to update the phone book
(delete all contacts in the terminal and
0 Type of Setting BYTE
add contacts in the message);
2: Indicates additional phone book;
3: Indicates to modify the phone book
(indexed by contacts)
total number of
1 BYTE
contacts
See Table 52 for the data format of
2 Contact item
phone book contact items
 Table 52: The data format of phone book contact items
Start Byte Field Type of Data Description
1: Incoming; 2: Outgoing; 3:
0 Sign BYTE
Incoming/Outgoing
1 number length BYTE
2 Phone number STRING length n
2+n Contact length BYTE
3+n Contact STRING GBK encoded

6.33 Vehicle Control

Message ID: 0x8500.

The data format of the vehicle control message body is shown in Table 53.
Table 53: The data format of the vehicle control message body
Start Byte Field Type of Data Description
See Table 54 for the data format of the
0 control sign BYTE
control command flag bit

Table 54: The data format of the control command flag bit
Bit Sign
0 0: Door unlocked; 1: Door locked
1-7 Reserve

6.34 Vehicle Control Response

Message ID: 0x0500.

The data format of the vehicle control response message body is shown in

Table 55.
Table 55: The data format of the vehicle control response message body
Start Byte Field Type of Data Description
Response serial The serial number of the
0 WORD
number corresponding vehicle control message
Determine whether the control is
Location information
2 successful or not according to the
report message body
corresponding status bit
6.35 Set Circular Area

Message ID: 0x8600.

See Table 56 for setting the data format of the circular area message body.

Note: This message protocol supports the periodic time range. If you want to

limit the daily 8:30-18:00, the start/end time is set to:

00-00-00-08-30-00/00-00-00-18 -00-00, others and so on.

Table 56: Setting the data format of the circular area message body
Start Byte Field Type of Data Description
0: update area;
0 Setting Properties BYTE 1: Additional area;
2: Modify the area
Determine whether the control is
1 Total Area BYTE successful or not according to the
corresponding status bit
See Table 57 for the area item content
2 Area Item
data format of the circular area

Table 57: The area ite content data format of the circular area
Start Byte Field Type of Data Description
0 Area ID DWORD
See Table 58 for area attribute
4 Area Properties WORD
definitions
Latitude value in degrees multiplied by
6 Center Point Latitude DWORD 10 to the 6th power to the nearest
millionth of a degree
Longitude value in degrees multiplied
Center Point
10 DWORD by 10 to the 6th power to the nearest
Longitude
millionth of a degree
The unit is meters (m), and the road
14 Radius DWORD segment is from the inflection point to
the next inflection point
YY-MM-DD-hh-mm-ss, if the area
18 Start Time BCD[6]
attribute 0 bit is 0, there is no field
YY-MM-DD-hh-mm-ss, if the area
24 End Time BCD[6]
attribute 0 bit is 0, there is no field
Km/h, if the area attribute 1 bit is 0,
30 Top Speed WORD
there is no such field
32 Overspeed Duration BYTE The unit is second (s) (similar
 expression, same as before), if the
1-bit of the area attribute is 0, there is
no such field

Table 58: Area Attribute Definitions

Bit Sign
0 1: According to time
1 1: Speed limit
2 1: Alarm to the driver when entering the area
3 1: Enter the area and send an alarm to the platform
4 1: Alarm to the driver when leaving the area
5 1: Send an alarm to the platform when leaving the area
6 0: north latitude; 1: south latitude
7 0: East longitude; 1: West longitude
8 0: Allow door opening; 1: Prohibit opening
9 - 13 Reserve
0: Turn on the communication module when entering the area; 1:
14
Turn off the communication module when entering the area
0: Do not collect GNSS detailed positioning data when entering
15 the area; 1: Collect GNSS detailed positioning data when entering
the area

6.36 Delete Circular Area

Message ID: 0x8601.

See Table 59 for the data format of the message body for deleting the circular

area.
Table 59: The data format of the message body for deleting the circular area
Start Byte Field Type of Data Description
The number of areas included in this
message, no more than 125, more
0 Area Numbers BYTE than 125 are recommended to use
multiple messages, 0 is to delete all
circular areas
1 Area ID1 DWORD

... ... DWORD

Area IDn DWORD

6.37 Set Rectangle Area

Message ID: 0x8602.

See Table 60 for setting the format of the message body data in the

rectangular area.
Table 60: Setting the format of the message body data in rectangular area
Start Byte Field Type of Data Description
0: update area;
0 Setting Properties BYTE 1: Additional area;
2: Modify the area
1 Total Area BYTE
See Table 61 for the area item content
2 Area Item
data format of the rectangular area

Table 61: The area item content data format of the rectangular area
Start Byte Field Type of Data Description
0 Area ID DWORD
See Table 58 for area attribute
4 Area Properties WORD
definitions
Latitude value in degrees multiplied by
Latitude of upper left
6 DWORD 10 to the 6th power to the nearest
point
millionth of a degree
Longitude value in degrees multiplied
Longitude of upper
10 DWORD by 10 to the 6th power to the nearest
left point
millionth of a degree
Latitude value in degrees multiplied by
Latitude of lower
14 DWORD 10 to the 6th power to the nearest
right point
millionth of a degree
Longitude value in degrees multiplied
Longitude of lower
18 DWORD by 10 to the 6th power to the nearest
right point
millionth of a degree
YY-MM-DD-hh-mm-ss, if the area
22 Start Time BCD[6]
attribute 0 bit is 0, there is no field
YY-MM-DD-hh-mm-ss, if the area
28 End Time BCD[6]
attribute 0 bit is 0, there is no field
Km/h, if the area attribute 1 bit is 0,
34 Top Speed WORD
there is no such field
The unit is second (s) (similar
expression, same as before), if the
36 Overspeed Duration BYTE
1-bit of the area attribute is 0, there is
no such field
6.38 Delete Rectangular Area

Message ID: 0x8603.

See Table 62 for the data format of the message body for deleting the

rectangular area.
Table 59: The data format of the message body for deleting rectangular area
Start Byte Field Type of Data Description
The number of areas included in this
message, no more than 125, more
0 Area Numbers BYTE than 125 are recommended to use
multiple messages, 0 is to delete all
rectangular areas
1 Area ID1 DWORD

... ... DWORD

Area IDn DWORD

6.39 Set Polygon Area

Message ID: 0x8604.

See Table 63 for setting the data format of the polygon area message body.
Table 63: Setting the data format of the polygon area message body
Start Byte Field Type of Data Description
0 Area ID DWORD
See Table 58 for area attribute
4 Area Properties WORD
definitions
YY-MM-DD-hh-mm-ss, if the area
6 Start Time BCD[6]
attribute 0 bit is 0, there is no field
YY-MM-DD-hh-mm-ss, if the area
12 End Time BCD[6]
attribute 0 bit is 0, there is no field
Km/h, if the area attribute 1 bit is 0,
18 Top Speed WORD
there is no such field
The unit is second (s) (similar
expression, same as before), if the
20 Overspeed Duration BYTE
1-bit of the area attribute is 0, there is
no such field
The total number of
21 WORD
vertices in the area
23 Vertex Item See Table 64 for the vertex item data
 format of the polygon area

Table 64: The vertex item data format of the polygon area
Start Byte Field Type of Data Description
Latitude value in degrees multiplied by
0 Vertex Latitude DWORD 10 to the 6th power to the nearest
millionth of a degree
Longitude value in degrees multiplied
4 Vertex Longitude DWORD by 10 to the 6th power to the nearest
millionth of a degree

6.40 Delete Polygon Area

Message ID: 0x8605.

See Table 65 for the data format of the message body for deleting the polygon

area.
Table 59: The data format of the message body for deleting polygon area
Start Byte Field Type of Data Description
The number of areas included in this
message, no more than 125, more
0 Area Numbers BYTE than 125 are recommended to use
multiple messages, 0 is to delete all
polygon areas
1 Area ID1 DWORD

... ... DWORD

Area IDn DWORD

6.41 Set Route

Message ID: 0x8606.

See Table 66 for setting the route message body data format.
Table 66: Setting the route message body data format
Start Byte Field Type of Data Description
0 Route ID DWORD
Route attribute data format see Table
4 Route Properties WORD
67
6 Start Time BCD[6] YY-MM-DD-hh-mm-ss, if the area
 attribute 0 bit is 0, there is no field
YY-MM-DD-hh-mm-ss, if the area
12 End Time BCD[6]
attribute 0 bit is 0, there is no field
Total number of Km/h, if the area attribute 1 bit is 0,
18 inflection points of WORD there is no such field
the route
See Table 68 for the data format of the
20 Inflection point
route inflection point item

Table 67: Route attribute data format

Bit Sign
0 1: According to time
1 Reserve
2 1: Alarm to the driver when entering the route
3 1: Enter the route and send an alarm to the platform
4 1: Alarm to the driver when leaving the route
5 1: Send an alarm to the platform when leaving the route
6 - 15 Reserve

Table 68: The data format of the route inflection point item
Start Byte Field Type of Data Description
0 Inflection point ID DWORD
See Table 58 for area attribute
4 Route ID DWORD
definitions
Latitude value in degrees multiplied by
Inflection point
8 DWORD 10 to the 6th power to the nearest
latitude
millionth of a degree
Longitude value in degrees multiplied
Inflection point
12 DWORD by 10 to the 6th power to the nearest
longitude
millionth of a degree
The unit is meters (m), and the road
16 Route width BYTE segment is from the inflection point to
the next inflection point
See Table 69 for the data format of
17 Route Properties BYTE
road segment attributes
The unit is second (s), if the 0 bit of the
Road segment travel
18 WORD road segment attribute is 0, there is no
too long threshold
such field
The unit is second (s), if the 0 bit of the
Road segment under
20 WORD road segment attribute is 0, there is no
travel threshold
such field
Road section Km/h, if the area attribute 1 bit is 0,
22 WORD
maximum speed there is no such field
 The unit is second (s), if the 0 bit of the
Duration of speeding
24 BYTE road segment attribute is 0, there is no
on the road
such field

Table 69: The data format of road segment attributes

Bit Sign
0 1: Travel time
1 1: Speed limit
2 0: north latitude; 1: south latitude
3 0: East longitude; 1: West longitude
4-7 Reserve

6.42 Delete Route

Message ID: 0x8607.

See Table 70 for the data format of the message body for deleting route.
Table 70: The data format of the message body for deleting the route
Start Byte Field Type of Data Description
The number of areas included in this
message, no more than 125, more
0 Route Numbers BYTE than 125 are recommended to use
multiple messages, 0 is to delete all
routes
1 Route ID1 DWORD

... ... DWORD

Route IDn DWORD

6.43 Driving Record Data Collection Command

Message ID: 0x8700.

See Table 71 for the data format of the command message body of the driving

record data collection.

Table 71: The data format of the command message body of the driving record data
collection
Start Byte Field Type of Data Description
See the relevant requirements in GB/T
0 Command word BYTE
19056 for the list of command words
See the relevant content in GB/T
19056 for the content format of the
1 Data block data block, including
The complete data package required
by GB/T 19056, which can be empty.

6.44 Driving Record Data Upload

Message ID: 0x0700.

See Table 72 for the data format of the message body for uploading the

driving record data.

Table 72: The data format of the message body for uploading the driving record data
Start Byte Field Type of Data Description
The serial number of the
Response serial
0 WORD corresponding driving record data
number
collection command message
The command word issued by the
2 Command word BYTE
corresponding platform
See the relevant content in GB/T
19056 for the content format of the
3 Data block data block, including
The complete data package required
by GB/T 19056, which can be empty.

6.45 Driving Record Parameter Download Command

Message ID: 0x8701.

See Table 73 for the data format of the command message body for

downloading the driving record parameters.

 Table 73: The data format of the command message body for downloading the
driving record parameters
Start Byte Field Type of Data Description
See the relevant requirements in GB/T
0 Command word BYTE
19056 for the list of command words
See the relevant content in GB/T
19056 for the content format of the
1 Data block data block, including
The complete data package required
by GB/T 19056, which can be empty.

6.46 E-Waybill Reporting

Message ID: 0x0701.

See Table 74 for the data format of the electronic waybill report message

body.
Table 74: The data format of the E-waybill report message body
Start Byte Field Type of Data Description
0 E-Waybill Length DWORD
4 E-Waybill Content Electronic Waybill Packet

6.47 Report Driver Identification Information Request

Message ID: 0x8702.

The message body of the request for reporting driver identity information is

empty.

6.48 Collect and Report Driver Identity Information

Message ID: 0x0702.

This instruction is automatically triggered after the IC card of the terminal

qualification certificate is inserted or pulled out. After receiving the 0x8702

command, use this command to reply. See Table 75 for the data format of the

driver identity information collection and reporting message body.

Table 75: The data format of the driver identity information collection and reporting
message body
Start Byte Field Type of Data Description
0x01: The IC card of the qualification
certificate is inserted (the driver goes
to work);
0 Status BYTE
0x02: The IC card of the qualification
certificate is pulled out (the driver gets
off work).
Card insertion/removal time,
YY-MM-DD-hh-mm-ss;
1 Time BCD[6]
The following fields are only valid and
populated when the status is 0x01.
0x00: IC card reading is successful;
0x01: Card reading failed because the
card key authentication failed;
0x02: Card reading failed because the
card has been locked;
0x03: Card reading failed because the
7 IC card reading result BYTE
card was pulled out;
0x04: Card reading failed due to data
verification error.
The following fields are only valid
when the IC card read result is equal to
0x00.
8 Driver's name length BYTE n
9 Driver's name STRING Driver's name
Qualification The length is 20 digits, if it is
9+n STRING
certificate code insufficient, 0x00 is added.
The length of the
29+n name of the issuing BYTE m
authority
The name of the certificate-issuing
30+n Issuing agency name STRING
institution
30+n+m Certificate validity BCD[4] YYYYMMDD
6.49 Bulk Upload of Positioning Data

Message ID: 0x0704.

See Table 76 for the batch upload data format of positioning data.
Table 76: The batch upload data format of positioning data
Start Byte Field Type of Data Description
Number of data The number of position report data
0 WORD
items items included, > 0
0: Batch report for normal position, 1:
1 Location data type BYTE
Supplementary report for blind area
Location reporting
2 See Table 77 for definitions
data item

Table 77: Location reporting data item data format

Start Byte Field Type of Data Description
Location report data The number of position report data
0 WORD
body length items included, > 0
Location reporting See 6.12 Location Information Report
2 BYTE[n]
data body for definition

6.50 CAN Bus Data Upload

Message ID: 0x0705.

The data format of CAN bus data upload is shown in Table 78.
Table 78: The data format of CAN bus data upload
Start Byte Field Type of Data Description
Number of data The number of CAN bus data items
0 WORD
items included, > 0
CAN bus data Receive time of 1st CAN bus data,
2 BCD[5]
reception time hh-mm-ss-msms
8 CAN bus data item See Table 79 for definitions

Table 79: CAN bus data item data format

Start Byte Field Type of Data Description
bit31 represents the CAN channel
number, 0: CAN1, 1: CAN2;
0 CAN ID BYTE[4]
bit30 indicates the frame type, 0:
standard frame, 1: extended frame;
 bit29 represents the data collection
method, 0: raw data, 1: the average
value of the collection interval;
bit28-bit0 represent CAN bus ID.
4 CAN Data BYTE[8] CAN Data

6.51 Multimedia Event Information Upload

Message ID: 0x0800.

See Table 80 for the upload data format of the multimedia event message.
Table 80: The upload data format of the multimedia event message
Start Byte Field Type of Data Description
0 Multimedia data ID DWORD >0
4 Type of multimedia BYTE 0: Image; 1: Audio; 2: Video;
Multimedia format 0: JPEG; 1: TIF; 2: MP3; 3: WAV; 4:
5 BYTE
encoding WMV; other reserved
0: Command issued by the platform; 1:
Timing action; 2: Robbery alarm
triggered; 3: Collision rollover alarm
triggered; 4: Door open to take
6 Event item code BYTE
pictures; 5: Door closed to take
pictures; km to more than 20 km; 7:
take photos at a fixed distance; other
reservations
7 Channel ID BYTE

6.52 Multimedia Data Upload

Message ID: 0x0801.

See Table 81 for the data format of the multimedia data upload message

body.
 Table 81: The data format of the multimedia data upload message body
Start Byte Field Type of Data Description
0 Multimedia ID DWORD >0
4 Type of multimedia BYTE 0: Image; 1: Audio; 2: Video;
Multimedia format 0: JPEG; 1: TIF; 2: MP3; 3: WAV; 4:
5 BYTE
encoding WMV; other reserved
0: Command issued by the platform; 1:
Timed action; 2: Robbery alarm
6 Event item code BYTE
triggered; 3: Collision rollover alarm
triggered; others reserved
7 Channel ID BYTE
Location information
Location basic information data
8 report (0x0200) BYTE[28]
representing multimedia data
message body
Multimedia Data
36
Packet

6.53 Multimedia Data Upload Response

Message ID: 0x8800.

See Table 82 for the data format of the multimedia data upload response

message body.
Table 82: The data format of the multimedia data upload response message body
Start Byte Field Type of Data Description
>0, no subsequent fields if all packets
0 Multimedia ID DWORD
are received
Total number of
4 retransmitted BYTE n
packets
The sequence numbers of the
List of retransmitted retransmission packets are arranged in
5 BYTE[2*n]
packet IDs order, such as "packet ID1 packet
ID2...packet IDn".

Note: The response to this message should use the 0x0801 message to retransmit
the sub-packet in the retransmission ID list once, which is exactly the same as the
original sub-packet message.
6.54 The Camera Immediately Shoots Command

Message ID: 0x8801.

See Table 83 for the data format of the camera immediate shooting command

message body.
Table 83: The data format of the camera immediately shooting commend message
body
Start Byte Field Type of Data Description
0 Channel ID BYTE >0
0 means stop shooting; 0xFFFF means
1 Shooting Command WORD video recording; other means the
number of pictures taken
Photo Seconds, 0 means taking pictures at
3 interval/recording WORD the smallest interval or recording all
time the time
1: save;
5 Save sign BYTE
0: real-time upload
0x01:320*240;
0x02:640*480;
0x03:800*600;
0x04:1024*768;
6 Resolution BYTE
0x05:176*144;[Qcif];
0x06:352*288;[Cif];
0x07:704*288;[HALF D1];
0x08:704*576;[D1];
1-10, 1 means the least quality loss, 10
7 Image/Video Quality BYTE
means the most compression ratio
8 Brightness BYTE 0-255
9 Contrast BYTE 0-127
10 Saturation BYTE 0-127
11 Chroma BYTE 0-255
If the terminal does not support the resolution required by the system, take the closest
resolution to shoot and upload

6.55 The Camera Immediately Shoots Command

Message ID: 0x0805.

See Table 84 for the body data format of the camera immediate shooting
command response message body. This command is used to answer the

camera immediate shooting command 0x8801 issued by the monitoring

center.
Table 84: The body data format of the camera immediate shooting command
response message body
Start Byte Field Type of Data Description
The message serial number
corresponding to the immediate
0 Reply serial number WORD
shooting command of the platform
camera
0: success; 1: failure; 2: channel not
2 Result BYTE supported. The following fields are
only valid when result=0.
Number of n, the number of successful
3 WORD
multimedia IDs multimedia shoots
4 Multimedia ID List BYTE[4*n]

6.56 Stored Multimedia Data Retrieval

Message ID: 0x8802.

See Table 85 for the data format of the stored multimedia data retrieval

message body.

Note: Set the start time/end time to 00-00-00-00-00-00 without pressing the

time range.
Table 85: The data format of the stored multimedia data retrieval message body
Start Byte Field Type of Data Description
0 Multimedia Type BYTE 0: Image; 1: Audio; 2: Video;
0 means to retrieve all channels of this
1 Channel ID BYTE
media type;
0: Command issued by the platform; 1:
Timed action; 2: Robbery alarm
2 Event Item Code BYTE
triggered; 3: Collision rollover alarm
triggered; others reserved
3 Start Time BCD[6] YY-MM-DD-hh-mm-ss
9 End Time BCD[6] YY-MM-DD-hh-mm-ss
6.57 Store Multimedia Data Retrieval Response

Message ID: 0x0802.

See Table 86 for the data format of the stored multimedia data retrieval

response message body.

Table 86: The data format of the stored multimedia data retrieval response message
body
Start Byte Field Type of Data Description
The serial number of the
0 Reply serial number WORD corresponding multimedia data
retrieval message
Total number of The total number of multimedia data
2 multimedia data WORD items that meet the retrieval
items conditions
See Table 87 for the data format of
4 Search term
multimedia search items

Table 87: The data format of multimedia search items

Start Byte Field Type of Data Description
0 Multimedia ID DWORD ＞0
4 Multimedia Type BYTE 0: Image; 1: Audio; 2: Video
5 Channel ID BYTE
0: Command issued by the platform; 1:
Timed action; 2: Robbery alarm
6 event item code BYTE
triggered; 3: Collision rollover alarm
triggered; others reserved
Location information Location basic information data
7 report (0x0200) BYTE[28] indicating the start time of shooting or
message body recording

6.58 Store Multimedia Data Upload Command

Message ID: 0x8803.

See Table 88 for the data format of the message body of the stored

multimedia data upload command.

 Table 88: The date format of the message body of the stored multimedia data
upload command
Start Byte Field Type of Data Description
0 Multimedia Type BYTE 0: Image; 1: Audio; 2: Video;
1 Channel ID BYTE
0: Command issued by the platform; 1:
Timed action; 2: Robbery alarm
2 Event Item Code BYTE
triggered; 3: Collision rollover alarm
triggered; others reserved
3 Start Time BCD[6] YY-MM-DD-hh-mm-ss
9 End Time BCD[6] YY-MM-DD-hh-mm-ss
15 Delete Flag BYTE 0: reserved; 1: deleted;

6.59 Recording Start Command

Message ID: 0x8804.

The data format of the recording start command message body is shown in

Table 89.
Table89: The data format of the recording start command message body
Start Byte Field Type of Data Description
0: stop recording; 0x01: start
0 Record command BYTE
recording;
The unit is second (s), 0 means
1 Record time WORD
recording all the time
3 Save flag BYTE 0: real-time upload; 1: save
0: 8K; 1: 11K; 2: 23K; 3: 32K; other
4 Audio sample rate BYTE
reserved

6.60 A Single Stored Multimedia Data Retrieval and Upload Command

Message ID: 0x8805.

See Table 90 for the message body data format of a single stored multimedia

data retrieval and upload command.

Table 90: The message body data format of a single stored multimedia data retrieval
and upload command
Start Byte Field Type of Data Description
0 Multimedia ID DWORD ＞0
4 Delete Flag BYTE 0: reserved; 1: deleted;

6.61 Data downlink transparent transmission

Message ID: 0x8900.

See Table 91 for the data format of the downlink transparent transmission

message body.
Table 91: The data format of the downlink transparent transmission message body
Start Byte Field Type of Data Description
Transparent See Table 93 for the definition of
0 BYTE
message type transparent message types
Transparent
1
message content

6.62 Data Uplink Transparent Transmission

Message ID: 0x0900.

See Table 92 for the data format of the data uplink transparent transmission

message body.
Table 92: The data format of the data uplink transparent transmission message body
Start Byte Field Type of Data Description
Transparent See Table 93 for the definition of
0 BYTE
message type transparent message types
Transparent
1
message content
 Table 93: The definition of transparent message types
Transparent Message Type Definition Description
GNSS module detailed
0x00 GNSS module detailed positioning data
positioning data
The upload message of the road transport
permit IC card information is 64Byte, and
the download message is 24Byte. The
Road Transport Permit IC
0x0B time-out time for the transparent
Card Information
transmission of the road transport permit IC
card authentication is 30s. After the
timeout, do not retransmit.
Serial port 1 transparent Serial port 1 transparently transmits
0x41
transmission messages
Serial port 2 transparent Serial port 2 transparently transmits
0x42
transmission messages
User-defined transparent
0xF0 - 0xFF User-defined transparent message
transmission

6.63 Data Compression Report

Message ID: 0x0901.

See Table 94 for the data format of the data compression report message

body.
Table 94: The data format of the data compression report message body
Start Byte Field Type of Data Description
Compressed
0 DWORD
message length
The compressed message body is the
Compressed
4 message that needs to be compressed
message body
after the GZIP compression algorithm

6.64 Platform RSA Public Key

Message ID: 0x8A00.

The data format of the platform RSA public key message body is shown in

Table 95.
 Table 95: The data format of the platform RSA public key message body
Start Byte Field Type of Data Description
0 e DWORD e in platform RSA public key {e,n}
4 n BYTE[128] n in RSA public key {e,n}

6.65 Terminal RSA Public Key

Message ID: 0x0A00.

The data format of the terminal RSA public key message body is shown in

Table 96.
Table 96: The data format of the terminal RSA public key message body
Start Byte Field Type of Data Description
0 e DWORD e in terminal RSA public key {e,n}
4 n BYTE[128] n in RSA public key {e,n}
 Appendix A
Vehicle Terminal and External Device Communication Protocol

A.1 Device

A1.1 Host Device

The host device shall comply with JT/T 794.

A1.2 Slave Device

The slave machine includes various point-to-point serial communication

peripheral devices, such as scheduling display screen, intelligent peripherals,

fuel quantity detection device, collision rollover detection device, etc.

A2 Communication Protocol

A2.1 Frame Format Definition

The frame format followed by all slave-master communication is shown in

Table A.1.
Table A.1: Frame format definition
Peripheral
Identification Check Version Manufacturer Command User Identification
Type
Bit Code Number Number Type Data Bit
Number
n
1 Byte 1 Byte 2 Byte 2 Byte 1 Byte 1 Byte 1 Byte
Byte

The contents of Table A.1 are explained as follows:

a) Identification bit: It is represented by 0x7e. If 0x7e appears in the check

code, message header and message body, it must be escaped. The escape

rules are defined as follows:

0x7e <————> 0x7d followed by a 0x02;

0x7d <————> 0x7d followed by a 0x01;

The escape process is as follows:

When sending a message: message encapsulation -> calculate and fill check

code -> escape;

When receiving a message: escape and restore --> verify the check code -->

parse the message;

Example 1:

Send a packet with the content of 0x30 0x7e 0x08 0x7d 0x55, then

encapsulate as follows: 0x7e 0x30 0x7d 0x020x08 0x7d 0x01 0x55 0x7e;

b) Check code: the accumulated sum from the manufacturer number to the

user data, and then take the accumulated lower 8 digits as the check code;

Example 2:

The accumulated sum is 0x1388, then the check code is 0x88;

c) Version number: identifies the version of the communication protocol;

d) Manufacturer number: the manufacturer code of the peripheral slave;

e) Peripheral type number: a unique type number corresponding to each

peripheral, which is used for the peripheral interface driver of the host to

distinguish what kind of data is sent by the peripheral; see Table A.2 for the

peripheral type number;

f) Command type: The type of information used by the peripheral and the

host for various data exchanges. The command type is divided into two

categories: general protocol and proprietary protocol: General protocol

mainly includes some basic, necessary, and common information interaction

types between the slave and the host. ; Proprietary protocol defines the

unique information interaction type between various peripherals and the host;

the command type is shown in Table A.3;

g) User data: refers to the content customized by specific business functions

in the data that the peripheral device interacts with the host except the above

parts;

h) The data of the communication frame adopts the big-endian

representation.
 Table A.2: Peripheral Type Number Table
Peripheral Type Number
Industry Information Terminal 0x01
Scheduling Display 0x02
Car Navigation Display 0x03
Fuel Level Detector 0x04
Acceleration Detector 0x05
Burglar Alarm 0x06
Interface Extender 0x07
Load Detector 0x08
Passenger Flow Detector 0x09
Universal Sensor 0x0A
Road Transport Permit IC Card Reader 0x0B
Customize 0xF0 - 0xFF

Table A.3: Command Type

Protocol Type Type of business function Command Type
Power-on
0x01
indication/response
Link Probe/Reply 0x02
Slave Power
0x03
Control/Response
Peripheral Common
Query slave version
Protocol 0x04
number information
Slave self-test/response 0x05
Slave firmware
0x06
update/answer
Reserve 0x07 - 0x3F
Road Transport Permit IC
Card Authentication 0x40
Request/Reply
Road transport license IC
card reading result 0x41
notification/response
Dedicated Protocol Card Pull
0x42
Notification/Answer
Active trigger to read IC
0x43
card/answer
Proprietary function
business protocol for 0x44 - 0xFF
various slave peripherals
A2.2 Addition Rules for Peripheral Protocols

The addition and modification of peripheral protocols should follow the

following rules:

a) The send and reply protocols of the same function use the same command

type;

b) For peripherals with many command types, when adding new command

types, try to use variable parameters to reduce the occupation of command

types.

A.3 General Protocol Description

A3.1 Slave Device Power-on Indication

See Table A.4 for the power-on instructions of the slave device.
Table A.4: Power-on Instructions of the slave device
Command
Step Description User Data Data Direction
Type
Power-on
1 01H indication No Down
response
Power-on
2 01H No Up
indication

A3.2 Peripheral Link Inquiry

See Table A.5 for peripheral link polling commands.

 Table A.5: Peripheral Link Polling Commands
Command Data
Step Description User Data
Type Direction
link maintenance time
The high-order byte is first, and the
low-order byte is last; the high-byte
unit is minutes (min), and the low-byte
1 02H Link Inquiry Up
unit is seconds (s); the recommended
link inquiry time is 15s-30s; after the
link times out, the host will Cancel the
registration information of the slave
Link Inquiry
2 02H No Down
Response

A3.3 Slave Device Power Control

See Table A.6 for slave device power control instructions.

Table A.6: Slave device power control instructions.
Command Data
Step Description User Data
Type Direction
Slave Control type:
device 0x00 - the slave exits the power saving
1 03H Down
power mode;
control 0x01 - Slave enters power saving mode
Reply Type:
Slave
0x01 - The operation is successful;
device
0x02 - Operation failed (slave cannot
2 03H power Up
enter power saving mode or exit
control
power saving mode due to special
response
circumstances)

A3.4 Query Slave Device Version Number Information

See Table A.7 for the command to query the slave device version number

information.
 Table A.7: The command to query the slave device version number information.
Command Data
Step Description User Data
Type Direction
Query the
slave
1 04H device No Down
version
number
Query the
slave
Slave version number, WORD
device
2 04H Such as: 0x0207, which means version Up
version
2.07
number
response

A3.5 Slave Device Self-check

See Table A.8 for slave device self-test instructions.

Table A.8: Slave device self-test instructions.
Command Data
Step Description User Data
Type Direction
Slave Device Self-test slave type, BYTE, as defined
1 05H Down
Self-check in Table A.2
Self-test slave type, BYTE, as defined
Self-check in Table A.2
2 05H result Self-test results, BYTE Up
information 0x01: Self-check succeeded; 0x02:
Self-check failed.
Note: The timeout time of this command is 1s. If there is no response, it will be
resent at most three times.
After receiving the failure of the self-test, the terminal will set the corresponding
alarm sign and give a voice prompt or screen display.

A3.6 Slave Device Firmware Update

Slave device firmware update instructions are shown in Table A.9.

 Table A.9: Slave device firmware update instructions
Command Data
Step Description User Data
Type Direction
Total number of message
packets, WORD
Update slave
Package serial number, WORD,
1 06H module Down
starting from 1
FirmWare
Packet data, with a maximum
length of 256 bytes
Package serial number, WORD
Response result, BYTE
0: correct;
Confirm
2 06H 1: Non-this firmware program, Up
information
terminate the upgrade;
2: Resend (after three times,
terminate this upgrade).
Note: The timeout time of this command is 1s. If there is no response, it will be
resent at most three times.

A3.7 Query Peripheral Properties

See Table A.10 for the command to query peripheral properties.

Table A.10: The command to query peripheral properties
Command Data
Step Description User Data
Type Direction
Query
1 07H peripheral No Down
properties
Peripheral Manufacturer Number, 5
Query BYTE
peripheral Peripheral hardware version number,
2 07H Up
properties 3 BYTE
response Peripheral software version number,
3 BYTE
Note: Example of version number, 0x010B02 means v1.12.2.
The timeout time of this command is 1s. If there is no response, it will be resent at
most three times.
A.4 Dedicated Protocol Description

A4.1 Road Transport Permit IC Card Authentication Request

When the module detects that a card is inserted, and after the module is reset

or powered on again, and the physical card number of the IC card in the card

slot is inconsistent with the last read card number, it will automatically trigger

the road transport permit IC card authentication request uplink command.

See Table A.11 for the request instruction for the IC card authentication of the

road transport permit.

Table A.11: The request instruction for the IC card authentication of the road
transport permit.
Command Data
Step Description User Data
Type Direction
Status bits, BYTE,
0x00: IC card reading is successful;
0x01: IC card is not inserted;
0x02: IC card reading failed;
IC card
0x03: IC card of non-practice
1 40H authenticati Up
qualification certificate;
on request
0x04: IC card is locked.
Data area (valid when status bit =
0x00), card basic information and
authentication information (64 bytes)
IC card authentication request
response result, BYTE
0x00: The authentication request was
successfully completed;
IC card 0x01: The terminal is not online;
authenticati 0x02: The terminal transparent
2 40H Up
on request transmission authentication center
response times out and no response;
0x03: The terminal confirms receipt
of the information (When IC card
authentication request card reading
result = 0x01-0x04).
 Data area (valid when IC card
authentication request response
result = 0x00), IC card authentication
request returns verification data (24
bytes).
Note: When the command goes up and the IC card authentication request status bit
is 0x00, the timeout period is 35S. In other states and downlink, the timeout period
is 1s. If there is no response, it will be resent three times at most.

A. When the status bit is 0x00, the terminal sends 64 bytes of card basic

information and authentication information to the authentication center, and

returns 1 or 25 bytes of result information to the card reader module

according to different situations.

a. When the IC card authentication request response result returned by the

terminal to the card reader module is 0x00, the card reader module starts to

read the card information, and then automatically starts the 41H command to

feed back the result to the terminal, and the terminal voice prompts the driver

with the corresponding result, and when the card is successfully read Then

use the 0x0702 command to send the driver's identity information to the

certification center and monitoring platform;

b. When the response result of the IC card authentication request returned by

the terminal to the card reader module is 0x01, wait for 20 minutes, and use

the 43H command to actively trigger the card reader module to read the IC

card;

c. When the IC card authentication request response result returned by the

terminal to the card reader module is 0x02, the card reader module resends

40H three times. After three unsuccessful attempts, the terminal ends the
process and voice prompts the driver with the corresponding result;

d. When the IC card authentication request response result returned by the

terminal to the card reader module is 0x03, the process ends, and the

terminal voice prompts the driver with the corresponding result.

B. When the status bit is not 0x00, the terminal ends the process and voice

prompts the driver with the corresponding result.

A4.2 Notification of the result of reading the IC card of the Road Transport

Permit

See Table A.12 for the notification instruction of the reading result of the IC

card of the road transport permit.

Table A.12: The notification instruction of the reading result of the IC card of the
road transport permit.
Command Data
Step Description User Data
Type Direction
IC card reading result, BYTE
0x00: The IC card is successfully read,
and there is follow-up data at this
time;
0x01: Card reading failed because the
card key authentication failed;
IC card
0x02: Card reading failed because the
reading
1 41H card has been locked; Up
result
0x03: Card reading failed because the
notification
card was pulled out;
0x04: Card reading failed due to data
verification error.
Data area (valid when the IC card
read result is 0x00), driver identity
information, see Table A.13.
2 41H The driver's No Down
 identity
information
is confirmed
Note: The timeout time of this command is 1s. If there is no response, it will be
resent at most three times.

A. When the terminal receives the IC card reading result of 0x00, it uses the

0x0702 command to send the driver's identity information to the certification

center and the home platform;

B. When the terminal receives an IC card reading result other than 0x00, it

ends the process and voice prompts the driver with the corresponding result.

Table A.13: Driver identity information

Start Byte Field Type of Data Description
0 Driver's name length BYTE Length is n
1 Driver's name STRING Driver's name
Qualification
1+n STRING 20 digits long
certificate number
The length of the
21+n name of the issuing BYTE length is m
authority
The name of the certificate-issuing
22+n Issuing agency name STRING
institution
22+n+m Certificate validity BCD[4] YYYYMMDD

A4.3 Card Removal Notification

Refer to Table A.14 for the card pullout notification instructions.

Table A.14: The card pullout notification instructions
Command Data
Step Description User Data
Type Direction
1 42H Card removal notification No Up
Card removal notification
2 42H No Down
received confirmation
Note: The timeout time of this command is 1s. If there is no response, it will be
resent at most three times.

When the terminal receives the card pullout notification, it uses the 0x0702

command to send the driver's off-duty information to the certification center

and monitoring platform.

A4.4 Active trigger to read IC card

See Table A.15 for the command to actively trigger reading the IC card.
Table A.15: The command to actively trigger reading the IC card
Command Data
Step Description User Data
Type Direction
1 43H Active trigger to read IC card No Down
Active trigger to read IC card
2 43H No Up
received confirmation
Note: The timeout time of this command is 1s. If there is no response, it will be
resent at most three times.

This command is used for terminal roll call, terminal is offline, or the terminal

uploads IC card authentication information overtime, etc. After the card

reader module receives this command, it will automatically trigger the 40H

command to re-read the card.

 Appendix B
Message Comparison Table

See Table B.1 for the message comparison table of the terminal

communication protocol.

Table B.1: The message comparison table

Message Message
No Message Name No Message Name
ID ID
Terminal general
1 0x0001 35 Set circular area 0x8600
response
2 Platform general response 0x8001 36 Delete circular area 0x8601
3 Terminal Heratbeat 0x0002 37 Set rectangular area 0x8602
Retransmission
4 0x8003 38 Delete rectangular area 0x8603
sub-packaging request
5 Terminal register 0x0100 39 Set polygon area 0x8604
6 Terminal Register response 0x8100 40 Delete polygon area 0x8605
7 Terminal logout 0x0003 41 Set route 0x8606
8 Terminal authentication 0x0102 42 Delete route 0x8607
Drive recorder data
9 Set terminal parameter 0x8103 43 0x8700
collection command
Drive recorder data
10 Query terminal parameter 0x8104 44 0x0700
upload
Query terminal parameter Drive recorder parameter
11 0x0104 45 0x8701
response download command
12 Terminal control 0x8105 46 E-Waybill Reporting 0x0701
Query specified terminal Collect and report driver
13 0x8106 47 0x0702
parameter identity information
Report driver
14 Query terminal properties 0x8107 48 identification information 0x8702
request
Query terminal properties Bulk upload of
15 0x0107 49 0x0704
response positioning data
Issue terminal upgrade
16 0x8108 50 CAN bus data upload 0x0705
package
Terminal upgrade result Multimedia event
17 0x0108 51 0x0800
notification information upload
Location information
18 0x0200 52 Multimedia data upload 0x0801
report
 Location information Multimedia data upload
19 0x8201 53 0x8800
query response
Location information The camera shoots the
20 0x0201 54 0x8801
query response command immediately
The camera immediately
Temporary position
21 0x8202 55 shoots the command 0x0805
tracking control
response
Manual acknowledgment Stored multimedia data
22 0x8203 56 0x8802
of alarm messages retrieval
Stored multimedia data
23 Text message delivery 0x8300 57 0x0802
retrieval response
Stored multimedia data
24 Event Setting 0x8301 58 0x8803
upload
25 Event Report 0x0301 59 Recording start command 0x8804
Single stored multimedia
26 Issue a question 0x8302 60 data retrieval and upload 0x8805
command
Data downlink
27 Question response 0x0302 61 0x8900
transparent transmission
Information on demand Data uplink transparent
28 0x8303 62 0x0900
menu settings transmission
Information on
29 0x0303 63 Data compression report 0x0901
demand/cancellation
30 Information Service 0x8304 64 Platform RSA public key 0x8A00
31 Phone call back 0x8400 65 Terminal RSA public key 0x0A00
Platform downlink 0x8F00 ~
32 Set phone book 0x8401 66
message retention 0x8FFF
Platform uplink message 0x0F00 ~
33 Vehicle control 0x8500 67
retention 0x0FFF
34 Vehicle control response 0x0500