Vehicle relay fault management method, device and equipment and storage medium

Abstract

The application discloses a whole vehicle relay fault management method, device and equipment and a storage medium, relates to the relay management technical field, and the method comprises the following steps: obtaining relay grouping data and relay set data of a whole vehicle relay according to a preset relay grouping strategy; obtaining periodical message data according to the relay grouping data and the relay set data; and performing whole vehicle fault management according to the periodical message data. Through relay grouping management, corresponding message design, gateway transmission and vehicle machine processing, the application realizes rapid positioning and efficient diagnosis of faults, solves the technical problem of how to accurately position a faulty relay, and improves the efficiency of fault diagnosis and maintenance and the reliability of the system.

Description

Technical Field

[0001] This application relates to the technical field of relay management, and in particular to a method, device, equipment and storage medium for managing relay faults in a vehicle. Background Technology

[0002] With the increasing electrification of automobiles, the number of relays in vehicles has significantly increased, placing higher demands on relay fault management. As a key component in the automotive electrical system, the stability and reliability of relays directly affect the overall performance and safety of the vehicle. Currently, the most common method for automotive fault diagnosis is the OBD-II fault diagnosis system. This system has a driving recorder function, capable of monitoring and reporting various system states of the vehicle, including emission control, engine performance, and electrical systems. When the system detects an anomaly, it stores a fault code (DTC), which can be read using specialized scanning tools, helping technicians quickly locate the problem. However, the OBD-II system has several limitations, such as the inability to store very short-cycle and intermittent faults in a timely manner, reliance on external tools for fault code reading and clearing, and the provision of relatively general fault information that may not accurately pinpoint the specific cause of the problem. Furthermore, remote diagnostic technology also has some drawbacks, such as the risk of wireless data transmission being attacked and leaked; the reliance on network connectivity, with unstable networks or areas without coverage rendering it unusable; and the high cost of implementing and maintaining remote diagnostic technology, including data traffic fees and server storage requirements.

[0003] Therefore, how to accurately locate faulty relays and improve fault diagnosis efficiency is an urgent problem to be solved. Summary of the Invention

[0004] The main objective of this application is to provide a method, device, equipment, and storage medium for managing vehicle relay faults, aiming to solve the technical problem of how to accurately locate faulty relays and improve fault diagnosis efficiency.

[0005] To achieve the above objectives, this application proposes a method for managing vehicle relay faults, the method comprising:

[0006] Obtain relay grouping data and relay set data for the entire vehicle relays according to the preset relay grouping strategy;

[0007] Periodic message data is obtained based on the relay group data and the relay set data;

[0008] Vehicle fault management is performed based on the periodic message data.

[0009] In one embodiment, the step of obtaining relay group data and relay set data of the vehicle relays according to a preset relay grouping strategy includes:

[0010] The functional and location information of the vehicle's relays, as well as the vehicle's network structure, are obtained according to a preset relay grouping strategy.

[0011] Based on the functional information, the location information, and the network structure, the vehicle relays are grouped to obtain relay group data and relay set data.

[0012] In one embodiment, the step of grouping the vehicle relays according to the functional information, the location information, and the network structure to obtain relay group data and relay set data includes:

[0013] Based on the functional information and the location information, the vehicle relays are grouped to obtain relay grouping data;

[0014] Based on the network structure and the relay group data, the relay set is set to obtain the relay set data.

[0015] In one embodiment, the step of performing vehicle fault management based on the periodic message data includes:

[0016] The instruction data and relay status data are obtained based on the periodic message data;

[0017] Vehicle fault diagnosis and predictive maintenance are performed based on the instruction data and the relay status data.

[0018] In one embodiment, the instruction data includes instruction content and issuance time, the relay status data includes relay status and relay confirmation time, and the step of performing vehicle fault diagnosis and predictive maintenance based on the instruction data and the relay status data includes:

[0019] When the instruction content is inconsistent with the relay status or the difference between the relay confirmation time and the issuance time is greater than a preset delay threshold, abnormal data is marked and the abnormal data is recorded in the vehicle log.

[0020] Vehicle fault diagnosis and predictive maintenance are performed based on the vehicle's logs.

[0021] In one embodiment, the step of performing vehicle fault diagnosis and predictive maintenance based on the vehicle system log includes:

[0022] Analyze the historical status and fault modes of the relays based on the abnormal data in the vehicle's log;

[0023] Predict relay lifespan and failure points based on the historical status and failure modes;

[0024] Execute the corresponding preset maintenance strategy based on the relay lifespan and the fault point.

[0025] In one embodiment, the step of obtaining periodic message data based on the relay group data and the relay set data includes:

[0026] The relay identifier and the relay group identifier are obtained based on the relay group data and the relay set data;

[0027] The periodic message data of the corresponding relay is obtained based on the relay identifier and the relay group identifier.

[0028] Furthermore, to achieve the above objectives, this application also proposes a vehicle relay fault management device, the device comprising:

[0029] The relay grouping module is used to obtain relay grouping data and relay set data of the vehicle relays according to a preset relay grouping strategy;

[0030] The message acquisition module is used to acquire periodic message data based on the relay group data and the relay set data;

[0031] The fault management module is used to manage vehicle faults based on the periodic message data.

[0032] In addition, to achieve the above objectives, this application also proposes a vehicle relay fault management device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the vehicle relay fault management method described above.

[0033] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the vehicle relay fault management method described above.

[0034] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the vehicle relay fault management method described above.

[0035] This application provides a method for managing vehicle relay faults. The method includes: acquiring relay group data and relay set data of the vehicle relays according to a preset relay grouping strategy; acquiring periodic message data based on the relay group data and the relay set data; and performing vehicle fault management based on the periodic message data. In summary, this application, through relay group management and corresponding message design, gateway transmission, and vehicle-mounted system processing, achieves rapid fault location and efficient diagnosis, solves the technical problem of accurately locating faulty relays, and improves the efficiency of fault diagnosis and maintenance, as well as the reliability of the system. Attached Figure Description

[0036] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0037] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a flowchart illustrating the first embodiment of the vehicle relay fault management method of this application.

[0039] Figure 2 This is a flowchart illustrating the second embodiment of the vehicle relay fault management method of this application.

[0040] Figure 3 This is a flowchart illustrating the third embodiment of the vehicle relay fault management method of this application.

[0041] Figure 4 This is a schematic diagram of the module structure of the vehicle relay fault management device according to an embodiment of this application;

[0042] Figure 5 This is a schematic diagram of the equipment structure of the hardware operating environment involved in the vehicle relay fault management method in this application embodiment.

[0043] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0044] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0045] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0046] The main solution of this application embodiment is: to obtain relay group data and relay set data of the vehicle relays according to a preset relay grouping strategy; to obtain periodic message data according to the relay group data and the relay set data; and to perform vehicle fault management according to the periodic message data.

[0047] With the increasing electrification of automobiles, the number of relays in vehicles has significantly increased, placing higher demands on relay fault management. As a key component in the automotive electrical system, the stability and reliability of relays directly affect the overall performance and safety of the vehicle. Currently, the most common method for automotive fault diagnosis is the OBD-II fault diagnosis system. This system has a driving recorder function, capable of monitoring and reporting various system states of the vehicle, including emission control, engine performance, and electrical systems. When the system detects an anomaly, it stores a fault code (DTC), which can be read using specialized scanning tools, helping technicians quickly locate the problem. However, the OBD-II system has several limitations, such as the inability to store very short-cycle and intermittent faults in a timely manner, reliance on external tools for fault code reading and clearing, and the provision of relatively general fault information that may not accurately pinpoint the specific cause of the problem. Furthermore, remote diagnostic technology also has some drawbacks, such as the risk of wireless data transmission being attacked and leaked; the reliance on network connectivity, with unstable networks or areas without coverage rendering it unusable; and the high cost of implementing and maintaining remote diagnostic technology, including data traffic fees and server storage requirements. Therefore, how to accurately locate faulty relays and improve fault diagnosis efficiency is an urgent problem to be solved.

[0048] This application achieves rapid fault location and efficient diagnosis through relay group management and corresponding message design, gateway transmission and vehicle-mounted system processing. It solves the technical problem of how to accurately locate faulty relays, and improves the efficiency of fault diagnosis and maintenance as well as the reliability of the system.

[0049] It should be noted that the executing entity in this embodiment can be a vehicle relay fault management system, a computing service device with data processing, network communication, and program execution functions, or an electronic device capable of implementing the aforementioned vehicle relay fault management functions, etc. This embodiment does not specifically limit it in this way. The following uses a vehicle relay fault management system as an example to describe this embodiment and the following embodiments.

[0050] Based on this, the embodiments of this application provide a method for managing vehicle relay faults, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the vehicle relay fault management method of this application.

[0051] In this embodiment, the vehicle relay fault management method includes steps S10 to S30:

[0052] Step S10: Obtain the relay group data and relay set data of the whole vehicle relays according to the preset relay grouping strategy.

[0053] It should be noted that in this step, the system categorizes the vehicle's relays according to a preset relay grouping strategy (i.e., based on the relays' function and location). Specifically, relays are divided into different groups, such as power management, controller, motor, and high-voltage system groups. Relays within each group have similar functions or are located in similar positions. Understandably, this facilitates data management and fault diagnosis. For example, for an electric vehicle, its relays can be divided into the following groups: Vehicle Low-Voltage System Relay Group 1: Includes relays such as IGN1, IGN2, IGN3, and ACC, which are mainly responsible for the vehicle's low-voltage power management. Vehicle Actuator Motor Relay Group 2: Includes relays for the fuel tank cap, charging port, sunroof, wipers, compressor, and doors and windows, which control various actuator motors in the vehicle. Vehicle High-Voltage System Relay Group 3: Covers high-voltage system relays such as DC-DC, BMS, VCU, MCU, and GCU, used for high-voltage battery management and motor control in electric vehicles. After assigning a unique identifier to each relay group, the system also retrieves preset relay set data. These aggregated data sets correspond to different network segments of the vehicle network, ensuring efficient and accurate data transmission.

[0054] Additionally, it should be noted that the preset relay grouping strategy is not static; it can be adjusted and optimized according to different vehicle models or configurations.

[0055] Step S20: Obtain periodic message data based on the relay group data and the relay set data.

[0056] It should be noted that in this step, once the relay grouping and set data are set, the system will match a dedicated message for each relay set based on the relay grouping data and the number of relay sets. These messages will be used to periodically update the relay status information, including relay commands, feedback, and physical measurements (such as voltage, current, and temperature). For example, for the IGN1 relay in relay group 1 of the vehicle's low-voltage system, a periodic status update message can be designed, containing the IGN1 relay's status information, such as whether it is on, its on timestamp, and physical measurements. These messages will be sent at preset time intervals to ensure that the main controller can monitor the relay status in real time.

[0057] Additionally, it should be noted that before the message matching process, each message is designed with signal integrity and redundancy in mind to handle potential data loss or errors. Furthermore, each message is assigned a unique identifier (such as a Transaction ID) to clearly trace the relationship between instructions and responses in subsequent data processing.

[0058] In one feasible implementation, step S20 specifically includes:

[0059] Step S201: Obtain the relay identifier and the relay group identifier based on the relay group data and the relay set data.

[0060] It should be noted that relay group data refers to information that groups vehicle relays according to their functions (such as power management, controller itself, motor, and high-voltage system) and physical locations. Relay set data, on the other hand, is a specific set assigned to each relay group. These sets correspond to different network segments of the vehicle network, ensuring efficient and accurate data transmission. Specifically, in this step, the system matches a specific relay with its corresponding relay group based on the relay group data and relay set data. The system can obtain the relay identifier (RelayID) and relay group identifier (Relay Group ID) for each relay. For example, suppose the vehicle's low-voltage system relay group 1 contains four relays: IGN1, IGN2, IGN3, and ACC, and they are assigned unique identifiers 0x1, 0x2, 0x3, and 0x4, respectively. When the system reads the group data for relay IGN1, it can automatically match it with the relay identifier 0x1 and the relay group identifier (indicating that it belongs to low-voltage system relay group 1).

[0061] Additionally, it's important to note that the Relay ID is a code used to uniquely identify each relay, enabling the system to accurately identify and operate specific relays. The RelayGroup ID, on the other hand, identifies the group to which a relay belongs, facilitating group management of relays and thus improving data processing efficiency.

[0062] Step S202: Obtain the periodic message data of the corresponding relay based on the relay identifier and the relay group identifier.

[0063] It should be noted that periodic message data refers to messages containing relay status information that the system periodically sends. These messages are transmitted through a specific message structure (such as the periodic status update message described above), and contain information such as relay commands, feedback, and physical quantity measurements. Specifically, in this step, the system matches the corresponding relay periodic message data based on the relay identifier and relay group identifier. Then, the system parses the message to extract the required relay status information. For example, assuming the system needs to obtain the periodic message data of relay IGN1, it can retrieve the corresponding message using the relay identifier 0x1 and the relay group identifier (such as Group-01). This message data contains the IGN1 command content (such as "Turn ON"), the command issuance time, the status confirmation (such as "ON") and the status confirmation time, as well as physical quantity measurements (such as voltage, current, and temperature).

[0064] Step S30: Perform vehicle fault management based on the periodic message data.

[0065] It should be noted that in this step, after receiving these periodic message data, the system unpacks and processes them. By parsing the various signals in the messages, the system can monitor the status of the relays in real time and detect potential faults. Specifically, if the main controller finds that the status of a relay has not changed in several consecutive message cycles, or if there is a significant delay between the status confirmation time and the command issuance time, the system will determine that there is a problem with the relay and trigger the fault diagnosis process. The fault diagnosis process includes further signal analysis and circuit testing based on the message data to accurately locate the fault. Once the fault is confirmed, the main controller will record the fault information and take corresponding maintenance measures. These measures include, but are not limited to, sending warning messages to the driver, triggering the power-off mechanism of the safety protection to protect the vehicle from further damage, or recommending that the vehicle be sent to a repair shop for inspection.

[0066] This embodiment provides a method for managing vehicle relay faults. The method includes: acquiring relay group data and relay set data of the vehicle relays according to a preset relay grouping strategy; acquiring periodic message data based on the relay group data and the relay set data; and performing vehicle fault management based on the periodic message data. In summary, this embodiment, through relay group management and corresponding message design, gateway transmission, and vehicle-mounted system processing, achieves rapid fault location and efficient diagnosis, solves the technical problem of accurately locating faulty relays, and improves the efficiency of fault diagnosis and maintenance, as well as the reliability of the system.

[0067] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 , Figure 2 This is a flowchart illustrating the second embodiment of the vehicle relay fault management method of this application. Step S10 specifically includes:

[0068] Step S101: Obtain the functional and location information of the vehicle relays and the network structure of the vehicle according to the preset relay grouping strategy.

[0069] It's important to note that in this step, the system collects and organizes relevant information about all vehicle relays according to a preset relay grouping strategy. This information primarily includes relay functional information, location information, and the vehicle's network structure. Functional information refers to the specific tasks or roles that relays perform in the vehicle's electrical system, such as power management, controller power supply, motor control, or high-voltage system control. Location information refers to the physical location of the relays within the vehicle. Understandably, location information helps the system determine the physical distance and connection relationships between relays, thereby determining the data transmission path. The vehicle's network structure refers to the connection methods and communication protocols between various parts of the vehicle's electrical system. This includes the division between different network segments, communication rates, and data formats. Understanding the vehicle's network structure helps the system develop more reasonable data transmission strategies for relay grouping and aggregation.

[0070] Step S102: Group the vehicle relays according to the functional information, the location information, and the network structure to obtain relay group data and relay set data.

[0071] It's important to note that in this step, the system groups the vehicle's relays based on the acquired functional information, location information, and network structure. The purpose of grouping is to group relays with similar functions, adjacent locations, or close network connections into the same group for unified management and data transmission. During the grouping process, the system uses preset grouping rules, such as grouping by relay function type (e.g., power management, motor control). Then, it refines and adjusts the initial grouping based on the relay's location information and network structure. For example, for relays that are adjacent in location and have close network connections, the system will group them into the same set to achieve more efficient data transmission and fault location. After grouping, the system generates relay group data and relay set data. This data includes the grouping information, set information, and associated network address and identifier for each relay. For example, the system groups all power management-related relays into one group and assigns them a specific set. Then, based on the relay's location and network connection, the system further subdivides the relays within that group into several subsets, each corresponding to a specific network segment and data transmission path.

[0072] In one feasible implementation, step S102 specifically includes:

[0073] Step A10: Group the vehicle relays according to the functional information and the location information to obtain relay group data.

[0074] It should be noted that in this step, the system initially classifies each relay on the vehicle based on its functional and location information. Functional information mainly refers to the role the relay plays in the vehicle's electrical system, such as power management, controller self-control, motor drive, or high-voltage system control. Location information refers to the physical installation location of the relay on the vehicle. Specifically, the system groups relays with similar functional attributes together, forming initial functional groups. For example, all relays responsible for power management (such as IGN1, IGN2, IGN3, ACC, etc.) are grouped into vehicle low-voltage system relay group 1. Then, based on the location information, the relays within the functional groups are fine-tuned to form the final relay groups, ensuring that relays within the same group are also physically close, facilitating subsequent wiring and data transmission. For example, vehicle actuator motor relay group 2 includes fuel tank cap relays, charging port relays, sunroof relays, wiper relays, compressor relays, and door / window relays. Although these relays have different functions, they are all used to control the vehicle's actuator motors, and their locations on the vehicle are relatively concentrated, therefore they are grouped together.

[0075] Step A20: Set the relay set according to the network structure and the relay group data to obtain the relay set data.

[0076] It's important to note that in this step, the system groups relays within the same group and located in the same or adjacent network segments into a set based on the relay grouping data and network structure. This ensures that relays within each set can transmit data through an efficient communication path, reducing the possibility of data loss and errors. Relay set data refers to a collection that records information such as the relay identifier, set identifier, and the network segment to which the set belongs. Specifically, the system assigns a unique identifier to each set (e.g., Relay-Group-01, Relay-Group-02, etc.) and records the mapping relationship between these identifiers and the corresponding relays and network segments in the set data. In this way, the system can quickly locate any relay using the set data and understand its group, set, and network segment information, facilitating subsequent data transmission and fault diagnosis.

[0077] In this embodiment, by integrating relay functions, location information, and the vehicle network structure, efficient grouping and aggregation settings of relays are achieved, providing a clear data transmission path for relay management, improving the accuracy and efficiency of fault diagnosis, and also providing a foundation for subsequent message design, data transmission, and fault diagnosis, thereby improving fault diagnosis efficiency and system reliability.

[0078] Based on the first and second embodiments of this application, in the third embodiment of this application, the content that is the same as or similar to that in embodiments one and two above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 3 , Figure 3 This is a flowchart illustrating the third embodiment of the vehicle relay fault management method of this application. Step S30 specifically includes:

[0079] Step S301: Obtain instruction data and relay status data based on the periodic message data.

[0080] It should be noted that periodic message data is sent periodically from various relay groups in the vehicle network to the gateway, and then transmitted from the gateway to the vehicle's infotainment system. The system first receives and parses these message data, and then extracts command data and relay status data based on the message structure. Command data mainly includes the command content (Command) and the issuance time (CommandTimestamp). For example, a command might indicate "Open sunroof" (Command: Turn ON), and be sent at a timestamp of "2023-10-01 12:00:00". This command data indicates that the system attempted to open the sunroof at the specified time. Relay status data includes the relay status (StatusConfirmation) and the relay confirmation time (Status Timestamp). For example, if the sunroof relay successfully executes the opening operation, it will return status data indicating that the relay status is "ON" (Status Confirmation: ON) and confirming the timestamp as "2023-10-01 12:00:01". This status data confirms that the command has been successfully executed and provides information on the execution time.

[0081] Understandably, by extracting and analyzing this instruction data and relay status data, the system can monitor the operating status and response time of each relay in the vehicle network in real time, providing basic data for subsequent fault diagnosis and predictive maintenance.

[0082] Step S302: Perform vehicle fault diagnosis and predictive maintenance based on the instruction data and the relay status data.

[0083] It's important to note that in this step, after acquiring the command data and relay status data, the system further analyzes and processes this data to achieve vehicle fault diagnosis and predictive maintenance. For example, for vehicle fault diagnosis, the system compares the consistency between the command data and the relay status data. If the commands are inconsistent, it indicates that the relay has malfunctioned. At this time, the vehicle system records the fault information and triggers the corresponding fault diagnosis process, such as sending a fault alarm and generating a fault diagnosis report. For predictive maintenance, the system predicts the relay's lifespan and potential failure points based on historical data and preset algorithm models. Once a potential fault risk is predicted, the vehicle system will notify the owner or maintenance personnel in advance so that timely maintenance or replacement of the relay can be performed, thereby avoiding the occurrence of sudden faults.

[0084] Additionally, it should be noted that the vehicle's fault diagnosis and predictive maintenance functions rely on the design of relay groups and messages, as well as the corresponding collected historical data. By continuously accumulating experience with historical data, the vehicle's infotainment system can continuously improve the accuracy of fault diagnosis and the effectiveness of predictive maintenance.

[0085] In one feasible implementation, step S302 specifically includes:

[0086] Step B10: When the instruction content is inconsistent with the relay status or the difference between the relay confirmation time and the issuance time is greater than a preset delay threshold, mark the abnormal data and record the abnormal data in the vehicle log.

[0087] It's important to note that when the vehicle's infotainment system receives command data (including command content and issuance time) from the main controller, it compares this data with the actual status data of the relays after execution (including relay status and status confirmation time). If the command content and relay status are inconsistent—for example, the command requires the relay to turn ON, but the relay status is OFF—or the difference between the relay confirmation time and the command issuance time exceeds a preset delay threshold (e.g., the set normal response time is 50 milliseconds, but the actual delay reaches 100 milliseconds)—then the vehicle's infotainment system will mark these inconsistent or delayed data as abnormal data. The system will record this abnormal data in a log, which includes not only detailed information about the abnormal data but also the time of occurrence, the source address, and the destination address, for subsequent in-depth analysis and fault diagnosis.

[0088] Additionally, it should be noted that the preset delay threshold is set comprehensively based on factors such as the communication speed of the vehicle network and the normal response time of different relays, to ensure that faults can be detected in a timely manner without causing false alarms due to excessive sensitivity.

[0089] Understandably, the purpose of this step is to accurately locate and handle potential faults when they occur, preventing them from escalating into more serious consequences.

[0090] Step B20: Perform vehicle fault diagnosis and predictive maintenance based on the vehicle log.

[0091] It's important to note that in this step, the system analyzes the vehicle's infotainment logs and performs vehicle-wide fault diagnosis based on the abnormal data recorded in the logs. Specifically, by analyzing the type and frequency of abnormal data, it can identify specific relay groups or relays with potential faults, allowing for targeted repairs or replacements. Furthermore, the data in the vehicle's infotainment logs can also be used for predictive maintenance. By analyzing historical data, common characteristics or patterns before relay failures can be identified, such as trends in relay physical quantities and the frequency of abnormal data occurrences. When these characteristics or patterns reappear, maintenance can be performed proactively to prevent failures.

[0092] In one feasible implementation, step B20 specifically includes:

[0093] Step B201: Analyze the historical status and fault modes of the relays based on the abnormal data in the vehicle log.

[0094] It should be noted that in this step, the system parses the vehicle's logs to extract abnormal data related to the relay status. This data includes the relay's command issuance time, status confirmation time, physical quantity measurements (such as voltage, current, and temperature), and any feedback that deviates from the expected status. By analyzing this abnormal data, the system can trace the relay's historical status and identify potential fault modes.

[0095] Additionally, it should be noted that historical states refer to the sum of all states and events experienced by the relay over a past period, including normal and abnormal states. Fault modes, on the other hand, refer to the characteristics exhibited by the relay when a fault occurs; these behaviors and characteristics can be identified and summarized through the analysis of abnormal data.

[0096] Step B202: Predict the relay life and failure point based on the historical status and the failure mode.

[0097] It should be noted that after identifying the relay's failure mode, the system predicts the relay's lifespan and the point of failure based on historical states and failure modes. For example, for the IGN1 relay, the system uses machine learning algorithms (such as time series analysis and regression analysis) to model its historical state data to predict its future state change trends. By analyzing the model's output, the system can estimate the remaining lifespan of the IGN1 relay and predict the time and location when it may fail again.

[0098] Additionally, it should be noted that relay life refers to the effective operating time or number of cycles a relay can maintain under normal operating conditions. The fault point, on the other hand, refers to the specific location where the faulty relay is located.

[0099] Step B203: Execute the corresponding preset maintenance strategy based on the relay lifespan and the fault point.

