CN104881454A - Updating method and system of parameter - Google Patents
Updating method and system of parameter Download PDFInfo
- Publication number
- CN104881454A CN104881454A CN201510257419.XA CN201510257419A CN104881454A CN 104881454 A CN104881454 A CN 104881454A CN 201510257419 A CN201510257419 A CN 201510257419A CN 104881454 A CN104881454 A CN 104881454A
- Authority
- CN
- China
- Prior art keywords
- parameter
- client
- service end
- version identifier
- database
- 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2308—Concurrency control
- G06F16/2315—Optimistic concurrency control
- G06F16/2329—Optimistic concurrency control using versioning
Abstract
The invention provides an updating method and system of a parameter. The method according to the embodiment of the invention comprises the following steps: determining the parameter in a database to update through a server, further transmitting parameter updating data to a client using the parameter to update the parameter stored by the client according to the parameter updating data by the client. Thus, since the parameter stored by the client is the parameter after updating of the parameter updating data immediately transmitted by the client after parameter updating in the database determined by the server and the is latest parameter in the database, the use of the parameter in the database by the client each time needs only to read the parameter stored by the client, reading operation is not required to be performed on the database; the problem of long acqusition time of the parameter caused by the need of performing the reading operation on the database during use of the parameter in the database each time in the prior art can be avoided, so that the parameter acqusition efficiency is improved.
Description
[technical field]
The present invention relates to database technical field, particularly relate to a kind of update method and system of parameter.
[background technology]
Database (Database) be organize according to data structure, the warehouse of store and management data, operated on it by database manipulation equipment, to realize the reading, renewal etc. of parameter.If there is the parameter that operation system needs in usage data storehouse, need to carry out read operation by database manipulation equipment to database, to obtain required parameter.Because the parameter in database is not changeless, but can often change, usually, in order to ensure the real-time that parameter upgrades, operation system, when needing the parameter in usage data storehouse, can carry out read operation by database manipulation equipment to data, to obtain up-to-date parameter.
But, because the parameter in each usage data storehouse of operation system all needs to carry out read operation to database, make the acquisition time of parameter longer, like this, result in the reduction of the efficiency of parameter acquiring.
[summary of the invention]
Many aspects of the present invention provide a kind of update method and system of parameter, in order to improve the efficiency of parameter acquiring.
An aspect of of the present present invention, provides a kind of update method of parameter, comprising:
Parameter in service end determination database upgrades;
Described service end sends parameter more new data to using the client of described parameter, to make described client according to described parameter more new data, to the parameter that described client stores, carries out update process.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further, and more new data packets draws together parameter information to described parameter, parameter upgrades instruction and parameter version identifier.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further, described method also comprises:
If the parameter version identifier that described parameter is more included in new data and the parameter version identifier that described client stores inconsistent, described client upgrades instruction according to described parameter, the parameter version identifier that the parameter information utilizing described parameter more included in new data and described parameter are more included in new data, the parameter version identifier that the parameter store described client and described client store, carries out update process.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further, and described service end comprises first service end equipment and at least one second service end equipment;
Parameter in described service end determination database upgrades, and comprising:
Described first service end equipment performs renewal rewards theory, to upgrade the parameter in described database to described database;
If the operating result of described renewal rewards theory is successfully, described first service end equipment determines that the parameter in described database upgrades;
Described service end sends parameter more new data to client, comprising:
Described first service end equipment instruction at least one second service end equipment described, sends described parameter more new data to described client.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further, described method also comprises:
Described client obtains the parameter version identifier described in described database corresponding to client from described service end;
If the parameter version identifier that the parameter version identifier described in described database corresponding to client and described client store is inconsistent, described client obtains from described service end whole parameters that client described in described database uses;
Described client utilizes the parameter version identifier described in described whole parameter and described database corresponding to client, the parameter version identifier that the parameter store described client and described client store, and carries out update process.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further, described method also comprises:
Described service end obtains the parameter version identifier described in described database corresponding to client;
If the parameter version identifier corresponding to described client that the parameter version identifier described in described database corresponding to client and described service end store is inconsistent, described service end obtains whole parameters that client described in described database uses;
Described service end utilizes the parameter version identifier described in described whole parameter and described database corresponding to client, whole parameter that the described client stored described service end uses and the parameter version identifier corresponding to described client that described service end stores, carry out update process.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further, and described client obtains the parameter version identifier described in described database corresponding to client from described service end, comprising:
Described service end receives the first acquisition request that described client sends, and described first obtains request for the parameter version identifier described in database described in acquisition request corresponding to client;
Parameter version identifier corresponding to the described client that described service end stores by described service end, sends to described client.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further, and described client obtains from described service end whole parameters that client described in described database uses, and comprising:
Described service end receives the second acquisition request that described client sends, and described second obtains request is used for whole parameters that described in acquisition request, described in database, client uses;
Whole parameters that the described client that described service end stores by described service end uses, send to described client.
Another aspect of the present invention, provides a kind of renewal system of parameter, comprising:
Service end, for determining that the parameter in database upgrades; And to using the client of described parameter to send parameter more new data;
Described client, for receiving the described parameter more new data that described service end sends; And according to described parameter more new data, to the parameter that described client stores, carry out update process.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further, and more new data packets draws together parameter information to described parameter, parameter upgrades instruction and parameter version identifier.
Aspect as above and arbitrary possible implementation, provide a kind of implementation, described client further, also for
If the parameter version identifier that described parameter is more included in new data and the parameter version identifier that described client stores inconsistent, instruction is upgraded according to described parameter, the parameter version identifier that the parameter information utilizing described parameter more included in new data and described parameter are more included in new data, the parameter version identifier that the parameter store described client and described client store, carries out update process.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further, and described service end specifically comprises first service end equipment and at least one second service end equipment;
Described first service end equipment, for performing renewal rewards theory, to upgrade the parameter in described database to described database; If the operating result of described renewal rewards theory is successfully, determine that the parameter in described database upgrades; And instruction at least one second service end equipment described, send described parameter more new data to described client;
Each second service end equipment at least one second service end equipment described, for the instruction according to described first service end equipment, sends described parameter more new data to described client.
Aspect as above and arbitrary possible implementation, provide a kind of implementation, described client further, also for
The parameter version identifier described in described database corresponding to client is obtained from described service end; If the parameter version identifier that the parameter version identifier described in described database corresponding to client and described client store is inconsistent, obtain from described service end whole parameters that client described in described database uses; And utilizing parameter version identifier described in described whole parameter and described database corresponding to client, the parameter version identifier that the parameter store described client and described client store, carries out update process.
Aspect as above and arbitrary possible implementation, provide a kind of implementation, described service end further, also for
Obtain the parameter version identifier described in described database corresponding to client; If the parameter version identifier corresponding to described client that the parameter version identifier described in described database corresponding to client and described service end store is inconsistent, obtain whole parameters that client described in described database uses; And utilize parameter version identifier described in described whole parameter and described database corresponding to client, whole parameter that the described client stored described service end uses and the parameter version identifier corresponding to described client that described service end stores, carry out update process.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further,
Described client, obtains request specifically for sending first to described service end, and described first acquisition request is used for the parameter version identifier described in acquisition request described in database corresponding to client; And the parameter version identifier corresponding to described client that the described service end receiving the transmission of described server stores;
Described service end, specifically for receiving described client described first obtains request; And the parameter version identifier corresponding to described client that described service end stored, send to described client.
Aspect as above and arbitrary possible implementation, provide a kind of implementation further,
Described client, obtains request specifically for sending second to described service end, and described second obtains request is used for whole parameters that described in acquisition request, described in database, client uses; And receive whole parameters that the described client that stores of described service end that described server sends uses;
Described service end, specifically for receiving described client described second obtains request; And whole parameters that the described client described service end to be stored uses, send to described client.
As shown from the above technical solution, the embodiment of the present invention is upgraded by the parameter in service end determination database, and then to using the client of described parameter to send parameter more new data, to make described client according to described parameter more new data, to the parameter that described client stores, carry out update process, like this, the parameter stored due to client be the parameter that sends immediately after client upgrades according to the parameter in service end determination database more new data carry out after update process parameter, it is parameter up-to-date in database, therefore, the parameter that parameter in each usage data storehouse of client only needs reading client to store, without the need to carrying out read operation to database, the parameter in prior art in each usage data storehouse can be avoided all to need to carry out read operation to database and the longer problem of the acquisition time of the parameter caused, thus improve the efficiency of parameter acquiring.
In addition, adopt technical scheme provided by the invention, after the parameter in service end determination database upgrades, immediately to using the client of described parameter to send parameter more new data, therefore, the described parameter that client can be made to store is updated in time, effectively can improve the real-time that parameter upgrades.
In addition, adopt technical scheme provided by the invention, due to the parameter that the parameter in each usage data storehouse of client only needs reading client to store, without the need to carrying out read operation to database, the phenomenon that database can be avoided to block occurs, thus reduces the pressure of database.
In addition, adopt technical scheme provided by the invention, by client from the parameter version identifier corresponding to client described in service end acquisition database, if the parameter version identifier that the parameter version identifier described in described database corresponding to client and described client store is inconsistent, described client obtains from described service end whole parameters that client described in described database uses, and then then can utilize parameter version identifier described in described whole parameter and described database corresponding to client, the parameter version identifier that the parameter store described client and described client store, carry out update process, the parameter stored due to client be whole parameters of obtaining from service end according to this client of client carry out after update process data, therefore, when service end sends parameter renewal data failure or client receiving parameter upgrades data failure, the parameter that client stores remains parameter up-to-date in database, effectively can improve the reliability of parameter acquiring.
[accompanying drawing explanation]
In order to be illustrated more clearly in the technical scheme in the embodiment of the present invention, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
The schematic flow sheet of the update method of the parameter that Fig. 1 provides for one embodiment of the invention;
The structural representation of the renewal system of the parameter that Fig. 2 provides for another embodiment of the present invention;
The structural representation of the renewal system of the parameter that Fig. 3 provides for another embodiment of the present invention.
[embodiment]
For making the object of the embodiment of the present invention, technical scheme and advantage clearly, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making other embodiments whole obtained under creative work prerequisite, belong to the scope of protection of the invention.
It should be noted that, terminal involved in the embodiment of the present invention can include but not limited to mobile phone, personal digital assistant (Personal Digital Assistant, PDA), radio hand-held equipment, panel computer (Tablet Computer), PC (Personal Computer, PC), MP3 player, MP4 player, wearable device (such as, intelligent glasses, intelligent watch, Intelligent bracelet etc.) etc.
In addition, term "and/or" herein, being only a kind of incidence relation describing affiliated partner, can there are three kinds of relations in expression, and such as, A and/or B, can represent: individualism A, exists A and B simultaneously, these three kinds of situations of individualism B.In addition, character "/" herein, general expression forward-backward correlation is to the relation liking a kind of "or".
The schematic flow sheet of the update method of the parameter that Fig. 1 provides for one embodiment of the invention, as shown in Figure 1.
101, the parameter in service end determination database upgrades.
It should be noted that, namely there is the quantity of the parameter upgraded in described parameter, can be one, or can also be several, the present embodiment be particularly limited this.
102, described service end sends parameter more new data to using the client of described parameter, to make described client according to described parameter more new data, to the parameter that described client stores, carries out update process.
This process, can be called that service end performs propelling movement task.
It should be noted that, the executive agent of 101 and 102 and service end, and other entities and client, can for being positioned at the application of local terminal, or can also for being arranged in plug-in unit or SDK (Software Development Kit) (the Software Development Kit of the application of local terminal, the functional unit such as SDK), or can also for being arranged in the processing engine of the server of network side, or can also for being positioned at the distributed system of network side, the present embodiment is not particularly limited this, and the present embodiment is not particularly limited this.
Be understandable that, described application can be mounted in the local program (nativeApp) in terminal, or can also be a web page program (webApp) of browser in terminal, and the present embodiment is not particularly limited this.
Like this, upgraded by the parameter in service end determination database, and then to using the client of described parameter to send parameter more new data, to make described client according to described parameter more new data, to the parameter that described client stores, carry out update process, like this, the parameter stored due to client be the parameter that sends immediately after client upgrades according to the parameter in service end determination database more new data carry out after update process parameter, it is parameter up-to-date in database, therefore, the parameter that parameter in each usage data storehouse of client only needs reading client to store, without the need to carrying out read operation to database, the parameter in prior art in each usage data storehouse can be avoided all to need to carry out read operation to database and the longer problem of the acquisition time of the parameter caused, thus improve the efficiency of parameter acquiring.
Database involved in the present embodiment can adopt relevant database, such as, oracle database, DB2 database, Structured Query Language (SQL) (Structured Query Language, SQL) server (Server) database, MySQL database etc., or key assignments (Key-Value) type database can also be adopted, such as, non-SQL (Not Only SQL) NoSQL database, Redis database, the present embodiment is not particularly limited this.The mode of operation that service end is carried out database, can according to the difference of database, and in different ways, detailed description see related content of the prior art, can repeat no more herein.
Alternatively, in one of the present embodiment possible implementation, the described parameter that described service end sends more new data can include but not limited to that parameter information, parameter upgrade instruction and parameter version identifier, and the present embodiment is not particularly limited this.
Wherein,
Described parameter information, being used to indicate the essential information needing the parameter of carrying out renewal rewards theory, can be parameter name, such as, when needing to delete certain parameter etc., only need in described parameter information to comprise parameter name, or can also be parameter name and parameter value, such as, when needing to increase certain parameter or revise certain parameter etc., not only need in described parameter information to comprise parameter name, also need to comprise parameter value further, the present embodiment is not particularly limited this.
Described parameter upgrades instruction, be used to indicate the renewal rewards theory needing to carry out parameter, instruction can be increased for parameter, be used to indicate the increase operation needing to carry out parameter, or can also indicate for parameter modification, be used to indicate the retouching operation needing to carry out parameter, or instruction can also be deleted for parameter, be used to indicate the deletion action needing to carry out parameter, the present embodiment is not particularly limited this.
Described parameter version identifier, is used to indicate the identification number of the version of the parameter indicated by described parameter information, and these parameters often upgrade once, and the parameter version identifier of its correspondence just has corresponding change.Particularly, parameter version identifier specifically can adopt numeral to identify, or letter can also be adopted to identify, or numeral can also be adopted to be combined into line identifier with alphabetical, and the present embodiment is not particularly limited this.
As a rule, in a database, the whole parameter used for certain operation system and parameter name and parameter value, arrange a parameter version identifier, in order to identify the version of these parameters.So-called operation system, can be any operating system performing a certain business that needs, can include but not limited to payment system or transaction system, the present embodiment be particularly limited this.
When any one parameter in these parameters or several parameter occur to upgrade, such as, parameter name upgrades, and parameter value upgrades, or parameter name and parameter value all upgrade, etc., parameter version identifier will change accordingly.With parameter version identifier for numeral is illustrated, the parameter version identifier of the parameter that current business system uses is 1, and when any one parameter in these parameters or several parameter occur to upgrade, parameter version identifier then can be updated to 2, the like, the trend increased progressively can be presented.
Particularly, the parameter version identifier that client specifically can store parameter version identifier included in described parameter more new data and described client, judge, whether consistent with the parameter version identifier that described client stores to determine more included in the new data parameter version identifier of described parameter.Unanimously so-called, refer to the parameter version identifier that described parameter is more included in new data and the parameter version identifier that described client stores, identical.
In a concrete implementation procedure, if more included in the new data parameter version identifier of described parameter is consistent with the parameter version identifier that described client stores, illustrate that the parameter that described client stores is exactly the most recent parameters that client described in database uses, described client does not then need to perform any operation.
In the implementation procedure that another is concrete, if the parameter version identifier that described parameter is more included in new data and the parameter version identifier that described client stores inconsistent, illustrate that the parameter that described client stores not is the most recent parameters that client described in database uses, described client then can upgrade instruction according to described parameter, the parameter version identifier that the parameter information utilizing described parameter more included in new data and described parameter are more included in new data, the parameter version identifier that the parameter store described client and described client store, carry out update process.
Particularly, client determine the parameter version identifier that described parameter is more included in new data and the parameter version identifier that described client stores inconsistent after, client specifically can these parameters of storing of this client of direct control, carry out update process.
Alternatively, in one of the present embodiment possible implementation, service end can dispose multiple stage server device, and these server device are all logically of equal value.System can Stochastic choice server device, and as first service end equipment, then Stochastic choice multiple stage server device again, as second service end equipment.These server device form a cluster, this cluster can be made up of 1 or multiple servers, and each server device takies the process resource of a part of cluster, that is, the corresponding station server of each server device, every station server can dispose multiple server device.
In a concrete implementation procedure, in 101, described first service end equipment performs renewal rewards theory to described database, to upgrade the parameter in described database, such as, can utilize database manipulation language, performs renewal rewards theory to described database.If the operating result of described renewal rewards theory is successfully, described first service end equipment then can determine that the parameter in described database upgrades.
Correspondingly, in 102, described first service end equipment specifically can indicate at least one second service end equipment described, sends described parameter more new data to described client.Particularly, specifically to each second service end equipment at least one second service end equipment described, an instruction can be sent, can including but not limited to the mark of the client of the described parameter of use and parameter more new data in this instruction.
Such as, described first service end equipment can create asynchronous thread, each second service end equipment at least one second service end equipment described, sends instruction.
After each second service end equipment receives this instruction at least one second service end equipment described, then according to this instruction, described parameter more new data can be sent to described client.
Such as, described each second service end equipment can create asynchronous thread, sends described parameter more new data to described client, and can also send parameter updating request required for it to other clients.
Be understandable that, similarly, described client can dispose multiple stage client device equally, and these client devices are all logically of equal value.System can Stochastic choice client device, the receiving equipment of the parameter sent as second service end equipment more new data, then this client device again by received parameter more new data send to other client devices of this client.These client devices form a cluster, this cluster can be made up of 1 or multiple servers, and each client device takies the process resource of a part of cluster, that is, the corresponding station server of each client device, every station server can dispose multiple client device.
Alternatively, in one of the present embodiment possible implementation, the parameter more new data that client sends except receiving service end passively, and then according to this parameter more new data, carry out outside update process, initiatively to some lastest imformations of service end acquisition request, and then according to this lastest imformation, update process can also be carried out.This process, can be called that client executing pulls task.
Particularly, described client specifically can obtain parameter version identifier described in described database corresponding to client from described service end.Then, the parameter version identifier that client specifically can store the parameter version identifier corresponding to client described in described database and described client, judge, whether consistent with the parameter version identifier that described client stores to determine the parameter version identifier described in described database corresponding to client.Unanimously so-called, refer to the parameter version identifier that parameter version identifier described in described database corresponding to client and described client store, identical.
In a concrete implementation procedure, if the parameter version identifier described in described database corresponding to client is consistent with the parameter version identifier that described client stores, illustrate that the parameter that described client stores is exactly the most recent parameters that client described in database uses, described client does not then need to perform any operation.
In the implementation procedure that another is concrete, if the parameter version identifier that the parameter version identifier described in described database corresponding to client and described client store is inconsistent, illustrate that the parameter that described client stores not is the most recent parameters that client described in database uses, described client then can obtain from described service end whole parameters that client described in described database uses, and then utilize parameter version identifier described in described whole parameter and described database corresponding to client, the parameter version identifier that the parameter store described client and described client store, carry out update process.
Particularly, client is from after described service end obtains whole parameters that client described in described database uses, and client specifically can whole parameters of storing of this client of direct control, carry out update process.Like this, may there is a problem: in the process of carrying out update process, the parameter that operation system reads from client may be null value, can affect the normal operation of operation system.
In order to ensure the normal operation of operation system, client is from after described service end obtains whole parameters that client described in described database uses, the parameter stored before described client is still as the content that operation system reads, until client is to obtaining whole parameters that client described in described database uses from described service end, to carry out stores processor complete, the content just parameter of up-to-date storage read as operation system.Now, to the parameter stored before, respective handling can be carried out, such as, delete processing or invalidation etc.
Alternatively, in one of the present embodiment possible implementation, except the ability that client can have cached parameters, service end also can have the ability of the whole parameters in cache database.Particularly, whole parameter that specifically clients whole in database can be used, and the parameter version identifier of these parameters, carry out stores processor.
In a concrete implementation procedure, described service end specifically can obtain the parameter version identifier described in described database corresponding to client.Then, the parameter version identifier corresponding to described client that service end specifically can store the parameter version identifier corresponding to client described in described database and described service end, judge, whether consistent to determine the parameter version identifier corresponding to the described client that parameter version identifier described in described database corresponding to client and described service end store.Unanimously so-called, refer to the parameter version identifier corresponding to described client that parameter version identifier described in described database corresponding to client and described service end store, identical.
If the parameter version identifier corresponding to the described client that the parameter version identifier described in described database corresponding to client and described service end store is consistent, illustrate that the parameter that the described client that described service end stores uses is exactly the most recent parameters that client described in database uses, described service end does not then need to perform any operation.
If the parameter version identifier corresponding to described client that the parameter version identifier described in described database corresponding to client and described service end store is inconsistent, illustrate that the parameter that the described client that described service end stores uses not is the most recent parameters that client described in database uses, described service end then can obtain whole parameters that client described in described database uses, and then utilize parameter version identifier described in described whole parameter and described database corresponding to client, whole parameter that the described client stored described service end uses and the parameter version identifier corresponding to described client that described service end stores, carry out update process.
In the implementation procedure that another is concrete, described service end specifically can receive the first acquisition request that described client sends, and described first obtains request for the parameter version identifier described in database described in acquisition request corresponding to client.Because described service end stores whole parameters that client described in described database uses, and the parameter version identifier corresponding to this client, therefore, the parameter version identifier corresponding to described client that described service end then can directly store by described service end, sends to described client.If service end does not store the parameter version identifier corresponding to described client, so, described service end then can obtain the parameter version identifier corresponding to described client from database, then, then sends to this client.
Like this, described client then can parameter version identifier corresponding to client described in received described database, determines whether the whole parameters needing client described in database described in acquisition request to use.In the implementation procedure that another is concrete, described service end specifically can receive the second acquisition request that described client sends, and described second obtains request is used for whole parameters that described in acquisition request, described in database, client uses.Then, whole parameters that the described client that described service end stores then can use by described service end, send to described client.If service end does not store whole parameters that described client uses, so, described service end then can obtain whole parameters that described client uses from database, then, then sends to this client.
In the present embodiment, upgraded by the parameter in service end determination database, and then to using the client of described parameter to send parameter more new data, to make described client according to described parameter more new data, to the parameter that described client stores, carry out update process, like this, the parameter stored due to client be the parameter that sends immediately after client upgrades according to the parameter in service end determination database more new data carry out after update process parameter, it is parameter up-to-date in database, therefore, the parameter that parameter in each usage data storehouse of client only needs reading client to store, without the need to carrying out read operation to database, the parameter in prior art in each usage data storehouse can be avoided all to need to carry out read operation to database and the longer problem of the acquisition time of the parameter caused, thus improve the efficiency of parameter acquiring.
In addition, adopt technical scheme provided by the invention, after the parameter in service end determination database upgrades, immediately to using the client of described parameter to send parameter more new data, therefore, the described parameter that client can be made to store is updated in time, effectively can improve the real-time that parameter upgrades.
In addition, adopt technical scheme provided by the invention, due to the parameter that the parameter in each usage data storehouse of client only needs reading client to store, without the need to carrying out read operation to database, the phenomenon that database can be avoided to block occurs, thus reduces the pressure of database.
In addition, adopt technical scheme provided by the invention, by client from the parameter version identifier corresponding to client described in service end acquisition database, if the parameter version identifier that the parameter version identifier described in described database corresponding to client and described client store is inconsistent, described client obtains from described service end whole parameters that client described in described database uses, and then then can utilize parameter version identifier described in described whole parameter and described database corresponding to client, the parameter version identifier that the parameter store described client and described client store, carry out update process, the parameter stored due to client be whole parameters of obtaining from service end according to this client of client carry out after update process data, therefore, when service end sends parameter renewal data failure or client receiving parameter upgrades data failure, the parameter that client stores remains parameter up-to-date in database, effectively can improve the reliability of parameter acquiring.
It should be noted that, for aforesaid each embodiment of the method, in order to simple description, therefore it is all expressed as a series of combination of actions, but those skilled in the art should know, the present invention is not by the restriction of described sequence of movement, because according to the present invention, some step can adopt other orders or carry out simultaneously.Secondly, those skilled in the art also should know, the embodiment described in instructions all belongs to preferred embodiment, and involved action and module might not be that the present invention is necessary.
In the above-described embodiments, the description of each embodiment is all emphasized particularly on different fields, in certain embodiment, there is no the part described in detail, can see the associated description of other embodiments.
The structural representation of the renewal system of the parameter that Fig. 2 provides for another embodiment of the present invention, as shown in Figure 3.The renewal system of the parameter of the present embodiment can comprise service end 21 and client 22.Wherein, service end 21, for determining that the parameter in database upgrades; And to using the client 22 of described parameter to send parameter more new data; Described client 22, for receiving the described parameter more new data that described service end 21 sends; And according to described parameter more new data, to the parameter that described client 22 stores, carry out update process.
It should be noted that, service end included in the renewal system of the parameter that the present embodiment provides or client, can for being positioned at the application of local terminal, or can also for being arranged in plug-in unit or SDK (Software Development Kit) (the Software Development Kit of the application of local terminal, the functional unit such as SDK), or can also for being arranged in the processing engine of the server of network side, or can also for being positioned at the distributed system of network side, the present embodiment is not particularly limited this, and the present embodiment is not particularly limited this.
Be understandable that, described application can be mounted in the local program (nativeApp) in terminal, or can also be a web page program (webApp) of browser in terminal, and the present embodiment is not particularly limited this.
Alternatively, in one of the present embodiment possible implementation, described parameter more new data can include but not limited to that parameter information, parameter upgrade instruction and parameter version identifier, and the present embodiment is not particularly limited this.
Alternatively, in one of the present embodiment possible implementation, described client 22, the parameter version identifier that more included in the new data parameter version identifier of described parameter and described client 22 store if can also be further used for is inconsistent, instruction is upgraded according to described parameter, the parameter version identifier that the parameter information utilizing described parameter more included in new data and described parameter are more included in new data, the parameter version identifier that the parameter store described client 22 and described client 22 store, carries out update process.
Alternatively, in one of the present embodiment possible implementation, as shown in Figure 3, described service end 21 specifically can include but not limited to first service end equipment 31 and at least one second service end equipment 32
1, 32
232
n.Wherein, n be more than or equal to 1 integer.Wherein,
Described first service end equipment 31, for performing renewal rewards theory, to upgrade the parameter in described database to described database; If the operating result of described renewal rewards theory is successfully, determine that the parameter in described database upgrades; And instruction at least one second service end equipment 32 described
1, 32
232
n, send described parameter more new data to described client 22;
At least one second service end equipment 32 described
1, 32
232
nin each second service end equipment 32
i, i for being greater than 0, and is less than or equal to the integer of n, for the instruction according to described first service end equipment 31, sends described parameter more new data to described client 22.
Alternatively, in one of the present embodiment possible implementation, described client 22, can also be further used for obtaining parameter version identifier described in described database corresponding to client 22 from described service end 21; If the parameter version identifier that the parameter version identifier described in described database corresponding to client 22 and described client 22 store is inconsistent, obtain from described service end 21 whole parameters that client 22 described in described database uses; And utilizing parameter version identifier described in described whole parameter and described database corresponding to client 22, the parameter version identifier that the parameter store described client 22 and described client 22 store, carries out update process.
Alternatively, in one of the present embodiment possible implementation, described service end 21, can also be further used for the parameter version identifier obtained described in described database corresponding to client 22; If the parameter version identifier corresponding to described client 22 that the parameter version identifier described in described database corresponding to client 22 and described service end 21 store is inconsistent, obtain whole parameters that client 22 described in described database uses; And utilize parameter version identifier described in described whole parameter and described database corresponding to client 22, whole parameter that the described client 22 stored described service end 21 uses and the parameter version identifier corresponding to described client 22 that described service end 21 stores, carry out update process.
In a concrete implementation, in one of the present embodiment possible implementation, described client 22, specifically may be used for sending the first acquisition request to described service end 21, described first obtains request for the parameter version identifier described in database described in acquisition request corresponding to client 22; And the parameter version identifier corresponding to described client 22 that the described service end 21 receiving the transmission of described server stores.
Correspondingly, described service end 21, specifically then may be used for receiving described client 22 described first obtains request; And the parameter version identifier corresponding to described client 22 that described service end 21 stored, send to described client 22.
In the implementation that another is concrete, described client 22, specifically may be used for sending the second acquisition request to described service end 21, and described second obtains request is used for whole parameters that described in acquisition request, described in database, client 22 uses; And receive whole parameters that the described client 22 that stores of described service end 21 that described server sends uses.
Correspondingly, described service end 21, specifically then may be used for receiving described client 22 described second obtains request; And by whole parameters that the described client 22 that described service end 21 stores uses, send to described client 22.
It should be noted that, method in the embodiment that Fig. 1 is corresponding, the renewal system of the parameter that can be provided by the present embodiment realizes.Detailed description see the related content in embodiment corresponding to Fig. 1, can repeat no more herein.
In the present embodiment, upgraded by the parameter in service end determination database, and then to using the client of described parameter to send parameter more new data, to make described client according to described parameter more new data, to the parameter that described client stores, carry out update process, like this, the parameter stored due to client be the parameter that sends immediately after client upgrades according to the parameter in service end determination database more new data carry out after update process parameter, it is parameter up-to-date in database, therefore, the parameter that parameter in each usage data storehouse of client only needs reading client to store, without the need to carrying out read operation to database, the parameter in prior art in each usage data storehouse can be avoided all to need to carry out read operation to database and the longer problem of the acquisition time of the parameter caused, thus improve the efficiency of parameter acquiring.
In addition, adopt technical scheme provided by the invention, after the parameter in service end determination database upgrades, immediately to using the client of described parameter to send parameter more new data, therefore, the described parameter that client can be made to store is updated in time, effectively can improve the real-time that parameter upgrades.
In addition, adopt technical scheme provided by the invention, due to the parameter that the parameter in each usage data storehouse of client only needs reading client to store, without the need to carrying out read operation to database, the phenomenon that database can be avoided to block occurs, thus reduces the pressure of database.
In addition, adopt technical scheme provided by the invention, by client from the parameter version identifier corresponding to client described in service end acquisition database, if the parameter version identifier that the parameter version identifier described in described database corresponding to client and described client store is inconsistent, described client obtains from described service end whole parameters that client described in described database uses, and then then can utilize parameter version identifier described in described whole parameter and described database corresponding to client, the parameter version identifier that the parameter store described client and described client store, carry out update process, the parameter stored due to client be whole parameters of obtaining from service end according to this client of client carry out after update process data, therefore, when service end sends parameter renewal data failure or client receiving parameter upgrades data failure, the parameter that client stores remains parameter up-to-date in database, effectively can improve the reliability of parameter acquiring.
Those skilled in the art can be well understood to, and for convenience and simplicity of description, the system of foregoing description, the specific works process of device and unit, with reference to the corresponding process in preceding method embodiment, can not repeat them here.
In several embodiment provided by the present invention, should be understood that, disclosed system, apparatus and method, can realize by another way.Such as, device embodiment described above is only schematic, such as, the division of described unit, be only a kind of logic function to divide, actual can have other dividing mode when realizing, such as multiple unit or assembly can in conjunction with or another system can be integrated into, or some features can be ignored, or do not perform.Another point, shown or discussed coupling each other or direct-coupling or communication connection can be by some interfaces, and the indirect coupling of device or unit or communication connection can be electrical, machinery or other form.
The described unit illustrated as separating component or can may not be and physically separates, and the parts as unit display can be or may not be physical location, namely can be positioned at a place, or also can be distributed in multiple network element.Some or all of unit wherein can be selected according to the actual needs to realize the object of the present embodiment scheme.
In addition, each functional unit in each embodiment of the present invention can be integrated in a processing unit, also can be that the independent physics of unit exists, also can two or more unit in a unit integrated.Above-mentioned integrated unit both can adopt the form of hardware to realize, and the form that hardware also can be adopted to add SFU software functional unit realizes.
The above-mentioned integrated unit realized with the form of SFU software functional unit, can be stored in a computer read/write memory medium.Above-mentioned SFU software functional unit is stored in a storage medium, comprising some instructions in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) or processor (processor) perform the part steps of method described in each embodiment of the present invention.And aforesaid storage medium comprises: USB flash disk, portable hard drive, ROM (read-only memory) (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disc or CD etc. various can be program code stored medium.
Last it is noted that above embodiment is only in order to illustrate technical scheme of the present invention, be not intended to limit; Although with reference to previous embodiment to invention has been detailed description, those of ordinary skill in the art is to be understood that: it still can be modified to the technical scheme described in foregoing embodiments, or carries out equivalent replacement to wherein portion of techniques feature; And these amendments or replacement, do not make the essence of appropriate technical solution depart from the spirit and scope of various embodiments of the present invention technical scheme.
Claims (16)
1. a update method for parameter, is characterized in that, comprising:
Parameter in service end determination database upgrades;
Described service end sends parameter more new data to using the client of described parameter, to make described client according to described parameter more new data, to the parameter that described client stores, carries out update process.
2. method according to claim 1, is characterized in that, more new data packets draws together parameter information to described parameter, parameter upgrades instruction and parameter version identifier.
3. method according to claim 2, is characterized in that, described method also comprises:
If the parameter version identifier that described parameter is more included in new data and the parameter version identifier that described client stores inconsistent, described client upgrades instruction according to described parameter, the parameter version identifier that the parameter information utilizing described parameter more included in new data and described parameter are more included in new data, the parameter version identifier that the parameter store described client and described client store, carries out update process.
4. method according to claim 1, is characterized in that, described service end comprises first service end equipment and at least one second service end equipment;
Parameter in described service end determination database upgrades, and comprising:
Described first service end equipment performs renewal rewards theory, to upgrade the parameter in described database to described database;
If the operating result of described renewal rewards theory is successfully, described first service end equipment determines that the parameter in described database upgrades;
Described service end sends parameter more new data to client, comprising:
Described first service end equipment instruction at least one second service end equipment described, sends described parameter more new data to described client.
5. the method according to the arbitrary claim of Claims 1 to 4, is characterized in that, described method also comprises:
Described client obtains the parameter version identifier described in described database corresponding to client from described service end;
If the parameter version identifier that the parameter version identifier described in described database corresponding to client and described client store is inconsistent, described client obtains from described service end whole parameters that client described in described database uses;
Described client utilizes the parameter version identifier described in described whole parameter and described database corresponding to client, the parameter version identifier that the parameter store described client and described client store, and carries out update process.
6. method according to claim 5, is characterized in that, described method also comprises:
Described service end obtains the parameter version identifier described in described database corresponding to client;
If the parameter version identifier corresponding to described client that the parameter version identifier described in described database corresponding to client and described service end store is inconsistent, described service end obtains whole parameters that client described in described database uses;
Described service end utilizes the parameter version identifier described in described whole parameter and described database corresponding to client, whole parameter that the described client stored described service end uses and the parameter version identifier corresponding to described client that described service end stores, carry out update process.
7. method according to claim 6, is characterized in that, described client obtains the parameter version identifier described in described database corresponding to client from described service end, comprising:
Described service end receives the first acquisition request that described client sends, and described first obtains request for the parameter version identifier described in database described in acquisition request corresponding to client;
Parameter version identifier corresponding to the described client that described service end stores by described service end, sends to described client.
8. the method according to claim 6 or 7, is characterized in that, described client obtains from described service end whole parameters that client described in described database uses, and comprising:
Described service end receives the second acquisition request that described client sends, and described second obtains request is used for whole parameters that described in acquisition request, described in database, client uses;
Whole parameters that the described client that described service end stores by described service end uses, send to described client.
9. a renewal system for parameter, is characterized in that, comprising:
Service end, for determining that the parameter in database upgrades; And to using the client of described parameter to send parameter more new data;
Described client, for receiving the described parameter more new data that described service end sends; And according to described parameter more new data, to the parameter that described client stores, carry out update process.
10. system according to claim 9, is characterized in that, more new data packets draws together parameter information to described parameter, parameter upgrades instruction and parameter version identifier.
11. systems according to claim 10, is characterized in that, described client, also for
If the parameter version identifier that described parameter is more included in new data and the parameter version identifier that described client stores inconsistent, instruction is upgraded according to described parameter, the parameter version identifier that the parameter information utilizing described parameter more included in new data and described parameter are more included in new data, the parameter version identifier that the parameter store described client and described client store, carries out update process.
12. systems according to claim 9, is characterized in that, described service end specifically comprises first service end equipment and at least one second service end equipment;
Described first service end equipment, for performing renewal rewards theory, to upgrade the parameter in described database to described database; If the operating result of described renewal rewards theory is successfully, determine that the parameter in described database upgrades; And instruction at least one second service end equipment described, send described parameter more new data to described client;
Each second service end equipment at least one second service end equipment described, for the instruction according to described first service end equipment, sends described parameter more new data to described client.
13. systems according to the arbitrary claim of claim 9 ~ 12, is characterized in that, described client, also for
The parameter version identifier described in described database corresponding to client is obtained from described service end; If the parameter version identifier that the parameter version identifier described in described database corresponding to client and described client store is inconsistent, obtain from described service end whole parameters that client described in described database uses; And utilizing parameter version identifier described in described whole parameter and described database corresponding to client, the parameter version identifier that the parameter store described client and described client store, carries out update process.
14. systems according to claim 13, is characterized in that, described service end, also for
Obtain the parameter version identifier described in described database corresponding to client; If the parameter version identifier corresponding to described client that the parameter version identifier described in described database corresponding to client and described service end store is inconsistent, obtain whole parameters that client described in described database uses; And utilize parameter version identifier described in described whole parameter and described database corresponding to client, whole parameter that the described client stored described service end uses and the parameter version identifier corresponding to described client that described service end stores, carry out update process.
15. systems according to claim 14, is characterized in that,
Described client, obtains request specifically for sending first to described service end, and described first acquisition request is used for the parameter version identifier described in acquisition request described in database corresponding to client; And the parameter version identifier corresponding to described client that the described service end receiving the transmission of described server stores;
Described service end, specifically for receiving described client described first obtains request; And the parameter version identifier corresponding to described client that described service end stored, send to described client.
16. systems according to claims 14 or 15, is characterized in that,
Described client, obtains request specifically for sending second to described service end, and described second obtains request is used for whole parameters that described in acquisition request, described in database, client uses; And receive whole parameters that the described client that stores of described service end that described server sends uses;
Described service end, specifically for receiving described client described second obtains request; And whole parameters that the described client described service end to be stored uses, send to described client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510257419.XA CN104881454A (en) | 2015-05-19 | 2015-05-19 | Updating method and system of parameter |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510257419.XA CN104881454A (en) | 2015-05-19 | 2015-05-19 | Updating method and system of parameter |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104881454A true CN104881454A (en) | 2015-09-02 |
Family
ID=53948947
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510257419.XA Pending CN104881454A (en) | 2015-05-19 | 2015-05-19 | Updating method and system of parameter |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104881454A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105071975A (en) * | 2015-09-07 | 2015-11-18 | 北京瑞星信息技术有限公司 | Data transmission and distribution method and system |
| CN105511914A (en) * | 2015-12-01 | 2016-04-20 | 百度在线网络技术（北京）有限公司 | Application update method, device and system |
| WO2017092348A1 (en) * | 2015-12-02 | 2017-06-08 | 乐视控股（北京）有限公司 | Updating method, configuration and system for key-value pair database of client terminal |
| CN109697131A (en) * | 2018-12-06 | 2019-04-30 | 京信通信系统（中国）有限公司 | Parameter management, synchronous method and device between process |
| CN111240737A (en) * | 2020-01-20 | 2020-06-05 | 杭州海兴电力科技股份有限公司 | Dynamic service parameter configuration method based on Redis |
| CN111796851A (en) * | 2020-08-06 | 2020-10-20 | 北京百度网讯科技有限公司 | Client base library updating method and device, electronic equipment and storage medium |
| CN115309431A (en) * | 2022-09-29 | 2022-11-08 | 荣耀终端有限公司 | Parameter updating method, readable medium and electronic equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050154915A1 (en) * | 2004-01-09 | 2005-07-14 | Peterson Matthew T. | Networked computer user identification and authentication apparatus method and system |
| CN101009516A (en) * | 2006-01-26 | 2007-08-01 | 华为技术有限公司 | A method and system for data synchronization |
| CN102255752A (en) * | 2011-06-30 | 2011-11-23 | 北京新媒传信科技有限公司 | Configuration management system and method of server cluster |
| CN102609488A (en) * | 2012-01-20 | 2012-07-25 | 北京星网锐捷网络技术有限公司 | Client, data query method of client, server and data query system |
| CN103812849A (en) * | 2012-11-15 | 2014-05-21 | 腾讯科技（深圳）有限公司 | Local cache updating method and system, client and server |
| CN104066077A (en) * | 2014-06-24 | 2014-09-24 | 青岛海信移动通信技术股份有限公司 | OTA downloading and upgrading method and device thereof |
| CN104580454A (en) * | 2014-12-31 | 2015-04-29 | 乐视网信息技术（北京）股份有限公司 | Data synchronizing method, device and system |
-
2015
- 2015-05-19 CN CN201510257419.XA patent/CN104881454A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050154915A1 (en) * | 2004-01-09 | 2005-07-14 | Peterson Matthew T. | Networked computer user identification and authentication apparatus method and system |
| CN101009516A (en) * | 2006-01-26 | 2007-08-01 | 华为技术有限公司 | A method and system for data synchronization |
| CN102255752A (en) * | 2011-06-30 | 2011-11-23 | 北京新媒传信科技有限公司 | Configuration management system and method of server cluster |
| CN102609488A (en) * | 2012-01-20 | 2012-07-25 | 北京星网锐捷网络技术有限公司 | Client, data query method of client, server and data query system |
| CN103812849A (en) * | 2012-11-15 | 2014-05-21 | 腾讯科技（深圳）有限公司 | Local cache updating method and system, client and server |
| CN104066077A (en) * | 2014-06-24 | 2014-09-24 | 青岛海信移动通信技术股份有限公司 | OTA downloading and upgrading method and device thereof |
| CN104580454A (en) * | 2014-12-31 | 2015-04-29 | 乐视网信息技术（北京）股份有限公司 | Data synchronizing method, device and system |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105071975A (en) * | 2015-09-07 | 2015-11-18 | 北京瑞星信息技术有限公司 | Data transmission and distribution method and system |
| CN105071975B (en) * | 2015-09-07 | 2019-03-12 | 北京瑞星网安技术股份有限公司 | The method and system of data transmission and distribution |
| CN105511914A (en) * | 2015-12-01 | 2016-04-20 | 百度在线网络技术（北京）有限公司 | Application update method, device and system |
| CN105511914B (en) * | 2015-12-01 | 2019-05-31 | 百度在线网络技术（北京）有限公司 | Using update method, device and system |
| WO2017092348A1 (en) * | 2015-12-02 | 2017-06-08 | 乐视控股（北京）有限公司 | Updating method, configuration and system for key-value pair database of client terminal |
| CN109697131A (en) * | 2018-12-06 | 2019-04-30 | 京信通信系统（中国）有限公司 | Parameter management, synchronous method and device between process |
| CN109697131B (en) * | 2018-12-06 | 2021-08-24 | 京信网络系统股份有限公司 | Method and device for managing and synchronizing parameters between processes |
| CN111240737A (en) * | 2020-01-20 | 2020-06-05 | 杭州海兴电力科技股份有限公司 | Dynamic service parameter configuration method based on Redis |
| CN111240737B (en) * | 2020-01-20 | 2023-05-05 | 杭州海兴电力科技股份有限公司 | Redis-based dynamic service parameter configuration method |
| CN111796851A (en) * | 2020-08-06 | 2020-10-20 | 北京百度网讯科技有限公司 | Client base library updating method and device, electronic equipment and storage medium |
| CN115309431A (en) * | 2022-09-29 | 2022-11-08 | 荣耀终端有限公司 | Parameter updating method, readable medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104881454A (en) | Updating method and system of parameter | |
| CN108846753B (en) | Method and apparatus for processing data | |
| CN112765271A (en) | Block chain transaction index storage method and device, computer equipment and medium | |
| CN112073994A (en) | Method and device for over-the-air upgrading, electronic equipment and readable storage medium | |
| CN105450705A (en) | Service data processing method and apparatus | |
| CN113364877B (en) | Data processing method, device, electronic equipment and medium | |
| CN112988770B (en) | Method, device, electronic equipment and storage medium for updating serial number | |
| CN105491078A (en) | Data processing method and device in SOA system, and SOA system | |
| CN113961510A (en) | File processing method, device, equipment and storage medium | |
| CN104346426A (en) | Shared data de-duplication method and system | |
| CN115455058A (en) | Cache data processing method and device, computer equipment and storage medium | |
| CN110554951A (en) | Method and device for managing embedded points | |
| CN114153856A (en) | Host data double-writing method and device | |
| CN104063377A (en) | Information processing method and electronic equipment using same | |
| CN112860662A (en) | Data blood relationship establishing method and device, computer equipment and storage medium | |
| CN112416934A (en) | hive table incremental data synchronization method and device, computer equipment and storage medium | |
| CN112565356A (en) | Data storage method and device and electronic equipment | |
| CN111475468A (en) | Log access method, device, equipment and storage medium of newly added system | |
| CN112395337A (en) | Data export method and device | |
| CN116450723A (en) | Data extraction method, device, computer equipment and storage medium | |
| CN110866001A (en) | Method and device for determining order to be processed | |
| CN109087097B (en) | Method and device for updating same identifier of chain code | |
| CN105243123A (en) | Method and apparatus for generating difference file of offline map file and updating offline map file | |
| CN108196979B (en) | Data backup method and device | |
| CN112235332A (en) | Read-write switching method and device for cluster |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20150902 |
|
| RJ01 | Rejection of invention patent application after publication |