OTA upgrading method and device and system for OTA upgrading

Abstract

An OTA upgrade method, an apparatus and a system for OTA upgrade, the method comprising: generating OTA upgrade arrangement information according to M to-be-upgraded ECUs of an intelligent device, the OTA upgrade arrangement information indicating at least one upgrade stage, an intelligent device state required by a first upgrade stage in the at least one upgrade stage, and a flash sequence of the at least one ECU in the first upgrade stage; wherein the total number of the ECUs included in each upgrading stage in the at least one upgrading stage is M, and M is an integer greater than or equal to 1; and sending OTA upgrade arrangement information to the intelligent device, wherein the OTA upgrade arrangement information is used for the intelligent device to carry out ECU flashing. The technical scheme of the invention can be applied to the technical field of Internet of Vehicles, such as the OTA upgrading field of new energy vehicles and intelligent vehicles, and is beneficial to improving the flexibility of OTA upgrading control and reducing the cost of OTA upgrading control.

Description

OTA upgrade method, device and system for OTA upgrade Technical Field

[0001] The present application relates to the field of vehicle networking technology, and more specifically, to an OTA upgrade method, an apparatus and a system for OTA upgrade. Background Art

[0002] Over-the-air (OTA) technology, which downloads data over wireless networks, is now widely used to upgrade devices such as vehicles, televisions, mobile phones, tablets, and set-top boxes. OTA technology primarily performs automatic upgrades by downloading or copying OTA upgrade packages. OTA upgrades are fast and have minimal impact on data, making them the primary method for upgrading terminal functions.

[0003] When upgrading a vehicle at the entire vehicle level, multiple electronic control units (ECUs) are involved. These ECUs may need to be upgraded sequentially or in parallel, and each ECU may require different vehicle states, resulting in different upgrade control logic for different vehicle models. Furthermore, the ECU flashing sequence in current OTA upgrade technology is typically hard-coded into the upgrade software code, requiring customized upgrade software for different vehicle models, increasing the cost of OTA upgrades.

[0004] Summary of the Invention

[0005] The present application provides an OTA upgrade method, an apparatus and a system for OTA upgrade, and provides a way to arrange the ECU flash writing sequence and conditions, which helps to improve the flexibility of OTA upgrade control and reduce the cost of OTA upgrade control.

[0006] In a first aspect, an OTA upgrade method is provided, which can be executed by an OTA server, or by a chip or circuit in the OTA server. The method may include: generating first OTA upgrade scheduling information based on M ECUs to be upgraded in a smart device, the first OTA upgrade scheduling information indicating at least one upgrade stage, the smart device state required for the first upgrade stage in at least one upgrade stage, and the flashing order of at least one ECU in the first upgrade stage; wherein the total number of ECUs included in each upgrade stage in at least one upgrade stage is M, and M is an integer greater than or equal to 1; sending the first OTA upgrade scheduling information to the smart device, the first OTA upgrade scheduling information being used for the smart device to flash the ECU.

[0007] In this technical solution, the OTA server can generate, in real time, information indicating the flashing order, upgrade phase, and required smart device status for multiple ECUs to be upgraded, and send it to the smart devices for OTA upgrades. This eliminates the need to hard-code information such as the flashing order and required smart device status for the smart device ECUs during the OTA upgrade process. This improves the flexibility of ECU flashing control during the OTA upgrade process and reduces the cost of OTA upgrade control.

[0008] In a second aspect, an OTA upgrade method is provided, which can be executed by an OTA server, or by a chip or circuit in the OTA server. The method may include: generating first OTA upgrade scheduling information based on M ECUs to be upgraded, the first OTA upgrade scheduling information indicating at least one upgrade stage and a flashing order of at least one ECU in the first upgrade stage; wherein, at least one upgrade stage includes a first upgrade stage, the total number of ECUs included in each upgrade stage in at least one upgrade stage is M, and M is an integer greater than or equal to 1; sending the first OTA upgrade scheduling information to a smart device, the first OTA upgrade scheduling information being used for the smart device to flash the ECU.

[0009] It is understandable that the state of each ECU in the smart device may be different when it is OTA upgraded. For example, taking the smart device as a vehicle, the ECU that manages the power battery in the vehicle can generally only be flashed when the vehicle is in a low-voltage state (i.e., the vehicle is powered by a low-voltage battery), and other ECUs generally need to be flashed when the vehicle is in a high-voltage state (i.e., the vehicle is powered by a power battery). Therefore, the smart device can pre-set the smart device state required for each ECU to perform an OTA upgrade. Furthermore, after the smart device receives the first OTA upgrade arrangement information, it flashes the ECU according to the flashing order indicated by the OTA upgrade arrangement information and the pre-set smart device state required for the ECU to perform an OTA upgrade.

[0010] In combination with the second aspect, in certain implementations of the second aspect, the first OTA upgrade arrangement information further indicates a smart device state required in the first upgrade phase.

[0011] In combination with the first aspect or the second aspect, in certain implementations of the first aspect or the second aspect, the method further includes: based on the first OTA upgrade scheduling information, controlling the display device to display at least one of the following: stage information of the first upgrade stage, information on the smart device status required for the first upgrade stage, or the flashing order of at least one ECU.

[0012] The stage information of the first upgrade stage indicates a specific stage of the first upgrade stage. For example, the stage information may indicate which specific stage the first upgrade stage is among installation, activation, and rollback.

[0013] In some implementations, the flashing order of the at least one ECU may be represented by a topological relationship of ECU icons, where each ECU icon represents an ECU in the smart device. Alternatively, the flashing order of the at least one ECU may be represented by other means, such as text or a table.

[0014] In the above technical solution, by displaying the stage information of the first upgrade stage, the information on the status of the smart device required for the first upgrade stage, and one or more items of the flashing order of at least one ECU, the user can intuitively determine whether the OTA upgrade arrangement information is consistent with expectations, which helps to improve the efficiency of OTA upgrade control.

[0015] In combination with the first aspect or the second aspect, in certain implementations of the first aspect or the second aspect, first OTA upgrade scheduling information is generated based on the M electronic control units ECU to be upgraded, including: generating second OTA upgrade scheduling information based on the M ECUs; updating any one of the following items in the second OTA upgrade scheduling information according to user instructions to obtain the first OTA upgrade scheduling information: the flashing order of at least one ECU; information on the status of the smart device required for the first upgrade stage; or stage information of the first upgrade stage.

[0016] In the above technical solution, a method is provided for users to modify the OTA upgrade arrangement information, so that users can flexibly divide the upgrade stages for different vehicles or models, customize the smart device status required for the upgrade stage, and the serial and parallel order of flashing ECUs, which helps to reduce the development cost of OTA upgrade control.

[0017] In combination with the first aspect or the second aspect, in certain implementations of the first aspect or the second aspect, the method further includes: receiving ECU flashing information from a smart device, the ECU flashing information indicating the flashing result and / or flashing progress of a first ECU, and at least one ECU including the first ECU; according to the ECU flashing information, controlling the display device to display the upgrade progress of the first upgrade stage, the upgrade progress including the flashing result and / or flashing progress of the first ECU.

[0018] In the above technical solution, during the OTA upgrade process, the flashing results and / or flashing progress of each ECU in at least one ECU can be displayed through a display device, so that the user can intuitively determine the upgrade progress and the ECU that failed to flash, which facilitates subsequent problem handling and operation and maintenance management.

[0019] In combination with the first aspect or the second aspect, in certain implementations of the first aspect or the second aspect, the first upgrade stage includes any one of the following: installation, activation, and rollback.

[0020] In combination with the first aspect or the second aspect, in certain implementations of the first aspect or the second aspect, first OTA upgrade scheduling information is generated based on the M electronic control units ECU to be upgraded, including: generating first OTA upgrade scheduling information based on the M ECUs and smart device upgrade scheduling information; wherein the smart device upgrade scheduling information indicates the upgrade stage of each ECU in the N ECUs in the smart device, the smart device status information required for each upgrade stage, and the flashing order of the ECUs in each upgrade stage in each upgrade stage, and the N ECUs include M ECUs.

[0021] It can be understood that N is an integer greater than or equal to M.

[0022] Exemplarily, the N ECUs may be all ECUs in the smart device, or they may be some of the ECUs in the smart device. For example, the N ECUs may be ECUs in the smart device that support OTA upgrades. The smart device upgrade schedule information may be generated based on user instructions, for example, in response to a user operation in an interface displaying the upgrade schedule information; or the smart device upgrade schedule information may be imported externally.

[0023] In this technical solution, users can pre-configure upgrade schedule information for all ECUs in a smart device. When performing an OTA upgrade on the smart device, the OTA upgrade schedule is generated for the ECUs to be upgraded based on the pre-configured upgrade schedule information. Furthermore, if some ECUs require flashing, there's no need to send the upgrade schedule for all ECUs in the smart device to the vehicle, which helps reduce communication overhead.

[0024] In combination with the first aspect or the second aspect, in certain implementations of the first aspect or the second aspect, the smart device state required in the first upgrade stage includes a power supply state and / or a KL15 state of the smart device.

[0025] In some implementations, taking a vehicle as an example, the smart device status required for the first upgrade phase may also include the vehicle status, such as the vehicle's driving status and vehicle availability status. The vehicle's driving status indicates whether the vehicle is allowed to drive during the upgrade process; the vehicle's availability status indicates whether all vehicle functions are disabled or partially available during the upgrade process.

[0026] In the above technical solution, the OTA upgrade arrangement information is used to directly indicate to the vehicle the smart device status required for the first upgrade stage, which helps to improve the flexibility of OTA upgrade control.

[0027] In a third aspect, an OTA upgrade method is provided, which can be executed by a smart device, or by a chip or circuit in the smart device. The method may include: receiving first OTA upgrade scheduling information, the first OTA upgrade scheduling information indicating at least one upgrade stage, the smart device state required for the first upgrade stage in at least one upgrade stage, and the flashing order of at least one ECU in the first upgrade stage; controlling the smart device to adjust to the smart device state required for the first upgrade stage according to the first OTA upgrade scheduling information, and controlling at least one ECU to flash according to the flashing order.

[0028] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: sending ECU flash information to the OTA server, the ECU flash information indicating the flash result and / or flash progress of the first ECU, and at least one ECU including the first ECU; wherein the ECU flash information is used by the OTA server to display the upgrade progress of the first upgrade stage, and the upgrade progress includes the flash result and / or flash progress of the first ECU.

[0029] In combination with the third aspect, in certain implementations of the third aspect, the first upgrade stage includes any one of the following: installation, activation, and rollback.

[0030] In combination with the third aspect, in certain implementations of the third aspect, the smart device state required in the first upgrade stage includes a power supply state and / or a KL15 state of the smart device.

[0031] In a fourth aspect, a device for OTA upgrade is provided, which includes a processing unit and a transceiver unit, wherein the processing unit is used to: generate first OTA upgrade scheduling information based on M electronic control units ECU to be upgraded, the first OTA upgrade scheduling information indicates at least one upgrade stage, the smart device status required for the first upgrade stage in at least one upgrade stage, and the flashing order of at least one ECU in the first upgrade stage; wherein the total number of ECUs included in each upgrade stage in at least one upgrade stage is M, and M is an integer greater than or equal to 1; the transceiver unit is used to: send the first OTA upgrade scheduling information to the smart device, and the first OTA upgrade scheduling information is used for the smart device to flash the ECU.

[0032] In combination with the fourth aspect, in certain implementations of the fourth aspect, the processing unit is further used to: control the display device to display at least one of the following items based on the first OTA upgrade scheduling information: stage information of the first upgrade stage, information on the status of the smart device required for the first upgrade stage, or the flashing order of at least one ECU.

[0033] In combination with the fourth aspect, in certain implementations of the fourth aspect, the processing unit is used to: generate second OTA upgrade scheduling information based on M ECUs; update any one of the following items in the second OTA upgrade scheduling information according to user instructions to obtain first OTA upgrade scheduling information: the flashing order of at least one ECU; information on the smart device status required for the first upgrade stage; and stage information of the first upgrade stage.

[0034] In combination with the fourth aspect, in certain implementations of the fourth aspect, the transceiver unit is further used to: receive ECU flash information from a smart device, the ECU flash information indicating the flash result and / or flash progress of a first ECU, and at least one ECU includes the first ECU; the processing unit is used to: control the display device to display the upgrade progress of the first upgrade stage according to the ECU flash information, and the upgrade progress includes the flash result and / or flash progress of the first ECU.

[0035] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first upgrade stage includes any one of the following: installation, activation, and rollback.

[0036] In combination with the fourth aspect, in certain implementations of the fourth aspect, the processing unit is used to: generate first OTA upgrade scheduling information based on M ECUs and smart device upgrade scheduling information; wherein the smart device upgrade scheduling information indicates the upgrade stage of each ECU in the N ECUs in the smart device, the smart device status information required for each upgrade stage, and the flashing order of the ECUs in each upgrade stage in each upgrade stage, and the N ECUs include M ECUs.

[0037] In combination with the fourth aspect, in certain implementations of the fourth aspect, the smart device state required in the first upgrade stage includes a power supply state and / or a KL15 state of the smart device.

[0038] In a fifth aspect, a device for OTA upgrade is provided, which includes a transceiver unit and a processing unit, wherein the transceiver unit is used to: receive first OTA upgrade scheduling information, the first OTA upgrade scheduling information indicates at least one upgrade stage, the smart device state required for the first upgrade stage in at least one upgrade stage, and the flashing order of at least one ECU in the first upgrade stage; the processing unit is used to: control the smart device to adjust to the smart device state required for the first upgrade stage according to the first OTA upgrade scheduling information, and control at least one ECU to flash in the flashing order.

[0039] In combination with the fifth aspect, in certain implementations of the fifth aspect, the transceiver unit is further used to: send ECU flash information to the OTA server, the ECU flash information indicating the flash result and / or flash progress of the first ECU, and at least one ECU includes the first ECU; wherein the ECU flash information is used by the OTA server to display the upgrade progress of the first upgrade stage, and the upgrade progress includes the flash result and / or flash progress of the first ECU.

[0040] In combination with the fifth aspect, in certain implementations of the fifth aspect, the first upgrade stage includes any one of the following: installation, activation, and rollback.

[0041] In combination with the fifth aspect, in certain implementations of the fifth aspect, the smart device status required in the first upgrade stage includes a power supply status and / or a KL15 status of the smart device.

[0042] In the sixth aspect, an OTA upgrade device is provided, which includes at least one processor, the at least one processor is coupled to at least one memory, and the at least one processor is used to execute a computer program or instruction stored in the at least one memory so that the device performs a method in any possible implementation of the first aspect or the second aspect.

[0043] In the seventh aspect, an OTA upgrade device is provided, which includes at least one processor, the at least one processor is coupled to at least one memory, and the at least one processor is used to execute a computer program or instruction stored in the at least one memory so that the device performs a method as in any possible implementation method of the third aspect.

[0044] In an eighth aspect, an OTA server is provided, which includes a device as in any possible implementation of the fourth aspect or the sixth aspect.

[0045] In a ninth aspect, a smart device is provided, comprising an apparatus as in any possible implementation of the fifth aspect or the seventh aspect.

[0046] In combination with the ninth aspect, in certain implementations of the ninth aspect, the smart device is a vehicle.

[0047] In the tenth aspect, a system for OTA upgrade is provided, the system comprising the device of any possible implementation of the fourth aspect and the device of any possible implementation of the fifth aspect; or, the system comprising the device of any possible implementation of the sixth aspect and the device of any possible implementation of the seventh aspect; or, the system comprising the OTA server of any possible implementation of the eighth aspect and the smart device of any possible implementation of the ninth aspect.

[0048] In the eleventh aspect, a computer program product is provided, comprising: a computer program code, which, when executed on a computer, enables the computer to execute a method in any possible implementation of the first aspect, the second aspect, or the fourth aspect.

[0049] It should be noted that the above-mentioned computer program code may be stored in whole or in part on a first storage medium, wherein the first storage medium may be packaged together with the processor or separately from the processor.

[0050] In the twelfth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores instructions. When the instructions are executed by a processor, the processor implements the method in any possible implementation of the first aspect, the second aspect, or the fourth aspect.

[0051] In a thirteenth aspect, a chip is provided, which includes a circuit for executing the method in any possible implementation of the first aspect, the second aspect, or the fourth aspect.

[0052] The beneficial effects brought about by the third to thirteenth aspects mentioned above can be specifically referred to the description of the beneficial effects in the first or second aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] FIG1 is a schematic block diagram of an OTA upgrade system architecture provided in an embodiment of the present application;

[0054] FIG2 is another schematic block diagram of the OTA upgrade system architecture provided in an embodiment of the present application;

[0055] FIG3 is a schematic flow chart of an OTA upgrade method provided in an embodiment of the present application;

[0056] FIG4 is a schematic diagram of an OTA upgrade related information display interface provided in an embodiment of the present application;

[0057] FIG5 is another schematic diagram of an OTA upgrade related information display interface provided in an embodiment of the present application;

[0058] FIG6 is a schematic block diagram of an OTA upgrade device provided in an embodiment of the present application;

[0059] FIG7 is another schematic block diagram of the OTA upgrade device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] The embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0061] Figure 1 shows a schematic diagram of an OTA upgrade system architecture provided by an embodiment of the present application. As shown in Figure 1, the system includes an OTA server 100 and a smart device 200. The OTA server 100 includes a management entry module 110 and a business management service module 120; the smart device 200 includes an upgrade management module 210 and a flash management module 220. OTA upgrade-related information, such as OTA upgrade packages and control information during the OTA upgrade process, can be transmitted between the OTA server 100 and the smart device 200 through the business management service module 120 and the upgrade management module 210.

[0062] More specifically, the management entry module 110 provides an interface for managing OTA upgrade-related information. For example, the management entry module 110 can determine the OTA upgrade scheduling information based on the information of the ECU to be upgraded and the smart device upgrade scheduling information; or, the management entry module 110 can generate OTA upgrade scheduling information in response to user operations. The above-mentioned smart device upgrade scheduling information indicates the OTA upgrade stages corresponding to all ECUs in the vehicle, the smart device status required for the OTA upgrade, and the upgrade order of at least one ECU in each OTA upgrade stage. The above-mentioned OTA upgrade scheduling information includes information on the ECU flashing order of the smart device during the current OTA upgrade process and information on the smart device status required for the OTA upgrade, or the OTA upgrade scheduling information may also include information on the OTA upgrade stage. The OTA upgrade scheduling information can be understood as a type of control information in the OTA upgrade process.

[0063] The management entry module 110 saves the OTA upgrade schedule information to the service management service module 120. When the smart device 200 needs to be upgraded, the service management service module 120 sends the OTA upgrade schedule information to the upgrade management module 210. The upgrade management module 210 parses the OTA upgrade schedule information, adjusts the smart device status according to the OTA upgrade schedule information, and controls the ECU flashing.

[0064] The flash management module 220 is used to perform specific ECU flashing and to feed back ECU flashing information to the upgrade management module 210. The ECU flashing information includes the ECU flashing results and / or flashing progress. The upgrade management module 210 sends the ECU flashing information to the business management service module 120, and the business management service module 120 stores the ECU flashing information. The management entry module 110 queries the business management service module 120 to obtain the ECU flashing information, and controls the display of the OTA upgrade progress and the flashing progress or flashing results of each ECU during the OTA upgrade process based on the ECU flashing results. In addition, the management entry module 110 can also control the display device to display the OTA upgrade scheduling information.

[0065] The smart devices involved in this application may include land vehicles, water vehicles, air vehicles, industrial equipment, agricultural equipment, or entertainment equipment, etc. For example, the smart device can be a vehicle, which is a vehicle in a broad sense, and can be a vehicle (such as a commercial vehicle, a passenger car, a motorcycle, a flying car, a train, etc.), an industrial vehicle (such as a forklift, a trailer, a tractor, etc.), an engineering vehicle (such as an excavator, a bulldozer, a crane, etc.), agricultural equipment (such as a lawn mower, a harvester, etc.), amusement equipment, a toy vehicle, etc. The embodiments of this application do not specifically limit the type of vehicle. For another example, the smart device can be an intelligent robot, a smart home device, a drone, an airplane, or a ship, etc. The following takes the smart device as an example to introduce the technical solution of this application.

[0066] Taking the smart device 200 as a vehicle as an example, FIG2 shows a schematic diagram of a system architecture when the OTA upgrade solution provided in an embodiment of the present application is applied in a vehicle. As shown in FIG2 , the vehicle may include at least one ECU (such as ECU 1 to ECU n), a device for communicating with external devices inside the vehicle, such as a communication box (telematics box, T-Box), a gateway (gateway, GW) and a control center. Among them, GW is a core component in the electronic and electrical architecture of the entire vehicle. As the data interaction hub of the entire vehicle network, it can route network data such as the control area network (CAN) and the local interconnect network (LIN) in different networks. The control center realizes data transmission and reception between the ECU through the gateway.

[0067] In some implementations, the upgrade management module 210 and the flash management module 220 can be set in the same device, for example, in a gateway or a control center, and the upgrade management module 210 establishes a connection with the business management service module 120 in the OTA server 100 through a T-Box; or, the upgrade management module 210 and the flash management module 220 can also be set in a T-Box. In some implementations, the upgrade management module 210 and the flash management module 220 can also be set in different devices, for example, the upgrade management module 210 is set in a T-Box, and the flash management module is set in a gateway or a control center. In a specific implementation, the upgrade management module 210 can control the vehicle status through the gateway, and the flash management module 220 controls the flashing of the target ECU through the gateway.

[0068] When the vehicle's electronic and electrical architecture is a domain-centralized architecture, the control center may be a domain controller, such as a vehicle domain controller (VDC), an advanced driving domain controller (ADC), or a cockpit domain controller (CDC). For another example, the control center may include an in-car application-server (ICAS) controller, a body domain controller (BDC), a special equipment system (SAS), a media graphics unit (MGU), a body super core (BSC), or an advanced driving assistant system super core (ADAS super core), and this application does not limit this. The ICAS may include at least one of the following: a vehicle control server ICAS1, an intelligent driving server ICAS2, an intelligent cockpit server ICAS3, and an infotainment server ICAS4. Alternatively, the control center may include the central computing platform in the above-mentioned embodiment, for example, a vehicle central computer (VCC). When the vehicle electrical and electronic architecture is a centralized architecture, the control center may be a central computing platform, such as a vehicle central computer (VCC).

[0069] It should be understood that the architectures shown in FIG. 1 and FIG. 2 are merely exemplary. In a specific implementation, the system shown in FIG. 1 or FIG. 2 may include more or fewer modules or components.

[0070] The above introduces the system architecture provided by the embodiment of the present application, and the following describes in detail the method provided by the embodiment of the present application.

[0071] Figure 3 shows a schematic flowchart of the OTA upgrade method provided in an embodiment of the present application. The method 300 shown in Figure 3 can be executed by the system shown in Figure 1 or Figure 2, wherein the steps executed by the OTA server can be executed by a chip or circuit set in the OTA server, and the steps executed by the smart device can be executed by a chip or circuit set in the smart device. The method includes S301 to S305.

[0072] S301, the OTA server generates first OTA upgrade scheduling information based on M ECUs to be upgraded in the smart device. The first OTA upgrade scheduling information indicates at least one upgrade stage, a smart device state required for a first upgrade stage in at least one upgrade stage, and an upgrade order of at least one ECU in the first upgrade stage.

[0073] The total number of ECUs included in each upgrade stage in at least one upgrade stage is M, and M is an integer greater than or equal to 1.

[0074] Illustratively, before executing S301 , the smart device may report information of M ECUs to be upgraded to the OTA server; or, the OTA server determines the M ECUs to be upgraded of the smart device in response to a user operation, wherein the user operation is used to select the M ECUs.

[0075] For example, the first upgrade phase can be one of an installation phase, an activation phase, and a rollback phase. The smart device state required for the first upgrade phase can include a required power supply state, such as whether a high voltage state or a low voltage state is required. Alternatively, the smart device state required for the first upgrade phase can include whether KL15 power-up is required. The upgrade sequence for at least one ECU can include a serial upgrade sequence for two or more ECUs and / or a parallel upgrade sequence for two or more ECUs.

[0076] It should be noted that the power supply status refers to whether the smart device is powered by a high-voltage battery (or engine) or a low-voltage battery. When the smart device is powered by a high-voltage battery, the power supply status is high; when the smart device is powered by a low-voltage battery, the power supply status is low. The high-voltage battery can be a power battery, and the low-voltage battery can be a storage battery. The KL15 is used to directly power some ECUs in a low-voltage state. If some ECUs need to be powered on by the KL15 to wake up, these ECUs need to be powered on by the KL15 during the flashing process. If some ECUs can wake up without the KL15, these ECUs do not need to be powered on by the KL15 during the flashing process.

[0077] In some implementations, generating first OTA upgrade scheduling information based on the M ECUs to be upgraded may include: generating second OTA upgrade scheduling information based on the M ECUs; updating any of the following items in the second OTA upgrade scheduling information according to user instructions to obtain the first OTA upgrade scheduling information: the flashing order of at least one ECU; information on the smart device status required for the first upgrade phase; or phase information of the first upgrade phase.

[0078] In other implementations, generating the first OTA upgrade schedule information based on the M ECUs to be upgraded may further include: generating the first OTA upgrade schedule information based on the M ECUs and smart device upgrade schedule information. The smart device upgrade schedule information indicates the upgrade stage of each of the N ECUs in the smart device, smart device status information required for each upgrade stage, and the flashing order of the ECUs within each upgrade stage, where the N ECUs include the M ECUs. Exemplarily, the N ECUs may be all ECUs in the smart device, or may be a portion of the ECUs in the smart device.

[0079] For example, the smart device upgrade arrangement information may be generated according to a user instruction, or may be externally imported into an OTA server.

[0080] In some further implementations, the first OTA upgrade schedule information may be generated according to a user instruction.

[0081] Exemplarily, generating OTA upgrade orchestration information according to user instructions may include: S1, determining upgrade stage 1 according to a first instruction, S2, determining the smart device state required for upgrade stage 1 according to a second instruction, and S3, determining at least one ECU in upgrade stage 1 and the upgrade order of at least one ECU according to a third instruction. The OTA upgrade orchestration information may include the above-mentioned smart device upgrade orchestration information, or may also include the first OTA upgrade orchestration information. When the OTA upgrade orchestration information is the first OTA upgrade orchestration information, upgrade stage 1 may be the first upgrade stage; when the OTA upgrade orchestration information is the smart device upgrade orchestration information, upgrade stage 1 may be any of the upgrade stages described in the above embodiments. In the specific implementation process, the execution order of S1 to S3 may be S1 to S3 sequentially, or may be executed in any flexible combination order, for example, executing S3 first, and then executing S1 and S2. The following describes an implementation method for generating OTA upgrade orchestration information according to user instructions in conjunction with Figure 4.

[0082] As shown in (a) of Figure 4, the OTA server controls the layout interface of the display device to display the upgrade stage information area 401 and the ECU selection area 402. Among them, the upgrade stage information area 401 includes several stages that may be involved in the OTA upgrade, and the ECU selection area 402 includes multiple icons, each icon indicating an ECU. In a specific implementation, the ECUs that need to be upgraded in a certain stage can be determined in response to the user dragging one or more icons in the ECU selection area 402 into a certain stage in the upgrade stage information area 401. For example, if the user drags the icons of ECU_1 to ECU_7 to the installation stage of the upgrade stage information area 401, the OTA server can determine that the ECUs that need to be upgraded in the installation stage include ECU_1 to ECU_7. It is understandable that the third instruction may include an instruction generated based on the user dragging the icons of ECU_1 to ECU_7 to the installation stage.

[0083] Furthermore, in response to a user clicking on a specific stage in the upgrade stage information area 401, the user can switch to the detailed configuration interface for that stage. Taking the installation stage as an example, as shown in FIG4(b), the detailed configuration interface 403 includes icons for ECU_1 to ECU_7, which are determined to require upgrading during the installation stage in response to the user's dragging action, as well as a status settings bar 404 and a toolbar 405. For example, the status settings bar 404 includes information related to the smart device status required for the upgrade, such as power supply status information 4041 and KL15 status information. The KL15 status indicates whether the KL15 is powered on or off. When the KL15 is off, the KL15 is powered off; when the KL15 is on, the KL15 is powered on. If the user clicks the "High Voltage" button in 4041, it is determined that the power supply needs to be high voltage during the installation stage. If the user clicks the "On" button in 4042, it is determined that the KL15 needs to be powered on during the installation stage. Furthermore, in response to a user clicking one or more of the icons ECU_1 through ECU_7, or clicking the "Remove" button in toolbar 405, the ECUs indicated by these one or more icons can be deleted from the installation phase. For example, in response to a user clicking a connecting line and then clicking the icons of ECU_4 and ECU_5, respectively, a flashing order relationship between ECU_4 and ECU_5 can be established; and in response to a user clicking a connecting line and then clicking the icons of ECU_4 and ECU_6, ​​respectively, a flashing order relationship between ECU_4 and ECU_6 can be established. Based on the flashing order of ECU_4 and ECU_5, and the flashing order of ECU_4 and ECU_6, ​​the OTA server can determine that ECU_4 and ECU_5, and ECU_4 and ECU_6, ​​are flashed serially, respectively, and that ECU_5 and ECU_6 are flashed in parallel. It can be understood that the first instruction may include an instruction generated based on the user clicking on the installation stage; the second instruction may include an instruction generated based on the user clicking on a button in the status setting bar 404; the third instruction may include an instruction generated based on the user clicking on the connecting line and then clicking on the icons of two ECUs respectively, and the third instruction may also include an instruction generated based on the user clicking on the "Remove" button and then clicking on the icon of a certain ECU.

[0084] Optionally, after executing S301, S302' may also be executed: the OTA server controls a display device to display OTA upgrade scheduling information. For example, after the flashing order of at least one ECU in upgrade phase 1 and the required smart device status for upgrade phase 1 are set, the OTA server may control the display device to display a scheduling interface as shown in FIG4(c). This scheduling interface includes information about the upgrade phase and the required smart device status, such as the "High Voltage Installation Phase" shown in block 406. "Installation Phase" indicates the specific upgrade phase, and "High Voltage" indicates the required smart device status for upgrade phase 1. This scheduling interface may also display an icon for at least one ECU in upgrade phase 1, such as icon 407 for ECU_1, and icons indicating the flashing order of at least one ECU, such as connecting line 408, with the arrow indicating the flashing direction, i.e., after ECU_1 is flashed, ECU_2 is flashed. Furthermore, FIG4(c) also intuitively displays the serial and parallel flashing order between at least one ECU, such as parallel flashing between ECU_1 and ECU_4 and serial flashing between ECU_1 and ECU_3.

[0085] S302: The OTA server sends first OTA upgrade scheduling information to the smart device.

[0086] For example, taking the smart device as a vehicle, the OTA server can send the first OTA upgrade arrangement information to the vehicle through the vehicle's T-Box.

[0087] S303: The smart device flashes the ECU according to the first OTA upgrade arrangement information.

[0088] Exemplarily, the smart device adjusts the smart device to the corresponding smart device state according to the information of the smart device state required in the first upgrade phase, and then controls the flashing of each ECU in the at least one ECU in sequence according to the upgrade order of the at least one ECU.

[0089] S304: The smart device sends ECU flashing information to the OTA server.

[0090] Exemplarily, the ECU flashing information may include an ECU flashing result and / or an ECU flashing progress.

[0091] For example, during the flashing process of one or more ECUs, the smart device can send the flashing progress information of each of the one or more ECUs to the OTA server. Alternatively, after the flashing results of one or more ECUs are completed, the smart device can send the flashing result information of each of the one or more ECUs to the OTA server, such as flashing success or flashing failure.

[0092] In some implementations, the smart device periodically reports ECU flash information to the OTA server. The ECU flash information reported in each cycle may include information about the ECU being flashed, as well as information about the ECU that has been flashed but not reported in the previous cycle.

[0093] S305 , the OTA server controls the display device to display the upgrade progress of the first upgrade phase according to the ECU flashing information. The upgrade progress includes the ECU flashing progress and / or the ECU flashing result.

[0094] For example, if the ECU flashing information indicates the flashing result and / or flashing progress of a first ECU, the OTA server can determine the upgrade progress of the first upgrade phase based on the location of the first ECU in the at least one ECU, as well as the flashing result and / or flashing progress of the first ECU. For example, if the first ECU includes ECU_1 and ECU_4 in the installation phase, and the ECU flashing information indicates that the flashing of ECU_1 and ECU_4 has been completed and successful, the OTA server can determine that the current upgrade progress is that the flashing of ECU_1 and ECU_4 has been completed and successful, and control the display device to display that the flashing of ECU_1 and ECU_4 has been successful, and that the ECUs following ECU_1 and ECU_4 in the upgrade order have not yet been flashed. For another example, if the first ECU includes ECU_2 in the installation phase, and the ECU flashing information indicates that ECU_2 is being flashed, the OTA server can determine that the current upgrade progress is that the flashing of ECU_2 has been completed, and that the ECUs following ECU_2 have not yet been flashed.

[0095] For example, when the control display device displays the upgrade progress, different colors can be used to represent the different states of each ECU. For example, as shown in Figure 5, the display device displays the upgrade progress of the high-voltage installation phase in the status interface. Color 1 indicates that the execution (or flashing) is completed and successful, color 2 indicates that the flashing is in progress, color 3 indicates that the execution (or flashing) has not yet been completed, and color 4 indicates that the flashing has failed.

[0096] It should be noted that the interfaces shown in Figures 4 and 5 are only exemplary. In actual implementation, the OTA upgrade scheduling information and OTA upgrade progress information can be displayed in other forms.

[0097] The present invention provides an OTA upgrade method that provides a flexible way to organize and display OTA upgrade information. Through an operation interface, users can flexibly divide upgrade stages, customize the smart device states required for each upgrade stage, and specify the serial and parallel order of ECU flashing, thereby reducing the development cost of OTA upgrade control. Furthermore, during the OTA upgrade process, the operation interface can display the upgrade progress, such as the flashing results and / or flashing progress of each ECU, to operation and maintenance personnel, facilitating operation and maintenance management.

[0098] The above text describes in detail the OTA upgrade method provided by the embodiments of the present application in conjunction with Figures 1 to 5. In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0099] The apparatus provided in the embodiments of the present application will be described in detail below with reference to Figures 6 and 7. It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment, and therefore, for matters not described in detail, reference can be made to the method embodiment above, and for the sake of brevity, no further description will be given here.

[0100] Figure 6 shows a schematic block diagram of an apparatus 1000 for OTA upgrade provided in an embodiment of the present application. The apparatus 1000 may include units for executing the method in Figure 3. In addition, each unit in the apparatus 1000 is for implementing the corresponding process of the method embodiment in Figure 3.

[0101] Specifically, the device 1000 includes a processing unit 1010 and a transceiver unit 1020 .

[0102] Optionally, the device 1000 also includes a storage unit, which can be used to store instructions and / or data, and the processing unit 1010 can read the instructions and / or data in the storage unit so that the device implements the relevant actions performed by the terminal device in the aforementioned various method embodiments.

[0103] The apparatus 1000 can be used to execute the actions performed by the OTA server or smart device in each of the above method embodiments. In this case, the apparatus 1000 can be a component of the OTA server or smart device, for example, a chip or integrated circuit in the OTA server or smart device. The processing unit 1010 is used to execute the processing-related operations of the OTA server or smart device in the above method embodiments, and the transceiver unit 1020 is used to execute the transceiver-related operations of the OTA server or smart device in the above method embodiments.

[0104] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0105] In a specific implementation, the actions performed by the processing unit 1010 and the transceiver unit 1020 may be implemented by one processor, or may be implemented by multiple processors.

[0106] In an embodiment of the present application, the processor may be a central processing unit (CPU), a digital signal processor (DSP), etc. Alternatively, the processor may be a circuit having a signal processing capability, and in one implementation, the processor may implement a certain function through the logical relationship of a hardware circuit, the logical relationship of the hardware circuit being fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as a field programmable gate array (FPGA). In a reconfigurable hardware circuit, the processor loads a configuration document to implement the process of hardware circuit configuration, which may be understood as a process in which the processor loads instructions to implement the functions of some or all of the above units. In addition, it may also be a hardware circuit designed for artificial intelligence, which may be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0107] Figure 7 is another schematic block diagram of an apparatus for OTA upgrade provided in an embodiment of the present application. The apparatus 1100 shown in Figure 7 may include: a processor 1110, a transceiver 1120, and a memory 1130. The processor 1110, the transceiver 1120, and the memory 1130 are connected via an internal connection path, the memory 1130 is used to store instructions, and the processor 1110 is used to execute the instructions stored in the memory 1130 to implement the methods in the above embodiments. Optionally, the memory 1130 can be coupled to the processor 1110 through an interface or integrated with the processor 1110.

[0108] It should be noted that the transceiver 1120 may include but is not limited to a transceiver device such as an input / output interface to implement communication between the apparatus 1100 and other devices or a communication network.

[0109] Memory 1130 may be a volatile memory and / or a non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM may be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0110] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0111] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0112] The transceiver 1120 uses a transceiver device such as but not limited to a transceiver to implement communication between the apparatus 1100 and other devices or a communication network, so as to receive / send data / information used to implement the methods in the above embodiments.

[0113] The device 1100 may be a chip or circuit provided in the above-mentioned OTA server, or the device 1100 may also be a chip or circuit provided in a smart device.

[0114] An embodiment of the present application also provides a system for OTA upgrade, which includes the above-mentioned device 1000 or device 1100, or the system includes the OTA server and smart device in the above-mentioned embodiment.

[0115] An embodiment of the present application further provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer implements the methods in the above embodiments of the present application.

[0116] An embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the computer implements the methods in the above embodiments of the present application.

[0117] An embodiment of the present application also provides a chip, including a circuit, for executing the methods in the above embodiments of the present application.

[0118] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0119] In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is a kind of association relationship that describes associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In this application, "at least one" refers to one or more, and "more than one" refers to two or more. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0120] In the embodiments of this application, prefixes such as "first" and "second" are used only to distinguish different description objects and have no limiting effect on the position, order, priority, quantity, or content of the described objects. The use of prefixes such as ordinal numbers in the embodiments of this application to distinguish description objects does not constitute a limitation on the described objects. For a statement of the described objects, please refer to the description in the context of the claims or embodiments, and the use of such prefixes should not constitute an unnecessary limitation.

[0121] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0122] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0123] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0124] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0125] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. An OTA upgrade method, characterized in that, Including: Generating first OTA upgrade scheduling information according to M electronic control units (ECUs) to be upgraded in the intelligent device, where the first OTA upgrade scheduling information indicates at least one upgrade stage, the intelligent device status required for the first upgrade stage in the at least one upgrade stage, and the flashing order of at least one ECU in the first upgrade stage; Wherein, the total number of ECUs included in each upgrade stage in the at least one upgrade stage is M, and M is an integer greater than or equal to 1; Sending the first OTA upgrade scheduling information to the intelligent device, where the first OTA upgrade scheduling information is used for the intelligent device to perform ECU flashing.

2. The method according to claim 1, wherein The method further includes: Controlling a display device to display at least one of the following according to the first OTA upgrade scheduling information: the stage information of the first upgrade stage, the information of the intelligent device status required for the first upgrade stage, or the flashing order of the at least one ECU.

3. The method according to claim 1 or 2, characterized in that, The generating the first OTA upgrade scheduling information according to M electronic control units (ECUs) to be upgraded in the intelligent device includes: Generating second OTA upgrade scheduling information according to the M ECUs; Updating any one of the following in the second OTA upgrade scheduling information according to a user instruction to obtain the first OTA upgrade scheduling information: The flashing order of the at least one ECU; The information of the intelligent device status required for the first upgrade stage; or The stage information of the first upgrade stage.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Receiving ECU flashing information from the intelligent device, where the ECU flashing information indicates the flashing result and / or flashing progress of a first ECU, and the at least one ECU includes the first ECU; Controlling a display device to display the upgrade progress of the first upgrade stage according to the ECU flashing information, where the upgrade progress includes the flashing result and / or flashing progress of the first ECU.

5. The method according to any one of claims 1 to 4, characterized in that, The first upgrade stage includes any one of the following: installation, activation, rollback.

6. The method according to any one of claims 1 to 5, characterized in that The generating the first OTA upgrade scheduling information according to M electronic control units (ECUs) to be upgraded in the intelligent device includes: Generating the first OTA upgrade scheduling information according to the M ECUs and intelligent device upgrade scheduling information; Wherein, the intelligent device upgrade scheduling information indicates the upgrade stage of each of the N ECUs in the intelligent device, the intelligent device status information required for each upgrade stage, and the flashing order of the ECUs in each upgrade stage, and the N ECUs include the M ECUs.

7. The method according to any one of claims 1 to 6, characterized in that, The intelligent device status required for the first upgrade stage includes the power supply status and / or KL15 status of the intelligent device.

8. An OTA upgrade method, characterized in that, Including: Receiving first OTA upgrade scheduling information, where the first OTA upgrade scheduling information indicates at least one upgrade stage, the intelligent device status required for the first upgrade stage in the at least one upgrade stage, and the flashing order of at least one ECU in the first upgrade stage; Controlling the intelligent device to adjust to the intelligent device status required for the first upgrade stage according to the first OTA upgrade scheduling information, and controlling the at least one ECU to perform flashing according to the flashing order.

9. The method according to claim 8, wherein The method further includes: Sending ECU flashing information to an OTA server, where the ECU flashing information indicates the flashing result and / or flashing progress of a first ECU, and the at least one ECU includes the first ECU; Wherein, the ECU flashing information is used for the OTA server to display the upgrade progress of the first upgrade stage, and the upgrade progress includes the flashing result and / or flashing progress of the first ECU.

10. The method according to claim 8 or 9, characterized in that, The first upgrade stage includes any one of the following: installation, activation, rollback.

11. The method according to any one of claims 8 to 10, characterized in that, The smart device status required for the first upgrade stage includes the power supply status and / or KL15 status of the smart device.

12. An apparatus for OTA upgrade, characterized in that, It includes: A processing unit, configured to generate first OTA upgrade scheduling information according to M electronic control units (ECUs) to be upgraded by a smart device, where the first OTA upgrade scheduling information indicates at least one upgrade stage, the smart device status required for the first upgrade stage in the at least one upgrade stage, and the flashing order of at least one ECU in the first upgrade stage; Wherein, the total number of ECUs included in each upgrade stage in the at least one upgrade stage is M, and M is an integer greater than or equal to 1; A transceiver unit, configured to send the first OTA upgrade scheduling information to the smart device, and the first OTA upgrade scheduling information is used for the smart device to perform ECU flashing.

13. The device according to claim 12, characterized in that, The processing unit is further configured to: According to the first OTA upgrade scheduling information, control a display device to display at least one of the following: the stage information of the first upgrade stage, the information of the smart device status required for the first upgrade stage, or the flashing order of the at least one ECU.

14. The device according to claim 12 or 13, characterized in that, The processing unit is configured to: Generate second OTA upgrade scheduling information according to the M ECUs; Update any one of the following in the second OTA upgrade scheduling information according to a user instruction to obtain the first OTA upgrade scheduling information: The flashing order of the at least one ECU; The information of the smart device status required for the first upgrade stage; or The stage information of the first upgrade stage.

15. The device according to any one of claims 12 to 14, characterized in that The transceiver unit is further configured to: Receive ECU flashing information from the smart device, where the ECU flashing information indicates the flashing result and / or flashing progress of a first ECU, and the at least one ECU includes the first ECU; The processing unit is configured to: According to the ECU flashing information, control a display device to display the upgrade progress of the first upgrade stage, and the upgrade progress includes the flashing result and / or flashing progress of the first ECU.

16. The device according to any one of claims 12 to 15, characterized in that, The first upgrade stage includes any one of the following: installation, activation, rollback.

17. The device according to any one of claims 12 to 16, characterized in that The processing unit is configured to: Generate the first OTA upgrade scheduling information according to the M ECUs and the smart device upgrade scheduling information; Wherein, the smart device upgrade scheduling information indicates the upgrade stage of each of the N ECUs in the smart device, the smart device status information required for each upgrade stage, and the flashing order of each ECU in each upgrade stage, and the N ECUs include the M ECUs.

18. The device according to any one of claims 12 to 17, characterized in that The smart device states required for the first upgrade stage include the power supply state and / or the KL15 state of the smart device.

19. A device for OTA upgrade, characterized in that, Comprising: a transceiver unit configured to receive first OTA upgrade orchestration information, the first OTA upgrade orchestration information indicating at least one upgrade stage, the smart device states required for a first upgrade stage among the at least one upgrade stage, and the flashing order of at least one ECU in the first upgrade stage; a processing unit configured to control the smart device to adjust to the smart device states required for the first upgrade stage according to the first OTA upgrade orchestration information, and control the at least one ECU to perform flashing according to the flashing order.

20. The device according to claim 19, characterized in that, The transceiver unit is further configured to: send ECU flashing information to an OTA server, the ECU flashing information indicating the flashing result and / or the flashing progress of a first ECU, the at least one ECU including the first ECU; wherein the ECU flashing information is used for the OTA server to display the upgrade progress of the first upgrade stage, the upgrade progress including the flashing result and / or the flashing progress of the first ECU.

21. The device according to claim 19 or 20, characterized in that, The first upgrade stage includes any one of the following: installation, activation, rollback.

22. The device according to any one of claims 19 to 21, characterized in that, The smart device states required for the first upgrade stage include the power supply state and / or the KL15 state of the smart device.

23. A device for OTA upgrade, characterized in that, Comprising at least one processor, the at least one processor being coupled to at least one memory, the at least one processor being configured to execute computer programs or instructions stored in the at least one memory, so that the device executes the method according to any one of claims 1 to 7, or the method according to any one of claims 8 to 11.

24. A system for OTA upgrade, characterized in that, Comprising the device according to any one of claims 12 to 18, and the device according to any one of claims 19 to 22.

25. A computer-readable storage medium, characterized in that, Stored thereon are instructions which, when executed by a processor, cause the processor to implement the method according to any one of claims 1 to 7, or the method according to any one of claims 8 to 11.

26. A chip, characterized in that, The chip includes circuitry configured to execute the method according to any one of claims 1 to 7, or the method according to any one of claims 8 to 11.

Images