OVER-THE-AIR OTA TECHNOLOGY BASED UPGRADE METHOD AND COMMUNICATION DEVICE

Abstract

An upgrade method and a communication device based on over-the-air OTA technology that solves the problem of the risk of vehicle management are provided. The method includes: an OTA cloud receives vehicle fleet information from a first device, the first device is configured to manage a vehicle fleet, the vehicle fleet includes at least two vehicles, and the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet; and the OTA cloud sends first upgrade task information to a second target vehicle, the first upgrade task information includes an upgrade package, the second target vehicle is at least one vehicle determined from the first target vehicle by the first device, the first target vehicle is related to the vehicle fleet information and the first vehicle, and the first vehicle is a vehicle that needs to be upgraded and is obtained by the OTA cloud. The first device determines the second target vehicle that is allowed to perform the upgrade, and the OTA cloud sends the first upgrade task information to the second target vehicle, which is useful for improving the security of the management of vehicles in the vehicle fleet.

Description

[Technical field]

[0001] The present application relates to the field of communication technology, and in particular to an upgrade method and a communication device based on over-the-air OTA technology. [Background technology]

[0002] With the development of science and technology, terminal devices are gradually used in people's daily lives, and people's requirements for the intelligence, security, etc. of terminal devices are increasingly increasing. Usually, various types of software (such as applications) are deployed on the terminal devices. For example, the terminal device is a vehicle. Usually, an intelligent cockpit, a sensing system, an automatic driving system, and other hardware are deployed on the vehicle, and an in-vehicle operating system, a navigation application, an audio-video playback application, etc. are also deployed. The software enhances the functionality of the terminal device. However, the possibility of vulnerabilities, failure to meet functional requirements, etc. is higher. In this case, the original version needs to be upgraded to a more advanced version, etc. Therefore, in order to update the software version, the software of the terminal device needs to be upgraded.

[0003] At present, upgrades based on over-the-air (OTA) technology are fast and have little impact on data, so they are widely applied to upgrade smart TVs, mobile phones, tablet computers, set-top boxes, vehicles, etc. OTA is a technology that downloads data through wireless networks. Take a vehicle as an example. OTA technology can be used by original equipment manufacturers (OEMs) to upgrade the software of a vehicle. This helps manufacturers reduce recall costs, respond quickly to requests, and improve user experience.

[0004] Currently, upgrades are mainly performed by an OTA cloud server using OTA technology at two levels. One level is the vehicle type level. Specifically, an upgrade version is released by the OTA cloud server and an upgrade task is pushed based on the vehicle type. The other level is the vehicle level. Specifically, the upgrade progress is tracked by the OTA cloud server based on the vehicle, and the upgrade is performed after the driver confirms the upgrade. However, in practical application scenarios, multiple vehicles may belong to the same owner (fleet owner, FO), and these vehicles belonging to the same owner may be referred to as a vehicle fleet. If the vehicles are still upgraded based on two levels, the vehicle owner cannot see the upgrade status of the vehicle. As a result, the vehicle owner cannot manage and control the software version of the vehicle in a timely manner, which results in vehicle management risks. Summary of the Invention [Means for solving the problem]

[0005] In this application, an upgrade method and a communication device based on OTA technology are provided to improve the security of vehicle management.

[0006] According to a first aspect, the present application provides an upgrade method based on OTA technology. The method includes the steps of receiving vehicle fleet information from a first device, where the first device is configured to manage a vehicle fleet, the vehicle fleet includes at least two vehicles, and the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet, and sending first upgrade task information to a second target vehicle, where the first upgrade task information includes an upgrade package. The second target vehicle is at least one vehicle determined by the first device from the first target vehicle. The first target vehicle is related to the vehicle fleet information and the first vehicle. The first vehicle is a vehicle that needs to be upgraded and is obtained by the OTA cloud.

[0007] The method may be performed by an OTA cloud, which may also be referred to as an OTA cloud side, an OTA cloud server, etc.

[0008] According to the above solution, the first device sends vehicle fleet information to the OTA cloud, so that the OTA cloud can obtain vehicle identifiers of vehicles belonging to the same vehicle fleet, and then send first upgrade task information to a second target vehicle that needs to be upgraded and is determined by the first device, which is useful for improving the security of the management of vehicles in the vehicle fleet by the first device, and for improving the level of the management of software of vehicles in the vehicle fleet by the first device.

[0009] In a possible implementation, the OTA cloud may determine a first target vehicle based on vehicle fleet information from the first device and a first vehicle identifier. The first vehicle identifier is an identifier of a vehicle that needs to be upgraded and is obtained by the OTA cloud server. The first target vehicle is a vehicle in the vehicle fleet that needs to be upgraded and is determined by the OTA cloud.

[0010] First, the OTA cloud determines the first target vehicle in the fleet that needs an upgrade, which allows the first device to quickly determine which first target vehicle is allowed to complete the upgrade.

[0011] Below, two examples of methods for determining the second target vehicle are given.

[0012] Method 1 The OTA cloud sends a first request message to the first device. The first request message is used to request the first device to determine a first target vehicle that is authorized to perform the upgrade. The first target vehicle that is authorized to perform the upgrade and determined by the first device is referred to as a second target vehicle. By way of example, the first request message includes a vehicle identifier of the first target vehicle.

[0013] In response, the OTA cloud receives a first response message from the first device or the second target vehicle. The first response message includes information about the second target vehicle. For example, the first response message includes a vehicle identifier of the second target vehicle.

[0014] In a possible implementation, the first request message further includes relevant information of the upgrade task, and the relevant information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0015] The first device can use the relevant information of the upgrade task carried in the first request message to flexibly select the first target vehicle that is allowed to carry out the upgrade based on the actual situation.

[0016] Furthermore, in a possible implementation, the first upgrade task information further includes an upgrade type, and the upgrade type is a confirmed upgrade.

[0017] After determining that the upgrade type is a confirmed upgrade, the second target vehicle may perform the upgrade according to the OTA upgrade procedure based on the upgrade package in the received first upgrade task information without confirmation by the user (or referred to as the driver) of the second target vehicle, thereby reducing the burden on the driver.

[0018] Method 2 The OTA cloud sends first instruction information to the first target vehicle, the first instruction information instructing the first target vehicle to request the first device to confirm whether the upgrade is allowed, and the OTA cloud receives a second response message from the first device or the second target vehicle, the second response message including information about the second target vehicle.

[0019] Furthermore, in a possible implementation, as an example, the first instruction information may include an address of the first device.

[0020] The OTA cloud sends a first instruction information to the first target vehicle to initiate the first device to determine whether the first target vehicle is authorized to perform the upgrade. This is useful for improving the security of the management of the vehicles in the fleet by the first device, and can improve the level of management of the software of the vehicles in the fleet by the first device. In addition to the above, after the first device determines whether the first target vehicle is authorized to perform the upgrade, it is not necessary to prompt or ask the driver for confirmation through the HMI. This is useful for reducing the burden on the driver.

[0021] Furthermore, in a possible implementation, the first instruction information may further include relevant information of the upgrade task, where the relevant information of the upgrade task includes at least one of the duration required for the upgrade, the purpose of the upgrade, or the changes brought about by the upgrade.

[0022] The first instruction information carries the relevant information of the upgrade task, so that the first target vehicle can determine whether to send a second request message to the OTA cloud or the first device. Furthermore, when the first target vehicle sends the second request message to the first device, the second request message can also carry the relevant information of the upgrade task. This is useful for the first device to determine whether the first target vehicle that sent the second request message is allowed to perform the upgrade based on the relevant information of the upgrade task.

[0023] Based on the above, in a possible implementation, the method further includes the OTA cloud receiving an upgrade result from the second target vehicle. The upgrade result includes upgrade success, upgrade failure, rollback success, or rollback failure.

[0024] Further, in a possible implementation, the OTA cloud sends the upgrade result to the first device.

[0025] After completing the OTA-based upgrade, the second target vehicle notifies the OTA cloud of the upgrade result in a timely manner. Furthermore, the OTA cloud can synchronize the upgrade result of the second target vehicle to the first device in a timely manner, so that the upgrade information of the first device, the OTA cloud and the second target vehicle can be synchronized. In this way, the first device can effectively and reliably manage the upgrade status of each vehicle in the vehicle fleet.

[0026] In another possible implementation, the OTA cloud receives the upgrade results from the second target vehicle forwarded by the first device.

[0027] After completing the OTA-based upgrade, the second target vehicle notifies the first device of the upgrade result in a timely manner. Furthermore, the first device can synchronize the upgrade result of the second target vehicle to the OTA cloud in a timely manner, so that the upgrade information of the first device, the OTA cloud and the second target vehicle can be synchronized. In this way, the first device can effectively and reliably manage the upgrade status of each vehicle in the vehicle fleet.

[0028] According to a second aspect, the present application provides an upgrade method based on OTA technology, the method includes: a first device sends vehicle fleet information to an OTA cloud, where the vehicle fleet includes at least two vehicles, and the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet; the first device receives a first request message from the OTA cloud, where the first request message includes a vehicle identifier of a first target vehicle, the first target vehicle being a vehicle in the vehicle fleet that needs to be upgraded and determined by the OTA cloud; the first device determines at least one vehicle among the first target vehicles as a second target vehicle based on the first request message; and the first device sends a first response message to the OTA cloud, where the first response message includes information about the second target vehicle.

[0029] In a possible implementation, the first request message further includes relevant information of the upgrade task, and the relevant information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0030] In a possible implementation, the method further includes the first device receiving an upgrade result from the second target vehicle, the upgrade result including upgrade success, upgrade failure, rollback success, or rollback failure.

[0031] Furthermore, in a possible implementation, the method further includes the first device sending the upgrade result to the OTA cloud.

[0032] In another possible implementation, the first device receives the upgrade results of the second target vehicle transferred by the OTA cloud.

[0033] According to a third aspect, the present application provides an upgrade method based on OTA technology, the method includes: a second target vehicle receiving first upgrade task information from an OTA cloud, the first upgrade task information including an upgrade package and an upgrade task type; and directly performing an upgrade based on the upgrade package when it is determined that the upgrade type is a confirmed upgrade.

[0034] For technical effects that can be realized in any one of the second and third aspects, please refer to the description of the beneficial effects of the first aspect, and the details will not be described again in this description.

[0035] According to a fourth aspect, the present application provides an upgrade method based on OTA technology. The method includes the steps of: receiving vehicle fleet information from a first device, the first device being configured to manage a vehicle fleet, the vehicle fleet including at least two vehicles, and the vehicle fleet information including vehicle identifiers of vehicles belonging to the same vehicle fleet; and sending second upgrade task information to a first target vehicle, the second upgrade task information including an upgrade package and first instruction information. The first target vehicle is related to the vehicle fleet information and the first vehicle. The first vehicle is a vehicle that needs to be upgraded and is obtained by the OTA cloud. The first instruction information instructs the first target vehicle to request the first device to confirm whether the first target vehicle is authorized to perform the upgrade. It is found that the upgrade package corresponds to the first target vehicle that is authorized to perform the upgrade.

[0036] The method may be performed by an OTA cloud, which may also be referred to as an OTA cloud side, an OTA cloud server, etc.

[0037] According to the above solution, the first device sends vehicle group information to the OTA cloud, so that the OTA cloud can obtain vehicle identifiers of vehicles belonging to the same vehicle group. Furthermore, the OTA cloud sends second upgrade task information including first instruction information to the first target vehicle, instructing the first target vehicle to request the first device to confirm whether the first target vehicle is authorized to perform the upgrade. In this way, the first device can determine whether the first target vehicle is authorized to perform the upgrade.

[0038] In a possible implementation, the OTA cloud may determine a first target vehicle based on vehicle fleet information from the first device and a first vehicle identifier. The first vehicle identifier is an identifier of a vehicle that needs to be upgraded and is obtained by the OTA cloud server. The first target vehicle is a vehicle in the vehicle fleet that needs to be upgraded and is determined by the OTA cloud.

[0039] In a possible implementation, the first indication information includes an address of the first device.

[0040] The first target vehicle can use the address of the first device to accurately and quickly determine the first device.

[0041] In a possible implementation, the second upgrade task information further includes related information of the upgrade task, and the related information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0042] The first device can use the relevant information of the upgrade task carried in the first request message to flexibly select the first target vehicle that is allowed to carry out the upgrade based on the actual situation.

[0043] In a possible implementation, the method further includes the OTA cloud receiving an upgrade result from the second target vehicle, the upgrade result including upgrade success, upgrade failure, rollback success, or rollback failure.

[0044] Further, in a possible implementation, the OTA cloud sends the upgrade result to the first device.

[0045] After completing the OTA-based upgrade, the second target vehicle notifies the OTA cloud of the upgrade result in a timely manner. Furthermore, the OTA cloud can synchronize the upgrade result of the second target vehicle to the first device in a timely manner, so that the upgrade information of the first device, the OTA cloud and the second target vehicle can be synchronized. In this way, the first device can effectively and reliably manage the upgrade status of each vehicle in the vehicle fleet.

[0046] In another possible implementation, the OTA cloud receives the upgrade results from the second target vehicle forwarded by the first device.

[0047] After completing the OTA-based upgrade, the second target vehicle notifies the first device of the upgrade result in a timely manner. Furthermore, the first device can synchronize the upgrade result of the second target vehicle to the OTA cloud in a timely manner, so that the upgrade information of the first device, the OTA cloud and the second target vehicle can be synchronized. In this way, the first device can effectively and reliably manage the upgrade status of each vehicle in the vehicle fleet.

[0048] According to a fifth aspect, the present application provides an upgrade method based on OTA technology, the method includes: a first device sends vehicle fleet information to an OTA cloud, the first device is configured to manage a vehicle fleet, the vehicle fleet includes at least two vehicles, and the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet; the first device receives a third request message from a first target vehicle, the third request message is used to request the first device to confirm whether the first target vehicle is authorized to perform an upgrade, the first target vehicle is related to the vehicle fleet information and the first vehicle, the first vehicle is a vehicle that needs to be upgraded and is obtained by the OTA cloud; and the first device sends a third response message to the first target vehicle, the third response message includes information indicating that the first target vehicle is authorized to perform an upgrade.

[0049] In a possible implementation, the third request message may further include relevant information of the upgrade task, where the relevant information of the upgrade task includes at least one of the duration required for the upgrade, the purpose of the upgrade, or the changes brought about by the upgrade.

[0050] In a possible implementation, the method further includes the first device receiving an upgrade result from the first target vehicle, where the upgrade result includes upgrade success, upgrade failure, rollback success, or rollback failure.

[0051] Furthermore, in a possible implementation, the method further includes the first device sending the upgrade result to the OTA cloud.

[0052] In another possible implementation, a first device receives an upgrade result of a first target vehicle transferred by an OTA cloud.

[0053] According to a sixth aspect, the present application provides an upgrade method based on OTA technology, the method including: receiving second upgrade task information from an OTA cloud, the second upgrade task information including an upgrade package and first instruction information, the first instruction information instructing the first target vehicle to request the first device to confirm whether the first target vehicle is authorized to perform the upgrade; the first device is configured to manage a vehicle fleet, the vehicle fleet includes at least two vehicles, the vehicle fleet information includes vehicle identifiers of the vehicles belonging to the same vehicle fleet, the first target vehicle is related to the vehicle fleet information and the first vehicle, and the first vehicle is configured to receive the upgrade package from the OTA cloud, the second upgrade task information including an upgrade package and first instruction information instructing the first target vehicle to request the first device to confirm whether the first target vehicle is authorized to perform the upgrade; the vehicle for which an upgrade is required and acquired by the OTA cloud; sending a third request message to the first device or the OTA cloud based on the second upgrade task information, where the third request message is used to request the first device to confirm whether the first target vehicle is authorized to perform the upgrade; and receiving a third response message from the first device, where the third response message includes information indicating that the first target vehicle is authorized to perform the upgrade.

[0054] The method may be performed by a first target vehicle.

[0055] In a possible implementation, the third request message further includes relevant information of the upgrade task, where the relevant information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0056] In a possible implementation, an upgrade result of the first target vehicle is sent to the first device or the OTA cloud, where the upgrade result includes upgrade success, upgrade failure, rollback success, or rollback failure.

[0057] For technical effects that can be realized in any one of the fifth and sixth aspects, please refer to the description of the beneficial effects of the fourth aspect, and the details will not be described again in this description.

[0058] According to a seventh aspect, the present application provides an upgrade method based on OTA technology, the method includes: receiving vehicle fleet information from a first device, the first device is configured to manage a vehicle fleet, the vehicle fleet includes at least two vehicles, the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet; and sending third upgrade task information to the first device, the third upgrade task information includes a vehicle identifier and an upgrade package of a first target vehicle, the first target vehicle is related to the vehicle fleet information and the first vehicle, the first vehicle is a vehicle that needs to be upgraded and is obtained by the OTA cloud, the upgrade package corresponds to the first target vehicle, and the upgrade package corresponds to a second target vehicle, the second target vehicle is at least one vehicle determined by the first device from the first target vehicle.

[0059] The method may be performed by an OTA cloud, which may also be referred to as an OTA cloud side, an OTA cloud server, etc.

[0060] According to the above solution, the first device sends vehicle fleet information to the OTA cloud, so that the OTA cloud can obtain vehicle identifiers of vehicles belonging to the same vehicle fleet, and further sends third upgrade task information to the first device, the third upgrade task information including the vehicle identifier of the first target vehicle. In this way, the first device can determine which first target vehicle is allowed to carry out the upgrade, which is useful for improving the security of the management of vehicles in the vehicle fleet.

[0061] In a possible implementation, the OTA cloud may determine a first target vehicle based on vehicle fleet information from the first device and a first vehicle identifier. The first vehicle identifier is an identifier of a vehicle that needs to be upgraded and is obtained by the OTA cloud server. The first target vehicle is a vehicle in the vehicle fleet that needs to be upgraded and is determined by the OTA cloud.

[0062] First, the OTA cloud determines the first target vehicle in the fleet that needs an upgrade, which allows the first device to quickly determine which first target vehicle is allowed to complete the upgrade.

[0063] In a possible implementation, the third upgrade task information further includes related information of the upgrade task, and the related information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0064] In a possible implementation, the method further includes the OTA cloud receiving an upgrade result from the second target vehicle, the upgrade result including upgrade success, upgrade failure, rollback success, or rollback failure.

[0065] Further, in a possible implementation, the OTA cloud sends the upgrade result to the first device.

[0066] After completing the OTA-based upgrade, the second target vehicle notifies the OTA cloud of the upgrade result in a timely manner. Furthermore, the OTA cloud can synchronize the upgrade result of the second target vehicle to the first device in a timely manner, so that the upgrade information of the first device, the OTA cloud and the second target vehicle can be synchronized. In this way, the first device can effectively and reliably manage the upgrade status of each vehicle in the vehicle fleet.

[0067] In another possible implementation, the OTA cloud receives the upgrade results from the second target vehicle forwarded by the first device.

[0068] After completing the OTA-based upgrade, the second target vehicle notifies the first device of the upgrade result in a timely manner. Furthermore, the first device can synchronize the upgrade result of the second target vehicle to the OTA cloud in a timely manner, so that the upgrade information of the first device, the OTA cloud and the second target vehicle can be synchronized. In this way, the first device can effectively and reliably manage the upgrade status of each vehicle in the vehicle fleet.

[0069] According to an eighth aspect, the present application provides an upgrade method based on OTA technology, the method includes: a first device sends vehicle fleet information to an OTA cloud, the first device is configured to manage a vehicle fleet, the vehicle fleet includes at least two vehicles, and the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet; the first device receives third upgrade task information from the OTA cloud, the third upgrade task information includes a first target vehicle identifier and an upgrade package; the first device determines at least one vehicle in the first target vehicles as a second target vehicle based on the third upgrade task information; and the first device sends fourth upgrade task information to the second target vehicle, the fourth upgrade task information being related to the third upgrade task information.

[0070] In a possible implementation, the fourth upgrade task information includes information obtained after the first device performs a digital signature on the upgrade package.

[0071] A digital signature is performed on the upgrade package included in the third upgrade task information to further improve security of communication between the first device and the second target vehicle.

[0072] In a possible implementation, the fourth upgrade task information further includes an upgrade type, and the upgrade type is a confirmed upgrade.

[0073] In a possible implementation, the method further includes the first device receiving an upgrade result from the second target vehicle, the upgrade result including upgrade success, upgrade failure, rollback success, or rollback failure.

[0074] Furthermore, in a possible implementation, the method further includes the first device sending the upgrade result to the OTA cloud.

[0075] In another possible implementation, the first device receives the upgrade results of the second target vehicle transferred by the OTA cloud.

[0076] For technical effects that can be realized in any of the eighth aspects, please refer to the description of the beneficial effects of the seventh aspect, and the details will not be described again in this description.

[0077] According to a ninth aspect, the present application provides a communication device, configured to perform a method according to the first aspect and any one of the possible implementations of the first aspect, configured to perform a method according to the second aspect and any one of the possible implementations of the second aspect, configured to perform a method according to the third aspect and any one of the possible implementations of the third aspect, configured to perform a method according to the fourth aspect and any one of the possible implementations of the fourth aspect, configured to perform a method according to the fifth aspect and any one of the possible implementations of the fifth aspect, configured to perform a method according to the sixth aspect and any one of the possible implementations of the sixth aspect, configured to perform a method according to the seventh aspect and any one of the possible implementations of the seventh aspect, or configured to perform a method according to the eighth aspect and any one of the possible implementations of the eighth aspect, including corresponding functional modules respectively configured to perform steps of the above methods. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0078] In a possible implementation, the communication device may be an OTA cloud, a first device, a vehicle, or a module used in the OTA cloud, the first device, or the vehicle, such as a chip, a chip system, or a circuit. For beneficial effects, please refer to the corresponding method description. This description will not be repeated in detail. The communication device may include an interface circuit and a processor. Through logic circuits or by executing code instructions, the processor is configured to perform a method according to the first aspect and any one of its possible implementations, to perform a method according to the second aspect and any one of its possible implementations, to perform a method according to the third aspect and any one of its possible implementations, to perform a method according to the fourth aspect and any one of its possible implementations, to perform a method according to the fifth aspect and any one of its possible implementations, to perform a method according to the sixth aspect and any one of its possible implementations, to perform a method according to the seventh aspect and any one of its possible implementations, or to perform a method according to the eighth aspect and any one of its possible implementations. The interface circuit is configured to receive signals from a communication device other than the communication device, to transmit signals to the processor, and to transmit signals from the processor to a communication device other than the communication device. The interface circuit may be a separate receiver, a separate transmitter, or a transceiver incorporating both receiving and transmitting functions. Alternatively, the communication device may further include a memory. The memory may be coupled to the processor and configured to store program instructions and data required for the communication device. Alternatively, the communication device may further include a memory. The memory may be coupled to the processor and configured to store program instructions and data required for the communication device.

[0079] Please refer to the above method description for possible implementations, and the details will not be described again in this description.

[0080] According to a tenth aspect, the present application provides a communication device, configured to perform a method according to the first aspect and any one of the possible implementations of the first aspect, configured to perform a method according to the second aspect and any one of the possible implementations of the second aspect, configured to perform a method according to the third aspect and any one of the possible implementations of the third aspect, configured to perform a method according to the fourth aspect and any one of the possible implementations of the fourth aspect, configured to perform a method according to the fifth aspect and any one of the possible implementations of the fifth aspect, configured to perform a method according to the sixth aspect and any one of the possible implementations of the sixth aspect, configured to perform a method according to the seventh aspect and any one of the possible implementations of the seventh aspect, or configured to perform a method according to the eighth aspect and any one of the possible implementations of the eighth aspect, including corresponding functional modules respectively configured to perform steps of the above methods. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0081] In a possible implementation, the communication device may be an OTA cloud, a first device, or a vehicle. The communication device may include a processing module and a transceiver module. These modules may perform the corresponding functions of the terminal device of the above method example. For details, please refer to the detailed description of the method example. This description will not repeat the details.

[0082] According to an eleventh aspect, the present application provides a chip including a processor, coupled to a memory and configured to execute computer programs or instructions stored in the memory to enable the chip to perform a method according to the first aspect and any one of its possible implementations, to perform a method according to the second aspect and any one of its possible implementations, to perform a method according to the third aspect and any one of its possible implementations, to perform a method according to the fourth aspect and any one of its possible implementations, to perform a method according to the fifth aspect and any one of its possible implementations, to perform a method according to the sixth aspect and any one of its possible implementations, to perform a method according to the seventh aspect and any one of its possible implementations, or to perform a method according to the eighth aspect and any one of its possible implementations.

[0083] According to a twelfth aspect, the present application provides a communication system. The communication system includes an OTA cloud, a first device, and a second target vehicle. The OTA cloud may be configured to perform a method according to any one of the first aspect and possible implementations of the first aspect. The first device may be configured to perform a method according to any one of the second aspect and possible implementations of the second aspect. The second target vehicle is configured to perform a method according to any one of the third aspect and possible implementations of the third aspect.

[0084] According to a thirteenth aspect, the present application provides a communication system. The communication system includes an OTA cloud, a first device, and a first target vehicle. The OTA cloud may be configured to perform a method according to any one of the fourth aspect and possible implementations of the fourth aspect. The first device may be configured to perform a method according to any one of the fifth aspect and possible implementations of the fifth aspect. The first target vehicle may be configured to perform a method according to any one of the sixth aspect and possible implementations of the sixth aspect.

[0085] According to a fourteenth aspect, the present application provides a communication system. The communication system includes an OTA cloud and a first device. The OTA cloud may be configured to perform the method according to any one of the seventh aspect and possible implementations of the seventh aspect. The first device may be configured to perform the method according to any one of the eighth aspect and possible implementations of the eighth aspect.

[0086] According to a fifteenth aspect, the present application provides a computer readable storage medium. The computer readable storage medium stores a computer program or instructions. When the computer program or instructions are executed by a communication device, the communication device is enabled to perform a method according to the first aspect and any one of the possible implementations of the first aspect, to perform a method according to the second aspect and any one of the possible implementations of the second aspect, to perform a method according to the third aspect and any one of the possible implementations of the third aspect, to perform a method according to the fourth aspect and any one of the possible implementations of the fourth aspect, to perform a method according to the fifth aspect and any one of the possible implementations of the fifth aspect, to perform a method according to the sixth aspect and any one of the possible implementations of the sixth aspect, to perform a method according to the seventh aspect and any one of the possible implementations of the seventh aspect, or to perform a method according to the eighth aspect and any one of the possible implementations of the eighth aspect.

[0087] According to a sixteenth aspect, the present application provides a computer program product, the computer program product including a computer program or instructions, which when executed by a communication device, enables the communication device to perform a method according to the first aspect and any one of the possible implementations of the first aspect, to perform a method according to the second aspect and any one of the possible implementations of the second aspect, to perform a method according to the third aspect and any one of the possible implementations of the third aspect, to perform a method according to the fourth aspect and any one of the possible implementations of the fourth aspect, to perform a method according to the fifth aspect and any one of the possible implementations of the fifth aspect, to perform a method according to the sixth aspect and any one of the possible implementations of the sixth aspect, to perform a method according to the seventh aspect and any one of the possible implementations of the seventh aspect, or to perform a method according to the eighth aspect and any one of the possible implementations of the eighth aspect. [Brief description of the drawings]

[0088] [Figure 1] FIG. 1 is an architecture diagram of a communication system according to the present application. [Diagram 2] FIG. 1 is a diagram of a possible application scenario of the present application. [Diagram 3] 1 is a schematic flowchart of an upgrade method based on OTA technology according to the present application; [Figure 4] 2 is a schematic flowchart of a method for determining a second target vehicle by a first device according to the present application; [Diagram 5] 4 is a schematic flowchart of another method for determining a second target vehicle by a first device according to the present application. [Figure 6] 4 is a schematic flowchart of yet another method for determining a second target vehicle by a first device according to the present application; [Figure 7] 4 is a schematic flowchart of a second target vehicle upgrading method according to the present application; [Figure 8] 4 is a schematic flowchart of another upgrade method based on OTA technology according to the present application; [Figure 9] 1 is a schematic flowchart of a method for determining, by a first device, a first target vehicle that is permitted to perform an upgrade according to the present application; [Figure 10] 4 is a schematic flow chart of another method for determining, by a first device, a first target vehicle that is permitted to perform an upgrade according to the present application; [Figure 11] 4 is a schematic flowchart of another upgrade method based on OTA technology according to the present application; [Figure 12] 4 is a schematic flowchart of a method for sending fourth upgrade task information to a second target vehicle by a first device according to the present application; [Figure 13] FIG. 2 is a diagram of the structure of a communication device according to the present application; [Figure 14] FIG. 2 is a diagram of the structure of a communication device according to the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0089] Hereinafter, embodiments of the present application will be described in detail with reference to the accompanying drawings.

[0090] FIG. 1 is a diagram of the architecture of a communication system to which the present application can be applied. The communication system may include a server, a first device, and a second device. As an example, in FIG. 1, the communication system includes a server 101, a first device 102, and four second devices (second device 103a, second device 103b, second device 103c, and second device 103d, respectively). The second device 103a, the second device 103b, and the second device 103c belong to the same group. The first device 102 is configured to manage a group (or referred to as a group) including the second device. It can also be seen that the second device 103a, the second device 103b, and the second device 103c belong to the first device 102. It should be noted that the communication system may further include a second device that does not belong to the group (or group), for example, the second device 103d. The communication between the server 101 and the first device 102, and the communication between the server 101 and the second device 103a, the second device 103b, the second device 103c, and the second device 103d may be implemented through a mobile communication network (e.g., a network such as 2G / 3G / 4G / 5G / future 6G), a wireless local area network (wireless local area network, WLAN), or the like, or may be implemented using a short-range communication technology. In an embodiment of the present application, the short-range communication technology may include a technology that supports wireless short-range communication. The wireless short-range communication includes a communication in which both communication parties transmit information using radio waves and the transmission distance is in a short range (e.g., within 100 meters), and may be referred to as short-range wireless communication. Short-range wireless communication includes, but is not limited to, Bluetooth technology, wireless fidelity (Wi-Fi) technology, near field communication (NFC) technology, Wi-Fi Aware technology, general short-range communication technologies, and short-range communication technologies defined by the SparkLink Alliance.The communication between the first device 102 and the second device 103b, the second device 103c and the second device 103d may be implemented through a mobile communication network (e.g., a network such as 2G / 3G / 4G / 5G / future 6G), a WLAN, a Wi-Fi network, etc., or may be implemented using a short-range communication technology. For the short-range communication technology, please refer to the above related description. This description will not be repeated in detail.

[0091] The server 101 may be a single server or a server cluster including multiple servers. For example, the server 101 may be a server cluster in which multiple servers are deployed using a distributed architecture. The server cluster may include one or more of a cloud computing server, a content delivery network (CDN) server, a domain name system (DNS) server, etc. The servers may cooperate with each other to jointly perform functions such as computation, data storage, and communication. For ease of explanation, the single server, the distributed server, the server cluster, etc. are collectively referred to as a server in this application. Furthermore, the server may be a physical device, a virtual machine, a container, etc. that is deployed on a cloud. The server may store an upgrade file of the second device. The first device 102 may be a user equipment (UE), a host, a server, a terminal device such as a mobile phone, a notebook computer, or a tablet computer configured to manage a group including the second device. By way of example, the second device (e.g., second device 103a, second device 103b, second device 103c, or second device 103d) may be a device such as a vehicle, a smart TV, a smartphone, a tablet computer, or a set-top box.

[0092] It should be noted that the configurations and numbers of the server, the first device and the second device shown in FIG. 1 are merely examples and do not constitute limitations to the present application.

[0093] Based on the above, FIG. 2 is a diagram of a possible application scenario according to the present application. The application scenario is described using an example in which vehicles in a vehicle fleet are upgraded based on OTA. In the application scenario, as an example, the server is an OTA cloud 201 (or referred to as an OTA cloud side, an OTA cloud server, etc.), the first device 202 is a host connected to a display, and the second devices are vehicles 203a, 203b, and 203c. The vehicles 203a, 203b, and 203c belong to the same vehicle fleet. The vehicle fleet belongs to the first device 202, i.e., the first device 202 is configured to manage the vehicles 203a, 203b, and 203c. The first device 202 may be referred to as a vehicle fleet (or vehicle) owner. The OTA cloud 201 may communicate with the first device 202 through a mobile communication network (e.g., a network such as 2G / 3G / 4G / 5G / future 6G), through a WLAN, or using a short-range communication technology. In the present application, the manner in which the first device communicates with the OTA cloud is not limited. Furthermore, the OTA cloud may communicate with the vehicle 203a, the vehicle 203b, the vehicle 203c, and the vehicle 203d through a mobile communication network (e.g., a network such as 2G / 3G / 4G / 5G / future 6G), through a WLAN, or using a short-range communication technology. Furthermore, the first device 202 may communicate with the vehicle 203a, the vehicle 203b, the vehicle 203c, and the vehicle 203d through a mobile communication network (e.g., a network such as 2G / 3G / 4G / 5G / future 6G), through a WLAN, or using a short-range communication technology.

[0094] The vehicles (e.g., vehicle 203a, vehicle 203b, and vehicle 203c) may be any type of vehicle that can perform software upgrades, including, for example, intelligent vehicles, electric vehicles, digital vehicles, automobiles, trucks, motorcycles, buses, lawnmowers, entertainment vehicles, playground vehicles, construction devices, trams, and golf carts, without limitation in this application. Vehicle 203a is used as an example in FIG. 2. The vehicle includes at least one of a gateway (GW), a human-machine interaction (HMI) system, a telematics control unit (TCU), a telematics box (Tbox), an electronic control unit (ECU), and an embedded software hardware platform used to support intelligent driving, i.e., a vehicle computing platform, such as a mobile data center (MDC). The GW is the core component of the vehicle's electronic and electrical architecture. The GW acts as the data exchange hub of the vehicle network and may route network data within various networks, such as controller area network (CAN), local interconnect network (LIN), and media oriented system transport (MOST) network. The MDC is the vehicle's intelligent vehicle computing platform, and the MDC may be used to implement the vehicle's autonomous driving functions. The HMI is the vehicle's infotainment system.The TCU and Tbox are mainly configured to communicate with devices outside the vehicle, outside the vehicle's background system, etc. (e.g., cloud, fleet owner). The ECU is a dedicated microcomputer controller of the vehicle. The ECU includes, but is not limited to, a vehicle integrated / integration unit (VIU), a cockpit domain controller (CDC), a vehicle domain controller (VDC), etc. It should be noted that in this application, what needs to be upgraded may include, but is not limited to, any one or more of the GW, MDC, HMI, TCU, Tbox, and ECU, and may also include an operating system, navigation software, map software, monitoring software, etc.

[0095] The OTA cloud is a server that exchanges information with the vehicle in the process of the OTA-based upgrade. Typically, the OTA cloud may be a server that provides the OTA-based upgrade. For example, the OTA cloud may establish a connection to a software development device through an internet protocol (IP) network to obtain a software package required for the upgrade, and send the software package to the vehicle that needs to be upgraded. In addition, the OTA cloud may further indicate to the vehicle which software needs to be upgraded. For example, the OTA cloud stores an identification number and software version information of each vehicle. Typically, the OTA cloud may be managed by an OEM. The first device may be a host configured to manage a fleet of vehicles, and the host may be connected to a display.

[0096] Further, in a possible implementation, in a vehicle, an OTA primary module (or referred to as an OTA master module or an upgrade main module) may be deployed in a GW, and some of the other components have OTA secondary modules (or referred to as an OTA slave module or an upgrade secondary module of the corresponding component). The OTA primary module may be configured to coordinate the OTA secondary modules of each component to perform the upgrade task. In particular, the OTA primary module of the GW receives the upgrade package sent by the OTA cloud, and distributes the upgrade package to the OTA secondary modules. In this way, the OTA secondary module points another component of the vehicle to install and activate the upgrade package, thereby completing the upgrade of one or more components of the vehicle. It can be seen that the OTA primary module may be deployed in a TCU module or a Tbox module instead of the above.

[0097] It is understood that the configurations and numbers of the OTA cloud, the first device, and the vehicle shown in FIG. 2 are merely examples and do not constitute limitations to the present application.

[0098] It should be noted that the above described system architecture and application scenarios are intended to more clearly describe the technical solutions in the present application, and do not constitute limitations on the technical solutions provided in the present application. For example, the OTA-based upgrade method of the present application may be further applied to upgrade scenarios of devices such as smart TVs, smartphones, tablet computers, and set-top boxes.

[0099] As described in the background art, the users and owners of vehicles belonging to the same vehicle fleet are usually different. Therefore, the upgrade status of the vehicle is not visible to the vehicle owner. As a result, the vehicle owner cannot manage and control the software version of the vehicle in a timely manner, which results in the risk of vehicle management.

[0100] In view of the above problems, the present application provides an OTA-based upgrade method, which enables a fleet owner to timely manage and control the upgrade status of vehicles in the fleet, thereby improving the security of vehicle management.

[0101] The OTA-based upgrade method provided in this application may be applied to the communication system shown in Fig. 1. In the OTA-based upgrade method described below, the OTA cloud may be the server 101 in Fig. 1, the first device may be the first device 102 in Fig. 1, and the vehicle in the vehicle fleet may be the second device 103a, the second device 103b, or the second device 103c in Fig. 1. Alternatively, the OTA-based upgrade method provided in this application may be applied to the application scenario shown in Fig. 2. The OTA cloud may be the OTA cloud 201 in Fig. 2, the first device may be the first device 202 in Fig. 2, and the vehicle in the vehicle fleet may be the vehicle 203a, the vehicle 203b, or the vehicle 203c in Fig. 2.

[0102] Based on the above, the upgrade method based on OTA technology provided in this application will be specifically described below with reference to FIG. 3 to FIG.

[0103] 3 is a schematic flow chart of an upgrade method based on OTA technology according to the present application. The method may include the following steps:

[0104] Step 301: A first device sends vehicle fleet information to the OTA cloud. In response, the OTA cloud receives vehicle fleet information from the first device.

[0105] The first device is configured to manage a fleet of vehicles, the fleet including at least two vehicles, and the fleet information includes vehicle identifiers of vehicles belonging to the same fleet. By way of example, but not limited to, the vehicle identifiers may include a vehicle identification number (VIN). With reference to FIG. 2, the fleet information may include a vehicle identifier of vehicle 203a, a vehicle identifier of vehicle 203b, and a vehicle identifier of vehicle 203c. Furthermore, in an optional implementation, the fleet information may further include a fleet identifier.

[0106] Table 1 shows possible vehicle fleet information provided in this application. Table 1 shows that the vehicle identifiers corresponding to vehicle fleet identifier 1 include VIN1 through VIN3, the vehicle identifiers corresponding to vehicle fleet identifier 2 include VIN4 and VIN5, etc.

[0107] [Table 1]

[0108] As an example, vehicles belonging to the same owner may form a vehicle group, and it can be seen that the vehicles in the vehicle group belong to the same vehicle group. With reference to FIG. 2, a vehicle 203a, a vehicle 203b, and a vehicle 203c belong to the same vehicle group. The vehicle group may be managed by a first device. It can be seen that the first device may be configured to manage one or more vehicle groups. To facilitate the description of the solution of the present application, an example in which the first device manages one vehicle group is used for the description.

[0109] Step 302: The OTA cloud determines a first target vehicle based on the vehicle fleet information from the first device and the first vehicle identifier.

[0110] Step 302 is an optional step.

[0111] The first vehicle is a vehicle that needs to be upgraded and is obtained by the OTA cloud. The first vehicle identifier is a vehicle identifier of the first vehicle. The first target vehicle is related to the vehicle fleet information and the first vehicle. Specifically, the first target vehicle may be a vehicle that needs to be upgraded in a vehicle fleet corresponding to the vehicle fleet information and is determined by the OTA cloud based on the vehicle fleet information and the first vehicle.

[0112] In a possible implementation example, the OTA cloud determines that N first vehicles need to be upgraded, and one first vehicle corresponds to one first vehicle identifier. It can also be seen that the OTA cloud determines that N first vehicles corresponding to the N first vehicle identifiers need to be upgraded, where N is a positive integer. For example, if the vehicle's software has vulnerabilities (i.e., the vulnerabilities need to be fixed), new functions need to be added, security protection needs to be upgraded, architecture needs to be upgraded, etc., the OTA cloud may determine that the vehicle needs to be upgraded, and the OTA cloud may generate a corresponding upgrade package.

[0113] Further, in an optional implementation, the OTA cloud may determine a vehicle group identifier to which the first vehicle identifier belongs, or may determine whether the vehicle group identifier included in the vehicle group information is the same as the vehicle group identifier to which the first vehicle identifier belongs. If the vehicle group identifier included in the vehicle group information is the same as the vehicle group identifier to which the first vehicle identifier belongs, the OTA cloud may use the first vehicle identifier to match the vehicle identifiers in the vehicle group information one by one, and determine a vehicle that is the same as the first vehicle identifier and corresponds to a vehicle identifier that is one of the vehicle identifiers in the vehicle group information as a first target vehicle. For example, the OTA cloud may determine M first target vehicles based on the vehicle group information and N first vehicle identifiers (M is a positive integer equal to or less than N).

[0114] For example, the OTA cloud may pre-store the correspondence between the vehicle group identifier and the vehicle identifier. Furthermore, the OTA cloud may further create an account for each corresponding vehicle group, and store the vehicle group, the vehicle group identifier, and an account corresponding to the vehicle identifier (e.g., the first vehicle identifier) ​​of a vehicle (e.g., the first vehicle) included in the vehicle group. It can be seen that the first device may pre-acquire vehicle group information of the managed vehicle group. For example, the vehicle group information of the managed vehicle group may be input by a user.

[0115] Step 303: The OTA cloud sends the first upgrade task information to the second target vehicle. In response, the second target vehicle receives the first upgrade task information from the OTA cloud.

[0116] The first upgrade task information includes an upgrade package. The second target vehicle is at least one vehicle determined by the first device from the first target vehicle. For possible determination methods, please refer to the descriptions of Method 1 and Method 2. This description will not repeat the details.

[0117] In addition, apart from the above, the first upgrade task information may further include an upgrade type. The upgrade type may include, but is not limited to, a confirmed upgrade (i.e., the first device has confirmed that the upgrade can be performed directly), a silent upgrade (a direct upgrade is performed without notifying the user), a conventional upgrade (a direct upgrade is performed with the user's consent), a forced upgrade (a direct upgrade is performed without the user's consent after notifying the user), etc. As an example, the user may be a driver of the second target vehicle.

[0118] From steps 301 to 303, it can be seen that the first device sends vehicle fleet information to the OTA cloud, so that the OTA cloud can obtain vehicle identifiers of vehicles belonging to the same vehicle fleet, and send first upgrade task information to a second target vehicle that needs to be upgraded and is determined by the first device.

[0119] Before step 301, a secure channel (also referred to as secure communication) between the OTA cloud and the first device may also be pre-established. For example, before sending the vehicle fleet information to the OTA cloud, the first device may perform some configuration, such as setting a certificate and a private key. Based on the configured information, a secure channel may be established between the OTA cloud and the first device. For example, the secure channel may include, but is not limited to, one or more secure channels based on hypertext transfer protocol over secure socket layer (HTTPS) and datagram transport layer security (DTLS). The type of the secure channel is not limited in the present application. The secure channel between the OTA cloud and the first device is useful for preventing information (e.g., vehicle fleet information) and data exchanged between the first device and the OTA cloud from being leaked, tampered with, corrupted, etc.

[0120] Before step 303, a secure channel may also be pre-established between the OTA cloud and a vehicle in the fleet (e.g., a second target vehicle). For details, refer to the secure channel established between the OTA cloud and the first device. The secure channel between the OTA cloud and the vehicle in the fleet is useful for preventing information (e.g., the first upgrade task information) and data exchanged between the vehicle in the fleet and the OTA cloud from being leaked, tampered with, corrupted, etc.

[0121] Based on what is described in FIG. 3, three possible examples of methods for determining the second target vehicle are given below.

[0122] Method 1 4 is a schematic flowchart of a method for determining a second target vehicle by a first device according to the present application. The method includes the following steps:

[0123] Step 401: The OTA cloud sends a first request message to the first device, and in response, the first device receives the first request message from the OTA cloud.

[0124] The first request message is used to request the first device to determine a second target vehicle from the first target vehicle that is authorized to perform the upgrade. Illustratively, the first request message includes a vehicle identifier of the first target vehicle.

[0125] Further, in an optionally selectable implementation, the first request message may further include relevant information for the upgrade task, the relevant information for the upgrade task including at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0126] Further, in an optional implementation, the associated information of the upgrade task may further include upgrade conditions, upgrade order, user notification policy, upgrade package size, etc. The upgrade conditions may ensure that the vehicle is successful in downloading the upgrade package. By way of example, the upgrade conditions may include a condition that the vehicle is not in one or more of an emergency operation state, an engine running state, insufficient storage space, remaining traffic is less than a predefined traffic threshold, etc. The upgrade order may indicate a time order in which various components are upgraded. The upgrade package size may range from approximately a few megabytes (M) to over 10M.

[0127] It should be noted that the above upgrade types may also belong to one item of related information of an upgrade task.

[0128] Step 402: The first device determines at least one vehicle among the first target vehicles as a second target vehicle based on the first request message.

[0129] It can be seen that the number of first target vehicles is equal to or greater than the number of second target vehicles.

[0130] In a possible implementation, the first device may determine all of the first target vehicles as the second target vehicles that are permitted to perform the upgrade.

[0131] In another possible implementation, the first device may determine a portion of the first target vehicle as the second target vehicle that is permitted to perform the upgrade.

[0132] In yet another possible implementation, the first device may determine from the first target vehicle a second target vehicle on which the upgrade is permitted to be completed based on at least one of the time period required for the upgrade, the purpose of the upgrade, the changes brought about by the upgrade, etc.

[0133] It should be noted that the above provided possible implementations in which the first device determines the second target vehicle that is permitted to perform the upgrade from the first target vehicle are merely examples and are not limiting in this application.

[0134] After determining the second target vehicle, the first device may notify the OTA cloud with the following three possible solutions: In solution 1, the following step 403 is performed; In solution 2, the following steps 404 to 406 are performed; In solution 3, the following steps 407 and 408 are performed.

[0135] Step 403: The first device sends a first response message to the OTA cloud, and in response, the OTA cloud receives a first response message from the first device.

[0136] It can also be seen that the first device sends a first response message directly to the OTA cloud.

[0137] The first response message may include information about the second target vehicle. It is also understood that the first response message may include information related to the second target vehicle that is permitted to perform the upgrade and is selected from the first target vehicles. As an example, the first response message includes a second target vehicle identifier. It should be noted that instead of the above, the information about the second target vehicle may be other possible information, for example, any pre-agreed form of information. This is not limited in the present application.

[0138] Step 404: The first device sends second instruction information to the second target vehicle that is authorized to perform the upgrade, and in response, the second target vehicle receives second instruction information from the first device.

[0139] The second indication information may indicate whether the second target vehicle is allowed to upgrade or not, or may indicate that the second target vehicle is allowed to upgrade. The specific form of the second indication information may be pre-agreed by the first device and the second target vehicle. For example, if the second indication information is "1", this indicates that the second target vehicle is allowed to upgrade, or the second indication information is an identifier of the second target vehicle. It should be noted that the specific content of the second indication information may be notified or performed by the first device to the second target vehicle. This is not limited in the present application.

[0140] Here, when the first device determines that there are multiple second target vehicles, the first device may send the second instruction information to each of the multiple second target vehicles.

[0141] Step 405: The second target vehicle generates a first response message based on the second indication information.

[0142] For an explanation of the first response message, please refer to the explanation of step 403. Details will not be repeated in this description.

[0143] Step 406: The second target vehicle sends a first response message to the OTA cloud. In response, the OTA cloud receives a first response message from the second target vehicle.

[0144] Step 407: The first device sends a first response message to the second target vehicle, and in response, the second target vehicle receives a first response message from the first device.

[0145] Here, if the first device determines that there are multiple second target vehicles, the first device may send the first response message to each of the multiple second target vehicles.

[0146] Step 408: The second target vehicle sends a first response message to the OTA cloud.

[0147] In steps 407 and 408, it is also seen that the second target vehicle is configured to transparently transmit the first response message of the first device.

[0148] According to steps 401 to 408, the first device can use the relevant information of the upgrade task carried in the first request message to flexibly select the first target vehicle that is allowed to perform the upgrade based on the actual situation. In addition, the first device can collectively determine the second target vehicle that is allowed to perform the upgrade from the first target vehicle, which is useful for simplifying the management of the vehicle fleet by the first device.

[0149] Method 2 5 is a schematic flow chart of another method for determining a second target vehicle by a first device according to the present application. The method includes the following steps:

[0150] Step 501: The OTA cloud sends first instruction information to a first target vehicle, and in response, the first target vehicle receives the first instruction information from the OTA cloud.

[0151] The first instruction indicates to the first target vehicle to request the first device to confirm whether the upgrade is permitted.

[0152] In a possible implementation, the first indication information includes an address of the first device. For example, the address may be a uniform resource locator (URL) link. The URL link may be linked to a web page or an application (APP) of the first device. In this manner, the first target vehicle can accurately and quickly determine the first device.

[0153] Step 502: The first target vehicle sends a second request message to the OTA cloud according to the first instruction information, and the OTA cloud correspondingly receives the second request message from the first target vehicle.

[0154] The second request message is used to request the first device to determine whether the first target vehicle is authorized to perform the upgrade. By way of example, the second request message includes a vehicle identifier of the first target vehicle.

[0155] In addition, in an optional implementation, the first instruction information further includes upgrade task related information, which may include, but is not limited to, at least one of a required time period for the upgrade, a purpose of the upgrade, or a change brought about by the upgrade. The upgrade task related information may be used by the first target vehicle to determine whether to send the second request message to the OTA cloud.

