Vehicle upgrading control method and device, equipment and medium

Abstract

The invention discloses a vehicle upgrading control method and device, equipment and a medium. The method comprises the following steps: sending a downloading request to a to-be-upgraded node through a main node; the node to be upgraded comprises at least one of a first controller which needs to be subjected to preprocessing operation and pre-installation operation, a second controller which needs to be subjected to preprocessing operation and does not need to be subjected to pre-installation operation, and a third controller which does not need to be subjected to preprocessing operation and pre-installation operation; according to the downloading request, carrying out at least one of downloading operation, preprocessing operation and pre-installation operation on the upgrading data packet through the to-be-upgraded node, and feeding back operation process information of the upgrading data packet to the main node; and when it is determined that the operation of the to-be-upgraded node on the upgrade data packet is completed, upgrading the to-be-upgraded node according to the type of the to-be-upgraded node through the main node, and receiving an upgrade result fed back by the to-be-upgraded node. According to the method and the device, the OTA upgrading efficiency under the heterogeneous architecture can be improved. The method can be widely applied to the technical field of vehicles.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a vehicle upgrade control method, device, equipment and medium. Background Technology

[0002] As automotive electronic and electrical architecture evolves towards EEA 3.0, vehicles are transitioning from traditional distributed control to centralized domain control architecture. During this process, the vehicle topology presents a complex situation of coexistence of Ethernet and CAN buses, and mixed deployment of heterogeneous controllers. These architectural differences lead to significant variations in onboard controller software updates, communication protocols, and resource allocation, especially in multi-core processors where different controller nodes have different response conditions to OTA upgrades.

[0003] In related technologies, when performing OTA upgrades on vehicles, a uniform upgrade process is often used for all controller nodes within the vehicle using the same strategy. However, in practical applications, it has been found that due to the different functional requirements of controller nodes with different networks and architectures, the strategies supported for upgrade processing also vary. Current upgrade solutions are prone to issues with flashing efficiency or compatibility, leading to reduced upgrade efficiency or affecting normal vehicle use and a poor user experience.

[0004] In summary, the problems with the relevant technologies urgently need to be addressed. Summary of the Invention

[0005] The purpose of this application is to at least partially solve one of the technical problems existing in the related art.

[0006] Therefore, one object of the embodiments of this application is to provide a vehicle upgrade control method, apparatus, device and medium.

[0007] To achieve the above-mentioned technical objectives, the technical solutions adopted in the embodiments of this application include: On one hand, embodiments of this application provide a vehicle upgrade control method, the method comprising: The master node sends a download request to the node to be upgraded; wherein the node to be upgraded includes at least one of the following: a first controller that requires preprocessing and pre-installation operations, a second controller that requires preprocessing but does not require pre-installation operations, and a third controller that does not require preprocessing and pre-installation operations. According to the download request, at least one of the following operations is performed on the upgrade data package through the node to be upgraded: download operation, preprocessing operation, and pre-installation operation, and the operation process information of the upgrade data package is fed back to the master node. Once it is determined that the node to be upgraded has completed its operation on the upgrade data packet, the master node performs the upgrade process on the node to be upgraded according to its type, and receives the upgrade result from the node to be upgraded.

[0008] In addition, the vehicle upgrade control method according to the above embodiments of this application may also have the following additional technical features: Furthermore, in one embodiment of this application, the step of performing at least one of the following operations—downloading, preprocessing, and pre-installing—on the upgrade data package through the node to be upgraded, and feeding back the upgrade data package operation flow information to the master node, includes: If the node to be upgraded is the first controller, the upgrade data package is downloaded from the cloud server through the node to be upgraded, and the download progress information of the upgrade data package is fed back to the master node; The upgrade data packet is preprocessed by the node to be upgraded, and the preprocessing result of the upgrade data packet is fed back to the master node; The upgrade data package is pre-installed through the node to be upgraded, and the pre-installation result of the upgrade data package is fed back to the master node.

[0009] Furthermore, in one embodiment of this application, the upgrade process performed by the master node according to the type of the node to be upgraded includes: The master node sends a segmentation command to the node to be upgraded in order to perform an upgrade process on the node to be upgraded.

[0010] Furthermore, in one embodiment of this application, the step of performing at least one of the following operations—downloading, preprocessing, and pre-installing—on the upgrade data package through the node to be upgraded, and feeding back the upgrade data package operation flow information to the master node, includes: If the node to be upgraded is the second controller, the upgrade data package is downloaded from the cloud server through the node to be upgraded, and the download progress information of the upgrade data package is fed back to the master node; The node to be upgraded performs preprocessing operations on the upgrade data packet and feeds back the preprocessing results of the upgrade data packet to the master node.

[0011] Furthermore, in one embodiment of this application, the upgrade process performed by the master node according to the type of the node to be upgraded includes: The master node sends an upgrade command to the node to be upgraded to execute a complete upgrade task, thereby performing an upgrade process on the node to be upgraded.

[0012] Furthermore, in one embodiment of this application, the step of performing at least one of the following operations—downloading, preprocessing, and pre-installing—on the upgrade data package through the node to be upgraded, and feeding back the upgrade data package operation flow information to the master node, includes: If the node to be upgraded is the third controller, the upgrade data package is downloaded from the cloud server through the node to be upgraded, and the download progress information of the upgrade data package is fed back to the master node.

[0013] Furthermore, in one embodiment of this application, the upgrade process performed by the master node according to the type of the node to be upgraded includes: The master node sends preprocessing instructions to the node to be upgraded. The upgrade data packet is preprocessed by the node to be upgraded, and the preprocessing result of the upgrade data packet is fed back to the master node; The master node sends an upgrade command to the node to be upgraded to execute a complete upgrade task, thereby performing an upgrade process on the node to be upgraded.

[0014] On the other hand, embodiments of this application provide a vehicle upgrade control device, the device comprising: The sending unit is used to send a download request to the node to be upgraded through the master node; wherein the node to be upgraded includes at least one of the following: a first controller that requires preprocessing and pre-installation operations, a second controller that requires preprocessing operations but does not require pre-installation operations, and a third controller that does not require preprocessing and pre-installation operations. The download unit is used to perform at least one of the following operations on the upgrade data package through the node to be upgraded, namely download operation, preprocessing operation and pre-installation operation, according to the download request, and to feed back the operation process information of the upgrade data package to the master node; The processing unit is configured to, when it is determined that the node to be upgraded has completed its operation on the upgrade data packet, perform upgrade processing on the node to be upgraded according to the type of the node to be upgraded through the master node, and receive the upgrade result fed back by the node to be upgraded.

[0015] On the other hand, embodiments of this application provide an electronic device, including: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the vehicle upgrade control method described above.

[0016] On the other hand, embodiments of this application also provide a computer-readable storage medium storing a processor-executable program, which, when executed by a processor, is used to implement the above-described vehicle upgrade control method.

[0017] The advantages and beneficial effects of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application: This application discloses a vehicle upgrade control method, apparatus, device, and medium. A master node sends a download request to a node to be upgraded. The node to be upgraded includes at least one of the following: a first controller requiring pre-processing and pre-installation operations; a second controller requiring pre-processing but not pre-installation operations; and a third controller not requiring pre-processing and pre-installation operations. Based on the download request, the node to be upgraded performs at least one of the following operations on the upgrade data packet: download, pre-processing, and pre-installation, and feeds back the operation flow information of the upgrade data packet to the master node. When it is determined that the operation on the upgrade data packet by the node to be upgraded is completed, the master node performs upgrade processing on the node to be upgraded according to its type and receives the upgrade result fed back by the node to be upgraded. The technical solution of this application can achieve differentiated upgrade process management by intelligently scheduling nodes to be upgraded (including controllers of different types) through the master node. It dynamically allocates download, pre-processing, and pre-installation tasks according to the node type and provides real-time feedback on the operation status. The master node coordinates the upgrade execution, which can significantly improve the efficiency and reliability of OTA upgrades under heterogeneous architectures. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the following description is provided with accompanying drawings of the relevant technical solutions in the embodiments of this application or the prior art. It should be understood that the accompanying drawings described below are only for the purpose of clearly illustrating some embodiments of the technical solutions in this application. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0019] Figure 1 This is a schematic diagram illustrating the implementation environment of a vehicle upgrade control method provided in this application embodiment; Figure 2 This is a flowchart illustrating a vehicle upgrade control method provided in an embodiment of this application; Figure 3 This is a schematic diagram of an upgrade process for a node to be upgraded, provided in an embodiment of this application. Figure 4 This is a schematic diagram of information interaction during a vehicle upgrade process provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a vehicle upgrade control device provided in the embodiments of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0020] The present application will be further described below with reference to the accompanying drawings and specific embodiments. The described embodiments should not be considered as limitations on the present application, and all other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of the present application.

