Vehicle fault management method and system

Abstract

The embodiment of the invention provides a vehicle fault management method and system, and relates to the technical field of vehicle after-sales management. The method comprises the steps that each vehicle end packages at least one generated fault code into a fault code packet and sends the fault code packet to a vehicle monitoring end, and each fault code packet is marked with vehicle information of the corresponding vehicle end. And the vehicle monitoring end receives the fault code packets sent by the vehicle ends and analyzes the fault code packets to obtain corresponding fault plaintext data packets, and each fault plaintext data packet comprises at least one piece of fault plaintext data. And storing each fault plaintext data packet into a database. And the after-sales server calls the fault plaintext data packets from the database. And generating a fault reminding table corresponding to each vehicle end according to each fault plaintext data packet based on a preset fault reminding table generation rule. And notifying the corresponding after-sales staff to process the fault based on the fault reminding table. According to the invention, the vehicle fault processing efficiency can be effectively improved.

Description

Technical Field

[0001] This invention relates to the field of vehicle after-sales management technology, and more specifically, to a vehicle fault management method and system. Background Technology

[0002] With the rapid development of new energy technologies, the special vehicle sector has also rapidly entered the era of electrification. New energy special vehicles (such as water trucks and garbage trucks) have quickly seized the market due to their advantages such as low operating costs and high intelligence. However, their highly integrated characteristics have also placed higher demands on after-sales service.

[0003] In related technologies, when a vehicle malfunctions, the corresponding after-sales service personnel are typically notified directly to handle the situation. However, once the after-sales service personnel arrive at the vehicle, they still need to determine the fault and perform the necessary repairs on-site, which means that the efficiency of fault handling needs to be improved. Summary of the Invention

[0004] The present invention aims to, for example, provide a vehicle fault management method and system that can at least partially solve the above-mentioned technical problems.

[0005] The embodiments of the present invention can be implemented as follows: In a first aspect, embodiments of the present invention provide a vehicle fault management method, applied to a vehicle fault management system, the vehicle fault management system including multiple vehicle terminals, a vehicle monitoring terminal, and an after-sales service terminal, wherein the vehicle monitoring terminal is communicatively connected to the after-sales service terminal and each of the vehicle terminals; the method includes: Each of the vehicle terminals packages at least one generated fault code into a fault code packet and sends it to the vehicle monitoring terminal. Each fault code packet is marked with the vehicle information of the corresponding vehicle terminal. The vehicle monitoring terminal receives fault code packets sent by each of the vehicle terminals, parses each fault code packet to obtain the corresponding fault plaintext data packet, and each fault plaintext data packet includes at least one fault plaintext data; and stores each fault plaintext data packet into the database. The after-sales service terminal retrieves each of the fault plaintext data packets from the database; based on the preset fault reminder table generation rules, it generates a fault reminder table corresponding to each of the vehicle terminals according to each of the fault plaintext data packets; and notifies the corresponding after-sales staff to handle the fault based on the fault reminder table.

[0006] Optionally, before each of the vehicle terminals packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal, the method further includes: Each of the aforementioned vehicle terminals monitors multiple vehicle status data within a preset time period; Based on the vehicle status data, determine whether a fault has occurred at the vehicle end; If a fault is determined to occur, a fault code and fault association information corresponding to the fault are generated, and the fault codes and fault association information generated within the preset time period are packaged into the fault code package.

[0007] Optionally, each of the vehicle terminals is equipped with a remote information processor, and each of the vehicle terminals packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal, including: Each of the vehicle terminals packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal through the remote information processor set in each of the vehicle terminals; The vehicle monitoring terminal receives fault code packets sent by each of the vehicle terminals, parses each fault code packet, and obtains the corresponding plaintext fault data packet, including: The vehicle monitoring terminal receives fault code packets sent by each of the vehicle terminals through a remote information processor; Based on the protocol content corresponding to each of the remote information processors, each fault code packet is parsed to obtain the corresponding plaintext fault data and fault association information. The plaintext data of each fault and the fault association information are repackaged into a plaintext data packet of fault.

