Upgrading method of vehicle-mounted domain controller, domain controller, vehicle and program product

By responding to upgrade requests on the domain controller and processing them by the MCU in the default session, the compatibility problem between the on-board domain controller and the ECU in software upgrade is solved, and the simultaneous upgrade of the ECU and the domain controller is realized, simplifying the entire process Car upgrade process.

CN118963811AInactive Publication Date: 2024-11-15BEIJING JIDU TECH CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202411440818.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-15
Publication Date
2024-11-15
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The on-board domain controller based on Linux system is incompatible with conventional ECUs in software upgrades, resulting in different upgrade strategies and the software upgrade cannot be performed simultaneously.

Method used

By responding to the upgrade request in the domain controller's SoC, and the MCU completes the pre-upgrade process in the default session, ensuring that the working modes between the domain controller and the ECU are compatible, thereby achieving the same upgrade strategy in the vehicle upgrade process. and simultaneous software upgrades.

Benefits of technology

It realizes software upgrade compatibility between ECU and domain controller, allowing both to be upgraded at the same time, simplifying the vehicle upgrade process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118963811A_ABST
    Figure CN118963811A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides an upgrading method of a vehicle-mounted domain controller, the domain controller, a vehicle and a program product, the domain controller comprises an SoC and an MCU, the method is applied to the MCU, and the method comprises the steps that under the condition that a pre-upgrading notification for the domain controller is received, pre-upgrading processing is executed in a default session; the pre-upgrading notification is sent by the SoC based on the domain controller upgrading request; the domain controller upgrading request is sent to the SoC by an upgrading request direction; and executing a preset recovery process in a default session when an upgrade completion notification for the domain controller sent by the SoC is received. The SoC responds to an upgrade request of the domain controller to enter a programming session, and the MCU completes pre-upgrade processing of the domain controller in a default session, so that the working modes between the domain controller and other vehicle-mounted modules are aligned. For the whole vehicle upgrading process, the domain controller enters a programming session in the pre-upgrading stage. For the domain controller, the MCU executes preparatory work of a pre-upgrade stage in a default session, thereby realizing upgrade compatibility.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to an upgrade method for a vehicle-mounted domain controller, a domain controller, a vehicle, and a program product. Background Art

[0002] With the rapid development of automotive-defined software, the vehicle's OTA (Over-the-Air Technology) has become more mature and stable. As a software iteration channel, the stability of OTA is directly related to the launch of new functions. Usually, the software update of ECU is completed by bootloader in the boot layer. However, for the vehicle domain controller based on Linux system, it usually completes the software upgrade in the APP (Application) layer above the boot layer. This leads to the technical problem that conventional ECU and domain controller are incompatible in software upgrade. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a method for upgrading a vehicle-mounted domain controller, a domain controller, a vehicle and a program product, so as to achieve the technical effect of compatible ECU and domain controller upgrades.

[0004] A first aspect of an embodiment of the present application provides a method for upgrading a vehicle-mounted domain controller, wherein the domain controller includes a system on chip (SoC) and a microcontroller unit (MCU). The method is applied to the MCU, and the method includes: In the case of receiving a pre-upgrade notification for the domain controller, performing a preset pre-upgrade process in a default session; wherein the pre-upgrade notification is sent by the SoC based on a domain controller upgrade request; and the domain controller upgrade request is sent by an upgrade requester to the SoC; When receiving the upgrade completion notification for the domain controller sent by the SoC, a preset recovery process is performed in the default session.

[0005] In the above implementation process, the SoC in the domain controller enters the programming session in response to the domain controller upgrade request, and the MCU completes the pre-upgrade processing of the domain controller in the default session, thereby aligning the working modes between the domain controller and other modules to be upgraded. For the whole vehicle upgrade process, the domain controller enters the programming session in the pre-upgrade stage, but for the domain controller, it is the MCU that performs the preparatory work in the pre-upgrade stage in the default session. Therefore, the whole vehicle upgrade process can adopt the same upgrade strategy, and initiate upgrade requests for other modules to be upgraded and the domain controller at the same time. The software upgrades of both can also be carried out at the same time, achieving upgrade compatibility between the two.

[0006] Furthermore, the domain controller upgrade request is sent by the upgrade requester to the SoC through functional addressing and / or physical addressing.

[0007] In the above implementation process, the upgrade requester completes the process of sending the domain controller upgrade request to the SoC of the domain controller by means of functional addressing and / or physical addressing.

[0008] Furthermore, after completing the pre-upgrade process, the method further includes: Pre-upgrade readiness information is sent to the SoC, so that the SoC sends an upgrade response based on the domain controller upgrade request to the upgrade requester.

[0009] In the above implementation process, the upgrade readiness information is fed back to the SoC through the MCU, so that the SoC feeds back the upgrade response to the upgrade requester at the APP layer, thereby aligning the working modes between the domain controller and the ECU and achieving upgrade compatibility between the two.

[0010] Furthermore, the pre-upgrade process includes one or more of shutting down the diagnostic fault code storage service, shutting down the network management, silencing the domain controller bus, and maintaining the diagnostic route; and the recovery process is the reverse process of the pre-upgrade process.

[0011] Furthermore, the method further comprises: In case of receiving the MCU upgrade request sent by the SoC, the programming session is entered from the default session to perform software upgrade processing, and after the upgrade, the default session is entered from the programming session.

[0012] In the above implementation process, the SoC guides the MCU to complete the upgrade process, that is, the MCU no longer responds to the domain controller upgrade request in the vehicle upgrade process, but only responds to the MCU upgrade request of the SoC.

[0013] A second aspect of an embodiment of the present application provides a method for upgrading a vehicle-mounted domain controller, wherein the domain controller includes a system on chip (SoC) and a microcontroller unit (MCU), and the method is applied to the SoC, and the method includes: Receiving a domain controller upgrade request sent by an upgrade requester; Entering a programming session from a default session, and sending a pre-upgrade notification for the domain controller to the MCU, where the pre-upgrade notification is used to instruct the MCU to perform a pre-upgrade process; When the domain controller completes the upgrade, the default session is entered from the programming session, and an upgrade completion notification is sent to the MCU, where the upgrade completion notification is used to instruct the MCU to perform a recovery process.

[0014] Furthermore, the MCU is used to manage the power supply of the domain controller, and the SoC is electrically connected to the power supply; the method further includes: When it is determined that the MCU is to be restarted, a power supply maintaining signal is sent to the power supply so that the power supply maintains supplying power to the domain controller.

[0015] In the above implementation process, when the MCU is restarted, the SoC holds the power pin to keep it in the power supply state, thereby avoiding the situation where the domain controller loses power and connection due to the MCU entering the boot.

[0016] Furthermore, the SoC is deployed with a unified diagnostic service UDS, and the pre-upgrade notification and the upgrade completion notification are sent based on a protocol provided by the UDS.

[0017] A third aspect of the embodiment of the present application provides a vehicle-mounted domain controller, including a system on chip SoC and a microcontroller unit MCU; wherein, The SoC is configured to receive a domain controller upgrade request sent by an upgrade requester, enter a programming session from a default session, and send a pre-upgrade notification to the MCU; when the domain controller is upgraded, enter the default session from the programming session and send an upgrade completion notification to the MCU; The MCU is used to execute a preset pre-upgrade process in a default session when receiving the pre-upgrade notification; and to execute a preset recovery process in the default session when receiving the upgrade completion notification.

[0018] A fourth aspect of an embodiment of the present application provides a vehicle, which is equipped with one or more vehicle-mounted domain controllers as described in the third aspect.

[0019] A fifth aspect of an embodiment of the present application provides a computer program product, wherein the computer program product includes a computer program, and when the computer program is executed by a processor, the method described in any one of the first aspect or the second aspect is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0021] Figure 1 A schematic diagram of a process for upgrading a vehicle domain controller provided in an embodiment of the present application; Figure 2A flowchart of another method for upgrading a vehicle-mounted domain controller provided in an embodiment of the present application; Figure 3 A schematic diagram of the structure of a vehicle-mounted domain controller provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0023] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0024] The vehicle-mounted domain controller is a heterogeneous platform, usually including SoC (System on Chip), MCU (Microcontroller Unit), and other modules in the domain. The other modules in the domain may include but are not limited to GNSS (Global Navigation Satellite System) modules, camera modules, radar modules, etc. Among them, SoC is a high-performance chip, and MCU uses a chip with a high functional safety level to handle tasks with high real-time requirements.

[0025] In the related technology, since the domain controller is a heterogeneous platform, its SoC chip completes the software upgrade at the APP layer, the MCU completes the software upgrade at the boot layer, and the ECU completes the software upgrade at the boot layer. This leads to the need to adopt different upgrade strategies for the ECU and the domain controller respectively in terms of the vehicle upgrade process. The ECU and the domain controller must be upgraded separately, and the software upgrades of the two cannot be performed at the same time. Therefore, the ECU and the domain controller are incompatible in software upgrade.

[0026] In order to solve this technical problem, the present application provides an upgrade method, a domain controller, a vehicle and a program product for a vehicle-mounted domain controller. When the upgrade requester initiates a domain controller upgrade request, the SoC in the domain controller responds to enter the programming session and informs the MCU through a pre-upgrade notification. In response to the pre-upgrade notification for the domain controller, the MCU remains in the default session to perform the pre-upgrade process, so that the domain controller is ready for pre-upgrade preparation. When the domain controller completes the upgrade, the SoC exits the programming session, and through the upgrade completion notification for the domain controller, the MCU performs the recovery process in the default session, so that the domain controller returns to the working state. In this way, from the perspective of the whole vehicle upgrade process, the upgrade requester initiates an upgrade request to the ECU and the domain controller respectively, and the SoC in the ECU and the domain controller enters the programming session in response to the upgrade request, and the MCU completes the pre-upgrade process of the domain controller in the default session, thereby aligning the working modes between the ECU and the domain controller. For the whole vehicle upgrade process, the domain controller enters the programming session in the pre-upgrade stage, but for the domain controller, the MCU performs the pre-upgrade stage preparations in the default session. Therefore, the whole vehicle upgrade process can adopt the same upgrade strategy, initiate upgrade requests to the ECU and domain controller at the same time, and the software upgrades of both can be carried out at the same time, achieving upgrade compatibility between the ECU and the domain controller.

[0027] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0028] It should be understood that the vehicle described in the embodiments of the present application may be a pure electric vehicle, or a hybrid vehicle, a gas-electric hybrid vehicle, a fuel cell vehicle, or a vehicle of other energy types with a motor, and the embodiments of the present application are not limited thereto. The types of vehicles in the embodiments of the present application may include sedans, off-road vehicles, trucks, buses, etc., and the embodiments of the present application are not limited thereto. The vehicles in the embodiments of the present application may be vehicles with automatic intelligent driving, manned vehicles, or manned vehicles with assisted intelligent driving functions, and the embodiments of the present application are not limited thereto.

[0029] Combine the following Figure 1-Figure 3 The present invention describes an upgrade method of a vehicle-mounted domain controller, a domain controller, a vehicle, and a program product according to an embodiment of the present invention. Figure 1A schematic flow chart of a method for upgrading a vehicle-mounted domain controller is shown, and the method is applied to the MCU of the domain controller. In the vehicle upgrade process, there may be one or more domain controllers to be upgraded. At this time, the MCU in each vehicle-mounted domain controller can complete the upgrade of the domain controller through the upgrade method provided by this application. The method includes steps 110 to 120.

[0030] Step 110: When receiving the pre-upgrade notification for the domain controller, execute a preset pre-upgrade process in a default session.

[0031] The pre-upgrade notification is sent by the SoC based on a domain controller upgrade request; and the domain controller upgrade request is sent by the upgrade requester to the SoC.

[0032] In the vehicle upgrade process, the upgrade requester will send a domain controller upgrade request to the SoC in the domain controller. The upgrade requester may include but is not limited to the diagnostic instrument connected to the vehicle, and the OTA master (master device), etc. Of course, while initiating the domain controller upgrade request, the upgrade requester can also initiate ECU upgrade requests to other ECUs of the vehicle at the same time. And the upgrade requester can initiate domain controller upgrade requests to one or more domain controllers at the same time.

[0033] In response to the domain controller upgrade request, the SoC in the domain controller sends a pre-upgrade notification to the MCU, which is used to indicate that the domain controller needs to perform pre-upgrade preparations. Therefore, the MCU responds to the pre-upgrade notification and remains in the default session to perform pre-upgrade processing for the domain controller. At this point, the domain controller enters the pre-upgrade phase.

[0034] In some embodiments, the pre-upgrade process may include one or more of shutting down the DTC (Diagnostic Trouble Code) storage service, shutting down the network management, silencing the domain controller bus, and maintaining the diagnostic route. The domain controller bus silencing includes silencing the CAN (Controller Area Network) and / or FlexRay bus to reduce the bus load.

[0035] Step 120: upon receiving the upgrade completion notification for the domain controller sent by the SoC, executing a preset recovery process in the default session.

[0036] After the MCU completes the pre-upgrade process in the default session, the domain controller can enter the upgrade phase and perform software upgrade. Specifically, the domain controller includes multiple modules such as SoC and MUC. The upgrade of the domain controller refers to the software upgrade of some or all modules in the domain controller.

[0037] After the domain controller completes the upgrade, the SoC will send an upgrade completion notification for the domain controller to the MCU. The upgrade completion notification is used to indicate that the domain controller needs to be restored to a working state. Therefore, the MCU responds to the upgrade completion notification and remains in the default session to perform the preset recovery process. At this point, the domain controller enters the post-upgrade stage. The recovery process is the reverse process of the pre-upgrade process. For example, if the pre-upgrade process includes turning off the DTC storage service, the recovery process includes turning on the DTC storage service. That is, the pre-upgrade process includes turning on the DTC storage service, turning on network management, and waking up the domain controller bus.

[0038] It can be seen that in the whole vehicle upgrade process, the SoC in the domain controller responds to the domain controller upgrade request, and the MCU does not respond to the domain controller upgrade request, but responds to the pre-upgrade notification sent by the SoC, and remains in the default session for pre-upgrade processing. When the SoC responds to the domain controller upgrade request and the MCU receives the pre-upgrade notification, the domain controller actually enters the pseudo-boot mode. The so-called pseudo-boot is not a real boot. For the whole vehicle upgrade process, since the domain controller has completed the pre-upgrade processing and given a corresponding response, it is believed that the domain controller has entered the programming session in the pre-upgrade stage. However, for the domain controller, the response is given at the APP layer, and the MCU performs the preparatory work in the pre-upgrade stage in the default session, that is, the pre-upgrade processing. Since the domain controller does not actually enter the boot mode, it is called pseudo-boot mode.

[0039] Exemplarily, when the MCU receives the pre-upgrade notification, it can determine whether the conditions for entering the pseudo-boot mode are met. If so, the domain controller enters the pseudo-boot mode, and the MCU remains in the default session for pre-upgrade processing. The conditions for entering the pseudo-boot mode may include any one of the following: 1) The domain controller receives a request to enter a programming session under physical addressing.

[0040] For example, the upgrade requester sends a domain controller upgrade request in the form of physical addressing, and the domain controller upgrade request is used to request the domain controller to enter a programming session.

[0041] 2) The domain controller receives a request to enter a programming session under functional addressing.

[0042] For example, the upgrade requester sends a domain controller upgrade request in the form of functional addressing, and the domain controller upgrade request is used to request the domain controller to enter a programming session.

[0043] 3) During a diagnostic flash process of a domain controller, a request to enter a programming session is received under functional addressing and / or a request to enter a programming session is received under physical addressing.

[0044] 4) In FOTA (Firmware Over-The-Air, over-the-air software upgrade of mobile terminals), the domain controller receives a request to enter a programming session sent by the OTA master under functional addressing.

[0045] The domain controller will remain in the pseudo-boot mode until the domain controller completes the upgrade. Exemplarily, when the MCU receives the upgrade completion notification, it can determine whether the conditions for exiting the pseudo-boot mode are met. If so, the domain controller exits the pseudo-boot mode, and the MCU remains in the default session for recovery processing. The conditions for exiting the pseudo-boot mode may include any of the following: 1) The domain controller receives a request to enter a programming session under physical addressing, but the hold time of the session hold service is less than a preset time threshold.

[0046] The time threshold is, for example, 30 seconds. When this condition is met, the domain controller exits the pseudo boot mode, and the SoC returns from the programming session to the default session.

[0047] 2) After receiving a request to enter a programming session under physical addressing, the domain controller receives a request to switch to a default session or an extended session.

[0048] When the condition is met, the domain controller exits the pseudo boot mode, and the SoC switches from the programming session to the corresponding session according to the request to switch to the default session or the extended session.

[0049] 3) The domain controller receives a reset request under physical addressing or functional addressing and restarts.

[0050] When this condition is met, the domain controller exits the pseudo-boot mode after restarting.

[0051] At this point, the upgrade process of the domain controller is completed from the perspective of the MCU.

[0052] also, Figure 2 A schematic flow diagram of a method for upgrading a vehicle-mounted domain controller is also shown, and the method is applied to a SoC of a domain controller. In the vehicle upgrade process, there may be one or more domain controllers to be upgraded. At this time, the SoC in each vehicle-mounted domain controller can complete the upgrade of the domain controller through the upgrade method provided by this application. The method includes steps 210 to 230.

[0053] Step 210: Receive a domain controller upgrade request sent by an upgrade requester.

[0054] Step 220: Enter a programming session from a default session, and send a pre-upgrade notification for the domain controller to the MCU.

[0055] The pre-upgrade notification is used to instruct the MCU to perform a pre-upgrade process.

[0056] In response to the domain controller upgrade request, the SoC enters a programming session and simultaneously sends a pre-upgrade notification for the domain controller to the MCU.

[0057] Exemplarily, the pre-upgrade notification may carry the first session state information of the SoC. The first session state information is used to indicate that the SoC has entered a programming session. In this way, the MCU can learn from the pre-upgrade notification that the SoC has currently entered a programming session, thereby executing the pre-upgrade processing of the domain controller, and the domain controller enters a pseudo-boot mode.

[0058] In addition, as mentioned above, the domain controller includes multiple modules such as SoC, MCU, etc., and each module in the domain controller may need to be upgraded or may not need to be upgraded. Therefore, after the SoC enters the programming session, the software version of each module in the domain controller can be traversed to determine each module that needs to be upgraded.

[0059] Step 230: When the domain controller completes the upgrade, enter the default session from the programming session and send an upgrade completion notification to the MCU.

[0060] The upgrade completion notification is used to instruct the MCU to perform recovery processing.

[0061] When the domain controller completes the upgrade, the SoC exits the programming session and enters the default session, and sends an upgrade completion notification to the MCU.

[0062] Exemplarily, the upgrade completion notification may carry the second session state information of the SoC. The second session state information is used to indicate that the SoC has exited the programming session. In this way, the MCU can learn from the upgrade completion notification that the SoC has currently exited the programming session, thereby executing the recovery process of the domain controller, and the domain controller exits the pseudo boot mode.

[0063] At this point, the upgrade process of the domain controller is completed from the perspective of SoC.

[0064] It can be seen that in the upgrade method of a vehicle-mounted domain controller provided in the present application, from the perspective of the vehicle upgrade process, the SoC in the domain controller enters the programming session in response to the domain controller upgrade request, and the MCU completes the pre-upgrade processing of the domain controller in the default session, thereby aligning the working mode between the domain controller and other modules to be upgraded (such as ECU). For the vehicle upgrade process, the domain controller enters the programming session in the pre-upgrade stage, but for the domain controller, it is the MCU that performs the preparatory work in the pre-upgrade stage in the default session. Therefore, the vehicle upgrade process can adopt the same upgrade strategy, and at the same time initiate upgrade requests for other modules to be upgraded and the domain controller, and the software upgrades of the two can also be carried out at the same time, achieving upgrade compatibility between the two.

