WO2022095896A1 - 一种车辆上的ecu管理方法、ecu以及可读存储介质 - Google Patents
一种车辆上的ecu管理方法、ecu以及可读存储介质 Download PDFInfo
- Publication number
- WO2022095896A1 WO2022095896A1 PCT/CN2021/128411 CN2021128411W WO2022095896A1 WO 2022095896 A1 WO2022095896 A1 WO 2022095896A1 CN 2021128411 W CN2021128411 W CN 2021128411W WO 2022095896 A1 WO2022095896 A1 WO 2022095896A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ecu
- abnormal
- restart
- state
- instruction
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000002159 abnormal effect Effects 0.000 claims abstract description 272
- 238000012544 monitoring process Methods 0.000 claims abstract description 25
- 230000009471 action Effects 0.000 claims abstract description 20
- 238000011084 recovery Methods 0.000 claims abstract description 15
- 238000007726 management method Methods 0.000 claims description 59
- 238000007689 inspection Methods 0.000 claims description 41
- 238000004891 communication Methods 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 11
- 238000012423 maintenance Methods 0.000 claims description 11
- 238000010295 mobile communication Methods 0.000 claims description 5
- 238000012550 audit Methods 0.000 description 20
- 230000005856 abnormality Effects 0.000 description 17
- 230000008569 process Effects 0.000 description 16
- 230000006870 function Effects 0.000 description 7
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000001934 delay Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
- G05B23/0286—Modifications to the monitored process, e.g. stopping operation or adapting control
- G05B23/0289—Reconfiguration to prevent failure, e.g. usually as a reaction to incipient failure detection
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
- G06F11/0739—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in automotive or aircraft systems
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
- G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
- B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/02—Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
- B60W50/0205—Diagnosing or detecting failures; Failure detection models
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/02—Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
- B60W50/032—Fixing failures by repairing failed parts, e.g. loosening a sticking valve
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3013—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1408—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
- H04L63/1425—Traffic logging, e.g. anomaly detection
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/24—Pc safety
- G05B2219/24065—Real time diagnostics
Definitions
- the embodiments of the present application relate to, but are not limited to, the technical field of automobiles, and specifically relate to, but are not limited to, an ECU management method on a vehicle, an ECU, and a readable storage medium.
- ECUs electronice control units
- the increase of ECUs represents the complexity of functions and the difficulty of stability.
- ECU nodes are composed of hardware and software.
- these ECUs are all black boxes, and users do not even know the existence of ECUs. If there is an abnormality in the ECU, at this time, the user must drive the car to the 4S shop for inspection and maintenance. This process is very troublesome and disgusting for the car owner.
- An ECU management method on a vehicle, an ECU, and a readable storage medium provided by the embodiments of the present application can monitor the state of the ECU of the entire vehicle, and when an abnormal ECU is detected, send a control command to it, so that the The abnormal ECU executes the corresponding recovery action according to the control command, so as to avoid the battery feeding caused by the abnormal ECU after the vehicle is turned off.
- an embodiment of the present application provides an electronic control unit management method on a vehicle, which includes monitoring the working state of at least one electronic control unit ECU on the vehicle, and when an abnormality in the abnormal working state is detected.
- a control instruction is sent to the abnormal ECU, wherein the control instruction is used to trigger the abnormal ECU to perform a corresponding recovery action.
- Embodiments of the present application further provide an electronic control unit, which includes a processor, a memory, and a communication bus.
- the communication bus is used to implement connection communication between the processor and the memory, and the processor is used to execute one or more computer programs stored in the memory to implement the steps of the aforementioned method for managing an electronic control unit on a vehicle.
- Embodiments of the present application further provide a computer-readable storage medium storing one or more computer programs.
- the one or more computer programs may be executed by one or more processors to implement the steps of the aforementioned method for managing an electronic control unit on a vehicle.
- FIG. 1 is a schematic diagram of the connection of the vehicle ECU according to the first embodiment of the application
- Fig. 3 is the flow chart of the second embodiment of the application.
- FIG. 5 is a flowchart of Embodiment 3 of the application.
- FIG. 6 is a flowchart of a method in an ignition state according to Embodiment 3 of the present application.
- Figure 1 is a schematic diagram of the connection of the vehicle ECU. Network messages, APP messages and diagnostic messages, the vehicle interacts with the CSP server through the TBOX.
- ECU Electronic Control Unit
- the entire function is completed by each ECU collaboratively.
- a specific ECU node is used as an inspection node to supervise the working status of other ECUs, and the common node is used as the object to be supervised.
- Vehicle-mounted mobile communication terminal TBOX also belongs to the ECU node, including the communication system that interacts with the external network through the wireless 3GPP network, and also supports the information exchange with other ECUs in the vehicle through CAN. It can also be used to interact with the server CSP, synchronize the business parameters and working status of each ECU, and perform vehicle ECU control.
- Vehicle cloud server CSP equivalent to the application system of the Internet of Vehicles, it is a vehicle operation information platform with cloud architecture. It is maintained by the car factory, provides application services to car owners and tracks the state of the vehicle during use. In this invention, it is passed by the car factory. It maintains and controls the ECU business parameters of the vehicle.
- CAN Controller Area Network, which is the most widely used field bus in vehicles at present. Each ECU exchanges information through CAN.
- the inspection node collects the information of other nodes from CAN to judge the state. , and the control of exceptions.
- FIG. 2 a method for managing an electronic control unit on a vehicle is proposed, please refer to FIG. 2 , including:
- the monitoring of the working state of at least one electronic control unit ECU on the vehicle may be performed through an inspection node configured on the vehicle to monitor the working state of the ECU.
- the inspection nodes that can be selected include the vehicle-mounted mobile communication terminal TBOX and the target ECU. Of course, only one of them can be selected, or the TBOX and the target ECU can be combined for selection, for example, TBOX and multiple target ECUs can be selected.
- the target ECU described in this embodiment may be based on the actual work performance of the ECU or the functional complexity of the ECU, and an ECU with relatively stable work or low functional complexity is selected as the inspection node, and then the inspection node ECU is used to check at least the ECU on the vehicle. The working status of an electronic control unit ECU is monitored.
- the specific monitoring means can assign a corresponding physical address to each ECU, thereby monitoring the working state of the ECU according to the corresponding physical address.
- a control command may also be sent to the abnormal ECU according to the corresponding physical address.
- the abnormal ECU can perform a corresponding recovery action according to the control command, thereby improving the running stability of the vehicle ECU. It can avoid vehicle battery feeding due to ECU abnormality, and improve user experience.
- control instruction includes at least one of the following: an ECU restart instruction for triggering the abnormal ECU to perform restart; an ECU shutdown instruction for triggering the abnormal ECU to perform shutdown; and an ECU shutdown instruction for triggering the abnormal ECU
- the ECU executes the ECU firmware update command for firmware update.
- the specific control instruction may be an ECU restart instruction, and the abnormal ECU may execute restart after receiving the ECU restart instruction.
- sending a control command to the abnormal ECU may directly send a command code corresponding to the control action to the ECU, for example, sending a UDS restart command 0x11 whose ID is the physical address of the corresponding ECU, and then waiting for 0x11 's reply. It can also send a custom UDS control command to the abnormal ECU, and the abnormal ECU knows that its own state is abnormal through the custom UDS control command, and thus performs a restart action, a shutdown action, or a firmware update action in cooperation with the corresponding control command.
- the ECU firmware update instruction described in this example may be an instruction only used to trigger an abnormal ECU to perform firmware update, that is, the ECU firmware update instruction may not include corresponding firmware.
- the abnormal ECU After the abnormal ECU receives the ECU firmware update instruction, it can obtain the firmware information that needs to be updated from the local storage, the server, or the local external storage device.
- the firmware update described in this embodiment may be updated to the latest version of the firmware, or may be updated in parallel, that is, keeping the firmware version number unchanged, or may be updated to an old firmware version, such as locally stored, or If the server or the local external storage device stores an old version of firmware with relatively stable performance corresponding to the ECU, the abnormal ECU can also be instructed to update the firmware through the ECU firmware update instruction.
- the message of the abnormal ECU performing the recovery action may be broadcast to the TBOX through the CAN bus, and then reported to the CSP server through the TBOX.
- monitor abnormal ECUs with abnormal working status including:
- the TBOX after the TBOX is turned on, it can collect the notification messages carrying the service parameters of each ECU sent by the CSP server, parse and save it, and broadcast it to other inspection nodes on the CAN bus through CAN. In this way, all audit nodes know the business parameters of each ECU in the normal operating state.
- the format of each ECU service parameter recorded by the CSP server can be set according to the uniqueness of the network management message ID of each ECU of the vehicle.
- the network management message ID represents a specific ECU node.
- the whole vehicle contains two key states: KL15off flameout state and KL15on ignition state, which can record these two key states and the corresponding ECU business parameters.
- the service state parameters of the current ECU can be obtained by parsing the network management message sent from the ECU, so that whether the state of the ECU is abnormal is determined by comparing the service state parameters with the normal service state parameters corresponding to the ECU. .
- the ECU before receiving the network management message uploaded by the ECU, it further includes:
- the abnormal state of the ECU may be determined directly according to the failure to normally receive the network management message sent by the ECU. For example, in the ignition state, the normal network management message sending interval from the server is t1, and after t1, if the audit node fails to receive the network management message of the ECU, it can directly determine the status of the ECU abnormal.
- the method for determining that the state of the ECU is abnormal includes at least one of the following:
- the service state parameters of normal driving can be obtained by sending the server when the device is turned on, or by reading the local storage.
- the RSS information corresponding to the ready-to-sleep state of the ECU can be extracted from the network management message, and the extracted RSS information can be compared according to the maintenance time that the RSS information is normally in RSS. If it exceeds the normal maintenance time of RSS, then It is determined that the state of the ECU is abnormal. Because in the flameout state, the normal RSS time service will exit after completion, and will not remain in the RSS state. If it remains in the RSS state, it means that an abnormality has occurred in an ECU. The abnormal ECU means that the network management message has been sent abnormally. ECU. The corresponding maximum service maintenance time of each ECU can be obtained through the server.
- the sending of a control command to the abnormal ECU includes at least one of the following:
- a control command may be sent to the abnormal ECU through the inspection node, or the ECU restart command may be sent directly to the abnormal ECU. After the abnormal ECU receives the command Do a restart.
- the fault code of the abnormal ECU is determined, and if it is determined according to the fault code that it can be recovered by restarting, the ECU restarting instruction is sent to the abnormal ECU.
- it can be determined according to the fault code that it can be recovered by restarting in the following ways. For example, by using a preset code comparison table or code database, after determining the fault code of the abnormal ECU, it is compared with the preset code comparison table or code database. , if it is determined by comparison that it can be recovered by restarting, the ECU restarting instruction is sent to the abnormal ECU. If there is no corresponding fault code record in the code record table, you can try to send the ECU restart command to the abnormal ECU. If the restart is successful, you can update the corresponding record table or database, and record the corresponding code as a restartable command. recover. If restart recovery fails, you can update the corresponding record table or database, and record the corresponding code as not recoverable by restart.
- the preset restart control rule referred to in this embodiment may be the number of restarts, for example, the restart instruction is executed cyclically three times, or the restart instruction is executed cyclically three times with a specified time interval between restarts, etc.
- the ECU shutdown command or the ECU firmware update command may be sent to the abnormal ECU. Since the restart control cannot restore the abnormal ECU, it is possible to update the firmware of the ECU or directly shut down.
- the ECU restart instruction to the abnormal ECU according to a preset restart control rule, and after monitoring that the abnormal ECU is still abnormal after restarting according to the ECU restart instruction, send the ECU firmware update instruction to the abnormal ECU , if the abnormal ECU is still abnormal after the firmware is updated, send the ECU shutdown command to the abnormal ECU.
- the restart control rule cannot restore the abnormal ECU and the firmware update cannot restore the faulty ECU
- the The ECU performs shutdown control to avoid level feed caused by ECU failure.
- the sending a control command to the abnormal ECU includes at least one of the following:
- sending a control command to the abnormal ECU includes directly sending an ECU restart command to the abnormal ECU. Since some ECUs cannot be restarted directly during the driving process of the vehicle, before sending a control command to the abnormal ECU, it can also be determined whether the abnormal ECU is set with a corresponding configuration item. In the case of the corresponding configuration item, a control command is sent to the abnormal ECU.
- an optional implementation may be, after the TBOX is powered on, by receiving the notification message carrying the service parameters of each ECU sent by the server, and parsing the notification message, so as to obtain whether each ECU is provided with a restart switch, and in the settings If there is a restart switch, it means that the ECU can restart or perform an update action in the ignition state.
- the ECU restart instruction or update instruction is directly sent to the abnormal ECU, so that the ECU can be controlled to perform state recovery in the ignition state.
- the fault code of the abnormal ECU is determined, and if it is determined according to the fault code that it can be recovered by restarting, the ECU restart instruction is sent to the abnormal ECU.
- the specific fault code comparison method please refer to the above-mentioned content.
- the ECU restarting instruction is sent to the abnormal ECU, thereby recovering the driving of the vehicle. ECU failure in the process.
- the fault code of the abnormal ECU is determined, and if it is determined according to the fault code that it cannot be recovered by restarting, the ECU shutdown instruction or the ECU firmware update instruction is sent to the abnormal ECU. That is, corresponding to the ignition state, if it is determined according to the fault code that it cannot be recovered by restarting, the ECU firmware update instruction may be sent to the abnormal ECU. If the ECU is still abnormal after the firmware is updated, a warning can be issued to the user to prompt the user that an ECU of the current vehicle is in an abnormal state.
- the ECU is still abnormal, and the abnormal situation of the corresponding ECU can be sent to the server side, and the corresponding solutions can be manually determined by professionals on the server side, such as rewriting the code, etc., and solve the problem from the server side. Abnormal state of the ECU.
- the ECU firmware update instruction can also be directly sent to the abnormal ECU; or, the ECU restart instruction can be sent to the abnormal ECU according to a preset restart control rule. After the restart instruction is still abnormal after restarting, the ECU firmware update instruction is sent to the abnormal ECU.
- the specific execution manner is the same as the execution manner in the flameout state, and details are not repeated here.
- sending the ECU restart instruction to the target ECU including:
- the ECU restart instruction is sent to the target ECU according to the restart sequence.
- each inspection node in this embodiment will monitor the working status of all ECUs except itself.
- the function selected by the ECU of the audit node is relatively simple, it may also fail.
- the ECUs of the audit node may fail at the same time within a period of time.
- the ECU restarting instructions may be sent to the plurality of target ECUs at different time points, so that the plurality of target ECUs perform restarting at different time points. That is to say, by sending restart commands to the inspection point ECU at different time nodes, it is ensured that all inspection nodes will not restart at the same time when multiple inspection nodes are faulty.
- the proportion of the target ECU in an abnormal state exceeds the set proportion threshold.
- the restart interval of each ECU is a certain time. For example, if the restart completion time of an ECU is 2 minutes, the set sequence restart interval can be 2 minutes.
- a plurality of nodes with relatively stable functions can be selected from the ECU nodes of the whole vehicle as inspection nodes, and the working status of other ECU nodes can be monitored by detecting the CAN bus.
- the maximum duration of each ECU's business and the business logic of the ECU are set. TBOX then broadcasts this message to other audit nodes.
- the inspection node detects that an ECU works abnormally, and the query has exceeded the maximum duration of its business, it is considered that the node is abnormal, and the vehicle status is judged. If it is considered to be a serious fault and its restart conditions are met, it will send CAN restart.
- the diagnosis command is given to the ECU, so that the ECU restarts to restore the initial state, and then returns to normal. Otherwise, the abnormality is sent to the server, and the server side conducts human judgment and operation, and conducts a preliminary analysis of the problem. Restart a certain ECU on the side, there is no need to enter the 4S shop again. This ensures that the abnormal node is not in an abnormal working state for a long time.
- the method of this embodiment can also avoid battery feeding due to an abnormality of the ECU, thereby improving the user's vehicle experience.
- a method for managing an electronic control unit on a vehicle including the following steps:
- the inspection node monitors the working state of at least one electronic control unit ECU on the vehicle;
- the inspection node sends a control instruction to the abnormal ECU, where the control instruction is used to trigger the abnormal ECU to perform a corresponding recovery action.
- the specific ones that can be selected as the inspection nodes can include the vehicle-mounted mobile communication terminal TBOX and the target ECU. Of course, only one of them can be selected, or the TBOX and the target ECU can be selected together. For example, in this embodiment, TBOX and multiple targets can be selected. ECU.
- the target ECU described in this embodiment may be based on the actual work performance of the ECU or the functional complexity of the ECU, and an ECU with relatively stable work or low functional complexity is selected as the inspection node, and then the inspection node ECU is used to check at least the ECU on the vehicle. The working status of an electronic control unit ECU is monitored.
- the TBOX After the TBOX is turned on, it can collect the notification messages that carry the service parameters of each ECU sent by the CSP server, parse and save them, and broadcast them to other inspection nodes on the CAN bus through CAN. In this way, all audit nodes know the business parameters of each ECU in the normal operating state.
- the format of each ECU service parameter recorded by the CSP server can be set according to the uniqueness of the network management message ID of each ECU of the vehicle.
- the network management message ID represents a specific ECU node.
- the network management message sent by the ECU to the audit node can include two key states: KL15off flameout state and KL15on ignition state. The audit node can record these two key states, and the network management message can also include the corresponding ECU business.
- the service state parameters of the current ECU can also be obtained by parsing the network management message sent from the ECU, so that whether the state of the ECU is determined by comparing the service state parameters with the normal service state parameters corresponding to the ECU abnormal.
- the specific monitoring means can assign a corresponding physical address to each ECU, thereby monitoring the working state of the ECU according to the corresponding physical address.
- a control command may also be sent to the abnormal ECU according to the corresponding physical address.
- the abnormal ECU can perform a corresponding recovery action according to the control command, thereby improving the running stability of the vehicle ECU. It can avoid vehicle battery feeding due to ECU abnormality, and improve user experience.
- control instruction includes at least one of the following: an ECU restart instruction for triggering the abnormal ECU to perform restart; an ECU shutdown instruction for triggering the abnormal ECU to perform shutdown; and an ECU shutdown instruction for triggering the abnormal ECU
- the ECU executes the ECU firmware update command for firmware update.
- the restarting of the ECU is controlled as an example for illustration.
- the method of this embodiment includes the following steps:
- S401 Receive a network management message sent by an ECU, where the network management message includes a service state parameter of a corresponding ECU;
- the inspection node sends an ECU restart instruction to the abnormal ECU, where the ECU restart instruction is used to trigger the abnormal ECU to perform a corresponding restart action.
- the method of the present application checks the node according to the ID of the received ECU network management message.
- This ID represents a certain ECU, which means that the ECU is in a non-ready sleep state RSS state, and this ECU may cause the network The reason for the abnormality is maintained, and then the next step is determined.
- KL15 Judging the state of KL15, if KL15 is in a state that requires the CAN network to work normally, it is not necessary to continue the abnormal monitoring process at this time, that is, it can be considered that the working state of the ECU is normal at this time, and no processing is required. If the KL15 is in a state that does not require the CAN network to work normally, continue to the next step.
- the ECU corresponding to the network management message is in the ready-to-sleep state RSS state. If it is not in the RSS state, it is not necessary to start the abnormal monitoring process at this time; it means that the ECU itself thinks that it is necessary to maintain the CAN network. If the inspection ECU abnormally maintains the CAN network, the abnormality will be monitored in other inspection ECU nodes, and the abnormality protection process will be started.
- the abnormal judgment basis can be obtained according to the AutoSar network management protocol.
- the state of the ECU in the off state, according to the comparison between the service state parameter and the normal service state parameter corresponding to the ECU, it is determined that the state of the ECU is abnormal, including: when the network management message is extracted to prepare The RSS information in the dormant state exceeds the maintenance time of the normal RSS, and it is determined that the state of the ECU is abnormal.
- the RSS information corresponding to the ready-to-sleep state of the ECU can be extracted from the network management message, and the extracted RSS information can be compared according to the maintenance time that the RSS information is normally in RSS. If it exceeds the normal maintenance time of RSS, then It is determined that the state of the ECU is abnormal. Because in the flameout state, the normal RSS time service will exit after completion, and will not remain in the RSS state. If it remains in the RSS state, it means that an abnormality has occurred in an ECU. The abnormal ECU means that the network management message has been sent abnormally. ECU. The corresponding maximum service maintenance time of each ECU can be obtained through the server.
- An optional implementation manner may be to calculate the time that the network management message is in the RSS this time, and calculate the time that the network management enters the RSS state according to the state provided by the network management message, so as to judge the time that the RSS is maintained this time.
- the normal RSS time service When the normal RSS time service is completed, it will exit, and will not remain in the RSS state. If it remains in the RSS state, it means that an abnormality has occurred in an ECU.
- the abnormal ECU is the ECU that has been sending network management messages abnormally.
- the service related to the CAN network of each ECU in the vehicle has its maximum duration, which can be obtained by parsing the notification message sent by the server. If the maintenance time of the RSS has exceeded the maximum service time of the ECU of the received message ID, the service of the ECU is considered abnormal, and the abnormal protection process is continued.
- the audit node sends a restart command to the corresponding ECU.
- the ECU that receives this command knows that its own CAN network is abnormal, and then takes action to restore the CAN network and reset all CAN-related states.
- the audit node broadcasts the abnormal restart message of the ECU to the TBOX through the CAN message, and the TBOX will report it to the CSP server.
- the server side can manually determine the solution to determine the abnormal state.
- Command operations in other flame-off states are similar to the above process, and are not repeated in this embodiment.
- the embodiment of the present application ensures that the abnormal node does not stay in the abnormal working state for a long time by controlling the restart of the abnormal ECU in the off state.
- the method of this embodiment can also avoid battery feeding due to an abnormality of the ECU, thereby improving the user's vehicle experience.
- a third embodiment of the present application proposes a method for managing an electronic control unit on a vehicle, as shown in FIG. 5 , including the following steps:
- the inspection node monitors the working state of at least one electronic control unit ECU on the vehicle;
- the inspection node sends a control instruction to the abnormal ECU, where the control instruction is used to trigger the abnormal ECU to perform a corresponding recovery action.
- the specific ones that can be selected as inspection nodes can include the vehicle-mounted mobile communication terminal TBOX and the target ECU. Of course, only one of them can be selected, or the TBOX and the target ECU can be selected together. For example, in this embodiment, TBOX and three targets are selected. ECU.
- the target ECU described in this embodiment may be based on the actual work performance of the ECU or the functional complexity of the ECU, and an ECU with relatively stable work or low functional complexity is selected as the inspection node, and then the inspection node ECU is used to check at least the ECU on the vehicle. The working status of an electronic control unit ECU is monitored.
- the TBOX After the TBOX is turned on, it can collect the notification messages that carry the service parameters of each ECU sent by the CSP server, parse and save them, and broadcast them to other inspection nodes on the CAN bus through CAN. In this way, all audit nodes know the business parameters of each ECU in the normal operating state.
- the format of each ECU service parameter recorded by the CSP server can be set according to the uniqueness of the network management message ID of each ECU of the vehicle.
- the network management message ID represents a specific ECU node.
- the network management message sent by the ECU to the audit node can contain two key states: KL15off flameout state and KL15on ignition state. The audit node can record these two key states, and the network management message can also include the corresponding ECU business.
- the service status parameters of the current ECU can also be obtained by parsing the network management message sent from the ECU, so as to determine whether the status of the ECU is determined by comparing the service status parameters with the normal service status parameters corresponding to the ECU. abnormal.
- the specific monitoring means can assign a corresponding physical address to each ECU, thereby monitoring the working state of the ECU according to the corresponding physical address.
- a control command may also be sent to the abnormal ECU according to the corresponding physical address.
- the abnormal ECU can perform a corresponding recovery action according to the control command, thereby improving the running stability of the vehicle ECU. It can avoid vehicle battery feeding due to ECU abnormality, and improve user experience.
- control instruction includes at least one of the following: an ECU restart instruction for triggering the abnormal ECU to perform restart; an ECU shutdown instruction for triggering the abnormal ECU to perform shutdown; and an ECU shutdown instruction for triggering the abnormal ECU
- the ECU executes the ECU firmware update command for firmware update.
- the control of ECU restarting in the ignition state is used as an example for illustration.
- the method of this embodiment includes the following steps:
- the inspection node After confirming that the abnormal ECU is set with a corresponding configuration item, the inspection node sends an ECU restart instruction to the abnormal ECU, where the ECU restart instruction is used to trigger the abnormal ECU to perform a corresponding restart action.
- the inspection node After confirming that the abnormal ECU is not set with a corresponding configuration item, the inspection node reports the abnormal ECU to the server, receives and analyzes the restart instruction issued by the server and sends it to the abnormal ECU.
- This embodiment corresponds to the electronic control unit management method in the ignition driving state.
- the inspection node uses the CAN bus to receive APP messages of other ECUs, which carry the service state of the ECUs.
- the ECU abnormality can be determined in the ignition state in the following two ways:
- the abnormal state of the ECU may be determined directly according to the failure to normally receive the network management message sent by the ECU. For example, in the ignition state, the normal network management message sending interval from the server is t1, and after t1, if the audit node fails to receive the network management message of the ECU, it can directly determine the status of the ECU abnormal.
- the state of the ECU in the ignition state of the KL15on, can be directly determined to be abnormal by comparing the service state parameters in the ignition state.
- the business state parameters of normal driving can be obtained by sending the server when the device is turned on, or by reading the local storage.
- the abnormal time may be accumulated with the confirmation of the abnormality as the starting time node.
- the abnormal time may be cleared.
- the abnormal time it is further determined whether the accumulated value of the abnormal time exceeds the set maximum abnormal time.
- the maximum abnormality interval is exceeded, it is then determined whether the abnormal ECU is set with a corresponding configuration item.
- an optional implementation may be, after the TBOX is powered on, by receiving the notification message carrying the service parameters of each ECU sent by the server, and parsing the notification message, so as to obtain whether each ECU is provided with a restart switch.
- a restart switch it means that the ECU can be restarted in the ignition state.
- the ECU restart instruction is directly sent to the abnormal ECU, thereby controlling the ECU to perform state recovery in the ignition state.
- the audit node After determining that the abnormal ECU does not have corresponding configuration items, the audit node reports the emergency event of the abnormal ECU business status to the TBOX, which in turn reports it to the CSP server, and the CSP server determines whether to restart the device. If the server side determines that the ECU needs to be restarted, the TBOX receives the restart instruction sent by the server, parses it, and sends it to the corresponding ECU.
- the embodiment of the present application ensures that the abnormal node does not stay in the abnormal working state for a long time by controlling the restart of the abnormal ECU in the ignition state, ensures the stable operation of the vehicle, effectively reduces the number of times the user goes to the 4S store, and improves the user's car experience.
- Embodiments of the present application further provide an electronic control unit, including: the electronic control unit includes a processor, a memory, and a communication bus;
- the communication bus is used to realize the connection communication between the processor and the memory
- the processor is configured to execute one or more computer programs stored in the memory to implement the steps of the electronic control unit management methods on the vehicle of the first, second and third embodiments.
- Embodiments of the present application further provide an automobile, wherein the automobile includes the aforementioned electronic control unit.
- Embodiments of the present application further provide a computer-readable storage medium, where the computer-readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to achieve The steps of the electronic control unit management method on the vehicle of the first, second and third embodiments.
- a control instruction is sent to the abnormal ECU.
- a control instruction is sent to the abnormal ECU.
- the abnormal ECU can perform the corresponding recovery action according to the control command, thereby improving the operation stability of the vehicle ECU, avoiding the vehicle battery feeding caused by the abnormal ECU, and improving the user experience.
- the functional modules/units in the system, and the device can be implemented as software (which can be implemented by computer program codes executable by a computing device). ), firmware, hardware, and their appropriate combination.
- the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical components Components execute cooperatively.
- Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit .
- communication media typically embodies computer readable instructions, data structures, computer program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery, as is well known to those of ordinary skill in the art medium. Therefore, the present application is not limited to any particular combination of hardware and software.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Automation & Control Theory (AREA)
- Mechanical Engineering (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Transportation (AREA)
- Human Computer Interaction (AREA)
- Mathematical Physics (AREA)
- Computer Hardware Design (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Chemical Kinetics & Catalysis (AREA)
- Chemical & Material Sciences (AREA)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
- Combined Controls Of Internal Combustion Engines (AREA)
- Safety Devices In Control Systems (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
Claims (10)
- 一种车辆上的电子控制单元管理方法,包括:对车辆上的至少一个电子控制单元ECU的工作状态进行监测;以及当监测到工作状态异常的异常ECU时,向所述异常ECU发送控制指令,其中所述控制指令用于触发所述异常ECU执行对应的恢复动作。
- 如权利要求1所述的车辆上的电子控制单元管理方法,其中,在所述车辆处于熄火状态下,所述向所述异常ECU发送控制指令至少包括如下中的一种:直接向所述异常ECU发送所述ECU重启指令;确定所述异常ECU的故障代码,若根据所述故障代码确定能通过重启恢复时,向所述异常ECU发送所述ECU重启指令;直接向所述异常ECU发送所述ECU关机指令;确定所述异常ECU的故障代码,若根据所述故障代码确定不能通过重启恢复时,向所述异常ECU发送所述ECU关机指令或所述ECU固件更新指令;直接向所述异常ECU发送所述ECU固件更新指令;按预设重启控制规则向所述异常ECU发送所述ECU重启指令,在监测到所述异常ECU根据所述ECU重启指令重启后仍异常后,向所述异常ECU发送所述ECU关机指令或所述ECU固件更新指令;按预设重启控制规则向所述异常ECU发送所述ECU重启指令,在监测到所述异常ECU根据所述ECU重启指令重启后仍异常后,向所述异常ECU发送所述ECU固件更新指令,若所述异常ECU固件更新后仍异常,向所述异常ECU发送所述ECU关机指令。
- 如权利要求1所述的车辆上的电子控制单元管理方法,其中,在所述车辆处于点火状态下,所述向所述异常ECU发送控制指令至少包括如下中的一种:直接向所述异常ECU发送ECU重启指令;确定所述异常ECU的故障代码,若根据所述故障代码确定能通过重启恢复时,向所述异常ECU发送所述ECU重启指令;确定所述异常ECU的故障代码,若根据所述故障代码确定不能通过重启恢复时,向所述异常ECU发送所述ECU固件更新指令;直接向所述异常ECU发送所述ECU固件更新指令;按预设重启控制规则向所述异常ECU发送所述ECU重启指令,在监测到所述异常ECU根据所述ECU重启指令重启后仍异常后,向所述异常ECU发送所述ECU固件更新指令。
- 如权利要求3所述的车辆上的电子控制单元管理方法,在发送所述ECU重启指令或所述ECU固件更新指令之前,还包括:确定所述异常ECU设置有对应的配置项。
- 如权利要求1-4任一项所述的车辆上的电子控制单元管理方法,其中,监测工作状态异常的异常ECU,包括:接收ECU发送的网络管理报文,所述网络管理报文包含对应ECU的业务状态参数;以及根据所述业务状态参数与所述ECU对应的正常业务状态参数进行对比,确定所述ECU的状态异常。
- 如权利要求5所述的车辆上的电子控制单元管理方法,其中,根据所述业务状态参数 与所述ECU对应的正常业务状态参数进行对比,确定所述ECU的状态异常的方式至少包括如下之一:当所述业务状态参数与正常行驶的业务状态参数不一致时,确定所述ECU的状态异常;当从所述网络管理报文提取到准备休眠状态RSS信息,超过正常处于RSS的维持时间,确定所述ECU的状态异常。
- 如权利要求2-4任一项所述的车辆上的电子控制单元管理方法,其中,对车辆上的至少一个电子控制单元ECU的工作状态进行监测,包括:通过在所述车辆上配置的稽查节点对所述ECU的工作状态进行监测;其中所述稽查节点包括车载移动通信终端和目标ECU中的至少之一。
- 如权利要求7所述的车辆上的电子控制单元管理方法,其中,在所述目标ECU包括多个,且多个所述目标ECU状态异常的情况下,向所述目标ECU发送所述ECU重启指令,包括:在不同的时间点向多个所述目标ECU发送所述ECU重启指令,使多个所述目标ECU在不同的时间点执行重启;或者,在处于异常状态的所述目标ECU的占比超过设定占比阈值的情况下,按照重启顺序向所述目标ECU发送所述ECU重启指令。
- 一种电子控制单元,包括处理器、存储器及通信总线,其中,所述通信总线用于实现处理器和存储器之间的连接通信;以及所述处理器用于执行存储器中存储的一个或者多个计算机程序,以实现如权利要求1至8中任一项所述的车辆上的电子控制单元管理方法的步骤。
- 一种计算机可读存储介质,存储有一个或者多个计算机程序,所述一个或者多个计算机程序可被一个或者多个处理器执行,以实现如权利要求1至8中任一项所述的车辆上的电子控制单元管理方法的步骤。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023519856A JP7508703B2 (ja) | 2020-11-09 | 2021-11-03 | 車両におけるecuの管理方法、ecuおよび可読記憶媒体 |
US18/246,555 US20230367664A1 (en) | 2020-11-09 | 2021-11-03 | Method for managing ecu on vehicle, and ecu and readable storage medium |
CA3193979A CA3193979A1 (en) | 2020-11-09 | 2021-11-03 | Method for managing ecu on vehicle, ecu and computer-readable storage medium |
EP21888593.7A EP4206839A4 (en) | 2020-11-09 | 2021-11-03 | METHOD FOR MANAGING ECU ON A VEHICLE AND ECU AND READABLE STORAGE MEDIUM |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011240019.5 | 2020-11-09 | ||
CN202011240019.5A CN114460913A (zh) | 2020-11-09 | 2020-11-09 | 一种车辆上的ecu管理方法、ecu以及可读存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022095896A1 true WO2022095896A1 (zh) | 2022-05-12 |
Family
ID=81404918
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/128411 WO2022095896A1 (zh) | 2020-11-09 | 2021-11-03 | 一种车辆上的ecu管理方法、ecu以及可读存储介质 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20230367664A1 (zh) |
EP (1) | EP4206839A4 (zh) |
JP (1) | JP7508703B2 (zh) |
CN (1) | CN114460913A (zh) |
CA (1) | CA3193979A1 (zh) |
WO (1) | WO2022095896A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115346287A (zh) * | 2022-07-18 | 2022-11-15 | 北京经纬恒润科技股份有限公司 | 信息配置方法及装置 |
WO2024151445A1 (en) * | 2023-01-10 | 2024-07-18 | Qualcomm Incorporated | Testing mixed safety systems |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20220146131A (ko) * | 2021-04-23 | 2022-11-01 | 현대자동차주식회사 | 차량 및 그 제어 방법 |
CN115396293A (zh) * | 2022-08-23 | 2022-11-25 | 科东(广州)软件科技有限公司 | 一种通信异常处理系统、方法、装置和存储介质 |
CN115583206A (zh) * | 2022-09-30 | 2023-01-10 | 重庆长安汽车股份有限公司 | 一种车辆异常消除方法及装置、电子设备、存储介质 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH1013494A (ja) * | 1996-06-20 | 1998-01-16 | Fujitsu Ltd | 伝送装置及びその復旧方式 |
CN104281071A (zh) * | 2013-07-05 | 2015-01-14 | 广州汽车集团股份有限公司 | 一种ecu的启动方法和ecu启动系统 |
CN104657304A (zh) * | 2013-11-22 | 2015-05-27 | 株式会社电装 | 电子控制单元 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3652232B2 (ja) | 2000-09-28 | 2005-05-25 | Necマイクロシステム株式会社 | マイクロコンピュータのエラー検出方法及びエラー検出回路及びマイクロコンピュータシステム |
JP4397621B2 (ja) | 2003-04-28 | 2010-01-13 | 富士通テン株式会社 | 異常監視装置 |
US11329953B2 (en) * | 2017-03-09 | 2022-05-10 | Argus Cyber Security Ltd. | System and method for providing cyber security to an in-vehicle network |
WO2019142180A1 (en) * | 2018-01-16 | 2019-07-25 | C2A-Sec, Ltd. | Intrusion anomaly monitoring in a vehicle environment |
JP2021067960A (ja) | 2018-02-14 | 2021-04-30 | 日立Astemo株式会社 | 車両監視システム |
US12063236B2 (en) | 2018-10-11 | 2024-08-13 | Nippon Telegraph And Telephone Corporation | Information processing apparatus, log analysis method and program |
-
2020
- 2020-11-09 CN CN202011240019.5A patent/CN114460913A/zh active Pending
-
2021
- 2021-11-03 EP EP21888593.7A patent/EP4206839A4/en active Pending
- 2021-11-03 US US18/246,555 patent/US20230367664A1/en active Pending
- 2021-11-03 CA CA3193979A patent/CA3193979A1/en active Pending
- 2021-11-03 JP JP2023519856A patent/JP7508703B2/ja active Active
- 2021-11-03 WO PCT/CN2021/128411 patent/WO2022095896A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH1013494A (ja) * | 1996-06-20 | 1998-01-16 | Fujitsu Ltd | 伝送装置及びその復旧方式 |
CN104281071A (zh) * | 2013-07-05 | 2015-01-14 | 广州汽车集团股份有限公司 | 一种ecu的启动方法和ecu启动系统 |
CN104657304A (zh) * | 2013-11-22 | 2015-05-27 | 株式会社电装 | 电子控制单元 |
Non-Patent Citations (1)
Title |
---|
See also references of EP4206839A4 * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115346287A (zh) * | 2022-07-18 | 2022-11-15 | 北京经纬恒润科技股份有限公司 | 信息配置方法及装置 |
CN115346287B (zh) * | 2022-07-18 | 2024-06-07 | 北京经纬恒润科技股份有限公司 | 信息配置方法及装置 |
WO2024151445A1 (en) * | 2023-01-10 | 2024-07-18 | Qualcomm Incorporated | Testing mixed safety systems |
Also Published As
Publication number | Publication date |
---|---|
CA3193979A1 (en) | 2022-05-12 |
EP4206839A4 (en) | 2024-03-06 |
US20230367664A1 (en) | 2023-11-16 |
JP2023547782A (ja) | 2023-11-14 |
EP4206839A1 (en) | 2023-07-05 |
CN114460913A (zh) | 2022-05-10 |
JP7508703B2 (ja) | 2024-07-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022095896A1 (zh) | 一种车辆上的ecu管理方法、ecu以及可读存储介质 | |
CN112380045B (zh) | 车辆异常检测方法、装置、设备及存储介质 | |
JP6760813B2 (ja) | ソフトウェア更新装置、ソフトウェア更新方法、ソフトウェア更新システム | |
AU2018374925B2 (en) | Starting method of energy storage system and energy storage device | |
CN113946148B (zh) | 一种基于多ecu协同控制的mcu芯片唤醒系统 | |
CN105313719B (zh) | 一种整车控制器及其唤醒过程监控方法 | |
CN112559003B (zh) | 域控制器软件升级方法、装置及域控制器 | |
US20220055637A1 (en) | Electronic control unit and computer readable medium | |
CN113923137A (zh) | 一种整车总线网络异常监控方法和系统 | |
CN112389352A (zh) | 一种整车静态电流管理系统及方法 | |
CN113467953A (zh) | 服务状态的切换方法、装置、服务器及存储介质 | |
CN113672254A (zh) | 车辆ota升级方法、装置、存储介质和无人驾驶设备 | |
CN115390539A (zh) | 车辆异常休眠诊断方法、装置、车辆及存储介质 | |
CN115230618A (zh) | 车辆及其控制方法 | |
CN114184992A (zh) | 用于验证电源监测的方法、装置和计算机程序 | |
CN117148824B (zh) | 一种故障恢复方法、装置、电子设备、存储介质及车辆 | |
US11579995B2 (en) | Electronic element, system comprising such an electronic element and method for monitoring and cutting off a processor on occurrence of a failure event | |
CN112799370B (zh) | 一种控制装置、车载系统软件还原方法及其系统 | |
CN116521201B (zh) | 电池包的软件升级方法和电池包 | |
RU2816885C2 (ru) | Способ взаимодействия с вычислительным устройством на бортовой шине транспортного средства | |
CN114044000B (zh) | 一种自动驾驶车辆hmi人机交互的安全冗余系统 | |
CN111625420B (zh) | 一种分布式训练任务处理方法、装置、设备及存储介质 | |
CN115387920B (zh) | 车辆远程升级系统、车辆 | |
US20230373500A1 (en) | Management of supervision of an electronic component of a land motor vehicle | |
CN117201375A (zh) | Ecu异常唤醒网络的检测方法、装置、车辆及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21888593 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3193979 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 2023519856 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202327024025 Country of ref document: IN |
|
ENP | Entry into the national phase |
Ref document number: 2021888593 Country of ref document: EP Effective date: 20230327 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |