Multi-firmware OTA upgrading method and device, server and storage medium

Abstract

Embodiments of the present application relate to the technical field of firmware upgrade, and disclose a multi-firmware OTA upgrade method and device, a server and a storage medium. The upgrade method comprises receiving a plurality of firmware to be upgraded; in response to a firmware upgrade request of a device end, issuing a firmware package matched with the firmware upgrade request to the device end; wherein the firmware package is generated according to a dependency relationship among the plurality of firmware to be upgraded and a dependency relationship between the plurality of firmware and an application program. Embodiments of the present application greatly reduce the management difficulty in multi-firmware upgrade with complex dependency relationships.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of Internet of Things, and in particular to a multi-firmware OTA upgrading method and device, a server and a storage medium. BACKGROUND

[0002] In recent years, the digital key technology applied to vehicles has developed rapidly. The embedded system of the digital key often contains multiple modules, and the digital key function is completed by multiple firmwares cooperating with each other, and the protocols of the multiple firmwares depend on each other, so that when a single firmware in the system is upgraded, the specific version and support situation (i.e. dependency relationship) of each firmware need to be considered, and there is also a dependency relationship between different firmware versions and the digital key application program, so the management difficulty of each version of firmware and their mutual support situation is increasing with the continuous upgrading of the system. SUMMARY

[0003] Embodiments of the present application provide a multi-firmware OTA upgrading method and device, a server and a storage medium to solve the problem of difficult management of multi-firmware upgrading with complex dependency relationships.

[0004] In a first aspect, embodiments of the present application provide a multi-firmware OTA upgrading method applied to a server, the method comprising:

[0005] receiving multiple firmwares to be upgraded;

[0006] in response to a firmware upgrading request of a device end, issuing a firmware package matched with the firmware upgrading request to the device end;

[0007] wherein the firmware package is generated according to the dependency relationship between the multiple firmwares to be upgraded and the dependency relationship between the multiple firmwares and an application program.

[0008] In addition, the firmware to be upgraded carries information of firmwares and an application program having a dependency relationship with the firmware upgrading; and the step of issuing a firmware package matched with the firmware upgrading request to the device end in response to the firmware upgrading request of the device end comprises:

[0009] finding multiple firmwares having a dependency relationship according to the information of firmwares and an application program having a dependency relationship with the firmware package carried by the firmware to generate a firmware package, generating unique identification information of the firmware package, and storing the firmware package and its unique identification information in a bound manner.

[0010] In addition, the step of issuing a firmware package matched with the firmware upgrading request to the device end in response to the firmware upgrading request of the device end comprises:

[0011] Receiving information of a plurality of firmwares which need to be merged into the firmware package to generate the firmware package, and generating unique identification information of the firmware package, and storing the firmware package and the unique identification information thereof.

[0012] In addition, the unique identification information of the firmware package comprises application version information supported by the firmware package and device type information of a device to be upgraded by using the firmware package; the upgrade request carries the application version information and the device type of the device end of the firmware to be upgraded;

[0013] The firmware package matched with the firmware upgrade request of the device end is downloaded to the device end in response to the firmware upgrade request.

[0014] The firmware package matched with the firmware upgrade request of the device end is downloaded to the device end in response to the firmware upgrade request.

[0015] In addition, the firmware to be upgraded carries information of firmware and application which have a dependency relationship with the firmware upgrade; the upgrade request carries the application version information and the device type of the device end of the firmware to be upgraded.

[0016] The firmware package matched with the firmware upgrade request of the device end is downloaded to the device end in response to the firmware upgrade request.

[0017] When receiving the firmware upgrade request of the device end, a plurality of firmwares which have a mutual dependency relationship are found according to the information of firmware and application which have a dependency relationship with the firmware package upgrade carried by the firmware, the application version information carried by the upgrade request and the device type of the device end of the firmware to be upgraded, to generate a firmware package corresponding to the upgrade request, and the firmware package is downloaded to the device end.

[0018] In addition, each firmware is a signature encrypted data packet and is stored in a binding manner with identification information of the firmware; wherein the identification information of the firmware comprises a firmware version number, and the firmware version number is increased successively.

[0019] In a second aspect, an embodiment of the present application provides a multi-firmware OTA upgrade method, applied to a device end, comprising:

[0020] Receiving a firmware package; the firmware package comprises at least two firmwares, and dependency between the at least two firmwares and between the at least two firmwares and an application satisfies a current upgrade requirement;

[0021] Performing firmware upgrade according to the firmware package.

[0022] In a third aspect, an embodiment of the present application provides a multi-firmware OTA upgrade device, configured in a service end, the device comprising:

[0023] receive a plurality of firmwares to be upgraded;

[0024] a delivery module configured to, in response to a firmware upgrade request from the device end, deliver a firmware package matching the firmware upgrade request to the device end;

[0025] The firmware package is generated according to a dependency relationship among the plurality of firmwares to be upgraded and a dependency relationship between the plurality of firmwares and an application program.

[0026] In a fourth aspect, an embodiment of the present application provides a server end, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the multi-firmware OTA upgrade method according to the first aspect when executing the program.

[0027] In a fifth aspect, an embodiment of the present application provides a computer readable storage medium having a computer program stored thereon, and the program is executable on a processor to implement the multi-firmware OTA upgrade method according to the first aspect or the second aspect.

[0028] The technical solution provided by the embodiment of the present application has at least the following positive effects compared with the prior art:

[0029] The multi-firmware OTA upgrade method provided by the embodiment of the present application receives a plurality of firmwares to be upgraded, generates a firmware package according to a dependency relationship among the plurality of firmwares to be upgraded and a dependency relationship between the plurality of firmwares and an application program, and in response to a firmware upgrade request from the device end, delivers a firmware package matching the firmware upgrade request to the device end to realize the cooperative upgrade of the plurality of firmwares (i.e., simultaneously satisfying the dependency relationship among the plurality of firmwares and the dependency relationship between each firmware and the application program), thereby avoiding the compatibility problems of the existing single firmware upgrade mode which needs to repeatedly consider the device type, firmware version, etc., and enabling one-time upgrade in a system unit, so as to greatly simplify the management difficulty of the multi-firmware upgrade with complex dependency relationship. BRIEF DESCRIPTION OF DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without any creative effort based on these drawings.

[0031] Figure 1 A dependency relationship diagram between the plurality of firmwares and the application program provided by the embodiment of the present application;

[0032] Figure 2 A flowchart of the multi-firmware OTA upgrade method provided by the first embodiment of the present application;

[0033] Figure 3 A flowchart of the multi-firmware OTA upgrade method provided for the second embodiment of the present application is shown in FIG. 2.

[0034] Figure 4 A flowchart of the multi-firmware OTA upgrade method provided for the third embodiment of the present application is shown in FIG. 3.

[0035] Figure 5 A flowchart of the multi-firmware OTA upgrade method provided for the fourth embodiment of the present application is shown in FIG. 4.

[0036] Figure 6 A flowchart of the multi-firmware OTA upgrade method provided for the fifth embodiment of the present application is shown in FIG. 5.

[0037] Figure 7 A structure diagram of the multi-firmware OTA upgrade device provided for the sixth embodiment of the present application is shown in FIG. 6.

[0038] Figure 8 A structure diagram of the server provided for the seventh embodiment of the present application is shown in FIG. 7. DETAILED DESCRIPTION

[0039] The present application will be further described below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only intended for explaining the present application but not limiting the present application. In addition, it should be noted that only the parts related to the present application are shown in the drawings for the convenience of description.

[0040] The multi-firmware OTA upgrade method provided by the embodiments of the present application is suitable for firmware upgrade of a system containing multiple firmwares and having dependency relationship between the multiple firmwares and between the multiple firmwares and application programs. Figure 1 The dependency relationship between the multiple firmwares and between the multiple firmwares and application programs is shown in FIG. 1. That is, there is inherent dependency relationship between different versions of different firmwares, and there is specific dependency relationship between different versions of different firmwares and different versions of different APPs. Exemplarily, the multiple firmwares are firmware A-C respectively, and the versions of the firmwares are 1-N, for example. The version of the application program (APP) is 2.0, for example, and the versions between 2.0 and 3.0, and the versions above 3.0. The dotted lines with arrows in the figure show the dependency relationship between different firmwares and different versions of the firmwares, and the solid lines with arrows show the dependency relationship between different firmwares and different versions of the firmwares and different versions of different APPs.