[0100] It's important to note that in this step, after determining the relay's lifespan and potential failure point, the system executes corresponding preset maintenance strategies based on this information. These strategies include preventative maintenance, restorative maintenance, and relay replacement. For example, for the IGN1 relay, if the predicted lifespan indicates a short remaining lifespan, the system will proactively perform preventative maintenance tasks, such as prompting the user to perform necessary maintenance or repairs, to extend its lifespan and reduce the likelihood of failure. If the predicted lifespan indicates that the relay has already failed or is about to malfunction, restorative maintenance should be performed, prompting the user to immediately repair or replace the relay to ensure the normal operation of the vehicle's electrical system.

[0101] Additionally, it should be noted that the preset maintenance strategy is a specific maintenance measure and plan formulated based on the relay's historical status, failure modes, relay lifespan, and failure points. Understandably, this strategy aims to proactively identify and resolve potential problems to optimize maintenance costs and improve overall vehicle performance and user experience. Furthermore, as the vehicle's operating environment and model change, the preset maintenance strategy can also be dynamically adjusted and optimized according to actual conditions.

[0102] In this embodiment, by monitoring, recording and analyzing the status data of each relay, timely fault detection and diagnosis are achieved, improving diagnostic efficiency, enhancing system reliability and reducing normal maintenance costs.

[0103] This application also provides a vehicle relay fault management device; please refer to... Figure 4 The vehicle relay fault management device includes:

[0104] Relay grouping module 10 is used to obtain relay grouping data and relay set data of the vehicle relays according to a preset relay grouping strategy;

[0105] Message acquisition module 20 is used to acquire periodic message data based on the relay group data and the relay set data;

[0106] The fault management module 30 is used to perform vehicle fault management based on the periodic message data.

[0107] The vehicle relay fault management device provided in this application, employing the vehicle relay fault management method in the above embodiments, can solve the technical problem of how to accurately locate faulty relays and improve fault diagnosis efficiency. Compared with the prior art, the beneficial effects of the vehicle relay fault management device provided in this application are the same as those of the vehicle relay fault management method provided in the above embodiments, and other technical features in the vehicle relay fault management device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0108] In one embodiment, the relay grouping module 10 is further configured to obtain the functional information and location information of the vehicle relays and the network structure of the vehicle according to a preset relay grouping strategy; and to group the vehicle relays according to the functional information, the location information and the network structure to obtain relay group data and relay set data.

[0109] In one embodiment, the relay grouping module 10 is further configured to group the vehicle relays according to the functional information and the location information to obtain relay grouping data; and to set a relay set according to the network structure and the relay grouping data to obtain relay set data.

[0110] In one embodiment, the message acquisition module 20 is further configured to obtain a relay identifier and a relay group identifier based on the relay group data and the relay set data; and to obtain periodic message data of the corresponding relay based on the relay identifier and the relay group identifier.

[0111] In one embodiment, the fault management module 30 is further configured to obtain instruction data and relay status data based on the periodic message data; and to perform vehicle fault diagnosis and predictive maintenance based on the instruction data and the relay status data.

[0112] In one embodiment, the fault management module 30 is further configured to mark abnormal data and record the abnormal data in the vehicle log when the instruction content is inconsistent with the relay status or when the difference between the relay confirmation time and the issuance time is greater than a preset delay threshold; and to perform vehicle fault diagnosis and predictive maintenance based on the vehicle log.

[0113] In one embodiment, the fault management module 30 is further configured to analyze the historical status and fault mode of the relay based on the abnormal data in the vehicle log; predict the relay life and fault point based on the historical status and fault mode; and execute the corresponding preset maintenance strategy based on the relay life and fault point.

[0114] This application provides a vehicle relay fault management device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the vehicle relay fault management method in the above embodiment 1.

[0115] The following is for reference. Figure 5 The diagram illustrates a structural schematic suitable for implementing a vehicle relay fault management device according to embodiments of this application. The vehicle relay fault management device in embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The vehicle relay fault management device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0116] like Figure 5As shown, the vehicle relay fault management device may include a processing unit 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the vehicle relay fault management device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the vehicle relay fault management device to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows a vehicle relay fault management device with various systems, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems can be implemented alternatively.

