Vehicle fault message pushing method and device, electronic equipment and storage medium

Abstract

This invention discloses a method, apparatus, electronic device, and storage medium for pushing vehicle fault messages, relating to the field of vehicle network technology. The method includes: generating vehicle fault messages based on fault code data and vehicle-related data; determining the dynamic fault level of the vehicle based on the fault code data and vehicle-related data using a dynamic evaluation model; determining the push recipients and push method based on the dynamic fault level; and personalizedly pushing the vehicle fault message to the push recipients according to the push method. The push recipients include vehicle drivers, fleet management platforms, or service station work order systems. By combining collected fault code data and vehicle-related data from multiple perspectives, a precise dynamic fault level of the vehicle is determined. The push recipients and push method are dynamically selected based on the dynamic fault level to achieve personalized and accurate push while reducing push interference to different recipients.

Description

Technical Field

[0001] This invention relates to the field of vehicle networking technology, and in particular to a method, apparatus, electronic device, and storage medium for pushing vehicle fault messages. Background Technology

[0002] Commercial vehicle operation scenarios are characterized by high loads, long mileage, and multiple operating conditions. Therefore, handling commercial vehicle malfunctions plays a very important role in ensuring safe driving.

[0003] However, current vehicles typically rely on onboard terminals to passively collect fault codes, which are only triggered when the driver actively queries the system or when the vehicle arrives for maintenance. This leads to untimely handling of emergency faults and frequent safety accidents. While the industry has proposed proactive fault information push notifications to address these issues, existing methods only determine the vehicle's fault level based on a single fault code. This can result in high-risk faults being underestimated and low-risk faults being overemphasized, leading to frequent, irrelevant warnings. Furthermore, the commercial vehicle operation chain is long, involving fleet managers, drivers, and maintenance service stations, but current push notification methods lack a collaborative mechanism between these parties, further reducing fault handling efficiency. Summary of the Invention

[0004] This invention provides a method, apparatus, electronic device, and storage medium for pushing vehicle fault messages, so as to achieve accurate push of vehicle fault messages.

[0005] According to a first aspect of the present invention, a method for pushing vehicle fault messages is provided. The method includes: collecting vehicle fault code data and vehicle association data, and generating a vehicle fault message based on the fault code data and the vehicle association data, wherein the vehicle association data includes real-time operating status, environmental data and historical maintenance records. The dynamic fault level of the vehicle is determined based on the fault code data and the vehicle-related data using a dynamic evaluation model. The push recipients and push methods are determined based on the dynamic fault level, and the vehicle fault messages are pushed to the push recipients in a personalized manner according to the push method. The push recipients include vehicle drivers, fleet management platforms, or service station work order systems.

[0006] According to another aspect of the present invention, a vehicle malfunction message push device is provided, the device comprising: The vehicle fault message generation module is used to collect vehicle fault code data and vehicle-related data, and generate vehicle fault messages based on the fault code data and vehicle-related data. The vehicle-related data includes real-time operating status, environmental data and historical maintenance records. The dynamic fault level determination module is used to determine the dynamic fault level of a vehicle based on the fault code data and the vehicle-related data using a dynamic evaluation model. The message push module is used to determine the push target and push method according to the dynamic fault level, and to push the vehicle fault message to the push target in a personalized manner according to the push method. The push target includes vehicle drivers, fleet management platforms or service station work order systems.

[0007] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: one or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any embodiment of the present invention.

[0008] According to another aspect of the present invention, a storage medium for computer-executable instructions is provided, on which a computer program is stored, which, when executed by a processor, implements the method described in any of the embodiments of the present invention.

[0009] The technical solution of this invention determines the accurate dynamic fault level of a vehicle by combining the collected fault code data and vehicle-related data from multiple perspectives. Based on the dynamic fault level, it dynamically selects the push target and push method to achieve personalized and accurate push while reducing push interference to different targets.

[0010] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart of a vehicle fault message push method according to Embodiment 1 of the present invention; Figure 2 This is a flowchart of another method for pushing vehicle fault messages according to Embodiment 2 of the present invention; Figure 3 This is a schematic diagram of the structure of a vehicle fault message push device according to Embodiment 3 of the present invention; Figure 4 This is a structural block diagram of an electronic device provided in Embodiment 4 of the present invention. Detailed Implementation

[0013] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0014] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, apparatus, product, or terminal device that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or terminal devices.

[0015] Example 1 Figure 1 This is a flowchart of a vehicle fault message push method provided in Embodiment 1 of the present invention. This embodiment is applicable to the situation of pushing vehicle fault messages. The method can be executed by a vehicle fault message push device, which can be implemented in hardware and / or software, and can be integrated into an electronic device with data processing capabilities. Figure 1 As shown, the method includes: S101 collects vehicle fault code data and vehicle-related data, and generates vehicle fault messages based on the fault code data and vehicle-related data.

[0016] Optionally, after collecting vehicle fault code data and vehicle-related data, the process also includes: filtering out duplicate fault codes in the fault code data to obtain filtered fault code data; obtaining the current collection time, and deleting historical fault codes from the filtered fault code data based on the current collection time to obtain preprocessed fault code data.

[0017] Specifically, the system collects vehicle fault code data in real time from a dedicated vehicle terminal. This system supports protocols commonly used in commercial vehicles, such as J1939 or ISO 15765-4, to ensure effective communication with the commercial vehicle and guarantee the accuracy of the collected fault code data. The fault code data includes fault codes generated during vehicle operation at different times. Each fault code is a string (consisting of one letter and four numbers). The first letter represents the system where the fault occurred, such as the powertrain (P), body system (B), chassis system (C), and network communication system (U). The first number represents the source of the code; for example, 0 indicates a universal code applicable to all brands of vehicles, while 1, 2, and 3 indicate manufacturer-specific codes defined by a specific vehicle manufacturer. Subsequent numbers describe the specific fault. For example, fault code P0301, where P indicates a problem with the powertrain, 0 indicates that it is a general standard code, 3 usually refers to the ignition system or misfire detection, and 0 indicates that a misfire was detected in cylinder 1. In addition, the collected fault code data usually includes multiple fault codes. This embodiment does not limit the number or format of fault codes included in the fault code data. As long as they can reflect the vehicle's fault information, they are all within the protection scope of this application.

[0018] In addition, in this embodiment, to ensure the accuracy of reasoning after acquiring fault code data, the fault code data undergoes two rounds of filtering to retain the most valuable information. The first layer of filtering removes duplicate fault codes, resulting in filtered fault code data. The purpose of this first layer is to prevent system overload; if the same fault is reported three times within one minute, the system only retains the first instance, ignoring subsequent duplicates to avoid interfering with the judgment. The second layer of filtering deletes historical fault codes, resulting in pre-processed fault code data. The system compares this data with historical maintenance records; if the fault has been reported and repaired before, it cannot be considered a new fault, ensuring that the data reflects the current, real problem.

[0019] Specifically, fault codes alone are usually insufficient to accurately determine the severity of a vehicle's fault. For instance, the same fault code appearing while climbing a hill under load has a completely different severity than one appearing while idling at a standstill. Generally, a fault code appearing while climbing a hill under load poses a greater risk to driving safety. This embodiment collects vehicle-related data along with fault code data. This data includes real-time operating status, environmental data, and historical maintenance records. Real-time operating status can include driving speed, load, or geographical location, while environmental data can include temperature or road conditions. This embodiment can package the acquired fault code data and vehicle-related data together to provide a comprehensive basis for accurately determining the dynamic fault level. Of course, this embodiment is merely illustrative and does not limit the specific content of the collected vehicle-related data.

[0020] Optionally, a vehicle fault message is generated based on fault code data and vehicle-related data, including: determining the vehicle fault type based on fault code data, determining the vehicle location information based on real-time operating status, and combining the fault type and location information to generate a vehicle fault message.

[0021] It is worth mentioning that, in this embodiment, after obtaining fault code data and vehicle association data, the system extracts each fault code contained in the fault code data and retrieves the vehicle's fault type from the fault code query fault type list. The fault type list contains the correspondence between fault codes and fault types, converting the fault codes into fault names that users can recognize. Of course, this embodiment is merely an example and does not limit the specific method of determining fault types. Furthermore, this embodiment also extracts the vehicle's current latitude and longitude coordinates or specific road location information from the real-time operating status. The obtained fault type and location are combined to generate a complete vehicle fault message. Since the vehicle fault information includes the vehicle's location information, when the vehicle fault information is pushed to the service station work order system, the service station work order system can allocate repair work orders to the nearest service station based on the location information, thereby improving the efficiency of subsequent vehicle repairs. In addition, the vehicle fault information in this embodiment uses a combination of fault codes and location information, mainly applied in vehicle networks, fleet management systems, and vehicle remote diagnostic systems, ensuring that rescue personnel or repair centers can know immediately what fault the vehicle has and where to go for rescue and repair, thereby improving vehicle safety.

[0022] S102, based on the dynamic evaluation model, determines the dynamic fault level of the vehicle according to fault code data and vehicle-related data.

[0023] Optionally, the dynamic fault level of the vehicle is determined based on the fault code data and vehicle association data using a dynamic evaluation model, including: determining the fault severity score based on the fault code data and vehicle association data using a dynamic evaluation model; and determining the dynamic fault level based on the fault severity score and the fault level classification list, wherein the dynamic fault level includes emergency faults, high-priority faults and low-priority faults.

[0024] Specifically, in this embodiment, when a vehicle malfunction is determined based on fault code data, some malfunctions are more serious, while others are minor malfunctions that do not affect the safe driving of the vehicle. For such minor malfunctions, there is usually no need to deal with them immediately, because in this embodiment, a dynamic evaluation model will score the severity of the malfunction based on the fault code data and vehicle-related data, thereby deciding whether to stop the vehicle for rescue immediately or wait until maintenance. The dynamic assessment model evaluates vehicle fault severity based on four dimensions: fault codes, real-time operating status, environmental data, and historical maintenance records. Different weights are assigned to each dimension. For example, different fault codes correspond to different fault types; faults involving power, braking, and special-purpose components receive higher weights due to their direct impact on life safety. Real-time operating status includes both stationary and moving states, with moving states typically receiving higher weights than stationary states. For instance, engine overheating during driving can lead to cylinder scoring, while the risk is lower when the vehicle is parked. Environmental data receives dynamically increased weights under high-temperature or heavy-load conditions, as minor issues can easily escalate into major accidents under harsh conditions. Historical maintenance records show increased weights for faults recurring within the past 30 days, indicating deep-seated problems or inadequate previous repairs requiring close monitoring. In this implementation, after inputting fault code data and vehicle-related data into the dynamic assessment model, the model determines the vehicle's fault severity score based on the received data and the corresponding weights for each dimension.

[0025] It should be noted that this implementation method determines the dynamic fault level based on the fault severity score, and specifically, the fault level classification list can be queried based on the fault severity score. The fault level classification list includes the correspondence between scores and levels, as shown in Table 1 below, which is an example of the fault level classification list: Table 1 The system uses a table to look up the dynamic fault level corresponding to the fault severity score. Emergency faults require immediate attention, such as a brake system malfunction while driving, necessitating immediate stopping and calling for assistance to avoid life-threatening situations. High-priority faults require prompt attention, such as an engine overheating under heavy load, requiring immediate unloading or inspection to prevent further damage. Low-priority faults can be addressed later, such as a malfunctioning interior reading light while parked in a garage, which does not affect driving and can be repaired during the next maintenance check. This implementation uses three fault levels as an example; in actual applications, the specific number of levels is not limited and can be set according to the required accuracy of the push notification.

[0026] It is worth mentioning that, in determining the vehicle fault level in this embodiment, it does not rely solely on fault codes, but combines multiple factors such as vehicle condition, road conditions, weather, and historical maintenance records. This makes the determined fault level more accurate, facilitates a comprehensive understanding of the vehicle's current fault status, and provides a foundation for subsequent personalized push notifications.

[0027] S103 determines the push target and push method based on the dynamic fault level, and pushes the vehicle fault message to the push target in a personalized manner according to the push method.

[0028] Optionally, the push recipients and push methods can be determined based on the dynamic fault level, including: when the dynamic fault level is an emergency fault, the push recipients include vehicle drivers, fleet management platforms, or service station work order systems; the push method for vehicle drivers is to provide pop-up notifications, sound alarms, and forced confirmations on the vehicle driver application; the push method for fleet management platforms is to combine SMS and email pushes; and the push method for service station work order systems is to display repair work orders on the service station work order system.

[0029] Optionally, when the push target is the service station work order system, the vehicle fault message is pushed to the push target in a personalized manner according to the push method, including: pushing the vehicle fault message to the service station work order system in the form of a repair work order, so that the service station work order system can determine the target repair resource and allocate the repair work order to the target repair resource, wherein the target repair resource includes the target service station and the target repair personnel.

[0030] Specifically, in this implementation, after determining the dynamic fault level, different push targets and push methods are determined according to the different levels to push the previously generated vehicle fault messages. For emergency faults, such as brake failure, all objects related to the vehicle need to be pushed, namely the vehicle driver, fleet management platform, and service station work order system, to ensure that everyone is immediately aware, forces access, and prevents accidents from occurring. Specifically, the push methods for vehicle drivers include pop-up notifications, audible alarms, and forced confirmation to ensure that the vehicle driver sees the vehicle fault message; the push methods for the fleet management platform include SMS push and email push, to ensure that vehicle management personnel can monitor the faulty vehicle in real time based on the SMS or email received on the platform; and for the service station work order system, repair work orders are automatically generated and displayed in a timely manner on the service station work order system.

[0031] It's important to note that by sending repair work orders to the service station's work order system, the service station can know in advance what kind of fault the vehicle has, its location, and its past repair history before the vehicle even arrives. This allows for the rapid customization of a repair plan, and when the vehicle arrives, repairs can be immediately carried out according to the pre-defined plan. Furthermore, the service station's work order system, upon receiving a work order, dynamically allocates repair resources based on the availability of work bays and the skills of repair personnel, shortening the fault handling time. For example, urgent faults are prioritized for allocation to available work bays and senior technicians, while high-priority faults are assigned to regular work bays. Moreover, if no work bays are available at the service station, the system can pre-determine the nearest alternative service station based on the vehicle's location information to further reduce waiting time for vehicle repairs.

[0032] Optionally, the push recipients and push methods are determined based on the dynamic fault level, including: when the dynamic fault level is a high-priority fault, the push recipients include vehicle drivers and the fleet management platform; the push method for vehicle drivers is a pop-up notification on the vehicle driver application, and the push method for the fleet management platform is an SMS push; when the dynamic fault level is a low-priority fault, the push recipients include vehicle drivers and the push method is storage in the message center of the vehicle driver application.

[0033] Specifically, for high-priority faults, such as engine overheating, push notifications are only sent to vehicle drivers and fleet management platforms. For drivers, the notification method is limited to pop-up alerts; for fleet management platforms, the notification method includes SMS messages. For low-priority faults, a silent recording mode is adopted. The push notification method stores the vehicle fault information only in the application's message center to reduce interference, allowing drivers to decide when to perform repairs during their free time. In summary, this implementation adopts different push strategies for different fault levels. For faults affecting driving safety, push notifications are sent to as many people as possible through multiple channels to ensure the vehicle is stopped and repaired as quickly as possible. For minor faults that do not pose a threat to driving safety, interference with different parties is minimized, and only the driver needs to be notified without affecting driving, avoiding waste of push resources and ineffective push notifications.

[0034] The technical solution of this invention determines the accurate dynamic fault level of a vehicle by combining the collected fault code data and vehicle-related data from multiple perspectives. Based on the dynamic fault level, it dynamically selects the push target and push method to achieve personalized and accurate push while reducing push interference to different targets.

[0035] Example 2 Figure 2 This is a flowchart of another method for pushing vehicle fault messages according to an embodiment of the present invention. Based on the above embodiment, after pushing the vehicle fault message to the target audience using the same push method, this embodiment further includes: acquiring full-process data of the fault handling for the vehicle fault message, and generating a processing report based on the full-process data; sending the processing report to a cloud server, and receiving a parameter optimization strategy generated by the cloud server based on the processing report; and adjusting the parameters of the dynamic evaluation model according to the parameter optimization strategy. Figure 2 As shown, the method includes: S201 collects vehicle fault code data and vehicle-related data, and generates vehicle fault messages based on the fault code data and vehicle-related data.

[0036] Optionally, after collecting vehicle fault code data and vehicle-related data, the process also includes: filtering out duplicate fault codes in the fault code data to obtain filtered fault code data; obtaining the current collection time, and deleting historical fault codes from the filtered fault code data based on the current collection time to obtain preprocessed fault code data.

[0037] Optionally, a vehicle fault message is generated based on fault code data and vehicle-related data, including: determining the vehicle fault type based on fault code data, determining the vehicle location information based on real-time operating status, and combining the fault type and location information to generate a vehicle fault message.

[0038] S202, based on a dynamic evaluation model, determines the dynamic fault level of a vehicle according to fault code data and vehicle-related data.

[0039] Optionally, the dynamic fault level of the vehicle is determined based on the fault code data and vehicle association data using a dynamic evaluation model, including: determining the fault severity score based on the fault code data and vehicle association data using a dynamic evaluation model; and determining the dynamic fault level based on the fault severity score and the fault level classification list, wherein the dynamic fault level includes emergency faults, high-priority faults and low-priority faults.

[0040] S203 determines the push recipients and push methods based on the dynamic fault level, and pushes vehicle fault messages to the push recipients in a personalized manner according to the push method.

[0041] Optionally, the push recipients and push methods can be determined based on the dynamic fault level, including: when the dynamic fault level is an emergency fault, the push recipients include vehicle drivers, fleet management platforms, or service station work order systems; the push method for vehicle drivers is to provide pop-up notifications, sound alarms, and forced confirmations on the vehicle driver application; the push method for fleet management platforms is to combine SMS and email pushes; and the push method for service station work order systems is to display repair work orders on the service station work order system.

[0042] Optionally, when the push target is the service station work order system, the vehicle fault message is pushed to the push target in a personalized manner according to the push method, including: pushing the vehicle fault message to the service station work order system in the form of a repair work order, so that the service station work order system can determine the target repair resource and allocate the repair work order to the target repair resource, wherein the target repair resource includes the target service station and the target repair personnel.

[0043] Optionally, the push recipients and push methods are determined based on the dynamic fault level, including: when the dynamic fault level is a high-priority fault, the push recipients include vehicle drivers and the fleet management platform; the push method for vehicle drivers is a pop-up notification on the vehicle driver application, and the push method for the fleet management platform is an SMS push; when the dynamic fault level is a low-priority fault, the push recipients include vehicle drivers and the push method is storage in the message center of the vehicle driver application.

[0044] S204: Obtain the entire fault handling process data for vehicle fault messages, and generate a processing report based on the entire fault handling process data.

[0045] Upon completion of the current fault handling, the entire fault handling process data is acquired. This data includes fault codes, fault types, confirmation of the pushed targets, and execution of maintenance strategies. This embodiment does not limit the content included in the fault handling process data. The information contained in the fault handling process data is parsed and processed, including key information extraction, specified parameter calculation, and invalid information deletion. A processing report is generated based on the parsed data. This report includes key parameter indicators from fault push and confirmation to maintenance, such as average response time, repaired parts, and maintenance duration. This embodiment does not limit the specific content included in the processing report.

[0046] S205 sends the processing report to the cloud server and receives the parameter optimization strategy generated by the cloud server based on the processing report.

[0047] Specifically, the system sends the aforementioned processing report to the cloud server. The cloud server uses big data and intelligent algorithms to analyze the processing report and retrieves case information corresponding to vehicles with the same fault from the database. Finally, it generates a parameter optimization strategy and sends it to the local system. The parameter optimization strategy can include specific adjustments to the weights in the dynamic evaluation model. For example, if the cloud server finds that engine failures occur more frequently in winter, it determines that the weights in the dynamic evaluation model corresponding to low temperatures in the environmental data need to be increased. Of course, this embodiment is only an example and does not limit the specific content of the parameter optimization strategy.

[0048] S206, Adjust the parameters of the dynamic evaluation model according to the parameter optimization strategy.

[0049] Specifically, when the system receives the parameter optimization strategy sent by the cloud server, it automatically adjusts the parameters of the dynamic evaluation model based on the optimization strategy. For example, the system initially considered "slight engine vibration" to be a low-priority issue (30 points). However, cloud-based analysis reveals that many vehicles recently suffered from "cylinder seizure" due to untimely handling of "slight vibration," leading to major repairs. The cloud server then issues a parameter optimization strategy, and the local system increases the weight of "engine vibration." Therefore, the next time "slight vibration" is encountered, the system will directly classify it as a high-priority issue and issue an early warning. Thus, it can be seen that the fault handling in this implementation is a closed-loop optimization, that is, recording all process data and feeding it back to the cloud, continuously optimizing the push strategy and resource allocation rules, improving system adaptability, making the system's fault diagnosis more accurate, the push more timely, and the repair efficiency higher.

[0050] This implementation supports commercial vehicle protocols such as J1939, and cleans data by combining operational status and environmental data to ensure the accuracy of fault information; it integrates fault code types, operational status, historical records, and environmental data, and optimizes weights through machine learning to achieve precise classification; it dynamically selects push channels and content based on fault level and role permissions (driver, fleet manager, service station) to reduce information interference; and it connects to the service station management system through API interface, combining workstation availability and maintenance personnel skills to achieve efficient matching of maintenance resources.

[0051] The technical solution of this invention determines the accurate dynamic fault level of a vehicle by combining the collected fault code data and vehicle-related data from multiple perspectives. Based on the dynamic fault level, it dynamically selects the push target and push method to achieve personalized and accurate push while reducing push interference to different targets.

[0052] Example 3 Figure 3 This is a schematic diagram of a vehicle fault message push device provided in an embodiment of the present invention. Figure 3 As shown, the device includes: a vehicle fault message generation module 310, a dynamic fault level determination module 320, and a message push module 330.

[0053] The vehicle fault message generation module 310 is used to collect vehicle fault code data and vehicle-related data, and generate vehicle fault messages based on the fault code data and vehicle-related data. The vehicle-related data includes real-time operating status, environmental data and historical maintenance records. The dynamic fault level determination module 320 is used to determine the dynamic fault level of a vehicle based on fault code data and vehicle-related data using a dynamic evaluation model. The message push module 330 is used to determine the push recipients and push methods based on the dynamic fault level, and to push vehicle fault messages to the push recipients in a personalized manner according to the push method. The push recipients include vehicle drivers, fleet management platforms or service station work order systems.

[0054] Optionally, the device also includes a fault code processing and filtering module, used to filter out duplicate fault codes in the fault code data and obtain filtered fault code data. Obtain the current acquisition time, and based on the current acquisition time, delete historical fault codes from the filtered fault code data to obtain preprocessed fault code data.

[0055] Optionally, a vehicle fault message generation module is used to determine the fault type of the vehicle based on fault code data and to determine the vehicle's location information based on real-time operating status. The fault type and location information are combined to generate a vehicle fault message.

