CN103823693A - Service pack installation method - Google Patents
Service pack installation method Download PDFInfo
- Publication number
- CN103823693A CN103823693A CN201410028711.XA CN201410028711A CN103823693A CN 103823693 A CN103823693 A CN 103823693A CN 201410028711 A CN201410028711 A CN 201410028711A CN 103823693 A CN103823693 A CN 103823693A
- Authority
- CN
- China
- Prior art keywords
- patch
- patch package
- installation
- package
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000009434 installation Methods 0.000 title claims abstract description 156
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000004458 analytical method Methods 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 230000008439 repair process Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012300 Sequence Analysis Methods 0.000 description 1
- 241000700605 Viruses Species 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
An embodiment of the invention discloses a service pack installation method and device. The method includes: according to bugs and related service packs thereof, generating service pack installation conditions including a registry table and/or file information based on each service pack; judging whether installation objects corresponding to the service packs satisfy the service pack installation conditions or not; if so, downloading and installing the service packs. The step for downloading and installing the service packs includes downloading and installing the service packs in sequence, or downloading each service pack and only installing a latest service pack in each service pack, or only downloading and installing the latest service pack in each service pack. When the method and the device are applied for pack installation, judgment conditions of the bug service packs are simple, and when multiple bug are detected at the same time, failure in service pack installation is possibly avoided by the service pack installation sequence; moreover, the latest service packs can be installed selectively, so that repeated bug fixes can be avoided, and system resources are saved.
Description
The patent application of the invention is a divisional application of Chinese patent application with the application date of 2011, 2 and 21, and the application number of 201110041779.8, entitled "method and device for installing patch package".
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for installing a patch package.
Background
In the process of software application, for example, various operating systems, various games, etc., it may be found that there is a problem or BUG, also called BUG, in the software, the BUG may interfere with the situation that a user is utilized by trojans, viruses or malicious software when using the software, or may reduce the security performance of the system and the software, so that the BUG may be repaired by modifying or updating the affected program or module to write some program language that can be inserted into the source program, and the program language for repairing the BUG is called patch package.
Taking operating system software as an example, a special website in the prior art may periodically release a patch package within a period of time, and a user may repair a related bug of the operating system by downloading and installing the patch package. However, the inventor finds that the following problems exist in the process of vulnerability determination and patch installation in the process of research on the prior art:
1. when a plurality of bugs are detected at the same time, the patch installation sequence may cause the installation of part of patches to fail;
2. repeated repairs to files that are also affected result in wasted system resources and poor user experience.
Disclosure of Invention
The embodiment of the application aims to provide a method and a device for installing a patch package so as to improve the installation power of the patch package and ensure the safety performance of a system.
In order to solve the technical problem, the embodiment of the application discloses the following technical scheme:
a method of installing a patch package, comprising:
generating patch package installation conditions based on registry and/or file information of each patch package according to the loopholes and related patch packages;
judging whether the installation object corresponding to the patch package meets the installation condition of the patch package;
when the installation condition of the patch package is met, downloading and installing the patch package; wherein,
the downloading and installing the patch package comprises:
and downloading and installing each patch package in sequence, or downloading each patch package and installing only the latest patch package in each patch package, or downloading and installing only the latest patch package in each patch package.
The registry information in the patch package installation condition includes: registry keys, registry key values;
the file information in the patch package installation condition comprises: file version information, file attributes.
The judging whether the installation object corresponding to the current patch package meets the installation condition of the patch package comprises the following steps:
it is determined whether a specified registry key, a value of the specified registry key, or a specified file exists in the system.
The judging whether the installation object corresponding to the patch package meets the installation condition of the patch package comprises:
and judging whether the specified registry key value and/or the version number of the file meet the preset condition or are in the specified range.
Downloading and installing the patch packages in sequence:
analyzing the release time and the release sequence of each patch package;
and determining the installation sequence of the patch packages according to the analysis result, and installing each patch package according to the installation sequence.
The downloading each patch package and installing only the latest patch package in each patch package comprises the following steps:
judging whether the downloaded patch packages use the same patch installation judgment conditions or not;
and when the same patch installation judging conditions are used, selecting the latest patch package for installation according to the release time of the patch package.
Further comprising:
after the patch package is installed, returning installation result information;
and when the installation result information shows that the patch package is unsuccessfully installed, judging whether the patch package is successfully installed.
Further comprising:
and after the installation of the patch package is finished, displaying the information of the patch package in an output interface.
An installation apparatus for a patch package, comprising:
the generating unit is used for generating patch package installation conditions based on the registry and/or the file information of each patch package according to the loopholes and the related patch packages;
a judging unit, configured to judge whether an installation object corresponding to the patch package satisfies the patch package installation condition;
the installation unit is used for downloading and installing the patch package when the installation condition of the patch package is met; wherein the downloading and installing the patch package comprises: and downloading and installing each patch package in sequence, or downloading each patch package and installing only the latest patch package in each patch package, or downloading and installing only the latest patch package in each patch package.
The registry information in each patch package installation condition generated by the generation unit includes: registry keys, registry key values; the file information includes: file version information, file attributes.
The judging unit comprises at least one of the following units:
a first information judgment unit for judging whether a specified registry key, a value of the specified registry key, or a specified file exists in the system;
and the second information judging unit is used for judging whether the specified registry key value and/or the version number of the file meet the preset condition or are in the specified range.
The mounting unit comprises at least one of the following:
the sequence installation unit is used for analyzing the release time and sequence of each patch package, determining the installation sequence of the patch packages according to the analysis result, and installing each patch package according to the installation sequence;
the selected installation unit is used for judging whether the downloaded patch packages use the same patch installation judgment conditions or not, and when the same patch installation judgment conditions are used, the latest patch package is selected to be installed according to the release time of the patch package;
and the direct installation unit is used for downloading and installing only the latest patch package in each patch package.
Further comprising:
the return unit is used for returning installation result information after the patch package is installed;
the judging unit is further configured to judge whether the patch package is successfully installed when the installation result information indicates that the patch package is unsuccessfully installed.
Further comprising:
and the display unit is used for displaying the information of the patch package in an output interface after the installation of the patch package is finished.
According to the technical scheme provided by the embodiment of the application, the patch package installation condition based on the registry and/or the file information of each patch package is generated according to the vulnerability and the related patch packages in the embodiment of the application, whether the installation object corresponding to the patch package meets the patch package installation condition is judged, and when the patch package installation condition is met, the patch package is downloaded and installed. When the patch installation is carried out by applying the embodiment of the application, each patch package can be downloaded and installed in sequence, or each patch package is downloaded and only the latest patch package in each patch package is installed, or only the latest patch package in each patch package is downloaded and installed; by applying the method and the device, when a plurality of bugs are detected simultaneously, the patch packages are installed in sequence, so that the failure of installation caused by the fact that the patch packages with later release time are installed first can be avoided; and by selecting and installing the latest patch package, the bug can not be repaired repeatedly when a plurality of patch packages with the same judgment condition are downloaded, so that system resources are saved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.
FIG. 1 is a flowchart of a first embodiment of a method for installing a patch package according to the present application;
FIG. 2 is a flowchart of a second embodiment of a method for installing a patch package according to the present application;
FIG. 3 is a flowchart of a third embodiment of a method for installing a patch package according to the present application;
FIG. 4A is a block diagram of an embodiment of an installation apparatus for a patch package of the present application;
FIG. 4B is a block diagram of an embodiment of the determining unit shown in FIG. 4A;
fig. 4C is a block diagram of an embodiment of the installation unit of fig. 4A of the present application.
Detailed Description
The following embodiment of the invention provides a method and a device for installing a patch package.
In order to make the technical solutions in the embodiments of the present invention better understood and make the above objects, features and advantages of the embodiments of the present invention more comprehensible, the technical solutions in the embodiments of the present invention are described in further detail below with reference to the accompanying drawings.
Referring to fig. 1, a flowchart of a first embodiment of a method for installing a patch package of the present application is shown:
step 101: and generating patch package installation conditions based on the registry and/or file information of each patch package according to the loopholes and the related patch packages thereof.
The registry information in the patch package installation condition may include: registry keys, registry key values; the file information in the patch package installation condition may include: file version information, file attributes.
Step 102: judging whether an installation object corresponding to the patch package meets the installation condition of the patch package, if so, executing a step 103; otherwise, step 104 is performed.
Specifically, it may be determined whether a specified registry key, a value of the specified registry key, or a specified file exists in the system; it may also be determined whether a specified registry key and/or version number of the file meets a particular condition or is within a specified range.
Taking the registry partition as an example, assuming that patch kb370009 is a vulnerability to Adobe Flash Player remote code execution, the conditional scan logic of the patch includes the following two conditions:
HKEY _ LOCAL _ MACHINE \ SOFTWARE \ Microsoft \ Windows \ Currentversion \ Uninstall \ Adobe Flash Player ActiveX \ Displayversion less than 10.1.102.64; and
HKEY _ LOCAL _ MACHINE \ SOFTWARE \ Microsoft \ Windows \ Currentversion \ Uninstall \ Adobe Flash Player ActiveX \ Displayversion is more than or equal to 10.0.0.0;
according to the two judgment conditions, after the registry version number of the current system is obtained, whether the version number is in the registry range defined by the two judgment conditions can be compared.
It should be noted that, because the patch of Adobe Flash Player1 does not accumulate and update files at a certain fixed location every time it is upgraded, but writes the version number to be updated this time in the registry every time, or releases a new file under the C: \ WINDOWS \ system32\ Macromed \ Flash folder, for example, the last version is Flash10m. This means that it is difficult to scan the vulnerability based on the file name, and therefore the registry is selected to be scanned.
Taking the file version interval as an example, since Adobe upgrades in a certain range, the judgment condition is limited to upgrade users in a certain interval. Assume that patch kb2416400 is used to fix an IE browser bug, for version IE6.7.8. Wherein, microsoft also performs division and upgrade on the IE version, for example, the restriction conditions added for upgrading the IE7 are as follows:
prografiles \ internet explorer \ IEXPLORE. EXE is greater than or equal to 7.0.5730.11; and
prografiles \ internet explorer \ IEXPLORE. EXE is less than 7.1.0.0;
according to the two judgment conditions, the patch package released this time is upgraded only for the users in the IE section.
As another example, the restrictions added by the upgrade of IE8 are as follows:
prografiles \ internet explorer \ iexplore.exe is greater than or equal to 8.0.6001.18702;
programfiles \ internet explorer \ iexplore. exe is less than 8.1.0.0.
Step 103: and downloading and installing the patch package, and ending the current flow.
Installing the patch package includes: downloading and installing each patch package in sequence, or downloading each patch package and installing only the latest patch package in each patch package, or downloading and installing only the latest patch package in each patch package.
When downloading and installing each patch package in sequence, analyzing the release time and sequence of each patch package, determining the installation sequence of the patch packages according to the analysis result, and installing each patch package according to the installation sequence; during specific application, downloading and installation sequence analysis of each patch package can be completed at a server side, then the client side obtains the patch packages according to the determined installation sequence and installs the patch packages, or the client side directly downloads the patch packages from the server, analyzes the release time and the release sequence of each patch package, and then sequentially installs the patch packages according to the analysis result.
Downloading each patch package and only installing the latest patch package in each patch package, judging whether the downloaded patch packages use the same patch installation judgment condition, and selecting the latest patch package to install according to the release time of the patch package when the same patch installation judgment condition is used; in specific application, the client can download all the patch packages from the server, then the client judges the patch installation judgment condition of each downloaded patch package, and selects the patch package with the latest release time from the patch packages with consistent patch installation judgment conditions.
When only the latest patch package in each patch package is downloaded and installed, the latest patch package can be selected when the server finishes downloading all the patch packages and judges that the patch packages using the same judgment condition exist, and then the client downloads the latest patch package for installation.
Further, after the patch package is installed, the system may also return installation result information, for example, a code indicating that installation is successful or failed. Since some patch packages may still return codes that fail to be installed after the actual installation is successful, for example, office type patch packages, the system may further determine whether the patch packages are successfully installed when the system returns failure information for the installation of these patch packages.
In addition, after the installation of the patch package is finished, the system can output detailed information of the installed patch package in the user interface, such as the name of the patch package, the main purpose of the patch package and the like, so that the function of the patch package is shown to a user, and the user experience is improved.
Step 104: and the obtained patch package is not installed, and the current flow is ended.
Referring to fig. 2, a flowchart of a second embodiment of the method for installing a patch package of the present application shows a process of installing the patch package in order:
step 201: and generating patch package installation conditions based on the registry and/or file information of each patch package according to the loopholes and the related patch packages thereof.
The registry information in the patch package installation condition may include: registry key, registry key value. And judging whether the registry which exists in the system contains the acquired registry or not according to the registry key value and the key value size.
The file information in the patch package installation condition may include: file version information, file attributes. Whether the file exists can be judged according to the file attribute, and whether the file version number existing in the system contains the file version number can be determined according to the file version information.
Step 202: judging whether the installation object corresponding to the patch package meets the installation condition of the patch package, if so, executing step 203; otherwise, step 205 is performed.
When one of the registry information and the file information is acquired from the patch package, only the acquired information needs to be determined. For example, for the patch KB2467659, it is assumed that the patch only modifies the registry, so that it is not necessary to determine whether the patch is installed through the file information, but only needs to determine whether the patch is installed in the registry, and the registry information is as follows:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component BasedServicing\Packages\package_[*]_for_KB2467659[*]\installtimelow
step 203: and determining the installation sequence of the patch packages by analyzing the release time and the release sequence of each patch package in the downloaded patch packages.
Each time the patch package is downloaded may contain a plurality of patch packages, the update time of the patch packages may be different, and therefore, when the patch packages are installed, the installation sequence needs to be determined according to the update time between the patch packages and the relationship between the patch packages. For example, for the patch packages KB2416400 and KB2467659, it is assumed that the release dates of the two patch packages are the same, wherein the patch package KB2416400 is used for solving the CSS0day bug problem of the IE browser, but the patch repair will result in the coding error of the mail detection japanese mail (JIS), and the patch package KB2467659 is used for solving the problem, so when installing the patch package, the installation order of the patch package KB2416400 is advanced and the installation order of the patch package KB2467659 is followed by comparing the release dates and the relationship between each other, etc., so as to ensure that the problem of the coding error of the mail detection japanese mail (JIS) is solved while the CSS0day bug problem of the IE browser is solved.
Step 204: and installing the obtained patch packages according to the installation sequence, and ending the current flow.
Step 205: and the obtained patch package is not installed, and the current flow is ended.
When the obtained registry information and file information are included, it is indicated that no corresponding bug exists in the system, or the patch package is installed, so that the patch package does not need to be installed.
Referring to fig. 3, a flowchart of a third embodiment of the method for installing a patch package of the present application shows a process of installing a latest patch package:
step 301: and generating patch package installation conditions based on the registry and/or file information of each patch package according to the loopholes and the related patch packages thereof.
The registry information in the patch package installation condition may include: registry key, registry key value. And judging whether the registry which exists in the system contains the acquired registry or not according to the registry key value and the key value size.
The file information may include: file version number, file identification. Whether the file exists can be judged according to the file identification, and whether the file version number existing in the system contains the acquired file version number can be determined according to the file version number.
Step 302: judging whether the installation object corresponding to the patch package meets the installation condition of the patch package, if so, executing step 303; otherwise, step 306 is performed.
Step 303: judging whether the downloaded patch packages use the same patch installation judgment conditions, if so, executing a step 304; otherwise, step 305 is performed.
The downloaded patch packages may include a plurality of patch packages, and the update time of the patch packages may be different, so that at installation, a patch package with a later update time may include a function of updating a previous patch package, and if the same bug is repaired multiple times through the patch packages, system resources are consumed. Therefore, in the embodiment of the present application, it is determined whether the patch package uses the same patch installation determination condition, so as to determine whether the patch package repairs the same bug, and if there are multiple patch packages repairing the same bug, it is sufficient to select one patch package with the latest release time for repairing.
Step 304: and selecting the latest patch package for installation according to the release time of the patch package, and ending the current flow.
Step 305: and installing all the obtained patch packages, and ending the current flow.
Step 306: and the obtained patch package is not installed, and the current flow is ended.
If the current system does not meet the installation condition of the patch package, the corresponding bug does not exist in the system, or the patch package is already installed, so that the patch package does not need to be installed.
Corresponding to the embodiment of the installation method of the patch package, the application also provides an embodiment of an installation device of the patch package.
Referring to fig. 4A, a block diagram of an embodiment of an installation apparatus for a patch package of the present application is shown:
the installation device of the patch package comprises: a generating unit 410, a judging unit 420 and a mounting unit 430.
The generating unit 410 is configured to generate a patch package installation condition based on a registry and/or file information of each patch package according to the vulnerability and the related patch packages;
a determining unit 420, configured to determine whether an installation object corresponding to the patch package meets the patch package installation condition;
an installation unit 430, configured to download and install the patch package when the patch package installation condition is satisfied; wherein the downloading and installing the patch package comprises: and downloading and installing each patch package in sequence, or downloading each patch package and installing only the latest patch package in each patch package, or downloading and installing only the latest patch package in each patch package.
The registry information in the patch package installation condition may include: registry keys, registry key values; the file information in the patch package installation condition may include: file version information, file attributes.
Further, the installation apparatus of the patch package may further include (not shown in fig. 4A): the return unit is used for returning installation result information after the patch package is installed; the determining unit 420 is further configured to determine whether the patch package is successfully installed when the installation result information indicates that the patch package is unsuccessfully installed.
Further, the installation apparatus of the patch package may further include (not shown in fig. 4A): and the display unit is used for displaying the information of the patch package in an output interface after the installation of the patch package is finished.
Referring to fig. 4B, a block diagram of an embodiment of the determining unit in fig. 4A is shown:
the judging unit 420 may include at least one of the following units (fig. 4B shows both units):
a first information judgment unit 421 for judging whether a specified registry key, a value of the specified registry key, or a specified file exists in the system;
the second information determining unit 422 is configured to determine whether the specified registry key and/or the version number of the file meet a preset condition or are within a specified range.
Referring to fig. 4C, a block diagram of an embodiment of the installation unit in fig. 4A of the present application is shown:
the mounting unit 430 may include at least one of the following units (fig. 4C shows three units each):
a sequence installation unit 431, configured to analyze the release time and sequence of each patch package, determine an installation sequence of the patch packages according to an analysis result, and install each patch package according to the installation sequence;
a selecting and installing unit 432, configured to determine whether each downloaded patch package uses the same patch installation determination condition, and when the same patch installation determination condition is used, select the latest patch package for installation according to the release time of the patch package;
and the direct installation unit is used for downloading and installing only the latest patch package in each patch package.
As can be seen from the description of the above embodiment, in the embodiment of the present application, a patch package installation condition based on the registry and/or the file information of each patch package is generated according to a vulnerability and its related patch packages, whether an installation object corresponding to the patch package meets the patch package installation condition is determined, and when the patch package installation condition is met, the patch package is downloaded and installed. When the patch installation is carried out by applying the embodiment of the application, each patch package can be downloaded and installed in sequence, or each patch package is downloaded and only the latest patch package in each patch package is installed, or only the latest patch package in each patch package is downloaded and installed; by applying the method and the device, when a plurality of bugs are detected simultaneously, the patch packages are installed in sequence, so that the failure of installation caused by the fact that the patch packages with later release time are installed first can be avoided; and by selecting and installing the latest patch package, the bug can not be repaired repeatedly when a plurality of patch packages with the same judgment condition are downloaded, so that system resources are saved.
Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above-described embodiments of the present invention do not limit the scope of the present invention. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (17)
1. A patch package installation method, comprising:
generating patch package installation conditions according to the vulnerabilities and related patch packages thereof, wherein the patch package installation conditions comprise registry and/or file information based on each patch package;
judging whether an object to be provided with a patch package meets the patch package installation condition;
and if the installation condition of the patch package is met, downloading and installing the patch package.
2. The patch package installation method of claim 1, wherein the downloading and installing the patch package comprises:
analyzing the release time and the release sequence of each patch package;
and determining the installation sequence of the patch packages according to the analysis result, and installing each patch package according to the installation sequence.
3. The patch package installation method of claim 1, wherein the downloading and installing the patch package comprises:
downloading each patch package;
judging whether each downloaded patch package uses the same patch installation judgment condition;
the patch packs that use the same patch installation determination conditions are selected from among the patch packs that have the latest release time and are installed.
4. The patch package installation method of claim 1, wherein the downloading and installing the patch package comprises:
only the latest patch package in each patch package is downloaded and installed.
5. The method of any one of claims 1 to 4,
the registry comprises: registry keys, registry key values;
the file information includes: file version information, file attributes.
6. The method of claim 5, wherein the determining whether the object to install the patch package satisfies the patch package installation condition comprises:
and judging whether the specified registry key, the value of the specified registry key or the specified file exists in the object.
7. The method of claim 6, wherein the determining whether the object to install the patch package satisfies the patch package installation condition further comprises:
and judging whether the specified registry key value and/or the version number of the file meet the preset condition or are in the specified range.
8. A patch package installation method, comprising:
judging whether an object to be provided with a patch package meets the patch package installation conditions of the related patch packages, wherein the patch package installation conditions are generated according to the vulnerability and the related patch packages;
if the installation condition of the patch packages is met, analyzing the release time and the release sequence of each patch package;
and determining the installation sequence of the patch packages according to the analysis result, and installing each patch package according to the installation sequence.
9. The method as recited in claim 8, wherein the patch package installation condition includes registry and/or file information based on each patch package.
10. The method of claim 9, wherein,
the registry comprises: registry keys, registry key values;
the file information includes: file version information, file attributes.
11. The method of claim 10, wherein the determining whether the object to install the patch package satisfies the patch package installation condition comprises:
it is determined whether a specified registry key, a value of the specified registry key, or a specified file exists in the system.
12. The method of claim 11, wherein the determining whether the object to install the patch package satisfies the patch package installation condition further comprises:
and judging whether the specified registry key value and/or the version number of the file meet the preset condition or are in the specified range.
13. A patch package installation method, comprising:
judging whether an object to be provided with a patch package meets the patch package installation conditions of the related patch packages, wherein the patch package installation conditions are generated according to the vulnerability and the related patch packages;
downloading each patch package if the patch package installation condition is met;
judging whether each downloaded patch package uses the same patch installation judgment condition;
the patch packs that use the same patch installation determination conditions are selected from among the patch packs that have the latest release time and are installed.
14. The method as recited in claim 13, wherein the patch package installation condition includes registry and/or file information based on each patch package.
15. The method of claim 14, wherein,
the registry comprises: registry keys, registry key values;
the file information includes: file version information, file attributes.
16. The method of claim 15, wherein the determining whether the object to install the patch package satisfies the patch package installation condition comprises:
it is determined whether a specified registry key, a value of the specified registry key, or a specified file exists in the system.
17. The method of claim 16, wherein the determining whether the object to install the patch package satisfies the patch package installation condition further comprises:
and judging whether the specified registry key value and/or the version number of the file meet the preset condition or are in the specified range.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410028711.XA CN103823693A (en) | 2011-02-21 | 2011-02-21 | Service pack installation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410028711.XA CN103823693A (en) | 2011-02-21 | 2011-02-21 | Service pack installation method |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110041779.8A Division CN102087607B (en) | 2011-02-21 | 2011-02-21 | Method and device for installing patch packets |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103823693A true CN103823693A (en) | 2014-05-28 |
Family
ID=50758778
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410028711.XA Pending CN103823693A (en) | 2011-02-21 | 2011-02-21 | Service pack installation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103823693A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107391107A (en) * | 2017-06-12 | 2017-11-24 | 北京明朝万达科技股份有限公司 | The restorative procedure and device of a kind of application program |
| CN109445827A (en) * | 2018-11-16 | 2019-03-08 | 网易（杭州）网络有限公司 | A kind of method and device of game renewal, electronic equipment, storage medium |
| CN110134432A (en) * | 2019-04-19 | 2019-08-16 | 平安科技（深圳）有限公司 | The bug restorative procedure of application, device, computer equipment |
| CN111078264A (en) * | 2018-10-22 | 2020-04-28 | 杭州海康威视系统技术有限公司 | Application upgrading method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6161218A (en) * | 1996-01-16 | 2000-12-12 | Sun Microsystems Inc. | Software patch architecture |
| CN101009599A (en) * | 2007-01-24 | 2007-08-01 | 华为技术有限公司 | Remote load method, system and device of patch package file to the network element node |
| CN101008899A (en) * | 2007-01-26 | 2007-08-01 | 上海华为技术有限公司 | Software version update method and device in communication equipment |
| CN101119231A (en) * | 2007-07-19 | 2008-02-06 | 南京联创网络科技有限公司 | Method to centralized manage and automatic download mend of computer security leak base |
| CN102012990A (en) * | 2010-12-16 | 2011-04-13 | 北京安天电子设备有限公司 | Method and device for repairing bugs of third-party software |
-
2011
- 2011-02-21 CN CN201410028711.XA patent/CN103823693A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6161218A (en) * | 1996-01-16 | 2000-12-12 | Sun Microsystems Inc. | Software patch architecture |
| CN101009599A (en) * | 2007-01-24 | 2007-08-01 | 华为技术有限公司 | Remote load method, system and device of patch package file to the network element node |
| CN101008899A (en) * | 2007-01-26 | 2007-08-01 | 上海华为技术有限公司 | Software version update method and device in communication equipment |
| CN101119231A (en) * | 2007-07-19 | 2008-02-06 | 南京联创网络科技有限公司 | Method to centralized manage and automatic download mend of computer security leak base |
| CN102012990A (en) * | 2010-12-16 | 2011-04-13 | 北京安天电子设备有限公司 | Method and device for repairing bugs of third-party software |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107391107A (en) * | 2017-06-12 | 2017-11-24 | 北京明朝万达科技股份有限公司 | The restorative procedure and device of a kind of application program |
| CN111078264A (en) * | 2018-10-22 | 2020-04-28 | 杭州海康威视系统技术有限公司 | Application upgrading method and device |
| CN109445827A (en) * | 2018-11-16 | 2019-03-08 | 网易（杭州）网络有限公司 | A kind of method and device of game renewal, electronic equipment, storage medium |
| CN110134432A (en) * | 2019-04-19 | 2019-08-16 | 平安科技（深圳）有限公司 | The bug restorative procedure of application, device, computer equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105786538B (en) | software upgrading method and device based on android system | |
| US8495619B2 (en) | Method and system for pre-deployment conflict checking | |
| US8495615B2 (en) | Method, system and computer program for distributing software patches | |
| AU2010364976B2 (en) | Repairing corrupt software | |
| CN106598835B (en) | Application testing method, device and system | |
| KR101299099B1 (en) | Apparatus and method for management of optimized virtualization module in embedded system | |
| US8978015B2 (en) | Self validating applications | |
| CN106020873B (en) | Patch package loading method and device | |
| CN107273151B (en) | Safe Android App functional plug-in method | |
| CN102087607B (en) | Method and device for installing patch packets | |
| CN109800005B (en) | Client hot update method and device | |
| CN103810006B (en) | The installation method and device of service packs | |
| CN109614107B (en) | Integration method and device of software development kit | |
| CN108121650B (en) | Method and device for testing page user interface | |
| CN103823693A (en) | Service pack installation method | |
| WO2019237239A1 (en) | Data test method and apparatus, device/terminal/server and computer readable storage medium | |
| CN113342323A (en) | Method and device for software online development | |
| CN102156649B (en) | Patch installation method and device thereof | |
| CN111061486B (en) | Android application program increment method | |
| CN110837383B (en) | Application installation-free upgrading method and device | |
| US20180129490A1 (en) | Object ordering preservation during lto link stage | |
| CN107301105B (en) | Method and device for checking hot patch or dynamic library | |
| CN113849200B (en) | Installation optimization method and system for android application in android compatible environment | |
| CN115034165A (en) | Chip simulation verification method, system, equipment and storage medium | |
| CN111752735A (en) | SDK (software development kit) abnormity troubleshooting method and device and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140528 |
|
| RJ01 | Rejection of invention patent application after publication |