Vehicle diagnosis and OTA data link penetration implementation method, device and equipment

Abstract

The invention discloses a vehicle diagnosis and OTA data link connection implementation method, device and equipment, and relates to the technical field of vehicle diagnos.The method comprises the steps that on the basis of flashing operation on a controller, a diagnostic instrument uploads data flashing information to a TSP platform, and a T-BOX uploads DM1 fault code information of the controller to the TSP platform; and according to the data flashing information and the DM1 fault code information, the TSP platform clears unnecessary fault codes in the DM1 fault code information during the flashing period of the diagnostic instrument and identifies the flashing scene of the illegal diagnostic instrument. The data flashing information comprises a chassis number, a controller type and timestamp information. According to the method, display of unnecessary faults of the background can be reduced, complaints of the market after service are reduced, data channels of all platforms are opened, the front end, the rear end and the interior and exterior of the vehicle are thoroughly linked, the flashing process is further controlled, and the development cost is saved.

Description

Technical Field

[0001] The present application relates to the field of vehicle diagnosis technology, and in particular to a method, device and equipment for implementing vehicle diagnosis and OTA data link communication. Background Art

[0002] When the diagnostic instrument is flashing data to the vehicle controller, the instrument will report a fault code because it cannot receive the corresponding controller message. At the same time, this fault code will also be displayed in the network connection background. At present, the T-BOX (TelematicsBOX) is generally used to monitor the data flashing message by itself. After monitoring the data flashing message, the T-BOX stops uploading the DM1 fault code (engine fault code) information; in addition, the diagnostic protocol has special 85 and 28 services for this situation, which can control the communication of other controllers when the diagnostic instrument is flashing the controller and prevent its DTC (Diagnostic Trouble Code) from being reported.

[0003] Since the controller message fault code cannot be received during the controller flashing period and displayed on the instrument and the network connection background, it will cause more unnecessary display of fault codes, customer and after-market service complaints and other problems. At the same time, according to the relevant regulations of OTA (Over-the-Air Technology), the flashing record of offline devices needs to be uploaded to the relevant platform, and the existing technical solutions cannot meet this demand. If the solution is solved by upgrading the T-BOX solution, the T-BOX will monitor the data flashing message by itself. Because the upgrade of the T-BOX itself needs to be filed, and the amount of changes to the T-BOX is large, it is difficult to change the stock vehicles. In addition, since the controller flashing message is sent frequently, the T-BOX will occupy a lot of resources during the monitoring process, which is easy to affect other functions, and increasing resources requires increasing costs; if the problem is solved by the diagnosis 85, 28 service, all controllers of the vehicle need to have the diagnosis 85, 28 functions and be fully tested. At the same time, the diagnostic instrument's flashing process for all controllers must also be changed, which cannot be achieved in the short term. Summary of the invention

[0004] The present application provides a method, device and equipment for implementing vehicle diagnosis and OTA data link connection, which can reduce the display of unnecessary faults in the background, reduce complaints in the after-sales market, and open up the data channels of various platforms, completely linking the front-end and back-end, inside and outside the vehicle, further controlling the flashing process and saving development costs.

[0005] In a first aspect, an embodiment of the present application provides a method for implementing vehicle diagnosis and OTA data link penetration, and the method for implementing vehicle diagnosis and OTA data link penetration includes:

[0006] Based on the flash operation of the controller, the diagnostic instrument uploads the data flash information to the TSP platform, and the T-BOX uploads the DM1 fault code information of the controller to the TSP platform;

[0007] According to the data flashing information and the DM1 fault code information, the TSP platform clears unnecessary fault codes in the DM1 fault code information during the diagnostic instrument flashing period, and identifies illegal diagnostic instrument flashing scenarios.

[0008] In combination with the first aspect, in one implementation, the data flashing information includes a chassis number, a controller type, and timestamp information.

[0009] In combination with the first aspect, in one implementation, based on the flash operation on the controller, the diagnostic instrument uploads data flash information to the TSP platform, and the T-BOX uploads the DM1 fault code information of the controller to the TSP platform, specifically including:

[0010] When the diagnostic instrument performs data flashing operation on the vehicle's controller, the diagnostic instrument uploads the controller's data flashing information to the OTA platform, and the OTA platform uploads it to the TSP platform;

[0011] T-BOX transmits the controller's DM1 fault code information to the TSP platform.

[0012] In combination with the first aspect, in one implementation, according to the data flashing information and the DM1 fault code information, the TSP platform clears unnecessary fault codes during the diagnostic instrument flashing in the DM1 fault code information, and identifies illegal diagnostic instrument flashing scenarios, wherein the clearing of unnecessary fault codes during the diagnostic instrument flashing in the DM1 fault code information specifically includes:

[0013] The TSP platform compares the DM1 fault code information uploaded by the T-BOX with the data flash information uploaded by the diagnostic instrument;

[0014] Based on the comparison result, if the chassis number of the current vehicle stored in the TSP platform is consistent with the chassis number in the data flashing information, and the timestamp information in the DM1 fault code information is consistent with the timestamp information in the data flashing information, a screening operation is performed to obtain the fault code generated by the instrument during the controller flashing of the diagnostic instrument due to the instrument failing to receive the corresponding controller message;

[0015] Clear the screened fault codes in the DM1 fault code information to cancel the display on the TSP platform.

[0016] In combination with the first aspect, in one implementation, according to the data flashing information and the DM1 fault code information, the TSP platform clears unnecessary fault codes during the diagnostic instrument flashing in the DM1 fault code information, and identifies illegal diagnostic instrument flashing scenarios, wherein the identification of illegal diagnostic instrument flashing scenarios specifically includes:

[0017] When the diagnostic instrument performs a data flash operation on the vehicle's controller, if the TSP platform receives the DM1 fault code information uploaded by the T-BOX and does not receive the data flash information uploaded by the diagnostic instrument, it is determined that the current scenario is an illegal diagnostic instrument flash scenario and a risk warning is issued.

[0018] In combination with the first aspect, in one implementation, the method further includes:

[0019] When the diagnostic instrument performs diagnostic operations on the vehicle's controller, the diagnostic instrument uploads the diagnostic operation information to the OTA platform, and the OTA platform uploads it to the TSP platform;

[0020] The TSP platform controls T-BOX so as not to interfere with the diagnostic operation of the diagnostic instrument.

[0021] In combination with the first aspect, in one implementation, the method further includes:

[0022] When T-BOX performs diagnostic operations on the vehicle's controller, T-BOX uploads the diagnostic operation information to the TSP platform, which then transmits it to the OTA platform.

[0023] Determine whether the vehicle is currently connected to the diagnostic instrument:

[0024] If so, the OTA platform controls the diagnostic instrument to stop using;

[0025] If not, no action will be taken.

[0026] In a second aspect, an embodiment of the present application provides a vehicle diagnosis and OTA data link through implementation device, the vehicle diagnosis and OTA data link through implementation device comprising:

[0027] The upload module is used to drive the diagnostic instrument to upload data flash information to the TSP platform based on the flash operation of the controller, and drive the T-BOX to upload the DM1 fault code information of the controller to the TSP platform;

[0028] The execution module is used to drive the TSP platform to clear unnecessary fault codes in the DM1 fault code information during the diagnostic instrument flashing period and identify illegal diagnostic instrument flashing scenarios according to the data flashing information and the DM1 fault code information.

[0029] In combination with the second aspect, in one implementation, the data flashing information includes chassis number, controller type, and timestamp information.

[0030] In the third aspect, an embodiment of the present application provides a vehicle diagnosis and OTA data link connection implementation device, wherein the vehicle diagnosis and OTA data link connection implementation device includes a processor, a memory, and a vehicle diagnosis and OTA data link connection implementation program stored in the memory and executable by the processor, wherein when the vehicle diagnosis and OTA data link connection implementation program is executed by the processor, the steps of the above-mentioned vehicle diagnosis and OTA data link connection implementation method are implemented.

[0031] The beneficial effects brought by the technical solution provided in the embodiments of the present application include:

[0032] It can reduce the display of unnecessary faults in the background, reduce complaints in the after-sales market, open up data channels of various platforms, and completely link the front-end and back-end, inside and outside the vehicle, further control the flashing process, and there is no need for T-BOX to monitor the flashing messages, saving T-BOX resources, no need to increase T-BOX costs, no need to change T-BOX software and hardware, saving development costs, no need to upgrade T-BOX, no need to upgrade all controller diagnostic services of the whole vehicle, no need to change the controller flashing process in the diagnostic instrument, saving manpower and time costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 A flowchart of the vehicle diagnosis and OTA data link connection implementation method of this application;

