CN102801782B - A kind of synchronous updating method of data and system - Google Patents
A kind of synchronous updating method of data and system Download PDFInfo
- Publication number
- CN102801782B CN102801782B CN201210222616.4A CN201210222616A CN102801782B CN 102801782 B CN102801782 B CN 102801782B CN 201210222616 A CN201210222616 A CN 201210222616A CN 102801782 B CN102801782 B CN 102801782B
- Authority
- CN
- China
- Prior art keywords
- data
- sequence number
- new data
- flag bit
- upgrade
- 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.)
- Active
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Telephonic Communication Services (AREA)
Abstract
This application provides a kind of synchronous updating method and system of data, to solve, to be updated to power in data synchronization updating process low, the problem of the waste network bandwidth and resource.Described method comprises: receive user data requests, carry zone bit information in described user data requests; When described zone bit information represents that acquisition upgrades, judge whether the local renewal flag bit preserved is allow renewal; Upgrade if allow, then send the sequence number of described renewal flag bit and local data; Receive user data update request, described user data update request comprises the sequence number of more new data and more new data; Replace described local data with described more new data, replace the sequence number of described local data with the sequence number of described more new data, and send user data synchronization and be updated successfully response message; Upgrade if do not allow, then send described renewal flag bit and notify not allow to upgrade.The application ensure that the reliability of data synchronization updating, improves wasting of resources situation.
Description
Technical field
The application relates to communication technical field, particularly relates to a kind of synchronous updating method and system of data.
Background technology
IP Multimedia System (IPMultimediaSubsystem, IMS) is a kind of brand-new multimedia service form, and it can meet present terminal client demand that is more novel, more diverse multimedia business.At present, IMS is considered to the core technology of next generation network, is also to solve to move to merge with fixed network, introduces the important way of the differentiated services such as voice, data, video Triple Fusion.
Under IMS architecture system, user service data be maintained in application server (ApplicationServer, AS) complete in, after user upgrades business datum, AS needs will upgrade data syn-chronization to home subscriber server (HomeSubscriberServer, HSS), SequenceNumber in sequence number (SequenceNumber) in the more local storage data of HSS and more new data, if the local SequenceNumber stored in data is less than the SequenceNumber in more new data, then allow Data Update, otherwise HSS returns error message.
As shown in Figure 1, be the schematic flow sheet of AS and AS ' when simultaneously asking more new data, detailed process is as follows:
1, AS system needs to upgrade business datum, uses user data requests (UserDataRequest, UDR) order to send the request obtaining data SequenceNumber to HSS system.
2, after HSS system receives request, SequenceNumber is returned to AS system by user data response (UserDataAnswer, UDA) order, suppose SequenceNumber=n.
3, AS ' system needs renewal business datum to use UDR ' to order the request sending acquisition data SequenceNumber to HSS system.
4, after HSS system receives request, SequenceNumber is returned to AS ' system by UDA ' order, the SequenceNumber=n of now AS ' acquisition.
5, AS system update business datum by n+1.
6, AS system by upgrade after data by user data update request (ProfileUpdateRequest, PUR) command routing to HSS system.
7, after HSS system receives PUR order, the SequenceNumber value n+1 that inspection AS sends is greater than the SequenceNumber value n in current HSS system, and condition is set up, more new data, the SequenceNumber=n+1 now in HSS system.
8, HSS system is back into merit user data update response (ProfileUpdateAnswer, PUA).
9, AS ' system update business datum by n+1.
10, the data after renewal are passed through PUR ' command routing to HSS system by AS ' system.
11, after HSS system receives PUR ' order, the SequenceNumber value n+1 that inspection AS ' sends equals the SequenceNumber value n+1 in current HSS system, condition failure.
12, HSS system returns erroneous user data renewal response by PUA ' order.
Therefore, when the multiple threads in same operation system call PUR command request renewal business datum simultaneously, or same user contracts multiple business, when calling PUR order to HSS request renewal business datum in each business simultaneously, SequenceNumber in the more new data that each request is submitted to is identical, therefore, only has a PUR request to be updated successfully, receive success response, the PUR request of other failure all will receive error message.And for upgrading failed request, AS needs Multiple through then out UDR order to obtain SequenceNumber value and performs PUR order more new data simultaneously, affect the network bandwidth and resource.
Summary of the invention
Technical problems to be solved in this application are to provide a kind of synchronous updating method and system of data, and to solve, to be updated to power in data synchronization updating process low, the problem of the waste network bandwidth and resource.
In order to solve the problem, this application discloses a kind of synchronous updating method of data, comprising:
Receive user data requests, in described user data requests, carry zone bit information;
When described zone bit information represents that acquisition upgrades, judge whether the local renewal flag bit preserved is allow renewal;
Upgrade if allow, then send the sequence number of described renewal flag bit and local data;
Receive user data update request, described user data update request comprises the sequence number of more new data and more new data, and the sequence number of described more new data calculates based on the sequence number of described local data;
Replace described local data with described more new data, replace the sequence number of described local data with the sequence number of described more new data, and send user data synchronization and be updated successfully response message;
Upgrade if do not allow, then send described renewal flag bit and notify not allow to upgrade.
Preferably, after the sequence number sending described renewal flag bit and local data, also comprise:
Described renewal flag bit is revised as and does not allow to upgrade.
Preferably, after transmission user data synchronization is updated successfully response message, also comprise:
Described renewal flag bit is revised as and allows to upgrade.
Preferably, replacing described local data with described more new data, before replacing the sequence number of described local data with the sequence number of described more new data, also comprising:
The sequence number of more new data described in whether the sequence number of more described local data is less than, if so, then performs described replacement.
Preferably, the sequence number that the sequence number of described more new data equals described local data adds 1.
On the other hand, disclosed herein as well is a kind of synchronous updating system of data, comprising:
First receiver module, for receiving user data requests, carries zone bit information in described user data requests;
Judge module, during for representing that when described zone bit information acquisition upgrades, judges whether the local renewal flag bit preserved is allow renewal;
First sending module, for when allowing to upgrade, sends the sequence number of described renewal flag bit and local data;
Second receiver module, for receiving user data update request, described user data update request comprises the sequence number of more new data and more new data, and the sequence number of described more new data calculates based on the sequence number of described local data;
Replacement module, for replacing described local data with described more new data, replaces the sequence number of described local data with the sequence number of described more new data, and sends user data synchronization and be updated successfully response message;
Second sending module, for when not allowing to upgrade, sending described renewal flag bit and notifying not allow to upgrade.
Preferably, described system also comprises:
First modified module, for send described renewal flag bit and local data at the first sending module sequence number after, described renewal flag bit is revised as and does not allow to upgrade.
Preferably, described system also comprises:
Second modified module, after being updated successfully response message in replacement module transmission user data synchronization, being revised as described renewal flag bit and allowing to upgrade.
Preferably, described system also comprises:
Comparison module, for replacing described local data at the described more new data of replacement module, before replacing the sequence number of described local data with the sequence number of described more new data, the sequence number of more new data described in whether the sequence number of more described local data is less than, if so, then described replacement module performs described replacement.
Preferably, the sequence number that the sequence number of described more new data equals described local data adds 1.
Compared with prior art, the application comprises following advantage:
First, the application upgrades flag bit by increasing in the local data of HSS system, upgrade for identifying current whether permission, when allowing renewal, the sequence number of local data is sent to AS, carry out the synchronized update of data, and real time modifying upgrades the sequence number of flag bit and local data, to ensure accurately to carry out to Data Update next time.Accordingly, first AS obtains renewal by transmission user data requests, when described flag bit is when allowing renewal, then sends user data update request further, when described flag bit is when not allowing renewal, then will resends user data requests and obtain renewal.The application ensure that the reliability of data synchronization updating by above-mentioned processing procedure, when for the multiple threads in multiple business or same operation system, request msg upgrades simultaneously, can ensure synchronously, exactly to perform between each business or thread.
Secondly, during due to the request msg renewal simultaneously of the multiple threads in multiple business or same operation system, can synchronously, exactly perform between each business or thread, therefore, AS will receive Data Update success response, and do not need to repeat PUR order more new data again, thus improve wasting of resources situation.
Again, increase and upgrade after flag bit in the local data of HSS system, whether AS system can described renewal flag bit that more new data can be returned by HSS system judge, more friendly for interface definition.
Accompanying drawing explanation
Fig. 1 is the schematic flow sheet of AS and AS ' described in prior art when simultaneously asking more new data;
Fig. 2 is the flow chart of the synchronous updating method of a kind of data described in the embodiment of the present application one;
Fig. 3 is the flow chart of the synchronous updating method of a kind of data described in the embodiment of the present application two;
Fig. 4 is the command transfer process schematic described in the embodiment of the present application between AS and HSS;
Fig. 5 is the schematic flow sheet of AS and AS ' described in the embodiment of the present application when simultaneously asking more new data;
Fig. 6 is the structured flowchart of the synchronous updating system of a kind of data described in the embodiment of the present application three;
Fig. 7 is the structured flowchart of the synchronous updating system of a kind of data described in the embodiment of the present application four.
Embodiment
For enabling above-mentioned purpose, the feature and advantage of the application more become apparent, below in conjunction with the drawings and specific embodiments, the application is described in further detail.
The application upgrades flag bit by increasing in the local data of HSS system, when AS system needs to HSS system propelling data, the synchronized update of data is carried out when described renewal flag bit is and allows renewal, ensure that the reliability of data synchronization updating, when for the multiple threads in multiple business or same operation system, request msg upgrades simultaneously, can ensure synchronously, exactly to perform between each business or thread.
With reference to Fig. 2, show the flow chart of the synchronous updating method of a kind of data described in the embodiment of the present application one, described method comprises:
Step S201, receives user data requests, carries zone bit information in described user data requests.
Under IMS architecture system, being maintained in AS of user service data completes, and after user upgrades business datum, AS system needs will upgrade data syn-chronization to HSS system, and now AS system sends user data requests UDR order to HSS system.
Because the embodiment of the present application adds renewal flag bit in HSS system, upgrade for identifying current whether permission, therefore, in the user data requests that AS sends to HSS, carry zone bit information, for identifying sent user data requests, whether this zone bit information represents that acquisition upgrades.
Concrete, in UDR order, expand the zone bit information that a name is called SeqLock, be used for identifying this order and whether represent that acquisition upgrades.Wherein, the value of SeqLock is 0 or 1, when the value of SeqLock is 1, then represents that this UDR order upgrades for obtaining; When the value of SeqLock is 0, then represent that this UDR order is for obtaining other business datum orders, as obtained the order of the data such as User Status, initial filter standard or norm.
Certainly, the embodiment of the present application also can set when the value of SeqLock is 0, represents that this UDR order upgrades for obtaining; When the value of SeqLock is 1, represent that this UDR order is for obtaining other business datum orders, the application is not limited this.
Step S202, when described zone bit information represents that acquisition upgrades, judges whether the local renewal flag bit preserved is allow renewal.
After the user data requests that HSS system acceptance sends to AS system, determine whether the zone bit information in this user data requests represents that acquisition upgrades, namely judge the value of the SeqLock in UDR order, when the value of SeqLock is 1, described zone bit information represents that acquisition upgrades.
The zone bit information determining in the UDR order that AS sends represents and obtains when upgrading, and HSS system judges whether the local renewal flag bit preserved is allow renewal.Concrete, in the local data of HSS, increase the renewal flag bit that a name is called Lock, wherein the value of Lock is 0 or 1, when the value of Lock is 1, represents that the data in current HSS system allow to upgrade; When the value of Lock is 0, represent that the data in current HSS system do not allow to upgrade.
Certainly, the embodiment of the present application also can set when the value of Lock is 0, represents that the data in current HSS system allow to upgrade; When the value of Lock is 1, represent that the data in current HSS system do not allow to upgrade, the application is not limited this.
Step S203, upgrades if allow, then sends the sequence number of described renewal flag bit and local data.
HSS system judges that the local renewal flag bit preserved upgrades for allowing, the value of the Lock namely in current system is 1, then the sequence number of local data in this renewal flag bit and HSS system is sent to AS system by user data response UDA order, instruction AS system is current can be upgraded.
Step S204, receives user data update request, and described user data update request comprises the sequence number of more new data and more new data, and the sequence number of described more new data calculates based on the sequence number of described local data.
After AS system acceptance to the sequence number upgrading local data in flag bit and HSS system, judge that current permission upgrades (Lock=1) according to described renewal flag bit, then AS calculates the sequence number of more new data based on the sequence number of local data in the HSS system received, and send user data update request PUR order to HSS, comprise the sequence number of more new data and more new data in described user data update request.
Preferably, in the present embodiment, the sequence number of described local data is added 1, obtains the sequence number of more new data after receiving the sequence number of the local data that HSS sends by AS.Certainly, the sequence number of more new data described in can also calculating by other means, the application is not limited concrete computational methods.
Step S205, replaces described local data with described more new data, replaces the sequence number of described local data with the sequence number of described more new data, and sends user data synchronization and be updated successfully response message.
HSS then performs the renewal of local data, replaces described local data with described more new data, replace the sequence number of described local data with the sequence number of described more new data after receiving the user data update request of AS transmission.After Data Update, the data in HSS and AS can keep synchronous, and HSS sends user data synchronization by PUA order to AS and is updated successfully response message.
Step S206, upgrades if do not allow, then send described renewal flag bit and notify not allow to upgrade.
When HSS system judges the local renewal flag bit preserved for not allowing to upgrade, the value of the Lock namely in current system is 0, then this renewal flag bit is sent to AS system by user data response UDA order, and current permission of instruction AS system upgrades.
After AS system acceptance to renewal flag bit, judge that current permission upgrades (Lock=0) according to described renewal flag bit, then need to resend user data requests UDR order to HSS system.
Data synchronization updating method described in the present embodiment can reach following technique effect by performing each step above-mentioned:
First, the present embodiment upgrades flag bit by increasing in the local data of HSS system, upgrading, allowing, when upgrading, the sequence number of local data is sent to AS, carrying out the synchronized update of data for identifying current whether permission.Accordingly, first AS obtains renewal by transmission user data requests, when described flag bit is when allowing renewal, then sends user data update request further, when described flag bit is when not allowing renewal, then will resends user data requests and obtain renewal.The embodiment of the present application ensure that the reliability of data synchronization updating by above-mentioned processing procedure, when for the multiple threads in multiple business or same operation system, request msg upgrades simultaneously, can ensure synchronously, exactly to perform between each business or thread.
Secondly, during due to the request msg renewal simultaneously of the multiple threads in multiple business or same operation system, can synchronously, exactly perform between each business or thread, therefore, AS will receive Data Update success response, and do not need to repeat PUR order more new data again, thus improve wasting of resources situation.
Again, increase and upgrade after flag bit in the local data of HSS system, whether AS system can described renewal flag bit that more new data can be returned by HSS system judge, more friendly for interface definition.
With reference to Fig. 3, show the flow chart of the synchronous updating method of a kind of data described in the embodiment of the present application two, described method comprises:
Step S301, receives user data requests, carries zone bit information in described user data requests.
Step S302, when described zone bit information represents that acquisition upgrades, judges whether the local renewal flag bit preserved is allow renewal.
Step S303, upgrades if allow, then sends the sequence number of described renewal flag bit and local data.
Step S304, is revised as described renewal flag bit and does not allow to upgrade.
HSS judges that the renewal flag bit preserved current this locality upgrades for allowing, and after the sequence number of described renewal flag bit and local data is sent to AS, also needs the renewal flag bit of this locality to be revised as not allowing to upgrade.Namely current HSS carries out the synchronized update process of data with an AS, if now there is other AS also to ask more new data, then the renewal flag bit now in HSS system upgrades for not allowing, and HSS will the update request of other AS of refusal.
Step S305, receives user data update request, and described user data update request comprises the sequence number of more new data and more new data, and the sequence number of described more new data calculates based on the sequence number of described local data.
Preferably, the sequence number that the sequence number of described more new data equals described local data adds 1.
Step S306, the sequence number of more new data described in whether the sequence number of more described local data is less than, if so, then performs described replacement.
After HSS receives user data update request, the sequence number of more new data that more described user data update request is comprised and the sequence number of local data, the sequence number of more new data described in if the sequence number of described local data is less than, then illustrate current can more new data, HSS performs step S307.The sequence number of more new data described in if the sequence number of described local data is not less than, then present data transmission mistake is described, renewal process terminates.
Step S307, replaces described local data with described more new data, replaces the sequence number of described local data with the sequence number of described more new data, and sends user data synchronization and be updated successfully response message.
Step S308, is revised as described renewal flag bit and allows to upgrade.
In order to ensure that the data synchronization updating of each AS and HSS can both be successful, be revised as by renewal flag bit in step s 304 and do not allow to upgrade, namely HSS refuses the Data Update request of other AS at no point in the update process.Therefore, after current AS and HSS data synchronization updating success, HSS also needs renewal flag bit to be revised as permission and upgrades, to ensure accurately to carry out to Data Update next time.
Step S309, upgrades if do not allow, then send described renewal flag bit and notify not allow to upgrade.
In the present embodiment, HSS upgrades flag bit by real time modifying, in the data synchronization updating process of current AS and HSS, do not allow other AS more new data, and after current AS and HSS data synchronization updating success, renewal flag bit is revised as and allows to upgrade, ensure that the data synchronization updating process of each AS and HSS can be successful, further increase the reliability of data synchronization updating.
Below, the data synchronization updating process described in the embodiment of the present application is specifically introduced.
First, the command transfer process between AS and HSS is described, as shown in Figure 4, it should be noted that, do not comprise renewal flag bit in HSS in this process, in AS, do not comprise zone bit information yet, command transfer process when this process just carries out the synchronized update of data for illustration of AS and HSS.
In HSS system, the Store form of business datum is as follows:
Described command transfer process comprises:
Step 1, when the business datum change of AS system, needs to upgrade business datum, uses UDR order to send the request obtaining data SequenceNumber to HSS system.
Step 2, returns to AS system by the SequenceNumber of local data by UDA order after HSS system receives request.
Step 3, the value of the SequenceNumber received also is added 1 by AS system update data, and the SequenceNumber of more new data and more new data is sent to HSS system by PUR order.
Step 4, after HSS system acceptance to PUR order, relatively whether the SequenceNumber of local data is less than the SequenceNumber of more new data, if, then use more new data to replace local data, more the SequenceNumber of new data replaces the SequenceNumber of local data, and by PUA order return data synchronized update success response information, otherwise, return DIAMETER_ERROR_TRANSPARENT_DATA_OUT_OF_SYNC errored response.
Below, illustrate method flow when AS and AS ' in the embodiment of the present application asks more new data simultaneously, in HSS system, the Store form of business datum is as follows:
As shown in Figure 5, described method comprises:
Step a1, AS system needs to upgrade business datum, sends user data requests UDR order to HSS system, carries zone bit information SeqLock=1 in this order, represents to obtain to upgrade.
Step a2, HSS system judges the local renewal flag bit Lock=1 preserved, and represents and allows to upgrade, return UDA order, carry the sequence number SequenceNumber of described renewal flag bit and local data in this order, the Lock in system is revised as 0 simultaneously, refuses other update requests.
Step a3, AS ' system needs to upgrade business datum, sends user data requests UDR ' order to HSS system, carries zone bit information SeqLock=1 in this order, represents to obtain to upgrade.
Step a4, HSS system judges the local renewal flag bit Lock=0 preserved, and represents and does not allow to upgrade, return UDA ' order, carries described renewal flag bit in this order.
Step a5, AS system judges the Lock=1 in UDA order, then more new data the value of the SequenceNumber received is added 1, obtains the SequenceNumber of more new data.
The SequenceNumber of more new data and more new data is sent to HSS system by PUR order by step a6, AS system.
Step a7, after HSS system receives PUR order, relatively the SequenceNumber of local data is less than the SequenceNumber of the more new data that AS sends, then replace described local data with the more new data that AS transmits, the SequenceNumber of described local data is replaced with the SequenceNumber of more new data, and send PUA order return data synchronized update success response information, Lock is revised as 1 simultaneously.
Step a8, AS ' system judges the Lock=0 in UDA ' order, represents and does not allow at present to upgrade.
Step a9, AS ' system sends UDR ' order to HSS system again, carries zone bit information SeqLock=1 in this order, represents to obtain to upgrade.
Step a10, HSS system judges the local renewal flag bit Lock=1 preserved, and represents and allows to upgrade, return UDA ' order, carry the SequenceNumber of described renewal flag bit and local data in this order, the Lock in system is revised as 0 simultaneously, refuses other update requests.
Step a11, AS ' system judges the Lock=1 in UDA ' order, then more new data the value of the SequenceNumber received is added 1, obtains the SequenceNumber of more new data.
The SequenceNumber of more new data and more new data is sent to HSS system by PUR ' order by step a12, AS ' system.
Step a13, after HSS system receives PUR ' order, relatively the SequenceNumber of local data is less than the SequenceNumber of the more new data that AS ' sends, then replace described local data with the more new data of AS ' transmission, the SequenceNumber of described local data is replaced with the SequenceNumber of more new data, and send PUA ' order return data synchronized update success response information, Lock is revised as 1 simultaneously.
With reference to Fig. 6, show the structured flowchart of the synchronous updating system of a kind of data described in the embodiment of the present application three, described system comprises:
First receiver module 601, for receiving user data requests, carries zone bit information in described user data requests;
Judge module 602, during for representing that when described zone bit information acquisition upgrades, judges whether the local renewal flag bit preserved is allow renewal;
First sending module 603, for when allowing to upgrade, sends the sequence number of described renewal flag bit and local data;
Second receiver module 604, for receiving user data update request, described user data update request comprises the sequence number of more new data and more new data, and the sequence number of described more new data calculates based on the sequence number of described local data; Preferably, the sequence number that the sequence number of described more new data equals described local data adds 1;
Replacement module 605, for replacing described local data with described more new data, replaces the sequence number of described local data with the sequence number of described more new data, and sends user data synchronization and be updated successfully response message;
Second sending module 606, for when not allowing to upgrade, sending described renewal flag bit and notifying not allow to upgrade.
Data synchronization updating system described in the present embodiment can reach following technique effect by above-mentioned modules:
First, the present embodiment upgrades flag bit by increasing in the local data of HSS system, upgrading, allowing, when upgrading, the sequence number of local data is sent to AS, carrying out the synchronized update of data for identifying current whether permission.Accordingly, first AS obtains renewal by transmission user data requests, when described flag bit is when allowing renewal, then sends user data update request further, when described flag bit is when not allowing renewal, then will resends user data requests and obtain renewal.The embodiment of the present application ensure that the reliability of data synchronization updating by above-mentioned processing procedure, when for the multiple threads in multiple business or same operation system, request msg upgrades simultaneously, can ensure synchronously, exactly to perform between each business or thread.
Secondly, during due to the request msg renewal simultaneously of the multiple threads in multiple business or same operation system, can synchronously, exactly perform between each business or thread, therefore, AS will receive Data Update success response, and do not need to repeat PUR order more new data again, thus improve wasting of resources situation.
Again, increase and upgrade after flag bit in the local data of HSS system, whether AS system can described renewal flag bit that more new data can be returned by HSS system judge, more friendly for interface definition.
With reference to Fig. 7, show the structured flowchart of the synchronous updating system of a kind of data described in the embodiment of the present application four, described system comprises:
First receiver module 701, for receiving user data requests, carries zone bit information in described user data requests;
Judge module 702, during for representing that when described zone bit information acquisition upgrades, judges whether the local renewal flag bit preserved is allow renewal;
First sending module 703, for when allowing to upgrade, sends the sequence number of described renewal flag bit and local data;
First modified module 704, for send described renewal flag bit and local data at the first sending module sequence number after, described renewal flag bit is revised as and does not allow to upgrade;
Second receiver module 705, for receiving user data update request, described user data update request comprises the sequence number of more new data and more new data, and the sequence number of described more new data calculates based on the sequence number of described local data; Preferably, the sequence number that the sequence number of described more new data equals described local data adds 1;
Comparison module 706, for replacing described local data at the described more new data of replacement module, before replacing the sequence number of described local data with the sequence number of described more new data, the sequence number of more new data described in whether the sequence number of more described local data is less than, if so, then described replacement module performs described replacement;
Replacement module 707, for replacing described local data with described more new data, replaces the sequence number of described local data with the sequence number of described more new data, and sends user data synchronization and be updated successfully response message;
Second modified module 708, after being updated successfully response message in replacement module transmission user data synchronization, being revised as described renewal flag bit and allowing to upgrade;
Second sending module 709, for when not allowing to upgrade, sending described renewal flag bit and notifying not allow to upgrade.
In the present embodiment, HSS upgrades flag bit by real time modifying, in the data synchronization updating process of current AS and HSS, do not allow other AS more new data, and after current AS and HSS data synchronization updating success, renewal flag bit is revised as and allows to upgrade, ensure that the data synchronization updating process of each AS and HSS can be successful, further increase the reliability of data synchronization updating.
For system embodiment, due to itself and embodiment of the method basic simlarity, so description is fairly simple, relevant part illustrates see the part of embodiment of the method.
Each embodiment in this specification all adopts the mode of going forward one by one to describe, and what each embodiment stressed is the difference with other embodiments, between each embodiment identical similar part mutually see.
The application can describe in the general context of computer executable instructions, such as program module.Usually, program module comprises the routine, program, object, assembly, data structure etc. that perform particular task or realize particular abstract data type.Also can put into practice the application in a distributed computing environment, in these distributed computing environment (DCE), be executed the task by the remote processing devices be connected by communication network.In a distributed computing environment, program module can be arranged in the local and remote computer-readable storage medium comprising memory device.
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 specification all belongs to preferred embodiment, and involved action and module might not be that the present invention is necessary.
Finally, also it should be noted that, in this article, the such as relational terms of first and second grades and so on is only used for an entity or operation to separate with another entity or operating space, and not necessarily requires or imply the relation that there is any this reality between these entities or operation or sequentially.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thus make to comprise the process of a series of key element, method, commodity or equipment and not only comprise those key elements, but also comprise other key elements clearly do not listed, or also comprise by the intrinsic key element of this process, method, commodity or equipment.When not more restrictions, the key element limited by statement " comprising ... ", and be not precluded within process, method, commodity or the equipment comprising described key element and also there is other identical element.
Above to synchronous updating method and the system of a kind of data that the application provides, be described in detail, apply specific case herein to set forth the principle of the application and execution mode, the explanation of above embodiment is just for helping method and the core concept thereof of understanding the application; Meanwhile, for one of ordinary skill in the art, according to the thought of the application, all will change in specific embodiments and applications, in sum, this description should not be construed as the restriction to the application.
Claims (6)
1. a synchronous updating method for data, is characterized in that, comprising:
Receive user data requests, in described user data requests, carry zone bit information;
When described zone bit information represents that acquisition upgrades, judge whether the local renewal flag bit preserved is allow renewal;
Upgrade if allow, then send the sequence number of described renewal flag bit and local data; After the sequence number sending described renewal flag bit and local data, described renewal flag bit is revised as and does not allow to upgrade;
Receive user data update request, described user data update request comprises the sequence number of more new data and more new data, and the sequence number of described more new data calculates based on the sequence number of described local data;
Replace described local data with described more new data, replace the sequence number of described local data with the sequence number of described more new data, and send user data synchronization and be updated successfully response message;
Described renewal flag bit is revised as and allows to upgrade;
Upgrade if do not allow, then send described renewal flag bit and notify not allow to upgrade.
2. method according to claim 1, is characterized in that, is replacing described local data with described more new data, before replacing the sequence number of described local data, also comprises with the sequence number of described more new data:
The sequence number of more new data described in whether the sequence number of more described local data is less than, if so, then performs described replacement.
3. method according to claim 1, is characterized in that, the sequence number that the sequence number of described more new data equals described local data adds 1.
4. a synchronous updating system for data, is characterized in that, comprising:
First receiver module, for receiving user data requests, carries zone bit information in described user data requests;
Judge module, during for representing that when described zone bit information acquisition upgrades, judges whether the local renewal flag bit preserved is allow renewal;
First sending module, for when allowing to upgrade, sends the sequence number of described renewal flag bit and local data;
First modified module, for send described renewal flag bit and local data at the first sending module sequence number after, described renewal flag bit is revised as and does not allow to upgrade;
Second receiver module, for receiving user data update request, described user data update request comprises the sequence number of more new data and more new data, and the sequence number of described more new data calculates based on the sequence number of described local data;
Replacement module, for replacing described local data with described more new data, replaces the sequence number of described local data with the sequence number of described more new data, and sends user data synchronization and be updated successfully response message;
Second modified module, after being updated successfully response message in replacement module transmission user data synchronization, being revised as described renewal flag bit and allowing to upgrade;
Second sending module, for when not allowing to upgrade, sending described renewal flag bit and notifying not allow to upgrade.
5. system according to claim 4, is characterized in that, also comprises:
Comparison module, for replacing described local data at the described more new data of replacement module, before replacing the sequence number of described local data with the sequence number of described more new data, the sequence number of more new data described in whether the sequence number of more described local data is less than, if so, then described replacement module performs described replacement.
6. system according to claim 4, is characterized in that, the sequence number that the sequence number of described more new data equals described local data adds 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210222616.4A CN102801782B (en) | 2012-06-28 | 2012-06-28 | A kind of synchronous updating method of data and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210222616.4A CN102801782B (en) | 2012-06-28 | 2012-06-28 | A kind of synchronous updating method of data and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102801782A CN102801782A (en) | 2012-11-28 |
| CN102801782B true CN102801782B (en) | 2015-12-02 |
Family
ID=47200742
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210222616.4A Active CN102801782B (en) | 2012-06-28 | 2012-06-28 | A kind of synchronous updating method of data and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102801782B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103491137A (en) * | 2013-09-02 | 2014-01-01 | 用友软件股份有限公司 | Data synchronizing system and data synchronizing method |
| CN105744617B (en) * | 2016-02-25 | 2020-01-14 | 普兴移动通讯设备有限公司 | Synchronization method and device |
| CN106961426B (en) * | 2017-03-09 | 2020-04-24 | 深圳创维－Rgb电子有限公司 | Communication method and device of intelligent equipment |
| CN107479781A (en) * | 2017-07-20 | 2017-12-15 | 努比亚技术有限公司 | A kind of update method and terminal of application icon color |
| CN108509689A (en) * | 2018-03-09 | 2018-09-07 | 南京信息工程大学 | A kind of electrical figure dynamic creation method towards intelligent substation |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1919129A1 (en) * | 2006-10-31 | 2008-05-07 | Huawei Technologies Co., Ltd. | Method and system for synchronizing network management topology data |
| CN101316256A (en) * | 2007-05-28 | 2008-12-03 | 微码（北京）移动技术有限公司 | Data updating method |
| CN101527835A (en) * | 2009-04-13 | 2009-09-09 | 中兴通讯股份有限公司 | Method for transmitting mobile multimedia broadcasting program message and corresponding device |
| CN102024040A (en) * | 2010-12-08 | 2011-04-20 | 北京握奇数据系统有限公司 | Database synchronization method, device and system |
-
2012
- 2012-06-28 CN CN201210222616.4A patent/CN102801782B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1919129A1 (en) * | 2006-10-31 | 2008-05-07 | Huawei Technologies Co., Ltd. | Method and system for synchronizing network management topology data |
| CN101316256A (en) * | 2007-05-28 | 2008-12-03 | 微码（北京）移动技术有限公司 | Data updating method |
| CN101527835A (en) * | 2009-04-13 | 2009-09-09 | 中兴通讯股份有限公司 | Method for transmitting mobile multimedia broadcasting program message and corresponding device |
| CN102024040A (en) * | 2010-12-08 | 2011-04-20 | 北京握奇数据系统有限公司 | Database synchronization method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102801782A (en) | 2012-11-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102801782B (en) | A kind of synchronous updating method of data and system | |
| CN110311983B (en) | Service request processing method, device and system, electronic equipment and storage medium | |
| EP3060018B1 (en) | Registration method and system for common service entity | |
| CN109542865A (en) | Distributed cluster system configuration file synchronous method, device, system and medium | |
| CN109522363B (en) | Cloud platform synchronization method, system, equipment and storage medium based on block chain | |
| CN109451032B (en) | Message transmission system | |
| CN104199957A (en) | Redis universal agent implementation method | |
| CN110795503A (en) | Multi-cluster data synchronization method and related device of distributed storage system | |
| CN109547524B (en) | User behavior storage method, device, equipment and storage medium based on Internet of things | |
| CN111399764B (en) | Data storage method, data reading device, data storage equipment and data storage medium | |
| US20150088995A1 (en) | Method and apparatus for sharing contents using information of group change in content oriented network environment | |
| EP2723017A1 (en) | Method, apparatus and system for implementing distributed auto-incrementing counting | |
| CN110389935A (en) | A kind of method, equipment and computer storage medium starting small routine | |
| CN102917012A (en) | Storage and communication de-duplication | |
| CN113691635A (en) | Method and device for calling micro service, electronic equipment and readable storage medium | |
| CN111510480A (en) | Request sending method and device and first server | |
| CN109542841A (en) | The method and terminal device of data snapshot are created in cluster | |
| CN110798358A (en) | Distributed service identification method and device, computer readable medium and electronic equipment | |
| CN113420400B (en) | Routing relation establishment method, request processing method, device and equipment | |
| CN112738153B (en) | Gateway selection method, system, device, server and medium in service system | |
| CN104602047A (en) | Share method of EPG (error pattern generator) data, server, terminal and system | |
| CN114090687A (en) | Data synchronization method and device | |
| CN111083192B (en) | Data consensus method and device and electronic equipment | |
| CN111581032B (en) | Method, device, equipment and storage medium for operating data and rolling back data | |
| US20240152504A1 (en) | Data interaction method, apparatus, and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |