CN103067484B - A kind of method and system of auto-update application program - Google Patents
A kind of method and system of auto-update application program Download PDFInfo
- Publication number
- CN103067484B CN103067484B CN201210570429.5A CN201210570429A CN103067484B CN 103067484 B CN103067484 B CN 103067484B CN 201210570429 A CN201210570429 A CN 201210570429A CN 103067484 B CN103067484 B CN 103067484B
- Authority
- CN
- China
- Prior art keywords
- client
- server
- client application
- upgrade components
- application
- 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.)
- Expired - Fee Related
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of method and system of auto-update application program, system comprises the client, Web server, database server and the file server that comprise upgrade components.Method comprises: S1, upgrade components obtain the server end version number of the client application of database server stores by Web server; S2, upgrade components obtain the current client release number of client application; S3, upgrade components judge whether server end version number and client release be number identical, and when difference by Web server access file server, transaction file are downloaded to client; S4, upgrade components use transaction file updating client application program, and revise client release number; Amended client release number is stored into database server by S5, upgrade components.Realize automatic decision and the execution of upgrading, and allow administrative staff to check the update status of the application version of each client.
Description
Technical field
The present invention relates to computer realm, more particularly, relate to a kind of method and system of auto-update application program.
Background technology
Client application based on client/server (C/S, Client/Server) schema management system is deployed in different physical nodes, compares dispersion.In use, due to a variety of causes, application program needs to modify.After each amendment completes, client more new capital requires that user reinstalls application program.And C/S model management system may have tens, individual even several thousand clients of hundreds of, and client may distribute dispersion, each application program updating, all can expend huge maintenance workload.
Therefore, the shortcoming that C/S model is maximum is exactly that maintenance upgrade is loaded down with trivial details.Maintenance upgrade work after system installation is the most important link of application program life cycle.For the upgrading of the client application of C/S model, the past realizes often by online file and copying of USB flash disk.This method needs manual intervention, sometimes also may with virus, and when a lot of application programs of client carry out frequent updating, the task of renewal is just heavy can't bear, and also often occurs the client of omitting upgrading.
Upgrading due to application program is a lasting process, so there will be a lot of upgraded version.But what run in client can only be a unified application version, while multiple like this version, there is the instability that also result in the application program of FTP client FTP and unreliable.
Carry out application program updating according to existing mode and there is following problems:
(1) professional needs the upgrade job carrying out application program to scene, labor intensive resource;
(2) complicated operation, because upgrading is partly, makes the mistake constantly;
(3) user must be appreciated that and will go down loading updating document upgrading application program, and the Experience Degree of user is not high;
(4) Component Gallery is chaotic, and administrative staff cannot the update status of application version of each client of global knowledge.
Summary of the invention
The method and system of auto-update application program of the present invention needs professional's execute-in-place for prior art, and complicated operation, complete upgrading cannot be carried out to application software, Component Gallery is chaotic, administrative staff cannot the defect of update status of application version of each client of global knowledge, a kind of method and system of auto-update application program is provided, can automatic decision application program the need of upgrading, and to needing the application program of upgrading to carry out complete upgrading, and administrative staff are allowed to check the update status of the application version of each client.
The technical scheme that the present invention solves the employing of its technical problem is: a kind of method providing auto-update application program, comprises the following steps:
The upgrade components of S1, client, by Web server accessing database server, obtains the server end version number of the client application that described database server stores;
S2, described upgrade components read client local profile, obtain the client release number that client application is current;
S3, described upgrade components judge whether described server end version number and described client release be number identical, and when both are not identical by described Web server access file server, download to client by with a described server version number corresponding transaction file;
S4, described upgrade components use the transaction file downloaded to upgrade described client application, and are revised as by described client release number consistent with described server end version number;
Amended client release number, by described Web server, is stored into described database server by S5, described upgrade components;
Wherein, described database server comprises relational database, and described relational database comprises the lastest imformation of client application, and lastest imformation comprises the client release number upgrading mark and client application;
Described step S5 comprises following sub-step:
Described upgrade components accesses described database server by described Web server, marks described renewal mark, and amended client release number is stored into described relational database, to replace original client release number.
Preferably, step S3 comprises the following steps:
S3a, described upgrade components judge that whether described server end version number and described client release be number identical, if both are identical execution S3b, otherwise performs S3c;
S3b, perform described client application;
S3c, described upgrade components access described file server by described Web server, download to client by with a described server version number corresponding transaction file.
Further preferably, step S3c comprises the following steps:
S3c1, described upgrade components access described database server by described Web server, and what obtain the transaction file corresponding with described server end version number of described database server storage deposits path;
S3c2, described upgrade components by described Web server, deposit file server described in path access according to described transaction file, download to client by with a described server version number corresponding transaction file.
Further preferably, described relational database also comprises the version information of client application, and the version information of described client application also comprises from date and date of expiry, revised context and the publisher of client application corresponding to the system number of client, described server end version number; The time that the lastest imformation of described client application also comprises the system number of client, the IP address of client, the computer name of client, the physical location of client and upgraded for the last time.
Preferably, described method also comprised step before step S1:
S0, start described client application, described client application calls described upgrade components.
Preferably, described method also comprises step:
S6, described upgrade components delete the transaction file downloaded.
There is provided a kind of system of auto-update application program, the client comprising Web server and be connected with described Web server by communication network, be is characterized in that, the system of described auto-update application program also comprises:
Database server, it is connected with described Web server, it comprises relational database, described relational database comprises the version information of client application and the lastest imformation of client application, the version information of described client application comprises server end version number, and the lastest imformation of described client application comprises the client release number upgrading mark and client application; And
File server, it is connected with described Web server, for storage update file;
Described client also comprises upgrade components, described upgrade components accesses described database server by described Web server, obtain the described server end version number of client application, described upgrade components reads client local profile, obtain the client release number that client application is current, described upgrade components judges whether described server end version number and described client release be number identical, and access described file server when both are not identical by described Web server, described client is downloaded to by with a described server version number corresponding transaction file, the transaction file downloaded is used to upgrade described client application, and described client release number is revised as consistent with described server end version number,
Described upgrade components also accesses described database server by described Web server, marks described renewal mark, and amended client release number is stored into described relational database, to replace original client release number.
Preferably, what the version information of described client application also comprised transaction file deposits path; Described upgrade components is when described server end version number and described client release are number not identical, described database server is accessed by described Web server, what obtain described transaction file deposits path, and by described Web server, deposit file server described in path access according to described transaction file, download to described client by with a described server version number corresponding transaction file.
Preferably, the version information of described client application also comprises from date and date of expiry, revised context and the publisher of client application corresponding to the system number of client, described server end version number; The time that the lastest imformation of described client application also comprises the system number of client, the IP address of client, the computer name of client, the physical location of client and upgraded for the last time.
The method and system of auto-update application program of the present invention has following beneficial effect: after startup client application, upgrade components starts, upgrade components obtains client release number and the server end version number of application program, current client application is gone out the need of upgrading by multilevel iudge, and when needing upgrading, transaction file corresponding for server end version number is downloaded to customer side, transaction file is used to be version corresponding to server end version number by the edition upgrading of current client application, and amended client release number is saved in database server, when needs user participates in judging, achieve the automation complete upgrading of client application degree, in addition, allow administrative staff by Web server accessing database server, read the lastest imformation of the client application in relational database, monitor the upgrade case of the application program of each client, realize the global administration to client application upgrading.
Accompanying drawing explanation
Fig. 1 is the schematic diagram of system one embodiment of auto-update application program of the present invention;
Fig. 2 is the functional block diagram of the client in the present invention;
Fig. 3 is the workflow diagram that the system of auto-update application program of the present invention realizes auto-update;
Fig. 4 is the flow chart of method first embodiment of auto-update application program of the present invention;
Fig. 5 is the flow chart of method second embodiment of auto-update application program of the present invention.
Embodiment
Below in conjunction with drawings and Examples, the present invention is further explained.
Fig. 1 is the schematic diagram of system 100 1 embodiment of auto-update application program of the present invention, and see Fig. 1 and Fig. 2, system 100 of the present invention comprises Web server 110, multiple long-range client 120, database server 130 and file server 140.Client such as, by communication network, local area network (LAN), metropolitan area network, wide area network, connects Web server 110.Database server 130 is connected with Web server 110 respectively with file server 140.
Wherein, the access mode of Web server 110 for providing transaction file to download, can adopt File Transfer Protocol or HTTP mode to download, according to the network bandwidth, fail safe, performance etc. because usually selecting.Such as adopt the downloading mode of HTTP multithreading, the main cause of adopting in this way is that http protocol is simple and quick, can customize each data package size downloaded, and allows the data object of transmission any type.
Database server 130 comprises relational database, and relational database comprises the version information of client application and the lastest imformation of client application.Wherein, the version information of client application comprise the system number of client, the server end version number of client application journey, the from date of the client-side program of this version and date of expiry (from date of the client application that server end version number is corresponding and date of expiry), revised context (improvement that the client application of this version is done compared with money version), transaction file deposit path and publisher.The lastest imformation of client application also comprise the system number of client 120, the IP address of client 120, the computer name of client 120, client 120 physical location (physical address of computer), upgrade the time that mark, the client release number of client application and client application upgraded for the last time.
File server 140 is for storing the transaction file upgraded to by client application needed for the version corresponding with server end version number.
Client 120 comprises upgrade components 121.Fig. 3 is the workflow diagram (in HTTP mode) that the system 100 of auto-update application program of the present invention realizes auto-update, as shown in Figure 3, when client 120 starts client application, client application calls upgrade components 121, now, client application does not also perform.Upgrade components 121 reads local configuration file, and local profile comprises for the configuration information of the relational database of connection data storehouse server 130 and the current client release number of client application, i.e. the version number of current application program.Upgrade components 121, according to the configuration information of the relational database for connection data storehouse server 130, by Web server 110 accessing database server 130, obtains the server end version number of the client application stored in relational database.
Upgrade components 121 judges that whether the server end version number and the client release that obtain be number identical, determines whether to upgrade with this.After an application issued, be a baseline version when each client is issued initial, as V1.0.After server updating, version model changes, produce V1.1, V1.2 etc. version like this (note: the 1st numeral key plate this. the 2nd numeral time version, general great renewal and improvement. major version number of just upgrading).According to version model height, client determines that active client application program is the need of upgrading.
If server end version number and client release are number identical, representing current client application is latest edition, without the need to upgrading, now directly will perform client application, and preferably, upgrade components 121 is closed simultaneously.If both are not identical, represent current client application and need upgrading, upgrade components 121 is by Web server 110 accessing database server 130, what obtain transaction file deposits path, and deposit path access file server 140 by Web server 110 according to transaction file, download to client 120 by with a server version number corresponding transaction file.Wherein, upgrade components 121 this avoid the problem of sharing conflict under transaction file being downloaded to client 120 1 interim application catalogs.
After transaction file has been downloaded, upgrade components 121 uses the application program of transaction file updating client current version, and client release number is revised as consistent with server end version number, by Web server 110 accessing database server 130, flag update mark, new client release number is stored in relational database, to replace original client release number.Download Info by client this locality is recorded in the daily record of database server 130, to avoid repeatedly upgrading.
Wherein, upgrade components 121 uses the detailed process of the application program of transaction file updating client current version to be: under the transaction file of download being copied to the corresponding catalogue of client, replace original old program file.In addition, the transaction file under the interim application catalog of rear destruction has been copied.After having upgraded, the client application after upgrading will be performed.
System 100 of the present invention, allow administrative staff by Web server accessing database server 130, read the lastest imformation of the client application in relational database, monitor the upgrade case of the application program of each client 120, realize the global administration to client application upgrading.
In other embodiments of its system 100 of the present invention, the program for realizing upgrade components 121 function can also be write, and write in client application.Same, when starting client application, the program that client application can call for realizing upgrade components 121 function realizes similar function.
Fig. 4 is the flow chart of method first embodiment of auto-update application program of the present invention, and as shown in Figure 4, in the present embodiment, method of the present invention comprises the following steps:
S1, upgrade components 121, by Web server 110 accessing database server 130, obtain the server end version number of the client application that described database server 130 stores;
S2, upgrade components 121 read client 120 local profile, obtain the client release number that client application is current;
S3, upgrade components 121 judge whether server end version number and described client release be number identical, and when both are not identical by Web server 110 access file server 140, download to client 120 by with a server version number corresponding transaction file;
S4, upgrade components 121 use the transaction file downloaded to upgrade described client application, and are revised as by client release number consistent with server end version number;
Amended client release number, by described Web server 110, is stored into described database server 130 by S5, upgrade components 121.
In the present embodiment, step S3 comprises the following steps: S3a, upgrade components 121 judge that whether server end version number and client release be number identical, if both are identical execution S3b, otherwise performs S3c; S3b, execution client application; S3c, upgrade components 121, by Web server 110 access file server 140, download to client 120 by with a server version number corresponding transaction file.
Wherein, step S3c comprises the following steps: S3c1, upgrade components 121 are by Web server 110 accessing database server 130, and what obtain the transaction file corresponding with server end version number of database server 130 storage deposits path; S3c2, upgrade components 121, by Web server 110, deposit path access file server 140 according to transaction file, download to client 120 by with a server version number corresponding transaction file.
Database server 130 comprises relational database, relational database comprises the lastest imformation of client application and the lastest imformation of client application, wherein, the lastest imformation of client application comprise the system number of client, the server end version of client application number, the from date of client application corresponding to server end version number and date of expiry, revised context and publisher.The lastest imformation of client application comprise the system number of client 120, the IP address of client 120, the computer name of client 120, client 120 physical location, upgrade mark, the client release number of client application and time of having upgraded for the last time.
In step s 5, amended client release number is stored into database server 130 by described Web server 110 by upgrade components 121, to replace the client release number of the client application of client application.
Fig. 5 is the flow chart of method second embodiment of auto-update application program of the present invention, as shown in Figure 5, in the present embodiment, before step S1, also comprises step: S0, startup client application, client application calls upgrade components 121.Method of the present invention also comprises step: S6, upgrade components 121 delete the transaction file downloaded.
In the present embodiment, all the other situations are identical with method first embodiment of auto-update application program of the present invention, do not repeat them here.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within right of the present invention.In addition, the technical characteristic in various embodiments of the present invention may be used alone, can also be used in combination.Further, the order of the step recorded in method of the present invention is not limited to the present invention, and such as, the order of step S1 and S2 can be exchanged, and the order of step S5 and S6 can be exchanged.
Claims (9)
1. a method for auto-update application program, is characterized in that, comprises the following steps:
The upgrade components (121) of S1, client (120), by Web server (110) accessing database server (130), obtains the server end version number of the client application that described database server (130) stores;
S2, described upgrade components (121) read client (120) local profile, obtain the client release number that client application is current;
S3, described upgrade components (121) judge whether described server end version number and described client release be number identical, and when both are not identical by described Web server (110) access file server (140), download to client (120) by with a described server version number corresponding transaction file;
S4, described upgrade components (121) use the transaction file downloaded to upgrade described client application, and are revised as by described client release number consistent with described server end version number;
Amended client release number, by described Web server (110), is stored into described database server (130) by S5, described upgrade components (121);
Wherein, described database server (130) comprises relational database, and described relational database comprises the lastest imformation of client application, and lastest imformation comprises the client release number upgrading mark and client application;
Described step S5 comprises following sub-step:
Described upgrade components (121) accesses described database server (130) by described Web server (110), mark described renewal mark, and amended client release number is stored into described relational database, to replace original client release number.
2. the method for auto-update application program according to claim 1, it is characterized in that, step S3 comprises the following steps:
S3a, described upgrade components (121) judge that whether described server end version number and described client release be number identical, if both are identical execution S3b, otherwise performs S3c;
S3b, perform described client application;
S3c, described upgrade components (121) access described file server (140) by described Web server (110), download to client (120) by with a described server version number corresponding transaction file.
3. the method for auto-update application program according to claim 2, it is characterized in that, step S3c comprises the following steps:
S3c1, described upgrade components (121) access described database server (130) by described Web server (110), and what obtain the transaction file corresponding with described server end version number that described database server (130) stores deposits path;
S3c2, described upgrade components (121) are by described Web server (110), deposit file server described in path access (140) according to described transaction file, download to client (120) by with a described server version number corresponding transaction file.
4. the method for auto-update application program according to claim 3, it is characterized in that, described relational database also comprises the version information of client application, and the version information of described client application comprises from date and date of expiry, revised context and the publisher of client application corresponding to the system number of client, described server end version number; The time that the lastest imformation of described client application also comprises the system number of client (120), the IP address of client (120), the computer name of client (120), the physical location of client (120) and upgraded for the last time.
5. the method for auto-update application program according to claim 1, is characterized in that, described method also comprised step before step S1:
S0, start described client application, described client application calls described upgrade components (121).
6. the method for auto-update application program according to claim 1, is characterized in that, described method also comprises step:
S6, described upgrade components (121) delete the transaction file downloaded.
7. the system of an auto-update application program, the client (120) comprising Web server (110) and be connected with described Web server (110) by communication network, it is characterized in that, the system of described auto-update application program also comprises:
Database server (130), it is connected with described Web server (110), it comprises relational database, described relational database comprises the version information of client application and the lastest imformation of client application, the version information of described client application comprises server end version number, and the lastest imformation of described client application comprises the client release number upgrading mark and client application; And
File server (140), it is connected with described Web server (110), for storage update file;
Described client (120) also comprises upgrade components (121), described upgrade components (121) accesses described database server (130) by described Web server (110), obtain the described server end version number of client application, described upgrade components (121) reads client (120) local profile, obtain the client release number that client application is current, described upgrade components (121) judges whether described server end version number and described client release be number identical, and access described file server (140) when both are not identical by described Web server (110), described client (120) is downloaded to by with a described server version number corresponding transaction file, the transaction file downloaded is used to upgrade described client application, and described client release number is revised as consistent with described server end version number,
Described upgrade components (121) also accesses described database server (130) by described Web server (110), mark described renewal mark, and amended client release number is stored into described relational database, to replace original client release number.
8. the system of auto-update application program according to claim 7, what it is characterized in that the version information of described client application also comprises transaction file deposits path; Described upgrade components (121) is when described server end version number and described client release are number not identical, described database server (130) is accessed by described Web server (110), what obtain described transaction file deposits path, and by described Web server (110), deposit file server described in path access (140) according to described transaction file, download to described client (120) by with a described server version number corresponding transaction file.
9. the system of auto-update application program according to claim 8, it is characterized in that, the version information of described client application also comprises from date and date of expiry, revised context and the publisher of client application corresponding to the system number of client, described server end version number; The time that the lastest imformation of described client application also comprises the system number of client (120), the IP address of client (120), the computer name of client (120), the physical location of client (120) and upgraded for the last time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210570429.5A CN103067484B (en) | 2012-12-25 | 2012-12-25 | A kind of method and system of auto-update application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210570429.5A CN103067484B (en) | 2012-12-25 | 2012-12-25 | A kind of method and system of auto-update application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103067484A CN103067484A (en) | 2013-04-24 |
| CN103067484B true CN103067484B (en) | 2015-11-18 |
Family
ID=48109938
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210570429.5A Expired - Fee Related CN103067484B (en) | 2012-12-25 | 2012-12-25 | A kind of method and system of auto-update application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103067484B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105528205A (en) * | 2015-11-30 | 2016-04-27 | 用友优普信息技术有限公司 | Update control method and update control system |
| CN105955763A (en) * | 2016-04-20 | 2016-09-21 | 努比亚技术有限公司 | Terminal, and control method based on application program |
| CN112925544A (en) * | 2021-02-26 | 2021-06-08 | 湖南强智科技发展有限公司 | Method and device for updating application program, electronic equipment and computer storage medium |
Families Citing this family (39)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279373B (en) * | 2013-05-31 | 2017-09-22 | 广州市动景计算机科技有限公司 | The update method and device of browser case function |
| CN104378403A (en) * | 2013-08-16 | 2015-02-25 | 中兴通讯股份有限公司 | Terminal and updating method thereof |
| CN103631869B (en) * | 2013-11-05 | 2018-04-17 | 北京奇虎科技有限公司 | A kind of method and apparatus for alleviating server-side database access pressure |
| CN104007994B (en) * | 2014-06-11 | 2015-04-01 | 焦点科技股份有限公司 | Updating method, upgrading method and upgrading system based on strategy storeroom interaction |
| CN105302587B (en) * | 2014-06-30 | 2019-01-11 | 腾讯科技（深圳）有限公司 | Data-updating method and device |
| CN104199695A (en) * | 2014-08-27 | 2014-12-10 | 浪潮软件股份有限公司 | Automatic upgrading method of Web applications |
| CN104199666B (en) * | 2014-09-09 | 2018-05-29 | 北京京东尚科信息技术有限公司 | A kind of application program Dynamic Configuration and device |
| CN105790997A (en) * | 2014-12-26 | 2016-07-20 | 北大医疗信息技术有限公司 | Configuration data update method and system, client and server |
| CN104639652A (en) * | 2015-03-04 | 2015-05-20 | 太仓市同维电子有限公司 | Method and system for automatically updating programs |
| CN106155651B (en) * | 2015-03-31 | 2019-03-01 | 广州四三九九信息科技有限公司 | The automation publication of application version and the method and system of update |
| CN104834550A (en) * | 2015-05-29 | 2015-08-12 | 北京京东尚科信息技术有限公司 | Method and device for updating distributed web crawlers |
| CN105071975B (en) * | 2015-09-07 | 2019-03-12 | 北京瑞星网安技术股份有限公司 | The method and system of data transmission and distribution |
| CN105743974A (en) * | 2016-01-26 | 2016-07-06 | 北京乐动卓越科技有限公司 | Client information updating method |
| CN107026830A (en) * | 2016-02-02 | 2017-08-08 | 上海格尔软件股份有限公司 | The safety method that a kind of application program is upgraded automatically |
| CN105867941A (en) * | 2016-04-18 | 2016-08-17 | 深圳市永兴元科技有限公司 | Software upgrading system and realization method thereof |
| CN105975298A (en) * | 2016-04-29 | 2016-09-28 | 福建联迪商用设备有限公司 | Method and system for remotely controlling applications of Android terminal |
| CN107704278A (en) * | 2016-08-08 | 2018-02-16 | 北京京东尚科信息技术有限公司 | Application upgrade method and apparatus |
| CN106445610A (en) * | 2016-10-08 | 2017-02-22 | 乐视控股（北京）有限公司 | Application processing method and device |
| CN106528204A (en) * | 2016-10-12 | 2017-03-22 | 杭州华为数字技术有限公司 | System upgrading method and apparatus |
| CN106599221A (en) * | 2016-12-16 | 2017-04-26 | 北京用友审计软件有限公司 | Data processing method and device |
| CN106790115B (en) * | 2016-12-27 | 2019-11-05 | 北京天融信网络安全技术有限公司 | Nginx upstream agent service system and implementation method |
| WO2018170786A1 (en) * | 2017-03-22 | 2018-09-27 | 华为技术有限公司 | Application program updating method |
| CN107015831A (en) * | 2017-03-31 | 2017-08-04 | 武汉票据交易中心有限公司 | A kind of client updating management method upgraded based on server end and system |
| CN107343031A (en) * | 2017-06-21 | 2017-11-10 | 福建中金在线信息科技有限公司 | A kind of method, apparatus for automatically updating file, electronic equipment and storage medium |
| CN107291511A (en) * | 2017-06-30 | 2017-10-24 | 百度在线网络技术（北京）有限公司 | Method and apparatus for the application program updating of vehicle-mounted Android system |
| CN107608688A (en) * | 2017-07-28 | 2018-01-19 | 福建联迪商用设备有限公司 | Terminal device timesharing upgrade method and computer-readable recording medium |
| CN107967145A (en) * | 2017-11-16 | 2018-04-27 | 南京轩世琪源软件科技有限公司 | A kind of Mobile payment terminal system hot upgrade method online |
| CN108132794A (en) * | 2017-12-29 | 2018-06-08 | 普华基础软件股份有限公司 | A kind of operating system update method and system |
| CN108845821B (en) * | 2018-09-28 | 2022-01-14 | 南昌努比亚技术有限公司 | Application program updating method, terminal and computer readable storage medium |
| CN109002315A (en) * | 2018-10-31 | 2018-12-14 | Oppo广东移动通信有限公司 | Application program update method, apparatus, terminal and storage medium |
| CN109634634A (en) * | 2018-12-12 | 2019-04-16 | 浪潮(北京)电子信息产业有限公司 | A kind of BMC firmware upgrade method, device and terminal |
| CN109491693A (en) * | 2018-12-29 | 2019-03-19 | 深圳点猫科技有限公司 | A kind of the heat update processing method and electronic equipment of graphical programming client |
| CN110209412A (en) * | 2019-04-26 | 2019-09-06 | 视联动力信息技术股份有限公司 | A kind of system version update method, device and readable storage medium storing program for executing |
| CN111666081B (en) * | 2020-04-30 | 2024-04-05 | 平安科技（深圳）有限公司 | Git-based project version release method, device, equipment and medium |
| CN111787340A (en) * | 2020-05-25 | 2020-10-16 | 天津车之家数据信息技术有限公司 | Network live broadcast system and method |
| CN111984297A (en) * | 2020-09-15 | 2020-11-24 | 南京伟思医疗科技股份有限公司 | Central server distributed automatic upgrading method based on 4G network |
| CN112667258B (en) * | 2020-12-23 | 2023-10-31 | 艾体威尔电子技术(北京)有限公司 | Remote upgrading method for external equipment program of android POS machine |
| CN114760320B (en) * | 2020-12-29 | 2023-09-12 | 广州视源电子科技股份有限公司 | Data synchronization method and system for client and middle server and client |
| CN115914451A (en) * | 2022-10-27 | 2023-04-04 | 兴业银行股份有限公司 | Forced updating method and system for android application version |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101158906A (en) * | 2007-08-10 | 2008-04-09 | 林明辉 | Customer terminals program automatic update method |
| CN101409709A (en) * | 2008-11-24 | 2009-04-15 | 浪潮通信信息系统有限公司 | Method for publishing client terminal program of communication network management system automatically |
| CN102098662A (en) * | 2009-12-09 | 2011-06-15 | 乐金电子(中国)研究开发中心有限公司 | Method and system for updating software of mobile terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100400458B1 (en) * | 2001-05-14 | 2003-10-01 | 엘지전자 주식회사 | Method to Upgrade a Protocol used in Network available Home Appliance |
-
2012
- 2012-12-25 CN CN201210570429.5A patent/CN103067484B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101158906A (en) * | 2007-08-10 | 2008-04-09 | 林明辉 | Customer terminals program automatic update method |
| CN101409709A (en) * | 2008-11-24 | 2009-04-15 | 浪潮通信信息系统有限公司 | Method for publishing client terminal program of communication network management system automatically |
| CN102098662A (en) * | 2009-12-09 | 2011-06-15 | 乐金电子(中国)研究开发中心有限公司 | Method and system for updating software of mobile terminal |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105528205A (en) * | 2015-11-30 | 2016-04-27 | 用友优普信息技术有限公司 | Update control method and update control system |
| CN105955763A (en) * | 2016-04-20 | 2016-09-21 | 努比亚技术有限公司 | Terminal, and control method based on application program |
| CN112925544A (en) * | 2021-02-26 | 2021-06-08 | 湖南强智科技发展有限公司 | Method and device for updating application program, electronic equipment and computer storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103067484A (en) | 2013-04-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103067484B (en) | A kind of method and system of auto-update application program | |
| CN110546606B (en) | Tenant upgrade analysis system and method | |
| JP7011737B2 (en) | Systems and methods for connector development and integrated channel deployment | |
| US10452646B2 (en) | Deploying changes in a multi-tenancy database system | |
| US20180203690A1 (en) | Application Programming Interface for Providing Access to Computing Platform Definitions | |
| RU2404451C2 (en) | Framework for expandable and automatic replicating management of configuration of pool of servers | |
| CN101689182B (en) | Efficient updates for distributed file systems | |
| JP5788934B2 (en) | Cloud computing based data sharing system and method | |
| US9733920B2 (en) | System, method and computer program product for associating a plurality of stored elements with a creation of a patch | |
| US9208184B1 (en) | System design support apparatus and system design supporting method | |
| CN1668010A (en) | Tag-based schema for distributing update metadata in an update distribution system | |
| US20200234213A1 (en) | Method and system for implementing an adaptive data governance system | |
| US8549129B2 (en) | Live migration method for large-scale IT management systems | |
| CN105723363A (en) | Master schema shared across multiple tenants with dynamic update | |
| CN103475721A (en) | System for updating digital assets and method thereof | |
| US20140109089A1 (en) | System to rebuild difference virtual hard disk for updating operation system and method thereof | |
| US10824642B2 (en) | Data synchronization architecture | |
| US20170235558A1 (en) | System and method for recapture and rebuild of application definition from installed instance | |
| JP2007080167A (en) | Software resource distribution system and method, and program | |
| CN106325909A (en) | Method and system for updating multiple images in private cloud system | |
| EP2874059A1 (en) | Personal cloud storage chain service system and method | |
| US20220150121A1 (en) | Provisioning resources for a datacenter on a cloud platform based on a platform independent declarative specification | |
| US10909487B2 (en) | Workflow customization | |
| US20180004767A1 (en) | REST APIs for Data Services | |
| US11886551B2 (en) | Systems and methods for asset management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C53 | Correction of patent for invention or patent application | ||
| CB02 | Change of applicant information |
Address after: 518040, No. 6, building 7, two software park, hi tech Zone, Guangdong, Shenzhen Applicant after: TELEWAVE INFORMATION TECHNOLOGY CO., LTD. Address before: 518057, No. 6, building 7, two software park, hi tech Zone, Guangdong, Shenzhen Applicant before: Shenzhen Telewave Communication Technology Co., Ltd. |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: APPLICANT; FROM: SHENZHEN TELEWAVE COMMUNICATION TECHNOLOGY CO., LTD. TO: TELEWAVE INFORMATION CO., LTD. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20151118 Termination date: 20171225 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |