Method, system, medium, and vehicle for configuration information synchronization within a domain controller

Abstract

This invention discloses a method for synchronizing configuration information within a domain controller. Both the MPU and MCU ends of the domain controller include configuration information for four partitions (set1-set4). The MPU end is connected to a cloud platform. Synchronization is achieved by comparing the timestamps of the configuration information for the four partitions on the MPU and MCU ends; and by comparing the timestamps of the cloud platform end and the cloud-based big data configuration information within set4 of the MPU. This invention solves the problem of vehicle malfunction caused by untimely synchronization of configuration information within an automotive domain controller.

Description

Technical Field

[0001] This invention relates to the field of automotive technology, and more specifically to a method, system, medium, and vehicle for synchronizing configuration information within a domain controller. Background Technology

[0002] Currently, the electronic and electrical architecture of new energy vehicles is gradually shifting from distributed control architecture to integrated domain control, and more powerful domain controllers can effectively reduce the overall vehicle cost. Firstly, the MPU (Microprocessor Unit) within a multi-processor-based domain controller lacks flash storage for configuration information; the MPU's configuration information can only be stored in internal files. When this internal file configuration information is lost due to abnormal environments, file corruption, or configuration file updates, some normal vehicle functions will become unusable. Secondly, the MCU (Microprocessor Unit) cannot directly connect to the cloud platform, making it impossible to directly obtain configuration information such as large data CAN IDs and full CAN IDs.

[0003] Chinese patent CN113890663A discloses a domain controller time synchronization management method, system, and vehicle, including the following steps: the MPU's time source includes NTP, GPS, and MCU; the MPU obtains and updates the time from at least one of NTP, GPS, and MCU, and synchronizes the new time to the MCU; the MCU's time source includes the MPU and hardware RTC; the MCU obtains and updates the time from at least one of the MPU and hardware RTC, and synchronizes the new time to the MPU and ECU; the ECU's time source includes the MCU; the ECU obtains and updates the time from the MCU. This invention solves the problem of time inconsistency between functional domains caused by long-term operation of existing domain controllers, when there is no network signal in the external environment, and when some functional domains restart due to power failure. The time synchronization between the MPU and MCU is based on priority, which differs from this application. Summary of the Invention

[0004] This invention provides a method, system, medium, and vehicle for synchronizing configuration information within a domain controller, so as to achieve synchronized updates of configuration information (TBOX TUID, certificate information, VIN, APN, big data information, etc.) between MCU (microcontroller unit) and MPU (microprocessor unit).

[0005] The technical solution of the present invention is as follows:

[0006] The first aspect of the present invention proposes a method for synchronizing configuration information within a domain controller. Both the MPU and MCU ends of the domain controller include configuration information for four partitions (set1-set4). The MPU end is connected to a cloud platform. Synchronization is achieved by comparing the timestamps of the configuration information of the four partitions on the MPU end and the MCU end; synchronization is also achieved by comparing the timestamps of the cloud platform end and the cloud-based big data configuration information within set4 of the MPU.

[0007] Furthermore, set1 contains configuration information such as device TUID; set2 contains certificate information, including root certificate, terminal certificate, terminal certificate key, OTA certificate, and other configuration information; set3 mainly contains configuration information such as vehicle VIN, TSP URL, SK, and PIN; set4 mainly contains APN information, including APN1, APN2, and other configuration information; and the cloud platform big data includes configuration information such as diagnostic CAN ID and full CAN ID.

[0008] Furthermore, the configuration information of the four partitions on the MPU and MCU sides is bidirectionally synchronized.

[0009] Furthermore, the configuration information between the MPU and the cloud platform mainly refers to the synchronization of cloud-based big data configuration information within set4. This is a one-way synchronization, from the cloud platform to the MPU.

[0010] Furthermore, the specific steps include:

[0011] Step 1: Before the vehicle goes into sleep mode, the MPU and MCU send their respective configuration times to each other via the VIC protocol, and determine whether synchronization is needed by comparing the timestamp sizes.

[0012] After receiving the SET1-SET4 configuration timestamps from the MPU, the MCU first compares them with the local system time. If the timestamp is greater than the system time, it is considered abnormal and no synchronization is performed. If the timestamp is less than the system time, it compares them with the local SET1-SET4 configuration timestamps on the MCU. If any partition configuration timestamp in the MPU's SET1-SET4 is less than the partition configuration timestamp in the MCU's local SET1-SET4, then the corresponding partition configuration will be marked as needing to be synchronized to the MPU.

[0013] After receiving the SET1-SET4 configuration timestamps from the MCU, the MPU compares them with the SET1-SET4 configuration timestamps on the MPU side. If any of the partition configuration timestamps in the SET1-SET4 on the MCU side are less than those in the SET1-SET4 on the MPU side, then the corresponding partition configuration will be marked as needing to be synchronized to the MCU side.

[0014] Step 2: Determine whether the MPU and MCU sides have any flags that need to be synchronized to each other. If so, synchronize the configuration of the corresponding partition to the other side; otherwise, wait for the synchronization message from the other side.

[0015] Step 3: When the vehicle is powered on and woken up, the MPU sends a request with a configuration timestamp to the cloud platform via the HTTP protocol. After receiving the request with a timestamp from the MPU, the cloud platform compares the timestamp sent by the MPU with the configuration time mounted on the cloud platform. If the configuration timestamp of the MPU is less than the configuration time of the cloud platform, the cloud platform will synchronize the configuration information to the MPU.

[0016] A second aspect of the present invention provides a system for synchronizing configuration information within a domain controller, comprising a memory and a controller, wherein the memory stores a computer-readable program that, when invoked by the controller, can execute the steps of the method for synchronizing configuration information within a domain controller as described above.

[0017] A third aspect of the invention provides a computer-readable medium storing a configuration information synchronization program within a domain controller, which, when executed by at least one processor, causes the at least one processor to perform the method steps of the first aspect.

[0018] A fourth aspect of the invention provides a vehicle employing a system for synchronizing configuration information within a domain controller as described in the second aspect.

[0019] The advantages of this invention include at least the following:

[0020] When the internal file storing configuration information in the MPU becomes corrupted or its contents are lost, the configuration information stored in the MCU's flash memory will be synchronized to the MPU via the VIC protocol after waking from sleep. When the cloud platform updates big data configuration information, the MPU (microprocessor unit) that interacts directly with the cloud platform will synchronize the updated configuration information to its internal storage file and then synchronize it to the MCU via the VIC protocol after waking from sleep, ensuring the normal operation of the vehicle domain controller system. Attached Figure Description

[0021] Figure 1 This is a schematic diagram illustrating the synchronization of configuration information within the domain controller of the present invention;

[0022] Figure 2 A flowchart illustrating the process of synchronizing configuration information from the MCU to the MPU.

[0023] Figure 3 A flowchart illustrating the process of synchronizing configuration information from the MPU to the MCU.

[0024] Figure 4 This is a flowchart illustrating the process of synchronizing cloud-based big data configuration information within set4 of the MPU on the cloud platform. Detailed Implementation

[0025] MCU stands for Microcontroller Unit, also known as a single-chip microcomputer or microcontroller. It is a chip-level computer that integrates a central processing unit with a reduced frequency and specifications, and peripheral interfaces such as memory, counter, USB, A / D conversion, UART, PLC, DMA, and even LCD driver circuits onto a single chip. It can be used to perform different combinations of control for different applications. Therefore, MCU chip is a microcontroller chip.

[0026] MPU, or microprocessor, is essentially the central processing unit (CPU) of a microcomputer. To support the powerful computing capabilities of an MPU and ensure its efficient use, it's essential to run complex, computationally intensive programs and tasks. This typically requires a large capacity of memory. However, large-capacity memory is difficult to integrate into the logic-centric MPU; therefore, MPUs usually require external, large-capacity memory, primarily DDR memory and FLASH. To support complex operating systems and large programs, the MPU often also integrates a high-performance memory controller, memory management unit (MMU), and other complex storage mechanisms and hardware.

[0027] Therefore, from a structural perspective, MPUs, which need to run complex and demanding programs, generally require external memory to operate. MCUs, on the other hand, often only perform stimulus-response process control and auxiliary functions, with relatively simple functions, requiring only a small on-chip memory. This is an important superficial difference between MPUs and MCUs, but not the core reason.

[0028] It is clear that the difference between MPUs and MCUs stems from their different application focuses; they are two types of devices optimized in different ways to meet different application scenarios. MPUs emphasize powerful computing capabilities to execute complex and diverse large programs, typically requiring large external memory. MCUs, on the other hand, usually run simpler tasks, performing management / control functions for hardware devices. They generally do not require strong computing / processing capabilities and therefore do not need large memory to support running large programs. They are typically integrated on a single chip to achieve system "monolithization."

[0029] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0030] like Figure 1 As shown in Embodiment 1, a method for synchronizing configuration information within a domain controller is disclosed. Both the MPU and MCU ends of the domain controller include configuration information for four partitions, set1-set4. The MPU end is connected to a cloud platform. Synchronization is achieved by comparing the timestamps of the configuration information of the four partitions on the MPU end and the MCU end; synchronization is also achieved by comparing the timestamps of the cloud platform end and the cloud-based big data configuration information in set4 of the MPU.

[0031] Furthermore, set1 contains configuration information such as device TUID; set2 contains certificate information, including root certificate, terminal certificate, terminal certificate key, OTA certificate, and other configuration information; set3 mainly contains configuration information such as vehicle VIN, TSP URL, SK, and PIN; set4 mainly contains APN information, including APN1, APN2, and other configuration information; and the cloud platform big data includes configuration information such as diagnostic CAN ID and full CAN ID.

[0032] Furthermore, the configuration information of the four partitions on the MPU and MCU sides is bidirectionally synchronized.

[0033] Furthermore, the configuration information between the MPU and the cloud platform mainly refers to the synchronization of cloud-based big data configuration information within set4. This is a one-way synchronization, from the cloud platform to the MPU.

[0034] Furthermore, such as Figure 2 , Figure 3 , Figure 4 As shown, a method for synchronizing configuration information within a domain controller specifically includes the following steps:

[0035] Step 1: Before the vehicle goes into sleep mode, the MPU and MCU send their respective configuration times to each other via the VIC protocol, and determine whether synchronization is needed by comparing the timestamp sizes.

[0036] After receiving the SET1-SET4 configuration timestamps from the MPU, the MCU first compares them with the local system time. If the timestamp is greater than the system time, it is considered abnormal and no synchronization is performed. If the timestamp is less than the system time, it compares them with the local SET1-SET4 configuration timestamps on the MCU. If any partition configuration timestamp in the MPU's SET1-SET4 is less than the partition configuration timestamp in the MCU's local SET1-SET4, then the corresponding partition configuration will be marked as needing to be synchronized to the MPU.

[0037] After receiving the SET1-SET4 configuration timestamps from the MCU, the MPU compares them with the SET1-SET4 configuration timestamps on the MPU side. If any of the partition configuration timestamps in the SET1-SET4 on the MCU side are less than those in the SET1-SET4 on the MPU side, then the corresponding partition configuration will be marked as needing to be synchronized to the MCU side.

[0038] Step 2: Determine whether the MPU and MCU sides have any flags that need to be synchronized to each other. If so, synchronize the configuration of the corresponding partition to the other side; otherwise, wait for the synchronization message from the other side.

[0039] Step 3: When the vehicle is powered on and woken up, the MPU sends a request with a configuration timestamp to the cloud platform via the HTTP protocol. After receiving the request with a timestamp from the MPU, the cloud platform compares the timestamp sent by the MPU with the configuration time mounted on the cloud platform. If the configuration timestamp of the MPU is less than the configuration time of the cloud platform, the cloud platform will synchronize the configuration information to the MPU.

[0040] Example 2 is a system for synchronizing configuration information within a domain controller, including a memory and a controller. The memory stores a computer-readable program, which, when invoked by the controller, can execute the steps of the method for synchronizing configuration information within a domain controller as described in Example 1.

