Upgrading method and related device

Abstract

An upgrading method and a related device are applied to the technical field of networked vehicles. The method is applied to the vehicle, the vehicle comprises a first node, a second node, a first electronic control unit (ECU) and a second electronic control unit (ECU), and the first ECU is connected to the second node; the method comprises the following steps: a first node sends first information, wherein the first information is used for indicating to turn off a first message receiving and transmitting function of a first ECU; the first node sends second information, wherein the second information is used for carrying out OTA upgrading on the first ECU; wherein when the OTA upgrade is carried out on the first ECU, the function of receiving and transmitting the first message by the first ECU is turned off, the function of receiving and transmitting the first message by the second ECU is turned on, and the second ECU is different from the first ECU. According to the method, normal service functions of other ECUs which are not subjected to OTA upgrading can be ensured in the process of carrying out OTA upgrading on part of ECUs.

Description

Upgrading method and related device Technical Field

[0001] The present application relates to the field of connected vehicle technology, and in particular to an upgrading method and related devices. Background Art

[0002] Over the air (OTA) technology is a technology for downloading data via a wireless network. It is now widely used to upgrade devices such as vehicles, televisions, mobile phones, tablets, and set-top boxes. For example, for vehicles, OTA can be used to remotely upgrade or repair vehicle software. The software manager can upload the software to the cloud, and the vehicle can automatically or at the user's option download the software from the cloud to update the local software, thereby achieving functional upgrades or updates to the local vehicle system. For example, the vehicle's electronic control unit (ECU) can be upgraded through OTA, and the upgrade of the ECU can achieve an upgrade of vehicle performance. Due to the convenience of OTA upgrades, OTA technology is being used more and more widely.

[0003] However, in order to ensure the success rate of flashing, the current OTA upgrade will shut down the vehicle application message communication. Since the underlying business communication is disconnected, the ECU of the vehicle may not be able to provide normal business functions during the OTA upgrade process.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide an upgrade method and related devices, which can ensure the normal business functions of other ECUs that are not undergoing OTA upgrades during the OTA upgrade of some ECUs.

[0006] In a first aspect, an embodiment of the present application provides an upgrade method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method is applied to a vehicle, which includes a first node, a second node, a first electronic control unit ECU, and a second electronic control unit ECU, wherein the first ECU is connected to the second node; the method includes:

[0007] The first node sends first information, where the first information is used to instruct the first ECU to shut down a function of sending and receiving a first message;

[0008] The first node sends second information, where the second information is used to perform an over-the-air (OTA) upgrade on the first ECU;

[0009] When the first ECU is OTA upgraded, the function of the first ECU receiving and sending the first message is turned off, and the function of the second ECU receiving and sending the first message is turned on, and the second ECU is different from the first ECU.

[0010] In an embodiment of the present application, an upgrade method is provided, which is applied to a vehicle, wherein a first node of the vehicle sends first information and second information, wherein the first information is used to indicate to shut down the function of the first ECU connected to the second node of the vehicle to send and receive the first message, and the second information is used to perform OTA upgrade on the first ECU. By sending the first information and the second information, the first node of the vehicle can make it possible to shut down the function of the first ECU to send and receive the first message when the first ECU is OTA upgraded, and turn on the function of the second ECU of the vehicle to send and receive the first message.

[0011] In the embodiment of the present application, the function of the first ECU to send and receive the first message can be understood as sending and receiving the first message based on the in-vehicle wired network communication connected to the first ECU. Correspondingly, shutting off the function of the first ECU to send and receive the first message can be understood as shutting off the communication function of the in-vehicle wired network connected to the first ECU.

[0012] Compared with the currently commonly used OTA upgrade method of shutting down the vehicle application message communication to ensure the success rate of flashing, the upgrade method in the embodiment of the present application can send the first information and the second information to a specific node (second node) in the vehicle through multicast transmission or point-to-point transmission, and can indicate to shut down the function of the ECU connected to the second node to send and receive the first message, thereby performing an OTA upgrade on the ECU connected to the second node. At the same time, the ECUs connected to the nodes that have not received the first information and the second information (other nodes except the second node) can normally send and receive the first message and provide normal business functions. Through the embodiment of the present application, it is possible to ensure the normal business functions of other ECUs that are not undergoing OTA upgrades while performing OTA upgrades on some ECUs.

[0013] It is understandable that the above-mentioned vehicles can be replaced by terminal devices, which can be drones, flying cars, ships, mobile robots, etc., which need to download data through wireless networks to update local software.

[0014] In a possible implementation, a processing priority of the upgrade message corresponding to the OTA upgrade is lower than a processing priority of the first message.

[0015] In an embodiment of the present application, a possible specific implementation of the processing priority of the first message is provided, specifically, the processing priority of the upgrade message corresponding to the OTA upgrade is lower than the processing priority of the first message.

[0016] The upgrade message corresponding to the OTA upgrade in the embodiment of the present application can be a diagnostic message, specifically a diagnostic message in the unified diagnostic service (UDS) standard protocol, used to flash the diagnostic message to the ECU to achieve the OTA upgrade. The first message in the embodiment of the present application can be an application message, specifically an application message for low-level service communication within the vehicle, used to ensure that each ECU in the vehicle provides normal service functions.

[0017] In an embodiment of the present application, under the vehicle bus architecture, the processing priority of the upgrade message (diagnostic message) corresponding to the OTA upgrade is lower than the processing priority of the application message (first message) of the underlying business communication in the vehicle. Therefore, in order to avoid frame loss during the OTA upgrade of the first ECU, the first node sends a first information instruction to shut down the function of the first ECU connected to the second node to send and receive the first message, making way for the diagnostic message flashing during the OTA upgrade, thereby ensuring the success rate of the diagnostic message flashing and realizing the OTA upgrade of the first ECU.

[0018] In a possible implementation manner, the vehicle further includes a third node, which is different from the second node, and the second ECU is an ECU connected to the third node.

[0019] In an embodiment of the present application, a possible specific implementation of a second ECU is provided, specifically, the second ECU is different from the first ECU, the second ECU is an ECU connected to the third node, the first ECU is an ECU connected to the second node, and the third node and the second node are different nodes in the vehicle.

[0020] The second and third nodes in the embodiments of the present application can be understood as nodes within the vehicle, such as a vehicle integration unit (VIU) or virtual private gateway (VGW), used for information forwarding and network interconnection. Each of the second and third nodes has one or more ECUs connected to it. These ECUs transmit and receive messages through the message routing and forwarding functions of the second or third node, enabling underlying service communications within the vehicle and providing corresponding service functions.

[0021] In an embodiment of the present application, for the scenario of multiple nodes (VIU / VGW) in the vehicle, multiple ECUs in the vehicle can be grouped according to different VIU / VGWs, and multiple ECUs hanging under the same VIU / VGW can be regarded as the same group, and multiple ECUs hanging under different VIU / VGWs can be regarded as different groups. By sending the first information and the second information to a specific VIU / VGW (second node) in the vehicle, it can be instructed to shut down the function of receiving and sending the first message to the ECUs in the same group hanging under the VIU / VGW (second node), thereby realizing the shutdown of the communication message of the local VIU / VGW (second node) in the vehicle, thereby performing OTA upgrades on the ECUs in the same group hanging under the VIU / VGW (second node), and ensuring that the communication messages of the ECUs hanging under other VIU / VGW (third node) that have not received the first information and the second information are normally sent and received, providing normal business functions.

[0022] In a possible implementation manner, the first information is further used to instruct to shut down a function of the second node to send and receive the first message.

[0023] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, the first information is also used to instruct the second node to shut down its function of receiving and sending the first message. For scenarios with multiple nodes (VIU / VGW) in a vehicle, by sending the first information to a specific node (the second node) in the vehicle, it is possible to instruct the ECU connected to the second node to shut down its function of receiving and sending the first message. It is also possible to instruct the second node to shut down its function of routing and forwarding the first message, thereby shutting down the communication message of the local node (the second node) in the vehicle, thereby performing an OTA upgrade on the ECU connected to the node.

[0024] Optionally, the first node sends indication information to instruct the third node to enable a function of sending and receiving the first message.

[0025] Optionally, the indication information is further used to instruct the ECU connected to the third node to enable a function of sending and receiving the first message.

[0026] Optionally, the indication information and the first information are carried in different messages, or the indication information and the first information are carried in different fields of the same message.

[0027] Optionally, the function of the third node to send and receive the first message is enabled by default.

[0028] Optionally, the function of the ECU connected to the third node to send and receive the first message is turned on by default.

[0029] In one possible implementation, the first ECU is an ECU connected to a first in-vehicle wired network, the second ECU is an ECU connected to a second in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

[0030] In an embodiment of the present application, a possible specific implementation of a second ECU is provided, specifically, the second ECU is different from the first ECU, the second ECU is an ECU connected to the second in-vehicle wired network, the first ECU is an ECU connected to the first in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

[0031] The second node in the embodiments of the present application can be understood as a vehicle integration unit (VIU) or virtual private gateway (VGW) within the vehicle, a node used for information forwarding and network interconnection. The second node is connected to multiple in-vehicle wired networks, each of which is connected to one or more ECUs. These ECUs send and receive messages through their respective in-vehicle wired networks and the message routing and forwarding function of the second node, implementing low-level service communications within the vehicle and providing corresponding service functions.

[0032] In the embodiment of the present application, for the scenario where there are multiple in-car wired networks hanging under the second node in the car, the multiple ECUs in the car can be grouped according to different in-car wired networks, and the multiple ECUs connected to the same in-car wired network are regarded as the same group, and the multiple ECUs connected to different in-car wired networks are regarded as different groups. By sending the first information and the second information to a specific node (the second node) in the car, it can be instructed to shut down the function of sending and receiving the first message to the ECUs of the same group connected to one or more in-car wired networks (the first in-car wired network) hanging under the second node, thereby realizing the shutdown of the communication message of the local in-car wired network (the first in-car wired network) hanging under the second node in the car, thereby performing OTA upgrade on the same group of ECUs connected to the local in-car wired network (the first in-car wired network), and ensuring that the communication message of the ECUs connected to other in-car wired networks (the second in-car wired network) hanging under the second node in the car are sent and received normally, providing normal business functions.

[0033] In a possible implementation manner, the first in-vehicle wired network and the second in-vehicle wired network have the same wired network standard, for example, both are Controller Area Network (CAN) or both are Ethernet.

[0034] In an embodiment of the present application, a possible specific implementation of an in-vehicle wired network is provided, specifically, the first in-vehicle wired network and the second in-vehicle wired network corresponding to the second node have the same wired network format, which can be both controller area network (CAN) or both Ethernet. It is understandable that when the first in-vehicle wired network is a first CAN line and the second in-vehicle wired network is a second CAN line, by sending the first information and the second information to a specific node (the second node) in the vehicle, it is possible to instruct to shut down the function of receiving and sending the first message to the same group of ECUs connected to the first CAN line under the second node, thereby realizing the shutdown of the communication message of the local CAN line (the first CAN line) under the second node in the vehicle, thereby performing OTA upgrade on the same group of ECUs connected to the local CAN line (the first CAN line), and ensuring that the communication message of the ECUs connected to the other CAN lines (the second CAN lines) under the second node in the vehicle are normally sent and received, providing normal business functions.

[0035] In one possible implementation, the method further includes:

[0036] The first node sends third information, where the third information is used to instruct the second node to shut down a function of sending and receiving a first message corresponding to the first in-vehicle wired network.

[0037] In an embodiment of the present application, a possible specific implementation method of shutting down the function of the second node to receive and send the first message corresponding to the first in-vehicle wired network is provided, specifically, the first node sends a third message, and the third message is used to indicate the shutdown of the function of the second node to receive and send the first message corresponding to the first in-vehicle wired network. For the scenario where there are multiple in-vehicle wired networks hanging under the second node in the vehicle, since the ECUs connected to some of the in-vehicle wired networks (the first in-vehicle wired network) hanging under the second node need to shut down the function of receiving and sending the first message for OTA upgrade, the ECUs connected to other in-vehicle wired networks (the second in-vehicle wired network) hanging under the second node need to turn on the function of receiving and sending the first message to provide normal business functions, so the function of the second node to route and forward the first message cannot be completely shut down. Through the embodiments of the present application, third information can be sent to a specific node (second node) in the vehicle through multicast transmission or point-to-point transmission, instructing to shut down the function of the second node to route and forward the first message corresponding to the first in-vehicle wired network, thereby realizing the shutdown of the communication message of the local in-vehicle wired network (first in-vehicle wired network) hanging under the second node, thereby performing OTA upgrade on the ECU connected to the local in-vehicle wired network (first in-vehicle wired network).

[0038] In a possible implementation, the third information is further used to instruct to enable a function of the second node to send and receive the first message corresponding to the second in-vehicle wired network.

