Processing method and processing apparatus, and means of transport

Abstract

Embodiments of this application provide a processing method and apparatus, as well as a means of transport. The method may be applied to the field of intelligent vehicles. The method includes the steps of: obtaining information on an update sequence for a plurality of components and a set of essential matching relationship components in an over-the-air (OTA) update process, wherein the plurality of components include a first component; and, if the first component fails to update, updating at least a portion of the components to be updated and / or rolling back a portion of the successfully updated components based on the information on the update sequence and the set of essential matching relationship components, wherein the update priority of the components to be updated is later than that of the first component, and the update priority of the successfully updated components is earlier than that of the first component. According to the method described above, it is possible to improve the efficiency of OTA updates and reduce unnecessary rollback operations.

Description

Technical Field

[0001] This application claims the priority of Chinese Patent Application No. 202310911510.3, titled "PROCESSING METHOD AND APPARATUS, AND TRANSPORTATION MEANS", filed with the China National Intellectual Property Administration on July 21, 2023, and the entire content of the Chinese patent application is incorporated herein by reference.

Background Art

[0002] Since intelligent vehicles are widely used in daily life, users expect that intelligent vehicles and related devices can bring a more comfortable intelligent experience. Under such a background, over-the-air (OTA) technology has gradually become an essential basic function of intelligent vehicles. Vehicle OTA can mean that software packages are pushed from the cloud to the vehicle, and functions such as software installation and / or update are completed for the vehicle. As a result of using over-the-air technology, new functions can be added to the vehicle, or existing functions of the vehicle can be optimized, thereby greatly enriching the user's intelligent experience.

[0003] Each intelligent vehicle can contain tens or even hundreds of electronic control units (ECUs). Therefore, some ECUs may not be updated during the OTA update process. When some ECUs fail to update, the current handling strategy is that the vehicle may trigger a rollback. In other words, a malfunction in any component causes the vehicle to roll back the successfully updated components to their previous versions. However, this method carries the risk of the rollback procedure failing, resulting in a lower success rate for the OTA update task. Furthermore, the vehicle may perform unnecessary rollback actions, making the overall OTA update a time-consuming and complex process. [Overview of the project]

[0004] Embodiments of this application provide a processing method and apparatus, as well as a means of transport, which as a result can improve the efficiency of OTA updates and reduce unnecessary rollback operations. [Means for solving the problem]

[0005] According to a first embodiment, a processing method is provided. The method includes the steps of: obtaining information about an update sequence for multiple components and a set of required matching relationship components in an over-the-air (OTA) update process, wherein the multiple components include a first component; and, if the first component fails to update, updating at least some of the components to be updated and / or rolling back some of the components that have been successfully updated, based on the information about the update sequence and the set of required matching relationship components, wherein the update order of the components to be updated is later than the update order of the first component, and the update order of the components that have been successfully updated is earlier than the update order of the first component.

[0006] Optionally, the required matching relationship component set includes one or more of the following: the minimum human driving component set, the key unlocking and locking component set, the autonomous driving component set, and the cockpit domain component set.

[0007] Optionally, information regarding the required matching relation set may be transmitted by the server to the transport or stored in the transport.

[0008] In this embodiment of the present application, if, in the OTA update process, it is determined that a first component has failed to update based on information regarding the component update sequence and the required matching relationship component set, the transport means may update at least some of the components to be updated and / or roll back some of the updated components. In this way, if a first component fails to update, the transport means does not need to skip the update process for the component to be updated, nor does it need to roll back all successfully updated components to their pre-update versions. Such a processing method can improve the efficiency of OTA updates and reduce unnecessary rollback operations.

[0009] In relation to the first aspect, in some embodiments of the first aspect, if the first component is not a component of the required matching relationship component set, the step of updating at least some of the components to be updated and / or rolling back some of the components that have been successfully updated, based on information about the update sequence and the required matching relationship component set, if the first component fails to be updated, includes the step of updating all of the components that are to be updated based on the update sequence if the first component fails to be updated and the first component is not the last of several components to be updated.

[0010] In this embodiment of the present application, in the OTA update process, if a first component does not belong to the essential matching relationship component set and is not the last component to be updated, the transport means may update all components to be updated based on the update sequence. In this way, if the first component fails to be updated, the transport means does not need to skip or interrupt the update process for the component to be updated, thereby ensuring that the OTA update process is not affected by the failure of a single component.

[0011] In relation to the first aspect, in some embodiments of the first aspect, the first component is a component of the required matching relationship component set, and if the first component fails to be updated, the step of updating at least some of the components to be updated and / or rolling back some of the components that have been successfully updated, based on information about the update sequence and the required matching relationship component set, includes, if the first component fails to be updated and the successfully updated components include components of the required matching relationship component set, updating components that are among the components to be updated but not in the required matching relationship component set, and rolling back components that are among the successfully updated components but are in the required matching relationship component set, based on the update sequence.

[0012] In this embodiment of the present application, in the OTA update process, if a first component is a component of the essential matching relationship component set and the update of the first component fails, the transport means may roll back only the components that are among the successfully updated components and belong to the components that are in the essential matching relationship component set, rather than rolling back all the updated components. This targeted rollback strategy can make the rollback operation more precise and narrow the rollback scope, thereby saving time and resources for OTA updates. Furthermore, instead of skipping the update process of the components to be updated, the transport means may continue to update components that are among the components to be updated but do not belong to the essential matching relationship component set. In this way, the efficiency of OTA updates can be improved.

[0013] In relation to the first aspect, in some embodiments of the first aspect, the essential matching relation component set is the operation relation component set.

[0014] In relation to the first aspect, in some embodiments of the first aspect, the method further includes the step of notifying the user that an OTA update process has failed.

[0015] Optionally, the transport may send error prompt information on the display to notify the user that an update failed, or the transport may remind the user that an update failed by illuminating a corresponding abnormal status indicator on the dashboard, or the transport may play an audible alarm or warning tone to indicate that an OTA update process failed.

[0016] Optionally, the delivery method may generate further detailed reports or logs. These reports or logs may include specific information about the update failure to help users or technical support personnel further analyze and resolve the issue of the OTA update failing.

[0017] In relation to the first aspect, in some embodiments of the first aspect, the method further includes skipping the removal of the downloaded software package corresponding to the component that failed to update.

[0018] In this embodiment of the present application, if the first component fails to update, the downloaded software package corresponding to the failed component does not need to be deleted. In this way, time and resources for the OTA update can be saved after the user resumes the OTA update procedure.

[0019] In relation to the first aspect, in some embodiments of the first aspect, the method further includes a step of prompting the user to restart the OTA update process.

[0020] In relation to the first aspect, in some embodiments of the first aspect, the method further includes the step of rolling back the first components before rolling back any of the components that have been successfully updated based on information about the update sequence and the required matching relationship component set.

[0021] In relation to the first aspect, in some embodiments of the first aspect, the step of obtaining information regarding the update sequence of multiple components and the required matching relationship component set in an over-the-air OTA update process includes the step of receiving OTA update information transmitted by a server, wherein the OTA update information includes information regarding the update sequence of multiple components and the required matching relationship component set.

[0022] Optionally, the OTA update information may further include information indicating that the precision rollback switch is turned on. Based on the information indicating that the precision rollback switch is turned on, the update sequence of multiple components, and information about the required matching relationship component set, the transport may roll back some of the components that have been successfully updated.

[0023] Alternatively, in the aforementioned embodiment, if the OTA update information received by the transport means includes information indicating that the precision rollback switch is off, the transport means rolls back all updated components based on the information.

[0024] In this embodiment of the present application, the transport means can roll back specific components of the successfully updated components in a targeted manner based on the instructions in the OTA update information, without having to roll back all of the updated components. Such a precise rollback method allows for a narrower scope of rollback operations, reducing the risk of rollback failures and improving the efficiency and stability of the OTA update process.

[0025] According to a second embodiment, a processing method is provided. The method includes the steps of determining information regarding the update sequence of a plurality of components and the set of essential matching relationships in an OTA update process, and transmitting the OTA update information to a means of transport, wherein the OTA update information includes information regarding the update sequence of a plurality of components and the set of essential matching relationships.

[0026] According to a third aspect, a processing method is provided. The method includes receiving, by a transport means, OTA update failure information indicating that a failure has occurred in a first component in an OTA update process, and transmitting, to the transport means, a processing strategy based on information regarding an update sequence of a plurality of components and a set of components in an essential matching relationship, the processing strategy indicating the transport means to update at least a part of the components to be updated and / or roll back a part of the components successfully updated, the plurality of components including the first component, an update rank of the components to be updated being later than an update rank of the first component, and an update rank of the components successfully updated being earlier than the update rank of the first component.

[0027] In this embodiment of the present application, in the process where a failure occurs in an OTA update, the server configures a processing strategy, and the transport means only needs to execute the processing strategy without performing additional calculations and determinations, thereby avoiding unnecessary energy consumption. Compared with performing a large amount of calculations and decisions on the transport means, providing the processing strategy by the server can effectively reduce energy consumption and extend the battery life of the transport means.

[0028] In some embodiments related to the third aspect, when the first component is not a component of the set of components in an essential matching relationship and the first component is not the last component to be updated among the plurality of components, the processing strategy indicates the transport means to update all of the components to be updated.

[0029] In connection with the third aspect, in some embodiments of the third aspect, when the first component is a component of the set of essential matching relationship components, the processing strategy is to update a component that is among the components to be updated and not in the set of essential matching relationship components, and roll back a component that is among the successfully updated components and in the set of essential matching relationship components.

[0030] According to a fourth aspect, a processing method is provided. The method includes: transmitting to a server OTA update failure information indicating that a failure has occurred in a first component in an OTA update process; receiving a processing strategy transmitted by the server, the processing strategy indicating a means of transportation for updating at least a part of the components to be updated and / or rolling back a part of the successfully updated components, a plurality of components including the first component, the update order of the components to be updated being later than the update order of the first component, and the update order of the successfully updated components being earlier than the update order of the first component; and updating at least a part of the components to be updated and / or rolling back a part of the successfully updated components according to the processing strategy.

[0031] In this embodiment of the present application, in the process where a failure occurs in the OTA update, the server configures the processing strategy, and the means of transportation only needs to execute the processing strategy without performing additional calculations and determinations, thereby avoiding unnecessary energy consumption. Compared with performing a large amount of calculations and decision-making on the means of transportation, providing the processing strategy by the server can effectively reduce energy consumption and extend the battery life of the means of transportation.

[0032] In relation to the fourth aspect, in some embodiments of the fourth aspect, if the first component is not a component of the required matching relation component set and the first component is not the last component to be updated among a plurality of components, the processing strategy provides a means of updating all of the components to be updated, and updating at least some of the components to be updated and / or rolling back some of the components that have been successfully updated according to the processing strategy includes updating all of the components to be updated according to the processing strategy.

[0033] In relation to the fourth aspect, in some embodiments of the fourth aspect, when the first component is a component of the essential matching relationship component set, the processing strategy provides a transport means for updating components that are in the components to be updated but are not in the essential matching relationship component set, and for rolling back components that are in the essential matching relationship component set but are in the successfully updated components, and the steps of updating at least a portion of the components to be updated and / or rolling back a portion of the successfully updated components according to the processing strategy include updating components that are in the components to be updated but are not in the essential matching relationship component set, and for rolling back components that are in the successfully updated components but are in the essential matching relationship component set.

[0034] According to a fifth aspect, a processing device is provided. The device includes an acquisition unit configured to acquire an update sequence for a plurality of components and information regarding a set of essential matching relationship components in an over-the-air (OTA) update process, wherein the plurality of components include a first component, and a processing unit configured to update at least a portion of the components to be updated and / or roll back a portion of the components that have been successfully updated, based on the update sequence and the information regarding the set of essential matching relationship components, if the first component fails to update, wherein the update priority of the components to be updated is later than the update priority of the first component, and the update priority of the components that have been successfully updated is earlier than the update priority of the first component.

[0035] In relation to the fifth aspect, in some embodiments of the fifth aspect, the first component is not a component of the essential matching relationship component set, and The processing unit is specifically configured to update all components that should be updated based on the update sequence if the first component fails to update and the first component is not the last component to be updated among multiple components.

[0036] In relation to the fifth aspect, in some embodiments of the fifth aspect, the first component is a component of the required matching relationship component set, and the processing unit is particularly configured to update components that are in the components to be updated but are not in the required matching relationship component set, and to roll back components that are in the components that are in the successfully updated components but are in the required matching relationship component set, based on the update sequence, if the first component fails to update and the successfully updated components include components of the required matching relationship component set.

[0037] In relation to the fifth aspect, in some embodiments of the fifth aspect, the essential matching relation component set is the operation relation component set.

[0038] In relation to the fifth aspect, in some embodiments of the fifth aspect, the processing unit is further configured to notify the user that a failure has occurred in the OTA update process.

[0039] In relation to the fifth aspect, in some embodiments of the fifth aspect, the processing unit is further configured to skip deleting the downloaded software package corresponding to the component that failed to update.

[0040] In relation to the fifth aspect, in some embodiments of the fifth aspect, the processing unit is further configured to prompt the user to restart the OTA update process.

[0041] In relation to the fifth aspect, in some embodiments of the fifth aspect, the processing unit is further configured to roll back the first component.

[0042] In relation to the fifth aspect, in some embodiments of the fifth aspect, the device further includes a transceiver unit configured to receive OTA update information transmitted by a server, wherein the OTA update information includes information about update sequences of multiple components and required matching relationship component sets.

[0043] According to a sixth aspect, a processing device is provided. The device includes a transceiver unit configured to receive OTA update information transmitted by a server, wherein the OTA update information includes information about update sequences of multiple components and required matching relationship component sets.

[0044] According to a seventh aspect, a processing device is provided. The device includes a transceiver unit configured to receive OTA update failure information transmitted by a transport means, the transceiver unit indicating that the OTA update failure information indicates that a failure has occurred in a first component in the OTA update process, and a processing unit configured to transmit a processing strategy to a transport means based on information regarding the update sequence of a plurality of components and a set of required matching relationships, the processing strategy indicating the transport means to update at least a portion of the components to be updated and / or roll back a portion of the components that have been successfully updated, wherein the plurality of components include a first component, the update priority of the components to be updated is later than the update priority of the first component, and the update priority of the components that have been successfully updated is earlier than the update priority of the first component.

[0045] In relation to the seventh aspect, in some embodiments of the seventh aspect, if the first component is not a component of the required matching relation component set and the first component is not the last component to be updated among multiple components, the processing strategy provides a means of updating all components to be updated.

[0046] In relation to the seventh aspect, in some embodiments of the seventh aspect, when the first component is a component of the essential matching relationship component set, the processing strategy provides a transport means for updating components that are in the component to be updated but are not in the essential matching relationship component set, and for rolling back components that are in the successfully updated component but are in the essential matching relationship component set.

[0047] According to the eighth aspect, a processing device is provided. The device includes a transceiver unit configured to transmit OTA update failure information to a server, wherein the OTA update failure information indicates that a first component has failed in the OTA update process, and the transceiver unit receives a processing strategy transmitted by the server, wherein the processing strategy indicates transport means for updating at least a portion of the components to be updated and / or rolling back a portion of the components that have been successfully updated, and the plurality of components include the first component, the update priority of the components to be updated is later than the update priority of the first component, and the update priority of the components that have been successfully updated is earlier than the update priority of the first component; and a processing unit configured to update at least a portion of the components to be updated and / or roll back a portion of the components that have been successfully updated according to the processing strategy.

[0048] In relation to the eighth aspect, in some embodiments of the eighth aspect, if the first component is not a component of the essential matching relation component set and the first component is not the last component to be updated among a plurality of components, the processing strategy provides a means of updating all components to be updated, and the processing unit is specifically configured to update all components to be updated according to the processing strategy.

[0049] In relation to the eighth aspect, in some embodiments of the eighth aspect, when the first component is a component of the essential matching relationship component set, the processing strategy provides a transport means for updating components that are in the components to be updated but are not in the essential matching relationship component set, and for rolling back components that are in the essential matching relationship component set but are in the successfully updated components, and the processing unit is particularly configured to update components that are in the components to be updated but are not in the essential matching relationship component set, and for rolling back components that are in the successfully updated components but are in the essential matching relationship component set.

[0050] According to the ninth aspect, a processing apparatus is provided, comprising at least one processor and memory. The at least one processor is coupled to the memory and configured to read and execute instructions from the memory in order to enable the apparatus to carry out a method according to any one of the embodiments of the first to fourth aspects.

[0051] According to the tenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores program code, and when the computer program code is executed on a computer, the computer is able to perform a method according to any one of the embodiments of the first to fourth aspects.

[0052] According to the eleventh aspect, a chip is provided. The chip includes a circuit, which is configured to carry out a method according to any one of the embodiments of the first to fourth aspects.

[0053] According to the twelfth aspect, a computer program product is provided. The computer product includes a computer program, and when the computer program is executed, the computer is capable of performing a method according to any one of the embodiments of the first to fourth aspects.

[0054] According to the 13th aspect, a means of transport is provided, including a processing apparatus according to one of the embodiments of the 5th or 8th aspect.

[0055] According to the 14th aspect, a server is provided, which includes a processing device according to one of the embodiments of the 6th or 7th aspect. [Brief explanation of the drawing]

[0056] [Figure 1] This is a diagram illustrating the function of the transport means according to an embodiment of this application. [Figure 2] This document shows a system architecture to which the processing method according to the embodiments of this application can be applied. [Figure 3] This is a schematic flowchart of the data processing method according to the embodiment of this application. [Figure 4A] This is a schematic flowchart of another processing method according to an embodiment of this application. [Figure 4B] This is a schematic flowchart of another processing method according to an embodiment of this application. [Figure 5] This is a diagram showing the component update sequence configuration according to an embodiment of the present application. [Figure 6] This is another diagram showing the component update sequence configuration according to an embodiment of the present application. [Figure 7(a)] This is a diagram illustrating a scenario to which the processing method according to the embodiment of this application can be applied. [Figure 7(b)] This is a diagram illustrating a scenario to which the processing method according to the embodiment of this application can be applied. [Figure 7(c)] This is a diagram illustrating a scenario to which the processing method according to the embodiment of this application can be applied. [Figure 7(d)] This is a diagram illustrating a scenario to which the processing method according to the embodiment of this application can be applied. [Figure 8] The present invention shows an apparatus according to an embodiment of this application. [Figure 9] Another processing apparatus according to an embodiment of this application is shown. [Modes for carrying out the invention]

[0057] In the description of embodiments of this application, unless otherwise specified, “ / ” means “or.” For example, A / B may indicate A or B. The term “and / or” as used herein simply describes the relevant relationship for describing the relevant subject matter and indicates that three relationships may exist. For example, A and / or B may indicate the following three cases: namely, A only, A and B both, and B only. In this application, “at least one” means one or more, and “multiple” means two or more. At least one of the following items(parts) or similar expressions indicate any combination of these items, including a single item(part) or any combination of multiple items(parts). For example, at least one item(part) of a, b, or c may indicate a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.

[0058] The prefixes "first," "second," etc., used in the embodiments of this application are merely intended to distinguish different subjects and do not impose any restrictions on the location, order, priority, quantity, or content of the described subjects. The use of prefixes such as ordinal numbers used to distinguish the subjects described in the embodiments of this application does not constitute a limitation on the described subjects. For a description of the described subjects, please refer to the claims or the contextual description in the embodiments. The use of such prefixes should not constitute an unnecessary limitation.

[0059] The technical solutions of the embodiments of this application will be described below with reference to the attached drawings.

[0060] Figure 1 illustrates the function of the transport means 100 according to an embodiment of this application. Please understand that Figure 1 and the related description are for illustrative purposes only and do not limit the transport means in the embodiment of this application.

[0061] The transport means 100 may include multiple subsystems, for example, a sensing system 120 and a computing platform 130. Optionally, the transport means 100 may include more or fewer subsystems, each subsystem may include one or more components. Furthermore, all subsystems and components of the transport means 100 may be interconnected by wire or wireless means.

[0062] The detection system 120 may include several types of sensors configured to detect information about the surrounding environment of the transport means 100. For example, the detection system 120 may include a positioning system. The positioning system may be a global positioning system (GPS), a BeiDou system, or another positioning system. The detection system 120 may include one or more of an inertial measurement unit (IMU), a lidar, a millimeter-wave radar, an ultrasonic radar, and a camera device.

[0063] Some or all of the functions of the transport means 100 may be controlled by a computing platform 130. The computing platform 130 may include processors 131 to 13n (where n is a positive integer). A processor is a circuit having signal processing capabilities. In some embodiments, a processor may be a circuit having the ability to read and execute instructions, and may be, for example, a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which may be understood as a microprocessor), or a digital signal processor (DSP). In other embodiments, a processor may perform specific functions by using logical relationships of hardware circuits. Logical relationships of hardware circuits may be fixed or reconfigurable. For example, a processor may be a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process by which a processor loads a configuration document and implements the configuration of the hardware circuit can be understood as the process by which a processor loads instructions and implements some or all of the functions of a unit. In addition, the processor may, alternatively, be a hardware circuit designed for artificial intelligence and can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), or a deep learning processing unit (DPU). In addition, the computing platform 130 may further include memory, which is configured to store instructions. Some or all of the processors 131 to 13n may call instructions from memory to perform their corresponding functions.

[0064] The computing platform 130 can control the functions of the transport means 100 based on inputs received from subsystems (e.g., the sensing system 120). For example, the computing platform 130 can control the transport means to perform an OTA update based on inputs received from the sensing system 120. In some embodiments, the computing platform 130 may be configured to control the transport means 100 and many aspects of the transport means subsystems.

[0065] The display device 140 may be configured to display the progress of the OTA update. If a failure occurs in the OTA update process, the display device may be configured to remind the user.

[0066] The components described above are merely examples, and are optional. In actual application, components within the aforementioned modules may be added or removed based on actual requirements. Figure 1 should not be understood as an limitation to embodiments of this application.

[0067] In this application, the means of transport 100 may include land transport means, water transport means, air transport means, industrial devices, agricultural devices, entertainment devices, etc. For example, the means of transport 100 may be a vehicle. A vehicle is a vehicle in a broad sense and may be a means of transport (e.g., commercial vehicles, passenger cars, motorcycles, flying vehicles, trains, etc.), industrial vehicles (e.g., pallet trucks, trailers, tractors, etc.), work vehicles (e.g., hydraulic excavators, bulldozers, cranes, etc.), agricultural devices (e.g., lawnmowers, harvesters, etc.), entertainment devices, or toy vehicles. In embodiments of this application, the type of vehicle is not particularly limited. As another example, the means of transport 100 may be an aircraft or a ship.

[0068] The following describes the technical problems that need to be solved in this application and the technical solutions used in this application, using the example that the means of transport 100 is a vehicle.

[0069] As intelligent vehicles are widely used in daily life, users expect intelligent vehicles and associated devices to provide a more comfortable intelligent experience. Against this backdrop, OTA (Over-the-Air) updates are gradually becoming an essential basic function of intelligent vehicles. Vehicle OTA can mean that software packages are pushed from the cloud to the vehicle, and functions such as software installation and / or updates are completed for the vehicle. Over-the-air technology is used, and as a result, new functions may be added to the vehicle, or existing functions of the vehicle may be optimized, thereby greatly enriching the user's intelligent experience.

[0070] Each intelligent vehicle can contain tens or even hundreds of electronic control units (ECUs). Therefore, some ECUs may not be updated during the OTA update process. When some ECUs fail to update, the current handling strategy is that the vehicle may trigger a rollback. In other words, a malfunction in any component causes the vehicle to roll back the successfully updated components to their previous versions. However, this method carries the risk of the rollback procedure failing, resulting in a lower success rate for the OTA update task. Furthermore, the vehicle may perform unnecessary rollback actions, making the overall OTA update a time-consuming and complex process.

[0071] Embodiments of this application provide a processing method and apparatus, as well as a means of transport, which as a result can improve the efficiency of OTA updates and reduce unnecessary rollback operations.

[0072] Figure 2 shows a system architecture to which the processing method according to the embodiment of this application can be applied.

[0073] As shown in Figure 2, the architecture 200 may include a server, a mobile phone, an OTA primary control deployment module, and a controller area network (CAN) gateway.

[0074] The server may include a cloud configuration module, which may support at least one of the following: configuring the update sequence for all ECUs in the vehicle, configuring a vehicle rollback or precise rollback strategy, configuring one or more sets of essential matching relationship components, and communication between the server and the vehicle's OTA main control module over a mobile communication network (e.g., 2G / 3G / 4G / 5G). The mobile phone and the server may also communicate with each other over the mobile communication network. For example, the server may obtain OTA update progress and update result information from the OTA main control module and push that information to the mobile phone over the mobile communication network. The user can use the mobile phone to check the progress and results of the vehicle's OTA update at any time.

[0075] The OTA main control deployment module may include an OTA main control module, a component installation management module, and a CAN / unified diagnostic service (UDS) module.

[0076] The OTA main control module may include a rollback strategy configuration module and a main procedure control and scheduling module. The rollback strategy configuration module may communicate with the OTA server and request the download and saving of the rollback strategy configuration. Furthermore, the rollback strategy configuration module may interact with the main procedure control and scheduling module and provide access to the rollback strategy. The main procedure control and scheduling module may schedule the OTA procedure based on the update component list and update sequence configuration delivered by the server. The main procedure control and scheduling module may further implement precise rollback rules. If an OTA update fails, the main procedure control and scheduling module may request the rollback strategy configuration module to query the required matching relationship component set and perform subsequent update actions according to the precise rollback rules. For example, if the main procedure control and scheduling module determines that a component that failed to update is in a first component set, the main procedure control and scheduling module may skip the remaining components in the set that have not been updated and roll back the components that were successfully updated in the set. On the contrary, the main procedure control and scheduling module may continue to control component updates based on the OTA update sequence. The component installation management module may be configured to coordinate updates of multiple components on the vehicle and analyze the impact of component update exceptions. The CAN / unified diagnostic service (UDS) communication module may be configured to communicate with a CAN gateway. The CAN gateway may be a core component of the vehicle's electrical and electronic architecture and may be used as the vehicle's data exchange hub. The OTA main control deployment module may control updates of related components (e.g., ECU1~ECUn) via the CAN gateway. Optionally, the first component set may be a required matching component relationship set.

[0077] In this embodiment of the present application, the server may be deployed on an electronic device having communication and storage functions, or it may be deployed on a virtual machine in the cloud.

[0078] Figure 3 is a schematic flowchart of the processing method according to an embodiment of the present application. Method 300 may include steps S301 to S304.

[0079] S301: The server determines information regarding the update sequence of multiple components and the required matching relationship component set in the OTA update process.

[0080] S302: The server sends OTA update information to the transport.

[0081] OTA update information includes information about the update sequence of multiple components and the required matching relationship component set.

[0082] Optionally, the required matching relationship component set may include one or more of the following: the minimum human driving component set, the key unlocking and locking component set, the autonomous driving component set, and the cockpit domain component set. The minimum human driving component set can be understood as the minimum range of components required when a driver is operating the vehicle. The autonomous driving component set can be understood as the set of components required when the means of transport is operating autonomously.

[0083] Optionally, the required matching relationship component set is the driving-related component set.

[0084] Optionally, the OTA update information may further include status information for the precision rollback switch. Specifically, when the precision rollback switch is turned on, the transport may execute a precision rollback strategy if a component fails to update. When the precision rollback switch is turned off, the transport may execute a vehicle rollback strategy if a component fails to update.

[0085] S303: The transport means obtains information regarding the update sequence of multiple components and the set of required matching relationships in the OTA update process.

[0086] Multiple components include the first component.

[0087] Optionally, steps S301 and S302 may not be performed in method 300. In this case, the transport means may constitute information regarding the update sequence of multiple components and the set of required matching relationships.

[0088] S304: Based on information regarding the update sequence and required matching relationship component set, if the first component fails to update, the transport means updates at least some of the components that should be updated and / or rolls back some of the components that were successfully updated.

[0089] The update priority of a component that needs updating is lower than the update priority of the first component, while the update priority of a component that has been successfully updated is higher than the update priority of the first component.

[0090] Optionally, before step S304, method 300 further includes rolling back the first component.

[0091] Alternatively, if the precision rollback switch in the OTA update information is turned off in step S302, in step S304, the transport means may stop updating the component to be updated and / or roll back all components that have been successfully updated.

[0092] In this embodiment of the present application, if, in the OTA update process, it is determined that a first component has failed to update based on information regarding the component update sequence and the required matching relationship component set, the transport means may update at least some of the components to be updated and / or roll back some of the updated components. In this way, if a first component fails to update, the transport means does not need to skip the update process for the component to be updated, nor does it need to roll back all successfully updated components to their pre-update versions. Such a processing method can improve the efficiency of OTA updates and reduce unnecessary rollback operations.

[0093] In step S304, the transport means may determine whether the first component belongs to a set of essential matching relationships in order to select a different component update and / or component rollback strategy.

[0094] In the embodiment, if the transport means determines that the first component is not a component in the required matching relationship component set, that the first component has failed to update, and that the first component is not the last component to be updated among multiple components, the transport means may update all components to be updated based on the update sequence. In this way, if the first component fails to update, the transport means does not need to skip or interrupt the update process for the components to be updated, thereby ensuring that the OTA update process is not affected by the failure of a single component.

[0095] In one embodiment, if the transport means determines that a first component is a component of the essential matching relationship component set, and that the first component fails to update, and that a successfully updated component includes a component of the essential matching relationship component set, then, based on the update sequence, the transport means may update the components in the component to be updated that are not in the essential matching relationship component set, and roll back the components in the successfully updated component that are in the essential matching relationship component set. This targeted rollback strategy can make the rollback operation more precise and narrow the rollback scope, thereby saving time and resources for OTA updates. Furthermore, instead of skipping the update process for the component to be updated, the transport means may continue to update components in the component to be updated that are not in the essential matching relationship component set. In this way, the efficiency of OTA updates can be improved.

[0096] After step S304, the transport may further notify the user that a failure occurred in the OTA update process.

[0097] Optionally, the transport may send error prompt information on its display to notify the user that an update has failed, or the transport may notify the user that an update has failed by illuminating a corresponding abnormal status indicator on the dashboard, or the transport may play an audible alarm or warning tone to indicate that an OTA update process has failed.

[0098] Optionally, the delivery method may generate further detailed reports or logs. These reports or logs may include specific information about the update failure to help users or technical support personnel further analyze and resolve the issue of the OTA update failing.

[0099] After step S304, the transporter does not need to remove the downloaded software package corresponding to the component that failed to update. In this way, time and resources for the OTA update can be saved after the user resumes the OTA update procedure.

[0100] After step S304, the transport may further prompt the user to resume the OTA update process.

[0101] In this embodiment, in step S302, the OTA update information sent by the server to the transport means may include only the update sequence for multiple components. In this case, step S303 may be replaced by the transport means obtaining the update sequence for multiple components and performing the update based on the update sequence. Step S304 may be replaced as follows: If the transport means discovers that the first component has failed to update, the transport means may send OTA update failure information to the server, which indicates that the first component has failed.

[0102] After receiving OTA update failure information, the server may send a processing strategy to the transport based on information about the update sequence of multiple components and the required matching relationship component set, instructing the transport to update at least some of the components to be updated and / or roll back some of the components that were successfully updated. After receiving the processing strategy, the transport may update at least some of the components to be updated and / or roll back some of the components that were successfully updated. In this way, in processes where an OTA update fails, the server configures a processing strategy, and the transport only needs to execute the processing strategy without performing any additional calculations and decisions, thereby avoiding unnecessary energy consumption. Compared to performing large amounts of calculations and decisions on the transport, providing a processing strategy by the server effectively reduces energy consumption and extends the battery life of the transport.

[0103] Optionally, if the first component is not a component in the required matching relation component set, and the first component is not the last component to be updated among multiple components, the processing strategy may instruct the transport to update all components that are to be updated.

[0104] Optionally, if the first component is a component of the required matching relationship component set, the processing strategy may instruct the transport to update the component to be updated that is not in the required matching relationship component set, and to roll back the component that is in the successfully updated component and is in the required matching relationship component set.

[0105] In the embodiments of this application, unless otherwise specified and without logical inconsistency, the terminology and / or descriptions in all embodiments are consistent and may be referenced to one another, and it should be further understood that technical features in different embodiments may be combined on the basis of their internal logical relationships to form new embodiments.

[0106] Figures 4A and 4B are schematic flowcharts of another processing method according to embodiments of this application. Method 400 can specifically illustrate steps S301 to S304 of Method 300. Hereinafter, Method 400 will be described using an example in which the means of transport is a vehicle.

[0107] S401: The cloud generates a list of all ECUs in the vehicle.

[0108] The cloud can be a server in architecture 200 and method 300.

[0109] For example, the list of all ECUs in a vehicle may include ECU1 to ECUn, where n is a positive integer.

[0110] S402: The cloud configures the update sequence for all ECUs in the vehicle.

[0111] Optionally, the cloud can configure a serial update sequence for the ECUs. For example, if the ECU list includes ECU1 to ECU10, the cloud can configure an update sequence for 10 ECUs, as shown in Figures 4A and 4B(a).

[0112] Optionally, the cloud can configure a parallel update sequence for ECUs. For example, if the ECU list includes ECU1 to ECU10, the cloud can configure an update sequence for 10 ECUs, as shown in Figures 4A and 4B(b). In other words, ECU1 and ECU4, ECU2 and ECU5, and ECU3 and ECU7 can be updated simultaneously.

[0113] S403: The cloud constitutes the essential matching relationship component set for the vehicle.

[0114] For example, one or more essential matching relationship component sets, such as a minimum human driving component set, a key unlocking and locking component set, an autonomous driving component set, and a cockpit domain component set, may be defined in the ECU list. Components that satisfy a set classification may be classified into one or more sets, while components that do not satisfy a set classification may be classified into loose mapping relationship component sets.

[0115] For example, the ECU list includes ECU1 to ECU10. ECU1 to ECU3 are components related to unlocking and locking, ECU4 and ECU5 are components related to the cockpit domain, and ECU7 to ECU10 are components that do not satisfy any mandatory matching relationship component set classification. Therefore, ECU1 to ECU3 may be classified as the key unlocking and locking component set, ECU4 and ECU5 as the cockpit domain component set, and ECU7 to ECU10 as the loosely mapping relationship component set.

[0116] If a component optionally belongs to multiple required matching relationship component sets, those multiple required matching relationship component sets can be combined into a single set.

[0117] For example, the ECU list includes ECU1 to ECU5. ECU1 to ECU3 are components related to unlocking and locking, and ECU3 to ECU5 are components related to the cockpit domain. ECU3 belongs to both the key unlocking and locking component set and the cockpit domain component set. Therefore, the key unlocking and locking component set and the cockpit domain component set can be combined into a single set.

[0118] For example, if essential matching relationship component sets are defined in the ECU list, these sets may be classified from the perspectives of driving safety, whether the vehicle is usable, and whether the vehicle's basic functions are working correctly. Specific classification examples can be shown in Table 1.

[0119] [Table 1]

[0120] S404: The cloud creates the software version.

[0121] The ECU list may include, for example, ECU1, ECU2, ECU3, ECU6, ECU7, ECU8, and ECU10, with the updated version being V2.0. In this case, the version numbers corresponding to the components may be shown in Table 2.

[0122] [Table 2]

[0123] S405: The cloud configures a precise rollback strategy for the current task.

[0124] Optionally, the cloud may form a final, precise rollback strategy based on the set of essential matching relationship components obtained through the classification in step S403.

[0125] Optionally, the cloud can adjust the set of required matching components based on the characteristics of the current OTA update task and form a final, precise rollback strategy based on the adjusted set of required matching relationship components.

[0126] It should be understood that a precise rollback strategy in Method 300 may be a strategy that updates at least some of the components that should be updated, and / or rolls back some of the components that have been successfully updated.

[0127] S406: The cloud pushes relevant information about the current task to the vehicle.

[0128] Optionally, the relevant information for the current task may include at least one of the following: the vehicle update sequence, the required matching relationship component set, the precision rollback switch, and the new version information updated by the vehicle (e.g., the information shown in Table 2).

[0129] A precision rollback switch may be indicated in method 300 by status information of the precision rollback switch. Specifically, when the precision rollback switch is turned on, the vehicle may execute a precision rollback strategy when a component fails to update. When the precision rollback switch is turned off, the vehicle may execute a vehicle rollback strategy when a component fails to update. Furthermore, a specific form of the precision rollback switch may be adjusted by the operator based on actual requirements.

[0130] S407: The vehicle receives relevant information for the current update task.

[0131] For example, if the relevant information for the current task includes a set of essential matching relationship components, the vehicle may store the set of essential matching relationship components in a rollback strategy configuration module.

[0132] S408: The vehicle will download the current update software package.

[0133] S409: Vehicles will begin receiving ECU updates sequentially (starting with the first ECU on the list).

[0134] Specifically, when a vehicle initiates an ECU update, the vehicle's OTA main control module may retrieve a subset of the vehicle's entire ECU update sequence based on the update components delivered by the cloud, and then begin updating the components one by one based on the new update sequence subset.

[0135] For example, if a component fails to update, the OTA main control module may query the rollback strategy configuration module for the required matching relationship component set and request that subsequent update actions be performed according to precise rollback rules. In other words, if the component that failed to update belongs to the required matching relationship component set, the update process for the remaining components in the set that have not been updated may be skipped, and components that were successfully updated may be rolled back. If the component that failed to update belongs to a loose mapping relationship component set, the update may continue to be performed based on the component's update sequence.

[0136] For example, as shown in Figure 6, the components in the solid line block may be components of the required matching relation component set, while the components in the dashed line block may be components of the loose mapping relation component set.

[0137] Scenario 1: If ECU1 fails during an OTA update, since ECU1, ECU2, ECU3, and ECU6 all belong to the required matching relationship component set, in this case the updates of ECU2, ECU3, and ECU6 may be skipped, ECU7, ECU8, and ECU9 will be updated sequentially, and ECU1 will be rolled back.

[0138] Scenario 2: If ECU3 fails during an OTA update, components ECU7, ECU8, and ECU9 may continue to be updated sequentially, the update of ECU6 will be skipped, and ECU3, ECU2, and ECU1 will be rolled back sequentially.

[0139] Scenario 3: If ECU7 fails during an OTA update, since ECU7, ECU8, and ECU9 all belong to a loosely mapped component set, the components of ECU8 and ECU9 may continue to be updated sequentially, eventually updating ECU6 and rolling back ECU7.

[0140] Scenario 4: If ECU6 fails during an OTA update, ECU6, ECU3, ECU2, and ECU1 will be rolled back in sequence.

[0141] In all four scenarios, the update task fails if a specific component is not updated to the latest version. However, the software package downloaded by the vehicle is not deleted and remains stored in the vehicle. Furthermore, the vehicle can remind the user that the update task failed and that the update procedure can be restarted. If the vehicle detects that the user has restarted the update procedure, it only needs to update the component that failed to update last time.

[0142] In the four scenarios, the components are updated again in the following order:

[0143] Scenario 1: ECU1, ECU2, ECU3, and ECU6 are updated sequentially.

[0144] Scenario 2: ECU1, ECU2, ECU3, and ECU6 are updated sequentially.

[0145] Scenario 3: Only ECU7 needs updating.

[0146] Scenario 4: ECU1, ECU2, ECU3, and ECU6 are updated sequentially.

[0147] S410: The vehicle determines whether the current ECU has been successfully updated.

[0148] If the vehicle determines that the OTA update was successful, step S411 may be executed; otherwise, the vehicle may execute step S413.

[0149] S411: The vehicle determines whether the update of all ECUs has been completed.

[0150] If the vehicle determines that the OTA update is complete, step S412 may be executed; otherwise, the vehicle may execute step S409 again.

[0151] S412: The update was successful, and the vehicle prompts the user to experience the new version.

[0152] Optionally, the vehicle can remind the user that the OTA update was successful by playing a warning tone, displaying prompt information on the display, or playing a voice message, prompting the user to experience the new version.

[0153] S413: The vehicle determines whether to perform a precise rollback procedure.

[0154] If it is determined that the vehicle needs to perform a precise rollback procedure, step S414 may be performed; otherwise, step S417 may be performed.

[0155] S414: The vehicle determines the type of ECU that failed to be updated.

[0156] If the vehicle determines that the component that failed to update is a component of the required matching relationship component set, the vehicle may execute step S415; otherwise, the vehicle may execute step S416.

[0157] S415: The vehicle will skip any outdated components in the set.

[0158] S416: The vehicle determines whether the update of all ECUs has been completed.

[0159] If the vehicle determines that the OTA update is complete, step S418 may be executed; otherwise, the vehicle may execute step S409 again.

[0160] S417: The vehicle stops continuing the update and performs the vehicle rollback procedure.

[0161] S418: In the process of performing a vehicle rollback, if a failure occurs, the vehicle will not delete the update package and will remind the user to perform the OTA update again.

[0162] In this embodiment of the present application, if an OTA update fails, the vehicle may roll back some of its components according to precise rollback rules configured in the cloud. In this way, it is not necessary to roll back all successfully updated components to their previous versions. This can improve the efficiency of OTA updates and reduce unnecessary rollback operations.

[0163] Figures 7(a) to 7(d) illustrate scenarios to which the processing method according to the embodiments of this application may be applied. Methods 300 and 400 may be applicable to these scenarios.

[0164] As shown in Figure 7(a), the interface 700 and function bar 710 are displayed on the vehicle's central control screen. The interface 700 includes user account login information 701 (if the account is not logged into the current vehicle), a Bluetooth function icon 702, a Wi-Fi function icon 703, a cellular network signal icon 704, an in-vehicle map application search box 705, a card 706 for displaying all applications installed in the vehicle, a card 707 for switching to display the in-vehicle music application, a card 708 for displaying the vehicle's charge status and remaining driving range, and a card 709 for displaying the vehicle's 370-degree surround view function. The in-vehicle map application search box 705 may also include user-configured return-home control 7051 and work-from-home control 7052. The function bar 710 includes icons 711 for switching to the desktop display on the central control screen, an in-car circulation icon 712, a driver's seat heating function icon 713, a driver's seat area air conditioning temperature display icon 714, a passenger seat area air conditioning temperature display icon 715, a passenger seat heating function icon 716, and a volume setting icon 717.

[0165] A graphical user interface (GUI) is shown in Figure 7(b). The GUI includes a prompt box 718 used to notify the user that the vehicle meets the conditions for an OTA update and whether to proceed with the OTA update procedure. When the vehicle detects that the driver has tapped the entry control on the prompt box 718, the vehicle may perform the OTA update. If the vehicle detects that a component has failed during the OTA update process, it may perform actions according to precise rollback rules and notify the user that the OTA update process has failed.

[0166] For example, if the vehicle determines that a component that failed to update belongs to a required matching relationship component set, the vehicle may skip the remaining unupdated components in the required matching relationship component set and roll back the updated components of the required matching relationship component set. If the vehicle determines that a component that failed to update does not belong to a required matching relationship component set, the vehicle may continue executing the update based on the update sequence and roll back the component that failed to update. During the process of the vehicle performing the rollback, the GUI shown in Figure 7(c) may be displayed on the vehicle's central control screen. The GUI includes prompt text 719 and a voice assistant 720. The voice assistant 720 may notify the user in voice and text format that "the OTA update process has failed and the vehicle is performing a rollback operation, and the downloaded software package is still being retained."

[0167] After the rollback operation is complete, the GUI shown in Figure 8(d) may be displayed on the vehicle's central control screen. The GUI includes a prompt box 721 used to inform the user that the vehicle's rollback operation is complete and whether to restart the OTA update process. Once the vehicle detects that the driver has tapped the start control on the prompt box 721, the vehicle only needs to re-update the components that failed to update last time.

[0168] In this embodiment of the present application, if a component fails to update during the OTA update process, the vehicle does not need to skip the update process for the component to be updated, nor does it need to roll back all successfully updated components to their previous versions. Such a processing method can improve the efficiency of OTA updates and reduce unnecessary rollback operations.

[0169] The application scenarios shown in Figures 7(a) to 7(d) are merely illustrative examples and should not be understood as limitations to this application. The content prompted to the user by the vehicle may be determined based on the actual application of the processing method.

[0170] In the embodiments of this application, unless otherwise specified and without logical inconsistency, the terminology and / or descriptions in all embodiments are consistent and may be referenced to one another, and it should be further understood that technical features in different embodiments may be combined on the basis of their internal logical relationships to form new embodiments.

[0171] Embodiments of this application further provide an apparatus configured to implement any one of the methods described above. The apparatus includes a unit configured to perform a step performed by the transport means 100 in any one of the methods described above.

[0172] Figure 8 shows a processing apparatus 800 according to an embodiment of the present application. The apparatus 800 may include an acquisition unit 810, a transceiver unit 820, and a processing unit 830. The acquisition unit 810 is configured to acquire instructions and / or data. The transceiver unit 820 is configured to send and receive instructions and / or data. The acquisition unit 810 and the transceiver unit 820 may also be referred to as a communication interface or communication unit. The processing unit 830 is configured to perform data processing so that the apparatus 800 carries out the processing method described above.

[0173] Optionally, the device 800 may further include a storage unit configured to perform a corresponding storage function and to store corresponding instructions and / or data.

[0174] In the design, the device 800 may be configured to perform the operations performed by the transport means in the above-described embodiment.

[0175] The device 800 may include an acquisition unit 810 configured to acquire update sequences for multiple components and information regarding a set of essential matching relationship components in an over-the-air (OTA) update process, wherein the multiple components include a first component, and a processing unit 830 configured to update at least some of the components to be updated and / or roll back some of the components that have been successfully updated, based on the update sequence and information regarding the set of essential matching relationship components, if the first component fails to update, wherein the update priority of the components to be updated is later than that of the first component, and the update priority of the components that have been successfully updated is earlier than that of the first component.

[0176] In possible embodiments, the first component is not a component of the required matching relation component set, and the processing unit 830 is specifically configured to update all components that should be updated based on the update sequence if the first component fails to update and the first component is not the last component to be updated among a plurality of components.

[0177] In possible embodiments, the first component is a component of the required matching relationship component set, and the processing unit 830 is specifically configured to update components that are among the components to be updated but are not in the required matching relationship component set, and to roll back components that are among the successfully updated components but are in the required matching relationship component set, based on the update sequence, if the first component fails to update and the successfully updated components include components of the required matching relationship component set.

[0178] In possible embodiments, the required matching relationship component set is the operation-related component set.

[0179] In possible embodiments, the processing unit 830 is further configured to notify the user that the OTA update process has failed.

[0180] In possible embodiments, the processing unit 830 is further configured to skip deleting the downloaded software package corresponding to the component that failed to update.

[0181] In possible embodiments, the processing unit 830 is further configured to prompt the user to resume the OTA update process.

[0182] In possible embodiments, the processing unit 830 is further configured to roll back the first component.

[0183] In possible embodiments, the device further includes a transceiver unit 820 configured to receive OTA update information transmitted by a server, the OTA update information includes information about update sequences for multiple components and required matching relationship component sets.

