Logistics vehicle fault determination method and device

Abstract

The invention belongs to the field of vehicles, and discloses a logistics vehicle fault determination method and device. The method comprises the steps that when the logistics vehicle breaks down, the OTA vehicle end program receives a vehicle state message sent by the logistics vehicle when the logistics vehicle breaks down; the OTA vehicle end program analyzes the vehicle state message to obtain a fault code and a fault cause of a fault of the logistics vehicle; the OTA vehicle end program judges whether a fault log is transmitted back or not according to the fault code and a pre-stored fault information table; if the fault log is returned, the OTA vehicle end program reads a log storage path of the fault log in the fault information table, packages a log file of the fault log and sends the packaged log file to the server, and the server sends the packaged log file to the OTA vehicle end program; and a technician downloads the fault log based on the server to carry out fault analysis and solution. According to the invention, the troubleshooting efficiency and the maintenance efficiency of the logistics vehicle can be improved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a method and device for determining a logistics vehicle failure. Background Art

[0002] At present, unmanned logistics vehicles often face functional limitations caused by vehicle failures during development, testing, and production operations. The monitoring of unmanned logistics vehicle failures relies on staff to monitor the status of the vehicle from time to time to discover the failure of the unmanned logistics vehicle. Since unmanned logistics vehicles are dispersed during work, troubleshooting is time-consuming and laborious, and the failure is not discovered in time, resulting in low troubleshooting efficiency. Summary of the invention

[0003] Based on this, it is necessary to provide a method and device for determining logistics vehicle failures in response to the above technical problems.

[0004] In a first aspect, a method for determining a logistics vehicle fault is provided, the method being applied to a logistics vehicle fault determination system, the system comprising a logistics vehicle and a server, the logistics vehicle being installed with an over-the-air upgrade OTA vehicle-side program, the method comprising:

[0005] When the logistics vehicle breaks down, the OTA vehicle-side program receives the vehicle status message sent by the logistics vehicle at the time of the breakdown;

[0006] The OTA vehicle-side program parses the vehicle status message to obtain the fault code and fault cause of the logistics vehicle;

[0007] The OTA vehicle-side program determines whether to send back the fault log according to the fault code and the pre-stored fault information table;

[0008] If the fault log is sent back, the OTA vehicle-side program reads the log storage path of the fault log in the fault information table, packages the log file of the fault log, and sends the packaged log file to the server, so that the technician can download the fault log based on the server to perform fault analysis and resolution.

[0009] As an optional implementation, the fault information table includes multiple fault codes, and the OTA vehicle-side program determines whether to return the fault log according to the fault code and the pre-stored fault information table, including:

[0010] The OTA vehicle-side program matches the fault code with multiple fault codes in the fault information table one by one. If the match is successful, the OTA vehicle-side program determines the fault type and determines to send back the fault log;

[0011] If the match is not successful, the OTA vehicle-side program determines not to send back the fault log.

[0012] As an optional implementation, the method further includes:

[0013] If the packaged log file of the fault log is successfully sent to the server, the OTA vehicle-side program obtains the log information of the fault log and sends the log information to the server;

[0014] If the packaged log file of the fault log is not successfully sent to the server, the OTA vehicle-side program sends a prompt to the server that the log file upload failed.

[0015] As an optional implementation, the log information includes the file name of the log file, the file size, the vehicle VIN code of the logistics vehicle, the core type, the vehicle-side path, the corresponding module of the fault of the logistics vehicle, the fault code, the fault cause and the upload time.

[0016] In a second aspect, a device for determining a logistics vehicle fault is provided, the device being applied to a system for determining a logistics vehicle fault, the system comprising a logistics vehicle and a server, the logistics vehicle being installed with an over-the-air upgrade OTA vehicle-side program, the device comprising:

[0017] A fault monitoring module is used for the OTA vehicle-side program to receive a vehicle status message sent by the logistics vehicle when the logistics vehicle fails;

[0018] A parsing module, used for the OTA vehicle-side program to parse the vehicle status message to obtain the fault code and fault cause of the logistics vehicle;

[0019] A determination module, used for the OTA vehicle-side program to determine whether to return a fault log according to the fault code and a pre-stored fault information table;

[0020] The log feedback module is used to, if the fault log is fed back, the OTA vehicle-side program reads the log storage path of the fault log in the fault information table, packages the log file of the fault log, and sends the packaged log file to the server, so that the technician can download the fault log based on the server to analyze and solve the fault.

[0021] As an optional implementation manner, the fault information table includes multiple fault codes, and the determination module is specifically used to:

[0022] The OTA vehicle-side program matches the fault code with multiple fault codes in the fault information table one by one. If the match is successful, the OTA vehicle-side program determines the fault type and determines to send back the fault log;

[0023] If the match is not successful, the OTA vehicle-side program determines not to send back the fault log.

[0024] As an optional implementation, the device further includes:

[0025] An acquisition module, configured to, if the packaged log file of the fault log is successfully sent to the server, cause the OTA vehicle-side program to acquire log information of the fault log and send the log information to the server;

[0026] The upload module is used for sending a log file upload failure prompt to the server by the OTA vehicle-side program if the packaged log file of the fault log is not successfully sent to the server.

[0027] As an optional implementation, the log information includes the file name of the log file, the file size, the vehicle VIN code of the logistics vehicle, the core type, the vehicle-side path, the corresponding module of the fault of the logistics vehicle, the fault code, the fault cause and the upload time.

[0028] In a third aspect, a system for determining a logistics vehicle failure is provided, and the system for determining a logistics vehicle failure comprises: a method for determining a logistics vehicle failure as described in the first aspect and an apparatus for determining a logistics vehicle failure as described in the second aspect.

[0029] In a fourth aspect, a computer device is provided, comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, and when the processor executes the computer program, the method steps described in the first aspect are implemented.

[0030] In a fifth aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the method steps described in the first aspect are implemented.

[0031] The present application provides a method and device for determining a logistics vehicle fault. The technical solution provided by the embodiment of the present application at least brings the following beneficial effects: when the logistics vehicle fails, the OTA vehicle-side program receives the vehicle status message sent by the logistics vehicle at the time of the failure; the OTA vehicle-side program parses the vehicle status message to obtain the fault code and fault cause of the logistics vehicle failure; the OTA vehicle-side program determines whether to return the fault log based on the fault code and the pre-stored fault information table; if the fault log is returned, the OTA vehicle-side program reads the log storage path of the fault log in the fault information table, packages the log file of the fault log, and sends the packaged log file to the server, so that the technician can download the fault log based on the server for fault analysis and resolution. In this way, when a logistics vehicle fails, the vehicle status message of the logistics vehicle is received through the OTA vehicle-side program, the fault code is obtained after parsing, the fault log is obtained based on the fault code, and the fault log is sent to the server, so that the technician can analyze and resolve the fault based on the fault log. In other words, when a logistics vehicle breaks down, the fault log can be automatically sent back to the server, eliminating the need for manual on-site search and on-site troubleshooting, which greatly improves the efficiency of fault troubleshooting and logistics vehicle maintenance.

[0032] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0034] Figure 1 A schematic diagram of the structure of a logistics vehicle fault determination system provided in an embodiment of the present application;

[0035] Figure 2 A flowchart of a method for determining a logistics vehicle failure provided in an embodiment of the present application;

[0036] Figure 3 A flowchart of an example of a method for determining a logistics vehicle failure provided in an embodiment of the present application;

[0037] Figure 4 A schematic diagram of the structure of a device for determining a logistics vehicle failure provided in an embodiment of the present application;

[0038] Figure 5 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0040] The method for determining a logistics vehicle failure provided in the embodiment of the present application can be applied to a logistics vehicle failure determination system. Figure 1 As shown, the logistics vehicle fault determination system includes a logistics vehicle 101 and a server 102 , and an OTA (Over-the-Air Technology) vehicle-side program 103 is installed in the logistics vehicle 101 . The logistics vehicle 101 is connected to the server 102 .

[0041] Logistics vehicle 101 is used to send a vehicle status message to a designated message topic when a failure occurs.

[0042] The server 102 is used to receive the log file of the fault log sent by the OTA vehicle-side program 103, so that the technicians can download the fault log based on the server 102 and perform fault analysis and resolution on the fault of the logistics vehicle 101.

[0043] The OTA vehicle-side program 103 is used to receive the vehicle status message sent by the logistics vehicle 101 when the logistics vehicle 101 fails. The OTA vehicle-side program 103 parses the vehicle status message to obtain the fault code and cause of the fault of the logistics vehicle 101. The OTA vehicle-side program 103 determines whether to return the fault log based on the fault code and the pre-stored fault information table. If the fault log is returned, the OTA vehicle-side program 103 reads the log storage path of the fault log in the fault information table, packages the log file of the fault log, and sends the packaged log file to the server 102.

[0044] The following will describe in detail a method for determining a logistics vehicle failure provided by an embodiment of the present application in conjunction with a specific implementation method. Figure 2 A flow chart of a method for determining a logistics vehicle failure provided in an embodiment of the present application, such as Figure 2 As shown, the specific steps are as follows:

[0045] Step 201, when a logistics vehicle breaks down, the OTA vehicle-side program receives a vehicle status message sent by the logistics vehicle at the time of the breakdown.

[0046] In implementation, unmanned logistics vehicles often face functional limitations caused by vehicle failures during development, testing and production operations. The monitoring of unmanned logistics vehicle failures relies on staff to monitor the status of the vehicle from time to time to discover the failure of the unmanned logistics vehicle. Since unmanned logistics vehicles are scattered when working, it is time-consuming and laborious to troubleshoot the failure, the failure is not discovered in time, and the troubleshooting efficiency is low. In order to locate the module where the problem of the logistics vehicle is located, it is necessary to confirm the fault code during the period when the logistics vehicle fails, and obtain the fault log of the vehicle module corresponding to the fault. This application monitors multiple vehicle fault codes remotely in real time, and automatically triggers the acquisition of the fault log of the logistics vehicle when a fault code appears and remotely transmits it back to the server. The developer directly downloads the fault vehicle log on the server for fault problem analysis, which will greatly improve the troubleshooting and maintenance efficiency of unmanned logistics vehicles. When a logistics vehicle fails, the management module of the logistics vehicle will send a fault message to the specified message topic. An OTA vehicle-side program is installed on the vehicle side of the logistics vehicle, and the MQTT (Message Queuing Telemetry Transport) status information topic of the unmanned logistics vehicle is subscribed to. The OTA vehicle-side program subscribes to the message topic through MQTT and obtains the vehicle status message sent by the logistics vehicle in real time. The status information can be in json format. By adding a fault monitoring module, the problem of untimely fault detection of unmanned logistics vehicles can be effectively solved. In this way, when a logistics vehicle fails, the OTA vehicle-side program receives the vehicle status message sent by the logistics vehicle at the time of the failure. The logistics vehicle can be an unmanned logistics vehicle.

[0047] Step 202: The OTA vehicle-side program parses the vehicle status message to obtain the fault code and cause of the logistics vehicle failure.

[0048] In implementation, the OTA vehicle-side program obtains the vehicle status message sent by the logistics vehicle to the server in real time by subscribing to the MQTT status topic of the unmanned logistics vehicle. After the OTA vehicle-side program obtains the vehicle status message of the logistics vehicle, it needs to parse the vehicle status message. Among them, the vehicle status message can be parsed through json message parsing. For example, the vehicle status message received by the OTA vehicle-side program is string event; / / fault code (for example, 43881) and fault cause (for example, the logistics vehicle deviates from the route). The OTA vehicle-side program needs to parse the event field through json message parsing to obtain the fault code and fault cause within the time period when the parsed logistics vehicle sends the fault. For example, string dgcode; / / fault code (for example, 43881); string dgexplanation; / / fault cause (for example, the logistics vehicle deviates from the route). In this way, the vehicle status message can be parsed to obtain the fault code, and then the fault log can be obtained based on the fault code, so as to analyze and solve the fault based on the fault log.

[0049] Step 203, the OTA vehicle-side program determines whether to send back the fault log based on the fault code and the pre-stored fault information table.

[0050] In implementation, after the OTA vehicle-side program obtains the parsed fault code, it can determine whether the logistics vehicle needs to send a fault log back to the server when a fault occurs based on the fault code and the pre-stored fault information table. Among them, the pre-stored fault information table is the fault code pre-stored on the vehicle side of the logistics vehicle, as well as the fault type corresponding to the fault code and the log storage path of the log file of the fault log that needs to be uploaded. Therefore, when a fault code of a logistics vehicle appears, it is confirmed through the fault code and the pre-stored fault information table to determine whether the current fault of the logistics vehicle needs to send a fault log back to the server.

[0051] The specific process of executing step 203 is as follows:

[0052] Step 1: The OTA vehicle-side program matches the fault code with multiple fault codes in the fault information table one by one. If the match is successful, the OTA vehicle-side program determines the fault type and decides to send back the fault log.

[0053] In implementation, after the OTA vehicle-side program parses the fault code, it compares the fault code with multiple fault codes in the fault information table. By matching the fault code with multiple fault codes in the fault information table one by one, if the match is successful, it means that the fault of the logistics vehicle is recorded in the fault information table, and the fault type of the fault can be determined. The fault information table records the fault type corresponding to the fault code, as well as the corresponding log storage path of the fault log that needs to be returned. In other words, the fault types in the pre-stored fault information table need to return the fault log. Through the fault code json table, the corresponding relationship between the fault code and the log storage address of the fault log is bound. Therefore, when the fault code successfully matches multiple fault codes in the fault information table and determines the fault type, it is determined that the fault type needs to return the fault log. Therefore, the OTA vehicle-side program matches the fault code with multiple fault codes in the fault information table one by one. If the match is successful, the OTA vehicle-side program determines the fault type and determines to return the fault log. In this way, it is possible to remotely monitor the fault codes of multiple logistics vehicles in real time. When a fault code appears, it will automatically trigger the acquisition of the fault log of the logistics vehicle and remotely transmit it back to the server, effectively solving the problem of untimely discovery of logistics vehicle faults.

[0054] Step 2: If the match is not successful, the OTA vehicle-side program determines not to send back the fault log.

[0055] In implementation, the OTA vehicle-side program compares the fault code with multiple fault codes in the fault information table, and matches the fault code with the multiple fault codes in the fault information table one by one. If the match is not successful, it means that the fault of the logistics vehicle is not recorded in the fault information table. Because the fault information table records the fault type corresponding to the fault code, and the corresponding log storage path of the fault log that needs to be returned. The fault types in the pre-stored fault information table need to return the fault log. It can be seen that if the fault code of the logistics vehicle is compared with the fault information table, the fault code is not the fault code in the fault information table, and it will not be returned at this time. Then, the fault of the logistics vehicle does not need to return the fault log. Therefore, if the match is not successful, the OTA vehicle-side program determines not to return the fault log.

[0056] Step 204, if the fault log is sent back, the OTA vehicle-side program reads the log storage path of the fault log in the fault information table, packages the log file of the fault log, and sends the packaged log file to the server, so that the technician can download the fault log based on the server to analyze and solve the fault.

[0057] In implementation, after the fault code successfully matches multiple fault codes in the fault information table, it indicates that the fault type of the logistics vehicle requires a fault log to be sent back to the server. The fault information table records the fault type corresponding to the fault code, as well as the corresponding log storage path of the fault log that needs to be sent back. When it is necessary to send back the fault log, the OTA vehicle-side program reads the log storage path of the fault log in the fault information table according to the log storage path of the fault log corresponding to the fault type of the fault, packages the log file of the fault log, and sends the packaged log file to the server, thereby completing the return of the fault log, so that the technician can download the fault log based on the server for fault analysis and resolution. Since the fault logs of existing logistics vehicles need to be sent back to the computer at the actual vehicle site before the technicians can perform subsequent fault analysis, the logistics vehicles are relatively scattered when working, which is inefficient. In the solution of the present application, when a fault code appears, the vehicle's fault log is automatically triggered and remotely transmitted back to the server. There is no need to go to the site to waste time and effort to find logistics vehicles. The automatic packaging function of the log management module improves the efficiency of fault log transmission and realizes automatic monitoring and diagnosis of transmitted fault log data. Developers can directly download the faulty vehicle log on the server for problem analysis, which will greatly improve the efficiency of fault troubleshooting and unmanned logistics vehicle maintenance.

[0058] Furthermore, after the fault log is successfully sent back, the server also needs to record other log information of the fault. The specific process is as follows:

[0059] Step A: If the packaged fault log file is successfully sent to the server, the OTA vehicle-side program obtains the log information of the fault log and sends the log information to the server.

[0060] In implementation, the OTA vehicle-side program sends the packaged log file to the server and determines whether the log file is successfully sent to the server. If the packaged fault log file is successfully sent to the server, the OTA vehicle-side program also needs to send the log information of the fault log to the server so that the server can save the log information of the logistics vehicle. Therefore, the OTA vehicle-side program needs to obtain the log information of the fault log first, and then send the obtained log information to the server.

[0061] Among them, the log information includes the file name of the log file, file size, vehicle VIN code of the logistics vehicle, core type, vehicle-side path, corresponding module of the logistics vehicle's fault, fault code, fault cause and upload time.

[0062] Step B: If the packaged fault log file is not successfully sent to the server, the OTA vehicle-side program sends a log file upload failure prompt to the server.

[0063] In implementation, the OTA vehicle-side program sends the packaged log file to the server and determines whether the log file is successfully sent to the server. If the packaged fault log file is not successfully sent to the server, the OTA vehicle-side program needs to send a log file upload failure prompt to the server to prompt the developer to solve the backhaul problem. Among them, the reason for unsuccessful sending can be poor network or a problem with the OTA vehicle-side program.

[0064] Figure 3 This is a flow chart of an example of a method for determining a logistics vehicle failure provided in an embodiment of the present application. Figure 3 As shown, step 301, the OTA vehicle-side program subscribes to the vehicle status topic of the logistics vehicle; step 302, the OTA vehicle-side program monitors and parses the status message field in real time; step 303, the OTA vehicle-side program obtains the parsed fault code; step 304, the OTA vehicle-side program determines the fault type based on the fault code and fault information table, and determines whether the log needs to be returned; step 305, if yes, the OTA vehicle-side program packages and returns the corresponding fault log file according to the fault type; step 306, the OTA vehicle-side program reports the log information; step 307, the execution ends.

[0065] The embodiment of the present application provides a method for determining a logistics vehicle failure. When the logistics vehicle fails, the OTA vehicle-side program receives the vehicle status message sent by the logistics vehicle at the time of the failure; the OTA vehicle-side program parses the vehicle status message to obtain the fault code and fault cause of the logistics vehicle failure; the OTA vehicle-side program determines whether to return the fault log based on the fault code and the pre-stored fault information table; if the fault log is returned, the OTA vehicle-side program reads the log storage path of the fault log in the fault information table, packages the log file of the fault log, and sends the packaged log file to the server, so that the technician can download the fault log based on the server to analyze and solve the fault. In this way, when a logistics vehicle fails, the vehicle status message of the logistics vehicle is received through the OTA vehicle-side program, the fault code is obtained after parsing, the fault log is obtained based on the fault code, and the fault log is sent to the server, so that the technician can analyze and solve the fault based on the fault log. In other words, when a logistics vehicle breaks down, the fault log can be automatically sent back to the server, eliminating the need for manual on-site search and on-site troubleshooting, which greatly improves the efficiency of fault troubleshooting and logistics vehicle maintenance.

[0066] It should be understood that although Figures 2 to 3The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figures 2 to 3 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0067] It can be understood that the same / similar parts between the various embodiments of the above method in this specification can refer to each other, and each embodiment focuses on the differences from other embodiments. For related points, please refer to the description of other method embodiments.

[0068] The present application also provides a device for determining a logistics vehicle failure. Figure 4 As shown, the device comprises:

[0069] The fault monitoring module 401 is used for the OTA vehicle-side program to receive the vehicle status message sent by the logistics vehicle when the logistics vehicle fails;

[0070] The parsing module 402 is used for the OTA vehicle-side program to parse the vehicle status message to obtain the fault code and fault cause of the logistics vehicle;

[0071] The determination module 403 is used for the OTA vehicle-side program to determine whether to return the fault log according to the fault code and the pre-stored fault information table;

[0072] The log feedback module 404 is used to, if the fault log is fed back, then the OTA vehicle-side program reads the log storage path of the fault log in the fault information table, packages the log file of the fault log, and sends the packaged log file to the server, so that the technician can download the fault log based on the server to perform fault analysis and resolution.

[0073] As an optional implementation manner, the fault information table includes multiple fault codes, and the determination module 403 is specifically used to:

[0074] The OTA vehicle-side program matches the fault code with multiple fault codes in the fault information table one by one. If the match is successful, the OTA vehicle-side program determines the fault type and determines to send back the fault log;

[0075] If the match is not successful, the OTA vehicle-side program determines not to send back the fault log.

[0076] As an optional implementation, the device further includes:

[0077] An acquisition module, configured to, if the packaged log file of the fault log is successfully sent to the server, cause the OTA vehicle-side program to acquire log information of the fault log and send the log information to the server;

[0078] The upload module is used for sending a log file upload failure prompt to the server by the OTA vehicle-side program if the packaged log file of the fault log is not successfully sent to the server.

[0079] As an optional implementation, the log information includes the file name of the log file, the file size, the vehicle VIN code of the logistics vehicle, the core type, the vehicle-side path, the corresponding module of the fault of the logistics vehicle, the fault code, the fault cause and the upload time.

[0080] The embodiment of the present application provides a device for determining a logistics vehicle fault. When the logistics vehicle fails, the OTA vehicle-side program receives the vehicle status message sent by the logistics vehicle at the time of the failure; the OTA vehicle-side program parses the vehicle status message to obtain the fault code and fault cause of the logistics vehicle failure; the OTA vehicle-side program determines whether to return the fault log based on the fault code and the pre-stored fault information table; if the fault log is returned, the OTA vehicle-side program reads the log storage path of the fault log in the fault information table, packages the log file of the fault log, and sends the packaged log file to the server, so that the technician can download the fault log based on the server to analyze and solve the fault. In this way, when a logistics vehicle fails, the vehicle status message of the logistics vehicle is received through the OTA vehicle-side program, the fault code is obtained after parsing, the fault log is obtained based on the fault code, and the fault log is sent to the server, so that the technician can analyze and solve the fault based on the fault log. In other words, when a logistics vehicle breaks down, the fault log can be automatically sent back to the server, eliminating the need for manual on-site search and on-site troubleshooting, which greatly improves the efficiency of fault troubleshooting and logistics vehicle maintenance.

[0081] The specific definition of the device for determining a logistics vehicle failure can be found in the definition of the method for determining a logistics vehicle failure in the above text, and will not be repeated here. Each module in the above-mentioned device for determining a logistics vehicle failure can be implemented in whole or in part by software, hardware, and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0082] In one embodiment, a computer device is provided, such as Figure 5 As shown, it includes a memory and a processor, the memory stores a computer program that can be run on the processor, and the processor implements the above-mentioned method steps for determining the failure of the logistics vehicle when executing the computer program.