[0156] For example, after receiving the first instruction information, the first target vehicle may determine whether to send a second request message to the OTA cloud based on the relevant information of the upgrade task included in the first instruction information. In one example, the first target vehicle determines whether the current status is one or more of an emergency operation state, an engine running state, insufficient storage space, remaining traffic is less than a predefined traffic threshold, etc. If the first target vehicle determines that the current status is one or more of the above states, the first target vehicle may not temporarily send the second request message to the OTA cloud. In another example, if the first target vehicle determines that the current status is not one of the above states, the first target vehicle sends the second request message to the OTA cloud.

[0157] In a possible implementation, the second request message may further carry relevant information of the upgrade task, which is useful for the first device to determine whether the first target vehicle that sent the second request message is allowed to perform the upgrade based on the relevant information of the upgrade task.

[0158] Step 503: The OTA cloud forwards the second request message to the first device. In response, the first device receives the second request message from the OTA cloud.

[0159] In a possible implementation, the OTA cloud transparently sends the second request message to the first device. In another possible implementation, the OTA cloud may process the second request message and then forward the processed second request message to the first device, but the function and indication of the second request message remain unchanged. For example, when the communication protocol between the OTA cloud and the first target vehicle and the communication protocol between the OTA cloud and the first device are different, the OTA cloud may process the second request message to perform protocol conversion. In the present application, the specific implementation of the OTA cloud forwarding the second request message is not limited. Step 504: The first device determines the first target vehicle as the second target vehicle based on the second request message.

[0160] In a possible implementation, the first device directly determines that the first target vehicle that sent the second request message is permitted to perform the upgrade. It can also be seen that the first device may directly determine the first target vehicle that sent the second request message as the second target vehicle.

[0161] In another possible implementation example, the first device may determine whether the first target vehicle that sent the second request message is authorized to perform the upgrade based on the relevant information of the upgrade task carried in the second request message.

[0162] For example, one first target vehicle may send a second request message to the first device, and if the first device determines that the first target vehicle that sent the second request message is permitted to perform the upgrade, this corresponds to determining the first target vehicle that sent the second request message as a second target vehicle.

[0163] Step 505: The first device sends a second response message to the OTA cloud, and in response, the OTA cloud receives a second response message from the first device.

[0164] The second response message includes information about the second target vehicle. In a possible implementation, the second response message may directly include information about the second target vehicle. As an example, the second response message includes a vehicle identifier of the second target vehicle. In another possible implementation, the second response message may include third indication information. The third indication information points to information about the second target vehicle. It should be noted that the third indication information may be any pre-agreed form of information. This is not limited in the present application.

[0165] Method 3 6 is a schematic flow chart of yet another method for determining a second target vehicle by a first device according to the present application. The method includes the following steps:

[0166] Step 601: The OTA cloud sends first instruction information to a first target vehicle. In response, the first target vehicle receives the first instruction information from the OTA cloud.

[0167] For step 601, please refer to the description of step 501. Details will not be described in this description.

[0168] Step 602: The first target vehicle sends a second request message to the first device based on the first instruction information, and in response, the first device receives a second request message from the first target vehicle.

[0169] Step 603: The first device determines the first target vehicle as a second target vehicle based on the second request message.

[0170] For step 603, please refer to the description of step 504. Details will not be described in this description.

[0171] Step 604: The first device sends a second response message to the OTA cloud, and in response, the OTA cloud receives a second response message from the first device.

[0172] For step 604, please refer to the description of step 505. Details will not be described in this description.

[0173] In a possible scenario, method 2 can be applied when a vehicle in the fleet cannot directly communicate with the first device, and method 3 can be applied when a vehicle in the fleet can directly communicate with the first device. In addition, in a different scenario, when a vehicle in the fleet directly communicates with the first device, a fleet agent is deployed in at least one vehicle, and an OTA agent is deployed in another vehicle. A vehicle in which a fleet agent is deployed may directly communicate with the first device. A vehicle in which an OTA agent is deployed may directly communicate with a vehicle in which a fleet agent is deployed. The fleet agent is software that can interact with the first device and / or the OTA cloud and is deployed on the vehicle side. The OTA agent is software that is to be upgraded based on OTA.

[0174] According to the method 2 or 3, the first target vehicle can initiate the first device to confirm whether the first target vehicle is permitted to perform the upgrade based on the first instruction information, without prompting or asking the driver for confirmation through the HMI, which is useful for reducing the burden on the driver. In addition to the above, the first device determines which first target vehicle is permitted to perform the upgrade, which is useful for improving the security of the management of vehicles in the vehicle fleet.

[0175] After receiving the first upgrade task, the second target vehicle can perform an upgrade based on the first upgrade task information, and synchronize the upgrade result with the first device and OTA.

[0176] 7 is a schematic flowchart of a second target vehicle upgrading method according to the present application. The method includes the following steps:

[0177] Step 701: A second target vehicle performs an upgrade based on the first upgrade task information.

[0178] In a possible implementation, the first upgrade task information may further include an upgrade type. After determining that the upgrade type is a confirmed upgrade, the second target vehicle may perform an upgrade according to an OTA upgrade procedure based on the upgrade package included in the received first upgrade task information without confirmation by the user (or referred to as the driver) of the second target vehicle. This can reduce the burden on the driver.

[0179] In another possible implementation example, if the second target vehicle determines that the upgrade type is not a confirmed upgrade, the second target vehicle may prompt the user of the second target vehicle through the human-machine interaction HMI system to confirm whether to perform the upgrade. If it is detected that the user of the second target vehicle has confirmed to perform the upgrade, the second target vehicle may perform the upgrade based on the upgrade package included in the received first upgrade task information.

[0180] After the second target vehicle completes the upgrade, the upgrade result may be synchronized to the first device and the OTA cloud using the following two possible solutions: Solution A includes steps 702 and 703; Solution B includes steps 704 and 705.

[0181] Step 702: The second target vehicle sends the upgrade result to the OTA cloud. In response, the OTA cloud receives the upgrade result from the second target vehicle.

[0182] The upgrade result may include, but is not limited to, upgrade success, upgrade failure, rollback success, or rollback failure. In particular, if the second target vehicle successfully performs the upgrade, the second target vehicle sends the upgrade result of upgrade success to the OTA cloud. If the second target vehicle fails to perform the upgrade, the second target vehicle sends the upgrade result of upgrade failure to the OTA cloud. Furthermore, in an optional implementation, if the second target vehicle fails to perform the upgrade, the second target vehicle may perform a rollback to minimize the impact on the normal use of the vehicle. Based on this, if the rollback is successful, the second target vehicle may send the upgrade result of rollback success to the OTA cloud, and if the rollback is unsuccessful, the second target vehicle may send the upgrade result of rollback failure to the OTA cloud.

[0183] For example, a specific form of the upgrade result may be pre-agreed by the second target vehicle and the OTA cloud. For example, 1 indicates upgrade success, 0 indicates upgrade failure, 10 indicates rollback success, and 00 indicates rollback failure. Alternatively, a specific form of the upgrade result may be indicated by the second target vehicle to the OTA cloud. The present application is not limited to the specific form of the upgrade result.

[0184] Further, apart from the above, the upgrade result may further include information about the second target vehicle. In one example, the upgrade result may further include a vehicle identifier of the second target vehicle. In another example, the upgrade result may further include third instruction information. The third instruction information indicates the information about the second target vehicle. In this manner, the OTA cloud and the first device can quickly determine the upgrade result of the second target vehicle.

[0185] In one example, a second target vehicle may send the upgrade results to an OTA cloud that establishes a communication connection to a component such as a Tbox.

[0186] Step 703: The OTA cloud sends the upgrade result to the first device. In response, the first device receives the upgrade result from the OTA cloud.

[0187] It can also be seen that after receiving the upgrade result from the second target vehicle, the OTA cloud synchronizes the upgrade result to the first device in a timely manner.

[0188] Step 704: The second target vehicle sends the upgrade result to the first device. In response, the first device receives the upgrade result from the second target vehicle.

[0189] For step 704, please refer to the description of step 702. Specifically, the "OTA cloud" in step 702 may be replaced with "first device". This description will not repeat the details.

[0190] Step 705: The first device sends the upgrade result to the OTA cloud. In response, the OTA cloud receives the upgrade result from the first device.

[0191] In other words, after receiving the upgrade result from the second target vehicle, the first device synchronizes the upgrade result to the OTA cloud in a timely manner.

[0192] From steps 701 to 705, it can be seen that after the second target vehicle performs the upgrade based on OTA, the upgrade result can be notified to the OTA cloud or the first device in a timely manner. Furthermore, the OTA cloud can timely synchronize the upgrade result of the second target vehicle to the first device, or the first device can timely synchronize the upgrade result of the second target vehicle to the OTA cloud, so that the upgrade information of the first device, the OTA cloud, and the second target vehicle can be synchronized. In this way, the first device can effectively and reliably manage the upgrade status of each vehicle in the vehicle fleet.

[0193] 8 is a schematic flowchart of another upgrade method based on OTA technology according to the present application. The method may include the following steps.

[0194] Step 801: A first device sends vehicle fleet information to the OTA cloud. In response, the OTA cloud receives vehicle fleet information from the first device.

[0195] Step 801 is referred to as step 301. Details are not described in this description.

[0196] Step 802: The OTA cloud determines a first target vehicle based on the vehicle fleet information from the first device and the first vehicle identifier.

[0197] Step 802 is an optional step. For details, refer to step 302. This description will not repeat the details.

[0198] Step 803: The OTA cloud sends the second upgrade task information to the first target vehicle. In response, the first target vehicle receives the second upgrade task information from the OTA cloud.

[0199] The second upgrade task information includes an upgrade package and first instruction information. The first instruction information instructs the first target vehicle to request the first device to confirm whether the first target vehicle is allowed to perform the upgrade. Please refer to the description of step 501 for the description of the first instruction information. This description will not repeat the details. For example, after receiving the upgrade package in the second upgrade task information, the first target vehicle may first store the upgrade package.

[0200] In a possible implementation, the second upgrade task information may include a "notifier" attribute, and the first instruction information may be set in a field of the "notifier" attribute.

[0201] As an example, if there are M first target vehicles, the OTA cloud may send the second upgrade task information to each of the M first target vehicles (M is a positive integer).

[0202] In addition, in an optional implementation, the second upgrade task information further includes upgrade task related information, for which reference is made to the above related description, and will not be described in detail again in this description.

[0203] From steps 801 to 803, it can be seen that the first device sends vehicle group information to the OTA cloud, so that the OTA cloud can obtain vehicle identifiers of vehicles belonging to the same vehicle group. Furthermore, the OTA cloud sends second upgrade task information including first instruction information to the first target vehicle, instructing the first target vehicle to request the first device to confirm whether the first target vehicle is authorized to perform the upgrade. In this way, the first device can determine whether the first target vehicle is authorized to perform the upgrade.

[0204] For example, a secure channel (also referred to as secure communication) may be pre-established between the OTA cloud and the first device before step 801, and / or a secure channel may be pre-established between the OTA cloud and a vehicle in the fleet (e.g., a first target vehicle) before step 803. For details, see the related description above. This description will not repeat the details.

[0205] Based on FIG. 8, examples of schematic flowcharts of two methods for determining, by a first device, a first target vehicle that is allowed to carry out an upgrade are given below.

[0206] Method A 9 is a schematic flow chart of a method for determining a first target vehicle that is permitted to perform an upgrade according to the present application by a first device. The method includes the following steps:

[0207] Step 901: The first target vehicle sends a third request message to the OTA cloud based on the second upgrade task information, and the OTA cloud correspondingly receives a third request message from the first target vehicle.

[0208] The third request message is used to request the first device to confirm whether the first target vehicle is authorized to perform the upgrade. By way of example, the third request message includes a vehicle identifier of the first target vehicle.

[0209] It should be noted that the third request message may be the same as or different from the second request message of step 603 .

[0210] In addition, in an optional implementation example, the third request message may further include upgrade task related information. For the upgrade task related information, please refer to the related description of step 401. This description will not repeat the details. It can be seen that the upgrade task related information carried in the third request message may be carried when the OTA cloud sends the second upgrade task information to the first target vehicle in step 803, or may be sent by the OTA cloud to the first target vehicle before step 901.

[0211] Step 902: The OTA cloud forwards a third request message to the first device. In response, the first device receives the third request message from the OTA cloud.

[0212] In a possible implementation, the OTA cloud transparently sends the third request message to the first device. In another possible implementation, the OTA cloud may process the third request message and then forward the processed third request message to the first device, but the function and indication of the second request message remain unchanged. For example, when the communication protocol between the OTA cloud and the first target vehicle and the communication protocol between the OTA cloud and the first device are different, the OTA cloud's processing of the third request message may be to perform protocol conversion. The present application does not limit a specific implementation of the OTA cloud forwarding the third request message.

[0213] Step 903: The first device determines the first target vehicle as the second target vehicle based on the third request message.

[0214] For step 903, please refer to the description of step 504. Details will not be described in this description.

[0215] In a possible implementation, the first device determines that the first target vehicle that sent the third request message is permitted to perform the upgrade. It can also be seen that the first device may directly determine the first target vehicle that sent the third request message as the second target vehicle.

[0216] In another possible implementation example, the first device may determine whether the first target vehicle that sent the third request message is permitted to perform the upgrade based on relevant information of the upgrade task carried in the third request message, and may determine the first target vehicle as the second target vehicle if the first target vehicle that sent the third request message is permitted to perform the upgrade.

[0217] Step 904: The first device sends a third response message to the OTA cloud. In response, the OTA cloud receives a third response message from the first device.

[0218] The third response message includes information indicating that the first target vehicle is authorized to perform the upgrade. As an example, the third response message includes a vehicle identifier of the second target vehicle. The second target vehicle is the first target vehicle that is authorized to perform the upgrade and determined by the first device. It should be noted that the information indicating that the first target vehicle is authorized to perform the upgrade may be any pre-agreed form of information. This application is not limited thereto.

[0219] Step 905: The OTA cloud forwards the third response message to the first target vehicle. In response, the first target vehicle receives the third response message from the OTA cloud.

[0220] In a possible implementation, the OTA cloud transparently sends the third response message to the first device. In another possible implementation, the OTA cloud may process the third response message and then forward the processed third response message to the first target vehicle, but the function and indication of the third response message remain unchanged. For example, when the communication protocol between the OTA cloud and the first target vehicle and the communication protocol between the OTA cloud and the first device are different, the OTA cloud may process the third response message to perform protocol conversion. The present application does not limit a specific implementation of the OTA cloud forwarding the third response message.

[0221] It can be seen in Figure 8 that the second upgrade task information sent by the OTA cloud to each first target vehicle already includes the upgrade package, so that after receiving the third response message, the second target vehicle can directly perform the upgrade based on the stored upgrade package in the second upgrade task information.

[0222] In steps 901 to 905, the first target vehicle can initiate the first device to confirm which first target vehicle is to be upgraded based on the first instruction information included in the second upgrade task information, without prompting or asking the driver for confirmation through the HMI. This is useful for reducing the burden on the driver. In addition, the first device determines which first target vehicle is to be upgraded. This is useful for improving the security of the management of vehicles in the vehicle fleet.

[0223] Method B 10 is a schematic flow chart of another method for determining a first target vehicle that is permitted to perform an upgrade according to the present application by a first device. The method includes the following steps:

[0224] Step 1001: The first target vehicle sends a third request message to the first device based on the second upgrade task information, and in response, the first device receives a third request message from the first target vehicle.

[0225] For step 1001, please refer to the description of step 901. Specifically, the "OTA cloud" in step 901 may be replaced with the "first device." Other contents will not be described repeatedly in this description.

[0226] Step 1002: The first device determines the first target vehicle as the second target vehicle based on the third request message.

[0227] For step 1002, please refer to the description of step 903. Details will not be described in this description.

[0228] Step 1003: The first device sends a third response message to the first target vehicle, and in response, the first target vehicle receives a third response message from the first device.

[0229] For step 1003, please refer to the description of step 904. Specifically, the "OTA cloud" in step 904 may be replaced with the "first target vehicle." Other contents will not be described repeatedly in this description.

[0230] In possible situations, method A can be applied in situations where a vehicle in the fleet cannot communicate directly with the first device, and method B can be applied in situations where a vehicle in the fleet can communicate directly with the first device.

[0231] For example, after completing the upgrade based on the upgrade package in the second upgrade task information, the first target vehicle may synchronize the upgrade result with the OTA cloud and the first device. For details, please refer to the description in FIG. 7. Specifically, the "second target vehicle" in FIG. 7 may be replaced with the "first target vehicle". This description will not repeat the details.

[0232] 11 is a schematic flowchart of another upgrade method based on OTA technology according to the present application. The method may include the following steps.

[0233] Step 1101: A first device sends vehicle fleet information to the OTA cloud. In response, the OTA cloud receives vehicle fleet information from the first device.

[0234] Step 1101 is referred to as step 301. Details are not described in this description.

[0235] Step 1102: The OTA cloud determines a first target vehicle based on the vehicle fleet information and the first vehicle identifier.

[0236] Step 1102 is an optional step. For details, see step 302. This description will not repeat the details.

[0237] Step 1103: The OTA cloud sends third upgrade task information to the first device, and the first device correspondingly receives the third upgrade task information from the OTA cloud.

[0238] The third upgrade task information includes a vehicle identifier and an upgrade package of the first target vehicle.

[0239] In order to prevent the upgrade package from being tampered with or damaged, after generating the upgrade package, the OTA cloud may first encrypt the upgrade package. It can also be seen that the upgrade package included in the third upgrade task information may be an encrypted upgrade package.

[0240] Below are two examples of encryption methods that the OTA cloud uses to encrypt upgrade packages:

[0241] Method 1: Symmetric key encryption. In a possible implementation, the OTA cloud encrypts the upgrade package using a symmetric key encryption method to obtain an encrypted upgrade package. For example, the OTA cloud may use the advanced encryption standard (AES) algorithm to encrypt the upgrade package.

[0242] In addition, in an optional implementation, the OTA cloud may hold the symmetric key encryption algorithm and inform the first device of the symmetric key encryption algorithm. Alternatively, the OTA cloud and the first device may agree on the symmetric key encryption algorithm in advance. This application is not limited thereto.

[0243] Method 2: Asymmetric key encryption In a possible implementation, the OTA cloud encrypts the upgrade package with an asymmetric key encryption method to obtain an encrypted upgrade package. The OTA cloud may hold a key pair (e.g., a public key and a private key). The OTA cloud encrypts the upgrade package using the private key and informs the first device of the public key. The public key is used by the first device to decrypt the encrypted upgrade package.

[0244] It should be noted that the two encryption methods provided above are only examples, and other possible encryption methods may be used instead, which is not a limitation of the present application.

[0245] In a possible implementation, the third upgrade task information may further include upgrade task related information. For the upgrade task related information, please refer to the above related description. This description will not be repeated in detail.

[0246] Step 1104: The first device determines at least one vehicle among the first target vehicles as a second target vehicle based on the third upgrade task information.

[0247] The third upgrade task information includes the first target vehicle identifier and an upgrade package.

[0248] In a possible embodiment, the first device determines all of the first target vehicles corresponding to the first target vehicle identifiers included in the third upgrade task information as second target vehicles that are permitted to complete the upgrade.

[0249] In another possible embodiment, the first device determines a portion of the first target vehicle corresponding to the first target vehicle identifier included in the third upgrade task information as a second target vehicle that is permitted to complete the upgrade.

[0250] In yet another possible implementation example, when the third upgrade task information further includes upgrade task related information, the first device may determine a second target vehicle that is allowed to complete the upgrade based on the upgrade task related information from the first target vehicle corresponding to the first target vehicle identifier included in the third upgrade task information.

[0251] It should be noted that the above provided possible implementations in which the first device determines the second target vehicle that is permitted to perform the upgrade from the first target vehicle are merely examples and are not limiting in this application.

[0252] Step 1105: The first device sends fourth upgrade task information to the second target vehicle. In response, the second target vehicle receives the fourth upgrade task information from the first device.

[0253] The fourth upgrade task information is related to the third upgrade task information. In one example, the fourth upgrade task information is the same as the third upgrade task information. In another example, the fourth upgrade task information is obtained based on the third upgrade task information. For example, the fourth upgrade task information includes information obtained after the first device performs a digital signature on the received upgrade package. The digital signature is performed on the upgrade package included in the third upgrade task information to further improve the security of the communication between the first device and the second target vehicle.

[0254] In a possible implementation, the fourth upgrade task information may further include an upgrade type, where the upgrade type is a confirmed upgrade.

[0255] For example, after completing the upgrade based on the fourth upgrade task information, the second target vehicle may synchronize the upgrade result with the first device and the OTA cloud. For details, please refer to the description in FIG. 7. This description will not repeat the details.

[0256] From step 1101-step 1105, it can be seen that the first device sends vehicle group information to the OTA cloud, so that the OTA cloud can obtain vehicle identifiers of vehicles belonging to the same vehicle group, and further sends third upgrade task information including the vehicle identifier of the first target vehicle to the first device. In this way, the first device can determine which first target vehicle is allowed to carry out the upgrade, which is useful for improving the security of the management of vehicles in the vehicle group.

[0257] The above embodiment is applicable to a scenario where the first device can directly communicate with vehicles in a fleet managed by the first device. Furthermore, alternatively, in the fleet, a fleet agent is deployed in at least one vehicle and an OTA agent is deployed in another vehicle to implement direct communication between the vehicles in the fleet and the first device. The vehicle on which the fleet agent is deployed may directly communicate with the first device. The vehicle on which the OTA agent is deployed may directly communicate with the vehicle on which the fleet agent is deployed. It can be seen that the second target vehicle on which the OTA agent is deployed can be understood as an OTA client, and the OTA cloud can be understood as an OTA service side. The fleet agent may include software that can interact with the first device and / or the OTA cloud and is deployed on the vehicle side. The OTA agent may include software that is to be upgraded based on OTA, for example, software that supports OTA upgrade and software that performs OTA upgrade.

[0258] 12 is a schematic flowchart of a method for sending fourth upgrade task information to a second target vehicle by a first device according to the present application. The method includes the following steps:

[0259] Step 1201: A first device sends fourth upgrade task information to a second target vehicle in which a fleet agent is deployed, and in response, the second target vehicle in which a fleet agent is deployed receives the fourth upgrade task information from the first device.

[0260] Step 1202: The second target vehicle in which the fleet agent is deployed verifies the signed upgrade package in the fourth upgrade task, and performs step 1203 if the verification is successful, or terminates the upgrade task if the verification is unsuccessful.

[0261] Step 1202 is an optional step.

[0262] For example, before sending the upgrade package to the second target vehicle in which the fleet agent is deployed, the first device may first perform a digital signature on the upgrade package. After receiving the digitally signed upgrade package, the second target vehicle in which the fleet agent is deployed may first verify the digital signature of the upgrade package, and then perform subsequent processing after the digital signature is successfully verified. This is useful for improving the security of the upgrade package and reducing the possibility of upgrade errors.

[0263] Step 1203: A second target vehicle having a fleet agent deployed thereon sends a fourth upgrade task information to a second target vehicle having an OTA agent deployed thereon.

[0264] Step 1204: The second target vehicle in which the OTA agent is deployed performs an upgrade based on the fourth upgrade task information.

[0265] The fourth upgrade task information further includes an upgrade type of the confirmed upgrade.

[0266] In a possible implementation, after determining that the upgrade type is a confirmed upgrade, the second target vehicle in which the OTA agent is deployed may directly perform the upgrade according to the OTA upgrade procedure without driver confirmation.

[0267] Step 1205: The second target vehicle on which the OTA agent is deployed sends the upgrade result to the second target vehicle on which the fleet agent is deployed. In response, the second target vehicle on which the fleet agent is deployed receives the upgrade result from the second target vehicle on which the OTA agent is deployed.

[0268] For the upgrade result of step 1205, please refer to the related description above, and the details will not be described again in this description.

[0269] In addition, the process of synchronizing the upgrade result between the second target vehicle where the fleet agent is deployed, the first device, and the OTA cloud is referred to the above description of FIG. 7. This description will not repeat the details.

[0270] For example, the first device establishing a secure channel with a vehicle in a fleet may be the first device establishing a secure channel with a second target vehicle in which a fleet agent is deployed. It can be seen that in order to implement the functions of the above embodiments, the communication device includes corresponding hardware structures and / or software modules for performing each function. In combination with the example modules and method steps described in the embodiments disclosed in this application, those skilled in the art will naturally easily conceive that the present application can be implemented by hardware or a combination of hardware and computer software. Whether the functions are performed by hardware or computer software depends on the specific application scenario and design constraints of the technical solution.

[0271] Based on the above content and the same concept, Fig. 13 and Fig. 14 are diagrams of possible structures of communication devices according to the present application. These communication devices may be configured to implement the functions of the first device, OTA cloud, or vehicle in the above method embodiments, and thus the beneficial effects of the above method embodiments can also be realized. In the present application, the communication device may be the server 101, the first device 102, the second device 103a, the second device 103b, or the second device 103c shown in Fig. 1, or may be the OTA cloud 201, the first device 202, the vehicle 203a, the vehicle 203b, or the vehicle 203c shown in Fig. 2, or may be a module (e.g., a chip) applied to the vehicle, the first device, or the OTA cloud.

