OTA upgrade methods, vehicles, and storage media
The OTA upgrade method using a three-layer architecture and Ethernet multicast technology enables parallel and serial upgrades of the entire vehicle ECU, solving the problems of long upgrade time and inconsistent mode management, improving upgrade efficiency and reliability, and ensuring user experience.
Patent Information
- Application Number
- CN202611279511.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-21
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, the increase in the number of vehicle electronic control units (ECUs) leads to long OTA upgrade times, low upgrade efficiency, and inconsistent mode management during the upgrade process.
The OTA upgrade method adopts a three-layer architecture, including a vehicle upgrade master controller, a domain upgrade controller, and a domain flashing executor. Combined with Ethernet multicast technology, it realizes cross-domain parallel and intra-domain hierarchical serial flashing scheduling, and ensures upgrade synchronization and reliability through a unified OTA mode management mechanism across the entire domain.
It effectively shortens the upgrade time, improves upgrade efficiency, ensures the mode synchronization and reliability of the vehicle ECU during the upgrade process, avoids the problem of inconsistent status caused by mode loss, and improves the user experience through differentiated upgrade coordination scheduling and fault code clearing strategies.
Smart Images

Figure CN123114510A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and more specifically, to an OTA upgrade method, a vehicle, and a storage medium. Background Technology
[0002] As automotive electronic and electrical architecture evolves from a distributed to a domain-centralized model, the number of Electronic Control Units (ECUs) in vehicles has increased dramatically. Modern intelligent vehicles typically have more than 70 ECUs, distributed across different functional domains, including body control, intelligent driving, intelligent cockpit, and powertrain. Over-the-Air (OTA) upgrades have become the core means for continuous iteration and updates of vehicle ECUs. A key technological challenge facing the industry is how to minimize the upgrade time while ensuring upgrade safety and reliability.
[0003] Current upgrade solutions often employ a single upgrade master node, sequentially flashing and upgrading the software of all ECUs in the vehicle according to a predetermined order.
[0004] Because the vehicle contains a large number of ECUs, the overall time required is long and the upgrade efficiency is low. Summary of the Invention
[0005] The purpose of this application is to address the shortcomings of the prior art by providing an OTA upgrade method, vehicle, and storage medium to improve the efficiency of vehicle OTA upgrades.
[0006] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows: In a first aspect, embodiments of this application provide an OTA (Over-The-Air) upgrade method applied to a target vehicle. The target vehicle includes multiple first functional domains and second functional domains, each of which integrates a domain upgrade controller. A target functional domain within the multiple first functional domains also integrates a central upgrade controller. Each first functional domain is connected to one or more communication network segments. Each communication network segment carries one or more electronic control units. The method includes: The domain upgrade controller of the second functional domain interacts with the cloud via Ethernet to obtain upgrade packages for each electronic control unit and distributes them to the corresponding functional domain's domain upgrade controller. When the upgrade master controller determines that the target vehicle meets the upgrade conditions, it triggers each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain to enter OTA mode. The domain upgrade controller of each first functional domain assigns corresponding Ethernet multicast communication addresses to each communication network segment connected to the first functional domain. Each first functional domain's domain upgrade controller controls the parallel upgrade process between communication network segments under the first functional domain based on the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain, and controls the electronic control units under a communication network segment connected to the first functional domain to perform serial upgrade process based on the preset upgrade process and the upgrade package corresponding to each electronic control unit.
[0007] Optionally, when the upgrade master controller determines that the target vehicle meets the upgrade conditions, it triggers each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain to enter OTA mode, including: When the upgrade controller determines that the target vehicle meets the upgrade conditions, it calls the vehicle mode manager to broadcast the target command to the entire network segment. Each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain receive the target instruction, switch the status identifier to the first identifier to enter OTA mode, and start the timeout timer; During the timeout period or after entering OTA mode, determine whether to exit OTA mode based on the received signal.
[0008] Optionally, determining whether to exit the OTA mode based on the received signal during the timeout timer or after entering the OTA mode includes: If no upgrade signal is received during the timeout period, the status identifier is switched to the second identifier to exit the OTA mode; Alternatively, after entering the OTA mode, if a diagnostic keep-alive message is received within a preset time period, the timeout timer is reset, and the diagnostic keep-alive message is received again until no diagnostic keep-alive message is received within the timeout period, and the timeout timer expires. Then, the status identifier is switched to the second identifier to exit the OTA mode.
[0009] Optionally, each first functional domain also integrates an intra-domain write actuator, and the intra-domain write actuator of the first functional domain is connected to one or more communication network segments through one or more vehicle interface units respectively. The domain upgrade controller of each first functional domain controls the parallel upgrade process between communication network segments under the first functional domain according to the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain, including: The domain upgrade controller of the first functional domain sends upgrade instructions in parallel to the vehicle interface unit corresponding to each communication network segment according to the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain. The vehicle interface unit converts the upgrade instructions into upgrade messages corresponding to the communication network segment and sends them to the communication network segment to realize parallel upgrade processing between communication network segments.
[0010] Optionally, the step of controlling each electronic control unit under a communication network segment connected to the first functional domain to perform serial upgrade processing according to a preset upgrade process and the upgrade package corresponding to each electronic control unit includes: The domain upgrade controller of the first functional domain, based on the preset upgrade process and upgrade task type, uses the upgrade package corresponding to each electronic control unit to sequentially control each electronic control unit under a communication network segment to perform serial upgrade processing.
[0011] Optionally, the domain upgrade controller of the first functional domain, according to a preset upgrade process and upgrade task type, uses the upgrade package corresponding to each electronic control unit to sequentially control each electronic control unit under a communication network segment to perform serial upgrade processing, including: If the upgrade task type is high-voltage upgrade, then the high-voltage management service is invoked to power on the high voltage and maintain it; Based on the high and low voltage types and priorities of each electronic control unit under the communication network segment, determine each high voltage electronic control unit and its upgrade priority from among the electronic control units under the communication network segment; Based on the upgrade priority of each high-voltage electronic control unit, and following the preset upgrade process, each high-voltage electronic control unit is upgraded sequentially using the corresponding upgrade package. After the upgrade of each high-voltage electronic control unit is completed, the high-voltage management service is invoked to power off the high voltage. Determine each low-voltage electronic control unit and its upgrade priority from the remaining electronic control units under the communication network segment; Based on the upgrade priority of each low-voltage electronic control unit, and following the preset upgrade process, the upgrade packages corresponding to each low-voltage electronic control unit are used to upgrade each low-voltage electronic control unit in sequence.
[0012] Optionally, the step of upgrading each high-voltage electronic control unit according to its upgrade priority and following the preset upgrade process, using the corresponding upgrade package for each high-voltage electronic control unit, includes: Based on the upgrade priority of each high-voltage electronic control unit, determine the target high-voltage electronic control unit to be upgraded; According to the preset upgrade process, the target high-voltage electronic control unit is upgraded using the upgrade package corresponding to the target high-voltage electronic control unit through the domain flashing actuator. Determine whether the target high-voltage electronic control unit has been successfully upgraded; If the upgrade is successful, determine whether the upgraded software version of the target high-voltage electronic control unit is correct; If the version is correct, the target high-voltage electronic control unit is switched to the OTA exit waiting mode; If the upgrade fails and the number of re-flashes does not exceed the preset configuration number, then a re-flash is performed. Once the re-flash is complete and the version is correct, the target high-voltage electronic control unit is switched to the OTA exit waiting mode. If the version is incorrect, the target high-voltage electronic control unit will be rolled back using the domain flashing executor to roll back the software version of the target high-voltage electronic control unit to the previous version. After the rollback is completed, the target high-voltage electronic control unit will be switched to the OTA exit waiting mode.
[0013] Optionally, the method further includes: When all electronic control units in each communication network segment under each first functional domain have completed the upgrade and are in the waiting OTA exit mode, the domain upgrade controller of each first functional domain sequentially sends asset information acquisition instructions to each electronic control unit in each communication network segment under the first functional domain to obtain the asset information of each electronic control unit. The asset information includes one or more of the following: component part number, software version number, supplier code, electronic control unit identifier, serial number code, hardware version number, electronic control unit batch number, bootloader software version number, and backup area software version number. A dual-loop code clearing strategy is implemented using extended diagnostic mode and default diagnostic mode. Fault code clearing commands are sent sequentially to each electronic control unit in each communication network segment under the first functional domain to clear the temporary fault codes generated by each electronic control unit during the upgrade process.
[0014] Optionally, the step of controlling each electronic control unit under a communication network segment connected to the first functional domain to perform serial upgrade processing according to a preset upgrade process and the upgrade package corresponding to each electronic control unit includes: Each first functional domain's domain upgrade controller, based on a preset upgrade process and the upgrade package corresponding to each electronic control unit, uses the communication protocol corresponding to the first functional domain to control each electronic control unit under a communication network segment connected to the first functional domain to perform serial upgrade processing.
[0015] Optionally, the second functional domain further integrates an in-domain write executor; the method further includes: The domain upgrade controller of the second functional domain performs upgrade processing on the controller under the second functional domain through the domain-intra-domain flashing executor, based on the upgrade package obtained from the cloud.
[0016] Optionally, the method further includes: Each first functional domain's domain upgrade controller periodically reports the upgrade progress of the first functional domain to the overall upgrade controller in the target functional domain; The upgrade master controller integrates the upgrade progress of each first functional domain, obtains an intermediate integration result, and sends the intermediate integration result to the domain upgrade controller of the second functional domain. The domain upgrade controller of the second functional domain integrates the intermediate integration result with the upgrade progress of the second functional domain again to obtain the target integration result, and sends the target integration result to the cloud or the central control device of the target vehicle for visualization.
[0017] Secondly, embodiments of this application also provide a vehicle, including: multiple first functional domains and second functional domains, each first functional domain and second functional domain integrating a domain upgrade controller and an intra-domain flashing actuator; wherein, a target functional domain among the multiple first functional domains also integrates an upgrade master controller; the intra-domain flashing actuator in each first functional domain is connected to a communication network segment through one or more vehicle interface units; one or more electronic control units are mounted under each communication network segment; the domain upgrade controller of the second functional domain interacts with the cloud via Ethernet to obtain upgrade packages for each electronic control unit and distributes them to the domain upgrade controller of the corresponding functional domain; The domain upgrade controller in each first functional domain is used to execute the method steps executed by the domain upgrade controller in each first functional domain in the first aspect above. The domain upgrade controller in the second functional domain is used to execute the method steps performed by the domain upgrade controller in the second functional domain in the first aspect described above; The upgrade master controller in the target functional domain is used to execute the method steps performed by the upgrade master controller in the first aspect above.
[0018] Thirdly, embodiments of this application provide a computer-readable storage medium storing a computer program that is executed by a processor to perform the OTA upgrade method provided in the first aspect.
[0019] The beneficial effects of this application are: This application provides an OTA upgrade method, a vehicle, and a storage medium, comprising: a domain upgrade controller of a second functional domain interacting with the cloud via Ethernet to obtain upgrade packages for each electronic control unit and sending them to the corresponding domain upgrade controller of the functional domain; when the upgrade master controller determines that the target vehicle meets the upgrade conditions, triggering each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain to enter OTA mode; each domain upgrade controller of a first functional domain assigning a corresponding Ethernet multicast communication address to each communication network segment connected to the first functional domain; each domain upgrade controller of a first functional domain controlling the parallel upgrade processing between each communication network segment under the first functional domain according to the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain, and controlling each electronic control unit under a communication network segment connected to the first functional domain to perform serial upgrade processing according to a preset upgrade process and the upgrade package corresponding to each electronic control unit. This method divides the entire vehicle into functional domains, integrates domain upgrade controllers in each functional domain, and integrates a central upgrade controller in the core functional domain, enabling unified OTA upgrade management and control across the entire domain. The domain upgrade controllers in each functional domain can control parallel upgrade processing between domains. By assigning different Ethernet multicast communication addresses to multiple communication segments within a functional domain, and combining this with Ethernet multicast technology, parallel upgrade processing between multiple communication segments within a domain, as well as serial upgrade processing within a single communication segment, can be achieved. Compared to the traditional full-domain serial approach, this effectively shortens upgrade time and improves upgrade efficiency.
[0020] Secondly, by broadcasting target commands across the entire domain, combined with multiple safeguards including status flag switching, timeout signal reception, diagnostic keep-alive message reception, and persistent Flash storage, unified OTA mode synchronization management is achieved across the entire domain. This ensures that all ECUs in the vehicle maintain OTA mode synchronization throughout the entire upgrade process (including DUC self-upgrade activation), avoiding global state inconsistencies caused by OTA mode loss after DUC upgrade reset. The Flash persistence mechanism allows the VMM to restore its OTA mode state after its own upgrade activation, avoiding blind spots in mode management introduced by VMM upgrades.
[0021] In addition, the upgrade's fault tolerance is ensured through re-flashing and version rollback, thus guaranteeing the reliability of the upgrade.
[0022] Moreover, VUC enables differentiated upgrade coordination and scheduling across different functional domains, as well as the aggregation of upgrade progress. It achieves unified scheduling and progress aggregation for various upgrade methods and exhibits excellent scalability.
[0023] Based on the upgrade task type, high and low voltage partition upgrade processing is performed. By upgrading high voltage first and then low voltage, it can be ensured that the upgrade processing of high voltage safety-related ECUs is completed first under the condition of high voltage power supply guarantee, avoiding the inability to upgrade low voltage ECUs after high voltage loss and the high voltage safety hazards during the low voltage ECU upgrade process.
[0024] During the OTA exit phase, a dual-cycle fault code clearing strategy is adopted to ensure that temporary fault codes generated in different diagnostic session modes during the OTA upgrade process are completely cleared, avoiding residual fault lights on the vehicle's dashboard after the upgrade and improving the user's driving experience after the upgrade. Attached Figure Description
[0025] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0026] Figure 1 A schematic diagram of a vehicle system architecture provided in this application embodiment; Figure 2 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 1 ; Figure 3 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 2 ; Figure 4 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 3 ; Figure 5 A flowchart illustrating a high- and low-voltage zone security upgrade process is provided in this application embodiment; Figure 6 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 4 ; Figure 7 This is a schematic diagram of the entire upgrade process within a functional domain in the OTA upgrade method provided in the embodiments of this application; Figure 8 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 5 ; Figure 9 A schematic diagram of a processing flow for the OTA exit mode stage provided in an embodiment of this application; Figure 10 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 6 ; Figure 11 This is a schematic diagram of the architecture for multi-domain differentiated upgrade collaborative scheduling and visualization summary provided in the embodiments of this application. Detailed Implementation
[0027] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.
[0028] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.
[0029] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.
[0030] This solution proposes an Over-The-Air (OTA) upgrade method, which uses a three-layer architecture combining the Vehicle Control Unit (VUC), Domain Control Unit (DUC), and Intra-Domain Installer. It combines Ethernet multicast technology to achieve cross-domain parallel and intra-domain hierarchical serial parallel flashing scheduling, as well as a unified OTA mode management mechanism across the entire domain. This solves the problems of long upgrade time, insufficient parallelism, and inconsistent mode management in existing technologies.
[0031] Figure 1 A schematic diagram of a vehicle system architecture provided in this application embodiment, such as... Figure 1As shown, the vehicle covers four upgrade domains. Among them, Vehicle Dynamic Control (VDC), Continuous Damping Control (CDC), and Mobile Data Center (MDC) are all classified as the first functional domain, while the Telematics-BOX (TBOX) is classified as the second functional domain. CDC, within the first functional domain, also serves as the target functional domain.
[0032] The VDC functional domain integrates the Domain Upgrade Controller (VDC DUC) and the Domain Flashing Executioner (VDC Installer). It is mainly responsible for managing the upgrades of more than 60 ECUs under the VDC functional domain, including but not limited to the Engine Management System (EMS), Battery Management System (BMS), DC-DC Converter (DCDC), Motor Control Unit (MCU), Generator Control Unit (GCU), Integrated Power Brake (IPB), Electric Power Steering (EPS), Climate Control Unit (CCU), Positive Temperature Coefficient Front (PTCF / Positive Temperature Coefficient Rear, PTCR), Charging Box / Charge Booster (CHB), Tire Pressure Monitoring System (TPMS), various body controllers (doors, windows, seats, lights, etc.), and 3 Vehicle Interface Units (VIU).
[0033] As the target functional domain, the CDC functional domain integrates not only the domain upgrade controller CDC DUC and the domain flashing actuator CDC Installer, but also the CDC VUC. The CDC functional domain is responsible for managing the upgrades of cockpit-related controllers under the CDC domain, including but not limited to the instrument cluster (IC), head-up display (HUD), enhanced parking assist (EPA), phase light modulator (PLM), and cabin distribution system (CDS).
[0034] The MDC functional domain integrates the Domain Upgrade Controller (MDC DUC) and the Domain Intradomain Write Executioner (MDC Installer), which are responsible for managing the upgrades of sensors and controllers under the MDC domain, including but not limited to Ultrasonic Sensor Controller (USSC), Inertial Navigation System (INS), Short Range Radar Rear Left / Rear Right (SRRRL / SRRRR), Medium Range Radar Front Center (MRRFC), and Laser Radar Sensor Front Center / Front Left / Front Right (LRSFC / LRSFL / LRSFR).
[0035] The TBOX functional domain integrates the domain upgrade controller TBOX DUC and the domain flashing executor TBOX Installer, which are responsible for its own upgrade management and vehicle-cloud communication link.
[0036] Among them, the CDC functional domain is the core functional domain, on which the vehicle upgrade master controller (VUC) is deployed. The VUC is the global master controller for the vehicle OTA upgrade and is responsible for coordinating the DUCs of the four functional domains (VDC, CDC, MDC and TBOX) to complete the vehicle upgrade process, including but not limited to: upgrade precondition detection, upgrade task management, inter-domain parallel scheduling, upgrade progress aggregation, OTA mode entry / exit control, high and low voltage power supply management, etc.
[0037] The VDC functional domain has the most ECUs in the vehicle and connects to three VIUs (VIU1, VIU2, and VIU3). Each VIU connects to one or more CAN / CANFD communication network segments, and each communication network segment connects to multiple ECUs. The CDC functional domain connects to only one communication network segment. The MDC functional domain connects to two communication network segments. The TBOX functional domain does not have any ECUs mounted. The TBOX functional domain mainly interacts with the cloud or electronic devices via Ethernet to obtain upgrade packages and distributes the upgrade packages to each functional domain via Ethernet. It can also summarize the upgrade progress of each functional domain and upload it to the cloud, electronic devices, or vehicle terminals.
[0038] In this diagram, red lines represent the public CAN bus, yellow lines represent the private CAN bus, and green lines represent Ethernet.
[0039] Figure 2 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 1 ;like Figure 2 As shown, the method includes: S101, the domain upgrade controller of the second functional domain interacts with the cloud via Ethernet to obtain upgrade packages for each electronic control unit and distributes them to the corresponding functional domain's domain upgrade controller.
[0040] As explained above, the second functional domain is the TBOX functional domain. The TBOX DUC in the TBOX functional domain can interact with the cloud via Ethernet to obtain upgrade packages for the target vehicle's ECUs. The upgrade packages may contain software upgrade data, such as new software versions or content to be updated. The TBOX DUC then distributes the obtained upgrade packages for each ECU to the corresponding DUC in the functional domain.
[0041] In some embodiments, the upgrade requirement may only target a subset of ECUs in the target vehicle. In such cases, the acquired upgrade package will only contain upgrade packages for those ECUs that need to be upgraded. For ECUs mounted under the VDC functional domain, the TBOX DUC will send the corresponding upgrade package to the VDC DUC; similarly, for ECUs mounted under the CDC functional domain, the TBOX DUC will send the corresponding upgrade package to the CDC DUC; and for ECUs mounted under the MDC functional domain, the TBOX DUC will send the corresponding upgrade package to the MDC DUC. The upgrade package for the TBOX DUC will be stored locally.
[0042] S102. When the upgrade master controller determines that the target vehicle meets the upgrade conditions, it triggers each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain to enter OTA mode.
[0043] Optionally, before executing the upgrade process, a precondition judgment is performed to determine whether the vehicle meets the upgrade conditions. This judgment can be performed by the OTA VUC deployed in the CDC functional domain. When the upgrade conditions are met, the ECUs under the three functional domains of VDC, CDC, and MDC are triggered to enter OTA mode synchronously, and the TBOXDUC under the TBOX functional domain is also controlled to enter OTA mode.
[0044] Next, the system enters the global Diagnostic Trouble Code (DTC) disabling phase. Specifically, each functional domain's DUC broadcasts a function addressing diagnostic command F10 83 (entering extended session mode) to its own functional domain after a 500ms delay. Every 2 seconds, it periodically broadcasts a function addressing command F3E 80 (maintaining the diagnostic session), and after a 500ms delay, it sends a function addressing command F8582 (disabling ECU DTC recording). During this phase, all ECUs respond positively by default.
[0045] By completely disabling the recording of DTCs, all ECUs in the vehicle can pause the recording of fault codes, preventing the generation of a large number of temporary fault codes during OTA upgrades and affecting the user experience.
[0046] S103. The domain upgrade controller of each first functional domain assigns the corresponding Ethernet multicast communication address to each communication network segment connected to the first functional domain.
[0047] For each of the above first functional domains, when there are multiple communication network segments connected under the first functional domain, a unique Ethernet multicast communication address, that is, an Ethernet multicast Internet Protocol (IP) address, can be assigned to each communication network segment connected to it through the DUC of the first functional domain.
[0048] For example, if multiple communication network segments are connected under a VDC functional domain, different Ethernet multicast IP addresses can be assigned to each communication network segment connected under each VIU through the VDC DUC, and each communication network segment corresponds to an independent multicast channel.
[0049] If only one communication network segment is connected under the functional domain, skip this step.
[0050] S104. The domain upgrade controller of each first functional domain controls the parallel upgrade process between the communication segments under the first functional domain according to the Ethernet multicast communication address corresponding to each communication segment connected to the first functional domain, and controls the electronic control units under a communication segment connected to the first functional domain to perform serial upgrade process according to the preset upgrade process and the upgrade package corresponding to each electronic control unit.
[0051] For scenarios involving multiple communication network segments connected within a functional domain, by assigning different Ethernet multicast IP addresses to each communication network segment, the DUC can simultaneously send corresponding upgrade commands to each communication network segment via different multicast IPs, thereby achieving parallel upgrade processing between communication network segments under different VIUs. For example, the communication network segments connected under VIU1, VIU2, and VIU3 within the VDC functional domain can undergo parallel upgrade processing. While the communication network segments under VIU1 are performing upgrade processing, the communication network segments under VIU2 and VIU3 are also simultaneously performing upgrade processing, thus enabling parallel processing between communication network segments within the domain.
[0052] For upgrade processing within a single communication network segment, a serial upgrade process can be performed within that segment according to a preset upgrade procedure.
[0053] The preset upgrade process can include several important processes such as upgrade preparation process, upgrade execution process, upgrade completion process, upgrade re-flash process, and version rollback process.
[0054] In some embodiments, the upgrades of the four functional domains—VDC, CDC, MDC, and TBOX—are also executed in parallel. After each ECU in the VDC, CDC, and MDC functional domains, as well as the TBOX DUC, synchronously enters OTA mode, the VDC DUC can control the upgrade processing of each ECU connected to the VDC functional domain. Simultaneously, the CDC DUC synchronously controls the upgrade processing of each ECU connected to the CDC functional domain, the MDC DUC synchronously controls the upgrade processing of each ECU connected to the MDC functional domain, and the TBOX DUC synchronously controls its own upgrade processing. This achieves parallel upgrade processing across vehicle domains, parallel upgrade processing of communication network segments within the same domain, and serial upgrade processing within a single communication network segment.
[0055] In summary, the OTA upgrade method provided in this embodiment includes: the domain upgrade controller of the second functional domain interacts with the cloud via Ethernet to obtain upgrade packages for each electronic control unit and sends them to the corresponding domain upgrade controller of the functional domain; when the upgrade master controller determines that the target vehicle meets the upgrade conditions, it triggers each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain to enter OTA mode; each domain upgrade controller of the first functional domain allocates a corresponding Ethernet multicast communication address to each communication network segment connected to the first functional domain; each domain upgrade controller of the first functional domain controls the parallel upgrade processing between each communication network segment under the first functional domain according to the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain, and controls each electronic control unit under a communication network segment connected to the first functional domain to perform serial upgrade processing according to the preset upgrade process and the upgrade package corresponding to each electronic control unit. This method divides the entire vehicle into functional domains, integrates domain upgrade controllers in each functional domain, and integrates a central upgrade controller in the core functional domain, enabling unified OTA upgrade management and control across the entire domain. The domain upgrade controllers in each functional domain can control parallel upgrade processing between domains. By assigning different Ethernet multicast communication addresses to multiple communication segments within a functional domain, and combining this with Ethernet multicast technology, parallel upgrade processing between multiple communication segments within a domain, as well as serial upgrade processing within a single communication segment, can be achieved. Compared to the traditional full-domain serial approach, this effectively shortens upgrade time and improves upgrade efficiency.
[0056] Figure 3 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 2 Optionally, in step S102, when the upgrade master controller determines that the target vehicle meets the upgrade conditions, it triggers each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain to enter OTA mode, including: S201. When the upgrade master controller determines that the target vehicle meets the upgrade conditions, it calls the vehicle mode manager to broadcast the target command to the entire network segment.
[0057] In some embodiments, the OTA VUC in the CDC functional domain sends a mode setting request to the Vehicle Motion Manager (VMM) in the VIU1 of the VDC functional domain. After receiving the mode setting request, the VMM broadcasts the USageMode=0x4 (OTA Updating) instruction across the entire network segment via the Ethernet service interface and CAN signal to notify all ECUs in the entire network segment that an OTA upgrade is about to begin.
[0058] S202, each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain receive the target instruction, switch the status identifier to the first identifier to enter OTA mode, and start the timeout timer.
[0059] The VMM broadcast command UsageMode=0x4 can be heard by all ECUs and TBOX DUC. After receiving the command, each ECU and TBOX DUC will switch its own status flag OTAMode from the initial default False to True, thereby entering OTA mode, and at the same time, a 2-minute timeout timer can be started.
[0060] S203. During the timeout period or after entering OTA mode, determine whether to exit OTA mode based on the received signal.
[0061] Optionally, the decision to exit OTA mode can be made based on the signal reception during the timeout period or the signal reception within a preset time after entering OTA mode.
[0062] Optionally, in step S203, during the timeout period or after entering OTA mode, it is determined whether to exit OTA mode based on the received signal, including: if no upgrade signal is received during the timeout period, the status identifier is switched to the second identifier to exit OTA mode.
[0063] In one implementation, if no UsageMode=OTA signal or a non-OTA UsageMode signal is received during the 2-minute timeout period (i.e., no upgrade-related signal is received), the OTAMode status flag is switched to False, and the OTA mode is exited. In other words, if no upgrade signal is received after entering OTA mode, the upgrade is not performed by default, and the OTA mode can be exited.
[0064] Alternatively, after entering OTA mode, if a diagnostic keep-alive message is received within a preset time period, the timeout timer is reset, and the diagnostic keep-alive message is received again until no diagnostic keep-alive message is received within the timeout period, and the timeout timer expires. Then, the status flag is switched to the second flag to exit OTA mode.
[0065] In another implementation, to ensure the persistence of OTA mode during the domain upgrade controller's own upgrade activation process, after entering OTA mode, as long as a diagnostic keep-alive message is received within 2 seconds, OTAMode=True can be maintained and the 2-minute timeout timer can be reset, without relying on the upgrade signal USageMode. In this way, as long as a diagnostic keep-alive message is received every 2 minutes, OTA mode can be maintained until no diagnostic keep-alive message is received for more than 2 minutes and no upgrade signal is received within the 2-minute timeout timer. Then, OTAMode is set to False and OTA mode is exited.
[0066] This mechanism ensures that the OTA mode will not exit due to a brief loss of signal during the reset and activation process after the ECU performs a software upgrade.
[0067] Optionally, the VMM persistently stores the OTA delay exit time in Flash to ensure that the VIU1 can maintain OTA mode after completing software upgrades and activation. The default delay exit time is 3 minutes, which can be extended to 30 minutes in Recovery mode upgrade scenarios. The delay time in Flash is cleared after exiting OTA mode.
[0068] Optionally, each first functional domain also integrates an intra-domain flashing actuator, which is connected to one or more communication network segments through one or more vehicle interface units. In step S103, the domain upgrade controller of each first functional domain controls the parallel upgrade process between the communication network segments under the first functional domain according to the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain. This includes: the domain upgrade controller of the first functional domain sends upgrade instructions in parallel to the vehicle interface unit corresponding to each communication network segment according to the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain. The vehicle interface unit converts the upgrade instructions into upgrade messages corresponding to the communication network segment and sends them to the communication network segment to realize the parallel upgrade process between the communication network segments.
[0069] Taking the VDC functional domain as an example, each communication network segment is connected to the corresponding VIU, that is, VIU1, VIU2 and VIU3 can be connected to one or more communication network segments respectively.
[0070] For parallel upgrade processing between communication network segments within each domain, the VDC DUC can simultaneously send diagnostic commands to VIU1, VIU2, and VIU3 based on the Ethernet multicast communication addresses allocated to each communication network segment. Upon receiving the diagnostic commands, VIU1, VIU2, and VIU3 can convert them into diagnostic messages for their respective connected communication network segments and distribute them to the corresponding communication network segments to execute the upgrade process. The diagnostic commands contain upgrade instructions. Each VIU simultaneously receives the diagnostic commands, and the communication network segments under each VIU execute the upgrade process in parallel.
[0071] Optionally, in step S104, according to the preset upgrade process and the upgrade package corresponding to each electronic control unit, the electronic control units under a communication network segment connected to the first functional domain are controlled to perform serial upgrade processing, including: the domain upgrade controller of the first functional domain, according to the preset upgrade process and upgrade task type, uses the upgrade package corresponding to each electronic control unit to sequentially control each electronic control unit under a communication network segment to perform serial upgrade processing.
[0072] For upgrade processing within a single communication network segment, a serial process can be executed based on a preset upgrade procedure to upgrade each ECU within the single communication network segment in sequence.
[0073] In some embodiments, during the upgrade process, it can be determined whether the upgrade task requires high-voltage support, that is, whether the upgrade task type is a high-voltage upgrade or a low-voltage upgrade. If it is a high-voltage upgrade task, the high-voltage ECUs need to be upgraded sequentially first. Only after all the high-voltage ECUs have been upgraded can the remaining low-voltage ECUs be upgraded sequentially. If it is a low-voltage upgrade task, all the low-voltage ECUs are upgraded sequentially directly.
[0074] Therefore, when performing serial upgrade processing within a single communication network segment, it is necessary to sort the upgrade priorities of each ECU within the communication network segment according to the upgrade task type so that the serial upgrade processing can be performed in sequence.
[0075] Figure 4 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 3 Optionally, in the above steps, the domain upgrade controller of the first functional domain, according to the preset upgrade process and upgrade task type, uses the upgrade package corresponding to each electronic control unit to sequentially control each electronic control unit under a communication network segment to perform serial upgrade processing, including: S301. If the upgrade task type is high voltage upgrade, then call the high voltage management service to power on the high voltage and maintain it.
[0076] In one scenario, if the upgrade task type is a high-voltage upgrade, the OTA VUC in the CDC functional domain first calls the high-voltage management service of the first functional domain to request high-voltage power-on and maintain it.
[0077] S302. Based on the high and low voltage types and priorities of each electronic control unit under the communication network segment, determine each high voltage electronic control unit and its upgrade priority from among the electronic control units under the communication network segment.
[0078] After confirming successful high-voltage power-on, a high-voltage power-on success confirmation message is sent to the domain upgrade controller of the first functional domain. The domain upgrade controller of the first functional domain then identifies all high-voltage ECUs based on the high and low voltage types and priorities of each ECU within a single communication network segment, and determines the upgrade priority of each high-voltage ECU.
[0079] S303. Based on the upgrade priority of each high-voltage electronic control unit, and following the preset upgrade process, upgrade each high-voltage electronic control unit sequentially using the corresponding upgrade package.
[0080] According to the upgrade priority of each high-voltage ECU, the preset upgrade process is used to perform upgrade processing on each high-voltage ECU in sequence.
[0081] S304. After the upgrade of each high-voltage electronic control unit is completed, the high-voltage management service is invoked to power off the high voltage.
[0082] After all high-voltage ECUs have been upgraded, an OTA VUC is requested to power down the high voltage. The OTA VUC then calls the high-voltage management service to power down the high voltage.
[0083] S305. Determine the low-voltage electronic control unit and its upgrade priority from the remaining electronic control units under the communication network segment.
[0084] S306. Based on the upgrade priority of each low-voltage electronic control unit, and following the preset upgrade process, upgrade each low-voltage electronic control unit sequentially using the corresponding upgrade package.
[0085] Then, the remaining low-voltage ECUs are upgraded in sequence according to their upgrade priority.
[0086] In some embodiments, if the upgrade task type is low-voltage upgrade, it is first confirmed that the high voltage is in a power-off state, and under the power-off state of the high voltage, the low-voltage upgrade process is directly performed on each low-voltage ECU in sequence according to the upgrade priority of each low-voltage ECU.
[0087] Figure 5This application provides a flowchart of a high- and low-voltage zone security upgrade process. Figure 5 For detailed implementation of each step, please refer to [link / reference]. Figure 4 This will be understood in more detail here.
[0088] Figure 6 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 4 Optionally, in step S304, according to the upgrade priority of each high-voltage electronic control unit, and following a preset upgrade process, the upgrade packages corresponding to each high-voltage electronic control unit are used to sequentially upgrade each high-voltage electronic control unit, including: S401. Based on the upgrade priority of each high-voltage electronic control unit, determine the target high-voltage electronic control unit to be upgraded.
[0089] This embodiment uses the upgrade process of any single ECU as an example to provide an overall description of the upgrade process. The target high-voltage electronic control unit to be upgraded can refer to any ECU that needs to be upgraded.
[0090] S402. Following the preset upgrade process, the target high-voltage electronic control unit is upgraded using the upgrade package corresponding to the target high-voltage electronic control unit via the domain flashing actuator.
[0091] After entering OTA mode, the first step is to execute the full-domain DTC blocking procedure. The specific steps may include: 1. The DUC within the functional domain broadcasts the function addressing command F10 83 within its own functional domain, and the ECU responds; 2. The DUC within the functional domain broadcasts the function addressing command F3E 80 within its own functional domain (sent once every 2 seconds), and the ECU responds; 3. The DUC within the functional domain broadcasts the function addressing command F85 82 within its own functional domain to block DTC recording, and the ECU responds.
[0092] The next step is to execute the upgrade preparation process, which may include the following steps: 1. The DUC sends the physical addressing command 31 01 0203 to perform pre-programming condition detection on the ECU. In OTA mode, the ECU directly replies with a positive response indicating success (skipping the judgment of communication-related conditions, such as vehicle speed and gear); 2. The DUC sends the function addressing command F28 83 01 (close communication 1), and the ECU responds to the command; 3. The DUC sends the function addressing command F28 83 03 (close communication 2), and the ECU responds to the command; 4. The DUC sends the physical addressing command P22 F0 F0 (query the activation area) to determine whether the ECU is a dual-zone controller, and the ECU responds to the command.
[0093] Then, the upgrade process is executed, and the specific steps may include: 1. DUC sends physical addressing command P10 02 (enters editing session mode); 2. DUC sends physical addressing command P27 09 / 0A (performs secure access); 3. DUC sends physical addressing command P2E F1 84 (writes fingerprint information); 4. DUC performs file transfer or software flashing according to the upgrade specifications, including service 34 (requests download, informing the starting address and total length of the downloaded data), service 38 (transfers data, for file transfer), service 36 (transfers data, for byte data transfer), service 37 (requests to exit transfer), and secure signature check 31 01 DD02, and supports the retransmission mechanism of service 36; 5. For dual-partition ECUs, DUC may optionally send physical addressing command P31 01 DD 0F (prevents partition switching); 6. DUC sends physical addressing command P31 01 FF 01 (data compatibility check); 7. For intelligent ECUs, DUC may optionally send physical addressing command P31 01 DD 03 (Start installation); 8. For intelligent ECUs, DUC can optionally send physical addressing commands P22 F0 F2 (to check upgrade progress).
[0094] It should be noted that the specific upgrade process can be executed by the domain-specific flashing executor deployed in the functional domain.
[0095] S403. Determine whether the target high-voltage electronic control unit has been successfully upgraded.
[0096] After all the above processes are completed, DUC determines whether the upgrade of the target ECU is successful.
[0097] S404. If the upgrade is successful, determine whether the upgraded software version of the target high-voltage electronic control unit is correct.
[0098] If the upgrade is successful, the upgrade completion process will be executed, and the specific steps include: 1. DUC sends function addressing command F2880 01 (open communication 1); 2. DUC sends function addressing command F28 80 03 (open communication 2); 3. Wait 5 seconds, DUC sends physical addressing command P11 01 (ECU reset); 4. DUC sends function addressing command F10 83 (enter extended mode); 5. DUC sends function addressing command F85 82 (disable DTC recording); 6. DUC sends physical addressing command P22 F1 89 (get software version number) to verify the flashing result.
[0099] Based on the obtained software version number, determine whether the upgraded software version of the target ECU is correct.
[0100] S405. If the version is correct, the high-voltage electronic control unit of the control target will switch to the OTA exit waiting mode.
[0101] If the software version is correct, wait to enter OTA exit mode.
[0102] S406. If the upgrade fails and the number of re-flashes has not exceeded the preset configuration number, then perform a re-flash. Once the re-flash is complete and the version is correct, switch the target high-voltage electronic control unit to the waiting OTA exit mode.
[0103] In some cases, if the upgrade fails and the number of re-flashes has not exceeded the configuration limit (usually 2), a re-flash procedure will be executed. The specific steps of the re-flash procedure may include: 1. DUC sends function addressing command F28 80 01 (opens communication 1); 2. DUC sends function addressing command F28 80 03 (opens communication 2); 3. DUC sends physical addressing command P11 01 (ECU reset); 4. DUC sends function addressing command F10 83 (enters extended mode); 5. DUC sends function addressing command F85 82 (disables DTC); 6. DUC resends commands according to the upgrade preparation procedure; 7. DUC resends commands according to the upgrade processing procedure.
[0104] If the number of retries exceeds the configured limit, the upgrade process will be completed, and the upgraded software version will be obtained to determine the correctness of the software version.
[0105] S407. If the version is incorrect, the target high-voltage electronic control unit will be rolled back using the domain flashing executor to roll back the software version of the target high-voltage electronic control unit to the previous version. After the rollback is completed, the target high-voltage electronic control unit will be switched to the OTA exit waiting mode.
[0106] Optionally, if the upgraded software version is incorrect, the rollback reason and notification can be fed back to the cloud (which can be the OTA platform) or the vehicle terminal via OTA VUC, and the rollback information can be displayed through a visual interface.
[0107] The version rollback process can be executed in the following ways: For ECUs that do not support dual partitions and do not support self-rollback: 1. DUC sends instructions according to the upgrade preparation process; 2. DUC sends instructions according to the upgrade processing process; 3. DUC sends instructions according to the upgrade completion process; For ECUs that do not support dual partitions but support self-rollback: follow the partition switching process; For ECUs that support dual partitions: follow the partition switching process.
[0108] After the version rollback process is completed, it is determined whether all ECUs have been rolled back. If so, it waits for OTA to exit mode.
[0109] Figure 7This is a schematic diagram illustrating the entire process of an OTA upgrade method within a functional domain, as provided in the embodiments of this application. Each step in the diagram is already shown. Figure 6 The detailed steps are explained in the documentation and will not be repeated here.
[0110] It is worth noting that the specific implementation steps of the aforementioned full-domain DTC ban process, upgrade preparation process, upgrade processing process, upgrade completion process, re-flashing process, and version rollback process can all be performed with reference to existing technologies. In each of the above processes, the physical addressing command and function addressing command sent by DUC are all sent to the ECU to be upgraded, and by default, the ECU responds positively.
[0111] In this diagram, the domain controller refers to the Domain Upgrade Controller (DUC). The flashing / installation preparation process refers to the upgrade preparation process described above; the flashing / installation execution process refers to the upgrade processing process described above; and the flashing / installation completion process refers to the upgrade completion process described above.
[0112] Figure 8 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 5 Optionally, this method also includes: S501. When all electronic control units in each communication network segment under each first functional domain have completed the upgrade and are in the waiting OTA exit mode, the domain upgrade controller of each first functional domain sends asset information acquisition instructions to each electronic control unit in each communication network segment under the first functional domain in sequence to obtain the asset information of each electronic control unit.
[0113] Asset information includes one or more of the following: part number, software version number, supplier code, electronic control unit identifier, serial number code, hardware version number, electronic control unit batch number, bootloader software version number, and backup area software version number.
[0114] While each ECU completes its upgrade and enters the OTA exit waiting mode, the asset information acquisition process and fault code clearing process can still be executed.
[0115] The specific steps of the asset information acquisition process may include: 1. DUC sends the function addressing instruction F10 81; 2. DUC sends the physical addressing instruction F22 xx xx (acquire asset information).
[0116] S502. A dual-cycle code clearing strategy is executed using extended diagnostic mode and default diagnostic mode. Fault code clearing instructions are sent sequentially to each electronic control unit in each communication network segment under the first functional domain to clear the temporary fault codes generated by each electronic control unit during the upgrade process.
[0117] After the asset information is acquired, the fault code clearing process is executed. In this embodiment, a dual-loop clearing strategy can be adopted, and the general steps include: First loop: 1. DUC sends function addressing instruction F10 83, with a delay of 1 second; 2. DUC sends function addressing instruction F85 82; 3. DUC sends function addressing instruction F10 83, with a delay of 10 seconds; 4. DUC sends function addressing instruction F14 FFFF FF; Second loop: 1. DUC sends function addressing instruction F10 83, with a delay of 1 second; 2. DUC sends function addressing instruction F85 81; 3. DUC sends function addressing instruction F10 81, with a delay of 10 seconds; 4. DUC sends function addressing instruction F14 FF FF FF.
[0118] The dual-cycle clearing strategy in this embodiment performs fault code clearing operations in extended diagnostic mode (83) and default diagnostic mode (81) respectively, covering temporary fault codes that may be generated in different diagnostic session modes, ensuring that all temporary fault codes generated during the OTA upgrade process are completely cleared, and significantly improving the consistency of the vehicle's fault code-free state after the OTA upgrade.
[0119] Figure 9 This is a schematic diagram of a processing flow for the OTA exit mode stage provided in an embodiment of this application. Each step has been described above and will not be repeated here.
[0120] Optionally, in step S104, according to the preset upgrade process and the upgrade package corresponding to each electronic control unit, the electronic control units under a communication network segment connected to the first functional domain are controlled to perform serial upgrade processing, including: the domain upgrade controller of each first functional domain controls the electronic control units under a communication network segment connected to the first functional domain to perform serial upgrade processing according to the preset upgrade process and the upgrade package corresponding to each electronic control unit, using the communication protocol corresponding to the first functional domain.
[0121] In some embodiments, differentiated upgrade processes may be performed using differentiated strategies for different functional domains.
[0122] For upgrades of ECUs within the VDC functional domain, Unified Diagnostic Services (UDS) can be used, with unified scheduling by the VDC DUC. The EMS controller uses a proprietary protocol from United Automotive Electronics Corporation (UAEC) and requires separate adaptation.
[0123] For the upgrade processing of each ECU under the MDC functional domain, the software upgrade is completed using the MDC private protocol and is uniformly scheduled by MDC DUC.
[0124] Upgrades for each ECU within the CDC functional domain can be divided into two categories: IC, PIC, CDS, and PLM complete software upgrades through the CDC proprietary communication protocol, namely the Inter-Integrated Circuit I2C bus; HUD and EPA are upgraded through UDS.
[0125] Optionally, the second functional domain also integrates an in-domain write executor; this method also includes: The domain upgrade controller of the second functional domain performs upgrade processing on the controllers under the second functional domain through the domain-intra-domain flashing executor, based on the upgrade package obtained from the cloud.
[0126] For the TBOX functional domain, a self-installation mode is used to complete its own upgrade.
[0127] Figure 10 A flowchart illustrating the OTA upgrade method provided in this application embodiment. Figure 6 Optionally, this method also includes: S601. The domain upgrade controller of each first functional domain periodically reports the upgrade progress of the first functional domain to the upgrade master controller in the target functional domain.
[0128] S602. The upgrade master controller integrates the upgrade progress of each first functional domain, obtains the intermediate integration result, and sends the intermediate integration result to the domain upgrade controller of the second functional domain.
[0129] S603, the domain upgrade controller of the second functional domain integrates the intermediate integration results with the upgrade progress of the second functional domain again to obtain the target integration result, and sends the target integration result to the cloud or the central control device of the target vehicle for visualization.
[0130] In some embodiments, the upgrade progress of each functional domain can also be aggregated and summarized to OTA VUC. OTA VUC sends the aggregation result to TBOX DUC, and after summarizing it with the upgrade progress of the TBOX functional domain, TBOX DUC sends the final summary result, i.e. the target integration result, to the cloud, vehicle terminal, or vehicle central control device via Ethernet for visualization, thereby realizing global visualization of the entire vehicle's full-domain upgrade.
[0131] Figure 11 This is a schematic diagram of the architecture for multi-domain differentiated upgrade collaborative scheduling and visualization summary provided in the embodiments of this application. The specific steps will not be described in detail.
[0132] In summary, the OTA upgrade method provided in this embodiment includes: the domain upgrade controller of the second functional domain interacts with the cloud via Ethernet to obtain upgrade packages for each electronic control unit and sends them to the corresponding domain upgrade controller of the functional domain; when the upgrade master controller determines that the target vehicle meets the upgrade conditions, it triggers each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain to enter OTA mode; each domain upgrade controller of the first functional domain allocates a corresponding Ethernet multicast communication address to each communication network segment connected to the first functional domain; each domain upgrade controller of the first functional domain controls the parallel upgrade processing between each communication network segment under the first functional domain according to the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain, and controls each electronic control unit under a communication network segment connected to the first functional domain to perform serial upgrade processing according to the preset upgrade process and the upgrade package corresponding to each electronic control unit. This method divides the entire vehicle into functional domains, integrates domain upgrade controllers in each functional domain, and integrates a central upgrade controller in the core functional domain, enabling unified OTA upgrade management and control across the entire domain. The domain upgrade controllers in each functional domain can control parallel upgrade processing between domains. By assigning different Ethernet multicast communication addresses to multiple communication segments within a functional domain, and combining this with Ethernet multicast technology, parallel upgrade processing between multiple communication segments within a domain, as well as serial upgrade processing within a single communication segment, can be achieved. Compared to the traditional full-domain serial approach, this effectively shortens upgrade time and improves upgrade efficiency.
[0133] Secondly, by broadcasting target commands across the entire domain, combined with multiple safeguards including status flag switching, timeout signal reception, diagnostic keep-alive message reception, and persistent Flash storage, unified OTA mode synchronization management is achieved across the entire domain. This ensures that all ECUs in the vehicle maintain OTA mode synchronization throughout the entire upgrade process (including DUC self-upgrade activation), avoiding global state inconsistencies caused by OTA mode loss after DUC upgrade reset. The Flash persistence mechanism allows the VMM to restore its OTA mode state after its own upgrade activation, avoiding blind spots in mode management introduced by VMM upgrades.
[0134] In addition, the upgrade's fault tolerance is ensured through re-flashing and version rollback, thus guaranteeing the reliability of the upgrade.
[0135] Moreover, VUC enables differentiated upgrade coordination and scheduling across different functional domains, as well as the aggregation of upgrade progress. It achieves unified scheduling and progress aggregation for various upgrade methods and exhibits excellent scalability.
[0136] Based on the upgrade task type, high and low voltage partition upgrade processing is performed. By upgrading high voltage first and then low voltage, it can be ensured that the upgrade processing of high voltage safety-related ECUs is completed first under the condition of high voltage power supply guarantee, avoiding the inability to upgrade low voltage ECUs after high voltage loss and the high voltage safety hazards during the low voltage ECU upgrade process.
[0137] During the OTA exit phase, a dual-cycle fault code clearing strategy is adopted to ensure that temporary fault codes generated in different diagnostic session modes during the OTA upgrade process are completely cleared, avoiding residual fault lights on the vehicle's dashboard after the upgrade and improving the user's driving experience after the upgrade.
[0138] These controllers can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together as a system-on-a-chip (SOC).
[0139] The controllers described above can connect or communicate with each other via wired or wireless connections. Wired connections may include metal cables, optical fibers, hybrid cables, or any combination thereof. Wireless connections may include connections via LAN, WAN, Bluetooth, ZigBee, or NFC, or any combination thereof. Two or more units can be combined into a single module, and any module can be divided into two or more units. Those skilled in the art will readily understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here.
[0140] Optionally, this application also provides a program product, such as a computer-readable storage medium, including a program that, when executed by a processor, performs the above-described method embodiments.
[0141] In the several embodiments provided in this application, it should be understood that the disclosed methods can be implemented in other ways. Furthermore, the mutual couplings or direct couplings or communication connections shown or discussed can be indirect couplings or communication connections through some interfaces, devices, or units, and can be electrical, mechanical, or other forms.
[0142] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0143] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.
[0144] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
Claims
1. An OTA upgrade method, characterized in that, include: The method is applied to a target vehicle, which includes multiple first functional domains and second functional domains, each of which integrates a domain upgrade controller; wherein a target functional domain among the multiple first functional domains also integrates a master upgrade controller; each first functional domain is connected to one or more communication network segments; each communication network segment is connected to one or more electronic control units; the method includes: The domain upgrade controller of the second functional domain interacts with the cloud via Ethernet to obtain upgrade packages for each electronic control unit and distributes them to the corresponding functional domain's domain upgrade controller. When the upgrade master controller determines that the target vehicle meets the upgrade conditions, it triggers each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain to enter OTA mode. The domain upgrade controller of each first functional domain assigns corresponding Ethernet multicast communication addresses to each communication network segment connected to the first functional domain. Each first functional domain's domain upgrade controller controls the parallel upgrade process between communication network segments under the first functional domain based on the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain, and controls the electronic control units under a communication network segment connected to the first functional domain to perform serial upgrade process based on the preset upgrade process and the upgrade package corresponding to each electronic control unit.
2. The method according to claim 1, characterized in that, When the upgrade master controller determines that the target vehicle meets the upgrade conditions, it triggers each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain to enter OTA mode, including: When the upgrade controller determines that the target vehicle meets the upgrade conditions, it calls the vehicle mode manager to broadcast the target command to the entire network segment. Each electronic control unit under each communication network segment and the domain upgrade controller of the second functional domain receive the target instruction, switch the status identifier to the first identifier to enter OTA mode, and start the timeout timer; During the timeout period or after entering OTA mode, determine whether to exit OTA mode based on the received signal.
3. The method according to claim 1, characterized in that, Each first functional domain also integrates an intra-domain write actuator, which is connected to one or more communication network segments through one or more vehicle interface units. The domain upgrade controller of each first functional domain controls the parallel upgrade process between communication network segments under the first functional domain according to the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain, including: The domain upgrade controller of the first functional domain sends upgrade instructions in parallel to the vehicle interface unit corresponding to each communication network segment according to the Ethernet multicast communication address corresponding to each communication network segment connected to the first functional domain. The vehicle interface unit converts the upgrade instructions into upgrade messages corresponding to the communication network segment and sends them to the communication network segment to realize parallel upgrade processing between communication network segments.
4. The method according to claim 1, characterized in that, The step of controlling each electronic control unit under a communication network segment connected to the first functional domain to perform serial upgrade processing according to a preset upgrade process and the upgrade package corresponding to each electronic control unit includes: The domain upgrade controller of the first functional domain, based on the preset upgrade process and upgrade task type, uses the upgrade package corresponding to each electronic control unit to sequentially control each electronic control unit under a communication network segment to perform serial upgrade processing.
5. The method according to claim 4, characterized in that, The domain upgrade controller of the first functional domain, based on a preset upgrade process and upgrade task type, uses the upgrade package corresponding to each electronic control unit to sequentially control each electronic control unit under a communication network segment to perform serial upgrade processing, including: If the upgrade task type is high-voltage upgrade, then the high-voltage management service is invoked to power on the high voltage and maintain it; Based on the high and low voltage types and priorities of each electronic control unit under the communication network segment, determine each high voltage electronic control unit and its upgrade priority from among the electronic control units under the communication network segment; Based on the upgrade priority of each high-voltage electronic control unit, and following the preset upgrade process, each high-voltage electronic control unit is upgraded sequentially using the corresponding upgrade package. After the upgrade of each high-voltage electronic control unit is completed, the high-voltage management service is invoked to power off the high voltage. Determine each low-voltage electronic control unit and its upgrade priority from the remaining electronic control units under the communication network segment; Based on the upgrade priority of each low-voltage electronic control unit, and following the preset upgrade process, the upgrade packages corresponding to each low-voltage electronic control unit are used to upgrade each low-voltage electronic control unit in sequence.
6. The method according to claim 5, characterized in that, The upgrade process, based on the upgrade priority of each high-voltage electronic control unit and following the preset upgrade procedure, sequentially upgrades each high-voltage electronic control unit using the corresponding upgrade package, including: Based on the upgrade priority of each high-voltage electronic control unit, determine the target high-voltage electronic control unit to be upgraded; According to the preset upgrade process, the target high-voltage electronic control unit is upgraded using the upgrade package corresponding to the target high-voltage electronic control unit through the domain flashing actuator. Determine whether the target high-voltage electronic control unit has been successfully upgraded; If the upgrade is successful, determine whether the upgraded software version of the target high-voltage electronic control unit is correct; If the version is correct, control the target high-voltage electronic control unit to switch to the OTA exit waiting mode; If the upgrade fails and the number of re-flashes does not exceed the preset configuration number, then a re-flash is performed. Once the re-flash is complete and the version is correct, the target high-voltage electronic control unit is switched to the OTA exit waiting mode. If the version is incorrect, the target high-voltage electronic control unit will be rolled back using the domain flashing executor to roll back the software version of the target high-voltage electronic control unit to the previous version. After the rollback is completed, the target high-voltage electronic control unit will be switched to the OTA exit waiting mode.
7. The method according to claim 1, characterized in that, The step of controlling each electronic control unit under a communication network segment connected to the first functional domain to perform serial upgrade processing according to a preset upgrade process and the upgrade package corresponding to each electronic control unit includes: Each first functional domain's domain upgrade controller, based on a preset upgrade process and the upgrade package corresponding to each electronic control unit, uses the communication protocol corresponding to the first functional domain to control each electronic control unit under a communication network segment connected to the first functional domain to perform serial upgrade processing.
8. The method according to claim 1, characterized in that, The method further includes: Each first functional domain's domain upgrade controller periodically reports the upgrade progress of the first functional domain to the overall upgrade controller in the target functional domain; The upgrade master controller integrates the upgrade progress of each first functional domain, obtains an intermediate integration result, and sends the intermediate integration result to the domain upgrade controller of the second functional domain. The domain upgrade controller of the second functional domain integrates the intermediate integration result with the upgrade progress of the second functional domain again to obtain the target integration result, and sends the target integration result to the cloud or the central control device of the target vehicle for visualization.
9. A vehicle, characterized in that, include: The system comprises multiple first functional domains and second functional domains, each integrating a domain upgrade controller and an intra-domain flashing actuator. A target functional domain within each of the first functional domains also integrates a central upgrade controller. The intra-domain flashing actuators in each first functional domain are connected to a communication network segment via one or more vehicle interface units. Each communication network segment carries one or more electronic control units (ECUs). The domain upgrade controller of the second functional domain interacts with the cloud via Ethernet to obtain upgrade packages for each ECU and distributes them to the corresponding domain upgrade controller. The domain upgrade controller in each first functional domain is used to execute the method steps executed by the domain upgrade controller in each first functional domain as described in any one of claims 1-8; The domain upgrade controller in the second functional domain is used to execute the method steps performed by the domain upgrade controller in the second functional domain as described in any one of claims 1-8; The upgrade master controller in the target functional domain is used to execute the method steps performed by the upgrade master controller as described in any one of claims 1-8.
10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which is executed by a processor to implement the steps of the method as described in any one of claims 1-8.