[0184] The device 800 may include a transceiver unit 820 which transmits OTA update failure information to a server, the OTA update failure information indicating that a failure has occurred in a first component in the OTA update process, and a processing strategy transmitted by the server which indicates transport means for updating at least a portion of the components to be updated and / or rolling back a portion of the components that have been successfully updated, and a plurality of components including a first component, configured such that the update priority of the components to be updated is later than the update priority of the first component and the update priority of the components that have been successfully updated is earlier than the update priority of the first component; and a processing unit 830 which is configured to update at least a portion of the components to be updated and / or roll back a portion of the components that have been successfully updated according to the processing strategy.

[0185] In possible embodiments, if the first component is not a component of the required matching relation component set and the first component is not the last component to be updated among multiple components, the processing strategy indicates a means of updating all components to be updated, and the processing unit 830 is specifically configured to update all components to be updated according to the processing strategy.

[0186] In possible embodiments, when the first component is a component of the Essential Matching Relationship Component Set, the processing strategy provides a transport means for updating components that are in the components to be updated but are not in the Essential Matching Relationship Component Set, and for rolling back components that are in the Essential Matching Relationship Component Set but are in the successfully updated components, and the processing unit 830 is specifically configured to update components that are in the components to be updated but are not in the Essential Matching Relationship Component Set, and for rolling back components that are in the successfully updated components but are in the Essential Matching Relationship Component Set.

[0187] In the design, the device 800 may be configured to perform the operations performed by the server in the above-described embodiment.

[0188] Device 800 includes a transceiver unit 820 configured to receive OTA update information transmitted by a server, the transceiver unit 820 including information about update sequences for multiple components and required matching relationship component sets.

[0189] The device 800 includes a transceiver unit 820 configured to receive OTA update failure information transmitted by a transport means, the transceiver unit 820 indicating that the OTA update failure information indicates that a failure has occurred in a first component in the OTA update process, and a processing unit 830 configured to transmit a processing strategy to a transport means based on information regarding the update sequence of a plurality of components and a set of required matching relationships, the processing strategy indicating that the transport means update at least a portion of the components to be updated and / or roll back a portion of the components that have been successfully updated, the plurality of components including a first component, the update priority of the components to be updated being later than the update priority of the first component, and the update priority of the components that have been successfully updated being earlier than the update priority of the first component.

[0190] In possible embodiments, if the first component is not a component of the required matching relation component set, and the first component is not the last component to be updated among multiple components, the processing strategy provides a means of updating all components to be updated.

[0191] In possible embodiments, when the first component is a component of the required matching relationship component set, the processing strategy provides a transport means for updating components that are in the component to be updated but are not in the required matching relationship component set, and for rolling back components that are in the successfully updated component but are in the required matching relationship component set.

[0192] Optionally, if the device 800 is located in the transport means 100, the processing unit 830 may be the processor 131 shown in Figure 1.

[0193] Figure 9 shows another processing apparatus 900 according to an embodiment of the present application. The apparatus 900 may be used with the transport means 100 of Figure 1.

[0194] The device 900 includes a memory 910, a processor 920, and a communication interface 930. The memory 910, processor 920, and communication interface 930 are connected via an internal connection path. The memory 910 is configured to store instructions. The processor 920 is configured to execute instructions stored in the memory 910 and control the communication interface 930 to retrieve information, or to enable the device 900 to perform the aforementioned processing methods. Optionally, the memory 910 may be coupled to the processor 920 via an interface, or may be integrated with the processor 920.

[0195] It should be noted that the communication interface 930 uses a transceiver, for example, but not limited to a transceiver. The communication interface 930 may further include an input / output interface.

[0196] The processor 920 stores one or more computer programs, each of which includes instructions. When the instructions are executed by the processor 920, the processing unit 900 becomes capable of executing the processing method described in the above-described embodiment.

[0197] In the implementation process, the steps of the method described above may be carried out using the hardware integrated logic circuits of the processor 920 or using instructions in the form of software. The methods disclosed with reference to embodiments of this application may be performed and completed directly by a hardware processor or may be performed and completed using a combination of hardware and software modules within the processor. The software modules may be located in mature storage media in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage media is located in memory 910, and the processor 920 reads the information from memory 910 and, together with the processor hardware, completes the steps of the method described above. To avoid repetition, the details will not be described again here.

[0198] Optionally, the communication interface 930 in Figure 9 may implement the acquisition unit 810 or the transceiver unit 820 in Figure 8, and the processor 920 in Figure 9 may implement the processing unit 830 in Figure 8.

[0199] Optionally, device 800 or device 900 may be a computing platform. The computing platform may be an in-vehicle computing platform or a cloud computing platform.

[0200] Optionally, device 800 or device 900 may be the transport means 100 in Figure 1.

[0201] Optionally, device 800 or device 900 may be the computing platform 130 of the transport means shown in Figure 1.

[0202] Embodiments of this application further provide a computer-readable storage medium that stores program code, and when the computer program code is executed by a computer, the computer can execute any of the methods shown in Figure 3 or Figures 4A and 4B.

[0203] Embodiments of this application further provide a computer program product which includes a computer program, and when the computer program is executed, the computer is capable of performing any of the methods shown in Figure 3 or Figures 4A and 4B.

[0204] Embodiments of this application further provide a chip including a circuit. The circuit is configured to perform any method shown in Figure 3 or Figures 4A and 4B.

[0205] Embodiments of this application further provide a transport means including any processing apparatus shown in Figure 8 or Figure 9.

[0206] Embodiments of this application further provide a server including any processing unit shown in Figure 8 or Figure 9.

[0207] Embodiments of this application further provide a processing system including a transport means and a server.

[0208] Those skilled in the art will recognize that the units and algorithmic steps in the examples described with reference to the embodiments disclosed herein may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may implement the functions described using various methods for specific applications, but such embodiments should not be considered to exceed the scope of this application.

[0209] For the sake of brevity, it will be readily apparent to those skilled in the art that the detailed operating processes of the aforementioned systems, apparatus, and units can be described by referring to the corresponding processes in the method embodiments described above. Details will not be repeated here.

[0210] It should be understood that in some embodiments provided in this application, the disclosed systems, apparatus, and methods may be implemented in other ways. For example, the embodiments of the apparatus described are merely illustrative. For example, the division into units is merely a logical functional division, and in actual implementation, there may be other divisions. For example, multiple units or components may be coupled or integrated into another system, or some features may be ignored or not performed. In addition, the presented or described mutual coupling or direct coupling or communication connection may be implemented using some interfaces. Indirect coupling or communication connection between apparatus or units may be implemented in electronic, mechanical, or other forms.

[0211] Units described as separate components may or may not be physically separate, and components presented as units may or may not be physical units, may be located in one place, or may be distributed across multiple network units. Some or all of the units may be selected based on the actual requirements to achieve the objectives of the solution of the embodiment.

[0212] In addition, the functional units in the embodiments of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit.

[0213] When a function is implemented in the form of a software function unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of this application, in essence, or in part with respect to the present art, or a part of the technical solutions, may be implemented in the form of a software product. The software product is stored in a storage medium and includes several instructions that instruct a computing device (which may be a personal computer, server, or network device) to perform all or part of the steps of the method described in embodiments of this application. The storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0214] The foregoing description is merely a specific implementation of the present application and is not intended to limit the scope of protection of this application. Any modification or substitution that is readily conceivable by a person skilled in the art within the technical scope disclosed in this application shall fall within the scope of protection of this application. Accordingly, the scope of protection of this application shall be subject to the scope of protection of the claims. [Explanation of Symbols]

[0215] 100 Means of transportation 120 detection systems 130 Computing Platforms 131 processors 140 Display device 200 Architectures 300 ways 400 ways 700 Interface 701 User Account Login Information 702 Bluetooth function icon 703 Wi-Fi function icon 704 Cellular network signal icon 705 App search box 706 cards 707 Cards 708 cards 709 cards 710 Function Bar 711 Icons 712 In-car circulation icon 713 Driver's seat heating function icon 714 Driver's seat area air conditioning temperature display icon 715 Passenger seat area air conditioning temperature display icon 716 Passenger seat heating function icon 717 Volume setting icon 718 Prompt Box 719 Prompt text 720 Voice Assistant 721 Prompt Box 800 devices, processing equipment 810 units acquired 820 Transceiver Unit 830 processing units 900 devices, processing equipment 910 memory 920 Processor 930 Communication Interface 7051 Return-to-home control 7052 Attendance control

Claims

1. A processing method, A step of obtaining information regarding the update sequence of multiple components and the set of essential matching relationship components in an over-the-air (OTA) update process, wherein the multiple components comprise a first component. If the first component fails to update, a step of updating at least some of the components to be updated and / or rolling back some of the components that have been successfully updated, based on the information relating to the update sequence and the required matching relationship component set, wherein the update order of the components to be updated is later than the update order of the first component, and the update order of the components that have been successfully updated is earlier than the update order of the first component. A method that includes [a certain feature].

2. If the first component is not a component of the required matching relationship component set, and the first component fails to update, the steps of updating at least a portion of the component to be updated and / or rolling back a portion of the successfully updated component, based on the information relating to the update sequence and the required matching relationship component set, are: The method according to claim 1, further comprising the step of updating all of the components to be updated based on the update sequence if the first component fails to update and the first component is not the last component to be updated among the plurality of components.

3. The first component is a component of the required matching relationship component set, and if the first component fails to be updated, the step of updating at least a portion of the component to be updated and / or rolling back a portion of the successfully updated component, based on the information relating to the update sequence and the required matching relationship component set, The method according to claim 1, further comprising the steps of: if the first component fails to be updated and the successfully updated component comprises components of the required matching relationship component set, updating components in the component to be updated that are not in the required matching relationship component set, and rolling back components in the successfully updated component that are in the required matching relationship component set, based on the update sequence.

4. The method according to any one of claims 1 to 3, wherein the essential matching relationship component set is an operation-related component set.

5. The method according to any one of claims 1 to 4, further comprising the step of notifying a user that a failure has occurred in the OTA update process.

6. The method according to claim 5, further comprising the step of skipping the step of deleting the downloaded software package corresponding to the component that failed to update.

7. The method described above is The method according to claim 5 or 6, further comprising the step of prompting the user to resume the OTA update process.

8. The method described above is The method according to any one of claims 1 to 7, further comprising the step of rolling back the first component.

9. The step of obtaining the information relating to the update sequence of the plurality of components and the set of required matching relationships in the over-the-air OTA update process is: The method according to any one of claims 1 to 8, comprising the step of receiving OTA update information transmitted by a server, wherein the OTA update information comprises the information relating to the update sequence of the plurality of components and the set of required matching relationships components.

10. A processing method, The OTA update process includes a step of determining information regarding the update sequence of multiple components and the required matching relationship component set, A step of transmitting OTA update information to a means of transport, wherein the OTA update information comprises the update sequence of the plurality of components and the information relating to the set of essential matching relationships components, A method that includes [a certain feature].

11. A processing method, A step of receiving OTA update failure information transmitted by a means of transport, wherein the OTA update failure information indicates that a first component failed in the OTA update process; A step of transmitting a processing strategy to the transport means based on information regarding the update sequence of a plurality of components and the set of required matching relationships of components, wherein the processing strategy instructs the transport means to update at least a portion of the components to be updated and / or roll back a portion of the components that have been successfully updated, the plurality of components comprising the first component, the update order of the components to be updated being later than the update order of the first component, and the update order of the successfully updated components being earlier than the update order of the first component. A method that includes [a certain feature].

12. The method according to claim 11, wherein if the first component is not a component of the required matching relationship component set and the first component is not the last component to be updated among the plurality of components, the processing strategy instructs the transport means to update all of the components to be updated.

13. The method according to claim 11, wherein, when the first component is a component of the required matching relationship component set, the processing strategy instructs the transport means to update a component that is in the component to be updated but is not in the required matching relationship component set, and to roll back a component that is in the successfully updated component but is in the required matching relationship component set.

14. Processing apparatus, An acquisition unit configured to acquire update sequences for multiple components and information regarding the set of essential matching relationships for an over-the-air (OTA) update process, wherein the multiple components include a first component, A processing unit configured to update at least some of the components to be updated and / or roll back some of the components that have been successfully updated, based on the information relating to the update sequence and the set of required matching relationships, if the first component fails to update, wherein the update order of the components to be updated is later than the update order of the first component, and the update order of the components that have been successfully updated is earlier than the update order of the first component. A device equipped with the following features.

15. The first component is not a component of the required matching relationship component set, and The apparatus according to claim 14, wherein the processing unit is particularly configured to update all of the components to be updated based on an update sequence if the first component fails to be updated and the first component is not the last component to be updated among the plurality of components.

16. The first component is a component of the set of required matching relationships, and The apparatus according to claim 14, wherein the processing unit is particularly configured to update a component that is in the component to be updated but is not in the essential matching relationship component set, and to roll back the component that is in the successfully updated component but is in the essential matching relationship component set, based on the update sequence, when the first component fails to be updated and the successfully updated component includes a component from the essential matching relationship component set.

17. The apparatus according to any one of claims 14 to 16, wherein the essential matching relationship component set is an operation-related component set.

18. The apparatus according to any one of claims 14 to 17, wherein the processing unit is further configured to notify the user that a failure has occurred in the OTA update process.

19. The apparatus according to claim 18, wherein the processing unit is further configured to skip deleting downloaded software packages corresponding to components that failed to be updated.

20. The apparatus according to claim 18 or 19, wherein the processing unit is further configured to prompt the user to resume the OTA update process.

21. The apparatus according to any one of claims 14 to 20, wherein the processing unit is further configured to roll back the first component.

22. The aforementioned device includes a transceiver unit, The transceiver unit is configured to receive OTA update information transmitted by the server, and the OTA update information comprises the update sequence of the plurality of components and the information relating to the set of required matching relationships. The apparatus according to any one of claims 14 to 21.

23. Processing apparatus, A processing unit configured to determine information regarding the update sequence of multiple components and the set of essential matching relationships in the OTA update process, A transceiver unit configured to transmit OTA update information to a transport means, wherein the OTA update information comprises the update sequence of the plurality of components and the information relating to the essential matching relationship component set, A device equipped with the following features.

24. Processing apparatus, A transceiver unit configured to receive OTA update failure information transmitted by a means of transport, wherein the OTA update failure information indicates that a first component failed in the OTA update process, A processing unit configured to transmit a processing strategy to a transport means based on information regarding the update sequence of multiple components and the set of required matching relationships of components, wherein the processing strategy indicates the transport means to update at least some of the components to be updated and / or roll back some of the components that have been successfully updated, and the multiple components comprise the first component, the update order of the components to be updated is later than the update order of the first component, and the update order of the successfully updated components is earlier than the update order of the first component, A device equipped with the following features.

25. If the first component is not a component of the required matching relationship component set, and the first component is not the last component to be updated among the plurality of components, the processing strategy instructs the transport means to update all of the components to be updated, according to claim 24.

26. The apparatus according to claim 24, wherein, when the first component is a component of the required matching relationship component set, the processing strategy instructs the transport means to update a component that is in the component to be updated but is not in the required matching relationship component set, and to roll back a component that is in the successfully updated component but is in the required matching relationship component set.

27. A processing unit comprising a processor and memory, wherein the processor is coupled to the memory and configured to read and execute instructions from the memory in order to perform the method according to any one of claims 1 to 9.

28. A processing apparatus comprising a processor and memory, wherein the processor is coupled to the memory and configured to read and execute instructions from the memory in order to perform the method according to any one of claims 10 to 13.

29. A computer-readable storage medium, wherein the computer-readable storage medium stores program code, and when the computer program code is executed by a computer, the computer is enabled to perform the method according to any one of claims 1 to 13.

30. A chip comprising a circuit, wherein the circuit is configured to carry out the method described in any one of claims 1 to 13.

31. A transport means comprising the processing apparatus according to any one of claims 14 to 22.

32. A server comprising the processing device according to any one of claims 23 to 26.

Images