JT/T 808-2019_English: PDF (JT/T808-2019)
Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
JT/T 808-2019 | English | 605 |
Add to Cart
|
0--9 seconds. Auto-delivery
|
[Including 2021XG] GNSS for operating vehicles. General specifications for vehicle terminal communication protocol and data format
| Valid |
JT/T 808-2019
|
JT/T 808-2011 | English | 150 |
Add to Cart
|
0--9 seconds. Auto-delivery
|
GNSS system for operational vehicles. General specifications for vehicle terminal communication protocol and data format
| Obsolete |
JT/T 808-2011
|
Standard ID | JT/T 808-2019 (JT/T808-2019) | Description (Translated English) | GNSS for operating vehicles. General specifications for vehicle terminal communication protocol and data format | Sector / Industry | Highway & Transportation Industry Standard (Recommended) | Classification of Chinese Standard | M53 | Classification of International Standard | 03.220.20; 35.240.60 | Word Count Estimation | 56,526 | Date of Issue | 2019-03-15 | Date of Implementation | 2019-07-01 | Summary | This standard specifies the communication protocol and data format between the on-board terminal of the road transport vehicle satellite positioning system and the supervision/monitoring platform, including protocol basis, communication connection, message processing, protocol classification and requirements and data format. This standard applies to the communication between the on-board terminal of the satellite positioning system of the road transport vehicle and the supervision/monitoring platform. | Standard ID | JT/T 808-2011 (JT/T808-2011) | Description (Translated English) | GNSS system for operational vehicles. General specifications for vehicle terminal communication protocol and data format | Sector / Industry | Highway & Transportation Industry Standard (Recommended) | Classification of Chinese Standard | M53 | Classification of International Standard | 03.220.20; 35.240.60 | Word Count Estimation | 41,475 | Date of Issue | 2011-05-23 | Date of Implementation | 2011-08-01 | Quoted Standard | GB/T 2260; GB/T 19056; JT/T 415-2006; JT/T 794 | Drafting Organization | Fujian Provincial Department of Transportation | Administrative Organization | National Standardization Technical Committee of road transport | Regulation (derived from) | Ministry of Transport Notice No. 28 of 2011 | Summary | This standard specifies the road transport vehicle satellite positioning system vehicle terminal (hereinafter referred to as the terminal) and regulatory/monitoring platform (hereinafter referred to as platform) and the communication protocol between data formats, including protocol based communication connection, message processing, protocol classification and description and data formats. This standard applies to road transport vehicle satellite positioning system vehicle for communication between terminals and platforms. |
JT/T 808-2019
JT
TRANSPORT INDUSTRY STANDARD
OF THE PEOPLE’S REPUBLIC OF CHINA
ICS 03.220.20; 35.240.60
M 53
Filing No.:
Replacing JT/T 808-2011
GNSS for operating vehicles - General specifications for
vehicle terminal communication protocol and data format
[Including Amendment No.1 2021XG1]
ISSUED ON: MARCH 15, 2019
IMPLEMENTED ON: JULY 01, 2019
Issued by: Ministry of Transport of PRC
Table of Contents
Foreword ... 3
1 Scope ... 6
2 Normative references ... 6
3 Terms and definitions, abbreviations ... 6
4 Protocol basics ... 9
5 Communication connection ... 12
6 Message processing ... 13
7 Protocol classification and requirements ... 14
8 Data format ... 19
Appendix A (Normative) Communication protocol between on-board terminal
and external equipment ... 56
Appendix B (Normative) Message comparisons ... 64
Amendment No.1 ... 66
GNSS for operating vehicles - General specifications for
vehicle terminal communication protocol and data format
1 Scope
This standard specifies the communication protocol and data format, between the on-
board terminal of the satellite positioning system of road transport vehicles and the
monitoring/monitoring platform, including protocol basis, communication connection,
message processing, protocol classification and requirements, data format.
This standard applies to the communication -- between the on-board terminal of the
satellite positioning system of road transport vehicles and the supervision/monitoring
platform.
2 Normative references
The following documents are essential to the application of this document. For the dated
documents, only the versions with the dates indicated are applicable to this document;
for the undated documents, only the latest version (including all the amendments) is
applicable to this standard.
GB/T 2260 Codes for the administrative divisions of the Peoples Republic of China
GB/T 19056 Vehicle travelling data recorder
JT/T 697.7-2014 Basic data element of transportation information - Part 7: Basic
data element of road transportation information
JT/T 794 GNSS system for operating vehicles - Technical specification for vehicle
terminals
3 Terms and definitions, abbreviations
3.1 Terms and definitions
The following terms and definitions apply to this document.
3.1.1
Abnormal data communication link
The format and content of each different command message body is determined by each
command, see Chapter 7 for specific requirements.
4.4.5 Check code
The calculation rule of the check code shall start from the first byte of the message
header, XOR operation with the next byte, until the end of the last byte of the message
body; the length of the check code is one byte.
5 Communication connection
5.1 Connection establishment
The daily data connection -- between the terminal and the platform -- can use TCP or
UDP. After the terminal is reset, it shall establish a connection with the platform. After
the connection is established, it will immediately send a terminal authentication
message to the platform, for authentication.
5.2 Maintenance of connection
After the connection is established and the terminal authentication is successful, the
terminal shall periodically send a terminal heartbeat message to the platform; the
platform will send a platform general response message to the terminal, after receiving
it; the sending period is specified by the terminal parameters.
5.3 Disconnection of connection
Both the platform and the terminal shall actively determine whether the connection is
disconnected.
The platform shall use the following methods, to determine whether the terminal
connection is disconnected:
- In the TCP connection mode, judge the active disconnection according to the TCP
protocol;
- A terminal with the same identity establishes a new connection, indicating that the
original connection has been disconnected;
- No message from the terminal is received, within a certain period of time.
The terminal shall use the following methods, to determine whether the connection is
disconnected:
- In the TCP connection mode, it is judged that the platform is actively disconnected
according to the TCP protocol;
When the terminal communication mode is switched to the SMS message mode, the
PDU eight-bit encoding method shall be adopted. For messages with a length exceeding
140 bytes, sub-packaging processing shall be carried out, according to the SMS service
plan.
The response, retransmission, storage mechanism of SMS messages shall meet the
requirements of 6.1. Response timeout time and number of retransmission shall be
processed, according to the relevant setting values of parameter ID0x0006 and 0x0007,
in Table 13.
7 Protocol classification and requirements
7.1 Classification
Protocols are described in functional categories. If not specified, the TCP
communication mode is used by default. See Appendix A, for the communication
protocol between the onboard terminal and the external device. See Appendix B, for the
message comparison between message names and message IDs in the protocol.
7.2 Terminal management protocol
7.2.1 Terminal registration/deregistration
When the terminal is in the unregistered state, it shall register first. After the registration
is successful, the terminal obtains the authentication code and saves it. The
authentication code can be used, when the terminal is authenticated. Before the vehicle
removes or replaces the terminal, the terminal shall perform a logout operation, to
cancel the corresponding relationship between the terminal and the vehicle.
If the terminal chooses to send terminal registration and terminal deregistration
messages, through SMS, the platform shall send a terminal registration response
through SMS, to reply to terminal registration, meanwhile send a platform general
response through SMS, to reply to terminal deregistration.
7.2.2 Terminal authentication
Registered terminals shall be authenticated, immediately after establishing a connection
with the platform. The terminal shall not send other messages, before the authentication
is successful.
The terminal shall perform authentication by sending a terminal authentication message;
the platform shall reply with a general response message of the terminal.
7.2.3 Set/query of terminal parameters
The platform sets terminal parameters, by sending a terminal parameter setting message;
the terminal replies with a general terminal response message. The platform inquires
terminal parameters, by sending an inquiry terminal parameter message; the terminal
replies with an inquiry terminal parameter response message. Terminals under different
network standards shall support some unique parameters of their respective networks.
7.2.4 Terminal control
The platform controls the terminal, by sending a terminal control message; the terminal
replies with a general terminal response message.
7.3 Position and alarm protocol
7.3.1 Position information report
The terminal periodically sends location information report messages, according to
parameter settings.
According to the parameter control, the terminal can send a position information report
message, when it judges that the vehicle is turning.
7.3.2 Location information query
The platform queries the current location information of the specified vehicle terminal,
by sending a location information query message; the terminal replies with a location
information query response message.
7.3.3 Temporary position tracking control
The platform starts/stops location tracking, by sending a temporary location tracking
control message. The location tracking requires the terminal to report periodically
before stopping, meanwhile report at the time interval specified by the message. The
terminal replies with a general terminal response message.
7.3.4 Terminal alarm
When the terminal judges that the alarm condition is met, it sends a location information
report message; 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 location information report message body.
If the alarm sign is maintained, until the alarm condition is released, the position
information report message shall be sent, immediately after the alarm condition is
released, meanwhile the corresponding alarm flag shall be cleared.
7.4 Information protocol
7.4.1 Sending text information
7.5.1 Callback
The platform requires the terminal to call back the phone, according to the specified
phone number, by sending a call back message; specify whether to follow the
monitoring mode. When calling back, the terminal shall not turn on the loudspeaker.
The callback message requires the terminal to reply with a general terminal response
message.
7.5.2 Setting phonebook
The platform sets the phonebook for the terminal, by sending a set phonebook message,
which requires the terminal to reply with a general terminal response message.
7.6 Vehicle control protocol
The platform requires the terminal to control the vehicle, according to the specified
operation, by sending the vehicle control message. After receiving it, the terminal shall
immediately reply with a general terminal response message. After replying to the
general response message, the terminal shall control the vehicle; then reply the vehicle
control response message, according to the result.
7.7 Vehicle management protocols
The platform sets the area and route of the terminal, by sending messages such as setting
circular area, rectangular area, polygonal area and route. The terminal judges whether
the alarm condition is met, according to the area and line attributes. Alarms include
speeding alarms, access area or route alarms, as well as insufficient or too long road
segment travel time alarms. The terminal shall include corresponding additional
location information, in the location information report message.
The value range of area or route ID is 1 ~ 0xFFFFFFFF. If the set ID is the same as the
same type of area or route ID, which is already in the terminal, update the area or route
data corresponding to this ID.
The platform can also delete the areas and routes, which are saved on the terminal, by
deleting messages such as circular areas, rectangular areas, polygonal areas, routes.
To set/delete area and route messages, the terminal needs to reply with a general
terminal response message.
7.8 Information collection protocol
7.8.1 Collection of driver identity information data
The terminal collects the driver's identity information data, uploads it to the platform
for identification; the platform responds with a message of success or failure.
7.8.2 Collection of electronic waybill data
The terminal collects the electronic waybill data and uploads it to the platform.
7.8.3 Collection of driving record data
The platform requires the terminal to upload the specified data, by sending a driving
record data collection command message. This message requires the terminal to reply
to the driving record data upload message.
7.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. This message requires the terminal to
reply with a general terminal response message.
7.9 Multimedia protocol
7.9.1 Upload of multimedia event information
When the terminal actively takes pictures or records, due to a specific event, it shall
actively upload the multimedia event message, after the event occurs. This message
requires the platform to reply with a general reply message.
7.9.2 Upload of multimedia data
The terminal sends a multimedia data upload message, to upload the multimedia data.
Before each complete multimedia data, the position information report message body
when recording shall be added, that is, the position multimedia data. The platform
determines the receiving timeout time, based on the total number of packets. After
receiving all data packets or reaching the timeout time, the platform sends a multimedia
data upload response message to the terminal; such message confirms receipt of all data
packets or requires the terminal to retransmit the specified data packets.
7.9.3 Immediate shooting of camera
The platform issues a shooting command to the terminal, by sending the camera
immediate shooting command message, which requires the terminal to reply with a
general terminal response message. If real-time upload is specified, the camera image
or video shall be uploaded in real time, after shooting by the terminal; otherwise, the
image or video shall be stored.
7.9.4 Startup of recording
The platform issues a recording command to the terminal, by sending a recording start
command message, which requires the terminal to reply with a general terminal
response message. If real-time upload is specified, the terminal shall upload the audio
data after recording; otherwise, it will store the audio data.
7.9.5 Retrieval and access of terminal storage multimedia data
The platform obtains the terminal's storage of multimedia data, by sending a stored
multimedia data retrieval message, which requires the terminal to reply with a stored
multimedia data retrieval response message.
According to the retrieval results, 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 with a general response message of the terminal.
7.10 General data transmission category
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, for uplink and downlink data exchange.
For longer messages, the terminal can use the GZIP compression algorithm to compress
the data; meanwhile upload the message in the form of data compression reporting.
7.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; the terminal replies with
the terminal RSA public key message, and vice versa.
8 Data format
8.1 Terminal's general response
Message ID: 0x0001.
The data format of the general response message body of the terminal is as shown in
Table 4.
8.2 Platform's general response
Message ID: 0x8001.
The data format of the general response message body of the platform is as shown in
Table 5.
......
JT/T 808-2011
JT
TRANSPORT INDUSTRY STANDARD
OF THE PEOPLE’S REPUBLIC OF CHINA
ICS 03.220.20; 35.240.60
M 53
Record No.:
GNSS System for Operational Vehicles -
General Specifications for Vehicle Terminal
Communication protocol and Data Format
ISSUED ON: MAY 23, 2011
IMPLEMENTED ON: AUGUST 01, 2011
Issued by: Ministry of Transport of the People’s Republic of China
Table of Contents
Foreword ... 3
1 Scope ... 4
2 Normative References ... 4
3 Terms, Definitions and Abbreviations ... 4
4 Protocol Basis ... 6
5 Communication Connection ... 9
6 Message Processing ... 10
7 Protocol Classification and Description ... 11
8 Data Format ... 17
Appendix A (Normative) Communication Protocol between Vehicle Terminal
and External Equipment ... 45
Appendix B (Normative) Message Contrast List ... 49
GNSS System for Operational Vehicles -
General Specifications for Vehicle Terminal
Communication protocol and Data Format
1 Scope
This Standard specifies the communication protocol and data format BETWEEN
vehicle terminal (hereinafter referred to as terminal) of the GNSS system for
operational vehicles AND supervising/monitoring platform (hereinafter referred to as
platform); including protocol basis, communication connection, message processing,
protocol classification/description and data format.
This Standard is applicable to the communication BETWEEN the vehicle terminal of
GNSS system for operational vehicle AND the platform.
2 Normative References
The following documents are essential to the application of this document. For the
dated documents, only the versions with the dates indicated are applicable to this
document; for the undated documents, only the latest version (including all the
amendments) are applicable to this document.
GB/T 2260 Codes for the Administrative Divisions of the Peoples Republic of
China
GB/T 19056 Vehicle Traveling Data Recorder
JT/T 415-2006 Electronic Government Platform for Administration of Road
Transportation - Cataloguing and Coding Rules
JT/T 794 GNSS System for Operating Vehicles - Technical Specification for
Vehicle Terminals
3 Terms, Definitions and Abbreviations
3.1 Terms and definitions
For the purpose of this document, the following terms and definitions apply.
3.1.1 Abnormal data communication link
The wireless communication link is disconnected or temporarily suspended (such as
during a call).
3.1.2 Register
The terminal sends a message to the platform to inform it that it is installed on a certain
vehicle.
3.1.3 Deregister
The terminal sends a message to the platform to inform it that it is removed from the
vehicle where it is installed.
3.1.4 Authentication
When the terminal connects to the platform, it sends a message to the platform to
enable the platform to verify its identity.
3.1.5 Location reporting strategy
Fixed-time and fixed distance report; or a combination of both.
3.1.6 Location reporting program
The rules for the periodic reporting interval are determined according to the relevant
conditions.
3.1.7 Additional points report while turning
The terminal sends a location information and report message when it is determined
that the vehicle is turning. The sampling frequency is no less than 1Hz; the azimuth
change rate of the vehicle shall be no less than 15°/s, and last for at least 3s.
3.1.8 Answering strategy
The rules for the terminal to answer to the call automatically or manually.
3.1.9 SMS text alarm
When the terminal alarms, it sends the text message in SMS mode.
3.1.10 Event item
The event item is preset by the platform on the terminal; it consists of an even code
--- 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 terminal heartbeat, has not been
received within a certain period of time.
The terminal determines the method of disconnecting the TCP connection:
--- According to the TCP protocol, judge that the platform is actively disconnected;
--- Data communication link is disconnected;
--- The data communication is normal; no response has been received after the
number of retransmissions has been reached.
6 Message Processing
6.1 TCP and UDP message processing
6.1.1 Message actively sent by the platform
All the messages actively sent by the platform are required to be responded by the
terminal; the response can be divided into general response and special response,
which shall be determined by each specific functional protocol. After the sender waits
for the response to time out, resend the message. The response timeout period and
the number of retransmissions shall be specified by the platform parameters; the
calculation formula of the response timeout period after each retransmission is shown
in Formula (1):
Where:
TN+1 – response timeout period after each retransmission;
TN – previous response timeout period;
N – the number of retransmissions.
6.1.2 Message actively sent by the terminal
6.1.2.1 Normal data communication link
When the data communication link is normal, all the messages actively sent by the
terminal are required to be responded; the response can be divided into general
correspondence between the terminal and the vehicle.
If the terminal chooses to send the terminal registration/deregistration messages by
means of SMS, platform shall send a terminal registration response to reply to the
terminal registration through the SMS mode; send the platform general response to
reply the terminal deregistration through the SMS mode.
7.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 before the authentication succeeds.
The terminal authenticates by sending a terminal authentication message, and the
platform replies to the platform general response message.
7.2.3 Setting/Querying terminal parameters
The platform sets the terminal parameters by sending a setting terminal parameter
message, and the terminal replies to the terminal general response message. The
platform queries the terminal parameters by sending a query terminal parameter
message, and the terminal replies to the query terminal parameter response message.
Terminals in different network formats should support some unique parameters of their
respective networks.
7.2.4 Terminal control
The platform controls the terminal by sending a terminal control message, and the
terminal replies to the terminal general response message.
7.3 Location, Alarm Protocol
7.3.1 Location information report
The terminal periodically sends a location information report message according to the
parameter setting.
According to the parameter control, the terminal can send a location information report
message when it is determined that the vehicle is turning.
7.3.2 Location information query
The platform sends a location information query message to query the location
information of the specified vehicle terminal; the terminal replies to the location
information query response message.
7.3.3 Temporary location tracking control
The platform sets message through sending information on-demand menu; send the
information on-demand item list to the terminal for saving; the driver can select the on-
demand/cancel corresponding information service through the menu; after selection,
the terminal sends an information on-demand/cancel message to the platform.
After the information is on-demand, it shall receive information service messages from
the platform, such as news and weather forecasts, etc.
The information on-demand menu setting message requires the terminal to reply to
the terminal general response message.
For the information on-demand/cancel message, it requires the platform to reply to the
platform general response message.
For the information service message, it requires the terminal to reply to the terminal
general response message.
7.5 Telephone protocol
7.5.1 Telephone callback
The platform sends a call back message, asks the terminal to call back the phone
according to the specified phone number, and specifies whether to press the monitor
mode (the terminal does not turn on the speaker).
For the telephone callback message, it requires the terminal to reply to the terminal
general response message.
7.5.2 Setting the telephone book
The platform sets a phone book to the terminal by sending a set phone book message,
and the message requires the terminal to reply to the terminal universal response
message.
7.6 Vehicle control protocol
The platform requests the terminal to control the vehicle according to the specified
operation by sending a vehicle control message. The terminal responds to the terminal
general response message immediately upon receipt. The terminal then controls the
vehicle and returns a vehicle control response message based on the result.
7.7 Vehicle administration protocol
The platform sets the area and route for the terminal by sending a message such as
setting a circular area, setting a rectangular area, setting a polygonal area, and setting
a route. The terminal judges whether the alarm condition is met according to the area
and route attributes, and the alarm includes an overspeed alarm, an entry/exit
data. Attach the location information report message body during shooting in the front
of each complete multimedia data, 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, and the message
confirms that all the data packets are received or the terminal is required to retransmit
the specified data packet.
7.9.3 Camera shoots immediately
The platform issues a shooting command to the terminal by sending the camera
immediately-shooting command message; such message needs the terminal to reply
to the terminal general response message. If real-time upload is specified, the camera
image/video is uploaded after the terminal captures, otherwise the image/video is
stored.
7.9.4 Recording start
The platform issues a recording command to the terminal through sending recording
start command; such message needs the terminal to reply to the terminal general
response message. If real-time upload is specified, the terminal uploads audio data
after recording, otherwise the audio data is stored.
7.9.5 Retrieving terminals storage multimedia data and extraction
The platform obtains a situation in which the terminal stores the multimedia data by
transmitting the stored multimedia data retrieval message, and the message needs the
terminal to reply to the stored multimedia data retrieval response message.
According to the search result, the platform may send the stored multimedia data
upload message, and request the terminal to upload the specified multimedia data,
and the message needs the terminal to reply to the terminal universal response
message.
7.10 Conventional data transmission
The message that is not defined in the protocol but needs to be transmitted in actual
use can use the data uplink transparent transmission message and the data downlink
transparent transmission message to perform uplink and downlink data exchange.
The terminal can compress the longer message by using the GZIP compression
algorithm and upload the message by using the data compression report message.
7.11 Encryption protocol
If encrypted communication is required between the platform and the terminal, the RSA
0×0012 STRING Primary server wireless communication dial-up password
0×0013 STRING Primary server address, IP or domain name
0×0014 STRING Backup server APN, wireless communication dial-up access point
0×0015 STRING Backup server wireless communication dial-up username
0×0016 STRING Backup server wireless communication dial-up password
0×0017 STRING Backup server address, IP or domain name
0×0018 DWORD Server TCP port
0×0019 DWORD Server UDP port
0×001A~0×001F Reserved
0×0020 DWORD Location reporting strategy, 0: fixed-time report; 1: fixed-distance report; 2: both fixed-time and fixed-distance report
0×0021 DWORD
Location reporting program. 0: according to ACC state; 1: according to
log-in state and ACC state, firstly judge the log-in state, if it is logged-in,
the abide by the ACC state
0×0022 DWORD The driver is not logged in to report the time interval, in second (s) >0
0×0023~0×0026 DWORD Reserved
0×0027 DWORD Report the time interval during sleep, in second (s) >0
0×0028 DWORD Report the time interval during the emergency alarm, in second (s) >0
Table 11 – Continued
Parameter ID Data type Descriptions and requirements
0×0029 DWORD Default time reporting interval, in second (s), >0
0×002A~0×002B DWORD Reserved
0×002C DWORD Default distance reporting interval, in meter (m), >0
0×002D DWORD Reporting distance interval with driver not logged in, in meter (m), >0
0×002E DWORD Reporting distance interval during sleeping, in meter (m), >0
0×002F DWORD Reporting distance interval during emergency alarm, in meter (m), >0
0×0030 DWORD Angle of additional points report while turning, < 180
0×0031~0×003F Reserved
0×0040 STRING Monitoring platform telephone number
0×0041 STRING Reset telephone number; such telephone number can be used to dial to the terminal phone and reset the terminal
0×0042 STRING
Restore the exit-factory default telephone number; such telephone
number can be used to dial to the terminal phone and restore the exit-
factory settings
0×0043 STRING Monitoring platform SMS telephone number
0×0044 STRING Receive terminal SMS text alarm number
0×0045 DWORD Terminal call answering strategy, 0: auto answer; 1: auto answer during ACC ON, manual answer during ACC OFF
0×0046 DWORD Maximum talk time each time, in second (s); 0 indicates not allowed to talk; 0×FFFFFFFF indicates not limited
0×0047 DWORD Maximum talk time each month, in second (s); 0 indicates not allowed to talk; 0×FFFFFFFF indicates not limited
format can refer to
Table 15
separated by the half-width semicolon. Control commands are as
follows: “connection control; monitoring platform authentication code;
dial-up point name; dial-up username; dial-up password; address; TCP
port; UDP port; time limit for connecting to the specified server,” if certain
parameter has no value, empty it; if the connection control value is “1”,
then there is no subsequent parameter
3 No Terminal shutdown
4 No Terminal reset
5 No Terminal restores the exit-factory setting
6 No Turn off data communication
7 No Turn off all wireless communication
Table 15 – Command Parameter Format
Field Data type Descriptions and requirements
Connection control BYTE
0: switch to the specified monitoring platform server; enter into emergency
state after connecting to the server; in this state, only the monitoring platform
that issues the control command can send control commands including SMS;
1: switch to the original default monitoring platform server; and restore the
normal state
Dial-up point name STRING
Generally, it is a server APN, a wireless communication dial-up access point;
If the network standard is CDMA, the value is a PPP connection dialing
number
Dial-up username STRING Server wireless communication dial-up username
Dial-up password STRING Server wireless communication dial-up 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
Monitoring platform
authentication
code
STRING
Authentication code issued by the monitoring platform is only used for
authentication after terminal is connected to the monitoring platform; the
original authentication code is used for the terminal to connect back to the
original monitoring platform
Hardware version STRING Hardware version number of the terminal, self-defined by the manufacturer
Firmware version STRING Firmware version number of the terminal, self-defined by the manufacturer
URL address STRING Complete URL address
Time limit for
connecting to the
specified server
WORD
If the unit is minute (min), the value is not 0, it indicates the terminal shall
connect back to the original address before the expiration date after the
terminal receiving the command of upgrading or connecting to specified
server. If the value is 0, it indicates always connecting to the specified server
8.12 location information reporting
Message ID: 0×0200.
1: emergency alarm,
trigger after triggering the
alarm switch
Clear after receiving the response
1 1: overspeed alarm Maintain the flag until the alarm condition is released
2 1: fatigue driving Maintain the flag until the alarm condition is released
3 1: early-warning Clear after receiving a response
4 1: GNSS module failure Maintain the flag until the alarm condition is released
5 1: GNSS antenna is not connected or is cut Maintain the flag until the alarm condition is released
6 1: GNSS antenna short-circuit Maintain the flag until the alarm condition is released
7 1: Terminal mains undervoltage Maintain the flag until the alarm condition is released
8 1: Terminal mains power-fail Maintain the flag until the alarm condition is released
9 1: Terminal LCD or display failure Maintain the flag until the alarm condition is released
10 1: TTS module failure Maintain the flag until the alarm condition is released
11 1: camera failure Maintain the flag until the alarm condition is released
12~17 Reserved
18 1: accumulated driving timeout on the current day Maintain the flag until the alarm condition is released
19 1: timeout parking Maintain the flag until the alarm condition is released
20 1: access area Clear after receiving the response
21 1: access route Clear after receiving the response
22
1: Insufficient/excessive
driving time on the road-
section
Clear after receiving the response
23 1: Route deviation alarm Maintain the flag until the alarm condition is released
24 1: vehicle VSS failure Maintain the flag until the alarm condition is released
25 1: abnormal vehicle oil quantity Maintain the flag until the alarm condition is released
26 1: theft of the vehicle (via vehicle burglar alarm) Maintain the flag until the alarm condition is released
27 1: illegal ignition of vehicle Clear after receiving the response
28 1: illegal displacement of vehicle Clear after receiving the response
29 1: collision rollover alarm Maintain the flag until the alarm condition is released
30~31 Reserved
The format for location additional information item can refer to Table 19.
The data format for setting circular area message body can refer to Table 45.
NOTE: this message protocol supports the cycle time range; if the daily limit of 8:30 – 18:00 is
required; the start/end time is set to: 00-00-00-08-30-00/00-00-00-18-00-00, and so on.
Table 45 – Data Format for Setting Circular Area Message Body
Start byte Field Data type Descriptions and requirements
0 Setting attribute BYTE
0: update area;
1: add area;
2: modify area
1 The total number of areas BYTE
2 Area item Data format for circular area item content can refer to Table 46
Table 46 – Data Format for Circular Area Item Content
Start byte Field Data type Descriptions and requirements
0 Area ID DWORD
4 Area attribute WORD Definition of area attribute can refer to Table 47
6 Latitude of central point DWORD
Latitude value with degree as unit is multiplied by 106;
accurate to one millionth of a degree
10 Longitude of central point DWORD
Longitude value with degree as unit is multiplied by 106;
accurate to the one millionth of a degree
14 Radius DWORD In meter (m); the road-section is from such reflection point to the next reflection
18 Start time BCD [6] YY-MM-DD-hh-mm-ss; if the bit 0 of the area attribute is 0, there is no such field
24 End time BCD [6] YY-MM-DD-hh-mm-ss; if the bit 0 of the area attribute is 0, there is no such field
30 Maximum speed WORD
(km/h); if the bit 1 of the area attribute is 0, there is no
such field
32 Overspeed duration BYTE
In second (s) (similar description is modified as before); if
the bit 1 of the area attribute is 0, there is no such field
Table 47 – Definition of Area Attribute
Bit Flag Bit Flag
0 1: as per time 5 1: alarm to platform when leaving area
1 1: speed limit 6 0: north-latitude; 1: south-latitude
2 1: alarm to driver when entering into area 7 0: east-longitude; 1: west-longitude
3 1: alarm to platform when entering into area 8~15 Reserved
4 1: alarm to driver when leaving area
3 1: alarm to platform when entering route
Table 57 – Data Format for Route Inflection Point Item
Start
byte Field Data type Descriptions and requirements
0 Inflection point ID DWORD
4 Road-section ID DWORD
8 Inflection point latitude DWORD
The latitude value with degree as unit is multiplied by 106;
accurate to one millionth of a degree
12 Inflection point longitude DWORD
The longitude value with degree as unit is multiplied by
106; accurate to one millionth of a degree
16 Width of road-section BYTE
In meter (m); road-section indicates from one inflection
point to the next one
17 Attribute of road-section BYTE
Data format for road-section attribute can refer to Table
58
18
Threshold for too-
long driving on
road-section
WORD In second (s); if the bit 0 of road-section attribute is 0; there is no such filed
20
Threshold for
insufficient driving
on road-section
WORD In second (s); if the bit 0 of road-section attribute is 0; there is no such filed
22 Maximum speed on road-section WORD
In kilometer/hour (km/h); if the bit 1 of road-section
attribute is 0, there is no such field
24
Overspeed
duration time on
road-section
BYTE In second (s); if the bit 1 of road-section attribute is 0; there is no such filed
Table 58 – Data Format for Road-section Attribute
Bit Flag Bit Flag
0 1: driving time 3 0: east-longitude; 1: west-longitude
1 1: speed limit 4~7 Reserved
2 0: north-latitude; 1: south-latitude
8.35 Deleting route
Message ID: 0×8607.
The data format for deleting route message body can refer to Table 59.
Table 59 -- Data Format for Deleting Route Message Body
Start byte Field Data type Descriptions and requirements
0 The number of routes BYTE
The number of areas contained in this message is less
than 125; if it exceeds 125, it is suggested to use multiple
messages; 0 indicates deleting all rectangular areas
0 Channel ID BYTE >0
1 Shooting command WORD 0 indicates stop shooting; 0×FFFF indicates video recording; others indicate the number of photos
3 Photo interval/video recording time WORD
In second (s); 0 indicates taking photo at the
minimum interval or always video recording
5 Save flag BYTE 1: save; 0: upload in real time
6 Resolution a BYTE
7 Quality of image/video BYTE
1~10, 1 indicates minimum quality loss; 10 indicates
largest compression ratio
8 Brightness BYTE 0~255
9 Contrast BYTE 0~127
10 Saturation BYTE 0~127
11 Color BYTE 0~255
a If the terminal does not support the resolution required by the system, take the closest resolution to
upload it.
8.45 Storing multimedia data retrieval
Message ID: 0×8802.
The data format for storing multimedia data retrieval message body can refer to Table
69.
NOTE: If the time range is not abided by, the start/end time shall be set 00-00-00-00-00-00.
Table 69 -- Data Format for Storing Multimedia Data Retrieval Message Body
Start byte Field Data type Descriptions and requirements
0 Multimedia type BYTE 0: image; 1: audio; 2: video
1 Channel ID BYTE 0 indicates all channels that retrieve this media type
2 Event item encoding BYTE
0: platform issues command; 1: fixed-time action 2:
trigger robbery alarm; 3: trigger collision rollover alarm;
others reserved
3 Start time BCD [6] YY-MM-DD-hh-mm-ss
9 End time BCD [6] YY-MM-DD-hh-mm-ss
8.46 Storing multimedia data retrieval response
Message ID: 0×0802.
Message ID: 0×8804.
The data format for sound recording start command message body can refer to Table
73.
Table 73 – Data Format for Sound Recording Start Command Message Body
Start byte Field Data type Descriptions and requirements
0 Sound recording command BYTE 0: stop recording; 0×01 start recording
1 Sound recording time WORD In second (s); 0 indicates always sound recording
3 Storage flag BYTE 0: upload in real time; 1: storage
4 Audio sampling rate BYTE 0: 8K; 1: 11K; 2: 23K, 3: 32K; others reserved
8.49 Data downlink passthrough
Message ID: 0×8900.
The data format for data downlink passthrough message body can refer to Table 74.
Table 74 -- Data Format for Data Downlink Passthrough Message Body
Start byte Field Data type Descriptions and requirements
0 Passthrough message type BYTE
1 Passthrough message content
8.50 Data uplink passthrough
Message ID: 0×0900.
The data format for data uplink passthrough message body can refer to Table 75.
Table 75 – Data Format for Data Uplink Passthrough Message Body
Start byte Field Data type Descriptions and requirements
0 Passthrough message type BYTE
1 Passthrough message content
8.51 Data compression report
Message ID: 0×0901.
The data format for data compression report message body can refer to Table 76.
Table 76 -- Data Format for Data Compression Report Message Body
Start byte Field Data type Descriptions and requirements
0 Length of compression message DWORD
When receiving a message: escaping and restoring → verifying check code
→ parsing message.
Example 1:
Send a data package with contents of 0×30 0×7e 0×08 0×7d 0×55; after
encapsulating, it becomes: 0×7e 0×30 0×7d 0×02 0×08 0×7d 0×01 0×55 0×7e.
b) Check code: the accumulated-sum from the manufacturer-number to the user
data; then take the lower eight bits from the accumulated-sum as the check code.
Example 2:
The accumulated-sum is 0×1388; the check code is 0×88.
c) Version No.: identify the communication protocol version.
d) Manufacturer No.: Manufacturer No. of the external device.
e) External type No.: each type of external accessory has a unique type No., which
is used for the external accessory interface driver of the host to distinguish the
data sent from which external; the external accessory type No. can refer to Table
A.2.
f) Command type: information type for various data interaction between the external
accessory and the host; the command type is divided into general and special
protocols. The general protocol mainly includes the basic, necessary and
common information interaction type between the device and the host; while the
special protocol defines the special information interaction type between various
external accessories and the host. Command type can refer to Table A.3.
g) User data: the content of the data interacted by the external accessory and the
host, which is customized by the special business functions except for the above
parts.
h) The data of the communication frame is expressed by the big-endian.
Table A.2 – External Type Number-List
External accessory type S/N External accessory type S/N
Industry information terminal 0×01 Anti-theft alarm 0×06
Dispatch display 0×02 Interface extender 0×07
Vehicle navigation display 0×03 Load detector 0×08
Oil quantity detector 0×04 Passenger flow detector 0×09
Acceleration detector 0×05 Universal sensor 0×0A
......
|