JT/T 808-2019 PDF English
Search result: JT/T 808-2019_English: PDF (JT/T808-2019)
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Name of Chinese Standard | Status |
| 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-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 |
BUY with any currencies (Euro, JPY, GBP, KRW etc.): JT/T 808-2019 Related standards: JT/T 808-2019
PDF Preview: JT/T 808-2019
PDF Preview: JT/T 808-2011
JT/T 808-2019: PDF in English (JTT 808-2019) 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.
......
Source: Above contents are excerpted from the PDF -- translated/reviewed by: www.chinesestandard.net / Wayne Zheng et al.
|