In-vehicle domain control computer systems, methods, systems, devices, products, and media

Abstract

The invention discloses a vehicle-mounted domain control computer system, method, system, device, product and medium, and relates to the technical field of vehicle-mounted computers.The vehicle-mounted domain control computer system comprises a management switching module, at least one function node and a management node, the function node is detachably connected with a corresponding interface of the management switching module, hardware does not need to be embedded, and the management switching module is connected with the management node. Hardware resources can be dynamically replaced along with software iteration, a controller of a management node accurately matches a first upgrade file version with current actual hardware configuration based on a real-time hardware connection state and then directionally transmits the first upgrade file version, so that the problem that pre-embedded hardware is idle due to architecture change or debugging failure is avoided, and the hardware upgrading efficiency is improved. The technical effects of improving the upgrading efficiency and the hardware resource utilization rate are achieved.

Description

Technical Field

[0001] The present application relates to the field of vehicle-mounted computer technology, and in particular to vehicle-mounted domain control computer systems, methods, systems, devices, products and media. Background Art

[0002] As automotive electrical and electronic architecture evolves from distributed to centralized, onboard domain control computers (DCs) integrate traditionally decentralized ECU (Electronic Control Unit) functions, such as perception, decision-making, and execution control, significantly reducing system complexity and wiring costs, becoming the core vehicle for intelligent systems. However, this trend toward centralized hardware systems conflicts with the demand for rapid software iteration. Hardware design, commissioning, and manufacturing cycles typically span years, while software architecture and algorithm updates occur monthly. To address this discrepancy, a hardware pre-embedded strategy is employed. This involves pre-deploying redundant resources (such as redundant computing chips, additional sensor interfaces, and large-capacity storage) during the hardware design phase to reserve physical capacity for future software upgrades. However, during subsequent software upgrades, if software debugging fails to meet expectations, these pre-embedded resources cannot be effectively utilized. Furthermore, if system architecture upgrades lead to mismatches in hardware interfaces or computing architectures, the pre-embedded dedicated hardware will become completely incompatible at the physical layer. This ultimately leads to idle redundant hardware, increasing system cost, power consumption, and space usage.

[0003] Therefore, how to provide a solution to the above technical problems is a problem that those skilled in the art need to solve at present. Summary of the Invention

[0004] The present application provides a vehicle-mounted domain control computer system, method, system, device, product and medium to at least solve the problem of idle pre-embedded hardware caused by architecture changes or debugging failures in related technologies.

[0005] The present application provides an on-vehicle domain control computer system, comprising: a management switching module, including an on-vehicle Ethernet switch and an on-vehicle Ethernet management bus, the on-vehicle Ethernet switch including multiple interfaces; at least one functional node, detachably connected to a corresponding interface of the on-vehicle Ethernet switch; a management node, connected to a corresponding interface of the on-vehicle Ethernet switch, comprising a controller and a first memory, the controller being configured to receive a first upgrade file version through an external communication node, write the first upgrade file version into the first memory, and when a preset trigger condition is met, obtain current hardware connection information of the on-vehicle Ethernet switch based on the on-vehicle Ethernet management bus, and control the on-vehicle Ethernet switch to transmit the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node through the on-vehicle Ethernet management bus.

[0006] The present application also provides an upgrade method, which is applied to the controller of the vehicle-mounted domain control computer system as described above, and the upgrade method includes: receiving a first upgrade file version through an external communication node; writing the first upgrade file version into the first memory of the management node of the vehicle-mounted domain control computer system; when a preset trigger condition is met, obtaining the current hardware connection information of the vehicle-mounted Ethernet switch of the vehicle-mounted domain control computer system based on the vehicle-mounted Ethernet management bus, and controlling the vehicle-mounted Ethernet switch to transmit the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node of the vehicle-mounted domain control computer system through the vehicle-mounted Ethernet management bus.

[0007] The present application also provides an upgrade system, which includes: a receiving module for receiving a first upgrade file version through an external communication node; a writing module for writing the first upgrade file version into a first memory in a management node of a vehicle-mounted domain control computer system; an upgrade module for obtaining the current hardware connection information of the vehicle-mounted Ethernet switch of the vehicle-mounted domain control computer system based on the vehicle-mounted Ethernet management bus when a preset trigger condition is met, and controlling the vehicle-mounted Ethernet switch to transmit the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node of the vehicle-mounted domain control computer system through the vehicle-mounted Ethernet management bus.

[0008] The present application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for implementing the steps of the above-mentioned upgrading method when executing the computer program.

[0009] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned upgrading method are implemented.

[0010] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned upgrading method when executed by a processor.

[0011] Through this application, since the functional nodes in the vehicle-mounted domain control computer system are detachably connected to the corresponding interfaces of the management switching module, there is no need for pre-embedded hardware, so that hardware resources can be dynamically replaced with software iterations. The controller of the management node accurately matches the first upgrade file version with the current actual hardware configuration based on the real-time hardware connection status and then transmits it in a targeted manner, thereby avoiding the problem of idle pre-embedded hardware caused by architecture changes or debugging failures, and achieving the technical effect of improving upgrade efficiency and hardware resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0013] Figure 1 A schematic structural diagram of the first vehicle-mounted domain control computer system provided in an embodiment of the present application.

[0014] Figure 2 A schematic structural diagram of the second vehicle-mounted domain control computer system provided in an embodiment of the present application.

[0015] Figure 3 A schematic structural diagram of the third vehicle-mounted domain control computer system provided in an embodiment of the present application.

[0016] Figure 4 A schematic structural diagram of the fourth vehicle-mounted domain control computer system provided in an embodiment of the present application.

[0017] Figure 5 A schematic structural diagram of the fifth vehicle-mounted domain control computer system provided in an embodiment of the present application.

[0018] Figure 6 A schematic diagram of powering on a vehicle-mounted domain control computer system provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0020] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0021] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0022] like Figure 1 The present application provides a vehicle-mounted domain control computer system, including: a management switching module, including a vehicle-mounted Ethernet switch 11 and a vehicle-mounted Ethernet management bus 12, the vehicle-mounted Ethernet switch 11 including multiple interfaces; at least one functional node 2, detachably connected to the corresponding interface of the vehicle-mounted Ethernet switch 11; a management node, connected to the corresponding interface of the vehicle-mounted Ethernet switch 11, including a controller 31 and a first memory 32, the controller 31 being configured to receive a first upgrade file version through an external communication node, and write the first upgrade file version into the first memory 32. When a preset trigger condition is met, the controller 31 obtains the current hardware connection information of the vehicle-mounted Ethernet switch 11 based on the vehicle-mounted Ethernet management bus 12, and controls the vehicle-mounted Ethernet switch 11 to transmit the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node through the vehicle-mounted Ethernet management bus 12.

[0023] In this embodiment, the management switching module includes an onboard Ethernet switch 11 and an onboard Ethernet management bus 12. The onboard Ethernet switch 11 is equipped with multiple interfaces for connecting and managing communications between multiple functional nodes 2 and supporting the management of hardware connection information. A functional node 2 is an independent functional unit within the onboard domain control computer system, including but not limited to a computing node, a storage node, and a sensing node. Each functional node 2 is connected to an interface on the onboard Ethernet switch 11 via an interface that corresponds one-to-one with the interface. It is understood that the interface between the functional node 2 and the onboard Ethernet switch 11 can be detachably connected, allowing the functional node 2 to be replaced or upgraded as needed without requiring large-scale changes to the entire system. This design improves the system's flexibility and scalability, enabling it to better adapt to future technological developments and changing user needs.

[0024] The management node is the core control unit in the vehicle domain control computer system, comprising a controller 31 and a first memory 32. The management node is responsible for receiving and storing upgrade files and, based on hardware connection information, controlling the vehicle Ethernet switch 11 to transmit the upgrade files to the target functional node via the vehicle Ethernet management bus 12. The contents of the first upgrade file version include, but are not limited to, updated software code and configuration information. The preset trigger conditions in this embodiment are conditions for initiating the upgrade process, including but not limited to the vehicle being parked, the system detecting a low voltage state, and manual user triggering. Hardware connection information includes, but is not limited to, hardware information about the functional node 2 to which the vehicle Ethernet switch 11 is currently connected, including but not limited to the type and IP (Internet Protocol) address of the functional node 2.

[0025] Specifically, the on-board Ethernet switch 11 receives the first upgrade file version through the external communication interface and stores it in the first memory 32 of the management node. As an optional embodiment, a preset verification algorithm can be used to perform integrity verification on the first upgrade file version. The preset verification algorithm includes but is not limited to a hash algorithm. The file version that passes the integrity verification is retained in the first memory 32, and the file version that fails the integrity verification is deleted from the first memory 32, thereby ensuring that the received upgrade file has not been tampered with or damaged, thereby improving the security and reliability of the system upgrade.

[0026] Waiting for the preset trigger conditions to be met, for example, when the vehicle is in a parked state or the system detects a low voltage state, the controller 31 determines the address of the target functional module based on the hardware information of the functional node 2 currently connected to the monitored on-board Ethernet switch 11. The controller 31 controls the on-board Ethernet switch 11 to transmit the upgrade file matching the current hardware to the first storage space of the target functional node according to the above address, ensuring that the upgrade file version matching the hardware configuration is selected during the upgrade process to avoid system failures caused by hardware incompatibility. After receiving the first upgrade file version, the target functional node executes the upgrade operation to complete the update.

[0027] This embodiment realizes the dynamic management of software upgrades by receiving and storing upgrade files and controlling the management switching module through the management node. Even if redundant resources are reserved during the hardware design phase, the management node can dynamically select the matching upgrade file version according to the current hardware configuration to ensure the effective matching of software upgrades and hardware resources, and avoid the failure of pre-buried resources due to mismatch of hardware interfaces or computing power architecture. At the same time, by dynamically matching the upgrade file version, the problem of idle redundant hardware caused by software debugging not meeting expectations or system architecture upgrades is reduced, and the system cost, power consumption and space occupancy are reduced. The user experience is improved by pre-set trigger conditions and an automated user-free upgrade process. At the same time, the dynamic matching mechanism of the upgrade file can improve the efficiency and accuracy of the upgrade process and reduce user waiting time.

[0028] In an exemplary embodiment, the controller 31 is further configured to maintain a mapping table between the hardware identification information of each functional node 2 and its compatible file version range, obtain the hardware identification information of the target functional node based on the on-board Ethernet management bus 12, query the mapping table, and verify whether the first upgrade file version is within the file version range corresponding to the hardware identification information. If so, it is determined that the first upgrade file version matches the current hardware configuration.

[0029] The hardware identification information of each functional node 2 is unique, including but not limited to the hardware version number, chip model, interface type, and IP address of the functional node 2. This information is used to distinguish functional nodes 2 with different hardware configurations. The firmware version range corresponding to each piece of hardware identification information indicates the firmware version range that the hardware can support. For example, hardware version H2.0 is compatible with firmware versions F2.0 to F2.2.

[0030] In this embodiment, the controller 31 is also used to maintain a mapping table. The mapping table is a data structure that stores the mapping relationship between the hardware identification information of the functional node 2 and its compatible file version range. For example, hardware version H1.0 is compatible with firmware versions F1.0 to F1.1, and hardware version H2.0 is compatible with firmware versions F2.0 to F2.2. After obtaining the target functional node corresponding to the first upgrade file version, the hardware identification information of the target functional node is first obtained, and the mapping table is queried to verify whether the first upgrade file version is within the file version range corresponding to the hardware identification information. If so, it is determined that the first upgrade file version matches the current hardware configuration. When the subsequent preset trigger condition is met, the first upgrade file version can be written to the first storage space of the corresponding target functional node.

[0031] For example, assume that there are two functional nodes 2 in the vehicle domain control computer system, namely a computing node and a perception node. The hardware identification information of the computing node is hardware version H2.0, the IP address is 192.168.1.100, and the compatible file version range is firmware version F2.0 to F2.2; the hardware identification information of the perception node is hardware version H1.0, the IP address is 192.168.1.101, and the compatible file version range is firmware version F1.0 to F1.1.

[0032] The management node receives the first upgrade file version F2.1 via an external communication interface, stores the received upgrade file version F2.1 in first memory 32, and performs an integrity check on upgrade file version F2.1 using a hash algorithm. If the check succeeds, the file version is retained in first memory 32; if the check fails, the file version is deleted from first memory 32. The management node obtains the hardware identification information of the target functional node (e.g., a computing node) corresponding to the first upgrade file version F2.1, queries a mapping table, and finds hardware version H2.0 and IP address 192.168.1.100. The compatible file version range corresponding to hardware version H2.0 is F2.0 to F2.2, and F2.1 falls within the compatible range. The management node determines that the first upgrade file version F2.1 matches the current hardware configuration, and transmits the matching upgrade file version F2.1 to the first storage space of the computing node at IP address 192.168.1.100.

[0033] By maintaining the mapping table and verifying the upgrade file version, this embodiment can ensure that only the firmware version that is compatible with the hardware configuration will be installed on the target functional node by the management node, avoiding system failures caused by hardware incompatibility, reducing the problem of redundant hardware idleness caused by software debugging not meeting expectations or system architecture upgrades, and reducing system costs, power consumption and space occupancy.

[0034] In an exemplary embodiment, the preset trigger condition includes a preset upgrade time period; the controller 31 is specifically configured to determine whether the total upgrade duration of each first upgrade file version stored in the first memory 32 is greater than the duration of the preset upgrade time period, and if so, determine the upgrade priority of the functional node 2 corresponding to each first upgrade file version. When the preset trigger condition is met, the on-board Ethernet switch 11 is controlled to transmit the first upgrade file version matching the current hardware configuration in a descending order of upgrade priority to the first storage space of the target functional node in sequence through the on-board Ethernet management bus 12.

[0035] In this embodiment, the preset trigger condition includes a preset upgrade time period, such as 2 am to 4 am. Taking into account that before the preset trigger condition is met, there may be multiple functional nodes 2 that need to be upgraded stored in the first memory 32. Therefore, this embodiment first obtains the total time required for the functional nodes 2 that need to be upgraded to complete the upgrade, that is, the total upgrade duration. In this embodiment, an upgrade priority is also set in advance for each functional node 2. Specifically, the corresponding upgrade priority can be set according to the importance or urgency of the functional node 2. The functional node 2 with a high priority will be upgraded before the functional node 2 with a low priority. If the total upgrade duration is longer than the duration of the preset upgrade time period, this upgrade will trigger the upgrade of each functional node 2 in order from high to low upgrade priority. The functional node 2 whose upgrade time exceeds the preset upgrade time period will not perform the upgrade operation in this upgrade, and will wait until the next time the preset trigger condition is met.

[0036] For example, assume that the vehicle domain control computer system has three functional nodes 2: a compute node, a sensor node, and a storage node. The compute node upgrade takes one hour and has a high priority. The sensor node upgrade takes one hour and has a medium priority. The storage node upgrade takes one hour and has a low priority. The preset upgrade time period is from 2:00 AM to 4:00 AM, with a total duration of two hours. The total upgrade time for all functional nodes 2 is three hours, which is longer than the preset upgrade time period.

[0037] The management node receives the first upgrade file version from each functional node 2 via the external communication interface and stores it in the first memory 32. When a preset trigger condition is met (e.g., between 2:00 AM and 4:00 AM), the management node begins the upgrade process, first upgrading the compute nodes and then the sensor nodes. At this point, the preset upgrade window has expired (4:00 AM), and the upgrade of the storage nodes (lower priority) has not been completed. The management node records the incomplete functional nodes 2 (storage nodes) and their corresponding upgrade file versions, and waits for the next preset upgrade window (2:00 AM to 4:00 AM) to complete the remaining upgrade tasks.

[0038] This embodiment optimizes upgrade time management by presetting upgrade time periods and prioritizing upgrades, ensuring that key functional nodes 2 are upgraded first, improving system reliability and user experience. Furthermore, the system can flexibly handle unfinished upgrade tasks, ensuring that all functional nodes 2 are ultimately upgraded, enhancing the system's adaptability and flexibility.

[0039] Please refer to Figure 2 Based on the above embodiment, the vehicle-mounted domain control computer system further includes: The backup module is configured to store a backup running file version of at least one functional node 2, where the backup running file version is a file version during which the functional node 2 stably runs for a first preset time period.

[0040] The controller 31 is further configured to, when detecting a function node 2 that has failed to be upgraded and a preset trigger condition is met, control the function node 2 that has failed to be upgraded to run according to the corresponding backup running file version in the backup module.

[0041] In this embodiment, a backup running version refers to a file version that enables functional node 2 to operate stably for a certain period of time (a first preset period of time). This version is considered reliable and can be used as a recovery point. The backup module is used to store the backup running file version of at least one functional node 2, ensuring that in the event of an upgrade failure or failure, the system can roll back to a known stable running file version. For example, if a functional node 2 has run continuously for seven days without experiencing any failures under a certain file version, this file version is considered stable and can be determined as the backup running version.

[0042] In this embodiment, by storing the backup running file version of functional node 2, a quick rollback to a known stable version can be achieved during the upgrade process or in the event of a failure. This reduces the risk of system unavailability caused by the upgrade, shortens system downtime, and improves system reliability. Furthermore, users do not need to worry about system failures that may occur during the upgrade process; the system automatically rolls back to a stable version. This automated rollback mechanism reduces user intervention and improves the user experience.

[0043] In an exemplary embodiment, the functional node 2 includes a first-class functional node 2, the backup module includes a second storage space provided in the first-class functional node 2, and the second storage space is configured to store the backup operation file version of the first-class functional node 2 to which it belongs; the controller 31 is specifically configured to switch the first-class functional node 2 to the second storage space for operation when it detects that the upgrade of the first-class functional node 2 fails.

[0044] In this embodiment, the first-type functional node 2 includes two storage spaces, one of which is used to store backup versions of running files. If an upgrade of the first-type functional node 2 fails, the controller 31 can immediately switch the node to the second storage space for operation, quickly restoring the node to a stable state. This embodiment reduces system downtime caused by upgrade failures and improves overall system reliability.

[0045] In an exemplary embodiment, the backup module includes a second memory provided in the management node, and the controller 31 is further configured to receive the backup running file version through the external communication node and write the backup running file version into the second memory. When a functional node 2 that fails to upgrade is detected, when a preset trigger condition is met, the current hardware connection information of the on-board Ethernet switch 11 is obtained based on the on-board Ethernet management bus 12, and the on-board Ethernet switch 11 is controlled to transmit the corresponding backup running file version to the first storage space of the functional node 2 that fails to upgrade through the on-board Ethernet management bus 12.

[0046] In this embodiment, the management node is also provided with a second memory, which is used to store the backup operation data of several key functional nodes 2, as well as the backup operation data of functional nodes 2 that do not have a second storage space, further enhancing the reliability and fault tolerance of the system. When it is detected that the upgrade of the functional node 2 fails, the management node can quickly and directedly transfer the backup operation file version to the first storage space of the functional node 2 that failed to upgrade when the preset trigger conditions are met, thereby achieving rapid recovery. This centralized backup solution not only provides reliable backup support for the functional nodes 2 that do not have redundant storage capabilities, but also simplifies the overall architecture of the system and reduces the complexity of backup management by centrally managing backup files. At the same time, even if an unexpected situation occurs during the upgrade process, the solution of this embodiment can quickly restore to a stable operating state, reducing the system downtime caused by the upgrade failure, ensuring the continuity and stability of the vehicle's key functions, and further improving the user experience and the overall performance of the system.

[0047] In an exemplary embodiment, the controller 31 is also configured to mark the backup running version corresponding to the target functional node as a cleanable state in the second memory if it is detected that the target functional node has been successfully upgraded and has been running stably for more than a second preset time period. When the occupancy rate of the second memory exceeds a preset threshold, the backup running version marked as a cleanable state is cleaned according to the version sequence.

[0048] In this embodiment, after detecting that the target functional node has been successfully upgraded and has been running stably for more than a second preset time period, the controller 31 marks the corresponding backup running version in the second memory as being in a cleanable state, and when the occupancy rate of the second storage space exceeds a preset threshold, the controller 31 cleans up these backup running versions marked as being in a cleanable state in version sequence. This mechanism effectively optimizes the management of backup storage space and ensures the efficient use of storage resources. By retaining only the necessary backup versions, the system can avoid the problem of insufficient storage space caused by too many backup files, thereby reducing storage costs and improving the operating efficiency of the system. At the same time, this on-demand cleaning method also ensures that a stable version can be quickly restored when needed, taking into account the reliability and resource utilization efficiency of the system, and further improving the overall performance and user experience of the vehicle-mounted domain control computer system.

[0049] In an exemplary embodiment, the functional node 2 also includes an interface conversion module, the first end of the interface conversion module is connected to the upgrade interface of the functional node 2 to which it belongs, and the second end of the interface conversion module is connected to the first storage space in the functional node 2 to which it belongs. The interface conversion module is configured to convert the original data received by its first end into target data adapted to the first storage space connected to its second end.

[0050] In this embodiment, considering that the vehicle-mounted domain control computer system includes functional modules with different architectures and differs in their management interfaces (including debugging interfaces, firmware upgrade interfaces, etc.), this embodiment introduces an interface conversion module to uniformly convert the management interfaces of these functional modules into an in-vehicle Ethernet interface. This effectively resolves the management interface incompatibility issue caused by differences in the functional module architectures within the vehicle-mounted domain control computer system. The interface conversion module includes, but is not limited to, a functional safety MCU (Microcontroller Unit). This interface standardization enables the system to centrally manage each functional module through a unified Ethernet switch, greatly simplifying the overall system architecture and management complexity. Furthermore, the interface conversion module converts raw data into target data adapted for the first storage space, ensuring accurate and efficient data transmission and improving system compatibility and reliability. Furthermore, it facilitates remote management and upgrades of the system via OTA (Over-The-Air) technology, further enhancing the system's intelligence and user experience. The use of the interface conversion module not only reduces the difficulty and cost of system integration but also provides greater flexibility for future expansion and upgrades of functional modules, enhancing the scalability and adaptability of the vehicle-mounted domain control computer system, enabling it to better meet the evolving needs of in-vehicle electronic systems.

[0051] In an exemplary embodiment, the management switching module also includes a management interface, and the external communication node is connected to the management interface. The on-board Ethernet switch 11 is also configured to receive the second upgrade file version through the external communication node and transmit the second upgrade file version to the storage space of the target functional node through the on-board Ethernet management bus 12.

[0052] In this embodiment, a direct communication link from the external communication node to the functional node 2 is also provided, which is used to transmit the second upgrade file version directly to the functional node 2 through the direct communication link during the debugging process, thereby improving debugging efficiency and reducing delays and errors caused by multi-level transmission. This direct transmission method allows developers to quickly verify the functionality and compatibility of the new firmware, accelerating the product development and optimization process. At the same time, the existence of the direct communication link also provides an additional redundant path for the system, enhancing the reliability of the system. During normal operation, the management switching module can receive the upgrade file through the external communication node and transmit it to the target functional node in a targeted manner. In debugging or emergency situations, the direct link can be used as a backup path to ensure timely updating and maintenance of the key functional node 2. This embodiment not only improves the flexibility and adaptability of the system, but also provides strong support for the development and maintenance of complex vehicle-mounted systems, further improving the overall performance and user experience of the vehicle-mounted domain control computer system.

[0053] In an exemplary embodiment, referring to Figure 3 As shown, it also includes: a communication exchange module, including an interconnected communication switch and a high-speed bus, and the interconnected communication switch is provided with multiple interfaces; the functional node 2 is detachably connected to the corresponding interface of the interconnected communication switch, and any two functional nodes 2 perform data exchange operations through the high-speed bus.

[0054] In this embodiment, considering the strong AI (Artificial Intelligence) computing scenarios of the onboard domain control computer, large-scale data interaction occurs between the platform's functional modules and computing nodes, with high requirements for real-time and reliable data. Therefore, this embodiment utilizes a high-bandwidth communication bus to interconnect multiple nodes. The platform and tightly coupled communication switches are connected in a star-shaped topology, with the platform providing only high-bandwidth differential line interfaces. This allows for flexible coordination between the platform's master control nodes and computing nodes across various computer architectures. This platform architecture supports architectures based on the PCIe (Peripheral Component Interconnect Express) topology as well as coherent bus architectures such as CXL (Compute Express Link). Changes to the control host and computing nodes can be made without changing the platform's interconnection topology. This facilitates hardware upgrades of the modular core computing platform, particularly in vehicles already equipped with interconnect cables and networks. At the same time, the platform architecture supports point-to-point communication interconnection between perception nodes and computing nodes. The architecture stipulates the use of high-speed communication cables and interfaces between modules. These interconnections are independent and tightly coupled outside the communication switch topology. The platform's critical mission communication paths and management interface paths are independent to ensure the reliability of data transmission.

[0055] In an exemplary embodiment, it further includes: a control node, wherein the communication interface of the control node is connected to the corresponding interface of the interconnected communication switch, and is configured to update its own storage space according to the data interaction operation between any two functional nodes 2.

[0056] In this embodiment, considering the complex in-vehicle computing environment, especially in strong AI computing scenarios, large-scale data interaction between functional nodes 2 requires extremely high real-time and reliability. By monitoring these interactions, the control node can intelligently adjust the data transmission strategy to ensure the priority transmission of mission-critical data, thereby improving the overall performance of the system.

[0057] In an exemplary embodiment, referring to Figure 4As shown, it also includes: a power bus and multiple power supply branches, the first ends of the multiple power supply branches are all connected to the power bus, and the second ends of the multiple power supply branches are correspondingly connected to the first power supply interface of the management node, the power supply interface of the functional node 2 and the power supply interface of the control node; the controller 31 is also configured to control at least one functional node 2 and the control node to be powered on in sequence according to a preset power-on sequence; it also includes switches provided on each power supply branch, and the controller 31 is specifically configured to control the switches on the corresponding power supply branches to be turned on in sequence according to the preset power-on sequence.

[0058] It also includes a standby power supply, a first end of the standby power supply is connected to the power bus, a second end of the standby power supply is connected to the second power supply interface of the management node, and the standby power supply is configured to power the management node when the management node is in a wake-up state.

[0059] In this embodiment, the main power supply voltage of the platform's power bus is defined as 12V or 24V (two standards), and a 3.3V standby power supply is provided to the platform's management node. The power supply interface of each functional node 2 includes a switch controlled by the platform's management node, specifically an electronic switch. The interfaces of other modules receive power from the power bus, and the bus does not perform voltage conversion, that is, it is equivalent to the two standard voltages defined by the bus. The on-board BMS (Battery Management System) power supply is directly connected to the platform's power bus, so the platform power supply is equal to the vehicle's BMS power supply voltage without conversion. The power bus system includes a DC / DC module. The standby power supply voltage is 3.3V, which is output to the platform's management node. The platform's management node includes the platform's power-on timing management, which is achieved by controlling the electronic switch output from the power supply bus to each module. The logic of the power-on timing is closely related to the initialization program of each node of the platform. The platform power-on timing logic is as follows: Figure 5 shown.

[0060] Reference Figure 6 As shown, the present invention utilizes a tightly coupled interconnected high-speed bus, an onboard Ethernet management bus 12, and a power bus as the platform core. Standard interfaces are defined and functional modules are divided according to the functions of the onboard domain control computer. These modules include control (host) nodes, computing nodes, sensing nodes, interconnected communication switches, external communication nodes, storage nodes, and the platform's management node. Based on the standard interfaces defined for each functional module, hardware units are decoupled from the platform, enabling flexible deployment and upgrades based on demand.

[0061] The present application also provides an upgrade method, which is applied to the controller of the vehicle-mounted domain control computer system as described in any of the embodiments above, and the upgrade method includes: receiving a first upgrade file version through an external communication node; writing the first upgrade file version into the first memory of the management node of the vehicle-mounted domain control computer system; when a preset trigger condition is met, obtaining the current hardware connection information of the vehicle-mounted Ethernet switch of the vehicle-mounted domain control computer system based on the vehicle-mounted Ethernet management bus, and controlling the vehicle-mounted Ethernet switch to transmit the first upgrade file version that matches the current hardware configuration to the first storage space of the target functional node of the vehicle-mounted domain control computer system through the vehicle-mounted Ethernet management bus.

[0062] In an exemplary embodiment, the upgrade method also includes: maintaining a mapping table between the hardware identification information of each functional node and its compatible file version range, obtaining the hardware identification information of the target functional node based on the on-board Ethernet management bus, querying the mapping table, and verifying whether the first upgrade file version is within the file version range corresponding to the hardware identification information. If so, determining that the first upgrade file version matches the current hardware configuration.

[0063] In an exemplary embodiment, the preset trigger condition includes a preset upgrade time period; when the preset trigger condition is met, based on the current hardware connection information of the management switching module of the vehicle-mounted domain control computer system, the process of controlling the management switching module to direct the transmission of the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node of the vehicle-mounted domain control computer system includes: determining whether the total upgrade duration of each first upgrade file version stored in the first memory is greater than the duration of the preset upgrade time period; if so, determining the upgrade priority of the functional node corresponding to each first upgrade file version; when the preset trigger condition is met, controlling the vehicle-mounted Ethernet switch to direct the transmission of the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node through the vehicle-mounted Ethernet management bus in descending order of upgrade priority.

[0064] In an exemplary embodiment, the vehicle-mounted domain control computer system further includes a backup module configured to store a backup running file version of at least one functional node, where the backup running file version is a file version of the functional node that has been running stably for a first preset time period.

[0065] In an exemplary embodiment, the upgrade method further includes: when a function node that fails to upgrade is detected, and a preset trigger condition is met, controlling the function node that fails to upgrade to run according to the corresponding backup running file version in the backup module.

[0066] In an exemplary embodiment, the functional node includes a first-class functional node, the backup module includes a second storage space provided in the first-class functional node, and the second storage space is configured to store the backup operation file version of the first-class functional node to which it belongs; when a functional node that fails to upgrade is detected, when a preset trigger condition is met, the process of controlling the functional node that fails to upgrade to run according to the corresponding backup operation file version in the backup module includes: when it is detected that the first-class functional node fails to upgrade, the first-class functional node is switched to the second storage space for operation.

[0067] In an exemplary embodiment, the backup module includes a second memory provided in the management node, and the upgrade method further includes: receiving a backup running file version through an external communication node, writing the backup running file version into the second memory, and when a functional node that fails to upgrade is detected, when a preset trigger condition is met, obtaining the current hardware connection information of the on-board Ethernet switch based on the on-board Ethernet management bus, and controlling the on-board Ethernet switch to transmit the corresponding backup running file version to the first storage space of the functional node that fails to upgrade through the on-board Ethernet management bus.

[0068] In an exemplary embodiment, the upgrade method also includes: if it is detected that the target functional node is successfully upgraded and has been running stably for more than a second preset time period, marking the backup running version corresponding to the target functional node as a cleanable state in the second memory, and when the occupancy rate of the second memory exceeds a preset threshold, cleaning the backup running version marked as a cleanable state according to the version sequence.

[0069] In an exemplary embodiment, the functional node also includes an interface conversion module, the first end of the interface conversion module is connected to the upgrade interface of the functional node to which it belongs, and the second end of the interface conversion module is connected to the first storage space in the functional node to which it belongs. The upgrade method also includes: converting the original data received by its own first end into target data adapted to the first storage space connected to its own second end through the interface conversion module.

[0070] In an exemplary embodiment, the management switching module includes a management interface, and the external communication node is connected to the management interface. The upgrade method also includes: transmitting the second upgrade file version received by the external communication node through the vehicle-mounted Ethernet switch to the storage space of the target functional node through the vehicle-mounted Ethernet management bus.

[0071] In an exemplary embodiment, the vehicle-mounted domain control computer system also includes a communication exchange module, including an interconnected communication switch and a high-speed bus, and the interconnected communication switch is provided with multiple interfaces; the functional nodes and the corresponding interfaces of the interconnected communication switch are detachably connected, and any two functional nodes perform data interaction operations through the high-speed bus.

[0072] In an exemplary embodiment, the vehicle-mounted domain control computer system also includes a power bus and multiple power supply branches, the first ends of the multiple power supply branches are all connected to the power bus, and the second ends of the multiple power supply branches are correspondingly connected to the first power supply interface of the management node, the power supply interface of the functional node and the power supply interface of the control node; the upgrade method also includes: controlling at least one functional node and the control node to power on in sequence according to a preset power-on sequence.

[0073] In an exemplary embodiment, the vehicle-mounted domain control computer system further includes switches provided on each power supply branch; the upgrade method further includes: sequentially controlling the switches on the corresponding power supply branches to be turned on according to a preset power-on sequence.

[0074] The present application also provides an upgrade system, which includes: a receiving module for receiving a first upgrade file version through an external communication node; a writing module for writing the first upgrade file version into a first memory in a management node of a vehicle-mounted domain control computer system; an upgrade module for obtaining the current hardware connection information of the vehicle-mounted Ethernet switch of the vehicle-mounted domain control computer system based on the vehicle-mounted Ethernet management bus when a preset trigger condition is met, and controlling the vehicle-mounted Ethernet switch to transmit the first upgrade file version that matches the current hardware configuration to the first storage space of the target functional node of the vehicle-mounted domain control computer system through the vehicle-mounted Ethernet management bus.

[0075] In an exemplary embodiment, the upgrade system is also used to: maintain a mapping table between the hardware identification information of each functional node and its compatible file version range, obtain the hardware identification information of the target functional node based on the on-board Ethernet management bus, query the mapping table, and verify whether the first upgrade file version is within the file version range corresponding to the hardware identification information. If so, determine that the first upgrade file version matches the current hardware configuration.

[0076] In an exemplary embodiment, the preset trigger condition includes a preset upgrade time period; when the preset trigger condition is met, based on the current hardware connection information of the management switching module of the vehicle-mounted domain control computer system, the process of controlling the management switching module to direct the transmission of the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node of the vehicle-mounted domain control computer system includes: determining whether the total upgrade duration of each first upgrade file version stored in the first memory is greater than the duration of the preset upgrade time period; if so, determining the upgrade priority of the functional node corresponding to each first upgrade file version; when the preset trigger condition is met, controlling the vehicle-mounted Ethernet switch to direct the transmission of the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node through the vehicle-mounted Ethernet management bus in descending order of upgrade priority.

[0077] In an exemplary embodiment, the vehicle-mounted domain control computer system further includes a backup module configured to store a backup running file version of at least one functional node, where the backup running file version is a file version of the functional node that has been running stably for a first preset time period.

[0078] In an exemplary embodiment, the upgrade system is further configured to: upon detecting a function node that has failed to be upgraded, and when a preset trigger condition is met, control the function node that has failed to be upgraded to run according to the corresponding backup running file version in the backup module.

[0079] In an exemplary embodiment, the functional node includes a first-class functional node, the backup module includes a second storage space provided in the first-class functional node, and the second storage space is configured to store the backup operation file version of the first-class functional node to which it belongs; when a functional node that fails to upgrade is detected, when a preset trigger condition is met, the process of controlling the functional node that fails to upgrade to run according to the corresponding backup operation file version in the backup module includes: when it is detected that the first-class functional node fails to upgrade, the first-class functional node is switched to the second storage space for operation.

[0080] In an exemplary embodiment, the backup module includes a second memory provided in the management node, and the upgrade system is further used to: receive the backup running file version through the external communication node, write the backup running file version into the second memory, and when a functional node that fails to upgrade is detected, when a preset trigger condition is met, obtain the current hardware connection information of the on-board Ethernet switch based on the on-board Ethernet management bus, and control the on-board Ethernet switch to transmit the corresponding backup running file version to the first storage space of the functional node that fails to upgrade through the on-board Ethernet management bus.

[0081] In an exemplary embodiment, the upgrade system is also used to: if it is detected that the target functional node is successfully upgraded and has been running stably for more than a second preset time period, mark the backup running version corresponding to the target functional node in the second memory as a cleanable state; when the occupancy rate of the second memory exceeds a preset threshold, clean the backup running version marked as a cleanable state according to the version sequence.

[0082] In an exemplary embodiment, the functional node also includes an interface conversion module, the first end of the interface conversion module is connected to the upgrade interface of the functional node to which it belongs, and the second end of the interface conversion module is connected to the first storage space in the functional node to which it belongs. The upgrade system is also used to: convert the original data received by its own first end into target data adapted to the first storage space connected to its own second end through the interface conversion module.

[0083] In an exemplary embodiment, the management switching module includes a management interface, the external communication node is connected to the management interface, and the upgrade system is also used to: transmit the second upgrade file version received by the external communication node through the vehicle-mounted Ethernet switch to the storage space of the target functional node through the vehicle-mounted Ethernet management bus.

[0084] In an exemplary embodiment, the vehicle-mounted domain control computer system also includes a communication exchange module, including an interconnected communication switch and a high-speed bus, and the interconnected communication switch is provided with multiple interfaces; the functional nodes and the corresponding interfaces of the interconnected communication switch are detachably connected, and any two functional nodes perform data interaction operations through the high-speed bus.

[0085] In an exemplary embodiment, the vehicle-mounted domain control computer system also includes a power bus and multiple power supply branches, the first ends of the multiple power supply branches are all connected to the power bus, and the second ends of the multiple power supply branches are correspondingly connected to the first power supply interface of the management node, the power supply interface of the functional node and the power supply interface of the control node; the upgrade system is also used to: control at least one functional node and the control node to power on in sequence according to a preset power-on sequence.

[0086] In an exemplary embodiment, the vehicle-mounted domain control computer system also includes switches provided on each power supply branch; the upgrade system is further used to control the conduction of the switches on the corresponding power supply branches in sequence according to a preset power-on sequence.

[0087] An embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any of the above-mentioned upgrade method embodiments.

[0088] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any of the above-mentioned upgrade method embodiments when running.

[0089] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0090] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any of the above-mentioned upgrade method embodiments are implemented.

[0091] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the above-mentioned upgrade method embodiments are implemented.

[0092] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0093] The above is a detailed introduction to the vehicle-mounted domain control computer system, method, system, device, product and medium provided by the present application. This article uses specific examples to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core ideas. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

Claims

1. A vehicle-mounted domain control computer system, characterized in that: include: A management switching module, comprising an on-board Ethernet switch and an on-board Ethernet management bus, wherein the on-board Ethernet switch comprises multiple interfaces; at least one functional node, detachably connected to a corresponding interface of the vehicle Ethernet switch; A management node is connected to the corresponding interface of the vehicle Ethernet switch, and includes a controller and a first memory. The controller is configured to receive a first upgrade file version through an external communication node, write the first upgrade file version into the first memory, and when a preset trigger condition is met, obtain the current hardware connection information of the vehicle Ethernet switch based on the vehicle Ethernet management bus, and control the vehicle Ethernet switch to transmit the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node through the vehicle Ethernet management bus.

2. The vehicle-mounted domain control computer system according to claim 1, characterized in that: The controller is further configured to maintain a mapping table between the hardware identification information of each functional node and its compatible file version range, obtain the hardware identification information of the target functional node based on the on-board Ethernet management bus, query the mapping table, and verify whether the first upgrade file version is within the file version range corresponding to the hardware identification information. If so, it is determined that the first upgrade file version matches the current hardware configuration.

3. The vehicle-mounted domain control computer system according to claim 1, characterized in that: The preset trigger condition includes a preset upgrade time period; The controller is specifically configured to determine whether the total upgrade duration of each first upgrade file version stored in the first memory is greater than the duration of the preset upgrade time period; if so, determine the upgrade priority of the functional node corresponding to each first upgrade file version; and when a preset trigger condition is met, control the on-board Ethernet switch to sequentially and directionally transmit the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node through the on-board Ethernet management bus in descending order of the upgrade priority.

4. The vehicle-mounted domain control computer system according to claim 1, characterized in that: The vehicle-mounted domain control computer system further includes: The backup module is configured to store a backup running file version of at least one of the functional nodes, where the backup running file version is a file version of the functional node that has been running stably for a first preset time period.

5. The vehicle-mounted domain control computer system according to claim 4, characterized in that: The controller is further configured to, when detecting a function node that has failed to be upgraded and when the preset trigger condition is met, control the function node that has failed to be upgraded to run according to the corresponding backup running file version in the backup module.

6. The vehicle-mounted domain control computer system according to claim 5, characterized in that: The functional node includes a first type functional node, the backup module includes a second storage space provided in the first type functional node, and the second storage space is configured to store a backup running file version of the first type functional node to which it belongs; The controller is specifically configured to switch the first type of functional node to the second storage space for operation when detecting that the first type of functional node fails to be upgraded.

7. The vehicle-mounted domain control computer system according to claim 4, characterized in that: The backup module includes a second memory provided in the management node. The controller is further configured to receive the backup running file version through the external communication node and write the backup running file version into the second memory. When a functional node that fails to upgrade is detected and the preset trigger condition is met, the controller obtains the current hardware connection information of the on-board Ethernet switch based on the on-board Ethernet management bus, and controls the on-board Ethernet switch to transmit the corresponding backup running file version to the first storage space of the functional node that fails to upgrade through the on-board Ethernet management bus.

8. The vehicle-mounted domain control computer system according to claim 7, characterized in that: The controller is also configured to mark the backup running version corresponding to the target functional node as a cleanable state in the second memory if it is detected that the target functional node has been successfully upgraded and has been running stably for more than a second preset time period. When the occupancy rate of the second memory exceeds a preset threshold, the backup running version marked as the cleanable state is cleaned up according to the version sequence.

9. The vehicle-mounted domain control computer system according to claim 1, characterized in that: The functional node also includes an interface conversion module, the first end of the interface conversion module is connected to the upgrade interface of the functional node to which it belongs, and the second end of the interface conversion module is connected to the first storage space in the functional node to which it belongs. The interface conversion module is configured to convert the original data received by its first end into target data adapted to the first storage space connected to its second end.

10. The vehicle-mounted domain control computer system according to claim 9, characterized in that: The management switching module also includes a management interface, the external communication node is connected to the management interface, and the on-board Ethernet switch is further configured to receive a second upgrade file version through the external communication node and transmit the second upgrade file version to the storage space of the target functional node through the on-board Ethernet management bus.

11. The vehicle-mounted domain control computer system according to claim 1, characterized in that: Also includes: A communication exchange module, comprising an interconnected communication switch and a high-speed bus, wherein the interconnected communication switch is provided with a plurality of interfaces; The functional nodes are detachably connected to corresponding interfaces of the interconnected communication switch, and any two functional nodes perform data exchange operations through the high-speed bus.

12. The vehicle-mounted domain control computer system according to claim 11, characterized in that: Also includes: A control node, wherein the communication interface of the control node is connected to the corresponding interface of the interconnected communication switch, and is configured to update its own storage space according to the data interaction operation between any two of the functional nodes.

13. The vehicle-mounted domain control computer system according to any one of claims 1 to 12, characterized in that: Also includes: A power bus and multiple power supply branches, wherein the first ends of the multiple power supply branches are connected to the power bus, and the second ends of the multiple power supply branches are correspondingly connected to the first power supply interface of the management node, the power supply interface of the functional node, and the power supply interface of the control node; The controller is further configured to control the at least one functional node and the control node to be powered on in sequence according to a preset power-on sequence.

14. The vehicle-mounted domain control computer system according to claim 13, characterized in that: Also includes: The switches provided on each of the power supply branches, the controller is specifically configured to control the switches on the corresponding power supply branches to be turned on in sequence according to the preset power-on sequence.

15. The vehicle-mounted domain control computer system according to claim 13, characterized in that: Also includes: A standby power supply, wherein the first end of the standby power supply is connected to the power bus, the second end of the standby power supply is connected to the second power supply interface of the management node, and the standby power supply is configured to power the management node when the management node is in a wake-up state.

16. An upgrade method, characterized in that: The controller of the vehicle-mounted domain control computer system according to any one of claims 1 to 15, wherein the upgrade method comprises: Receiving a first upgrade file version through an external communication node; Writing the first upgrade file version into the first memory of the management node of the vehicle-mounted domain control computer system; When the preset trigger conditions are met, the current hardware connection information of the on-board Ethernet switch of the on-board domain control computer system is obtained based on the on-board Ethernet management bus, and the on-board Ethernet switch is controlled to transmit the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node of the on-board domain control computer system through the on-board Ethernet management bus.

17. An upgrade system, characterized in that: The upgrade system includes: A receiving module, configured to receive a first upgrade file version via an external communication node; A writing module, configured to write the first upgrade file version into a first memory in a management node of the vehicle-mounted domain control computer system; The upgrade module is used to obtain the current hardware connection information of the on-board Ethernet switch of the on-board domain control computer system based on the on-board Ethernet management bus when the preset trigger conditions are met, and control the on-board Ethernet switch to transmit the first upgrade file version matching the current hardware configuration to the first storage space of the target functional node of the on-board domain control computer system through the on-board Ethernet management bus.

18. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the upgrading method according to claim 16 are implemented.

19. An electronic device, characterized in that: include: memory for storing computer programs; A processor, configured to implement the steps of the upgrading method according to claim 16 when executing the computer program.

20. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which implements the steps of the upgrading method according to claim 16 when executed by a processor.

Images