[0272] As shown in Figure 13, the communication device 1300 includes a processing module 1301 and a transceiver module 1302. The communication device 1300 is configured to perform an embodiment of the method shown in Figure 3, 4, 5, 7, 8, 9, 10, 11 or 12.

[0273] When the communications apparatus 1300 is configured to perform the functions of the OTA cloud of the method embodiment shown in FIG. 3, under the control of the processing module 1301, the transceiver module 1302 is configured to receive vehicle fleet information from the first device, where the first device is configured to manage the vehicle fleet, where the vehicle fleet includes at least two vehicles, where the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet, send first upgrade task information to a second target vehicle, where the first upgrade task information includes an upgrade package, where the second target vehicle is at least one vehicle determined from the first target vehicle by the first device, where the first target vehicle is related to the vehicle fleet information and the first vehicle, where the first vehicle is a vehicle that requires an upgrade and has been obtained by the OTA cloud.

[0274] In a possible implementation, the transceiver module 1302 is further configured to send a first request message to the first device, the first request message including a vehicle identifier of the first target vehicle, and receive a first response message from the first device or the second target vehicle, the first response message including information about the second target vehicle. In a possible implementation, the first response message may directly include information about the second target vehicle. As an example, the first response message includes a vehicle identifier of the second target vehicle. In another possible implementation, the first response message may include third indication information. The third indication information points to information about the second target vehicle. The third indication information may be any pre-agreed form of information. This application is not limited thereto.

[0275] In a possible implementation, the first request message further includes relevant information of the upgrade task, and the relevant information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0276] In a possible implementation, the first upgrade task information further includes an upgrade type, and the upgrade type is a confirmed upgrade.

[0277] In a possible implementation, the transceiver module 1302 is further configured to send first instruction information to the first target vehicle, where the first instruction information indicates to the first target vehicle to request the first device to confirm whether the upgrade is allowed, and receive a second response message from the first device or the second target vehicle, where the second response message includes information regarding the second target vehicle.

[0278] In a possible implementation, the first indication information includes an address of the first device.

[0279] In a possible implementation, the first instruction information further includes relevant information of the upgrade task, and the relevant information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0280] In a possible implementation, the transceiver module 1302 is further configured to receive an upgrade result from the second target vehicle, the upgrade result including upgrade success, upgrade failure, rollback success, or rollback failure.

[0281] In a possible implementation, the transceiver module 1302 is further configured to send the upgrade result to the first device.

[0282] When the communication device 1300 is configured to perform the functions of the first device of the embodiment of the method illustrated in FIG. 3, the transceiver module 1302 is configured to send vehicle fleet information to the OTA cloud, the first device is configured to manage the vehicle fleet, the vehicle fleet includes at least two vehicles, the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet, receive a first request message from the OTA cloud, the first request message includes a vehicle identifier of a first target vehicle, the first target vehicle is a vehicle in the vehicle fleet that needs upgrading and is determined by the OTA cloud. The processing module 1301 is configured to determine at least one vehicle in the first target vehicles as a second target vehicle based on the first request message. The transceiver module 1302 is further configured to send a first response message to the OTA cloud, the first response message includes information about the second target vehicle.

[0283] In a possible implementation, the first request message further includes relevant information of the upgrade task, and the relevant information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0284] In a possible implementation, the transceiver module 1302 is further configured to receive an upgrade result from the second target vehicle, the upgrade result including upgrade success, upgrade failure, rollback success, or rollback failure.

[0285] In a possible implementation, the transceiver module 1302 is further used by the first device to send the upgrade result to the OTA cloud.

[0286] For a more detailed description of the processing module 1301 and the transceiver module 1302, please refer to the relevant description of the embodiment of the method shown in Figure 3. The details will not be described again in this description.

[0287] It should be understood that in an embodiment of the present application, the processing module 1301 may be implemented by a processor or a processor-related circuit component, and the transceiver module 1302 may be implemented by a transceiver or a transceiver-related circuit component.

[0288] When the communications apparatus 1300 is configured to perform the functions of the OTA cloud of the method embodiment shown in FIG. 8, under the control of the processing module 1301, the transceiver module 1302 is configured to: receive vehicle fleet information from the first device, where the first device is configured to manage the vehicle fleet, where the vehicle fleet includes at least two vehicles, where the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet, send second upgrade task information to the first target vehicle, where the second upgrade task information includes an upgrade package and first instruction information, where the first target vehicle is related to the vehicle fleet information and the first vehicle, where the first vehicle is a vehicle that requires an upgrade and has been obtained by the OTA cloud, and where the first instruction information indicates to the first target vehicle to request the first device to confirm whether the first target vehicle is authorized to perform the upgrade.

[0289] In a possible implementation, the first indication information includes an address of the first device.

[0290] In a possible implementation, the second upgrade task information further includes related information of the upgrade task, and the related information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0291] In a possible implementation, the transceiver module 1302 is further configured to receive an upgrade result from the second target vehicle, the upgrade result including upgrade success, upgrade failure, rollback success, or rollback failure.

[0292] In a possible implementation, the transceiver module 1302 is further configured to send the upgrade result to the first device.

[0293] When the communications apparatus 1300 is configured to perform the functions of the first device of the method embodiment shown in FIG. 8 , the transceiver module 1302 is configured to: send vehicle fleet information to the OTA cloud, the first device is configured to manage the vehicle fleet, the vehicle fleet includes at least two vehicles, the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet, receive a third request message from the first target vehicle, the third request message is used to request the first device to confirm whether the first target vehicle is authorized to perform the upgrade, the first target vehicle is related to the vehicle fleet information and the first vehicle, the first vehicle is a vehicle that requires an upgrade and has been acquired by the OTA cloud, send a third response message to the first target vehicle, the third response message includes information indicating that the first target vehicle is authorized to perform the upgrade.

[0294] In a possible implementation, the third request message further includes relevant information of the upgrade task, where the relevant information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0295] In a possible implementation, the transceiver module 1302 is further configured to receive an upgrade result from the first target vehicle, the upgrade result including upgrade success, upgrade failure, rollback success, or rollback failure.

[0296] In a possible implementation, the transceiver module 1302 is further configured to send the upgrade result to an OTA cloud.

[0297] For a more detailed description of the processing module 1301 and the transceiver module 1302, please refer to the relevant description of the embodiment of the method shown in Figure 8. The details will not be repeated in this description.

[0298] It should be understood that in an embodiment of the present application, the processing module 1301 may be implemented by a processor or a processor-related circuit component, and the transceiver module 1302 may be implemented by a transceiver or a transceiver-related circuit component.

[0299] When the communications apparatus 1300 is configured to perform the functions of the OTA cloud of the method embodiment shown in FIG. 11 , under the control of the processing module 1301, the transceiver module 1302 is configured to receive vehicle fleet information from the first device, the first device is configured to manage the vehicle fleet, the vehicle fleet includes at least two vehicles, the vehicle fleet information includes vehicle identifiers of vehicles belonging to the same vehicle fleet, send third upgrade task information to the first device, the third upgrade task information includes a vehicle identifier and an upgrade package of a first target vehicle, the first target vehicle is related to the vehicle fleet information and the first vehicle, the first vehicle is a vehicle that needs an upgrade and has been obtained by the OTA cloud, the upgrade package corresponds to a second target vehicle, and the second target vehicle is at least one vehicle determined by the first device from the first target vehicle.

[0300] In a possible implementation, the third upgrade task information further includes related information of the upgrade task, and the related information of the upgrade task includes at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

[0301] In a possible implementation, the transceiver module 1302 is further configured to receive an upgrade result from the second target vehicle, the upgrade result including upgrade success, upgrade failure, rollback success, or rollback failure.

[0302] In a possible implementation, the transceiver module 1302 is further configured to send the upgrade result to the first device.

[0303] When the communication device 1300 is configured to perform the functions of the first device of the embodiment of the method illustrated in FIG. 11, the transceiver module 1302 is configured to send vehicle fleet information to the OTA cloud, the first device is configured to manage the vehicle fleet, the vehicle fleet includes at least two vehicles, the vehicle fleet information includes vehicle identifiers of the vehicles belonging to the same vehicle fleet, and receive third upgrade task information from the OTA cloud, the third upgrade task information includes a first target vehicle identifier and an upgrade package. The processing module 1301 is configured to determine at least one vehicle among the first target vehicles as a second target vehicle based on the third upgrade task information. The transceiver module 1302 is further configured to send fourth upgrade task information to the second target vehicle, the fourth upgrade task information being related to the third upgrade task information.

[0304] In a possible implementation, the fourth upgrade task information includes information obtained after the first device performs a digital signature on the upgrade package.

[0305] In a possible implementation, the fourth upgrade task information further includes an upgrade type, and the upgrade type is a confirmed upgrade.

[0306] In a possible implementation, the transceiver module 1302 is further configured to receive an upgrade result from the second target vehicle, the upgrade result including upgrade success, upgrade failure, rollback success, or rollback failure.

[0307] In a possible implementation, the transceiver module 1302 is further configured to send the upgrade result to an OTA cloud.

[0308] For a more detailed description of the processing module 1301 and the transceiver module 1302, please refer to the relevant description of the embodiment of the method shown in Figure 11. The details will not be repeated in this description.

[0309] It should be understood that in an embodiment of the present application, the processing module 1301 may be implemented by a processor or a processor-related circuit component, and the transceiver module 1302 may be implemented by a transceiver or a transceiver-related circuit component.

[0310] It should be understood that the division of the communication device into parts is merely a logical functional division. In actual implementation, all or part of the parts may be incorporated into a physical entity or may be physically separated. In addition to the above, the parts of the communication device may be implemented in the form of software being called by a processor. As an example, the communication device includes a processor. The processor is connected to a memory. The memory stores instructions. The processor calls the instructions stored in the memory to perform any one of the above methods or to perform the functions of each part of the communication device. As an example, the processor is a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory is a memory of the communication device or a memory external to the communication device. The memory may include, but is not limited to, random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disk, removable hard disk, CD-ROM, or any other form of storage medium known in the art. By way of example, the storage medium may be coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may be a component of the processor. The processor and the storage medium may be located in the ASIC. Additionally, the ASIC may be located in the first device, the OTA cloud, or the vehicle. Of course, the processor and the storage medium may alternatively be present as discrete components in the first device, the OTA cloud, or the vehicle.

[0311] Alternatively, the components of the communication device may be implemented in the form of a hardware circuit, and the functions of some or all of the components may be implemented by designing the hardware circuit. The hardware circuit may be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the components are implemented by designing the logical relationships between the elements of the circuit. For another example, in another implementation, the hardware circuit may be implemented by a programmable logic device (PLD). An example is a field programmable gate array (FPGA). The field programmable gate array may include a number of logic gate circuits. A configuration file is used to configure the connection relationships between the logic gate circuits, and the functions of some or all of the components are implemented. All of the components of the communication device may be implemented in the form of a hardware circuit or in the form of a processor calling software, or some of the components may be implemented in the form of a processor calling software, and the remaining components may be implemented in the form of a hardware circuit.

[0312] In an embodiment of the present application, the processor is a circuit having a signal processing capability. In one implementation, the processor may be a circuit having a capability of loading and executing instructions, such as a CPU, a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor may implement a function using a logical relationship of a hardware circuit. The logical relationship of the hardware circuit may be fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an ASIC or a PLD, such as an FPGA. If the hardware circuit is reconfigurable, the process of the processor loading a configuration document and implementing the configuration of the hardware circuit may be understood as the process of the processor loading instructions and implementing the function of a part or all of the part. In addition to the above, the processor may alternatively be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, for example a neural network processing unit (NPU), a tensor processing unit (TPU) or a deep learning processing unit (DPU).

[0313] It will be appreciated that each portion of the communications device may be one or more processors (i.e., processing circuitry) configured to implement the above methods, and may be, for example, a CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0314] In addition to the above, all or some of the portions of the communication device may be integrated or implemented separately. In one implementation, the portions are integrated and implemented in the form of a system-on-a-chip (SOC). The SOC may include at least one processor configured to perform any one of the methods described above or to perform the functions of the portions of the device. The at least one processor may be of different types. By way of example, the at least one processor may include a CPU and an FPGA, a CPU and an artificial intelligence processor, or a CPU and a GPU.

[0315] Based on the above and the same concept, the present application further provides a communication device 1400, as shown in Fig. 14. The communication device 1400 may include a processor 1401 and a communication interface 1402. The processor 1401 and the communication interface 1402 are coupled to each other. It can be seen that the communication interface 1402 may be an interface circuit or an input / output interface. Apart from the above, the communication device 1400 may further include a memory 1403 configured to store instructions to be executed by the processor 1401, to store input data required by the processor 1401 to execute the instructions, and to store data generated after the processor 1401 executes the instructions.

