A system software verification method and device

Abstract

The embodiment of the present invention provides a system software verification method and device, which relates to the field of system software verification, and solves the problem of being unable to quickly verify whether the system software version of the train control center has been successfully upgraded. The main technical scheme of the present invention is: deploying a standard version of the system software compression package and a standard version of the configuration data compression package into a verification folder and calculating the first file fingerprint of the verification folder; obtaining the folder to be verified corresponding to the system software upgrade and calculating the second file fingerprint of the folder to be verified, wherein the folder to be verified includes the system software of the version to be verified and the configuration data of the version to be verified; comparing the first file fingerprint and the second file fingerprint to see if they are the same; if they are the same, outputting that the system software upgrade is successful; if they are not the same, searching for the file corresponding to the failure of the system software upgrade. The embodiment of the present invention is used to quickly verify whether the system software version has been successfully upgraded.

Description

Technical Field

[0001] The present invention relates to the field of system software verification, and in particular to a system software verification method and device. Background Art

[0002] With the rapid development of my country's social economy, higher requirements have been put forward for the transportation capacity of railways. Improving the speed of trains is the key to improving the railway operation capacity, and the train operation control system is an important technical support means to achieve the goal. The CTCS-2 train control system is currently widely used in China. Among them, the train control center, as the core ground safety equipment of the CTCS-2 train control system, plays a vital role in the efficient and safe operation of trains.

[0003] For the train control center, the normal operation of its internal system functions and the stability of its external interfaces require the support of system software. For on-site debugging personnel, it is usually necessary to compare the version number of the upgraded standard system software version with the version number of the system software to be verified. If they are consistent, it means that the system software upgrade is successful; however, the debugging personnel found that although the version number of the system software version is consistent, errors still occur during the use of the software; in response to this problem, the debugging personnel extracted a part of the folders from the system software version with the consistent version number and compared them with the folders corresponding to the standard system software in detail, and found that some files in some folders were missing and some files in some folders were changed; it was inferred that the errors in the use of the software may be caused by the omission and change of files in the folders. However, since the number of folders corresponding to the system software version of the train control center is very large, it is impossible to manually check the missing and changed files one by one. Therefore, there is an urgent need for a method that can quickly verify whether the system software version of the train control center has been successfully upgraded. Summary of the invention

[0004] In view of this, the present invention provides a system software verification method, which can quickly verify whether the system software version of the train control center is successfully upgraded.

[0005] To solve the above technical problems, the embodiments of the present invention provide the following technical solutions:

[0006] In a first aspect, an embodiment of the present invention provides a system software verification method, comprising:

[0007] Deploy a standard version of the system software compressed package and a standard version of the configuration data compressed package into a verification folder and calculate a first file fingerprint of the verification folder;

[0008] Obtaining a folder to be verified corresponding to the system software after the upgrade and calculating a second file fingerprint of the folder to be verified, wherein the folder to be verified includes the system software of the version to be verified and configuration data of the version to be verified;

[0009] comparing the first file fingerprint and the second file fingerprint to see whether they are the same;

[0010] If they are the same, the output system software upgrade is successful;

[0011] If they are not the same, search for the file that caused the system software upgrade failure.

[0012] In a second aspect, an embodiment of the present invention provides a system software verification device, including:

[0013] A first calculation module, used for deploying a standard version of the system software compressed package and a standard version of the configuration data compressed package into a verification folder and calculating a first file fingerprint of the verification folder;

[0014] A second calculation module is used to obtain a folder to be verified corresponding to the system software after the upgrade and calculate a second file fingerprint of the folder to be verified, wherein the folder to be verified includes the system software of the version to be verified and the configuration data of the version to be verified;

[0015] A comparison module, comparing the first file fingerprint and the second file fingerprint to see whether they are the same;

[0016] The output module outputs that the system software upgrade is successful if the first file fingerprint is the same as the second file fingerprint;

[0017] The first search module searches for a file corresponding to the failure of the system software upgrade if the first file fingerprint is different from the second file fingerprint.

[0018] In a third aspect, an embodiment of the present invention provides a storage medium, which includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the method in one or more of the above-mentioned technical solutions.

[0019] In a fourth aspect, an embodiment of the present invention provides a processor, which is used to run a program, wherein the program executes the method in one or more of the above-mentioned technical solutions when running.

[0020] The present invention provides a method for verifying the version of the system software of a train control center. First, a standard version of the system software compression package and a standard version of the configuration data compression package are deployed into a verification folder, so that the first file fingerprint of the verification folder can be calculated; wherein the calculated first file fingerprint can be used as a comparison standard for whether the system software is successfully upgraded; then the folder to be verified corresponding to the system software upgrade is obtained, and the second file fingerprint of the folder to be verified is calculated; wherein the folder to be verified includes the system software of the version to be verified and the configuration data of the version to be verified. By comparing the first file fingerprint with the second file fingerprint, it can be quickly determined whether the file in the folder to be verified has changed; if the first file fingerprint is the same as the second file fingerprint, it means that the system software upgrade is successful; if they are not the same, the corresponding file that caused the failure of the system software upgrade is searched. Compared with the prior art, which only compares the system software version number and causes errors in the software during operation, the present invention can quickly determine whether there is any change in the corresponding folder to be verified after the system software is upgraded by comparing the first file fingerprint of the verification folder and the second file fingerprint of the folder to be verified; if there is no change, it means that the system upgrade is successful. If there is a change, the corresponding file can be further searched, which helps to improve the efficiency of verifying the system software. At the same time, the comparison based on file fingerprints also helps to improve the accuracy of verification.

[0021] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] By reading the detailed description of the preferred embodiment below, various other advantages and benefits will become clear to those of ordinary skill in the art. The accompanying drawings are only used for the purpose of illustrating the preferred embodiment and are not considered to be limitations of the present invention. In addition, the same reference symbols are used to represent the same components throughout the accompanying drawings.

[0023] Figure 1 The following is a flow chart of the verification method of the system software in the embodiment of the present invention. Figure 1 ;

[0024] Figure 2 The following is a flow chart of the verification method of the system software in the embodiment of the present invention. Figure 2 ;

[0025] Figure 3 It is the verification operation interface of the system software in the embodiment of the present invention Figure 1 ;

[0026] Figure 4It is the verification operation interface of the system software in the embodiment of the present invention Figure 2 ;

[0027] Figure 5 It is the verification operation interface of the system software in the embodiment of the present invention Figure 3 ;

[0028] Figure 6 The structure of the verification device of the system software in the embodiment of the present invention is shown in FIG. Figure 1 ;

[0029] Figure 7 The structure of the verification device of the system software in the embodiment of the present invention is shown in FIG. Figure 2 . DETAILED DESCRIPTION

[0030] In order to make the purpose, technical scheme and advantages of the embodiments of the present invention clearer, exemplary embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0031] In the description of the embodiments of the present invention, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of the present invention, "plurality" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0032] The method in the embodiment of the present invention is described in detail below.

[0033] Figure 1 The flowchart of the verification method of the system software in the embodiment of the present invention is shown as follows Figure 1 , see Figure 1 As shown, the method may include:

[0034] S101: deploy a standard version of the system software compressed package and a standard version of the configuration data compressed package into a verification folder and calculate a first file fingerprint of the verification folder.

[0035] Among them, system software refers to the system that controls and coordinates computers and external devices and supports the development and operation of application software. It is a collection of various programs that do not require user intervention. Its main function is to schedule, monitor and maintain computer systems; it is responsible for managing various independent hardware in the computer system so that they can work in coordination. System software allows computer users and other software to treat the computer as a whole without having to consider how each underlying hardware works. The standard version of the system software compression package refers to the system software compression package that can be used as a verification template. After the system software is upgraded, the standard version of the system software can be used to verify whether the system software has been upgraded successfully.

[0036] Among them, the configuration data of the standard version is the data required for configuring the system software.

[0037] Specifically, the system software can be the system software of LKD2-KA (i.e., the train control center system software), the system software of ILOCK-E (i.e., the fully electronic computer interlocking system software), the system software of ILOCK (i.e., the computer interlocking system software), the system software of FZk-CTC (i.e., the centralized dispatching system software), the system software of CSM-KA (i.e., the railway signal centralized monitoring system software), the system software of TDCS (i.e., the train dispatching and command system software), the system software of STP-KA (i.e., the wireless shunting locomotive signal and monitoring system software), etc.

[0038] It should be noted that the process of deploying the standard version of the system software compressed package and the standard version of the configuration data compressed package to the verification folder is consistent with the system software upgrade process. Generally, after obtaining the standard version of the system software compressed package and the standard version of the configuration data compressed package, a verification folder will be automatically generated. The verification folder is a folder used to verify whether the system software has been damaged during the upgrade process, where the file damage includes the file being changed or the file being omitted.

[0039] The first file fingerprint is a unique identifier of the verification file, which can be obtained through a hash algorithm, such as MD5 Message-Digest Algorithm, MD4 Message-Digest Algorithm, Secure Hash Algorithm 1 (SHA-1), and can also be obtained through cyclic redundancy check technology (CRC). Among them, the MD5 Message-Digest Algorithm is a widely used cryptographic hash function that can generate a 128-bit (16-byte) hash value to ensure that information transmission is complete and consistent.

[0040] S102: Obtain the folder to be verified corresponding to the system software upgrade and calculate the second file fingerprint of the folder to be verified.

[0041] The folder to be verified includes the system software of the version to be verified and the configuration data of the version to be verified. Generally, after obtaining the system software of the version to be verified and the configuration data of the version to be verified, a folder to be verified is automatically generated, and the system software of the version to be verified and the configuration data of the version to be verified are moved to the folder to be verified.

[0042] It should be noted that the system software of the version to be verified and the configuration data of the version to be verified in the folder to be verified are obtained from the system in which the system software has been installed. For example, the system software of LKD2-KA (ie, the train control center system software) and the configuration data corresponding to the system software are obtained from the train control center.

[0043] Among them, the second file fingerprint is a unique identifier of the file to be verified, which can be obtained through a hash algorithm, for example: MD5 Message-Digest Algorithm, MD4 Message-Digest Algorithm, Secure Hash Algorithm 1 (SHA-1), and can also be obtained through cyclic redundancy check technology (Cyclic Redundancy Check, CRC).

[0044] It should be noted that the calculated first file fingerprint and second file fingerprint may be presented in a variety of ways, such as numbers, letters, a combination of numbers and letters, and codes, and the specific presentation method is not limited here.

[0045] S103: Compare the first file fingerprint and the second file fingerprint to see if they are the same.

[0046] By comparing the first file fingerprint and the second file fingerprint, it can be determined whether the system software and configuration data in the folder to be verified have been changed or omitted. If the first file fingerprint is the same as the second file fingerprint, it means that the system software and configuration data in the folder to be verified have not been changed or omitted; if the first file fingerprint is different from the second file fingerprint, it means that the system software and configuration data in the folder to be verified have been changed or omitted.

[0047] S104: If the first file fingerprint is the same as the second file fingerprint, output that the system software upgrade is successful.

[0048] If the first file fingerprint is the same as the second file fingerprint, it means that the files related to the system software and configuration data have not been changed or omitted during the upgrade process of the system software, thereby quickly determining that the system software upgrade is successful.

[0049] S105: If the first file fingerprint is different from the second file fingerprint, searching for the file that causes the system software upgrade failure.

[0050] If the first file fingerprint is different from the second file fingerprint, it means that the files related to the system software and configuration data are changed or omitted during the upgrade process, that is, the system software upgrade fails. After determining that the system software upgrade fails, it is necessary to find the file that caused the system software upgrade failure; the file that caused the system software upgrade failure can be found by matching the file fingerprints of each file in the verification folder and the folder to be verified. The staff can re-upgrade the system software based on the found files.

[0051] The present invention provides a method for verifying the version of the system software of a train control center. First, a standard version of the system software compression package and a standard version of the configuration data compression package are deployed into a verification folder, so that the first file fingerprint of the verification folder can be calculated; wherein the calculated first file fingerprint is a comparison standard for whether the system software is successfully upgraded; then the folder to be verified corresponding to the system software upgrade is obtained, and the second file fingerprint of the folder to be verified is calculated; wherein the folder to be verified includes the system software of the version to be verified and the configuration data of the version to be verified. By comparing the first file fingerprint with the second file fingerprint, it can be quickly determined whether the file in the folder to be verified has changed; if the first file fingerprint is the same as the second file fingerprint, it means that the system software upgrade is successful; if they are not the same, the corresponding file that caused the failure of the system software upgrade is searched. Compared with the prior art, which only compares the system software version number and causes errors in the software during operation, the present invention can quickly determine whether there is a change in the corresponding folder to be verified after the system software is upgraded by comparing the first file fingerprint of the verification folder with the second file fingerprint of the folder to be verified; if there is no change, it means that the system upgrade is successful. If there is a change, the corresponding file can be further searched, and the file fingerprint of each file in the verification folder and the folder to be verified can be matched to obtain the file that caused the failure of the system software upgrade, which helps the staff to re-upgrade the system software.

[0052] Further, as Figure 1 The embodiment of the present invention provides another method for verifying system software by refining and expanding the method shown.

[0053] Figure 2 FIG. 1 is a flow chart of a method for verifying system software in an embodiment of the present invention. Figure 2 , see Figure 2 As shown, another system software verification method provided by the embodiment of the present invention may include:

[0054] S201. Obtain identification information in a project release form according to a received user instruction.

[0055] Among them, the project release form records the identification information of the latest version of system software.

[0056] The system software identification information may be the version number of the system software and the version number of the configuration data, for example: the version number of the system software is V2.3.0, and the version number of the configuration data is V1.0.2; or it may be identification information set by the user.

[0057] It should be noted that the identification information in the project release form may be input by the staff; generally, before the system software is upgraded, the staff will record the latest system software version information that needs to be upgraded in the project release form.

[0058] S202: Search, from a data server according to the identification information, for a system software compression package of a standard version and a configuration data compression package of a standard version that match the identification information.

[0059] In the embodiment of the present invention, according to the identification information recorded in the project release form, the most recently updated standard version system software compressed package and the standard version configuration data compressed package in the data server can be searched.

[0060] Furthermore, a connection relationship can be established between the project release form and the data server. For example, a hyperlink with identification information of a standard system software compressed package and a standard version of the configuration data compressed package is recorded in the project release form. The user can obtain the corresponding standard version of the system software compressed package and the standard version of the configuration data compressed package in the server by simply clicking on the hyperlink of the identification information in the project release form.

[0061] S203: deploy a standard version of the system software compressed package and a standard version of the configuration data compressed package into a verification folder and calculate a first file fingerprint of the verification folder.

[0062] Specifically, a corresponding verification sub-folder is established in the verification folder according to the system modules involved in the execution process of the standard version of the system software; according to the preset first search keyword, the standard version of the system software compression package is obtained; the standard version of the system software compression package is decompressed to obtain a first file; according to the keywords contained in the first file, the first file is deployed to the corresponding verification sub-folder by looking up a comparison table, and the comparison table records the keywords associated with the verification sub-folder; according to the preset second search keyword, the standard version of the configuration data compression package is obtained; the standard version of the configuration data compression package is decompressed to obtain a second file; according to the keywords contained in the second file, the second file is deployed to the corresponding verification sub-folder by looking up a comparison table; the first file fingerprint of the verification folder is calculated by using the MD5 information digest algorithm.

[0063] It should be noted that system software generally involves multiple system modules, and the upgrade process of system software is also the upgrade process of each system module. Each system module corresponds to a folder; therefore, in the deployment process of the verification folder, it is necessary to first establish a verification subfolder according to the system modules involved in the system software.

[0064] It should be noted that, since there is only one system software compression package for a version, the corresponding preset first search keyword is also one, and the corresponding standard version of the system software compression package can be searched according to the preset first search keyword. For example: according to the preset first search keyword "TCPS", the system software compression package named "LKD2-TCPS_Bproduct_V2.2.6.0.4.rar" can be searched. It should be noted that in the process of upgrading different versions, the corresponding standard version of the system software compression package can be searched according to the preset first search keyword "TCPS".

[0065] In an embodiment of the present invention, the first file obtained by decompressing the standard version of the system software compressed package can be one or more. The decompression process of the compressed package can be to decompress the file or to decompress it to the current folder. Decompressing the file means directly decompressing all the files in the compressed package, that is, after decompressing the standard version of the system software compressed package, multiple first files are directly obtained. Decompressing to the current folder means decompressing all the files in the file into a folder, that is, after decompressing the standard version of the system software compressed package, a folder is obtained, and multiple first files are stored in the folder.

[0066] In an embodiment of the present invention, the search comparison table records keywords associated with the verification subfolder, and these keywords are arranged in a certain order. The folders of different levels in the first file can be searched in sequence according to the order of the keywords. For example, the keywords can be arranged as setup; self-starting image; rack version; up; UPAPP.out, bootrom.sys, UPBIT.out, vxWorks. Among them, first search for the folder with the keyword "setup" in the first file, enter the "setup" folder to search for the folder with the keyword "self-starting image", enter the "self-starting image" folder to search for the folder with the keyword "rack version", enter the "rack version" folder to search for the folder with the keyword "up", enter the "up" folder to obtain the four files UPAPP.out, bootrom.sys, UPBIT.out, and vxWorks, and copy and paste these four files into the corresponding verification subfolder. Among them, the folder with the keyword "setup" is at the first level; the folder with the keyword "self-starting image" is at the second level; the folder with the keyword "rack version" is at the third level; the folder with the keyword "up" is at the fourth level; the folder with the keywords "UPAPP.out, bootrom.sys, UPBIT.out, vxWorks" is at the fifth level.

[0067] It should be noted that there may be multiple configuration data compression packages corresponding to a version of system software, so there may also be multiple corresponding preset second search keywords. According to the preset second search keywords, the configuration data compression packages of the corresponding standard versions can be searched. For example: according to the preset second search keywords "VLE" and "DVCOM", the configuration data compression packages named "Nanhua_VLE_V1.0.0.rar" and "Nanhua_DVCOM_V1.0.0.rar" can be searched.

[0068] S204: Obtain the folder to be verified corresponding to the system software upgrade and calculate the second file fingerprint of the folder to be verified.

[0069] The folder to be verified includes the system software of the version to be verified and the configuration data of the version to be verified. Figure 3 As shown, you can click "Request Version Information" to obtain the corresponding folder to be verified after the system software is upgraded.

[0070] S205: Compare the first file fingerprint and the second file fingerprint to see whether they are the same.

[0071] like Figure 3 As shown, you can click "Verify with local file" to start comparing the first file fingerprint with the second file fingerprint.

[0072] S206: If the first file fingerprint is the same as the second file fingerprint, output that the system software upgrade is successful.

[0073] like Figure 4 As shown, after the first file fingerprint is compared to the second file fingerprint and it is found that the fingerprint is the same, a pop-up box of "Verification Successful" can be popped up to inform the staff that the system software upgrade is successful. After the staff clicks the OK button, the verification work is completed.

[0074] S207: If they are not the same, obtain the verification subfolders in the verification folder, and calculate the third file fingerprint of each verification subfolder.

[0075] like Figure 5 As shown, after comparing the first file fingerprint and the second file fingerprint, a pop-up box of "Verification Failed" can be popped up to inform the staff that the system software upgrade failed. After the staff clicks the OK button, the next step of calculation is performed to feedback the error file.

[0076] It should be noted that the verification subfolder may be a first-level verification subfolder in the verification folder.

[0077] The third file fingerprint is a unique identifier of each check sub-file, which can be obtained through a hash algorithm, such as MD5 Message-Digest Algorithm, MD4 Message-Digest Algorithm, Secure Hash Algorithm 1 (SHA-1), and can also be obtained through a cyclic redundancy check (CRC) technology.

[0078] S208: Obtain subfolders to be verified in the folder to be verified, and calculate the fourth file fingerprint of each subfolder to be verified.

[0079] It should be noted that the subfolder to be verified may be a verification subfolder of the first level in the verification folder.

[0080] Among them, the fourth file fingerprint is a unique identifier of each sub-file to be verified, which can be obtained through a hash algorithm, for example: MD5 Message-Digest Algorithm, MD4 Message-Digest Algorithm, Secure Hash Algorithm 1 (SHA-1), and can also be obtained through a cyclic redundancy check technology (Cyclic Redundancy Check, CRC).

[0081] S209: Match the third file fingerprint and the fourth file fingerprint, and obtain the third file fingerprint and the fourth file fingerprint that are not matched successfully.

[0082] In the embodiment of the present invention, the missing folder or the changed folder can be found by matching the third file fingerprint and the fourth file fingerprint.

[0083] Exemplarily, the situation in which changes occur in the folder to be verified is that the calculated third file fingerprint is 11, 12, 13, and 14; the calculated fourth file fingerprint is 12, 11, 16, and 17, and there are no 16 and 17 in the third file. This means that the folders corresponding to 16 and 17 in the fourth file fingerprint are the changed folder to be verified, and the result is that the third file fingerprints 13 and 14 and the fourth file fingerprints 16 and 17 do not match successfully.

[0084] Exemplarily, the omission occurs in the folder to be verified as follows: the calculated third file fingerprint is 11, 12, 13, 14; the calculated fourth file fingerprint is 11, 12, 13, and there is no 14 in the fourth file fingerprint. This means that the folder corresponding to the file fingerprint 14 is omitted in the folder to be verified, and the result is that the third file fingerprint 14 fails to match.

[0085] It should be noted that the calculated third file fingerprint and fourth file fingerprint may be presented in a variety of ways such as numbers, letters, a combination of numbers and letters, and codes, and the specific presentation method is not limited here.

[0086] S210: Determine the error correction file corresponding to the third file fingerprint that fails to match and the error file corresponding to the fourth file fingerprint.

[0087] In an embodiment of the present invention, the error correction file corresponding to the third file fingerprint that failed to match and the error file corresponding to the fourth file fingerprint can both be fed back. Among them, feeding back both the error file and the error correction file allows the staff to intuitively view the correct files in the verification folder corresponding to the error files in the files to be verified, as well as the files missed in the folder to be verified, so that the staff can quickly find the problem and correct it as soon as possible.

[0088] The present invention provides a method for verifying the system software version of a train control center. First, the identification information in the project release form is obtained according to the received user instruction. Then, according to the identification information, a standard version of the system software compression package and a standard version of the configuration data compression package matching the identification information are searched from the data server. The whole process is completely automated by the program, which can avoid manual operation to extract the wrong system software compression package and configuration data compression package, thereby causing the failure of the later system software verification. In the present invention, by comparing the first file fingerprint of the verification folder and the second file fingerprint of the folder to be verified, it can be quickly determined whether the corresponding folder to be verified has changed after the system software is upgraded; if there is no change, it means that the system upgrade is successful. If there is a change, the third file fingerprint of each verification subfolder and the fourth file fingerprint of the subfolder to be verified are further calculated. By matching the third file fingerprint and the fourth file fingerprint, the error file in the folder to be verified and the correct file corresponding to the error file and the missing file can be accurately fed back, so that the staff can quickly find the problem and correct it as soon as possible.

[0089] Furthermore, in combination with the actual process of deploying a standard version of a system software compression package and a standard version of a configuration data compression package into a verification folder, an embodiment of the present invention provides a method for deploying a verification folder.

[0090] Methods for deploying verification files include:

[0091] Preparation:

[0092] Obtain identification information in the project release form according to the received user instruction;

[0093] According to the identification information, search the data server for the standard version of the system software compression package and the standard version of the configuration data compression package that match the identification information; among them, the standard version of the system software compression package obtained is LKD2-TCPS_Bproduct_V2.2.6.0.4.rar, and the standard version of the configuration data compression package obtained is Nanhua_BOOL_V1.0.1.rar, Nanhua_DVCOM_V1.0.0.rar, Nanhua_info_V1.0.3.rar, and Nanhua_VLE_V1.0.0.rar.

[0094] Deploy the obtained standard version system software compressed package and standard version configuration data compressed package to the sub-directory version verification folder in the MAIN folder.

[0095] The standard system software deployment process of the lower computer:

[0096] S301. Create 6 verification sub-folders in the verification folder.

[0097] Six verification subfolders are created, namely, A series DVCOM, A series upper module, A series lower module, B series DVCOM, B series upper module, and B series lower module. It should be noted that the verification folder only contains six verification subfolders, and no other files exist.

[0098] S302. Fuzzy search the compressed package with the suffix .rar according to the preset keyword "TCPS" to obtain LKD2-TCPS_Bproduct_V2.2.6.0.4.rar, which is a standard version of the system software compressed package.

[0099] S303, decompressing the compressed package in step S302, and obtaining the standard version system software file of the lower computer.

[0100] S304. Accurately search for folders with the keyword "setup".

[0101] S305. Enter the "setup" folder and accurately search for the folder with the keyword "self-starting image".

[0102] S306. Enter the "self-starting image" folder and accurately search for the folder with the keyword "rack version".

[0103] S307. Enter the "Rack Version" folder and accurately search for folders with the keywords "UP", "down", and "dvcom".

[0104] S308. Enter the "UP" folder, accurately search for files named "uppapp.out", "bootrom.sys", "upbit.out", and "vxworks", and copy the four files here to the verification subfolders "A series module" and "B series module" folders respectively.

[0105] S309. Return to step S307, enter the "down" folder, accurately search for files named "downapp.out", "bootrom.sys", "vxworks", and "downbit.out", and copy the four files here to the "A system module" and "B system module" folders of the verification subfolder respectively.

[0106] S310, return to step S307, enter the "dvcom" folder, accurately search for files named "vxworks" and "bootrom.sys", and copy the two files here to the "A series DVCOM" and "B series DVCOM" folders of the verification subfolder respectively.

[0107] S311. Complete the lower computer standard system software deployment process and enter the VLE configuration file deployment process.

[0108] VLE configuration file deployment process:

[0109] S312. Fuzzy search the compressed package with the suffix .rar according to the preset keyword "VLE" to obtain Nanhua_VLE_V1.0.0.rar, which is a compressed package of VLE configuration files.

[0110] S313. Decompress the compressed package in step S312 to obtain the VLE configuration file.

[0111] S314. Accurately search for folders with the keywords "A-UP", "A-DOWN", "B-UP", and "B-DOWN".

[0112] S315. If the four folders of the keywords "A-UP", "A-DOWN", "B-UP", and "B-DOWN" are accurately searched, go to step S316.

[0113] S316. If the four folders of the keywords "A-UP", "A-DOWN", "B-UP" and "B-DOWN" cannot be accurately searched, go to step S316.

[0114] S317, decompress the compressed package in step S312, and fuzzy search for files with the keyword "VLE".

[0115] S318. Enter the "VLE" folder, accurately search for the four folders with the keywords "A-UP", "A-DOWN", "B-UP", and "B-DOWN", and enter step S319.

[0116] S319. Enter the "A-UP" folder, accurately search for files named "sysgenst.ini", "synvp2.ini", and "uesrboot.cfg", and copy the three files here to the "A-UP Module" folder in the verification subfolder.

[0117] S320. Enter the "A-DOWN" folder, accurately search for files named "hostcfg.ini", "sysgenst.ini", and "uesrboot.cfg", and copy the three files here to the "A-series module" folder in the verification subfolder.

[0118] S321. Enter the "B-UP" folder, accurately search for files named "sysgenst.ini", "synvp2.ini", and "uesrboot.cfg", and copy the three files here to the "A Series Module" folder in the verification subfolder.

[0119] S322. Enter the "B-DOWN" folder, accurately search for files named "hostcfg.ini", "sysgenst.ini", and "uesrboot.cfg", and copy the three files here to the "B-DOWN" folder in the verification subfolder.

[0120] S323. Complete the VLE configuration file deployment process and enter the DVCOM configuration file deployment process.

[0121] DVCOM configuration file deployment process:

[0122] S324. Fuzzy search the compressed package with the suffix .rar according to the preset keyword "DVOCM" to obtain Nanhua_DVOCM_V1.0.0.rar, which is a compressed package of DVCOM configuration files.

[0123] S325 . Decompress the compressed package in step S324 to obtain the DVCOM configuration file.

[0124] S326. Accurately search for folders with the keyword "DVCOM"; if there are 2 folders containing the keyword "DVCOM", go to step S327; if there is 1 folder containing the keyword "DVCOM", go to step S331; if there are 3 folders containing the keyword "DVCOM", go to step S332.

[0125] S327. Fuzzy search for folders containing the keywords "A, D" at the same time.

[0126] S328. Enter the folder containing the keywords "A, D" and accurately search for folders with file names such as "fsfb.ini", "leu_map.ini", "leu.ini", "userboot.cfg", "sysgenet.ini", and "synvp2.ini", and copy the six files here to the "A Series DVCOM" folder in the verification folder.

[0127] Among them, if the two files "leu.ini" and "leu_map.ini" cannot be found accurately, the processing of these two files will be abandoned.

[0128] S329. Fuzzy search for folders containing the keywords "B, D" at the same time.

[0129] S330. Enter the folder containing the keywords "B, D" and accurately search for folders with file names of "fsfb.ini", "leu_map.ini", "leu.ini", "userboot.cfg", "sysgenet.ini", and "synvp2.ini", and copy the six files here to the "B Series DVCOM" folder in the verification folder.

[0130] Among them, if the two files "leu.ini" and "leu_map.ini" cannot be found accurately, the processing of these two files will be abandoned.

[0131] S331, enter the folder containing the keyword "DVCOM"; if there are only two folders containing the keyword "DVCOM" in the current path, repeat steps S327 to S330; if there are only at least 3 folders containing the keyword "DVCOM" in the current path, enter step S332.

[0132] S332. Calculate the number of subfolders contained in the folder containing the keyword "DVCOM", and divide the total number of subfolders by 2.

[0133] S333. If the result is 2, rename the A series DVCOM folder in the verification folder to "A series DVCOM-1", "A series DVCOM-2", and rename the B series DVCOM folder to "B series DVCOM-1", "B series DVCOM-2"; if the result is 3, rename the "A series DVCOM" folder in the verification folder to "A series DVCOM-1", "A series DVCOM-2", "A series DVCOM-3", and rename the "B series DVCOM" folder to "B series DVCOM-1", "B series DVCOM-2". Rename them to “B Series DVCOM-1”, “B Series DVCOM-2”, “B Series DVCOM-3”; if the result is 4, rename the “A Series DVCOM” folder in the verification folder to “A Series DVCOM-1”, “A Series DVCOM-2”, “A Series DVCOM-3”, “A Series DVCOM-4”, and at the same time rename the “B Series DVCOM” folder to “B Series DVCOM-1”, “B Series DVCOM-2”, “B Series DVCOM-3”, “B Series DVCOM-4”.

[0134] It should be noted that here "A series DVCOM" is renamed as "A series DVCOM-1" and "A series DVCOM-2". Specifically, after copying and pasting "A series DVCOM", two "A series DVCOM" are obtained, and these two "A series DVCOM" are renamed as "A series DVCOM-1" and "A series DVCOM-2" respectively.

[0135] It should be noted that here "B series DVCOM" is renamed as "B series DVCOM-1" and "B series DVCOM-2". Specifically, after copying and pasting "B series DVCOM", two "B series DVCOM" are obtained. These two "B series DVCOM" are renamed as "B series DVCOM-1" and "B series DVCOM-2" respectively.

[0136] S334. Fuzzy search for all folders containing the keyword "A"; if the folder name contains the keyword "1" and the number of sub-files contained in the folder is greater than the number of sub-files contained in all other folders containing the keyword "A", go to step S335; if the folder name contains the keyword "M" and the number of sub-files contained in the folder is greater than the number of sub-files contained in all other folders containing the keyword "A", go to step S343.

