Vehicle remote diagnosis method and device and electronic equipment

By adopting the first-in-first-out principle of message queue in remote vehicle diagnosis, the problem of low efficiency when multiple vehicles issuing data is solved, and the order issuance of batch vehicle instructions is realized, which improves the efficiency and reliability of remote diagnosis.

CN119094575APending Publication Date: 2024-12-06ZHEJIANG GEELY HLDG GRP CO LTD +2
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411202710.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-29
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The existing remote vehicle diagnostic methods are less efficient when sending data from multiple vehicles, and require repeated calls to queuing of interfaces, resulting in inefficient issuance.

Method used

The first-in-first-out principle of message queue is adopted to obtain and issue instructions from the message queue of each online vehicle to ensure that the instructions of batch vehicles are issued in sequence, avoid duplication and omissions, and improve issuance efficiency.

Benefits of technology

It improves the issuance efficiency of vehicle remote diagnosis, ensures that instructions are carried out in sequence, enhances the reliability of instructions, and avoids repeated interface occupation and waiting time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094575A_ABST
    Figure CN119094575A_ABST
Patent Text Reader

Abstract

The invention provides a vehicle remote diagnosis method and device and electronic equipment. The method comprises the following steps: acquiring each online vehicle in to-be-delivered vehicles in batches; according to a first-in first-out principle of the message queue, starting from a first instruction needing to be issued in the message queue of each online vehicle, acquiring an instruction needing to be issued by each online vehicle; wherein the instruction is used for remote diagnosis; the message queue is generated by the following steps: constructing an instruction according to information of diagnosis communication data files corresponding to vehicles to be issued in batches; storing the instruction in a message queue to generate a message queue of each online vehicle; starting from the first instruction, instructions needing to be issued by all the online vehicles are correspondingly issued to all the online vehicles respectively; and under the condition that diagnosis response data returned by each online vehicle is received, issuing a next instruction after the instruction to each online vehicle until all instructions required to be issued by all online vehicles are responded. Therefore, the issuing efficiency is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle remote diagnosis, and in particular to a vehicle remote diagnosis method, device and electronic equipment. Background Art

[0002] Vehicle remote diagnosis is the process of using remote connection technology to diagnose, monitor and maintain vehicle faults through diagnostic tools or platforms to achieve remote fault diagnosis.

[0003] Related technology remote vehicle diagnostics methods are primarily implemented on a platform-side, vehicle-by-vehicle basis. Each time data is sent to a vehicle, the platform uses specially configured interfaces, such as one for configuration information, one for fault codes, and one for freeze frames, to deliver the vehicle's configuration information, fault codes, freeze frames, and other data.

[0004] In short, when multiple vehicles need to send data, the above interface needs to be called repeatedly to queue up for sending. After sending data to one vehicle, it can be sent to the next vehicle, which has low sending efficiency. Summary of the Invention

[0005] The present application provides an improved vehicle remote diagnosis method, device and electronic device.

[0006] This application provides a vehicle remote diagnosis method, comprising:

[0007] Get all online vehicles in the vehicles to be sent in batches;

[0008] According to the first-in-first-out principle of the message queue, starting from the first instruction to be issued in the message queue of each online vehicle, the instructions to be issued to each online vehicle are obtained; wherein the instructions are used for remote diagnosis; the message queue is generated by the following steps: constructing the instructions based on the information of the diagnostic communication data file corresponding to the vehicles to be batch-issued; and storing the instructions in the message queue to generate the message queue of each online vehicle;

[0009] Starting from the first instruction, the instructions required to be issued to each online vehicle are issued to each online vehicle respectively;

[0010] When receiving the diagnostic response data returned by each online vehicle in response to the issued instruction, the next instruction after the instruction is issued to each online vehicle until all online vehicles have completed responding to the instructions.

[0011] Furthermore, the step of obtaining each online vehicle in the vehicles to be sent in batches includes:

[0012] Periodically poll to see if offline vehicles in the batch of vehicles are online;

[0013] If the offline vehicle comes online, the online offline vehicle will be used as the online vehicle; the online vehicle is not a blacklisted vehicle.

[0014] Furthermore, after the instructions required to be issued to each online vehicle are respectively issued to each online vehicle starting from the first instruction, the method further includes:

[0015] The first vehicle is not received to return the diagnostic response data in response to the issued instruction, and the first vehicle is treated as a vehicle to be dispatched; the first vehicle is offline when the instruction is issued;

[0016] Periodically poll whether the vehicle to be dispatched is online again;

[0017] When the vehicle to be dispatched comes online again, the diagnostic response data is received from the first vehicle in response to the issued instruction, and the next instruction after the instruction in the message queue of the first vehicle is read;

[0018] The next instruction is issued to the first vehicle.

[0019] Furthermore, starting from the first instruction, the instructions required to be issued to each online vehicle are issued to each online vehicle respectively, including:

[0020] For each online vehicle in the vehicles to be sent in batches, starting from the first instruction in the message queue of each online vehicle, the instructions that need to be sent to each online vehicle are sent to each online vehicle respectively;

[0021] The step of sending a next instruction after the instruction is sent to each online vehicle upon receiving the diagnostic response data returned by each online vehicle in response to the sent instruction comprises:

[0022] Upon receiving the diagnostic response data returned by each online vehicle, taking out the next instruction of the instruction from the message queue of each online vehicle;

[0023] The next instruction is issued to each online vehicle.

[0024] Furthermore, according to the first-in-first-out principle of the message queue, starting from the first instruction to be issued in the message queue of each online vehicle, obtaining the instructions to be issued by each online vehicle includes:

[0025] According to the vehicle unique identifiers of the vehicles to be distributed in batches, information of the diagnostic communication data files corresponding to the vehicles to be distributed in batches is obtained;

[0026] Search the message queues of each online vehicle to see if there is a corresponding instruction for the information of the diagnostic communication data file;

[0027] If it exists, obtaining the instruction from the message queue;

[0028] The step of constructing the instruction based on the information of the diagnostic communication data file corresponding to the vehicles to be distributed in batches includes:

[0029] If not, constructing the instruction according to the information of the diagnostic communication data file and storing the instruction in the message queue;

[0030] The step of storing the instruction in a message queue and generating the message queue for each online vehicle includes:

[0031] According to the unique vehicle identifiers of the vehicles to be distributed in batches and in accordance with the instructions, an identifier of a message queue is constructed to generate the message queue.

[0032] Further, the instructions include instructions for configuration information;

[0033] The method of constructing a message queue identifier according to the unique vehicle identifiers of the vehicles to be batch-issued and the instruction, and generating the message queue includes:

[0034] According to the unique vehicle identifiers of the vehicles to be distributed in batches, the instructions of the configuration information are added to the message queue, the identifier of the message queue is constructed, and the message queue of each online vehicle is generated.

[0035] Furthermore, the instructions include instructions for fault codes and instructions for freeze frames;

[0036] The method of constructing a message queue identifier according to the unique vehicle identifiers of the vehicles to be batch-issued and the instruction, and generating the message queue includes:

[0037] According to the unique vehicle identification of the vehicles to be sent in batches, the fault code instructions and the freeze frame instructions are added to different message queues respectively, and different message queue identifications are constructed to generate message queues for each online vehicle.

[0038] Furthermore, the method further comprises: receiving a blacklist vehicle inputted periodically through an interactive interface; the inputted blacklist vehicle is used to update an existing vehicle blacklist;

[0039] and / or,

[0040] After receiving the diagnostic response data returned by each online vehicle in response to the issued command, the method further includes: constructing a successfully sent data group for the message queue of each online vehicle; and constructing an expiration time for the successfully sent data group.

[0041] The present application provides a vehicle remote diagnostic device, comprising:

[0042] The dispatched vehicle determination module is used to obtain each online vehicle in the vehicles to be dispatched in batches;

[0043] A batch instruction acquisition module is configured to acquire instructions to be issued to each online vehicle, starting with the first instruction to be issued in the message queue of each online vehicle, in accordance with the first-in-first-out principle of the message queue; wherein the instructions are used for remote diagnosis; the message queue is generated by: constructing the instructions based on information in the diagnostic communication data file corresponding to the vehicles to be issued in batch; and storing the instructions in the message queue to generate the message queue for each online vehicle;

[0044] A vehicle batch sending module is used to send the instructions that need to be sent to each online vehicle respectively, starting from the first instruction;

[0045] The diagnostic response data receiving module is used to send the next instruction after receiving the diagnostic response data returned by each online vehicle in response to the issued instruction to each online vehicle until all online vehicles have completed the response to all the instructions.

[0046] The present application provides an electronic device, comprising one or more processors, for implementing any of the methods described above.

[0047] The present application provides a computer-readable storage medium having a program stored thereon. When the program is executed by a processor, the method described in any one of the above items is implemented.

[0048] The present application provides a computer program product, comprising a computer program / instruction, which implements any of the above methods when executed by a processor.

[0049] In some embodiments, the vehicle remote diagnosis method of the present application obtains the required instructions for each online vehicle in the batch of vehicles to be issued, starting with the first instruction to be issued in the message queue of each online vehicle, according to the first-in-first-out principle of the message queue, and then issues the instructions to each online vehicle. This allows the targeted issuance of remote diagnosis instructions to batch vehicles, rather than issuing instructions to each vehicle after the instructions have been issued to the next one, thereby improving the efficiency of the issuance process. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 Schematic diagram of an application scenario of a vehicle remote diagnosis method according to an embodiment of the present application;

[0051] Figure 2FIG2 is a flow chart of a vehicle remote diagnosis method according to an embodiment of the present application;

[0052] Figure 3 The figure shows a specific flow chart of the vehicle remote diagnosis method according to an embodiment of the present application;

[0053] Figure 4 It is a schematic diagram of the process of the vehicle remote diagnosis device according to an embodiment of the present application;

[0054] Figure 5 Shown is a schematic structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatuses and methods consistent with certain aspects of one or more embodiments of this specification, as detailed in the appended claims.

[0056] It should be noted that in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than those described in this specification. In addition, a single step described in this specification may be broken down into multiple steps for description in other embodiments, and multiple steps described in this specification may be combined into a single step for description in other embodiments.

[0057] The related art remote vehicle diagnostic method uses an interface for configuration information, an interface for fault codes, and an interface for freeze frames. When multiple vehicles need to send data, these interfaces must be repeatedly called to queue up for transmission. After one vehicle has been sent data, another can be sent to the next, resulting in low transmission efficiency. Furthermore, to ensure the effectiveness of each interface's processing, the platform in the related art remote vehicle diagnostic method waits two seconds after receiving a response to a command before sending the next command, which also reduces transmission efficiency.

[0058] To address the issue of low delivery efficiency, an embodiment of the present application provides a vehicle remote diagnosis method. For each online vehicle in a batch of vehicles to be delivered, the method, following the first-in-first-out principle of the message queue, retrieves the required instructions for each online vehicle, starting with the first instruction to be delivered in the message queue of each online vehicle, and then delivers the instructions to each online vehicle. This allows for targeted delivery of remote diagnosis instructions to a batch of vehicles, rather than requiring delivery to each vehicle in turn, thereby improving delivery efficiency. Furthermore, the message queue is generated based on instructions constructed from information in the diagnostic communication data file, and instructions are delivered to each online vehicle, starting with the first instruction in the message queue. Furthermore, by receiving diagnostic response data from each online vehicle, the first instruction is ensured to be delivered accurately. Furthermore, based on the diagnostic response data returned for the delivered instruction, the next instruction following the delivered instruction is delivered to each online vehicle. This ensures that all instructions are delivered to each vehicle in sequence, preventing duplicate and missed instructions and improving instruction reliability.

[0059] Figure 1 Shown is a schematic diagram of an application scenario of the vehicle remote diagnosis method according to an embodiment of the present application.

[0060] like Figure 1 As shown, the application scenario of the vehicle remote diagnosis method is the scenario of interaction between the platform and the vehicle.

[0061] The scenarios of the interaction between the platform end 11 and the vehicle may include but are not limited to the platform end 11, a TSP (Telematics Service Provider) server, and the vehicle end.

[0062] It should be noted that the above-mentioned platform end 11 is mainly used to maintain the information of the diagnostic communication data file, parse the information of the diagnostic communication data file, and obtain the diagnostic instructions; the data related to the diagnostic instructions are written into the message queue such as the redis queue. Later, the instructions are directly obtained from the redis queue for use. The servers of the above-mentioned platform end 11 may include but are not limited to remote diagnostic servers or vehicle background servers. These servers may be deployed in the cloud or may run in the private network within the enterprise. The executor of the vehicle remote diagnosis method in this article can be the remote diagnostic server or vehicle background server of the platform end 11.

[0063] The TSP server 12 is used to connect the platform 11 and the vehicle terminal to establish a data transmission bridge between the platform 11 and the vehicle terminal. For example, the TSP server 12 can be a TSP platform. The TSP server 12 is used to forward diagnostic and configuration instructions between the platform 11 and the controller.

[0064] The vehicle-side terminal may include, but is not limited to, a vehicle-mounted terminal and a controller. The controller may be an ECU (Electronic Control Unit) or an MCU (Microcontroller Unit). The vehicle-mounted terminal may be a TBOX (Telematics Box), which serves as a communication bridge between the vehicle and the platform 11, collecting data from various vehicle components and uploading this data to the platform 11. The vehicle-mounted TBOX terminal primarily receives issued diagnostic instructions and returns response data. Diagnostic instructions are issued between the vehicle-mounted TBOX and the controller based on the vehicle's status. Thus, interaction between the platform 11 and the vehicle TBOX is achieved through the TSP server 12.

[0065] The specific interaction process between the platform 11 and the vehicle's TBOX is as follows:

[0066] (1) The platform 11 issues a command through the TSP platform. This command is used for remote diagnosis and monitoring of the status of a device or system. This command is used for remote diagnosis and may also be referred to as a remote diagnosis command in this article. These commands are usually sent to the vehicle side via a network or remote connection to obtain a diagnostic response from the vehicle side. In this way, no physical contact or on-site operation is required, which greatly improves the efficiency of diagnosis and maintenance.

[0067] (2) The TSP platform receives the remote diagnosis instruction sent by the platform terminal 11.

[0068] (3) The vehicle-mounted terminal TBOX receives the diagnostic file containing the remote diagnostic instructions sent by the platform terminal 11 and forwards it to the electronic control unit to achieve interaction with the electronic control unit. The diagnostic file includes the combined instructions.

[0069] (4) An electronic control unit is used to parse the diagnostic file and generate diagnostic response data. The diagnostic response data is used to indicate that the instruction callback is successful. The diagnostic response data may include but is not limited to positive response data indicating that the diagnosis has passed or negative response data indicating that the diagnosis has not passed. The electronic control unit sends the above diagnostic response data to the platform end 11 through the vehicle terminal TBOX for remote diagnostic analysis and processing. Of course, the electronic control unit also stores vehicle operation data, and the vehicle operation data corresponding to the vehicle operation parameters can be obtained from the electronic control unit.

[0070] (5) The platform 11 receives the diagnostic response data returned by each vehicle and sends the next instruction to each vehicle until all online vehicles have completed the response to all remote diagnostic instructions that need to be sent.

[0071] During the above-mentioned interaction, the vehicle terminal TBOX sends the diagnostic response data to the platform terminal 11, which then performs further processing and analysis. The platform terminal 11 receives the diagnostic response data from the vehicle terminal TBOX and ensures that the next command is sent only after the callback is successful. This improves the reliability of command issuance and avoids repeated issuance of the same command.

[0072] Figure 2 Shown is a flow chart of a vehicle remote diagnosis method according to an embodiment of the present application.

[0073] like Figure 2 As shown, the vehicle remote diagnosis method may include but is not limited to the following steps 110 to 140:

[0074] Step 110: Obtain each online vehicle in the vehicles to be sent in batches.

[0075] The "Vehicles to be Batch-Sent" refers to all vehicles that require remote diagnostic instructions. This refers to a collection of vehicles, not just a single vehicle. These vehicles can be of the same model or batch. The "Vehicles to be Batch-Sent" designates a batch of vehicles to which remote diagnostic instructions need to be issued.

[0076] Next, the vehicles to be dispatched in batches may include but are not limited to online vehicles and / or offline vehicles.

[0077] Step 120, according to the first-in-first-out principle of the message queue, starting from the first instruction to be issued in the message queue of each online vehicle, obtains the instructions to be issued to each online vehicle; wherein the instructions are used for remote diagnosis; the message queue is generated by the following steps: constructing instructions based on the information of the diagnostic communication data file corresponding to the vehicles to be batch-issued; and storing the instructions in the message queue to generate a message queue for each online vehicle.

[0078] The above instructions are configured in advance to indicate that after each online vehicle receives the issued instruction, it executes the corresponding instruction and returns diagnostic response data based on the issued instruction.

[0079] On the one hand, for online vehicles, commands can be issued to online vehicles. On the other hand, for offline vehicles, the offline vehicle can be polled to see if it is online. Once the offline vehicle is online, it will start issuing commands to the online vehicle. On the other hand, if a vehicle goes offline while issuing commands to an online vehicle, it will be treated as a dispatched vehicle and the dispatched vehicle will be polled to see if it is online again. Commands can then be issued to the dispatched vehicle again. See below for details.

[0080] The above-mentioned batch distribution can refer to obtaining a large number of vehicles that need to be distributed at one time, and then distributing them one by one according to the instructions that need to be distributed to each vehicle. The cycle for each vehicle is similar to a waterfall form, and it is normally non-interrupted in the middle until the instruction distribution is completed.

[0081] At the same time, batch delivery is performed on a one-time basis, per vehicle and per command, to the message queue. All commands for each vehicle are added to its own message queue, eliminating the need for a separate message queue for all vehicles. For online vehicles, the first command is delivered to each vehicle. If the vehicle responds to the command, the queue outputs the next command to the vehicle until all commands have been delivered and responded to.

[0082] In this article, issuing instructions can be instructions that need to be issued in the early stage of the platform configuration. It is a service that performs the issuing task. This service mainly handles the vehicle functions that need to be issued, the reading and storage of instruction data, the issuance of data instructions, queue processing, and the return of the diagnostic response data of the instruction is first received through Kafka and then consumed and stored. Among them, Kafka is an open source stream processing platform and message queue system for processing large-scale real-time data streams and providing high throughput, persistent storage and horizontal scalability. Issuing instructions means that all vehicles issue instructions in parallel. For a single vehicle, all instructions are issued one by one for each vehicle.

[0083] Step 130 , starting from the first instruction, the instructions that need to be sent to each online vehicle are sent to each online vehicle respectively.

[0084] In this article, the process from the first instruction to issuing instructions to each online vehicle and receiving the above-mentioned diagnostic response data can be called the remote diagnosis process.

[0085] Step 140 : When receiving the diagnostic response data returned by each online vehicle in response to the issued command, the next command after the issued command is issued to each online vehicle until all online vehicles have responded to all commands.

[0086] It should be noted that the aforementioned instructions may include, but are not limited to, configuration information instructions. These instructions may also include, but are not limited to, fault code instructions and freeze frame instructions. The freeze frame instruction is sent after the fault code instruction is sent. Multiple instructions may be present, for example, multiple configuration information may be present.

[0087] If the instructions that need to be issued are complete, that is, instructions containing configuration information, fault code instructions, and freeze frame instructions. First, obtain all the instructions for each vehicle and enter them into each vehicle's respective message queue. Then, after the instructions are written to the message queue, issue the first configuration information instruction to the TSP platform (the instruction data will be encapsulated in Kafka, and later, the write service consumer Kafka will write the issued instructions into big data). After waiting for the diagnostic response data for the first configuration information to be returned, issue the next configuration instruction (at the same time, the returned result is encapsulated in Kafka, and later Kafka consumption updates the status value of the instruction in the database), until the fault code instructions and freeze frame instructions are issued one by one in sequence.

[0088] In this context, step 140 may further include issuing the next instruction after the previously issued instruction to each online vehicle if diagnostic response data is received from each online vehicle without waiting for a period of time. In this manner, since the present application does not use the same configured interface, thus preventing the same interface from being occupied, after receiving the diagnostic response data, the next instruction can be issued directly without waiting for several seconds, thereby improving the efficiency of issuing instructions.

[0089] Combine Figure 1 As shown in this article, the following two optional methods are used to obtain each online vehicle in the vehicles to be batched:

[0090] In one optional approach, first, a message is sent to the vehicles to be batch-sent. Second, if a response is received from the vehicle to the message, the vehicle is determined to be online. Third, if no response is received from the vehicle to the message, the vehicle is determined to be offline. The vehicles to be batch-sent are not on a blacklist. Blacklisted vehicles are vehicles to which no instructions are required, and are used to preemptively exclude these vehicles to avoid invalid instructions.

[0091] Messages may include, but are not limited to, heartbeat signals or request signals. Online vehicles can primarily parse message data through a separate service; based on the reported data, the vehicle's online status is obtained in real time. The message data includes the aforementioned messages, and message data can be sent every 10 seconds.

[0092] In this way, it is possible to determine whether the vehicle is offline or online by sending a message and receiving a response.

[0093] Figure 3 The figure shows a specific flow chart of the vehicle remote diagnosis method according to an embodiment of the present application.

[0094] In such Figure 3In another optional approach, a periodic poll is performed to determine whether offline vehicles in the batch to be dispatched are online. If an offline vehicle comes online, the online vehicle is considered online. Online vehicles are not blacklisted. In this way, if an initial round of commands needs to be dispatched but the vehicle is offline, polling can be used to determine whether the vehicle is online. If the vehicle is online, the command is dispatched; otherwise, polling continues. This allows all vehicles to be dispatched in batches to be determined to be online or offline, enabling the dispatch of commands and the acquisition of data.

[0095] Combine Figure 2 As shown, the instructions to be issued to each online vehicle in the vehicles to be issued in batches can be determined by either of the following two methods:

[0096] In the first optional determination method, according to the first-in-first-out principle of the message queue, the instructions to be issued in the message queue of each online vehicle are taken out from the message queue pre-generated by each online vehicle. The message queue of each online vehicle is pre-generated using the following steps 1 and 2:

[0097] Step 1: Obtain the instructions that need to be issued to each online vehicle in the vehicles to be issued in batches for the first time.

[0098] Among them, the above-mentioned step 1 may further include: obtaining information of the diagnostic communication data file corresponding to the vehicles to be distributed in batches according to the vehicle unique identification of the vehicles to be distributed in batches; and constructing the instructions to be distributed according to the information of the diagnostic communication data file.

[0099] The message queue is primarily used to receive command requests from the vehicle, store the data after the command is issued, and update the corresponding data in the database with the returned command status. The message queue can include, but is not limited to, one or more of ActiveMQ queues, Redis queues, and RabbitMQ queues.

[0100] It should be noted that the ActiveMQ queues mentioned above are queues implemented based on the ActiveMQ message broker system. ActiveMQ provides two messaging modes: queues and topics. Queues are a point-to-point messaging model, where each message can only be received by one consumer. In ActiveMQ, queues implement a FIFO (First-In, First-Out) messaging mechanism.

[0101] The RabbitMQ queue mentioned above refers to a queue implemented based on the RabbitMQ message broker system. RabbitMQ queues are FIFO, meaning that commands are sent to the queue in the same order in which they were submitted.

[0102] The above-mentioned Redis queue refers to a queue implemented using the list in the Redis data structure. The Redis queue implements the first-in-first-out order by inserting instructions at the end of the list and then getting instructions from the head of the list.

[0103] The second step is to generate a message queue for each online vehicle according to the instructions that need to be issued.

[0104] In the first optional determination method described above, the instructions required for each online vehicle in the batch of vehicles to be issued are initially obtained; a message queue for each online vehicle is generated based on the instructions required for issuance. Subsequently, the instructions required for issuance in the message queue of each online vehicle are retrieved from the pre-generated message queue, which is highly efficient and eliminates the need for repeated instruction acquisition.

[0105] The above step 120 may further include, but is not limited to, the following steps ① to ③. The generation process of the above message queue includes the following steps ④ and ⑤:

[0106] Step ①, according to the vehicle unique identifier of the vehicle to be distributed in batches, obtain the information of the diagnostic communication data file corresponding to the vehicle to be distributed in batches.

[0107] The above-mentioned unique vehicle identifier may include, but is not limited to, a VIN (Vehicle Identification Number), which is used to indicate the uniqueness of the vehicle.

[0108] Step ②: Search the message queues of each online vehicle to see if there is an instruction corresponding to the information of the diagnostic communication data file.

[0109] Step ③, if it exists, get the instruction from the message queue.

[0110] In step 4, if the command does not exist, the command is constructed based on the information in the diagnostic communication data file and stored in the message queue. Simultaneously, the command to be issued is stored in the database. Upon receiving diagnostic response data from each online vehicle, the corresponding diagnostic response data is recorded in the database according to the issued command. This decouples the issuance of commands from the storage of diagnostic response data, facilitating faster response times.

[0111] The above step ④ may further include the following situations:

[0112] In the first case, if it does not exist, the configuration information instructions are constructed based on the information of the diagnostic communication data file, and the information is queried from the database at one time and saved in the message queue. For example, the information of the diagnostic communication data file may include, but is not limited to, information of an ODX (Open Diagnostic eXchange Format) file. For example, one vehicle model can generate an ODX file information. Based on the ODX file information, the configuration information instructions are constructed, and the database is queried at one time and saved in the redis queue. Combined with Figure 3 As shown, the configuration information is obtained for the first time and written into the redis queue. The second and subsequent times are obtained directly from the redis queue.

[0113] In the second case, if it does not exist, the fault code instruction is constructed based on the information of the diagnostic communication data file, and it is queried from the database at one time and saved in the message queue. For example, based on the ODX file information, the fault code instruction is constructed, and the database is queried at one time and saved in the redis queue. Figure 3 As shown, the instruction for obtaining the fault code is firstly obtained and written into the redis queue, and the instruction for the second and subsequent times is directly obtained from the redis queue.

[0114] In the third case, if it does not exist, the freeze frame instruction is constructed based on the information of the diagnostic communication data file, and the instruction is queried from the database at one time and saved in the message queue. For example, based on the ODX file information, the freeze frame instruction is constructed, and the database is queried at one time and saved in the redis queue. Figure 3 As shown, the freeze frame instruction is obtained for the first time and written into the redis queue. The second and subsequent instructions are obtained directly from the redis queue.

[0115] In short, if there is no instruction when reading instructions from the message queue for the first time, the instruction will be written to the message queue. The second and subsequent times of reading instructions, the instruction will be read directly from the message queue. In this way, using the message queue to store instructions and other data decouples data from the database, avoiding the degradation of database performance caused by storing all data in the database.

[0116] Step 5: According to the unique vehicle identifiers of the vehicles to be distributed in batches and the instructions, an identifier of a message queue is constructed to generate the message queue.

[0117] The following is an example of the acquisition process of the above instructions:

[0118] [1] The platform obtains the corresponding ODX file information based on VIN.

[0119] [2] The platform searches for the redis queue based on the information in the ODX file. If not, it constructs instructions based on the information in the ODX file and writes the instructions into the redis queue.

[0120] [3],The platform constructs different redis keys based on the configuration information,,fault codes, and freeze frames, and saves the data to the redis queue.

[0121] [4] The platform issues instructions.

[0122] [5] The platform receives the diagnostic response data returned by the command and updates the status.

[0123] In the second optional determination method, the instructions to be issued to each online vehicle in the vehicles to be issued in batches are directly obtained. In this way, the instructions need to be obtained each time, which improves the real-time performance of the instruction acquisition.

[0124] Combine Figure 3 As shown, for a vehicle that has not received the diagnostic response data returned in response to the issued command, it is considered that the online vehicle is currently offline and has been offline, and the following steps 1) to 4) are used for scheduled scheduling:

[0125] 1) After step 130, if the first vehicle does not return the diagnostic response data to the issued command, the first vehicle is treated as a vehicle to be dispatched. The first vehicle is offline when the command is issued.

[0126] The above-mentioned vehicles to be dispatched are vehicles that are offline when the instructions are issued, and are used to represent the objects of subsequent periodic polling.

[0127] 2) Periodically poll whether the vehicle to be dispatched is online again.

[0128] The term "cycle" in this document refers to the duration of a poll. This cycle can be set based on user needs. The shorter the cycle, the more frequent the polling, and the more timely the re-online confirmation of the vehicle to be dispatched, but the system load is greater. Therefore, the duration of the cycle is set to balance the timeliness of the re-online confirmation of the vehicle to be dispatched and the system load. For example, the duration of the cycle is greater than 8 seconds. For example, the duration of the cycle can be 9 seconds, 10 seconds, 11 seconds, and 12 seconds. This is not limited here, and no further examples are given.

[0129] 3) When the vehicle to be dispatched comes online again, the diagnostic response data is received from the first vehicle in response to the issued instruction, and the next instruction after the instruction in the message queue of the first vehicle is read.

[0130] 4) Sending the next instruction to the first vehicle and each online vehicle.

[0131] In this embodiment of the present application, a message queue is used to store all instructions that need to be issued to the dispatched vehicle. Once the dispatched vehicle comes online again, the next instruction can be issued. This allows the same instruction to be issued once, avoiding the need to issue it twice. It also allows for the determination of whether a vehicle is online or offline, as well as data acquisition issues, to avoid invalid instruction issuance (instructions failing to reach offline vehicles).

[0132] Combine Figure 2 As shown, the above step 120 may further include the following step 1, and the above step 140 may further include the following step 2 and step 3.

[0133] In the first step, for each online vehicle in the vehicles to be sent in batches, starting from the first instruction in the message queue of each online vehicle, the instructions that need to be sent to each online vehicle are sent to each online vehicle respectively.

[0134] The second step is to retrieve the next instruction of the instruction from the message queue of each online vehicle when the diagnostic response data returned by each online vehicle is received.

[0135] Step 3: Send the next instruction to each online vehicle.

[0136] The following is an example of the platform issuing instructions to a bicycle:

[0137] <1> , the platform side first sends a configuration information instruction to the vehicle side based on the command information of the message queue, such as the redis queue.

[0138] <2> , the vehicle side monitors the data diagnostic instructions in the MQTT (Message Queuing Telemetry Transport) channel and obtains status detection instructions.

[0139] <3> After receiving the status detection instruction, the vehicle terminal generates diagnostic response data corresponding to the status detection instruction and feeds back the diagnostic response data to the server on the platform side.

[0140] <4> After Kafka receives the vehicle information instruction, the Redis queue continues to send the next instruction and encapsulates the previous data status into another topic. The write service will then update the corresponding data.

[0141] <5> , the platform executes the above process, and after the callback is successful, it continues until all executions are completed.

[0142] The message queue in step ⑤ above can be implemented through the following optional embodiments:

[0143] In a first optional embodiment, the above-mentioned instructions to be issued include instructions for configuration information; according to the unique vehicle identification of the vehicles to be issued in batches, the instructions for the above-mentioned configuration information are added to the message queue, the identification of the message queue is constructed, and the message queue of each online vehicle is generated.

[0144] In an embodiment of the present application, when only instructions for configuration information need to be sent, only the instructions for configuration information can be added to the message queue, and the configuration information of different online vehicles corresponds to different message queue identifiers.

[0145] In a second optional embodiment, the above-mentioned instructions that need to be issued include fault code instructions and freeze frame instructions; according to the vehicle unique identification of the vehicles to be issued in batches, the fault code instructions and freeze frame instructions are added to different message queues respectively, and different message queue identifications are constructed to generate message queues for each online vehicle.

[0146] For example, a Redis queue is constructed: configuration instructions are written first, followed by fault code instructions, and finally freeze frame instructions. After all instructions are written to the Redis queue, a configuration instruction is sent first. After the vehicle receives a response, the next configuration instruction is sent.

[0147] In a third optional embodiment, the configuration information instructions, fault code instructions and freeze frame instructions are added to different message queues respectively, and different message queue identifiers are constructed to generate a message queue for each online vehicle.

[0148] The identifiers of the message queues are used to indicate different types of instructions. The identifiers of the message queues added by the configuration information instructions, the message queues added by the fault code instructions, and the message queues added by the freeze frame instructions are all different.

[0149] The above message queue is like a Redis queue. For example, configuration information, fault codes, freeze frames, and identifiers (Redis keys) of different Redis queues are constructed, and corresponding success or failure data are written to the Redis queue for later batch data delivery.

[0150] The Redis queue for vehicle M is as follows:

[0151] For vehicle M, the key (identifier) ​​of the Redis queue is D1, where D1 represents the DTC (Diagnostic Trouble Code). The value of the Redis queue is the instruction of the fault code.

[0152] For vehicle M, the key (identifier) ​​of the Redis queue is F1, which stands for FFD (freeze Frame Data). The value of the Redis queue is the instruction for freezing the frame.

[0153] For vehicle M, the key (identifier) ​​of the Redis queue is C1, which represents Config Info (Configuration Information). The value of the Redis queue is the instruction of the configuration information.

[0154] Next, the Redis queue of vehicle N is as follows:

[0155] For vehicle N, the key (identifier) ​​of the Redis queue is D2, where D2 represents the DTC (Diagnostic Trouble Code). The value of the Redis queue is the instruction of the trouble code.

[0156] For vehicle N, the key (identifier) ​​of the Redis queue is F2, which stands for FFD (freeze Frame Data). The value of the Redis queue is the instruction to freeze the frame.

[0157] For vehicle N, the key (identifier) ​​of the Redis queue is C2, where C2 stands for Config Info (Configuration Information). The value of the Redis queue is the instruction of the configuration information.

[0158] In this paper, N and M represent the unique identification of the vehicle respectively.

[0159] In some embodiments, the above method further includes: receiving blacklist vehicles inputted periodically through the interactive interface; the inputted blacklist vehicles are used to update the existing vehicle blacklist.

[0160] It should be noted that blacklisted vehicles refer to vehicles that do not need to be issued. The above-mentioned blacklisted vehicles can be personalized according to the platform configuration. It is implemented according to different users. For individual users, all vehicles are obtained, and vehicles that do not need to be issued are added to the blacklist. For platform users such as service station inspectors, platform users add vehicles that do not need to be issued diagnostic instructions to the blacklist according to management needs. Management needs include some vehicles being upgraded, and management time. In this way, blacklisted vehicles can be updated regularly, and vehicles on the blacklist can be released in time, or vehicles that do not need instructions to be issued can be identified as blacklisted vehicles in a timely manner.

[0161] The above-mentioned vehicle blacklist refers to a list containing all the vehicles that do not need to be sent.

[0162] In addition, platform users can also create accounts on the platform to handle vehicle division, and can also choose to query configuration information or fault query. However, before the freeze frame query, they need to select fault query first and then freeze frame query.

[0163] In this embodiment of the present application, before batch delivery, the configured vehicles to be delivered, blacklisted vehicles, online vehicles, and the information to be delivered, such as configuration information query or fault code, are obtained. Then, the online status of these vehicles is obtained and data is delivered to the online vehicles. This improves the effectiveness of the delivered messages.

[0164] In some embodiments, after receiving the diagnostic response data returned by each online vehicle in response to the issued command, the method further includes: constructing a successfully sent data group in the message queue of each online vehicle; and establishing an expiration time for the successfully sent data group. The successfully sent data group may be a successfully sent vehicle table.

[0165] It should be noted that an example of building an expiration time is as follows: when writing the configuration information, fault code, freeze frame and other information sent by each vehicle into the Redis queue, an expiration time is built to 23:59:59 on the same day, that is, the data for that day is cached.

[0166] In the embodiment of the present application, the data group successfully sent by the constructed message queue is directly filtered out for the vehicle when it is sent in batches.

[0167] Based on the same application concept as the above method, the embodiment of the present application also proposes a vehicle remote diagnosis device, such as Figure 4 As shown, the device may include but is not limited to the following modules:

[0168] The dispatched vehicle determination module 31 is used to obtain each online vehicle in the vehicles to be dispatched in batches;

[0169] The batch instruction acquisition module 32 is configured to acquire instructions to be issued to each online vehicle, starting from the first instruction to be issued in the message queue of each online vehicle, in accordance with the first-in-first-out principle of the message queue. The instructions are used for remote diagnosis. The message queue is generated by: constructing the instructions based on the information in the diagnostic communication data file corresponding to the vehicles to be issued in batch; and storing the instructions in the message queue to generate the message queue for each online vehicle.

[0170] The vehicle batch sending module 33 is used to send the instructions that need to be sent to each online vehicle respectively, starting from the first instruction;

[0171] The diagnostic response data receiving module 34 is used to send the next instruction after receiving the diagnostic response data returned by each online vehicle in response to the issued instruction to each online vehicle until all online vehicles have responded to all the instructions.

[0172] In some embodiments, the above-mentioned device further includes: a vehicle offline and online data construction module, which is mainly used based on GB32960, GB17691, and HJ1239 information reported by the vehicle in real time.

[0173] In some embodiments, the apparatus further comprises a vehicle blacklist construction module that receives blacklisted vehicles periodically inputted through an interactive interface; the inputted blacklisted vehicles are used to update existing blacklisted vehicles. Thus, the vehicle blacklist construction module is primarily used to configure vehicles that do not need to be issued.

[0174] In some embodiments, the above-mentioned device also includes: a vehicle sending construction module, which is used to obtain vehicle information that needs to be sent based on the intersection of all vehicles, online vehicles, and blacklisted vehicles, as vehicles to be sent in batches.

[0175] In some embodiments, the above-mentioned device also includes: a message queue expiration time construction module, which is used to construct a successfully sent data group of the message queue of each online vehicle after receiving the diagnostic response data returned by each online vehicle in response to the issued instruction; and construct an expiration time for the successfully sent data group.

[0176] The implementation process of the functions and effects of each module in the above-mentioned device is specifically detailed in the implementation process of the corresponding steps in the above-mentioned method, which can achieve the same technical effect and will not be repeated here.

[0177] An embodiment of the present application provides an electronic device, including the above vehicle remote diagnosis device.

[0178] Figure 5 Shown is a schematic structural diagram of an electronic device 50 provided in an embodiment of the present application.

[0179] like Figure 5 As shown, the electronic device 50 includes one or more processors 51 for implementing the vehicle remote diagnosis method described above.

[0180] In some embodiments, the electronic device 50 may include a storage medium 59. For example, the computer-readable storage medium may store a program that can be called by the processor 51, and may include a non-volatile storage medium. In some embodiments, the electronic device 50 may include a memory 58 and an interface 57. In some embodiments, the electronic device 50 may also include other hardware depending on the actual application.

[0181] The computer-readable storage medium of the embodiment of the present application stores a program thereon, which, when executed by the processor 51 , is used to implement the vehicle remote diagnosis method described above.

[0182] The present application provides a computer program product, comprising a computer program / instruction, which implements any of the above methods when executed by a processor.

[0183] The present application may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing program code. Computer-readable storage media include permanent and non-permanent, removable and non-removable media, and information storage may be implemented by any method or technology. Information may be computer-readable instructions, data structures, modules of a program, or other data. Examples of computer-readable storage media include but are not limited to: phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by a computing device.

[0184] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

[0185] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, the phrase "comprises a ..." defining an element does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

Claims