[0083] In one embodiment, a computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the above-mentioned method for determining a logistics vehicle failure.

[0084] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0085] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0086] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data for analysis, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0087] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0088] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0089] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for determining a logistics vehicle failure, characterized in that: The method is applied to a logistics vehicle fault determination system, the system comprising a logistics vehicle and a server, the logistics vehicle is equipped with an over-the-air upgrade OTA vehicle-side program, and the method comprises: When the logistics vehicle breaks down, the OTA vehicle-side program receives the vehicle status message sent by the logistics vehicle at the time of the breakdown; The OTA vehicle-side program parses the vehicle status message to obtain the fault code and fault cause of the logistics vehicle; The OTA vehicle-side program determines whether to send back the fault log according to the fault code and the pre-stored fault information table; If the fault log is sent back, the OTA vehicle-side program reads the log storage path of the fault log in the fault information table, packages the log file of the fault log, and sends the packaged log file to the server, so that the technician can download the fault log based on the server to perform fault analysis and resolution.

2. The method according to claim 1, characterized in that: The fault information table includes multiple fault codes, and the OTA vehicle-side program determines whether to return the fault log according to the fault code and the pre-stored fault information table, including: The OTA vehicle-side program matches the fault code with multiple fault codes in the fault information table one by one. If the match is successful, the OTA vehicle-side program determines the fault type and determines to send back the fault log; If the match is not successful, the OTA vehicle-side program determines not to send back the fault log.

3. The method according to claim 1, characterized in that The method further comprises: If the packaged log file of the fault log is successfully sent to the server, the OTA vehicle-side program obtains the log information of the fault log and sends the log information to the server; If the packaged log file of the fault log is not successfully sent to the server, the OTA vehicle-side program sends a prompt to the server that the log file upload failed.

4. The method according to claim 3, characterized in that The log information includes the file name of the log file, the file size, the vehicle VIN code of the logistics vehicle, the core type, the vehicle-side path, the corresponding module of the fault of the logistics vehicle, the fault code, the cause of the fault and the upload time.

5. A device for determining a logistics vehicle failure, characterized in that: The device is applied to a logistics vehicle fault determination system, the system includes a logistics vehicle and a server, the logistics vehicle is installed with an over-the-air upgrade OTA vehicle-side program, and the device includes: A fault monitoring module is used for the OTA vehicle-side program to receive a vehicle status message sent by the logistics vehicle when the logistics vehicle fails; A parsing module, used for the OTA vehicle-side program to parse the vehicle status message to obtain the fault code and fault cause of the logistics vehicle; A determination module, used for the OTA vehicle-side program to determine whether to return a fault log according to the fault code and a pre-stored fault information table; The log feedback module is used to, if the fault log is fed back, the OTA vehicle-side program reads the log storage path of the fault log in the fault information table, packages the log file of the fault log, and sends the packaged log file to the server, so that the technician can download the fault log based on the server to analyze and solve the fault.

6. The device according to claim 5, characterized in that The fault information table includes a plurality of fault codes, and the determination module is specifically used for: The OTA vehicle-side program matches the fault code with multiple fault codes in the fault information table one by one. If the match is successful, the OTA vehicle-side program determines the fault type and determines to send back the fault log; If the match is not successful, the OTA vehicle-side program determines not to send back the fault log.

7. The device according to claim 5, characterized in that The device also includes: An acquisition module, configured to, if the packaged log file of the fault log is successfully sent to the server, cause the OTA vehicle-side program to acquire log information of the fault log and send the log information to the server; The upload module is used for sending a log file upload failure prompt to the server by the OTA vehicle-side program if the packaged log file of the fault log is not successfully sent to the server.

8. The device according to claim 7, characterized in that The log information includes the file name of the log file, the file size, the vehicle VIN code of the logistics vehicle, the core type, the vehicle-side path, the corresponding module of the fault of the logistics vehicle, the fault code, the cause of the fault and the upload time.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images