[0065] In some embodiments, the upgrade requester includes but is not limited to a vehicle diagnostic instrument or an OTA master device. The upgrade request method sends a domain controller upgrade request to the SoC through functional addressing and / or physical addressing.

[0066] It is understandable that functional addressing is a one-to-many addressing method, and physical addressing is a one-to-one addressing method. In some scenarios, the upgrade requester will first send a domain controller upgrade request to the domain controller through functional addressing, and then send the domain controller upgrade request to the domain controller again through physical addressing to ensure that the domain controller can respond to the upgrade.

[0067] It can be seen that in this embodiment, the upgrade requester completes the process of sending the domain controller upgrade request to the SoC of the domain controller by means of functional addressing and / or physical addressing.

[0068] In some embodiments, after the MCU completes the pre-upgrade process, the MCU further performs the following steps: Pre-upgrade readiness information is sent to the SoC, so that the SoC sends an upgrade response based on the domain controller upgrade request to the upgrade requester.

[0069] When the MCU completes the pre-upgrade processing, it means that the domain controller has completed the pre-upgrade preparations, so it can send pre-upgrade readiness information to the SoC. Subsequently, the SoC sends an upgrade response to the upgrade requester to notify the upgrade requester that the domain controller has completed the upgrade preparations. It can be seen that for the domain controller, the SoC gives an upgrade response in the APP layer. When all modules to be upgraded in the vehicle (domain controller, ECU, etc.) have completed the upgrade preparations and aligned the working mode, they can enter the next upgrade stage for flashing and upgrading.

[0070] In this embodiment, the upgrade readiness information is fed back to the SoC through the MCU, so that the SoC feeds back the upgrade response to the upgrade requester at the APP layer, thereby aligning the working modes between the domain controller and the ECU and achieving upgrade compatibility between the two.

[0071] In some embodiments, the SoC is deployed with UDS (Unified Diagnostic Services), based on which the pre-upgrade notification and upgrade completion notification sent by the SoC to the MCU are sent based on the protocol provided by the UDS.

[0072] For example, the protocol provided by UDS does not use programming session commands, but instead uses process control commands to complete the sending of pre-upgrade notifications and upgrade completion notifications.

[0073] In addition, in some embodiments, if the MCU has software to be upgraded installed, the MCU further performs the following steps: In case of receiving the MCU upgrade request sent by the SoC, the programming session is entered from the default session to perform software upgrade processing, and after the upgrade, the default session is entered from the programming session.

[0074] For example, after entering the programming session, the SoC can determine the module to be upgraded in the domain controller. If the MCU has software to be upgraded installed, the SoC will upgrade and flash the MCU during the domain controller upgrade process.

[0075] Specifically, the SoC can send an MCU upgrade request to the MCU, and the MCU upgrade request is used to guide the MCU into a programming session. The MCU upgrade request can be sent based on the protocol provided by the UDS. At this time, the MCU enters the boot layer. When the MCU receives the MCU upgrade request, its external refresh request flag will be set to valid, and it will enter the programming session for software upgrade processing. At the same time, after the upgrade is completed, the programming session is exited and the default session is returned. At this time, the MCU exits the boot layer.

[0076] After the MCU returns to the default session, the SoC remains in the programming session and the domain controller continues to remain in pseudo-boot until the domain controller completes the upgrade.

[0077] It can be seen that when the MCU needs to be upgraded, the SoC guides the MCU to complete the upgrade process through the method provided in this embodiment. That is, the MCU no longer responds to the request to enter the programming session in the vehicle upgrade process (i.e., the domain controller upgrade request), and only responds to the request to enter the programming session sent by the SoC (i.e., the MCU upgrade request described in this embodiment).