[0041] Taking a digital key application as an example, a digital key system often contains multiple modules, and multiple firmwares need to cooperate with each other to complete the digital key function, such as using the digital key to lock / unlock, etc. The multiple firmwares contained in the digital key system include Bluetooth firmware, RSP (Remote Service Provider, RSP for short) firmware and other related firmwares, etc. Among them, the digital key RSP uses an asymmetric cryptographic algorithm to realize the bidirectional authentication of the smart device and the vehicle. It can be understood that the number of firmwares involved in the digital key application is often more than 2. The digital key APP can also be updated continuously according to the changes in business requirements, thereby continuously generating new digital key APP versions.

[0042] The embodiment of the application combines multiple firmwares with a dependency relationship and supporting the same APP version into a firmware package, and downloads the matched firmware package to the device end during upgrading, thereby greatly simplifying the management problem of multi-firmware upgrading with complex dependency relationships.

[0043] Embodiment one

[0044] Figure 2 The flowchart of the multi-firmware OTA upgrading method provided by the embodiment one of the application, the embodiment is applied to a server end, which can be various servers supporting OTA technology, thereby realizing the OTA upgrading of multiple firmwares. The embodiment does not limit this. The method can be executed by an upgrading device provided by the embodiment of the application, the device can be realized in the form of software and / or hardware, and is configured in the server end. The embodiment of the application specifically includes the following steps:

[0045] Step 201, receiving multiple firmwares to be upgraded.

[0046] Exemplarily, each received firmware is a signed and encrypted data packet and is stored in binding with the identification information of the firmware. The identification information of the firmware can include a firmware version number, and the firmware version number is increased successively.

[0047] Specifically, the firmware can be made by a firmware developer and then uploaded to the server end. When uploading the firmware, the type of the firmware to be uploaded can be selected first, that is, the firmware is a Bluetooth firmware or other type of firmware. Then the firmware to be uploaded is verified, and after the verification succeeds, the basic information of the firmware, such as the file header length, the firmware version number and the hardware code, is extracted as the identification information of the firmware, and then the firmware is signed and encrypted to generate an encrypted firmware data packet to be upgraded, and then uploaded to the server end.

[0048] The firmware version number is increased each time the firmware is updated, thereby facilitating the uniqueness of the firmware version.

[0049] Step 202, in response to the firmware upgrade request of the device end, the firmware package matched with the firmware upgrade request is sent to the device end.

[0050] The firmware package is generated according to the dependency relationship among the plurality of firmware to be upgraded and the dependency relationship between the plurality of firmware and the application. In other words, the firmware package contains all the firmware to be upgraded involved in this upgrade process, that is, there is a dependency relationship among these firmware, for example, firmware A is upgraded to the latest version, and firmware B must also be upgraded to the latest version at the same time, and these firmware can support the same version of APP, for example, the minimum version of the APP supported by all firmware is taken as the APP version supported by the firmware. The generated firmware package has unique identification information. The server can send the firmware package directly to the device end, such as the car machine end, or can send it to the car machine end through a smart phone, etc., which is not limited here.

[0051] Compared with the prior art, the multi-firmware OTA upgrade method of the embodiment of the application generates a firmware package according to the dependency relationship among the plurality of firmware to be upgraded and the dependency relationship between the plurality of firmware and the application, and sends the firmware package matched with the firmware upgrade request to the device end to realize the cooperative upgrade of the plurality of firmware, thereby greatly simplifying the management difficulty of multi-firmware upgrade with complex dependency relationship.

[0052] Embodiment two

[0053] Figure 3 The flowchart of the multi-firmware OTA upgrade method provided for this embodiment two is shown. As shown in the figure, Figure 3 The embodiment of the application specifically includes the following steps:

[0054] Step 201, receiving a plurality of firmware to be upgraded.

[0055] The firmware to be upgraded carries the information of the firmware and the application having a dependency relationship with the firmware upgrade. For example, when the latest version of firmware A has a dependency relationship with the latest version of firmware B, the firmware data of firmware A and / or firmware B can carry the information of the firmware dependent thereon. And firmware A and / or firmware B can carry the information of the dependent APP. Thus, according to the information of the dependent firmware and APP carried by the firmware, the information of all the firmware to be upgraded and the version of the APP supported by these firmware can be determined. The information of the firmware and the application having a dependency relationship with the firmware upgrade carried by the firmware to be upgraded can be added by the firmware developer, so that the management of the dependency relationship among the firmware and between the firmware and the APP can be automatically realized by adding the dependency information in the firmware, greatly reducing the management difficulty of multi-firmware upgrade.

[0056] Step 2021a, according to the information of the firmware carrying the firmware having a dependency relationship with the firmware upgrade and the application, find the mutually dependent multiple firmware to generate a firmware package, and generate unique identification information of the firmware package, and store the firmware package and its unique identification information.

[0057] The mutually dependent multiple firmware is all firmware that needs to be upgraded synchronously when the corresponding upgrade is completed. As described above, the information of all firmware can be obtained through the dependency information carried by the firmware, and the multiple clean firmware is obtained after the carried dependency information is removed, and the multiple clean firmware is taken as a firmware package, for example, the multiple firmware can be made into a compressed package.

[0058] It can be understood that the firmware package can have unique identification information, so as to ensure the uniqueness of the firmware package. The unique identification information of the firmware package can include application program version information supported by the firmware package and device type information of the device upgraded by the firmware package. Through the device type, the firmware upgrade of different devices can be distinguished, and through the APP version information, the firmware package matched with the APP version can be easily found. Specifically, the version number of the firmware package can adopt a 3-segment code, such as 1.1.1, and the version number of the firmware package increases with the increase of the upgrade times, for example, when the current firmware package version number is 1.1.1, it can only be upgraded to 1.1.2, but cannot be reduced to 1.1.0.

[0059] Step 2022a, according to the version information of the application and the device type, find the matched firmware package and deliver it to the device end.

[0060] The upgrade request carries the version information of the application and the device type of the device end of the firmware to be upgraded, so as to match the corresponding firmware package according to the APP version information and the device type of the device end of the firmware to be upgraded, and deliver the firmware package to the device end. It can be understood that the firmware package can be encrypted twice to further improve the data security. At the same time, the firmware package can be delivered to the device end in slices, which is not limited here.

[0061] Compared with the prior art, the multi-firmware OTA upgrade method of the embodiment of the application generates a firmware package according to the dependency relationship between the multiple firmware to be upgraded and the dependency relationship between the multiple firmware and the application, and delivers the firmware package matched with the firmware upgrade request to the device end to realize the cooperative upgrade of the multiple firmware, thereby greatly simplifying the management difficulty of the multi-firmware upgrade with complex dependency relationship.

[0062] Embodiment three

[0063] Figure 4 The flowchart of the multi-firmware OTA upgrade method provided for this embodiment three is shown. As shown in Figure 4 the embodiment of the application specifically includes the following steps:

[0064] Step 201, receiving a plurality of firmware to be upgraded.

[0065] Unlike the second embodiment, the firmware received in step 201 in this embodiment can not carry its dependency information with other firmware and APPs.

[0066] Step 2021b, receiving information of a plurality of firmware to be merged into a firmware package to generate the firmware package, and generating unique identification information of the firmware package, and storing the firmware package and its unique identification information.

[0067] The information of the plurality of firmware to be merged into the firmware package can be uploaded by the firmware developer alone. That is, after each firmware to be upgraded is uploaded to the server, the information of the plurality of firmware to be put into the same firmware package can be collected by inputting through the terminal and sent to the server.

[0068] Specifically, the name and version of the firmware package can be defined and ensured to be unique. The firmware type to be upgraded and the supported hardware type can be selected. The firmware type is, for example, Bluetooth and RSP firmware, and the hardware type is, for example, vehicle. All firmware versions supported by the system can be queried, and each basic firmware version required is selected, and according to different firmware types, the firmware version to be optionally upgraded is selected. For example, when making the first edition of the firmware package, all firmware can be selected to put the initial version of all firmware into the firmware package, and when upgrading, only the firmware to be upgraded can be selected to put it into the firmware package. All APP versions that have been put on the shelf can be queried, and the lowest APP version supported by all firmware in the firmware package is selected, and then the dependency information between the firmware and the dependency information between the firmware and the APP are sent to the server. It can be understood that in some examples, the firmware package can also be generated directly on the terminal and sent to the server. It is worth mentioning that after the firmware package is generated, the uniqueness of the firmware package can be further verified, such as by comparing the version of each sub-firmware in the firmware package to ensure that the version of each sub-firmware is upgraded each time, and on this basis, when the versions of the sub-firmware in the firmware package are different, the uniqueness of the firmware package can be determined.

