Vehicle OTA upgrading method and device, electronic equipment and storage medium

Abstract

The invention provides an OTA upgrading method and device of a vehicle, electronic equipment and a storage medium. The method comprises the steps that an OTA upgrading task issued by an OTA platform is received; and reading configuration information of the vehicle. And if the configuration information indicates that the vehicle is an unmanned vehicle, performing OTA upgrading on the vehicle according to an unmanned vehicle upgrading process for the OTA upgrading task.

Description

TECHNICAL FIELD

[0001] The present specification relates to the technical field of wireless communication, and particularly relates to an OTA upgrade method and device of a vehicle, an electronic device and a storage medium. BACKGROUND

[0002] Traditional vehicles need to be manually driven by users, and with the rapid development of unmanned driving technology, these vehicles also begin to have unmanned driving functions, but at the current stage, the manual driving function (referred to as "manned vehicle") is still retained. In life, the widespread application of fully automatic driving vehicles (referred to as "unmanned vehicles") also appears in succession. For example, unmanned taxis, unmanned delivery vehicles and the like managed by a platform in a unified and remote manner.

[0003] In the application scenario of OTA upgrade of vehicles, the OTA upgrade processes of manned vehicles and unmanned vehicles are not completely the same. For example, a manned vehicle needs to be authorized by a user before it can be OTA upgraded, while an unmanned vehicle can be directly OTA upgraded without authorization.

[0004] For vehicle manufacturers, how to compatibly OTA upgrade manned vehicles and unmanned vehicles with as little change as possible to the traditional upgrade process has become a new challenge in the field of OTA upgrade of vehicles. SUMMARY

[0005] To overcome the problems in the related art, the present specification provides an OTA upgrade method and device of a vehicle, an electronic device and a storage medium.

[0006] According to a first aspect of an embodiment of the present specification, an OTA upgrade method of a vehicle is provided, and the method comprises: receiving an OTA upgrade task issued by an OTA platform; reading configuration information of the vehicle; if the configuration information indicates that the vehicle is an unmanned vehicle, performing OTA upgrade for the vehicle according to an unmanned vehicle upgrade process for the OTA upgrade task.

[0007] According to a second aspect of an embodiment of the present specification, an OTA upgrade device of a vehicle is provided, and the device comprises: an OTA upgrade task receiving module configured to receive an OTA upgrade task issued by an OTA platform; a configuration information reading module configured to read configuration information of the vehicle; a vehicle upgrade module configured to, if the configuration information indicates that the vehicle is an unmanned vehicle, perform OTA upgrade for the vehicle according to an unmanned vehicle upgrade process for the OTA upgrade task.

[0008] According to a third aspect of the embodiments of the present specification, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method according to the first aspect when executing the program.

[0009] According to a fourth aspect of the embodiments of the present specification, a computer readable storage medium is provided, which stores a computer program, wherein the program is executable on a processor to implement the steps of the method according to the first aspect.

[0010] The technical solutions provided by the embodiments of the present specification can include the following beneficial effects: In the embodiments of the present specification, the OTA platform can issue OTA upgrade tasks for unmanned vehicles and manned vehicles, and the vehicle receiving the task can determine the type of the vehicle by reading the configuration information, so as to execute the corresponding OTA upgrade process.

[0011] It can be seen that the OTA platform of the present solution does not need to distinguish between the OTA upgrade tasks of unmanned vehicles and manned vehicles, and the platform only needs to issue OTA upgrade tasks uniformly, and the vehicle can determine the type of the vehicle by reading the configuration information, and then execute the corresponding upgrade process. The present solution is compatible with the OTA upgrade process of manned vehicles and unmanned vehicles, simplifies the complexity of the OTA platform operating the OTA upgrade tasks of unmanned vehicles and manned vehicles, and improves the operating efficiency.

[0012] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present specification. BRIEF DESCRIPTION OF DRAWINGS

[0013] The accompanying drawings incorporated in the specification and forming a part of the specification illustrate the embodiments consistent with the present specification, and together with the specification serve to explain the principles of the present specification.

[0014] Figure 1 is a flowchart of an OTA upgrade method of a vehicle according to an exemplary embodiment of the present specification.

[0015] Figure 2 is a schematic diagram of an OTA upgrade process of an unmanned vehicle in a reservation mode according to an exemplary embodiment of the present specification.

[0016] Figure 3 is a schematic diagram of an OTA upgrade process of an unmanned vehicle in an immediate installation mode according to an exemplary embodiment of the present specification.

[0017] Figure 4 is a schematic diagram of an electronic device according to an exemplary embodiment of the present specification.

[0018] Figure 5This is a block diagram illustrating an OTA (Over-The-Air) upgrade device for a vehicle according to an exemplary embodiment. Detailed Implementation

[0019] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.

[0020] The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of this specification. The singular forms “a,” “the,” and “the” as used in this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0021] It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0022] Traditional vehicles require manual driving. With the rapid development of autonomous driving technology, these vehicles have begun to possess autonomous driving capabilities, but currently still retain manual driving functions. These vehicles can be called "manned vehicles," are the private property of the users, and serve the users' personal travel needs.

[0023] Meanwhile, fully autonomous vehicles are increasingly being used in daily life. For example, vehicles are managed centrally by an operation and dispatch platform and serve as tools for providing public services. Examples include driverless taxis and driverless delivery vehicles. These vehicles can be called "manned vehicles," and their dispatch, operation, and service targets are all determined by the platform, serving as shared assets to provide services to the public.

[0024] Due to these differences in service attributes, there are some differences in the OTA upgrade process between autonomous vehicles and manned vehicles. For example, for manned vehicles, the timing of OTA upgrades and whether an upgrade is necessary both require user authorization on the vehicle side before subsequent steps can proceed. Users can authorize OTA upgrade times to upgrade vehicle functions. In contrast, the OTA upgrade decision for autonomous vehicles is made by the operation and dispatch platform. No authorization is required on the vehicle side. After receiving the OTA upgrade task from the platform, the autonomous vehicle can directly upgrade its functions under safe upgrade conditions without any authorization operation on the vehicle side, following the task instructions.

[0025] Traditional OTA upgrade processes are all based on authorized upgrade models for manned vehicles. With the widespread application of driverless vehicles, how to make as few changes as possible to the traditional vehicle upgrade process while being compatible with the OTA upgrade processes of both manned and driverless vehicles has become a new challenge in the field of vehicle OTA upgrades.

[0026] Therefore, this specification provides an OTA upgrade method for vehicles to be compatible with the upgrade processes of manned and unmanned vehicles.

[0027] The embodiments described in this specification will now be described in detail.

[0028] Figure 1 This is a flowchart illustrating an OTA (Over-The-Air) upgrade method for a vehicle according to an exemplary embodiment. The method can be applied to vehicles, such as... Figure 1 As shown, steps 101-104 are included: Step 101: Receive the OTA upgrade task issued by the OTA platform.

[0029] Step 102: Read the vehicle's configuration information.

[0030] Step 103: If the configuration information indicates that the vehicle is an unmanned vehicle, then for the OTA upgrade task, perform an OTA upgrade for the vehicle according to the unmanned vehicle upgrade process.

[0031] OTA (Over-the-Air Technology) refers to the remote updating, repair, or upgrading of a device's software or firmware via a wireless network (such as cellular network, WiFi, etc.) without requiring a physical connection to the device.

[0032] In the application scenarios of this solution, OTA upgrades can include, but are not limited to, upgrades to the vehicle's firmware. The upgrade targets are the underlying firmware programs within the ECU (Electronic Control Unit), involving the bootloader, operating system, and underlying drivers. For example, updating the control logic of the engine or motor.

[0033] OTA (Over-The-Air) updates can target automotive software, including various in-vehicle applications. For example, updating music, video, and navigation applications to add new features or fix bugs.

[0034] OTA (Over-The-Air) upgrades can target ECU configuration files or function switches, remotely changing vehicle parameter configurations and enabling or disabling certain pre-installed hardware functions. For example, if a vehicle is equipped with heated seats, users can pay to permanently activate this function via OTA or subscribe to it monthly.

[0035] OTA upgrades can target the vehicle's AI model. For example, OTA can be used to distribute newly trained model parameters.

[0036] It should be noted that the above-mentioned OTA upgrade targets, including but not limited to, are all applicable to the OTA upgrade process of this solution, which is compatible with both manned and unmanned vehicles.

[0037] The OTA platform, also known as the OTA cloud server, is the core control center of the entire OTA system, responsible for tasks such as data management, task scheduling, and communication with vehicles.

[0038] The OTA platform is responsible for storing software version information and update packages for each ECU in a vehicle. These update packages contain the code needed to fix vulnerabilities, optimize performance, or add new features. The OTA platform can manage and maintain software versions for different vehicle models and configurations, ensuring that each vehicle receives the correct installation package.

[0039] OTA platforms can collect basic vehicle information, such as vehicle identification number (VIN), vehicle model, and software version, to create a vehicle profile. They can also monitor the vehicle's online status and software update status in real time, allowing for timely understanding of the vehicle's OTA progress.

[0040] OTA platforms can determine which vehicles need software updates based on factors such as the vehicle's software version and usage, and then develop corresponding upgrade plans. The update task and corresponding software update package are then pushed to the target vehicles.

[0041] When communicating and transmitting data with vehicles, OTA platforms can authenticate the vehicle's identity to ensure that update data is only sent to legitimate vehicles. Simultaneously, they can encrypt the transmitted data to prevent it from being stolen or tampered with during transmission.

[0042] OTA platforms can record the entire OTA process for a vehicle, including update requests, download progress, and installation results. Analyzing the recorded data allows for the evaluation of OTA effectiveness, the identification of potential problems, and the provision of a basis for subsequent upgrades and optimizations.

[0043] An OTA (Over-The-Air) update task can include information such as a list of features to be upgraded, the upgrade version, and the upgrade mode. It can be used to notify the vehicle when, what, and what content will be upgraded. The vehicle can respond to the OTA update task by downloading the software installation package and then installing the software.

[0044] In one embodiment, if the configuration information indicates that the vehicle is a manned vehicle, then for the OTA upgrade task, the vehicle is upgraded via OTA according to the manned vehicle upgrade process.

[0045] In an exemplary application scenario, assuming vehicle A is a manned vehicle, after receiving an OTA upgrade task from the OTA platform, vehicle A can determine its type based on its configuration information. In this scenario, the configuration information indicates that vehicle A is a manned vehicle. Vehicle A can display a notification for this OTA upgrade task on its central control screen. After agreeing to the OTA upgrade task, the user can choose to schedule an upgrade for the future or upgrade immediately. Finally, the vehicle can be upgraded using the downloaded software installation package, provided the vehicle is in a safe upgrade condition.

[0046] Assuming vehicle B is an autonomous vehicle, after receiving an OTA upgrade task from the OTA platform, vehicle B can determine its type by reading its configuration information. In this scenario, the configuration information indicates that vehicle B is an autonomous vehicle. Vehicle B can then choose to upgrade the vehicle during a scheduled time period or immediately using the downloaded software installation package, according to the instructions of the OTA upgrade task.

[0047] In the above-mentioned OTA upgrade process for manned and unmanned vehicles, manned vehicles require user authorization on the vehicle side before subsequent software installation operations can be performed, while unmanned vehicles do not require any authorization on the vehicle side and can respond to the issued OTA upgrade task to directly perform the corresponding function upgrade.

[0048] In this embodiment, the OTA platform can uniformly issue OTA upgrade tasks for both unmanned and manned vehicles. The OTA upgrade task does not need to distinguish between manned and unmanned vehicles. The vehicle receiving the task can determine its type by reading the configuration information and then execute the corresponding OTA upgrade process.

[0049] As can be seen, this OTA platform eliminates the need for differentiated OTA upgrade tasks for both manned and autonomous vehicles. Furthermore, it doesn't require concern about the type of vehicle executing the issued OTA tasks. The platform only needs to uniformly issue OTA upgrade tasks, and vehicles can determine their type by reading configuration information and then adaptively execute the corresponding upgrade process. This solution is compatible with both manned and autonomous vehicle OTA upgrade processes, simplifying the complexity of operating OTA upgrade tasks for both types of vehicles and improving operational efficiency.

[0050] In one embodiment, for specific identifiers in the configuration information that can effectively distinguish between manned and unmanned vehicles, different values ​​can be assigned to these specific identifiers to indicate whether the vehicle is a manned or unmanned vehicle. By reading the values ​​of the specific identifiers written in the configuration information, it can be determined whether the vehicle is a manned or unmanned vehicle based on the content of the values.

[0051] For example, the specific identifier could be an identifier for a specific vehicle configuration, such as the configuration of a steering wheel. If the value of the identifier indicates that there is no steering wheel, then the vehicle is an autonomous vehicle; if the value of the identifier indicates that there is a steering wheel, then the vehicle is a manned vehicle.

[0052] The specific configuration identifier can be written into the configuration information during vehicle production. For example, in the function configuration DID=F101, BITE=1 in BYTE0 indicates an unmanned vehicle, and BITE=0 indicates a manned vehicle. Here, BITE can represent a specific identifier, and 1 and 0 can represent the value of that identifier.

[0053] In this embodiment, no additional processing logic is required to identify the vehicle type. The specific identifier used can be inherent to the vehicle itself. The vehicle is identified as manned or unmanned by the value of the specific identifier written in the configuration information. The judgment logic is simple and reliable.

[0054] In one embodiment, the configuration information can be configured in the OTA upgrade management module. Specifically, the OTA upgrade management module can be the OTA master. The OTA master typically refers to the OTA master control unit on the vehicle side, which is the component that enables communication between the vehicle and the OTA platform and performs software updates. The ECU hosted by the OTA master can have specific identifiers configured in its configuration information beforehand. After startup, the OTA master can read the configuration information of the hosted ECU to determine whether the vehicle is manned or unmanned.

[0055] In this embodiment, after startup, the OTA master can directly obtain configuration information from the ECU it is hosted in, without needing to query other ECUs to obtain the vehicle type, thus avoiding the problem of being unable to obtain the vehicle type due to network issues or other ECU malfunctions.

[0056] Next, this manual will introduce the upgrade process for manned vehicles and driverless vehicles respectively: ① People and vehicles In one embodiment, if the configuration information indicates that the vehicle is an unmanned vehicle, then for the OTA upgrade task, the vehicle can determine whether the OTA upgrade task has been authorized. If the authorization is successful, the vehicle can read the upgrade mode issued by the OTA platform from the OTA upgrade task and perform an OTA upgrade for the vehicle according to the upgrade mode; wherein, the OTA upgrade task includes the upgrade mode.

[0057] The basis for determining whether an OTA upgrade task is authorized can be whether the vehicle receives an instruction from the user agreeing to the upgrade.

[0058] In one exemplary application scenario, after receiving an OTA upgrade task from the OTA platform, the vehicle can send an OTA upgrade authorization notification to the vehicle's central control screen. This notification may include the upgrade mode, upgrade version number, update size, and update content. The user can choose an upgrade mode, which may include an immediate installation mode or a scheduled mode. If the user chooses the scheduled mode, they can select a time slot, during which the vehicle can undergo an OTA upgrade. Alternatively, the user can choose the immediate installation mode, in which case the vehicle can check if the current vehicle environment meets the upgrade requirements; if so, it can immediately perform the OTA upgrade.

[0059] If the current vehicle environment does not meet the upgrade requirements or the upgrade fails, a notification can be sent to the vehicle's central control screen, along with the reason for the failure to the OTA platform. The user can then interact with the central control screen to select a new appointment time to attempt the upgrade again. If the upgrade fails due to not meeting the upgrade requirements, the reason for the failure can be displayed on the central control screen. After user confirmation, the vehicle's status will be readjusted, and the OTA upgrade process will be attempted again.

[0060] Of course, the successful installation result can also be displayed on the central control screen to notify the user that the installation was successful.

[0061] In this embodiment, the vehicle can determine that it is a manned vehicle and automatically switch to the manned vehicle upgrade process to perform OTA upgrade.

[0062] ② Driverless cars In one embodiment, if the configuration information indicates that the vehicle is an autonomous vehicle, then for an OTA upgrade task, the upgrade mode issued by the OTA platform can be read from the OTA upgrade task, and the vehicle can be upgraded via OTA according to the upgrade mode; wherein, the OTA upgrade task includes the upgrade mode.

[0063] In one embodiment, the upgrade mode includes a scheduled mode and an immediate installation mode. The scheduled mode allows the vehicle to be upgraded at a pre-scheduled time, avoiding any unavailability of the vehicle during the upgrade process. For example, the upgrade process can be performed at night when the vehicle is idle. The immediate installation mode, on the other hand, allows the vehicle upgrade process to be performed if the vehicle's condition meets the upgrade requirements.

[0064] Specifically, when performing an OTA upgrade on the vehicle according to the upgrade mode, if the upgrade mode is the reservation mode, when the reservation time arrives, it can be determined whether the vehicle meets the upgrade conditions. If it does, then an OTA upgrade is performed on the vehicle.

[0065] For example, such as Figure 2 As shown, OTA platform operators can schedule upgrade times for the autonomous vehicles they operate and issue OTA upgrade tasks to the vehicle. These tasks include a scheduling mode. After the vehicle is powered on and off, the OTAmaster starts and can read configuration information through an internal interface to determine if the vehicle is autonomous. The ECU hosted by the OTAmaster can read the scheduling mode from the OTA upgrade task and wake up the OTAmaster when the scheduled upgrade time arrives. After the OTAmaster is awakened, it can determine whether the vehicle meets the upgrade conditions. These conditions may include the vehicle being stationary, not charging, in Park (P) gear, powered off, doors locked, and battery voltage greater than 12.5V. If these conditions are met, the vehicle can download the software installation package via the TBOX and then install the software. The installation result can be uploaded to the OTA platform without any notification on the autonomous vehicle. If the installation is successful, the OTAmaster can be put into idle mode to await the next task.

[0066] When the upgrade mode is in reservation mode, if the vehicle does not meet the upgrade conditions when the reservation time arrives, a failure notification can be sent to the OTA platform, and a new OTA upgrade task issued by the OTA platform can be received. The new OTA upgrade task includes a new reservation mode.

[0067] When performing an OTA upgrade on the vehicle according to the upgrade mode, if the upgrade mode is the immediate installation mode, the vehicle is remotely powered on while it is safely parked, and it is determined whether the vehicle meets the upgrade conditions. If it does, the vehicle is upgraded via OTA, and then remotely powered off after the upgrade is completed.

[0068] In this embodiment, the vehicle can determine that it is an unmanned vehicle and automatically switch to the unmanned vehicle upgrade process to perform OTA upgrade.

[0069] For example, such as Figure 3 As shown, the vehicle can be parked in a safe location after the engine is turned off. The OTA platform can issue an unmanned factory mode to the TSP (Telematics Service Provider) platform, enabling the TSP platform to respond to this mode and remotely power on the vehicle. Upon detecting the power-on, the OTA master on the vehicle can read the configuration information to determine whether the vehicle is manned or unmanned, thus preparing for different OTA upgrade procedures. The OTA platform can issue an OTA upgrade task to the vehicle. The OTA master reads the immediate installation mode from the OTA upgrade task, and then downloads the software installation package via the TBOX. After the download is complete, it can further determine whether the vehicle meets the upgrade conditions. These conditions may include the vehicle being stationary, not charging, in Park (P) gear, powered off, doors locked, and battery voltage greater than 12.5V. If these conditions are met, the software installation proceeds. After the upgrade is complete, the vehicle is remotely powered off via the TSP platform. Finally, it enters an idle state, waiting for the next power-on query task.

[0070] If the upgrade conditions are not met, the autonomous vehicle does not need to display a failure result on the vehicle's end; instead, it can send a failure notification to the OTA platform and wait for the next upgrade task. Conversely, the successful installation result does not need to be displayed on the vehicle's end either.

[0071] Corresponding to the embodiments of the foregoing methods, this specification also provides embodiments of the apparatus and the terminal to which it is applied.

[0072] Figure 4 This is a schematic diagram illustrating the structure of an electronic device according to an exemplary embodiment. Figure 4As shown, at the hardware level, the electronic device 400 includes a processor 402, an internal bus 404, a network interface 406, memory 408, and non-volatile memory 410, and may also include other hardware required for business operations. One or more embodiments of this specification can be implemented in software, for example, the processor 402 reads the corresponding computer program from the non-volatile memory 410 into memory 408 and then runs it. Of course, in addition to software implementation, one or more embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to each logic module, but can also be hardware or logic devices.

[0073] Figure 5 This is a block diagram illustrating an OTA (Over-The-Air) upgrade device for a vehicle according to an exemplary embodiment. Figure 5 As shown, this device can be applied to, for example Figure 4 The electronic device 400 shown implements the technical solution of this specification. The device includes: The OTA upgrade task receiving module 502 is used to receive OTA upgrade tasks issued by the OTA platform.

[0074] The configuration information reading module 504 is used to read the vehicle's configuration information.

[0075] The vehicle upgrade module 506 is used to perform an OTA upgrade for the vehicle according to the unmanned vehicle upgrade process if the configuration information indicates that the vehicle is an unmanned vehicle.

[0076] Optionally, the vehicle upgrade module 506 is further configured to perform an OTA upgrade for the vehicle according to the manned vehicle upgrade process for the OTA upgrade task if the configuration information indicates that the vehicle is a manned vehicle.

[0077] Optionally, different values ​​of a specific identifier written in the configuration information indicate whether the vehicle is a manned vehicle or an unmanned vehicle, and the configuration information reading module 504 is specifically used to read the value of the specific identifier.

[0078] Optionally, the configuration information is configured in the OTA upgrade management module.

[0079] Optionally, the vehicle upgrade module 506 is specifically used to determine whether the OTA upgrade task is authorized. If the authorization is successful, it reads the upgrade mode issued by the OTA platform from the OTA upgrade task and performs an OTA upgrade for the vehicle according to the upgrade mode; wherein, the OTA upgrade task includes the upgrade mode.