[0316] When the communications device 1400 is configured to implement the methods shown in FIG. 3, FIG. 8 or FIG. 11, the processor 1401 is configured to perform the functions of the processing module 1301 and to perform the functions of the transceiver module 1302 through the communications interface 1402.

[0317] Based on the above and the same concept, the present application provides a chip. The chip may include a processor and an interface circuit. In addition, in an optional implementation, the chip may further include a memory. The processor is configured to execute a computer program or instructions stored in the memory to enable the chip to perform the method of any possible implementation of the method embodiments shown in Figure 3, Figure 4, Figure 5, Figure 7, Figure 8, Figure 9, Figure 10, Figure 11 or Figure 12.

[0318] All or part of the above embodiments may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded into a computer and executed, all or part of the procedures or functions of the embodiments of the present application are performed. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user terminal, or another programmable device. The computer programs or instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer programs or instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner. The computer-readable storage medium may be any available medium accessible by a computer, or may be a data storage device incorporating one or more available media, such as a server or a data center. The available media may be magnetic media, such as floppy disks, hard disk drives, or magnetic tapes; optical media, such as digital video discs (DVD); or semiconductor media, such as solid state drives (SSD).

[0319] In the embodiments of the present application, unless otherwise specified or there is a logical contradiction, the terms and / or descriptions between different embodiments are consistent and can refer to each other, and the technical features of different embodiments can be combined based on their internal logical relationships to form a new embodiment.

[0320] In this application, "at least one" means one or more, and "plurality" means two or more. The term "and / or" describes a relationship of association between related items and indicates that a triple relationship may exist. For example, A and / or B may indicate that only A is present, that both A and B are present, or that only B is present, where A and B may be singular or plural. "At least one of the immediately preceding items" or similar expressions refers to any combination of the items (including any combination of singular items or plural items). For example, at least one of a, b, or c may refer to 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. In the description of the body of this application, the character " / " in most cases indicates an "or" relationship between related items. In the written form of this application, the character " / " indicates a relationship of "division" between related items. In addition to the above, in the embodiments of this application, the term "for example" is used to indicate providing an example, illustration, or explanation. Any embodiment or design system described as an "example" in this application is not necessarily described as preferred or more advantageous than another embodiment or design system. In other words, this can be understood as the use of the word "example" is intended to present a concept in a particular way, and does not constitute a limitation on this application.

[0321] It is understood that various numbers in the present application are used only to differentiate for ease of description, and are not used to limit the scope of the embodiments of the present application. The sequence numbers of the above processes do not refer to the order of execution, and the order of execution of the processes is naturally determined based on the functions and internal logic of the processes. The terms "first", "second", etc. are used to distinguish similar ones, but do not necessarily indicate a specific order or sequence. In addition to the above, the terms "include" and "have" and variations thereof are intended to cover the inclusion of an exemplary enumeration, for example, to include a sequence of steps or portions. A method, system, product, or device is not necessarily limited to the steps or portions of the method, system, product, or device that are expressly recited, but may include other steps or portions that are not expressly recited or that are inherent in such a process, method, product, or device.

[0322] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Correspondingly, this specification and the accompanying drawings are merely illustrative examples of the solutions defined by the appended claims, and any or all modifications, variations, combinations and equivalents are to be considered as covering the scope of the present application.

[0323] It is apparent that those skilled in the art can make various modifications and variations to the present application without departing from the spirit and scope of the present invention. In this case, the present application intends to cover the modifications and variations of the embodiments of the present application as long as such modifications and variations are within the scope of the claims of the present application and their equivalent techniques. [Explanation of symbols]

[0324] 1 Vehicle Fleet Identifier 2 Vehicle Fleet Identifier 101 Server 102 First Device 103a Second Device 103b Second Device 103c Second Device 103d Second Device 201 OTA Cloud 202 First Device 203a Vehicle 203b Vehicle 203c Vehicle 203d vehicle 1300 Communication Equipment 1301 Processing Module 1302 Transceiver Module 1400 Communication Equipment 1401 Processor 1402 Communication Interface 1403 Memory

Claims

1. receiving vehicle fleet information from a first device, the first device being configured to manage a vehicle fleet, the vehicle fleet comprising at least two vehicles, the vehicle fleet information comprising vehicle identifiers of vehicles belonging to the same vehicle fleet; sending first upgrade task information to a second target vehicle, the first upgrade task information comprising an upgrade package, the second target vehicle being at least one vehicle determined by the first device from a first target vehicle, the first target vehicle being related to the vehicle fleet information and a first vehicle, the first vehicle being a vehicle that requires an upgrade and that has been acquired by an OTA cloud; An upgrade method based on over the air OTA technology, comprising:

2. The method comprises: sending a first request message to the first device, the first request message comprising a vehicle identifier of the first target vehicle; receiving a first response message from the first device or the second target vehicle, the first response message comprising information about the second target vehicle; The method of claim 1 further comprising:

3. 3. The method of claim 2, wherein the first request message further comprises related information of an upgrade task, the related information of the upgrade task comprising at least one of a time period required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

4. The method of claim 1 , wherein the first upgrade task information further comprises an upgrade type, the upgrade type being a confirmed upgrade.

5. The method comprises: sending a first instruction to the first target vehicle, the first instruction instructing the first target vehicle to request the first device to confirm whether an upgrade is permitted; receiving a second response message from the first device or the second target vehicle, the second response message comprising information regarding the second target vehicle; The method of claim 1 further comprising:

6. The method of claim 5 , wherein the first indication comprises an address of the first device.

7. The method of claim 5 or 6, wherein the first instruction information further comprises relevant information of an upgrade task, and the relevant information of the upgrade task comprises at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

8. The method comprises: receiving an upgrade result from the second target vehicle, the upgrade result comprising upgrade success, upgrade failure, rollback success, or rollback failure; The method of claim 1 , further comprising:

9. The method comprises: Sending the upgrade result to the first device. The method of claim 8 , comprising:

10. sending vehicle fleet information by a first device to an OTA cloud, the first device being configured to manage a vehicle fleet, the vehicle fleet comprising at least two vehicles, the vehicle fleet information comprising vehicle identifiers of vehicles belonging to the same vehicle fleet; receiving, by the first device, a first request message from the OTA cloud, the first request message comprising a vehicle identifier of a first target vehicle, the first target vehicle being a vehicle in the fleet that needs upgrading and that has been determined by the OTA cloud; determining, by the first device, at least one vehicle among the first target vehicles as a second target vehicle based on the first request message; sending a first response message by the first device to the OTA cloud, the first response message comprising information about the second target vehicle; An upgrade method based on over the air OTA technology, comprising:

11. 11. The method of claim 10, wherein the first request message further comprises related information of an upgrade task, the related information of the upgrade task comprising at least one of a time period required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

12. The method comprises: receiving an upgrade result from the second target vehicle by the first device, the upgrade result comprising upgrade success, upgrade failure, rollback success, or rollback failure; The method of claim 10 or 11, further comprising:

13. The method comprises: Sending the upgrade result to the OTA cloud by the first device. The method of claim 12 further comprising:

14. receiving vehicle fleet information from a first device, the first device being configured to manage a vehicle fleet, the vehicle fleet comprising at least two vehicles, the vehicle fleet information comprising vehicle identifiers of vehicles belonging to the same vehicle fleet; sending second upgrade task information to a first target vehicle, the second upgrade task information comprising an upgrade package and first instruction information, the first target vehicle being related to the vehicle fleet information and a first vehicle, the first vehicle being a vehicle that requires an upgrade and that has been acquired by an OTA cloud, the first instruction information instructing the first target vehicle to request the first device to confirm whether the first target vehicle is authorized to perform an upgrade; An upgrade method based on over the air OTA technology, comprising:

15. The method of claim 14 , wherein the first indication comprises an address of the first device.

16. 16. The method of claim 14 or 15, wherein the second update task information further comprises related information of an upgrade task, the related information of the upgrade task comprising at least one of a duration required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

17. sending vehicle fleet information by a first device to an OTA cloud, the first device being configured to manage a vehicle fleet, the vehicle fleet comprising at least two vehicles, the vehicle fleet information comprising vehicle identifiers of vehicles belonging to the same vehicle fleet; receiving, by the first device, a third request message from a first target vehicle, the third request message being used to request the first device to confirm whether the first target vehicle is authorized to perform an upgrade, the first target vehicle being related to the vehicle fleet information and a first vehicle, the first vehicle being a vehicle that needs an upgrade and has been acquired by the OTA cloud; sending a third response message by the first device to the first target vehicle, the third response message comprising information indicating that the first target vehicle is authorized to complete an upgrade; An upgrade method based on over the air OTA technology, comprising:

18. 20. The method of claim 17, wherein the third request message further comprises related information of an upgrade task, the related information of the upgrade task comprising at least one of a time period required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

19. receiving second upgrade task information from an over the air OTA cloud, the second upgrade task information comprising an upgrade package and first instruction information, the first instruction information instructing the first target vehicle to request the first device to confirm whether the first target vehicle is authorized to perform the upgrade, the first device being configured to manage a fleet of vehicles, the fleet of vehicles comprising at least two vehicles, vehicle fleet information comprising vehicle identifiers of vehicles belonging to the same fleet of vehicles, the first target vehicle being related to the vehicle fleet information and the first vehicle, the first vehicle being a vehicle that requires an upgrade and has been acquired by the OTA cloud; sending a third request message to the first device or the OTA cloud based on the second upgrade task information, the third request message being used to request the first device to confirm whether the first target vehicle is authorized to perform an upgrade; and receiving a third response message from the first device, the third response message comprising information indicating that the first target vehicle is authorized to complete an upgrade; An upgrade method based on over the air OTA technology, comprising:

20. 20. The method of claim 19, wherein the third request message further comprises related information of an upgrade task, the related information of the upgrade task comprising at least one of a time period required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

21. receiving vehicle fleet information from a first device, the first device being configured to manage a vehicle fleet, the vehicle fleet comprising at least two vehicles, the vehicle fleet information comprising vehicle identifiers of vehicles belonging to the same vehicle fleet; sending third upgrade task information to the first device, the third upgrade task information comprising a vehicle identifier and an upgrade package of a first target vehicle, the first target vehicle being related to the vehicle fleet information and a first vehicle, the first vehicle being a vehicle that requires an upgrade and that has been acquired by an OTA cloud, the upgrade package corresponding to a second target vehicle, the second target vehicle being at least one vehicle determined by the first device from the first target vehicle; An upgrade method based on over the air OTA technology, comprising:

22. 22. The method of claim 21, wherein the third update task information further comprises related information of an upgrade task, the related information of the upgrade task comprising at least one of a time period required for the upgrade, a purpose of the upgrade, or changes brought about by the upgrade.

23. sending vehicle fleet information by a first device to an OTA cloud, the first device being configured to manage a vehicle fleet, the vehicle fleet comprising at least two vehicles, the vehicle fleet information comprising vehicle identifiers of vehicles belonging to the same vehicle fleet; receiving, by the first device, third upgrade task information from the OTA cloud, the third upgrade task information comprising a first target vehicle identifier and an upgrade package; determining, by the first device, at least one vehicle among the first target vehicles as a second target vehicle based on the third upgrade task information; sending fourth upgrade task information by the first device to the second target vehicle, the fourth upgrade task information being related to the third upgrade task information; An upgrade method based on over the air OTA technology, comprising:

24. 24. The method of claim 23, wherein the fourth upgrade task information comprises information obtained after the first device performs a digital signature on the upgrade package.

25. The method of claim 23 or 24, wherein the fourth upgrade task information further comprises an upgrade type, the upgrade type being a confirmed upgrade.

26. A communications device comprising modules configured to perform a method according to any one of claims 1 to 25.

27. 26. A communications device comprising a processor, the processor connected to a memory, the memory configured to store a computer program, the processor configured to execute the computer program stored in the memory to enable the communications device to perform a method according to any one of claims 1 to 25.

28. A communication apparatus configured to perform the method according to any one of claims 1 to 9 and a first device configured to perform the method according to any one of claims 10 to 13, or A communication apparatus configured to perform the method according to any one of claims 14 to 16, a first device configured to perform the method according to claim 17 or 18, and a communication apparatus configured to perform the method according to claim 19 or 20, or A communication apparatus configured to perform the method according to claim 21 or 22 and a first device configured to perform the method according to any one of claims 23 to 25. Communication systems.

29. 26. A computer readable storage medium storing a computer program or instructions, which when executed by a communication device, enables the communication device to perform a method according to any one of claims 1 to 25.

30. A computer program product comprising a computer program or instructions, which when executed by a communication device, enables the communication device to perform a method according to any one of claims 1 to 25.

Images