[0137] S335. Enter the folder containing the keyword "1", accurately search for folders with file names such as "fsfb.ini", "leu_map.ini", "leu.ini", "userboot.cfg", "sysgenet.ini", "synvp2.ini", and "ms_con.ini", and copy the seven files here to the "A Series DVCOM-1" file in the verification subfolder.

[0138] S336. Enter the folder containing the keyword "2", accurately search for folders with file names "leu.ini", "userboot.cfg", "sysgenet.ini", and "ms_con.ini", and copy the four files here to the "A Series DVCOM-2" file in the verification sub-file.

[0139] S337. Enter the folder containing the keyword "3", accurately search for folders with file names "leu.ini", "userboot.cfg", "sysgenet.ini", and "ms_con.ini", and copy the four files here to the "A Series DVCOM-3" file in the verification subfolder.

[0140] S338. Enter the folder containing the keyword "4", accurately search for folders with file names such as "leu.ini", "userboot.cfg", "sysgenet.ini", and "ms_con.ini", and copy the four files here to the "A Series DVCOM-4" file in the verification subfolder.

[0141] S339. Enter the folder containing the keyword "1", accurately search for file names such as "fsfb.ini", "leu_map.ini", "leu.ini", "userboot.cfg", "sysgenet.ini", "synvp2.ini", and "ms_con.ini", and copy the seven files here to the "B Series DVCOM-1" file in the verification subfolder.

[0142] S340. Enter the folder containing the keyword "2", accurately search for folders with file names "leu.ini", "userboot.cfg", "sysgenet.ini", and "ms_con.ini", and copy the four files here to the "B Series DVCOM-2" file in the verification subfolder.

[0143] S341. Enter the folder containing the keyword "3", accurately search for folders with file names such as "leu.ini", "userboot.cfg", "sysgenet.ini", and "ms_con.ini", and copy the four files here to the "B Series DVCOM-3" file in the verification subfolder.

[0144] S342. Enter the folder containing the keyword "4", accurately search for folders with file names "leu.ini", "userboot.cfg", "sysgenet.ini", and "ms_con.ini", and copy the four files here to the "B Series DVCOM-4" file in the verification subfolder.

[0145] S343. Enter the folder containing the keywords "A, M", accurately search for folders with file names such as "fsfb.ini", "userboot.cfg", "sysgenet.ini", "synvp2.ini", "ms_con.ini", and "bdu.ini", and copy the six files here to the "A Series DVCOM-1" folder in the verification subfolder.

[0146] S344. Enter the folder containing the keyword "A, 1", accurately search for folders with file names "userboot.cfg", "sysgenet.ini", "ms_con.ini", and "bdu.ini", and copy the four files here to the "A Series DVCOM-2" folder in the verification subfolder.

[0147] S345. Enter the folder containing the keyword "A, 2", accurately search for folders with file names "userboot.cfg", "sysgenet.ini", "ms_con.ini", and "bdu.ini", and copy the four files here to the "A Series DVCOM-3" folder in the verification subfolder.

[0148] S346. Enter the folder containing the keywords "A, 3", accurately search for folders with file names "userboot.cfg", "sysgenet.ini", "ms_con.ini", and "bdu.ini", and copy the four files here to the "A Series DVCOM-4" folder in the verification subfolder.

[0149] S347. Enter the folder containing the keywords "B, M", accurately search for folders with file names such as "fsfb.ini", "userboot.cfg", "sysgenet.ini", "synvp2.ini", "ms_con.ini", and "bdu.ini", and copy the six files here to the "B Series DVCOM-1" folder in the verification subfolder.

[0150] S348. Enter the folder containing the keyword "B, 1", accurately search for folders with file names "userboot.cfg", "sysgenet.ini", "ms_con.ini", and "bdu.ini", and copy the four files here to the "B Series DVCOM-2" folder in the verification subfolder.

[0151] S349. Enter the folder containing the keyword "B, 2", accurately search for folders with file names such as "userboot.cfg", "sysgenet.ini", "ms_con.ini", and "bdu.ini", and copy the four files here to the "B Series DVCOM-3" folder in the verification subfolder.

[0152] S350. Enter the folder containing the keyword "B, 3", accurately search for folders with file names "userboot.cfg", "sysgenet.ini", "ms_con.ini", and "bdu.ini", and copy the four files here to the "B Series DVCOM-4" folder in the verification subfolder.

[0153] S351. Enter step S310 in the "Standard System Software Deployment Process for Lower Computers", enter the "dvcom" folder, accurately search for files named "vxworks" and "bootrom.sys", and copy the two files here to all folders containing the keywords "A Series DVCOM" and "B Series DVCOM" in the verification subfolder.

[0154] S352, complete the DVCOM configuration file deployment process and enter the BOOL data deployment process.

[0155] BOOL data deployment process:

[0156] S351. Fuzzy search the compressed package with the suffix .rar according to the preset keyword "BOOL" to obtain Nanhua_BOOL_V1.0.0.rar, which is a BOOL data compressed package.

[0157] S352, decompress the compressed package in step S351 to obtain a BOOL data file.

[0158] S353. Accurately search for folders containing the keyword "BOOLCAD1". If a folder containing the keyword "BOOLCAD1" is accurately found, go to step S356; if no folder containing the keyword "BOOLCAD1" is accurately found, go to step S354.

[0159] S354, decompress the compressed package in step S351, and fuzzy search the folder whose keyword is "BOOL".

[0160] S355. Enter the "BOOL" folder and accurately search for the folder with the keyword "BOOLCAD1".

[0161] S356. Enter the "BOOLCAD1" folder, accurately search for the file name with the keyword "VPICAA.ADS", and copy the "VPICAA.ADS" file to the "A series upper module" and "A series lower module" folders in the verification subfolder.

[0162] S357. Enter the "BOOLCAD1" folder, accurately search for the file name with the keyword "VPICAA.BDS", and copy the "VPICAA.BDS" file to the "B system upper module" and "B system lower module" folders in the verification subfolder.

[0163] S358. Rename the "VPICAA.BDS" in the "B system upper module" and "B system lower module" folders in the verification subfolder to "VPICAA.ADS".

[0164] S359, complete the BOOL data deployment process and enter the offline data deployment process.

[0165] Offline data deployment process:

[0166] S360. Fuzzy search for compressed files with the suffix .rar based on the preset keyword "INFO".

[0167] S361. Decompress the compressed package in step S360 to obtain offline data.

[0168] S362. Accurately search for the folder with the keyword "OutPut"; if found, proceed to step S365; if not found, proceed to step S363.

[0169] S363, decompress the compressed package in step S360, and fuzzy search the folder whose keyword is "INFO".

[0170] S364. Enter the "INFO" folder and search for the folder with the keyword "OutPut" precisely.

[0171] S365. Enter the "OutPut" folder, accurately search for the file name with the keyword "LK2Info.dat", and copy the "LK2Info.dat" file to the "A series module" and "B series module" folders in the verification subfolder;

[0172] S366. Enter the "OutPut" folder, accurately search for the file name with the keyword "DownLK2Info.dat", and copy the "DownLK2Info.dat" file to the "A system module" and "B system module" folders in the verification subfolder.

[0173] S367. Rename the "DownLK2Info.dat" in the "A system module" and "B system module" folders in the verification subfolder to "LK2Info.dat".

[0174] S368. Complete the offline data deployment process.

[0175] It should be noted that the English characters involved in the above steps are not case sensitive.

[0176] Based on the same inventive concept, as an implementation of the above method, an embodiment of the present invention further provides a system software verification device. Figure 6 The structure of the device in the embodiment of the present invention is shown in FIG. Figure 1 , see Figure 6 As shown, the device may include:

[0177] A first calculation module 401 is used to deploy a standard version of the system software compressed package and a standard version of the configuration data compressed package into a verification folder and calculate a first file fingerprint of the verification folder;

[0178] The second calculation module 402 is used to obtain the folder to be verified corresponding to the system software after the upgrade and calculate the second file fingerprint of the folder to be verified, wherein the folder to be verified includes the system software of the version to be verified and the configuration data of the version to be verified;

[0179] A comparison module 403 compares the first file fingerprint calculated by the first calculation module 401 with the second file fingerprint calculated by the second calculation module 402 to see whether they are the same;

[0180] Output module 404, if the first file fingerprint calculated by the first calculation module 401 is the same as the second file fingerprint calculated by the second calculation module 402, then output that the system software upgrade is successful;

[0181] The first search module 405 searches for a file corresponding to the failure of the system software upgrade if the first file fingerprint calculated by the first calculation module 401 is different from the second file fingerprint calculated by the second calculation module 402 .

[0182] Further, such as Figure 7 As shown, the device also includes:

[0183] The acquisition module 406 is used to acquire the identification information in the project release form according to the received user instruction;

[0184] The second search module 407 is used to search the standard version of the system software compressed package and the standard version of the configuration data compressed package that match the identification information from the data server according to the identification information after the first acquisition module 406 acquires the identification information in the project release form.

[0185] Further, such as Figure 7 As shown, the first calculation module 401 includes:

[0186] An establishment submodule 4011 is used to establish a corresponding verification subfolder in the verification folder according to the system modules involved in the execution process of the standard version of the system software after the second search module 407 finds the system software compressed package and the standard version of the configuration data compressed package;

[0187] The first acquisition submodule 4012 is used to acquire the standard version of the system software compressed package according to the preset first search keyword after the verification subfolder is established by the establishment submodule 4011;

[0188] A first decompression submodule 4013 is used to decompress the standard version of the system software compressed package obtained by the first obtaining submodule 4012 to obtain a first file;

[0189] A first deployment submodule 4014 is used to deploy the first file to a corresponding verification subfolder by searching a comparison table according to keywords contained in the first file after the first decompression submodule 4013 obtains the first file, wherein the comparison table records keywords associated with the verification subfolder;

[0190] A second acquisition submodule 4015 is used to acquire the configuration data compression package of the standard version according to a preset second search keyword after the first deployment submodule 4014 deploys the first file to the corresponding verification subfile;

[0191] A second decompression submodule 4016 is used to decompress the configuration data compression package of the standard version to obtain a second file after the second acquisition submodule 4015 acquires the configuration data compression package of the standard version;

[0192] The second deployment submodule 4017 is used to deploy the second file to a corresponding verification subfolder by searching a comparison table according to keywords contained in the second file after the second decompression submodule 4016 obtains the second file;

[0193] The first calculation submodule 4018 is used to deploy the second file to the corresponding verification subfolder in the second deployment submodule 4017, and calculate the first file fingerprint of the verification folder by using the MD5 information digest algorithm.

[0194] Further, such as Figure 7 As shown, the first search module 405 includes:

[0195] The second calculation submodule 4051 is used for obtaining the verification subfolders in the verification folder and calculating the third file fingerprint of each verification subfolder when the first file fingerprint calculated by the first calculation module 401 is different from the second file fingerprint calculated by the second calculation module 402;

[0196] A third verification submodule 4052 is configured to obtain a subfolder to be verified in the folder to be verified and calculate a fourth file fingerprint of each subfolder to be verified when the first file fingerprint calculated by the first calculation module 401 is different from the second file fingerprint calculated by the second calculation module 402;

[0197] The matching submodule 4053 is used to match the third file fingerprint calculated by the second calculation submodule 4051 with the fourth file fingerprint calculated by the third verification submodule 4052, and obtain the third file fingerprint and the fourth file fingerprint that are not matched successfully;

[0198] The determination submodule 4054 is used to determine the error correction file corresponding to the third file fingerprint that the matching submodule 4053 failed to match and the error file corresponding to the fourth file fingerprint.

[0199] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0200] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0201] The algorithm and display provided herein are not inherently related to any particular computer, virtual system or other device. Various general purpose systems can also be used together with the teachings based on this. According to the above description, it is obvious that the structure required for constructing such systems. In addition, the present invention is not directed to any specific programming language either. It should be understood that various programming languages ​​can be utilized to realize the content of the present invention described herein, and the description of the above specific languages ​​is for disclosing the best mode of the present invention.

[0202] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.

[0203] Similarly, it should be understood that in order to streamline the present disclosure and aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of the present invention, various features of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, this disclosed method should not be interpreted as reflecting the intention that the claimed invention requires more features than those explicitly recited in each claim. More specifically, as reflected in the claims below, inventive aspects lie in less than all the features of the individual embodiments disclosed above. Therefore, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, with each claim itself serving as a separate embodiment of the present invention.

[0204] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition they may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

[0205] In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present invention and form different embodiments. For example, in the claims below, any one of the claimed embodiments may be used in any combination.

