标准编号:	JT/T 808-2019
中文名称:	道路运输车辆卫星定位系统 终端通讯协议及数据格式
英文名称:	GNSS system for operational vehicles. General specifications for vehicle terminal communication protocol and data format
中标分类:	M53    雷达、导航设备与系统
行业分类:	JT    交通行业标准
发布机构:	中华人民共和国交通运输部
发布日期:	2019-03-15
实施日期:	2019-7-1
标准状态:	superseded
被新标准替代:	JT/T 808-2019/XG1-2021 《道路运输车辆卫星定位系统 终端通信协议及数据格式》行业标准第1号修改单
替代旧标准:	JT/T 808-2011 道路运输车辆卫星定位系统 终端通讯协议及数据格式
翻译语言:	英文
文件格式:	PDF
中文字符数:	50000 字
翻译价格(元):	3200.0
交付时间:	付款后 1 个工作日

Codeofchina.com is in charge of this English translation. In case of any doubt about the English translation, the Chinese original shall be considered authoritative. This standard is developed in accordance with the rules given in G/T 1.1-2009. This standard replaces JT/T 808-2011 GNSS system for operational vehicles - General specifications for vehicle terminal communication protocol and data format. In addition to a number of editorial changes, the following main technical changes have been made with respect to JT/T 808-2011: ——The 14th bit of the message body attribute format of message header is modified to "version identity" (see 4.4.3; 4.4.3 of Edition 2011); ——The terminal phone number length in the message header is modified (see 4.4.3; 4.4.3 of Edition 2011); ——The server time query request is added (see 8.4); ——The additional points report request for terminal subpacket is added (see 8.7); ——The terminal model, terminal ID length and license plate format description of the register message are modified (see 8.8; 8.4 of Edition 2011); ——The manufacturer ID length and format definition of terminal register message as well as the reference standard for license plate color are modified (see 8.8; 8.8 of Edition 2011); ——The format of terminal authentication message is modified, and the software version number and IMEI number fields are added (see 8.11; 8.11 of Edition 2011); ——The definition of license plate color in terminal parameters setting is modified (see 8.12; 8.12 of Edition 2011); ——The parameter content of terminal parameters setting is modified (see 8.12; 8.12 of Edition 2011); ——The instruction of “specified terminal parameters query” is added (see 8.14); ——The instruction of “terminal attribute query” is added (see 8.16); ——The parameter description of controlling the terminal to connect to the designated server in the terminal control instruction are modified. Three control instructions, i.e., "terminal shutdown", “close data communication" and "close all wireless communication", are deleted. The data type description of wireless upgrade command removal command parameter is deleted, and the specific command parameter type is subject to the parameter type of the corresponding command word (see 8.16; 8.16 of Edition 2011); ——The requirements on event setting, event report, question issuing, question answering, information on-demand menu setting, information on-demand/cancellation and information service in the data format are deleted (see 8.17, 8.18, 8.19, 8.20, 8.21, 8.22 and 8.23 of Edition 2011); ——The instruction of “terminal upgrade patch issuing” is added (see 8.19); ——The requirements for the message of location information reporting are modified (see 8.21; 8.21 of Edition 2011); ——The instruction of “artificial acknowledgment alarm” is added (see 8.25); ——The instruction of “terminal link detection” is added (see 8.26); ——The requirements for text information issuance are modified (see 8.27; 8.27 of Edition 2011); ——The data format of vehicle control instruction is modified (see 8.30; 8.12 of Edition 2011); ——Definitions such as opening and closing door for the area attribute of circular area establishment instruction are added (see 8.32); ——The name fields for rectangular area establishment, circular area establishment, polygonal area establishment, route establishment, etc. are added (see 8.32~8.38); ——The message bodies “area or route data query response” are added (see 8.40); ——The field definition of data block for driving record data acquisition command is added (see 8.42); ——The request for reporting driver's identity information is added (see 8.46); ——The structure of driver's identity information acquisition and reporting message is modified (see 8.47; 8.47 of Edition 2011); ——The request for batch uploading of locating data is added (see 8.48); ——The request for CAN bus data uploading is added (see 8.49); ——The location information field for multimedia data uploading is added (see 8.51); ——The definitions of minimum resolution and maximum resolution of the command of immediate shooting for camera are added (see 8.53); ——The response to command of immediate shooting for camera is added (see 8.54); ——The data format of multimedia retrieval item for stored multimedia data retrieval response is added (see 8.56); ——The instruction for single stored multimedia data retrieval and uploading is added (see 8.59); ——The transparent transmission message type definition table of the transparent transmission message type description is added in the downlink data transparent transmission instruction (see 8.60); ——The transparent transmission message type description of the uplink data transparent transmission instruction is modified (see 8.61; 8.61 of Edition 2011); ——The peripheral type number table is modified, and the peripheral type of burglar alarm is added (see Table A.2); ——The command type table is modified, and the content of special protocol related to road transport certificate IC card and the content of peripheral self-test and firmware update are added (see Table A.3); ——The slave version number information query instruction is added (see A3.4); ——The slave self-test instruction is added (see A3.5); ——The slave firmware update instruction is added (see A3.6); ——The instruction for peripheral attribute query is added (see A3.7); ——The description of special protocol for IC card authentication is added (see A.4); ——The table for message comparison is modified, all newly added instructions are supplemented, and the scope of vendor defined uplink message and vendor defined downlink message is specified (see Annex B) This standard was proposed by and is under the jurisdiction of SAC/TC 521 National Technical Committee on Road Transport of Standardization Administration of China. The previous edition of this standard is as follows: ——JT/T 808-2011. 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 GNSS for operating vehicles and the supervision/monitoring platform, including protocol basis, communication connection, message processing, protocol classification and requirements, and data format. This standard is applicable to the communication between the on-board terminal of GNSS for operating vehicles and the supervision/monitoring platform. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. 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, definitions and abbreviations 3.1 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1.1 abnormal data communication link state in which the wireless communication link is disconnected or temporarily suspended (such as during a call) 3.1.2 register operation that a terminal sends a message to the platform to inform its installation on a certain vehicle 3.1.3 unregister operation that a terminal sends a message to the platform to inform its removal from the vehicle 3.1.4 authentication operation that a terminal sends a message to the platform at the time of being connected to the platform to enable the platform to verify its identity and at the same time reports the protocol version currently in use to communicate with the platform 3.1.5 location reporting strategy rules for reporting at regular time interval or certain distance or a combination of both 3.1.6 location reporting program rules for determining location reporting interval according to location reporting strategy 3.1.7 additional points report while turning rules for the terminal to send the location information reporting message when judging that the vehicle will turn. The sampling frequency shall not be less than 1Hz, and the change rate of vehicle azimuth angle shall not be less than 15°/s, and the sampling shall last at least more than 3s 3.1.8 answering strategy rules for the terminal to answer incoming calls automatically or manually 3.1.9 sms text alarm operation of sending text messages by SMS when the terminal alarms 3.1.10 multi-center connection strategy the terminal shall report the same data content to multiple central servers at the same time. For the downlink instruction operation of central servers, the terminal shall only respond to the downlink instruction of the primary server, but not to the downlink instruction of the secondary server 3.2 Abbreviations For the purposes of this document, the following abbreviations apply. ID——Identity APN——Access Point Name GZIP——a GNU free software file compression program (GNU zip) LCD——Liquid Crystal Display RSA——an asymmetric cryptography algorithm (developed by Ron Rivest, Adi Shamirh, and Len Adleman, named after them) SMS——Short Message Service TCP——Transmission Control Protocol TTS——Text To Speech UDP——User Datagram Protocol VSS——Vehicle Speed Sensor GNSS——Global Navigation Satellite System GBK——Chinese Internal Code Specification 4 Protocol basis 4.1 Communication mode The communication mode adopted in the protocol shall meet the relevant requirements in JT/T 794. The communication protocol adopts TCP or UDP, with the supervision/monitoring platform (hereinafter referred to as "platform") as the server side and the on-board terminal of GNSS for operating vehicles (hereinafter referred to as "terminal") as the client side. In case of an abnormal data communication link, the terminal may communicate via SMS message. 4.2 Data type See Table 1 for data types used in protocol messages. Table 1 Data types Data type Description and requirement BYTE Unsigned single-byte integer (byte, 8 bits) WORD Unsigned double-byte integer (byte, 16 bits) DWORD Unsigned four-byte integer (double word, 32 bits) BYTE[n] n bytes BCD[n] 8421 code, n bytes STRING GBK code. Null if there is no data 4.3 Transmission rules The protocol shall adopt the network byte order in big-endian mode to transmit word and double word. The transmission rules are agreed as follows: ——BYTE transmission, which is performed in the form of byte stream; ——WORD transmission, in which the high 8 bits are transmitted first, and then the low 8 bits are transmitted; ——DWORD transmission, in which the high 24 bits are transmitted first, then the high 16 bits, the high 8 bits, and finally the low 8 bits. 4.4 Message composition 4.4.1 Message structure Each message consists of identity bits, a message header, a message body and a check code, and the message structure is shown in Figure 1. Identity bit Message header Message body Check code Identity bit Figure 1 Message structure diagram 4.4.2 Identity bit The identity bit shall be represented by 0x7e, and if 0x7e and 0x7d appear in the check code, message header and message body, they shall be escaped. The escape rules are defined as follows: Firstly, 0x7d is escaped and converted into fixed two-byte data: 0x7d 0x01; Secondly, 0x7e is escaped and converted into fixed two-byte data: 0x7d 0x02. The escape process is as follows: When sending a message: first encapsulate the message, then calculate and fill in the check code, and finally escape it; When receiving a message: firstly escape and restore the message, then verify the check code, and finally parse the message. Example: When sending a data packet of 0x30 0x7e 0x08 0x7d 0x55, it is encapsulated as follows: 0x7e 0x30 0x7d 0x02 0x08 0x7d 0x01 0x55 0x7e.

Foreword II 1 Scope 2 Normative references 3 Terms, definitions and abbreviations 4 Protocol basis 5 Communication connection 6 Message processing 7 Protocol classification and requirements 8 Data format Annex A (Normative) Communication protocol between on-board terminal and external equipment Annex B (Normative) Table for message comparison

道路运输车辆卫星定位系统终端通信协议及数据格式 1范围 本标准规定了道路运输车辆卫星定位系统车载终端与监管/监控平台之间的通信协议与数据格式，包括协议基础、通信连接、消息处理、协议分类与要求及数据格式。 本标准适用于道路运输车辆卫星定位系统车载终端和监管/监控平台之间的通信。 2规范性引用文件 下列文件对于本文件的应用是必不可少的。凡是注日期的引用文件，仅注日期的版本适用于本文件。凡是不注日期的引用文件，其最新版本（包括所有的修改单）适用于本文件。 GB/T 2260 中华人民共和国行政区划代码 GB/T 19056 汽车行驶记录仪 JT/T 697.7-2014 交通信息基础数据元 第7部分：道路运输信息基础数据元 JT/T 794 道路运输车辆卫星定位系统 车载终端技术要求 3术语和定义、缩略语 3.1术语和定义 下列术语和定义适用于本文件。 3.1.1 数据通信链路异常abnormal data communication link 无线通信链路断开，或暂时挂起（如通话过程中）的状态。 3.1.2 注册register 终端向平台发送消息告知其安装在某一车辆上的操作。 3.1.3 注销unregister 终端向平台发送消息告知从所安装车辆拆下。 3.1.4 鉴权authentication 终端连接上平台时向平台发送消息以使平台验证自己身份，同时上报目前在用与平台通信的协议版本。 3.1.5 位置汇报策略location reporting strategy 定时、定距汇报或两者结合的规则。 3.1.6 位置汇报方案location reporting program 根据位置汇报策略确定位置汇报间隔的规则。 3.1.7 拐点补传additional points report while turning 终端在判断出车辆拐弯时发送位置信息汇报消息的规则。采样频率不低于1Hz，汽车方位角变化率不低于15°/s，且至少持续3s以上。 3.1.8 电话接听策略answering strategy 终端自动或手动接听来电的规则。 3.1.9 短信文本报警sms text alarm 终端报警时以短信方式发送文本信息的操作。 3.1.10 多中心连接策略multi-center connection strategy 终端应同时向多个中心服务器汇报相同的数据内容，对于中心服务器下行的指令操作，终端应只应答主服务器下行的指令，不可应答从服务器下行的指令。 3.2缩略语 下列缩略语适用于本文件。 ID——标识（Identity） APN——接入点名称（Access Point Name） GZIP——一个GNU自由软件的文件压缩程序（GNU zip） LCD——液晶显示屏（Liquid Crystal Display） RSA——一种非对称密码算法（由Ron Rivest、Adi Shamirh、Len Adleman开发，取名来自三者的名字） SMS——短消息服务（Short Message Service） TCP——传输控制协议（Transmission Control Protocol） TTS——文本到语音（Text To Speech） UDP——用户数据报协议（User Datagram Protocol） VSS——车辆速度传感器（Vehicle Speed Sensor） GNSS——全球导航卫星系统（Global Navigation Satellite System） GBK——汉字内码扩展规范（Chinese Internal Code Specification） 4协议基础 4.1通信方式 协议采用的通信方式应符合JT/T 794中的相关规定，通信协议采用TCP或UDP，监管/监控平台（以下简称“平台”）作为服务器端，道路运输车辆卫星定位系统车载终端（以下简称“终端"）作为客户端。当数据通信链路异常时，终端可采用SMS消息方式进行通信。 4.2数据类型 协议消息中使用的数据类型见表1。 表1数据类型 数据类型 描述及要求 BYTE 无符号单字节整型（字节，8位） WORD 无符号双字节整型（字节，16位） DWORD 无符号四字节整型（双字，32位） BYTE[n] n字节 BCD[n] 8421码，n字节 STRING GBK编码，若无数据，置空 4.3传输规则 协议应采用大端模式的网络字节序来传递字和双字。传输规则约定如下： ——字节（BYTE）的传输，按照字节流的方式传输； ——字（WORD）的传输，先传递高八位，再传递低八位； ——双字（DWORD）的传输，先传递高二十四位，然后传递高十六位，再传递高八位，最后传递低八位。 4.4消息的组成 4.4.1消息结构 每条消息由标识位、消息头、消息体和校验码组成，消息结构如图1所示。 标识位 消息头 消息体 校验码 标识位 图1消息结构图 4.4.2标识位 标识位应采用0x7e表示，若校验码、消息头以及消息体中出现0x7e及0x7d，则要进行转义处理。转义规则定义如下： 先对0x7d进行转义，转换为固定两字节数据：0x7d 0x01； 再对0x7e进行转义，转换为固定两字节数据：0x7d 0x02。 转义处理过程如下： 发送消息时：先对消息进行封装，然后计算并填充校验码，最后进行转义处理； 接收消息时：先对消息进行转义还原处理，然后验证校验码，最后解析消息。 示例：发送一包内容为0x30 0x7e 0x08 0x7d 0x55的数据包，则经过封装如下：0x7e 0x30 0x7d 0x02 0x08 0x7d 0x01 0x55 0x7e。 4.4.3消息头 4.4.3.1消息头内容详见表2。 4.4.3.2消息体属性格式结构如图2所示。 表2消息头内容 起始字节 字段 数据类型 描述及要求 0 消息ID WORD — 2 消息体属性 WORD 消息体属性格式结构见图2 4 协议版本号 BYTE 协议版本，每次关键修订递增，初始版本为1 5 终端手机号 BCD[10] 根据安装后终端自身的手机号转换。手机号不足位的，则在前补充数字0 15 消息流水号 WORD 按发送顺序从0开始循环累加 17 消息包封装项 — 如果消息体属性中相关标识位确定消息分包处理，则该项有内容，否则无该项 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 保留 版本标识 分包 数据加密方式 消息体长度 注：版本标识位的值固定为1。 图2消息体属性格式结构图 4.4.3.3数据应按照如下方式进行加密： ——bit10～bit12为数据加密标识位； ——当此三位都为0，表示消息体不加密； ——当第10位为1，表示消息体经过RSA算法加密； ——其他位为保留位。 4.4.3.4消息分包应按照如下要求进行处理： ——当消息体属性中第13位为1时表示消息体为长消息，进行分包发送处理，具体分包信息由消息包封装项决定； ——若第13位为0，则消息头中无消息包封装项字段。 消息包封装项内容见表3。 表3消息包封装项内容 起始字节 字段 数据类型 描述及要求 0 消息总包数 WORD 该消息分包后的总包数 2 包序号 WORD 从1开始 4.4.3.5版本标识应按照如下要求进行处理： ——当第14位为0，表示协议为2011年的版本，该版本未引入版本标识功能； ——当第14位为1，表示协议已经引入版本标识功能，并且在终端鉴权报文的鉴权码后跟随着协议版本号，引入版本标识功能后初始版本号为1，后续每次关键性修订版本号都会递增。 4.4.4消息体 每个不同的命令消息体格式内容由各命令确定，具体要求见第7章。 4.4.5校验码 校验码的计算规则应从消息头首字节开始，同后一字节进行异或操纵，直到消息体末字节结束；校验码长度为一字节。 5通信连接 5.1连接的建立 终端与平台的数据日常连接可采用TCP或UDP方式，终端复位后应与平台建立连接，连接建立后立即向平台发送终端鉴权消息进行鉴权。 5.2连接的维持 连接建立和终端鉴权成功后，终端应周期性地向平台发送终端心跳消息，平台收到后向终端发送平台通用应答消息，发送周期由终端参数指定。 5.3连接的断开 平台与终端双方都应主动判断连接是否断开。 平台应采用以下方法判断终端连接是否断开： ——在TCP连接模式下根据TCP协议判断主动断开； ——相同身份的终端建立新连接，表明原连接已断开； ——在一定的时间内未收到终端发出的消息。 终端应采用以下方法判断连接是否断开： ——在TCP连接模式下根据TCP协议判断出平台主动断开； ——达到重传次数后仍未收到应答。 6消息处理 6.1TCP和UDP消息处理. 6.1.1平台主发的消息 所有平台主发的消息均应要求终端应答。应答分为通用应答和专门应答两种方式，由各具体功能协议决定。发送方等待应答超时后，应对消息进行重发。应答超时时间和重传次数由平台参数指定，每次重传后的应答超时时间的计算方法见式（1）。 TN+1=TN×（N+1） （1） 式中：TN+1——每次重传后的应答超时时间，单位为s； TN——前一次的应答超时时间，单位为s； N——重传次数，单位为次。 6.1.2终端主发的消息 6.1.2.1数据通信链路正常 数据通信链路正常时，所有终端主发的消息均应要求平台应答。应答应分为通用应答和专门应答，由各具体功能协议决定。终端等待应答超时后，应对消息进行重发。应答超时时间和重传次数由终端参数指定，每次重传后的应答超时时间的计算方法见式（1）。对于终端发送的关键报警消息，若达到重传次数后仍未收到应答，则应对其进行保存。以后在发送其他消息前应先发送保存的关键报警消息。 6.1.2.2数据通信链路异常 数据通信链路异常时，终端应对需发送的位置信息汇报消息进行保存。在数据通信链路恢复正常后，应立即发送保存的消息。 6.2SMS消息处理 终端通信方式切换为SMS消息方式时，应采用PDU八位编码方式，对于长度超过140字节的消息，应按照短信服务规划进行分包处理。 SMS消息的应答、重传和保存机制应符合6.1的要求。应答超时时间及重传次数应按照表13中参数ID0x0006及0x0007的相关设定值处理。 7协议分类与要求 7.1分类 协议按照功能分类进行描述。无特别指明，缺省采用TCP通信方式。车载终端与外接设备通信协议见附录A。协议中消息名称与消息ID的消息对照表见附录B。 7.2终端管理类协议 7.2.1终端注册/注销 终端在未注册状态下，应首先进行注册，注册成功后终端获得鉴权码并进行保存，鉴权码可在终端鉴权时使用。车辆拆除或更换终端前，终端应执行注销操作，取消终端和车辆的对应关系。 如终端选择通过SMS方式发送终端注册和终端注销消息，平台应通过SMS方式发送终端注册应答对终端注册进行回复，通过SMS方式发送平台通用应答对终端注销进行回复。 7.2.2终端鉴权 已注册的终端，每次与平台建立连接后，应立即进行鉴权。鉴权成功前终端不应发送其他消息。 终端应通过发送终端鉴权消息进行鉴权，平台应回复终端通用应答消息。 7.2.3设置/查询终端参数 平台通过发送设置终端参数消息设置终端参数，终端回复终端通用应答消息。平台通过发送查询终端参数消息查询终端参数，终端回复查询终端参数应答消息。不同网络制式下的终端应支持各自网络的一些特有参数。 7.2.4终端控制 平台通过发送终端控制消息对终端进行控制，终端回复终端通用应答消息。 7.3位置、报警类协议 7.3.1位置信息汇报 终端根据参数设定周期性发送位置信息汇报消息。 根据参数控制，终端在判断出车辆拐弯时可发送位置信息汇报消息。 7.3.2位置信息查询 平台通过发送位置信息查询消息，查询指定车载终端当时位置信息，终端回复位置信息查询应答消息。 7.3.3临时位置跟踪控制 平台通过发送临时位置跟踪控制消息启动/停止位置跟踪，位置跟踪要求终端停止之前的周期汇报，按消息指定时间间隔进行汇报。终端回复终端通用应答消息。 7.3.4终端报警 终端判断满足报警条件时发送位置信息汇报消息，在位置汇报消息中设置相应的报警标志，平台可通过回复平台通用应答消息进行报警处理。 各报警类型见位置信息汇报消息体中的描述。报警标志维持至报警条件解除的报警，在报警条件解除后应立即发送位置信息汇报消息，清除相应的报警标志。 7.4信息类协议 7.4.1文本信息下发 平台通过发送文本信息下发消息，按指定方式通知驾驶员。终端回复终端通用应答消息。 7.4.2事件设置及报告 平台通过发送事件设置消息，将事件列表发到终端存储，驾驶员在遇到相应事件后可进入事件列表界面进行选择，选择后终端向平台发出事件报告消息。 对于事件设置消息，终端应回复终端通用应答消息。 对于事件报告消息，平台应回复平台通用应答消息。