Device upgrading method, vehicle-mounted host, device, computer storage medium and vehicle

Abstract

The application discloses a device upgrading method, a vehicle-mounted host, a device, a computer storage medium and a vehicle, and relates to the technical field of device upgrading. The device upgrading method comprises the following steps: determining a group of associated devices to be upgraded; sending an upgrading request message carrying a first identifier of the group of associated devices to be upgraded and an upgrading package; if at least one upgrading failure message carrying the first identifier is received, sending a rollback broadcast message carrying the first identifier, so as to instruct a device storing the first identifier and successfully upgraded to rollback to a version before upgrading; and if the number of the upgrading success messages carrying the first identifier received is the same as the number of the devices in the group of associated devices to be upgraded, it is determined that the upgrading is completed. According to the scheme, the power consumption of upgrading is greatly reduced.

Description

Technical Field

[0001] This invention relates to the field of vehicle technology, and more specifically to a device upgrade method, an on-board host, a device, a computer storage medium, and a vehicle. Background Technology

[0002] As vehicles become increasingly intelligent, the coupling between the various components within them also increases. Upgrading the entire vehicle (hereinafter referred to as the vehicle) requires an efficient and stable upgrade method to ensure both user experience and the stability of the vehicle's functions.

[0003] The current upgrade method for the whole vehicle is to upgrade each component in the vehicle in parallel. If the upgrade of a component fails, in order to meet compatibility requirements, other upgraded components need to be rolled back to the version before the upgrade. At this time, it is necessary to roll back each upgraded component one by one.

[0004] However, with vehicle upgrades becoming more frequent and the increasing number of high-power devices required for vehicle intelligence, the aforementioned vehicle upgrade methods result in excessively long upgrade times and excessive power consumption. Summary of the Invention

[0005] An invention was proposed to solve at least one of the above problems.

[0006] In a first aspect, the present invention provides a device upgrade method applied to a vehicle to be upgraded, the vehicle to be upgraded including an on-board host and at least two associated device groups, each of the associated device groups including at least one device, the on-board host being communicatively connected to each device, the method comprising:

[0007] Identify the at least two associated device groups that are to be upgraded;

[0008] Send an upgrade request message carrying the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded;

[0009] If at least one upgrade failure message carrying the first identifier is received, a rollback broadcast message carrying the first identifier is sent to instruct the device that stores the first identifier and has successfully upgraded to roll back to the version before the upgrade; if the number of received upgrade success messages carrying the first identifier is the same as the number of devices in the device group to be upgraded, then it is determined that the device group to be upgraded has completed the upgrade.

[0010] Optionally, before sending the upgrade request message carrying the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded, the method further includes:

[0011] Send an upgrade broadcast message carrying the first identifier, so that the device receiving the upgrade broadcast message can determine whether to maintain the working state or switch to the sleep state based on whether the first identifier is the same as the second identifier stored in its own memory.

[0012] Optionally, before sending the rollback broadcast message carrying the first identifier, the method further includes:

[0013] Send an upgrade termination message carrying the first identifier, so that the device receiving the upgrade termination message determines that the first identifier is the same as the second identifier stored in its own memory and that the upgrade has not been completed, and then stops the upgrade.

[0014] Secondly, the present invention also provides a device upgrade method applied to a vehicle to be upgraded, wherein the vehicle to be upgraded includes an on-board host and at least two associated device groups, each of the associated device groups including at least one device, the on-board host being communicatively connected to each device, and the method comprising:

[0015] Receive an upgrade request message sent by the vehicle host, which carries the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded;

[0016] After determining that the first identifier is the same as the second identifier stored within itself, it retrieves its own upgrade file from the upgrade package and performs the upgrade.

[0017] If the upgrade is confirmed to be successful, the upgrade success identifier is saved and an upgrade success message carrying the first identifier is sent to the vehicle host. If the upgrade is confirmed to be unsuccessful, the system is rolled back to the version before the upgrade and an upgrade failure message carrying the first identifier is sent to the vehicle host.

[0018] If a rollback broadcast message carrying the first identifier is received from the vehicle host, the system determines that the first identifier is the same as the second identifier stored in its own system, saves the upgrade success identifier, and then rolls back to the version before the upgrade.

[0019] Optionally, before receiving the upgrade request message sent by the vehicle host, which carries the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded, the method further includes:

[0020] The vehicle host receives an upgrade broadcast message carrying the first identifier, the upgrade broadcast message being sent by the vehicle host after determining the associated device group to be upgraded among the at least two associated device groups;

[0021] The system determines whether to maintain the working state or switch to a hibernation state based on whether the first identifier is the same as the second identifier stored in the system.

[0022] Specifically, the system determines whether to maintain the working state or switch to a hibernation state based on whether the first identifier is the same as the second identifier stored within itself. This includes:

[0023] Determine whether the first identifier is the same as the second identifier stored in itself;

[0024] If it is determined that the first identifier is the same as the second identifier stored in its own memory, the system remains in working state; if it is determined that the first identifier is different from the second identifier stored in its own memory, the system switches to hibernation state.

[0025] Optional, also includes:

[0026] If an upgrade termination message carrying the first identifier is received from the vehicle host, it is determined whether the first identifier is the same as the second identifier stored in the host.

[0027] If it is determined that the first identifier is the same as the second identifier stored within itself, then it is determined whether to complete the upgrade;

[0028] If it is determined that the upgrade has not been completed, then stop the upgrade.

[0029] Optionally, after rolling back to the version before the upgrade, the following may also be included:

[0030] Remove the upgrade success marker.

[0031] Thirdly, the present invention also provides an in-vehicle host, the in-vehicle host comprising:

[0032] Memory is used to store executable program instructions;

[0033] One or more processors are configured to execute the program instructions stored in the memory, causing the processors to perform the device upgrade method as described in the first aspect.

[0034] Fourthly, the present invention also provides a device, the device comprising:

[0035] Memory is used to store executable program instructions;

[0036] One or more processors are configured to execute the program instructions stored in the memory, causing the processors to perform the device upgrade method as described in the second aspect.

[0037] Fifthly, the present invention also provides a computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the device upgrade method described in the first method, or implements the device upgrade method described in the second aspect.

[0038] In a sixth aspect, the present invention also provides a vehicle comprising the vehicle-mounted host of the third aspect and the device of the fourth aspect described above.

[0039] The device upgrade method, vehicle host, device, computer storage medium, and vehicle provided by this invention allow the devices in the associated device group to be upgraded to report the upgrade results to the vehicle host after parallel upgrades. The vehicle host then determines whether the associated device group needs to be rolled back. If a rollback is required, the upgraded devices are rolled back in parallel. If no rollback is required, the associated device group is considered to have completed the upgrade. Since the devices in the device group can be upgraded and rolled back in parallel, the upgrade time is greatly reduced, thereby significantly reducing the power consumption of the upgrade. Furthermore, regardless of whether the upgrade is completed, the vehicle to be upgraded can be ensured to be in normal working condition, thus improving the stability of the vehicle to be upgraded. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 A schematic diagram of the architecture of the vehicle to be upgraded according to an embodiment of the present invention is shown;

[0042] Figure 2 A flowchart of a device upgrade method with an in-vehicle host as the execution subject is shown in one embodiment of the present invention;

[0043] Figure 3 A flowchart of a device upgrade method with a device as the execution subject is shown in one embodiment of the present invention. Detailed Implementation

[0044] To make the objectives, technical solutions, and advantages of the present invention more apparent, exemplary embodiments according to the present invention will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are merely a part of the embodiments of the present invention, and not all of the embodiments of the present invention. It should be understood that the present invention is not limited to the exemplary embodiments described herein. Based on the embodiments of the present invention described herein, all other embodiments obtained by those skilled in the art without inventive effort should fall within the protection scope of the present invention.

[0045] In the following description, numerous specific details are set forth in order to provide a more thorough understanding of the invention. However, it will be apparent to those skilled in the art that the invention can be practiced without one or more of these details. In other instances, certain technical features well-known in the art have not been described in order to avoid obscuring the invention.

[0046] It should be understood that the invention can be embodied in various forms and should not be construed as being limited to the embodiments set forth herein. Rather, providing these embodiments will make the disclosure thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0047] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the invention. When used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the terms “comprising” and / or “including,” when used in this specification, identify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups. When used herein, the term “and / or” includes any and all combinations of the associated listed items.

[0048] To fully understand this invention, a detailed structure will be presented in the following description to illustrate the technical solution proposed by this invention. Optional embodiments of the invention are described in detail below; however, in addition to these detailed descriptions, the invention may have other embodiments.

[0049] The following detailed description of some embodiments of the present invention is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0050] To address the aforementioned technical problems, embodiments of the present invention provide a device upgrade method, applicable to, for example... Figure 1The vehicle to be upgraded, as shown, includes an onboard host and at least two associated device groups, with the onboard host communicating with each device. The onboard host can be a control node on the vehicle, such as a gateway, capable of controlling multiple devices for upgrades. Generally, the various devices in a vehicle do not operate independently. For example, to implement automatic parking, devices such as domain controllers, cameras, and ultrasonic radars need to work together. These devices can form an associated device group. All devices in the vehicle can be divided into multiple associated device groups according to actual needs. To distinguish these associated device groups, each group can be assigned an identifier. The onboard host stores the identifiers of each associated device group, and each device stores the identifier of its respective associated device group. Each device may, but is not limited to, store the identifier of its associated device group in diagnostic services. The communication connection between the onboard host and each device can, but is not limited to, be implemented through a Controller Area Network (CAN) bus or Ethernet. After the vehicle enters the upgrade process, the onboard host may, but is not limited to, use Over-the-Air (OTA) technology to download the upgrade package from the server. The following describes the device upgrade methods with the onboard host and each device as the execution entities.

[0051] First, we introduce the device upgrade method with the vehicle-mounted host as the main execution entity, such as... Figure 2 As shown, the specific steps include:

[0052] S21: Determine the associated device group to be upgraded from the at least two associated device groups.

[0053] Since the vehicle to be upgraded will include multiple associated device groups, the one that needs to be upgraded can be defined as the associated device group to be upgraded. The number of associated device groups to be upgraded can be one or more. Regardless of the number, the upgrade method is the same. The following explanation uses one associated device group to be upgraded as an example.

[0054] S22: Send an upgrade request message carrying the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded.

[0055] The identifier of the associated device group to be upgraded can be defined as a first identifier. The vehicle host can send an upgrade request message carrying the first identifier and the upgrade package of the associated device group to be upgraded. Since each device stores the identifier of its associated device group, this identifier can be defined as a second identifier. After receiving the upgrade request message, each device first determines whether the first identifier is the same as its stored second identifier. If they are the same, it obtains its own upgrade file from the upgrade package and performs the upgrade. If they are different, no upgrade is required. Subsequently, if the upgrade is successful, it saves the upgrade success identifier and sends an upgrade success message carrying the first identifier to the vehicle host to notify the vehicle host that the upgrade was successful. If the upgrade fails, it rolls back to the version before the upgrade and sends an upgrade failure message carrying the first identifier to the vehicle host to notify the vehicle host that the upgrade failed. This ensures that the devices in the associated device group to be upgraded are compatible and further ensures that the associated device group to be upgraded can work normally.

[0056] The upgrade success flag is used to indicate that the upgrade has been successful. It can be stored in the diagnostic service, but is not limited to being 1. For example, the upgrade success flag can be 1, but is not limited to being 1. Storing the upgrade success flag means setting it to 1 in the diagnostic service.

[0057] After the above steps, the vehicle host can upgrade each component of the related component group in parallel. Compared with upgrading components one by one, this can greatly reduce the upgrade time and thus reduce power consumption.

[0058] S23: If at least one upgrade failure message carrying the first identifier is received, a rollback broadcast message carrying the first identifier is sent to instruct the device that stores the first identifier and has successfully upgraded to roll back to the version before the upgrade; if the number of upgrade success messages carrying the first identifier received is the same as the number of devices in the device group to be upgraded, it is determined that the device group to be upgraded has completed the upgrade.

[0059] Devices in the group to be upgraded may fail to upgrade or all may upgrade successfully. If at least one upgrade failure message carrying a first identifier is received, it means that at least one device in the group to be upgraded has failed to upgrade. In this case, a rollback broadcast message carrying the first identifier is sent so that the device receiving the rollback broadcast message can determine that the first identifier is the same as its stored second identifier and, after confirming that the upgrade success identifier is saved, roll back to the version before the upgrade. Due to compatibility issues between devices in the group to be upgraded, in order to ensure the functional stability of the group, when one device in the group fails to upgrade, all devices in the group that have already been upgraded successfully, i.e., those that have saved the upgrade success identifier, need to roll back to the version before the upgrade. If the number of upgrade success messages carrying the first identifier received is the same as the number of devices in the group to be upgraded, it means that all devices in the group to be upgraded have been upgraded successfully, and the upgrade of the group to be upgraded is confirmed to be complete.

[0060] Specifically, for associated device groups A and B, rollback broadcast messages can be, but are not limited to, using rollback broadcast signals 0x34A, 0x34B, etc.

[0061] In this scheme, after the devices in the related device group to be upgraded are upgraded in parallel, they will report the upgrade results to the vehicle host. The vehicle host will then determine whether the related device group to be upgraded needs to be rolled back. If it is determined that a rollback is needed, the upgraded devices will be rolled back in parallel. If it is determined that a rollback is not needed, the related device group to be upgraded will be considered to have completed the upgrade. Since the devices in the device group to be upgraded can be upgraded and rolled back in parallel, the upgrade time is greatly reduced, thereby greatly reducing the power consumption of the upgrade. Moreover, regardless of whether the upgrade is completed or not, it can ensure that the vehicle to be upgraded is in normal working condition, thereby improving the stability of the vehicle to be upgraded.

[0062] Optionally, before sending the upgrade request message carrying the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group in step S22 above, the method further includes:

[0063] Send an upgrade broadcast message carrying a first identifier, so that the device receiving the upgrade broadcast message can determine whether to maintain the working state or switch to the sleep state based on whether the first identifier is the same as the second identifier stored in its own memory.

[0064] Since not all associated device groups require upgrades, to further reduce power consumption, devices that do not require upgrades can be instructed to enter a sleep state. Specifically, before sending an upgrade request message carrying the first identifier of the associated device group to be upgraded and the upgrade package for that group, an upgrade broadcast message carrying the first identifier is sent. Devices receiving the upgrade broadcast message determine whether to remain in operation or switch to a sleep state based on whether the first identifier matches their stored second identifier. For example, for associated device groups A and B, the upgrade broadcast message can, but is not limited to, use upgrade broadcast signals such as 0x12A and 0x12B.

[0065] Optionally, before sending the rollback broadcast message carrying the first identifier in S23 above, the process further includes:

[0066] Send an upgrade termination message carrying a first identifier, so that the device receiving the upgrade termination message determines that the first identifier is the same as the second identifier stored in its own memory and that the upgrade has not been completed, and then stops the upgrade.

[0067] Since at least one device in the group of devices to be upgraded has failed to upgrade, it is necessary to roll back all devices in the group to the version before the upgrade. Therefore, it is meaningless to continue upgrading for devices in the group that have not completed the upgrade. The vehicle host can immediately terminate the upgrade of all devices in the group. Specifically, it can send an upgrade termination message carrying a first identifier. Once the device that receives the upgrade termination message determines that the first identifier is the same as the second identifier stored in its own memory and that the upgrade has not been completed, it stops the upgrade.

[0068] By promptly terminating unnecessary upgrades, upgrade time can be further saved and power consumption waste reduced.

[0069] The above provides a device upgrade method using the vehicle-mounted head unit as the execution entity. The following describes device upgrade methods using various individual components as the execution entity, such as... Figure 3 As shown, the specific steps include:

[0070] S31: Receive an upgrade request message sent by the vehicle host, which carries the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded.

[0071] S32: After determining that the first identifier is the same as the second identifier stored in itself, retrieve its own upgrade file from the upgrade package and perform the upgrade.

[0072] Once it is determined that the first identifier and the second identifier are the same, it indicates that the associated device group needs to be upgraded, and the upgrade file can be obtained from the upgrade package to perform the upgrade.

[0073] S33: If the upgrade is confirmed to be successful, save the upgrade success flag and send an upgrade success message carrying the first flag to the vehicle host. If the upgrade is confirmed to be unsuccessful, roll back to the version before the upgrade and send an upgrade failure message carrying the first flag to the vehicle host.

[0074] When a device is upgraded, the upgrade may succeed or fail. If the upgrade is successful, the upgrade success flag is saved and an upgrade success message carrying the first flag is sent to the vehicle host. If the upgrade fails, the device is rolled back to the previous version and an upgrade failure message carrying the first flag is sent to the vehicle host. Alternatively, the device can roll back to the previous version and send an upgrade failure message carrying the first flag after a set number of retries that still fail. This ensures that the devices in the device group to be upgraded are compatible and further ensures that the device group to be upgraded can work normally.

[0075] If the vehicle host receives at least one upgrade failure message carrying a first identifier, it means that at least one device in the associated device group to be upgraded has failed to upgrade. Then it sends a rollback broadcast message carrying the first identifier. If the number of upgrade success messages carrying the first identifier received is the same as the number of devices in the associated device group to be upgraded, it means that all devices in the associated device group to be upgraded have been upgraded successfully. Then it is determined that the associated device group to be upgraded has completed the upgrade.

[0076] S34: If a rollback broadcast message carrying a first identifier is received from the vehicle host, the first identifier is determined to be the same as the second identifier stored in the host and the upgrade success identifier is saved before the rollback to the version before the upgrade.

[0077] If a rollback broadcast message carrying a first identifier is received from the vehicle's onboard unit, it is necessary to first determine whether the first identifier is the same as the second identifier stored in the unit. If they are the same, it indicates that the device belongs to the same associated device group. Then, it is further determined whether to save the upgrade success identifier. If saved, it means the upgrade was successful, and the unit is rolled back to the previous version. If not saved, it means the upgrade was unsuccessful, and no rollback is needed. This ensures that all devices in the associated device group to be upgraded are compatible, further ensuring that the associated device group to be upgraded can function normally.

[0078] It should be noted that each device can adopt a dual-partition upgrade strategy. Specifically, the device's storage space is divided into at least two partitions: one partition for the previous version and the other for the upgrade version. If the upgrade fails, the previous version can be retrieved directly for rollback, which greatly enhances the security of device upgrades. If some devices cannot be upgraded with dual partitions, an alternative approach is to back up the upgrade package during the implementation process. Specifically, the previous version's upgrade package is placed in the device's storage area. When the device needs to rollback, it can use the previous version's upgrade package to flush the partition and complete the rollback.

[0079] In this solution, after the devices in the device group to be upgraded are upgraded, they will report the upgrade results to the vehicle host. The vehicle host will then determine whether the device group to be upgraded needs to be rolled back. If it is determined that a rollback is needed, the upgraded devices will be rolled back in parallel. If it is determined that a rollback is not needed, the device group to be upgraded is considered to have completed the upgrade. Since the devices in the device group to be upgraded can be upgraded and rolled back in parallel, the upgrade time is greatly reduced, thereby significantly reducing the power consumption of the upgrade. Furthermore, regardless of whether the upgrade is completed or not, it can ensure that the vehicle to be upgraded is in normal working condition, thereby improving the stability of the vehicle to be upgraded.

[0080] Optionally, before receiving the upgrade request message carrying the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group sent by the vehicle host in S31 above, the method further includes:

[0081] The vehicle host receives an upgrade broadcast message carrying a first identifier, which is sent by the vehicle host after determining the at least two associated device groups to be upgraded.

[0082] The system determines whether to maintain the working state or switch to a hibernation state based on whether the first identifier is the same as the second identifier stored in the system.

[0083] Since not all associated device groups need to be upgraded, in order to further reduce power consumption, the vehicle host can notify the upgraded devices to remain in working state, while the non-upgraded devices enter a sleep state. Specifically, before sending the upgrade request message carrying the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded, an upgrade broadcast message carrying the first identifier is sent. If the device receives the upgrade broadcast message, it can determine whether to remain in working state or switch to sleep state based on whether the first identifier is the same as the second identifier stored in its own memory.

[0084] Specifically, the determination of whether to maintain the working state or switch to a hibernation state based on whether the first identifier is the same as the second identifier stored within itself includes:

[0085] Determine whether the first identifier is the same as the second identifier stored within itself;

[0086] If the first identifier is determined to be the same as the second identifier stored in its own memory, the system remains in working state; if the first identifier is determined to be different from the second identifier stored in its own memory, the system switches to hibernation state.

[0087] If the first identifier matches the second identifier stored in its own memory, it indicates that the device belongs to the same associated device group and requires an upgrade; in this case, it continues to operate. If the first identifier differs from the second identifier stored in its own memory, it indicates that the device does not belong to the same associated device group and does not require an upgrade; in this case, it can switch to a hibernation state. Based on this, by sending upgrade broadcast messages to each associated device group, devices in these groups are selectively upgraded, while those in groups that do not require upgrades enter a hibernation state. This is particularly useful for high-power associated device groups, allowing them to selectively hibernate, thereby significantly reducing power consumption during the upgrade process.

[0088] Optionally, the above methods also include:

[0089] If an upgrade termination message carrying the first identifier is received from the vehicle host, it is determined whether the first identifier is the same as the second identifier stored in the host.

[0090] If it is determined that the first identifier is the same as the second identifier stored within itself, then it is determined whether to complete the upgrade;

[0091] If it is determined that the upgrade has not been completed, then stop the upgrade.

[0092] If at least one device in the group of devices to be upgraded fails to upgrade, all devices in the group need to be rolled back to the version before the upgrade. Therefore, it is meaningless to continue upgrading devices in the group that have not yet completed the upgrade. The vehicle host can immediately terminate the upgrade of all devices in the group. Specifically, it can send an upgrade termination message carrying a first identifier. Once the device receiving the upgrade termination message determines that the first identifier is the same as the second identifier stored in its own memory and that the upgrade has not yet been completed, it stops the upgrade. Since the upgrade has not been completed, the device will still be in the version before the upgrade. Therefore, the upgrade can be stopped without rollback.

[0093] Optionally, after rolling back to the version before the upgrade in S34 above, it also includes:

[0094] Remove the upgrade success indicator.

[0095] Since the system has been rolled back to the version before the upgrade, the upgrade success indicator can be removed to facilitate future upgrades.

[0096] It should be noted that if the upgrade success flag is set to 1 in the diagnostic service, then deleting the upgrade success flag means deleting 1 in the diagnostic service. You can change 1 to 0, but it is not limited to that. In other words, anything other than 1 will work.

[0097] Based on the same inventive concept, the present invention also provides an in-vehicle host, the device comprising:

[0098] Memory is used to store executable program instructions;

[0099] One or more processors are configured to execute the program instructions stored in the memory, causing the processors to perform actions such as Figure 2 The device upgrade method shown.

[0100] Based on the same inventive concept, the present invention also provides a device, the device comprising:

[0101] Memory is used to store executable program instructions;

[0102] One or more processors are configured to execute the program instructions stored in the memory, causing the processors to perform actions such as Figure 3 The device upgrade method shown.

[0103] In addition, embodiments of the present invention also provide a computer storage medium on which a computer program is stored. One or more computer program instructions may be stored on the computer-readable storage medium, and a processor may execute the program instructions stored in the storage device to implement the functions (implemented by the processor) in the embodiments of the present invention described herein, and / or other desired functions, such as performing corresponding steps of the device upgrade method according to embodiments of the present invention. Various application programs and various data may also be stored in the computer-readable storage medium, such as various data used and / or generated by the application programs.

[0104] For example, the computer storage medium may include a memory card for a smartphone, a storage component for a tablet computer, a hard disk for a personal computer, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a portable compact disc read-only memory (CD-ROM), a USB memory, or any combination of the above storage media. The computer-readable storage medium may be any combination of one or more computer-readable storage media.

[0105] Although exemplary embodiments have been described herein with reference to the accompanying drawings, it should be understood that the above exemplary embodiments are merely illustrative and are not intended to limit the scope of the invention. Various changes and modifications can be made therein by those skilled in the art without departing from the scope and spirit of the invention. All such changes and modifications are intended to be included within the scope of the invention as claimed in the appended claims.

[0106] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0107] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed.

[0108] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0109] Similarly, it should be understood that, in order to streamline the invention and aid in understanding one or more of the various aspects of the invention, features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof in the description of exemplary embodiments of the invention. However, this approach should not be construed as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as reflected in the corresponding claims, its inventive point lies in solving the corresponding technical problem with fewer features than all of those in a single disclosed embodiment. Therefore, the claims following the detailed description are hereby expressly incorporated into that detailed description, wherein each claim itself is a separate embodiment of the invention.

[0110] Those skilled in the art will understand that, apart from the mutual exclusion of features, all features disclosed in this specification (including the accompanying claims, abstract, and drawings) and all processes or elements of any method or apparatus so disclosed can be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) may be replaced by an alternative feature serving the same, equivalent, or similar purpose.

[0111] Furthermore, those skilled in the art will understand that although some embodiments described herein include certain features but not others included in other embodiments, combinations of features from different embodiments are intended to be within the scope of the invention and form different embodiments. For example, in the claims, any of the claimed embodiments can be used in any combination.

[0112] The various component embodiments of the present invention can be implemented in hardware, or as software modules running on one or more processors, or a combination thereof. Those skilled in the art will understand that microprocessors or digital signal processors (DSPs) can be used in practice to implement some or all of the functions of some modules according to embodiments of the present invention. The present invention can also be implemented as an apparatus program (e.g., a computer program and computer program product) for performing some or all of the methods described herein. Such programs implementing the present invention can be stored on a computer-readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0113] It should be noted that the above embodiments are illustrative of the invention and not restrictive, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names.

Claims

1. A device upgrade method, applied to a vehicle to be upgraded, the vehicle to be upgraded including an on-board host and at least two associated device groups, each of the associated device groups including at least one device, the on-board host being communicatively connected to each device, characterized in that, The method includes: Identify the at least two associated device groups that are to be upgraded; Send an upgrade request message carrying the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded; If at least one upgrade failure message carrying the first identifier is received, a rollback broadcast message carrying the first identifier is sent to instruct the devices that have stored the first identifier and successfully upgraded to roll back to the version before the upgrade in parallel; if the number of upgrade success messages carrying the first identifier received is the same as the number of devices in the device group to be upgraded, then it is determined that the device group to be upgraded has completed the upgrade. Before sending the rollback broadcast message carrying the first identifier, the method further includes: Send an upgrade termination message carrying the first identifier, so that the device receiving the upgrade termination message determines that the first identifier is the same as the second identifier stored in its own memory and that the upgrade has not been completed, and then stops the upgrade.