[0034] Figure 2 This is a functional module diagram of the device for implementing vehicle diagnosis and OTA data link penetration in this application;

[0035] Figure 3 This is a schematic diagram of the hardware structure of the equipment used to implement vehicle diagnosis and OTA data link communication in this application. DETAILED DESCRIPTION

[0036] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0037] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0038] In a first aspect, an embodiment of the present application provides a method for implementing vehicle diagnosis and OTA data link connectivity.

[0039] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of the vehicle diagnosis and OTA data link connection implementation method of this application. Figure 1 As shown, the vehicle diagnosis and OTA data link connection implementation method includes:

[0040] S1: Based on the flash operation of the controller, the diagnostic instrument uploads the data flash information to the TSP platform, and the T-BOX uploads the DM1 fault code information of the controller to the TSP platform; the data flash information in this application includes the chassis number, controller type, and timestamp information.

[0041] Further, in one embodiment, based on the flash operation of the controller, the diagnostic instrument uploads the data flash information to the TSP platform, and the T-BOX uploads the DM1 fault code information of the controller to the TSP platform, specifically including:

[0042] S101: When the diagnostic instrument performs a data flashing operation on the vehicle controller, the diagnostic instrument uploads the controller data flashing information to the OTA platform, and the OTA platform uploads it to the TSP (Telematics Service Provider, automotive remote communication service system) platform;

[0043] Specifically, the diagnostic instrument uploads the data flashing information of the controller to the OTA platform, and then the OTA platform processes the data flashing information and uploads it to the TSP platform, or the TSP platform actively requests data from the OTA platform to obtain the data flashing information.

[0044] S102: T-BOX sends the controller's DM1 fault code information to the TSP platform.

[0045] That is, for T-BOX, its existing upload logic remains unchanged, and the DM1 fault code information of the controller in the vehicle is uploaded normally, that is, the fault information displayed by the instrument panel in the vehicle is forwarded to the TSP platform.

[0046] S2: Based on the data flashing information and DM1 fault code information, the TSP platform clears unnecessary fault codes during the diagnostic instrument flashing in the DM1 fault code information, and identifies illegal diagnostic instrument flashing scenarios. That is, the TSP platform clears unnecessary fault codes during the diagnostic instrument flashing of the DM1 fault code information uploaded by the T-BOX, and the data flashing information uploaded by the diagnostic instrument, specifically the timestamp information in the data flashing information, and screens out pirated diagnostic instrument flashing scenarios.

[0047] Further, in one embodiment, according to the data flashing information and the DM1 fault code information, the TSP platform clears unnecessary fault codes during the flashing of the diagnostic instrument in the DM1 fault code information, and identifies illegal diagnostic instrument flashing scenarios, wherein the clearing of unnecessary fault codes during the flashing of the diagnostic instrument in the DM1 fault code information specifically includes:

[0048] S201: The TSP platform compares the DM1 fault code information uploaded by the T-BOX with the data flashing information uploaded by the diagnostic instrument;

[0049] S202: Based on the comparison result, if the chassis number of the current vehicle stored in the TSP platform is consistent with the chassis number in the data flashing information, and the timestamp information in the DM1 fault code information is consistent with the timestamp information in the data flashing information, a screening operation is performed to obtain the fault code generated by the instrument due to the failure to receive the corresponding controller message during the controller flashing of the diagnostic instrument;

[0050] S203: Clear the fault code obtained by screening in the DM1 fault code information to cancel the display on the TSP platform.

[0051] Specifically, the TSP platform compares the DM1 fault code information uploaded by the T-BOX with the data flash information uploaded by the diagnostic instrument, that is, compares the relevant time information of the DM1 fault code information uploaded by the T-BOX with the timestamp information of the relevant controller data flash information uploaded by the diagnostic instrument. If the chassis number of the current vehicle recorded by the TSP platform is consistent with the chassis number in the data flash information uploaded by the diagnostic instrument, and the time of the DM1 fault code information uploaded by the T-BOX is consistent with the time of the data flash information uploaded by the diagnostic instrument, then the fault code reported by the instrument when the diagnostic instrument flashes the controller because it cannot receive the corresponding controller message can be filtered out.

[0052] Further, in one embodiment, according to the data flashing information and the DM1 fault code information, the TSP platform clears unnecessary fault codes during the diagnostic instrument flashing in the DM1 fault code information, and identifies illegal diagnostic instrument flashing scenarios, wherein the identification of illegal diagnostic instrument flashing scenarios specifically includes:

[0053] When the diagnostic instrument performs a data flash operation on the vehicle's controller, if the TSP platform receives the DM1 fault code information uploaded by the T-BOX and does not receive the data flash information uploaded by the diagnostic instrument, it is determined that the current scenario is an illegal diagnostic instrument flash scenario and a risk warning is issued.

[0054] Since there are cracked versions of diagnostic instruments on the market, which are usually used to flash the engine controller to modify post-processing or speed limit data, if the TSP platform only receives the DM1 fault code information sent by the T-BOX, but does not receive the timestamp information when the relevant controller data uploaded by the diagnostic instrument was flashed, the vehicle can be locked and the user can be informed of the risks. The customer service center can notify the customer by phone and inform them of the risks.

[0055] Furthermore, the vehicle diagnosis and OTA data link connection implementation method of the present application can also be used to solve the conflict problem between online diagnostic equipment and offline diagnostic equipment. Traditionally, the conflict problem between online diagnostic equipment and offline diagnostic equipment is usually solved by an in-vehicle gateway. The gateway uses arbitration to prevent the online test equipment from interfering with the offline diagnostic test equipment. This solution is based on the in-vehicle circulation method. The present application can solve the conflict problem between online diagnostic equipment and offline diagnostic equipment through an out-of-vehicle circulation method.

[0056] Specifically, when the diagnostic instrument performs diagnostic operations on the vehicle's controller, the diagnostic instrument uploads the diagnostic operation information to the OTA platform, and the OTA platform uploads it to the TSP platform. The TSP platform controls T-BOX not to interfere with the diagnostic operation of the diagnostic instrument. That is, the TSP platform informs T-BOX that the diagnostic instrument is in use at this time. After receiving the message from the TSP platform, T-BOX's behavior should not interfere with the diagnostic instrument.

[0057] Similarly, when T-BOX performs diagnostic operations on the vehicle's controller, T-BOX uploads the diagnostic operation information to the TSP platform, which is then transmitted to the OTA platform. It determines whether the vehicle is currently connected to the diagnostic instrument. If so, the OTA platform controls the diagnostic instrument to stop using it, that is, the OTA platform notifies the diagnostic instrument that T-BOX is not performing diagnostic operations at this time and does not use the functions of the diagnostic instrument. If not, no action is taken.

[0058] The following is a detailed description of the vehicle diagnosis and OTA data link implementation method of the present application.

[0059] When the diagnostic instrument flashes the vehicle controller, the diagnostic instrument uploads the data flashing information to the OTA platform (including chassis number, controller type, and timestamp information). The OTA platform synchronously uploads this information to the TSP platform. At the same time, T-BOX uploads the DM1 fault code information of the entire vehicle to the TSP platform truthfully. The TSP platform clears unnecessary fault codes during the flashing of the diagnostic instrument based on the data from both parties, and screens out the flashing scenarios of pirated diagnostic instruments.

[0060] For the export of the fault list, specifically: the TSP platform compares the DM1 fault code information uploaded by the T-BOX with the data flash information uploaded by the diagnostic instrument, that is, compares the relevant time information of the DM1 fault code information uploaded by the T-BOX with the timestamp information of the data flash information uploaded by the diagnostic instrument. If the current vehicle chassis number recorded by the TSP platform is consistent with the vehicle chassis number in the data flash information uploaded by the diagnostic instrument, and the time when the T-BOX uploads the DM1 fault code information is consistent with the time when the diagnostic instrument uploads the data flash information, then the fault code reported by the instrument due to failure to receive the corresponding controller message when the diagnostic instrument flashes the data to the controller can be screened out.

[0061] Furthermore, if the TSP platform only receives the DM1 fault code information sent by the T-BOX, but does not receive the timestamp information of the data flash information uploaded by the diagnostic instrument, it can lock the current vehicle and inform the user of the risks involved, and list this situation separately when exporting the fault list.

[0062] The vehicle diagnosis and OTA data link connection implementation method of the embodiment of the present application reduces the display of unnecessary faults in the background, reduces complaints in the after-sales market, and opens up the data channels of various platforms, completely linking the front-end and back-end, inside and outside the vehicle. On this basis, a lot of things can be done in the future (for example, the information uploaded by the diagnostic instrument to OTA may include the previous and next basic software versions, the SN number of the diagnostic instrument, the size and name of the flash file), and it is closer to the OTA regulations to further control the flash process; and there is no need for T-BOX to monitor the flash message, which saves T-BOX resources, does not need to increase T-BOX costs, does not need to change the software and hardware of T-BOX, saves development costs, does not need to upgrade T-BOX, does not need to upgrade all controller diagnostic services of the entire vehicle, and does not need to change the controller flash process in the diagnostic instrument, saving manpower and time costs.

[0063] In a second aspect, an embodiment of the present application also provides a device for implementing vehicle diagnosis and OTA data link communication.

[0064] In one embodiment, referring to Figure 2 , Figure 2 This is a functional module diagram of the vehicle diagnosis and OTA data link connection implementation device of this application. Figure 2 As shown, the vehicle diagnosis and OTA data link connection implementation device includes: an upload module and an execution module.

[0065] The upload module is used to drive the diagnostic instrument to upload data flashing information to the TSP platform based on the flashing operation of the controller, and drive the T-BOX to upload the DM1 fault code information of the controller to the TSP platform; the execution module is used to drive the TSP platform to clear unnecessary fault codes in the DM1 fault code information during the flashing of the diagnostic instrument according to the data flashing information and the DM1 fault code information, and to identify illegal diagnostic instrument flashing scenarios.

[0066] In this application, the data flashing information includes chassis number, controller type, and timestamp information.

[0067] In this application, based on the flash operation of the controller, the diagnostic instrument uploads the data flash information to the TSP platform, and the T-BOX uploads the DM1 fault code information of the controller to the TSP platform, specifically including:

[0068] When the diagnostic instrument performs data flashing operation on the vehicle's controller, the diagnostic instrument uploads the controller's data flashing information to the OTA platform, and the OTA platform uploads it to the TSP platform;

[0069] T-BOX transmits the controller's DM1 fault code information to the TSP platform.

[0070] Specifically, the diagnostic instrument uploads the controller's data flash information to the OTA platform, and then the OTA platform processes the data flash information and uploads it to the TSP platform, or the TSP platform actively requests data from the OTA platform to obtain the data flash information. For T-BOX, its existing upload logic remains unchanged, and the DM1 fault code information of the controller in the vehicle is uploaded normally, that is, the fault information displayed by the instrument panel in the vehicle is forwarded to the TSP platform.

[0071] In this application, according to the data flashing information and DM1 fault code information, the TSP platform clears unnecessary fault codes in the DM1 fault code information during the diagnostic instrument flashing period, and identifies illegal diagnostic instrument flashing scenarios, wherein the clearing of unnecessary fault codes in the DM1 fault code information during the diagnostic instrument flashing period specifically includes:

[0072] The TSP platform compares the DM1 fault code information uploaded by the T-BOX with the data flash information uploaded by the diagnostic instrument;

[0073] Based on the comparison result, if the chassis number of the current vehicle stored in the TSP platform is consistent with the chassis number in the data flashing information, and the timestamp information in the DM1 fault code information is consistent with the timestamp information in the data flashing information, a screening operation is performed to obtain the fault code generated by the instrument during the controller flashing of the diagnostic instrument due to the instrument failing to receive the corresponding controller message;

[0074] Clear the screened fault codes in the DM1 fault code information to cancel the display on the TSP platform.

[0075] Specifically, the TSP platform compares the DM1 fault code information uploaded by the T-BOX with the data flash information uploaded by the diagnostic instrument, that is, compares the relevant time information of the DM1 fault code information uploaded by the T-BOX with the timestamp information of the relevant controller data flash information uploaded by the diagnostic instrument. If the chassis number of the current vehicle recorded by the TSP platform is consistent with the chassis number in the data flash information uploaded by the diagnostic instrument, and the time of the DM1 fault code information uploaded by the T-BOX is consistent with the time of the data flash information uploaded by the diagnostic instrument, then the fault code reported by the instrument when the diagnostic instrument flashes the controller because it cannot receive the corresponding controller message can be filtered out.