[0080] Optionally, the vehicle upgrade module 506 is specifically used to read the upgrade mode issued by the OTA platform from the OTA upgrade task, and perform OTA upgrade for the vehicle according to the upgrade mode; wherein, the OTA upgrade task includes the upgrade mode.

[0081] Optionally, the upgrade mode includes a reservation mode and an immediate installation mode. Specifically, the vehicle upgrade module 506 is used to determine whether the vehicle meets the upgrade conditions when the reservation time arrives in the reservation mode. If it does, the vehicle is upgraded via OTA. In the case of the upgrade mode being the immediate installation mode, the vehicle is remotely powered on while it is safely parked, and the vehicle is determined whether it meets the upgrade conditions. If it does, the vehicle is upgraded via OTA, and the vehicle is remotely powered off after the upgrade is completed.

[0082] Optionally, the device further includes an upgrade failure handling module, which, if the upgrade mode is the scheduled mode and the conditions are not met, sends a failure notification to the OTA platform and receives a new OTA upgrade task issued by the OTA platform.

[0083] The specific implementation process of the functions and roles of each module in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0084] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0085] This specification also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the OTA upgrade method for any of the aforementioned vehicles provided in this application.

[0086] Specifically, computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, such as semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks.

[0087] This specification also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the OTA upgrade method for any of the aforementioned vehicles.

Claims

1. A method for OTA (Over-The-Air) upgrade of a vehicle, characterized in that, The method includes: Receive OTA upgrade tasks issued by the OTA platform; Read the vehicle's configuration information; If the configuration information indicates that the vehicle is an autonomous vehicle, then for the OTA upgrade task, the vehicle will be upgraded via OTA according to the autonomous vehicle upgrade process.

2. The method according to claim 1, characterized in that, The configuration information is configured in the OTA upgrade management module.

3. The method according to claim 1, characterized in that, The OTA upgrade of the vehicle according to the autonomous vehicle upgrade process includes: The upgrade mode issued by the OTA platform is read from the OTA upgrade task, and the vehicle is upgraded via OTA according to the upgrade mode; wherein, the OTA upgrade task includes the upgrade mode.

4. The method according to claim 3, characterized in that, The upgrade modes include a scheduled mode and an immediate installation mode. The OTA upgrade of the vehicle according to the upgrade mode includes: When the upgrade mode is the reservation mode, when the reservation time arrives, it is determined whether the vehicle meets the upgrade conditions. If it does, the vehicle is upgraded via OTA. When the upgrade mode is the immediate installation mode, the vehicle is remotely powered on while it is safely parked, and it is determined whether the vehicle meets the upgrade conditions. If it does, the vehicle is upgraded via OTA, and then remotely powered off after the upgrade is completed.

5. The method according to claim 4, characterized in that, The method further includes: If the upgrade mode is the reservation mode and the conditions are not met, a failure notification is sent to the OTA platform, and a new OTA upgrade task is received from the OTA platform.

6. The method according to claim 1, characterized in that, The method further includes: If the configuration information indicates that the vehicle is a manned vehicle, then for the OTA upgrade task, the vehicle will be upgraded via OTA according to the manned vehicle upgrade process.

7. The method according to claim 6, characterized in that, Different values ​​of the specific identifier written in the configuration information indicate whether the vehicle is a manned vehicle or an unmanned vehicle. The process of reading the vehicle's configuration information includes: Read the value of the specific identifier.

8. The method according to claim 6, characterized in that, The OTA upgrade of the vehicle according to the manned vehicle upgrade process includes: Determine whether the OTA upgrade task is authorized. If authorization is successful, read the upgrade mode issued by the OTA platform from the OTA upgrade task, and perform an OTA upgrade for the vehicle according to the upgrade mode; wherein, the OTA upgrade task includes the upgrade mode.

9. An OTA (Over-The-Air) upgrade device for a vehicle, characterized in that, The device includes: The OTA upgrade task receiving module is used to receive OTA upgrade tasks issued by the OTA platform. The configuration information reading module is used to read the vehicle's configuration information; The vehicle upgrade module is used to perform an OTA upgrade for the vehicle according to the OTA upgrade process if the configuration information indicates that the vehicle is an unmanned vehicle.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method as described in any one of claims 1-8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by a processor, it implements the steps of the method as described in any one of claims 1-8.

Images