A firmware configuration verification method and device, a management controller and a storage medium

Abstract

This invention provides a firmware configuration verification method, apparatus, management controller, and storage medium, relating to the field of management controllers. The management controller can be configured with a main firmware storage area, a backup firmware storage area, and a common storage area. A first firmware configuration file, a second firmware configuration file, and a common firmware configuration file are stored in these three storage areas respectively. Subsequently, during the startup phase, the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file can be compared to obtain a comparison result. Based on this comparison result, a more reliable firmware configuration file can be determined for startup, thereby ensuring the startup reliability of the management controller.

Description

Technical Field

[0001] This invention relates to the field of management controllers, and in particular to a firmware configuration verification method, apparatus, management controller, and storage medium. Background Technology

[0002] Management controllers are common components in server devices. In related technologies, management controllers can be configured with primary and backup firmware files to achieve high availability. However, since the primary and backup firmware files operate based on the same firmware configuration file, it is difficult to guarantee the normal startup of the management controller if the firmware configuration file is corrupted. Summary of the Invention

[0003] The purpose of this invention is to provide a firmware configuration verification method, apparatus, management controller, and storage medium, which can set multiple firmware configuration files in multiple independent storage areas, and determine the more reliable firmware configuration file by comparing the firmware configuration files in different storage areas, so that the startup can be based on the reliable firmware configuration file, thereby ensuring the startup reliability of the management controller.

[0004] To address the aforementioned technical problems, this invention provides a firmware configuration verification method applied to a management controller. The management controller has a main firmware storage area, a backup firmware storage area, and a common storage area. The main firmware storage area stores a first firmware configuration file, the backup firmware storage area stores a second firmware configuration file, and the common storage area stores a common firmware configuration file. The method includes:

[0005] During the startup phase, the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are compared to obtain the comparison results.

[0006] If the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, then the system will boot based on the identical firmware configuration file.

[0007] If the comparison results show that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, then the boot process will be based on the common firmware configuration file.

[0008] Optionally, the management controller has a main memory and a backup memory. Both the main memory and the backup memory have private partitions and public partitions. The private partition of the main memory is set as the main firmware storage area, and the private partition of the backup memory is set as the backup firmware storage area. The public partition of both the main memory and the backup memory is used to set up a common storage area. The private partitions of the main memory and the backup memory are used for firmware flashing.

[0009] Optionally, the main firmware storage area stores the main firmware file, and the backup firmware storage area stores the backup firmware file.

[0010] Before comparing the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, the following is also included:

[0011] Determine whether the version number of the main firmware file and the version number of the backup firmware file are the same;

[0012] If the version numbers are different, then the system will boot based on the backup firmware file and replace the main firmware file with the backup firmware file.

[0013] If the version numbers are the same, the data segments in the main firmware file and the data segments in the backup firmware file are compared to determine whether the main firmware file and the backup firmware file are consistent.

[0014] If the main firmware file and the backup firmware file have the same data, then the boot process will be based on the main firmware file.

[0015] If the main firmware file and the backup firmware file are inconsistent, then the system will determine to boot based on the backup firmware file and replace the main firmware file with the backup firmware file.

[0016] When determining the firmware file to be used for startup, the process proceeds to compare the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file.

[0017] Optionally, each data segment in the main firmware file is compared with each data segment in the backup firmware file to determine whether the main firmware file and the backup firmware file are data consistent, including:

[0018] The first data segment in the read-only partition of the main firmware storage area is taken as the data segment to be processed, and it is determined whether the data segment to be processed is a header file;

[0019] If the data segment to be processed is not a header file, then the next data segment in the read-only partition of the main firmware storage area will be used as the data segment to be processed, and the process will proceed to the step of determining whether the data segment to be processed is a header file.

[0020] If the data segment to be processed is a header file, then determine whether the data format of the data segment to be processed is a file system format;

[0021] If the data format of the data segment to be processed is not a file system format, then the next data segment in the read-only partition of the main firmware storage area will be used as the data segment to be processed, and the process will proceed to the step of determining whether the data segment to be processed is a header file.

[0022] If the data segment to be processed is in file system format, then determine the offset value of the data segment to be processed in the read-only partition, and take the corresponding data segment in the read-only partition of the spare firmware storage area as the data segment to be compared based on the offset value.

[0023] Calculate the first check value of the data segment to be processed, calculate the second check value of the data segment to be compared, and determine whether the first check value and the second check value are the same;

[0024] If the first check value and the second check value are different, it is determined that the main firmware file and the backup firmware file are inconsistent.

[0025] If the first check value and the second check value are the same, then determine whether all data segments in the read-only partition of the main firmware storage area have been processed.

[0026] If the data segment in the read-only partition of the main firmware storage area has not been processed, the next data segment in the read-only partition of the main firmware storage area will be taken as the data segment to be processed, and the step of determining whether the data segment to be processed is a header file will be entered.

[0027] If all data segments in the read-only partition of the main firmware storage area have been processed, then the main firmware file and the backup firmware file are considered to have the same data.

[0028] Optionally, the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are compared to obtain the comparison results, including:

[0029] Determine if the first firmware configuration file and the common firmware configuration file are the same;

[0030] If the first firmware configuration file and the common firmware configuration file are the same, a comparison result indicating that the first firmware configuration file and the common firmware configuration file are the same is generated;

[0031] If the first firmware configuration file and the common firmware configuration file are different, then determine whether the second firmware configuration file and the common firmware configuration file are the same.

[0032] If the second firmware configuration file and the common firmware configuration file are the same, a comparison result indicating that the second firmware configuration file and the common firmware configuration file are the same is generated;

[0033] If the second firmware configuration file and the common firmware configuration file are different, then determine whether the first firmware configuration file and the second firmware configuration file are the same.

[0034] If the first firmware configuration file and the second firmware configuration file are the same, a comparison result indicating that the first firmware configuration file and the second firmware configuration file are the same is generated.

[0035] If the first firmware configuration file and the second firmware configuration file are different, a comparison result is generated indicating that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different.

[0036] Optionally, it also includes:

[0037] If the first firmware configuration file and the second firmware configuration file are the same, then the common firmware configuration file is updated using the first firmware configuration file.

[0038] If the comparison results show that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, then the first firmware configuration file and the second firmware configuration file are updated using the common firmware configuration file.

[0039] Optionally, it also includes:

[0040] Upon receiving an updated firmware configuration file, the public firmware configuration file is updated using the updated firmware configuration file;

[0041] Update the first firmware configuration file and the second firmware configuration file using the updated public firmware configuration file.

[0042] Optionally, if the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, then booting is performed based on the identical firmware configuration file, including:

[0043] If the comparison result shows that the first firmware configuration file and the second firmware configuration file are the same, then the system will boot according to the first firmware configuration file.

[0044] If the comparison result shows that the first firmware configuration file and the common firmware configuration file are the same, then the system will boot according to the first firmware configuration file.

[0045] If the comparison result shows that the second firmware configuration file and the common firmware configuration file are the same, then the system will boot according to the second firmware configuration file.

[0046] The present invention also provides a firmware configuration verification device applied to a management controller. The management controller has a main firmware storage area, a backup firmware storage area, and a common storage area. The main firmware storage area stores a first firmware configuration file, the backup firmware storage area stores a second firmware configuration file, and the common storage area stores a common firmware configuration file. The device includes:

[0047] The comparison module is used to compare the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file during the startup phase and obtain the comparison result.

[0048] The first startup module is used to start the system based on the same firmware configuration file if the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file.

[0049] The second startup module is used to start the system based on the common firmware configuration file if the comparison results show that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different.

[0050] The present invention also provides a management controller, comprising:

[0051] Memory, used to store computer programs;

[0052] The processor is used to implement the firmware configuration verification method described above when executing computer programs.

[0053] The present invention also provides a non-volatile computer-readable storage medium storing computer-executable instructions, which, when loaded and executed by a processor, implement the aforementioned firmware configuration verification method.

[0054] This invention provides a firmware configuration verification method applied to a management controller. The management controller has a main firmware storage area, a backup firmware storage area, and a common storage area. The main firmware storage area stores a first firmware configuration file, the backup firmware storage area stores a second firmware configuration file, and the common storage area stores a common firmware configuration file. The method includes: during the startup phase, comparing the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file to obtain a comparison result; if the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, then startup is performed based on the identical firmware configuration file; if the comparison result shows that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, then startup is performed based on the common firmware configuration file.

[0055] As can be seen, this invention firstly establishes a primary firmware storage area, a backup firmware storage area, and a common storage area on the management controller. The primary firmware storage area stores a first firmware configuration file, the backup firmware storage area stores a second firmware configuration file, and the common storage area stores a common firmware configuration file, thus providing three firmware configuration files in three storage areas. Subsequently, during the startup phase, the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file can be compared to obtain the comparison result. If the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, then startup is performed based on the identical firmware configuration file; if the comparison result shows that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, then startup is performed based on the common firmware configuration file. In short, by comparing firmware configuration files in different storage areas, a more reliable firmware configuration file can be determined, and startup can be performed based on the reliable firmware configuration file, thereby ensuring the startup reliability of the management controller. This invention also provides a firmware configuration verification device, a management controller, and a non-volatile computer-readable storage medium, which have the above-mentioned beneficial effects. Attached Figure Description

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

[0057] Figure 1 This is a schematic diagram of a storage area provided in an embodiment of the present invention;

[0058] Figure 2 This is a schematic diagram illustrating the setting of storage partitions in a memory according to an embodiment of the present invention;

[0059] Figure 3 A flowchart of a firmware configuration verification method provided in an embodiment of the present invention;

[0060] Figure 4 This is a schematic diagram of a configuration file comparison process provided in an embodiment of the present invention;

[0061] Figure 5 This is a schematic diagram of a rollback process provided in an embodiment of the present invention;

[0062] Figure 6 This is a structural block diagram of a firmware configuration verification device provided in an embodiment of the present invention;

[0063] Figure 7This is a structural block diagram of a management controller provided in an embodiment of the present invention. Detailed Implementation

[0064] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0065] Management controllers are common components in server equipment. Common management controllers include Baseboard Management Controllers (BMCs), Integrated Lightout (iLO) managers, and Integrated Dell Remote Access Controllers (iDRACs). In related technologies, management controllers can be configured with primary and backup firmware files to achieve high availability. However, since both primary and backup firmware files operate based on the same firmware configuration file, it is difficult to guarantee the normal startup of the management controller if the firmware configuration file is corrupted.

[0066] In view of this, to address the technical problem of how to improve the reliability of firmware configuration files, the present invention provides a firmware configuration verification method. This method allows setting multiple firmware configuration files in multiple independent storage areas and comparing the firmware configuration files in different storage areas to determine the more reliable firmware configuration file. This enables startup based on the reliable firmware configuration file, thereby ensuring the startup reliability of the management controller.

[0067] The following section first introduces the improvements to the firmware configuration file storage method. For easier understanding, please refer to... Figure 1 , Figure 1This is a schematic diagram of a storage area provided in an embodiment of the present invention. In this embodiment, the management controller has three independent storage areas: a main firmware storage area, a backup firmware storage area, and a common storage area. The main firmware storage area stores a first firmware configuration file, the backup firmware storage area stores a second firmware configuration file, and the common storage area stores a common firmware configuration file. Under normal circumstances, the three firmware configuration files store the same firmware configuration, and it can be determined whether the firmware configuration files store the same firmware configuration by comparing them. In addition, when updating the firmware file, the main firmware file is only written to the main firmware storage area, the backup firmware file is only written to the backup firmware storage area, and the common storage area is not updated. In this embodiment, the common storage area is only used to store the common firmware configuration file. Therefore, with the above improvements, this embodiment can store three firmware configuration files in three independent storage areas, and the same firmware configuration file can be found by comparison, and the same firmware configuration file can be regarded as a reliable firmware configuration file; at the same time, a backup common firmware configuration file can also be stored in the common storage area to ensure that a usable firmware configuration file is still available when the first firmware configuration file and the second firmware configuration file fail.

[0068] It should be noted that this embodiment does not limit how the main firmware storage area, backup firmware storage area, and common storage area are configured. For example, the main firmware storage area, backup firmware storage area, and common storage area can be configured in the same memory of the management controller. Of course, to avoid the failure of a single memory, the management controller can have a main memory and a backup memory. Both the main memory and the backup memory have private partitions and common partitions. The private partition of the main memory is used for the main firmware storage area, and the private partition of the backup memory is used for the backup firmware storage area. The common partitions of both the main memory and the backup memory are used to create the common storage area. The private partitions of the main memory and the backup memory are used for firmware flashing. For easier understanding, please refer to... Figure 2 , Figure 2 This is a schematic diagram illustrating the setting of storage partitions in a memory according to an embodiment of the present invention. It can be seen that the main firmware memory has a private main firmware storage area, and the backup firmware memory has a private backup firmware storage area; the two can jointly form a common storage area. This further improves the storage reliability of the firmware configuration file.

[0069] Based on the above introduction, the firmware configuration verification method provided in the embodiments of the present invention will be described below. Please refer to... Figure 3 , Figure 3 A flowchart of a firmware configuration verification method provided in an embodiment of the present invention is shown. The method may include:

[0070] S101. During the startup phase, the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are compared to obtain the comparison results.

[0071] As described above, this embodiment can set multiple firmware configuration files in multiple independent storage areas. Therefore, in this step, when the management controller starts up, it can compare these multiple firmware configuration files, determine the firmware configuration file with the same firmware configuration content, and use it as the reliable file to start up, thereby improving the reliability of the firmware configuration.

[0072] It should be noted that this embodiment does not limit how the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are compared. For example, the firmware configuration content in each firmware configuration file can be compared; alternatively, only the size of each firmware configuration file can be compared, and if the sizes are different, it indicates that the firmware configuration files are different. Considering that comparing file sizes can achieve higher comparison efficiency, this embodiment can compare the file sizes of the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file to obtain the comparison result.

[0073] It should also be noted that this embodiment does not limit the comparison order of the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file. For example, the first firmware configuration file can be compared with the common firmware configuration file first. If the first firmware configuration file and the common firmware configuration file are different, then the second firmware configuration file is compared with the common firmware configuration file. If the second firmware configuration file and the common firmware configuration file are different, then the first firmware configuration file is compared with the second firmware configuration file. In this way, this embodiment can first determine whether the first firmware configuration file in the main firmware storage area is reliable, and then determine whether the first firmware configuration file in the backup firmware storage area is reliable. At the same time, considering that the common firmware configuration file has higher reliability, the first firmware configuration file and the second firmware configuration file can be compared with the common firmware configuration file respectively first, and then the first firmware configuration file can be compared with the second firmware configuration file, thereby achieving higher comparison efficiency.

[0074] Based on this, the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are compared to obtain the comparison results, which may include:

[0075] Step 11: Determine whether the first firmware configuration file and the common firmware configuration file are the same; if the first firmware configuration file and the common firmware configuration file are the same, proceed to step 12; if the first firmware configuration file and the common firmware configuration file are different, proceed to step 13.

[0076] Step 12: Generate a comparison result indicating that the first firmware configuration file and the common firmware configuration file are the same.

[0077] Step 13: Determine whether the second firmware configuration file and the common firmware configuration file are the same; if the second firmware configuration file and the common firmware configuration file are the same, proceed to step 14; if the second firmware configuration file and the common firmware configuration file are different, proceed to step 15.

[0078] Step 14: Generate a comparison result indicating that the second firmware configuration file and the public firmware configuration file are the same.

[0079] Step 15: Determine whether the first firmware configuration file and the second firmware configuration file are the same; if the first firmware configuration file and the second firmware configuration file are the same, proceed to step 16; if the first firmware configuration file and the second firmware configuration file are different, proceed to step 17.

[0080] Step 16: Generate a comparison result indicating that the first firmware configuration file and the second firmware configuration file are the same.

[0081] Step 17: Generate comparison results indicating that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different.

[0082] S102. If the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, then start the machine based on the identical firmware configuration file.

[0083] In this step, if the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, then the identical firmware configuration files can be regarded as reliable firmware configuration files, and the boot can be performed based on the reliable firmware configuration files.

[0084] For example, if the comparison result shows that the first firmware configuration file and the second firmware configuration file are the same, then the system can be started according to the first firmware configuration file; if the comparison result shows that the first firmware configuration file and the common firmware configuration file are the same, then the system can be started according to the first firmware configuration file; if the comparison result shows that the second firmware configuration file and the common firmware configuration file are the same, then the system can be started according to the second firmware configuration file.