[0039] In an embodiment of the present application, a possible specific implementation method of turning on the function of the second node to receive and send the first message corresponding to the second in-vehicle wired network is provided. Specifically, the third information is also used to indicate the function of turning on the second node to receive and send the first message corresponding to the second in-vehicle wired network. For the scenario where there are multiple in-vehicle wired networks hanging under the second node in the vehicle, since the ECUs connected to some of the in-vehicle wired networks (the first in-vehicle wired network) hanging under the second node need to turn off the function of receiving and sending the first message for OTA upgrade, the ECUs connected to other in-vehicle wired networks (the second in-vehicle wired network) hanging under the second node need to turn on the function of receiving and sending the first message to provide normal business functions, so the function of the second node to route and forward the first message cannot be completely turned off. Through the embodiments of the present application, third information can be sent to a specific node (second node) in the vehicle through multicast transmission or point-to-point transmission, instructing the second node to open the function of routing and forwarding the first message corresponding to the second in-vehicle wired network, thereby realizing the opening of the communication message of the local in-vehicle wired network (second in-vehicle wired network) hanging under the second node, thereby ensuring that while the ECU connected to the first in-vehicle wired network is being OTA upgraded, the ECU connected to the second in-vehicle wired network can provide normal business functions.

[0040] Optionally, the function of the second node sending and receiving the first message corresponding to the second in-vehicle wired network is turned on by default.

[0041] Optionally, the function of the ECU connected to the second in-vehicle wired network to send and receive the first message is turned on by default.

[0042] Optionally, the third information and the first information are carried in different messages, or the third information and the first information are carried in different fields of the same message.

[0043] In one possible implementation, the first information includes at least a first field and a second field, the first field being used to indicate whether the function of the ECU connected to the second node to send and receive the first message is turned off, and the second field being used to indicate whether the function of the ECU connected to the third node to send and receive the first message is turned off.

[0044] In an embodiment of the present application, a possible specific implementation of the first information is provided. Specifically, the first information includes at least a first field and a second field. The first field corresponds to the second node and is used to indicate whether the function of sending and receiving application messages of the ECU connected to the second node is turned off. The second field corresponds to the third node and is used to indicate whether the function of sending and receiving application messages of the ECU connected to the third node is turned off. Through this embodiment of the present application, it is possible to ensure the normal business functions of other ECUs that are not undergoing OTA upgrades during the OTA upgrade of some ECUs.

[0045] In one possible implementation, the method further includes:

[0046] The first node sends fourth information, where the fourth information is used to instruct to shut down the function of all or some of the ECUs in the vehicle to send and receive the first message.

[0047] In an embodiment of the present application, a possible specific implementation method for shutting down ECUs in a vehicle is provided. Specifically, a first node transmits fourth information, which is used to instruct the shutdown of the function of all or some ECUs in the vehicle to receive and send the first message. Through this embodiment of the present application, the entire vehicle can be silenced to perform an OTA upgrade on the entire vehicle, or some ECUs can be silenced to perform an OTA upgrade on the silenced ECUs.

[0048] In a second aspect, an embodiment of the present application provides an upgrade method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method is applied to a vehicle, which includes a first node, a second node, a first electronic control unit ECU, and a second electronic control unit ECU, wherein the first ECU is connected to the second node; the method includes:

[0049] The second node receives first information from the first node, where the first information is used to instruct to shut down a function of the first ECU to send and receive the first message;

[0050] The second node receives second information from the first node, where the second information is used to perform an over-the-air (OTA) upgrade on the first ECU;

[0051] When the first ECU is OTA upgraded, the function of the first ECU receiving and sending the first message is turned off, and the function of the second ECU receiving and sending the first message is turned on, and the second ECU is different from the first ECU.

[0052] In an embodiment of the present application, an upgrade method is provided, which is applied to a vehicle, wherein a second node of the vehicle receives first information and second information from a first node, wherein the first information is used to indicate to shut down the function of the first ECU connected to the second node of the vehicle to receive and send a first message, and the second information is used to perform an OTA upgrade on the first ECU. By sending the first information and the second information, the first node of the vehicle can make the function of the first ECU receiving and sending the first message shut down when the first ECU is OTA upgraded, and the function of the second ECU of the vehicle receiving and sending the first message turn on.

[0053] In the embodiment of the present application, the function of the first ECU to send and receive the first message can be understood as sending and receiving the first message based on the in-vehicle wired network communication connected to the first ECU. Correspondingly, shutting off the function of the first ECU to send and receive the first message can be understood as shutting off the communication function of the in-vehicle wired network connected to the first ECU.

[0054] Compared with the currently commonly used OTA upgrade method of shutting down the vehicle application message communication to ensure the success rate of flashing, the upgrade method in the embodiment of the present application can send the first information and the second information to a specific node (second node) in the vehicle through multicast transmission or point-to-point transmission, and can indicate to shut down the function of the ECU connected to the second node to send and receive the first message, thereby performing an OTA upgrade on the ECU connected to the second node. At the same time, the ECUs connected to the nodes that have not received the first information and the second information (other nodes except the second node) can normally send and receive the first message and provide normal business functions. Through the embodiment of the present application, it is possible to ensure the normal business functions of other ECUs that are not undergoing OTA upgrades while performing OTA upgrades on some ECUs.

[0055] It is understandable that the above-mentioned vehicles can be replaced by terminal devices, which can be drones, flying cars, ships, mobile robots, etc., which need to download data through wireless networks to update local software.

[0056] In a possible implementation, a processing priority of the upgrade message corresponding to the OTA upgrade is lower than a processing priority of the first message.

[0057] In an embodiment of the present application, a possible specific implementation of the processing priority of the first message is provided, specifically, the processing priority of the upgrade message corresponding to the OTA upgrade is lower than the processing priority of the first message.

[0058] The upgrade message corresponding to the OTA upgrade in the embodiment of the present application can be a diagnostic message, specifically a diagnostic message in the unified diagnostic service (UDS) standard protocol, used to flash the diagnostic message to the ECU to achieve the OTA upgrade. The first message in the embodiment of the present application can be an application message, specifically an application message for low-level service communication within the vehicle, used to ensure that each ECU in the vehicle provides normal service functions.

[0059] In an embodiment of the present application, under the vehicle bus architecture, the processing priority of the upgrade message (diagnostic message) corresponding to the OTA upgrade is lower than the processing priority of the application message (first message) of the underlying business communication in the vehicle. Therefore, in order to avoid frame loss during the OTA upgrade of the first ECU, the first node sends a first information instruction to shut down the function of the first ECU connected to the second node to send and receive the first message, making way for the diagnostic message flashing during the OTA upgrade, thereby ensuring the success rate of the diagnostic message flashing and realizing the OTA upgrade of the first ECU.

[0060] In a possible implementation manner, the vehicle further includes a third node, which is different from the second node, and the second ECU is an ECU connected to the third node.

[0061] In an embodiment of the present application, a possible specific implementation of a second ECU is provided, specifically, the second ECU is different from the first ECU, the second ECU is an ECU connected to the third node, the first ECU is an ECU connected to the second node, and the third node and the second node are different nodes in the vehicle.

[0062] The second and third nodes in the embodiments of the present application can be understood as nodes within the vehicle, such as a vehicle integration unit (VIU) or virtual private gateway (VGW), used for information forwarding and network interconnection. Each of the second and third nodes has one or more ECUs connected to it. These ECUs transmit and receive messages through the message routing and forwarding functions of the second or third node, enabling underlying service communications within the vehicle and providing corresponding service functions.

[0063] In an embodiment of the present application, for the scenario of multiple nodes (VIU / VGW) in the vehicle, multiple ECUs in the vehicle can be grouped according to different VIU / VGWs, and multiple ECUs hanging under the same VIU / VGW can be regarded as the same group, and multiple ECUs hanging under different VIU / VGWs can be regarded as different groups. By sending the first information and the second information to a specific VIU / VGW (second node) in the vehicle, it can be instructed to shut down the function of receiving and sending the first message to the ECUs in the same group hanging under the VIU / VGW (second node), thereby realizing the shutdown of the communication message of the local VIU / VGW (second node) in the vehicle, thereby performing OTA upgrades on the ECUs in the same group hanging under the VIU / VGW (second node), and ensuring that the communication messages of the ECUs hanging under other VIU / VGW (third node) that have not received the first information and the second information are normally sent and received, providing normal business functions.

[0064] In a possible implementation manner, the first information is further used to instruct to shut down a function of the second node to send and receive the first message.

[0065] In an embodiment of the present application, a possible specific implementation of the first information is provided, specifically, the first information is also used to instruct the second node to shut down its function of receiving and sending the first message. For scenarios with multiple nodes (VIU / VGW) in a vehicle, by sending the first information to a specific node (the second node) in the vehicle, it is possible to instruct the ECU connected to the second node to shut down its function of receiving and sending the first message. It is also possible to instruct the second node to shut down its function of routing and forwarding the first message, thereby shutting down the communication message of the local node (the second node) in the vehicle, thereby performing an OTA upgrade on the ECU connected to the node.

[0066] In one possible implementation, the first ECU is an ECU connected to a first in-vehicle wired network, the second ECU is an ECU connected to a second in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

[0067] In an embodiment of the present application, a possible specific implementation of a second ECU is provided, specifically, the second ECU is different from the first ECU, the second ECU is an ECU connected to the second in-vehicle wired network, the first ECU is an ECU connected to the first in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

[0068] The second node in the embodiments of the present application can be understood as a vehicle integration unit (VIU) or virtual private gateway (VGW) within the vehicle, a node used for information forwarding and network interconnection. The second node is connected to multiple in-vehicle wired networks, each of which is connected to one or more ECUs. These ECUs send and receive messages through their respective in-vehicle wired networks and the message routing and forwarding function of the second node, implementing low-level service communications within the vehicle and providing corresponding service functions.

[0069] In the embodiment of the present application, for the scenario where there are multiple in-car wired networks hanging under the second node in the car, the multiple ECUs in the car can be grouped according to different in-car wired networks, and the multiple ECUs connected to the same in-car wired network are regarded as the same group, and the multiple ECUs connected to different in-car wired networks are regarded as different groups. By sending the first information and the second information to a specific node (the second node) in the car, it can be instructed to shut down the function of sending and receiving the first message to the ECUs of the same group connected to one or more in-car wired networks (the first in-car wired network) hanging under the second node, thereby realizing the shutdown of the communication message of the local in-car wired network (the first in-car wired network) hanging under the second node in the car, thereby performing OTA upgrade on the same group of ECUs connected to the local in-car wired network (the first in-car wired network), and ensuring that the communication message of the ECUs connected to other in-car wired networks (the second in-car wired network) hanging under the second node in the car are sent and received normally, providing normal business functions.

[0070] In a possible implementation manner, the first in-vehicle wired network and the second in-vehicle wired network have the same wired network standard, for example, both are Controller Area Network (CAN) or both are Ethernet.

[0071] In an embodiment of the present application, a possible specific implementation of an in-vehicle wired network is provided, specifically, the first in-vehicle wired network and the second in-vehicle wired network corresponding to the second node have the same wired network format, which can be both controller area network (CAN) or both Ethernet. It is understandable that when the first in-vehicle wired network is a first CAN line and the second in-vehicle wired network is a second CAN line, by sending the first information and the second information to a specific node (the second node) in the vehicle, it is possible to instruct to shut down the function of receiving and sending the first message to the same group of ECUs connected to the first CAN line under the second node, thereby realizing the shutdown of the communication message of the local CAN line (the first CAN line) under the second node in the vehicle, thereby performing OTA upgrade on the same group of ECUs connected to the local CAN line (the first CAN line), and ensuring that the communication message of the ECUs connected to the other CAN lines (the second CAN lines) under the second node in the vehicle are normally sent and received, providing normal business functions.

[0072] In one possible implementation, the method further includes:

[0073] The second node receives third information from the first node, where the third information is used to instruct the second node to shut down a function of receiving and sending a first message corresponding to the first in-vehicle wired network.

[0074] In an embodiment of the present application, a possible specific implementation method for shutting down the function of the second node to receive and send the first message corresponding to the first in-vehicle wired network is provided, specifically, the second node receives third information from the first node, and the third information is used to indicate the shutdown of the function of the second node to receive and send the first message corresponding to the first in-vehicle wired network. For the scenario where there are multiple in-vehicle wired networks hanging under the second node in the vehicle, since the ECUs connected to some of the in-vehicle wired networks (the first in-vehicle wired network) hanging under the second node need to shut down the function of receiving and sending the first message for OTA upgrade, the ECUs connected to other in-vehicle wired networks (the second in-vehicle wired network) hanging under the second node need to turn on the function of receiving and sending the first message to provide normal business functions, so the function of the second node to route and forward the first message cannot be completely shut down. Through the embodiments of the present application, third information can be sent to a specific node (second node) in the vehicle through multicast transmission or point-to-point transmission, instructing to shut down the function of the second node to route and forward the first message corresponding to the first in-vehicle wired network, thereby realizing the shutdown of the communication message of the local in-vehicle wired network (first in-vehicle wired network) hanging under the second node, thereby performing OTA upgrade on the ECU connected to the local in-vehicle wired network (first in-vehicle wired network).

[0075] In a possible implementation, the third information is further used to instruct to enable a function of the second node to send and receive the first message corresponding to the second in-vehicle wired network.

[0076] In an embodiment of the present application, a possible specific implementation method of turning on the function of the second node to receive and send the first message corresponding to the second in-vehicle wired network is provided. Specifically, the third information is also used to indicate the function of turning on the second node to receive and send the first message corresponding to the second in-vehicle wired network. For the scenario where there are multiple in-vehicle wired networks hanging under the second node in the vehicle, since the ECUs connected to some of the in-vehicle wired networks (the first in-vehicle wired network) hanging under the second node need to turn off the function of receiving and sending the first message for OTA upgrade, the ECUs connected to other in-vehicle wired networks (the second in-vehicle wired network) hanging under the second node need to turn on the function of receiving and sending the first message to provide normal business functions, so the function of the second node to route and forward the first message cannot be completely turned off. Through the embodiments of the present application, third information can be sent to a specific node (second node) in the vehicle through multicast transmission or point-to-point transmission, instructing the second node to open the function of routing and forwarding the first message corresponding to the second in-vehicle wired network, thereby realizing the opening of the communication message of the local in-vehicle wired network (second in-vehicle wired network) hanging under the second node, thereby ensuring that while the ECU connected to the first in-vehicle wired network is being OTA upgraded, the ECU connected to the second in-vehicle wired network can provide normal business functions.

[0077] Optionally, the function of the second node sending and receiving the first message corresponding to the second in-vehicle wired network is turned on by default.

[0078] Optionally, the function of the ECU connected to the second in-vehicle wired network to send and receive the first message is turned on by default.

[0079] Optionally, the third information and the first information are carried in different messages, or the third information and the first information are carried in different fields of the same message.

[0080] In one possible implementation, the first information includes at least a first field and a second field, the first field being used to indicate whether the function of the ECU connected to the second node to send and receive the first message is turned off, and the second field being used to indicate whether the function of the ECU connected to the third node to send and receive the first message is turned off.

[0081] In an embodiment of the present application, a possible specific implementation of the first information is provided. Specifically, the first information includes at least a first field and a second field. The first field corresponds to the second node and is used to indicate whether the function of sending and receiving application messages of the ECU connected to the second node is turned off. The second field corresponds to the third node and is used to indicate whether the function of sending and receiving application messages of the ECU connected to the third node is turned off. Through this embodiment of the present application, it is possible to ensure the normal business functions of other ECUs that are not undergoing OTA upgrades during the OTA upgrade of some ECUs.

[0082] In one possible implementation, the method further includes:

[0083] The second node receives fourth information from the first node, where the fourth information is used to instruct to shut down a function of all or some of the ECUs in the vehicle to send and receive the first message.

[0084] In an embodiment of the present application, a possible specific implementation method for shutting down ECUs in a vehicle is provided. Specifically, a first node transmits fourth information, which is used to instruct the shutdown of the function of all or some ECUs in the vehicle to receive and send the first message. Through this embodiment of the present application, the entire vehicle can be silenced to perform an OTA upgrade on the entire vehicle, or some ECUs can be silenced to perform an OTA upgrade on the silenced ECUs.

[0085] In a third aspect, an embodiment of the present application provides a communication device, which includes a module or unit for executing any method described in the first aspect.

[0086] In one possible design, the apparatus includes:

[0087] a communication unit, configured to send a first message, wherein the first message is used to instruct the first ECU to shut down a function of sending and receiving a first message;

[0088] The communication unit is further configured to send second information, where the second information is used to perform an over-the-air (OTA) upgrade on the first ECU;

[0089] When the first ECU is OTA upgraded, the function of the first ECU receiving and sending the first message is turned off, and the function of the second ECU receiving and sending the first message is turned on, and the second ECU is different from the first ECU.

[0090] In one possible implementation, the device further includes:

[0091] A processing unit is configured to generate the first information and / or the second information.

[0092] In a possible implementation, a processing priority of the upgrade message corresponding to the OTA upgrade is lower than a processing priority of the first message.

[0093] In a possible implementation manner, the third node is different from the second node, and the second ECU is an ECU connected to the third node.

[0094] In a possible implementation manner, the first information is further used to instruct to shut down a function of the second node to send and receive the first message.

[0095] In one possible implementation, the first ECU is an ECU connected to a first in-vehicle wired network, the second ECU is an ECU connected to a second in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

[0096] In a possible implementation manner, the first in-vehicle wired network and the second in-vehicle wired network have the same wired network standard, for example, both are Controller Area Network (CAN) or both are Ethernet.

[0097] In a possible implementation, the communication unit is further configured to send third information, where the third information is configured to instruct to shut down a function of the second node to send and receive the first message corresponding to the first in-vehicle wired network.

[0098] In a possible implementation, the third information is further used to instruct to enable a function of the second node to send and receive the first message corresponding to the second in-vehicle wired network.

[0099] In one possible implementation, the first information includes at least a first field and a second field, the first field being used to indicate whether the function of the ECU connected to the second node to send and receive the first message is turned off, and the second field being used to indicate whether the function of the ECU connected to the third node to send and receive the first message is turned off.

[0100] In a possible implementation, the communication unit is further configured to send fourth information, where the fourth information is used to instruct to shut down the function of all or some of the ECUs in the vehicle to send and receive the first message.

[0101] Regarding the technical effects brought about by the third aspect and any possible implementation method, please refer to the introduction of the technical effects corresponding to the first aspect and the corresponding implementation method.

[0102] In a fourth aspect, an embodiment of the present application provides a communication device, which includes a module or unit for executing the method as described in any one of the second aspects.

[0103] In one possible design, the apparatus includes:

[0104] a communication unit, configured to receive first information from a first node, wherein the first information is used to instruct to shut down a function of the first ECU to send and receive a first message;

[0105] The communication unit is further configured to receive second information from the first node, where the second information is used to perform an over-the-air (OTA) upgrade on the first ECU;

[0106] When the first ECU is OTA upgraded, the function of the first ECU receiving and sending the first message is turned off, and the function of the second ECU receiving and sending the first message is turned on, and the second ECU is different from the first ECU.

[0107] In one possible implementation, the device further includes:

[0108] A processing unit is configured to determine whether to forward the first information and / or the second information to the first ECU.

[0109] In a possible implementation, a processing priority of the upgrade message corresponding to the OTA upgrade is lower than a processing priority of the first message.

[0110] In a possible implementation manner, the third node is different from the communication device, and the second ECU is an ECU connected to the third node.

[0111] In a possible implementation manner, the first information is further used to instruct to shut down the function of the communication device to send and receive the first message.

[0112] In one possible implementation, the first ECU is an ECU connected to a first in-vehicle wired network, the second ECU is an ECU connected to a second in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the communication device.

[0113] In a possible implementation manner, the first in-vehicle wired network and the second in-vehicle wired network have the same wired network standard, for example, both are Controller Area Network (CAN) or both are Ethernet.

[0114] In a possible implementation, the communication unit is further configured to receive third information from the first node, where the third information is used to instruct to shut down a function of the communication device to send and receive the first message corresponding to the first in-vehicle wired network.

[0115] In a possible implementation, the third information is further used to instruct to enable a function of the communication device to send and receive the first message corresponding to the second in-vehicle wired network.

[0116] In one possible implementation, the first information includes at least a first field and a second field, the first field being used to indicate whether the function of the ECU connected to the communication device to send and receive the first message is turned off, and the second field being used to indicate whether the function of the ECU connected to the third node to send and receive the first message is turned off.

[0117] In a possible implementation, the communication unit is further configured to receive fourth information from the first node, where the fourth information is used to instruct to shut down the function of all or some of the ECUs in the vehicle to send and receive the first message.

[0118] Regarding the technical effects brought about by the fourth aspect and any possible implementation method, please refer to the introduction of the technical effects corresponding to the second aspect and the corresponding implementation method.

[0119] Optionally, in the communication device described in any one of the third to fourth aspects and any possible implementation manner:

[0120] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication unit may be a transceiver or an input / output interface; and the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0121] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0122] In a fifth aspect, embodiments of the present application provide a communication device comprising a processor. The processor is coupled to a memory and can be configured to execute instructions in the memory to implement the method of any of the first and second aspects described above and any possible implementation methods. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

[0123] In a sixth aspect, embodiments of the present application provide a communication device, comprising: a logic circuit and a communication interface. The communication interface is configured to receive or send information; the logic circuit is configured to receive or send information via the communication interface, so that the communication device executes the method of any of the first and second aspects above, and any possible implementation thereof.

[0124] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program (also referred to as code, or instructions); when the computer program is run on a computer, the method of any one of the above-mentioned first to second aspects and any possible implementation method is implemented.

[0125] In an eighth aspect, an embodiment of the present application provides a computer program product, comprising: a computer program (also referred to as code, or instructions); when the computer program is run, it enables the computer to execute any one of the above-mentioned first to second aspects and any possible implementation method.

[0126] In a ninth aspect, an embodiment of the present application provides a chip, comprising a processor configured to execute instructions. When the processor executes the instructions, the chip performs the method of any one of the first and second aspects and any possible implementation methods described above. Optionally, the chip further comprises a communication interface configured to receive or send signals.

[0127] In the tenth aspect, an embodiment of the present application provides a vehicle end, which includes at least one communication device as described in the third aspect, or the communication device as described in the fourth aspect, or the communication device as described in the fifth aspect, or the communication device as described in the sixth aspect, or the chip as described in the ninth aspect.

[0128] In the eleventh aspect, an embodiment of the present application provides a system, which includes a first node and a second node, wherein the first node is used to execute the method of the above-mentioned first aspect and any possible implementation method, and the second node is used to execute the method of the above-mentioned second aspect and any possible implementation method.

[0129] In addition, in the process of executing the method described in any aspect of the first aspect to the second aspect and any possible implementation method, the process of sending information and / or receiving information in the above method can be understood as the process of the processor outputting information and / or the process of the processor receiving input information. When outputting information, the processor can output the information to the transceiver (or communication interface, or sending module) so that it can be transmitted by the transceiver. After the information is output by the processor, it may also need to undergo other processing before it reaches the transceiver. Similarly, when the processor receives input information, the transceiver (or communication interface, or sending module) receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, the information may need to undergo other processing before it is input into the processor.

[0130] Based on the above principles, for example, the sending of information mentioned in the above method can be understood as the processor outputting information. For another example, the receiving of information can be understood as the processor receiving input information.

[0131] Optionally, for the operations such as transmission, sending and receiving involved in the processor, if there is no special explanation, or if they do not conflict with their actual functions or internal logic in the relevant description, they can be more generally understood as processor output, reception, input and other operations.

[0132] Optionally, in the process of executing the method described in any aspect of the first to second aspects and any possible implementation method, the processor may be a processor specifically used to execute these methods, or a processor that executes these methods by executing computer instructions in a memory, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or may be separately provided on different chips. The embodiments of the present application do not limit the type of memory and the configuration of the memory and the processor.

[0133] In a possible implementation, the at least one memory is located outside the device.

[0134] In yet another possible implementation, the at least one memory is located within the device.

[0135] In another possible implementation, part of the at least one memory is located inside the device, and another part of the memory is located outside the device.

[0136] In this application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0137] In the embodiment of the present application, it is possible to ensure the normal business functions of other ECUs that are not undergoing OTA upgrades during the OTA upgrade of some ECUs. BRIEF DESCRIPTION OF THE DRAWINGS

[0138] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0139] FIG1 is a schematic diagram of the architecture of a vehicle upgrade system according to an embodiment of the present application;

[0140] FIG2 is a schematic diagram of the architecture of a vehicle provided in an embodiment of the present application;

[0141] FIG3 is a schematic diagram of the architecture of a vehicle based on a central computing architecture provided in an embodiment of the present application;

[0142] FIG4A is a schematic diagram of a vehicle topology architecture provided in an embodiment of the present application;

[0143] FIG4B is a schematic diagram of a vehicle topology architecture provided in an embodiment of the present application;

[0144] FIG5A is a schematic diagram of an ECU programming process provided in an embodiment of the present application;

[0145] FIG5B is a schematic diagram of an ECU programming process provided in an embodiment of the present application;

[0146] FIG6 is a schematic diagram of a vehicle system upgrade architecture provided in an embodiment of the present application;

[0147] FIG7 is a schematic diagram of a flow chart of an upgrade method provided in an embodiment of the present application;

[0148] FIG8 is a schematic diagram of an OTA flashing process provided in an embodiment of the present application;

[0149] FIG9 is a schematic diagram of an OTA flashing process provided in an embodiment of the present application;

[0150] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0151] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0152] FIG12 is a schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0153] In order to make the purpose, technical solutions and advantages of this application clearer, the embodiments of this application will be described below in conjunction with the drawings in the embodiments of this application.

[0154] The terms "first" and "second" in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to the process, method, product, or device.

[0155] The “embodiment” mentioned herein means that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It can be understood explicitly and implicitly by those skilled in the art that in the various embodiments of the present application, unless otherwise specified and there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment according to their inherent logical relationship.

[0156] It should be understood that in the present application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0157] It should be noted that in this application, "indication" can include direct indication, indirect indication, explicit indication, and implicit indication. When describing that a certain indication information is used to indicate A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.

[0158] In this application, the information indicated by the indication information is referred to as the information to be indicated. In specific implementations, there are many ways to indicate the information to be indicated. For example, but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or an index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, where the other information is associated with the information to be indicated. Alternatively, only a portion of the information to be indicated can be indicated, while the rest of the information to be indicated is known or agreed upon in advance. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-specified) order of the various information, thereby reducing indication overhead to a certain extent. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. The transmission period and / or transmission timing of these sub-information can be the same or different. The specific transmission method is not limited in this application. The transmission period and / or transmission timing of these sub-information can be pre-defined, for example, according to a protocol, or can be configured by the transmitting device sending configuration information to the receiving device.

[0159] It should be noted that in this application, "send" can be understood as "output" and "receive" can be understood as "input". "Send information to A", where "to A" only indicates the direction of information transmission, A is the destination, and does not limit "sending information to A" to direct transmission on the air interface. "Sending information to A" includes sending information directly to A, and also includes sending information indirectly to A through a transmitter, so "sending information to A" can also be understood as "outputting information to A". Similarly, "receiving information from A" indicates that the source of the information is A, including receiving information directly from A, and also including receiving information indirectly from A through a receiver, so "receiving information from A" can also be understood as "inputting information from A".

[0160] Please refer to FIG1 , which is a schematic diagram of a vehicle upgrade system provided in an embodiment of the present application.

[0161] As shown in FIG1 , the upgrade system includes: an OTA server (server) 101, an OTA master module (Master) 102, and an OTA slave module (slave) 103.

[0162] The OTA server 101 is used to send the upgrade data packet to the OTA Master. In some specific implementation scenarios, the OTA server is also called the OTA cloud.

[0163] The OTA master module (Master) 102 is an electronic device capable of transmitting and receiving data. It receives upgrade packages from the OTA server 101 and updates the vehicle's components based on these packages. Specifically, the OTA master module 102 distributes the received upgrade packages to one or more OTA slave modules 103 in the vehicle, instructing them to install and activate the upgrade packages, completing the upgrade.

[0164] Please refer to FIG. 2 , which is a schematic diagram of a possible vehicle architecture provided in an embodiment of the present application.

[0165] As shown in FIG2 , the vehicle architecture includes: OTA cloud 201 and vehicle 202 .

[0166] Vehicle 202 is based on the vehicle's electrical / electronic architecture (E / E), as shown in area 203. Vehicle 202 may include the following components: a mobile data center (MDC), a human-machine interaction (HMI), a gateway (GW), a telematics box (Tbox or TCU), an electronic control unit (ECU), and other modules. The GW is a core component of the vehicle's E / E architecture. As the data exchange hub for the entire vehicle network, it can route network data from different networks, such as the control area network (CAN), local interconnect network (LIN), media-oriented system transport (MOST), and FlexRay. The MDC is the vehicle's intelligent onboard computing platform. The T-BOX is primarily used to communicate with the vehicle's external systems, backend systems, and mobile applications. The HMI is the vehicle's infotainment system. The ECU is a dedicated microcomputer controller for the vehicle.

[0167] An update master module (which can be considered an OTA master) is deployed in the GW of vehicle 202, and an update slave module (which can be considered an OTA slave) is deployed in the remaining modules of vehicle 202. The update master module in the GW receives the upgrade package sent by the OTA cloud and distributes it to the upgrade slave modules of the corresponding components, so that the upgrade slave modules install and activate the upgrade package to complete the upgrade of the components. It can be seen that the upgrade master module in the GW is responsible for downloading the upgrade package of the entire vehicle and directing each component to install it. This will bring a heavy burden to the storage and load of the upgrade master module. For example, if the upgrade package is very large, there may be a problem of insufficient storage space in the upgrade master module.

[0168] In addition, since the vehicle 202 in Figure 2 is a vehicle based on an electronic and electrical architecture, the GW is a core component in the electronic and electrical architecture of the entire vehicle. Therefore, the upgrade main module can be deployed in the GW to reduce the complexity of routing. However, in other vehicle architectures, as the number of components increases and the structure becomes complex, if the upgrade main module is used to upgrade an ECU that is far away (where the long distance can be understood as a large number of hops required from the upgrade main module to the ECU to be upgraded), it will also affect the efficiency of the vehicle upgrade.

[0169] Please refer to FIG3 , which is a schematic diagram of the architecture of a vehicle based on a central computing architecture provided in an embodiment of the present application.

[0170] As shown in FIG3 , vehicle 30 is a vehicle based on a central computing architecture (CCA). The CCA includes several vehicle integrated / integration units (VIUs) and multiple automotive components. Multiple VIUs form a ring network to achieve high bandwidth (high-definition cameras, high-definition displays), low latency, and high-reliability processing capabilities to continuously improve competitiveness, simplify vehicle network configuration, and improve upgrade and maintenance efficiency. Automotive components (such as ECUs, Tboxes, etc.) can be connected to the VIU, or can be connected to a domain controller (DC) such as a cockpit domain controller (CDC), MDC, or vehicle domain controller (VDC), and then connected to the VIU via the DC. In this way, the traditional system for realizing electronic control functions in a vehicle avoids the need for each component of the vehicle to be connected to the domain control unit DC through its own wiring harness, which is conducive to reducing the length of the wiring harness in the system for realizing electronic control functions in the vehicle.

[0171] It is understandable that, compared to the automotive electrical / electronic architecture (E / E) used by vehicle 202 in FIG. 2 , among the multiple components of vehicle 30, some are connected to VIU1 (e.g., ECU2.1, ECU2.2, Tbox, etc.), some are connected to VIU2 (e.g., ECU4.1, ECU4.2, ECU4.3, etc.), some are connected to VIU3 (e.g., ECU5.1, ECU5.2, ECU5.3, etc.), and some are connected to VIU4 (e.g., ECU6.1, ECU6.2, ECU6.3, etc.). In this case, if the upgrade master module is deployed in the Tbox, for ECU5.1 that needs to be upgraded, the path of the distributed upgrade package will pass through the buses of VIU1, VIU2, and VIU3, and then through VIU3 to ECU5.1. It can be seen that due to the complexity of the upgrade route (which can be understood as the large number of hops), the method of distributing the upgrade package through the upgrade master node will increase the complexity of the vehicle upgrade and also affect the efficiency.

[0172] It should be noted that in the architecture shown in Figure 3, the connection lines in each node can be an Ethernet-based bus, or one or more of a controller area network (CAN) bus, a local interconnect network (LIN) bus, a multimedia oriented system transport (MOST) bus, FlexRay, etc.

[0173] It will be understood that the vehicle upgrade system schematic diagram shown in FIG1 is merely an example, and the vehicle architecture schematic diagrams shown in FIG2 and FIG3 are merely examples. For other forms of vehicle upgrade system schematic diagrams and vehicle architecture schematic diagrams, reference may be made to relevant standards or protocols, etc., which will not be described in detail here.

[0174] The various embodiments shown below may be applicable to the vehicle upgrade system shown in FIG. 1 and the vehicle architectures shown in FIG. 2 and FIG. 3 , and may also be applicable to other forms of vehicle upgrade systems and vehicle architectures, which will not be described in detail below.

[0175] This application provides an upgrade method that is applied to the field of connected vehicle technology, such as OTA upgrade of connected vehicles. In order to more clearly describe the solution of this application, some knowledge related to OTA upgrade is first introduced below.

[0176] Over the air (OTA) technology is a technology for downloading data via a wireless network. It is now widely used to upgrade vehicles, televisions, mobile phones, tablets, set-top boxes and other devices. For example, for vehicles, OTA can be used to remotely upgrade the internal firmware and software data of each controller in the vehicle. The software manager can upload the software to the cloud, and the vehicle can automatically or at the user's option download the software from the cloud to update the local software, thereby achieving functional upgrades or updates to the local vehicle system. For example, the vehicle's electronic control unit (ECU) can be upgraded through OTA, and the upgrade of the ECU can achieve an upgrade of the vehicle's performance. Due to the convenience of OTA upgrades, OTA technology is being used more and more widely.

[0177] Unified Diagnostic Service (UDS): This is a standardized protocol used by the automotive industry to diagnose and locate ECU faults. For example, it specifies the instructions to send to the ECU to read fault codes and the instructions to send to read data streams. In other words, it uses a set of instruments (generally called a host computer) to analyze the information and data within the vehicle's ECU. The language used by these instruments to communicate with the ECU is UDS.

[0178] Diagnostic service 31 service: also known as routine service, its full English name is Routine Control service. It can initiate the start, stop or obtain the results of routine execution through the diagnostic instrument / host computer through relevant diagnostic commands. Its common usage scenarios are erasing memory, resetting defined data, or detecting refresh conditions when refreshing the ECU.

[0179] Diagnostic Service 85: Controls the reporting or restoration of diagnostic trouble codes (DTCs).

[0180] Diagnostic Service 28: Mainly used for sending and receiving messages in the network, for example, controlling the sending and receiving of application messages, or controlling the sending and receiving of network management messages, so as to meet application requirements in certain scenarios.

[0181] Generally speaking, the main application scenarios for diagnostic services 28 are as follows:

[0182] (1) There are some special test scenarios, such as only wanting to receive or send corresponding network management messages and application messages;

[0183] (2) In most cases, it is used in the process of flashing the ECU. That is, executing the 28 service function addressing under pre-programmed conditions can suppress the sending and receiving of bus application messages and network management messages, so as to reduce the network bus load and improve the ECU download efficiency. At the same time, after the flashing is completed, the 28 service must be executed to enable the sending and receiving of the corresponding control messages. In this process, it is generally used in conjunction with the 85 service.

[0184] During traditional OTA upgrades, the ECU uses the unified diagnostic service (UDS) diagnostic protocol for OTA flashing. However, in the vehicle bus architecture, since the processing priority of UDS diagnostic messages is lower than the processing priority of application messages from the controller area network (CAN) bus, in order to avoid frame loss during diagnostic message flashing and ensure the success rate of OTA flashing, the OTA client will broadcast the diagnostic service 28 service (function addressing, whole-network broadcast) in advance to keep the vehicle ECU in silent communication.

[0185] Due to the disconnection of underlying service communications, the entire vehicle cannot provide normal service functions. To enhance the user experience of the entire smart car during the OTA flash process, for example, when upgrading ECUs outside the three-domain electric domain (such as intelligent driving, intelligent cockpit, body domain, and chassis domain), the three-domain electric domain ECUs, including the high-voltage power supply system, such as the battery management system (BMS), thermal management system (TMS), vehicle control unit (VCU) / vehicle direct communication (VDC), etc., must maintain normal operation, and the vehicle can maintain normal high-voltage operation. For example, when the body domain is not upgraded, functions such as doors, windows, and seat massage can maintain normal operation. For another example, when the high-voltage upgrade is maintained, the air conditioning can function, and the body domain's audio, video, and lighting functions are effective. To achieve these goals, a special solution is required to ensure application message communication between the corresponding ECUs.

[0186] The above OTA flashing process is further described below with reference to FIG. 4A and FIG. 4B .

[0187] Please refer to FIG. 4A , which is a schematic diagram of a vehicle topology architecture provided in an embodiment of the present application.

[0188] As shown in Figure 4A, the vehicle topology includes a VIU / GW, which is connected to one or more ECUs via different CAN lines. The VIU / GW is connected to the CDC subsystem via one CAN line, the VDC subsystem via another CAN line, and the body domain ECUs, including but not limited to the body control module (BCM), passive entry passive start (PEPS), and public key cryptosystems (PKC), via another CAN line. The VIU / GW is connected to the chassis domain ECUs, including but not limited to the electronic stability program (ESP) and electric power steering (EPS), via another CAN line. The VIU / GW is connected to the three electrical domain ECUs, including but not limited to the thermal management system (TMS), battery management system (BMS), and high-voltage power distribution unit (PDU), via another CAN line.

[0189] In Figure 4A, the OTA client sends the diagnostic service 28 to the VIU / GW. After receiving the 28 service, the VIU / GW turns off the application message routing and forwarding function, and forwards the 28 service to each ECU under it. After receiving the 28 service, each ECU turns off the application message sending and receiving function, so that the ECUs under the VIU / GW maintain communication silence, making way for the UDS diagnostic message flashing of each ECU.

[0190] Please refer to FIG. 4B , which is a schematic diagram of a vehicle topology architecture provided in an embodiment of the present application.

[0191] As shown in Figure 4B, the vehicle topology includes multiple VIUs / GWs, each connected to one or more ECUs via different CAN lines. The multiple VIUs form a ring network. One VIU connects to the CDC subsystem and the VDC subsystem via two CAN lines. Another VIU connects to the body-domain ECU and chassis-domain ECU via two CAN lines. The body-domain ECUs include but are not limited to BCM, PEPS, and PKC, while the chassis-domain ECUs include but are not limited to ESP and EPS. Yet another VIU connects to the powertrain-domain ECU and body-domain ECU via two CAN lines. The powertrain-domain ECUs include but are not limited to TMS, BMS, and PDU.

[0192] In Figure 4B, the OTA client sends diagnostic service 28 to multiple VIU / GWs. After receiving the 28 services, the multiple VIU / GWs turn off the application message routing and forwarding function, and forward the 28 services to each ECU hanging under them. After receiving the 28 services, each ECU turns off the application message sending and receiving function, so that the various ECUs hanging under the multiple VIU / GWs maintain communication silence, making way for the UDS diagnostic message flashing of each ECU.

[0193] In Figures 4A and 4B above, since the 28 service of the VIU / GW can only support one processing mode (turning on or off the function of sending and receiving application messages), the VIU / GW itself will not be divided into different VIU / GW groups or CAN groups in order to avoid conflicts in the switch of sending and receiving application messages. The currently commonly used upgrade method generally turns off the function of sending and receiving application messages (functional addressing) for the entire network (VGW / VIU), and then uses multiple OTA Client processes to install and control the ECU in a point-to-point upgrade (physical addressing) for different VIU / GW groups or CAN groups. After the upgrade and reset of the ECU (after resetting the ECU, the ECU will automatically turn on the application message communication function), the 28 service is sent again through physical addressing to turn off the ECU's application message communication function. This ensures that the CAN line communication is silent when other ECUs on the CAN line are upgraded.

[0194] The following further illustrates the ECU programming during the above OTA flashing process with reference to FIG. 5A and FIG. 5B .

[0195] Please refer to FIG5A , which is a schematic diagram of an ECU programming process provided in an embodiment of the present application.

[0196] Figure 5A shows the process for programming an ECU. During the pre-programming phase, the function of reporting diagnostic trouble codes (DTCs) is disabled through Diagnostic Service 85, and the function of sending and receiving application messages is disabled through Diagnostic Service 28. During the programming phase, diagnostic messages are flashed to the ECU through Diagnostic Services 34, 36, and 37. The ECU can be any of the ECUs shown in Figures 4A and 4B. During the post-programming phase, the ECU is reset through Diagnostic Service 11, and the function of sending and receiving application messages is enabled through Diagnostic Service 28. Finally, the function of reporting DTCs is enabled through Diagnostic Service 85.

[0197] Please refer to FIG5B , which is a schematic diagram of an ECU programming process provided in an embodiment of the present application.

[0198] As shown in Figure 5B, this is the process of parallel programming of ECUs on different CAN lines. In the pre-programming stage, the function of reporting DTCs for the entire vehicle / network segment is turned off through the diagnostic service 85 service, and the function of sending and receiving application messages for the entire vehicle / network segment is turned off through the diagnostic service 28 service. In the programming stage, diagnostic messages are flashed to ECUs on different CAN lines in parallel through the diagnostic services 34, 36, and 37 services. The ECUs on different CAN lines can be the ECUs on the CAN lines corresponding to the vehicle body domain, chassis domain, and three-electric domain in Figure 4A above. In the post-programming stage, the ECUs on different CAN lines are reset through the diagnostic service 11 service, and the function of sending and receiving application messages is turned on through the diagnostic service 28 service. Finally, the function of reporting DTCs is turned on through the diagnostic service 85 service.

[0199] As shown in Figures 4A and 4B above, in order to ensure the success rate of flashing, the current OTA upgrade will shut down the vehicle application message communication. Since the underlying business communication is disconnected, the ECU of the vehicle may not be able to provide normal business functions during the OTA upgrade process.

[0200] In response to the technical problem that the vehicle ECU cannot provide normal business functions during the above-mentioned OTA upgrade process, an embodiment of the present application provides an upgrade architecture for a vehicle system, and proposes a new upgrade method based on the upgrade architecture, which can ensure the normal business functions of other ECUs that are not undergoing OTA upgrades during the OTA upgrade of some ECUs.

[0201] Please refer to FIG. 6 , which is a schematic diagram of a vehicle system upgrade architecture provided in an embodiment of the present application.

[0202] As shown in Figure 6, the vehicle system upgrade architecture mainly includes an OTA controller module, a UDS installer module, a VIU / VGW, and an ECU. The OTA controller module and the UDS installer module can together form the X sensor data center (XDC) intelligent system. The VIU / VGW is connected between the XDC intelligent system and each ECU in the vehicle. The OTA controller module is used to control the OTA upgrade of the vehicle's ECUs, and the UDS installer module is used to flash diagnostic messages to the vehicle's ECUs. The OTA controller module and the UDS installer module work together to ensure the normal business functions of other ECUs that are not undergoing OTA upgrades during the OTA upgrade of some ECUs.

[0203] Based on the vehicle system upgrade architecture shown in FIG6 , the embodiment of the present application also provides a new upgrade method, which will be described below in conjunction with FIG7 .

[0204] Please refer to Figure 7, which is a flow chart of an upgrade method provided in an embodiment of the present application. The upgrade method is applied to the field of connected vehicle technology, such as OTA upgrade of connected vehicles. Specifically, the upgrade method is applied to a vehicle, which includes a first node, a second node, a first electronic control unit (ECU), and a second ECU, wherein the first ECU is connected to the second node; the upgrade method includes but is not limited to the following steps:

[0205] S701: A first node sends first information to a second node. Correspondingly, the second node receives the first information from the first node.

[0206] S702: The first node sends second information to the second node. Correspondingly, the second node receives the second information from the first node.

[0207] It is understood that the first node in the embodiment of the present application is a device equipped with a processor / chip that can be used to execute computer-executable instructions, and can also be a processor / chip that can be used to execute computer-executable instructions, and the embodiment of the present application does not limit this. Optionally, the first node can be a processor / chip in a connected car, for example, specifically the OTA control (OTA controller) module in Figure 6 above, or it can also be the UDS installation (UDS installer) module in Figure 6 above, or it can also be the XDC intelligent system composed of the OTA controller module and the UDS installer module in Figure 6 above, which is used to execute the upgrade method in the embodiment of the present application to ensure the normal business functions of other ECUs that are not undergoing OTA upgrades during the OTA upgrade of some ECUs.

[0208] It is understood that the second node in the embodiments of the present application is a device equipped with a processor / chip capable of executing computer-executable instructions, or may be a processor / chip capable of executing computer-executable instructions, and the embodiments of the present application are not limited thereto. Optionally, the second node may be a processor / chip within a connected vehicle, for example, specifically the VIU / VGW in FIG6 , which is used to participate in executing the upgrade method in the embodiments of the present application to ensure the normal service functions of other ECUs not undergoing OTA upgrades during the OTA upgrade of some ECUs.

[0209] It is understandable that the first ECU and the second ECU in the embodiment of the present application can be called "driving computers", "on-board computers", etc. In terms of use, they are automobile-specific microcomputer controllers, also called automobile-specific single-chip microcomputers. Like ordinary single-chip microcomputers, they are composed of a central processing unit (CPU), memory, input / output interface, analog-to-digital converter, and large-scale integrated circuits such as shaping and driving. Optionally, the first ECU and the second ECU can specifically be the ECUs in Figure 6 above, which are used to participate in the execution of the upgrade method in the embodiment of the present application, so as to achieve the normal business functions of other second ECUs that are not undergoing OTA upgrades during the OTA upgrade of the first ECU.

[0210] It is understandable that the vehicle in the embodiment of the present application can be replaced by a terminal device, which can be a drone, flying car, ship, mobile robot, etc., which needs to download data through a wireless network to update local software. The embodiment of the present application does not make specific limitations on this.

[0211] The first information is used to instruct to shut down the function of the first ECU connected to the second node of the vehicle to send and receive the first message, and the second information is used to perform OTA upgrade on the first ECU.

[0212] Specifically, by sending the first information and the second information, the first node of the vehicle can shut down the function of the first ECU receiving and sending the first message when the first ECU is OTA upgraded, and the function of the second ECU of the vehicle receiving and sending the first message is turned on.

[0213] Optionally, the first information may specifically be a UDS diagnostic service 28 service, which is used to shut down a function of the first ECU connected to the second node of the vehicle to send and receive the first message.

[0214] Optionally, the first node sends the first information and the second information to the second node. Specifically, the first information and the second information can be sent to a specific node (second node) in the vehicle through multicast sending or point-to-point sending. This embodiment of the present application is not limited to this.

[0215] The first message in the embodiment of the present application may be an application message, specifically an application message for underlying business communications within the vehicle, used to ensure that each ECU within the vehicle provides normal business functions.

[0216] In the embodiment of the present application, the function of the first ECU to send and receive the first message can be understood as sending and receiving the first message based on the in-vehicle wired network communication connected to the first ECU. Correspondingly, shutting off the function of the first ECU to send and receive the first message can be understood as shutting off the communication function of the in-vehicle wired network connected to the first ECU.

[0217] Similarly, the function of the second ECU receiving and sending the first message is similar to the function of the first ECU receiving and sending the first message. The principle of turning on the function of the second ECU receiving and sending the first message is similar to the principle of turning off the function of the first ECU receiving and sending the first message, which will not be repeated here.

[0218] Currently, in order to ensure the success rate of flashing, OTA upgrades will shut down the vehicle application message communication. Since the underlying business communication is disconnected, the vehicle's ECU may not be able to provide normal business functions during the OTA upgrade process.

[0219] Compared with the currently commonly used OTA upgrade method of shutting down the application message communication of the entire vehicle to ensure the success rate of flashing, the upgrade method in the embodiment of the present application can send the first information and the second information to a specific node (second node) in the vehicle through multicast sending or point-to-point sending, and can instruct to shut down the function of the ECU connected to the second node to send and receive the first message, thereby performing OTA upgrade on the ECU connected to the second node. At the same time, the ECUs connected to those nodes (other nodes except the second node) that have not received the first information and the second information can normally send and receive the first message and provide normal business functions.

[0220] Through the embodiments of the present application, it is possible to ensure the normal business functions of other ECUs that are not undergoing OTA upgrades during the OTA upgrade of some ECUs.

[0221] In a possible embodiment, the upgrade message corresponding to the OTA upgrade of the first ECU used by the above-mentioned second information may be a diagnostic message, specifically a diagnostic message in the unified diagnostic service (UDS) standard protocol, which is used to flash the diagnostic message of the ECU to achieve OTA upgrade.

[0222] It can be understood that under the vehicle bus architecture including but not limited to those shown in Figures 4A and 4B above, the processing priority of the upgrade message (diagnostic message) corresponding to the OTA upgrade is lower than the processing priority of the application message (first message) of the underlying business communication in the vehicle. Therefore, in order to avoid frame loss during the OTA upgrade of the first ECU, the first node sends a first information instruction to shut down the function of the first ECU connected to the second node to send and receive the first message, making way for the diagnostic message flashing during the OTA upgrade, thereby ensuring the success rate of the diagnostic message flashing and realizing the OTA upgrade of the first ECU.

[0223] In a possible embodiment, the first node of the vehicle sends the first information and the second information so that when the first ECU is OTA upgraded, the function of the first ECU to send and receive the first message is turned off, and the function of the second ECU of the vehicle to send and receive the first message is turned on. The specific application scenarios and implementation methods are as follows:

[0224] Case 1:

[0225] The first ECU is an ECU connected to the second node, and the second ECU is an ECU connected to the third node.

[0226] It is understood that the third node in the embodiments of the present application is similar to the second node described above. The third node is a device equipped with a processor / chip capable of executing computer-executable instructions. Alternatively, it may be a processor / chip capable of executing computer-executable instructions, and the embodiments of the present application are not limited thereto. Optionally, the third node may be a processor / chip within a connected vehicle, for example, the VIU / VGW described in FIG6 , which participates in the upgrade method described in the embodiments of the present application to ensure the normal operation of other ECUs not undergoing OTA upgrades during the OTA upgrade of some ECUs.

[0227] The third node and the second node can be understood as nodes such as a vehicle integration unit (VIU) or virtual private gateway (VGW) within the vehicle that forward information and implement network interconnection. These nodes (VIU / VGW) are different nodes within the vehicle, and the third node and the second node (VIU / VGW) form a ring network. The second and third nodes each connect to one or more ECUs via different CAN lines. These ECUs transmit and receive messages through the message routing and forwarding functions of the second or third node, enabling underlying service communications within the vehicle and providing corresponding service functions.

[0228] For the scenario of multiple nodes (VIU / VGW) in the vehicle, multiple ECUs in the vehicle can be grouped according to different VIU / VGWs. Multiple ECUs hanging under the same VIU / VGW can be regarded as the same group, and multiple ECUs hanging under different VIU / VGWs can be regarded as different groups.

[0229] By sending the first information and the second information to a specific VIU / VGW (second node) in the vehicle, it can be instructed to shut down the function of the ECU (first ECU) of the same group hanging under the VIU / VGW (second node) to send and receive the first message, thereby realizing the shutdown of the communication message of the local VIU / VGW (second node) in the vehicle, thereby performing OTA upgrade on the ECU (first ECU) of the same group hanging under the VIU / VGW (second node), and ensuring that the communication messages of the ECU (second ECU) hanging under other VIU / VGW (third node) that have not received the first information and the second information are normally sent and received, thereby providing normal business functions.

[0230] For example, taking FIG. 4B as an example, the second node, the third node, the first ECU, and the second ECU are further described:

[0231] The second node may be a VIU to which a body domain ECU and a chassis domain ECU are connected via two CAN lines respectively. The body domain ECU includes but is not limited to BCM, PEPS, PKC, etc., and the chassis domain ECU includes but is not limited to ESP, EPS, etc.

[0232] It can be understood that the first ECU connected to the second node is the body domain ECU and chassis domain ECU connected to the second node through two CAN lines respectively. These ECUs send and receive messages through the message routing and forwarding function of the second node to realize the underlying business communication within the vehicle, thereby providing corresponding business functions.

[0233] The third node may be a VIU to which a power domain ECU and a body domain ECU are connected via two CAN lines respectively. The power domain ECU includes but is not limited to a TMS, a BMS, a PDU, and the like.

[0234] It can be understood that the second ECU connected to the third node is the power domain ECU and the body domain ECU connected to the third node through two CAN lines respectively. These ECUs send and receive messages through the message routing and forwarding function of the third node, realize the underlying business communication within the vehicle, and thus provide corresponding business functions.

[0235] In Figure 4B, by sending the first and second information to a specific VIU (second node) in the vehicle, the ECUs (first ECU) in the same group connected to the VIU (second node) can be instructed to shut down the function of sending and receiving the first message. The group of ECUs includes the body domain ECU and chassis domain ECU connected to the second node via two CAN lines. This can achieve the shutdown of communication messages of the local VIU (second node) in the vehicle, thereby performing an OTA upgrade on the ECUs (first ECU) in the same group connected to the VIU (second node). It also ensures that the communication messages of other ECUs (second ECUs) connected to the VIU (third node) that have not received the first and second information can be normally sent and received, providing normal business functions. The group of ECUs includes the power domain ECU and body domain ECU connected to the third node via two CAN lines.

[0236] Through the embodiments of the present application, by grouping ECUs through the ring network VIU (for multiple VIU scenarios), local VIU communication message shutdown can be achieved, thereby ensuring that the ECU business functions of non-flashing VIUs are normal.

[0237] Optionally, the first information is further used to instruct to shut down the function of the second node to send and receive the first message.

[0238] For the scenario of multiple nodes (VIU / VGW) in the vehicle, by sending the first information to a specific node (the second node) in the vehicle, it can instruct the ECU under the second node to shut down the function of sending and receiving the first message, and it can also instruct the second node to shut down the function of routing and forwarding the first message, thereby realizing the shutdown of the communication message of the local node (the second node) in the vehicle, and thus performing OTA upgrade on the ECU under the node.

[0239] Optionally, the first node further sends instruction information for instructing the third node to enable a function of sending and receiving the first message.

[0240] Optionally, the indication information is also used to instruct the ECU connected to the third node to open a function of sending and receiving the first message.

[0241] Optionally, the indication information and the above-mentioned first information can be carried in different messages, or the indication information and the above-mentioned first information can be carried in different fields of the same message, which is not limited in the embodiment of the present application.

[0242] Optionally, the function of the third node to send and receive the first message is turned on by default. It can be understood that, in this case, the first node does not need to send an indication message to enable the function of the third node to send and receive the first message.

[0243] Optionally, the function of the ECU connected to the third node to send and receive the first message is turned on by default. It can be understood that in this case, the first node does not need to send an indication message to enable the function of the third node to send and receive the first message.

[0244] Case 2:

[0245] The first ECU is an ECU connected to a first in-vehicle wired network, and the second ECU is an ECU connected to a second in-vehicle wired network.

[0246] The first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

[0247] The second node can be understood as a vehicle integration unit (VIU) or virtual private gateway (VGW) within the vehicle, a node used for information forwarding and network interconnection. This second node connects to multiple in-vehicle wired networks, each of which is connected to one or more ECUs. These ECUs send and receive messages through their respective in-vehicle wired networks and the message routing and forwarding capabilities of the second node, enabling underlying service communications within the vehicle and providing corresponding service functions.

[0248] For the scenario where there are multiple in-vehicle wired networks connected to the second node in the vehicle, multiple ECUs in the vehicle can be grouped according to different in-vehicle wired networks. Multiple ECUs connected to the same in-vehicle wired network can be regarded as the same group, and multiple ECUs connected to different in-vehicle wired networks can be regarded as different groups.

[0249] By sending the first information and the second information to a specific node (the second node) in the vehicle, it can be instructed to shut down the function of sending and receiving the first message of the same group of ECUs connected to one or more in-vehicle wired networks (the first in-vehicle wired network) hanging under the second node, thereby realizing the shutdown of the communication message of the local in-vehicle wired network (the first in-vehicle wired network) hanging under the second node in the vehicle, thereby performing OTA upgrade on the same group of ECUs connected to the local in-vehicle wired network (the first in-vehicle wired network), and ensuring the normal sending and receiving of communication messages of the ECUs connected to other in-vehicle wired networks (the second in-vehicle wired network) hanging under the second node in the vehicle, thereby providing normal business functions.

[0250] For example, taking FIG. 4A above as an example, the second node, the first in-vehicle wired network, the second in-vehicle wired network, the first ECU, and the second ECU are further described:

[0251] The second node may be a VIU / GW to which one or more ECUs are connected via different CAN lines. Specifically, the second node is connected to a body domain ECU via a CAN line (the first in-vehicle wired network), and the body domain ECU includes but is not limited to BCM, PEPS, PKC, etc.

[0252] It can be understood that the first ECU connected to the first in-vehicle wired network hanging under the second node is a body domain ECU hung on the second node through a CAN line. These ECUs send and receive messages through the message routing and forwarding function of the first in-vehicle wired network hanging under the second node, realize the underlying business communication within the vehicle, and thus provide corresponding business functions.

[0253] The second node may be a VIU / GW to which one or more ECUs are connected via different CAN lines. Specifically, the second node is connected to a chassis domain ECU via another CAN line (a second in-vehicle wired network), and the chassis domain ECU includes but is not limited to ESP, EPS, etc.

[0254] It can be understood that the second ECU connected to the second in-vehicle wired network hanging under the second node is a chassis domain ECU hung on the second node through a CAN line. These ECUs send and receive messages through the message routing and forwarding function of the second in-vehicle wired network hanging under the second node, realize the underlying business communication within the vehicle, and thus provide corresponding business functions.

[0255] In FIG4A , by sending first and second information to a specific node (second node) within the vehicle, the first message transmission and reception function of the same group of ECUs (first ECU) connected to one or more in-vehicle wired networks (first in-vehicle wired networks) connected to the second node can be shut down. The group of ECUs includes the body-domain ECU connected to the second node via a CAN line. This can achieve the shutdown of communication messages of the local in-vehicle wired network (first in-vehicle wired network) connected to the second node within the vehicle, thereby performing an OTA upgrade on the same group of ECUs (first ECU) connected to the local in-vehicle wired network (first in-vehicle wired network). Furthermore, the normal transmission and reception of communication messages by ECUs (second ECUs) connected to other in-vehicle wired networks (second in-vehicle wired networks) connected to the second node within the vehicle is ensured, providing normal service functions. The group of ECUs includes the chassis-domain ECU connected to the second node via a CAN line.

[0256] Through the embodiments of the present application, by grouping ECUs through CAN lines (for scenarios with multiple CAN lines), local CAN line communication message shutdown can be achieved, thereby ensuring that the ECU business functions in the non-flashing network segment are normal.

[0257] Optionally, the first in-vehicle wired network and the second in-vehicle wired network have the same wired network standard.

[0258] For example, they may be both controller area networks (CAN) or both Ethernet, which is not limited in the embodiment of the present application.

[0259] It can be understood that when the first in-vehicle wired network is the first CAN line and the second in-vehicle wired network is the second CAN line, by sending the first information and the second information to a specific node (the second node) in the vehicle, it can be instructed to shut down the function of sending and receiving the first message of the same group of ECUs connected to the first CAN line hanging under the second node, thereby realizing the shutdown of the communication message of the local CAN line (the first CAN line) hanging under the second node in the vehicle, thereby performing OTA upgrade on the same group of ECUs connected to the local CAN line (the first CAN line), and ensuring that the communication messages of the ECUs connected to other CAN lines (the second CAN line) hanging under the second node in the vehicle are sent and received normally, providing normal business functions.

[0260] It is understood that the above-mentioned communication connection can be understood as a wireless connection or a wired connection for information exchange, and the embodiments of the present application are not limited to this. Among them, the wireless connection can be understood as the VIU communicating with other units in the car without going through the bus, for example, Bluetooth communication or Wi-Fi communication can be used. The wired connection can be understood as the VIU communicating with other units in the car based on the bus, for example, the controller area network (CAN) bus, local interconnect network (LIN) bus Ethernet communication technology, and new wired transmission methods that may appear in the future can be used.

[0261] Optionally, the first node also sends third information.

[0262] The third information is used to instruct to shut down the function of the second node to send and receive the first message corresponding to the first in-vehicle wired network.

[0263] Optionally, the third information may specifically be a UDS diagnostic service 31 service, which is used to shut down a function of sending and receiving a first message corresponding to a first in-vehicle wired network with a second node of the vehicle.

[0264] For the scenario where there are multiple in-vehicle wired networks hanging under the second node in the vehicle, since the ECUs connected to some of the in-vehicle wired networks (first in-vehicle wired networks) hanging under the second node need to turn off the function of sending and receiving the first message for OTA upgrade, the ECUs connected to other in-vehicle wired networks (second in-vehicle wired networks) hanging under the second node need to turn on the function of sending and receiving the first message to provide normal business functions. Therefore, the function of the second node to route and forward the first message cannot be completely turned off.

[0265] Through the embodiments of the present application, third information can be sent to a specific node (second node) in the vehicle through multicast transmission or point-to-point transmission, instructing to shut down the function of the second node to route and forward the first message corresponding to the first in-vehicle wired network, thereby realizing the shutdown of the communication message of the local in-vehicle wired network (first in-vehicle wired network) hanging under the second node, thereby performing OTA upgrade on the ECU connected to the local in-vehicle wired network (first in-vehicle wired network).

[0266] Optionally, the third information is also used to instruct to enable the function of the second node to send and receive the first message corresponding to the second in-vehicle wired network.

[0267] For the scenario where there are multiple in-vehicle wired networks hanging under the second node in the vehicle, since the ECUs connected to some of the in-vehicle wired networks (first in-vehicle wired networks) hanging under the second node need to turn off the function of sending and receiving the first message for OTA upgrade, the ECUs connected to other in-vehicle wired networks (second in-vehicle wired networks) hanging under the second node need to turn on the function of sending and receiving the first message to provide normal business functions. Therefore, the function of the second node to route and forward the first message cannot be completely turned off.

[0268] Through the embodiments of the present application, third information can be sent to a specific node (second node) in the vehicle through multicast transmission or point-to-point transmission, instructing the second node to open the function of routing and forwarding the first message corresponding to the second in-vehicle wired network, thereby realizing the opening of the communication message of the local in-vehicle wired network (second in-vehicle wired network) hanging under the second node, thereby ensuring that while the ECU connected to the first in-vehicle wired network is being OTA upgraded, the ECU connected to the second in-vehicle wired network can provide normal business functions.

[0269] Optionally, the function of the second node sending and receiving the first message corresponding to the second in-vehicle wired network is turned on by default. It can be understood that in this case, the first node can turn on the function of the second node sending and receiving the first message corresponding to the second in-vehicle wired network without the help of an instruction to send a third message.

[0270] Optionally, the function of the ECU connected to the second in-vehicle wired network to send and receive the first message is turned on by default. It can be understood that in this case, the first node can turn on the function of the ECU connected to the second in-vehicle wired network to send and receive the first message without the help of an instruction to send a third message.

[0271] Optionally, the third information and the above-mentioned first information can be carried in different messages, or the third information and the above-mentioned first information can be carried in different fields of the same message, which is not limited in the embodiment of the present application.

[0272] It should be understood that the application scenarios and implementation methods shown in the above-mentioned Case 1 and Case 2 only use VIU or CAN line to group ECUs as an illustrative example of a possible method of turning off the local ECU's function of receiving and sending the first message and turning on the local ECU's function of receiving and sending the first message, and should not be used to limit the embodiments of the present application. The possible embodiments of turning off the local ECU's function of receiving and sending the first message and turning on the local ECU's function of receiving and sending the first message obtained based on the supplement or reasonable deformation of the above-mentioned ECU grouping method all fall within the scope of protection of the embodiments of the present application.

[0273] In a possible embodiment, the first information includes at least a first field and a second field.

[0274] Among them, the first field corresponds to the second node, and is used to indicate whether the function of sending and receiving application messages of the ECU hanging under the second node is turned off, and the second field corresponds to the third node, and is used to indicate whether the function of sending and receiving application messages of the ECU hanging under the third node is turned off.

[0275] Through the embodiments of the present application, it is possible to ensure the normal business functions of other ECUs that are not undergoing OTA upgrades during the OTA upgrade of some ECUs.

[0276] Optionally, the first information includes a third field corresponding to the node.

[0277] Among them, when the third field is a valid field, for example, the third field corresponds to the address of one or more nodes, the node corresponding to the address can execute the function of shutting down the sending and receiving of application messages, and other nodes whose addresses do not correspond to the third field are not affected and can send and receive application messages to provide normal business functions.

[0278] Exemplarily, the first information can specifically be the UDS diagnostic service 28 service. Based on the frame structure design of the 28 service, the first field and the second field (optionally, the third field) in the 28 service frame structure can be used to realize the function of shutting down the first ECU connected to the second node of the vehicle to send and receive the first message.

[0279] In a possible embodiment, the first node further sends fourth information.

[0280] The fourth information is used to instruct to shut down the function of all or part of the ECUs in the vehicle to send and receive the first message.

[0281] Through the embodiments of the present application, the entire vehicle can be silenced to perform an OTA upgrade on the entire vehicle, or some ECUs can be silenced to perform an OTA upgrade on the silent ECUs, thereby ensuring the normal business functions of other ECUs that are not being upgraded through OTA while performing an OTA upgrade on some ECUs.

[0282] The OTA flash writing process in the upgrade method shown in FIG7 will be described below with reference to FIG8 and FIG9.

[0283] Please refer to Figure 8, which is a schematic diagram of an OTA flashing process provided in an embodiment of the present application.

[0284] As shown in Figure 8, this is the process of flashing ECUs under various VIUs in parallel in a multiple-VIU scenario. In this multiple-VIU scenario, ECUs are grouped by the ring network VIU to achieve local VIU communication message shutdown, thereby ensuring the normal business functions of the ECUs in the non-flashing VIUs.

[0285] Specifically, with reference to the vehicle topology shown in FIG. 4B , assuming that only the communication message receiving and sending functions of a specific VIU in the vehicle topology are turned off, the specific VIU is the VIU with ① the vehicle body domain and ② the chassis domain attached thereto. Completing the OTA flashing of the VIU and its attached ECUs includes, but is not limited to, the following specific steps:

[0286] Step 1: During OTA upgrade, the OTA UDS installer (i.e., the first node in FIG7 ) uses the group multicast function (different functional addressing addresses are assigned to different VIUs) to send 28 services and sends UDS 28 services to ECUs in different groups.

[0287] Step 2: The OTA UDS installer (i.e., the first node in Figure 7 above) broadcasts diagnostic messages in groups to different VIUs, for example: vehicle broadcast-0xE400 (indicating that diagnostic messages are sent to all VIUs in the vehicle), VIU1-0xE440 (indicating that diagnostic messages are sent only to VIU1), VIU2-0xE441 (indicating that diagnostic messages are sent only to VIU2), VIUn-0xE44n (indicating that diagnostic messages are sent only to VIUn), etc. The embodiments of the present application are not limited to this.

[0288] Step 3: After receiving the group function addressing 28 service, the VIU turns off / on the VIU's own application message receiving and sending function according to the 28 service instruction, and forwards the received diagnostic message to the downstream ECU.

[0289] Step 4: After receiving service 28, the downstream ECU turns off / on the application message sending and receiving function according to the instructions of service 28, and performs OTA flashing according to the received diagnostic message.

[0290] Through the embodiments of the present application, during the parallel OTA upgrade process, group function addressing can be used to shut down the function of sending and receiving application messages of a certain VIU and its downstream ECU, so that the normal business functions of other VIUs and downstream ECUs are not affected by the VIU and its downstream ECU during the upgrade process. This can improve the efficiency of parallel OTA upgrades while reducing the impact of OTA upgrades on vehicle functions.

[0291] Please refer to Figure 9, which is a schematic diagram of an OTA flashing process provided in an embodiment of the present application.

[0292] As shown in Figure 9, this is the process of flashing ECUs connected to each CAN line in parallel in a multi-CAN line scenario. In this multi-CAN line scenario, ECUs are grouped by CAN lines to achieve local CAN line communication message shutdown, thereby ensuring the normal business functions of ECUs in the non-flashing network segment.

[0293] Specifically, with reference to the vehicle topology shown in FIG. 4B , it is assumed that only the communication message receiving and sending function corresponding to a specified CAN line under a specified VIU in the vehicle topology is shut down. The specified VIU is a VIU connected to the ① body domain and the ② chassis domain, and the specified CAN line under the specified VIU is a CAN line connected to the ECU in the ① body domain. Completing the OTA flashing of the specified CAN line under the VIU and the ECU connected thereto includes but is not limited to the following specific steps:

[0294] Step 1: During OTA upgrade, the OTA UDS installer (i.e., the first node in Figure 7 above) sends a notification to the designated VIU through physical addressing to partially shut down the sending and receiving of application messages, such as the diagnostic service 31 service. After receiving the 31 service, the designated VIU partially shuts down the function of sending and receiving application messages as required, and shuts down the forwarding of the corresponding application messages in the body domain or chassis domain.

[0295] Step 2: The OTA UDS installer (ie, the first node in FIG7 ) sends the UDS 28 service to ECUs of different groups using the group multicast function (different functional addressing addresses are allocated to different VIUs).

[0296] Step 3: The OTA UDS installer (i.e., the first node in Figure 7 above) broadcasts diagnostic messages in groups to different VIUs, for example: vehicle broadcast-0xE400 (indicating that diagnostic messages are sent to all VIUs in the vehicle), VIU1-0xE440 / 0xE441 (indicating that diagnostic messages are sent only to VIU1), VIU2-0xE442 / 0xE443 (indicating that diagnostic messages are sent only to VIU2), VIUn-0xE44n (indicating that diagnostic messages are sent only to VIUn), etc. The embodiments of the present application are not limited to this.

[0297] Step 4: After VIU receives the group function addressing 28 service, it turns off / on the application message receiving and sending function of the corresponding CAN line of VIU according to the 28 service instruction, and forwards the received diagnostic message to the ECU connected to the corresponding CAN line. For example, 0Xe400 means forwarding the diagnostic message to all downstream ECUs; 0xE440 means VIU1 forwards the diagnostic message to the CAN line where the HUD is located; 0xE442 means VIU2 forwards the diagnostic message to the downstream body domain ECU; 0xE443 means VIU2 forwards the diagnostic message to the downstream chassis domain ECU; 0xE444 means VIUn forwards the diagnostic message to the downstream power domain ECU; 0xE445 means VIUn forwards the diagnostic message to the downstream body domain ECU, etc. The embodiment of the present application does not limit this.

[0298] Step 5: After receiving service 28, the downstream ECU turns off / on the application message sending and receiving function according to the instructions of service 28, and performs OTA flashing according to the received diagnostic message.

[0299] Through the embodiments of the present application, during the parallel OTA upgrade process, the group function addressing can be used to shut down only the function of the ECU connected to a certain CAN line of a certain VIU to send and receive application messages, and the diagnostic message is used to notify the VIU to shut down the application message communication forwarding function of a certain CAN line and the application message sending and receiving function of the VIU on the CAN line, so that the ECU connected to the CAN line does not affect the functions of other VIUs and the connected ECUs during the OTA upgrade process, which can improve the efficiency of the parallel OTA upgrade while reducing the impact of the OTA upgrade on the vehicle function.

[0300] The above describes in detail the methods of the embodiments of the present application. The following provides an apparatus for implementing any method in the embodiments of the present application. For example, an apparatus is provided that includes units (or means) for implementing each step performed by the device in any of the above methods.

[0301] Please refer to FIG10 , which is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0302] As shown in Figure 10, the communication device 100 may include a communication unit 1001 and a processing unit 1002. The communication unit 1001 and the processing unit 1002 may be software, hardware, or a combination of software and hardware.

[0303] The communication unit 1001 can implement a sending function and / or a receiving function, and can also be described as a transceiver unit. The communication unit 1001 can also be a unit that integrates an acquisition unit and a sending unit, wherein the acquisition unit is used to implement the receiving function and the sending unit is used to implement the sending function. Optionally, the communication unit 1001 can be used to receive information sent by other devices, and can also be used to send information to other devices.

[0304] In one possible design, the communication device 100 may correspond to the first node in the method embodiment shown in FIG. 7 , for example, the communication device 100 may be the first node or a chip in the first node. The communication device 100 may include a unit for executing the operations performed by the first node in the method embodiment shown in FIG. 7 , and each unit in the communication device 100 is respectively for implementing the operations performed by the first node in the method embodiment shown in FIG. 7 . The description of each unit is as follows:

[0305] The communication unit 1001 is configured to send a first message, where the first message is used to instruct the first ECU to disable a function of receiving and sending a first message.

[0306] The communication unit 1001 is further configured to send second information, where the second information is used to perform an over-the-air (OTA) upgrade on the first ECU;

[0307] When the first ECU is OTA upgraded, the function of the first ECU receiving and sending the first message is turned off, and the function of the second ECU receiving and sending the first message is turned on, and the second ECU is different from the first ECU.

[0308] In one possible implementation, the device further includes:

[0309] The processing unit 1002 is configured to generate the first information and / or the second information.

[0310] In a possible implementation, a processing priority of the upgrade message corresponding to the OTA upgrade is lower than a processing priority of the first message.

[0311] In a possible implementation manner, the third node is different from the second node, and the second ECU is an ECU connected to the third node.

[0312] In a possible implementation manner, the first information is further used to instruct to shut down a function of the second node to send and receive the first message.

[0313] In one possible implementation, the first ECU is an ECU connected to a first in-vehicle wired network, the second ECU is an ECU connected to a second in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

[0314] In a possible implementation manner, the first in-vehicle wired network and the second in-vehicle wired network have the same wired network standard, for example, both are Controller Area Network (CAN) or both are Ethernet.

[0315] In a possible implementation, the communication unit 1001 is further configured to send third information, where the third information is configured to instruct to shut down a function of the second node to send and receive the first message corresponding to the first in-vehicle wired network.

[0316] In a possible implementation, the third information is further used to instruct to enable a function of the second node to send and receive the first message corresponding to the second in-vehicle wired network.

[0317] In one possible implementation, the first information includes at least a first field and a second field, the first field being used to indicate whether the function of the ECU connected to the second node to send and receive the first message is turned off, and the second field being used to indicate whether the function of the ECU connected to the third node to send and receive the first message is turned off.

[0318] In a possible implementation, the communication unit 1001 is further configured to send fourth information, where the fourth information is used to instruct to shut down the function of all or some of the ECUs in the vehicle to send and receive the first message.

[0319] Regarding the technical effects brought about by this design and any possible implementation, please refer to the introduction of the technical effects corresponding to Figure 7 and the corresponding implementation.

[0320] In another possible design of the communication device 100 shown in FIG10 , the communication device 100 may correspond to the second node in the method embodiment shown in FIG7 above. For example, the communication device 100 may be the second node or a chip in the second node. The communication device 100 may include a unit for performing the operations performed by the second node in the method embodiment shown in FIG7 above, and each unit in the communication device 100 is respectively for implementing the operations performed by the second node in the method embodiment shown in FIG7 above. The description of each unit is as follows:

[0321] The communication unit 1001 is configured to receive first information from a first node, where the first information is used to instruct the first ECU to disable a function of receiving and sending a first message.

[0322] The communication unit 1001 is further configured to receive second information from the first node, where the second information is used to perform an over-the-air (OTA) upgrade on the first ECU;

[0323] When the first ECU is OTA upgraded, the function of the first ECU receiving and sending the first message is turned off, and the function of the second ECU receiving and sending the first message is turned on, and the second ECU is different from the first ECU.

[0324] In one possible implementation, the device further includes:

[0325] The processing unit 1002 is configured to determine whether to forward the first information and / or the second information to the first ECU.

[0326] In a possible implementation, a processing priority of the upgrade message corresponding to the OTA upgrade is lower than a processing priority of the first message.

[0327] In a possible implementation manner, the third node is different from the communication device, and the second ECU is an ECU connected to the third node.

[0328] In a possible implementation manner, the first information is further used to instruct to shut down the function of the communication device to send and receive the first message.

[0329] In one possible implementation, the first ECU is an ECU connected to a first in-vehicle wired network, the second ECU is an ECU connected to a second in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the communication device.

[0330] In a possible implementation manner, the first in-vehicle wired network and the second in-vehicle wired network have the same wired network standard, for example, both are Controller Area Network (CAN) or both are Ethernet.

[0331] In a possible implementation, the communication unit 1001 is further configured to receive third information from the first node, where the third information is configured to instruct the communication device to shut down a function of sending and receiving the first message corresponding to the first in-vehicle wired network.

[0332] In a possible implementation, the third information is further used to instruct to enable a function of the communication device to send and receive the first message corresponding to the second in-vehicle wired network.

[0333] In one possible implementation, the first information includes at least a first field and a second field, the first field being used to indicate whether the function of the ECU connected to the communication device to send and receive the first message is turned off, and the second field being used to indicate whether the function of the ECU connected to the third node to send and receive the first message is turned off.

[0334] In a possible implementation, the communication unit 1001 is further configured to receive fourth information from the first node, where the fourth information is used to instruct to shut down the function of all or some of the ECUs in the vehicle to send and receive the first message.

[0335] Regarding the technical effects brought about by this design and any possible implementation, please refer to the introduction of the technical effects corresponding to Figure 7 and the corresponding implementation.

[0336] Optionally, in any possible design of the communication device 100 shown in FIG10 :

[0337] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication unit may be a transceiver or an input / output interface; and the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0338] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0339] According to an embodiment of the present application, each unit in the device shown in Figure 10 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of the present application, other units can also be included based on electronic equipment. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by collaboration of multiple units.

[0340] It should be noted that the implementation of each unit may also refer to the corresponding description of the method embodiment shown in FIG. 7 .

[0341] In the communication device 100 described in FIG. 10 , it is possible to ensure normal service functions of other ECUs that are not undergoing OTA upgrades while performing OTA upgrades on some ECUs.

[0342] Please refer to FIG11 , which is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0343] It should be understood that the communication device 110 shown in Figure 11 is only an example. The communication device of the embodiment of the present application may also include other components, or include components with similar functions to the various components in Figure 11, or not necessarily include all the components in Figure 11.

[0344] The communication device 110 includes a communication interface 1101 and at least one processor 1102 .

[0345] The communication device 110 may correspond to any node or device among the first node and the second node. The communication interface 1101 is used to send and receive signals, and the at least one processor 1102 executes program instructions so that the communication device 110 implements the corresponding process of the method executed by the corresponding device in the above method embodiment.

[0346] In one possible design, the communication device 110 may correspond to the first node in the method embodiment shown in FIG. 7 . For example, the communication device 110 may be the first node or a chip in the first node. The communication device 110 may include components for executing the operations performed by the first node in the method embodiment described above, and each component in the communication device 110 is configured to implement the operations performed by the first node in the method embodiment described above. Specifically, the operations may be as follows:

[0347] The first node sends first information, where the first information is used to instruct the first ECU to shut down a function of sending and receiving a first message;

[0348] The first node sends second information, where the second information is used to perform an over-the-air (OTA) upgrade on the first ECU;

[0349] When the first ECU is OTA upgraded, the function of the first ECU receiving and sending the first message is turned off, and the function of the second ECU receiving and sending the first message is turned on, and the second ECU is different from the first ECU.

[0350] In a possible implementation, a processing priority of the upgrade message corresponding to the OTA upgrade is lower than a processing priority of the first message.

[0351] In a possible implementation manner, the vehicle further includes a third node, which is different from the second node, and the second ECU is an ECU connected to the third node.

[0352] In a possible implementation manner, the first information is further used to instruct to shut down a function of the second node to send and receive the first message.

[0353] In one possible implementation, the first ECU is an ECU connected to a first in-vehicle wired network, the second ECU is an ECU connected to a second in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

[0354] In a possible implementation manner, the first in-vehicle wired network and the second in-vehicle wired network have the same wired network standard, for example, both are Controller Area Network (CAN) or both are Ethernet.

[0355] In one possible implementation, the method further includes:

[0356] The first node sends third information, where the third information is used to instruct the second node to shut down a function of sending and receiving a first message corresponding to the first in-vehicle wired network.

[0357] In a possible implementation, the third information is further used to instruct to enable a function of the second node to send and receive the first message corresponding to the second in-vehicle wired network.

[0358] In one possible implementation, the first information includes at least a first field and a second field, the first field being used to indicate whether the function of the ECU connected to the second node to send and receive the first message is turned off, and the second field being used to indicate whether the function of the ECU connected to the third node to send and receive the first message is turned off.

[0359] In one possible implementation, the method further includes:

[0360] The first node sends fourth information, where the fourth information is used to instruct to shut down the function of all or some of the ECUs in the vehicle to send and receive the first message.

[0361] Regarding the technical effects brought about by this design and any possible implementation, please refer to the introduction of the technical effects corresponding to Figure 7 and the corresponding implementation.

[0362] In another possible design, the communication device 110 may correspond to the second node in the method embodiment shown in FIG. 7 . For example, the communication device 110 may be the second node or a chip in the second node. The communication device 110 may include components for executing the operations performed by the second node in the method embodiment described above, and each component in the communication device 110 is configured to implement the operations performed by the second node in the method embodiment described above. Specifically, the operations may be as follows:

[0363] The second node receives first information from the first node, where the first information is used to instruct to shut down a function of the first ECU to send and receive the first message;

[0364] The second node receives second information from the first node, where the second information is used to perform an over-the-air (OTA) upgrade on the first ECU;

[0365] When the first ECU is OTA-updated, the function of the first ECU receiving and sending the first message is turned off, and the function of the second ECU receiving and sending the first message is turned on. The second ECU is different from the first ECU.

[0366] In a possible implementation, a processing priority of the upgrade message corresponding to the OTA upgrade is lower than a processing priority of the first message.

[0367] In a possible implementation manner, the vehicle further includes a third node, which is different from the second node, and the second ECU is an ECU connected to the third node.

[0368] In a possible implementation manner, the first information is further used to instruct to shut down a function of the second node to send and receive the first message.

[0369] In one possible implementation, the first ECU is an ECU connected to a first in-vehicle wired network, the second ECU is an ECU connected to a second in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

[0370] In a possible implementation manner, the first in-vehicle wired network and the second in-vehicle wired network have the same wired network standard, for example, both are Controller Area Network (CAN) or both are Ethernet.

[0371] In one possible implementation, the method further includes:

[0372] The second node receives third information from the first node, where the third information is used to instruct the second node to shut down a function of receiving and sending a first message corresponding to the first in-vehicle wired network.

[0373] In a possible implementation, the third information is further used to instruct to enable a function of the second node to send and receive the first message corresponding to the second in-vehicle wired network.

[0374] In one possible implementation, the first information includes at least a first field and a second field, the first field being used to indicate whether the function of the ECU connected to the second node to send and receive the first message is turned off, and the second field being used to indicate whether the function of the ECU connected to the third node to send and receive the first message is turned off.

[0375] In one possible implementation, the method further includes:

[0376] The second node receives fourth information from the first node, where the fourth information is used to instruct to shut down a function of all or some of the ECUs in the vehicle to send and receive the first message.

[0377] Regarding the technical effects brought about by this design and any possible implementation, please refer to the introduction of the technical effects corresponding to Figure 7 and the corresponding implementation.

[0378] In the communication device 110 described in FIG. 11 , it is possible to ensure normal business functions of other ECUs that are not undergoing OTA upgrades while performing OTA upgrades on some ECUs.

[0379] For the case where the communication device may be a chip or a chip system, reference may be made to the schematic structural diagram of the chip shown in FIG12 .

[0380] As shown in Figure 12 , chip 120 includes a processor 1201 and an interface 1202. There may be one or more processors 1201, and there may be multiple interfaces 1202. It should be noted that the functions of processor 1201 and interface 1202 may be implemented through hardware design, software design, or a combination of hardware and software, without limitation.

[0381] Optionally, the chip 120 may further include a memory 1203 , which is used to store necessary program instructions and data.

[0382] In this application, processor 1201 may be configured to call from memory 1203 an implementation program for the communication method provided in one or more embodiments of this application on one or more devices or nodes in the first node and the second node, and execute the instructions contained in the program. Interface 1202 may be configured to output the execution results of processor 1201. In this application, interface 1202 may be specifically configured to output various messages or information from processor 1201.

[0383] For the upgrade method provided by one or more embodiments of the present application, please refer to the various embodiments shown in Figure 7 above, which will not be repeated here.

[0384] The processor in the embodiments of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0385] The memory in the embodiments of the present application is used to provide storage space, in which data such as an operating system and computer programs can be stored. The memory includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0386] According to the method provided in the embodiment of the present application, the embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on one or more processors, the method shown in Figure 7 can be implemented.

[0387] According to the method provided in the embodiment of the present application, the embodiment of the present application also provides a computer program product, which includes a computer program. When the computer program runs on a processor, it can implement the method shown in Figure 7 above.

[0388] An embodiment of the present application further provides a system, which includes at least one communication device 100 or communication device 110 or chip 120 as described above, and is used to execute the steps executed by the corresponding device in any of the embodiments of FIG. 7 .

[0389] An embodiment of the present application also provides a system, which includes a first node and a second node. The first node is used to execute the steps executed by the first node in any embodiment of Figure 7 above, and the second node is used to execute the steps executed by the second node in any embodiment of Figure 7 above.

[0390] An embodiment of the present application further provides a processing device, including a processor and an interface; the processor is used to execute the method in any of the above method embodiments.

[0391] It should be understood that the above-mentioned processing device can be a chip. For example, the processing device can be a field programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chip. The various methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0392] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0393] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disc (SSD)).

[0394] The units in the above-mentioned various apparatus embodiments completely correspond to the electronic devices in the method embodiments, and the corresponding modules or units perform the corresponding steps. For example, the communication unit (transceiver) performs the receiving or sending steps in the method embodiments, and other steps except sending and receiving can be performed by the processing unit (processor). The functions of the specific units can be referred to the corresponding method embodiments. Among them, there can be one or more processors.

[0395] It is understood that in the embodiments of the present application, the electronic device can perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples, and the embodiments of the present application can also perform other operations or variations of various operations. In addition, the various steps can be performed in a different order than those presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application need to be performed.

[0396] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0397] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0398] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0399] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0400] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0401] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0402] The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the scope of protection of the present application.

Claims

1. An upgrading method, characterized in that: Applied to a vehicle, the vehicle comprises a first node, a second node, a first electronic control unit ECU, and a second electronic control unit ECU, wherein the first ECU is connected to the second node; the method comprises: The first node sends first information, where the first information is used to instruct to shut down a function of the first ECU to send and receive a first message; The first node sends second information, where the second information is used to perform an over-the-air (OTA) upgrade of the first ECU; When the first ECU is OTA upgraded, the function of the first ECU receiving and sending the first message is turned off, and the function of the second ECU receiving and sending the first message is turned on, and the second ECU is different from the first ECU.

2. The method according to claim 1, characterized in that The processing priority of the upgrade message corresponding to the OTA upgrade is lower than the processing priority of the first message.

3. The method according to claim 1 or 2, characterized in that: The vehicle further includes a third node that is different from the second node, and the second ECU is an ECU connected to the third node.

4. The method according to any one of claims 1 to 3, characterized in that The first information is also used to instruct to shut down the function of the second node receiving and sending the first message.

5. The method according to claim 1 or 2, characterized in that: The first ECU is an ECU connected to a first in-vehicle wired network, the second ECU is an ECU connected to a second in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

6. The method according to claim 5, characterized in that The method further comprises: The first node sends third information, where the third information is used to instruct to shut down the function of the second node to send and receive the first message corresponding to the first in-vehicle wired network.

7. The method according to claim 5 or 6, characterized in that: The third information is also used to instruct to enable the function of the second node to send and receive the first message corresponding to the second in-vehicle wired network.

8. The method according to any one of claims 1 to 7, characterized in that The first information includes at least a first field and a second field, the first field is used to indicate whether the function of the ECU connected to the second node to send and receive the first message is turned off, and the second field is used to indicate whether the function of the ECU connected to the third node to send and receive the first message is turned off.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: The first node sends fourth information, where the fourth information is used to instruct to shut down the function of all or part of the ECUs in the vehicle to send and receive the first message.

10. An upgrading method, characterized in that: Applied to a vehicle, the vehicle comprises a first node, a second node, a first electronic control unit ECU, and a second electronic control unit ECU, wherein the first ECU is connected to the second node; the method comprises: The second node receives first information from the first node, where the first information is used to instruct to shut down a function of the first ECU to send and receive a first message; The second node receives second information from the first node, where the second information is used to perform an over-the-air (OTA) upgrade of the first ECU; When the first ECU is OTA upgraded, the function of the first ECU receiving and sending the first message is turned off, and the function of the second ECU receiving and sending the first message is turned on, and the second ECU is different from the first ECU.

11. The method according to claim 10, characterized in that The processing priority of the upgrade message corresponding to the OTA upgrade is lower than the processing priority of the first message.

12. The method according to claim 10 or 11, characterized in that: The vehicle further includes a third node that is different from the second node, and the second ECU is an ECU connected to the third node.

13. The method according to any one of claims 10 to 12, characterized in that The first information is also used to instruct to shut down the function of the second node receiving and sending the first message.

14. The method according to claim 10 or 11, characterized in that: The first ECU is an ECU connected to a first in-vehicle wired network, the second ECU is an ECU connected to a second in-vehicle wired network, and the first in-vehicle wired network and the second in-vehicle wired network are two different in-vehicle wired networks connected to the second node.

15. The method according to claim 14, characterized in that The method further comprises: The second node receives third information from the first node, where the third information is used to instruct to shut down a function of the second node to send and receive a first message corresponding to the first in-vehicle wired network.

16. The method according to claim 14 or 15, characterized in that The third information is also used to instruct to enable the function of the second node to send and receive the first message corresponding to the second in-vehicle wired network.

17. The method according to any one of claims 10 to 16, characterized in that The first information includes at least a first field and a second field, the first field is used to indicate whether the function of the ECU connected to the second node to send and receive the first message is turned off, and the second field is used to indicate whether the function of the ECU connected to the third node to send and receive the first message is turned off.

18. The method according to any one of claims 10 to 17, characterized in that The method further comprises: The second node receives fourth information from the first node, where the fourth information is used to instruct to shut down the function of all or part of the ECUs in the vehicle to send and receive the first message.

19. A communication device, characterized in that: The method comprises a module or a unit for executing the method as claimed in any one of claims 1 to 9 or claims 10 to 18.

20. A communication device, characterized in that: include: processor; When the processor calls the computer program or instruction in the memory, the method according to any one of claims 1 to 9 is executed, or the method according to any one of claims 10 to 18 is executed.

21. A communication device, characterized in that: comprising a logic circuit and an interface, wherein the logic circuit and the interface are coupled; The interface is used to input data to be processed, the logic circuit processes the data to be processed according to the method as described in any one of claims 1 to 9 or claims 10 to 18 to obtain processed data, and the interface is used to output the processed data.

22. A computer-readable storage medium, characterized in that: include: The computer-readable storage medium is used to store instructions or computer programs; when the instructions or the computer program are executed, the method according to any one of claims 1 to 9 is implemented, or the method according to any one of claims 10 to 18 is implemented.

23. A computer program product, characterized in that include: instructions or computer programs; When the instructions or the computer program are executed, the method according to any one of claims 1 to 9 is executed, or the method according to any one of claims 10 to 18 is executed.

24. A vehicle end, characterized in that: Comprising the communication device according to claim 19, or the communication device according to claim 20, or the communication device according to claim 21.

25. A system, characterized in that: include: a first node and a second node; The first node is used to execute the method according to any one of claims 1 to 9, and the second node is used to execute the method according to any one of claims 10 to 18.

Images