Distributed OTA upgrading method and system for intelligent networked automobile

Abstract

The invention discloses a distributed OTA upgrading method and system for an intelligent networked automobile, and belongs to the technical field of intelligent networked automobiles, and the method comprises the steps: when a vehicle has software to be upgraded, an OTA cloud issues a software upgrading task of each software to be upgraded to an OTA slave node of a group where each software to be upgraded is located; after receiving the software upgrading task, the OTA slave node downloads the upgrading packages of all the software to be upgraded in the group where the OTA slave node is located from the OTA cloud end, and all the software to be upgraded in the group where the OTA slave node is located is upgraded through the downloaded upgrading packages. The load and space requirements on the OTA main node are reduced, and the upgrading success rate, the upgrading stability and the upgrading efficiency of the whole vehicle OTA upgrading are improved.

Description

Technical Field

[0001] The present application relates to the technical field of intelligent connected vehicles, and in particular to a distributed OTA upgrade method and system for intelligent connected vehicles. Background Art

[0002] OTA (Over the Air Update), also known as remote air download technology, is a technology that changes vehicle performance, adds functions, or fixes system security vulnerabilities by updating vehicle controller firmware and software packages online. With the vigorous development of smart connected vehicles, OTA upgrade function has become a standard configuration of smart connected vehicles, allowing OEMs to quickly respond to user needs, improve user experience, and keep consumers using it frequently.

[0003] The OTA upgrade of the whole vehicle for intelligent connected vehicles with centralized domain controller architecture involves various functional domains of the vehicle as well as the controllers and sensors within the domains. Usually, the OTA master node (master) deployed on the central gateway coordinates the OTA slave nodes (slave) to complete the OTA upgrade of the whole vehicle. OTA slave nodes are divided into self-upgrade nodes (various functional domain controllers) and non-self-upgrade nodes (controllers and sensors). The current technical solution is to download and distribute the upgrade packages of each OTA slave node through the OTA master node to complete the OTA upgrade of the whole vehicle.

[0004] The upgrade packages of self-upgrade nodes are generally in the order of GB. When the existing technical solution is used to perform OTA upgrade of the entire vehicle, the upgrade packages of all the vehicle's self-upgrade nodes and non-self-upgrade nodes are downloaded and distributed by the OTA master node, which poses great challenges to the load and space requirements of the OTA master node, as well as the upgrade success rate, upgrade stability and upgrade efficiency of the entire vehicle OTA upgrade. Summary of the invention

[0005] The embodiment of the present application provides a distributed OTA upgrade method and system for intelligent connected vehicles, which can effectively address the KPI challenges such as upgrade success rate, upgrade stability and upgrade efficiency faced during vehicle OTA upgrade. The technical solution is as follows:

[0006] On the one hand, a distributed OTA upgrade method for an intelligent connected vehicle is provided, including:

[0007] When there is software to be upgraded in the vehicle, the OTA cloud sends the software upgrade tasks of each software to be upgraded to the OTA slave node of the group where each software to be upgraded is located;

[0008] After receiving the software upgrade task, the OTA slave node downloads the upgrade packages of all the software to be upgraded in the group where the OTA slave node is located from the OTA cloud, and uses the downloaded upgrade packages to upgrade all the software to be upgraded in the group where the OTA slave node is located.

[0009] In some embodiments, after the OTA slave node completes the software upgrade in the group to which the slave node belongs, the upgrade result is sent to the OTA cloud.

[0010] In some embodiments, software version information of each software in the group to which each OTA slave node belongs is obtained through each OTA slave node;

[0011] Each OTA slave node sends the acquired software version information to the OTA cloud;

[0012] The OTA cloud determines whether the vehicle has software that needs to be upgraded based on the received software version information.

[0013] In some embodiments, each OTA slave node sends the acquired software version information to the OTA cloud through the OTA master node;

[0014] The OTA slave node downloads the upgrade packages of all the software to be upgraded in the slave node from the OTA cloud through the OTA master node.

[0015] In some embodiments, when all upgrade packages of the software to be upgraded in the group to which each OTA slave node belongs are downloaded, the OTA master node determines whether the vehicle meets the OTA upgrade preconditions;

[0016] Only when the OTA master node determines that the vehicle meets the OTA upgrade preconditions, each OTA slave node will use the downloaded upgrade package to upgrade all the software to be upgraded in the group to which the OTA slave node belongs.

[0017] In some embodiments, detecting the parking gear and / or vehicle speed of the vehicle, and the ignition switch status of the vehicle;

[0018] When it is determined that the vehicle is stationary based on the parking gear and / or the vehicle speed, and the ignition switch state of the vehicle is powered on, the OTA master node determines that the vehicle meets the OTA upgrade preconditions.

[0019] On the other hand, a distributed OTA upgrade system for intelligent connected vehicles is provided, including:

[0020] OTA cloud, when there is software to be upgraded in the vehicle, sends the software upgrade task of each software to be upgraded to the OTA slave node of the group where each software to be upgraded is located;

[0021] The OTA slave node is used to download the upgrade packages of all the software to be upgraded in the group where the OTA slave node is located from the OTA cloud after receiving the software upgrade task, and use the downloaded upgrade packages to upgrade all the software to be upgraded in the group where the OTA slave node is located.

[0022] In some embodiments, the OTA slave node is further used to obtain software version information of each software in the group; and send the obtained software version information to the OTA cloud;

[0023] The OTA cloud is also used to determine whether the vehicle has software that needs to be upgraded based on the received software version information.

[0024] In some embodiments, the OTA slave node is communicatively connected to the OTA cloud via the OTA master node.

[0025] In some embodiments, each functional domain of the vehicle and all controllers and sensors within the domain belong to a group, and an OTA slave node is set in each group.

[0026] The beneficial effects brought by the technical solution provided by the embodiment of the present application include at least:

[0027] In an embodiment of the present application, an OTA slave node integrated in each functional domain controller of the vehicle is used to download and distribute upgrade packages for the software in the functional domain and all controllers and sensors within the domain, and the functional domain and all software to be upgraded within the domain are upgraded, thereby reducing the load and space requirements for the OTA master node and improving the upgrade success rate, upgrade stability and upgrade efficiency of the whole vehicle OTA upgrade; it can effectively cope with the KPI challenges such as upgrade success rate, upgrade stability and upgrade efficiency faced during the OTA upgrade of the whole vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0029] Figure 1 A flow chart of a distributed OTA upgrade method for an intelligent connected vehicle provided in an embodiment of the present application;

[0030] Figure 2 An architectural block diagram of a distributed OTA upgrade system for an intelligent connected vehicle provided in an embodiment of the present application. DETAILED DESCRIPTION

[0031] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0032] Before explaining the embodiments of the present application in detail, the application scenarios and system architectures involved in the embodiments of the present application are explained respectively.

[0033] First, the application scenarios involved in the embodiments of the present application are introduced.

[0034] OTA (Over the Air Update), also known as remote air download technology, is a technology that changes vehicle performance, adds functions, or fixes system security vulnerabilities by updating vehicle controller firmware and software packages online. With the vigorous development of smart connected vehicles, OTA upgrade function has become a standard configuration of smart connected vehicles, allowing OEMs to quickly respond to user needs, improve user experience, and keep consumers using it frequently.

[0035] Existing intelligent connected vehicles have multiple centralized functional domains, such as power domain, chassis domain, cockpit domain, intelligent driving domain and body domain. Each functional domain has multiple controllers and sensors. For example, the intelligent driving domain has multiple controllers and sensors such as front millimeter wave radar, corner millimeter wave radar, laser radar, ultrasonic controller, etc. Due to the large number of functional domains of intelligent connected vehicles and the large number of controllers and sensors under each domain, the KPIs of the OTA upgrade of the entire intelligent connected vehicle, such as the upgrade success rate, upgrade stability, and upgrade efficiency, have encountered great challenges.

[0036] The OTA upgrade of the whole vehicle of the intelligent connected car with a centralized architecture of domain controllers involves various functional domains as well as the controllers and sensors within the domains. Usually, the OTA master node (master) deployed on the central gateway coordinates the OTA slave nodes (slave) to complete the OTA upgrade of the whole vehicle. OTA slave nodes are divided into self-upgrade nodes (various functional domain controllers) and non-self-upgrade nodes (controllers and sensors). The current technical solution is to download and distribute the upgrade packages of each OTA slave node through the OTA master node to complete the OTA upgrade of the whole vehicle. The upgrade packages of self-upgrade nodes are generally in the order of GB, which poses a great challenge to the load and space requirements of the OTA master node.

[0037] Based on such an application scenario, an embodiment of the present application provides a distributed OTA upgrade method for an intelligent connected vehicle.

[0038] Next, the system architecture involved in the embodiments of the present application is introduced.

[0039] Figure 2 This is a block diagram of the architecture of a distributed OTA upgrade system for an intelligent connected vehicle provided in an embodiment of the present application, see Figure 2 The system includes an OTA cloud, an OTA master node (OTA master) and multiple functional domains; the OTA master node is set in the central gateway of the vehicle, and an OTA slave node (OTA slave) is set in each functional domain. Each functional domain also includes multiple sensors. Each functional domain and the controllers and sensors in the domain are combined into an OTA slave group. The upgrade tasks of the controllers and sensors in the OTAslave group are issued after the OTA master and the OTA cloud communicate. The OTA slave integrated in the functional domain controller downloads and distributes the upgrade package of this OTA slave group, and completes the OTA upgrade of the domain controller, controllers and sensors in this OTA slave group.

[0040] Specifically, the OTA slave is responsible for collecting the software version information of each software in the controller and sensor within the group, and passing this information to the OTA master.

[0041] The OTA master is responsible for collecting the software version information of each OTA slave group and sending the collected information to the OTA cloud.

[0042] The OTA cloud compares the versions of each software according to the software version information. When the version of each software is not the latest version, it determines that the software needs to be upgraded. When the vehicle has software that needs to be upgraded, the software upgrade task of each software to be upgraded is sent to the OTA slave to which the software to be upgraded belongs through the OTA master.

[0043] After each OTA slave receives the software upgrade task issued by the OTA master, it downloads the upgrade package of each software directly from the OTA cloud through the OTA master and stores it in the OTA slave. After the OTA upgrade package is downloaded, the OTAmaster detects whether the vehicle meets the OTA upgrade preconditions. When the OTA upgrade preconditions are met, the upgrade is triggered. After receiving the upgrade instruction, the OTAslave completes the OTA upgrade of the domain controller, controller and sensor in this OTA slave group.

[0044] After introducing the application scenarios and system architecture of the embodiments of the present application, a distributed OTA upgrade method for an intelligent connected vehicle provided in the embodiments of the present application will be described in detail with reference to the accompanying drawings.

[0045] Figure 1 A flowchart of a distributed OTA upgrade method for an intelligent connected vehicle provided in an embodiment of the present application, see Figure 1 , the method is applied to an intelligent connected car and comprises the following steps:

[0046] When there is software to be upgraded in the vehicle, the OTA cloud sends the software upgrade tasks of each software to be upgraded to the OTA slave node of the group where each software to be upgraded is located;

[0047] After receiving the software upgrade task, the OTA slave node downloads the upgrade packages of all the software to be upgraded in the group where the OTA slave node is located from the OTA cloud, and uses the downloaded upgrade packages to upgrade all the software to be upgraded in the group where the OTA slave node is located.

[0048] In an embodiment of the present application, an OTA slave node integrated in each functional domain controller of the vehicle is used to download and distribute software upgrade packages for the functional domain and all controllers and sensors within the domain, and the software upgrade package is used to upgrade the functional domain and all software to be upgraded within the domain, thereby reducing the load and space requirements for the OTA master node and improving the upgrade success rate, upgrade stability and upgrade efficiency of the entire vehicle OTA upgrade; it can effectively address KPI challenges such as upgrade success rate, upgrade stability and upgrade efficiency faced during the OTA upgrade of the entire vehicle.

[0049] In some embodiments, after the OTA slave node completes the software upgrade in the slave node, the upgrade result is sent to the OTA cloud.

[0050] In some embodiments, software version information of each software in the group to which each OTA slave node belongs is obtained through each OTA slave node;

[0051] Each OTA slave node sends the acquired software version information to the OTA cloud;

[0052] The OTA cloud determines whether the vehicle has software that needs to be upgraded based on the received software version information.

[0053] In some embodiments, each OTA slave node sends the acquired software version information to the OTA cloud through the OTA master node;

[0054] The OTA slave node downloads the upgrade packages of all the software to be upgraded in the slave node from the OTA cloud through the OTA master node.

[0055] In some embodiments, when all upgrade packages of the software to be upgraded in the group to which each OTA slave node belongs are downloaded, the OTA master node determines whether the vehicle meets the OTA upgrade preconditions;

[0056] Only when the OTA master node determines that the vehicle meets the OTA upgrade preconditions, each OTA slave node will use the downloaded upgrade package to upgrade all the software to be upgraded in the group to which the OTA slave node belongs.

[0057] In some embodiments, detecting the parking gear and / or vehicle speed of the vehicle, and the ignition switch status of the vehicle;

[0058] When it is determined that the vehicle is stationary based on the parking gear and / or the vehicle speed, and the ignition switch state of the vehicle is powered on, the OTA master node determines that the vehicle meets the OTA upgrade preconditions.

[0059] As an example, after the vehicle is powered on, the OTA slave collects the software version information of the software in the controllers and sensors in its group and reports it to the OTA master;

[0060] OTA master collects all software version information reported by OTA slaves and uploads it to the OTA cloud;

[0061] The OTA cloud compares the software version information uploaded by the vehicle-side OTA master to determine whether the software needs to be upgraded. Once it is determined that the vehicle has software to be upgraded, the software upgrade task is sent to the vehicle-side OTA master;

[0062] OTA master sends the upgrade tasks in each OTA slave group to each OTA slave;

[0063] Each OTA slave downloads and stores the upgrade packages of all controllers and sensor software in the OTA slave group from the cloud through TBOX (vehicle information communication module);

[0064] After the upgrade package is downloaded, the OTA master detects whether the vehicle meets the OTA upgrade preconditions of the entire vehicle. If the vehicle meets the OTA upgrade preconditions, it triggers each group to perform software upgrades.

[0065] OTA slave is responsible for OTA upgrade of all controllers and sensors in the OTA slave group. After the upgrade is completed, OTA slave collects the upgrade results of all controllers and sensors in the group and feeds them back to OTA master. OTA master collects the upgrade results reported by all OTA slaves to the OTA cloud.

[0066] All the above optional technical solutions can be combined in any way to form optional embodiments of the present application, and the embodiments of the present application will not be described in detail one by one.

[0067] After explaining a distributed OTA upgrade method for an intelligent connected vehicle provided in an embodiment of the present application, next, a distributed OTA upgrade system for an intelligent connected vehicle provided in an embodiment of the present application is introduced.

[0068] Figure 2 A distributed OTA upgrade system for an intelligent connected vehicle is provided in an embodiment of the present application. Figure 2 As shown, the system can be implemented by software, hardware or a combination of both.

[0069] The system includes:

[0070] OTA cloud, when there is software to be upgraded in the vehicle, sends the software upgrade task of each software to be upgraded to the OTA slave node of the group where each software to be upgraded is located;

[0071] The OTA slave node is used to download the upgrade packages of all the software to be upgraded in the group where the OTA slave node is located from the OTA cloud after receiving the software upgrade task, and use the downloaded upgrade packages to upgrade all the software to be upgraded in the group where the OTA slave node is located.

[0072] In some embodiments, the OTA slave node is further used to obtain software version information of each software in the group; and send the obtained software version information to the OTA cloud;

[0073] The OTA cloud is also used to determine whether the vehicle has software that needs to be upgraded based on the received software version information.

[0074] In some embodiments, the OTA slave node is communicatively connected to the OTA cloud via the OTA master node.

[0075] In some embodiments, each functional domain of the vehicle and all controllers and sensors within the domain belong to a group, and an OTA slave node is set in each group.

[0076] To summarize, in the embodiments of the present application, the OTA slave node integrated in each functional domain controller of the vehicle is used to download and distribute the upgrade packages of the software in the functional domain and all controllers and sensors within the domain, and the functional domain and all software to be upgraded within the domain are upgraded, thereby reducing the load and space requirements for the OTA master node and improving the upgrade success rate, upgrade stability and upgrade efficiency of the whole vehicle OTA upgrade; it can effectively cope with the KPI challenges such as upgrade success rate, upgrade stability and upgrade efficiency faced during the OTA upgrade of the whole vehicle.

[0077] It should be noted that the distributed OTA upgrade system for an intelligent connected vehicle and the distributed OTA upgrade method embodiment for an intelligent connected vehicle provided in the above-mentioned embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0078] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0079] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A distributed OTA upgrade method for an intelligent connected vehicle, characterized in that: include: When there is software to be upgraded in the vehicle, the OTA cloud sends the software upgrade tasks of each software to be upgraded to the OTA slave node of the group where each software to be upgraded is located; After receiving the software upgrade task, the OTA slave node downloads the upgrade packages of all the software to be upgraded in the group where the OTA slave node is located from the OTA cloud, and uses the downloaded upgrade packages to upgrade all the software to be upgraded in the group where the OTA slave node is located.

2. A distributed OTA upgrade method for an intelligent connected vehicle as claimed in claim 1, characterized in that: After the OTA slave node completes the software upgrade in the group to which the slave node belongs, it sends the upgrade result to the OTA cloud.

3. A distributed OTA upgrade method for an intelligent connected vehicle as claimed in claim 1, characterized in that: Obtain software version information of each software in the group to which each OTA slave node belongs through each OTA slave node; Each OTA slave node sends the acquired software version information to the OTA cloud; The OTA cloud determines whether the vehicle has software that needs to be upgraded based on the received software version information.

4. A distributed OTA upgrade method for an intelligent connected vehicle as claimed in claim 1, characterized in that: Each OTA slave node sends the acquired software version information to the OTA cloud through the OTA master node; The OTA slave node downloads the upgrade packages of all the software to be upgraded in the slave node from the OTA cloud through the OTA master node.

5. A distributed OTA upgrade method for an intelligent connected vehicle as claimed in claim 4, characterized in that: When all the upgrade packages of the software to be upgraded in the group of each OTA slave node are downloaded, the OTA master node determines whether the vehicle meets the OTA upgrade preconditions; Only when the OTA master node determines that the vehicle meets the OTA upgrade preconditions, each OTA slave node will use the downloaded upgrade package to upgrade all the software to be upgraded in the group to which the OTA slave node belongs.

6. A distributed OTA upgrade method for an intelligent connected vehicle as claimed in claim 5, characterized in that: Detecting the parking gear and / or vehicle speed of the vehicle, and the ignition switch status of the vehicle; When it is determined that the vehicle is stationary based on the parking gear and / or the vehicle speed, and the ignition switch state of the vehicle is powered on, the OTA master node determines that the vehicle meets the OTA upgrade preconditions.

7. A distributed OTA upgrade system for intelligent connected vehicles, characterized in that: include: OTA cloud, when there is software to be upgraded in the vehicle, sends the software upgrade task of each software to be upgraded to the OTA slave node of the group where each software to be upgraded is located; The OTA slave node is used to download the upgrade packages of all the software to be upgraded in the group where the OTA slave node is located from the OTA cloud after receiving the software upgrade task, and use the downloaded upgrade packages to upgrade all the software to be upgraded in the group where the OTA slave node is located.

8. A distributed OTA upgrade system for an intelligent connected vehicle as claimed in claim 7, characterized in that: The OTA slave node is also used to obtain the software version information of each software in the group; and send the obtained software version information to the OTA cloud; The OTA cloud is also used to determine whether the vehicle has software that needs to be upgraded based on the received software version information.

9. A distributed OTA upgrade system for an intelligent connected vehicle as claimed in claim 7, characterized in that: The OTA slave node communicates with the OTA cloud through the OTA master node.

10. A distributed OTA upgrade system for an intelligent connected vehicle as claimed in claim 7, characterized in that: Each functional domain of the vehicle and all controllers and sensors within the domain belong to a group, and an OTA slave node is set in each group.

Images