Home Cart Quotation About-Us
www.ChineseStandard.net
SEARCH

GB/T 37987-2019 English PDF

US$1319.00 · In stock
Delivery: <= 10 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 37987-2019: Specifications for application interface of read-write equipment for the electronic identification of motor vehicles
Status: Valid
Standard IDUSDBUY PDFLead-DaysStandard Title (Description)Status
GB/T 37987-20191319 Add to Cart 10 days Specifications for application interface of read-write equipment for the electronic identification of motor vehicles Valid

Similar standards

GB/T 37736   GB/T 37735   GB/T 37740   GB/T 45346   GB/T 17554.1   

Basic data

Standard ID: GB/T 37987-2019 (GB/T37987-2019)
Description (Translated English): Specifications for application interface of read-write equipment for the electronic identification of motor vehicles
Sector / Industry: National Standard (Recommended)
Classification of Chinese Standard: L70
Classification of International Standard: 35.200
Word Count Estimation: 98,993
Date of Issue: 2019-08-30
Date of Implementation: 2020-03-01
Issuing agency(ies): State Administration for Market Regulation, China National Standardization Administration

GB/T 37987-2019: Specifications for application interface of read-write equipment for the electronic identification of motor vehicles


---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Specifications for application interface of read-write equipment for the electronic identification of motor vehicles ICS 35.200 L70 National Standards of People's Republic of China Specification for application interface of motor vehicle electronic identification reading and writing equipment 2019-08-30 released 2020-03-01 Implementation State Administration for Market Regulation Issued by China National Standardization Administration

Table of contents

Preface Ⅲ 1 Scope 1 2 Normative references 1 3 Terms and definitions 1 4 Abbreviations 2 5 General rules 2 5.1 Communication protocol 2 5.2 Interaction types, functional requirements and typical interaction processes 3 5.3 Exception handling 4 6 Messages, parameters and identifiers 4 6.1 Message classification and composition 4 6.2 Parameter classification and requirements 4 6.3 Identifier 5 7 Communication link monitoring 5 7.1 Link establishment response message 5 7.2 Heartbeat request message 5 7.3 Heartbeat response message 6 7.4 Link disconnection request message 6 7.5 Broken link response message 6 8 Read and write device operation rules management 6 8.1 Identification Rule 6 8.2 Access rules 10 9 Read and write device management 14 9.1 Device attribute query 14 9.2 Device activation 15 9.3 Configuration Management 17 9.4 Program version management 18 9.5 Device event notification message 21 9.6 Logo Operation Log Management 21 9.7 Device log management 23 9.8 Alarm Management 25 9.9 Diagnostic test 26 9.10 System Management 26 10 Data reporting 26 10.1 Data report message 26 10.2 Reporting historical data 27 Appendix A (informative appendix) Typical interaction process 28 Appendix B (Normative Appendix) Message Identifier and Identification Code 30 Appendix C (Normative Appendix) Parameter Data Type 33 Appendix D (Normative Appendix) Structural parameter identifiers and identification codes 35 Appendix E (Normative Appendix) Parameter content of structural parameters 39 Appendix F (Normative Appendix) Alarm Code 86 Appendix G (informative appendix) Typical example 87 References 91

Foreword

This standard was drafted in accordance with the rules given in GB/T 1.1-2009. Please note that certain contents of this document may involve patents. The issuing agency of this document is not responsible for identifying these patents. This standard was proposed and managed by the Ministry of Public Security of the People's Republic of China. Drafting organizations of this standard. Traffic Management Research Institute of the Ministry of Public Security, Wuxi Huatong Intelligent Transportation Technology Development Co., Ltd., Tianjin Zhongxingzhi Technology Co., Ltd., Zhejiang Dahua Technology Co., Ltd., Jiangsu Jinzhongtian IOT Technology Co., Ltd., Shenzhen Jinyi Technology Co., Ltd. The main drafters of this standard. Sun Zhengliang, Hu Jiabin, Liu Dongbo, Xu Minjie, Jiang Hu, Qi Tianyu, Shen Huiliang, Xu Qingli, Xu Genhua. Specification for application interface of motor vehicle electronic identification reading and writing equipment

1 Scope

This standard specifies the general provisions for interactive communication between the electronic identification reading and writing equipment of motor vehicles and other equipment or systems, messages, parameters and identification Symbols, communication link monitoring, read-write device operation rule management, read-write device management and data reporting. This standard applies to the design and development of electronic identification reading and writing equipment for motor vehicles.

2 Normative references

The following documents are indispensable for the application of this document. For dated reference documents, only the dated version applies to this article Pieces. For undated references, the latest version (including all amendments) applies to this document. GB/T 2659-2000 Codes for names of countries and regions in the world GB/T 29768 Information Technology Radio Frequency Identification 800/900MHz Air Interface Protocol GB/T 35786 General Specification for Reading and Writing Equipment of Motor Vehicle Electronic Identification GB/T 35789.1-2017 General Specification for Motor Vehicle Electronic Marking Part 1.Automobile GM/T 0024-2014 SSLVPN technical specifications

3 Terms and definitions

The following terms and definitions defined in GB/T 35786 and GB/T 35789.1 apply to this document. 3.1 news The smallest unit of information for interactive communication between a read-write device and other devices or systems. 3.2 parameter The message is composed of a specified data type and sequence, and is a data sequence used to convey information. 3.3 Identification rules The rules described by multiple sets of parameters that must be followed when the read-write device performs identification operations or read operations on the electronic identification of motor vehicles. 3.4 Access rules The rules described by multiple sets of parameters that must be followed when the read-write device reads or writes the designated electronic vehicle identification. 3.5 Identifier A mnemonic consisting of multiple characters used to identify a message or parameter.

4 Abbreviations

The following abbreviations apply to this document.

5 General rules

5.1 Communication protocol 5.1.1 Ethernet communication The communication protocol should meet the following requirements. a) Support TCP protocol, the default communication port number is 5084; b) Support the SSL application layer security communication protocol, which meets the requirements of Chapter 5 and Chapter 6 in GM/T 0024-2014; c) Support HTTP application layer communication protocol, use the POST method defined in 4.3.3 in RFC7231 to send messages, use RFC Encoding is performed in the Base64 encoding method defined in 6.8 in 2045. 5.1.2 Serial communication The communication protocol should meet the following requirements. a) The communication frame is composed of 6 parts. frame header, source address, destination address, message, check code and frame end. The structure is shown in Figure 1.Part symbols Meet the following requirements. 1) The frame header and frame end are hexadecimal data 0x7E; 2) The source address and destination address are represented by 1 byte respectively, which respectively identify the address code of the message sender and the address of the message receiver coding; 3) The message meets the requirements of 6.1; 4) Escape when the hexadecimal numbers 0x7E, 0x7D appear in the source address, destination address and message, the escape method is. 0x7E Use 0x7D, 0x5E instead, 0x7D use 0x7D, 0x5D instead; 5) The check code uses CRC16, the generator polynomial is x16 x15 x2, and the initial value is 0xFFFF. Generating checksum The verification range is the escaped source address, destination address and message data. If the hexadecimal number 0x7E appears in the check code, When 0x7D is escaped, see 4) for the escape method. b) When the communication interface is EIA-RS-232C, EIA-RS-485 interface, under default conditions. the communication bit rate is 19200bit/s, byte The structure is 8 data bits, 1 stop bit, no parity bit, and no flow control. Figure 1 Serial communication data frame 5.2 Interaction types, functional requirements and typical interaction procedures 5.2.1 Types of interaction The interaction between the read-write device and other devices or systems is divided into communication link monitoring, read-write device operation rule management, read-write device management and 4 types of data reporting. 5.2.2 Functional requirements 5.2.2.1 Communication link monitoring Communication link monitoring is used to establish and maintain communication links under Ethernet communication conditions. 5.2.2.2 Operation rule management of read-write equipment Read-write device operation rule management is used for the configuration and maintenance of identification rules and access rules, and realizes the addition and maintenance of identification rules and access rules. Query, delete and other operations. 5.2.2.3 Read and write device management The read-write device management is used for the query and configuration of the basic attribute parameters of the read-write device, the monitoring of the running status, and the management of the program version. 5.2.2.4 Data reporting Data reporting is used for reading and writing equipment to upload the electronic vehicle identification information read to other equipment or systems. 5.2.3 Typical interaction process See Appendix A for the typical interaction process. 5.3 Exception handling When both parties in communication receive a message that cannot be resolved, they should be discarded. 6 Messages, parameters and identifiers 6.1 Message classification and composition 6.1.1 Classification In the process of interactive communication between the read-write device and other devices or systems, messages are divided into non-response messages and response messages according to response modes. Message processing should meet the following requirements. a) If no response message is received, there is no need to feed back the processing result to the sender; b) If a response message is received, the response message is sent to the sender and the processing result is fed back. 6.1.2 Composition The message consists of a message header and a message body, and multi-byte data is transmitted in big-endian mode. Among them, the message header consists of the device serial number, version number, It consists of 5 parts. message code, message length, and message number. The message composition structure is shown in Figure 2, and each part should meet the following requirements. a) Device serial number. the serial number of the read-write device, the length is 64 bits, which can uniquely identify the identity of the read-write device. b) Version number. The version number of the interface specification of the read-write device, the length is 8 bits, and the fixed value is 0x01. c) Message code. the identification code of the message type, the length is 16 bits. See Appendix B for the definition of message identifier and identification code. d) Message length. the number of bytes of the message body content, the length is 32 bits. e) Message number. the sequence number of the message, the length is 32 bits, and the value starts from 1 for recycling. The message number and phase of the response message The corresponding request message has the same message number. f) Message body. It consists of one or more parameters, or it can be empty. 6.2 Parameter classification and requirements 6.2.1 Parameter classification Parameters are divided into three types. simple parameters, array parameters and structure parameters. 6.2.2 Requirements 6.2.2.1 Simple parameters Simple parameter. It is composed of one or more bits or bytes, and the data type is shown in Table C.1 in Appendix C. 6.2.2.2 Array parameters Array parameters. It is composed of array length and array content, and should meet the following requirements (see Table C.2 in Appendix C for data types). a) Array length. the number of simple parameters, the length is 32 bits; b) Array content. a set of simple parameters of the same data type. 6.2.2.3 Structural parameters Structure parameter. It consists of three parts. parameter code, parameter length and parameter content. For data types, see Table C.3.in Appendix C. Each part Meet the following requirements. a) Parameter code. the identification code of the parameter type, the length is 16 bits. Refer to Appendix D for the definition of parameter identifiers and identification codes. b) Parameter length. the number of bytes of the parameter content, the length is 32 bits. c) Parameter content. The specific value of the parameter is composed of one or more parameters. 6.3 Identifier Message and parameter identifiers should meet the following requirements. a) The identifier consists of uppercase letters, lowercase letters, numbers and special characters, and no spaces are allowed. Special characters include hyphens (_), asterisk (*) and plus sign () 3 types. b) The message identifier starts with the string "M_" prefix. c) Simple parameters and array parameters start with the string "D_" prefix. d) The structure parameter identifier starts with the string "P_" prefix.

