Method and device for upgrading electronic control unit of whole vehicle

Abstract

The application discloses a whole vehicle electronic control unit (ECU) upgrading method and device. The upgrading method comprises the following steps: receiving a first operation of a user based on a first display interface, wherein the first operation comprises a dragging operation of dragging n target ECU topology components in m ECU topology components in the first display interface to an upgrading sequence region in the first display interface, and a connection operation of connecting the n target ECU topology components in the upgrading sequence region with preset starting nodes and ending nodes; generating an ECU topology component connection sequence diagram based on the first operation; generating an ECU upgrading link based on the ECU topology component connection sequence diagram; and controlling the ECU to be upgraded to a corresponding target version according to an upgrading sequence relationship indicated by the ECU upgrading link based on the ECU upgrading link.

Description

Technical Field

[0001] This application belongs to the field of vehicle electronic control unit (ECU) upgrade technology, and particularly relates to a method and device for upgrading a vehicle electronic control unit (ECU). Background Technology

[0002] With the rapid development of automotive intelligence and connectivity technologies, modern cars integrate a large number of Electronic Control Units (ECUs) to control various functional domains such as the engine, transmission, body, and entertainment system. To ensure vehicle functionality, safety, and performance, these ECUs require regular upgrades.

[0003] In existing ECU upgrade solutions, the upgrade order is typically pre-configured in a configuration file by a cloud server or technicians. This approach lacks flexibility and cannot adapt to different vehicle configurations or user-defined upgrade needs. Secondly, configuring the upgrade order is a highly specialized task, requiring developers to have a deep understanding of the dependencies and upgrade logic between various ECUs. This is accomplished by modifying code or configuration files, a cumbersome and error-prone process that results in low ECU upgrade efficiency. Summary of the Invention

[0004] This application provides a method, apparatus, device, medium, and product for upgrading a vehicle electronic control unit (ECU), which can improve the efficiency of ECU upgrades.

[0005] In a first aspect, embodiments of this application provide a method for upgrading a vehicle electronic control unit (ECU), including: The system receives a first operation from a user based on a first display interface. The first operation includes a drag operation to drag n target ECU topology components from m ECU topology components in the first display interface to an upgrade order area in the first display interface, and a connection operation to connect the n target ECU topology components in the upgrade order area to a preset start node and end node. One ECU topology component corresponds to one ECU, m≥2, n≤m. Based on the first operation, an ECU topology component connection sequence diagram is generated; Based on the ECU topology component connection sequence diagram, an ECU upgrade link is generated, wherein the ECU upgrade link represents the upgrade sequence relationship of n ECUs corresponding to n target ECU topology components; Based on the ECU upgrade link, the ECU is controlled to upgrade to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade link.

[0006] Secondly, embodiments of this application provide an upgrade device for a vehicle electronic control unit (ECU), comprising: The receiving module is used to receive a first operation by the user based on the first display interface. The first operation includes a drag operation to drag n target ECU topology components from m ECU topology components in the first display interface to the upgrade order area in the first display interface, and a connection operation to connect the n target ECU topology components in the upgrade order area with preset start and end nodes. One ECU topology component corresponds to one ECU, m≥2, n≤m. The generation module is used to generate an ECU topology component connection sequence diagram based on the first operation; The generation module is also used to generate an ECU upgrade link based on the ECU topology component connection sequence diagram, wherein the ECU upgrade link represents the upgrade order relationship of n ECUs corresponding to n target ECU topology components; The upgrade module is used to control the ECU to upgrade to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade link, based on the ECU upgrade link.

[0007] Thirdly, embodiments of this application provide an electronic device, the device comprising: Processor and memory storing computer program instructions; The processor executes computer program instructions to perform the upgrade method for the vehicle electronic control unit (ECU) described in the first aspect above.

[0008] Fourthly, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement the upgrade method for the vehicle electronic control unit (ECU) described in the first aspect.

[0009] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when processed by a processor, implements the upgrade method for the vehicle electronic control unit (ECU) described in the first aspect.

[0010] The vehicle electronic control unit (ECU) upgrade method and apparatus provided in this application embodiment receive a first operation from a user based on a first display interface, drag and drop n target ECU topology components to the upgrade sequence area and connect them to obtain an ECU topology component connection sequence diagram. The corresponding ECU is determined by the n target ECU topology components in the ECU topology component connection sequence diagram, and an ECU upgrade link can be generated based on multiple ECUs. This enables rapid and visual generation of ECU upgrade links, improves user experience, controls the ECU to upgrade to the corresponding upgrade version according to the upgrade link, realizes a customizable ECU upgrade process, and improves ECU upgrade efficiency. Attached Figure Description

[0011] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart illustrating a method for upgrading a vehicle electronic control unit (ECU) according to some embodiments of this application.

[0013] Figure 2 This is a schematic diagram of an exemplary first display interface provided for some embodiments of this application.

[0014] Figure 3 This is a flowchart illustrating a method for upgrading a vehicle electronic control unit (ECU) according to some embodiments of this application.

[0015] Figure 4 This is a schematic diagram of yet another exemplary first display interface provided for some embodiments of this application.

[0016] Figure 5 This is a schematic diagram of another exemplary first display interface provided for some embodiments of this application.

[0017] Figure 6 This is a schematic diagram of an exemplary second display interface provided for some embodiments of this application.

[0018] Figure 7 This is a schematic diagram of an exemplary preset display interface provided for some embodiments of this application.

[0019] Figure 8 This is a schematic diagram of an upgrade device for a vehicle electronic control unit (ECU) provided in some embodiments of this application.

[0020] Figure 9 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0021] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0022] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0023] Before describing the technical solutions provided in the embodiments of this application, in order to facilitate understanding of the embodiments of this application, this application first specifically explains the problems existing in the related technologies: Currently, to improve the control precision of vehicles, it is necessary to upgrade the ECUs in the vehicle. However, due to the large number of ECUs in the vehicle, when creating an upgrade task, users need to specify the upgrade order for the configuration files of a large number of ECUs, which results in low efficiency, high difficulty and lack of user customization.

[0024] Based on this, embodiments of this application provide a method and apparatus for upgrading a vehicle electronic control unit (ECU), which can solve the above-mentioned problems. Below, a detailed description of an upgrade method for a vehicle electronic control unit (ECU) provided by embodiments of this application will be provided. In some embodiments, such as Figure 1 As shown in the figure, this application embodiment provides a method for upgrading a vehicle electronic control unit (ECU), which may include: S110: Receive a first operation from the user based on the first display interface, wherein the first operation includes a drag operation to drag n target ECU topology components from m ECU topology components in the first display interface to the upgrade order area in the first display interface, and a connection operation to connect the n target ECU topology components in the upgrade order area with preset start and end nodes, wherein one ECU topology component corresponds to one ECU, m≥2, n≤m, and m and n are both integers.

[0025] It is conceivable that the upgrade method for the vehicle electronic control unit (ECU) provided in this application embodiment is based on a modular architecture, which includes the following four core modules: The basic module includes two main functional units: ECU type management and ECU instance management. The ECU type management unit includes an ECU type identifier (e.g., 0x00) used to match ECT topology components in the topology relationship diagram and upgrade sequence customization diagram. The ECU instance management unit includes an ECU name and an ECU identifier (e.g., 0x00DD) used for the unique identification of each ECU during the upgrade process. The visualization customization module includes a topology relationship display unit and an upgrade order customization unit. The topology relationship display unit includes parameters such as node coordinates, node display size, and topology node identifiers. It verifies the association between topology data and the ECU type list by matching status attributes (highlighting successful matches and graying out failed matches). The upgrade order customization unit supports node drag-and-drop, sequence arrangement, and node removal functions. It automatically generates the upgrade order after each ECU topology component connection is completed through a trigger mechanism. The topology component library provides a unified encapsulation of topology components. The upgrade order identifier attribute is used to distinguish between the two usage modes of topology relationship display and upgrade order customization. The encapsulated rendering interface realizes the visualization of node configuration attributes, and the coordinate transformation interface realizes the system conversion from screen coordinates to rendering coordinates. The two modes of topology relationship display and upgrade order customization are isolated through data processing to ensure the independent operation of the two functions. The upgrade execution module is used for upgrade task management and can record the upgrade ECU name, upgrade order, target version number, and priority level.

[0026] like Figure 2 As shown, Figure 2 This is a schematic diagram of an exemplary first display interface. Figure 2 It includes a first display area 201 for displaying m ECU topology components, and an upgrade sequence area 202 for users to perform drag-and-drop and connection operations. For example... Figure 2 Each ECU topology component includes an ECU identifier, such as 0xAA, 0xBB, and 0xCC, as shown in the figure.

[0027] Based on such Figure 2 The first display interface shown allows users to drag and drop n target ECU topology components to the upgrade sequence area 202, and connect these n target ECU topology components to preset start and end nodes. For example... Figure 2 In the process, users can drag and drop the three target ECU topology components 0xAA, 0xBB, and 0xCC to the upgrade sequence area 202, and then establish connection lines between the start node, 0xAA, 0xBB, 0xCC, and end node in sequence.

[0028] In some examples, the above is as follows Figure 2 The different ECU topology components are all encapsulated using a common encapsulation method. This common encapsulation method includes the render function, which is used to render the ECU topology components to achieve visualization; the coordinateTransform function, which is used to convert screen coordinates to rendering coordinates so that the first display interface can still be displayed normally on screens of different display sizes; and upgrade link generation functions such as getOrderByFlag, getFirstChild, and getDescendantNode, which are used to generate the ECU upgrade link based on the connection order of the target ECU topology components, start node, and end node.

[0029] S120: Based on the first operation, generate the ECU topology component connection sequence diagram.

[0030] After the user completes the connection of n target ECU topology components, start nodes, and end nodes, an ECU topology component connection sequence diagram is generated. For example... Figure 2 In the process, an ECU topology component connection sequence diagram is generated, including the start node, 0xAA, 0xBB, 0xCC and the end node.

[0031] S130: Based on the ECU topology component connection sequence diagram, generate the ECU upgrade link, where the ECU upgrade link represents the upgrade sequence relationship of n ECUs corresponding to n target ECU topology components.

[0032] Based on the ECU topology component connection sequence diagram above, the start and end nodes can be removed. Based on n target ECU topology components, the corresponding ECUs can be determined, and based on the connection relationships of the n target ECU topology components, the ECU upgrade sequence can be obtained. An ECU upgrade link can be generated, for example, based on... Figure 2 The ECU topology components are connected in a specific order to generate an ECU upgrade link of 0xAA-0xBB-0xCC.

[0033] S140: Based on the ECU upgrade link, control the ECU to upgrade to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade link.

[0034] Based on the aforementioned ECU upgrade link, upgrade commands and target versions can be issued to the corresponding ECUs, controlling the ECUs to upgrade according to the upgrade sequence indicated by the aforementioned ECU upgrade link.

[0035] It is conceivable that after the ECU upgrade is completed, a message indicating that the ECU upgrade is complete will be displayed.

[0036] The vehicle electronic control unit (ECU) upgrade method provided in this application automatically generates an ECU topology component connection sequence diagram by receiving drag-and-drop and connection operations from the user based on a first display interface, and further generates an ECU upgrade link, thereby controlling the ECU to upgrade according to a specified upgrade sequence. This method simplifies the ECU upgrade sequence configuration process through visual drag-and-drop operations, improving upgrade efficiency and accuracy. Simultaneously, preset start and end nodes ensure the integrity and correctness of the upgrade link, avoiding upgrade failures or equipment damage caused by incorrect upgrade sequence due to manual configuration files. Furthermore, this method supports flexible adjustment of the upgrade sequence; users can easily set the position and connection relationship of ECU topology components through drag-and-drop operations, automatically generating the upgrade link to meet upgrade needs in different scenarios. This intuitive and easy-to-use operation greatly reduces the user's operational threshold and enhances the user experience.

[0037] In some embodiments, such as Figure 3 As shown, based on the ECU topology component connection sequence diagram, an ECU upgrade link can be generated, which may include: S310: Based on the preset first direction traversal ECU topology component connection sequence diagram of n target ECU topology components, determine the first target ECU topology component connected to the start node, and determine all second target ECU topology components connected between the first target ECU topology component and the end node.

[0038] Here, the first direction mentioned above can be the direction from the start node to the end node. The first target ECU topology component and the second target ECU topology component can be determined using the upgrade link generation function encapsulated in the ECU topology component. The specific steps are as follows: Step 1: By executing the getOrderByFlag function, determine all start or end nodes by traversing the upgrade order region.

[0039] Here, the getOrderByFlag function is executed, and the global variable collectAllPipelines is declared to collect the preset start and end nodes. The start node, end node, and all target ECU topology components between the start and end nodes are stored in FlagArray. The start node is marked in FlagArray, and a corresponding priority level is created for the first ECU topology component to ensure that ECUs within the same level are upgraded in order, while there is a priority relationship between different levels.

[0040] Step 2: By executing the getFirstChild function, the data in FlagArray is traversed and the first target ECU topology component connected to the starting node is stored in firstNodeArray.

[0041] Step 3: Passing `firstNodeArray` as the argument, execute the `getDescendantNode` function for the first target ECU topology component to determine all second target ECU topology components connected between the first target ECU topology component and the end node. The `getDescendantNode` function recursively traverses each second target ECU topology component until the end node is reached, and simultaneously configures upgrade order values ​​for each node after the start node in ascending order to determine the upgrade order.

[0042] By following the steps above, the connection order of n target ECU topology components can be obtained.

[0043] S320: Determine the corresponding first ECU based on the first target ECU topology component, and determine the corresponding second ECU based on each second target ECU topology component.

[0044] The corresponding ECU can be determined based on the ECU identifier in the preset target ECU topology component.

[0045] S330: Generates an ECU upgrade path based on the first ECU and the second ECU.

[0046] By sorting the first ECU and the second ECU according to the connection order relationship indicated by the ECU topology component connection sequence diagram, we can obtain the first ECU and the second ECU.

[0047] For example Figure 2The topology connection sequence diagram shown is explained in detail. For the first target ECU topology components 0xAA and 0xEE, they correspond to priority 1 and priority 2 respectively. For the topology components after 0xAA, the sequence is traversed and determined as follows: 0xAA (upgrade order = 1) → 0xBB (upgrade order = 2) → 0xCC (upgrade order = 3). For 0xEE, the sequence is traversed and determined as follows: 0xEE (upgrade order = 1) → 0xHH (upgrade order = 2).

[0048] This application embodiment can accurately extract the correct target ECU topology component connection sequence by traversing the ECU topology component connection sequence diagram according to a preset first direction. By determining the first target ECU topology component connected to the start node, the second target ECU topology component between the first target ECU topology component and the end node is then determined, thereby determining the accurate ECU upgrade link, realizing the rapid generation of the ECU upgrade link, and improving the ECU upgrade efficiency.

[0049] It is conceivable that when generating the ECU topology component connection sequence diagram, the user at least graphically manipulates the order of the ECU topology components without actually modifying the ECU's configuration file or program code. This reduces the risk of ECU errors that may occur due to manual manipulation of the configuration file or program code. At the same time, generating the ECU upgrade link manually through a visual interface also improves the flexibility of the ECU upgrade process.

[0050] When a user drags or connects ECU topology components to generate an ECU topology component connection sequence diagram, the user may modify the ECU topology components. In some embodiments, generating an ECU topology component connection sequence diagram based on a first operation may include: Based on the first operation, an initial ECU topology component connection sequence diagram is generated; modification operations by the user on n target ECU topology components in the initial ECU topology component connection sequence diagram are received; based on the modification operations, an ECU topology component connection sequence diagram is generated.

[0051] Here, based on the first operation, an initial ECU topology component connection sequence diagram can be generated. The user can receive modification operations based on n target ECU topology components in the initial ECU topology component connection sequence diagram. The modification operations can include deleting any target ECU topology component, deleting the connection lines between target ECU topology components, or swapping the order of any two target ECU topology components, etc.

[0052] Based on the above modifications, an ECU topology component connection sequence diagram can be generated. This embodiment of the application improves the flexibility of the generated ECU upgrade path by receiving user modifications based on the initial ECU topology component connection sequence diagram and generating the ECU topology component connection sequence diagram.

[0053] It is conceivable that users might generate at least two sub-connection sequence diagrams based on multiple ECU topology components through drag-and-drop and connection operations. In some embodiments, such as Figure 4 As shown, the ECU topology component connection sequence diagram includes at least two sub-connection sequence diagrams, and the ECU upgrade link includes at least two sub-upgrade links. Based on the ECU topology component connection sequence diagram, an ECU upgrade link is generated, which may include: S410: Based on a preset first direction, traverse at least two sub-connection sequence diagrams of n target ECU topology components, determine at least two first target ECU topology components connected to the start node, and for each first target ECU topology component, determine all second target ECU topology components connected between the first target ECU topology component and the end node.

[0054] like Figure 5 As shown, Figure 5 This is a schematic diagram of another type of primary display interface, such as... Figure 5 It includes two sub-connection sequence diagrams, namely the start node, 0xAA, 0xBB, 0xCC and the end node, and the start node, 0xEE, 0xHH and the end node.

[0055] Similarly, the first target ECU topology component and the second target ECU topology component can be determined by the upgrade link generation function encapsulated in the ECU topology component.

[0056] Specifically, by executing the `getOrderByFlag` function, the start node is determined by traversing the upgrade order region, and the start node, end node, and all target ECU topology components between the start and end nodes are stored in `FlagArray`. Next, by executing the `getFirstChild` function, the data in `FlagArray` is traversed, and at least two first target ECU topology components connected to the start node are stored in `firstNodeArray`. Then, for any first target ECU topology component, the `getDescendantNode` function is executed to determine all second target ECU topology components connected to the end node.

[0057] S420: Based on at least two first target ECU topology components and a second target ECU topology component, determine at least two corresponding first ECUs and all second ECUs respectively.

[0058] Based on the at least two first target ECU topology components and the second target ECU topology components determined above, and based on the correspondence between ECU topology components and ECUs, at least two first ECUs and all second ECUs can be determined.

[0059] S430: Generate at least two sub-upgrade links based on at least two first ECUs and all second ECUs.

[0060] Based on the connection order of the target ECU topology components obtained through traversal, generate at least two sub-upgrade links from at least two first ECUs and all second ECUs.

[0061] For example, based on such Figure 5 The two sub-connection sequence diagrams shown result in two sub-upgrade links: 0xAA-0xBB-0xCC and 0xEE-0xHH.

[0062] Based on the ECU upgrade chain, the control ECU is upgraded to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade chain, including: S440: Based on at least two sub-upgrade links, control at least two first ECUs and all second ECUs to upgrade to the corresponding target version according to the upgrade order relationship indicated by at least two sub-upgrade links.

[0063] An ECU can be upgraded to a target version through at least two sub-upgrade links. Here, at least two sub-upgrade links can be controlled to simultaneously upgrade to the corresponding target version according to the upgrade order indicated by the at least two sub-upgrade links; that is, the ECUs of at least two sub-upgrade links can be upgraded in parallel, or the upgrades can be performed based on the priority order corresponding to each sub-upgrade link.

[0064] In this embodiment of the application, even when generating at least two sub-connection sequence diagrams based on the user's first operation, at least two corresponding sub-upgrade links can still be generated. This allows users to configure the upgrade order of multiple ECUs at once, reducing the configuration complexity of managing the upgrade order of multiple ECUs and improving the upgrade efficiency of ECUs.

[0065] In some embodiments, controlling at least two first ECUs and all second ECUs to upgrade to the corresponding target version according to the upgrade order relationship indicated by at least two sub-upgrade links may include: Based on the positional relationship of at least two first target ECU topology components, the priorities corresponding to at least two first target ECU topology components are determined respectively; based on the priorities and at least two sub-upgrade links, at least two first ECUs and all second ECUs are controlled to upgrade to the corresponding target version according to the priority order and the upgrade order relationship indicated by at least two sub-upgrade links.

[0066] Here, the positional relationship of at least two first target ECU topology components can be detected in a second preset direction, which can be a direction perpendicular to the aforementioned first preset direction, and the priority of each of the at least two first target ECU topology components can be determined.

[0067] For example, in such Figure 5 In the first display interface, after the getFirstChild function traverses to at least two first target ECU topology components 0xAA and 0xEE, based on their positional relationship, 0xAA and 0xEE can be assigned corresponding priority values ​​of 1 respectively. For example, the priority value of 0xAA is the first value, such as 1, and the priority value of 0xEE is the second value, such as 2. The higher the priority value, the higher the priority, that is, the priority of the sub-connection sequence diagram where 0xAA is located is higher than the priority of the sub-connection sequence diagram where 0xEE is located.

[0068] It can be assumed that the priority of the aforementioned sub-upgrade links 0xAA-0xBB-0xCC is higher than that of 0xEE-0xHH.

[0069] It can control at least two first ECUs and all second ECUs to upgrade to the corresponding target version according to the priority order and the upgrade order relationship indicated by at least two sub-upgrade links. That is, it can first control the sub-upgrade links with higher priority to upgrade to the corresponding target version according to the upgrade order relationship, and then control the sub-upgrade links with lower priority to upgrade to the corresponding target version according to the upgrade order relationship.

[0070] This application embodiment controls ECU upgrades by determining their corresponding priorities when generating multiple sub-upgrade links. This avoids the problem of upgrade failures caused by limited vehicle upgrade resources when generating multiple upgrade tasks. At the same time, it reduces uncertainties and potential conflicts in the upgrade processes of different ECUs, and improves the stability of the ECU upgrade process.

[0071] In some embodiments, before receiving a first operation from a user based on a preset first display interface, the upgrade method may further include: Obtain the ECU list of the entire vehicle, which includes m ECU identifiers; determine the corresponding m ECU topology components based on the m ECU identifiers; display a first display interface including the m ECU topology components and an upgrade sequence area, wherein the upgrade sequence area is a visual operation interface generated based on a preset graphics engine.

[0072] It can obtain a list of ECUs for the whole vehicle, including m ECU identifiers. In the preset ECU topology component library, it can identify m ECU topology components including ECU identifiers, and then display the first display interface of the m ECU topology components and the upgrade order area.

[0073] Here, the aforementioned upgrade sequence area refers to the visual operation interface that calls a preset graphics engine, such as Graph, for rendering, as shown in the image. Figure 1 Or such as Figure 5 The upgrade sequence area mentioned above may include pre-placed start and end nodes.

[0074] This application embodiment obtains the ECU list of the whole vehicle and directly generates a first display interface, which enables users to intuitively see which ECUs in the whole vehicle may need to be upgraded. This first display interface can be adapted to different vehicles, and the upgrade sequence area is a visual operation interface generated based on a graphics engine, which can provide users with an editable operation interface, making it the essential cornerstone for realizing the generation of upgrade links.

[0075] It is conceivable that users might want to visually understand the topological relationships between multiple ECUs in the vehicle. In some embodiments, the ECU list also includes topological relationship data for multiple ECUs; the upgrade method may further include: The system receives a second operation from the user based on the first display interface and displays a second display interface. The second display interface includes a topology diagram of m ECU topology components. The topology diagram of the m ECU topology components is used to characterize the topology relationship of the ECUs. The m ECU topology components in the second display interface do not support drag-and-drop or connection operations.

[0076] The first display interface mentioned above may include controls or menu options for viewing network topology. After the user clicks the "View Network Topology" control or menu option, a result such as... Figure 6 The topology diagram shown above is used to display the topology relationships of the ECUs in the vehicle. The topology diagram is in a "read-only" state, which can only be viewed by the user and cannot be edited. For example, it does not support drag-and-drop operations and connection operations.

[0077] In some embodiments, after obtaining the list of ECUs for the entire vehicle, a selection interface can be displayed, allowing users to choose to generate a first display interface or a second display interface based on the selection menu or controls in the selection interface.

[0078] This application embodiment generates a second display interface based on the user's second operation, enabling ECU topology components to be shared across different display interfaces. This reduces the user's development time for ECU topology components. Furthermore, the two different display interfaces are independent and isolated from each other, facilitating the user's comparison of the generated ECU topology component connection sequence diagram and topology relationship diagram. Based on the interdependencies between different ECUs displayed in the topology relationship diagram, a correct and coherent ECU upgrade link is generated.

[0079] In some embodiments, receiving a second operation from a user based on a first display interface and displaying a second display interface may include: Upon receiving a second operation from the user based on the first display interface, a preset display interface is obtained, wherein the preset display interface includes a preset topology diagram, wherein the topology diagram includes multiple initial ECU topology components, wherein each initial ECU topology component includes an ECU identifier; among the multiple initial ECU topology components, m ECU topology components including ECU identifiers are identified; the m ECU topology components are highlighted in the ECU topology components to obtain the second display interface.

[0080] After receiving the second operation, it can be displayed as follows: Figure 7 The preset display interface shown is as follows: Figure 7 The system includes a preset topology diagram. This preset topology diagram displays the topology relationships of multiple initial ECU topology components, where each initial ECU topology component corresponds to an actual ECU.

[0081] It's conceivable that for any given vehicle, some ECUs might not be included. Therefore, for the complete vehicle ECU list, we can identify m ECU topology components, including ECU identifiers, from multiple initial ECU topology components and highlight them, resulting in something like this. Figure 6 The second display interface shown.

[0082] Here, as Figure 6As shown, the ECU identifier can be used as a key field to associate and match the vehicle's ECU list with the initial ECU topology components. For successfully matched ECUs (i.e., those included in the vehicle), they are highlighted in the topology map of the second display interface, helping users quickly identify available ECUs for the current vehicle model. ECUs not included in the vehicle are grayed out in the topology map of the second display interface. This embodiment of the application obtains a preset display interface based on the user's second operation, matches the initial ECU topology components in the preset display interface with the vehicle's ECUs, determines m ECU topology components, and highlights them. This allows users to easily and intuitively see all ECUs present in the vehicle and the topology relationships between multiple ECUs, improving the user experience.

[0083] In some embodiments, based on the ECU upgrade link, controlling the ECU to upgrade to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade link may include: The system sends an upgrade command and the corresponding target version upgrade package to the first ECU in the ECU upgrade chain. After the first ECU is successfully upgraded, the system sends an upgrade command and the corresponding target version upgrade package to the next ECU in the ECU upgrade chain, until all ECUs in the ECU upgrade chain have been upgraded.

[0084] After determining the ECU upgrade path, an upgrade command and the corresponding target version upgrade package can be sent to the first ECU in the path. After the first ECU is upgraded, the upgrade command and the corresponding target version upgrade package can be sent to the next ECU. For example, first send the upgrade command and the corresponding target version upgrade package to the ECU at 0xAA in the 0xAA-0xBB-0xCC upgrade path. After the ECU at 0xAA is upgraded, send the upgrade command and the corresponding target version upgrade package to the next ECU at 0xBB.

[0085] Here, after the last ECU upgrade is completed, a notification message indicating that the upgrade is complete can be displayed on the screen so that the user can monitor the upgrade process.

[0086] This application embodiment maintains the dependency relationship between ECUs by waiting for the previous ECU to succeed before starting the next one. At the same time, it focuses on upgrading one ECU at a time, avoiding network bandwidth competition and resource congestion caused by multiple ECUs downloading upgrade packages at the same time and upgrading, thus improving the upgrade efficiency of ECUs.

[0087] Based on the same inventive concept, this application also provides an upgrade device for a vehicle electronic control unit (ECU).

[0088] In some embodiments, such as Figure 8As shown in the figure, this application embodiment provides an upgrade device for a vehicle ECU, which may include: The receiving module 801 is used to receive a first operation by the user based on the first display interface. The first operation includes a drag operation to drag n target ECU topology components from m ECU topology components in the first display interface to the upgrade order area in the first display interface, and a connection operation to connect the n target ECU topology components in the upgrade order area with preset start and end nodes. One ECU topology component corresponds to one ECU, m≥2, n≤m. The generation module 802 is used to generate an ECU topology component connection sequence diagram based on the first operation; The generation module 802 is also used to generate an ECU upgrade link based on the ECU topology component connection sequence diagram, wherein the ECU upgrade link represents the upgrade sequence relationship of n ECUs corresponding to n target ECU topology components; The upgrade module 803 is used to control the ECU to upgrade to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade link based on the ECU upgrade link.

[0089] This application embodiment receives a user's first operation based on a first display interface through a receiving module, and drags and connects n target ECU topology components to the upgrade sequence area through a generation module to obtain an ECU topology component connection sequence diagram. The generation module determines the corresponding ECU through the n target ECU topology components in the ECU topology component connection sequence diagram, and can generate ECU upgrade links based on multiple ECUs, realizing fast and visual generation of ECU upgrade links, improving user experience. The upgrade module controls the ECU to upgrade to the corresponding upgrade version according to the upgrade link, realizing a customizable upgrade process for ECUs and improving the upgrade efficiency of ECUs.

[0090] In some embodiments, the generation module can specifically be used for: Based on the preset first direction traversal ECU topology component connection sequence diagram of n target ECU topology components, determine the first target ECU topology component connected to the start node, and determine all second target ECU topology components connected between the first target ECU topology component and the end node; The first ECU is determined based on the first target ECU topology component, and the second ECU is determined based on each second target ECU topology component. An ECU upgrade path is generated based on the first ECU and the second ECU.

[0091] In some embodiments, the generation module can specifically be used for: Based on the first operation, an initial ECU topology component connection sequence diagram is generated; Receive user modification operations based on n target ECU topology components in the initial ECU topology component connection sequence diagram; Based on the modification operation, generate the ECU topology component connection sequence diagram. In some embodiments, the ECU topology component connection sequence diagram includes at least two sub-connection sequence diagrams, the ECU upgrade link includes at least two sub-upgrade links, and the generation module can specifically be used for: Based on a preset first direction traversal of at least two sub-connection sequence diagrams of n target ECU topology components, determine at least two first target ECU topology components connected to the start node, and for each first target ECU topology component, determine all second target ECU topology components connected between the first target ECU topology component and the end node; Based on at least two first target ECU topology components and a second target ECU topology component, at least two corresponding first ECUs and all second ECUs are determined respectively; Based on at least two first ECUs and all second ECUs, generate at least two sub-upgrade links; Based on the ECU upgrade chain, the control ECU is upgraded to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade chain, including: Based on at least two sub-upgrade links, control at least two first ECUs and all second ECUs to upgrade to the corresponding target version according to the upgrade order relationship indicated by at least two sub-upgrade links.

[0092] In some embodiments, the generation module can specifically be used for: Based on the positional relationship of at least two first target ECU topology components, determine the priority of each of the at least two first target ECU topology components. Based on priority and at least two sub-upgrade links, control at least two first ECUs and all second ECUs to upgrade to the corresponding target version according to the priority order and the upgrade order relationship indicated by at least two sub-upgrade links.

[0093] In some embodiments, the upgrade apparatus further includes a receiving module for: Obtain the ECU list for the entire vehicle, which includes m ECU identifiers; Based on m ECU identifiers, determine the corresponding m ECU topology components; The first display interface includes m ECU topology components and an upgrade sequence area, wherein the upgrade sequence area is a visual operation interface generated based on a preset graphics engine.

[0094] In some embodiments, the ECU list further includes topological relationship data of multiple ECUs; the receiving module is further configured to: The system receives a second operation from the user based on the first display interface and displays a second display interface. The second display interface includes a topology diagram of m ECU topology components. The topology diagram of the m ECU topology components is used to characterize the topology relationship of the ECUs. The m ECU topology components in the second display interface do not support drag-and-drop or connection operations.

[0095] In some embodiments, the receiving module may be specifically used for: Upon receiving a second operation from the user based on the first display interface, a preset display interface is obtained, wherein the preset display interface includes a preset topology diagram, wherein the topology diagram includes multiple initial ECU topology components, wherein an initial ECU topology component includes an ECU identifier. Among multiple initial ECU topology components, m ECU topology components, including ECU identifiers, are identified; In the ECU topology components, highlight m ECU topology components to obtain the second display interface.

[0096] In some embodiments, the upgrade module may specifically be used for: Send the upgrade command and the corresponding target version upgrade package to the first ECU in the ECU upgrade chain; After the first ECU is successfully upgraded, an upgrade command and the corresponding target version upgrade package are sent to the next ECU in the ECU upgrade chain, until all ECUs in the ECU upgrade chain have been upgraded.

[0097] The apparatus described above is used to implement the upgrade method of the corresponding vehicle electronic control unit (ECU) in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0098] Figure 9 A schematic diagram of the hardware structure of an electronic device is provided in the application embodiment.

[0099] The electronic device 900 may include a processor 901 and a memory 902 storing computer program instructions.

[0100] Specifically, the processor 901 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0101] Memory 902 may include mass storage for data or instructions. For example, and not limitingly, memory 902 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 902 may include removable or non-removable (or fixed) media. Where appropriate, memory 902 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 902 is non-volatile solid-state memory.

[0102] In a particular embodiment, memory 902 includes read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.

[0103] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to the first aspect of this application.

[0104] The processor 901 reads and executes computer program instructions stored in the memory 902 to implement any of the vehicle electronic control unit (ECU) upgrade methods described in the above embodiments.

[0105] In one example, the electronic device may also include a communication interface 903 and a bus 904. Wherein, for example... Figure 9 The processor 901, memory 902, and communication interface 903 are connected through bus 904 and complete communication with each other.

[0106] The communication interface 903 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0107] Bus 904 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 904 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0108] The electronic devices described above are used to implement the upgrade method of the corresponding vehicle electronic control unit (ECU) in any of the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0109] Furthermore, in conjunction with the upgrade method for the vehicle electronic control unit (ECU) in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the vehicle electronic control unit (ECU) upgrade methods in the above embodiments.

[0110] Furthermore, in conjunction with the upgrade method for the vehicle electronic control unit (ECU) in the above embodiments, this application embodiment can provide a computer program product to implement this method. When the instructions of this computer program product are executed by the processor of an electronic device, they implement any of the vehicle electronic control unit (ECU) upgrade methods in the above embodiments.

[0111] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this application (including the claims) is limited to these examples; within the framework of this application, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this application as described above, which are not provided in the details for the sake of brevity.

[0112] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0113] It should also be noted that the exemplary embodiments mentioned in this application describe methods or apparatuses based on a series of steps or devices. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0114] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0115] The above description is merely a specific embodiment of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the devices, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A method for upgrading a vehicle's electronic control unit (ECU), characterized in that, include: The system receives a first operation from a user based on a first display interface. The first operation includes a drag operation to drag n target ECU topology components from m ECU topology components in the first display interface to an upgrade order area in the first display interface, and a connection operation to connect the n target ECU topology components in the upgrade order area to a preset start node and end node. One ECU topology component corresponds to one ECU, m≥2, n≤m. Based on the first operation, an ECU topology component connection sequence diagram is generated; Based on the ECU topology component connection sequence diagram, an ECU upgrade link is generated, wherein the ECU upgrade link represents the upgrade sequence relationship of n ECUs corresponding to n target ECU topology components; Based on the ECU upgrade link, the ECU is controlled to upgrade to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade link.

2. The method for upgrading a vehicle electronic control unit (ECU) according to claim 1, characterized in that, Based on the ECU topology component connection sequence diagram, an ECU upgrade link is generated, including: Based on a preset first direction traversal of the n target ECU topology components of the ECU topology component connection sequence diagram, a first target ECU topology component connected to the start node is determined, and all second target ECU topology components connected between the first target ECU topology component and the end node are determined; The first ECU is determined based on the first target ECU topology component, and the second ECU is determined based on each of the second target ECU topology components. Based on the first ECU and the second ECU, the ECU upgrade link is generated.

3. The method for upgrading a vehicle electronic control unit (ECU) according to claim 1, characterized in that, The step of generating an ECU topology component connection sequence diagram based on the first operation includes: Based on the first operation, an initial ECU topology component connection sequence diagram is generated; Receive user modification operations based on n target ECU topology components in the initial ECU topology component connection sequence diagram; Based on the modification operation, a connection sequence diagram of the ECU topology components is generated.

4. The method for upgrading a vehicle electronic control unit (ECU) according to claim 2, characterized in that, The ECU topology component connection sequence diagram includes at least two sub-connection sequence diagrams, the ECU upgrade link includes at least two sub-upgrade links, and the generation of the ECU upgrade link based on the ECU topology component connection sequence diagram includes: Based on a preset first direction, traverse the n target ECU topology components of the at least two sub-connection sequence diagrams, determine at least two first target ECU topology components connected to the start node, and for each first target ECU topology component, determine all second target ECU topology components connected between the first target ECU topology component and the end node; Based on at least two first target ECU topology components and second target ECU topology components, at least two corresponding first ECUs and all second ECUs are determined respectively; Based on the at least two first ECUs and all second ECUs, at least two sub-upgrade links are generated; The step of controlling the ECU to upgrade to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade link, based on the ECU upgrade link, includes: Based on the at least two sub-upgrade links, control at least two first ECUs and all second ECUs to upgrade to the corresponding target version according to the upgrade order relationship indicated by the at least two sub-upgrade links.

5. The method for upgrading a vehicle electronic control unit (ECU) according to claim 4, characterized in that, The step of controlling at least two first ECUs and all second ECUs to upgrade to the corresponding target version according to the upgrade order indicated by the at least two sub-upgrade links includes: Based on the positional relationship of at least two first target ECU topology components, the priorities corresponding to at least two first target ECU topology components are determined respectively; Based on the priority and the at least two sub-upgrade links, control at least two first ECUs and all second ECUs to upgrade to the corresponding target version according to the priority order and the upgrade order relationship indicated by the at least two sub-upgrade links.

6. The method for upgrading a vehicle electronic control unit (ECU) according to claim 1, characterized in that, Before receiving the user's first operation based on a preset first display interface, the upgrade method further includes: Obtain the ECU list for the entire vehicle, wherein the ECU list includes m ECU identifiers; Based on the m ECU identifiers, determine the corresponding m ECU topology components; The first display interface includes m ECU topology components and the upgrade sequence area, wherein the upgrade sequence area is a visual operation interface generated based on a preset graphics engine.

7. The method for upgrading a vehicle electronic control unit (ECU) according to claim 6, characterized in that, The ECU list also includes topology data for multiple of the ECUs; The upgrade method also includes: The system receives a second operation from the user based on the first display interface and displays a second display interface. The second display interface includes a topology diagram of m ECU topology components. The topology diagram of the m ECU topology components is used to characterize the topology relationship of the ECU. The m ECU topology components in the second display interface do not support drag-and-drop or connection operations.

8. The method for upgrading a vehicle electronic control unit (ECU) according to claim 7, characterized in that, The step of receiving a second operation from the user based on the first display interface and displaying a second display interface includes: Upon receiving a second operation from the user based on the first display interface, a preset display interface is obtained, wherein the preset display interface includes a preset topology diagram, wherein the topology diagram includes multiple initial ECU topology components, wherein each initial ECU topology component includes an ECU identifier; Among the plurality of initial ECU topology components, m ECU topology components including the ECU identifier are identified; The m ECU topology components are highlighted in the ECU topology components to obtain the second display interface.

9. The method for upgrading a vehicle electronic control unit (ECU) according to claim 7, characterized in that, The step of controlling the ECU to upgrade to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade link, based on the ECU upgrade link, includes: Send an upgrade command and the corresponding target version upgrade package to the first ECU in the ECU upgrade chain; After the first ECU is successfully upgraded, an upgrade command and the corresponding target version upgrade package are sent to the next ECU in the ECU upgrade chain, until all ECUs in the ECU upgrade chain have been upgraded.

10. An upgrade device for a vehicle ECU, characterized in that, include: The receiving module is used to receive a first operation by the user based on the first display interface. The first operation includes a drag operation to drag n target ECU topology components from m ECU topology components in the first display interface to the upgrade order area in the first display interface, and a connection operation to connect the n target ECU topology components in the upgrade order area with preset start and end nodes. One ECU topology component corresponds to one ECU, m≥2, n≤m. The generation module is used to generate an ECU topology component connection sequence diagram based on the first operation; The generation module is also used to generate an ECU upgrade link based on the ECU topology component connection sequence diagram, wherein the ECU upgrade link represents the upgrade order relationship of n ECUs corresponding to n target ECU topology components; The upgrade module is used to control the ECU to upgrade to the corresponding target version according to the upgrade sequence indicated by the ECU upgrade link, based on the ECU upgrade link.

Images