[0008] Optionally, the after-sales service terminal retrieves each of the fault plaintext data packets from the database, including: The after-sales service terminal retrieves each of the fault plaintext data packets from the database at a preset frequency. The step of generating a fault alert table for each vehicle based on a preset fault alert table generation rule, according to each of the fault plaintext data packets, includes: The after-sales service terminal generates a fault reminder sub-table based on each of the fault plaintext data packets; The fault alert table is generated based on each of the aforementioned fault alert sub-tables and the corresponding vehicle information.

[0009] Optionally, generating a fault alert sub-table based on each of the fault plaintext data packets includes: For each fault plaintext data packet, the after-sales service terminal determines each fault plaintext data in the fault plaintext data packet; Based on the preset fault level, the target fault plaintext data with the highest fault level is determined from each of the fault plaintext data. Based on the preset fault level, each of the fault plaintext data, the fault code corresponding to each of the plaintext data, and the fault association information, the fault reminder sub-table is generated.

[0010] Optionally, the vehicle fault management system further includes multiple after-sales service terminals, each of which is communicatively connected to the after-sales service terminal; the step of notifying the corresponding after-sales personnel to handle the fault based on the fault reminder table includes: Each of the after-sales service terminals receives the fault reminder form and pushes the fault reminder form to the display interface of the after-sales service terminal for display. At the same time, each of the after-sales service terminals notifies the after-sales staff to check the fault reminder table by means of vibration or ringing.

[0011] Optionally, the method further includes: Each of the after-sales service terminals responds to the first operation of the after-sales staff by opening the corresponding fault reminder sub-table; Each of the after-sales service terminals responds to the second operation of the after-sales staff by generating a repair work order so that the corresponding after-sales staff can handle the fault.

[0012] Secondly, embodiments of the present invention provide a vehicle fault management system, which includes multiple vehicle terminals, a vehicle monitoring terminal, and an after-sales service terminal, wherein the vehicle monitoring terminal is communicatively connected to the after-sales service terminal and each of the vehicle terminals. Each of the vehicle terminals is used to package at least one generated fault code into a fault code package and send it to the vehicle monitoring terminal, wherein each fault code package is marked with the vehicle information of the corresponding vehicle terminal. The vehicle monitoring terminal is used to receive fault code packets sent by each of the vehicle terminals, parse each fault code packet to obtain the corresponding fault plaintext data packet, each fault plaintext data packet including at least one fault plaintext data; and store each fault plaintext data packet into the database. The after-sales service terminal is used to retrieve each of the fault plaintext data packets from the database; generate a fault reminder table corresponding to each of the vehicle terminals based on the preset fault reminder table generation rules and each of the fault plaintext data packets; and notify the corresponding after-sales staff to handle the fault based on the fault reminder table.

[0013] Optionally, each of the vehicle terminals is further used for: Monitor the status data of multiple vehicles within a preset time period; Based on the vehicle status data, determine whether a fault has occurred at the vehicle end; If a fault is determined to occur, a fault code and fault association information corresponding to the fault are generated, and the fault codes and fault association information generated within the preset time period are packaged into the fault code package.

[0014] Optionally, each vehicle terminal is equipped with a remote information processor, and each vehicle terminal packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal, including: Each generated fault code is packaged into a fault code package and sent to the vehicle monitoring terminal through the remote information processor set in each vehicle. The step of receiving fault code packets sent by each of the vehicle terminals, parsing each fault code packet to obtain the corresponding plaintext fault data packet includes: Receive fault code packets sent by each of the vehicle terminals through a remote information processor; parse each fault code packet based on the protocol content corresponding to each of the remote information processors to obtain the corresponding plaintext fault data and fault association information; repackage each plaintext fault data and fault association information into a plaintext fault data packet.

[0015] The beneficial effects of the embodiments of the present invention include, for example: A method for vehicle fault management systems is provided. When a fault code is generated at any vehicle, it is packaged and sent to the vehicle monitoring terminal. The vehicle monitoring terminal parses each fault code packet to obtain plaintext fault data packets. The after-sales service terminal retrieves each plaintext fault data packet and generates a corresponding fault alert table to notify after-sales personnel. After-sales personnel only need to receive the fault alert table and then handle the corresponding fault at the corresponding vehicle, eliminating the need for on-site fault confirmation and improving the overall efficiency of fault handling. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is one of the flowcharts of a vehicle fault management method provided in an embodiment of the present invention; Figure 2 This is one of the architecture diagrams of a vehicle fault management system provided in an embodiment of the present invention; Figure 3 This is the second flowchart of a vehicle fault management method provided in an embodiment of the present invention; Figure 4 This is a second architecture diagram of a vehicle fault management system provided in an embodiment of the present invention.

[0018] Icons: 01-Vehicle Fault Management System; 11-Vehicle Monitoring Terminal; 12-Vehicle Terminal; 13-After-Sales Service Terminal; 14-After-Sales Service Terminal. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0020] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0021] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0022] Furthermore, the terms "first" and "second" are used only to distinguish descriptions and should not be interpreted as indicating or implying relative importance.

[0023] It should be noted that, where there is no conflict, the features in the embodiments of the present invention can be combined with each other.

[0024] Although the penetration rate of new energy vehicles in the market is increasing year by year and growing rapidly, it is precisely because of this rapid growth that the problem of disconnect between after-sales service and vehicle sales has been exposed. The high integration and intelligence of vehicles also put forward higher requirements for after-sales service capabilities, especially in the field of special vehicles, where this problem is becoming increasingly prominent.

[0025] Due to the high degree of integration of components in new energy vehicles, simple visual inspections and functional tests during vehicle maintenance are insufficient to identify the root causes of malfunctions and other potential problems. This leads to long repair times, recurrence of previously repaired issues, and frequent rework, resulting in low customer satisfaction and even frequent complaints. Furthermore, maintenance of new energy special-purpose vehicles often requires accessing vehicle data for a comprehensive check to resolve all potential problems at once. Achieving this necessitates highly skilled after-sales service personnel, but currently, there is a disconnect between after-sales service capabilities and the market share of new energy vehicles.

[0026] Based on the above, embodiments of the present invention provide a vehicle fault management method and system, which can effectively alleviate the above-mentioned technical problems.

[0027] This invention provides a vehicle fault management method applied to a vehicle fault management system. The vehicle fault management system includes multiple vehicle terminals, a vehicle monitoring terminal, and an after-sales service terminal. The vehicle monitoring terminal is communicatively connected to the after-sales service terminal and each of the vehicle terminals. The method includes, for example: Figure 1 The following steps are shown: Step S110: Each vehicle terminal packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal, wherein each fault code package is marked with the vehicle information of the corresponding vehicle terminal.

[0028] Step S120: The vehicle monitoring terminal receives fault code packets sent by each of the vehicle terminals, parses each fault code packet to obtain the corresponding fault plaintext data packet, and each fault plaintext data packet includes at least one fault plaintext data; and stores each fault plaintext data packet into the database.

[0029] Step S130: The after-sales service terminal retrieves each of the fault plaintext data packets from the database; based on the preset fault reminder table generation rules, it generates a fault reminder table corresponding to each of the vehicle terminals according to each of the fault plaintext data packets; and notifies the corresponding after-sales staff to handle the fault based on the fault reminder table.

[0030] like Figure 2 The diagram shown is an architecture diagram of a vehicle fault management system 01 provided in an embodiment of the present invention. Each vehicle terminal 12 can represent a new energy special vehicle. The vehicle monitoring terminal 11 is connected to each vehicle terminal 12 via wireless communication. The after-sales service terminal 13 is also connected to the vehicle monitoring terminal 11 via wireless communication.

[0031] In step S110, each vehicle terminal 12 packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal 11. Each fault code package is marked with the vehicle information of the corresponding vehicle terminal 12.

[0032] When a fault occurs at vehicle terminal 12, the controller of vehicle terminal 12 (such as VCU (Vehicle Control Unit)) generates a fault code corresponding to the fault. If more than one fault occurs at the same vehicle terminal 12, the controller of vehicle terminal 12 generates multiple corresponding fault codes, and then packages these fault codes into a fault code package. The vehicle information of vehicle terminal 12 (such as license plate number, vehicle tonnage, vehicle model, etc.) is marked on the fault code package and sent to vehicle monitoring terminal 11.

[0033] Optionally, before each vehicle sends the generated at least one fault code as a fault code package to the vehicle monitoring terminal, the method further includes, for example, Figure 3 The following steps are shown: Step S210: Each vehicle terminal monitors multiple vehicle status data within a preset time period.

[0034] Step S220: Determine whether a fault has occurred on the vehicle side based on the status data of each vehicle.

[0035] Step S230: If a fault is determined to have occurred, generate the fault code and fault association information corresponding to the fault, and package the fault codes and fault association information generated within a preset time period into a fault code package.

[0036] Each vehicle controller 12 can periodically collect vehicle operating status parameters (i.e., vehicle status data) through multiple sensors installed on the vehicle. Based on the fault diagnosis conditions and logic rules preset in its internal program, it can analyze and judge these status parameters in real time. When the monitored status parameters meet specific fault conditions, the vehicle controller generates the corresponding fault code and fault association information (such as fault occurrence time, fault type, fault status, etc.).

[0037] For example, by comparing the collected vehicle status data with a preset threshold, it can be determined whether the vehicle status data is abnormal. If the vehicle status data exceeds the preset upper threshold or falls below the preset lower threshold, it is considered that the vehicle has a corresponding fault, and a corresponding fault code is generated. The VCU sends the fault code to the vehicle monitoring terminal 11. In a specific embodiment, if the VCU detects that conditions such as "music horn communication failure" or "low vehicle air pressure" are triggered, the VCU will generate a corresponding fault code such as 0x000D or 0x003C, package the two fault codes into a fault code package, mark the vehicle information of the vehicle terminal 12, and then send it to the vehicle monitoring terminal 11.

[0038] As an optional implementation, a remote information processor (such as an in-vehicle T-BOX) can be set up in each vehicle terminal 12. When the vehicle terminal 12 needs to send a fault code package, it sends it to the vehicle monitoring terminal 11 through the remote information processor.

[0039] In step S120, the vehicle monitoring terminal 11 receives fault code packets sent by each vehicle terminal 12, parses each fault code packet to obtain the corresponding fault plaintext data packet, and each fault plaintext data packet includes at least one fault plaintext data; and stores each fault plaintext data packet into the database.

[0040] The vehicle monitoring terminal 11 can be a cloud platform set up in the cloud. The vehicle monitoring terminal 11 receives fault code packets sent by each vehicle terminal 12 through the remote information processor in real time, and parses each fault code packet to obtain fault plaintext data packets that staff can directly understand by text, and stores these fault plaintext data packets in the database.

[0041] Optionally, the vehicle monitoring terminal receives fault code packets sent by each vehicle terminal, parses each fault code packet, and obtains the corresponding plaintext fault data packet, including: The vehicle monitoring terminal receives fault code packets sent by each vehicle terminal through the remote information processor.

[0042] Each fault code packet is parsed based on the protocol content corresponding to each remote information processor to obtain the corresponding plaintext fault data and fault association information. The plaintext fault data and fault association information are then repackaged into a plaintext fault data packet.

