Patch installation method, patch server, patch installation system and storage medium
By automatically comparing device configuration information with the patch server, identifying and packaging patches to be installed in real time, the problem of large workload and insufficient timeliness of patch installation in data centers is solved. This enables real-time automatic installation and incremental updates of patches, improving the stability of device operation.
Patent Information
- Application Number
- CN202511068982.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-31
- Publication Date
- 2025-11-07
AI Technical Summary
In data centers, existing technologies cannot effectively solve the problems of large workload for patch installation, complex patch package management, insufficient timeliness, and inability to install in a timely manner caused by the increase in the number of devices.
By obtaining the latest patch files and configuration information from the patch server, comparing the device configuration information, automatically determining the patches to be installed, packaging and distributing them, the system achieves real-time automatic installation and incremental updates of patches.
It enables real-time automatic patch installation, simplifies operation steps, saves time, and improves the timeliness of patch installation and the operational stability of network devices.
Smart Images

Figure CN120909620A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the field of data center network equipment, in particular to a patch installation method, a patch server, a system and a storage medium. BACKGROUND
[0002] Patch technology is a technology for dynamically repairing system vulnerabilities or defects without restarting the system or program, and its core advantage is to quickly and accurately repair system vulnerabilities or defects under the premise of ensuring business continuity. However, with the development of data center scale, the number of network devices has increased exponentially, and the number of device software versions that need to be maintained has also increased rapidly. When using patch technology for data center device maintenance operations, the following problems may be encountered: A. The number of devices that need to be operated increases, and the workload of maintenance personnel for patch checking and installation also increases exponentially.
[0003] B. Because the patch package is bound to the system software version, the increase in the data center system software version requires maintenance personnel to maintain a large number of patch packages of different versions.
[0004] C. Due to the increase in the number of devices and system versions, maintenance personnel cannot install patch packages in a timely manner.
[0005] In the existing technology, a patch server is configured to store, distribute and automatically install patch packages. This includes checking whether the system patch of the network device is stored in the patch medium storage server based on the system software version, downloading the corresponding system patch if the system patch of the network device is stored in the patch medium storage server, and automatically installing the system patch. However, the above technology cannot solve the following problems: A. Patch installation necessity problem. Devices often have software characteristics, hardware component differences and other problems, and simply relying on system software version may result in unnecessary patch file installation.
[0006] B. Timeliness of patch installation. The existing technology generally uses a server to trigger patch package automatic installation at a specified time or manually. There may be a lag in the installation of patch packages for serious vulnerabilities.
[0007] C. Network devices that cannot access the patch server due to special reasons need to be manually installed with patch packages, which is complex if there are many patches. SUMMARY
[0008] Therefore, the present application aims to provide a patch installation method, a patch server, a system and a storage medium to solve at least some of the problems in the prior art.
[0009] To achieve the above-mentioned purpose, the technical solutions adopted by the embodiments of the present application are as follows: In a first aspect, an embodiment of the present application provides a patch installation method applied to a patch server, the method comprising: acquiring and saving the latest released patch file and corresponding patch configuration information; receiving and saving the device configuration information uploaded by each managed network device; comparing the patch configuration information with the device configuration information, determining the network device to be installed with patches according to the comparison result, and acquiring all corresponding patches to be installed; packaging and issuing all the patches to be installed to the network device to be installed with patches, so that the network device to be installed with patches installs the patches.
[0010] In an optional implementation, the step of comparing the patch configuration information with the device configuration information comprises: when it is determined that there is the latest released patch file, comparing the patch configuration information corresponding to the latest released patch file with the device configuration information of all current managed network devices respectively; when it is determined that the configuration information of any managed network device is updated, comparing the patch configuration information corresponding to all current patch files with the current device configuration information of the any managed network device respectively.
[0011] In an optional implementation, the device configuration information comprises hardware configuration information and / or software configuration information; the patch configuration information comprises patch corresponding software configuration and / or patch corresponding hardware configuration; the step of comparing the patch configuration information with the device configuration information, determining the network device to be installed with patches according to the comparison result, and acquiring all corresponding patches to be installed comprises: if at least one of the hardware configuration information and the software configuration information has corresponding content in the patch corresponding software configuration and / or the patch corresponding hardware configuration, it is determined that the network device corresponding to the device configuration information is the network device to be installed with patches.
[0012] In an optional implementation, the step of packaging and issuing all the patches to be installed to the network device to be installed with patches comprises: packaging all the patches to be installed into one patch service package; the patch service package comprises patch service package header information and patch files; the service package header information comprises patch quantity, the file name of each patch, and the offset information of each patch in the patch service package file; issuing the patch service package to the network device to be installed with patches.
[0013] In a second aspect, an embodiment of the present application provides a patch server, comprising: a patch obtaining module, configured to obtain and save the latest published patch file and corresponding patch configuration information; a configuration receiving module, configured to receive and save the device configuration information uploaded by each managed network device; an information comparing module, configured to compare the patch configuration information with the device configuration information, determine the network device to be installed with the patch according to the comparison result, and obtain all corresponding network devices to be installed with the patch; a patch issuing module, configured to package and issue all the network devices to be installed with the patch to the network device to be installed with the patch, so that the network device to be installed with the patch installs the patch.
[0014] In an optional implementation, the information comparing module is specifically configured to: when it is determined that there is the latest published patch file, compare the patch configuration information corresponding to the latest published patch file with the device configuration information of all the current managed network devices respectively; when it is determined that the configuration information of any managed network device is updated, compare the patch configuration information corresponding to all the current patch files with the current device configuration information of the any managed network device.
[0015] In an optional implementation, the device configuration information includes hardware configuration information and / or software configuration information; the patch configuration information includes patch corresponding software configuration and / or patch corresponding hardware configuration; and the information comparing module is further configured to: if at least one of the hardware configuration information and the software configuration information has corresponding content in the patch corresponding software configuration and / or patch corresponding hardware configuration, it is determined that the network device corresponding to the device configuration information is the network device to be installed with the patch.
[0016] In an optional implementation, the patch issuing module further includes: a packaging submodule, configured to package all the network devices to be installed with the patch into one patch service package; the patch service package includes patch service package header information and patch files; the patch service package header information includes patch quantity, the file name of each patch, and the offset information of each patch in the patch service package file; an issuing submodule, configured to issue the patch service package to the network device to be installed with the patch.
[0017] In a third aspect, an embodiment of the present application provides a patch installation system, including a patch server and a network device. The patch server is configured to acquire and save the latest published patch file and corresponding patch configuration information, receive and save the device configuration information uploaded by each managed network device, compare the patch configuration information with the device configuration information, determine the network device to be installed with the patch according to the comparison result, acquire all corresponding patches to be installed, and package and issue all the patches to be installed to the network device to be installed with the patch. The network device is configured to install the patch to be installed.
[0018] In a fourth aspect, a computer readable storage medium is provided, and a computer program is stored in the computer readable storage medium, and the computer program is executed by a processor to implement the patch installation method in the first aspect.
[0019] The patch installation method provided by the embodiments of the present application does not require maintenance personnel to check each network device one by one to determine whether the network device needs to be installed with a patch, and the patch installation process can be triggered by comparing the patch configuration information with the device configuration information, so that the real-time automatic installation of the patch is realized. In addition, the corresponding patch to be installed can be acquired according to the device configuration information, so that the incremental update of the patch is realized, the patch installation time is saved, and the operation steps of the patch installation are also simplified by packaging and issuing all the patches to be installed to the network device.
[0020] In order to make the above objectives, characteristics and advantages of the present application more apparent and comprehensible, the following preferred embodiments are specifically described below, and the accompanying drawings are referred to, and the detailed description is as follows. BRIEF DESCRIPTION OF DRAWINGS
[0021] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments, and it should be understood that the following drawings only show some embodiments of the present application, and should not be regarded as a limitation to the scope, and for those skilled in the art, other related drawings can also be obtained without creative labor on the basis of the drawings.
[0022] Figure 1 A block schematic diagram of a patch server provided by the embodiments of the present application is shown; Figure 2 A flow schematic diagram of a patch installation method provided by the embodiments of the present application is shown; Figure 3 A schematic diagram of the interaction principle between a server and a network device provided by the embodiments of the present application is shown; Figure 4 A module schematic diagram of a patch server provided by the embodiments of the present application is shown.
[0023] FIG. 100-patch server; 110-memory; 120-processor; 130-communication module; 200-network device; 300-patch installation agent software; 401-patch acquisition module; 402-configuration receiving module; 403-information comparison module; 404-patch issuing module. DETAILED DESCRIPTION
[0024] The technical solutions in 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. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the accompanying drawings can be arranged and designed in various different configurations.
[0025] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.
[0026] It should be noted that the relational terms such as "first" and "second" and the like are used only to distinguish one entity or operation from another, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms "comprising", "including" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or apparatus including a series of elements includes not only those elements, but also other elements not explicitly listed or inherent to such a process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus including the element.
[0027] Please refer to Figure 1 is a block schematic diagram of the patch server 100. The patch server 100 includes a memory 110, a processor 120 and a communication module 130. The memory 110, the processor 120 and the communication module 130 are directly or indirectly electrically connected to each other to realize data transmission or interaction. For example, these elements can be electrically connected to each other through one or more communication buses or signal lines.
[0028] The memory 110 is configured to store programs or data. The memory 110 can be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electric Erasable Programmable Read-Only Memory (EEPROM), etc.
[0029] The processor 120 is configured to read / write the data or programs stored in the memory 110 and perform corresponding functions.
[0030] The communication module 130 is configured to establish a communication connection between the patch server 100 and other communication terminals through the network and to receive / transmit data through the network.
[0031] It should be understood that, Figure 1 The structure shown is only a structural schematic diagram of the patch server 100, and the patch server 100 can further include more or less components than those shown in the drawings or have a different configuration from that shown in the drawings. Figure 1 The components shown in the drawings can be implemented in hardware, software, or a combination thereof. Figure 1 Figure 1 The components shown in the drawings can be implemented in hardware, software, or a combination thereof.
[0032] Please refer to Figure 2 , Figure 2 A flowchart of a patch installation method provided by an embodiment of the present application is shown, the method being applied to a patch server, and the method comprising: S101, obtaining and saving a newly released patch file and corresponding patch configuration information.
[0033] In order to facilitate the searching and installation of patches, a corresponding patch configuration information table can be generated according to patch information, and the patch configuration information table mainly includes: a file name of the patch, a storage path, software configuration corresponding to the patch, and / or hardware configuration corresponding to the patch. The software configuration corresponding to the patch and / or the hardware configuration corresponding to the patch include: a system version bound by the patch, a feature involved by a vulnerability or defect solved by the patch, a hardware component involved by the vulnerability or defect solved by the patch, and a trigger factor of the vulnerability or defect. The trigger factor can include configuration switches, feature specifications, hardware classifications, etc. that trigger the vulnerability or defect. When a new version of the patch is released, the patch is uploaded to the server, and the corresponding patch configuration information table is improved.
[0034] In order to realize timely installation of the patch, a timer can be set on the patch server to acquire patch information and device configuration information of the network device at a timing, and then it is judged whether the patch information and the device configuration information satisfy preset conditions, i.e. patch installation conditions. When the patch installation conditions are satisfied, corresponding patch installation procedures are performed on the network device. The patch information can be directly obtained by querying the patch configuration information table.
[0035] S102, receive and save the device configuration information uploaded by each managed network device.
[0036] The number of network devices can be multiple, and the device configuration information of each network device can be queried in turn by polling, or the network device uploads the device configuration information to the server at a timing. The patch server can also collect information of all network devices connected to the server, and generate a configuration information table of the corresponding network device, thereby improving the query efficiency of the network device.
[0037] S103, compare the patch configuration information with the device configuration information, determine the network device to be installed with the patch according to the comparison result, and acquire all corresponding patches to be installed.
[0038] Among all the published patches, the network device can have installed a part of the patches. When the configuration of the network device changes and patch installation is required, the patch configuration information can be compared with the device configuration information, the network device to be installed with the patch is determined according to the comparison result, and the corresponding patch to be installed by the network device is determined, and then the network device is installed with the patch to be installed, thereby realizing incremental update of the patch. When a new patch is published, all managed network devices are polled, the patch configuration information can be compared with the device configuration information, and the network device to be installed with the patch is determined according to the comparison result.
[0039] S104, package and issue all the patches to be installed to the network device to be installed with the patch, so that the network device to be installed with the patch installs the patch to be installed.
[0040] Each network device to be installed with the patch can correspond to multiple patches to be installed. In order to simplify the installation operation, the multiple patches to be installed corresponding to each network device to be installed with the patch can be packaged and issued.
[0041] The embodiment realizes real-time automatic installation of the patch. In addition, the patch to be installed can be acquired according to the device configuration information, thereby realizing incremental update of the patch, saving patch installation time, and simplifying the operation steps of patch installation by packaging and issuing all the patches to be installed to the network device.
[0042] Refer toFigure 3 , Figure 3 Fig. 1 shows a schematic diagram of the interaction principle between a patch server and network devices according to an embodiment of the present application.
[0043] The patch server 100 is in communication connection with the network devices 200, wherein the number of the network devices 200 can be multiple, the patch server 100 stores various patches, each network device 200 can be installed with a patch installation agent software 300, the patch installation agent software 300 is used for collecting configuration of the network device 200, monitoring service, and communicating with the patch server 100.
[0044] In some scenarios, when the network device 200 cannot install the patch installation agent software 300, or the data processing capability of the network device 200 is poor, the patch installation agent software 300 can also be installed on the patch server 100, and the patch server 100 manages and controls the patch installation of the network device 200.
[0045] When the patch configuration information meets the preset condition or the device configuration information meets the preset condition, or both meet the preset condition, the steps of patch packaging and installation can be performed.
[0046] In an embodiment, the step of comparing the patch configuration information with the device configuration information comprises: When there is a newly released patch file, comparing the patch configuration information corresponding to the newly released patch file with the device configuration information of all currently managed network devices respectively; When the configuration information of any managed network device is updated, comparing the patch configuration information corresponding to all current patch files with the current device configuration information of the any managed network device.
[0047] Generally, when the patch is updated (i.e. there is a new patch version), it is determined whether the network device needs to be patched according to the patch configuration information of the released patch. All patches can be obtained through the patch configuration information table, so the information recorded in the patch configuration information table can be used to determine whether the patch is updated.
[0048] For example, the number of patches, the file name of the patch and other patch information in the patch configuration information table can be obtained and recorded at regular intervals, and then it is determined whether the current patch information is the same as the patch information at the previous time. If they are different, it means that the patch is updated, i.e. it is determined whether there is a newly released patch. At this time, the network device which needs to be patched can be determined according to the updated patch.
[0049] Alternatively, all patches are sorted according to the update time and other information of the patches in the patch configuration information table. Only the first or several patch information in the patch configuration information table needs to be checked periodically to determine whether the patch has been updated, i.e., whether there is a newly released patch.
[0050] In some scenarios, when a new patch is released, the updated patch may be for some network devices, and other devices do not need to install the patch. At this time, when the device configuration information of the other devices is queried to query the to-be-installed patch, the corresponding to-be-installed patch may not be queried, i.e., the number of to-be-installed patches is zero. For the network device with the number of to-be-installed patches being zero, it is indicated that the patch does not need to be installed, and only the network device with the number of to-be-installed patches being non-zero needs to be installed.
[0051] In addition to the update of the patch, the device configuration information of the network device may also change. When the device configuration information of the network device changes, various problems may occur in the network device, such as software and hardware incompatibility, and conflict between different configuration information. At this time, the corresponding patch needs to be downloaded for repair, so that the network device can operate normally.
[0052] Therefore, the device configuration information of the network device needs to be acquired in real time or periodically, and it is determined whether the device configuration information has changed. A patch installation agent software can be installed on the network device to acquire the device configuration information and record the device configuration information acquired each time. If the current device configuration information is different from the device configuration information at the previous moment, it is determined that the device configuration information has changed. At this time, the corresponding to-be-installed patch can be queried according to the current device configuration information. In some scenarios, after the configuration information of the network device changes, the network device can still operate normally. At this time, the to-be-installed patch may not be queried according to the current device configuration information, i.e., the number of to-be-installed patches is zero. At this time, the network device does not need to be installed with the patch.
[0053] In this embodiment, the patch file and the network device are monitored in real time to determine whether a newly released patch or the configuration information of the network device is updated. When the patch is released or the device configuration information is updated, the information is compared accordingly, so that the patch can be installed in time.
[0054] In an implementation manner, the device configuration information includes hardware configuration information and / or software configuration information; the patch configuration information includes software configuration corresponding to the patch and / or hardware configuration corresponding to the patch; and the step of comparing the patch configuration information with the device configuration information and determining the network device with to-be-installed patches and acquiring all corresponding to-be-installed patches according to the comparison result includes: If at least one of the hardware configuration information and the software configuration information corresponds to the patch, the network device corresponding to the device configuration information is determined as the network device to which the patch is to be installed.
[0055] The device configuration information mainly includes device version information, hardware configuration information and software configuration information, wherein the hardware information mainly includes CPU, switching chip, FUR (Furnace) device, wherein the FUR device includes BBU (Building baseband Unit), LPU (Language Processing Unit) and SFU (Switch Fabric Unit) and the like. The software information mainly includes system software version, installed patch package information, software characteristics and the like.
[0056] The device configuration information of the network device includes version information, hardware configuration information and software configuration information, and any change of any kind of configuration information can cause the network device to malfunction, therefore, when any kind of configuration information changes, it is necessary to determine whether the network device needs to be installed with a patch.
[0057] The embodiment monitors the device configuration information of the network device in multiple aspects, so that the network device can be installed with a patch in time when the device configuration information changes, thereby ensuring the real-time performance of the patch installation and improving the stability of the network device.
[0058] In an embodiment, the step of packaging and issuing all the patches to be installed to the network device to which the patch is to be installed comprises: packaging all the patches to be installed into a patch service package; the patch service package includes patch service package header information and patch files; the patch service package header information includes patch quantity, file name of each patch and offset information of each patch in the patch service package file; issuing the patch service package to the network device to which the patch is to be installed.
[0059] The connection mode of the server and the network device can be the same as or different from the connection mode of the server and the patch installation agent software. For example, the server and the network device can be connected through a network cable, and the server and the patch installation agent software can be connected through WiFi. The network cable communication is usually faster and more stable than the WiFi communication, therefore, the server can preferentially send the patch to be installed to the network device, and when the network device cannot be normally connected with the server or the communication quality between the network device and the server is poor, the server can package and send the patch to be installed to the patch installation agent software.
[0060] When the patch to be installed is packaged into a patch service package, corresponding patch service package header information can be generated, which includes the number of patches, the file name of each patch, the offset information of each patch in the patch service package file, etc., so as to record the patch service package information and facilitate the subsequent tracking when problems occur.
[0061] The embodiment realizes the communication interaction between the network device and the server in multiple ways. When part of the communication methods cannot be normally used, the patch to be installed can be distributed to the network device through other communication methods, the timely installation of the patch is realized, and the stability of the network device is ensured.
[0062] In an embodiment, the method further comprises: generating patch configuration information table according to the patch information, and querying the newly released patch corresponding to the device configuration information from the patch configuration information table; obtaining the installed patch corresponding to the network device through the patch installation agent software, and determining the patch to be installed according to the newly released patch and the installed patch; the patch to be installed is the patch in the released patch except the installed patch.
[0063] Different patches can be directed to different network devices. Therefore, in order to realize the rapid installation of the patch, the patch can be classified according to the network device corresponding to the patch. When the patch is released, the network device corresponding to the released patch can be quickly located, and then the network device which needs to be installed with the patch can be determined according to the specific information of the network device, so that it is not necessary to traverse all network devices when the patch is released, and the efficiency of the patch installation is greatly improved.
[0064] In an embodiment, the method further comprises: if the patch installation configuration information is the timing installation information, installing the patch to be installed according to the installation time corresponding to the timing installation information; if the patch installation configuration information is the real-time installation information, obtaining the running state of the network device in real time through the patch installation agent software, and installing the patch to be installed according to the running state.
[0065] For example, some network devices are set with patch installation time, such as installing the patch one hour after receiving the patch, or installing the patch at night after receiving the patch. At this time, the patch installation agent software on the network device can install the patch according to the set patch installation time.
[0066] The patch installation time of some network devices can not be set with a specific installation time, and then the patch installation agent software can monitor the running state of the network device in real time or at a fixed time, temporarily not performing patch installation when the network device is busy, and performing patch installation when the network device is idle, so as to maximize the normal work of the network device and save the patch installation time.
[0067] Please refer to Figure 4 , Figure 4 A functional module diagram of a patch server is provided for an embodiment of the application. It should be noted that the patch server 100 provided in the embodiment has the same basic principles and technical effects as the above method embodiments, and for brief description, the part not mentioned in the embodiment can refer to the corresponding content in the above embodiments. The patch server 100 comprises: A patch acquisition module 401 is configured to acquire and save the latest published patch file and corresponding patch configuration information; A configuration receiving module 402 is configured to receive and save the device configuration information uploaded by each managed network device; An information comparison module 403 is configured to compare the patch configuration information with the device configuration information, determine the network device to be installed with patches according to the comparison result, and acquire all corresponding patches to be installed; A patch issuing module 404 is configured to package and issue all the patches to be installed to the network device to be installed with patches, so that the network device to be installed with patches installs the patches to be installed.
[0068] In an embodiment, the information comparison module is specifically configured to: When it is determined that there is a latest published patch file, compare the patch configuration information corresponding to the latest published patch file with the device configuration information of all current managed network devices respectively; When it is determined that the configuration information of any managed network device is updated, compare the patch configuration information corresponding to all current patch files with the current device configuration information of the any managed network device respectively.
[0069] In an embodiment, the device configuration information comprises hardware configuration information and / or software configuration information; the patch configuration information comprises patch corresponding software configuration and / or patch corresponding hardware configuration; and the information comparison module is further configured to: If at least one of the hardware configuration information and the software configuration information has corresponding content in the patch corresponding software configuration and / or patch corresponding hardware configuration, it is determined that the network device corresponding to the device configuration information is the network device to be installed with patches.
[0070] In an embodiment, the patch issuing module further comprises: a packaging submodule, configured to package all the to-be-installed patches into one patch service package; the patch service package comprises patch service package header information and patch files; the patch service package header information comprises patch quantity, file name of each patch, and offset information of each patch in the patch service package file; a delivery submodule, configured to deliver the patch service package to the network device to which the to-be-installed patch belongs.
[0071] In one embodiment, the embodiment of the present application further provides a patch installation system, comprising a patch server and a network device; The patch server is configured to acquire and save the latest published patch file and corresponding patch configuration information, acquire and save the device configuration information uploaded by each managed network device, compare the patch configuration information with the device configuration information, determine the network device to which the to-be-installed patch belongs according to the comparison result, acquire all the corresponding to-be-installed patches, and deliver all the to-be-installed patches to the network device to which the to-be-installed patch belongs. The network device is configured to install the to-be-installed patch.
[0072] In several embodiments provided in the present application, it should be understood that the disclosed system and method can also be implemented by other manners. The system embodiments described above are only illustrative, for example, the flowchart and block diagram in the drawings show the possible implementation architecture, function and operation of the system, method and computer program product according to the embodiments of the present application. In this regard, each block in the flowchart or block diagram can represent a module, program segment or part of code, which comprises one or more executable instructions for implementing the specified logic function. It should also be noted that in some alternative implementation manners, the functions marked in the blocks can also occur in different order from that marked in the drawings. For example, two continuous blocks can actually be executed substantially in parallel, and sometimes they can be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for executing the specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.
[0073] In addition, each functional module in each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.
[0074] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts of the technical solutions that essentially contribute to the prior art or the parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the various embodiments of the present application. The aforementioned storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.
[0075] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.
Claims
1. A patch mounting method characterized by, Applied to a patch server, the method comprises: Obtaining and saving the latest published patch file and corresponding patch configuration information; Receiving and saving the device configuration information uploaded by each managed network device; Comparing the patch configuration information with the device configuration information, determining the network device to be installed with patches according to the comparison result, and obtaining all corresponding to-be-installed patches; Packaging and issuing all the to-be-installed patches to the network device to be installed with patches, so that the network device to be installed with patches installs the to-be-installed patches.
2. The patch mounting method according to claim 1, characterized by, The step of comparing the patch configuration information with the device configuration information comprises: When there is a latest published patch file, comparing the patch configuration information corresponding to the latest published patch file with the device configuration information of all current managed network devices respectively; When the configuration information of any managed network device is updated, comparing the patch configuration information corresponding to all current patch files with the current device configuration information of the any managed network device respectively.
3. The patch mounting method according to claim 1 or 2, characterized by, The device configuration information comprises hardware configuration information and / or software configuration information; the patch configuration information comprises patch corresponding software configuration and / or patch corresponding hardware configuration; the step of comparing the patch configuration information with the device configuration information, determining the network device to be installed with patches according to the comparison result, and obtaining all corresponding to-be-installed patches comprises: If at least one of the hardware configuration information and the software configuration information has corresponding content in the patch corresponding software configuration and / or patch corresponding hardware configuration, it is determined that the network device corresponding to the device configuration information is the network device to be installed with patches.
4. The patch mounting method according to claim 1, characterized by, The step of packaging and issuing all the to-be-installed patches to the network device to be installed with patches comprises: Packaging all the to-be-installed patches into a patch service package; the patch service package comprises patch service package header information and patch files; the patch service package header information comprises patch quantity, file name of each patch, and offset information of each patch in the patch service package file; Issuing the patch service package to the network device to be installed with patches.
5. A patch server, characterized in that, Comprise: A patch acquisition module for obtaining and saving the latest published patch file and corresponding patch configuration information; A configuration receiving module for receiving and saving the device configuration information uploaded by each managed network device; An information comparison module for comparing the patch configuration information with the device configuration information, determining the network device to be installed with patches according to the comparison result, and obtaining all corresponding to-be-installed patches; A patch issuing module for packaging and issuing all the to-be-installed patches to the network device to be installed with patches, so that the network device to be installed with patches installs the to-be-installed patches.
6. The patch server of claim 5, wherein, The information comparison module is specifically used for: When there is a latest published patch file, comparing the patch configuration information corresponding to the latest published patch file with the device configuration information of all current managed network devices respectively; When the configuration information of any managed network device is updated, comparing the patch configuration information corresponding to all current patch files with the current device configuration information of the any managed network device respectively.
7. The patch server according to claim 5 or 6, characterized in that, The device configuration information includes hardware configuration information and / or software configuration information; the patch configuration information includes patch corresponding software configuration and / or patch corresponding hardware configuration; the information comparison module is further used for: If at least one of the hardware configuration information and the software configuration information corresponds to the content of the patch corresponding software configuration and / or patch corresponding hardware configuration, it is determined that the network device corresponding to the device configuration information is a network device to be installed with a patch.
8. The patch server of claim 5, wherein, The patch issuing module further includes: A packaging submodule, configured to package all the to-be-installed patches into one patch service package; the patch service package includes patch service package header information and patch files; the patch service package header information includes patch quantity, the file name of each patch, and the offset information of each patch in the patch service package file; An issuing submodule, configured to issue the patch service package to the network device to be installed with a patch.
9. A patch installation system characterized by comprising: The patch server and the network device are included; The patch server is configured to acquire and save the latest published patch file and corresponding patch configuration information, receive and save the device configuration information uploaded by each managed network device, compare the patch configuration information with the device configuration information, determine the network device to be installed with a patch according to the comparison result, acquire all corresponding to-be-installed patches, and package and issue all the to-be-installed patches to the network device to be installed with a patch; The network device is configured to install the to-be-installed patch.
10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the patch installation method according to any one of claims 1-4.