[0078] In addition, in some embodiments, the MCU is used to manage the power supply of the domain controller, that is, the MCU manages the power supply to the domain controller. At the same time, the SoC is electrically connected to the power supply. During the process of the SoC upgrading the MCU, or after the upgrade, the MCU may restart. When the MCU restarts, the power management fails because the MCU is powered off, which in turn causes the power supply to stop supplying power to the domain controller, and the domain controller is powered off and loses connection with the upgrade requester. For this reason, in this embodiment, the SoC also performs the following steps: When it is determined that the MCU is to be restarted, a power supply maintaining signal is sent to the power supply so that the power supply maintains supplying power to the domain controller.

[0079] When the SoC guides the MCU to perform a software upgrade, if it is determined that the MCU needs to be restarted, a power maintenance signal is sent to the power supply of the domain controller. For example, the SoC can send a GPIO (General-purpose input / output) signal to the PIN pin of the power supply to keep the power supply in a powered state.

[0080] It can be seen that in this embodiment, when the MCU is restarted, the SoC holds the power pin to keep the device in a power supply state, thereby avoiding the situation where the domain controller loses power and connection due to the MCU entering boot.

[0081] In any of the above embodiments, or the solutions obtained by their combination, a pseudo-boot mode that complies with the vehicle upgrade process and adapts to the actual situation of the domain controller is proposed. The domain controller does not need to be restarted when entering the pseudo-boot mode, thereby reducing the risk of the domain controller losing connection. At the same time, the upgrade and flashing of each module in the domain controller is completed in the pseudo-boot mode of the domain controller, ensuring the stability of the SoC. And by pulling the power pin through the SoC, the domain controller is prevented from being powered off and disconnected after the MCU enters the boot.

[0082] Based on any of the above embodiments, the present application also provides Figure 3 A vehicle-mounted domain controller 300 is shown. The domain controller 300 includes a SoC 310 and an MCU 320. Of course, it may also include functional modules required by other services.

[0083] The SoC 310 is configured to receive a domain controller upgrade request sent by an upgrade requester, enter a programming session from a default session, and send a pre-upgrade notification to the MCU 320; when the domain controller is upgraded, enter the default session from the programming session and send an upgrade completion notification to the MCU 320; The MCU 320 is configured to execute a preset pre-upgrade process in a default session when receiving the pre-upgrade notification; and execute a preset recovery process in the default session when receiving the upgrade completion notification.

[0084] In some embodiments, the domain controller upgrade request is sent by the upgrade requester to the SoC through functional addressing and / or physical addressing.

[0085] In some embodiments, the MCU 320 is further configured to: The pre-upgrade ready information is sent to the SoC 310, so that the SoC 310 sends an upgrade response based on the domain controller upgrade request to the upgrade requester.

[0086] In some embodiments, the pre-upgrade process includes one or more of shutting down the diagnostic trouble code storage service, shutting down the network management, silencing the domain controller bus, and maintaining the diagnostic routing; and the recovery process is the reverse process of the pre-upgrade process.

[0087] In some embodiments, the MCU 320 is further configured to: In case of receiving the MCU upgrade request sent by the SoC 310, the programming session is entered from the default session to perform software upgrade processing, and after the upgrade, the default session is entered from the programming session.

[0088] In some embodiments, the MCU 320 is used to manage the power supply of the domain controller 300, and the SoC 310 is electrically connected to the power supply; the SoC 310 is also used to: When it is determined that the MCU 320 is to be restarted, a power supply maintaining signal is sent to the power supply so that the power supply maintains supplying power to the domain controller 300 .

[0089] In some embodiments, the SoC 310 is deployed with a unified diagnostic service UDS, and the pre-upgrade notification and the upgrade completion notification are sent based on a protocol provided by the UDS.

[0090] The implementation process of the functions and effects of the above-mentioned modules is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.

[0091] Based on a vehicle domain controller described in any of the above embodiments, the present application also provides a vehicle, wherein the vehicle is equipped with one or more Figure 3 The vehicle-mounted domain controller shown. Of course, other hardware required for the business may also be included.

[0092] The method for upgrading a vehicle-mounted domain controller described in any of the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it may be implemented in whole or in part in the form of a computer program product.

[0093] Therefore, the present application also provides a computer program product, which includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the present application is performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, a core network device, an OAM or other programmable device.

[0094] The computer program or 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 program or instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; it may also be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0095] The present application also provides a computer storage medium, which stores a computer program. When the computer program is executed by a processor, it can be used to execute a method for upgrading a vehicle domain controller described in any of the above embodiments.

[0096] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0097] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0098] If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, and other media that can store program codes.

[0099] The above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0100] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0101] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

Claims

1. A method for upgrading a vehicle-mounted domain controller, characterized in that: The domain controller includes a system on chip (SoC) and a microcontroller unit (MCU). The method is applied to the MCU. The method includes: In the case of receiving a pre-upgrade notification for the domain controller, performing a preset pre-upgrade process in a default session; wherein the pre-upgrade notification is sent by the SoC based on a domain controller upgrade request; and the domain controller upgrade request is sent by an upgrade requester to the SoC; When receiving the upgrade completion notification for the domain controller sent by the SoC, a preset recovery process is performed in the default session.

2. The method according to claim 1, characterized in that The domain controller upgrade request is sent by the upgrade requester to the SoC through functional addressing and / or physical addressing.

3. The method according to claim 1 or 2, characterized in that: After completing the pre-upgrade process, the method further includes: Pre-upgrade readiness information is sent to the SoC, so that the SoC sends an upgrade response based on the domain controller upgrade request to the upgrade requester.

4. The method according to claim 1 or 2, characterized in that: The pre-upgrade process includes one or more of shutting down the diagnostic fault code storage service, shutting down the network management, silencing the domain controller bus, and maintaining the diagnostic route; the recovery process is the reverse process of the pre-upgrade process.

5. The method according to claim 1 or 2, characterized in that: The method further comprises: In case of receiving the MCU upgrade request sent by the SoC, the programming session is entered from the default session to perform software upgrade processing, and after the upgrade, the default session is entered from the programming session.

6. A method for upgrading a vehicle-mounted domain controller, characterized in that: The domain controller includes a system on chip (SoC) and a microcontroller unit (MCU). The method is applied to the SoC. The method includes: Receiving a domain controller upgrade request sent by an upgrade requester; Entering a programming session from a default session, and sending a pre-upgrade notification for the domain controller to the MCU, wherein the pre-upgrade notification is used to instruct the MCU to perform a pre-upgrade process; When the domain controller completes the upgrade, the default session is entered from the programming session, and an upgrade completion notification is sent to the MCU, where the upgrade completion notification is used to instruct the MCU to perform a recovery process.

7. The method according to claim 6, characterized in that The MCU is used to manage the power supply of the domain controller, and the SoC is electrically connected to the power supply; the method further includes: When it is determined that the MCU is to be restarted, a power supply maintaining signal is sent to the power supply so that the power supply maintains supplying power to the domain controller.

8. The method according to claim 6, characterized in that The SoC is deployed with a unified diagnostic service UDS, and the pre-upgrade notification and the upgrade completion notification are sent based on a protocol provided by the UDS.

9. A vehicle-mounted domain controller, characterized in that: It includes system on chip SoC and microcontroller unit MCU; among which, The SoC is configured to receive a domain controller upgrade request sent by an upgrade requester, enter a programming session from a default session, and send a pre-upgrade notification to the MCU; when the domain controller is upgraded, enter the default session from the programming session and send an upgrade completion notification to the MCU; The MCU is used to execute a preset pre-upgrade process in a default session when receiving the pre-upgrade notification; and to execute a preset recovery process in the default session when receiving the upgrade completion notification.

10. A vehicle, characterized in that: The vehicle is equipped with one or more vehicle-mounted domain controllers as claimed in claim 9.

11. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 or 6 to 8 is implemented.

Citation Information

Patent Citations

  • Vehicle-mounted entertainment system upgrading method and system, intelligent cabin and electronic equipment

    CN117111982A

  • Data transmission method and system of vehicle-mounted domain controller

    CN118041961A

  • Vehicle communication method and system, vehicle and computer readable storage medium

    CN118175215A