2. The method as described in claim 1, characterized in that, Before sending the upgrade request message carrying the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded, the method further includes: Send an upgrade broadcast message carrying the first identifier, so that the device receiving the upgrade broadcast message can determine whether to maintain the working state or switch to the sleep state based on whether the first identifier is the same as the second identifier stored in its own memory.

3. A device upgrade method, applied to a vehicle to be upgraded, wherein the vehicle to be upgraded includes an on-board host and at least two associated device groups, each associated device group includes at least one device, the devices in the associated device groups to be upgraded are capable of parallel rollback, and the on-board host is communicatively connected to each device, characterized in that, The method includes: Receive an upgrade request message sent by the vehicle host, which carries the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded; After determining that the first identifier is the same as the second identifier stored within itself, it retrieves its own upgrade file from the upgrade package and performs the upgrade. If the upgrade is confirmed to be successful, the upgrade success identifier is saved and an upgrade success message carrying the first identifier is sent to the vehicle host. If the upgrade is confirmed to be unsuccessful, the system is rolled back to the version before the upgrade and an upgrade failure message carrying the first identifier is sent to the vehicle host. If a rollback broadcast message carrying the first identifier is received from the vehicle host, the system determines that the first identifier is the same as the second identifier stored in its own memory, saves the upgrade success identifier, and then rolls back to the version before the upgrade. The rollback broadcast message is sent by the vehicle host after receiving at least one upgrade failure message carrying the first identifier. Also includes: If an upgrade termination message carrying the first identifier is received from the vehicle host, it is determined whether the first identifier is the same as the second identifier stored in the vehicle host; the upgrade termination message is sent by the vehicle host before sending the rollback broadcast message carrying the first identifier. If it is determined that the first identifier is the same as the second identifier stored within itself, then it is determined whether to complete the upgrade; If it is determined that the upgrade has not been completed, then stop the upgrade.

4. The method as described in claim 3, characterized in that, Before receiving the upgrade request message sent by the vehicle host, which carries the first identifier of the associated device group to be upgraded and the upgrade package of the associated device group to be upgraded, the method further includes: The vehicle host receives an upgrade broadcast message carrying the first identifier, the upgrade broadcast message being sent by the vehicle host after determining the associated device group to be upgraded among the at least two associated device groups; The system determines whether to maintain the working state or switch to a hibernation state based on whether the first identifier is the same as the second identifier stored in the system.

5. The method as described in claim 4, characterized in that, The system determines whether to maintain the working state or switch to a hibernation state based on whether the first identifier is the same as the second identifier stored within itself. Specifically, this includes: Determine whether the first identifier is the same as the second identifier stored in itself; If it is determined that the first identifier is the same as the second identifier stored in its own memory, the system remains in working state; if it is determined that the first identifier is different from the second identifier stored in its own memory, the system switches to hibernation state.

6. The method according to any one of claims 3-5, characterized in that, After rolling back to the version before the upgrade, it also includes: Remove the upgrade success marker.

7. A vehicle-mounted host, characterized in that, The vehicle-mounted host includes: Memory is used to store executable program instructions; One or more processors are configured to execute the program instructions stored in the memory, causing the processors to perform the device upgrade method as described in any one of claims 1-2.

8. A device used in a vehicle, characterized in that, The device includes: Memory is used to store executable program instructions; One or more processors are configured to execute the program instructions stored in the memory, causing the processors to perform the device upgrade method as described in any one of claims 3-6.

9. A computer storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the device upgrade method as described in any one of claims 1-2, or implements the device upgrade method as described in any one of claims 3-6.

10. A vehicle, characterized in that, It includes the vehicle-mounted host as described in claim 7 and the device as described in claim 8.

Images