[0021] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0022] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0023] As automotive electronic and electrical architecture evolves towards EEA 3.0, vehicles are transitioning from traditional distributed control to centralized domain control architecture. During this process, the vehicle topology presents a complex situation of coexistence of Ethernet and CAN buses, and mixed deployment of heterogeneous controllers. These architectural differences lead to significant variations in onboard controller software updates, communication protocols, and resource allocation, especially in multi-core processors where different controller nodes have different response conditions to OTA upgrades.

[0024] In related technologies, when performing OTA upgrades on vehicles, a uniform upgrade process is often used for all controller nodes within the vehicle using the same strategy. However, in practical applications, it has been found that due to the different functional requirements of controller nodes with different networks and architectures, the strategies supported for upgrade processing also vary. Current upgrade solutions are prone to issues with flashing efficiency or compatibility, leading to reduced upgrade efficiency or affecting normal vehicle use and a poor user experience.

[0025] In view of this, this application provides a vehicle upgrade control method, in which a master node sends a download request to a node to be upgraded; wherein the node to be upgraded includes at least one of a first controller that requires preprocessing and pre-installation operations, a second controller that requires preprocessing but not pre-installation operations, and a third controller that does not require preprocessing and pre-installation operations; according to the download request, the node to be upgraded performs at least one of downloading, preprocessing, and pre-installation operations on the upgrade data package, and feeds back the operation process information of the upgrade data package to the master node; when it is determined that the operation of the upgrade data package by the node to be upgraded is completed, the master node performs upgrade processing on the node to be upgraded according to the type of the node to be upgraded, and receives the upgrade result fed back by the node to be upgraded. The technical solution of this application can realize differentiated upgrade process management by intelligently scheduling the nodes to be upgraded (including different types of controllers) by the master node, dynamically allocate download, preprocessing, and pre-installation tasks according to the node type, and provide real-time feedback on the operation status, and the master node uniformly coordinates the upgrade execution, which can significantly improve the efficiency and reliability of OTA upgrades under heterogeneous architecture.

[0026] Please refer to Figure 1 , Figure 1 This diagram illustrates an implementation environment for a vehicle upgrade control method provided in this embodiment. In this environment, the main hardware and software components include a vehicle 110 and a backend server 120. The vehicle 110 and the backend server 120 are connected. The vehicle upgrade control method provided in this embodiment can be executed independently on the vehicle 110 side or based on data interaction between the vehicle 110 and the backend server 120. The vehicle 110 can be any type of vehicle; the backend server 120 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0027] Vehicle 110 and backend server 120 can establish a communication connection via a wireless or wired network. This wireless or wired network uses standard communication technologies and / or protocols. The network can be the Internet or any other network, including but not limited to any combination of Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), mobile, wired or wireless networks, private networks, or virtual private networks.

[0028] Of course, this is understandable. Figure 1 The implementation environment described in this application is only one of the optional application scenarios for the vehicle upgrade control method provided in this embodiment. The actual application is not fixed. Figure 1 The software and hardware environment shown.

[0029] Below, in conjunction with the aforementioned description of the implementation environment, a vehicle upgrade control method provided in the embodiments of this application will be introduced and explained.

[0030] Please refer to Figure 2 , Figure 2 This is a schematic diagram of a vehicle upgrade control method provided in an embodiment of this application. The vehicle upgrade control method includes, but is not limited to: Step 210: Send a download request to the node to be upgraded through the master node; wherein the node to be upgraded includes at least one of a first controller that requires preprocessing and pre-installation operations, a second controller that requires preprocessing but does not require pre-installation operations, and a third controller that does not require preprocessing and pre-installation operations. Step 220: According to the download request, perform at least one of the following operations on the upgrade data package through the node to be upgraded: download operation, preprocessing operation, and pre-installation operation, and feed back the operation process information of the upgrade data package to the master node; Step 230: When it is determined that the node to be upgraded has completed the operation of the upgrade data packet, the master node performs the upgrade process on the node to be upgraded according to the type of the node to be upgraded, and receives the upgrade result fed back by the node to be upgraded.

[0031] This application provides a vehicle upgrade control method. This method can intelligently schedule nodes to be upgraded (including different types of controllers) through the master node to achieve differentiated upgrade process management. It can dynamically allocate download, preprocessing and pre-installation tasks according to the node type and provide real-time feedback on the operation status. The master node can uniformly coordinate the upgrade execution, which can significantly improve the efficiency and reliability of OTA upgrades under heterogeneous architecture.

[0032] It is readily understood by those skilled in the art that there are various types of controllers in vehicles. The vehicle upgrade control method in this application can be categorized into three types based on the upgrade process: One type is the controller that requires independently downloading the relevant upgrade data package and performing preprocessing and pre-installation operations. This type of controller is often A / B-side (i.e., the controller's internal storage area is divided into two partitions, A and B, each capable of independently storing a complete software version, forming a redundant structure that serves as a backup) and has a long operating system flashing time. For example, it might be a cockpit domain controller. In this application embodiment, this is referred to as the first controller. The other type is the controller that requires independently downloading the relevant upgrade data package and performing preprocessing operations, but does not require pre-installation operations. This type of controller may not be able to perform A / B-side upgrades, and the upgrade time is relatively short and controllable (e.g., within 10 minutes). In this application embodiment, this is referred to as the second controller. In addition, there is another type of controller that requires independent download of the relevant upgrade data package, but does not require preprocessing or pre-installation operations. This type of controller is often a controller with high CPU requirements when working. If preprocessing or pre-installation operations are performed during runtime, it may affect the working state of the controller, such as the intelligent driving domain controller. In this embodiment, this type of controller is referred to as the third controller.

[0033] This application provides a vehicle upgrade control method applicable to OTA upgrade scenarios in an Electrical and Electronic Architecture (EEA) 3.0 environment. This method coordinates the differentiated upgrade processes of the nodes to be upgraded through a master node (such as a central gateway or domain controller), ensuring that various controllers efficiently complete software updates while meeting their own functional constraints. The following detailed description, in conjunction with specific implementation methods, illustrates this method: In step 210, the master node can send a download request to the node to be upgraded according to a predefined upgrade strategy. As described above, in this embodiment, the node to be upgraded may include three types of controllers: the first controller (e.g., the cockpit domain controller): adopts an AB-side architecture and requires preprocessing operations (e.g., data decompression, signature verification) and pre-installation operations (e.g., partition switching preparation); the second controller (e.g., the body controller): only requires preprocessing, not pre-installation, and has a shorter upgrade time; the third controller (e.g., the intelligent driving domain controller): only needs to download the upgrade package, and preprocessing and pre-installation operations are prohibited to avoid CPU resource consumption during runtime.

[0034] The various controllers mentioned above can be distinguished by relevant flag bits. For example, as shown in Table 1, in the embodiments of this application, the functions that various controllers can perform can be distinguished by flag bits.

[0035] Table 1

[0036] In this embodiment of the application, the three flag bits in Table 1 can be arbitrarily combined based on certain rules (the pre-installation function and the pre-processing function must be implemented based on the independent download function) for the OTA cloud or vehicle terminal to design the controller's attributes. The OTA server makes targeted designs for the task distribution, progress writing and other processes for different controller attributes.

[0037] In step 210, when the master node sends a download request, it can carry metadata of the upgrade data packet (such as version number, checksum, target storage partition, etc.) and specify the operation permissions of each controller (such as whether background preprocessing or pre-installation is allowed).

[0038] In step 220, each node to be upgraded can perform differentiated operations and corresponding tasks according to its own type after receiving the download request, and report its status to the master node in real time. In this embodiment, the node to be upgraded can perform at least one of the download operation, preprocessing operation and pre-installation operation, and record its reported status as operation process information.

[0039] For example, in this embodiment, the download progress can be divided into three parts: upgrade package download, upgrade package preprocessing, and upgrade package pre-installation. Different nodes to be upgraded require different operations; therefore, each node can provide different operation flow information, which is not limited in this application.

[0040] In step 230, the master node coordinates the final upgrade execution. Specifically, after confirming that the nodes to be upgraded have completed the preliminary operations, the master node triggers the final upgrade operation according to the controller type. For example, for the first controller, it can switch to a new partition (e.g., from partition A to partition B) and verify system integrity after restarting. If the switch is successful, the upgrade is complete; if the switch fails, it automatically reverts to the old version partition. For the second controller, the master node can initiate the installation operation; successful installation indicates the upgrade is complete. For the third controller, the master node controls it to perform preprocessing and installation operations when the vehicle is in a safe state (e.g., the engine is off), thereby completing the upgrade task. After the upgrade is complete, each node to be upgraded can report its final status to the master node, which summarizes the results and generates an upgrade report. If an upgrade fails for a node, the master node can initiate a retry or rollback process to ensure system reliability.

[0041] It is understood that the vehicle upgrade control method provided in this application embodiment sends a download request to the node to be upgraded through a master node. The node to be upgraded includes at least one of the following: a first controller requiring preprocessing and pre-installation operations; a second controller requiring preprocessing but not pre-installation operations; and a third controller not requiring preprocessing and pre-installation operations. Based on the download request, the node to be upgraded performs at least one of downloading, preprocessing, and pre-installation operations on the upgrade data package and feeds back the operation flow information of the upgrade data package to the master node. When it is determined that the operation of the upgrade data package by the node to be upgraded is completed, the master node performs upgrade processing on the node to be upgraded according to its type and receives the upgrade result fed back by the node to be upgraded. This method can achieve differentiated upgrade process management by intelligently scheduling the nodes to be upgraded (including controllers of different types) through the master node, dynamically allocating download, preprocessing, and pre-installation tasks according to the node type, and providing real-time feedback on the operation status. The master node uniformly coordinates the upgrade execution, which can significantly improve the efficiency and reliability of OTA upgrades under heterogeneous architectures.

[0042] In some embodiments, the step of performing at least one of downloading, preprocessing, and pre-installing operations on the upgrade data package through the node to be upgraded, and feeding back the upgrade data package operation flow information to the master node, includes: If the node to be upgraded is the first controller, the upgrade data package is downloaded from the cloud server through the node to be upgraded, and the download progress information of the upgrade data package is fed back to the master node; The upgrade data packet is preprocessed by the node to be upgraded, and the preprocessing result of the upgrade data packet is fed back to the master node; The upgrade data package is pre-installed through the node to be upgraded, and the pre-installation result of the upgrade data package is fed back to the master node.

[0043] The upgrade process, performed by the master node according to the type of the node to be upgraded, includes: The master node sends a segmentation command to the node to be upgraded in order to perform an upgrade process on the node to be upgraded.

[0044] In some embodiments, the step of performing at least one of downloading, preprocessing, and pre-installing operations on the upgrade data package through the node to be upgraded, and feeding back the upgrade data package operation flow information to the master node, includes: If the node to be upgraded is the second controller, the upgrade data package is downloaded from the cloud server through the node to be upgraded, and the download progress information of the upgrade data package is fed back to the master node; The node to be upgraded performs preprocessing operations on the upgrade data packet and feeds back the preprocessing results of the upgrade data packet to the master node.

[0045] The upgrade process, performed by the master node according to the type of the node to be upgraded, includes: The master node sends an upgrade command to the node to be upgraded to execute a complete upgrade task, thereby performing an upgrade process on the node to be upgraded.

[0046] In some embodiments, the step of performing at least one of downloading, preprocessing, and pre-installing operations on the upgrade data package through the node to be upgraded, and feeding back the upgrade data package operation flow information to the master node, includes: If the node to be upgraded is the third controller, the upgrade data package is downloaded from the cloud server through the node to be upgraded, and the download progress information of the upgrade data package is fed back to the master node.

[0047] The upgrade process, performed by the master node according to the type of the node to be upgraded, includes: The master node sends preprocessing instructions to the node to be upgraded. The upgrade data packet is preprocessed by the node to be upgraded, and the preprocessing result of the upgrade data packet is fed back to the master node; The master node sends an upgrade command to the node to be upgraded to execute a complete upgrade task, thereby performing an upgrade process on the node to be upgraded.

[0048] Specifically, please refer to Figure 3 and Figure 4 , Figure 3 This illustration shows a schematic diagram of an upgrade process for a node to be upgraded, as provided in an embodiment of this application. Figure 4 This illustration shows an information interaction diagram of a vehicle upgrade process provided in an embodiment of this application.

[0049] like Figure 3 As shown in this embodiment, the relevant processes in the vehicle upgrade process are divided into multiple parts. Different types of controllers correspond to different processes, and their main features include: Independent download process: Unlike the traditional OTA upgrade process where the upgrade package is downloaded to the master node and then distributed during the upgrade, the independent download process transmits the download link, encryption key, and other information of the OTA upgrade package to the corresponding node, which then performs the download operation. This saves the transmission time of the master node in distributing the upgrade package and can effectively improve the upgrade efficiency for controllers with large upgrade packages.

[0050] For the pre-installation process of some controllers: Under the premise that the controller downloads independently and the hardware chip has the ability to upgrade the system by AB, after the controller downloads the upgrade package independently, the version upgrade is immediately performed on the backup side. This process supports interrupted and resumed installation. By moving the installation process to the independent download process, efficiency is improved. The download process is imperceptible to the user. After the user chooses to upgrade immediately or schedule an upgrade, when the OTA is actually executed, the aspect restart action is performed through diagnostic commands. This method can effectively shorten the time that the user perceives during the OTA upgrade.

[0051] For some controllers, the post-processing process is improved by moving the upgrade package processing flow to the OTA upgrade process. During the vehicle download process, the controller may not be able to allocate enough CPU resources for the controller upgrade package to perform decryption and decompression operations. If this is performed during the download, it may increase the download time and increase the probability of errors. During the OTA upgrade process, most CPU resources are released, and file processing can be quickly achieved by adjusting the data processing timing.

[0052] like Figure 4 As shown in this embodiment, when performing an OTA upgrade on the node to be upgraded, the master node can first synchronize the OTA upgrade task with the OTA cloud server, and then send a download request to the node to be upgraded, and the node to be upgraded will reply with a response.

[0053] Next, the node to be upgraded requests the upgrade data package from the cloud server. The master node obtains the download progress information from the node to be upgraded. In this embodiment, the download progress is divided into three parts: upgrade package download, upgrade package preprocessing, and upgrade package pre-installation. The controller can summarize the download progress information based on the processing status of each part and feed it back to the master node. Specifically, in this embodiment, the download progress information can be allocated according to the proportion of the actual estimated time and weighted according to the actual proportion. For example, for the first controller, its download progress can be obtained by weighting the progress of upgrade package download, upgrade package preprocessing, and upgrade package pre-installation; for the second controller, its download progress can be obtained by weighting the progress of upgrade package download and upgrade package preprocessing; and for the third controller, its download progress can be obtained based on the progress of upgrade package download.

[0054] Specifically, in this embodiment, the progress of the preprocessing and pre-installation stages can be fed back to the master node by the independently downloading controller based on the current upgrade package size, controller CPU utilization, and resource allocation, thereby ensuring a smoother OTA upgrade process. In this embodiment, the someip service can be used to synchronize information such as the upgrade package installation progress, and its data design scheme is shown in Table 2: Table 2

[0055] in: When PS_DownloadStage_enum = 2, PS_TotalLength_uint and PS_DownloadedLenth_uint are valid, and the overall download progress is calculated based on this information; When PS_DownloadStage_enum = 3~6, ​​the PS_DataProcess_uint data is valid; When PS_DownloadStage_enum = 7, the PS_InstallationProgress_uint data is valid.

[0056] In this embodiment, the OTA cloud server can be designed and adapted to add controller upgrade attributes that are consistent with the detailed classification identifier of the controller. The OTA cloud server designs relevant fields in the cloud for the pre-installation and post-processing processes, realizes the design and synchronization of controller attributes, and distinguishes controllers according to controller categories. The controller identifier is synchronized to the vehicle end through vehicle-cloud OMA communication, and the vehicle end performs OTA upgrades by interacting with the controller nodes according to the vehicle-cloud synchronization information.

[0057] In this embodiment, the first controller can preprocess the downloaded upgrade data package during the download process and report the preprocessing result back to the master node. If preprocessing fails, the upgrade data package can be downloaded again. After confirming that the first controller has completed preprocessing, the master node can grant pre-installation permission. The first controller responds with a default response, then pre-installs the upgrade data package and reports the pre-installation result.

[0058] The second controller can preprocess the downloaded upgrade data package during the download process and report the preprocessing results back to the master node. Similarly, if preprocessing fails, the upgrade data package can be downloaded again. The third controller can simply perform the download operation and then wait for the master node's upgrade command.

[0059] After the node to be upgraded completes the download task, the master node can perform the upgrade process according to the type of the node. Specifically, for the first controller, the master node can send an aspect command, the first controller executes the aspect action, and then can send the upgrade result back to the master node.

[0060] For the second controller, the master node can send an upgrade command to perform a complete upgrade task, thus upgrading the second controller. After the upgrade is complete, the second controller can report the upgrade result back to the master node. For the third controller, the master node can send a preprocessing command to it. The third controller performs preprocessing operations on the upgrade data packet and reports the preprocessing result back to the master node. If preprocessing fails, the upgrade data packet can be downloaded again. After preprocessing is complete, the master node sends an upgrade command to the third controller to perform a complete upgrade task, thus upgrading the third controller.

[0061] In this embodiment of the application, after the upgrade is completed, each node to be upgraded can report the software version number to the master node. Based on the software version number, the master node can determine whether the upgrade of the node to be upgraded was successful.

[0062] Reference Figure 5 This application also provides a vehicle upgrade control device, including: Sending unit 510 is used to send a download request to the node to be upgraded through the master node; wherein, the node to be upgraded includes at least one of a first controller that requires preprocessing and pre-installation operations, a second controller that requires preprocessing operations but does not require pre-installation operations, and a third controller that does not require preprocessing and pre-installation operations. Download unit 520 is used to perform at least one of download operation, preprocessing operation and pre-installation operation on upgrade data package through the node to be upgraded according to the download request, and to feed back the operation process information of upgrade data package to the master node. The processing unit 530 is configured to, when it is determined that the node to be upgraded has completed its operation on the upgrade data packet, perform upgrade processing on the node to be upgraded according to the type of the node to be upgraded through the master node, and receive the upgrade result fed back by the node to be upgraded.

[0063] It is understood that the content of the above method embodiments is applicable to the present device embodiments. The specific functions implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0064] Reference Figure 6 This application provides an electronic device, including: At least one processor 610; At least one memory 620 is used to store at least one program; When at least one program is executed by at least one processor 610, the at least one processor 610 implements the vehicle upgrade control method described above.

[0065] Similarly, the content of the above method embodiments is applicable to the embodiments of this electronic device. The specific functions implemented by the embodiments of this electronic device are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0066] This application embodiment also provides a computer-readable storage medium storing a program executable by a processor 610, which, when executed by the processor 610, is used to perform the above-described vehicle upgrade control method.

[0067] Similarly, the content of the above method embodiments is applicable to the present computer-readable storage medium embodiments. The specific functions implemented by the present computer-readable storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0068] In some alternative embodiments, the functions / operations mentioned in the block diagrams may not occur in the order shown in the operation diagrams. For example, depending on the functions / operations involved, two consecutively shown blocks may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order. Furthermore, the embodiments presented and described in the flowcharts of this application are provided by way of example to provide a more comprehensive understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed and sub-operations described as part of a larger operation are executed independently.

[0069] Furthermore, although this application is described in the context of functional modules, it should be understood that, unless otherwise stated to the contrary, one or more of the functions and / or features may be integrated into a single physical device and / or software module, or one or more functions and / or features may be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding this application. Rather, given the properties, functions, and internal relationships of the various functional modules in the apparatus disclosed herein, the actual implementation of the module will be understood within the scope of conventional technology for an engineer. Therefore, those skilled in the art can implement the application set forth in the claims using ordinary techniques without excessive experimentation. It is also understood that the specific concepts disclosed are merely illustrative and not intended to limit the scope of this application, which is determined by the full scope of the appended claims and their equivalents.

[0070] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0071] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-including system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0072] More specific examples (a non-exhaustive list) of computer-readable media include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0073] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0074] In the foregoing description of this specification, the references to terms such as "one embodiment," "another embodiment," or "some embodiments," etc., indicate that a specific feature, structure, material, or characteristic described in connection with an embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0075] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

[0076] The above is a detailed description of the preferred embodiments of this application, but this application is not limited to the embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application, and these equivalent modifications or substitutions are all included within the scope defined by the claims of this application.

Claims

1. A vehicle upgrade control method, characterized in that, The method includes: The master node sends a download request to the node to be upgraded; wherein the node to be upgraded includes at least one of the following: a first controller that requires preprocessing and pre-installation operations, a second controller that requires preprocessing but does not require pre-installation operations, and a third controller that does not require preprocessing and pre-installation operations. According to the download request, at least one of the following operations is performed on the upgrade data package through the node to be upgraded: download operation, preprocessing operation, and pre-installation operation, and the operation process information of the upgrade data package is fed back to the master node. Once it is determined that the node to be upgraded has completed its operation on the upgrade data packet, the master node performs the upgrade process on the node to be upgraded according to its type, and receives the upgrade result from the node to be upgraded.

2. The vehicle upgrade control method according to claim 1, characterized in that, The process of performing at least one of the following operations—downloading, preprocessing, and pre-installing—on the upgrade data package through the node to be upgraded, and then feeding back the upgrade data package operation flow information to the master node, includes: If the node to be upgraded is the first controller, the upgrade data package is downloaded from the cloud server through the node to be upgraded, and the download progress information of the upgrade data package is fed back to the master node; The upgrade data packet is preprocessed by the node to be upgraded, and the preprocessing result of the upgrade data packet is fed back to the master node; The upgrade data package is pre-installed through the node to be upgraded, and the pre-installation result of the upgrade data package is fed back to the master node.

3. The vehicle upgrade control method according to claim 2, characterized in that, The upgrade process, performed by the master node according to the type of the node to be upgraded, includes: The master node sends a segmentation command to the node to be upgraded in order to perform an upgrade process on the node to be upgraded.

4. The vehicle upgrade control method according to claim 1, characterized in that, The process of performing at least one of the following operations—downloading, preprocessing, and pre-installing—on the upgrade data package through the node to be upgraded, and then feeding back the upgrade data package operation flow information to the master node, includes: If the node to be upgraded is the second controller, the upgrade data package is downloaded from the cloud server through the node to be upgraded, and the download progress information of the upgrade data package is fed back to the master node; The node to be upgraded performs preprocessing operations on the upgrade data packet and feeds back the preprocessing results of the upgrade data packet to the master node.

5. The vehicle upgrade control method according to claim 4, characterized in that, The upgrade process, performed by the master node according to the type of the node to be upgraded, includes: The master node sends an upgrade command to the node to be upgraded to execute a complete upgrade task, thereby performing an upgrade process on the node to be upgraded.

6. The vehicle upgrade control method according to claim 1, characterized in that, The process of performing at least one of the following operations—downloading, preprocessing, and pre-installing—on the upgrade data package through the node to be upgraded, and then feeding back the upgrade data package operation flow information to the master node, includes: If the node to be upgraded is the third controller, the upgrade data package is downloaded from the cloud server through the node to be upgraded, and the download progress information of the upgrade data package is fed back to the master node.

7. A vehicle upgrade control method according to claim 6, characterized in that, The upgrade process, performed by the master node according to the type of the node to be upgraded, includes: The master node sends preprocessing instructions to the node to be upgraded. The upgrade data packet is preprocessed by the node to be upgraded, and the preprocessing result of the upgrade data packet is fed back to the master node; The master node sends an upgrade command to the node to be upgraded to execute a complete upgrade task, thereby performing an upgrade process on the node to be upgraded.

8. A vehicle upgrade control device, characterized in that, The device includes: The sending unit is used to send a download request to the node to be upgraded through the master node; wherein the node to be upgraded includes at least one of the following: a first controller that requires preprocessing and pre-installation operations, a second controller that requires preprocessing operations but does not require pre-installation operations, and a third controller that does not require preprocessing and pre-installation operations. The download unit is used to perform at least one of the following operations on the upgrade data package through the node to be upgraded, namely download operation, preprocessing operation and pre-installation operation, according to the download request, and to feed back the operation process information of the upgrade data package to the master node; The processing unit is configured to, when it is determined that the node to be upgraded has completed its operation on the upgrade data packet, perform upgrade processing on the node to be upgraded according to the type of the node to be upgraded through the master node, and receive the upgrade result fed back by the node to be upgraded.

9. An electronic device, characterized in that, include: At least one processor; At least one memory for storing at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements a vehicle upgrade control method as described in any one of claims 1-7.

10. A computer-readable storage medium storing a processor-executable program, characterized in that, The processor-executable program, when executed by the processor, is used to implement a vehicle upgrade control method as described in any one of claims 1-7.

Images