CN111008030A - Software online updating system and method based on xml file list and related device - Google Patents
Software online updating system and method based on xml file list and related device Download PDFInfo
- Publication number
- CN111008030A CN111008030A CN201911260046.6A CN201911260046A CN111008030A CN 111008030 A CN111008030 A CN 111008030A CN 201911260046 A CN201911260046 A CN 201911260046A CN 111008030 A CN111008030 A CN 111008030A
- Authority
- CN
- China
- Prior art keywords
- updating
- directory
- software
- file
- program
- 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
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a software online updating system, method and related device based on an xml file list, which do not need a client to download all installation packages for reinstallation, only need to download a small amount of update files for replacing application online, are quick to upgrade, do not need a special updating server, have low technical requirements on deployment personnel, are convenient to deploy, and solve the technical problems that when the existing Inno setup offline installation package is used or the Microsoft Windows Installer is used for deployment, the whole application program needs to be reinstalled, and the Microsoft CLICkone deployment scheme needs a special server, has high technical requirements on deployment personnel and is difficult to deploy.
Description
Technical Field
The application relates to the technical field of software updating, in particular to a software online updating system and method based on an xml file list.
Background
At present, when an ino setup offline installation package or Microsoft Windows installers are used for deploying an application program based on a client/server architecture, the whole application program needs to be reinstalled, and a Microsoft clickonce deployment scheme needs a special server, so that the technical requirement on deployment personnel is high, and the deployment is difficult.
Disclosure of Invention
The application provides an xml file list-based software online updating system, which is used for solving the technical problems that when an ino setup offline installation package is used or Microsoft Windows installers are used for deployment, the whole application program needs to be reinstalled, and a Microsoft clickone deployment scheme needs a special server, so that the technical requirements on deployment personnel are high, and the deployment is difficult.
In view of the above, a first aspect of the present application provides an online software updating system based on an xml file manifest, including: the method comprises the following steps that a server side, a client side updating program and a client side main program are adopted;
the server side is used for acquiring an xml manifest file and an update file, and issuing the xml manifest file and the update file to a preset position according to a preset directory structure;
the client updating program is used for downloading and verifying the updated files one by one according to a target version transmitted by the client main program through parameters and downloading all listed versions and all files matched with the listed versions one by one, and the versions are updated in parallel during downloading;
the client-side main program is used for checking the cached updating program updating file when the main program is started, updating the updating program, supporting the functions of version comparison and updating reminding, pulling all updating lists behind the version of the client-side main program through the server side, providing a selectable updating target for a user through the client-side main program, and prompting major updating to the client through the client-side if a forced updating instruction is detected and the client-side main program is in a forced range.
Optionally, the preset directory structure includes: the server-side root directory, the software identification directory, the area identification directory, the software category identification directory, the order number directory, the software main version number and the software version release batch directory.
Optionally, the software identifier directory is stored in a lower directory of the root directory, the area identifier directory is stored in a lower directory of the software identifier directory, the software type identifier directory is stored in a lower directory of the software identifier directory, the order number directory is stored in a lower directory of the software type identifier directory, and the software major version number and the software version release directory are stored in a lower directory of the order number directory in batches.
Optionally, the client main program supports the following functions:
pulling the enabled update file;
displaying the date of the update release;
displaying the version updated this time for version association to obtain version upgrading history, and downloading applications one by one according to the upgrading history;
displaying the current version and the release batch;
displaying update levels, wherein the update levels comprise common upgrade, important upgrade and forced upgrade;
configuring a forced upgrading range, and carrying out forced upgrading on the version in the specified range;
configuring a special reminding mechanism;
configuring a custom operation command, and updating a program to execute different operations according to different operation commands;
supporting version update description;
displaying a list of files to be downloaded;
displaying the relative path of the file at the server end;
displaying a path stored after the file is downloaded;
the name is saved after the file is downloaded, and the saved name is consistent with the saved name of the server side;
displaying the version of the update file;
displaying the file size;
performing MD5 check on the file;
indicating whether the file needs to be decompressed;
indicating a file decompression path needing to be decompressed;
indicating whether a reboot is required to apply the update;
displaying a relative path where the restart program is located;
the name of the restarted program is displayed.
Optionally, the update program upgrade file includes an update package of the.zip and an in-package file of the update package of the.zip.
The second aspect of the present application provides an online software updating method based on an xml file list, including:
when the main program is started, detecting a cached updating program upgrading file;
generating an update address, and pulling a current version update list of the server;
detecting whether forced updating exists or not, wherein the version is in a forced range, if so, inquiring a user whether updating is performed, and if not, listing an updating list for the user to select;
if the user does not update, the program is ended, and if the user updates, the parameters are transmitted to start the updating program;
if the version selected by the user from the updating list has the need-to-know prompt, popping up the need-to-know prompt, if the user confirms the need-to-know prompt, transmitting the parameters to start the updating program, otherwise, listing the updating list for the user to select;
after an updating program is started, loading an updating list, downloading all listed versions and all files matched with the listed versions one by one, and simultaneously updating the versions in parallel;
the server side obtains an xml manifest file and an update file, and issues the xml manifest file and the update file to a preset position according to a preset directory structure.
Optionally, the preset directory structure includes: the server-side root directory, the software identification directory, the area identification directory, the software category identification directory, the order number directory, the software main version number and the software version release batch directory.
Optionally, the software identifier directory is stored in a lower directory of the root directory, the area identifier directory is stored in a lower directory of the software identifier directory, the software type identifier directory is stored in a lower directory of the software identifier directory, the order number directory is stored in a lower directory of the software type identifier directory, and the software major version number and the software version release directory are stored in a lower directory of the order number directory in batches.
The third aspect of the application provides a device for updating software on line based on an xml file list, wherein the device is in communication connection with a server side and comprises a main program module and a program updating module;
the server side obtains an xml (extensible markup language) manifest file and an update file, and issues the xml manifest file and the update file to a preset position according to a preset directory structure;
the main program module is used for:
when the main program is started, detecting a cached updating program upgrading file;
generating an update address, and pulling a current version update list of the server;
detecting whether forced updating exists or not, wherein the version is in a forced range, if so, inquiring a user whether updating is performed, and if not, listing an updating list for the user to select;
if the user does not update, the program is ended, and if the user updates, the transmission parameter triggers the program updating module to start the updating program;
if the version selected by the user from the updating list has the need-to-know prompt, popping up the need-to-know prompt, if the user confirms the need-to-know prompt, transmitting the parameter to trigger the program updating module to start the updating program, and if not, listing the updating list for the user to select;
the program update module is to:
after the updating program is started, loading an updating list, downloading all listed versions and all files matched with the listed versions one by one, and simultaneously applying version updating in parallel.
The fourth aspect of the present application provides a client for online updating of software based on an xml file manifest, where the client includes the apparatus for online updating of software based on an xml file manifest according to the third aspect.
According to the technical scheme, the embodiment of the application has the following advantages:
in this application, a software online update system based on an xml file list is provided, including: the method comprises the following steps that a server side, a client side updating program and a client side main program are adopted; the server side is used for acquiring the xml manifest file and the update file and issuing the xml manifest file and the update file to a preset position according to a preset directory structure; the client updating program is used for downloading all listed versions and all files matched with the listed versions one by one according to a target version transmitted by a client main program through parameters, and simultaneously updating the versions in parallel; the client-side main program is used for checking the cached updating program updating file when the main program is started, updating the updating program, supporting the version comparison and updating reminding functions, pulling all updating lists behind the version of the client-side main program through the server side, providing a selectable updating target for a user through the client-side main program, and prompting major updating to the client through the client-side if a forced updating instruction is detected and the client-side main program is in a forced range. The software online updating system provided by the application does not need a client to download all installation packages for reinstallation, only needs to download a small amount of update files for replacing application online, is quick to upgrade, does not need a special updating server, has low technical requirements on deployment personnel, is convenient to deploy, and solves the technical problems that when the existing Inno setup offline installation package is used or Microsoft Windows Insteller is used for deployment, the whole application program needs to be reinstalled, and a Microsoft clickone deployment scheme needs a special server, has high technical requirements on deployment personnel, and is difficult to deploy.
Drawings
FIG. 1 is a schematic structural diagram of a software online updating system based on an xml file list according to an embodiment of the present application;
fig. 2 is a schematic diagram of a preset directory structure provided in an embodiment of the present application;
FIG. 3 is a program code diagram of a main program of a client provided in an embodiment of the present application;
FIG. 4 is a schematic illustration of a cached update program upgrade file;
fig. 5 is a schematic flowchart of a software online updating method based on an xml file list provided in an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
For easy understanding, please refer to fig. 1, an embodiment of the present application provides an online software updating system based on an xml file list, including: the method comprises the following steps that a server side, a client side updating program and a client side main program are adopted;
the server side is used for acquiring the xml manifest file and the update file and issuing the xml manifest file and the update file to a preset position according to a preset directory structure;
the client updating program is used for downloading all listed versions and all files matched with the listed versions one by one according to a target version transmitted by a client main program through parameters, and simultaneously updating the versions in parallel;
the client-side main program is used for checking the cached updating program updating file when the main program is started, updating the updating program, supporting the version comparison and updating reminding functions, pulling all updating lists behind the version of the client-side main program through the server side, providing a selectable updating target for a user through the client-side main program, and prompting major updating to the client through the client-side if a forced updating instruction is detected and the client-side main program is in a forced range.
It should be noted that the preset positions to which the server side issues the xml manifest file and the update file according to the preset directory structure are shown in fig. 2, where in fig. 2, 1 denotes a server side root directory to store online update resources; 2 denotes a software identification, which is designed to be used for other software; 3 represents a region mark, 0 represents global promotion, 66 represents Thailand edition, and 84 represents Vietnam edition, which supports subsequent increase; 4, software category identification, wherein the current 0 is determined as a basic version, and the software can be extended to 1 high-level version and 2 professional versions; 5, an order number is represented, the mainstream is 0, and the updating system design supports the provision of online push service for the customized version; 6, indicating the main version number of the software, and indicating the version of the pushed list; the release lot 7 for this version, which illustrates the release for the number of times, is also used for the release for the number of times for the customized version.
The program of the client main program can be represented as shown in fig. 3, in fig. 3:
a second row: the updating system designs a pre-sending test mode, and the formal system only pulls the enabled updating list, but the disabled updating list does not take effect, so that updating and debugging are facilitated;
fourth row: updating the release date;
the fifth element: the version targeted by the update is used for performing version association to obtain version upgrading history, and the application can be downloaded one by one according to the upgrading history;
a sixth row: current version, release batch;
the seventh row: updating grades, namely ordinary [ ordinary reminding ], important [ red special reminding ], and forced [ forced upgrading, which cannot be used without upgrading ];
eighth-ninth line: the upgrade is forced within a range, the version within the specified range is forced to upgrade, otherwise, the start of the network is not enabled (the network is disconnected, and the forced upgrade is disabled);
tenth-nineteenth rows: a special reminding mechanism is added, popup confirmation reminding is given according to the version of a special statement and a key description, such as copyright awareness updating and major version change, and multiple languages are supported;
twenty-first row: adding operation commands, which can be customized, and executing different operations according to different command updating programs, such as sdk registration updating and registry information updating, if a forced restart mode is applied to update the updating programs;
twenty-ninth row: version update description, supporting multiple languages, and specifying default language;
thirty-second-forty rows: a list of files to be downloaded;
the third twelve rows: the relative path of the file in the server is based on the path of the list file;
thirty-third row: storing a path after downloading the file, and updating the file according to the temp/of the folder where the program is located;
fourth row thirty: the name is saved after the file is downloaded, and is generally consistent with the server;
thirty-fifth element: updating the file version, designing for expansion, and carrying out version comparison synchronization;
third sixty-sixth line: the size of the file;
the third seventeenth row: checking the file MD5, and if the file MD5 fails for three times, terminating the updating;
thirty-eighth line: indicating whether the file needs to be decompressed;
the third nineteenth row: the file decompression path needing decompression is a relative path at present and is based on the path of the updating program;
forty-third row: indicating whether the system needs to be restarted to apply updating or not, and forcing the system to be restarted when the updating system is pushed to be updated;
forty-fourth row: restarting the relative path of the program, based on the path of the updating program;
forty-fifth row: the name of the restarted program.
The update program upgrade file cached in the embodiment of the present application is as shown in fig. 4, the update program upgrade file is limited to a ZIP update package, and a file in the ZIP update package is divided into two parts, namely, update.
The software online updating system based on the xml file list is convenient to deploy, does not need a professional deployment server, and can be deployed at a server side providing file services based on http, ftp and the like; the multi-version progressive upgrading is supported, one version can not be started to be upgraded at one time, and the target version can be upgraded at one time; the method supports the view of updated contents and multi-language; supporting regional and classified updating, and pushing updating aiming at different regional versions; md5 verification is supported, and the accuracy of downloading the file is ensured; self-updating of the updating program is supported, and self-improvement can be continuously carried out; the customized version is supported to provide updating service, and the customized version and the main version are under a set of management system; hierarchical updating is supported, including ordinary, important and forced updating; and updating and debugging are supported, and the effect is tested on the premise of not influencing formal users.
For easy understanding, please refer to fig. 5, an embodiment of a method for updating software online based on an xml file list is provided in the present application, the method includes:
when the main program is started, detecting a cached updating program upgrading file;
generating an update address, and pulling a current version update list of the server;
detecting whether forced updating exists or not, wherein the version is in a forced range, if so, inquiring a user whether updating is performed, and if not, listing an updating list for the user to select;
if the user does not update, the program is ended, and if the user updates, the parameters are transmitted to start the updating program;
if the version selected by the user from the updating list has the need-to-know prompt, popping up the need-to-know prompt, if the user confirms the need-to-know prompt, transmitting the parameters to start the updating program, otherwise, listing the updating list for the user to select;
after the updating program is started, loading an updating list, downloading all listed versions and all files matched with the listed versions one by one, and simultaneously updating the versions in parallel;
it should be noted that the server side obtains the xml manifest file and the update file, and issues the xml manifest file and the update file to a preset location according to a preset directory structure. The preset directory structure includes: the software version release system comprises a root directory, a software identification directory, an area identification directory, a software category identification directory, an order number directory, a software main version number and a software version release batch directory of a server side. The software identification catalog is stored in a lower-level catalog of the root catalog, the area identification catalog is stored in a lower-level catalog of the software identification catalog, the software category identification catalog is stored in a lower-level catalog of the software identification catalog, the order number catalog is stored in a lower-level catalog of the software category identification catalog, and the software major version number and the software version release catalog are stored in a lower-level catalog of the order number catalog in batches.
The application provides an embodiment of a device for software online updating based on an xml file list, the device is in communication connection with a server side, and the device comprises a main program module and a program updating module;
the server side obtains the xml manifest file and the update file, and the xml manifest file and the update file are issued to a preset position according to a preset directory structure;
the main program module is used for:
when the main program is started, detecting a cached updating program upgrading file;
generating an update address, and pulling a current version update list of the server;
detecting whether forced updating exists or not, wherein the version is in a forced range, if so, inquiring a user whether updating is performed, and if not, listing an updating list for the user to select;
if the user does not update, the program is ended, and if the user updates, the transmission parameter triggers the program updating module to start the updating program;
if the version selected by the user from the updating list has the need-to-know prompt, popping up the need-to-know prompt, if the user confirms the need-to-know prompt, transmitting the parameter to trigger the program updating module to start the updating program, and if not, listing the updating list for the user to select;
the program update module is to:
after the updating program is started, the updating list is loaded, all listed versions and all files matched with the listed versions are downloaded one by one, and version updating is applied in parallel while downloading.
The application provides an embodiment of a client for online updating of software based on an xml file list, and the client comprises the device for online updating of software based on an xml file list.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. 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.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
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, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer system (which may be a personal computer, a server, or a network system) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above 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; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. An online software updating system based on an xml file list, comprising: the method comprises the following steps that a server side, a client side updating program and a client side main program are adopted;
the server side is used for acquiring an xml manifest file and an update file, and issuing the xml manifest file and the update file to a preset position according to a preset directory structure;
the client updating program is used for downloading and verifying the updated files one by one according to a target version transmitted by the client main program through parameters and downloading all listed versions and all files matched with the listed versions one by one, and the versions are updated in parallel during downloading;
the client-side main program is used for checking the cached updating program updating file when the main program is started, updating the updating program, supporting the functions of version comparison and updating reminding, pulling all updating lists behind the version of the client-side main program through the server side, providing a selectable updating target for a user through the client-side main program, and prompting major updating to the client through the client-side if a forced updating instruction is detected and the client-side main program is in a forced range.
2. The xml file manifest-based software online update system of claim 1, wherein the preset directory structure comprises: the server-side root directory, the software identification directory, the area identification directory, the software category identification directory, the order number directory, the software main version number and the software version release batch directory.
3. The xml-file-list-based software online updating system according to claim 2, wherein the software identifier directory is stored in a lower directory of the root directory, the area identifier directory is stored in a lower directory of the software identifier directory, the software category identifier directory is stored in a lower directory of the software identifier directory, the order number directory is stored in a lower directory of the software category identifier directory, and the software major version number and the software version release directory are stored in a lower directory of the order number directory in batches.
4. The system for updating software based on xml file list on line according to claim 3, wherein said client main program supports the following functions:
pulling the enabled update file;
displaying the date of the update release;
displaying the version updated this time for version association to obtain version upgrading history, and downloading applications one by one according to the upgrading history;
displaying the current version and the release batch;
displaying update levels, wherein the update levels comprise common upgrade, important upgrade and forced upgrade;
configuring a forced upgrading range, and carrying out forced upgrading on the version in the specified range;
configuring a special reminding mechanism;
configuring a custom operation command, and updating a program to execute different operations according to different operation commands;
supporting version update description;
displaying a list of files to be downloaded;
displaying the relative path of the file at the server end;
displaying a path stored after the file is downloaded;
the name is saved after the file is downloaded, and the saved name is consistent with the saved name of the server side;
displaying the version of the update file;
displaying the file size;
performing MD5 check on the file;
indicating whether the file needs to be decompressed;
indicating a file decompression path needing to be decompressed;
indicating whether a reboot is required to apply the update;
displaying a relative path where the restart program is located;
the name of the restarted program is displayed.
5. The xml file manifest-based software online updating system of claim 1, wherein the update program upgrade file includes an update package of a.zip and an in-package file of the update package of a.zip.
6. An online software updating method based on an xml file list is characterized by comprising the following steps:
when the main program is started, detecting a cached updating program upgrading file;
generating an update address, and pulling a current version update list of the server;
detecting whether forced updating exists or not, wherein the version is in a forced range, if so, inquiring a user whether updating is performed, and if not, listing an updating list for the user to select;
if the user does not update, the program is ended, and if the user updates, the parameters are transmitted to start the updating program;
if the version selected by the user from the updating list has the need-to-know prompt, popping up the need-to-know prompt, if the user confirms the need-to-know prompt, transmitting the parameters to start the updating program, otherwise, listing the updating list for the user to select;
after an updating program is started, loading an updating list, downloading all listed versions and all files matched with the listed versions one by one, and simultaneously updating the versions in parallel;
the server side obtains an xml manifest file and an update file, and issues the xml manifest file and the update file to a preset position according to a preset directory structure.
7. The method for updating software on line based on xml file list according to claim 6, wherein said preset directory structure comprises: the server-side root directory, the software identification directory, the area identification directory, the software category identification directory, the order number directory, the software main version number and the software version release batch directory.
8. The method for updating software based on xml file list according to claim 7, wherein said software id directory is stored in a lower directory of said root directory, said area id directory is stored in a lower directory of said software id directory, said software category id directory is stored in a lower directory of said software id directory, said order number directory is stored in a lower directory of said software category id directory, and said software major version number and said software version release directory are stored in a lower directory of said order number directory in batch.
9. The device for updating the software on line based on the xml file list is in communication connection with a server side and is characterized by comprising a main program module and a program updating module;
the server side obtains an xml (extensible markup language) manifest file and an update file, and issues the xml manifest file and the update file to a preset position according to a preset directory structure;
the main program module is used for:
when the main program is started, detecting a cached updating program upgrading file;
generating an update address, and pulling a current version update list of the server;
detecting whether forced updating exists or not, wherein the version is in a forced range, if so, inquiring a user whether updating is performed, and if not, listing an updating list for the user to select;
if the user does not update, the program is ended, and if the user updates, the transmission parameter triggers the program updating module to start the updating program;
if the version selected by the user from the updating list has the need-to-know prompt, popping up the need-to-know prompt, if the user confirms the need-to-know prompt, transmitting the parameter to trigger the program updating module to start the updating program, and if not, listing the updating list for the user to select;
the program update module is to:
after the updating program is started, loading an updating list, downloading all listed versions and all files matched with the listed versions one by one, and simultaneously applying version updating in parallel.
10. A client for online update of software based on xml file list, characterized in that, the client comprises the online update of software based on xml file list apparatus according to claim 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911260046.6A CN111008030A (en) | 2019-12-10 | 2019-12-10 | Software online updating system and method based on xml file list and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911260046.6A CN111008030A (en) | 2019-12-10 | 2019-12-10 | Software online updating system and method based on xml file list and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111008030A true CN111008030A (en) | 2020-04-14 |
Family
ID=70114112
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911260046.6A Pending CN111008030A (en) | 2019-12-10 | 2019-12-10 | Software online updating system and method based on xml file list and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111008030A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111552499A (en) * | 2020-06-03 | 2020-08-18 | 上海通联金融服务有限公司 | AIC version replacement tool based on Shell language |
| CN112328283A (en) * | 2020-11-12 | 2021-02-05 | 北京字节跳动网络技术有限公司 | Application program updating method, device, equipment and medium |
| CN112445705A (en) * | 2020-11-17 | 2021-03-05 | 中国南方电网有限责任公司 | Software running system, method, device, computer equipment and storage medium |
| CN114338395A (en) * | 2021-12-29 | 2022-04-12 | 武汉烽火信息集成技术有限公司 | C/S communication network management method, storage medium, electronic equipment and system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102223380A (en) * | 2011-07-07 | 2011-10-19 | 昆明伯尔瑞科技开发有限公司 | Client terminal automatic updating frame based on Webservice and application thereof |
| US20130104115A1 (en) * | 2011-10-21 | 2013-04-25 | International Business Machines Corporation | Systems and methods for upgrading a version of software |
| CN103902299A (en) * | 2012-12-24 | 2014-07-02 | 航天信息股份有限公司 | Software version updating method and system |
| CN105808274A (en) * | 2014-12-30 | 2016-07-27 | 航天信息股份有限公司 | Software upgrading method and system as well as corresponding clients and servers |
| CN106201614A (en) * | 2016-07-11 | 2016-12-07 | 天津中兴智联科技有限公司 | A kind of universal method and system that multiple similar software can be carried out chain type upgrading |
-
2019
- 2019-12-10 CN CN201911260046.6A patent/CN111008030A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102223380A (en) * | 2011-07-07 | 2011-10-19 | 昆明伯尔瑞科技开发有限公司 | Client terminal automatic updating frame based on Webservice and application thereof |
| US20130104115A1 (en) * | 2011-10-21 | 2013-04-25 | International Business Machines Corporation | Systems and methods for upgrading a version of software |
| CN103902299A (en) * | 2012-12-24 | 2014-07-02 | 航天信息股份有限公司 | Software version updating method and system |
| CN105808274A (en) * | 2014-12-30 | 2016-07-27 | 航天信息股份有限公司 | Software upgrading method and system as well as corresponding clients and servers |
| CN106201614A (en) * | 2016-07-11 | 2016-12-07 | 天津中兴智联科技有限公司 | A kind of universal method and system that multiple similar software can be carried out chain type upgrading |
Non-Patent Citations (1)
| Title |
|---|
| 朱东杰等: "《软件测试与质量保证》", 30 June 2017 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111552499A (en) * | 2020-06-03 | 2020-08-18 | 上海通联金融服务有限公司 | AIC version replacement tool based on Shell language |
| CN112328283A (en) * | 2020-11-12 | 2021-02-05 | 北京字节跳动网络技术有限公司 | Application program updating method, device, equipment and medium |
| CN112445705A (en) * | 2020-11-17 | 2021-03-05 | 中国南方电网有限责任公司 | Software running system, method, device, computer equipment and storage medium |
| CN112445705B (en) * | 2020-11-17 | 2022-05-03 | 中国南方电网有限责任公司 | Software running system, method and device based on trusted verification and computer equipment |
| CN114338395A (en) * | 2021-12-29 | 2022-04-12 | 武汉烽火信息集成技术有限公司 | C/S communication network management method, storage medium, electronic equipment and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111008030A (en) | Software online updating system and method based on xml file list and related device | |
| US9146729B2 (en) | Deployment and updating of applications and drivers on a client device using an extensible markup language (XML) configuration file | |
| US9032052B2 (en) | Deployment of a driver or an application on a client device having a write-filter | |
| EP2786248B1 (en) | Automatic updating of an application or a driver on a client device using a deployment configuration file | |
| EP2786249B1 (en) | Creation or installation of a disk image for a target device having one of a plurality of hardware platforms | |
| CN102622241B (en) | A kind of method for upgrading software and device | |
| US20120323857A1 (en) | Method for Restoring Software Applications on Desktop Computers | |
| CN103942065B (en) | For updating the method and system of firmware compatibility data | |
| US20150178063A1 (en) | Automatic management of software patch installation | |
| EP2955627B1 (en) | Managing versions of components of a software suite | |
| CN105094913B (en) | System, base band firmware and system application upgrade method and device | |
| US20110041124A1 (en) | Version Management System | |
| US20090249283A1 (en) | Modelling software appliance | |
| KR101674975B1 (en) | System upgrade method, apparatus, device, program, and recording medium | |
| WO2014035931A1 (en) | Branded computer devices and apparatus to connect user and enterprise | |
| CN105389187B (en) | System updating method | |
| CN104765816B (en) | Browser upgrading method and device and electronic equipment | |
| EP3320436A1 (en) | System and method for provisioning cloud services across heterogeneous computing environments | |
| CN108536464A (en) | A kind of hot restorative procedure and device of application program | |
| CN105653298A (en) | Application program update method and terminal | |
| JP2012146241A (en) | Software update method, software update device, and software update program | |
| CN111679842B (en) | Application program hot update processing method, device and system | |
| US8381171B2 (en) | Customized networked-based commerce system packages | |
| CN106126271B (en) | Data upgrading method and device | |
| CN112947951A (en) | Software installation method and related equipment |
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 | ||
| CB02 | Change of applicant information |
Address after: Room 1301, No.132, Fengqi Road, phase III, software park, Xiamen City, Fujian Province Applicant after: Xiamen Entropy Technology Co.,Ltd. Address before: 361000, Xiamen three software park, Fujian Province, 8 North Street, room 2001 Applicant before: XIAMEN ZKTECO INFORMATION TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200414 |
|
| RJ01 | Rejection of invention patent application after publication |