CN113010197A - Application silence upgrading method, system, terminal equipment and storage medium - Google Patents
Application silence upgrading method, system, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN113010197A CN113010197A CN202010528608.7A CN202010528608A CN113010197A CN 113010197 A CN113010197 A CN 113010197A CN 202010528608 A CN202010528608 A CN 202010528608A CN 113010197 A CN113010197 A CN 113010197A
- Authority
- CN
- China
- Prior art keywords
- upgrade
- target application
- file
- loading
- path
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application provides an application silence upgrading method, a system, terminal equipment and a storage medium, wherein the method comprises the following steps: if any target application is detected to meet the preset silent upgrade condition, carrying out loading authority detection on the target application; if the test is qualified, obtaining the upgrade package catalog and inquiring the starting catalog; matching the upgrade files in the upgrade package directory with the start files in the start directory, and loading the upgrade files which are successfully matched; and loading the starting file which is not successfully matched, and after the loading of the starting file is finished, initializing the target application. When the local silence upgrading is realized, the same mode is adopted for inquiring the upgrading packet path, detecting the loading authority of the target application, inquiring the starting directory, loading the upgrading file and loading the starting file, further, different scripts are not required to be set for starting the application, and the application maintenance cost and the development efficiency are reduced.
Description
Technical Field
The present application belongs to the field of application upgrading, and in particular, to a method, a system, a terminal device, and a storage medium for upgrading application silence.
Background
With the rapid development of computer application technology, applications capable of being installed in an operating system are more and more abundant, and a user can complete a certain task function or certain task functions by using the corresponding applications, for example, the user reads news shown in a web page by using a browser application. In the existing application upgrading process, in order to prevent the application upgrading process from influencing the user operation, the application silent upgrading is more and more favored by people. Applying silent upgrade refers to: under the condition of not disturbing a user (not displaying an upgrading program interface), the upgrading program automatically finishes the upgrading of the application according to the set value of the timed upgrading.
In the prior art, for convenience of starting, a Spring boot application is started based on a single starting file, and then one or more starting files which depend on the Spring boot application are inconvenient to upgrade.
However, when the existing Spring boot application realizes local silence upgrade, the dependent start-up file needs to be externally arranged, and meanwhile, the application needs to be started through a special script, so that the application maintenance cost is high, the development efficiency is low, different start-up scripts need to be compiled for different applications, and when public components among different Spring boot applications need to be upgraded, the start-up files of all applications need to be found to be correspondingly replaced and restarted, so that the application silence upgrade efficiency is reduced.
Disclosure of Invention
The embodiment of the application silent upgrading method and system, the terminal device and the storage medium aim to solve the problems that in the existing Spring boot application silent upgrading process, different scripts are needed to be started for different Spring boot applications, and accordingly application maintenance cost is high and development efficiency is low.
In a first aspect, an embodiment of the present application provides an application silent upgrade method, where the method includes:
if any target application is detected to meet a preset silent upgrade condition, an upgrade package path is obtained, and loading permission detection is carried out on the target application according to the upgrade package path, wherein the upgrade package path is a package path of an upgrade package set for the target application;
if the loading authority of the target application is detected to be qualified, acquiring an upgrade package directory according to the upgrade package path, and inquiring a starting directory corresponding to the target application, wherein the starting directory comprises a starting file which needs to be loaded for starting the target application;
matching the upgrade files in the upgrade package directory with the start files in the start directory, and loading the upgrade files which are successfully matched so as to upgrade the start files matched with the upgrade files;
and loading the starting file which is not successfully matched, and after the loading of the starting file is finished, carrying out initialization operation on the target application so as to finish the silent upgrade operation of the target application.
Compared with the prior art, the embodiment of the application has the advantages that: when the target application realizes the local silent upgrade, the same method is adopted to carry out the query of an upgrade package path, the loading authority detection of the target application, the query of a start directory, the loading of an upgrade file and the loading operation of a start file, so that the application is started without setting different scripts, the application maintenance cost and the development efficiency are reduced, whether the upgrade file corresponding to the upgrade package path needs to be loaded by the target application or not is judged through the design of carrying out the loading authority detection on the target application according to the upgrade package path, the loading of invalid upgrade files is prevented, the application silent upgrade efficiency is improved, the upgrade file in the upgrade package directory is matched with the start file in the start directory to query the start file needing to be upgraded, the successfully matched upgrade file is loaded to achieve the effect of upgrading the corresponding start file, and based on the upgrading of the starting file, the effect of silent upgrading of the target application is achieved.
Further, the obtaining the upgrade package path includes:
acquiring a starting parameter corresponding to a starting program for starting the target application, and if an upgrading path is configured in the starting parameter, setting the upgrading path in the starting parameter as the upgrading packet path;
if the upgrade path is not configured in the starting parameters, acquiring the environment variable of the current operating system of the target application;
if the environment variable is configured with an upgrade path, setting the upgrade path in the environment variable as the upgrade package path;
and if the upgrading path is not configured in the environment variables, inquiring a default path preset in the starting program, and setting the default path as the upgrading package path.
Further, the detecting the loading authority of the target application according to the upgrade package path includes:
acquiring a root directory of the upgrade package path, and acquiring an authority configuration file in the root directory, wherein the authority configuration file comprises an authority updating configuration, and the authority updating configuration is used for detecting whether the target application has a loading authority for the upgrade package path;
if the authorized updating configuration stores configuration information, matching the name of the target application with the name of the configuration information in the authorized updating configuration;
if the name of the target application is matched with the name of the configuration information in the authorized updating configuration, judging that the loading authority detection of the target application is qualified, wherein the target application has loading authority aiming at the upgrade package path;
if the name of the target application is not matched with the name of the configuration information in the authorized updating configuration, determining that the loading authority detection of the target application is unqualified, and the target application does not have the loading authority for the upgrade package path.
Further, the permission configuration file further includes an unauthorized update configuration, where the unauthorized update configuration is used to detect whether the target application has no loading permission for the upgrade package path, and the detecting of the loading permission of the target application according to the upgrade package path further includes:
if the configuration information is not stored in the authorized updating configuration, reading the configuration information of the unauthorized updating configuration;
if configuration information is stored in the unauthorized update configuration, matching the name of the target application with the name of the configuration information in the unauthorized update configuration;
if the name of the target application is matched with the name of the configuration information in the unauthorized update configuration, determining that the loading permission detection of the target application is unqualified, wherein the target application does not have the loading permission for the upgrade package path;
if the name of the target application is not matched with the name of the configuration information in the unauthorized update configuration, judging that the loading permission detection of the target application is qualified, wherein the target application has loading permission for the upgrade package path;
if the configuration information is not stored in the unauthorized update configuration, determining that the loading permission detection of the target application is unqualified, and the target application does not have the loading permission for the upgrade package path.
Further, the matching the upgrade file in the upgrade package directory with the start file in the start directory, and loading the upgrade file successfully matched includes:
respectively acquiring file names of the upgrade file and the start file;
if the names of any one of the upgrading files and the starting file are the same, judging that the upgrading file is matched with the starting file, and loading the upgrading file which is successfully matched.
Further, the obtaining the upgrade package directory according to the upgrade package path includes:
acquiring a target version number in the authority configuration file, and performing directory query according to the upgrade package path;
and if the version number of the inquired catalog is the same as the target version number, setting the inquired catalog as the upgrade package catalog.
Further, after the directory query is performed according to the upgrade package path, the method further includes:
if the version number of the inquired directory is different from the target version number, judging that the upgrade package path is an invalid path;
and if the upgrade packet path is the invalid path, stopping the silent upgrade operation on the target application.
In a second aspect, an embodiment of the present application provides an application silent upgrade system, including:
the loading permission detection module is used for acquiring an upgrade package path and carrying out loading permission detection on the target application according to the upgrade package path if any target application is detected to meet a preset silent upgrade condition, wherein the upgrade package path is a package path of an upgrade package set for the target application;
the directory query module is used for acquiring an upgrade package directory according to the upgrade package path and querying a starting directory corresponding to the target application if the loading permission of the target application is detected to be qualified, wherein the starting directory comprises a starting file which needs to be loaded when the target application is started;
the upgrade file loading module is used for matching the upgrade file in the upgrade package directory with the start file in the start directory, and loading the upgrade file which is successfully matched so as to upgrade the start file matched with the upgrade file;
and the starting file loading module is used for loading the starting file which is not successfully matched and carrying out initialization operation on the target application after the starting file is loaded, so as to complete the silent upgrade operation of the target application.
In a third aspect, an embodiment of the present application provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor executes the computer program to implement the method described above.
In a fourth aspect, the present application provides a storage medium storing a computer program, and when the computer program is executed by a processor, the computer program implements the method as described above.
In a fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a terminal device, causes the terminal device to execute the application silent upgrade method described in any one of the above first aspects.
It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described below.
Fig. 1 is a flowchart of an application silent upgrade method according to a first embodiment of the present application;
fig. 2 is a flowchart of an application silent upgrade method according to a second embodiment of the present application;
fig. 3 is a flowchart of an application silent upgrade method according to a third embodiment of the present application;
fig. 4 is a schematic structural diagram of an application silent upgrade system according to a fourth embodiment of the present application;
fig. 5 is a schematic structural diagram of a terminal device according to a fifth embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
Example one
Please refer to fig. 1, which is a flowchart of an application silent upgrade method according to a first embodiment of the present application, including the steps of:
step S10, if any target application is detected to meet the preset silent upgrade condition, acquiring an upgrade package path, and carrying out loading authority detection on the target application according to the upgrade package path;
the target application is a Spring boot application, the preset silent upgrade condition is used to determine whether the target application needs to perform silent upgrade currently, and the preset silent upgrade condition may be set according to a user requirement, for example, the preset silent upgrade condition may be: judging whether a starting instruction of the target application is received, judging that the target application meets a preset silent upgrade condition when a starting condition of the target application is received, and running the target application.
Optionally, the preset silent upgrade condition may also be: judging whether a timing upgrade setting value in the target application is greater than a set threshold, wherein the timing upgrade setting value can be an application running time value, an application starting time value or an application closing time value.
Furthermore, in this step, the upgrade package path is a package path of an upgrade package set for the target application, the latest upgrade package can be queried according to the upgrade package path, and the upgrade package paths corresponding to different target applications can be the same, so that the update of common components among different target applications is effectively facilitated, the start-up files corresponding to all applications do not need to be found for replacement, and the application silent upgrade efficiency is improved.
In addition, in this step, through the design of performing loading permission detection on the target application according to the upgrade package path, whether the target application needs to load the upgrade file corresponding to the upgrade package path is determined, and if the loading permission detection of the target application is not qualified, it is determined that the target application does not need to load the upgrade file corresponding to the upgrade package path, and the silent upgrade operation on the target application is stopped, that is, the target application does not need to perform silent upgrade, so that the target application is prevented from loading invalid upgrade files, and the accuracy of application silent upgrade is improved.
Step S20, if the loading authority of the target application is detected to be qualified, acquiring an upgrade patch directory according to the upgrade patch path, and inquiring a starting directory corresponding to the target application;
wherein, the upgrade package directory stores at least one upgrade file, if the loading authority of the target application is detected to be qualified, the target application is judged to need to be subjected to silent upgrade, the upgrade package directory is obtained according to the upgrade package path to inquire the upgrade file corresponding to the upgrade package path,
further, the start directory includes a start file that needs to be loaded to start the target application, and the start file may be stored in the start directory by using a file name or a file image.
Step S30, matching the upgrade files in the upgrade package directory with the start files in the start directory, and loading the upgrade files successfully matched with each other to upgrade the start files matched with the upgrade files;
the upgrade file in the upgrade package directory is matched with the start file in the start directory to determine whether the start file in the start directory needs to be upgraded, for example, the upgrade package directory includes an upgrade file a1Upgrade file a2And upgrade file a3The start-up directory includes a start-up file b1And a start-up file b2And a start-up file b3And a start-up file b4Then the upgrade file a is added1Upgrade file a2And upgrade file a3Respectively with the start-up document b1And a start-up file b2And a start-up file b3And a start-up file b4Matching is carried out to judge the starting file b included in the starting directory1And a start-up file b2And a start-up file b3And a start-up file b4Whether an upgrade is needed.
Further, in this step, the upgrade file successfully matched is loaded to achieve the effect of upgrading the boot file matched with the upgrade file, and the target application is subjected to silent upgrade based on the upgrade of the boot file, for example, when the upgrade file a is used1And start-up file b3If the files are matched, the upgrade file a is judged1For starting up files b3The upgraded file is loaded by loading the upgraded file a1The effect of applying silent upgrade to the target is achieved.
In addition, in this step, when loading of any upgrade file is completed, the file name of the loaded upgrade file is stored, and a loaded name set is obtained.
Step S40, loading the starting file which is not successfully matched, and after the loading of the starting file is completed, performing initialization operation on the target application to complete the silent upgrade operation of the target application;
the starting files in the starting directory are screened based on the loaded name set to obtain the starting files which are not matched successfully, starting of the target application is effectively guaranteed through the design of loading the starting files which are not matched successfully in the starting directory, and data updating in the target application can be effectively completed through the design of initializing the target application after the loading of the starting files is completed.
Furthermore, in this step, through the design of loading the starting file which is not successfully matched in the starting directory, whether the target application can be started normally after the upgrade file which is successfully matched and the starting file which is not successfully matched are loaded is judged, and if the target application cannot be started after the completion of the loading of the starting file is detected, an upgrade error prompt is sent, so that the accuracy of silent upgrade of the target application is effectively improved.
In addition, in the step, the starting file which is not successfully matched can be automatically loaded in a user-defined loader mode, and the loading efficiency of the starting file is improved.
In the embodiment, when the local silent upgrade is realized, the same mode is adopted for the query of the upgrade package path, the loading authority detection of the target application, the query of the start directory, the loading of the upgrade file and the loading operation of the start file, so that different scripts are not required to be set for starting the application, the application maintenance cost and the development efficiency are reduced, whether the upgrade file corresponding to the upgrade package path needs to be loaded by the target application or not is judged through the design of the loading authority detection of the target application according to the upgrade package path, the loading of the invalid upgrade file is prevented, the application silent upgrade efficiency is improved, the upgrade file in the upgrade package directory is matched with the start file in the start directory to query the start file needing to be upgraded, and the successfully matched upgrade file is loaded, the effect of upgrading the corresponding starting file is achieved, and the effect of applying silent upgrading to the target is achieved based on the upgrading of the starting file.
Example two
Please refer to fig. 2, which is a flowchart of an application silent upgrade method according to a second embodiment of the present application, where the second embodiment is used to refine step S10 in the first embodiment to refine the steps describing how to obtain the upgrade package path, and the application silent upgrade method includes the steps of:
step S11, if any target application is detected to meet the preset silent upgrade condition, acquiring a starting parameter corresponding to a starting program for starting the target application;
the starting parameters are obtained by acquiring the starting file corresponding to the starting program and inquiring the parameters corresponding to the preset parameter identification in the starting file.
Further, the preset parameter identifier may be set in a manner of a text identifier, a numeric identifier, or a letter identifier, and the same preset parameter identifier may be used for different boot programs.
In this step, when the start parameter corresponding to the start program is acquired, it is determined whether an upgrade path is configured in the start parameter.
Step S21, if the start parameter is configured with an upgrade path, setting the upgrade path in the start parameter as the upgrade package path;
if the starting parameter is configured with the upgrade path, the upgrade path configured in the starting parameter is determined to be the upgrade package path set for the target application.
Step S31, if the upgrade path is not configured in the starting parameters, acquiring the environment variables of the current operating system of the target application;
the environment variables of the current operating system may be set according to the requirements of the user, where the environment variables (environment variables) refer to some parameters used in the operating system to specify the operating environment of the operating system, such as a temporary folder location, a system folder location, or an application upgrade path.
In this step, when the environment variable of the current operating system of the target application is acquired, it is determined whether an upgrade path is configured in the operation variable.
Step S41, if an upgrade path is configured in the environment variable, setting the upgrade path in the environment variable as the upgrade package path;
if the environment variable is configured with the upgrade path, the upgrade path in the environment variable is determined to be the upgrade package path set for the target application.
Step S51, if the upgrade path is not configured in the environment variables, inquiring a default path preset in the starting program, and setting the default path as the upgrade package path;
step S61, load authority detection is carried out on the target application according to the upgrade package path;
specifically, in this step, the performing, according to the upgrade package path, load permission detection on the target application includes:
step S610, acquiring a root directory of the upgrade package path, and acquiring an authority configuration file in the root directory;
the permission configuration file includes a permission update configuration, where the permission update configuration is used to detect whether the target application has a loading permission for the upgrade package path, and the permission update configuration in this embodiment may be an allow-projects configuration, an enable-projects configuration, a permit-projects configuration, or a permit-projects configuration.
Step S611, if the configuration information is stored in the authorized update configuration, matching the name of the target application with the name of the configuration information in the authorized update configuration;
if configuration information is stored in the authorized updating configuration, the configuration information stored in the authorized updating configuration is: the application name of the application which is authorized to load the upgrade file corresponding to the upgrade package path;
therefore, in this step, the name of the target application is matched with the name of the configuration information in the authorized update configuration, so as to determine whether the target application has a loading right for the upgrade file corresponding to the upgrade package path.
For example, when the right update configuration stores the configuration information c1And configuration information c2And configuration information c3The name of the target application is respectively associated with the configuration information c1And configuration information c2And configuration information c3Are matched.
Step S612, if the name of the target application is matched with the name of the configuration information in the authorized updating configuration, judging that the loading authority detection of the target application is qualified, wherein the target application has loading authority for the upgrade package path;
wherein, if the name of the target application and any configuration information c1And configuration information c2And configuration information c3If the names in the upgrade package path are matched, judging that the loading authority detection of the target application is qualified, wherein the target application has loading authority aiming at the upgrade file corresponding to the upgrade package path.
Step S613, if the name of the target application does not match the name of the configuration information in the authorized update configuration, determining that the loading permission detection of the target application is not qualified, and the target application does not have the loading permission for the upgrade package path.
Further, in this embodiment, the permission configuration file further includes an unauthorized update configuration, where the unauthorized update configuration is used to detect whether the target application has no loading permission for the upgrade package path, and the detecting the loading permission of the target application according to the upgrade package path further includes:
step S614, if the configuration information is not stored in the authorized updating configuration, reading the configuration information of the unauthorized updating configuration;
step S615, if configuration information is stored in the unauthorized update configuration, matching the name of the target application with the name of the configuration information in the unauthorized update configuration;
if configuration information is stored in the unauthorized update configuration, the configuration information stored in the unauthorized update configuration is: the application name of the application which is not authorized to load the upgrade file corresponding to the upgrade package path;
therefore, in this step, the name of the target application is matched with the name of the configuration information in the unauthorized update configuration, so as to determine whether the upgrade file corresponding to the upgrade package path by the target application does not have the loading authority.
Step S616, if the name of the target application matches the name of the configuration information in the unauthorized update configuration, determining that the loading permission detection of the target application is not qualified, and the target application does not have a loading permission for the upgrade package path;
step S617, if the name of the target application is not matched with the name of the configuration information in the unauthorized configuration, determining that the loading permission of the target application is detected to be qualified, where the target application has a loading permission for the upgrade package path;
step S618, if configuration information is not stored in the unauthorized update configuration, determining that the loading permission detection of the target application is not qualified, where the target application does not have a loading permission for the upgrade package path;
and judging that no application has loading authority to the upgrade file corresponding to the upgrade package path at present if the configuration information is not stored in the authorized update configuration and the unauthorized update configuration.
In addition, in this embodiment, if configuration information is set in both the authorized update configuration and the unauthorized update configuration, the configuration information in the authorized update configuration is set as valid information, and the configuration information in the unauthorized update configuration is set as invalid information, that is, the name of the target application is matched with the name of the configuration information in the authorized update configuration, so as to determine whether the target application has a loading right for the upgrade package path.
It should be noted that, in this step, by setting the design of the authorized update configuration and the unauthorized update configuration, the security problem caused by the excessively large application upgrade range is effectively prevented, and the security of the application silent upgrade is improved, for example, when the upgrade file corresponding to the upgrade package path needs to upgrade a large number of applications in the current operating system, the detection efficiency of the loading authority detection of the target application can be improved by performing information setting only on the configuration information in the unauthorized update configuration, and when the upgrade file corresponding to the upgrade package path needs to upgrade a small number of applications in the current operating system, the detection efficiency of the loading authority detection of the target application can be improved by performing information setting only on the configuration information in the authorized update configuration.
Step S71, if the loading authority of the target application is detected to be qualified, acquiring an upgrade patch directory according to the upgrade patch path, and inquiring a starting directory corresponding to the target application;
please refer to the explanation of step S20 in the first embodiment, and details of the explanation in this step are not repeated.
Step S81, matching the upgrade files in the upgrade package directory with the start files in the start directory, and loading the upgrade files successfully matched with each other to upgrade the start files matched with the upgrade files;
please refer to the explanation of step S30 in the first embodiment, and details of the explanation in this step are not repeated.
Step S91, loading the starting file which is not successfully matched, and after the loading of the starting file is completed, performing initialization operation on the target application to complete the silent upgrade operation of the target application;
please refer to the explanation of step S40 in the first embodiment, and details of the explanation in this step are not repeated.
In the embodiment, by acquiring the starting parameters corresponding to the starting program, the environment variables of the current operating system and the design of the default path in the starting program, the query of the upgrade package path can be effectively carried out, the accuracy of the detection of the loading authority of the target application is improved, by detecting the configuration information of the authority configuration file with authority updating configuration and without authority updating configuration, whether the upgrade file corresponding to the upgrade package path has the loading authority of the target application can be effectively judged, so as to judge whether the loading authority detection of the target application is qualified or not, further improve the accuracy of the detection of the loading authority of the target application, and by designing the loading authority detection of the target application according to the upgrade package path, whether the target application needs to load the upgrade file corresponding to the upgrade package path or not is judged, so as to prevent the loading of invalid upgrade files, the application silent upgrade efficiency is improved, the upgrade files in the upgrade package directory are matched with the start files in the start directory to inquire the start files to be upgraded, the successfully matched upgrade files are loaded to achieve the effect of upgrading the corresponding start files, and the effect of silent upgrade on the target application is achieved based on the upgrade of the start files.
EXAMPLE III
Please refer to fig. 3, which is a flowchart of an application silent upgrade method according to a third embodiment of the present application, where the second embodiment is used to refine step S20 in the first embodiment to refine the step of describing how to obtain an upgrade package directory according to the upgrade package path, and the application silent upgrade method includes the steps of:
step S12, if any target application is detected to meet the preset silent upgrade condition, acquiring an upgrade package path, and carrying out loading authority detection on the target application according to the upgrade package path;
please refer to the explanation of step S10 in the first embodiment, and details of the explanation in this step are not repeated.
Step S22, if the loading authority of the target application is detected to be qualified, acquiring a root directory of the upgrade package path, and acquiring an authority configuration file in the root directory;
please refer to the explanation of step S610 in the second embodiment, and details are not repeated for the explanation in this step.
Step S32, obtaining the target version number in the authority configuration file, and inquiring the directory according to the upgrade package path;
the authority configuration file is stored with version number information, the target version number is obtained by obtaining the version number in the version number information, and the target version number is used for inquiring the upgrade package directory.
Step S42, if the version number of the inquired catalog is the same as the target version number, setting the inquired catalog as the upgrade package catalog, and inquiring the starting catalog corresponding to the target application;
the starting directory comprises a starting file which needs to be loaded when the target application is started.
In this embodiment, if the queried directory version number is different from the target version number, the upgrade package path is determined to be an invalid path;
and if the upgrade package path is the invalid path, stopping the silent upgrade operation on the target application, wherein if the upgrade package path is the invalid path, judging that the target application does not need to perform silent upgrade.
Step S52, respectively obtaining the upgrade files in the upgrade patch directory and the file names of the start files in the start directory;
in the process of acquiring the file names of the upgrade file and the start-up file, the version number in the acquired file name is deleted, so that matching errors between the upgrade file and the start-up file caused by difference factors of the version number in subsequent steps are prevented.
Step S62, if the names of any upgrade file and the start file are the same, judging that the upgrade file is matched with the start file;
step S72, loading the upgrade files successfully matched to upgrade the start files matched with the upgrade files;
please refer to the explanation of step S30 in the first embodiment, and details of the explanation in this step are not repeated.
Step S82, loading the starting file which is not successfully matched, and after the loading of the starting file is completed, performing initialization operation on the target application to complete the silent upgrade operation of the target application;
please refer to the explanation of step S40 in the first embodiment, and details of the explanation in this step are not repeated.
In the embodiment, the accuracy of the directory query of the upgrade package is improved by acquiring the target version number in the permission configuration file to judge whether the directory queried according to the upgrade package path is the upgrade package directory, the matching between the upgrade file and the start file is judged by respectively acquiring the file names of the upgrade file and the start file, the upgrade file successfully matched is loaded to achieve the effect of upgrading the corresponding start file, the silent upgrade effect of the target application is achieved based on the upgrade of the start file, and the loading permission detection design of the target application according to the upgrade package path is used for judging whether the target application needs to load the upgrade file corresponding to the upgrade package path, so that the loading of invalid upgrade files is prevented, and the silent upgrade efficiency of the application is improved.
Example four
Corresponding to the application silent upgrade method described in the above embodiments, fig. 4 shows a schematic structural diagram of an application silent upgrade system 100 provided in the fourth embodiment of the present application, and for convenience of explanation, only the relevant parts related to the embodiments of the present application are shown.
Referring to fig. 4, the system includes: a loading authority detection module 10, a directory query module 11, an upgrade file loading module 12 and a start file loading module 13, wherein:
the loading permission detection module 10 is configured to, if it is detected that any target application meets a preset silent upgrade condition, acquire an upgrade package path, and perform loading permission detection on the target application according to the upgrade package path, where the upgrade package path is a package path of an upgrade package set for the target application.
Wherein, the loading authority detecting module 10 is further configured to: acquiring a starting parameter corresponding to a starting program for starting the target application, and if an upgrading path is configured in the starting parameter, setting the upgrading path in the starting parameter as the upgrading packet path;
if the upgrade path is not configured in the starting parameters, acquiring the environment variable of the current operating system of the target application;
if the environment variable is configured with an upgrade path, setting the upgrade path in the environment variable as the upgrade package path;
and if the upgrading path is not configured in the environment variables, inquiring a default path preset in the starting program, and setting the default path as the upgrading package path.
Optionally, the loading authority detecting module 10 is further configured to: acquiring a root directory of the upgrade package path, and acquiring an authority configuration file in the root directory, wherein the authority configuration file comprises an authority updating configuration, and the authority updating configuration is used for detecting whether the target application has a loading authority for the upgrade package path;
if the authorized updating configuration stores configuration information, matching the name of the target application with the name of the configuration information in the authorized updating configuration;
if the name of the target application is matched with the name of the configuration information in the authorized updating configuration, judging that the loading authority detection of the target application is qualified, wherein the target application has loading authority aiming at the upgrade package path;
if the name of the target application is not matched with the name of the configuration information in the authorized updating configuration, determining that the loading authority detection of the target application is unqualified, and the target application does not have the loading authority for the upgrade package path.
Further, the permission configuration file further includes an unauthorized update configuration, the unauthorized update configuration is configured to detect whether the target application does not have a loading permission for the upgrade package path, and the loading permission detection module 10 is further configured to:
if the configuration information is not stored in the authorized updating configuration, reading the configuration information of the unauthorized updating configuration;
if configuration information is stored in the unauthorized update configuration, matching the name of the target application with the name of the configuration information in the unauthorized update configuration;
if the name of the target application is matched with the name of the configuration information in the unauthorized update configuration, determining that the loading permission detection of the target application is unqualified, wherein the target application does not have the loading permission for the upgrade package path;
if the name of the target application is not matched with the name of the configuration information in the unauthorized update configuration, judging that the loading permission detection of the target application is qualified, wherein the target application has loading permission for the upgrade package path;
if the configuration information is not stored in the unauthorized update configuration, determining that the loading permission detection of the target application is unqualified, and the target application does not have the loading permission for the upgrade package path.
And the directory query module 11 is configured to, if the loading permission detection of the target application is qualified, obtain an upgrade package directory according to the upgrade package path, and query a start directory corresponding to the target application, where the start directory includes a start file that needs to be loaded to start the target application.
Wherein, the catalog inquiry module 11 is further configured to: acquiring a target version number in the authority configuration file, and performing directory query according to the upgrade package path;
and if the version number of the inquired catalog is the same as the target version number, setting the inquired catalog as the upgrade package catalog.
Preferably, the catalog inquiry module 11 is further configured to: if the version number of the inquired directory is different from the target version number, judging that the upgrade package path is an invalid path;
and if the upgrade packet path is the invalid path, stopping the silent upgrade operation on the target application.
And the upgrade file loading module 12 is configured to match the upgrade file in the upgrade package directory with the start file in the start directory, and load the upgrade file that is successfully matched, so as to upgrade the start file that is matched with the upgrade file.
Wherein, the upgrade file loading module 12 is further configured to: respectively acquiring file names of the upgrade file and the start file;
if the names of any one of the upgrading files and the starting file are the same, judging that the upgrading file is matched with the starting file, and loading the upgrading file which is successfully matched.
And the starting file loading module 13 is configured to load the starting file which is not successfully matched, and perform initialization operation on the target application after the loading of the starting file is completed, so as to complete the silent upgrade operation of the target application.
In the embodiment, when the local silent upgrade is realized, the same mode is adopted for the query of the upgrade package path, the loading authority detection of the target application, the query of the start directory, the loading of the upgrade file and the loading operation of the start file, so that different scripts are not required to be set for starting the application, the application maintenance cost and the development efficiency are reduced, whether the upgrade file corresponding to the upgrade package path needs to be loaded by the target application or not is judged through the design of the loading authority detection of the target application according to the upgrade package path, the loading of the invalid upgrade file is prevented, the application silent upgrade efficiency is improved, the upgrade file in the upgrade package directory is matched with the start file in the start directory to query the start file needing to be upgraded, and the successfully matched upgrade file is loaded, the effect of upgrading the corresponding starting file is achieved, and the effect of applying silent upgrading to the target is achieved based on the upgrading of the starting file.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/modules, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and reference may be made to the part of the embodiment of the method specifically, and details are not described here.
Fig. 5 is a schematic structural diagram of a terminal device 2 according to a fifth embodiment of the present application. As shown in fig. 5, the terminal device 2 of this embodiment includes: at least one processor 20 (only one processor is shown in fig. 5), a memory 21, and a computer program 22 stored in the memory 21 and executable on the at least one processor 20, the steps of any of the various method embodiments described above being implemented when the computer program 22 is executed by the processor 20.
The terminal device 2 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 20, a memory 21. Those skilled in the art will appreciate that fig. 5 is only an example of the terminal device 2, and does not constitute a limitation to the terminal device 2, and may include more or less components than those shown, or combine some components, or different components, such as an input-output device, a network access device, and the like.
The Processor 20 may be a Central Processing Unit (CPU), and the Processor 20 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 21 may in some embodiments be an internal storage unit of the terminal device 2, such as a hard disk or a memory of the terminal device 2. The memory 21 may also be an external storage device of the terminal device 2 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 2. Further, the memory 21 may also include both an internal storage unit and an external storage device of the terminal device 2. The memory 21 is used for storing an operating system, an application process, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer program. The memory 21 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
An embodiment of the present application further provides a network device, where the network device includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, the processor implementing the steps of any of the various method embodiments described above when executing the computer program.
The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above-mentioned method embodiments.
The embodiments of the present application provide a computer program product, which when running on a mobile terminal, enables the mobile terminal to implement the steps in the above method embodiments when executed.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other ways. For example, the above-described apparatus/network device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A method for applying silent upgrade, the method comprising:
if any target application is detected to meet a preset silent upgrade condition, an upgrade package path is obtained, and loading permission detection is carried out on the target application according to the upgrade package path, wherein the upgrade package path is a package path of an upgrade package set for the target application;
if the loading authority of the target application is detected to be qualified, acquiring an upgrade package directory according to the upgrade package path, and inquiring a starting directory corresponding to the target application, wherein the starting directory comprises a starting file which needs to be loaded for starting the target application;
matching the upgrade files in the upgrade package directory with the start files in the start directory, and loading the upgrade files which are successfully matched so as to upgrade the start files matched with the upgrade files;
and loading the starting file which is not successfully matched, and after the loading of the starting file is finished, carrying out initialization operation on the target application so as to finish the silent upgrade operation of the target application.
2. The application silent upgrade method of claim 1, wherein said obtaining an upgrade packet path comprises:
acquiring a starting parameter corresponding to a starting program for starting the target application, and if an upgrading path is configured in the starting parameter, setting the upgrading path in the starting parameter as the upgrading packet path;
if the upgrade path is not configured in the starting parameters, acquiring the environment variable of the current operating system of the target application;
if the environment variable is configured with an upgrade path, setting the upgrade path in the environment variable as the upgrade package path;
and if the upgrading path is not configured in the environment variables, inquiring a default path preset in the starting program, and setting the default path as the upgrading package path.
3. The application silent upgrade method of claim 1, wherein the detecting of the loading permission of the target application according to the upgrade package path comprises:
acquiring a root directory of the upgrade package path, and acquiring an authority configuration file in the root directory, wherein the authority configuration file comprises an authority updating configuration, and the authority updating configuration is used for detecting whether the target application has a loading authority for the upgrade package path;
if the authorized updating configuration stores configuration information, matching the name of the target application with the name of the configuration information in the authorized updating configuration;
if the name of the target application is matched with the name of the configuration information in the authorized updating configuration, judging that the loading authority detection of the target application is qualified, wherein the target application has loading authority aiming at the upgrade package path;
if the name of the target application is not matched with the name of the configuration information in the authorized updating configuration, determining that the loading authority detection of the target application is unqualified, and the target application does not have the loading authority for the upgrade package path.
4. The application silent upgrade method of claim 3, wherein the permission configuration file further comprises an unauthorized update configuration, the unauthorized update configuration being used to detect whether the target application does not have a loading permission for the upgrade package path, the loading permission detection of the target application according to the upgrade package path further comprising:
if the configuration information is not stored in the authorized updating configuration, reading the configuration information of the unauthorized updating configuration;
if configuration information is stored in the unauthorized update configuration, matching the name of the target application with the name of the configuration information in the unauthorized update configuration;
if the name of the target application is matched with the name of the configuration information in the unauthorized update configuration, determining that the loading permission detection of the target application is unqualified, wherein the target application does not have the loading permission for the upgrade package path;
if the name of the target application is not matched with the name of the configuration information in the unauthorized update configuration, judging that the loading permission detection of the target application is qualified, wherein the target application has loading permission for the upgrade package path;
if the configuration information is not stored in the unauthorized update configuration, determining that the loading permission detection of the target application is unqualified, and the target application does not have the loading permission for the upgrade package path.
5. The application silent upgrade method of claim 1, wherein the matching of the upgrade file in the upgrade package directory with the boot file in the boot directory and the loading of the upgrade file successfully matched comprises:
respectively acquiring file names of the upgrade file and the start file;
if the names of any one of the upgrading files and the starting file are the same, judging that the upgrading file is matched with the starting file, and loading the upgrading file which is successfully matched.
6. The application silent upgrade method of claim 3, wherein the obtaining an upgrade package directory according to the upgrade package path comprises:
acquiring a target version number in the authority configuration file, and performing directory query according to the upgrade package path;
and if the version number of the inquired catalog is the same as the target version number, setting the inquired catalog as the upgrade package catalog.
7. The application silent upgrade method of claim 6, wherein after the directory query according to the upgrade package path, the method further comprises:
if the version number of the inquired directory is different from the target version number, judging that the upgrade package path is an invalid path;
and if the upgrade packet path is the invalid path, stopping the silent upgrade operation on the target application.
8. An application-silent upgrade system, comprising:
the loading permission detection module is used for acquiring an upgrade package path and carrying out loading permission detection on the target application according to the upgrade package path if any target application is detected to meet a preset silent upgrade condition, wherein the upgrade package path is a package path of an upgrade package set for the target application;
the directory query module is used for acquiring an upgrade package directory according to the upgrade package path and querying a starting directory corresponding to the target application if the loading permission of the target application is detected to be qualified, wherein the starting directory comprises a starting file which needs to be loaded when the target application is started;
the upgrade file loading module is used for matching the upgrade file in the upgrade package directory with the start file in the start directory, and loading the upgrade file which is successfully matched so as to upgrade the start file matched with the upgrade file;
and the starting file loading module is used for loading the starting file which is not successfully matched and carrying out initialization operation on the target application after the starting file is loaded, so as to complete the silent upgrade operation of the target application.
9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the computer program.
10. A storage medium storing a computer program, characterized in that the computer program, when executed by a processor, implements the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010528608.7A CN113010197B (en) | 2020-06-11 | 2020-06-11 | Application silence upgrading method, system, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010528608.7A CN113010197B (en) | 2020-06-11 | 2020-06-11 | Application silence upgrading method, system, terminal equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113010197A true CN113010197A (en) | 2021-06-22 |
| CN113010197B CN113010197B (en) | 2023-04-11 |
Family
ID=76383032
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010528608.7A Active CN113010197B (en) | 2020-06-11 | 2020-06-11 | Application silence upgrading method, system, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113010197B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115904462A (en) * | 2023-02-10 | 2023-04-04 | 中航金网(北京)电子商务有限公司 | Application program upgrading method and device, electronic equipment and readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107436782A (en) * | 2017-07-03 | 2017-12-05 | 北京小米移动软件有限公司 | Application program silence installation method and device |
| CN108491216A (en) * | 2018-03-05 | 2018-09-04 | 北京指掌易科技有限公司 | A kind of method of android system unaware application installation upgrading |
| CN110362329A (en) * | 2019-07-18 | 2019-10-22 | 上海擎感智能科技有限公司 | A kind of version updating inspection method and system |
| CN110457052A (en) * | 2018-05-08 | 2019-11-15 | 优酷网络技术（北京）有限公司 | Application upgrade method and device |
| CN110750280A (en) * | 2019-09-30 | 2020-02-04 | 深圳市金百锐通信科技有限公司 | Application upgrading method and system based on Android platform and storage medium |
-
2020
- 2020-06-11 CN CN202010528608.7A patent/CN113010197B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107436782A (en) * | 2017-07-03 | 2017-12-05 | 北京小米移动软件有限公司 | Application program silence installation method and device |
| CN108491216A (en) * | 2018-03-05 | 2018-09-04 | 北京指掌易科技有限公司 | A kind of method of android system unaware application installation upgrading |
| CN110457052A (en) * | 2018-05-08 | 2019-11-15 | 优酷网络技术（北京）有限公司 | Application upgrade method and device |
| CN110362329A (en) * | 2019-07-18 | 2019-10-22 | 上海擎感智能科技有限公司 | A kind of version updating inspection method and system |
| CN110750280A (en) * | 2019-09-30 | 2020-02-04 | 深圳市金百锐通信科技有限公司 | Application upgrading method and system based on Android platform and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 李晓娟: "安卓系统的静默安装行为检测与安全加固研究" * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115904462A (en) * | 2023-02-10 | 2023-04-04 | 中航金网(北京)电子商务有限公司 | Application program upgrading method and device, electronic equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113010197B (en) | 2023-04-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108847950B (en) | Electronic device, cloud system software automatic deployment method and storage medium | |
| US9081967B2 (en) | System and method for protecting computers from software vulnerabilities | |
| CN104008340B (en) | Virus scanning and killing method and device | |
| CN109814524B (en) | Vehicle diagnosis method, device and system | |
| CN101556634B (en) | Method and system for managing and controlling using authority of external apparatus | |
| US20170351507A1 (en) | Silent upgrade of software with dependencies | |
| CN110162429B (en) | System repair method, server and storage medium | |
| US10757087B2 (en) | Secure client authentication based on conditional provisioning of code signature | |
| EP3163489A1 (en) | Token-based control of software installation and operation | |
| CN106293849B (en) | application updating method and terminal | |
| CN112579202B (en) | Method, device, equipment and storage medium for editing server program of Windows system | |
| CN106843947B (en) | Method and device for processing code defects | |
| CN115185550A (en) | Service deployment method, device, computer equipment and storage medium | |
| CN112671609A (en) | Asset census and safety detection method and device and terminal equipment | |
| CN110515671B (en) | Initialization method, initialization device, terminal device and readable storage medium | |
| CN113010197B (en) | Application silence upgrading method, system, terminal equipment and storage medium | |
| CN111062040A (en) | Method for determining unknown vulnerability, server and computer readable storage medium | |
| CN111177703A (en) | Method and device for determining data integrity of operating system | |
| CN113238790B (en) | Firmware program updating method and system based on SD card and EEPROM | |
| CN114185571A (en) | Firmware upgrading method and device of CPLD, terminal and readable storage medium | |
| CN114139161A (en) | Method, device, electronic equipment and medium for batch vulnerability detection | |
| CN113835729A (en) | Upgrading method and device, terminal equipment and computer readable storage medium | |
| CN103455750A (en) | High-security verification method and high-security verification system for embedded devices | |
| US11507367B2 (en) | Firmware update method and firmware update system thereof | |
| CN112100479A (en) | Application access method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |