CN105528205A - Update control method and update control system - Google Patents
Update control method and update control system Download PDFInfo
- Publication number
- CN105528205A CN105528205A CN201510857174.4A CN201510857174A CN105528205A CN 105528205 A CN105528205 A CN 105528205A CN 201510857174 A CN201510857174 A CN 201510857174A CN 105528205 A CN105528205 A CN 105528205A
- Authority
- CN
- China
- Prior art keywords
- client
- version
- enterprise servers
- control law
- described client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The present invention provides an update control method and an update control system. The update control method comprises the steps of obtaining a compatibility control rule of an enterprise server connected with a client from a public server; and determining whether the client and/or the enterprise server are required to be updated or not according to the compatibility control rule of the enterprise server. Through the technical scheme of the present invention, the problem that the client and the enterprise server cannot be compatible due to the fact that updates of the client and the enterprise server are not synchronous is solved, functional redundancy introduced for ensuring compatibility and maintenance cost are reduced, and enterprise users can be guided to correctly update versions of the client and/or the enterprise server according to self disposition conditions so as to ensure normal operation of systems.
Description
Technical field
The present invention relates to field of computer technology, in particular to one more new control method and a kind of renewal control system.
Background technology
Based in the application architecture of internet, service end is deployed on public service end usually, and be responsible for upgrading and safeguarding by application service provider, client is supplied to the public and downloads and installs, and is upgraded by final user.In this application scenarios, as shown in Figure 1, the corresponding relation of public service end and client normally one-to-many, namely provide service by a public service end, the client of all different editions all connects this public service end.In this system architecture, the renewal of client and public service end is compatible, usually adopts the mode of redundancy, and namely public service end keeps the compatibility to multiple client release, by same public service end by different service channels, provide service to the client of multiple different editions simultaneously.Meanwhile, by pushing the channels such as prompting or application market, user is guided client to be updated to latest edition, with complete compatible public service end function.
In this framework, for the function difference that each functional development iteration produces, can define different interfaces at public service end, such as, certain is applied in first version and achieves order interface, conducted interviews by specific service, in later release, because the change of order function logic, the client of redaction will enable new logic, corresponding service can be carried out expanding to support new client release, and namely service end comprises the functional redundancy of multiple version to support the client of different editions.Wherein, http://api.xxxx.com/order is first version of order placement service interface, for early stage client release provides service, http://api.xxxx.com/order/v2 is second version of order placement service, for the redaction client after changing logic provides service.
Along with the increase of user's actual needs, in enterprise-oriented internet, applications product, service end is deployed in corporate environment usually, and different enterprises is mutually isolated between disposing.As shown in Figure 2, typical pattern is: the product common policy server of software vendor provides the installation procedure of enterprise servers and client and upgrades patch, enterprise A and enterprise B are deployed with oneself enterprise servers respectively, both are different versions, are obtained and renewal client from the common policy server of software vendor by the user of enterprise A and enterprise B.
But, for enterprise's application architecture of this complexity, the deployment of enterprise servers and client and more new capital are determined by user and control, as the provider of product, although software vendor provides the renewal of product, but the Product Status cannot grasped in enterprise's applied environment, also mandatory requirement user cannot upgrade client and enterprise servers at special time.If user have updated client by application market, and enterprise servers are not yet updated to latest edition, now, upgrade if client has what's new to rely on enterprise servers, by causing, the what's new of client is unavailable, and client may be caused time serious abnormal.Otherwise, if enterprise servers upgrade and client does not upgrade time, if the function logic of enterprise servers has changed, unavailable or error in data of client etc. will have been caused.
Therefore need a kind of new technical scheme, can solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem.
Summary of the invention
The present invention, just based on the problems referred to above, proposes a kind of new technical scheme, can solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem.
In view of this, an aspect of of the present present invention proposes one more new control method, comprising: the compatible control law obtaining the enterprise servers be connected with client from public server; According to the described compatible control law of described enterprise servers, determine whether to need to upgrade described client and/or described enterprise servers.
In this technical scheme, user can in client to the compatible control law for issuing the public server acquisition enterprise servers upgraded for client and enterprise servers, thus the version determining client whether with the edition compatibility of enterprise servers, to determine whether further to need to upgrade client and/or enterprise servers.By this technical scheme, especially for client and the enterprise servers of complicated deployment scenario, solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem, reduce as ensureing the functional redundancy that compatibility is quoted and maintenance cost, enterprise customer can be guided correctly to upgrade the version of client and/or enterprise servers according to self deployment scenario, to ensure the normal operation of system.
In technique scheme, preferably, described from public server, obtain the compatible control law of the enterprise servers be connected with client before, also comprise: the service end version number obtaining described enterprise servers from described enterprise servers, in described public server, inquire about compatible control law corresponding to described service end version number for according to described service end version number.
In this technical scheme, client needs the service end version number obtained from enterprise servers, thus inquire about in public server according to this service end version number, the compatible control law that these enterprise servers are corresponding can be obtained, to determine that the client release that enterprise servers are corresponding is interval further by compatible control law.
In above-mentioned arbitrary technical scheme, preferably, the described compatible control law obtaining the enterprise servers be connected with client from public server, specifically comprise: with described service end version number for parameter call policy service interface, to send Rule request by described policy service interface to described public server; And the described compatible control law corresponding with described service end version number received from described public server.
In this technical scheme, client can pass through service end version number regulative strategy service interface, by this policy service interface to compatible control law corresponding to public server acquisition request service end version number.By this technical scheme, make client can obtain the compatible control law of the enterprise servers that it connects expediently, thus be convenient to the version correctly upgrading client and/or enterprise servers according to this compatible control law further according to self deployment scenario.
In addition, authentication function can also be had in public server side, if verify that this client does not obtain the authority of the compatible control law of its enterprise servers of asking or do not upgrade authority, then forbid that public server provides compatible control law to client, only when verifying that this client has corresponding authority, corresponding compatible control law could be provided to client.
In above-mentioned arbitrary technical scheme, preferably, the described described compatible control law according to described enterprise servers, determine whether to need to upgrade described client and/or described enterprise servers, comprise: according to described compatible control law, determine that the client release that described enterprise servers are supported is interval; Obtain the current version of described client, whether belong to described client release with the current version detecting described client interval.
In this technical scheme, according to the compatible control law of enterprise servers, the various client releases that enterprise servers are supported can be determined, namely client release is interval, now, need the version obtaining client self again, and then it is interval to determine whether the version of client self belongs to this client release, to determine according to testing result the renewal how correctly controlling client and/or enterprise servers.
In above-mentioned arbitrary technical scheme, preferably, also comprising: when the current version of described client being detected lower than minimum version in described client release interval, upgrading described client or prompting upgrades described client; When detecting that the current version of described client is more than or equal to the minimum version in described client release interval, and when being less than the most highest version in described client release interval, whether prompting upgrades described client, uses described current version for renewal client or continuation; When the most top version number that the current version of described client equals in described client release interval being detected, determine not need to upgrade described client; When the most top version number that the current version of described client is greater than in described client release interval being detected, whether prompting upgrades the version of described enterprise servers or whether carries out version degradation to described client.
In this technical scheme, if the current version of client is lower than the minimum version in client release interval, illustrates that the current version of client and enterprise servers cannot be compatible, normally cannot use, directly can upgrade or point out user manually to upgrade.If the current version of client is more than or equal to this minimum version, and when being less than the most highest version in client release interval, illustrate that the version of client and enterprise servers can be compatible, user both can upgrade the version of client, also can retain use current version.If when the current version of client equals most highest version, illustrate that the version of client and enterprise servers can be compatible, without the need to upgrading.If when the current version of client is higher than this most highest version, illustrate that the version of enterprise servers cannot provide normal service for the current version of client, both can not be compatible, therefore the version of the version of enterprise servers of can upgrading or reduction client is to make both compatible.By this technical scheme, solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem, reduce as ensureing the functional redundancy that compatibility is quoted and maintenance cost, enterprise customer can be guided correctly to upgrade the version of client and/or enterprise servers according to self deployment scenario, to ensure the normal operation of system.
Another aspect of the present invention proposes a kind of renewal control system, comprising: Rule unit, obtains the compatible control law of the enterprise servers be connected with client from public server; Upgrade control module, according to the described compatible control law of described enterprise servers, determine whether to need to upgrade described client and/or described enterprise servers.
In this technical scheme, user can in client to the compatible control law for issuing the public server acquisition enterprise servers upgraded for client and enterprise servers, thus the version determining client whether with the edition compatibility of enterprise servers, to determine whether further to need to upgrade client and/or enterprise servers.By this technical scheme, especially for client and the enterprise servers of complicated deployment scenario, solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem, reduce as ensureing the functional redundancy that compatibility is quoted and maintenance cost, enterprise customer can be guided correctly to upgrade the version of client and/or enterprise servers according to self deployment scenario, to ensure the normal operation of system.
In above-mentioned arbitrary technical scheme, preferably, also comprise: version number's acquiring unit, described from public server, obtain the compatible control law of the enterprise servers be connected with client before, obtain the service end version number of described enterprise servers from described enterprise servers, in described public server, inquire about compatible control law corresponding to described service end version number for according to described service end version number.
In this technical scheme, client needs the service end version number obtained from enterprise servers, thus inquire about in public server according to this service end version number, the compatible control law that these enterprise servers are corresponding can be obtained, to determine that the client release that enterprise servers are corresponding is interval further by compatible control law.
In above-mentioned arbitrary technical scheme, preferably, described Rule unit specifically comprises: interface interchange unit, with described service end version number for parameter call policy service interface, to send Rule request by described policy service interface to described public server; And receiving element, receive the described compatible control law corresponding with described service end version number from described public server.
In this technical scheme, client can pass through service end version number regulative strategy service interface, by this policy service interface to compatible control law corresponding to public server acquisition request service end version number.By this technical scheme, make client can obtain the compatible control law of the enterprise servers that it connects expediently, thus be convenient to the version correctly upgrading client and/or enterprise servers according to this compatible control law further according to self deployment scenario.
In addition, authentication function can also be had in public server side, if verify that this client does not obtain the authority of the compatible control law of its enterprise servers of asking or do not upgrade authority, then forbid that public server provides compatible control law to client, only when verifying that this client has corresponding authority, corresponding compatible control law could be provided to client.
In above-mentioned arbitrary technical scheme, preferably, described renewal control module comprises: interval determination unit, according to described compatible control law, determines that the client release that described enterprise servers are supported is interval; Client release acquiring unit, obtains the current version of described client, whether belongs to described client release interval with the current version detecting described client.
In this technical scheme, according to the compatible control law of enterprise servers, the various client releases that enterprise servers are supported can be determined, namely client release is interval, now, need the version obtaining client self again, and then it is interval to determine whether the version of client self belongs to this client release, to determine according to testing result the renewal how correctly controlling client and/or enterprise servers.
In above-mentioned arbitrary technical scheme, preferably, described renewal control module comprises: first controls subelement, when the current version of described client being detected lower than minimum version in described client release interval, upgrades described client or prompting upgrades described client; Second controls subelement, when detecting that the current version of described client is more than or equal to the minimum version in described client release interval, and when being less than the most highest version in described client release interval, whether prompting upgrades described client, uses described current version for renewal client or continuation; 3rd controls subelement, when the most top version number that the current version of described client equals in described client release interval being detected, determines not need to upgrade described client; 4th controls subelement, and when the most top version number that the current version of described client is greater than in described client release interval being detected, whether prompting upgrades the version of described enterprise servers or whether carry out version degradation to described client.
In this technical scheme, if the current version of client is lower than the minimum version in client release interval, illustrates that the current version of client and enterprise servers cannot be compatible, normally cannot use, directly can upgrade or point out user manually to upgrade.If the current version of client is more than or equal to this minimum version, and when being less than the most highest version in client release interval, illustrate that the version of client and enterprise servers can be compatible, user both can upgrade the version of client, also can retain use current version.If when the current version of client equals most highest version, illustrate that the version of client and enterprise servers can be compatible, without the need to upgrading.If when the current version of client is higher than this most highest version, illustrate that the version of enterprise servers cannot provide normal service for the current version of client, both can not be compatible, therefore the version of the version of enterprise servers of can upgrading or reduction client is to make both compatible.By this technical scheme, solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem, reduce as ensureing the functional redundancy that compatibility is quoted and maintenance cost, enterprise customer can be guided correctly to upgrade the version of client and/or enterprise servers according to self deployment scenario, to ensure the normal operation of system.
By above technical scheme, solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem, reduce as ensureing the functional redundancy that compatibility is quoted and maintenance cost, enterprise customer can be guided correctly to upgrade the version of client and/or enterprise servers according to self deployment scenario, to ensure the normal operation of system.
Accompanying drawing explanation
Fig. 1 shows the structural drawing that the different client release in correlation technique is connected with public service end;
The structural drawing that Fig. 2 shows the client in correlation technique, different enterprise server versions is connected with product common policy server;
Fig. 3 shows the process flow diagram of more new control method according to an embodiment of the invention;
Fig. 4 shows the block diagram of renewal control system according to an embodiment of the invention;
Fig. 5 shows the block diagram of renewal control system according to another embodiment of the invention;
Fig. 6 shows the mutual schematic diagram of client according to an embodiment of the invention, service end and public product update server.
Embodiment
In order to more clearly understand above-mentioned purpose of the present invention, feature and advantage, below in conjunction with the drawings and specific embodiments, the present invention is further described in detail.It should be noted that, when not conflicting, the feature in the embodiment of the application and embodiment can combine mutually.
Set forth a lot of detail in the following description so that fully understand the present invention; but; the present invention can also adopt other to be different from other modes described here and implement, and therefore, protection scope of the present invention is not by the restriction of following public specific embodiment.
Fig. 3 shows the process flow diagram of more new control method according to an embodiment of the invention.
As shown in Figure 3, more new control method according to an embodiment of the invention, comprising:
Step 302, obtains the compatible control law of the enterprise servers be connected with client from public server;
Step 304, according to the described compatible control law of described enterprise servers, determines whether to need to upgrade described client and/or described enterprise servers.
In this technical scheme, user can in client to the compatible control law for issuing the public server acquisition enterprise servers upgraded for client and enterprise servers, thus the version determining client whether with the edition compatibility of enterprise servers, to determine whether further to need to upgrade client and/or enterprise servers.By this technical scheme, especially for client and the enterprise servers of complicated deployment scenario, solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem, reduce as ensureing the functional redundancy that compatibility is quoted and maintenance cost, enterprise customer can be guided correctly to upgrade the version of client and/or enterprise servers according to self deployment scenario, to ensure the normal operation of system.
In technique scheme, preferably, before step 302, also comprise: the service end version number obtaining described enterprise servers from described enterprise servers, in described public server, inquire about compatible control law corresponding to described service end version number for according to described service end version number.
In this technical scheme, client needs the service end version number obtained from enterprise servers, thus inquire about in public server according to this service end version number, the compatible control law that these enterprise servers are corresponding can be obtained, to determine that the client release that enterprise servers are corresponding is interval further by compatible control law.
In above-mentioned arbitrary technical scheme, preferably, step 302 specifically comprises: with described service end version number for parameter call policy service interface, to send Rule request by described policy service interface to described public server; And the described compatible control law corresponding with described service end version number received from described public server.
In this technical scheme, client can pass through service end version number regulative strategy service interface, by this policy service interface to compatible control law corresponding to public server acquisition request service end version number.By this technical scheme, make client can obtain the compatible control law of the enterprise servers that it connects expediently, thus be convenient to the version correctly upgrading client and/or enterprise servers according to this compatible control law further according to self deployment scenario.
In addition, authentication function can also be had in public server side, if verify that this client does not obtain the authority of the compatible control law of its enterprise servers of asking or do not upgrade authority, then forbid that public server provides compatible control law to client, only when verifying that this client has corresponding authority, corresponding compatible control law could be provided to client.
In above-mentioned arbitrary technical scheme, preferably, step 304 comprises: according to described compatible control law, determines that the client release that described enterprise servers are supported is interval; Obtain the current version of described client, whether belong to described client release with the current version detecting described client interval.
In this technical scheme, according to the compatible control law of enterprise servers, the various client releases that enterprise servers are supported can be determined, namely client release is interval, now, need the version obtaining client self again, and then it is interval to determine whether the version of client self belongs to this client release, to determine according to testing result the renewal how correctly controlling client and/or enterprise servers.
In above-mentioned arbitrary technical scheme, preferably, step 304 also comprises: when the current version of described client being detected lower than minimum version in described client release interval, upgrades described client or prompting upgrades described client; When detecting that the current version of described client is more than or equal to the minimum version in described client release interval, and when being less than the most highest version in described client release interval, whether prompting upgrades described client, uses described current version for renewal client or continuation; When the most top version number that the current version of described client equals in described client release interval being detected, determine not need to upgrade described client; When the most top version number that the current version of described client is greater than in described client release interval being detected, whether prompting upgrades the version of described enterprise servers or whether carries out version degradation to described client.
In this technical scheme, if the current version of client is lower than the minimum version in client release interval, illustrates that the current version of client and enterprise servers cannot be compatible, normally cannot use, directly can upgrade or point out user manually to upgrade.If the current version of client is more than or equal to this minimum version, and when being less than the most highest version in client release interval, illustrate that the version of client and enterprise servers can be compatible, user both can upgrade the version of client, also can retain use current version.If when the current version of client equals most highest version, illustrate that the version of client and enterprise servers can be compatible, without the need to upgrading.If when the current version of client is higher than this most highest version, illustrate that the version of enterprise servers cannot provide normal service for the current version of client, both can not be compatible, therefore the version of the version of enterprise servers of can upgrading or reduction client is to make both compatible.By this technical scheme, solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem, reduce as ensureing the functional redundancy that compatibility is quoted and maintenance cost, enterprise customer can be guided correctly to upgrade the version of client and/or enterprise servers according to self deployment scenario, to ensure the normal operation of system.
Fig. 4 shows the block diagram of renewal control system according to an embodiment of the invention.
As shown in Figure 4, renewal control system 400 according to an embodiment of the invention, comprise: Rule unit 402 and renewal control module 404, wherein, Rule unit 402 for obtaining the compatible control law of the enterprise servers be connected with client from public server; Upgrade control module 404 for the compatible control law according to enterprise servers, determine whether to need to upgrade client and/or enterprise servers.
In this technical scheme, user can in client to the compatible control law for issuing the public server acquisition enterprise servers upgraded for client and enterprise servers, thus the version determining client whether with the edition compatibility of enterprise servers, to determine whether further to need to upgrade client and/or enterprise servers.By this technical scheme, especially for client and the enterprise servers of complicated deployment scenario, solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem, reduce as ensureing the functional redundancy that compatibility is quoted and maintenance cost, enterprise customer can be guided correctly to upgrade the version of client and/or enterprise servers according to self deployment scenario, to ensure the normal operation of system.
In above-mentioned arbitrary technical scheme, preferably, also comprise: version number's acquiring unit 406, before the compatible control law obtaining the enterprise servers be connected with client from public server, the service end version number of enterprise servers is obtained, for according to the service end version number compatible control law that inquiry service end version number is corresponding in public server from enterprise servers.
In this technical scheme, client needs the service end version number obtained from enterprise servers, thus inquire about in public server according to this service end version number, the compatible control law that these enterprise servers are corresponding can be obtained, to determine that the client release that enterprise servers are corresponding is interval further by compatible control law.
In above-mentioned arbitrary technical scheme, preferably, Rule unit 402 specifically comprises: interface interchange unit 4022, with service end version number for parameter call policy service interface, to send Rule request by policy service interface to public server; And receiving element 4024, receive the compatible control law corresponding with service end version number from public server.
In this technical scheme, client can pass through service end version number regulative strategy service interface, by this policy service interface to compatible control law corresponding to public server acquisition request service end version number.By this technical scheme, make client can obtain the compatible control law of the enterprise servers that it connects expediently, thus be convenient to the version correctly upgrading client and/or enterprise servers according to this compatible control law further according to self deployment scenario.
In addition, authentication function can also be had in public server side, if verify that this client does not obtain the authority of the compatible control law of its enterprise servers of asking or do not upgrade authority, then forbid that public server provides compatible control law to client, only when verifying that this client has corresponding authority, corresponding compatible control law could be provided to client.
In above-mentioned arbitrary technical scheme, preferably, upgrade control module 404 and comprise: interval determination unit 4042, according to compatible control law, determine that the client release that enterprise servers are supported is interval; Client release acquiring unit 4044, obtains the current version of client, whether belongs to client release interval with the current version detecting client.
In this technical scheme, according to the compatible control law of enterprise servers, the various client releases that enterprise servers are supported can be determined, namely client release is interval, now, need the version obtaining client self again, and then it is interval to determine whether the version of client self belongs to this client release, to determine according to testing result the renewal how correctly controlling client and/or enterprise servers.
In above-mentioned arbitrary technical scheme, preferably, upgrading control module 404 and comprise: first controls subelement 4046, when the current version of client being detected lower than minimum version in client release interval, upgrading client or prompting upgrades client; Second controls subelement 4048, when detecting that the current version of client is more than or equal to the minimum version in client release interval, and when being less than the most highest version in client release interval, whether prompting upgrades client, for renewal client or continue to use current version; 3rd controls subelement 40410, when the most top version number that the current version of client equals in client release interval being detected, determines not need to upgrade client; 4th controls subelement 40412, and when the most top version number that the current version of client is greater than in client release interval being detected, whether prompting upgrades the version of enterprise servers or whether carry out version degradation to client.
In this technical scheme, if the current version of client is lower than the minimum version in client release interval, illustrates that the current version of client and enterprise servers cannot be compatible, normally cannot use, directly can upgrade or point out user manually to upgrade.If the current version of client is more than or equal to this minimum version, and when being less than the most highest version in client release interval, illustrate that the version of client and enterprise servers can be compatible, user both can upgrade the version of client, also can retain use current version.If when the current version of client equals most highest version, illustrate that the version of client and enterprise servers can be compatible, without the need to upgrading.If when the current version of client is higher than this most highest version, illustrate that the version of enterprise servers cannot provide normal service for the current version of client, both can not be compatible, therefore the version of the version of enterprise servers of can upgrading or reduction client is to make both compatible.By this technical scheme, solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem, reduce as ensureing the functional redundancy that compatibility is quoted and maintenance cost, enterprise customer can be guided correctly to upgrade the version of client and/or enterprise servers according to self deployment scenario, to ensure the normal operation of system.
Fig. 5 shows the block diagram of renewal control system according to another embodiment of the invention.
As shown in Figure 5, in renewal control system 500 according to another embodiment of the invention, client 506 can pass through policy lookup service interface 5026 query strategy rule storage unit 5024 by policy lookup logical block 5062 in common policy server 502, therefrom obtain the compatible control law of enterprise's privately owned server 504 correspondence, i.e. policing rule, wherein, common policy server 502 serves 5022 publishing policy rules by policy issue.
Wherein, client 506 in advance by the version number of the privately owned server of version querying service 5042 inquiry enterprise of the privately owned server of enterprise 504, then according to its version number, can inquire about corresponding compatible control law from common policy server 502.And then, can according to compatible control law, the various client releases that the privately owned server of enterprise 504 is supported can be determined, namely client release is interval, now, need the version obtaining client 506 self again, and then it is interval to determine whether the version of client 506 self belongs to this client release, to determine according to testing result the renewal how correctly controlling the privately owned server 504 of client 506 and/or enterprise.
Client 506 upgrades version alternately by version updating unit 5066 and the product version update service 5028 of common policy server 502, and the privately owned server 504 of enterprise upgrades version alternately by version updating control module 5044 and the product version update service 5028 of common policy server 502.
Fig. 6 shows the mutual schematic diagram of client according to an embodiment of the invention, service end and public product update server.
As shown in Figure 6, after startup client, comprising:
Step 602, inquiry service end version number.Service end described here, the i.e. privately owned server of enterprise.
Step 604, return service end version number.
Step 606, regulative strategy service interface obtains compatible control law.
Step 608, returns corresponding compatible control law.
Step 610, obtains client release.
Step 612, judges whether to meet the compatible control law of application, if the edition compatibility of client and service end, enters step 614, otherwise, enter step 616.
Step 614, connects and carries out business operation.
Step 616, upgrades version, namely upgrades the version of client or service end.
Specifically, first client initiates request to the privately owned server of the enterprise specified, and the version flag obtaining enterprise servers is S; Client uses version flag S as parameter, initiates request to public product update server, obtains the compatible control law that version flag S is corresponding, determines that the client release interval that version flag S supports is designated [L, H].
To the specific descriptions of client release interval mark be: represent service end version with S, C represents client release, H represents the highest client release that service end is supported, L represents the minimum client release that service end is supported, wherein, * represent any version, U represents the highest client release scheduler that this server version is supported.In practical application scene, version information is as shown in table 1 below.
Table 1
In addition, client uses active client version, is labeled as C, and contrast client release interval [L, H] is mated, and according to the steering logic shown in table 2, determines single stepping.
Table 2
Wherein, for the scene needing to upgrade, user can proceed as follows according to strategy matching result:
When needing to upgrade client, the product renewing returned by policy service on the mobile apparatus by enterprise customer is linked, and downloads and installs the installation program of client of adaptive enterprises service end version, installs after upgrading and can normally use;
When needing update service end, can be selected to demote with adaptive enterprises service end version to the product that my mobile device is installed by enterprise customer, or notify enterprise administrator at enterprise servers update service end product to enable redaction function.
More than be described with reference to the accompanying drawings technical scheme of the present invention, by technical scheme of the present invention, solve the renewal of client and enterprise servers asynchronous cause cannot be compatible problem, reduce as ensureing the functional redundancy that compatibility is quoted and maintenance cost, enterprise customer can be guided correctly to upgrade the version of client and/or enterprise servers according to self deployment scenario, to ensure the normal operation of system.
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 protection scope of the present invention.
Claims (10)
1. a more new control method, is characterized in that, comprising:
The compatible control law of the enterprise servers be connected with client is obtained from public server;
According to the described compatible control law of described enterprise servers, determine whether to need to upgrade described client and/or described enterprise servers.
2. more new control method according to claim 1, is characterized in that, described from public server, obtain the compatible control law of the enterprise servers be connected with client before, also comprise:
Obtain the service end version number of described enterprise servers from described enterprise servers, in described public server, inquire about compatible control law corresponding to described service end version number for according to described service end version number.
3. more new control method according to claim 2, is characterized in that, the described compatible control law obtaining the enterprise servers be connected with client from public server, specifically comprises:
With described service end version number for parameter call policy service interface, to send Rule request by described policy service interface to described public server; And
Receive the described compatible control law corresponding with described service end version number from described public server.
4. more new control method according to any one of claim 1 to 3, is characterized in that, the described described compatible control law according to described enterprise servers, and determining whether needs to upgrade described client and/or described enterprise servers, comprising:
According to described compatible control law, determine that the client release that described enterprise servers are supported is interval;
Obtain the current version of described client, whether belong to described client release with the current version detecting described client interval.
5. more new control method according to claim 4, is characterized in that, also comprise:
When the current version of described client being detected lower than minimum version in described client release interval, upgrade described client or prompting upgrades described client;
When detecting that the current version of described client is more than or equal to the minimum version in described client release interval, and when being less than the most highest version in described client release interval, whether prompting upgrades described client, uses described current version for renewal client or continuation;
When the most top version number that the current version of described client equals in described client release interval being detected, determine not need to upgrade described client;
When the most top version number that the current version of described client is greater than in described client release interval being detected, whether prompting upgrades the version of described enterprise servers or whether carries out version degradation to described client.
6. upgrade a control system, it is characterized in that, comprising:
Rule unit, obtains the compatible control law of the enterprise servers be connected with client from public server;
Upgrade control module, according to the described compatible control law of described enterprise servers, determine whether to need to upgrade described client and/or described enterprise servers.
7. renewal control system according to claim 6, is characterized in that, also comprise:
Version number's acquiring unit, described from public server, obtain the compatible control law of the enterprise servers be connected with client before, obtain the service end version number of described enterprise servers from described enterprise servers, in described public server, inquire about compatible control law corresponding to described service end version number for according to described service end version number.
8. renewal control system according to claim 7, is characterized in that, described Rule unit specifically comprises:
Interface interchange unit, with described service end version number for parameter call policy service interface, to send Rule request by described policy service interface to described public server; And
Receiving element, receives the described compatible control law corresponding with described service end version number from described public server.
9. the renewal control system according to any one of claim 6 to 8, is characterized in that, described renewal control module comprises:
Interval determination unit, according to described compatible control law, determines that the client release that described enterprise servers are supported is interval;
Client release acquiring unit, obtains the current version of described client, whether belongs to described client release interval with the current version detecting described client.
10. renewal control system according to claim 9, is characterized in that, described renewal control module comprises:
First controls subelement, when the current version of described client being detected lower than minimum version in described client release interval, upgrades described client or prompting upgrades described client;
Second controls subelement, when detecting that the current version of described client is more than or equal to the minimum version in described client release interval, and when being less than the most highest version in described client release interval, whether prompting upgrades described client, uses described current version for renewal client or continuation;
3rd controls subelement, when the most top version number that the current version of described client equals in described client release interval being detected, determines not need to upgrade described client;
4th controls subelement, and when the most top version number that the current version of described client is greater than in described client release interval being detected, whether prompting upgrades the version of described enterprise servers or whether carry out version degradation to described client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510857174.4A CN105528205A (en) | 2015-11-30 | 2015-11-30 | Update control method and update control system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510857174.4A CN105528205A (en) | 2015-11-30 | 2015-11-30 | Update control method and update control system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105528205A true CN105528205A (en) | 2016-04-27 |
Family
ID=55770454
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510857174.4A Pending CN105528205A (en) | 2015-11-30 | 2015-11-30 | Update control method and update control system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105528205A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106951283A (en) * | 2017-03-13 | 2017-07-14 | 广州视源电子科技股份有限公司 | It is a kind of that the system and method that PC ends carry out software upgrading is assisted using mobile terminal |
| CN107861739A (en) * | 2017-11-06 | 2018-03-30 | 山东浪潮通软信息科技有限公司 | ReactNative applications method of adjustment, client and system |
| CN107943503A (en) * | 2017-12-07 | 2018-04-20 | 畅捷通信息技术股份有限公司 | The upgrade method of mobile application and the upgrade-system of mobile application |
| CN108205527A (en) * | 2016-12-16 | 2018-06-26 | 深圳联友科技有限公司 | A kind of method for drafting and device of engine data balance |
| CN108989072A (en) * | 2017-06-05 | 2018-12-11 | 阿里巴巴集团控股有限公司 | It is a kind of deployment, management and invocation component method and device |
| CN110069303A (en) * | 2019-03-20 | 2019-07-30 | 厦门网宿有限公司 | A kind of screen layout's update method and server, electronic equipment and storage medium |
| CN111625257A (en) * | 2020-05-25 | 2020-09-04 | 泰康保险集团股份有限公司 | Service platform upgrading method, system, equipment and storage medium |
| CN112417402A (en) * | 2020-11-27 | 2021-02-26 | 亿企赢网络科技有限公司 | Authority control method, authority control device and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1690961A (en) * | 2004-04-30 | 2005-11-02 | 鸿富锦精密工业（深圳）有限公司 | Client program automatic updating system and method |
| CN101009589A (en) * | 2006-01-26 | 2007-08-01 | 腾讯科技（深圳）有限公司 | A method and system for software upgrade |
| CN101136770A (en) * | 2006-10-13 | 2008-03-05 | 中兴通讯股份有限公司 | Automatically updating method and apparatus for telecom multi-branch network management system |
| CN101770380A (en) * | 2009-01-05 | 2010-07-07 | 英业达集团(天津)电子技术有限公司 | Upgrade method for software of client in enterprise |
| CN101179424B (en) * | 2006-11-29 | 2010-09-08 | 腾讯科技（深圳）有限公司 | Method and system for updating network client terminal |
| CN102622246A (en) * | 2012-02-27 | 2012-08-01 | 神州数码国信信息技术（苏州）有限公司 | Automatic software upgrading method |
| CN103067484B (en) * | 2012-12-25 | 2015-11-18 | 天维尔信息科技股份有限公司 | A kind of method and system of auto-update application program |
-
2015
- 2015-11-30 CN CN201510857174.4A patent/CN105528205A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1690961A (en) * | 2004-04-30 | 2005-11-02 | 鸿富锦精密工业（深圳）有限公司 | Client program automatic updating system and method |
| CN101009589A (en) * | 2006-01-26 | 2007-08-01 | 腾讯科技（深圳）有限公司 | A method and system for software upgrade |
| CN101136770A (en) * | 2006-10-13 | 2008-03-05 | 中兴通讯股份有限公司 | Automatically updating method and apparatus for telecom multi-branch network management system |
| CN101179424B (en) * | 2006-11-29 | 2010-09-08 | 腾讯科技（深圳）有限公司 | Method and system for updating network client terminal |
| CN101770380A (en) * | 2009-01-05 | 2010-07-07 | 英业达集团(天津)电子技术有限公司 | Upgrade method for software of client in enterprise |
| CN102622246A (en) * | 2012-02-27 | 2012-08-01 | 神州数码国信信息技术（苏州）有限公司 | Automatic software upgrading method |
| CN103067484B (en) * | 2012-12-25 | 2015-11-18 | 天维尔信息科技股份有限公司 | A kind of method and system of auto-update application program |
Non-Patent Citations (1)
| Title |
|---|
| 张钟澍，编著；: "《微机软故障识别与应急处理 1995年11月第1版》", 30 November 1995, 成都科技大学出版社 * |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108205527A (en) * | 2016-12-16 | 2018-06-26 | 深圳联友科技有限公司 | A kind of method for drafting and device of engine data balance |
| CN108205527B (en) * | 2016-12-16 | 2022-01-18 | 深圳联友科技有限公司 | Drawing method and device for engine data balance |
| CN106951283A (en) * | 2017-03-13 | 2017-07-14 | 广州视源电子科技股份有限公司 | It is a kind of that the system and method that PC ends carry out software upgrading is assisted using mobile terminal |
| CN108989072A (en) * | 2017-06-05 | 2018-12-11 | 阿里巴巴集团控股有限公司 | It is a kind of deployment, management and invocation component method and device |
| CN108989072B (en) * | 2017-06-05 | 2021-08-24 | 创新先进技术有限公司 | Method and device for deploying, managing and calling assembly |
| CN107861739A (en) * | 2017-11-06 | 2018-03-30 | 山东浪潮通软信息科技有限公司 | ReactNative applications method of adjustment, client and system |
| CN107943503A (en) * | 2017-12-07 | 2018-04-20 | 畅捷通信息技术股份有限公司 | The upgrade method of mobile application and the upgrade-system of mobile application |
| CN110069303A (en) * | 2019-03-20 | 2019-07-30 | 厦门网宿有限公司 | A kind of screen layout's update method and server, electronic equipment and storage medium |
| CN111625257A (en) * | 2020-05-25 | 2020-09-04 | 泰康保险集团股份有限公司 | Service platform upgrading method, system, equipment and storage medium |
| CN111625257B (en) * | 2020-05-25 | 2023-05-23 | 泰康保险集团股份有限公司 | Service platform upgrading method, system, equipment and storage medium |
| CN112417402A (en) * | 2020-11-27 | 2021-02-26 | 亿企赢网络科技有限公司 | Authority control method, authority control device and storage medium |
| CN112417402B (en) * | 2020-11-27 | 2024-04-12 | 亿企赢网络科技有限公司 | Authority control method, authority control device, authority control equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105528205A (en) | Update control method and update control system | |
| CN108111331B (en) | Method, device, storage medium, processor and system for acquiring update data packet | |
| CN101313298B (en) | Method for facilitating and managing software application program subscription | |
| EP3043261B1 (en) | Software installation method, device and system | |
| CN102006334B (en) | Method, system and device for installing software component | |
| US7448034B2 (en) | Build time determination and installation of drivers on cloned systems | |
| US8463884B2 (en) | Synchronization of mobile device with application server | |
| JP4916432B2 (en) | Application programming interface for managing the distribution of software updates in an update distribution system | |
| US8139509B2 (en) | Installation and management of mobile device [{S]} configuration | |
| KR101676042B1 (en) | Method and system for deploying non-backward compatible server versions in a client/server computing environment | |
| US20070014243A1 (en) | System and method for provisioning a user device | |
| WO2010121273A2 (en) | Revocation of application on mobile device | |
| WO2004010249A2 (en) | System and method for utilizing profile information | |
| AU2007235540A1 (en) | Creating templates of offline resources | |
| MXPA05006621A (en) | System and method for updating installation components in a networked environment. | |
| JP5248657B2 (en) | System for registry-based automated installation and component handling on devices | |
| CN101557584A (en) | Method for realizing application authority control of mobile terminal and device | |
| CN109831338A (en) | Vehicle system upgrade method, cloud server and mobile terminal | |
| KR101201276B1 (en) | Method, software and apparatus for performing actions on a wireless device using action lists and versioning | |
| CN103906034A (en) | Mobile application providing method and mobile application providing server | |
| CN114467320A (en) | System, method and computer program for transferring Subscriber Identity Module (SIM) information for SIM card or ESIM activation | |
| US20170115979A1 (en) | Enforcement of updates for devices unassociated with a directory service | |
| JP2005228009A (en) | Version update method for communication oriented application program and its program | |
| CN107463390B (en) | Software upgrading method and upgrading server | |
| KR101638689B1 (en) | System and method for providing client terminal to user customized synchronization service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160427 |