[0043] In one optional implementation, after receiving fault code packets sent by each vehicle terminal 12 through a remote information processor, the vehicle monitoring terminal 11 can parse the fault code packets based on the protocol content corresponding to each remote information processor, thereby obtaining one or more plaintext fault data and fault association information corresponding to each fault code packet. The plaintext fault data and corresponding fault association information are then repackaged into fault plaintext data packets, unit by unit, sent by the vehicle terminal 12, to obtain fault plaintext data packets.

[0044] In step S130, the after-sales service terminal 13 retrieves each fault plaintext data packet from the database; based on the preset fault reminder table generation rules, it generates a fault reminder table corresponding to each vehicle terminal 12 according to each fault plaintext data packet; and notifies the corresponding after-sales staff to handle the fault based on the fault reminder table.

[0045] The after-sales service terminal 13 retrieves the stored plaintext data packets of each fault from the database of the vehicle monitoring terminal 11, and generates a fault reminder table for each vehicle terminal 12 based on the preset fault reminder table generation rules. Finally, the fault reminder table is used to notify the corresponding after-sales personnel to handle the fault.

[0046] This method achieves remote, automatic, and standardized flow of fault information through a collaborative process involving automatic reporting from the vehicle terminal 12, centralized parsing and storage from the vehicle monitoring terminal 11, and automatic generation of fault reminder forms and notification to after-sales staff from the after-sales service terminal 13. This eliminates the need for after-sales staff to conduct preliminary fault confirmation on-site, thereby significantly improving the overall efficiency of fault handling.

[0047] For example, when the VCU of a vehicle 12 detects a communication failure of the music horn or low air pressure in the vehicle, it will generate a corresponding fault code and report it through the T-BOX. After the vehicle monitoring terminal 11 parses the data, it obtains the plaintext data packet of the fault. The after-sales service terminal 13 then generates a fault reminder table containing information such as the license plate number and fault type and pushes it to the after-sales engineer so that the after-sales engineer can handle the fault more quickly.

[0048] Optionally, the after-sales service server retrieves plaintext data packets for each fault from the database, including: The after-sales service terminal retrieves plaintext data packets of each fault from the database at a preset frequency.

[0049] Based on preset fault alert table generation rules, a fault alert table corresponding to each vehicle is generated according to each fault plaintext data packet, including: The after-sales service system generates a fault alert sub-table based on each fault plaintext data packet. Then, based on each fault alert sub-table and the corresponding vehicle information, a full fault alert table is generated.

[0050] In one optional implementation, the after-sales service terminal 13 can retrieve various fault plaintext data packets from the database at a preset frequency. For example, the after-sales service terminal 13 retrieves fault plaintext data packets at 5-minute intervals after the hour (00:05, 00:10, 00:15, etc.).

[0051] To generate the fault alert table, the after-sales service terminal 13 can be divided into two sub-steps: First, the after-sales service terminal 13 generates a corresponding fault alert sub-table based on each retrieved fault plaintext data packet; second, these generated fault alert sub-tables are integrated with their respective vehicle information to finally form a complete fault alert table containing information from each vehicle terminal 12. This generation method of first generating sub-tables and then summarizing makes the data processing logic clear and facilitates information aggregation and display for individual vehicles.

[0052] Optionally, a fault alert sub-table is generated based on each fault plaintext data packet, including: For each fault plaintext data packet, the after-sales service team identifies the individual fault plaintext data within it.

[0053] Based on the preset fault level, the target fault plaintext data with the highest fault level is determined from all fault plaintext data.

[0054] Based on the preset fault level, plaintext data of each fault, fault codes corresponding to each plaintext data, and associated information of each fault, a fault reminder sub-table is generated.

[0055] In one optional implementation, the after-sales service terminal 13 can determine the various fault plaintext data included in each fault plaintext data packet, and then classify different types of fault plaintext data into levels according to preset fault levels. The fault plaintext data with the highest fault level is determined as the target fault plaintext data. Finally, based on the preset fault level, each fault plaintext data, the fault code corresponding to each plaintext data, and each fault association information, a fault reminder sub-table is generated, as shown in Table 1. Among them, low vehicle air pressure and tire pressure alarm are both target fault plaintext data. When notifying after-sales staff, the target fault plaintext data will be displayed first.

[0056] Table 1 - Fault Alert Subtable

[0057] Optionally, the vehicle fault management system also includes multiple after-sales service terminals, each communicating with the after-sales service terminal. Based on the fault alert table, it notifies the corresponding after-sales personnel to handle the fault, including: Each after-sales service terminal receives the fault alert form and pushes it to the display interface of the after-sales service terminal for display.

[0058] Meanwhile, each after-sales service terminal notifies after-sales staff to check the fault reminder form via vibration or ringing.

[0059] After-sales service terminal 14 can be a portable device that after-sales staff can carry with them, such as a mobile phone, tablet, or laptop. Figure 4 As shown, multiple after-sales service terminals 14 are communicatively connected to after-sales service terminal 13. After-sales service terminal 13 simultaneously sends the generated fault alert table to each after-sales service terminal 14. Upon receiving the fault alert table, each after-sales service terminal 14 displays it on its display interface. While displaying the fault alert table, the after-sales service terminal 14 can also remind after-sales personnel to check the fault alert table through vibration, ringing, and light. The fault alert table can be as shown in Table 2.

[0060] Table 2 - Fault Alert Table

[0061] Optionally, the method further includes: Each after-sales service terminal responds to the first action of the after-sales staff by opening the corresponding fault alert sub-table. The second action of the after-sales staff then generates a repair work order, enabling the appropriate after-sales staff to handle the fault.

[0062] After receiving a prompt from the after-sales service terminal 14, the after-sales staff can open the after-sales service terminal 14 to operate the fault reminder table. The after-sales staff can select the vehicle terminal 12 that needs to be handled from the fault reminder table by swiping the screen and clicking (i.e., the first operation), and click on the license plate number corresponding to the vehicle terminal 12 to make the after-sales service terminal 14 display the corresponding fault reminder sub-table.

[0063] After opening the fault reminder sub-table, if the after-sales staff believes that the fault displayed on the fault reminder sub-table needs to be handled by them immediately, they can generate a repair work order through the second operation on the after-sales service terminal 14.

[0064] Based on the same inventive concept, such as Figure 2 As shown, this embodiment of the invention provides a vehicle fault management system 01, including multiple vehicle terminals 12, a vehicle monitoring terminal 11, and an after-sales service terminal 13. The vehicle monitoring terminal 11 is communicatively connected to the after-sales service terminal 13 and each vehicle terminal 12.

[0065] Each vehicle terminal 12 is used to package at least one generated fault code into a fault code package and send it to the vehicle monitoring terminal 11. Each fault code package is marked with the vehicle information of the corresponding vehicle terminal 12.

[0066] Vehicle monitoring terminal 11 is used to receive fault code packets sent by each vehicle terminal 12, parse each fault code packet to obtain the corresponding fault plaintext data packet, and each fault plaintext data packet includes at least one fault plaintext data. Each fault plaintext data packet is then stored in a database.

[0067] The after-sales service terminal 13 is used to retrieve plaintext data packets for each fault from the database. Based on preset fault alert table generation rules, it generates a fault alert table corresponding to each vehicle terminal 12 according to each plaintext data packet for each fault. Based on the fault alert table, it notifies the corresponding after-sales personnel to handle the fault.

[0068] Optionally, each vehicle terminal 12 is also used for: Monitor the status data of multiple vehicles within a preset time period.

[0069] Based on the status data of each vehicle, determine whether a fault has occurred at vehicle terminal 12.

[0070] If a fault is detected, a fault code and associated information corresponding to the fault are generated, and the fault codes and associated information generated within a preset time period are packaged into a fault code package.