[0206] The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components of a data access method, device, and system according to an embodiment of the present invention. The present invention may also be implemented as a device or device program (e.g., a computer program and a computer program product) for executing part or all of the methods described herein. Such a program implementing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0207] It should be noted that the above embodiments illustrate the present invention rather than limit it, and that those skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets should not be constructed as a limitation to the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising a number of different elements and by means of a suitably programmed computer. In a unit claim that lists a number of devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc., does not indicate any order. These words may be interpreted as names.

Claims

1. A system software verification method, characterized in that: include: Deploy a standard version of the system software compressed package and a standard version of the configuration data compressed package into a verification folder and calculate the first file fingerprint of the verification folder, wherein the deployment process of the verification folder includes establishing verification subfolders according to the system modules involved in the system software, and each system module corresponds to a folder; Obtaining a folder to be verified corresponding to the system software after the upgrade and calculating a second file fingerprint of the folder to be verified, wherein the folder to be verified includes the system software of the version to be verified and configuration data of the version to be verified; comparing the first file fingerprint and the second file fingerprint to see whether they are the same; If they are the same, the output system software upgrade is successful; If they are not the same, then search for the file that caused the system software upgrade failure; The files corresponding to the failure of system software upgrade are searched for: Obtain the verification subfolders in the verification folder, and calculate the third file fingerprint of each verification subfolder; Obtain the subfolders to be verified in the folder to be verified, and calculate the fourth file fingerprint of each subfolder to be verified; Matching the third file fingerprint and the fourth file fingerprint, and obtaining the third file fingerprint and the fourth file fingerprint that failed to match; Determine the error correction file corresponding to the third file fingerprint that fails to match and the error file corresponding to the fourth file fingerprint; The step of deploying a standard version of the system software compressed package and a standard version of the configuration data compressed package into a verification folder and calculating a first file fingerprint of the verification folder includes: Establish corresponding verification subfolders in the verification folder according to the system modules involved in the execution process of the standard version of the system software; According to the preset first search keyword, obtaining the system software compression package of the standard version; Decompressing the standard version of the system software compressed package to obtain a first file; According to the keywords contained in the first file, the first file is deployed to the corresponding verification subfolder by searching a comparison table, wherein the comparison table records the keywords associated with the verification subfolder, wherein the keywords are arranged in a certain order, and the deployment of the first file to the corresponding verification subfolder by searching the comparison table includes searching for folders in the first file according to the order of arrangement of the keywords.

2. The method according to claim 1, characterized in that: The step of deploying a standard version of the system software compressed package and a standard version of the configuration data compressed package into a verification folder and calculating a first file fingerprint of the verification folder includes: According to the preset second search keyword, obtain the configuration data compression package of the standard version; Decompressing the configuration data compression package of the standard version to obtain a second file; According to the keywords contained in the second file, deploy the second file to the corresponding verification subfolder by searching the comparison table; The first file fingerprint of the verification folder is calculated by using the MD5 information digest algorithm.

3. The method according to claims 1-2, characterized in that: Before deploying the standard version of the system software compressed package and the standard version of the configuration data compressed package into the verification folder and calculating the first file fingerprint of the verification folder, the method further includes: Obtain identification information in the project release form according to the received user instruction; According to the identification information, a standard version of the system software compressed package and a standard version of the configuration data compressed package matching the identification information are searched from the data server.

4. A system software verification device, characterized in that: include: A first calculation module is used to deploy a standard version of the system software compressed package and a standard version of the configuration data compressed package into a verification folder and calculate a first file fingerprint of the verification folder, wherein the deployment process of the verification folder includes establishing a verification subfolder according to the system modules involved in the system software, and each system module corresponds to a folder; A second calculation module is used to obtain a folder to be verified corresponding to the system software after the upgrade and calculate a second file fingerprint of the folder to be verified, wherein the folder to be verified includes the system software of the version to be verified and the configuration data of the version to be verified; A comparison module, comparing the first file fingerprint and the second file fingerprint to see whether they are the same; The output module outputs that the system software upgrade is successful if the first file fingerprint is the same as the second file fingerprint; a first search module, searching for a file corresponding to the failure of the system software upgrade if the first file fingerprint is different from the second file fingerprint; Wherein, the first search module includes: The second calculation submodule is used to obtain the verification subfolders in the verification folder and calculate the third file fingerprint of each verification subfolder; The third verification submodule is used to obtain the subfolders to be verified in the folder to be verified, and calculate the fourth file fingerprint of each subfolder to be verified; A matching submodule, used for matching the third file fingerprint and the fourth file fingerprint, and obtaining the third file fingerprint and the fourth file fingerprint that failed to match; A determination submodule, used to determine the error correction file corresponding to the third file fingerprint that failed to match and the error file corresponding to the fourth file fingerprint; The first computing module comprises: Establishing a submodule, used for establishing a corresponding verification subfolder in the verification folder according to the system modules involved in the execution process of the standard version of the system software after the second search module finds the system software compressed package and the standard version of the configuration data compressed package; A first acquisition submodule is used to acquire the system software compression package of the standard version according to a preset first search keyword after the establishment submodule has established the verification subfolder; A first decompression submodule, used to decompress the standard version of the system software compressed package obtained by the first obtaining submodule to obtain a first file; The first deployment submodule is used to deploy the first file to a corresponding verification subfolder by searching a comparison table according to keywords contained in the first file after the first decompression submodule obtains the first file. The comparison table records keywords associated with the verification subfolder, wherein the keywords are arranged in a certain order. Deploying the first file to the corresponding verification subfolder by searching the comparison table includes searching for folders in the first file according to the order of arrangement of the keywords.

5. The device according to claim 4, characterized in that The first computing module comprises: A second acquisition submodule, used to acquire the configuration data compression package of the standard version according to a preset second search keyword; A second decompression submodule, used to decompress the configuration data compression package of the standard version to obtain a second file; A second deployment submodule, configured to deploy the second file to a corresponding verification subfolder by searching a comparison table according to the keywords contained in the second file; The first calculation submodule is used to calculate the first file fingerprint of the verification folder by using the MD5 information digest algorithm.

6. The device according to claims 4-5, characterized in that The device also includes: An acquisition module, used to acquire identification information in the project release form according to a received user instruction; The second search module is used to search the data server for a standard version of the system software compressed package and a standard version of the configuration data compressed package that match the identification information according to the identification information.

7. A storage medium, characterized in that: The storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the system software verification method described in any one of claims 1 to 3.

8. A processor, characterized in that: The processor is used to run a program, wherein the system software verification method described in any one of claims 1 to 3 is executed when the program is run.

Images