[0056] Optionally, a dynamic fault severity determination module is used to determine the fault severity score based on fault code data and vehicle-related data using a dynamic evaluation model; Dynamic fault levels are determined based on fault severity scores and fault level classification lists. These dynamic fault levels include emergency faults, high-priority faults, and low-priority faults.

[0057] Optionally, the message push module includes a push target and push method determination unit, used to determine the push target, including vehicle drivers, fleet management platform or service station work order system, when the dynamic fault level is an emergency fault. The push notification method for vehicle drivers has been determined to be a pop-up notification, an audible alarm, and mandatory confirmation within the vehicle driver application. The push notification method for the fleet management platform was determined to be a combination of SMS and email. The method for pushing repair work orders to the service station work order system has been determined to be to display the repair work orders on the service station work order system.

[0058] Optionally, the message push module includes a push unit for pushing vehicle fault messages to the service station work order system in the form of a repair work order, so that the service station work order system can identify the target repair resource and allocate the repair work order to the target repair resource, wherein the target repair resource includes the target service station and the target repair personnel.

[0059] Optionally, the push target and push method determination unit is used to determine the push targets, including vehicle drivers and fleet management platforms, when the dynamic fault level is a high-priority fault. The push notification method for vehicle drivers has been determined to be a pop-up notification in the vehicle driver application, and the push notification method for the fleet management platform has been determined to be SMS push. When the dynamic fault level is a low-priority fault, the push recipients are determined to include vehicle drivers, and the push method is to store the message in the message center of the vehicle driver application.

[0060] Optionally, the device also includes a parameter adjustment module for acquiring fault handling process data for vehicle fault messages and generating a processing report based on the fault handling process data. Send the processing report to the cloud server and receive the parameter optimization strategy generated by the cloud server based on the processing report; The parameters of the dynamic evaluation model are adjusted according to the parameter optimization strategy.

[0061] The vehicle fault message push device provided in this embodiment of the invention can execute the vehicle fault message push method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0062] Example 4 Figure 4 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0063] The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the invention described and / or claimed herein.

[0064] like Figure 4As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0065] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other electronic devices through computer networks such as the Internet and / or various telecommunications networks.

[0066] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the method for pushing vehicle fault messages.

[0067] That is, the system collects vehicle fault code data and vehicle-related data, and generates vehicle fault messages based on the fault code data and vehicle-related data. The vehicle-related data includes real-time operating status, environmental data and historical maintenance records. The dynamic fault level of a vehicle is determined based on fault code data and vehicle-related data using a dynamic evaluation model. The push targets and push methods are determined based on the dynamic fault level, and vehicle fault messages are pushed to the push targets in a personalized manner according to the push method. The push targets include vehicle drivers, fleet management platforms or service station work order systems.

[0068] In some embodiments, the vehicle malfunction message push method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the vehicle malfunction message push method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the vehicle malfunction message push method by any other suitable means (e.g., by means of firmware).

[0069] Various embodiments of the apparatuses and techniques described above herein can be implemented in digital electronic circuit devices, integrated circuit devices, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), device-on-a-chip (SoC) devices, complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable device including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage device, at least one input device, and at least one output device, and transmitting data and instructions to the storage device, the at least one input device, and the at least one output device.

[0070] Computer programs used to implement the vehicle fault message push method of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to the processor of a general-purpose computer, a special-purpose computer, or other business-uninterrupted data migration device, such that when executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The computer programs can be executed entirely on the machine, partially on the machine, as a standalone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0071] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution apparatus, device, or electronic device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage electronics, magnetic storage electronics, or any suitable combination thereof.

[0072] To provide interaction with a user, the devices and techniques described herein can be implemented on an electronic device having: a display device (e.g., a touchscreen) for displaying information to the user; and buttons through which the user can provide input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0073] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0074] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A push method of a vehicle trouble message, characterized by, The method includes: Collect vehicle fault code data and vehicle-related data, and generate vehicle fault messages based on the fault code data and vehicle-related data. The vehicle-related data includes real-time operating status, environmental data, and historical maintenance records. The dynamic fault level of the vehicle is determined based on the fault code data and the vehicle-related data using a dynamic evaluation model. The push recipients and push methods are determined based on the dynamic fault level, and the vehicle fault messages are pushed to the push recipients in a personalized manner according to the push method. The push recipients include vehicle drivers, fleet management platforms, or service station work order systems.