[0085] Based on this, if the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, then booting based on the identical firmware configuration file may include:

[0086] Step 21: If the comparison result shows that the first firmware configuration file and the second firmware configuration file are the same, then start the system according to the first firmware configuration file.

[0087] Step 22: If the comparison result shows that the first firmware configuration file and the common firmware configuration file are the same, then start the program according to the first firmware configuration file.

[0088] Step 23: If the comparison result shows that the second firmware configuration file and the common firmware configuration file are the same, then start the program according to the second firmware configuration file.

[0089] S103. If the comparison results show that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, then the system will start according to the common firmware configuration file.

[0090] In this step, if the comparison results show that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, considering that when updating firmware files, the main firmware file is only flashed to the main firmware storage area, the backup firmware file is only flashed to the backup firmware storage area, and the common storage area is not flashed or updated, the common firmware configuration file is more reliable, so the boot is performed according to the common firmware configuration file.

[0091] Furthermore, after steps S102 and S103 are completed, considering the possibility of different firmware configuration files, to ensure data consistency, reliable firmware configuration files can be used to update the data of different firmware configuration files. Specifically, if the comparison results show that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, considering that the common firmware configuration file has higher reliability, the first firmware configuration file and the second firmware configuration file can be updated using the common firmware configuration file. If the comparison results show that the first firmware configuration file and the second firmware configuration file are the same, and the common firmware configuration file is different from both the first and second firmware configuration files, this indicates that the first firmware configuration file and the second firmware configuration file have higher reliability, therefore the first firmware configuration file can be used to update the common firmware configuration file.

[0092] Based on this, the method may also include:

[0093] Step 31: If the first firmware configuration file and the second firmware configuration file are the same, then update the common firmware configuration file using the first firmware configuration file.

[0094] Step 32: If the comparison results show that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, then update the first firmware configuration file and the second firmware configuration file using the common firmware configuration file.

[0095] Furthermore, when users need to adjust firmware configuration, they can first use the updated firmware configuration file to update the common firmware configuration file, prioritizing the update of the more reliable common firmware configuration file among the three firmware configuration files. Then, the updated common firmware configuration file can be used to update the first firmware configuration file and the second firmware configuration file, thereby improving the reliability of firmware configuration updates.

[0096] Based on this, the method may also include:

[0097] Step 41: Upon receiving the updated firmware configuration file, update the common firmware configuration file using the updated firmware configuration file.

[0098] Step 42: Update the first firmware configuration file and the second firmware configuration file using the updated public firmware configuration file.

[0099] Based on the above embodiments, the present invention can first set up a main firmware storage area, a backup firmware storage area, and a common storage area on the management controller. The main firmware storage area stores a first firmware configuration file, the backup firmware storage area stores a second firmware configuration file, and the common storage area stores a common firmware configuration file, thus setting up three firmware configuration files in three storage areas. Subsequently, during the startup phase, the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file can be compared to obtain the comparison result. If the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, then startup is performed based on the identical firmware configuration file; if the comparison result shows that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, then startup is performed based on the common firmware configuration file. In short, by comparing the firmware configuration files in different storage areas, a more reliable firmware configuration file can be determined, and startup can be performed based on the reliable firmware configuration file, thereby ensuring the startup reliability of the management controller.

[0100] Based on the above embodiments, to further improve the reliability of the management controller startup, this embodiment, in addition to verifying the firmware configuration file, can also verify the main firmware file in the main firmware storage area and the backup firmware file in the backup firmware storage area to verify the reliability of the main firmware file. The firmware file verification process is described below. Based on this, the main firmware storage area stores the main firmware file, and the backup firmware storage area stores the backup firmware file; before comparing the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, the following may also be included:

[0101] S201. Determine whether the version number of the main firmware file and the version number of the backup firmware file are the same.

[0102] In this embodiment, since firmware upgrades involve upgrading both the primary and backup firmware files to ensure consistency, if the version numbers of the primary and backup firmware files are the same, the primary firmware file can be preliminarily determined to be reliable. Conversely, if the version numbers of the primary and backup firmware files are different, a defect in the firmware upgrade can be identified, leading to the conclusion that the primary firmware file is unreliable. Therefore, if the primary firmware file is determined to be unreliable, booting can be performed based on the backup firmware file.

[0103] S202. If the version numbers are different, then the system will boot based on the backup firmware file and replace the main firmware file with the backup firmware file.

[0104] In this step, if the version numbers of the primary firmware file and the backup firmware file are inconsistent, the primary firmware file is considered faulty, and booting can then be performed based on the backup firmware file. Alternatively, if the primary firmware file is determined to be unreliable, the backup firmware file can be used to replace it, thus enabling firmware rollback.

[0105] S203. If the version numbers are the same, compare each data segment in the main firmware file with each data segment in the backup firmware file to determine whether the main firmware file and the backup firmware file are consistent.

[0106] In this step, after confirming that the version numbers of the main firmware file and the backup firmware file are the same, to further verify whether the main firmware file has been corrupted, the data consistency between the main firmware file and the backup firmware file can be further verified. For example, in this step, each data segment in the main firmware file can be compared with each data segment in the backup firmware file to determine whether the main firmware file and the backup firmware file have consistent data.

[0107] It should be noted that this embodiment does not limit how the data segments in the main firmware file are compared with the data segments in the backup firmware file; the method can be set according to actual application requirements. First, the firmware file can be stored in the read-only area of ​​the memory, therefore the data in the read-only area needs to be compared. Additionally, since header files typically identify the start position of a complete data segment, and data in file system formats (such as JFFS, Journaling Flash File System) usually records file system information, after retrieving a data segment from the read-only partition of the main firmware storage area, it can be determined whether the data segment is a header file or a file system format. If it is a header file or a file system format, it can be compared with the corresponding data segment in the read-only partition of the backup firmware storage area. Conversely, if the data segment is neither a header file nor a file system format, the next data segment needs to be retrieved from the read-only partition of the main firmware storage area.

[0108] In addition, to compare whether data segments are consistent, a checksum (e.g., hash value) can be calculated for each data segment, and these checksums can be compared. If the checksums match, the data segments are the same; if the checksums do not match, the data segments are inconsistent. Furthermore, if any data segment in the main firmware file is inconsistent with the corresponding data segment in the backup firmware file, it can be determined that there is a data inconsistency between the main firmware file and the backup firmware file.

[0109] Based on this, comparing each data segment in the main firmware file with each data segment in the backup firmware file to determine whether the main firmware file and the backup firmware file are data consistent can include:

[0110] Step 1: Take the first data segment in the read-only partition of the main firmware storage area as the data segment to be processed, and determine whether the data segment to be processed is a header file; if the data segment to be processed is not a header file, proceed to Step 2; if the data segment to be processed is a header file, proceed to Step 3.

[0111] It should be noted that this embodiment does not limit how to determine whether a data segment is a header file; relevant technologies for header files and firmware can be referenced.

[0112] Step 2: Take the next data segment in the read-only partition of the main firmware storage area as the data segment to be processed, and proceed to the step of determining whether the data segment to be processed is a header file.

[0113] Step 3: Determine whether the data format of the data segment to be processed is a file system format; if the data format of the data segment to be processed is not a file system format, proceed to step 4; if the data format of the data segment to be processed is a file system format, proceed to step 5.

[0114] It should be noted that this embodiment does not limit how to determine whether a data segment is in a file system format; relevant technologies of JFFS2 can be referred to.

[0115] Step 4: Take the next data segment in the read-only partition of the main firmware storage area as the data segment to be processed, and proceed to the step of determining whether the data segment to be processed is a header file.

[0116] Step 5: Determine the offset value of the data segment to be processed in the read-only partition, and use the corresponding data segment in the read-only partition of the spare firmware storage area as the data segment to be compared based on the offset value.

[0117] In this embodiment, the offset value is the distance of the data segment relative to the start position of the read-only partition. Since the main firmware file should be identical to the backup firmware file, the offset values ​​of each data segment in the main firmware file within the read-only partition of the main firmware storage area should be consistent with the offset values ​​of each data segment in the backup firmware file within the read-only partition of the backup firmware storage area. Therefore, the corresponding data segment can be queried based on the offset value.

[0118] Step 6: Calculate the first check value of the data segment to be processed, calculate the second check value of the data segment to be compared, and determine whether the first check value and the second check value are the same; if the first check value and the second check value are different, proceed to step 7; if the first check value and the second check value are the same, proceed to step 8.

[0119] It should be noted that this embodiment does not limit the calculation method of the verification value, and can be set according to the actual application requirements. For example, relevant technologies of hash value can be referred to.

[0120] Step 7: Determine if the main firmware file and the backup firmware file have inconsistent data;

[0121] Step 8: Determine whether all data segments in the read-only partition of the main firmware storage area have been processed; if the data segments in the read-only partition of the main firmware storage area have not been processed, proceed to step 9; if all data segments in the read-only partition of the main firmware storage area have been processed, proceed to step 10.

[0122] Step 9: Take the next data segment in the read-only partition of the main firmware storage area as the data segment to be processed, and proceed to the step of determining whether the data segment to be processed is a header file;

[0123] Step 10: Determine that the main firmware file and the backup firmware file have the same data.

[0124] S204. If the main firmware file and the backup firmware file have the same data, then the boot process will be based on the main firmware file.

[0125] In this step, if it is determined that the main firmware file and the backup firmware file have the same data, the main firmware file can be considered reliable, and the system can then boot based on the main firmware file.

[0126] S205. If the main firmware file and the backup firmware file are inconsistent, then the system will determine to start based on the backup firmware file and replace the main firmware file with the backup firmware file.

[0127] In this step, if it is determined that the main firmware file and the backup firmware file are inconsistent, it can be concluded that the main firmware file is corrupted, and booting can then be performed based on the backup firmware file. Of course, if it is determined that the main firmware file is unreliable, the backup firmware file can be used to replace the main firmware file to achieve firmware file rollback.

[0128] S206. When determining the firmware file to be used for startup, proceed to the step of comparing the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file.

[0129] In this step, after verifying the firmware file, the firmware configuration file can be verified.

[0130] Based on the above embodiments, the firmware configuration verification method described below will be introduced with specific examples. In this embodiment, the shared configuration file used by flash0 and flash1 can be changed to each flash having its own area to store the configuration file, while retaining the shared configuration file. When the baseboard management controller powers on, a judgment can be added when reading the configuration file to compare the size of the flash0 configuration file with the size of the shared configuration file and compare the size of the flash1 configuration file with the size of the shared configuration file.

[0131] Please refer to the configuration file comparison process. Figure 4 , Figure 4 The following is a schematic diagram of a configuration file comparison process provided by an embodiment of the present invention, and its specific implementation is as follows:

[0132] 1. When the sizes of the compared configuration files are equal, it is assumed that there is no abnormality in the configuration files, and the system will start normally according to flash0, while using the configuration files in flash0;

[0133] 2. When the sizes of the compared configuration files are not equal, compare the size of the configuration file stored in flash0 with the size of the configuration file stored in flash1. At this point, determine whether the configuration file in flash0 or flash1 is faulty.

[0134] 3. When the size of the flash0 configuration file is not equal to the size of the shared configuration file, compare the size of the flash1 configuration file with the size of the shared configuration file. If they are equal, it means that the flash1 configuration file is corrupted, and flash1 should be used to start.

[0135] 4. When the configuration files of flash1 are not equal, the shared configuration file is used directly to start the computer, and the shared configuration file is resynchronized to the configuration files of flash0 and flash1.

[0136] In addition, this embodiment also includes a rollback mechanism to ensure that the configuration files of flash0 and flash1 are aligned.

[0137] Please refer to the rollback process. Figure 5 , Figure 5 This is a schematic diagram of a rollback process provided in an embodiment of the present invention. The specific implementation of the rollback process is as follows:

[0138] 1. First, compare the version numbers of flash0 and flash1. If they are different, directly synchronize flash1 with the firmware content and configuration files of flash0.

[0139] 2. If the version numbers match, check the read-only partition, read a black file from the current image, and distinguish whether it is a header file. If it is not a header file, continue searching for black. If it is a header file, determine whether it is in JFFS2 format. If it is not in JFFS2 format, continue searching for black. If it is in JFFS2 format, calculate and record the current offset, and jump to the same position in flash1. Read the data of the same partition in flash1 according to black and calculate the checksum. If the checksum calculated with the flash1 partition is inconsistent, roll back.

[0140] 3. If the checksum calculated with the flash1 partition is consistent, compare it with the checksum in the flash0 partition. If they are inconsistent, roll back. If they are consistent, rebuild and check the read-only partition, read black from the current image, and form a closed loop.

[0141] The firmware configuration verification device, management controller, computer-readable storage medium, and computer program product provided in the embodiments of the present invention will be described below. The firmware configuration verification device, management controller, computer-readable storage medium, and computer program product described below can be referred to in correspondence with the firmware configuration verification method described above.

[0142] Please refer to Figure 6 , Figure 6This is a structural block diagram of a firmware configuration verification device provided in an embodiment of the present invention. The device is applied to a management controller, which has a main firmware storage area, a backup firmware storage area, and a common storage area. The main firmware storage area stores a first firmware configuration file, the backup firmware storage area stores a second firmware configuration file, and the common storage area stores a common firmware configuration file. The device may include:

[0143] The comparison module 601 is used to compare the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file during the startup phase to obtain the comparison result;

[0144] The first startup module 602 is used to start the system based on the same firmware configuration file if the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file.

[0145] The second boot module 603 is used to boot according to the common firmware configuration file if the comparison results show that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different.

[0146] Optionally, the main firmware storage area stores the main firmware file, and the backup firmware storage area stores the backup firmware file; the device may further include:

[0147] The version number detection module is used to determine whether the version number of the main firmware file and the version number of the backup firmware file are the same.

[0148] The first setting module is used to determine whether to start based on the backup firmware file if the version numbers are different, and to replace the main firmware file with the backup firmware file.

[0149] The data segment detection module is used to compare each data segment in the main firmware file with each data segment in the backup firmware file if the version numbers are the same, to determine whether the main firmware file and the backup firmware file have consistent data.

[0150] The second setting module is used to determine whether to start based on the main firmware file if the main firmware file and the backup firmware file have the same data.

[0151] The third setting module is used to determine whether to start the system based on the backup firmware file if the main firmware file and the backup firmware file are inconsistent, and to replace the main firmware file with the backup firmware file.

[0152] The process control module is used to enter the step of comparing the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file when determining the firmware file to be used for startup.

[0153] Optionally, the data segment detection module may include:

[0154] The header file determination submodule is used to take the first data segment in the read-only partition of the main firmware storage area as the data segment to be processed, and determine whether the data segment to be processed is a header file;

[0155] The first process control submodule is used to, if the data segment to be processed is not a header file, take the next data segment in the read-only partition of the main firmware storage area as the data segment to be processed, and proceed to the step of determining whether the data segment to be processed is a header file.

[0156] The data format determination submodule is used to determine whether the data format of the data segment to be processed is a file system format if the data segment to be processed is a header file.

[0157] The second process control submodule is used to take the next data segment in the read-only partition of the main firmware storage area as the data segment to be processed if the data format of the data segment to be processed is not a file system format, and then proceed to the step of determining whether the data segment to be processed is a header file.

[0158] The lookup submodule is used to determine the offset value of the data segment to be processed in the read-only partition if the data format of the data segment to be processed is a file system format, and to use the corresponding data segment in the read-only partition of the spare firmware storage area as the data segment to be compared based on the offset value.

[0159] The comparison submodule is used to calculate the first check value of the data segment to be processed, calculate the second check value of the data segment to be compared, and determine whether the first check value and the second check value are the same.

[0160] The first determination submodule is used to determine that the main firmware file and the backup firmware file are inconsistent if the first verification value and the second verification value are different.

[0161] The processing completion judgment submodule is used to determine whether all data segments in the read-only partition of the main firmware storage area have been processed if the first check value and the second check value are the same.

[0162] The loop control submodule is used to take the next data segment in the read-only partition of the main firmware storage area as the data segment to be processed if the data segment in the read-only partition of the main firmware storage area has not been processed, and then proceed to the step of determining whether the data segment to be processed is a header file.

[0163] The first determination submodule is used to determine that the main firmware file and the backup firmware file are consistent if all data segments in the read-only partition of the main firmware storage area have been processed.

[0164] Optionally, the comparison module 601 includes:

[0165] The first comparison submodule is used to determine whether the first firmware configuration file and the common firmware configuration file are the same;

[0166] The first result generation submodule is used to generate a comparison result indicating that the first firmware configuration file and the common firmware configuration file are the same if the first firmware configuration file and the common firmware configuration file are the same.

[0167] The second comparison submodule is used to determine whether the second firmware configuration file and the common firmware configuration file are the same if the first firmware configuration file and the common firmware configuration file are different.

[0168] The second result generation submodule is used to generate a comparison result indicating that the second firmware configuration file and the common firmware configuration file are the same if the second firmware configuration file and the common firmware configuration file are the same.

[0169] The third comparison submodule is used to determine whether the first firmware configuration file and the second firmware configuration file are the same if the second firmware configuration file and the common firmware configuration file are different.

[0170] The third result generation submodule is used to generate a comparison result indicating that the first firmware configuration file and the second firmware configuration file are the same if the first firmware configuration file and the second firmware configuration file are the same.

[0171] The fourth result generation submodule is used to generate a comparison result indicating that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different if the first firmware configuration file and the second firmware configuration file are different.

[0172] Optionally, the device may further include:

[0173] The first update module is used to update the common firmware configuration file using the first firmware configuration file if the first firmware configuration file and the second firmware configuration file are the same.

[0174] The second update module is used to update the first firmware configuration file and the second firmware configuration file using the common firmware configuration file if the comparison results show that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different.

[0175] Optionally, it also includes:

[0176] The third update module is used to update the public firmware configuration file using the updated firmware configuration file when an updated firmware configuration file is received.

[0177] The fourth update module is used to update the first firmware configuration file and the second firmware configuration file using the updated public firmware configuration file.

[0178] Optionally, the first startup module 602 includes:

[0179] The first boot submodule is used to boot according to the first firmware configuration file if the comparison result is that the first firmware configuration file and the second firmware configuration file are the same.

[0180] The second boot submodule is used to boot according to the first firmware configuration file if the comparison result is that the first firmware configuration file and the common firmware configuration file are the same.

[0181] The third boot submodule is used to boot according to the second firmware configuration file if the comparison result shows that the second firmware configuration file and the common firmware configuration file are the same.

[0182] Please refer to Figure 7 , Figure 7 This is a structural block diagram of a management controller provided in an embodiment of the present invention. The embodiment of the present invention provides a management controller 10, including a processor 11 and a memory 12; wherein, the memory 12 is used to store a computer program; the processor 11 is used to execute the firmware configuration verification method provided in the foregoing embodiment when executing the computer program.

[0183] For details regarding the firmware configuration verification method described above, please refer to the relevant content provided in the foregoing embodiments; further details will not be repeated here.

[0184] Furthermore, the memory 12, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, and the storage method can be temporary storage or permanent storage.

[0185] In addition, the management controller 10 also includes a power supply 13, a communication interface 14, an input / output interface 15, and a communication bus 16. The power supply 13 is used to provide operating voltage for the various hardware devices on the management controller 10. The communication interface 14 can create a data transmission channel between the management controller 10 and external devices. The communication protocol it follows can be any communication protocol applicable to the technical solution of this invention, and is not specifically limited here. The input / output interface 15 is used to acquire external input data or output data to the outside world. Its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0186] This invention also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the firmware configuration verification method described in the above embodiments.

[0187] Since the embodiments of the computer program product part correspond to the embodiments of the firmware configuration verification method part, please refer to the description of the embodiments of the firmware configuration verification method part for the embodiments of the computer program product part, and will not be repeated here.

[0188] This invention also provides a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the firmware configuration verification method described in the above embodiments.

[0189] Since the embodiments of the computer-readable storage medium portion correspond to the embodiments of the firmware configuration verification method portion, the embodiments of the storage medium portion are described in the description of the embodiments of the firmware configuration verification method portion, and will not be repeated here.

[0190] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

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

[0192] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0193] The firmware configuration verification method, apparatus, management controller, and storage medium provided by this invention have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this invention. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and core ideas of this invention. It should be noted that those skilled in the art can make various improvements and modifications to this invention without departing from its principles, and these improvements and modifications also fall within the protection scope of this invention.

Claims

1. A firmware configuration verification method, characterized by, The method is applied to a management controller, which has a main firmware storage area, a backup firmware storage area, and a common storage area. The main firmware storage area stores a first firmware configuration file, the backup firmware storage area stores a second firmware configuration file, and the common storage area stores a common firmware configuration file. The method includes: During the startup phase, the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are compared to obtain the comparison result. If the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, then the system will boot based on the identical firmware configuration files. If the comparison result shows that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, then the system will start according to the common firmware configuration file. The management controller has a main memory and a backup memory. Both the main memory and the backup memory have private partitions and public partitions. The private partition of the main memory is set as the main firmware storage area, and the private partition of the backup memory is set as the backup firmware storage area. The public partition of both the main memory and the backup memory is used to set as the public storage area. The private partitions of the main memory and the backup memory are used for firmware flashing.

2. The firmware configuration verification method according to claim 1, wherein The main firmware storage area stores the main firmware file, and the backup firmware storage area stores the backup firmware file. Before comparing the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, the method further includes: Determine whether the version number of the main firmware file and the version number of the backup firmware file are the same; If the version numbers are different, then the system will boot based on the backup firmware file and replace the main firmware file with the backup firmware file. If the version numbers are the same, then each data segment in the main firmware file is compared with each data segment in the backup firmware file to determine whether the main firmware file and the backup firmware file have the same data. If the main firmware file and the backup firmware file have the same data, then it is determined that the boot process will be based on the main firmware file. If the main firmware file and the backup firmware file have inconsistent data, then the system will determine to start based on the backup firmware file and replace the main firmware file with the backup firmware file. When determining the firmware file to be used for startup, the step of comparing the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file is performed.

3. The firmware configuration verification method according to claim 2, wherein The step of comparing each data segment in the main firmware file with each data segment in the backup firmware file to determine whether the main firmware file and the backup firmware file have consistent data includes: The first data segment in the read-only partition of the main firmware storage area is taken as the data segment to be processed, and it is determined whether the data segment to be processed is a header file; If the data segment to be processed is not a header file, then the next data segment in the read-only partition of the main firmware storage area is taken as the data segment to be processed, and the process proceeds to the step of determining whether the data segment to be processed is a header file. If the data segment to be processed is a header file, then determine whether the data format of the data segment to be processed is a file system format; If the data format of the data segment to be processed is not the file system format, then the next data segment in the read-only partition of the main firmware storage area is taken as the data segment to be processed, and the process proceeds to the step of determining whether the data segment to be processed is a header file. If the data format of the data segment to be processed is the file system format, then the offset value of the data segment to be processed in the read-only partition is determined, and the corresponding data segment in the read-only partition of the spare firmware storage area is taken as the data segment to be compared according to the offset value. Calculate the first check value of the data segment to be processed, calculate the second check value of the data segment to be compared, and determine whether the first check value and the second check value are the same; If the first verification value and the second verification value are different, it is determined that the main firmware file and the backup firmware file are inconsistent. If the first check value and the second check value are the same, then determine whether all data segments in the read-only partition of the main firmware storage area have been processed; If the data segment in the read-only partition of the main firmware storage area has not been processed, the next data segment in the read-only partition of the main firmware storage area will be used as the data segment to be processed, and the process will proceed to the step of determining whether the data segment to be processed is a header file. If all data segments in the read-only partition of the main firmware storage area have been processed, then the main firmware file and the backup firmware file are determined to be consistent.

4. The firmware configuration verification method according to any one of claims 1 to 3, characterized by, The comparison of the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file to obtain the comparison result includes: Determine whether the first firmware configuration file and the common firmware configuration file are the same; If the first firmware configuration file and the common firmware configuration file are the same, a comparison result indicating that the first firmware configuration file and the common firmware configuration file are the same is generated; If the first firmware configuration file and the common firmware configuration file are different, then determine whether the second firmware configuration file and the common firmware configuration file are the same; If the second firmware configuration file and the common firmware configuration file are the same, a comparison result indicating that the second firmware configuration file and the common firmware configuration file are the same is generated; If the second firmware configuration file and the common firmware configuration file are different, then determine whether the first firmware configuration file and the second firmware configuration file are the same; If the first firmware configuration file and the second firmware configuration file are the same, a comparison result indicating that the first firmware configuration file and the second firmware configuration file are the same is generated; If the first firmware configuration file and the second firmware configuration file are different, a comparison result is generated indicating that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different.

5. The firmware configuration verification method according to claim 4, wherein Also includes: If the first firmware configuration file and the second firmware configuration file are the same, then the common firmware configuration file is updated using the first firmware configuration file; If the comparison result shows that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different, then the first firmware configuration file and the second firmware configuration file are updated using the common firmware configuration file.

6. The firmware configuration verification method according to claim 4, wherein If the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file, then booting is performed based on the identical firmware configuration files, including: If the comparison result shows that the first firmware configuration file and the second firmware configuration file are the same, then the system is started according to the first firmware configuration file. If the comparison result shows that the first firmware configuration file and the common firmware configuration file are the same, then the system is started according to the first firmware configuration file; If the comparison result shows that the second firmware configuration file and the common firmware configuration file are the same, then the system will be started according to the second firmware configuration file.

7. A firmware configuration verification apparatus characterized by comprising: An apparatus for use with a management controller, the management controller having a main firmware storage area, a backup firmware storage area, and a common storage area, wherein the main firmware storage area stores a first firmware configuration file, the backup firmware storage area stores a second firmware configuration file, and the common storage area stores a common firmware configuration file, the apparatus comprising: The comparison module is used to compare the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file during the startup phase to obtain a comparison result. The first startup module is configured to start the system based on the same firmware configuration file if the comparison result shows that there is a pair of identical firmware configuration files among the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file. The second startup module is used to start the system based on the common firmware configuration file if the comparison result shows that the first firmware configuration file, the second firmware configuration file, and the common firmware configuration file are all different. The management controller has a main memory and a backup memory. Both the main memory and the backup memory have private partitions and public partitions. The private partition of the main memory is set as the main firmware storage area, and the private partition of the backup memory is set as the backup firmware storage area. The public partition of both the main memory and the backup memory is used to set as the public storage area. The private partitions of the main memory and the backup memory are used for firmware flashing.

8. A management controller, characterized in that, include: Memory, used to store computer programs; A processor for implementing the firmware configuration verification method as described in any one of claims 1 to 6 when executing the computer program.

9. A non-volatile computer-readable storage medium, characterized in that, The non-volatile computer-readable storage medium stores computer-executable instructions, which, when loaded and executed by a processor, implement the firmware configuration verification method as described in any one of claims 1 to 6.

Images