A vehicle terminal data acquisition method, vehicle terminal and data acquisition system

Abstract

This invention relates to a vehicle-mounted terminal data acquisition method, a vehicle-mounted terminal, and a data acquisition system, comprising: an application service application registration step, in which the control unit registers the request ID and response ID associated with the application service to the CAN communication unit, and the CAN communication unit creates corresponding identifiers and queues; a data acquisition request step, in which the control unit sends the data read request sent by the application service unit to the corresponding transmit queue, and the CAN communication unit communicates with the CAN bus based on the identifier to request data read; and a data monitoring and receiving step, in which the type of the CAN bus message is determined based on the ID of the CAN bus message; if it is a response to a request from the vehicle-mounted terminal, the received message is parsed and sent to the control unit. This invention can identify diagnostic messages in the CAN bus that share the same request ID / response ID as the application service of the vehicle-mounted terminal, avoid multi-frame flow control processing errors, and reduce data processing conflicts.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a data acquisition method, vehicle terminal, and data acquisition system for a vehicle-mounted terminal. Background Technology

[0002] The "Emission Limits and Measurement Methods for Pollutants from Heavy-Duty Diesel Vehicles (China VI)" (GB17691-2018), released in August 2018, stipulates that starting from Phase 6a, vehicles should be equipped with remote emission management on-board terminals that meet the requirements of Appendix Q, and vehicles are encouraged to transmit data in accordance with the requirements of Appendix Q of this standard. Starting from Phase 6b, manufacturers should ensure that vehicles transmit data in accordance with the requirements of Appendix Q of this standard throughout their entire life cycle, and the data will be received by the ecological and environmental authorities and manufacturers through a remote server.

[0003] According to standard requirements, vehicle-mounted terminals need to collect and report vehicle OBD information, engine data stream information, etc., but currently only diagnostic tools normally have the authority to read this data. Therefore, in actual use, vehicle-mounted terminals often use the address of the diagnostic tool to request data reading. When other network client nodes in the vehicle (such as other driving recorder terminals, vehicle infotainment systems, etc.) or external OBD diagnostic tools are reading data from the same address source, due to the identical identifier address, the vehicle-mounted terminal is very likely to accidentally trigger illegal flow control when receiving and processing multiple frames of data, causing conflicts in the data processing of other client nodes. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of the prior art and propose a vehicle terminal data acquisition method, vehicle terminal and data acquisition system, which can identify diagnostic messages in the CAN bus that share request ID / response ID with the same vehicle terminal application service, avoid multi-frame flow control processing with execution errors and reduce data processing conflicts.

[0005] The technical solution adopted by this invention to solve its technical problem is:

[0006] On the one hand, a method for collecting data from an in-vehicle terminal includes:

[0007] In the application service application registration process, the control unit registers the request ID and response ID associated with the application service to the CAN communication unit. The CAN communication unit creates corresponding read request identifiers, receive response identifiers, other network client node request identifiers, send queues, and receive buffers.

[0008] In the data acquisition request step, the control unit sends the data read request sent by the application business unit to the corresponding send queue. The CAN communication unit communicates with the CAN bus based on the read request identifier, the receive response identifier, and the request identifiers of other network client nodes to request to read data.

[0009] The data monitoring and receiving steps determine the type of the message based on the ID of the CAN bus message. The type includes a response to a request from the vehicle terminal, a request from another network client node, or a response to a request from another network client node. If it is a response to a request from the vehicle terminal, the received message is parsed and sent to the control unit.

[0010] Preferably, the application service application registration step specifically includes:

[0011] The control unit receives the data read request sent by the application service unit and registers the corresponding request ID and response ID to the CAN communication unit. Based on the request ID and response ID, the CAN communication unit creates the corresponding read request identifier, receive response identifier, other network client node request identifier, send queue and receive buffer, and initializes the read request identifier, receive response identifier and other network client node request identifier to false.

[0012] Preferably, the data acquisition request step specifically includes:

[0013] The control unit receives data read requests sent by the application service unit in real time, and adds the requested data to the corresponding transmit queue of the CAN communication unit according to its request ID and response ID. The CAN communication unit performs periodic scanning. When it reads that the read request identifier, receive response identifier and other network client node request identifiers are all false, it takes an instruction from the transmit queue, initiates a data read request to the CAN bus, and sets the read request identifier to true.

[0014] Preferably, the data acquisition request step further includes: if the read request identifier, the receive response identifier, and other network client node request identifiers are not all false, then wait for the next periodic scan to make a judgment.

[0015] Preferably, the data monitoring and receiving step specifically includes:

[0016] The CAN communication unit monitors CAN bus messages. When it determines that the message ID matches the request ID, it further determines whether the read request flag is true. If not, it determines that the request was sent by another network client node and sets the other network client node request flag to true. When it determines that the message ID matches the response ID, it sets the receive response flag to true and monitors the message. When it detects that the message transmission is complete, it sets the receive response flag and the other network client node request flag to false. If the read request flag is true, it parses the received message and sends it to the control unit, and then sets the read request flag to false.

[0017] Preferably, the application service includes one or more; each application service includes a different request ID and response ID, or several application services share a single request ID and response ID.

[0018] Preferably, the application service unit includes one or more; each application service unit includes one or more application services.

[0019] On the other hand, an in-vehicle terminal includes the aforementioned application service unit, control unit, and CAN communication unit; it also includes other communication units and a storage unit; the control unit is connected to the application service unit, CAN communication unit, other communication units, and storage unit respectively; the control unit communicates with a remote server through the other communication units; and the storage unit is used to store application service data.

[0020] In another aspect, a data acquisition system includes the aforementioned vehicle-mounted terminal; it also includes a remote server; the control unit communicates with the remote server through the other communication unit.

[0021] The present invention has the following beneficial effects:

[0022] (1) This invention identifies messages with the same diagnostic source in the CAN network, that is, monitors diagnostic messages with the same request ID and response ID shared by the vehicle terminal application services in the CAN bus, and avoids multi-frame flow control processing that executes errors at the CAN communication network layer, thereby reducing data processing conflicts on other network client nodes with the same diagnostic source attributes.

[0023] (2) By monitoring the process status of the same external diagnostic source and using a grouped instruction queue, the present invention achieves the independence and continuity of data collection for vehicle terminal application services.

[0024] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments, but the vehicle terminal data acquisition method, vehicle terminal and data acquisition system of the present invention are not limited to the embodiments. Attached Figure Description

[0025] Figure 1 This is a flowchart of the vehicle-mounted terminal data acquisition method according to an embodiment of the present invention;

[0026] Figure 2 This is a flowchart of the application service application registration process according to an embodiment of the present invention;

[0027] Figure 3 This is a flowchart of a data acquisition request according to an embodiment of the present invention;

[0028] Figure 4 This is a flowchart of the data monitoring and receiving steps according to an embodiment of the present invention;

[0029] Figure 5 This is a structural block diagram of the vehicle-mounted terminal according to an embodiment of the present invention;

[0030] Figure 6 This is a structural block diagram of the data acquisition system according to an embodiment of the present invention. Detailed Implementation

[0031] The objects and functions of the present invention, as well as the methods for achieving these objects and functions, will be clarified by referring to exemplary embodiments. However, the present invention is not limited to the exemplary embodiments disclosed below; it can be implemented in various forms. The purpose of this specification is merely to help those skilled in the art to comprehensively understand the specific details of the invention.

[0032] In the following description, embodiments of the invention will be illustrated with reference to the accompanying drawings. In the drawings, the same reference numerals represent the same or similar parts, or the same or similar steps.

[0033] It should be noted that the step labels in the specific implementation are only for making the document look clearer. In actual implementation, the order of the steps can be adjusted according to specific needs.

[0034] See Figure 1 As shown, a method for data acquisition from a vehicle-mounted terminal includes:

[0035] S101, Application service application registration step: The control unit registers the request ID and response ID associated with the application service to the CAN communication unit. The CAN communication unit creates the corresponding read request identifier, receive response identifier, other network client node request identifier, send queue and receive buffer.

[0036] S102, Data Acquisition Request Step: The control unit sends the data read request sent by the application service unit to the corresponding send queue. The CAN communication unit communicates with the CAN bus based on the read request identifier, the receive response identifier, and the request identifiers of other network client nodes to request to read data.

[0037] S103, Data monitoring and receiving step: Based on the ID of the CAN bus message, determine the type of the message; the type includes a response to a request from this vehicle terminal, a request sent by another network client node, or a response to a request from another network client node; if it is a response to a request from this vehicle terminal, parse the received message and send it to the control unit.

[0038] The application service application and registration steps specifically include:

[0039] The control unit receives the data read request sent by the application service unit and registers the corresponding request ID and response ID to the CAN communication unit. Based on the request ID and response ID, the CAN communication unit creates the corresponding read request identifier, receive response identifier, other network client node request identifier, send queue and receive buffer, and initializes the read request identifier, receive response identifier and other network client node request identifier to false.

[0040] The data acquisition request step specifically includes:

[0041] The control unit receives data read requests sent by the application service unit in real time, and adds the requested data to the corresponding transmit queue of the CAN communication unit according to its request ID and response ID. The CAN communication unit performs periodic scanning. When it reads that the read request identifier, receive response identifier and other network client node request identifiers are all false, it takes an instruction from the transmit queue, initiates a data read request to the CAN bus, and sets the read request identifier to true.

[0042] The data acquisition request step further includes: if the read request identifier, the receive response identifier, and other network client node request identifiers are not all false, then wait for the next periodic scan to make a judgment.

[0043] The data monitoring and receiving steps specifically include:

[0044] The CAN communication unit monitors CAN bus messages. When it determines that the message ID matches the request ID, it further determines whether the read request flag is true. If not, it determines that the request was sent by another network client node and sets the other network client node request flag to true. When it determines that the message ID matches the response ID, it sets the receive response flag to true and monitors the message. When it detects that the message transmission is complete, it sets the receive response flag and the other network client node request flag to false. If the read request flag is true, it parses the received message and sends it to the control unit, and then sets the read request flag to false.

[0045] In this embodiment, the process of reading and collecting diagnostic data using an in-vehicle terminal is described as follows:

[0046] (1) See Figure 2 As shown, the control unit collects application requests from each sub-application service to read diagnostic data, and pairs the CAN IDs of the requests and responses. (Request ID) and (Response ID) registered to the CAN communication unit;