[0076] In this application, according to the data flashing information and DM1 fault code information, the TSP platform clears unnecessary fault codes during the diagnostic instrument flashing in the DM1 fault code information, and identifies illegal diagnostic instrument flashing scenarios, wherein the identification of illegal diagnostic instrument flashing scenarios specifically includes:

[0077] When the diagnostic instrument performs a data flash operation on the vehicle's controller, if the TSP platform receives the DM1 fault code information uploaded by the T-BOX and does not receive the data flash information uploaded by the diagnostic instrument, it is determined that the current scenario is an illegal diagnostic instrument flash scenario and a risk warning is issued.

[0078] The present application also includes: when the diagnostic instrument performs diagnostic operations on the vehicle's controller, the diagnostic instrument uploads the diagnostic operation information to the OTA platform, and the OTA platform uploads it to the TSP platform; the TSP platform controls the T-BOX not to interfere with the diagnostic operation of the diagnostic instrument.

[0079] The present application also includes: when the T-BOX performs a diagnostic operation on the vehicle's controller, the T-BOX uploads the diagnostic operation information to the TSP platform, and the TSP platform transmits it to the OTA platform;

[0080] Determine whether the vehicle is currently connected to the diagnostic instrument:

[0081] If so, the OTA platform controls the diagnostic instrument to stop using;

[0082] If not, no action will be taken.

[0083] The vehicle diagnosis and OTA data link connection implementation device of the embodiment of the present application can reduce the display of unnecessary faults in the background, reduce complaints in the after-sales market, and open up the data channels of various platforms, so as to completely link the front-end and back-end, inside and outside the vehicle, further control the flashing process, and there is no need for the T-BOX to monitor the flashing messages, thus saving T-BOX resources, no need to increase the T-BOX cost, no need to change the T-BOX hardware and software, saving development costs, no need to upgrade the T-BOX, no need to upgrade all controller diagnostic services of the entire vehicle, and no need to change the controller flashing process in the diagnostic instrument, thus saving manpower and time costs.

[0084] On the third aspect, an embodiment of the present application provides a vehicle diagnosis and OTA data link connection implementation device, which can be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.

[0085] Reference Figure 3 , Figure 3 The hardware structure diagram of the vehicle diagnosis and OTA data link through implementation device involved in the embodiment of the present application is shown in FIG. In the embodiment of the present application, the vehicle diagnosis and OTA data link through implementation device may include a processor, a memory, a communication interface, and a communication bus.

[0086] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0087] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces, which are used to implement vehicle diagnosis and OTA data link penetration to realize the interconnection of devices inside the device, and interfaces used to implement vehicle diagnosis and OTA data link penetration to realize the interconnection of the device with other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display (Display), a keyboard (Keyboard), etc.

[0088] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0089] The processor may be a general-purpose processor, which may call the vehicle diagnosis and OTA data link penetration implementation program stored in the memory, and execute the vehicle diagnosis and OTA data link penetration implementation method provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). Among them, the method executed when the vehicle diagnosis and OTA data link penetration implementation program is called can refer to the various embodiments of the vehicle diagnosis and OTA data link penetration implementation method of the present application, which will not be repeated here.

[0090] Those skilled in the art will understand that Figure 3 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0091] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

[0092] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0093] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or. For example, A / B can mean A or B. The “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0094] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0095] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0096] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for realizing vehicle diagnosis and OTA data link penetration, characterized in that: The vehicle diagnosis and OTA data link connection implementation method includes: Based on the flash operation of the controller, the diagnostic instrument uploads the data flash information to the TSP platform, and the T-BOX uploads the DM1 fault code information of the controller to the TSP platform; According to the data flashing information and the DM1 fault code information, the TSP platform clears unnecessary fault codes in the DM1 fault code information during the diagnostic instrument flashing period, and identifies illegal diagnostic instrument flashing scenarios.

2. A vehicle diagnosis and OTA data link connection implementation method as claimed in claim 1, characterized in that: The data flashing information includes chassis number, controller type, and timestamp information.

3. A vehicle diagnosis and OTA data link connection implementation method as claimed in claim 1, characterized in that: Based on the flashing operation on the controller, the diagnostic instrument uploads the data flashing information to the TSP platform, and the T-BOX uploads the DM1 fault code information of the controller to the TSP platform, which specifically includes: When the diagnostic instrument performs data flashing operation on the vehicle's controller, the diagnostic instrument uploads the controller's data flashing information to the OTA platform, and the OTA platform uploads it to the TSP platform; T-BOX transmits the controller's DM1 fault code information to the TSP platform.

4. A vehicle diagnosis and OTA data link connection implementation method as claimed in claim 1, characterized in that: According to the data flashing information and the DM1 fault code information, the TSP platform clears unnecessary fault codes during the flashing of the diagnostic instrument in the DM1 fault code information, and identifies illegal flashing scenarios of the diagnostic instrument, wherein the clearing of unnecessary fault codes during the flashing of the diagnostic instrument in the DM1 fault code information specifically includes: The TSP platform compares the DM1 fault code information uploaded by the T-BOX with the data flash information uploaded by the diagnostic instrument; Based on the comparison result, if the chassis number of the current vehicle stored in the TSP platform is consistent with the chassis number in the data flashing information, and the timestamp information in the DM1 fault code information is consistent with the timestamp information in the data flashing information, a screening operation is performed to obtain the fault code generated by the instrument during the controller flashing of the diagnostic instrument due to the instrument failing to receive the corresponding controller message; Clear the screened fault codes in the DM1 fault code information to cancel the display on the TSP platform.

5. A vehicle diagnosis and OTA data link connection implementation method as claimed in claim 1, characterized in that: According to the data flashing information and the DM1 fault code information, the TSP platform clears unnecessary fault codes during the diagnostic instrument flashing in the DM1 fault code information, and identifies illegal diagnostic instrument flashing scenarios, wherein the identification of illegal diagnostic instrument flashing scenarios specifically includes: When the diagnostic instrument performs a data flash operation on the vehicle's controller, if the TSP platform receives the DM1 fault code information uploaded by the T-BOX and does not receive the data flash information uploaded by the diagnostic instrument, it is determined that the current scenario is an illegal diagnostic instrument flash scenario and a risk warning is issued.

6. A vehicle diagnosis and OTA data link connection implementation method as claimed in claim 1, characterized in that: The method further comprises: When the diagnostic instrument performs diagnostic operations on the vehicle's controller, the diagnostic instrument uploads the diagnostic operation information to the OTA platform, and the OTA platform uploads it to the TSP platform; The TSP platform controls T-BOX so as not to interfere with the diagnostic operation of the diagnostic instrument.

7. A vehicle diagnosis and OTA data link connection implementation method as claimed in claim 1, characterized in that: The method further comprises: When T-BOX performs diagnostic operations on the vehicle's controller, T-BOX uploads the diagnostic operation information to the TSP platform, which then transmits it to the OTA platform. Determine whether the vehicle is currently connected to the diagnostic instrument: If so, the OTA platform controls the diagnostic instrument to stop using; If not, no action will be taken.

8. A vehicle diagnosis and OTA data link connection implementation device, characterized in that: The vehicle diagnosis and OTA data link connection implementation device comprises: The upload module is used to drive the diagnostic instrument to upload data flash information to the TSP platform based on the flash operation of the controller, and drive the T-BOX to upload the DM1 fault code information of the controller to the TSP platform; The execution module is used to drive the TSP platform to clear unnecessary fault codes in the DM1 fault code information during the diagnostic instrument flashing period and identify illegal diagnostic instrument flashing scenarios according to the data flashing information and the DM1 fault code information.

9. A vehicle diagnosis and OTA data link connection implementation device as claimed in claim 8, characterized in that: The data flashing information includes chassis number, controller type, and timestamp information.

10. A vehicle diagnosis and OTA data link penetration implementation device, characterized in that: The vehicle diagnosis and OTA data link connectivity implementation device includes a processor, a memory, and a vehicle diagnosis and OTA data link connectivity implementation program stored in the memory and executable by the processor, wherein when the vehicle diagnosis and OTA data link connectivity implementation program is executed by the processor, the steps of the vehicle diagnosis and OTA data link connectivity implementation method as described in any one of claims 1 to 7 are implemented.

Images