[0041] Embodiment 3: A computer-readable medium storing a configuration information synchronization program within a domain controller. When the configuration information synchronization program within the domain controller is executed by at least one processor, the at least one processor performs the method steps as described in Embodiment 1.

[0042] Example 4 is a vehicle that uses a system for synchronizing configuration information within the domain controller as described in Example 2.

Claims

1. A method for configuration information synchronization in a domain controller, wherein the MPU side and the MCU side each include configuration information of four partitions of set1-set4, and the MPU side is connected with a cloud platform side, characterized in that, Synchronization is achieved by comparing the timestamps of the configuration information of the four partitions on the MPU and MCU sides; synchronization is also achieved by comparing the timestamps of the cloud big data configuration information in set4 of the cloud platform and the MPU. Specifically, the following steps are included: Step 1: Before the vehicle goes into sleep mode, the MPU and MCU send their respective configuration times to each other via the VIC protocol, and determine whether synchronization is needed by comparing the timestamp sizes; Step 2: Determine whether the MPU and MCU sides have a flag that needs to be synchronized to each other. If so, synchronize the configuration of the corresponding partition to the other side. If not, wait for the synchronization message from the other side. Step 3: When the vehicle is powered on and woken up, the MPU sends a request with a configuration timestamp to the cloud platform via the HTTP protocol. After receiving the request with a timestamp from the MPU, the cloud platform compares the timestamp sent by the MPU with the configuration time mounted on the cloud platform. If the configuration timestamp of the MPU is less than the configuration time of the cloud platform, the cloud platform will synchronize the configuration information to the MPU.

2. The method of configuration information synchronization according to claim 1, wherein, Set1 contains device TUID configuration information; set2 contains certificate information, including root certificate, terminal certificate, terminal certificate key, and OTA certificate configuration information; set3 contains vehicle VIN, TSP URL, SK, and PIN configuration information; set4 contains APN information, including APN1 and APN2 configuration information; and the cloud platform big data includes diagnostic CAN ID and full CAN ID configuration information.

3. The method for synchronizing configuration information as described in claim 1, characterized in that, The configuration information of the four partitions on the MPU and MCU sides is bidirectionally synchronized.

4. The method for synchronizing configuration information as described in claim 1, characterized in that, The configuration information between the MPU and the cloud platform is a one-way synchronization of the cloud big data configuration information within set4, from the cloud platform to the MPU.

5. The method for synchronizing configuration information as described in claim 1, characterized in that, Step 1 includes: After receiving the SET1-SET4 configuration timestamps from the MPU, the MCU first compares them with the local system time. If the timestamp is greater than the system time, it is considered abnormal and no synchronization is performed. If the timestamp is less than the system time, it is compared with the local SET1-SET4 configuration timestamps on the MCU. If any partition configuration timestamp in the MPU's SET1-SET4 is less than the partition configuration timestamp in the MCU's local SET1-SET4, the corresponding partition configuration is marked as needing to be synchronized to the MPU.

6. The method for synchronizing configuration information as described in claim 1, characterized in that, Step 1 includes: After receiving the SET1-SET4 configuration timestamps from the MCU, the MPU compares them with the SET1-SET4 configuration timestamps on the MPU. If any of the partition configuration timestamps in the SET1-SET4 on the MCU are less than the partition configuration timestamps in the SET1-SET4 on the MPU, the corresponding partition configuration is marked as needing to be synchronized to the MCU.

7. A system for synchronizing configuration information within a domain controller, comprising a memory and a controller, wherein the memory stores a computer-readable program, which, when invoked by the controller, can perform the steps of the method for synchronizing configuration information within a domain controller as described in any one of claims 1-6.

8. A computer-readable medium, characterized in that, The computer-readable medium stores a configuration information synchronization program within a domain controller, which, when executed by at least one processor, causes the at least one processor to perform the steps of the method as described in any one of claims 1 to 6.

9. A vehicle, characterized in that, A system that synchronizes configuration information within a domain controller as described in claim 7.

Images