[0047] The CAN communication unit responds to each registered diagnostic request and response group via CAN ID. and Each instance should be assigned a corresponding identifier, a separate sending queue, and a data receiving buffer. The identifier includes a read request identifier. Receive response identifier Other network client node request identifiers (Other network client nodes include the vehicle's driving recorder terminal, vehicle infotainment system, etc.); the read request identifier Used to identify when a read request is issued by the vehicle-mounted terminal; the received response identifier Used to identify when the vehicle-mounted terminal receives a response; the other network client nodes request the identifier. Used to identify when other network client nodes are making read requests.

[0048] See Figure 2 As shown in this embodiment, different sub-application services (such as emission collection and monitoring services, fault monitoring services, fuel-saving control services, etc.) can share the same CAN ID pair. (Request ID) and (Response ID), which can be used to distinguish different application services through an index identifier. Of course, different sub-application services can also have their own CAN ID pairs. (Request ID) and (Response ID).

[0049] (2) See Figure 3 As shown, the control unit receives diagnostic data reading requests from each sub-application service in real time, and adds the requested data to the corresponding transmission queue of the CAN communication unit in sequence according to the request and response CAN ID pair.

[0050] The CAN communication unit periodically scans and traverses the identifiers of each transmission queue, and when it detects that the transmission command condition is met ( It equals false. It equals false. If the value is false, a request instruction unit node is retrieved from the corresponding diagnostic request transmission queue, and a diagnostic data request is initiated to the CAN bus. Simultaneously, Set to true; if the condition is not met, wait for the next scan cycle.

[0051] (3) See Figure 4 As shown, the CAN communication unit monitors and parses bus messages. When it receives any one of them... Then Set to true, then perform further checks. Is it true, if If the value is true, it indicates that the response is a read request for the vehicle terminal. The CAN communication unit executes the flow control frame response according to the corresponding rules based on the message type and status (as shown in Table 1 below); if... If the value is false, it indicates that the message is a response from the CAN network server node to a request from another client node. The CAN communication unit only monitors the reception status and does not respond with a flow control frame. ,if If it is not equal to true, then Setting it to true indicates that other network client nodes on the bus are making the same data read request;

[0052] Table 1

[0053]

[0054] The CAN communication unit monitors and traverses the status of each response message, and when it identifies a response message... If all data has been sent, then... Set to false, and set Set to false; if If the value is true, the received data will be parsed and sent to the control unit, and at the same time... Set to false;

[0055] The control unit receives data packets forwarded by the CAN communication unit and distributes them to the corresponding application service units for data processing.

[0056] The control unit can either store the processed CAN data in the storage unit or send it to a remote server through other communication units, depending on the requirements.

[0057] See Figure 5 As shown, an in-vehicle terminal 1 includes the aforementioned application service unit 10, control unit 11, and CAN communication unit 12; it also includes other communication units 13 and a storage unit 14; the control unit 11 is connected to the application service unit 10, CAN communication unit 12, other communication units 13, and storage unit 14 respectively; the control unit 11 communicates with a remote server through the other communication units 13; the storage unit 14 is used to store application service data.

[0058] See Figure 6 As shown, a data acquisition system includes the vehicle-mounted terminal 1; it also includes a remote server 2; the control unit 11 communicates with the remote server 2 through the other communication unit 13.

[0059] The specific embodiments described above further illustrate the purpose, technical solution, and effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and do not limit the present invention. Modifications, substitutions, and variations made by those skilled in the art under the guidance of the present invention without departing from the spirit and scope of the claims are all within the protection scope of the present invention.

Claims

1. A method for data acquisition from a vehicle-mounted terminal, characterized in that, include: In the application service application registration process, the control unit receives the application service unit's request to read data and registers the corresponding request ID and response ID to the CAN communication unit. Based on the request ID and response ID, the CAN communication unit creates the corresponding read request identifier, receive response identifier, other network client node request identifier, send queue, and receive buffer, and initializes the read request identifier, receive response identifier, and other network client node request identifier to false. In the data acquisition request step, the control unit receives data read requests sent by the application service unit in real time, and adds the requested data to the corresponding transmission queue of the CAN communication unit according to its request ID and response ID; the CAN communication unit performs periodic scanning, and when it reads that the read request identifier, the receive response identifier and other network client node request identifiers are all false, it takes an instruction from the transmission queue, initiates a data read request to the CAN bus, and sets the read request identifier to true at the same time. In the data monitoring and receiving steps, the CAN communication unit monitors CAN bus messages. When it determines that the message ID matches the request ID, it further determines whether the read request identifier is true. If not, it determines that the request was sent by another network client node and sets the other network client node request identifier to true. When it determines that the message ID matches the response ID, it sets the receive response identifier to true and monitors the message. When it detects that the message transmission is complete, it sets the receive response identifier and the other network client node request identifier to false. If the read request identifier is true, the received message is parsed and sent to the control unit, and the read request identifier is set to false.

2. The vehicle-mounted terminal data acquisition method according to claim 1, characterized in that, The data acquisition request step further includes: if the read request identifier, the receive response identifier, and other network client node request identifiers are not all false, then wait for the next periodic scan to make a judgment.

3. The vehicle-mounted terminal data acquisition method according to claim 1, characterized in that, The application services include one or more; each application service includes a different request ID and response ID, or several application services share a single request ID and response ID.

4. The vehicle-mounted terminal data acquisition method according to claim 1, characterized in that, The application service unit includes one or more; each application service unit includes one or more application services.

5. A vehicle-mounted terminal, characterized in that, It includes the application service unit, control unit, and CAN communication unit as described in any one of claims 1 to 4; it also includes other communication units and a storage unit; the control unit is connected to the application service unit, CAN communication unit, other communication units, and storage unit respectively; the control unit communicates with a remote server through the other communication units; the storage unit is used to store application service data.

6. A data acquisition system, characterized in that, It includes the vehicle-mounted terminal as described in claim 5; it also includes a remote server; the control unit communicates with the remote server through the other communication unit.

Images