[0117] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0118] The vehicle relay fault management device provided in this application, employing the vehicle relay fault management method described in the above embodiments, can solve the technical problem of how to accurately locate faulty relays and improve fault diagnosis efficiency. Compared with the prior art, the beneficial effects of the vehicle relay fault management device provided in this application are the same as those of the vehicle relay fault management method provided in the above embodiments, and other technical features of this vehicle relay fault management device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0119] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0120] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0121] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the vehicle relay fault management method in the above embodiments.

[0122] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having 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 devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0123] The aforementioned computer-readable storage medium may be included in the vehicle relay fault management device; or it may exist independently and not be assembled into the vehicle relay fault management device.

[0124] The aforementioned computer-readable storage medium carries one or more programs. When the aforementioned one or more programs are executed by the vehicle relay fault management device, the vehicle relay fault management device: obtains relay group data and relay set data of the vehicle relays according to a preset relay grouping strategy; obtains periodic message data according to the relay group data and the relay set data; and performs vehicle fault management according to the periodic message data.

[0125] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0126] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated 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 the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0127] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0128] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described vehicle relay fault management method. This solves the technical problem of accurately locating faulty relays and improving fault diagnosis efficiency. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the vehicle relay fault management method provided in the above embodiments, and will not be repeated here.

[0129] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the vehicle relay fault management method described above.

[0130] The computer program product provided in this application can solve the technical problem of how to accurately locate faulty relays and improve fault diagnosis efficiency. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the vehicle relay fault management method provided in the above embodiments, and will not be repeated here.

[0131] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for managing relay faults in a vehicle, characterized in that, The method includes: The functional and location information of the vehicle's relays, as well as the vehicle's network structure, are obtained according to a preset relay grouping strategy. Based on the functional information, the location information, and the network structure, the vehicle relays are grouped to obtain relay group data and relay set data; Periodic message data is obtained based on the relay group data and the relay set data; Instruction data and relay status data are obtained based on the periodic message data. The instruction data includes the instruction content and the issuance time, and the relay status data includes the relay status and the relay confirmation time. When the instruction content is inconsistent with the relay status or the difference between the relay confirmation time and the issuance time is greater than a preset delay threshold, abnormal data is marked and the abnormal data is recorded in the vehicle log. Vehicle fault diagnosis and predictive maintenance are performed based on the vehicle's logs.

2. The method as described in claim 1, characterized in that, The step of grouping the vehicle relays according to the functional information, the location information, and the network structure to obtain relay group data and relay set data includes: Based on the functional information and the location information, the vehicle relays are grouped to obtain relay grouping data; Based on the network structure and the relay group data, the relay set is set to obtain the relay set data.

3. The method as described in claim 1, characterized in that, The steps for performing vehicle fault diagnosis and predictive maintenance based on the vehicle system logs include: Analyze the historical status and fault modes of the relays based on the abnormal data in the vehicle's log; Predict relay lifespan and failure points based on the historical status and failure modes; Execute the corresponding preset maintenance strategy based on the relay lifespan and the fault point.

4. The method as described in claim 1, characterized in that, The step of obtaining periodic message data based on the relay group data and the relay set data includes: The relay identifier and the relay group identifier are obtained based on the relay group data and the relay set data; The periodic message data of the corresponding relay is obtained based on the relay identifier and the relay group identifier.

5. A vehicle relay fault management device, characterized in that, The device includes: The relay grouping module is used to obtain the functional information and location information of the vehicle relays and the network structure of the vehicle according to a preset relay grouping strategy; and to group the vehicle relays according to the functional information, the location information and the network structure to obtain relay group data and relay set data. The message acquisition module is used to acquire periodic message data based on the relay group data and the relay set data; The fault management module is used to obtain instruction data and relay status data based on the periodic message data. The instruction data includes instruction content and issuance time, and the relay status data includes relay status and relay confirmation time. When the instruction content and the relay status are inconsistent, or when the difference between the relay confirmation time and the issuance time is greater than a preset delay threshold, abnormal data is marked and recorded in the vehicle system log. The module performs vehicle fault diagnosis and predictive maintenance based on the vehicle system log.

6. A vehicle relay fault management device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the vehicle relay fault management method as described in any one of claims 1 to 4.

7. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the vehicle relay fault management method as described in any one of claims 1 to 4.

Images