[0071] Optionally, each vehicle terminal 12 is equipped with a remote information processor, and each vehicle terminal 12 packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal 11, including: Each generated fault code is packaged into a fault code package and sent to the vehicle monitoring terminal 11 through the remote information processor set on each vehicle terminal 12.

[0072] Receive fault code packets sent by each vehicle terminal 12, parse each fault code packet to obtain the corresponding plaintext fault data packet, including: Receive fault code packets sent by each vehicle terminal 12 through the remote information processor; parse each fault code packet based on the protocol content corresponding to each remote information processor to obtain the corresponding plaintext fault data and fault association information. Repackage each plaintext fault data and fault association information into a plaintext fault data packet.

[0073] Regarding the aforementioned vehicle fault management system 01, the specific functions of each terminal have been described in detail in the embodiments of the vehicle fault management method provided in this specification, and will not be elaborated upon here.

[0074] The present invention has at least the following beneficial effects: This invention provides a method for a vehicle fault management system. When a fault code is generated at any vehicle, it is packaged and sent to the vehicle monitoring terminal. The vehicle monitoring terminal parses each fault code packet to obtain a plaintext fault data packet. The after-sales service terminal retrieves each plaintext fault data packet and generates a corresponding fault alert table to notify after-sales personnel. After-sales personnel only need to receive the fault alert table and then handle the corresponding fault at the corresponding vehicle, without needing to go to the site for fault confirmation, thus improving the efficiency of the entire fault handling process.

[0075] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative; for example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of the invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0076] In addition, the functional modules in the various embodiments of the present invention can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0077] If the functionality is implemented as a software module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0078] The above are merely specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A vehicle fault management method, characterized in that, An application is made in a vehicle fault management system, which includes multiple vehicle terminals, a vehicle monitoring terminal, and an after-sales service terminal. The vehicle monitoring terminal is communicatively connected to the after-sales service terminal and each of the vehicle terminals. The method includes: Each of the vehicle terminals packages at least one generated fault code into a fault code packet and sends it to the vehicle monitoring terminal. Each fault code packet is marked with the vehicle information of the corresponding vehicle terminal. The vehicle monitoring terminal receives fault code packets sent by each of the vehicle terminals, parses each fault code packet to obtain the corresponding fault plaintext data packet, and each fault plaintext data packet includes at least one fault plaintext data; and stores each fault plaintext data packet into the database. The after-sales service terminal retrieves each of the fault plaintext data packets from the database; based on the preset fault reminder table generation rules, it generates a fault reminder table corresponding to each of the vehicle terminals according to each of the fault plaintext data packets; and notifies the corresponding after-sales staff to handle the fault based on the fault reminder table.

2. The vehicle fault management method as described in claim 1, characterized in that, Before each of the aforementioned vehicle terminals packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal, the method further includes: Each of the aforementioned vehicle terminals monitors multiple vehicle status data within a preset time period; Based on the vehicle status data, determine whether a fault has occurred at the vehicle end; If a fault is determined to occur, a fault code and fault association information corresponding to the fault are generated, and the fault codes and fault association information generated within the preset time period are packaged into the fault code package.

3. The vehicle fault management method as described in claim 1, characterized in that, Each vehicle terminal is equipped with a remote information processor. Each vehicle terminal packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal, including: Each of the vehicle terminals packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal through the remote information processor set in each of the vehicle terminals; The vehicle monitoring terminal receives fault code packets sent by each of the vehicle terminals, parses each fault code packet, and obtains the corresponding plaintext fault data packet, including: The vehicle monitoring terminal receives fault code packets sent by each of the vehicle terminals through a remote information processor; Based on the protocol content corresponding to each of the remote information processors, each fault code packet is parsed to obtain the corresponding plaintext fault data and fault association information. The plaintext data of each fault and the fault association information are repackaged into a plaintext data packet of fault.