1. A vehicle remote diagnosis method, characterized in that: include: Get each online vehicle in the vehicles to be sent in batches; According to the first-in-first-out principle of the message queue, starting from the first instruction to be issued in the message queue of each online vehicle, the instructions to be issued by each online vehicle are obtained; wherein the instructions are used for remote diagnosis; the message queue is generated by the following steps: constructing the instructions according to the information of the diagnostic communication data file corresponding to the vehicles to be issued in batches; and storing the instructions in the message queue to generate the message queue of each online vehicle; Starting from the first instruction, the instructions that need to be issued to each online vehicle are issued to each online vehicle respectively; When receiving the diagnostic response data returned by each online vehicle in response to the issued command, the next command after the command is issued to each online vehicle until all the online vehicles have completed the response to the command.

2. The vehicle remote diagnosis method according to claim 1, characterized in that: The step of obtaining each online vehicle in the vehicles to be sent in batches includes: Periodically poll whether offline vehicles in the vehicles to be sent in batches are online; If the offline vehicle comes online, the online offline vehicle will be used as the online vehicle; the online vehicle does not belong to the blacklist vehicle.

3. The vehicle remote diagnosis method according to claim 1, characterized in that: After the instructions to be issued to each online vehicle are issued respectively to each online vehicle starting from the first instruction, the method further includes: The first vehicle is not received to return the diagnostic response data in response to the issued command, and the first vehicle is used as a vehicle to be dispatched; the first vehicle is offline when the command is issued; Periodically poll whether the vehicle to be dispatched is online again; When the to-be-dispatched vehicle is online again, receiving the diagnostic response data returned by the first vehicle in response to the issued instruction, and reading the next instruction after the instruction in the message queue of the first vehicle; The next instruction is issued to the first vehicle.

4. The vehicle remote diagnosis method according to claim 1, characterized in that: Starting from the first instruction, the instructions that need to be issued to each online vehicle are issued to each online vehicle respectively, including: For each online vehicle in the vehicles to be sent in batches, starting from the first instruction in the message queue of each online vehicle, the instructions to be sent to each online vehicle are sent to each online vehicle respectively; The step of sending a next instruction after the instruction to each online vehicle upon receiving the diagnostic response data returned by each online vehicle in response to the sent instruction comprises: Upon receiving the diagnostic response data returned by each online vehicle, taking out the next instruction of the instruction from the message queue of each online vehicle; The next instruction is issued to each online vehicle.

5. The vehicle remote diagnosis method according to claim 1, characterized in that: According to the first-in-first-out principle of the message queue, starting from the first instruction to be sent in the message queue of each online vehicle, obtaining the instruction to be sent by each online vehicle includes: According to the vehicle unique identifiers of the vehicles to be distributed in batches, obtaining information of the diagnostic communication data files corresponding to the vehicles to be distributed in batches; Searching the message queues of each online vehicle for instructions corresponding to the information of the diagnostic communication data file; If it exists, obtaining the instruction from the message queue; The step of constructing the instruction according to the information of the diagnostic communication data file corresponding to the vehicles to be distributed in batches includes: If not, constructing the instruction according to the information of the diagnostic communication data file, and storing the instruction in the message queue; The step of storing the instruction in a message queue and generating the message queue of each online vehicle includes: According to the unique vehicle identifiers of the vehicles to be sent in batches and according to the instructions, an identifier of a message queue is constructed to generate the message queue.

6. The vehicle remote diagnosis method according to claim 5, characterized in that: The instructions include instructions for configuring information; The step of constructing a message queue identifier according to the unique vehicle identifiers of the vehicles to be sent in batches and the instruction, and generating the message queue includes: According to the unique vehicle identifiers of the vehicles to be sent in batches, the instructions of the configuration information are added to the message queue, the identifier of the message queue is constructed, and the message queue of each online vehicle is generated.

7. The vehicle remote diagnosis method according to claim 5, characterized in that: The instructions include fault code instructions and freeze frame instructions; The step of constructing a message queue identifier according to the unique vehicle identifiers of the vehicles to be sent in batches and the instruction, and generating the message queue includes: According to the unique vehicle identification of the vehicles to be sent in batches, the fault code instructions and the freeze frame instructions are added to different message queues in turn, and different message queue identifications are constructed to generate message queues for each online vehicle.

8. The vehicle remote diagnosis method according to claim 1, characterized in that: The method further includes: receiving a blacklist vehicle inputted periodically through an interactive interface; the inputted blacklist vehicle is used to update an existing vehicle blacklist; and / or, After receiving the diagnostic response data returned by each online vehicle in response to the issued command, the method further includes: constructing a successfully sent data group for the message queue of each online vehicle; and constructing an expiration time for the successfully sent data group.

9. A vehicle remote diagnostic device, characterized in that: include: The dispatched vehicle determination module is used to obtain each online vehicle in the vehicles to be dispatched in batches; The batch instruction acquisition module is used to acquire the instructions to be issued by each online vehicle starting from the first instruction to be issued in the message queue of each online vehicle according to the first-in-first-out principle of the message queue; wherein the instructions are used for remote diagnosis; the message queue is generated by the following steps: constructing the instructions according to the information of the diagnostic communication data file corresponding to the vehicles to be issued in batches; and storing the instructions in the message queue to generate the message queue of each online vehicle; A vehicle batch sending module is used to send the instructions that need to be sent to each online vehicle respectively to each online vehicle starting from the first instruction; The diagnostic response data receiving module is used to send the next instruction after the instruction to each online vehicle when receiving the diagnostic response data returned by each online vehicle for the issued instruction, until all the online vehicles have completed the response to all the instructions.

10. An electronic device, characterized in that: The method comprises one or more processors for implementing the vehicle remote diagnosis method according to any one of claims 1 to 8.