A system and method involving vehicle active safety warning and remote services
By using a vehicle active safety early warning system to monitor and provide remote warnings in real time, the problem of component damage caused by overloading and high torque operation in new energy logistics vehicles has been solved, improving vehicle safety and maintenance efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- ZHEJIANG UFO AUTOMOBILE MFG CO LTD
- Filing Date
- 2026-03-11
- Publication Date
- 2026-06-30
AI Technical Summary
Existing vehicle remote monitoring systems lack proactive early warning mechanisms and cannot effectively prevent damage to key components of new energy logistics vehicles caused by overloading and high torque operation. Traditional maintenance methods rely on regular maintenance or repairs after a failure occurs, lacking prior warning.
Design a vehicle active safety warning system that monitors vehicle operating data in real time through the vehicle control unit (VCU), sets torque and load thresholds, accumulates high-risk states, and uploads warning information to the cloud using the remote communication module (TBOX). The cloud server processes the warning information and triggers service processes, and the server displays the warning information and provides service solutions.
It enables real-time monitoring and remote early warning of high-risk vehicle conditions, reminding users to conduct timely inspections to prevent damage to critical components such as leaf springs and rear axles, thereby improving vehicle safety and maintenance efficiency.
Smart Images
Figure CN122308322A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of automotive control, and more specifically to a system and method for active safety warning and remote services for vehicles. Background Technology
[0002] With the rapid development of the logistics industry, operational efficiency and cost control have become core concerns for fleet managers and individual vehicle owners. However, in actual operation, logistics vehicles, especially new energy logistics vehicles, often face the following severe challenges:
[0003] 1. In pursuit of maximizing the efficiency of a single trip, the phenomenon of overloading logistics vehicles is rampant despite repeated prohibitions. When vehicles operate under conditions exceeding their rated load for extended periods, critical load-bearing components such as the chassis, leaf springs, rear axle housing, and main reducer are subjected to alternating stresses far exceeding design standards. This prolonged overload condition can easily lead to serious mechanical failures such as leaf spring fatigue fracture, rear axle housing deformation or cracking, and gear wear in the main reducer.
[0004] 2. For new energy logistics vehicles, the motor has the output characteristics of constant torque at low speeds and constant power at high speeds. When the vehicle starts under heavy load, climbs hills, or accelerates to overtake, the motor often outputs high torque, especially the gears in the rear axle transmission system. Under high torque conditions, the contact stress on the tooth surface and the bending stress at the tooth root increase sharply. Each high-torque operation will cause microscopic damage to accumulate inside the gears. When the cumulative time of this high-torque condition reaches a certain threshold, the microscopic damage will expand into macroscopic pitting, spalling, or even tooth breakage. Traditional maintenance methods rely on regular maintenance or repair after a failure occurs, lacking proactive warning.
[0005] At present, existing vehicle remote monitoring systems are mostly focused on fault diagnosis and location, lacking proactive early warning and service mechanisms based on reliability test data.
[0006] In summary, a system and method involving vehicle active safety warning and remote services are proposed to address the problems mentioned in the background. Summary of the Invention
[0007] The purpose of this invention is to provide a system involving active safety warning and remote service for vehicles, including an on-board unit, a cloud terminal, and a service terminal. The on-board unit includes a vehicle control unit (VCU) and a remote information communication terminal (TBOX). The VCU is connected to the motor controller, battery management system (BMS), sensors, and electronic control unit via a CAN bus to collect vehicle operating data in real time and perform high-risk state judgment, cumulative counting, threshold comparison, and warning triggering logic. The TBOX is connected to the VCU via a CAN bus and is used to upload the warning information triggered by the VCU and the vehicle identification information to the cloud terminal via a mobile communication network.
[0008] The cloud includes a database and a cloud server. The cloud server is used to receive, process and store the warning data uploaded by TBOX and trigger preset service processes. The database is used to store historical data such as vehicle files, warning records, and service records.
[0009] The server receives and displays the warning message transmitted from the cloud.
[0010] Further specifying the steps, the details are as follows:
[0011] Step S1: Perform system initialization and calibration, and pre-set calibration parameters;
[0012] Step S2: Perform real-time data acquisition and status assessment;
[0013] Step S3: Trip data recording and processing;
[0014] In step S4, the VCU and remote communication work together to perform early warning judgment and triggering;
[0015] Step S5: Perform early warning reset and service follow-up.
[0016] Further specifying, the calibration parameter preset in step S1 includes:
[0017] High torque range: Defines the motor output torque as being continuously greater than T_high as the "high torque" state;
[0018] High torque cumulative time threshold T_total_threshold: corresponds to the risk of fatigue damage to the rear axle gears.
[0019] Cumulative time; Overload judgment threshold: by monitoring the suspension height sensor signal and the motor load current and vehicle...
[0020] A model relating speed and gradient is used to set a load threshold W_overload.
[0021] Overload cumulative time O_time_threshold / mileage threshold O_mileage_threshold: The cumulative time or mileage of overload operation corresponding to the risk of leaf spring fatigue and rear axle damage.
[0022] Further specifying, the specific steps of step S2 are as follows:
[0023] Step S2.1, the vehicle controller VCU collects the actual torque signal T_actual, vehicle speed signal V, suspension sensor height signal and vehicle mileage data emitted by the motor controller in real time at a fixed period when the vehicle is running. The system has a preset high torque judgment threshold T_high.
[0024] Step S2.2: Determine whether T_actual > T_high and vehicle speed V > 0. If so, and excluding situations where the vehicle is not revving while stationary, the VCU determines that the vehicle has entered a "high torque operating state" and starts a temporary accumulator timer t_current_trip_torque for this ignition. Otherwise, continue to check.
[0025] Step S2.3: Determine whether the estimated load is greater than W_overload and the vehicle speed is greater than 0. If so, the VCU determines that the vehicle has entered the "overload operation state" and starts the temporary accumulator timer t_current_trip_overload and the temporary accumulator odometer m_current_trip_overload for this ignition.
[0026] Further specifying, the specific steps in step S3 are as follows:
[0027] Step S3.1: Throughout the ignition cycle, the VCU continuously accumulates t_current_trip_torque, t_current_trip_overload, and m_current_trip_overload;
[0028] Step S3.2: Determine whether the vehicle key is switched to the "OFF" state. If yes, proceed to step S3.3; otherwise, continue the detection.
[0029] Step S3.3: Add the cumulative values t_current_trip_torque, t_current_trip_overload, and m_current_trip_overload of the current trip to the historical cumulative values stored in the non-volatile memory (NVM), using the following formula:
[0030] T_total_historical=T_total_historical+t_current_trip_torque
[0031] O_time_historical=O_time_historical+t_current_trip_overload
[0032] O_mileage_historical=O_mileage_historical+m_current_trip_overload
[0033] Step S3.4: Immediately write the updated historical cumulative values T_total_historical, O_time_historical, and O_mileage_historical to NVM to ensure that the data is not lost due to power failure.
[0034] Step S3.5: Clear the temporary accumulator for this cycle to prepare for the next ignition cycle.
[0035] Further specifying, the specific steps in step S4 are as follows:
[0036] In step S4.1, after each power-down storage operation, the VCU will immediately perform a threshold check or set an internal flag bit after each write to the NVM, which will be checked periodically by the VCU.
[0037] Step S4.2: If T_total_historical ≥ T_total_threshold, or O_time_historical ≥ O_time_threshold, or O_mileage_historical ≥ O_mileage_threshold, an early warning is triggered. The VCU sends an "active service early warning" signal to the TBOX via the CAN bus. This signal contains the type of early warning triggered and the current historical cumulative value.
[0038] Step S4.3: Data upload. After receiving the signal, the remote information communication terminal TBOX packages the warning information and the relevant vehicle VIN code through the mobile network and uploads them to the cloud server.
[0039] Step S4.4: The cloud and the server interact. After receiving the warning information, the cloud server records and displays it in the database and triggers the service process, pushing the warning message to the car owner via SMS or APP.
[0040] Step S4.5: After receiving the warning message, the vehicle owner can view the warning details through the vehicle terminal or mobile APP, including the specific values of the current high-voltage line temperature historical cumulative value T_total_historical, overload running time O_time_historical, and overload driving mileage O_mileage_historical, and compare them with the preset thresholds to understand the health status of the vehicle's high-voltage line system.
[0041] Step S4.6: The cloud server automatically matches recommended service plans based on the warning type and vehicle historical data, including scheduling an appointment at the nearest authorized service center, arranging on-site inspection services, or providing remote diagnostic support, and pushes the service plan to the car owner's APP for selection and confirmation.
[0042] Step S4.7: If the vehicle owner confirms the service appointment, the cloud server will synchronize the appointment information to the management system of the corresponding service center. The service center will prepare the necessary high-voltage line cooling system testing equipment and spare parts in advance according to the appointment time to ensure service efficiency.
[0043] Step S4.8: After the vehicle enters the service center, technicians use a dedicated diagnostic tool to read the complete historical data stored in the VCU, including detailed timestamps of each overload event, temperature curves, cooling system response status, and high-voltage wire aging assessment parameters, to conduct a comprehensive fault analysis.
[0044] Further specifying, the specific steps in step S5 are as follows:
[0045] Step S5.1: After the vehicle has been inspected or repaired at the 4S store, the repair technician uses a diagnostic tool to send a specific reset command to the VCU.
[0046] Step S5.2: When the vehicle controller (VCU) receives the instruction, it clears the corresponding historical accumulated values T_total_historical, O_time_historical, and O_mileage_historical to zero and stores them in the NVM again. The warning status is then lifted, and the system restarts a new round of accumulation and monitoring.
[0047] Step S5.3: The cloud server synchronously receives the repair completion confirmation information from the service center, updates the service record status in the vehicle file, archives the result of this warning processing to the database, and generates a complete repair report for the vehicle owner to view in the APP.
[0048] In step S5.4, the cloud server optimizes the threshold calibration parameters for similar vehicle models based on the correlation analysis between the current maintenance data and historical warning data, and feeds back the optimization suggestions to the vehicle R&D department for subsequent reliability test data calibration and system iteration upgrades.
[0049] The advantages of this invention compared to the prior art are as follows:
[0050] 1. A warning mechanism based on high torque operating time is implemented, which uses the vehicle control unit (VCU) to monitor and record the output torque of the vehicle motor in real time; a torque threshold range is set (such as being greater than a certain calibrated value), and the time when the torque exceeds the threshold is accumulated during each trip; when the accumulated time reaches the preset threshold (based on reliability test data, such as the torque time threshold corresponding to the damage of the rear axle gear), the system sends a warning message to the user through the TBOX remote communication module, prompting them to go to the 4S store for inspection.
[0051] 2. An early warning mechanism based on vehicle overload operation status is established, which utilizes the VCU to monitor the vehicle load status in real time and records the duration and mileage of each overload operation.
[0052] 3. Based on reliability test data, establish a correspondence table of "overload time - component damage". When the cumulative overload time or mileage reaches the preset threshold, the system will actively prompt the user to check to prevent risks such as leaf spring breakage and rear axle damage. Attached Figure Description
[0053] Figure 1 This is the logic control flowchart of the present invention;
[0054] Figure 2 This is a flowchart of step S3 of the present invention. Detailed Implementation
[0055] To enable those skilled in the art to better understand the technical solution of the present invention, the technical solution of the present invention will be further described below in conjunction with the accompanying drawings and embodiments.
[0056] Example:
[0057] like Figure 1 and Figure 2 As shown, a system involving vehicle active safety warning and remote service includes an on-board unit, a cloud terminal, and a service terminal. The on-board unit includes a vehicle control unit (VCU) and a remote information communication terminal (TBOX). The VCU is connected to a motor controller, a battery management system (BMS), sensors, and an electronic control unit via a CAN bus. It is used to collect vehicle operating data in real time and perform high-risk state judgment, cumulative counting, threshold comparison, and warning triggering logic. The TBOX is connected to the VCU via a CAN bus and is used to upload the warning information triggered by the VCU and the vehicle identification information to the cloud terminal via a mobile communication network.
[0058] The cloud includes a database and a cloud server. The cloud server is used to receive, process and store the warning data uploaded by TBOX and trigger preset service processes. The database is used to store historical data such as vehicle files, warning records, and service records.
[0059] The server receives and displays the warning message transmitted from the cloud.
[0060] A system involving vehicle active safety warning and remote services, comprising the following specific steps:
[0061] Step S1 involves system initialization and calibration. The calibration MAP and threshold values for key parameters are preset in the vehicle control unit (VCU). These parameters are largely derived from extensive vehicle reliability bench and road test data, including:
[0062] High torque range: Defined as a state where the motor output torque is continuously greater than T_high. The value of T_high can be calibrated according to different vehicle models and drive axle configurations.
[0063] High torque cumulative time threshold T_total_threshold: corresponds to the risk of fatigue damage to the rear axle gears.
[0064] Cumulative time (this data comes from the cumulative time of high torque experienced by the gear before micropitting or damage occurs in reliability tests, multiplied by a safety factor).
[0065] Overload detection threshold: determined by monitoring the suspension height sensor signal and the motor load current relative to the vehicle load.
[0066] A model relating speed and gradient is used to define a load threshold W_overload (e.g., the rated load).
[0067] (110%), when the estimated load continues to exceed this value, it is determined to be in an "overload operation" state;
[0068] Overload cumulative time O_time_threshold / Mileage threshold O_mileage_threshold: The cumulative time or mileage of overload operation corresponding to the risk of leaf spring fatigue and rear axle damage.
[0069] Step S2: Perform real-time data acquisition and status assessment;
[0070] Step S2.1: When the vehicle is running, the vehicle controller (VCU) collects the actual torque signal T_actual, vehicle speed signal V, suspension sensor height signal or other key signals used to estimate other loads and vehicle mileage data in real time at fixed intervals. The system has a preset high torque judgment threshold T_high.
[0071] Step S2.2: Determine whether T_actual > T_high and vehicle speed V > 0. If so, and excluding situations where the vehicle is not revving while stationary, the VCU determines that the vehicle has entered a "high torque operating state" and starts a temporary accumulator timer t_current_trip_torque for this ignition. Otherwise, continue to check.
[0072] Step S2.3: Determine whether the estimated load is greater than W_overload and the vehicle speed is greater than 0. If so, the VCU determines that the vehicle has entered the "overload operation state" and starts the temporary accumulator timer t_current_trip_overload and the temporary accumulator odometer m_current_trip_overload for this ignition.
[0073] Step S3: Data recording and processing;
[0074] Step S3.1: Throughout the ignition cycle, the VCU continuously accumulates t_current_trip_torque, t_current_trip_overload, and m_current_trip_overload;
[0075] Step S3.2: Determine whether the vehicle key is switched to the "OFF" state. If yes, proceed to step S3.3; otherwise, continue the detection.
[0076] Step S3.3: Add the cumulative values t_current_trip_torque, t_current_trip_overload, and m_current_trip_overload of the current trip to the historical cumulative values stored in the non-volatile memory (NVM), using the following formula:
[0077] T_total_historical=T_total_historical+t_current_trip_torque
[0078] O_time_historical=O_time_historical+t_current_trip_overload
[0079] O_mileage_historical=O_mileage_historical+m_current_trip_overload
[0080] Step S3.4: Immediately write the updated historical cumulative values T_total_historical, O_time_historical, and O_mileage_historical to NVM to ensure that the data is not lost due to power failure.
[0081] Step S3.5: Clear the temporary accumulator for this cycle to prepare for the next ignition cycle;
[0082] Step S4: After each power-down storage operation is completed, the VCU will immediately perform a threshold check or set an internal flag bit after each write to the NVM, which will be checked periodically by the VCU.
[0083] Step S4.2: If T_total_historical ≥ T_total_threshold, or O_time_historical ≥ O_time_threshold, or O_mileage_historical ≥ O_mileage_threshold, an early warning is triggered. The VCU sends an "active service early warning" signal to the TBOX via the CAN bus. This signal contains the type of early warning triggered and the current historical cumulative value.
[0084] Step S4.3: Data upload. After receiving the signal, the remote information communication terminal TBOX packages the warning information and the relevant vehicle VIN code through the mobile network and uploads them to the cloud server.
[0085] Step S4.4: The cloud and the server interact. After receiving the warning information, the cloud server records and displays it in the database and triggers the service process, pushing the warning message to the car owner via SMS or APP.
[0086] Step S4.5: After receiving the warning message, the vehicle owner can view the warning details through the vehicle terminal or mobile APP, including the specific values of the current high-voltage line temperature historical cumulative value T_total_historical, overload running time O_time_historical, and overload driving mileage O_mileage_historical, and compare them with the preset thresholds to understand the health status of the vehicle's high-voltage line system.
[0087] Step S4.6: The cloud server automatically matches recommended service plans based on the warning type and vehicle historical data, including scheduling an appointment at the nearest authorized service center, arranging on-site inspection services, or providing remote diagnostic support, and pushes the service plan to the car owner's APP for selection and confirmation.
[0088] Step S4.7: If the vehicle owner confirms the service appointment, the cloud server will synchronize the appointment information to the management system of the corresponding service center. The service center will prepare the necessary high-voltage line cooling system testing equipment and spare parts in advance according to the appointment time to ensure service efficiency.
[0089] Step S4.8: After the vehicle enters the service center, technicians use a dedicated diagnostic tool to read the complete historical data stored in the VCU, including detailed timestamps of each overload event, temperature curves, cooling system response status, and high-voltage wire aging assessment parameters, to conduct a comprehensive fault analysis.
[0090] Step S5: Perform early warning reset and service follow-up;
[0091] Step S5.1: After the vehicle has been inspected or repaired at the 4S store, the repair technician uses a diagnostic tool to send a specific reset command to the VCU.
[0092] Step S5.2: When the vehicle controller (VCU) receives the instruction, it clears the corresponding historical accumulated values T_total_historical, O_time_historical, and O_mileage_historical to zero and stores them in the NVM again. The warning status is then lifted, and the system restarts a new round of accumulation and monitoring.
[0093] Step S5.3: The cloud server synchronously receives the repair completion confirmation information from the service center, updates the service record status in the vehicle file, archives the result of this warning processing to the database, and generates a complete repair report for the vehicle owner to view in the APP.
[0094] In step S5.4, the cloud server optimizes the threshold calibration parameters for similar vehicle models based on the correlation analysis between the current maintenance data and historical warning data, and feeds back the optimization suggestions to the vehicle R&D department for subsequent reliability test data calibration and system iteration upgrades.
[0095] The above provides a detailed description of a system and method for vehicle active safety warning and remote service provided by the present invention. The description of specific embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made to the present invention without departing from the present invention, and these improvements and modifications also fall within the protection scope of the claims of the present invention.
Claims
1. A system involving active safety warning and remote services for vehicles, characterized in that: The system includes an on-board unit, a cloud platform, and a service unit. The on-board unit includes a vehicle control unit (VCU) and a remote information communication terminal (TBOX). The VCU is connected to the motor controller, battery management system (BMS), sensors, and electronic control unit via a CAN bus. It is used to collect vehicle operating data in real time and perform high-risk status judgment, cumulative counting, threshold comparison, and warning triggering logic. The TBOX is connected to the VCU via a CAN bus and is used to upload the warning information triggered by the VCU and the vehicle identification information to the cloud platform via a mobile communication network. The cloud includes a database and a cloud server. The cloud server is used to receive, process and store the warning data uploaded by TBOX and trigger preset service processes. The database is used to store historical data such as vehicle files, warning records, and service records. The server receives and displays the warning message transmitted from the cloud.
2. The method of a system involving active safety warning and remote service for vehicles according to claim 1, characterized in that: The specific steps are as follows: Step S1: Perform system initialization and calibration, and pre-set calibration parameters; Step S2: Perform real-time data acquisition and status assessment; Step S3: Trip data recording and processing; In step S4, the VCU and remote communication work together to perform early warning judgment and triggering; Step S5: Perform early warning reset and service follow-up.
3. A system for active vehicle safety warning and remote services according to claim 2 The method is characterized by: The calibration parameter preset in step S1 includes: High torque range: Defines the motor output torque as being continuously greater than T_high as the "high torque" state; High torque cumulative time threshold T_total_threshold: corresponds to the risk of fatigue damage to the rear axle gears. Cumulative time; Overload judgment threshold: by monitoring the suspension height sensor signal and the motor load current and vehicle... A model relating speed and gradient is used to set a load threshold W_overload. Overload cumulative time O_time_threshold / mileage threshold O_mileage_threshold: The cumulative time or mileage of overload operation corresponding to the risk of leaf spring fatigue and rear axle damage.
4. The method of a system involving active safety warning and remote service for vehicles according to claim 2, characterized in that... The specific steps of step S2 are as follows: Step S2.1, the vehicle controller VCU collects the actual torque signal T_actual, vehicle speed signal V, suspension sensor height signal and vehicle mileage data emitted by the motor controller in real time at a fixed period when the vehicle is running. The system has a preset high torque judgment threshold T_high. Step S2.2: Determine whether T_actual > T_high and vehicle speed V > 0. If so, and excluding situations where the vehicle is not revving while stationary, the VCU determines that the vehicle has entered a "high torque operating state" and starts a temporary accumulator timer t_current_trip_torque for this ignition. Otherwise, continue to check. Step S2.3: Determine whether the estimated load is greater than W_overload and the vehicle speed is greater than 0. If so, the VCU determines that the vehicle has entered the "overload operation state" and starts the temporary accumulator timer t_current_trip_overload and the temporary accumulator odometer m_current_trip_overload for this ignition.
5. The method of a system involving active safety warning and remote service for vehicles according to claim 2, characterized in that: The specific steps in step S3 are as follows: Step S3.1: Throughout the ignition cycle, the VCU continuously accumulates t_current_trip_torque, t_current_trip_overload, and m_current_trip_overload; Step S3.2: Determine whether the vehicle key is switched to the "OFF" state. If yes, proceed to step S3.3; otherwise, continue the detection. Step S3.3: Add the cumulative values t_current_trip_torque, t_current_trip_overload, and m_current_trip_overload of the current trip to the historical cumulative values stored in the non-volatile memory (NVM), using the following formula: T_total_historical=T_total_historical+t_current_trip_torque O_time_historical=O_time_historical+t_current_trip_overload O_mileage_historical=O_mileage_historical+m_current_trip_overload Step S3.4: Immediately write the updated historical cumulative values T_total_historical, O_time_historical, and O_mileage_historical to NVM to ensure that the data is not lost due to power failure. Step S3.5: Clear the temporary accumulator for this cycle to prepare for the next ignition cycle.
6. The method of a system involving active safety warning and remote service for vehicles according to claim 2, characterized in that: The specific steps in step S4 are as follows: Step S4.1: After each power-down storage operation is completed, the VCU will immediately perform a threshold check or set an internal flag bit after each write to the NVM, which will be checked periodically by the VCU. Step S4.2: If T_total_historical ≥ T_total_threshold, or O_time_historical ≥ O_time_threshold, or O_mileage_historical ≥ O_mileage_threshold, an early warning is triggered. The VCU sends an "active service early warning" signal to the TBOX via the CAN bus. This signal contains the type of early warning triggered and the current historical cumulative value. Step S4.3: Data upload. After receiving the signal, the remote information communication terminal TBOX packages the warning information and the relevant vehicle VIN code through the mobile network and uploads them to the cloud server. Step S4.4: The cloud and the server interact. After receiving the warning information, the cloud server records and displays it in the database and triggers the service process, pushing the warning message to the car owner via SMS. Step S4.5: After receiving the warning message, the vehicle owner can view the warning details through the server, including the current historical cumulative value of high-voltage line temperature T_total_historical, overload running time O_time_historical, and overload driving mileage O_mileage_historical, and compare them with the preset thresholds to understand the health status of the vehicle's high-voltage line system. Step S4.6: The cloud server automatically matches recommended service plans based on the warning type and vehicle historical data, including scheduling an appointment at the nearest authorized service center, arranging on-site inspection services, or providing remote diagnostic support, and pushes the service plan to the car owner's APP for selection and confirmation. Step S4.7: If the vehicle owner confirms the service appointment, the cloud server will synchronize the appointment information to the management system of the corresponding service center. The service center will prepare the necessary high-voltage line cooling system testing equipment and spare parts in advance according to the appointment time to ensure service efficiency. Step S4.8: After the vehicle enters the service center, technicians use a dedicated diagnostic tool to read the complete historical data stored in the VCU, including detailed timestamps of each overload event, temperature curves, cooling system response status, and high-voltage wire aging assessment parameters, to conduct a comprehensive fault analysis.
7. The method of a system involving active safety warning and remote service for vehicles according to claim 1, characterized in that: The specific steps in step S5 are as follows: Step S5.1: After the vehicle has been inspected or repaired at the 4S store, the repair technician uses a diagnostic tool to send a specific reset command to the VCU. Step S5.2: When the vehicle controller (VCU) receives the instruction, it clears the corresponding historical accumulated values T_total_historical, O_time_historical, and O_mileage_historical to zero and stores them in the NVM again. The warning status is then lifted, and the system restarts a new round of accumulation and monitoring. Step S5.3: The cloud server synchronously receives the repair completion confirmation information from the service center, updates the service record status in the vehicle file, archives the result of this warning processing to the database, and generates a complete repair report for the vehicle owner to view in the APP. In step S5.4, the cloud server optimizes the threshold calibration parameters for similar vehicle models based on the correlation analysis between the current maintenance data and historical warning data, and feeds back the optimization suggestions to the vehicle R&D department for subsequent reliability test data calibration and system iteration upgrades.