4. The vehicle fault management method as described in claim 3, characterized in that, The after-sales service terminal retrieves each of the fault plaintext data packets from the database, including: The after-sales service terminal retrieves each of the fault plaintext data packets from the database at a preset frequency. The step of generating a fault alert table for each vehicle based on a preset fault alert table generation rule, according to each of the fault plaintext data packets, includes: The after-sales service terminal generates a fault reminder sub-table based on each of the fault plaintext data packets; The fault alert table is generated based on each of the aforementioned fault alert sub-tables and the corresponding vehicle information.

5. The vehicle fault management method as described in claim 4, characterized in that, The step of generating a fault alert sub-table based on each of the fault plaintext data packets includes: For each fault plaintext data packet, the after-sales service terminal determines each fault plaintext data in the fault plaintext data packet; Based on the preset fault level, the target fault plaintext data with the highest fault level is determined from each of the fault plaintext data. Based on the preset fault level, each of the fault plaintext data, the fault code corresponding to each of the plaintext data, and the fault association information, the fault reminder sub-table is generated.

6. The vehicle fault management method as described in claim 5, characterized in that, The vehicle fault management system also includes multiple after-sales service terminals, each of which is communicatively connected to the after-sales service terminal; the step of notifying the corresponding after-sales personnel to handle the fault based on the fault reminder table includes: Each of the after-sales service terminals receives the fault reminder form and pushes the fault reminder form to the display interface of the after-sales service terminal for display. At the same time, each of the after-sales service terminals notifies the after-sales staff to check the fault reminder table by means of vibration or ringing.

7. The vehicle fault management method as described in claim 6, characterized in that, The method further includes: Each of the after-sales service terminals responds to the first operation of the after-sales staff by opening the corresponding fault reminder sub-table; Each of the after-sales service terminals responds to the second operation of the after-sales staff by generating a repair work order so that the corresponding after-sales staff can handle the fault.

8. A vehicle fault management system, characterized in that, The vehicle fault management system includes multiple vehicle terminals, a vehicle monitoring terminal, and an after-sales service terminal. The vehicle monitoring terminal is communicatively connected to the after-sales service terminal and each of the vehicle terminals. Each of the vehicle terminals is used to package at least one generated fault code into a fault code package and send it to the vehicle monitoring terminal, wherein each fault code package is marked with the vehicle information of the corresponding vehicle terminal. The vehicle monitoring terminal is used to receive fault code packets sent by each of the vehicle terminals, parse each fault code packet to obtain the corresponding fault plaintext data packet, each fault plaintext data packet including at least one fault plaintext data; and store each fault plaintext data packet into the database. The after-sales service terminal is used to retrieve each of the fault plaintext data packets from the database; generate a fault reminder table corresponding to each of the vehicle terminals based on the preset fault reminder table generation rules and each of the fault plaintext data packets; and notify the corresponding after-sales staff to handle the fault based on the fault reminder table.

9. The vehicle fault management system as described in claim 8, characterized in that, Each of the aforementioned vehicle terminals is also used for: Monitor the status data of multiple vehicles within a preset time period; Based on the vehicle status data, determine whether a fault has occurred at the vehicle end; If a fault is determined to occur, a fault code and fault association information corresponding to the fault are generated, and the fault codes and fault association information generated within the preset time period are packaged into the fault code package.

10. The vehicle fault management system as described in claim 8, characterized in that, Each vehicle terminal is equipped with a remote information processor. Each vehicle terminal packages at least one generated fault code into a fault code package and sends it to the vehicle monitoring terminal, including: Each generated fault code is packaged into a fault code package and sent to the vehicle monitoring terminal through the remote information processor set in each vehicle. The step of receiving fault code packets sent by each of the vehicle terminals, parsing each fault code packet to obtain the corresponding plaintext fault data packet includes: Receive fault code packets sent by each of the vehicle terminals through a remote information processor; parse each fault code packet based on the protocol content corresponding to each of the remote information processors to obtain the corresponding plaintext fault data and fault association information; repackage each plaintext fault data and fault association information into a plaintext fault data packet.

Images