7 Communication link monitoring

7.1 Link establishment response message The message identifier is M_ConnectionAck, the link establishment response message, and the message body content is shown in Table 1.When the Ethernet port is used, the communication parties Either party can establish a communication link according to the requirements of the TCP protocol. After the communication link is established, the reading and writing device should send this message to other devices or systems. Table 1 Message body content of link establishment response Serial number parameter identifier parameter data type parameter content 1 P_ConnectionAck P1 Link establishment response parameter. See Table E.1 in Appendix E 7.2 Heartbeat request message The message identifier is M_Keepalive, the heartbeat request message has no message body content. When the Ethernet port is used, the Send this message to other devices or systems at time t. Time t should be from 1s to the maximum random time set in Table E.2 (D_MaxTrig- gerValue) randomly generated within the value range. 7.3 Heartbeat response message The message identifier is M_KeepaliveAck, the heartbeat response message has no message body content. Other devices or systems receive the Send this message after the incoming heartbeat request message. When the heartbeat response message times out for 3 consecutive times, the communication link should be closed, and the Initiate a new connection or wait for the other party to initiate a connection again. 7.4 Link disconnection request message The message identifier is M_Disconnect, the disconnection request message, and there is no message body content. When either party needs to interrupt the communication link, Send this message. 7.5 Link broken response message The message identifier is M_DisconnectAck, the disconnection response message has no message body content. After receiving the disconnection request message, send to the other party Send this message to confirm that the communication link is closed. 8 Operation rule management of read-write equipment 8.1 Identification rules 8.1.1 Rule generation Other devices or systems send a request message for adding identification rules (M_AddSelectSpec), and the reading and writing device generates identification rules based on the request message. 8.1.2 Rule status The status of the recognition rule is divided into three types. disabled, ready, and enabled. When the recognition rules are initially generated, the status should be disabled or ready. 8.1.3 State transition The state transition of the recognition rule is shown in Figure 3.The state transition should meet the following requirements. a) The identification rule in the disabled state, the read-write device receives the activation identification rule request message from other devices or systems When requesting to activate the recognition rule, the recognition rule state jumps to the ready state. b) The recognition rules in the ready state can be changed in the following ways. 1) Other devices or systems send a request message for enabling identification rules (M_StartSelectSpec) to jump to the enabled state; 2) When the conditions specified by the recognition rule enable trigger parameter (P_SelectSpecStartTrigger) are met, it will automatically jump to the enabled state; 3) Other devices or systems send a request message (M_DisableSelectSpec) to disable the recognition rule and jump to the disabled state. c) The recognition rules in the enabled state can be converted in the following ways. 1) Other devices or systems send a stop recognition rule request message (M_StopSelectSpec) to jump to the ready state; 2) When the conditions specified by the recognition rule stop trigger parameter (P_SelectSpecStopTrigger) are met, it will automatically jump to the ready state; 3) Other devices or systems send a request message (M_DisableSelectSpec) to disable the recognition rule and jump to the disabled state. 8.1.4 Rule deletion The reader/writer device deletes the corresponding recognition rule after receiving the request message (M_DeleteSelectSpec) for deleting the recognition rule from other devices or systems. 8.1.5 Data reporting requirements When the reporting conditions set by the identification report rule parameter (P_SelectReportSpec) are met, the read-write device will report the address parameters according to the (P_ReportDestination) requires that the data be uploaded to other devices or systems through the designated communication link. 8.1.6 Message content 8.1.6.1 Add recognition rule request message The message identifier is M_AddSelectSpec, and the request message for adding identification rules is shown in Table 2. 8.1.6.2 Add recognition rule response message The message identifier is M_AddSelectSpecAck, add a recognition rule response message, and the content of the message body is shown in Table 3. Table 3 The content of the response message body for adding the recognition rule Serial number parameter identifier parameter data type parameter content 1 P_Status P1 Message response parameter, return message execution result, see Table E.25 in Appendix E 8.1.6.3 Delete identification rule request message The message identifier is M_DeleteSelectSpec, the delete identification rule request message, and the message body content is shown in Table 4. 8.1.6.4 Delete recognition rule response message The message identifier is M_DeleteSelectSpecAck, delete the recognition rule response message, and the message body content is shown in Table 5. 8.1.6.5 Enable identification rule request message The message identifier is M_StartSelectSpec, the request message for enabling identification rules, and the message body content is shown in Table 6. 8.1.6.6 Enable recognition rule response message The message identifier is M_StartSelectSpecAck, the identification rule response message is enabled, and the message body content is shown in Table 7. 8.1.6.7 Stop Recognition Rule Request Message The message identifier is M_StopSelectSpec, the stop recognition rule request message, and the message body content is shown in Table 8. 8.1.6.8 Stop recognition rule response message The message identifier is M_StopSelectSpecAck, the stop recognition rule response message, and the message body content is shown in Table 9. 8.1.6.9 Activate recognition rule request message The message identifier is M_EnableSelectSpec, the activation identification rule request message, and the message body content is shown in Table 10. 8.1.6.10 Activate recognition rule response message The message identifier is M_EnableSelectSpecAck, the activation identification rule response message, and the message body content is shown in Table 11. 8.1.6.11 Disable recognition rule request message The message identifier is M_DisableSelectSpec, a request message for disabling the identification rule, and the message body content is shown in Table 12. 8.1.6.12 Disable recognition rul......
Image     

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GB/T 37987-2019_English be delivered?

Answer: Upon your order, we will start to translate GB/T 37987-2019_English as soon as possible, and keep you informed of the progress. The lead time is typically 6 ~ 10 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of GB/T 37987-2019_English with my colleagues?

Answer: Yes. The purchased PDF of GB/T 37987-2019_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.

Question 3: Does the price include tax/VAT?

Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countries

Question 4: Do you accept my currency other than USD?

Answer: Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.