2. The method of claim 1, wherein, After collecting the vehicle's fault code data and vehicle-related data, the following is also included: The duplicate fault codes in the fault code data are filtered to obtain the filtered fault code data. Obtain the current acquisition time, and based on the current acquisition time, delete historical fault codes from the filtered fault code data to obtain preprocessed fault code data.

3. The method of claim 1, wherein, The step of generating a vehicle fault message based on the fault code data and the vehicle association data includes: The fault type of the vehicle is determined based on the fault code data, and the location information of the vehicle is determined based on the real-time operating status. The vehicle fault message is generated by combining the fault type and the location information.

4. The method of claim 1, wherein, The determination of the vehicle's dynamic fault level based on the dynamic evaluation model according to the fault code data and the vehicle correlation data includes: Based on the dynamic evaluation model, a fault severity score is determined according to the fault code data and the vehicle-related data; The dynamic fault level is determined based on the fault severity score and fault level classification list, wherein the dynamic fault level includes emergency faults, high-priority faults, and low-priority faults.

5. The method of claim 1, wherein, The step of determining the push target and push method based on the dynamic fault level includes: When the dynamic fault level is an emergency fault, the push recipients are determined to include vehicle drivers, fleet management platforms, or service station work order systems. The push notification method for the vehicle driver is determined to be a pop-up notification, an sound alarm, and forced confirmation on the vehicle driver application; The push notification method for the fleet management platform was determined to be a combination of SMS and email. The push method for the service station work order system is determined to be to display the repair work orders on the service station work order system.

6. The method of claim 5, wherein, When the push target is the service station work order system, the step of personalizedly pushing the vehicle fault message to the push target in accordance with the push method includes: The vehicle malfunction message is pushed to the service station work order system in the form of a repair work order, so that the service station work order system can identify the target repair resource and assign the repair work order to the target repair resource, wherein the target repair resource includes the target service station and the target repair personnel.

7. The method of claim 1, wherein, The step of determining the push target and push method based on the dynamic fault level includes: When the dynamic fault level is a high-priority fault, the push targets are determined to include vehicle drivers and fleet management platforms; The push notification method for the vehicle driver is determined to be a pop-up notification on the vehicle driver application, and the push notification method for the fleet manager platform is determined to be a text message. When the dynamic fault level is a low-priority fault, it is determined that the push object includes the vehicle driver and the push method is to store it in the message center of the vehicle driver application.

8. The method of claim 1, wherein, After pushing the vehicle malfunction message to the push recipient according to the push method, the method further includes: Acquire the complete fault handling process data for the vehicle fault message, and generate a processing report based on the complete fault handling process data; The processing report is sent to the cloud server, and the parameter optimization strategy generated by the cloud server based on the processing report is received. The parameters of the dynamic evaluation model are adjusted according to the parameter optimization strategy.

9. A push apparatus of vehicle trouble information, characterized by comprising: The device includes: The vehicle fault message generation module is used to collect vehicle fault code data and vehicle-related data, and generate vehicle fault messages based on the fault code data and vehicle-related data. The vehicle-related data includes real-time operating status, environmental data and historical maintenance records. The dynamic fault level determination module is used to determine the dynamic fault level of a vehicle based on the fault code data and the vehicle-related data using a dynamic evaluation model. The message push module is used to determine the push target and push method according to the dynamic fault level, and to push the vehicle fault message to the push target in a personalized manner according to the push method. The push target includes vehicle drivers, fleet management platforms or service station work order systems.

10. An electronic device, comprising: The electronic device includes: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-8.

11. A storage medium of computer executable instructions, on which a computer program is stored, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-8.

Images