Firewall upgrade method, device, storage medium and processor

Abstract

The present invention discloses a method, device, storage medium and processor for upgrading a firewall. The method comprises: collecting version information of the current version file in the firewall, wherein the version information at least comprises: a version path and a current version attribute, wherein the version path stores a version set corresponding to the current version file, wherein the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; according to the current version attribute, determining a target version attribute of a target version file in the version set; and upgrading the firewall based on the difference between the current version attribute and the target version attribute. The present invention solves the technical problem of low upgrade efficiency of existing firewalls.

Description

Technical Field

[0001] The present invention relates to the field of computers, and in particular to a method, device, storage medium and processor for upgrading a firewall. Background Art

[0002] In order to meet the needs of different customer groups and improve competitiveness, firewall product companies will select different architecture chips according to market development needs, such as X86, NP, multi-core, etc., to develop different series of firewall products. Each series of products contains various models of platform products. As the number of product platforms continues to increase, the corresponding software versions are also increasing. In order to facilitate software management, the concept of trunk and branch is introduced to manage each platform version. Since most of the platform versions have commonalities or inheritance relationships, each trunk and branch can correspond to many platform versions. Therefore, the version file server generally stores software version files according to series, branches, and platform structures.

[0003] Based on this complex combination of branches, series, and platforms, when you need to upgrade the versions of a batch of devices of different models in batches, you need to find the target version file location according to the corresponding rules, find the upgradeable version file, and then perform the upgrade operation.

[0004] However, in the existing upgrade process, the server obtains the current version information of the client by parsing the version upgrade request sent by the client; matches the upgrade versions stored in the server with the current version information of the client respectively to obtain at least one upgrade version; according to the number of upgrade versions, selects the same number of clients from all clients requesting upgrade as samples of each upgrade version, and uses the selected number as the starting margin of each sample; determines the upgradeable margin of each sample in parallel, and when the upgrade margin of the sample is sufficient, returns the corresponding upgrade version and related upgrade information to the requesting client in the sample.

[0005] However, the existing upgrade method requires the server and client to have a special protocol parsing mechanism, and the upgrade needs to be initiated by the client, manually searching one by one to confirm the required version of the corresponding platform, which is not convenient for unified management, and has a large workload, low efficiency, and is prone to errors.

[0006] Currently, no effective solution has been proposed to address the problem of low upgrade efficiency of existing firewalls. Summary of the invention

[0007] The embodiments of the present invention provide a method, device, storage medium and processor for upgrading a firewall, so as to at least solve the technical problem of low upgrading efficiency of the existing firewall.

[0008] According to one aspect of an embodiment of the present invention, a method for upgrading a firewall is provided, comprising: collecting version information of a current version file in the firewall, wherein the version information at least includes: a version path and a current version attribute, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; according to the current version attribute, determining a target version attribute of a target version file in the version set; and upgrading the firewall based on the difference between the current version attribute and the target version attribute.

[0009] Optionally, the version attributes include at least: a product series identifier and a version branch identifier, wherein the product series identifier is a first-level management identifier of the version file, and the version branch identifier is a second-level management identifier of the version file, and collecting the version information of the firewall includes: collecting the current version attributes of the firewall; identifying the current product series identifier and the current version branch identifier in the current version attributes; and generating the version path based on the current product series identifier, the current version branch identifier and a preset root directory.

[0010] Optionally, the version attributes also include: a version platform identifier and version release information, wherein the version platform identifier is a third-level management identifier of the version file; determining the target version attributes of the target version file in the version set based on the current version attributes includes: identifying the current version platform identifier in the current version attributes; screening a version subset corresponding to the current version platform identifier in the version set, wherein the version files in the version subset have the same version platform identifier; selecting the latest released version file in the version subset as the target version file based on the version release information; and determining the target version attributes of the target version file.

[0011] Optionally, the version release information indicates the release order of the version files through a version code; selecting the latest released version file in the version subset as the target version file based on the version release information includes: selecting the version file with the last release order in the version subset as the target version file according to the version code.

[0012] Optionally, the version release information indicates the release time of the version file through the version time; selecting the latest released version file in the version subset as the target version file based on the version release information includes: selecting the version file with the most recent release time in the version subset as the target version file according to the version time.

[0013] Optionally, upgrading the firewall based on the difference between the current version attributes and the target version attributes includes: determining a current version file corresponding to the current version attributes and a target version file corresponding to the target version attributes in the version set; determining a version file to be upgraded based on the current version file and the target version file, wherein the version file to be upgraded includes at least: the target version file, a transition version file released between the current version file and the target version file; and upgrading the firewall based on the version file to be upgraded.

[0014] According to another aspect of an embodiment of the present invention, a firewall upgrade device is also provided, including: a collection unit, used to collect version information of a current version file in the firewall, wherein the version information includes at least: a version path and a current version attribute, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; a determination unit, used to determine a target version attribute of a target version file in the version set according to the current version attribute; and an upgrade unit, used to upgrade the firewall based on the difference between the current version attribute and the target version attribute.

[0015] Optionally, the version attributes include at least: a product series identifier and a version branch identifier, wherein the product series identifier is a first-level management identifier of the version file, and the collection unit includes: a collection module, used to collect the current version attributes of the firewall; a first identification module, used to identify the current product series identifier and the current version branch identifier in the current version attributes; and a generation module, used to generate the version path based on the current product series identifier, the current version branch identifier and a preset root directory.

[0016] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is further provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the above-mentioned firewall upgrade method.

[0017] According to another aspect of an embodiment of the present invention, a processor is further provided, and the processor is used to run a program, wherein the above-mentioned firewall upgrade method is executed when the program is running.

[0018] In an embodiment of the present invention, version information of the current version file in the firewall is collected, wherein the version information at least includes: a version path and a current version attribute, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; according to the current version attribute, a target version attribute of the target version file is determined in the version set; the firewall is upgraded based on the difference between the current version attribute and the target version attribute; thereby, the version path is obtained based on the version information of the current version file running in the firewall, and the version file can be automatically obtained from the version set based on the version path for upgrading, thereby achieving the purpose of automatically upgrading the firewall, realizing the technical effect of improving the efficiency of firewall upgrading, and thus solving the technical problem of low efficiency of existing firewall upgrading. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0020] Figure 1 is a flow chart of a method for upgrading a firewall according to an embodiment of the present invention;

[0021] Figure 2 is a schematic diagram of a data structure supporting parallel upgrade of firewall multi-platform adaptive versions according to an embodiment of the present invention;

[0022] Figure 3 It is a schematic diagram of a single firewall adaptive version upgrade process according to an embodiment of the present invention;

[0023] Figure 4 is a schematic diagram of collecting version-related information from a firewall device according to an embodiment of the present invention;

[0024] Figure 5 is a schematic diagram of extracting necessary information of a version path according to an embodiment of the present invention;

[0025] Figure 6 is a schematic diagram of a data table for recording version paths according to an embodiment of the present invention;

[0026] Figure 7 A schematic diagram of accessing a version file server to obtain a target version according to an embodiment of the present invention Figure 1 ;

[0027] Figure 8 A schematic diagram of accessing a version file server to obtain a target version according to an embodiment of the present invention Figure 2 ;

[0028] Fig. 9 is a schematic diagram of a data table for recording a target version according to an embodiment of the present invention;

[0029] Fig.10a A data table for recording upgrade results according to an embodiment of the present invention is shown in FIG. Figure 1 ;

[0030] Fig.10b A data table for recording upgrade results according to an embodiment of the present invention is shown in FIG. Figure 2 ;

[0031] Fig.10c A data table for recording upgrade results according to an embodiment of the present invention is shown in FIG. Figure 3 ;

[0032] Fig.10d A data table for recording upgrade results according to an embodiment of the present invention is shown in FIG. Figure 4 ;

[0033] Fig.11 is a schematic diagram of a firewall upgrade device according to an embodiment of the present invention;

[0034] Fig.12 It is a structural block diagram of a computer terminal according to an embodiment of the present invention. DETAILED DESCRIPTION

[0035] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0036] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0037] According to an embodiment of the present invention, an embodiment of a method for upgrading a firewall is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0038] Figure 1 is a flowchart of a method for upgrading a firewall according to an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0039] Step S102, collecting version information of the current version file in the firewall, wherein the version information at least includes: a version path and current version attributes, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute;

[0040] Step S104, determining the target version attribute of the target version file in the version set according to the current version attribute;

[0041] Step S106: Upgrading the firewall based on the difference between the current version attributes and the target version attributes.

[0042] In an embodiment of the present invention, version information of the current version file in the firewall is collected, wherein the version information at least includes: a version path and a current version attribute, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; according to the current version attribute, a target version attribute of the target version file is determined in the version set; the firewall is upgraded based on the difference between the current version attribute and the target version attribute; thereby, the version path is obtained based on the version information of the current version file running in the firewall, and the version file can be automatically obtained from the version set based on the version path for upgrading, thereby achieving the purpose of automatically upgrading the firewall, realizing the technical effect of improving the efficiency of firewall upgrading, and thus solving the technical problem of low efficiency of existing firewall upgrading.

[0043] In the above step S102, there may be multiple firewalls, and the version information also includes identification information of the firewalls; in the process of upgrading the firewalls, each firewall may be upgraded separately according to the identification information of the firewalls.

[0044] Optionally, an upgrade scheme for each firewall is determined according to identification information of the firewall, such as determining a version file for upgrading each firewall.

[0045] Optionally, the identification information of the firewall is a unique representation of the firewall, which may be a product serial number of the firewall, such as an SN number; or may be a combination of a serial port server address and a port number.

[0046] In the above step S102, the version set is a storage device for storing at least one version file, such as a folder for storing version files, or a version file server for storing version files.

[0047] Optionally, the firewall and the version file server may be connected via a serial port server.

[0048] In the above step S102, the version attribute includes a multi-level management identifier of the version file, and at least one version file in the version set is managed by the management identifier.

[0049] Optionally, the version file includes at least three levels of management identifiers, including: a product series identifier representing a first-level management identifier, a version branch identifier representing a second-level management identifier, and a version platform identifier representing a third-level management identifier; wherein the first-level management identifier is higher in level than the second-level management identifier, and the second-level management identifier is higher in level than the third-level management identifier.

[0050] Optionally, the management identifiers at each level may be represented by the name of the version file or the name of the folder where the version file is located.

[0051] Optionally, the folder of the first-level management identification includes the folder of the second-level management identification; the folder of the second-level management identification includes the folder of the third-level management identification.

[0052] As an optional embodiment, the version attributes include at least: a product series identifier and a version branch identifier, wherein the product series identifier is a first-level management identifier of the version file, and the version branch identifier is a second-level management identifier of the version file. Collecting the version information of the firewall includes: collecting the current version attributes of the firewall; identifying the current product series identifier and the current version branch identifier in the current version attributes; and generating a version path based on the current product series identifier, the current version branch identifier and the preset root directory.

[0053] The above-mentioned embodiment of the present invention collects the current version attributes of the firewall, identifies the current product series identifier and the current version branch identifier from the current version attributes, and then generates a version path according to the current product series identifier, the current version branch identifier and the preset root directory, thereby realizing the collection of the version path.

[0054] As an optional embodiment, the version attributes also include: a version platform identifier and version release information, wherein the version platform identifier is a third-level management identifier of the version file; determining the target version attributes of the target version file in the version collection based on the current version attributes includes: identifying the current version platform identifier in the current version attributes; screening a version subset corresponding to the current version platform identifier in the version collection, wherein the version files in the version subset have the same version platform identifier; selecting the latest released version file in the version subset as the target version file based on the version release information; and determining the target version attributes of the target version file.

[0055] The above-mentioned embodiment of the present invention can filter out a version subset corresponding to the current version platform identifier in the version collection by identifying the current version platform identifier in the current version attributes, and then obtain the latest released version file as the target version file from the version subset, and obtain the target version attributes of the target version file, thereby realizing the determination of the target version attributes.

[0056] Optionally, the version collection is a folder storing version files, and the version sub-collection is a portion of version files filtered out from the folder.

[0057] Optionally, the platform identifier can be represented by the file name of the version file. For example, if the file name of the version file is "HS-A1000-R8-V6-r0904.bin", the version platform identifier can be represented by the characters: "HS-A1000-R8-V6". Based on the version platform identifier, the version files of the A1000 platform that support version v6 can be filtered out.

[0058] Optionally, the version release information indicates the release time or release order of the version file, and can be represented by the file name of the version file. For example, if the file name of the version file is "HS-A1000-R8-V6-r0904.bin", the version release information can be represented by the characters "r0904".

[0059] As an optional embodiment, the version release information indicates the release order of the version files through version codes; selecting the latest released version file in the version subset as the target version file based on the version release information includes: selecting the version file with the last release order in the version subset as the target version file according to the version code.

[0060] In the above-mentioned embodiment of the present invention, the version release information represents the release order of the version files through version codes, and the version codes of the version files are increased one by one based on the release order of the version files. Based on the version codes, it can be determined that the version file with the last release order in the version subset is the latest released version file, and the version file is determined as the target version file, thereby realizing the determination of the target version file.

[0061] Optionally, the version code can be indicated by the file name of the version file.

[0062] For example, the version code can be represented by the characters "r0904", "r0905" and "r0905", the release time of the version file corresponding to the characters "r0904" is earlier than the release time of the version file corresponding to the characters "r0905", and the release time of the version file corresponding to the characters "r0905" is earlier than the release time of the version file corresponding to the characters "r0906".

[0063] Optionally, the version files in the version subset may be sorted based on the version codes, and the target version file may be determined based on the sorting of the version files.

[0064] As an optional embodiment, the version release information indicates the release time of the version file through the version time; selecting the latest released version file in the version subset as the target version file based on the version release information includes: selecting the version file with the most recent release time in the version subset as the target version file according to the version time.

[0065] In the above-mentioned embodiment of the present invention, the version release information represents the release time of the version file through the version time. Based on the version time, it can be determined that the version file with the most recent release time in the version subset is the latest released version file, and the version file is determined as the target version file, thereby realizing the determination of the target version file.

[0066] Optionally, the version time can be indicated by the file name of the version file.

[0067] For example, the version time can be represented by the characters "20210101", "20210105" and "20210112". The release time of the version file corresponding to the characters "20210101" is earlier than the release time of the version file corresponding to the characters "20210105", and the release time of the version file corresponding to the characters "20210105" is earlier than the release time of the version file corresponding to the characters "20210112".

[0068] Optionally, the version files in the version subset may be sorted based on the version time, and the target version file may be determined based on the sorting of the version files.

[0069] As an optional embodiment, upgrading a firewall based on the difference between the current version attributes and the target version attributes includes: determining in a version set a current version file corresponding to the current version attributes and a target version file corresponding to the target version attributes; determining a version file to be upgraded based on the current version file and the target version file, wherein the version file to be upgraded includes at least: a target version file, and a transition version file released between the current version file and the target version file; and upgrading the firewall based on the version file to be upgraded.

[0070] In the above embodiment of the present invention, the current version file corresponding to the current version attribute and the target version file corresponding to the target version attribute are determined in the version set. The version file to be upgraded required for upgrading the firewall is the transition version file between the current version file and the target version file in the version set, and the target version file. Then, the firewall can be upgraded based on the version file to be upgraded, thereby realizing automatic upgrade of the firewall.

[0071] The present invention also provides a preferred embodiment, which provides a processing solution that supports parallel upgrades of firewall multi-platform adaptive versions.

[0072] This solution uses a set of automated parallel processing techniques, which connects to the firewall, issues instructions, collects and extracts necessary information such as products (i.e. product series identifiers), branches (i.e. version branch identifiers), platforms (i.e. version platform identifiers) to form a version path, and accesses the corresponding directory (i.e. version collection) on the version server according to the version path. By comparing the version name and file creation time, the corresponding latest version is selected and automatically upgraded. After completion, the upgrade results are fed back to the user.

[0073] Figure 2 is a schematic diagram of a data structure supporting parallel upgrade of firewall multi-platform adaptive versions according to an embodiment of the present invention, such as Figure 2 As shown, the version information of each firewall is recorded through a data table, such as recording the serial port server and port number combination of the firewall through column A in the data table, recording the serial number (i.e. SN number) of the firewall through column B, recording the version path of the firewall through column C, recording the current version attributes through column D, stimulating the target version attributes through column E, and stimulating the upgrade result of the firewall through column F.

[0074] Optionally, each firewall serves as a processing unit, and a combination of the serial port server and the port number or the SN number serves as a unique identifier (ie, identification information) of the firewall.

[0075] Optionally, each processing unit independently collects data, extracts information (ie, collects version information), and generates a version path.

[0076] Optionally, each processing unit processes in parallel, and outputs the device identification (ie, identification information), the version path and the current version (ie, current version attributes) in sequence according to the time difference characteristics.

[0077] Optionally, the version file server is accessed using the version path formed by each processing unit (ie, firewall).

[0078] Optionally, by comparing versions, the target version is output (ie, the target version file and target version attributes are determined).

[0079] Optionally, each firewall enters an upgrade state based on a target version file or a target version attribute and outputs an upgrade result.

[0080] Figure 3 FIG. 1 is a schematic diagram of a single firewall adaptive version upgrade process according to an embodiment of the present invention. Figure 3 As shown in the figure, the upgrade process of a firewall is taken as an example to explain the implementation process of each functional module; the steps include:

[0081] Step S1: Log in to the firewall to collect version related information (ie collect version information).

[0082] Step S2: extract necessary version path information (ie, extract product series identifier and version branch identifier).

[0083] Step S3: Compose a version path.

[0084] Step S4: Access the version file server to obtain the target version (such as obtaining the target version file, or the target version attribute).

[0085] Step S5: Determine whether there is a target version to be upgraded (such as upgrading to a target version file).

[0086] Step S6: Enter the upgrade phase.

[0087] Step S7: Feedback the upgrade result to the user.

[0088] Figure 4 is a schematic diagram of collecting version related information from a firewall device according to an embodiment of the present invention. Figure 4 As shown, in the above step S1, the version-related information (ie, version information) may be collected from the firewall device through the "show version" command.

[0089] Figure 5 is a schematic diagram of extracting necessary information of a version path according to an embodiment of the present invention, such as Figure 5As shown, the above step S2 can extract the necessary information of the version path (i.e., the current version attributes), including: product series identifier "A", product serial number "123456", version branch identifier "branch_R8", current version (such as version name) "HS-A1000-R8-V6-r0904.bin", and version platform identifier "A1000".

[0090] Optionally, the above step S3 can form a version path based on the product series identifier, version branch identifier and fixed root directory extracted in step S2: "Dailybuild / A / branch_R8 / ".

[0091] Figure 6 is a schematic diagram of a data table for recording version paths according to an embodiment of the present invention, such as Figure 6 As shown, the serial server IP and port combination, SN, the composed version path and the current version (such as version name) are input into the table file.

[0092] Figure 7 A schematic diagram of accessing a version file server to obtain a target version according to an embodiment of the present invention Figure 1 ,like Figure 7 As shown, in the above step S4, the fixed IP of the version file server and the path output in step S3 form a complete folder location of the target version, and access the following path "ftp: / / ip / Dailybuild / A / branch_R8 / " through Ftp.

[0093] Figure 8 A schematic diagram of accessing a version file server to obtain a target version according to an embodiment of the present invention Figure 2 ,like Figure 8 As shown, in Figure 7 The branch directory shown has versions of different dates for the two platforms A1000 and B1000. The current version "HS-A1000-R8-V6-r0904.bin" output in step S2 is matched one by one with all version files in the current directory through the first segment position characters "HS-A1000-R8-V6" to filter out all related versions of the A1000 platform that support version v6. The latest created file version is filtered out by comparing the version file attributes, and "HS-A1000-R8-V6-r0906.bin" is the target version.

[0094] Fig. 9 is a schematic diagram of a data table for recording target versions according to an embodiment of the present invention. Figure 7 As shown, the price will be Figure 8 The target version determined in step S3 is entered into cell E2 of the table.

[0095] Optionally, in step S5, the string size is compared between the D2 cell version and the E2 cell version. If the current version is greater than or equal to the target version, the process proceeds to step S7 to prompt the user that the current version is the latest version and does not need to be upgraded. If the current version is less than the target version, the process proceeds to step S6 to enter the upgrade phase.

[0096] Optionally, in the above step S6, if the current version is smaller than the target version, the upgrade phase is entered.

[0097] Fig.10a A data table for recording upgrade results according to an embodiment of the present invention is shown in FIG. Figure 1 ; Fig.10b A data table for recording upgrade results according to an embodiment of the present invention is shown in FIG. Figure 2 ; Fig.10c A data table for recording upgrade results according to an embodiment of the present invention is shown in FIG. Figure 3 ; Fig.10d A data table for recording upgrade results according to an embodiment of the present invention is shown in FIG. Figure 4 As shown in the figure, enter the upgrade success, failure and no upgrade results into the F2 cell of the table, and feed back the F2 cell value to the front-end user. Fig.10a As shown, the upgrade fails as Fig.10b As shown, no upgrade is required. Fig.10c and Fig.10d shown.

[0098] The above-mentioned embodiments of the present invention are suitable for batch upgrade scenarios of existing Beta firewalls; batch upgrades of multiple firewall platforms such as intranet automated testing and SLT testing.

[0099] The above-mentioned embodiments of the present invention can greatly reduce the risk of enterprise employees choosing the wrong upgrade version when upgrading multiple firewall platform products at the same time; greatly shorten the time for upgrading multiple platforms at the same time through parallel processing, and improve work efficiency; solve the problem that when upgrading branch versions of firewalls of multiple platforms of multiple series, it is necessary to manually search and confirm the required versions of the corresponding platforms one by one, which is labor-intensive, inefficient, and prone to errors; and solve the problem that the manual serial upgrade of versions of multiple platforms is slow and time-consuming.

[0100] According to an embodiment of the present invention, an embodiment of a firewall upgrade device is also provided. It should be noted that the firewall upgrade device can be used to execute the firewall upgrade method in the embodiment of the present invention, and the firewall upgrade method in the embodiment of the present invention can be executed in the firewall upgrade device.

[0101] Fig.11 is a schematic diagram of a firewall upgrade device according to an embodiment of the present invention, such as Fig.11 As shown, the device may include: a collection unit 1102, used to collect version information of the current version file in the firewall, wherein the version information at least includes: a version path and a current version attribute, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; a determination unit 1104, used to determine the target version attribute of the target version file in the version set according to the current version attribute; an upgrade unit 1106, used to upgrade the firewall based on the difference between the current version attribute and the target version attribute.

[0102] It should be noted that the collection unit 1102 in this embodiment can be used to execute step S102 in the embodiment of the present application, the determination unit 1104 in this embodiment can be used to execute step S104 in the embodiment of the present application, and the upgrade unit 1106 in this embodiment can be used to execute step S106 in the embodiment of the present application. The examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments.

[0103] In an embodiment of the present invention, version information of the current version file in the firewall is collected, wherein the version information at least includes: a version path and a current version attribute, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; according to the current version attribute, a target version attribute of the target version file is determined in the version set; the firewall is upgraded based on the difference between the current version attribute and the target version attribute; thereby, the version path is obtained based on the version information of the current version file running in the firewall, and the version file can be automatically obtained from the version set based on the version path for upgrading, thereby achieving the purpose of automatically upgrading the firewall, realizing the technical effect of improving the efficiency of firewall upgrading, and thus solving the technical problem of low efficiency of existing firewall upgrading.

[0104] As an optional embodiment, the version attributes include at least: a product series identifier and a version branch identifier, wherein the product series identifier is a first-level management identifier of the version file, and the collection unit includes: a collection module, used to collect the current version attributes of the firewall; a first identification module, used to identify the current product series identifier and the current version branch identifier in the current version attributes; a generation module, used to generate a version path based on the current product series identifier, the current version branch identifier and the preset root directory.

[0105] As an optional embodiment, the version attributes also include: a version platform identifier and version release information, wherein the version platform identifier is a third-level management identifier of the version file; the determination unit includes: a second identification module, used to identify the current version platform identifier in the current version attributes; a screening module, used to screen a version subset corresponding to the current version platform identifier in the version collection, wherein the version files in the version subset have the same version platform identifier; a selection module, used to select the latest released version file in the version subset as the target version file based on the version release information; and a first determination module, used to determine the target version attribute of the target version file.

[0106] As an optional embodiment, the version release information indicates the release order of the version files through version codes; the selection module includes: a first selection submodule, used to select the version file with the last release order in the version subset as the target version file according to the version code.

[0107] As an optional embodiment, the version release information indicates the release time of the version file through the version time; the selection module includes: a second selection submodule, used to select the version file with the most recent release time in the version subset as the target version file according to the version time.

[0108] As an optional embodiment, the upgrade unit includes: a second determination module, used to determine the current version file corresponding to the current version attribute and the target version file corresponding to the target version attribute in the version set; a third determination module, used to determine the version file to be upgraded based on the current version file and the target version file, wherein the version file to be upgraded includes at least: the target version file, and the transition version file released between the current version file and the target version file; an upgrade module, used to upgrade the firewall according to the version file to be upgraded.

[0109] The embodiment of the present invention can provide a computer terminal, which can be any computer terminal device in a computer terminal group. Optionally, in this embodiment, the computer terminal can also be replaced by a terminal device such as a mobile terminal.

[0110] Optionally, in this embodiment, the computer terminal may be located in at least one network device among a plurality of network devices of the computer network.

[0111] In this embodiment, the above-mentioned computer terminal can execute the program code of the following steps in the firewall upgrade method: collecting version information of the current version file in the firewall, wherein the version information at least includes: a version path and a current version attribute, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; according to the current version attribute, determining the target version attribute of the target version file in the version set; and upgrading the firewall based on the difference between the current version attribute and the target version attribute.

[0112] Optionally, Fig.12 is a structural block diagram of a computer terminal according to an embodiment of the present invention. Fig.12 As shown, the computer terminal 120 may include: one or more (only one is shown in the figure) processors 122 and a memory 124.

[0113] Among them, the memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the upgrade method and device of the firewall in the embodiment of the present invention. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, the upgrade method of the firewall mentioned above is realized. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include a memory remotely arranged relative to the processor, and these remote memories can be connected to the terminal 120 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0114] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: collect version information of the current version file in the firewall, wherein the version information includes at least: a version path and a current version attribute, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; according to the current version attribute, determine the target version attribute of the target version file in the version set; and upgrade the firewall based on the difference between the current version attribute and the target version attribute.

[0115] In an embodiment of the present invention, version information of the current version file in the firewall is collected, wherein the version information at least includes: a version path and a current version attribute, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; according to the current version attribute, a target version attribute of the target version file is determined in the version set; the firewall is upgraded based on the difference between the current version attribute and the target version attribute; thereby, the version path is obtained based on the version information of the current version file running in the firewall, and the version file can be automatically obtained from the version set based on the version path for upgrading, thereby achieving the purpose of automatically upgrading the firewall, realizing the technical effect of improving the efficiency of firewall upgrading, and thus solving the technical problem of low efficiency of existing firewall upgrading.

[0116] Optionally, the version attributes include at least: a product series identifier and a version branch identifier, wherein the product series identifier is a first-level management identifier of the version file, and the version branch identifier is a second-level management identifier of the version file. The above-mentioned processor can also execute the program code of the following steps: collecting the current version attributes of the firewall; identifying the current product series identifier and the current version branch identifier in the current version attributes; generating a version path based on the current product series identifier, the current version branch identifier and the preset root directory.

[0117] Optionally, the version attributes also include: a version platform identifier and version release information, wherein the version platform identifier is a third-level management identifier of the version file; the above-mentioned processor can also execute the program code of the following steps: identifying the current version platform identifier in the current version attributes; filtering the version subset corresponding to the current version platform identifier in the version collection, wherein the version files in the version subset have the same version platform identifier; selecting the latest released version file in the version subset as the target version file based on the version release information; and determining the target version attribute of the target version file.

[0118] Optionally, the version release information indicates the release order of the version files through version codes; the processor may also execute program code of the following steps: according to the version code, selecting the version file with the last release order in the version subset as the target version file.

[0119] Optionally, the version release information indicates the release time of the version file through the version time; the processor may also execute the program code of the following steps: according to the version time, selecting the version file with the most recent release time in the version subset as the target version file.

[0120] Optionally, the processor may also execute the program code of the following steps: determining the current version file corresponding to the current version attribute and the target version file corresponding to the target version attribute in the version set; determining the version file to be upgraded based on the current version file and the target version file, wherein the version file to be upgraded includes at least: the target version file, and the transition version file released between the current version file and the target version file; and upgrading the firewall based on the version file to be upgraded.

[0121] By adopting the embodiment of the present invention, a firewall upgrade solution is provided. By collecting the version information of the current version file in the firewall, wherein the version information at least includes: a version path and a current version attribute, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has a corresponding version attribute; according to the current version attribute, the target version attribute of the target version file is determined in the version set; the firewall is upgraded based on the difference between the current version attribute and the target version attribute; thus, the version path is obtained based on the version information of the current version file running in the firewall, and the version file can be automatically obtained from the version set based on the version path for upgrading, thereby achieving the purpose of automatically upgrading the firewall, realizing the technical effect of improving the upgrade efficiency of the firewall, and thus solving the technical problem of low upgrade efficiency of the existing firewall.

[0122] It can be understood by those skilled in the art that Fig.12 The structure shown is for illustration only, and the computer terminal may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a handheld computer, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Fig.12 The structure of the electronic device is not limited. For example, the computer terminal 120 may also include Fig.12 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Fig.12 Different configurations are shown.

[0123] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0124] The embodiment of the present invention further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the firewall upgrade method provided in the above embodiment.

[0125] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0126] Optionally, in this embodiment, the storage medium is configured to store program code for executing the following steps: collecting version information of the current version file in the firewall, wherein the version information includes at least: a version path and current version attributes, the version path stores a version set corresponding to the current version file, the version set stores at least one version file corresponding to the firewall, and each version file has corresponding version attributes; according to the current version attributes, determining a target version attribute of the target version file in the version set; and upgrading the firewall based on the difference between the current version attributes and the target version attributes.

[0127] Optionally, in this embodiment, the version attributes include at least: a product series identifier and a version branch identifier, wherein the product series identifier is a first-level management identifier of the version file, and the version branch identifier is a second-level management identifier of the version file, and the storage medium is configured to store program code for executing the following steps: collecting the current version attributes of the firewall; identifying the current product series identifier and the current version branch identifier in the current version attributes; and generating a version path based on the current product series identifier, the current version branch identifier and the preset root directory.

[0128] Optionally, in this embodiment, the version attributes also include: a version platform identifier and version release information, wherein the version platform identifier is a third-level management identifier of the version file; the storage medium is configured to store program code for executing the following steps: identifying the current version platform identifier in the current version attributes; filtering a version subset corresponding to the current version platform identifier in the version collection, wherein the version files in the version subset have the same version platform identifier; selecting the latest released version file in the version subset as the target version file based on the version release information; and determining the target version attributes of the target version file.

[0129] Optionally, in this embodiment, the version release information indicates the release order of the version files through version codes; the storage medium is configured to store program code for executing the following steps: according to the version code, selecting the version file with the last release order in the version subset as the target version file.

[0130] Optionally, in this embodiment, the version release information indicates the release time of the version file through the version time; the storage medium is configured to store program code for executing the following steps: according to the version time, selecting the version file with the most recent release time in the version subset as the target version file.

[0131] Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: determining a current version file corresponding to a current version attribute and a target version file corresponding to a target version attribute in a version set; determining a version file to be upgraded based on the current version file and the target version file, wherein the version file to be upgraded includes at least: a target version file, a transition version file released between the current version file and the target version file; and upgrading the firewall based on the version file to be upgraded.

[0132] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0133] In the above embodiments of the present invention, 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.

[0134] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0135] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0136] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0137] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0138] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for upgrading a firewall, characterized in that: include: Collecting version information of the current version file in the firewall, wherein the version information at least includes: a version path and current version attributes, wherein the version path stores a version set corresponding to the current version file, wherein the version set is a folder for storing version files, wherein the version set stores at least one version file corresponding to the firewall, wherein each version file has corresponding version attributes, wherein the version attributes at least include: a product series identifier and a version branch identifier, wherein the product series identifier is a primary management identifier of the version file, and the version branch identifier is a secondary management identifier of the version file; Determining a target version attribute of a target version file in the version set according to the current version attribute; Upgrading the firewall based on the difference between the current version attribute and the target version attribute; The version information of the collected firewall includes: Collecting the current version attributes of the firewall; Identify the current product series identifier and the current version branch identifier in the current version attribute; The version path is generated based on the current product series identifier, the current version branch identifier and the preset root directory.

2. The method according to claim 1, characterized in that The version attribute also includes: a version platform identifier and version release information, wherein the version platform identifier is a third-level management identifier of the version file; according to the current version attribute, determining the target version attribute of the target version file in the version set includes: Identify the current version platform identifier in the current version attribute; Filtering the version subset corresponding to the current version platform identifier in the version set, wherein the version files in the version subset have the same version platform identifier; Selecting the latest released version file from the version subset as the target version file based on the version release information; A target version attribute of the target version file is determined.

3. The method according to claim 2, characterized in that The version release information indicates the release order of the version files through version codes; and selecting the latest released version file in the version subset as the target version file based on the version release information includes: According to the version code, the version file with the latest release order is selected in the version subset as the target version file.

4. The method according to claim 2, characterized in that: The version release information indicates the release time of the version file through the version time; and selecting the latest released version file in the version subset as the target version file based on the version release information includes: According to the version time, the version file with the most recent release time is selected from the version subset as the target version file.

5. The method according to claim 1, characterized in that Upgrading the firewall based on the difference between the current version attribute and the target version attribute includes: Determine in the version set a current version file corresponding to the current version attribute and a target version file corresponding to the target version attribute; Determine a version file to be upgraded according to the current version file and the target version file, wherein the version file to be upgraded at least includes: the target version file, and a transition version file released between the current version file and the target version file; The firewall is upgraded according to the version file to be upgraded.

6. A firewall upgrade device, characterized in that: include: A collection unit, used for collecting version information of the current version file in the firewall, wherein the version information at least includes: a version path and a current version attribute, wherein the version path stores a version set corresponding to the current version file, wherein the version set is a folder for storing version files, wherein the version set stores at least one version file corresponding to the firewall, wherein each version file has a corresponding version attribute, wherein the version attribute at least includes: a product series identifier and a version branch identifier, wherein the product series identifier is a primary management identifier of the version file, and the version branch identifier is a secondary management identifier of the version file; a determining unit, configured to determine a target version attribute of a target version file in the version set according to the current version attribute; An upgrading unit, configured to upgrade the firewall based on a difference between the current version attribute and the target version attribute; Wherein, the acquisition unit comprises: A collection module, used for collecting the current version attributes of the firewall; A first identification module, used to identify the current product series identifier and the current version branch identifier in the current version attribute; A generation module is used to generate the version path based on the current product series identifier, the current version branch identifier and the preset root directory.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the firewall upgrade method according to any one of claims 1 to 5.

8. A processor, characterized in that: The processor is used to run a program, wherein the program executes the firewall upgrade method described in any one of claims 1 to 5 when running.

Images