[0069] Step 2022b, finding a matched firmware package according to the version information of the application program and the device type, and downloading to the device end.

[0070] This step can be the same as step 2022a of the second embodiment, which will not be described here.

[0071] Compared with the prior art, the multi-firmware OTA upgrade method of the embodiment of the application greatly simplifies the management difficulty of multi-firmware upgrade with complex dependency relationship by generating a firmware package according to the dependency relationship among the multiple firmwares to be upgraded and the dependency relationship between the multiple firmwares and the application program, and delivering the firmware package matching the firmware upgrade request to the device end to realize the cooperative upgrade of the multiple firmwares.

[0072] Embodiment Four

[0073] Figure 5 A flowchart of the multi-firmware OTA upgrade method provided for the fourth embodiment. The fourth embodiment is substantially the same as the second embodiment, and the main difference is that in the second embodiment, the firmware package is generated and stored in the service end, and the stored firmware package is delivered to the device end when the device end needs to be upgraded, while in the fourth embodiment, the firmware package is generated in real time and delivered to the device end when the upgrade request from the device end is received, and the service end does not need to store the firmware package. As shown in Figure 5 The embodiment of the application specifically comprises the following steps:

[0074] Step 201, receiving multiple firmwares to be upgraded.

[0075] The firmware to be upgraded carries the information of the firmware and the application program having a dependency relationship with the firmware upgrade.

[0076] Step 2021c, when the firmware upgrade request from the device end is received, the multiple firmwares having a mutual dependency are found according to the information of the firmware and the application program having a dependency relationship with the firmware upgrade carried by the firmware, the version information of the application program carried by the upgrade request, and the device type of the device end of the firmware to be upgraded, so as to generate the firmware package corresponding to the upgrade request.

[0077] Specifically, the firmware matching the APP version can be screened according to the version information of the application program carried by the upgrade request, the firmware type can be determined according to the device type of the device end of the firmware to be upgraded carried by the upgrade request, and all the firmwares and their firmware versions needing to be upgraded synchronously can be further determined according to the information of the firmware and the application program having a dependency relationship with the firmware upgrade carried by the firmware, so as to generate the firmware package corresponding to the upgrade request in real time. It should be noted that the unique identification information of the firmware package can also be generated, which is not limited here. By generating the firmware package in real time, the storage space of the service end can be saved.

[0078] Step 2022c, and delivering to the device end.

[0079] Compared with the prior art, the multi-firmware OTA upgrading method of the embodiment of the application greatly simplifies the management difficulty of multi-firmware upgrading with complex dependency relationship by generating a firmware package according to the dependency relationship among the multiple firmwares to be upgraded and the dependency relationship between the multiple firmwares and the application program, and delivering the firmware package matching the firmware upgrading request to the device end to realize the cooperative upgrading of the multiple firmwares.

[0080] Embodiment five

[0081] Figure 6 A flowchart of the multi-firmware OTA upgrading method provided by the embodiment five of the application is shown in the figure. The embodiment is applied to a device end containing multiple firmwares. The device end can be a vehicle in a digital key system or other embedded system, which is not specifically limited here. The method can be executed by an upgrading apparatus provided by the embodiment of the application. The apparatus can be realized in the form of software and / or hardware and is configured in the device end.

[0082] The embodiment of the application specifically includes the following steps:

[0083] Step 601, receiving a firmware package.

[0084] The firmware package includes at least two firmwares, and the dependency among the at least two firmwares and between the at least two firmwares and the application program meets the upgrading requirement this time.

[0085] Step 602, performing firmware upgrading according to the firmware package.

[0086] Specifically, the device end can parse each firmware in the firmware package and respectively utilize each firmware to perform upgrading.

[0087] Compared with the prior art, the multi-firmware OTA upgrading method of the embodiment of the application greatly simplifies the management difficulty of multi-firmware upgrading with complex dependency relationship by generating a firmware package according to the dependency relationship among the multiple firmwares to be upgraded and the dependency relationship between the multiple firmwares and the application program, and delivering the firmware package matching the firmware upgrading request to the device end to realize the cooperative upgrading of the multiple firmwares.

[0088] Embodiment six

[0089] The embodiment of the application provides a multi-firmware OTA upgrading apparatus. As shown in the figure, the upgrading apparatus 700 includes a receiving module 701 and a delivering module 702. Figure 7

[0090] The receiving module 701 is used for receiving multiple firmwares to be upgraded.

[0091] ​The issuing module 702 is configured to issue a firmware package matched with the firmware upgrade request to the device end in response to the firmware upgrade request of the device end. The firmware package is generated according to the dependency relationship among the plurality of firmwares to be upgraded and the dependency relationship between the plurality of firmwares and the application program.

[0092] Optionally, the firmware to be upgraded carries information of the firmware and the application program having a dependency relationship with the firmware upgrade; accordingly, the issuing module 702 can comprise a generating submodule (not shown in the figure) configured to find the plurality of firmwares having a mutual dependency according to the information of the firmware and the application program having a dependency relationship with the firmware upgrade carried by the firmware, to generate the firmware package, and to generate unique identification information of the firmware package, and to store the firmware package and the unique identification information thereof in a bound manner.

[0093] As an alternative, the generating submodule can be configured to receive information of the plurality of firmwares to be merged into the firmware package to generate the firmware package, and to generate unique identification information of the firmware package, and to store the firmware package and the unique identification information thereof in a bound manner.

[0094] Optionally, the unique identification information of the firmware package comprises application program version information supported by the firmware package and device type information of the device to be upgraded by using the firmware package; the upgrade request carries the version information of the application program and the device type of the device end of the firmware to be upgraded; accordingly, the issuing module 702 can further comprise a matching submodule configured to find a matched firmware package according to the version information of the application program and the device type, and to issue to the device end.

[0095] As an alternative, the firmware to be upgraded carries information of the firmware and the application program having a dependency relationship with the firmware upgrade; the upgrade request carries the version information of the application program and the device type of the device end of the firmware to be upgraded; accordingly, the issuing module 702 can be further configured to, when receiving the firmware upgrade request of the device end, find the plurality of firmwares having a mutual dependency according to the information of the firmware and the application program having a dependency relationship with the firmware upgrade carried by the firmware, the version information of the application program carried by the upgrade request, and the device type of the device end of the firmware to be upgraded, to generate the firmware package corresponding to the upgrade request, and to issue to the device end.

[0096] Optionally, each of the firmwares is a signature encrypted data package and is stored in a bound manner with identification information of the firmware; the identification information of the firmware comprises a firmware version number, and the firmware version number is increased successively.

[0097] Compared with the prior art, the multi-firmware OTA upgrading method of the embodiment of the application greatly simplifies the management difficulty of multi-firmware upgrading with complex dependency relationship by generating a firmware package according to the dependency relationship among the plurality of firmware to be upgraded and the dependency relationship between the plurality of firmware and the application program, and delivering the firmware package matched with the firmware upgrading request to the device end to realize the cooperative upgrading of the plurality of firmware.

[0098] The upgrading device provided by the embodiment can execute the upgrading method provided by any one of embodiments one to four, has the function modules and beneficial effects corresponding to the execution method. The implementation principle and technical effects of the embodiment are similar to those of the above method embodiments, which will not be described here.

[0099] Embodiment seven

[0100] Figure 8 The structural schematic diagram of the server provided by the embodiment seven of the application. The server 80 includes a memory 81, a processor 82, and a computer program stored on the memory 81 and executable on the processor 82, and the processor 82 implements the technical solution of the server side in any one of the above method embodiments when executing the program.

[0101] Embodiment eight

[0102] The embodiment eight of the application provides a computer readable storage medium, which stores a computer program, and the computer program is used for executing the technical solution of the server side in any one of the method embodiments when executed by a computer processor.

[0103] Through the above description of the embodiments, those skilled in the art can clearly understand that the application can be realized by means of software and necessary general hardware, and of course can also be realized by hardware, but in many cases the former is a better embodiment. Based on such understanding, the technical solutions of the application can be embodied in the form of a software product, and the computer software product can be stored in a computer readable storage medium, such as a floppy disk, a read-only memory (ROM), a random access memory (RAM), a FLASH, a hard disk or an optical disk, etc., including a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a grid device, etc.) to execute the methods described in various embodiments of the application.

[0104] It is worth noting that in the above embodiment of the updating device, each unit and module included is only divided according to functional logic, but is not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy mutual distinction, and do not limit the protection scope of the application.

[0105] Note that the above merely describes preferred embodiments of the present application and the principles of the technology applied. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and that various obvious changes, modifications and substitutions can be made thereto without departing from the scope of the present application. Therefore, although the present application has been described in detail by way of the above embodiments, the present application is not limited to the above embodiments but includes all possible embodiments that can be derived from the above embodiments without departing from the concept of the present application, and the scope of the present application is defined by the appended claims.

Claims

1. A multi-firmware OTA upgrade method, applied to a server, characterized in that, The method includes: Receive multiple firmware updates to be performed; In response to a firmware upgrade request from the device, a firmware package matching the firmware upgrade request is sent to the device. The firmware package is generated based on the dependencies between the multiple firmware files to be upgraded and the dependencies between the multiple firmware files and the application. The firmware to be upgraded carries information about firmware and applications that are dependent on this firmware upgrade; the upgrade request carries application version information and the device type of the device side of the firmware to be upgraded. The step of responding to a firmware upgrade request from the device by sending a firmware package matching the firmware upgrade request to the device includes: When a firmware upgrade request is received from the device, the firmware package corresponding to the upgrade request is generated based on the firmware and application information that are dependent on the firmware upgrade, the version information of the application carried in the upgrade request, and the device type of the device to be upgraded. The firmware to be upgraded carries information about firmware and applications that depend on this firmware upgrade; the step of sending a firmware package matching the firmware upgrade request to the device in response to the device includes: Based on the information of the firmware and applications that are dependent on this firmware upgrade carried by the firmware, multiple interdependent firmwares are found to generate a firmware package, and a unique identifier information for the firmware package is generated. The firmware package is then bound and stored with its unique identifier information.

2. The multi-firmware OTA upgrade method according to claim 1, characterized in that, The unique identification information of the firmware package includes: application version information supported by the firmware package and device type information of the device using the firmware package for upgrading; the upgrade request carries application version information and device type of the device to be upgraded. The step of responding to a firmware upgrade request from the device by sending a firmware package matching the firmware upgrade request to the device also includes: The system locates a matching firmware package based on the application's version information and device type, and then sends it to the device.

3. The multi-firmware OTA upgrade method according to claim 1, characterized in that, Each firmware is a signed encrypted data packet and is bound to the firmware's identification information and stored therein; wherein, the firmware identification information includes a firmware version number, and the firmware version number increases sequentially.

4. A multi-firmware OTA upgrade device, configured on a server, characterized in that, The device includes: The receiving module is used to receive multiple firmware files to be upgraded; The delivery module is used to respond to the firmware upgrade request from the device and deliver the firmware package that matches the firmware upgrade request to the device. The firmware package is generated based on the dependencies between the multiple firmware files to be upgraded and the dependencies between the multiple firmware files and the application. The firmware to be upgraded carries information about firmware and applications that are dependent on this firmware upgrade; the upgrade request carries application version information and the device type of the device side of the firmware to be upgraded. The delivery module is used to, when receiving a firmware upgrade request from the device, find multiple interdependent firmwares based on the firmware and application information carried by the firmware that are dependent on this firmware upgrade, the version information of the application carried by the upgrade request, and the device type of the device to be upgraded, in order to generate a firmware package corresponding to this upgrade request and deliver it to the device. The firmware to be upgraded carries information about firmware and applications that are dependent on this firmware upgrade; accordingly, the distribution module includes: a generation submodule, which is used to find multiple mutually dependent firmware based on the information about firmware and applications that are dependent on this firmware upgrade carried by the firmware to generate a firmware package, and generate unique identification information for the firmware package, and bind and store the firmware package with its unique identification information.

5. A server-side component, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the multi-firmware OTA upgrade method as described in any one of claims 1-3.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements the multi-firmware OTA upgrade method as described in any one of claims 1-3.

Images