Disclosure of Invention
The application aims at providing a software release step checking method, a device, an electronic device and a storage medium, which can automatically check the steps of software release, are beneficial to improving the efficiency of the checking process, reducing the error rate of the checking process and reducing the time consumption of the checking process.
Embodiments of the application may be implemented as follows:
in a first aspect, the present application provides a method for checking a software release step, including:
Acquiring release step information of target software, wherein the release step information is used for indicating steps to be executed when the target software is released;
Generating a step list according to the release step information of the target software, wherein the step list comprises at least one step;
and respectively checking the information of each step in the step list, and generating a release step checking result according to the checking result.
In an alternative embodiment, the information for each step includes: the order of the steps and the integrity;
Checking the information of each step in the step list respectively, wherein the checking comprises the following steps:
acquiring release type information of target software;
determining a target step sequence list according to release type information of target software and a preset first mapping table, wherein the target step sequence list is used for indicating release steps and release step sequences corresponding to the release type information of the target software, and the preset first mapping table is used for indicating mapping relations between release type information of the software and the step sequence list;
and checking the sequence and the integrity of each step in the step list according to the target step sequence list.
In an alternative embodiment, checking the order and integrity of the steps in the step list according to the target step order list includes:
comparing the step sequence of the target step sequence list with that of the step list, and determining whether the sequence of each step in the step list is correct;
If the sequence of each step in the step list is correct, determining the integrity of each step in the step list according to the target step sequence list and the content of the steps with the same sequence in the step list.
In an alternative embodiment, the information for each step includes: the order of the steps and the integrity;
Checking the information of each step in the step list respectively, wherein the checking comprises the following steps:
acquiring release type information of target software;
Determining a target weight mapping table according to release type information of the target software and a preset second mapping table, wherein the target weight mapping table is used for indicating weights of release steps corresponding to the release type information of the target software, and the preset second mapping table is used for indicating mapping relations between release type information of the software and the weight mapping tables;
And checking the sequence and the integrity of each step in the step list according to the target weight mapping table.
In an alternative embodiment, checking the order and integrity of the steps in the step list according to the target weight mapping table includes:
determining the weight of each step in the step list according to the target weight mapping table;
determining whether the sequence of each step in the step list is correct according to the weight sequence of each step in the step list;
if the sequence of each step in the step list is correct, determining the integrity of each step in the step list according to the target weight mapping table and the content of the step with the same sequence in the step list.
In an alternative embodiment, before checking the information of each step in the step list, the method further comprises:
Acquiring parameter information of target software, wherein the parameter information at least comprises: a numbered list of server groups and execution dates;
An inspection processing function is generated based on the parameter information of the target software, and is used for inspecting the information of each step in the step list.
In an alternative embodiment, the information for each step includes: the content of the steps; checking the information of each step in the step list respectively, wherein the checking comprises the following steps:
Acquiring a preset third mapping table, wherein the third mapping table is used for indicating the mapping relation between each step in the step list and the checking processing function;
Sequentially determining checking processing functions corresponding to all steps in the step list according to a preset third mapping table;
And sequentially running the checking processing functions corresponding to the steps in the step list to obtain the checking result of the contents of the steps in the step list.
In an alternative embodiment, obtaining the publishing step information of the target software includes:
acquiring an instance identity of a software function release platform, and releasing target software through the software function release platform;
And acquiring the release step information of the target software through a release step information interface of the software function release platform according to the instance identity of the software function release platform.
In an alternative embodiment, the method further includes, after checking the information of each step in the step list and generating the inspection result of the publishing step according to the inspection result:
And converting the format of the inspection result of the issuing step to obtain a target inspection result, wherein the format of the target inspection result is a text indentation format.
In an alternative embodiment, generating the step list according to the release step information of the target software includes:
acquiring a preset fourth mapping table, wherein the fourth mapping table is used for indicating the mapping relation between the field names and the standard field names in the publishing step information;
determining standard field names corresponding to each field name in the release step information according to a preset fourth mapping table;
Extracting the values of the field names in the release step information, converting the values of the field names in the release step information into the values of the corresponding standard field names, and generating an extraction conversion result.
And generating a step list according to the extraction and conversion result.
In a second aspect, the present application provides a software release step checking apparatus, the apparatus comprising:
the information acquisition module is used for acquiring release step information of the target software, wherein the release step information is used for indicating steps required to be executed when the target software is released;
the list generation module is used for generating a step list according to the release step information of the target software, wherein the step list comprises at least one step;
And the result generation module is used for respectively checking the information of each step in the step list and generating a release step checking result according to the checking result.
In a third aspect, the present application provides an electronic device comprising: a processor, a storage medium, and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium in communication over the bus when the electronic device is operating, the processor executing the machine-readable instructions to perform the steps of any of the methods as in the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of any of the methods of the first aspect.
The application provides a software release step checking method, a device, electronic equipment and a storage medium, wherein release step information of target software is obtained and is used for indicating steps required to be executed when the target software is released; generating a step list according to the release step information of the target software, wherein the step list comprises at least one step; the information of each step in the step list is checked respectively, and the checking result of the release step is generated according to the checking result, so that the software release step can be checked automatically, the efficiency of the checking process is improved, the error rate of the checking process is reduced, and the time consumption of the checking process is reduced.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
In the description of the present application, it should be noted that, if the terms "upper", "lower", "inner", "outer", and the like indicate an azimuth or a positional relationship based on the azimuth or the positional relationship shown in the drawings, or the azimuth or the positional relationship in which the inventive product is conventionally put in use, it is merely for convenience of describing the present application and simplifying the description, and it is not indicated or implied that the apparatus or element referred to must have a specific azimuth, be configured and operated in a specific azimuth, and thus it should not be construed as limiting the present application.
Furthermore, the terms "first," "second," and the like, if any, are used merely for distinguishing between descriptions and not for indicating or implying a relative importance.
It should be noted that the features of the embodiments of the present application may be combined with each other without conflict.
Before the embodiments of the present application are specifically described, application scenarios of the present application will be described.
At present, when software is released, usually, more operation steps are involved, for example, whether the version number of the code to be released is consistent with the latest version number of the code version management warehouse, whether the version number of the update file to be released, the MD5 (Message-Digest Algorithm) value and the content thereof meet the specified rules are confirmed, and the steps and settings are different for different function release types. In the prior art, these steps are usually created by a software release platform according to a preset template to generate a release step instance, and then a functional release inspector manually performs inspection and confirmation on each step.
However, the steps of manually checking the software release are inefficient, error rate is high, and the process is time consuming.
In order to solve the problem, the embodiment of the application provides a software release step checking method, a device, electronic equipment and a storage medium, which can automatically check the steps of software release, thereby improving the efficiency of the checking process, reducing the error rate of the checking process and reducing the time consumption of the checking process.
Referring to fig. 1, the method for checking a software release step provided by the present application includes:
S101: and acquiring release step information of the target software, wherein the release step information is used for indicating steps required to be executed when the target software is released.
It should be specifically noted that, the software release step in the embodiment of the present application may also be referred to as a software function release step, where the two names have the same meaning.
Before the software is released on the software release platform, the software generally goes through multiple steps to test the function and stability, and the release step information in the embodiment of the application is used for indicating the steps to be executed when the target software is released. Specifically, the release step information can be obtained through an outbound step information http/https interface or a TCP (Transmission Control Protocol ) interface provided by a software release platform of the target software to be released.
S102: generating a step list according to the release step information of the target software, wherein the step list comprises at least one step.
Depending on the software function distribution platform, the structure or format of the distribution step information may also be different. In the embodiment of the application, the release step information of the target software is uniformly processed into the step list with the preset format, so that the step list with the preset format can be automatically checked later, and the efficiency and the accuracy of the checking process can be improved.
Optionally, each step in the step list may include a step ID (Identity document, identity), a step name, a step type, a group, and step additional information, which is not limited by the present application.
It should be noted that, the step additional information of different steps is also different, for example, the step additional information of the step of uploading the passcode includes the project names, version numbers and server group information of all codes, and the step additional information of the step of uploading the patch file includes the version number of the patch file, the MD5 value of the patch file, etc., which is merely illustrative and not meant to limit the present application.
S103: and respectively checking the information of each step in the step list, and generating a release step checking result according to the checking result.
In particular, the information of each step may include the order, integrity, content, and the like of each step. The sequence of each step in the step list and the complete line of each step and the content of each step can be checked respectively, and the inspection result of the release step is generated according to the inspection result.
It should be noted that, in the embodiment of the present application, the inspection result of the publishing step may be a list structure, where each element in the list represents an inspection result, including the content of the inspection, the status of the inspection, and a text description of the result, where the status of the inspection may be described by True or False, true represents that the inspection has no abnormality, and False represents that the inspection finds a problem. Of course, this is merely illustrative and the application is not limited in this regard.
According to the software release step checking method, release step information for indicating steps required to be executed when target software is released is firstly obtained, and release step information of different software release platforms generally has different structures or formats, so that the method is different from a mode of manually checking each step in release step information in the prior art, and the release step information of the target software is processed into a step list comprising at least one step, so that release step information with different structures or formats is unified into the format of the step list, the subsequent automatic checking of the information of each step in the step list is facilitated, and release step checking results are generated according to checking results.
In an alternative embodiment, the information for each step includes: the order of the steps and the integrity; checking the information of each step in the step list respectively, wherein the checking comprises the following steps: acquiring release type information of target software; determining a target step sequence list according to release type information of target software and a preset first mapping table, wherein the target step sequence list is used for indicating release steps and release step sequences corresponding to the release type information of the target software, and the preset first mapping table is used for indicating mapping relations between release type information of the software and the step sequence list; and checking the sequence and the integrity of each step in the step list according to the target step sequence list.
In particular, the release types of the target software may include regular updates, hot updates, hotfix (patches), and updates to different services or different server groups, with different release types typically having different release steps and sequences of release steps. In the embodiment of the application, the first mapping table indicating the mapping relation between each piece of release type information of the software and each step sequence list can be pre-established, so that the corresponding step sequence list can be automatically and quickly determined after the release type information of the target software is acquired.
It should be noted that, the step sequence list here refers to: in the embodiment of the application, the step sequence list corresponding to each piece of release type information of the software is confirmed in advance, that is, in the embodiment of the application, errors may exist in the step list, and the step sequence list is confirmed in advance to be correct.
Referring to fig. 2, for example, a predetermined first mapping table includes a type a, a type b, and a type c, wherein the type a has a mapping relationship with the step sequence list a, the type b has a mapping relationship with the step sequence list b, the type c has a mapping relationship with the step sequence list c, and the step sequence list a includes a step 1 with a sequence of 1, a step 2 with a sequence of 2, and a step 3 with a sequence of 3. Assuming that the release type information of the target software is type a, and according to a preset first mapping table, the step sequence list corresponding to the type a is step sequence list a, wherein the step sequence list a is the target step sequence list, and the sequence and the integrity of each step in the step list can be checked through the step sequence list a.
In an alternative embodiment, checking the order and integrity of the steps in the step list according to the target step order list includes: comparing the step sequence of the target step sequence list with that of the step list, and determining whether the sequence of each step in the step list is correct; if the sequence of each step in the step list is correct, determining the integrity of each step in the step list according to the target step sequence list and the content of the steps with the same sequence in the step list.
Alternatively, it may be checked whether the order of steps in the step list is the same as the order of steps in the target step order list, and if so, the order of steps in the step list is wrong, and the subsequent process of determining the integrity is not performed; if the content of the step sequence list is the same, the sequence of each step in the step list is correct, whether the content exists in the step sequence list, which is the same as the content of the step sequence list, exists, the integrity check of each step in the step list passes, and if the content does not exist, the integrity check of each step in the step list does not pass.
In an alternative embodiment, the information for each step includes: the order of the steps and the integrity; checking the information of each step in the step list respectively, wherein the checking comprises the following steps: acquiring release type information of target software; determining a target weight mapping table according to release type information of the target software and a preset second mapping table, wherein the target weight mapping table is used for indicating weights of release steps corresponding to the release type information of the target software, and the preset second mapping table is used for indicating mapping relations between release type information of the software and the weight mapping tables; and checking the sequence and the integrity of each step in the step list according to the target weight mapping table.
In the embodiment of the application, the second mapping table indicating the mapping relation between each piece of release type information of the software and each weight mapping table can be established in advance, so that the corresponding weight mapping table can be automatically and quickly determined after the release type information of the target software is acquired.
The weight map table here means: the weight of each release step corresponding to the release type information of the software, namely the weight mapping table comprises information of each release step and weight information corresponding to each release step. In the embodiment of the present application, there may be an error in the step list, and the weight mapping table is confirmed in advance, is correct, the embodiment of the application checks the sequence and the integrity of each step in the step list through the weight mapping table, which is beneficial to lower error rate in the checking process.
In an alternative embodiment, checking the order and integrity of the steps in the step list according to the target weight mapping table includes: determining the weight of each step in the step list according to the target weight mapping table; determining whether the sequence of each step in the step list is correct according to the weight sequence of each step in the step list; if the sequence of each step in the step list is correct, determining the integrity of each step in the step list according to the target weight mapping table and the content of the step with the same sequence in the step list.
In the embodiment of the application, firstly, the weight of each step in the step list is determined according to the weight of each release step in the target weight mapping table, and then whether the sequence of each step in the step list is correct is determined according to the weight sequence of each step in the step list. For example, assuming that each publishing step in the target weight mapping table is arranged according to the execution sequence, the publishing step ordered in front has higher weight, the publishing step ordered in back has lower weight, determining the weight of each step in the step list according to the weight of each publishing step in the target weight mapping table, judging whether the weights of each step in the step list are arranged in reverse order, if not, indicating that the sequence of each step in the step list has an error, and not performing the step of checking the integrity later. If so, the sequence of each step in the step list is correct, whether the content of the step with the same sequence as the target weight mapping table exists in the step list is judged, if so, the integrity check of each step in the step list is passed, and if part of the content does not exist, the integrity check of each step in the step list is not passed.
Referring to fig. 3, for example, the preset second mapping table includes a type a, a type b, and a type c, wherein the type a has a mapping relationship with the weight mapping table a, the type b has a mapping relationship with the weight mapping table b, the type c has a mapping relationship with the weight mapping table c, and the weight mapping table a includes a step 1 with a weight of 3, a step 2 with a weight of 2, and a step 3 with a weight of 1. Assuming that the release type information of the target software is type a, and according to a preset second mapping table, the weight mapping table corresponding to the type a is weight mapping table a, wherein the weight mapping table a is the target weight mapping table, and the sequence and the integrity of each step in the step list can be checked through the weight mapping table a.
In an alternative embodiment, before checking the information of each step in the step list, the method further comprises: acquiring parameter information of target software, wherein the parameter information at least comprises: a numbered list of server groups and execution dates; an inspection processing function is generated based on the parameter information of the target software, and is used for inspecting the information of each step in the step list.
Specifically, the parameter information of the target software may be obtained by acquiring real-time input of the user, or may be obtained by storing the parameter information input in advance by the user in a storage medium of a computer, and by reading the storage medium of the computer, where the storage medium of the computer may include a memory, a magnetic disk, a database, and the like, which is not limited in the present application.
If the number list of the specific target server group is specified in the parameter information, the target inspection processing function may be generated from the number list of the target server group, and the target inspection processing function may be used to check whether the number list information of the server group at each step in the step list matches with the number list of the target server group, and if the number list information matches with the number list of the target server group, the inspection is passed, and if the number list information does not match, the inspection is not passed.
In an alternative embodiment, the information for each step includes: the content of the steps; checking the information of each step in the step list respectively, wherein the checking comprises the following steps: acquiring a preset third mapping table, wherein the third mapping table is used for indicating the mapping relation between each step in the step list and the checking processing function; sequentially determining checking processing functions corresponding to all steps in the step list according to a preset third mapping table; and sequentially running the checking processing functions corresponding to the steps in the step list to obtain the checking result of the contents of the steps in the step list.
In the embodiment of the application, corresponding checking processing functions can be defined in advance for different steps, namely, a third mapping table for indicating the mapping relation between each step in the step list and the checking processing functions is established in advance, then the checking processing functions corresponding to each step in the step list are determined, and finally the checking result of the content of each step in the step list is obtained by sequentially running the checking processing functions corresponding to each step in the step list.
In an alternative embodiment, obtaining the publishing step information of the target software includes: acquiring an instance identity of a software function release platform, and releasing target software through the software function release platform; and acquiring the release step information of the target software through a release step information interface of the software function release platform according to the instance identity of the software function release platform.
Specifically, if the target software is released through the software function release platform, the instance identity of the software function release platform can be obtained, and according to the instance identity of the software function release platform, release step information is obtained through an outbound step information http/https interface or a TCP interface provided by the software release platform of the target software to be released. The application is not limited in this regard.
In an alternative embodiment, the method further includes, after checking the information of each step in the step list and generating the inspection result of the publishing step according to the inspection result: and converting the format of the inspection result of the issuing step to obtain a target inspection result, wherein the format of the target inspection result is a text indentation format.
In the embodiment of the application, the data in the checking result is converted into the target checking result with text format and indentation, so that the user can quickly know whether the step list has abnormality or not and which abnormality exists through the formatted target checking result, thereby greatly reducing the workload of the user.
In an alternative embodiment, generating the step list according to the release step information of the target software includes: acquiring a preset fourth mapping table, wherein the fourth mapping table is used for indicating the mapping relation between the field names and the standard field names in the publishing step information; determining standard field names corresponding to each field name in the release step information according to a preset fourth mapping table; extracting the values of the field names in the release step information, converting the values of the field names in the release step information into the values of the corresponding standard field names, and generating an extraction conversion result. And generating a step list according to the extraction and conversion result.
Optionally, a fourth mapping table indicating a mapping relationship between the field names in the publishing step information and the standard field names may be pre-established, where the mapping relationship between the field names in the publishing step information and the standard field names may be set according to the needs, which is not limited in the present application.
Depending on the software function distribution platform, the structure or format of the distribution step information may also be different. In the embodiment of the application, the release step information of the target software is processed into the step list with the uniform format, so that the step list with the preset format can be automatically checked later, and the efficiency and the accuracy of the checking process can be improved.
Referring to fig. 4, the present application further provides a software release step checking device 40, which includes:
The information acquisition module 401 is configured to acquire release step information of the target software, where the release step information is used to indicate a step that needs to be executed when the target software is released;
a list generating module 402, configured to generate a step list according to the publishing step information of the target software, where the step list includes at least one step;
The result generating module 403 is configured to check information of each step in the step list, and generate a published step inspection result according to the inspection result.
In an alternative embodiment, the information for each step includes: the order of the steps and the integrity; the result generating module 403 is specifically configured to obtain release type information of the target software; determining a target step sequence list according to release type information of target software and a preset first mapping table, wherein the target step sequence list is used for indicating release steps and release step sequences corresponding to the release type information of the target software, and the preset first mapping table is used for indicating mapping relations between release type information of the software and the step sequence list; and checking the sequence and the integrity of each step in the step list according to the target step sequence list.
In an alternative embodiment, the result generating module 403 is further specifically configured to compare the target step sequence list with the step sequence of the step list, and determine whether the sequence of each step in the step list is correct; if the sequence of each step in the step list is correct, determining the integrity of each step in the step list according to the target step sequence list and the content of the steps with the same sequence in the step list.
In an alternative embodiment, the information for each step includes: the order of the steps and the integrity; the result generating module 403 is specifically configured to obtain release type information of the target software; determining a target weight mapping table according to release type information of the target software and a preset second mapping table, wherein the target weight mapping table is used for indicating weights of release steps corresponding to the release type information of the target software, and the preset second mapping table is used for indicating mapping relations between release type information of the software and the weight mapping tables; and checking the sequence and the integrity of each step in the step list according to the target weight mapping table.
In an alternative embodiment, the result generating module 403 is further specifically configured to determine weights of the steps in the step list according to the target weight mapping table; determining whether the sequence of each step in the step list is correct according to the weight sequence of each step in the step list; if the sequence of each step in the step list is correct, determining the integrity of each step in the step list according to the target weight mapping table and the content of the step with the same sequence in the step list.
In an alternative embodiment, the apparatus further comprises: the parameter acquisition module is used for acquiring parameter information of the target software, wherein the parameter information at least comprises: a numbered list of server groups and execution dates; an inspection processing function is generated based on the parameter information of the target software, and is used for inspecting the information of each step in the step list.
In an alternative embodiment, the information for each step includes: the content of the steps; the result generating module 403 is specifically configured to obtain a preset third mapping table, where the third mapping table is used to indicate a mapping relationship between each step in the step list and the inspection processing function; sequentially determining checking processing functions corresponding to all steps in the step list according to a preset third mapping table; and sequentially running the checking processing functions corresponding to the steps in the step list to obtain the checking result of the contents of the steps in the step list.
In an alternative embodiment, the information obtaining module 401 is specifically configured to obtain an instance identity of the software function publishing platform, and the target software is published by the software function publishing platform; and acquiring the release step information of the target software through a release step information interface of the software function release platform according to the instance identity of the software function release platform.
In an alternative embodiment, the apparatus further comprises: the conversion module is used for carrying out format conversion on the inspection result of the issuing step to obtain a target inspection result, wherein the format of the target inspection result is a text indentation format.
In an optional embodiment, the list generating module 402 is specifically configured to obtain a preset fourth mapping table, where the fourth mapping table is used to indicate a mapping relationship between a field name and a standard field name in the publishing step information; determining standard field names corresponding to each field name in the release step information according to a preset fourth mapping table; extracting the values of the field names in the release step information, converting the values of the field names in the release step information into the values of the corresponding standard field names, and generating an extraction conversion result. And generating a step list according to the extraction and conversion result.
Referring to fig. 5, the present application further provides an electronic device 50, including: processor 501, storage medium 502, and bus 503, storage medium 502 storing machine-readable instructions executable by processor 501, processor 501 executing machine-readable instructions to perform steps of a method as in any of the preceding embodiments when electronic device 50 is operating, processor 501 communicating with storage medium 502 via bus 503.
The application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of any of the methods of the previous embodiments.
According to the software release step checking method provided by the application, release step information of the target software is obtained, and the release step information is used for indicating steps to be executed when the target software is released; generating a step list according to the release step information of the target software, wherein the step list comprises at least one step; the information of each step in the step list is checked respectively, and the checking result of the release step is generated according to the checking result, so that the software release step can be checked automatically, the efficiency of the checking process is improved, the error rate of the checking process is reduced, and the time consumption of the checking process is reduced.
In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.
The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (english: processor) to perform some of the steps of the methods according to the embodiments of the application. And the aforementioned storage medium includes: u disk, mobile hard disk, read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any changes or substitutions easily contemplated by those skilled in the art within the scope of the present application should be included in the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.