CN103259672A - Software upgrading method and software upgrading system - Google Patents
Software upgrading method and software upgrading system Download PDFInfo
- Publication number
- CN103259672A CN103259672A CN2012100380162A CN201210038016A CN103259672A CN 103259672 A CN103259672 A CN 103259672A CN 2012100380162 A CN2012100380162 A CN 2012100380162A CN 201210038016 A CN201210038016 A CN 201210038016A CN 103259672 A CN103259672 A CN 103259672A
- Authority
- CN
- China
- Prior art keywords
- client
- version
- control server
- flow
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (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)
Abstract
The invention discloses a software upgrading method and a software upgrading system. The software upgrading method includes the following steps: a version control server generates an increment upgrading file list according to version information of an upgradable version of a client terminal and version information of an original version of the client terminal; the version control server sends the increment upgrading file list to the client terminal; a flow control server receives a downloading flow request message sent by the client terminal, wherein the downloading flow request information carries flow needed in downloading upgrading files in the increment upgrading file list by the client terminal; the flow control server judges whether required flow can be distributed nor not, and if the required flow can be distributed, a file server transmits the upgrading files in the increment upgrading file list to the client terminal. The software upgrading method and the software upgrading system solve the problems that in the prior art, when the client terminal upgrades software in a centralizing mode, downloading flow needed by the software upgrading system is overlarge so that a downloading request can not be effectively dealt with, and therefore a resource utilization rate and upgrading capacity of the software system are improved.
Description
Technical field
The application relates to internet arena, in particular to a kind of method for upgrading software and system.
Background technology
Instant communication software is used more and more widely, and at present, the software updating control method of main flow mainly contains following several:
1) client is obtained the latest version information of software from server, then with self the software version of installed software compare, if the version of the software that obtains from server is newer than the version of self mounted software, then client is upgraded this software.
2) server determines according to IP or client's scope of client whether this client can upgrade, and has only when the IP address of this client or client's scope satisfy the condition of setting and just the software of this client is upgraded.
3) listed files of the upgrade file that provides according to server of client, listed files contrast with this locality, the listed files that generate to need the file of change carries out selectivity according to the listed files of the file of the needs change that generates from server then and downloads and cover.
Yet all there is certain problem in three kinds of above-mentioned method for upgrading software:
When 1) carrying out software upgrading by method 1, when redaction of server issue, there is a large amount of users simultaneously this redaction to be downloaded probably, causes the download pressure of server excessive, improved the probability of upgrading failed download.
When 2) carrying out software upgrading by method 2, though user's download scope has been carried out control to a certain degree, alleviated the download pressure of server, but still can't avoid the generation of the problems referred to above, and the means that scope is downloaded in the control of adopting this mode to carry out software upgrading are more single, can't satisfy the tangible problem of instant communication users heap sort.
When 3) carrying out software upgrading by method 3, mainly be to lay particular emphasis on to reduce the flow that the user downloads, can alleviate load of server in certain program, yet, server all compares listed files at every turn, and when number of files was too much, efficient was also lower.
Yet, above-mentioned three kinds of upgrade methods all can't solve in the prior art effectively when client concentrates the required downloading flow of software update system when software upgraded excessive and cause the problem that can't effectively handle download request, also can't distinguish customer group and carry out different edition upgradings.
Summary of the invention
The application's main purpose is to provide a kind of method for upgrading software and system, concentrates the required downloading flow of software update system when software upgraded excessive and cause the problem that can't effectively handle download request to solve at least in the prior art when client.
An aspect according to the application provides a kind of method for upgrading software, comprising: version control server generates the tabulation of increment upgrade file according to the version information of the source version of the version information of the scalable version of client and client; Version control server sends to client with the tabulation of increment upgrade file; Flow control server receives the downloading flow request message that client sends, and wherein, carries the required flow of upgrade file in the tabulation of client downloads increment upgrade file in the downloading flow request message; Flow control server judges whether to distribute required flow; If can distribute required flow, then file server is transferred to client with the upgrade file in the tabulation of increment upgrade file.
Preferably, flow control server judges whether can distribute after the required flow, and method for upgrading software also comprises: if can not distribute required flow, then flow control server sends request failure message to client.
Preferably, flow control server judges whether to distribute the step of required flow to comprise: flow control server judges whether the quantity of current client of upgrading reaches the maximum N that system allows the quantity of the client downloaded simultaneously
Max=W/V
0, wherein, W represents the bandwidth of file server; V
0The download limits speed of representing each connection; If do not reach, then flow control server is judged and can be distributed required flow; Otherwise flow control server is judged and can not be distributed required flow.
Preferably, after client sent request failure message, method for upgrading software also comprised at flow control server:
Client sends the downloading flow request message every the scheduled time to flow control server after receiving request failure message, the upgrade file in receiving the increment upgrade file tabulation that file server sends.
Preferably, before version control server generated the tabulation of increment upgrade file according to the version information of the source version of the version information of the scalable version of client and client, method for upgrading software also comprises: version control server obtained the client-side information of client; Version control server is determined the scalable version of client according to client-side information.
Preferably, version control server determines that according to client-side information the step of the scalable version of client comprises: version control server selects to be applicable to the strategy of client from predefined strategy according to client-side information, wherein, the strategy number of users that comprises open update time and/or allow to upgrade simultaneously; Version control server is determined target version type and the version number corresponding with client-side information according to the strategy selected, and with determined target version type and version number as scalable version.
Preferably, version control server comprises according to the step that the version information of the source version of the version information of the scalable version of client and client generates the tabulation of increment upgrade file: version control server is determined the client type of client according to the client-side information of client; Version control server is selected the upgrade file tabulation corresponding to client type from the version information of scalable version; Version control server compares with the upgrade file tabulation selected with corresponding to the source file tabulation of the version information of source version, and the fileinfo except source file is tabulated in the upgrade file tabulation is tabulated as the increment upgrade file.
According to the application on the other hand, a kind of software update system is provided, comprise: version control server, flow control server and file server, wherein, version control server comprises: generation unit is used for generating the tabulation of increment upgrade file according to the version information of the source version of the version information of the scalable version of client and client; First transmitting element is used for the tabulation of increment upgrade file is sent to client; Flow control server comprises: receiving element, be used for receiving the downloading flow request message that client sends, and wherein, carry the required flow of upgrade file in the tabulation of client downloads increment upgrade file in the downloading flow request message; Judging unit is used for judging whether to distribute required flow; File server comprises: transmission unit, be used for going out to distribute required flow when judgment unit judges, and the upgrade file in the tabulation of increment upgrade file is transferred to client.
Preferably, flow control server also comprises: second transmitting element is used for sending request failure message to client when judgment unit judges goes out to distribute required flow.
Preferably, judging unit comprises: whether judge module, the quantity that is used for judging current client of upgrading reach the maximum N that system allows the quantity of the client downloaded simultaneously
Max=W/V
0, wherein, W represents the bandwidth of file server;
0The download limits speed of representing each connection; If do not reach, then flow control server is judged and can be distributed required flow; Otherwise flow control server is judged and can not be distributed required flow.
Preferably, generation unit comprises: determination module, for the client type of determining client according to the client-side information of client; Select module, be used for selecting to tabulate corresponding to the upgrade file of client type from the version information of scalable version; Generation module is used for the upgrade file tabulation that will select and compares corresponding to the source file tabulation of the version information of source version, and the fileinfo except source file is tabulated in the upgrade file tabulation is tabulated as the increment upgrade file.
Technical scheme by the application, having increased the downloading control module judges that server is current and whether can provide enough downloading flow to client, only when judging the flow that can provide enough, software update system just carries out software upgrading to client, thereby concentrate the required downloading flow of software update system when software upgraded excessive and cause the problem that effectively to handle download request when client in the solution prior art, improve resource utilization and the upgrading ability of software systems.Further, version control server adopts incremental form to generate the client required listed files of upgrading, and has reduced the flow of user end to server request, thereby has reduced the transmission burden of server.
Description of drawings
Accompanying drawing described herein is used to provide the further understanding to the application, constitutes the application's a part, and the application's illustrative examples and explanation thereof are used for explaining the application, do not constitute the improper restriction to the application.In the accompanying drawings:
Fig. 1 is a kind of structural representation according to the software update system of the embodiment of the present application;
Fig. 2 is a kind of preferred structure block diagram according to the software update system of the embodiment of the present application;
Fig. 3 is the another kind of preferred structure block diagram according to the software update system of the embodiment of the present application;
Fig. 4 is another the preferred structure block diagram according to the software update system of the embodiment of the present application;
Fig. 5 is another the preferred structure block diagram according to the software update system of the embodiment of the present application;
Fig. 6 is a kind of preferred flow charts according to the method for upgrading software of the embodiment of the present application;
Fig. 7 is the another kind of preferred flow charts according to the method for upgrading software of the embodiment of the present application;
Fig. 8 is another preferred flow charts according to the method for upgrading software of the embodiment of the present application;
Fig. 9 is another preferred flow charts according to the method for upgrading software of the embodiment of the present application;
Figure 10 is another preferred flow charts according to the method for upgrading software of the embodiment of the present application;
Figure 11 is another preferred flow charts according to the method for upgrading software of the embodiment of the present application.
Embodiment
Hereinafter will describe the application with reference to the accompanying drawings and in conjunction with the embodiments in detail.Need to prove that under the situation of not conflicting, embodiment and the feature among the embodiment among the application can make up mutually.
Before the further details of each embodiment that describes the application, a suitable counting system structure of the principle that can be used for realizing the application will be described with reference to Figure 1.In the following description, except as otherwise noted, otherwise each embodiment of the application will be described with reference to the symbolic representation of the action of being carried out by one or more computers and operation.Thus, be appreciated that this class action and the operation that are called as the computer execution sometimes comprise that the processing unit of computer is to representing the manipulation of the signal of telecommunication of data with structured form.This manipulation transforms data or the position in the accumulator system of computer safeguard it, the operation of computer is reshuffled or changed to this mode of all understanding with those skilled in the art.The data structure of service data is the physical location of memory with defined particular community of form of data.Yet although describe the application in above-mentioned context, it does not also mean that restrictively, and as understood by those skilled in the art, the each side of hereinafter described action and operation also available hardware realizes.
Turn to accompanying drawing, wherein identical reference number refers to identical element, and the application's principle is regarded as realizing in a suitable computing environment.Below describe the embodiment based on described the application, and should not think to limit the application about the alternative embodiment clearly do not described herein.
Fig. 1 shows the schematic diagram of an example computer architecture that can be used for these equipment.For purposes of illustration, the architecture of painting only is an example of proper environment, is not that the scope of application or function to the application proposes any limitation.This computing system should be interpreted as that arbitrary assembly shown in Figure 1 or its combination are had any dependence or demand yet.
The application's principle can use other universal or special calculating or communication environment or configuration to operate.The example that is applicable to the application's well-known computing system, environment and configuration includes but not limited to, personal computer, server, multicomputer system, the system based on little processing, minicomputer, mainframe computer and the distributed computing environment (DCE) that comprises arbitrary said system or equipment.
In its most basic configuration, software update system 100 among Fig. 1 comprises at least: version control server 102, flow control server 104 and file server 106, each server in this software update system links to each other with one or more clients (instant communication client) 108, and being used for provides software upgrade service to instant communication client.These servers can include but not limited to microprocessor MCU or programmable logic device FPGA etc. processing unit, be used for the storage data storage device and with the transmitting device of client communication; Client 108 can comprise: microprocessor MCU, with the transmitting device of server communication, with the display unit of user interactions.In the present specification and claims, " system " also can be defined as can executive software, firmware or microcode realize any nextport hardware component NextPort of function or the combination of nextport hardware component NextPort.Software update system 100 even can be distributed is to realize distributed function.
As used in this application, term " module ", " assembly " or " unit " can refer to software object or the routine in software update system 100 execution.Different assembly described herein, module, unit, engine and service can be implemented as object or the process of carrying out (for example, as independent thread) at software update system 100.Although system and method described herein realizes with software that preferably the realization of the combination of hardware or software and hardware also may and be conceived.
Embodiment 1
Based on software update system shown in Figure 1, Fig. 2 is a kind of preferred construction schematic diagram according to the embodiment of the present application software update system:
1) version control server 202 comprises: generation unit 2022 is used for generating the tabulation of increment upgrade file according to the version information of the source version of the version information of the scalable version of client 208 and client 208; First transmitting element 2024 is used for the tabulation of increment upgrade file is sent to client; For example, the existing mounted source of client version is 2.1 versions, version control server provides up-to-date upgraded version 2.2, version control server is according to generating 2.2 versions with respect to the increment upgrade file tabulation of 2.1 versions based on the version information of 2.1 versions and the version information of 2.2 versions, just the version information to 2.1 versions and 2.2 versions compares, with the file spanned file tabulation that has in 2.2 versions and do not have in 2.1 versions.
2) flow control server 204 comprises: receiving element 2042, be used for receiving the downloading flow request message that client 208 sends, and wherein, carry the required flow of upgrade file in the tabulation of client downloads increment upgrade file in the downloading flow request message; Judging unit 2044 is used for judging whether to distribute required flow; For example, client is the required flows to the server request of 2.2 versions receiving 2.1 edition upgradings of calculating self increment upgrade file tabulation back, and the flow value that obtains is sent to flow control server.
3) file server 206 comprises: transmission unit 2062, be used for going out to distribute required flow when judgment unit judges, and the upgrade file in the tabulation of increment upgrade file is transferred to client 208.For example, flow control server is receiving after 2.1 edition upgradings with client that client sends over become the required flow information of 2.2 versions, judge whether to provide to this client and satisfy 2.1 edition upgradings to the required flow of 2.2 versions, can provide at flow control server under the situation of enough flow, file server can send to the user from 2.1 edition upgradings to the required file of 2.2 versions with client, so that the user can carry out the upgrading of software.
In above-mentioned preferred implementation, having increased the downloading control module judges that server is current and whether can provide enough downloading flow to client, only when judging the flow that can provide enough, software update system just carries out software upgrading to client, thereby concentrate the required downloading flow of software update system when software upgraded excessive and cause the problem that effectively to handle download request when client in the solution prior art, improve resource utilization and the upgrading ability of software systems.Further, version control server adopts incremental form to generate the client required listed files of upgrading, and has reduced the flow of user end to server request, thereby has reduced the transmission burden of server.
Preferably, version control server 202 sends to client with the tabulation of increment upgrade file with the form of XML file, carries the storage address of file in this increment upgrade file tabulation and the MD5 value of file correspondence in this XML file.
In preferred implementation of the application, as shown in Figure 3, flow control server 204 also comprises: second transmitting element 2046 is used for sending request failure message to client when judgment unit judges goes out to distribute required flow.
In preferred implementation of the application, as shown in Figure 4, judging unit 2044 comprises: whether judge module 402, the quantity that is used for judging current client of upgrading reach the maximum N that system allows the quantity of the client downloaded simultaneously
Max=W/V
0, wherein, W represents the bandwidth of file server; V
0The download limits speed of representing each connection; If do not reach, then flow control server is judged and can be distributed required flow; Otherwise flow control server is judged and can not be distributed required flow.For example, the bandwidth of file server is 10000M, it is 1M that each client is downloaded required speed, then show and to support 10000 clients to download simultaneously, flow control server is when receiving the download request of client, whether the number of judging the current client of downloading reaches 10000, if current have 9000 clients downloading, then allowing to carry out file to the client that current request is downloaded downloads, if current have 10000 clients to download, then judging at this moment, file server can't send required file to the client that current request is downloaded.
In above-mentioned preferred implementation, the download limits speed that the bandwidth of flow control server by file server is connected with each determines that system allows the maximum of the quantity of the client downloaded simultaneously, when the flow request that receives client, whether the number of judging the client of upgrading in the ban earlier reaches maximum, thereby determine whether current system can distribute enough flows to this client, and the algorithm of this implementation is simple, efficient and real-time is good.Realized by the way under situation about not influencing processing time of the upgrade request of client, can controlling the downloading flow of file server well.
In preferred implementation of the application, client also is used for after the request failure message that receives flow control server 204 transmissions, send the downloading flow request message every the scheduled time to flow control server 204, the upgrade file in receiving the increment upgrade file tabulation that file server 206 sends.For example, client is after receiving request failure message, the 5 fens clockwise flow control servers in every interval send a flow request message, suppose after repeating to send 3 request messages, this client has been received upgrade file, shows that then this client is to have obtained required upgrade file after 15 minutes.
In above-mentioned preferred implementation, client is after receiving request failure message, can continue the transmitted traffic request message, up to the upgrade file of receiving that file server sends, thereby guaranteed that each user who asks upgrading and satisfied upgrading to require can upgrade to software, has reached the equilibrium distribution to the downloading flow of file server.
In preferred implementation of the application, version control server 202 also was used for before the version information according to the source version of the version information of the scalable version of client and client generates the tabulation of increment upgrade file, generated the scalable version that obtains the client-side information of client before the tabulation of increment upgrade file and determine client according to client-side information according to the version information of the source version of the version information of the scalable version of client and client.Preferably, client-side information mainly be exactly in this client corresponding to the relevant information of this software, these relevant informations include but not limited to following one of at least: the request IP of user account number, source version number, source software type and client, user account number type and user account number grade.In above-mentioned preferred implementation, version control server is determined the scalable version of this client according to client-side information, thereby can realize the flexible control to software upgrading according to dissimilar definite different upgraded versions of different clients.
In preferred implementation of the application, version control server 202 also is used for selecting to be applicable to the strategy of client according to client-side information from predefined strategy, wherein, and the number of users that strategy comprises open update time and/or allows to upgrade simultaneously; Version control server is determined target version type and the version number corresponding with client-side information according to the strategy selected, and determined target version type and version number is determined the scalable version of client as scalable version.In above-mentioned preferred implementation, the different escalation policys that version control server is set have the number of users that open update time and same time upgrades in these strategies, and then determine upgraded version corresponding to this client according to concrete strategy.
For example, can determine different update time according to the number of the account grade of client, the more high more long update time of grade correspondence, for example, grade is that 1 opening update time is that late 6:00 upgrades to late 6:00 to late 12:00 to late 10:00, grade 2 openings, thereby realized determining different escalation policys according to different user client information, improved the flexibility that system upgrades to software.
In preferred implementation of the application, as shown in Figure 5, generation unit 2022 comprises: determination module 502, for the client type of determining client according to the client-side information of client; Select module 504, be used for selecting to tabulate corresponding to the upgrade file of client type from the version information of scalable version; Generation module 506 is used for the upgrade file tabulation that will select and compares corresponding to the source file tabulation of the version information of source version, and the fileinfo except source file is tabulated in the upgrade file tabulation is tabulated as the increment upgrade file.
In above-mentioned preferred implementation, the application can be according to user's identity or the current definite upgrade file tabulations such as type of client software, be that example describes with the e-commerce field, client can be buyer's identity or seller's identity, can carry out buyer and seller's differentiation to client by the application, if the corresponding buyer's identity of this client, then from the upgraded version of determining, select to compare corresponding to the upgrade file of realizing buyer's function and the source file of source version, thereby generate the increment upgrade file tabulation with the buyer client coupling, realized distinguishing the problem that customer group is carried out specific upgrade, also upgrade with regard to being equivalent to just client to be carried out the file relevant with self, can't be by distinguishing the problem that different user groups carries out different upgradings in the prior art thereby solved, further reduce the burden of file server downloading flow, improved upgrade speed of software and efficient.
Embodiment 2
On the basis of the software update system of Fig. 2-shown in Figure 5, the application provides a kind of preferred method for upgrading software.As shown in Figure 6, this method can comprise the steps:
S602: version control server generates the tabulation of increment upgrade file according to the version information of the source version of the version information of the scalable version of client and client; For example, the existing mounted source of client version is 2.1 versions, version control server provides up-to-date upgraded version 2.2, version control server is according to generating 2.2 versions with respect to the increment upgrade file tabulation of 2.1 versions based on the version information of 2.1 versions and the version information of 2.2 versions, just the version information to 2.1 versions and 2.2 versions compares, with the file spanned file tabulation that has in 2.2 versions and do not have in 2.1 versions.
S604: version control server sends to client with the tabulation of increment upgrade file;
S606: flow control server receives the downloading flow request message that client sends, and wherein, carries the required flow of upgrade file in the tabulation of client downloads increment upgrade file in the downloading flow request message; For example, client is the required flows to the server request of 2.2 versions receiving 2.1 edition upgradings of calculating self increment upgrade file tabulation back, and the flow value that obtains is sent to flow control server.
S608: flow control server judges whether to distribute required flow;
S610: if can distribute required flow, then file server is transferred to client with the upgrade file in the tabulation of increment upgrade file; For example, flow control server is receiving after 2.1 edition upgradings with client that client sends over become the required flow information of 2.2 versions, judge whether to provide to this client and satisfy 2.1 edition upgradings to the required flow of 2.2 versions, can provide at flow control server under the situation of enough flow, file server can send to the user from 2.1 edition upgradings to the required file of 2.2 versions with client, so that the user can carry out the upgrading of software.
S612: if can not distribute required flow, then flow control server sends request failure message to client.
In above-mentioned preferred implementation, having increased the downloading control module judges that server is current and whether can provide enough downloading flow to client, only when judging the flow that can provide enough, software update system just carries out software upgrading to client, thereby concentrate the required downloading flow of software update system when software upgraded excessive and cause the problem that effectively to handle download request when client in the solution prior art, improve resource utilization and the upgrading ability of software systems.Further, version control server adopts incremental form to generate the client required listed files of upgrading, and has reduced the flow of user end to server request, thereby has reduced the transmission burden of server.
Preferably, version control server sends to client with the tabulation of increment upgrade file with the form of XML file, carries the storage address of file in this increment upgrade file tabulation and the MD5 value of file correspondence in this XML file.
In preferred implementation of the application, flow control server judges whether to distribute the step of required flow to comprise: flow control server judges whether the quantity of current client of upgrading reaches the maximum N that system allows the quantity of the client downloaded simultaneously
Max=W/V
0, wherein, W represents the bandwidth of file server; V
0The download limits speed of representing each connection; If do not reach, then flow control server is judged and can be distributed required flow; Otherwise flow control server is judged and can not be distributed required flow.For example, the bandwidth of file server is 10000M, it is 1M that each client is downloaded required speed, then show and to support 10000 clients to download simultaneously, flow control server is when receiving the download request of client, whether the number of judging the current client of downloading reaches 10000, if current have 9000 clients downloading, then allowing to carry out file to the client that current request is downloaded downloads, if current have 10000 clients to download, then judging at this moment, file server can't send required file to the client that current request is downloaded.
In above-mentioned preferred implementation, the download limits speed that the bandwidth of flow control server by file server is connected with each determines that system allows the maximum of the quantity of the client downloaded simultaneously, when the flow request that receives client, whether the number of judging the client of upgrading in the ban earlier reaches maximum, thereby determine whether current system can distribute enough flows to this client, and the algorithm of this implementation is simple, efficient and real-time is good.Realized by the way under situation about not influencing processing time of the upgrade request of client, can controlling the downloading flow of file server well.
In preferred implementation of the application, at flow control server after client sends request failure message, method for upgrading software also comprises: client is after receiving request failure message, send the downloading flow request message every the scheduled time to flow control server, the upgrade file in receiving the increment upgrade file tabulation that file server sends.For example, client is after receiving request failure message, the 5 fens clockwise flow control servers in every interval send a flow request message, suppose after repeating to send 3 request messages, this client has been received upgrade file, shows that then this client is to have obtained required upgrade file after 15 minutes.
In above-mentioned preferred implementation, client is after receiving request failure message, can continue the transmitted traffic request message, up to the upgrade file of receiving that file server sends, thereby guaranteed that each user who asks upgrading and satisfied upgrading to require can upgrade to software, has reached the equilibrium distribution to the downloading flow of file server.
In preferred implementation of the application, before version control server generated the tabulation of increment upgrade file according to the version information of the source version of the version information of the scalable version of client and client, method for upgrading software also comprises: version control server obtained the client-side information of client; Version control server is determined the scalable version of client according to client-side information.Preferably, client-side information mainly be exactly in this client corresponding to the relevant information of this software, these relevant informations include but not limited to following one of at least: the request IP of user account number, source version number, source software type and client, user account number type and user account number grade.In above-mentioned preferred implementation, version control server is determined the scalable version of this client according to client-side information, thereby can realize the flexible control to software upgrading according to dissimilar definite different upgraded versions of different clients.
In preferred implementation of the application, version control server determines that according to client-side information the step of the scalable version of client comprises: version control server selects to be applicable to the strategy of client from predefined strategy according to client-side information, wherein, the strategy number of users that comprises open update time and/or allow to upgrade simultaneously; Version control server is determined target version type and the version number corresponding with client-side information according to the strategy selected, and with determined target version type and version number as scalable version.In above-mentioned preferred implementation, the different escalation policys that version control server is set have the number of users that open update time and same time upgrades in these strategies, and then determine upgraded version corresponding to this client according to concrete strategy.
For example, can determine different update time according to the number of the account grade of client, the more high more long update time of grade correspondence, for example, grade is that 1 opening update time is that late 6:00 upgrades to late 6:00 to late 12:00 to late 10:00, grade 2 openings, thereby realized determining different escalation policys according to different user client information, improved the flexibility that system upgrades to software.
In preferred implementation of the application, as shown in Figure 7, version control server comprises according to the step that the version information of the source version of the version information of the scalable version of client and client generates the tabulation of increment upgrade file:
S702: version control server is determined the client type of client according to the client-side information of client;
S704: version control server is selected the upgrade file tabulation corresponding to client type from the version information of scalable version; For example, the client of current request upgrading is the buyer, then version control server with among the version 2 .2 corresponding to comparing corresponding to the required file of buyer among the required file of buyer and the version 2 .1, and generate the tabulation of increment upgrade file, the required file of seller among the version 2 .2 is not then processed.
S706: version control server compares with the upgrade file tabulation selected with corresponding to the source file tabulation of the version information of source version, and the fileinfo except source file is tabulated in the upgrade file tabulation is tabulated as the increment upgrade file.
In above-mentioned preferred implementation, the application can be according to user's identity or the current definite upgrade file tabulations such as type of client software, be that example describes with the e-commerce field, client can be buyer's identity or seller's identity, can carry out buyer and seller's differentiation to client by the application, if the corresponding buyer's identity of this client, then from the upgraded version of determining, select to compare corresponding to the upgrade file of realizing buyer's function and the source file of source version, thereby generate the increment upgrade file tabulation with the buyer client coupling, realized distinguishing the problem that customer group is carried out specific upgrade, also upgrade with regard to being equivalent to just client to be carried out the file relevant with self, further reduce the burden of file server downloading flow, improved upgrade speed of software and efficient.
In preferred implementation of the application, client can be carried out software upgrading by step as shown in Figure 8:
S802: whether client has upgradeable version to the version control server inquiry, if there is not available edition, then waits for inquiry next time; If have, then receive the increment upgrade file tabulation that version control server returns.For example, the existing mounted software of client is 2.2 versions, the latest edition that server can provide now also is 2.2 versions, then when client is inquired about scalable file to version control server, client will not receive the increment upgrade file, just show the current version that this client is upgraded that do not have to be fit to yet.
S804: filename and the corresponding MD5 value of file of each file that records the listed files of the XML form that client traversal sends over from version control server, compare with local file, if there is not this document in this locality, perhaps the MD5 value of listed file is different with the MD5 value of this document of local storage among the XML, then this document is added the change tabulation, thereby form a change file tabulation of downloading of needing, and calculate need be from the total flow of server data downloaded.
S806: client is to traffic server request flow, and till traffic server agreed that this client is carried out the file download, client was constantly downloaded All Files from file server, finishes up to download.
Client is carried out the upgrading of software by the way, has reduced the downloading flow of file, has reached the purpose of rationally utilizing the effective downloaded resources of server.
Embodiment 3
The application provides a kind of preferred embodiment to come further the application to be made an explanation, but it should be noted that the preferred embodiment just limits the application improperly in order better to describe the application, not constitute.
Based on software update system shown in Figure 1, the upgrading of finishing a software mainly needs version control server, flow control server, file server and four parts of client upgrading module, finishes upgrading to self software thereby client upgrading module conducts interviews to first three server successively.
To be that example is described in detail these four parts below with the software upgrading of instant communication client.
1) version control server
Version control server is the main step of carrying out as shown in Figure 9 in software upgrade process:
S902: version control server receives the upgrade request of client.
S904: user account number, source version number, source software type and request IP according to the instant communication client that obtains, search the escalation policy that meets this client from the strategy that sets in advance.Preferably, escalation policy may be set different open update time according to source version number, user account number type, user account number grade, IP etc., thus the each number of users of downloading of restriction.
S906: determine target version type and version number.
S908: determine the feature list that these client needs are upgraded according to the user account number type.
S910: generate the listed files of corresponding purpose version according to the feature list of determining, and compare with source release type and version number's corresponding file tabulation according to the listed files of purpose version, generate the increment upgrade file and tabulate.
S912: the storage address of the file in the increment upgrade file tabulation that generates and the MD5 value of file correspondence are generated the XML file, this document is returned to client.
2) flow control server
Flow control server is the main step of carrying out as shown in figure 10 in software upgrade process:
S1002: flow control server is after receiving the flow request message of client, according to the bandwidth W of file server, and the download limits speed V of each connection
0, each user's maximum downloading flow C
Max, calculate the maximum N that file server allows the quantity of the client downloaded simultaneously
Max=W/V
0, each user once downloads the maximum of T of required time
Max=C
Max/ V
0
S1004: flow control server generates the preposition formation L of initialization, and the length that this formation is set is T
Max, be initialized as this formation L[i]=0, wherein, the i item represents the number clients of finishing that i downloaded in the time of second.Simultaneously, the current download number of initialization N
Current=0, current time sheet T
Current=0, be T because each user downloads the maximum duration that needs
Max, therefore, every through T
MaxAfter second, expression last consignment of user has downloaded certainly and has finished, can be again from L[0] beginning label.Use L[0] represent T
MaxSecond, and L[1] represent T
Max+ 1 second, by that analogy.
S1006: flow control server is judged the current number N that is downloading after receiving client's flow download request (supposing that the flow that request is downloaded is C)
CurrentWhether less than N
MaxIf then carry out S1008; Otherwise then carry out S1010.
S1008: return the permission download message to client, calculate the needed time T=C/V of this client downloads
0, through T after second, the value of the preposition queue element (QE) of correspondence is added 1, i.e. L[(T
Current+ t) mod T
Max]=L[(T
Current+ t) mod T
Max]+1 was illustrated in through T after second, and downloading the number of finishing increases by 1, then carries out S1012.
S1010: return to client and not allow download message.
S1012: whenever through 1 second, current timeslice is added 1, i.e. T
Current=(T
Current+ 1) mod T
MaxAnd deduct in the current number and download the number clients of finishing, i.e. N
Current=N
Current-L[T
Current].
3) file server
File server is used for providing file to download to client after client is obtained the flow of flow control server distribution.
Based on software update system shown in Figure 1, can adopt flow process as shown in figure 11 that software is upgraded, step comprises:
S1102: instant communication client regularly sends to version control server with client-side information.
S1104: version server judges whether to be fit to the upgraded version of this client based on client-side information, and when judging suitable upgraded version, version control server produces the tabulation of increment upgrade file and this tabulation is sent to client.
S1106: client is after receiving the tabulation of increment upgrade file, the corresponding MD5 value of the filename of each file that records the listed files of the XML form that traversal sends over from version control server and file, compare with local file, if there is not this document in this locality, perhaps the MD5 value of listed file is different with the MD5 value of this document of local storage among the XML, then this document is added the change tabulation, thereby form a change file tabulation of downloading of needing, and calculate need be from the total flow of server data downloaded.
S1108: client is to the corresponding downloading flow of flow control server application.
S1110: flow control server, judges whether to be allocated successfully to the client dispense flow rate according to preposition algorithm, if distribute failure, then returns to client and does not allow download message, carries out S1112; Otherwise, then carry out S1114.
S1112: client is after certain time interval, then execution S1108, again to flow control server application downloading flow.
S1114: client is obtained the installation of upgrading of file the increment upgrade file tabulation from file server.
By above description as can be known, the application has following advantage:
1) the application takes all factors into consideration the user and lands ID, the client source version, multiple client-side information such as client ip, whether common this client software of decision has upgradeable version, under above-mentioned situation about taking all factors into consideration, added by the preposition algorithm of download, judge the current downloading control module that whether allows this client to upgrade, only when judging the flow that can provide enough, software update system just carries out software upgrading to client, thereby concentrate the required downloading flow of software update system when software upgraded excessive and cause the problem that effectively to handle download request when client in the solution prior art, improve resource utilization and the upgrading ability of software systems.
2) the application generates the tabulation of increment upgrade file according to user's source version information, can compare rapidly and verify thereby reach when client being upgraded at every turn.
3) the application is according to user's identity and the current type of client software, the content that decision need be upgraded, can't be by distinguishing the problem that different user groups carries out different upgradings in the prior art thereby solved, further reduce the burden of file server downloading flow, improved upgrade speed of software and efficient.
Obviously, those skilled in the art should be understood that, each module of above-mentioned the application or each step can realize with the general calculation device, they can concentrate on the single calculation element, perhaps be distributed on the network that a plurality of calculation elements form, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in the storage device and be carried out by calculation element, and in some cases, can carry out step shown or that describe with the order that is different from herein, perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the application is not restricted to any specific hardware and software combination.
The above is the application's preferred embodiment only, is not limited to the application, and for a person skilled in the art, the application can have various changes and variation.All within the application's spirit and principle, any modification of doing, be equal to replacement, improvement etc., all should be included within the application's the protection range.
Claims (11)
1. a method for upgrading software is characterized in that, comprising:
Version control server generates the tabulation of increment upgrade file according to the version information of the source version of the version information of the scalable version of client and described client;
Described version control server sends to described client with described increment upgrade file tabulation;
Flow control server receives the downloading flow request message that described client sends, and wherein, carries the required flow of upgrade file in the described increment upgrade file tabulation of described client downloads in the described downloading flow request message;
Described flow control server judges whether to distribute described required flow;
If can distribute described required flow, then file server is transferred to described client with the upgrade file in the described increment upgrade file tabulation.
2. method according to claim 1 is characterized in that, described flow control server judges whether to distribute after the described required flow, also comprises:
If can not distribute described required flow, then described flow control server sends request failure message to described client.
3. method according to claim 1 is characterized in that, described flow control server judges whether to distribute the step of described required flow to comprise:
Described flow control server judges whether the quantity of current client of upgrading reaches the maximum N that system allows the quantity of the client downloaded simultaneously
Max=W/V
0, wherein, W represents the bandwidth of file server; V
0The download limits speed of representing each connection;
If do not reach, then described flow control server is judged and can be distributed described required flow; Otherwise described flow control server is judged and can not be distributed described required flow.
4. method according to claim 2 is characterized in that,, also comprises after described client sends request failure message at described flow control server:
Described client sends the downloading flow request message every the scheduled time to described flow control server after receiving the described request failed message, the upgrade file in receiving the described increment upgrade file tabulation that described file server sends.
5. method according to claim 1 is characterized in that, before described version control server generates the tabulation of increment upgrade file according to the version information of the source version of the version information of the scalable version of client and described client, also comprises:
Described version control server obtains the client-side information of described client;
Described version control server is determined the scalable version of described client according to described client-side information.
6. method according to claim 5 is characterized in that, described version control server determines that according to described client-side information the step of the scalable version of described client comprises:
Described version control server selects to be applicable to the strategy of described client according to client-side information from predefined strategy, wherein, and the number of users that described strategy comprises open update time and/or allows to upgrade simultaneously;
Described version control server is determined target version type and the version number corresponding with described client-side information according to the strategy of selecting, and with determined target version type and version number as scalable version.
7. according to each described method in the claim 1 to 6, it is characterized in that described version control server comprises according to the step that the version information of the source version of the version information of the scalable version of client and described client generates the tabulation of increment upgrade file:
Described version control server is determined the client type of described client according to the client-side information of described client;
Described version control server is selected the upgrade file tabulation corresponding to described client type from the version information of described scalable version;
The described upgrade file tabulation that described version control server will be selected and compare corresponding to the source file tabulation of the version information of described source version is tabulated the fileinfo except described source file is tabulated in the described upgrade file tabulation as described increment upgrade file.
8. a software update system is characterized in that, comprising: version control server, flow control server and file server, wherein,
Described version control server comprises:
Generation unit is used for generating the tabulation of increment upgrade file according to the version information of the source version of the version information of the scalable version of client and described client;
First transmitting element is used for described increment upgrade file tabulation is sent to described client;
Described flow control server comprises:
Receiving element is used for receiving the downloading flow request message that described client sends, and wherein, carries the required flow of upgrade file in the described increment upgrade file tabulation of described client downloads in the described downloading flow request message;
Judging unit is used for judging whether to distribute described required flow;
Described file server comprises:
Transmission unit is used for going out to distribute described required flow when judgment unit judges, and the upgrade file in the described increment upgrade file tabulation is transferred to described client.
9. system according to claim 8 is characterized in that, described flow control server also comprises:
Second transmitting element is used for when judgment unit judges goes out to distribute described required flow, to described client transmission request failure message.
10. system according to claim 9 is characterized in that, described judging unit comprises:
Whether judge module, the quantity that is used for judging current client of upgrading reach the maximum N that system allows the quantity of the client downloaded simultaneously
Max=W/V
0, wherein, W represents the bandwidth of file server; V
0The download limits speed of representing each connection; If do not reach, then described flow control server is judged and can be distributed described required flow; Otherwise described flow control server is judged and can not be distributed described required flow.
11. each described system in 10 according to Claim 8 is characterized in that described generation unit comprises:
Determination module is for the client type of determining described client according to the client-side information of described client;
Select module, be used for selecting to tabulate corresponding to the upgrade file of described client type from the version information of described scalable version;
Generation module, be used for the described upgrade file tabulation that to select and compare corresponding to the source file tabulation of the version information of described source version, the fileinfo except described source file is tabulated in the described upgrade file tabulation is tabulated as described increment upgrade file.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610973767.1A CN107104814B (en) | 2012-02-17 | 2012-02-17 | Software upgrading method and system |
| CN201210038016.2A CN103259672B (en) | 2012-02-17 | 2012-02-17 | Method for upgrading software and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210038016.2A CN103259672B (en) | 2012-02-17 | 2012-02-17 | Method for upgrading software and system |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610973767.1A Division CN107104814B (en) | 2012-02-17 | 2012-02-17 | Software upgrading method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103259672A true CN103259672A (en) | 2013-08-21 |
| CN103259672B CN103259672B (en) | 2016-09-28 |
Family
ID=48963389
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610973767.1A Active CN107104814B (en) | 2012-02-17 | 2012-02-17 | Software upgrading method and system |
| CN201210038016.2A Active CN103259672B (en) | 2012-02-17 | 2012-02-17 | Method for upgrading software and system |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610973767.1A Active CN107104814B (en) | 2012-02-17 | 2012-02-17 | Software upgrading method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN107104814B (en) |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103455359A (en) * | 2013-09-22 | 2013-12-18 | 金蝶软件（中国）有限公司 | Method, device and system for patch installation |
| CN103605505A (en) * | 2013-10-11 | 2014-02-26 | 索尔思光电（成都）有限公司 | Sharing method of software configuration files |
| CN103685495A (en) * | 2013-12-05 | 2014-03-26 | 金蝶软件（中国）有限公司 | Method and system for upgrading software |
| CN104753826A (en) * | 2015-03-31 | 2015-07-01 | 天脉聚源（北京）教育科技有限公司 | Bandwidth allocation method and device |
| CN105323106A (en) * | 2014-08-04 | 2016-02-10 | 中兴通讯股份有限公司 | Software upgrade management method, equipment and system |
| CN105357308A (en) * | 2015-11-18 | 2016-02-24 | 天脉聚源(北京)传媒科技有限公司 | Data downloading method and apparatus |
| CN105487894A (en) * | 2015-11-27 | 2016-04-13 | 浪潮软件集团有限公司 | Remote updating method of distributed software system |
| CN105681073A (en) * | 2015-12-25 | 2016-06-15 | 北京奇虎科技有限公司 | Application program updating method and device |
| CN106487852A (en) * | 2015-08-31 | 2017-03-08 | 阿里巴巴集团控股有限公司 | Realize the synchronous method of client file, device, terminal unit and system |
| CN106886433A (en) * | 2015-12-16 | 2017-06-23 | 阿里巴巴集团控股有限公司 | The update method and device of client software |
| CN109766131A (en) * | 2017-11-06 | 2019-05-17 | 上海宝信软件股份有限公司 | The system and method for the intelligent automatic upgrading of software is realized based on multithreading |
| CN110336862A (en) * | 2019-06-19 | 2019-10-15 | 上海二三四五网络科技有限公司 | The method for upgrading system of batch Intelligent hardware |
| CN111427595A (en) * | 2019-09-03 | 2020-07-17 | 杭州海康威视数字技术股份有限公司 | Client upgrading method, device and system |
| CN112286541A (en) * | 2020-11-03 | 2021-01-29 | 浪潮云信息技术股份公司 | File distribution method |
| WO2021135301A1 (en) * | 2019-12-30 | 2021-07-08 | 深圳Tcl新技术有限公司 | Application upgrade method and computer device |
| CN114237681A (en) * | 2021-12-16 | 2022-03-25 | 拟仁智能科技(杭州)有限公司 | File differential upgrading method and system based on reverse differential logic |
| CN114666397A (en) * | 2022-01-29 | 2022-06-24 | 北京北信源软件股份有限公司 | Client version updating method and system |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107562439A (en) * | 2017-09-29 | 2018-01-09 | 河南职业技术学院 | Computer based firmware upgrade method and device for upgrading firmware |
| CN108599997A (en) * | 2018-04-04 | 2018-09-28 | 北京奇艺世纪科技有限公司 | Upgrade control method and device |
| CN108777632B (en) * | 2018-05-18 | 2022-02-25 | 创新先进技术有限公司 | Data processing method, client, service platform and configuration platform |
| CN111343217B (en) * | 2018-12-18 | 2023-04-07 | 阿里巴巴集团控股有限公司 | Resource data downloading method and device, terminal equipment and computer storage medium |
| CN111381857A (en) * | 2018-12-27 | 2020-07-07 | 北京骑胜科技有限公司 | Firmware upgrading method and device, electronic equipment and storage medium |
| CN110764807B (en) | 2019-10-29 | 2021-10-29 | 京东方科技集团股份有限公司 | Upgrading method, system, server and terminal equipment |
| CN111679854B (en) * | 2020-06-15 | 2024-01-23 | 中国银行股份有限公司 | Version control method, device and system of software product |
| CN113190262B (en) * | 2021-04-16 | 2024-05-10 | 华强方特(深圳)软件有限公司 | Cloud-based distributed software version management and control system and control method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1645931A1 (en) * | 2004-10-11 | 2006-04-12 | Telefonaktiebolaget LM Ericsson (publ) | Secure loading and storing of data in a data processing device |
| CN101753524A (en) * | 2008-12-15 | 2010-06-23 | 青岛海信传媒网络技术有限公司 | Method and system for upgrading software |
| CN102081536A (en) * | 2010-12-30 | 2011-06-01 | 华为终端有限公司 | Method for updating increment, and server |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100479372C (en) * | 2003-06-22 | 2009-04-15 | 华为技术有限公司 | Method of automatic software update for terminal equipment |
| CN100527080C (en) * | 2004-08-14 | 2009-08-12 | 艾利森电话股份有限公司 | Method for software program synchronization |
| CN100505640C (en) * | 2006-01-26 | 2009-06-24 | 腾讯科技（深圳）有限公司 | A method and system for software upgrade |
| CN101110788B (en) * | 2006-07-20 | 2010-09-08 | 阿里巴巴集团控股有限公司 | Method and system for updating client software |
| CN101035016A (en) * | 2007-02-08 | 2007-09-12 | 中兴通讯股份有限公司 | Terminal equipment configuration system and method |
| CN100514943C (en) * | 2007-05-24 | 2009-07-15 | 中国联合网络通信集团有限公司 | An upgrade management method and system for instant message client |
| CN101119517B (en) * | 2007-07-12 | 2010-11-10 | 深圳市融创天下科技发展有限公司 | Method of automatic downloading software from network server |
| CN101227335A (en) * | 2008-01-25 | 2008-07-23 | 中兴通讯股份有限公司 | Method for upgrading software version of network cell device |
| US10656931B2 (en) * | 2009-05-26 | 2020-05-19 | Comcast Cable Communications, Llc | Network event triggered software updates |
| CN102036224B (en) * | 2009-09-29 | 2013-09-18 | 中国移动通信集团设计院有限公司 | Method, system and upgrading control entity for informing mobile equipment of upgrading software |
| CN102045321B (en) * | 2009-10-23 | 2014-06-04 | 阿里巴巴集团控股有限公司 | Flow control method and system for software downloading |
| CN101848230A (en) * | 2010-01-27 | 2010-09-29 | 宇龙计算机通信科技(深圳)有限公司 | Method for pushing application program and application program server |
-
2012
- 2012-02-17 CN CN201610973767.1A patent/CN107104814B/en active Active
- 2012-02-17 CN CN201210038016.2A patent/CN103259672B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1645931A1 (en) * | 2004-10-11 | 2006-04-12 | Telefonaktiebolaget LM Ericsson (publ) | Secure loading and storing of data in a data processing device |
| CN101753524A (en) * | 2008-12-15 | 2010-06-23 | 青岛海信传媒网络技术有限公司 | Method and system for upgrading software |
| CN102081536A (en) * | 2010-12-30 | 2011-06-01 | 华为终端有限公司 | Method for updating increment, and server |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103455359A (en) * | 2013-09-22 | 2013-12-18 | 金蝶软件（中国）有限公司 | Method, device and system for patch installation |
| CN103605505A (en) * | 2013-10-11 | 2014-02-26 | 索尔思光电（成都）有限公司 | Sharing method of software configuration files |
| CN103685495A (en) * | 2013-12-05 | 2014-03-26 | 金蝶软件（中国）有限公司 | Method and system for upgrading software |
| CN103685495B (en) * | 2013-12-05 | 2019-08-16 | 金蝶软件（中国）有限公司 | The upgrade method and system of software |
| CN105323106A (en) * | 2014-08-04 | 2016-02-10 | 中兴通讯股份有限公司 | Software upgrade management method, equipment and system |
| WO2016019725A1 (en) * | 2014-08-04 | 2016-02-11 | 中兴通讯股份有限公司 | Software upgrade management method, device, system and computer storage medium |
| CN104753826A (en) * | 2015-03-31 | 2015-07-01 | 天脉聚源（北京）教育科技有限公司 | Bandwidth allocation method and device |
| CN106487852A (en) * | 2015-08-31 | 2017-03-08 | 阿里巴巴集团控股有限公司 | Realize the synchronous method of client file, device, terminal unit and system |
| CN105357308B (en) * | 2015-11-18 | 2018-05-08 | 天脉聚源(北京)传媒科技有限公司 | A kind of data download method and device |
| CN105357308A (en) * | 2015-11-18 | 2016-02-24 | 天脉聚源(北京)传媒科技有限公司 | Data downloading method and apparatus |
| CN105487894A (en) * | 2015-11-27 | 2016-04-13 | 浪潮软件集团有限公司 | Remote updating method of distributed software system |
| CN106886433A (en) * | 2015-12-16 | 2017-06-23 | 阿里巴巴集团控股有限公司 | The update method and device of client software |
| CN105681073A (en) * | 2015-12-25 | 2016-06-15 | 北京奇虎科技有限公司 | Application program updating method and device |
| CN109766131A (en) * | 2017-11-06 | 2019-05-17 | 上海宝信软件股份有限公司 | The system and method for the intelligent automatic upgrading of software is realized based on multithreading |
| CN110336862A (en) * | 2019-06-19 | 2019-10-15 | 上海二三四五网络科技有限公司 | The method for upgrading system of batch Intelligent hardware |
| CN111427595A (en) * | 2019-09-03 | 2020-07-17 | 杭州海康威视数字技术股份有限公司 | Client upgrading method, device and system |
| CN111427595B (en) * | 2019-09-03 | 2024-03-05 | 杭州海康威视数字技术股份有限公司 | Client upgrading method, device and system |
| WO2021135301A1 (en) * | 2019-12-30 | 2021-07-08 | 深圳Tcl新技术有限公司 | Application upgrade method and computer device |
| CN113127021A (en) * | 2019-12-30 | 2021-07-16 | 深圳Tcl新技术有限公司 | Application upgrading method and computer equipment |
| CN112286541A (en) * | 2020-11-03 | 2021-01-29 | 浪潮云信息技术股份公司 | File distribution method |
| CN114237681A (en) * | 2021-12-16 | 2022-03-25 | 拟仁智能科技(杭州)有限公司 | File differential upgrading method and system based on reverse differential logic |
| CN114666397A (en) * | 2022-01-29 | 2022-06-24 | 北京北信源软件股份有限公司 | Client version updating method and system |
| CN114666397B (en) * | 2022-01-29 | 2024-07-23 | 北京北信源软件股份有限公司 | Client version updating method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107104814B (en) | 2021-07-06 |
| CN103259672B (en) | 2016-09-28 |
| CN107104814A (en) | 2017-08-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103259672A (en) | Software upgrading method and software upgrading system | |
| CN108173774B (en) | Client upgrading method and system | |
| US8381216B2 (en) | Dynamic thread pool management | |
| CN106663030B (en) | Scalable failover communication in distributed clusters | |
| CN112165691B (en) | Content delivery network scheduling method, device, server and medium | |
| US20110138396A1 (en) | Method and system for data distribution in high performance computing cluster | |
| KR101817437B1 (en) | Method and apparatus for controlling data transmission | |
| WO2018123030A1 (en) | Priority control method and data processing system | |
| CN103679392A (en) | Task scheduling processing method and system | |
| CN113127168A (en) | Service distribution method, system, device, server and medium | |
| KR101033813B1 (en) | Cloud computing network system and file distrubuting method of the same | |
| CN104125294A (en) | Method and system for big data safety management | |
| WO2006050349A2 (en) | Methods and apparatus for running applications on computer grids | |
| US9535758B2 (en) | Managing data distribution to networked client computing devices | |
| US20070050447A1 (en) | Method and device arrangement for managing a client/server environment | |
| CN112860421B (en) | Method, apparatus and computer program product for job processing | |
| CN106657195B (en) | Task processing method and relay device | |
| CN107045452B (en) | Virtual machine scheduling method and device | |
| CN102597957B (en) | System deployment determination system, system deployment determination method and program | |
| CN111858012A (en) | Task scheduling method, device, equipment and medium | |
| US20190109886A1 (en) | Selected data exchange | |
| CN102200928A (en) | Computation resource control apparatus, computation resource control method, and non-transitory computer-readable recording medium | |
| EP2711836B1 (en) | Data distribution system | |
| CN116319960A (en) | Service release method, device, computer equipment and storage medium | |
| WO2021237221A1 (en) | Machine learning based application sizing engine for intelligent infrastructure orchestration |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1184610 Country of ref document: HK |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: GR Ref document number: 1184610 Country of ref document: HK |