CN115794204A - Firmware management method, system, equipment and storage medium - Google Patents
Firmware management method, system, equipment and storage medium Download PDFInfo
- Publication number
- CN115794204A CN115794204A CN202211411653.XA CN202211411653A CN115794204A CN 115794204 A CN115794204 A CN 115794204A CN 202211411653 A CN202211411653 A CN 202211411653A CN 115794204 A CN115794204 A CN 115794204A
- Authority
- CN
- China
- Prior art keywords
- firmware
- version
- newly developed
- difference log
- identification field
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 47
- 238000012360 testing method Methods 0.000 claims abstract description 73
- 230000004044 response Effects 0.000 claims abstract description 33
- 238000004519 manufacturing process Methods 0.000 claims description 51
- 238000000034 method Methods 0.000 claims description 20
- 238000011156 evaluation Methods 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 8
- 238000012790 confirmation Methods 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 8
- 238000011161 development Methods 0.000 description 7
- 230000018109 developmental process Effects 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 3
- 230000014509 gene expression Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
Images
Abstract
The invention discloses a firmware management method, which comprises the following steps: in response to receiving newly developed firmware, obtaining an identification field in the newly developed firmware; establishing an incidence relation with the existing standard version firmware or customized version firmware according to the version information in the identification field; comparing the content of the newly developed firmware with the content of the firmware establishing the association relationship and generating a difference log; testing the difference log; and responding to the test passing, and upgrading the firmware of the corresponding version according to the difference log. The invention also discloses a system, a computer device and a readable storage medium. The scheme provided by the invention realizes the unified management of the standard version firmware and the customized version firmware of a single model product by establishing the association relationship between the standard version firmware and the customized version firmware developed in the life cycle of a server product.
Description
Technical Field
The present invention relates to the field of firmware, and in particular, to a firmware management method, system, device, and storage medium.
Background
Common server product Firmware (Firmware) includes BIOS, BMC, RMC, etc., and these Firmware will develop a standard version based on a server product, and when there is a customization demand for a client, perform customization development based on the standard version to generate a customized version. The development of the customized versions of the firmware of the server product is usually to perform individual management aiming at a certain order of a target client, the customization requirements of the server are many, the customized versions of the firmware are more and more along with the introduction of new clients, the independent management mode of the firmware of the customized versions can cause management confusion along with the increase of the firmware of the customized versions, the difficulty is caused to the upgrade and maintenance of the firmware versions at the later stage, the unified upgrade management based on the standard versions cannot be realized, and the quick positioning and problem processing of the use condition of the customized versions cannot be realized.
At present, the customized version of the server firmware is independently managed based on the standard version development and production customized version and is delivered to a client for use. However, the server customized version is managed independently and is delivered to a target project or a client for independent management and use after the development is completed, so that the management of the firmware customized version is disordered, the unified upgrade management based on a standard version cannot be realized, the quick positioning and problem handling of the service condition of the customized version cannot be realized, and troubles are caused to project groups, production manufacturing and field maintenance which are responsible for server products.
Disclosure of Invention
In view of this, in order to overcome at least one aspect of the above problems, an embodiment of the present invention provides a firmware management method, including the following steps:
in response to receiving newly developed firmware, obtaining an identification field in the newly developed firmware;
establishing an incidence relation with the existing standard version firmware or customized version firmware according to the version information in the identification field;
comparing the content of the newly developed firmware with the content of the firmware establishing the association relationship and generating a difference log;
testing the difference log;
and responding to the test passing, and upgrading the firmware of the corresponding version according to the difference log.
In some embodiments, establishing an association relationship with existing standard version firmware or custom version firmware according to the version information in the identification field further includes:
acquiring a product model, a firmware type and a version number in the identification field;
and associating the newly developed firmware to the existing standard version firmware or the custom version firmware according to the product model number, the firmware type and the version number to establish an association tree, wherein the product model number and the firmware type of the corresponding existing standard version firmware or the custom version firmware are the same as those of the newly developed firmware, and the version number of the corresponding existing standard version firmware or the custom version firmware is different from that of the newly developed firmware.
In some embodiments, associating the newly developed firmware under an existing standard version firmware or custom version firmware according to the product model number, firmware type, and version number to establish an association tree further comprises:
acquiring an association rule;
judging whether the product model, the firmware type and the version number in the identification field accord with association rules or not;
in response to compliance with an association rule, associating the newly developed firmware to an existing standard version firmware or custom version firmware.
In some embodiments, comparing the content of the newly developed firmware with the content of the firmware establishing the association relationship and generating a difference log further comprises:
dividing the newly developed firmware into a plurality of modules according to a preset mark field;
comparing each module of the newly developed firmware with a corresponding module in the firmware establishing an association relationship;
and generating a difference log divided by the modules based on the comparison result.
In some embodiments, testing the difference log further comprises:
in response to the test failing, returning the newly developed firmware to the developer.
In some embodiments, in response to a test passing, upgrading the corresponding version of firmware according to the difference log, further comprising:
in response to the test passing, sending the difference log to an administrator;
and receiving the feedback of the administrator and confirming whether the firmware of the corresponding version is upgraded by using the difference log according to the feedback result.
In some embodiments, further comprising:
and responding to the confirmation of updating the firmware of the corresponding version by using the difference log according to the feedback of the administrator, and determining and updating the module needing to be updated in the firmware of the corresponding version according to the difference log.
In some embodiments, further comprising:
and responding to successful upgrading, and performing evaluation test on the upgraded firmware of the corresponding version.
In some embodiments, further comprising:
and updating the identification field in the upgraded firmware of the corresponding version into the identification field corresponding to the newly developed firmware.
In some embodiments, further comprising:
and sending the updated identification field of the firmware of the corresponding version to an order production system so that the order production system produces an order according to the updated firmware of the corresponding version.
In some embodiments, further comprising:
and sending the identifier field of the upgraded firmware of the corresponding version to a customer service system so that the customer service system upgrades the firmware in the produced order to the upgraded firmware of the corresponding version according to the upgraded firmware of the corresponding version.
In some embodiments, further comprising:
and receiving order information fed back by the order production system or the customer service system and updating the production order information of the upgraded firmware with the corresponding version according to the order information.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a firmware management system, including:
the acquisition module is configured to respond to the receiving of newly developed firmware and acquire an identification field in the newly developed firmware;
the establishing module is configured to establish an incidence relation with the existing standard version firmware or customized version firmware according to the version information in the identification field;
the comparison module is configured to compare the content of the newly developed firmware with the content of the firmware establishing the association relationship and generate a difference log;
a test module configured to test the difference log;
and the upgrading module is configured to respond to the test passing and upgrade the firmware of the corresponding version according to the difference log.
In some embodiments, the setup module is further configured to:
acquiring the product model, the firmware type and the version number in the identification field;
and associating the newly developed firmware to the existing standard version firmware or the custom version firmware according to the product model number, the firmware type and the version number to establish an association tree, wherein the product model number and the firmware type of the corresponding existing standard version firmware or the custom version firmware are the same as those of the newly developed firmware, and the version number of the corresponding existing standard version firmware or the custom version firmware is different from that of the newly developed firmware.
In some embodiments, the setup module is further configured to:
acquiring an association rule;
judging whether the product model, the firmware type and the version number in the identification field conform to association rules or not;
in response to compliance with an association rule, associating the newly developed firmware to an existing standard version firmware or custom version firmware.
In some embodiments, the comparison module is further configured to:
dividing the newly developed firmware into a plurality of modules according to a preset mark field;
comparing each module of the newly developed firmware with a corresponding module in the firmware establishing an association relationship;
and generating a difference log divided by the modules based on the comparison result.
In some embodiments, the test module is further configured to:
in response to the test failing, returning the newly developed firmware to the developer.
In some embodiments, the upgrade module is further configured to:
in response to the test passing, sending the difference log to an administrator;
and receiving the feedback of the administrator and confirming whether the firmware of the corresponding version is upgraded by using the difference log according to the feedback result.
In some embodiments, the upgrade module is further configured to:
and responding to the confirmation of updating the firmware of the corresponding version by using the difference log according to the feedback of the administrator, and determining and updating the module needing to be updated in the firmware of the corresponding version according to the difference log.
In some embodiments, the upgrade module is further configured to:
and responding to successful upgrading, and performing evaluation test on the upgraded firmware of the corresponding version.
In some embodiments, the upgrade module is further configured to:
and updating the identification field in the upgraded firmware of the corresponding version into the identification field corresponding to the newly developed firmware.
In some embodiments, the method further comprises the step of:
and sending the updated identification field of the firmware of the corresponding version to an order production system so that the order production system produces an order according to the updated firmware of the corresponding version.
In some embodiments, the transmitting module is further configured to:
and sending the identifier field of the upgraded firmware of the corresponding version to a customer service system so that the customer service system upgrades the firmware in the produced order to the upgraded firmware of the corresponding version according to the upgraded firmware of the corresponding version.
In some embodiments, the apparatus further comprises a receiving module configured to:
and receiving order information fed back by the order production system or the customer service system and updating the production order information of the upgraded firmware with the corresponding version according to the order information.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer apparatus, including:
at least one processor; and
a memory storing a computer program operable on the processor, wherein the processor executes the program to perform any of the steps of the firmware management method as described above.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer-readable storage medium storing a computer program which, when executed by a processor, performs the steps of any of the firmware management methods described above.
The invention has one of the following beneficial technical effects: the scheme provided by the invention realizes the unified management of the standard version firmware and the customized version firmware of a single model product by establishing the association relationship between the standard version firmware and the customized version firmware developed in the life cycle of a server product.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained by using the drawings without creative efforts.
FIG. 1 is a flowchart illustrating a firmware management method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating firmware version information according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a dependency tree according to an embodiment of the present invention;
FIG. 4 is a block diagram of a firmware module according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a difference log provided by an embodiment of the present invention;
FIG. 6 is an interaction diagram of an order production system, a customer service system, and a firmware management system according to an embodiment of the invention;
FIG. 7 is a block diagram of a firmware management system according to an embodiment of the present invention;
FIG. 8 is a schematic structural diagram of a computer device provided in an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are only used for convenience of expression and should not be construed as a limitation to the embodiments of the present invention, and no description is given in the following embodiments.
According to an aspect of the present invention, an embodiment of the present invention provides a firmware management method, as shown in fig. 1, which may include the steps of:
s1, responding to the received newly developed firmware, and acquiring an identification field in the newly developed firmware;
s2, establishing an association relation with the existing standard version firmware or customized version firmware according to the version information in the identification field;
s3, comparing the content of the newly developed firmware with the content of the firmware establishing the association relationship and generating a difference log;
s4, testing the difference log;
and S5, responding to the test passing, and upgrading the firmware of the corresponding version according to the difference log.
The scheme provided by the invention realizes the unified management of the standard version firmware and the customized version firmware of a single model product by establishing the association relationship between the standard version firmware and the customized version firmware developed in the life cycle of a server product.
In some embodiments, establishing an association relationship with existing standard version firmware or custom version firmware according to the version information in the identification field further includes:
acquiring the product model, the firmware type and the version number in the identification field;
and associating the newly developed firmware to the existing standard version firmware or the custom version firmware according to the product model number, the firmware type and the version number to establish an association tree, wherein the product model number and the firmware type of the corresponding existing standard version firmware or the custom version firmware are the same as those of the newly developed firmware, and the version number of the corresponding existing standard version firmware or the custom version firmware is different from that of the newly developed firmware.
In some embodiments, associating the newly developed firmware under an existing standard version firmware or custom version firmware according to the product model number, firmware type, and version number to establish an association tree further comprises:
acquiring an association rule;
judging whether the product model, the firmware type and the version number in the identification field conform to association rules or not;
in response to compliance with an association rule, associating the newly developed firmware to an existing standard version firmware or custom version firmware.
Specifically, when the system establishes a rule for automatically capturing and associating the firmware version, and the server develops the finished standard version firmware or the customized version firmware, the system automatically captures the version information to establish an association tree, and in some embodiments, the firmware version information may be as shown in fig. 2. In some embodiments, as shown in fig. 3, the association rule may be firmware X (firmware type) _ XXX (product model) _ standard version vxy.yy, and when the system recognizes that the firmware version information is firmware X (firmware type) _ XXX (product model) _ standard version vxy.yy, the system allows firmware to upload and associate the firmware under the XXX product, and associates the customized version firmware developed based on the standard version with the standard version by comparing with the information of the standard version.
In some embodiments, comparing the content of the newly developed firmware with the content of the firmware establishing the association relationship and generating a difference log further comprises:
dividing the newly developed firmware into a plurality of modules according to a preset mark field;
comparing each module of the newly developed firmware with a corresponding module in the firmware establishing the association relationship;
and generating a difference log divided by the modules based on the comparison result.
Specifically, the firmware can be developed in a modularized manner, the system can realize rapid development based on the customized version of the standard version, online automatic comparison of differences is realized, a management log is formed, the standard version upgrading and synchronous customized version upgrading are realized through the system, and the test is controlled and controlled. As shown in fig. 4 and 5, the module division flag field may be integrated in firmware development, so that when the firmware uploads the system, the system compares the differences between versions based on the module and generates a difference log between the standard version and the custom version before and after upgrading or a difference log between the standard versions of the custom version.
In some embodiments, testing the difference log further comprises:
in response to the test failing, returning the newly developed firmware to the developer.
In some embodiments, in response to the test passing, upgrading the corresponding version of firmware according to the difference log, further comprising:
in response to the test passing, sending the difference log to an administrator;
and receiving the feedback of the administrator and confirming whether the firmware of the corresponding version is upgraded by using the difference log according to the feedback result.
In some embodiments, further comprising:
and responding to the confirmation of updating the firmware of the corresponding version by using the difference log according to the feedback of the administrator, and determining and updating the module needing to be updated in the firmware of the corresponding version according to the difference log.
In some embodiments, further comprising:
and responding to successful upgrading, and performing evaluation test on the upgraded firmware of the corresponding version.
In some embodiments, further comprising:
and updating the identification field in the upgraded firmware of the corresponding version into the identification field corresponding to the newly developed firmware.
Specifically, when the version is upgraded, the system sends the evaluation test of the tester after finishing comparison difference before and after upgrading the version, the evaluation test is displayed outwards after the test is passed, and the test is not returned to be responsible for the developer to develop and upload again.
And after the version test is passed, the system is released formally. The difference points developed based on the previous version are sent to a customized version responsible person to confirm whether the customized version is upgraded or not, the responsible person confirms the upgrade, the system automatically updates the difference part between the customized version and the upgraded standard version, refreshes the version information of the customized internal firmware to be consistent with the standard version information after the upgrade, and establishes an association relation; and when the responsible person confirms that the customized firmware version is not upgraded, the un-upgraded customized version establishing flag bit marks that the customized firmware version is not upgraded. Similarly, after the customized version is upgraded, the difference between the customized version and the standard version is compared to form a difference record, the difference record is sent to a customized version test responsible person for evaluation test, and the upgraded customized version is released formally after the test is passed.
In some embodiments, further comprising:
and sending the updated identification field of the firmware of the corresponding version to an order production system so that the order production system produces an order according to the updated firmware of the corresponding version.
In some embodiments, further comprising:
and sending the identifier field of the upgraded firmware of the corresponding version to a customer service system so that the customer service system upgrades the firmware in the produced order to the upgraded firmware of the corresponding version according to the upgraded firmware of the corresponding version.
In some embodiments, further comprising:
and receiving order information fed back by the order production system or the customer service system and updating the production order information of the upgraded firmware with the corresponding version according to the order information.
Specifically, as shown in fig. 6, the firmware version management system establishes an information transmission interface with the order production system and the customer service system, and after the firmware version of the product is upgraded, the firmware version management system sends the upgraded firmware version and information to the order production system and the customer service system. The latest firmware version is used during machine production or maintenance, after the machine production or maintenance is finished, the order production system returns the order information or the maintained order information to the firmware version management system, and the firmware version management system establishes the association between the order information and the firmware version for inquiry and use.
When the firmware version of the machine type is upgraded, comparing the version difference before and after upgrading, confirming whether the produced machine needs to be upgraded on the whole line based on the version difference, and quickly acquiring the order information of the produced machine in the firmware version management system when the whole line is needed to be upgraded. The order of the machine for finishing the firmware upgrade is updated in the customer service system and is transmitted back to the firmware version management system.
In the following, taking the version management of the BMC firmware of the server as an example, the firmware management method provided by the present invention is described in detail:
and 1, integrating firmware version information in the BMC, developing the BOM according to modularization, and establishing a module mark. The version information rule is defined as a standard version: BMC _ model information _ standard version _ vxy.yy, custom version: BMC _ model information _ standard version _ vxz.
2. When the standard version or the customized version BMC uploads the system, the system can capture version information in the firmware, confirm the association relationship by comparing the version information of the customized version with the version information of the standard version, and establish association in the system.
3. When the customized version BMC uploads the system, the association relationship is established, meanwhile, the comparison is carried out on the customized version BMC and the firmware content of the standard version, and a comparison difference log is generated and recorded based on the module.
4. When the standard version is upgraded in the system, for example, when the standard version is upgraded from BMC (baseboard management controller) _ model information _ standard version _ V00.00 to BMC _ model information _ standard version _ V10.00, the system compares the contents of the two standard versions to generate a difference log divided by modules, the difference log and the new version firmware are sent to a test engineer for test evaluation, and the difference log and the new version firmware are formally released in the system after the test is passed.
5. And if the test is not passed, returning to the firmware developer to modify the firmware and upload again, and repeating the step 4.
6. After the upgraded standard version test is released, the system sends the difference log before and after the standard version is upgraded to a person responsible for the customized version firmware developed based on the standard version.
7. And the system automatically updates the module with the difference between the customized version and the standard version after the responsible person of the customized version firmware confirms that the customized version is synchronously updated.
8. And after the firmware of the customized version is updated according to the standard version upgrading content, the firmware of the customized version is compared in the same way and generates a difference log to be sent to a test engineer, the test engineer evaluates the customized version after test upgrading, and the test releases the customized version formally.
9. And (5) repeating the step (2) when the customized version is released, and establishing the association relation between the released customized version and the standard version.
10. The firmware version management system establishes a data interface with the order production system and the customer service system, when the firmware version is released or upgraded, the firmware version management system sends the latest firmware version information to the order production system or the customer service system, the latest version firmware is used for the production of new products of the order production system, and after the production is finished, the order information is fed back to the firmware version management system and synchronously sent to the customer service system. The client system receives the latest version information, upgrades the version of the produced machine to the latest version, and refreshes the order and the firmware version information and returns the order and the firmware version information to the firmware version management system. And the firmware version management system refreshes the production order information corresponding to the standard firmware version or the customized firmware version according to the latest order and the firmware version information returned by the order production system and the customer service system.
The firmware management method provided by the invention realizes the management of the standard version and the customized version firmware based on the version information and the modularized content in the firmware through system development, establishes data transmission between the firmware management system and a production system and a customer service system, realizes the association between the standard version and the customized version firmware and order information, and realizes the rapid import and query of firmware upgrading and machine production or upgrading maintenance. Firstly, integrating firmware version information and modularization information in developed firmware; secondly, the system acquires firmware version information and compares the firmware content difference to produce a difference log when the firmware is uploaded, establishes an association relation between a standard version and a supply version by acquiring the firmware version information and comparing the firmware version information and the supply version when the firmware is uploaded, and generates the difference log divided by modules by comparing the firmware version content before and after upgrading or the standard version content and the customized version content; thirdly, the system sends the difference log to a development or test engineer for synchronous upgrading of the customized version and the standard version or evaluation test; fourthly, the firmware version management system establishes data transmission with the order production system and the customer service system, the firmware version system can transmit the latest firmware version to the order production system or the customer service system, and establishes a relationship between the order information and the firmware version information returned by the order production system and the customer service system; the order production system carries out machine production based on the firmware with the latest version and transmits order information to the firmware version management system and the customer service system; the customer service system can record the upgrade of the produced order machine according to the latest firmware and return the information to the firmware version management system.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a firmware management system 400, as shown in fig. 7, including:
an obtaining module 401 configured to, in response to receiving the newly developed firmware, obtain an identification field in the newly developed firmware;
an establishing module 402 configured to establish an association relationship with an existing standard version firmware or a customized version firmware according to the version information in the identification field;
a comparison module 403 configured to compare the content of the newly developed firmware with the content of the firmware establishing the association relationship and generate a difference log;
a testing module 404 configured to test the difference log;
and the upgrading module 405 is configured to respond to the test passing and upgrade the firmware of the corresponding version according to the difference log.
In some embodiments, the establishing module 402 is further configured to:
acquiring the product model, the firmware type and the version number in the identification field;
and associating the newly developed firmware to the existing standard version firmware or the custom version firmware according to the product model number, the firmware type and the version number to establish an association tree, wherein the product model number and the firmware type of the corresponding existing standard version firmware or the custom version firmware are the same as those of the newly developed firmware, and the version number of the corresponding existing standard version firmware or the custom version firmware is different from that of the newly developed firmware.
In some embodiments, the establishing module 402 is further configured to:
acquiring an association rule;
judging whether the product model, the firmware type and the version number in the identification field conform to association rules or not;
in response to compliance with an association rule, associating the newly developed firmware to an existing standard version firmware or custom version firmware.
In some embodiments, the comparison module 403 is further configured to:
dividing the newly developed firmware into a plurality of modules according to a preset mark field;
comparing each module of the newly developed firmware with a corresponding module in the firmware establishing an association relationship;
and generating a difference log divided by the modules based on the comparison result.
In some embodiments, the test module 404 is further configured to:
in response to the test failing, returning the newly developed firmware to the developer.
In some embodiments, the upgrade module 405 is further configured to:
in response to the test passing, sending the difference log to an administrator;
and receiving the feedback of the administrator and confirming whether the firmware of the corresponding version is upgraded by using the difference log according to the feedback result.
In some embodiments, the upgrade module 405 is further configured to:
and responding to the confirmation of updating the firmware of the corresponding version by using the difference log according to the feedback of the administrator, and determining and updating the module needing to be updated in the firmware of the corresponding version according to the difference log.
In some embodiments, the upgrade module 405 is further configured to:
and responding to successful upgrading, and performing evaluation test on the upgraded firmware of the corresponding version.
In some embodiments, the upgrade module 405 is further configured to:
and updating the identification field in the upgraded firmware of the corresponding version into the identification field corresponding to the newly developed firmware.
In some embodiments, the method further comprises the step of:
and sending the updated identification field of the firmware of the corresponding version to an order production system so that the order production system produces an order according to the updated firmware of the corresponding version.
In some embodiments, the transmitting module is further configured to:
and sending the identification field of the upgraded firmware of the corresponding version to a customer service system so that the customer service system upgrades the firmware in the produced order to the upgraded firmware of the corresponding version according to the upgraded firmware of the corresponding version.
In some embodiments, the apparatus further comprises a receiving module configured to:
and receiving order information fed back by the order production system or the customer service system and updating the production order information of the upgraded firmware with the corresponding version according to the order information.
According to the scheme provided by the invention, the association relation is established between the standard version firmware and the customized version firmware developed in the life cycle of the server product, so that the unified management of the standard version firmware and the customized version firmware of a single-model product is realized.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 8, an embodiment of the present invention further provides a computer apparatus 501, including:
at least one processor 520; and
a memory 510, the memory 510 storing a computer program 511 executable on the processor, the processor 520 executing the program to perform the steps of:
in response to receiving newly developed firmware, obtaining an identification field in the newly developed firmware;
establishing an incidence relation with the existing standard version firmware or customized version firmware according to the version information in the identification field;
comparing the content of the newly developed firmware with the content of the firmware establishing the association relationship and generating a difference log;
testing the difference log;
and responding to the test passing, and upgrading the firmware of the corresponding version according to the difference log.
In some embodiments, establishing an association relationship with an existing standard version firmware or a customized version firmware according to the version information in the identification field further comprises:
acquiring the product model, the firmware type and the version number in the identification field;
and associating the newly developed firmware to the existing standard version firmware or the custom version firmware according to the product model number, the firmware type and the version number to establish an association tree, wherein the product model number and the firmware type of the corresponding existing standard version firmware or the custom version firmware are the same as those of the newly developed firmware, and the version number of the corresponding existing standard version firmware or the custom version firmware is different from that of the newly developed firmware.
In some embodiments, associating the newly developed firmware under an existing standard version firmware or custom version firmware according to the product model number, firmware type, and version number to establish an association tree further comprises:
acquiring an association rule;
judging whether the product model, the firmware type and the version number in the identification field conform to association rules or not;
in response to compliance with an association rule, associating the newly developed firmware to an existing standard version firmware or custom version firmware.
In some embodiments, comparing the content of the newly developed firmware with the content of the firmware establishing the association relationship and generating a difference log further comprises:
dividing the newly developed firmware into a plurality of modules according to a preset mark field;
comparing each module of the newly developed firmware with a corresponding module in the firmware establishing an association relationship;
and generating a difference log divided by the modules based on the comparison result.
In some embodiments, testing the difference log further comprises:
in response to the test failing, returning the newly developed firmware to the developer.
In some embodiments, in response to a test passing, upgrading the corresponding version of firmware according to the difference log, further comprising:
in response to the test passing, sending the difference log to an administrator;
and receiving the feedback of the administrator and confirming whether the firmware of the corresponding version is upgraded by using the difference log according to the feedback result.
In some embodiments, further comprising:
and responding to the confirmation of updating the firmware of the corresponding version by using the difference log according to the feedback of the administrator, and determining and updating the module needing to be updated in the firmware of the corresponding version according to the difference log.
In some embodiments, further comprising:
and responding to successful upgrading, and performing evaluation test on the upgraded firmware of the corresponding version.
In some embodiments, further comprising:
and updating the identification field in the upgraded firmware of the corresponding version into the identification field corresponding to the newly developed firmware.
In some embodiments, further comprising:
and sending the updated identification field of the firmware of the corresponding version to an order production system so that the order production system produces an order according to the updated firmware of the corresponding version.
In some embodiments, further comprising:
and sending the identification field of the upgraded firmware of the corresponding version to a customer service system so that the customer service system upgrades the firmware in the produced order to the upgraded firmware of the corresponding version according to the upgraded firmware of the corresponding version.
In some embodiments, further comprising:
and receiving order information fed back by the order production system or the customer service system and updating the production order information of the upgraded firmware with the corresponding version according to the order information.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 9, an embodiment of the present invention further provides a computer-readable storage medium 601, the computer-readable storage medium 601 stores a computer program 610, and the computer program 610 performs the following steps when executed by a processor:
in response to receiving newly developed firmware, obtaining an identification field in the newly developed firmware;
establishing an incidence relation with the existing standard version firmware or customized version firmware according to the version information in the identification field;
comparing the content of the newly developed firmware with the content of the firmware establishing the association relationship and generating a difference log;
testing the difference log;
and responding to the test passing, and upgrading the firmware of the corresponding version according to the difference log.
In some embodiments, establishing an association relationship with an existing standard version firmware or a customized version firmware according to the version information in the identification field further comprises:
acquiring the product model, the firmware type and the version number in the identification field;
and associating the newly developed firmware to the existing standard version firmware or the custom version firmware according to the product model number, the firmware type and the version number to establish an association tree, wherein the product model number and the firmware type of the corresponding existing standard version firmware or the custom version firmware are the same as those of the newly developed firmware, and the version number of the corresponding existing standard version firmware or the custom version firmware is different from that of the newly developed firmware.
In some embodiments, associating the newly developed firmware under an existing standard version firmware or custom version firmware according to the product model number, firmware type, and version number to establish an association tree further comprises:
acquiring an association rule;
judging whether the product model, the firmware type and the version number in the identification field conform to association rules or not;
in response to compliance with an association rule, associating the newly developed firmware to an existing standard version firmware or custom version firmware.
In some embodiments, comparing the content of the newly developed firmware with the content of the firmware establishing the association relationship and generating a difference log further comprises:
dividing the newly developed firmware into a plurality of modules according to a preset mark field;
comparing each module of the newly developed firmware with a corresponding module in the firmware establishing the association relationship;
and generating a difference log divided by the modules based on the comparison result.
In some embodiments, testing the difference log further comprises:
in response to the test failing, returning the newly developed firmware to the developer.
In some embodiments, in response to a test passing, upgrading the corresponding version of firmware according to the difference log, further comprising:
in response to the test passing, sending the difference log to an administrator;
and receiving the feedback of the administrator and confirming whether the firmware of the corresponding version is upgraded by using the difference log according to the feedback result.
In some embodiments, further comprising:
and responding to the confirmation of updating the firmware of the corresponding version by using the difference log according to the feedback of the administrator, and determining and updating the module needing to be updated in the firmware of the corresponding version according to the difference log.
In some embodiments, further comprising:
and responding to successful upgrading, and performing evaluation test on the upgraded firmware of the corresponding version.
In some embodiments, further comprising:
and updating the identification field in the upgraded firmware of the corresponding version into the identification field corresponding to the newly developed firmware.
In some embodiments, further comprising:
and sending the updated identification field of the firmware of the corresponding version to an order production system so that the order production system produces an order according to the updated firmware of the corresponding version.
In some embodiments, further comprising:
and sending the identifier field of the upgraded firmware of the corresponding version to a customer service system so that the customer service system upgrades the firmware in the produced order to the upgraded firmware of the corresponding version according to the upgraded firmware of the corresponding version.
In some embodiments, further comprising:
and receiving order information fed back by the order production system or the customer service system and updating the production order information of the upgraded firmware with the corresponding version according to the order information.
Finally, it should be noted that, as will be understood by those skilled in the art, all or part of the processes of the methods of the above embodiments may be implemented by a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the embodiments of the methods described above.
Further, it should be appreciated that the computer-readable storage media (e.g., memory) herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.
Claims (15)
1. A firmware management method, comprising the steps of:
in response to receiving newly developed firmware, obtaining an identification field in the newly developed firmware;
establishing an incidence relation with the existing standard version firmware or customized version firmware according to the version information in the identification field;
comparing the content of the newly developed firmware with the content of the firmware establishing the association relationship and generating a difference log;
testing the difference log;
and responding to the test passing, and upgrading the firmware of the corresponding version according to the difference log.
2. The method of claim 1, wherein establishing an association with an existing standard version firmware or a custom version firmware based on version information in the identification field, further comprises:
acquiring the product model, the firmware type and the version number in the identification field;
and associating the newly developed firmware to the existing standard version firmware or the custom version firmware according to the product model number, the firmware type and the version number to establish an association tree, wherein the product model number and the firmware type of the corresponding existing standard version firmware or the custom version firmware are the same as those of the newly developed firmware, and the version number of the corresponding existing standard version firmware or the custom version firmware is different from that of the newly developed firmware.
3. The method of claim 2, wherein associating the newly developed firmware under an existing standard version firmware or custom version firmware according to the product model number, firmware type, and version number to build an association tree further comprises:
acquiring an association rule;
judging whether the product model, the firmware type and the version number in the identification field conform to association rules or not;
in response to an association rule being met, associating the newly developed firmware to an existing standard version firmware or custom version firmware.
4. The method of claim 1, wherein comparing the content of the newly developed firmware to the content of the association-established firmware and generating a difference log, further comprises:
dividing the newly developed firmware into a plurality of modules according to a preset mark field;
comparing each module of the newly developed firmware with a corresponding module in the firmware establishing an association relationship;
and generating a difference log divided by the modules based on the comparison result.
5. The method of claim 1, wherein the difference log is tested, further comprising:
in response to the test failing, returning the newly developed firmware to the developer.
6. The method of claim 4, wherein in response to a test passing, upgrading a corresponding version of firmware from the difference log, further comprising:
in response to the test passing, sending the difference log to an administrator;
and receiving the feedback of the administrator and confirming whether the firmware of the corresponding version is upgraded by using the difference log according to the feedback result.
7. The method of claim 6, further comprising:
and in response to the confirmation of updating the firmware of the corresponding version by using the difference log according to the feedback of the administrator, determining and updating the module needing to be updated in the firmware of the corresponding version according to the difference log.
8. The method of claim 7, further comprising:
and responding to successful upgrading, and performing evaluation test on the upgraded firmware of the corresponding version.
9. The method of claim 7, further comprising:
and updating the identification field in the upgraded firmware of the corresponding version into the identification field corresponding to the newly developed firmware.
10. The method of claim 9, further comprising:
and sending the updated identification field of the firmware of the corresponding version to an order production system so that the order production system produces an order according to the updated firmware of the corresponding version.
11. The method of claim 9, further comprising:
and sending the identifier field of the upgraded firmware of the corresponding version to a customer service system so that the customer service system upgrades the firmware in the produced order to the upgraded firmware of the corresponding version according to the upgraded firmware of the corresponding version.
12. The method of claim 10 or 11, further comprising:
and receiving order information fed back by the order production system or the customer service system and updating the production order information of the upgraded firmware with the corresponding version according to the order information.
13. A firmware management system, comprising:
the acquisition module is configured to respond to the receiving of newly developed firmware and acquire an identification field in the newly developed firmware;
the establishing module is configured to establish an incidence relation with the existing standard version firmware or customized version firmware according to the version information in the identification field;
the comparison module is configured to compare the content of the newly developed firmware with the content of the firmware establishing the association relationship and generate a difference log;
a test module configured to test the difference log;
and the upgrading module is configured to respond to the test passing and upgrade the firmware of the corresponding version according to the difference log.
14. A computer device, comprising:
at least one processor; and
memory storing a computer program operable on the processor, wherein the processor executes the program to perform the steps of the method according to any of claims 1-12.
15. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211411653.XA CN115794204A (en) | 2022-11-11 | 2022-11-11 | Firmware management method, system, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211411653.XA CN115794204A (en) | 2022-11-11 | 2022-11-11 | Firmware management method, system, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115794204A true CN115794204A (en) | 2023-03-14 |
Family
ID=85436923
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211411653.XA Pending CN115794204A (en) | 2022-11-11 | 2022-11-11 | Firmware management method, system, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115794204A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117742777A (en) * | 2024-02-21 | 2024-03-22 | 沐曦集成电路(上海)有限公司 | Chip file version management system |
-
2022
- 2022-11-11 CN CN202211411653.XA patent/CN115794204A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117742777A (en) * | 2024-02-21 | 2024-03-22 | 沐曦集成电路(上海)有限公司 | Chip file version management system |
| CN117742777B (en) * | 2024-02-21 | 2024-05-03 | 沐曦集成电路(上海)有限公司 | Chip file version management system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109683899A (en) | A kind of software integrating method and device | |
| CN106575227B (en) | Automatic software update framework | |
| CN106886410A (en) | A kind of software version management system | |
| CN111367545A (en) | Terminal upgrading method and device, server, terminal equipment and readable storage medium | |
| CN115794204A (en) | Firmware management method, system, equipment and storage medium | |
| CN111813788A (en) | Information query method and device and information synchronization method and device | |
| CN112698622B (en) | Automatic control method, device and machine readable storage medium | |
| CN111506358A (en) | Method and device for updating container configuration | |
| CN110442349A (en) | Method and apparatus for servicing dilatation | |
| CN110362462A (en) | A kind of power distribution network information interaction test method and system | |
| CN112463585A (en) | Solid state disk code testing method and system, storage medium and electronic equipment | |
| CN111488253A (en) | Configuration method, device and system of monitoring equipment and intelligent terminal | |
| EP3683675A1 (en) | System, apparatus and method of integrated deployment | |
| CN107203471B (en) | Joint debugging method, service platform and computer storage medium | |
| CN113934710B (en) | Data acquisition method and device | |
| CN110347609B (en) | Method and device for testing blockchain software | |
| CN113672521A (en) | Program testing method and device and electronic equipment | |
| CN114816887A (en) | Method, system, equipment and medium for checking topology setting of hard disk backboard of server | |
| CN113190413A (en) | Server hardware information processing method and device | |
| CN117149921B (en) | Component management method, system, equipment and storage medium | |
| CN113971191A (en) | Data import method and device and computer readable storage medium | |
| CN111399903B (en) | Server connection method, device and related equipment | |
| CN113592229B (en) | Fitment material acceptance method and device | |
| CN111581042A (en) | Cluster deployment method, deployment platform and server to be deployed | |
| CN116560722B (en) | Operation and maintenance flow processing method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |