WO2025129447A1 - Ota升级方法、用于ota升级的装置和系统 - Google Patents

Ota升级方法、用于ota升级的装置和系统 Download PDF

Info

Publication number
WO2025129447A1
WO2025129447A1 PCT/CN2023/139848 CN2023139848W WO2025129447A1 WO 2025129447 A1 WO2025129447 A1 WO 2025129447A1 CN 2023139848 W CN2023139848 W CN 2023139848W WO 2025129447 A1 WO2025129447 A1 WO 2025129447A1
Authority
WO
WIPO (PCT)
Prior art keywords
upgrade
ecu
stage
ota
flashing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/139848
Other languages
English (en)
French (fr)
Inventor
徐友明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Yinwang Intelligent Technology Co Ltd
Original Assignee
Shenzhen Yinwang Intelligent Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Yinwang Intelligent Technology Co Ltd filed Critical Shenzhen Yinwang Intelligent Technology Co Ltd
Priority to CN202380037436.5A priority Critical patent/CN120642371A/zh
Priority to PCT/CN2023/139848 priority patent/WO2025129447A1/zh
Publication of WO2025129447A1 publication Critical patent/WO2025129447A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the present application relates to the field of vehicle networking technology, and more specifically, to an OTA upgrade method, a device and a system for OTA upgrade.
  • ECUs electronice control units
  • multiple ECUs may be dependent on each other or can be upgraded in parallel.
  • vehicle state required by each ECU in the multiple ECUs may be different, resulting in different upgrade control logics for vehicles of different models.
  • the ECU flashing order in the current OTA upgrade technology is generally "hard-coded" in the upgrade software code, which requires customized upgrade software for different models, increasing the cost of OTA upgrades.
  • 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.
  • an OTA upgrade method which can be executed by an OTA server, or by a chip or circuit in the OTA server, and the method can include: generating first OTA upgrade scheduling information according to M ECUs to be upgraded of a smart device, the first OTA upgrade scheduling information indicating at least one upgrade stage, a smart device state required for a first upgrade stage in at least one upgrade stage, and a 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.
  • the OTA server can generate information indicating the flashing order of multiple ECUs, the upgrade stage, and the smart device status required for the upgrade process in real time according to the multiple ECUs to be upgraded, and send it to the smart device for OTA upgrade.
  • the OTA upgrade process there is no need to "hard-code" information such as the flashing order of the smart device ECU and the smart device status required for the upgrade in the software code, which helps to improve the flexibility of ECU flashing control during the OTA upgrade process and reduce the cost of OTA upgrade control.
  • an OTA upgrade method which can be executed by an OTA server, or by a chip or circuit in the OTA server, and 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, and 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, and the first OTA upgrade scheduling information is used for the smart device to flash the ECU.
  • the required state of each ECU in the smart device may be different during OTA upgrade.
  • the ECU that manages the power battery in the vehicle can generally only be flashed when the vehicle is in a low-voltage state (that is, 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 (that is, 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. Further, after the smart device receives the first OTA upgrade scheduling information, it flashes the ECU according to the flashing order indicated by the OTA upgrade scheduling information and the pre-set smart device state required for the ECU to perform an OTA upgrade.
  • the stage information of the first upgrade stage indicates a specific stage of the first upgrade stage.
  • the stage information may indicate which specific stage of the first upgrade stage is installation, activation, or rollback.
  • the user can intuitively determine whether the OTA upgrade scheduling information is consistent with expectations, which helps to improve the efficiency of OTA upgrade control.
  • a method for modifying OTA upgrade arrangement information is provided for users, so that users can flexibly divide the upgrade stages according to 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.
  • the method further includes: receiving ECU flash information from a smart device, the ECU flash information indicating a flash result and/or flash progress of a first ECU, and at least one ECU including the first ECU; according to the ECU flash information, controlling a display device to display an upgrade progress of the first upgrade stage, the upgrade progress including the flash result and/or flash progress of the first ECU.
  • the first upgrade stage includes any one of the following: installation, activation, and rollback.
  • first OTA upgrade scheduling information is generated based on M electronic control units ECU to be upgraded, including: generating 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 ECUs in each upgrade stage in each upgrade stage, and the N ECUs include M ECUs.
  • N is an integer greater than or equal to M.
  • the N ECUs may be all ECUs in the smart device, or the N ECUs may be part 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 scheduling information may be generated according to user instructions, for example, the smart device upgrade scheduling information may be generated in response to user operations in an interface that displays the upgrade scheduling information; or, the smart device upgrade scheduling information may be externally imported.
  • the user can configure the upgrade arrangement information for all ECUs of the smart device in advance.
  • the OTA upgrade arrangement information can be generated for the ECU to be upgraded based on the ECU to be upgraded of the smart device and the pre-configured upgrade arrangement information.
  • some ECUs need to be flashed there is no need to send the upgrade arrangement information for all ECUs of the smart device to the vehicle, which helps to save communication overhead.
  • the smart device state required in the first upgrade stage includes a power supply state and/or a KL15 state of the smart device.
  • the smart device status required for the first upgrade stage may also include the vehicle status, such as vehicle driving status, vehicle availability status, etc.
  • vehicle driving status indicates whether the vehicle is allowed to drive during the upgrade process; the vehicle availability status indicates that all functions of the vehicle are disabled or partially available during the upgrade process.
  • 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.
  • an OTA upgrade method which can be executed by a smart device, or by a chip or circuit in the smart device, and the method may include: receiving first OTA upgrade scheduling information, the first OTA upgrade scheduling information indicating at least one upgrade stage, a smart device state required for a first upgrade stage in at least one upgrade stage, and a flashing sequence of at least one ECU in the first upgrade stage; control the smart device to adjust to the smart device state required for the first upgrade stage according to the first OTA upgrade arrangement information, and control at least one ECU to flash in accordance with the flash sequence.
  • the method also 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 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.
  • the first upgrade stage includes any one of the following: installation, activation, and rollback.
  • the smart device state required in the first upgrade stage includes a power supply state and/or a KL15 state of the smart device.
  • the processing unit is also 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.
  • the transceiver unit is also used to: receive ECU flash information from a smart device, the ECU flash information indicating a flash result and/or flash progress of a first ECU, and at least one ECU includes a first ECU; the processing unit is used to: control a display device to display an upgrade progress of the first upgrade stage according to the ECU flash information, the upgrade progress including the flash result and/or flash progress of the first ECU.
  • the first upgrade stage includes any of the following: installation, activation, and rollback.
  • 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.
  • an OTA upgrade device comprising 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 the third A method in any possible implementation of the aspect.
  • the smart device is a vehicle.
  • a system for OTA upgrade comprising an apparatus in any possible implementation manner of the fourth aspect and an apparatus in any possible implementation manner of the fifth aspect; or, the system comprising an apparatus in any possible implementation manner of the sixth aspect and an apparatus in any possible implementation manner of the seventh aspect; or, the system comprising an OTA server in any possible implementation manner of the eighth aspect and an intelligent device in any possible implementation manner of the ninth aspect.
  • a chip which includes a circuit for executing a method in any possible implementation of the first aspect, the second aspect, or the fourth aspect.
  • FIG1 is a schematic block diagram of an OTA upgrade system architecture provided in an embodiment of the present application.
  • FIG3 is a schematic flow chart of an OTA upgrade method provided in an embodiment of the present application.
  • FIG. 7 is another schematic block diagram of the OTA upgrade device provided in an embodiment of the present application.
  • FIG1 shows a schematic diagram of an OTA upgrade system architecture provided in an embodiment of the present application.
  • 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, control information during OTA upgrades, etc., 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.
  • the above-mentioned OTA upgrade scheduling information includes information on the ECU flashing order of the smart device during the 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 kind of control information in the OTA upgrade process.
  • the management entry module 110 saves the OTA upgrade scheduling information to the business management service module 120.
  • the business management service module 120 sends the OTA upgrade scheduling information to the upgrade management module 210.
  • the upgrade management module 210 parses the OTA upgrade scheduling information, adjusts the smart device status according to the OTA upgrade scheduling information, and controls the ECU flashing.
  • 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, where the ECU flashing information includes the ECU flashing result and/or the 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 according to the ECU flashing result.
  • the management entry module 110 can also control the display device to display the OTA upgrade scheduling information.
  • the intelligent devices involved in this application may include land vehicles, water vehicles, air vehicles, industrial equipment, agricultural equipment, or entertainment equipment, etc.
  • the intelligent 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 embodiment of this application does not specifically limit the type of vehicle.
  • the intelligent device can be an intelligent robot, a smart home device, a drone, an airplane, or a ship, etc. The following takes the intelligent device as an example of a vehicle to introduce the technical solution of this application.
  • FIG2 shows a schematic diagram of a system architecture when the OTA upgrade solution provided in the embodiment of the present application is applied in a vehicle.
  • the vehicle may include at least one ECU (such as ECU 1 to ECU n), a device for communicating with devices inside and outside the vehicle, such as a communication box (telematics box, T-Box), a gateway (gateway, GW) and a control center.
  • ECU such as ECU 1 to ECU n
  • a device for communicating with devices inside and outside the vehicle such as a communication box (telematics box, T-Box), a gateway (gateway, GW) and a control center.
  • GW is a core component in the electronic and electrical architecture of the whole vehicle.
  • the data interaction hub of the whole vehicle network can route network data such as the control area network (controller area network, CAN) and the local interconnect network (local interconnect network, LIN) in different networks, and the control center realizes data transmission and reception between the ECU through the gateway.
  • network data such as the control area network (controller area network, CAN) and the local interconnect network (local interconnect network, LIN) in different networks, and the control center realizes data transmission and reception between the ECU through the gateway.
  • 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.
  • 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.
  • the upgrade management module 210 can regulate the vehicle status through the gateway, and the flash management module 220 controls the flashing of the target ECU through the gateway.
  • the control center may be a domain controller, such as a vehicle domain controller (VDC), an advanced driving domain controller (ADC), and a cockpit domain controller (CDC).
  • 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), and an advanced driving assistant system super core (ADAS super core), and this application does not limit this.
  • 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.
  • control center may include the central computing platform in the above-mentioned embodiment, for example, it may include a vehicle central computer (VCC).
  • VCC vehicle central computer
  • the control center may be a central computing platform, such as a vehicle central computer (VCC).
  • 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.
  • Figure 3 shows a schematic flow chart 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.
  • the OTA server generates first OTA upgrade scheduling information according to M ECUs to be upgraded of the smart device, where 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.
  • 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 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.
  • the first upgrade stage may be one of an installation stage, an activation stage, and a rollback stage.
  • the smart device state required in the first upgrade stage may include a power supply state required in the first upgrade stage, such as a high voltage state or a low voltage state required in the first upgrade stage, or,
  • the smart device state required in the first upgrade phase may also be whether the KL15 needs to be powered on.
  • the upgrade sequence of at least one ECU may include a sequence of serial upgrades of two or more ECUs and/or a sequence of parallel upgrades of two or more ECUs.
  • the power supply status refers to whether the smart device is powered by a high-voltage battery (or engine) or a low-voltage battery.
  • the power supply status is a high-voltage state; when the smart device is powered by a low-voltage battery, the power supply status is a low-voltage state.
  • the high-voltage battery can be a power battery
  • the low-voltage battery can be a storage battery.
  • KL15 power is used to directly power some ECUs in a low-voltage state.
  • generating first OTA upgrade scheduling information based on 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 status of smart devices required for the first upgrade stage; or stage information of the first upgrade stage.
  • generating the first OTA upgrade arrangement information according to the M ECUs to be upgraded may also include: generating the first OTA upgrade arrangement information according to the M ECUs and the smart device upgrade arrangement information.
  • the smart device upgrade arrangement 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 the M ECUs.
  • the N ECUs may be all ECUs in the smart device, or may be part of the ECUs in the smart device.
  • the smart device upgrade arrangement information may be generated according to a user instruction, or may be externally imported into an OTA server.
  • the first OTA upgrade scheduling information may be generated according to a user instruction.
  • generating OTA upgrade scheduling 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 scheduling information may include the above-mentioned smart device upgrade scheduling information, or may also include the first OTA upgrade scheduling information.
  • upgrade stage 1 may be the first upgrade stage; when the OTA upgrade scheduling information is the smart device upgrade scheduling information, upgrade stage 1 may be any upgrade stage of the upgrade stages described in the above embodiments.
  • the execution order of S1 to S3 may be S1 to S3 in sequence, or may be executed in any flexible combination order, for example, S3 is executed first, and then S1 and S2 are executed.
  • S3 is executed first, and then S1 and S2 are executed.
  • 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.
  • the upgrade stage information area 401 includes several stages that may be involved in the OTA upgrade
  • the ECU selection area 402 includes multiple icons, each icon indicating an ECU.
  • the ECU that needs 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.
  • the user drags the icons of ECU_1 to ECU_7 to the installation stage of the upgrade stage information area 401, and the OTA server can determine that the ECUs that need to be upgraded in the installation stage include ECU_1 to ECU_7.
  • the third instruction may include instructions generated according to the user dragging the icons of ECU_1 to ECU_7 to the installation stage.
  • the detailed configuration interface 403 includes icons of ECU_1 to ECU_7 that need to be upgraded in the installation stage determined in response to the user's dragging action, and also includes a status setting bar 404 and a toolbar 405.
  • the status setting bar 404 includes relevant information about the state of the smart device required for the upgrade, such as information 4041 of the power supply state and information about the KL15 state.
  • the KL15 state indicates the power-up and power-down state of the KL15 electricity.
  • the KL15 When the KL15 is turned off, the KL15 electricity is in the power-down state, and when the KL15 is turned on, the KL15 electricity is in the power-on state. If it is detected that the user clicks the "high voltage” button in 4041, it is determined that the power supply state needs to be in the high voltage state in the installation stage, and if it is detected that the user clicks the "ON" button in 4042, it is determined that the KL15 electricity needs to be in the power-on state in the installation stage. In addition, in response to the user clicking on one or more of the icons of ECU_1 to ECU_7, and the user clicking on the "Remove” button in the toolbar 405, the ECUs indicated by the one or more icons can be deleted from the installation phase.
  • a relationship between the flashing order of ECU_4 and ECU_5 can be established; in response to the user clicking on the icon of ECU_4 and the icon of ECU_6 respectively after clicking on the connection line, a relationship between the flashing order of ECU_4 and ECU_6 can be established.
  • the OTA server can determine the order in which ECU_4 and ECU_5, and ECU_4 and ECU_6 are flashed serially, and the order in which ECU_5 and ECU_6 are flashed in parallel, based on the flashing order of ECU_4 and ECU_5 and the flashing order of ECU_4 and ECU_6.
  • the first instruction may include the following steps:
  • the first instruction may include an instruction generated by the operation of the user clicking a button in the status setting bar 404;
  • the second instruction may include an instruction generated by the operation of the user clicking the connecting line and then clicking the icons of two ECUs respectively, and
  • the third instruction may also include an instruction generated by the operation of the user clicking the "Remove" button after clicking the icon of a certain ECU.
  • the OTA server controls the display device to display the OTA upgrade arrangement information.
  • the OTA server can control the display device to display the arrangement interface shown in (c) of Figure 4, which includes the information of the upgrade stage and the smart device status required, such as the "high voltage installation stage” shown in box 406, "installation stage” represents the specific upgrade stage, and "high voltage” represents the smart device status required for the upgrade stage 1.
  • the arrangement interface can also display the icon of at least one ECU in the upgrade stage 1, such as the icon 407 of ECU_1, and the icon representing the flashing order of at least one ECU, such as the connecting line 408, the arrow direction is the flashing direction, that is, ECU_1 is flashed and then ECU_2 is flashed.
  • the serial and parallel flashing order between at least one ECU can also be intuitively displayed, such as parallel flashing between ECU_1 and ECU_4, and serial flashing from ECU_1 to ECU_3.
  • the OTA server sends first OTA upgrade scheduling information to the smart device.
  • the OTA server may send the first OTA upgrade scheduling information to the vehicle through the vehicle's T-Box.
  • the smart device performs ECU flashing according to the first OTA upgrade arrangement information.
  • the smart device adjusts the smart device to a corresponding smart device state according to information about the smart device state required in the first upgrade phase, and then sequentially controls the flashing of each ECU in at least one ECU according to an upgrade sequence of at least one ECU.
  • the smart device sends ECU flashing information to the OTA server.
  • the ECU flashing information may include an ECU flashing result and/or an ECU flashing progress.
  • 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 and was not reported in the previous cycle.
  • the OTA server controls the display device to display the upgrade progress of the first upgrade stage according to the ECU flashing information, where the upgrade progress includes the ECU flashing progress and/or the ECU flashing result.
  • the OTA server can determine that the current upgrade progress is that ECU_2 has been flashed, and the ECUs after ECU_2 have not been flashed.
  • the control display device displays the upgrade progress
  • different colors can be used to indicate different states of each ECU. For example, as shown in FIG5 , the display device displays the upgrade progress of the high-voltage installation stage 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 performed, and color 4 indicates that the flashing has failed.
  • FIG. 4 and FIG. 5 are only exemplary illustrations. In actual implementation, the OTA upgrade scheduling information and the OTA upgrade progress information may be displayed in other forms.
  • the embodiment of the present application provides a method for OTA upgrade, which provides a way to flexibly arrange and display OTA upgrade arrangement information. Users can flexibly divide different upgrade stages, customize the smart device status required for the upgrade stage, and the serial and parallel order of flashing ECUs through the operation interface, which helps to reduce the development cost of OTA upgrade control.
  • the upgrade progress can be displayed to the operation and maintenance personnel through the operation interface, such as the flashing results and/or flashing progress of each ECU, which is convenient for operation and maintenance management.
  • FIG. 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 The units in the apparatus 1000 are used to implement the corresponding processes of the method embodiment in FIG3 .
  • the device 1000 includes a processing unit 1010 and a transceiver unit 1020 .
  • 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 method embodiments.
  • a storage unit which can be used to store instructions and/or data
  • 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 method embodiments.
  • the device 1000 can be used to execute the actions executed by the OTA server or smart device in each of the above method embodiments.
  • the device 1000 can be a component of the OTA server or smart device, for example, the device 1000 can also be 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
  • the transceiver unit 1020 is used to execute the transceiver-related operations of the OTA server or smart device in the above method embodiments.
  • the actions performed by the processing unit 1010 and the transceiver unit 1020 may be implemented by one processor, or may also be implemented by multiple processors.
  • the processor may be a central processing unit (CPU), a digital signal processor (DSP), etc.
  • the processor may be a circuit with signal processing capability.
  • the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the hardware circuit may be fixed or reconfigurable.
  • the processor may be a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as a field programmable gate array (FPGA).
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • the process of the processor loading a configuration document to implement the hardware circuit configuration may be understood as the process of the processor loading instructions to implement the functions of some or all of the above units.
  • it can also be a hardware circuit designed for artificial intelligence, which can 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.
  • FIG7 is another schematic block diagram of a device for OTA upgrade provided in an embodiment of the present application.
  • the device 1100 shown in FIG7 may include: a processor 1110, a transceiver 1120, and a memory 1130.
  • the processor 1110, the transceiver 1120, and the memory 1130 are connected through 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-mentioned embodiments.
  • the memory 1130 can be coupled to the processor 1110 through an interface, or integrated with the processor 1110.
  • transceiver 1120 may include but is not limited to a transceiver device such as an input/output interface to achieve communication between the device 1100 and other devices or communication networks.
  • the memory 1130 may be a volatile memory and/or a nonvolatile memory.
  • the nonvolatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory may be a random access memory (RAM).
  • RAM random access memory
  • a RAM may be used as an external cache.
  • RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).
  • 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.
  • memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
  • 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 to receive/send data/information used to implement the methods in the above embodiments.
  • 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 to receive/send data/information used to implement the methods in the above embodiments.
  • the device 1100 may be a chip or a circuit disposed in the above-mentioned OTA server, or the device 1100 may also be a chip or a circuit disposed in a smart device.
  • 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.
  • the present application also provides a computer program product, which includes computer program code.
  • the code runs on a computer, the computer implements the methods in the above embodiments of the present application.
  • An embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions.
  • the computer instructions When the computer instructions are executed on a computer, the computer implements the methods in the above embodiments of the present application.
  • 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.
  • At least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple.
  • prefixes such as "first" and “second” used in the embodiments of the present application are only used 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 used to distinguish description objects in the embodiments of the present application does not constitute a limitation on the described objects. For the 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.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, 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.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)

Abstract

一种OTA升级方法、用于OTA升级的装置和系统，该方法包括：根据智能设备待升级的M个ECU生成OTA升级编排信息，OTA升级编排信息指示至少一个升级阶段、至少一个升级阶段中的第一升级阶段所需智能设备状态以及第一升级阶段中至少一个ECU的刷写顺序；其中，至少一个升级阶段中每个升级阶段包括的ECU的总数为M，且M为大于或等于1的整数；向智能设备发送OTA升级编排信息，OTA升级编排信息用于智能设备进行ECU刷写。本申请的技术方案可以应用于车联网技术领域，如新能源车辆、智能车辆的OTA升级领域，有助于提高OTA升级控制的灵活性，降低OTA升级控制的成本。

Description

OTA升级方法、用于OTA升级的装置和系统 技术领域
本申请涉及车联网技术领域，更具体地，涉及一种OTA升级方法、用于OTA升级的装置和系统。
背景技术
空中下载技术或空中升级技术(over the air，OTA)是一种通过无线网络进行数据下载的技术，现已被广泛应用于车辆、电视、手机、平板电脑、机顶盒等设备的升级。OTA技术主要通过下载OTA升级包或拷贝OTA升级包的方式进行自动升级，OTA升级速度快、对数据的影响小，因此OTA升级成为了终端功能升级的主要方式。
在对车辆进行整车级升级时，会涉及车辆中的多个电子控制单元(electronic controller unit，ECU)，多个ECU在升级的过程中存在先后依赖或者可以并行升级的情况，并且多个ECU中每个ECU所需的车辆状态可能不同，导致不同车型的车辆的升级控制逻辑不同。此外，当前OTA升级技术中的ECU刷写顺序一般都是在升级软件代码中是“写死”的，这就导致针对不同车型需要定制升级软件，使得OTA升级的成本增加。
发明内容
本申请提供一种OTA升级方法、用于OTA升级的装置和系统，提供一种能够编排ECU刷写顺序及条件的途径，有助于提高OTA升级控制的灵活性，降低OTA升级控制的成本。
第一方面，提供了一种OTA升级方法，该方法可以由OTA服务器执行，或者由OTA服务器中的芯片或电路执行，该方法可以包括：根据智能设备待升级的M个ECU生成第一OTA升级编排信息，第一OTA升级编排信息指示至少一个升级阶段、至少一个升级阶段中的第一升级阶段所需智能设备状态以及第一升级阶段中至少一个ECU的刷写顺序；其中，至少一个升级阶段中每个升级阶段包括的ECU的总数为M，且M为大于或等于1的整数；向智能设备发送第一OTA升级编排信息，第一OTA升级编排信息用于智能设备进行ECU刷写。
在上述技术方案中，OTA服务器能够根据待升级的多个ECU，实时生成指示多个ECU刷写顺序、升级阶段以及升级过程所需智能设备状态的信息，并发送给智能设备以使其进行OTA升级。也就是说，在OTA升级过程中，无需将智能设备ECU刷写顺序、升级所需智能设备状态等信息“写死”在软件代码中，有助于提高OTA升级过程中ECU刷写控制的灵活性，降低OTA升级控制的成本。
第二方面，提供了一种OTA升级方法，该方法可以由OTA服务器执行，或者由OTA服务器中的芯片或电路执行，该方法可以包括：根据待升级的M个ECU生成第一OTA升级编排信息，第一OTA升级编排信息指示至少一个升级阶段以及第一升级阶段中至少一个ECU的刷写顺序；其中，至少一个升级阶段包括第一升级阶段，至少一个升级阶段中每个升级阶段包括的ECU的总数为M，且M为大于或等于1的整数；向智能设备发送第一OTA升级编排信息，第一OTA升级编排信息用于智能设备进行ECU刷写。
可以理解的是，智能设备中的每个ECU在OTA升级时，所需智能设备的状态可能不同。例如，以智能设备为车辆为例，车辆中管理动力电池的ECU一般只能在车辆处于低压状态(即车辆由低压电池供电)时进行刷写，其他ECU一般需要在车辆处于高压状态(即车辆由动力电池供电)时进行刷写。因此，智能设备可以预先设置各ECU进行OTA升级时所需的智能设备状态，进一步地，智能设备接收到第一OTA升级编排信息之后，根据OTA升级编排信息指示的刷写顺序，以及预先设置的ECU进行OTA升级时所需的智能设备状态进行ECU刷写。
结合第二方面，在第二方面的某些实现方式中，第一OTA升级编排信息还指示第一升级阶段所需智能设备状态。
结合第一方面或第二方面，在第一方面或第二方面的某些实现方式中，该方法还包括：根据第一OTA升级编排信息，控制显示装置显示如下至少一项：第一升级阶段的阶段信息，第一升级阶段所需智能设备状态的信息，或至少一个ECU的刷写顺序。
其中，第一升级阶段的阶段信息指示第一升级阶段的具体阶段，例如，阶段信息可以指示第一升级阶段为安装、激活、回滚中的具体哪一阶段的信息。
在一些实现方式中，至少一个ECU的刷写顺序可以通过ECU图标的拓扑关系表征，其中，每个ECU图标代表智能设备中的一个ECU。或者，至少一个ECU的刷写顺序也可以是通过其他方式表征的，例如，通过文字或表格形式。
在上述技术方案中，通过显示第一升级阶段的阶段信息，第一升级阶段所需智能设备状态的信息，以及至少一个ECU的刷写顺序中的一项或多项，可以使用户直观确定OTA升级编排信息是否与预期相符，有助于提高OTA升级控制的效率。
结合第一方面或第二方面，在第一方面或第二方面的某些实现方式中，根据待升级的M个电子控制单元ECU生成第一OTA升级编排信息，包括：根据M个ECU生成第二OTA升级编排信息；根据用户指令更新第二OTA升级编排信息中的如下任一项，得到第一OTA升级编排信息：至少一个ECU的刷写顺序；第一升级阶段所需智能设备状态的信息；或第一升级阶段的阶段信息。
在上述技术方案中，为用户提供修改OTA升级编排信息的方法，使得用户可以针对不同车辆或车型灵活划分升级阶段、定制升级阶段所需智能设备状态以及刷写ECU的串并行顺序，有助于降低OTA升级控制的开发成本。
结合第一方面或第二方面，在第一方面或第二方面的某些实现方式中，该方法还包括：接收来自智能设备的ECU刷写信息，ECU刷写信息指示第一ECU的刷写结果和/或刷写进度，至少一个ECU包括第一ECU；根据ECU刷写信息，控制显示装置显示第一升级阶段的升级进度，升级进度包括第一ECU的刷写结果和/或刷写进度。
在上述技术方案中，在OTA升级过程中，能够通过显示装置显示至少一个ECU中每个ECU的刷写结果和/或刷写进度，以使得用户能够直观确定升级进度以及刷写失败的ECU，便于后续的问题处理和运维管理。
结合第一方面或第二方面，在第一方面或第二方面的某些实现方式中，第一升级阶段包括如下任一项：安装、激活、回滚。
结合第一方面或第二方面，在第一方面或第二方面的某些实现方式中，根据待升级的M个电子控制单元ECU生成第一OTA升级编排信息，包括：根据M个ECU和智能设备升级编排信息生成第一OTA升级编排信息；其中，智能设备升级编排信息指示智能设备中的N个ECU中每个ECU所处的升级阶段、各升级阶段所需智能设备状态信息，以及各升级阶段中每个升级阶段内ECU的刷写顺序，N个ECU包括M个ECU。
可以理解的是，N为大于或等于M的整数。
示例性地，N个ECU可以为智能设备中的所有ECU，或者N个ECU也可以为智能设备中的部分ECU，例如，N个ECU可以为智能设备中支持OTA升级的ECU。智能设备升级编排信息可以为根据用户指令生成的，例如，智能设备升级编排信息可以为响应与用户在显示升级编排信息的界面中的操作生成的；或者，智能设备升级编排信息也可以为外部导入的。
在上述技术方案中，用户可以预先针对智能设备的所有ECU配置升级编排信息，在智能设备实际进行OTA升级时，可以根据智能设备待升级的ECU以及预先配置的升级编排信息为待升级的ECU生成OTA升级编排信息。并且，在部分ECU需要刷写时，无需将针对智能设备所有ECU的升级编排信息发送给车辆，有助于节省通信开销。
结合第一方面或第二方面，在第一方面或第二方面的某些实现方式中，第一升级阶段所需智能设备状态包括智能设备的供电状态和/或KL15状态。
在一些实现方式中，以智能设备为车辆为例，第一升级阶段所需智能设备状态还可以包括整车状态，如车辆行驶状态、车辆可用状态等。其中，车辆行驶状态指示升级过程中是否允许车辆行驶；车辆可用状态指示升级过程中车辆的所有功能均禁用或部分可用。
在上述技术方案中，通过OTA升级编排信息直接向车辆指示第一升级阶段所需的智能设备状态，有助于提高OTA升级控制的灵活性。
第三方面，提供了一种OTA升级方法，该方法可以由智能设备执行，或者由智能设备中的芯片或电路执行，该方法可以包括：接收第一OTA升级编排信息，第一OTA升级编排信息指示至少一个升级阶段、至少一个升级阶段中的第一升级阶段所需智能设备状态以及第一升级阶段中至少一个ECU的刷写顺 序；根据第一OTA升级编排信息控制智能设备调节至第一升级阶段所需智能设备状态，并控制至少一个ECU按照刷写顺序进行刷写。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：向OTA服务器发送ECU刷写信息，ECU刷写信息指示第一ECU的刷写结果和/或刷写进度，至少一个ECU包括第一ECU；其中，ECU刷写信息用于OTA服务器显示第一升级阶段的升级进度，升级进度包括第一ECU的刷写结果和/或刷写进度。
结合第三方面，在第三方面的某些实现方式中，第一升级阶段包括如下任一项：安装、激活、回滚。
结合第三方面，在第三方面的某些实现方式中，第一升级阶段所需智能设备状态包括智能设备的供电状态和/或KL15状态。
第四方面，提供了一种用于OTA升级的装置，该装置包括处理单元和收发单元，其中处理单元用于：根据待升级的M个电子控制单元ECU生成第一OTA升级编排信息，第一OTA升级编排信息指示至少一个升级阶段、至少一个升级阶段中的第一升级阶段所需智能设备状态以及第一升级阶段中至少一个ECU的刷写顺序；其中，至少一个升级阶段中每个升级阶段包括的ECU的总数为M，且M为大于或等于1的整数；收发单元用于：向智能设备发送第一OTA升级编排信息，第一OTA升级编排信息用于智能设备进行ECU刷写。
结合第四方面，在第四方面的某些实现方式中，处理单元还用于：根据第一OTA升级编排信息，控制显示装置显示如下至少一项：第一升级阶段的阶段信息，第一升级阶段所需智能设备状态的信息，或至少一个ECU的刷写顺序。
结合第四方面，在第四方面的某些实现方式中，处理单元用于：根据M个ECU生成第二OTA升级编排信息；根据用户指令更新第二OTA升级编排信息中的如下任一项，得到第一OTA升级编排信息：至少一个ECU的刷写顺序；第一升级阶段所需智能设备状态的信息；第一升级阶段的阶段信息。
结合第四方面，在第四方面的某些实现方式中，收发单元还用于：接收来自智能设备的ECU刷写信息，ECU刷写信息指示第一ECU的刷写结果和/或刷写进度，至少一个ECU包括第一ECU；处理单元用于：根据ECU刷写信息，控制显示装置显示第一升级阶段的升级进度，升级进度包括第一ECU的刷写结果和/或刷写进度。
结合第四方面，在第四方面的某些实现方式中，第一升级阶段包括如下任一项：安装、激活、回滚。
结合第四方面，在第四方面的某些实现方式中，处理单元用于：根据M个ECU和智能设备升级编排信息生成第一OTA升级编排信息；其中，智能设备升级编排信息指示智能设备中的N个ECU中每个ECU所处的升级阶段、各升级阶段所需智能设备状态信息，以及各升级阶段中每个升级阶段内ECU的刷写顺序，N个ECU包括M个ECU。
结合第四方面，在第四方面的某些实现方式中，第一升级阶段所需智能设备状态包括智能设备的供电状态和/或KL15状态。
第五方面，提供了一种用于OTA升级的装置，该装置包括收发单元和处理单元，其中，收发单元用于：接收第一OTA升级编排信息，第一OTA升级编排信息指示至少一个升级阶段、至少一个升级阶段中的第一升级阶段所需智能设备状态以及第一升级阶段中至少一个ECU的刷写顺序；处理单元用于：根据第一OTA升级编排信息控制智能设备调节至第一升级阶段所需智能设备状态，并控制至少一个ECU按照刷写顺序进行刷写。
结合第五方面，在第五方面的某些实现方式中，收发单元还用于：向OTA服务器发送ECU刷写信息，ECU刷写信息指示第一ECU的刷写结果和/或刷写进度，至少一个ECU包括第一ECU；其中，ECU刷写信息用于OTA服务器显示第一升级阶段的升级进度，升级进度包括第一ECU的刷写结果和/或刷写进度。
结合第五方面，在第五方面的某些实现方式中，第一升级阶段包括如下任一项：安装、激活、回滚。
结合第五方面，在第五方面的某些实现方式中，第一升级阶段所需智能设备状态包括智能设备的供电状态和/或KL15状态。
第六方面，提供了一种OTA升级装置，该装置包括至少一个处理器，至少一个处理器与至少一个存储器耦合，至少一个处理器用于执行至少一个存储器中存储的计算机程序或指令，以使装置执行如第一方面或第二方面中任一种可能的实现方式中的方法。
第七方面，提供了一种OTA升级装置，该装置包括至少一个处理器，至少一个处理器与至少一个存储器耦合，至少一个处理器用于执行至少一个存储器中存储的计算机程序或指令，以使装置执行如第三 方面中任一种可能的实现方式中的方法。
第八方面，提供了一种OTA服务器，该OTA服务器包括如第四方面或第六方面中任一种可能实现方式中的装置。
第九方面，提供了一种智能设备，该智能设备包括如第五方面或第七方面中任一种可能实现方式中的装置。
结合第九方面，在第九方面的某些实现方式中，该智能设备为车辆。
第十方面，提供了一种用于OTA升级的系统，该系统包括第四方面任一种可能实现方式中的装置以及第五方面任一种可能实现方式中的装置；或者，该系统包括第六方面任一种可能实现方式中的装置以及第七方面任一种可能实现方式中的装置；或者，该系统包括第八方面任一种可能实现方式中的OTA服务器以及第九方面任一种可能实现方式中的智能设备。
第十一方面，提供了一种计算机程序产品，上述计算机程序产品包括：计算机程序代码，当上述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面或第二方面或第四方面中任一种可能实现方式中的方法。
需要说明的是，上述计算机程序代码可以全部或部分存储在第一存储介质上，其中第一存储介质可以与处理器封装在一起的，也可以与处理器单独封装。
第十二方面，提供了一种计算机可读存储介质，上述计算机可读存储介质存储有指令，当上述指令被处理器执行时，使得处理器实现上述第一方面或第二方面或第四方面中任一种可能实现方式中的方法。
第十三方面，提供了一种芯片，该芯片包括电路，该电路用于执行上述第一方面或第二方面或第四方面中任一种可能实现方式中的方法。
上述第三方面至第十三方面带来的有益效果具体可以参考第一方面或第二方面中有益效果的描述，在此不再赘述。
附图说明
图1是本申请实施例提供的OTA升级系统架构的示意性框图；
图2是本申请实施例提供的OTA升级系统架构的又一示意性框图；
图3是本申请实施例提供的OTA升级方法的示意性流程图；
图4是本申请实施例提供的OTA升级相关信息显示界面的一种示意图；
图5是本申请实施例提供的OTA升级相关信息显示界面的又一种示意图；
图6是本申请实施例提供的OTA升级装置的示意性框图；
图7是本申请实施例提供的OTA升级装置的又一示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例进行描述。
图1示出了本申请实施例提供的一种OTA升级系统架构的示意图。如图1所示，该系统包括OTA服务器100和智能设备200。其中，OTA服务器100包括管理入口模块110和业务管理服务模块120；智能设备200包括升级管理模块210和刷写管理模块220。OTA服务器100和智能设备200之间可以通过业务管理服务模块120和升级管理模块210传输OTA升级相关信息，如OTA升级包、OTA升级过程中的控制信息等。
更为具体地，管理入口模块110提供管理OTA升级相关信息的接口，例如，管理入口模块110能够根据待升级ECU的信息和智能设备升级编排信息确定OTA升级编排信息；或者，管理入口模块110可以响应于用户的操作生成OTA升级编排信息。上述智能设备升级编排信息指示车辆中所有ECU对应的OTA升级阶段、OTA升级所需智能设备状态，以及每个OTA升级阶段中至少一个ECU的升级顺序。上述OTA升级编排信息包括智能设备当次OTA升级过程的ECU刷写顺序的信息和OTA升级所需智能设备状态的信息，或者OTA升级编排信息还可以包括OTA升级阶段的信息。该OTA升级编排信息可以理解为一种OTA升级过程中的控制信息。
管理入口模块110将OTA升级编排信息保存至业务管理服务模块120，在智能设备200需要升级时，业务管理服务模块120将OTA升级编排信息发送至升级管理模块210。升级管理模块210对OTA升级编排信息进行解析，根据OTA升级编排信息调节智能设备状态，并控制ECU刷写。
刷写管理模块220用于执行具体的ECU刷写，并向升级管理模块210反馈ECU刷写信息，该ECU刷写信息包括ECU刷写结果和/或刷写进度。升级管理模块210将ECU刷写信息发送至业务管理服务模块120，业务管理服务模块120存储ECU刷写信息。管理入口模块110查询业务管理服务模块120获取ECU刷写信息，并根据ECU刷写结果控制显示OTA升级进度和OTA升级过程中每个ECU的刷写进度或刷写结果。此外，管理入口模块110还可以控制显示装置显示OTA升级编排信息。
本申请涉及的智能设备，可以包括陆上交通工具、水上交通工具、空中交通工具、工业设备、农业设备、或娱乐设备等。例如智能设备可以为车辆，该车辆为广义概念上的车辆，可以是交通工具(如商用车、乘用车、摩托车、飞行车、火车等)，工业车辆(如：叉车、挂车、牵引车等)，工程车辆(如挖掘机、推土车、吊车等)，农用设备(如割草机、收割机等)，游乐设备，玩具车辆等，本申请实施例对车辆的类型不作具体限定。再如，智能设备可以为智能机器人、智能家居设备、无人机、飞机、或轮船等。以下以智能设备为车辆为例，对本申请的技术方案进行介绍。
以智能设备200为车辆为例，图2示出了本申请实施例提供的OTA升级方案在车辆中应用时的一种系统架构示意图。如图2所示，车辆可以包括至少一个ECU(如ECU 1至ECU n)、车内与车外设备通信的装置例如通信盒子(telematics box，T-Box)、网关(gateway，GW)和控制中心。其中，GW是整车电子电气架构中的核心部件，其作为整车网络的数据交互枢纽，可将控制区域网络(controller area network，CAN)、局域互联网络(local interconnect network，LIN)等网络数据在不同网络中进行路由，控制中心通过网关实现与ECU之间的数据收发。
在一些实现方式中，升级管理模块210和刷写管理模块220可以设置在同一装置中，例如设置在网关或控制中心中，升级管理模块210通过T-Box与OTA服务器100中的业务管理服务模块120建立连接；或者，升级管理模块210和刷写管理模块220也可以设置在T-Box中。在一些实现方式中，升级管理模块210和刷写管理模块220也可以设置在不同装置中，例如，升级管理模块210设置在T-Box中，刷写管理模块设置在网关或控制中心中。在具体实现时，升级管理模块210可以通过网关调控车辆状态，刷写管理模块220通过网关控制目标ECU刷写。
在车辆电子电气架构为域集中式架构时，控制中心可以为域控制器，如车辆域控制器(vehicle domain controller，VDC)、自动驾驶域控制器(advanced driving domain controller，ADC)、座舱域控制器(cockpit domain controller，CDC)。再例如，控制中心可以包括车载应用服务(in-car application-server，ICAS)控制器，车身控制器(body domain controller，BDC)，特殊装备系统(special equipment system，SAS)，媒体图形单元(media graphics unit，MGU)，车身超级核心(body super core，BSC)，高级驾驶辅助系统超级核心(advanced driving assistant system super core，ADAS super core)中的任一个，本申请对此不做限定。其中，ICAS可以包括如下至少一项：车辆控制服务器ICAS1、智能驾驶服务器ICAS2、智能座舱服务器ICAS3、信息娱乐服务器ICAS4。或者，控制中心可以包括上述实施例中的中央计算平台，例如，可以包括车载中央计算机(Vehicle Central Computer，VCC)。在车辆电子电气架构为中央集中式架构时，控制中心可以为中央计算平台，如车载中央计算机(Vehicle Central Computer，VCC)等。
应理解，图1和图2所示架构仅为示例性说明，在具体实现过程中，图1或图2所示系统可以包括更多或更少的模块或部件。
以上介绍了本申请实施例提供的系统架构，以下详细介绍本申请实施例提供的方法。
图3示出了本申请实施例提供的OTA升级方法的示意性流程图，图3所示方法300可以由图1或图2所示系统执行，其中，由OTA服务器执行的步骤可以由设置在OTA服务器中的芯片或电路执行，由智能设备执行的步骤可以由设置在智能设备中的芯片或电路执行，该方法包括S301至S305。
S301，OTA服务器根据智能设备待升级的M个ECU生成第一OTA升级编排信息，该第一OTA升级编排信息指示至少一个升级阶段、至少一个升级阶段中第一升级阶段所需智能设备状态以及第一升级阶段中至少一个ECU的升级顺序。
其中，至少一个升级阶段中每个升级阶段包括的ECU的总数为M，M为大于或等于1的整数。
示例性地，在执行S301之前，智能设备可以向OTA服务器上报待升级的M个ECU的信息；或者，OTA服务器响应于用户的操作确定智能设备待升级的M个ECU，其中，用户的操作用于选择M个ECU。
示例性地，第一升级阶段可以为安装阶段、激活阶段、回滚阶段中的一个。第一升级阶段所需智能设备状态可以包括第一升级阶段所需的供电状态，如在第一升级阶段需要高压状态或者低压状态，或者， 第一升级阶段所需的智能设备状态也可以为是否需要KL15电上电。至少一个ECU的升级顺序可以包括两个及以上ECU串行升级的顺序和/或两个及以上ECU并行升级的顺序。
需要说明的是，供电状态是指智能设备由高压电池(或发动机)还是低压电池供电，在智能设备由高压电池供电时，供电状态为高压状态；在智能设备由低压电池供电时，供电状态为低压状态。其中，高压电池可以为动力电池，低压电池可以为蓄电池。KL15电用于在低压状态下直接给部分ECU供电，若部分ECU需要在KL15电上电时才能唤醒，则这部分ECU刷写过程中需要KL15电上电。在一些ECU不需要KL15电上电即可唤醒时，这些ECU刷写过程中就不需要KL15电上电。
在一些实现方式中，根据待升级的M个ECU生成第一OTA升级编排信息可以包括：根据M个ECU生成第二OTA升级编排信息；根据用户指令更新第二OTA升级编排信息中的如下任一项，得到所述第一OTA升级编排信息：至少一个ECU的刷写顺序；第一升级阶段所需智能设备状态的信息；或所述第一升级阶段的阶段信息。
在另一些实现方式中，根据待升级的M个ECU生成第一OTA升级编排信息还可以包括：根据M个ECU和智能设备升级编排信息生成第一OTA升级编排信息。其中，智能设备升级编排信息指示智能设备中的N个ECU中每个ECU所处的升级阶段、各升级阶段所需智能设备状态信息，以及各升级阶段中每个升级阶段内ECU的刷写顺序，N个ECU包括M个ECU。示例性地，N个ECU可以为智能设备中的所有ECU，或者也可以为智能设备中的部分ECU。
示例性地，智能设备升级编排信息可以为根据用户指令生成的，或者也可以为外部导入OTA服务器的。
在又一些实现方式中，上述第一OTA升级编排信息可以为根据用户指令生成的。
示例性地，根据用户指令生成OTA升级编排信息，可以包括：S1，根据第一指令确定升级阶段1，S2，根据第二指令确定升级阶段1所需的智能设备状态，S3，根据第三指令确定升级阶段1中的至少一个ECU以及至少一个ECU的升级顺序。其中，OTA升级编排信息可以包括上述智能设备升级编排信息，或者也可以包括第一OTA升级编排信息。在OTA升级编排信息为第一OTA升级编排信息时，升级阶段1可以为第一升级阶段；在OTA升级编排信息为智能设备升级编排信息时，升级阶段1可以为上述实施例中所述的各升级阶段的任一升级阶段。在具体实现过程中，S1至S3的执行顺序可以为S1至S3顺序执行，或者也可以为以任意灵活的组合顺序执行，例如，先执行S3，再执行S1和S2。以下结合图4说明根据用户指令生成OTA升级编排信息的一种实现方式。
如图4中的(a)所示，OTA服务器控制显示装置的编排界面显示升级阶段信息区401和ECU选择区402。其中，升级阶段信息区401包括OTA升级可能涉及的几个阶段，ECU选择区402包括多个图标，每个图标指示一个ECU。在具体实现时，可以响应于用户将ECU选择区402中的一个或多个图标拖拽进入升级阶段信息区401中某个阶段的操作，确定需要在某个阶段中升级的ECU。例如，用户将ECU_1至ECU_7的图标拖拽至升级阶段信息区401的安装阶段，则OTA服务器可以确定在安装阶段需要升级的ECU包括ECU_1至ECU_7。可以理解的是，第三指令可以包括根据用户将ECU_1至ECU_7的图标拖拽至安装阶段的操作生成的指令。
进一步地，可以响应于用户点击升级阶段信息区401中某个阶段的操作，切换至该阶段的详细配置界面。以安装阶段为例，如图4中的(b)所示，详细配置界面403中包括响应于用户拖拽动作确定的安装阶段需要升级的ECU_1至ECU_7的图标，还包括状态设置栏404以及工具栏405。示例性地，状态设置栏404包括升级所需智能设备状态的相关信息，如供电状态的信息4041和KL15状态的信息等。其中，KL15状态指示KL15电的上下电状态，在KL15处于关闭时，KL15电处于下电状态，在KL15处于开启时，KL15电处于上电状态。假如检测到用户点击4041中“高压”按钮的操作，则确定在安装阶段供电状态需要处于高压状态，检测到用户点击4042中的“ON”按钮，则确定在安装阶段KL15电需要处于上电状态。此外，响应于用户点击ECU_1至ECU_7的图标中的一个或多个图标的操作，以及用户点击工具栏405中“移除”按钮的操作，可以从安装阶段删除上述一个或多个图标指示的ECU。示例性地，响应于用户点击连接线之后分别点击ECU_4的图标和ECU_5的图标的操作，可以建立ECU_4和ECU_5先后刷写顺序的关系；响应于用户点击连接线之后分别点击ECU_4的图标和ECU_6的图标的操作，可以建立ECU_4和ECU_6先后刷写顺序的关系。OTA服务器可以根据ECU_4和ECU_5的先后刷写顺序以及ECU_4和ECU_6的先后刷写顺序，确定ECU_4和ECU_5，以及ECU_4和ECU_6分别为串行刷写的顺序，ECU_5和ECU_6之间为并行刷写的顺序。可以理解的是，第一指令可以包括根据用户点击安装阶 段的操作生成的指令；第二指令可以包括用户点击状态设置栏404中某个按钮的操作生成的指令；第三指令可以包括根据用户点击连接线之后分别点击两个ECU的图标的操作生成的指令，第三指令还可以包括根据用户点击某个ECU的图标之后点击“移除”按钮的操作生成的指令。
可选地，执行S301之后还可以执行S302’：OTA服务器控制显示装置显示OTA升级编排信息。示例性地，在升级阶段1中至少一个ECU的刷写顺序以及升级阶段1所需智能设备状态设置完成之后，OTA服务器可以控制显示装置显示如图4中的(c)所示的编排界面，该编排界面中包括升级阶段及其所需智能设备状态的信息，如框406所示的“高压安装阶段”，“安装阶段”表示具体的升级阶段，“高压”表示升级阶段1所需智能设备状态。该编排界面还可以显示升级阶段1中的至少一个ECU的图标，如ECU_1的图标407，以及表示至少一个ECU的刷写顺序的图标，如连接线408，箭头方向为刷写方向，即ECU_1刷写完毕再对ECU_2进行刷写。此外，从图4中的(c)还可以直观展现至少一个ECU之间的串并行刷写顺序，如ECU_1和ECU_4之间为并行刷写，ECU_1至ECU_3为串行刷写。
S302，OTA服务器向智能设备发送第一OTA升级编排信息。
示例性地，以智能设备为车辆为例，OTA服务器可以通过车辆的T-Box向车辆发送第一OTA升级编排信息。
S303，智能设备根据第一OTA升级编排信息进行ECU刷写。
示例性地，智能设备根据第一升级阶段所需的智能设备状态的信息，将智能设备调节至相应智能设备状态，进而根据至少一个ECU的升级顺序，依次控制至少一个ECU中的每个ECU刷写。
S304，智能设备向OTA服务器发送ECU刷写信息。
示例性地，ECU刷写信息可以包括ECU刷写结果和/或ECU刷写进度。
例如，在一个或多个ECU刷写的过程中，智能设备可以向OTA服务器发送该一个或多个ECU中每个ECU的刷写进度的信息。或者，在一个或多个ECU刷写结果后，智能设备可以向OTA服务器发送该一个或多个ECU中每个ECU的刷写结果的信息，如刷写成功或刷写失败。
在一些实现方式中，智能设备周期性向OTA服务器上报ECU刷写信息，每个周期内上报的ECU刷写信息中可以包括正在刷写的ECU的信息，以及已经刷写完毕且在上一个周期内未上报的ECU的信息。
S305，OTA服务器根据ECU刷写信息，控制显示装置显示第一升级阶段的升级进度，该升级进度包括ECU刷写进度和/或ECU刷写结果。
示例性地，ECU刷写信息指示第一ECU的刷写结果和/或刷写进度，则可以OTA服务器可以根据第一ECU在至少一个ECU中的位置，以及第一ECU的刷写结果和/或刷写进度确定第一升级阶段的升级进度。例如，以第一ECU包括安装阶段中的ECU_1和ECU_4为例，且ECU刷写信息指示ECU_1和ECU_4刷写完毕，且刷写成功，则OTA服务器可以确定当前升级进度为ECU_1和ECU_4刷写完毕且成功，并控制显示装置显示ECU_1和ECU_4刷写成功，且升级顺序排在ECU_1和ECU_4之后的ECU还未进行刷写。再例如，以第一ECU包括安装阶段中的ECU_2为例，且ECU刷写信息指示ECU_2正在刷写，则OTA服务器可以确定当前升级进度为已经刷写至ECU_2，且ECU_2之后的ECU还未刷写。
示例性地，在控制显示装置显示升级进度时，可以使用不同颜色表示各ECU的不同状态。例如，如图5所示，显示装置在状态界面中显示高压安装阶段的升级进度，颜色1表示执行(或刷写)完毕且成功，颜色2表示正在刷写，颜色3表示还未执行(或刷写)，颜色4表示刷写失败。
需要说明的是，图4和图5所示界面仅为示例性说明，在实际实现时，可以通过其他形式显示OTA升级编排信息以及OTA升级进度信息。
本申请实施例提供一种OTA升级的方法，该方法提供了一种能够灵活编排OTA升级编排信息并显示OTA升级编排信息的途径，用户通过操作界面即可灵活划分不同升级阶段、定制升级阶段所需智能设备状态以及刷写ECU的串并行顺序，有助于降低OTA升级控制的开发成本。并且，在OTA升级过程中，能够通过操作界面向运维人员显示升级进度，如各ECU的刷写结果和/或刷写进度，便于运维管理。
上文中结合图1至图5详细说明了本申请实施例提供的OTA升级方法。在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，各个实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
下面将结合图6和图7详细说明本申请实施例提供的装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
图6示出了本申请实施例提供的用于OTA升级的装置1000的示意性框图，该装置1000可以包括用 于执行图3中的方法的单元。并且，该装置1000中的各单元为了实现图3中的方法实施例的相应流程。
具体地，该装置1000包括处理单元1010和收发单元1020。
可选地，该装置1000还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元1010可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中的由终端设备执行的相关动作。
该装置1000可以用于执行上文各个方法实施例中的OTA服务器或智能设备所执行的动作，这时，该装置1000可以为OTA服务器或智能设备的组成部件，例如，装置1000也可以为OTA服务器或智能设备中的一个芯片或集成电路。处理单元1010用于执行上文方法实施例中OTA服务器或智能设备的处理相关的操作，收发单元1020用于执行上文方法实施例中OTA服务器或智能设备的收发相关的操作。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在具体实现中，处理单元1010和收发单元1020执行的动作可以由一个处理器实现，或者也可以由多个处理器实现。
在本申请实施例中，处理器可以为中央处理单元(central processing unit，CPU)，数字信号处理器(digital signal processor，DSP)等。或者，处理器可以是一种具有信号的处理能力的电路，在一种实现中，处理器可以通过硬件电路的逻辑关系实现一定功能，该硬件电路的逻辑关系是固定的或可以重构的，例如处理器为专用集成电路(application-specific integrated circuit，ASIC)或可编程逻辑器件(programmable logic device，PLD)实现的硬件电路，例如现场可编辑逻辑门阵列(field programmable gate array，FPGA)。在可重构的硬件电路中，处理器加载配置文档，实现硬件电路配置的过程，可以理解为处理器加载指令，以实现以上部分或全部单元的功能的过程。此外，还可以是针对人工智能设计的硬件电路，其可以理解为一种ASIC，例如神经网络处理单元(neural network processing unit，NPU)、张量处理单元(tensor processing unit，TPU)、深度学习处理单元(deep learning processing unit，DPU)等。
图7是本申请实施例提供的用于OTA升级的装置又一示意性框图。图7所示的装置1100可以包括：处理器1110、收发器1120以及存储器1130。其中，处理器1110、收发器1120以及存储器1130通过内部连接通路相连，该存储器1130用于存储指令，该处理器1110用于执行该存储器1130存储的指令，以实现上述各实施例中的方法。可选地，存储器1130既可以和处理器1110通过接口耦合，也可以和处理器1110集成在一起。
需要说明的是，上述收发器1120可以包括但不限于输入/输出接口(input/output interface)一类的收发装置，来实现装置1100与其他设备或通信网络之间的通信。
存储器1130可以是易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
收发器1120使用例如但不限于收发器一类的收发装置，来实现装置1100与其他设备或通信网络之间的通信，以接收/发送用于实现上述各实施例中的方法的数据/信息。
装置1100可以为设置于上述OTA服务器中的芯片或电路，或者装置1100也可以为设置在智能设备中的芯片或电路。
本申请实施例还提供一种用于OTA升级的系统，该系统包括上述装置1000或装置1100，或者，该系统包括上述实施例中的OTA服务器以及智能设备。
本申请实施例还提供一种计算机程序产品，该计算机程序产品包括计算机程序代码，当计算机程序 代码在计算机上运行时，使得计算机实现本申请上述各实施例中的方法。
本申请实施例还提供一种计算机可读存储介质，该计算机可读介质存储有计算机指令，当计算机指令在计算机上运行时，使得计算机实现本申请上述各实施例中的方法。
本申请实施例还提供一种芯片，包括电路，用于执行本申请上述各实施例中的方法。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请实施例的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
本申请实施例中采用诸如“第一”、“第二”的前缀词，仅仅为了区分不同的描述对象，对被描述对象的位置、顺序、优先级、数量或内容等没有限定作用。本申请实施例中对序数词等用于区分描述对象的前缀词的使用不对所描述对象构成限制，对所描述对象的陈述参见权利要求或实施例中上下文的描述，不应因为使用这种前缀词而构成多余的限制。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，各个实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (26)

  1. 一种OTA升级方法，其特征在于，包括：
    根据智能设备待升级的M个电子控制单元ECU生成第一OTA升级编排信息，所述第一OTA升级编排信息指示至少一个升级阶段、所述至少一个升级阶段中的第一升级阶段所需智能设备状态以及所述第一升级阶段中至少一个ECU的刷写顺序；
    其中，所述至少一个升级阶段中每个升级阶段包括的ECU的总数为M，且M为大于或等于1的整数；
    向所述智能设备发送所述第一OTA升级编排信息，所述第一OTA升级编排信息用于所述智能设备进行ECU刷写。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    根据所述第一OTA升级编排信息，控制显示装置显示如下至少一项：所述第一升级阶段的阶段信息，所述第一升级阶段所需智能设备状态的信息，或所述至少一个ECU的刷写顺序。
  3. 如权利要求1或2所述的方法，其特征在于，所述根据智能设备待升级的M个电子控制单元ECU生成第一OTA升级编排信息，包括：
    根据所述M个ECU生成第二OTA升级编排信息；
    根据用户指令更新所述第二OTA升级编排信息中的如下任一项，得到所述第一OTA升级编排信息：
    所述至少一个ECU的刷写顺序；
    所述第一升级阶段所需智能设备状态的信息；或
    所述第一升级阶段的阶段信息。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述智能设备的ECU刷写信息，所述ECU刷写信息指示第一ECU的刷写结果和/或刷写进度，所述至少一个ECU包括所述第一ECU；
    根据所述ECU刷写信息，控制显示装置显示所述第一升级阶段的升级进度，所述升级进度包括所述第一ECU的刷写结果和/或刷写进度。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，所述第一升级阶段包括如下任一项：安装、激活、回滚。
  6. 如权利要求1至5中任一项所述的方法，其特征在于，所述根据智能设备待升级的M个电子控制单元ECU生成第一OTA升级编排信息，包括：
    根据所述M个ECU和智能设备升级编排信息生成所述第一OTA升级编排信息；
    其中，所述智能设备升级编排信息指示所述智能设备中的N个ECU中每个ECU所处的升级阶段、各升级阶段所需智能设备状态信息，以及所述各升级阶段中每个升级阶段内ECU的刷写顺序，所述N个ECU包括所述M个ECU。
  7. 如权利要求1至6中任一项所述的方法，其特征在于，所述第一升级阶段所需智能设备状态包括所述智能设备的供电状态和/或KL15状态。
  8. 一种OTA升级方法，其特征在于，包括：
    接收第一OTA升级编排信息，所述第一OTA升级编排信息指示至少一个升级阶段、所述至少一个升级阶段中的第一升级阶段所需智能设备状态以及所述第一升级阶段中至少一个ECU的刷写顺序；
    根据所述第一OTA升级编排信息控制智能设备调节至所述第一升级阶段所需智能设备状态，并控制所述至少一个ECU按照所述刷写顺序进行刷写。
  9. 如权利要求8所述的方法，其特征在于，所述方法还包括：
    向OTA服务器发送ECU刷写信息，所述ECU刷写信息指示第一ECU的刷写结果和/或刷写进度，所述至少一个ECU包括所述第一ECU；
    其中，所述ECU刷写信息用于所述OTA服务器显示所述第一升级阶段的升级进度，所述升级进度包括所述第一ECU的刷写结果和/或刷写进度。
  10. 如权利要求8或9所述的方法，其特征在于，所述第一升级阶段包括如下任一项：安装、激活、回滚。
  11. 如权利要求8至10中任一项所述的方法，其特征在于，所述第一升级阶段所需智能设备状态包 括所述智能设备的供电状态和/或KL15状态。
  12. 一种用于OTA升级的装置，其特征在于，包括：
    处理单元，用于根据智能设备待升级的M个电子控制单元ECU生成第一OTA升级编排信息，所述第一OTA升级编排信息指示至少一个升级阶段、所述至少一个升级阶段中的第一升级阶段所需智能设备状态以及所述第一升级阶段中至少一个ECU的刷写顺序；
    其中，所述至少一个升级阶段中每个升级阶段包括的ECU的总数为M，且M为大于或等于1的整数；
    收发单元，用于向所述智能设备发送所述第一OTA升级编排信息，所述第一OTA升级编排信息用于所述智能设备进行ECU刷写。
  13. 如权利要求12所述的装置，其特征在于，所述处理单元还用于：
    根据所述第一OTA升级编排信息，控制显示装置显示如下至少一项：所述第一升级阶段的阶段信息，所述第一升级阶段所需智能设备状态的信息，或所述至少一个ECU的刷写顺序。
  14. 如权利要求12或13所述的装置，其特征在于，所述处理单元用于：
    根据所述M个ECU生成第二OTA升级编排信息；
    根据用户指令更新所述第二OTA升级编排信息中的如下任一项，得到所述第一OTA升级编排信息：
    所述至少一个ECU的刷写顺序；
    所述第一升级阶段所需智能设备状态的信息；或
    所述第一升级阶段的阶段信息。
  15. 如权利要求12至14中任一项所述的装置，其特征在于，所述收发单元还用于：
    接收来自所述智能设备的ECU刷写信息，所述ECU刷写信息指示第一ECU的刷写结果和/或刷写进度，所述至少一个ECU包括所述第一ECU；
    所述处理单元用于：根据所述ECU刷写信息，控制显示装置显示所述第一升级阶段的升级进度，所述升级进度包括所述第一ECU的刷写结果和/或刷写进度。
  16. 如权利要求12至15中任一项所述的装置，其特征在于，所述第一升级阶段包括如下任一项：安装、激活、回滚。
  17. 如权利要求12至16中任一项所述的装置，其特征在于，所述处理单元用于：
    根据所述M个ECU和智能设备升级编排信息生成所述第一OTA升级编排信息；
    其中，所述智能设备升级编排信息指示所述智能设备中的N个ECU中每个ECU所处的升级阶段、各升级阶段所需智能设备状态信息，以及所述各升级阶段中每个升级阶段内ECU的刷写顺序，所述N个ECU包括所述M个ECU。
  18. 如权利要求12至17中任一项所述的装置，其特征在于，所述第一升级阶段所需智能设备状态包括所述智能设备的供电状态和/或KL15状态。
  19. 一种用于OTA升级的装置，其特征在于，包括：
    收发单元，用于接收第一OTA升级编排信息，所述第一OTA升级编排信息指示至少一个升级阶段、所述至少一个升级阶段中的第一升级阶段所需智能设备状态以及所述第一升级阶段中至少一个ECU的刷写顺序；
    处理单元，用于根据所述第一OTA升级编排信息控制智能设备调节至所述第一升级阶段所需智能设备状态，并控制所述至少一个ECU按照所述刷写顺序进行刷写。
  20. 如权利要求19所述的装置，其特征在于，所述收发单元还用于：
    向OTA服务器发送ECU刷写信息，所述ECU刷写信息指示第一ECU的刷写结果和/或刷写进度，所述至少一个ECU包括所述第一ECU；
    其中，所述ECU刷写信息用于所述OTA服务器显示所述第一升级阶段的升级进度，所述升级进度包括所述第一ECU的刷写结果和/或刷写进度。
  21. 如权利要求19或20所述的装置，其特征在于，所述第一升级阶段包括如下任一项：安装、激活、回滚。
  22. 如权利要求19至21中任一项所述的装置，其特征在于，所述第一升级阶段所需智能设备状态包括所述智能设备的供电状态和/或KL15状态。
  23. 一种用于OTA升级的装置，其特征在于，包括至少一个处理器，所述至少一个处理器与至少一个存储器耦合，所述至少一个处理器用于执行所述至少一个存储器中存储的计算机程序或指令，以使所 述装置执行如权利要求1至7中任一项所述的方法，或者，如权利要求8至11中任一项所述的方法。
  24. 一种用于OTA升级的系统，其特征在于，包括如权利要求12至18中任一项所述的装置，以及如权利要求19至22中任一项所述的装置。
  25. 一种计算机可读存储介质，其特征在于，其上存储有指令，所述指令被处理器执行时，以使得处理器实现如权利要求1至7中任一项所述的方法，或者，如权利要求8至11中任一项所述的方法。
  26. 一种芯片，其特征在于，所述芯片包括电路，所述电路用于执行如权利要求1至7中任一项所述的方法，或者，如权利要求8至11中任一项所述的方法。
PCT/CN2023/139848 2023-12-19 2023-12-19 Ota升级方法、用于ota升级的装置和系统 Pending WO2025129447A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202380037436.5A CN120642371A (zh) 2023-12-19 2023-12-19 Ota升级方法、用于ota升级的装置和系统
PCT/CN2023/139848 WO2025129447A1 (zh) 2023-12-19 2023-12-19 Ota升级方法、用于ota升级的装置和系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/139848 WO2025129447A1 (zh) 2023-12-19 2023-12-19 Ota升级方法、用于ota升级的装置和系统

Publications (1)

Publication Number Publication Date
WO2025129447A1 true WO2025129447A1 (zh) 2025-06-26

Family

ID=96136059

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/139848 Pending WO2025129447A1 (zh) 2023-12-19 2023-12-19 Ota升级方法、用于ota升级的装置和系统

Country Status (2)

Country Link
CN (1) CN120642371A (zh)
WO (1) WO2025129447A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112913190A (zh) * 2021-02-04 2021-06-04 华为技术有限公司 基于空中下载技术ota的升级方法及装置
CN115562705A (zh) * 2022-10-28 2023-01-03 深圳市元征科技股份有限公司 Ecu刷写方法、装置、终端设备及存储介质
CN115987964A (zh) * 2022-11-28 2023-04-18 镁佳(北京)科技有限公司 一种整车fota升级系统及方法
CN116643775A (zh) * 2023-06-20 2023-08-25 岚图汽车科技有限公司 一种车辆ota升级控制方法及相关设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112913190A (zh) * 2021-02-04 2021-06-04 华为技术有限公司 基于空中下载技术ota的升级方法及装置
CN115562705A (zh) * 2022-10-28 2023-01-03 深圳市元征科技股份有限公司 Ecu刷写方法、装置、终端设备及存储介质
CN115987964A (zh) * 2022-11-28 2023-04-18 镁佳(北京)科技有限公司 一种整车fota升级系统及方法
CN116643775A (zh) * 2023-06-20 2023-08-25 岚图汽车科技有限公司 一种车辆ota升级控制方法及相关设备

Also Published As

Publication number Publication date
CN120642371A (zh) 2025-09-12

Similar Documents

Publication Publication Date Title
CN112104736B (zh) 一种基于ota的多ecu升级方法
US11468329B2 (en) Techniques to manage training or trained models for deep learning applications
EP4345604A1 (en) Over-the-air (ota) upgrading method and apparatus
US20230401052A1 (en) Map update method, apparatus, and system
CN115550449B (zh) 基于车联网的数字商品处理方法、装置、设备及介质
US12449801B2 (en) Electronic control device and method for setting control data
CN118838312A (zh) 车辆底盘模型在环测试系统、方法、介质和车辆
US12413552B2 (en) In-vehicle control apparatus
WO2025129447A1 (zh) Ota升级方法、用于ota升级的装置和系统
CN116149628A (zh) 一种车端服务装配方法、架构、装置、设备及介质
WO2025162113A1 (zh) 硬件缓冲区配置方法、装置以及车辆
JP2024530431A (ja) オーバーザエア（ｏｔａ）アップグレード方法および装置
WO2024140414A1 (zh) 处理方法、装置以及运载工具
CN114398095B (zh) 算子的卸载及注册方法、装置、存储介质及电子装置
JP7475559B2 (ja) 車両用制御装置
CN117539221A (zh) 诊断方法、用于诊断的装置和智能驾驶设备
CN117808406A (zh) 一种飞行器系统的技术状态管理方法、装置、设备及介质
WO2024152148A1 (zh) 一种设备救援方法及相关设备
CN116795354A (zh) 一种安卓车载应用开发的框架系统和开发方法
CN111123883A (zh) 双驱动无人车仿真方法、装置、设备及计算机可读介质
CN118679469A (zh) 资源仲裁的方法和仲裁节点
CN114745466B (zh) 一种基于Linux系统手机互联插件化设计系统和方法
CN116743576B (zh) 车辆的动态配置方法、装置、云服务器及存储介质
US20250330377A1 (en) Configuration Method and Apparatus
WO2025020956A1 (zh) 处理方法、装置以及运载工具

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202380037436.5

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23961792

Country of ref document: EP

Kind code of ref document: A1

WWP Wipo information: published in national office

Ref document number: 202380037436.5

Country of ref document: CN