CN1691667A - Method for implementing inter-system data synchronization - Google Patents
Method for implementing inter-system data synchronization Download PDFInfo
- Publication number
- CN1691667A CN1691667A CN 200410037024 CN200410037024A CN1691667A CN 1691667 A CN1691667 A CN 1691667A CN 200410037024 CN200410037024 CN 200410037024 CN 200410037024 A CN200410037024 A CN 200410037024A CN 1691667 A CN1691667 A CN 1691667A
- Authority
- CN
- China
- Prior art keywords
- resource
- sign
- synchrolock
- data
- synchronous
- 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
Images
Abstract
The invention discloses method to synchronize system data, which is: the first system applies synchronous resource to the second system by request message of SNMP; if failure, end the application or continue; or else obtain the mastery of the resource and block other application; then the first system sends synchronous startup request to the second system, and carries address to receive synchronous data for first system in request; according to address mentioned, the second system builds connection to the first system by TCP, and takes the data synchronous operation from the connection; when synchronous operation ends, the first system releases resource aforementioned, the second system brings synchronous result.
Description
Technical field
The present invention relates to the communication technology, relate in particular to a kind of method that realizes that inter-system data is synchronous.
Background technology
Because network management system is very complicated, therefore, adopts the multi-zone supervision way usually, promptly network management system is divided into: Network Element Layer, NE management layer, Sub-Network Management Layer, NML, SML and transaction management layer.The most of Simple Network Management Protocol (snmp protocol) that adopts of upper and lower level system interface, this agreement is generally based on user datagram (UDP) host-host protocol.Therefore, come synchronous the superior and the subordinate system data based on snmp protocol, arrival, data traffic are difficult to problems such as control and cancellation synchronously according to the order of sequence then can to produce synchrodata packet loss, packet.Adopt multiplayer system structure, therefore the situation that also exists a following level system to be managed by a plurality of superior system, needs to solve how to prevent that a plurality of superior system are provided with down level system and cause the inconsistent problem of data.
Mainly come synchrodata between system at present by following several method:
Method one, the synchronous mass data of employing SNMP Inform; Promptly adopt the protocol data bag type of SNMP, have to send bag and corresponding respond packet, send bag if receive respond packet then confirm that the other side has received.Owing to adopt bag of the every transmission of this method all to need wait acknowledge, therefore have inefficient shortcoming.
Method two, Query Result is kept in the management information bank (mib) of subordinate's webmaster, waits for that superior system obtains.This method not only needs to take a large amount of internal memories, and data that can not expression data structure more complicated, and efficient is also lower.
Method three, SNMP promptly replace udp protocol with Transmission Control Protocol based on ICP/IP protocol, thereby guarantee the reliable of transfer of data.This method is utilized special SNMP API, requires system of the superior and the subordinate all need therefore, not only require relatively harshness, and versatility be poor based on the SNMP of TCP/IP.
Method four, employing trap synchrodata.Promptly adopt the protocol data bag type of SNMP, have only the bag of transmission not have respond packet, there is lost data packets in this method, the shortcoming of restive flow, thereby it is synchronous to satisfy mass data.
Summary of the invention
The invention provides a kind of method that realizes that inter-system data is synchronous, exist or inefficiency to solve in the prior art, otherwise the versatility difference and require harsh, or have the data packet loss, flow is restive and data cover problem.
For addressing the above problem, the invention provides following technical scheme:
A kind of method that realizes that inter-system data is synchronous communicates by Simple Network Management Protocol (SNMP) between described system; It is characterized in that this method comprises the steps:
Request message among A, the employing SNMP of first system is to second system application isochronous resources; If apply for successfully, then obtain the control of this resource and block this resource of other system application, continue step B, otherwise finish application or continuation application;
B, first system send to second system and begin request and the address of carrying first system's receiving isochronous data in this request synchronously;
C, second system connect with first system by transmission control protocol (TCP) according to described address, and carry out the data synchronization operation by this connection and first system; And
D, after simultaneous operation finishes, discharge described resource by first system, and generate synchronized result by second system.
Wherein:
Steps A comprises:
A1, first system are to second system request synchrolock sign and occupation condition;
A2, second system judge whether the time that takies resource is overtime, if not overtime, then directly return synchrolock sign and occupation condition to first system, otherwise discharge this resource, and return synchrolock sign and occupation condition to first system;
A3, first system judge according to the return messages of second system whether resource is occupied, if, ending request or return steps A 1 then, otherwise carry out steps A 4;
A4, the utilization of first system need take the time of resource and the synchrolock sign of acquisition is provided with second system;
A5, second system judge whether the current synchrolock sign of native system is identical with the synchrolock sign that receives, if identical then permission is provided with, second system increases 1 with the value of this synchrolock sign, and be set and first system need take the resource time the synchronous time started, and return to first system success message is set; Otherwise do not allow to be provided with and return failed message is set to first system.
Also establish a synchronous regime sign in second system, first system can be provided with this sign during data sync, and second system then identifies the simultaneous operation that decides next step according to this synchronous regime in data sync in the cycle.
Simultaneous operation finishes back release resource and comprises step:
The synchrolock sign that D1, first system obtain before with simultaneous operation increases by 1, and the time that needs take resource is set to 0;
D2, time and the synchrolock sign of utilizing described needs to take resource are provided with second system;
D3, second system judge whether the current synchrolock sign of native system is identical with the synchrolock sign that receives, if identical then permission is provided with, second system of system need take the resource time and be set to 0 discharging resource, and returns to first system success message is set; Otherwise do not allow to be provided with and return failed message is set to first system.
The present invention has following beneficial effect:
1, the present invention utilizes general snmp protocol to carry out the inquiry and the setting operation of general small data quantity, but for the transmission of big data quantity, adopts Transmission Control Protocol to carry out, and guarantees the reliable and efficient of big transfer of data; Avoid the unreliable and inefficient of simple SNMP big data quantity transmission like this, avoided utilizing specific (special) requirements again based on the snmp protocol of TCP.
2, the present invention passes through the application resource and block the request of other system to this resource during simultaneous operation before upper and lower level synchrodata, thereby can carry out data sync reliably, the problem of having avoided a plurality of superior system that following level system is provided with and having caused data to be capped is consistent data.
3, after with EOS, generate synchronized result, wait for the superior system inquiry, make that system of the superior and the subordinate can parallel processing task separately.
4, by synchronous regime is set, may command simultaneous operation, thereby the present invention can support functions such as synchronous cancellation, wait and recovery, and support synchrodata to appointed positions, needn't with the same process of superior system.
Description of drawings
Fig. 1 is the hierarchy schematic diagram of network management system;
Fig. 2 is a flow chart of the present invention.
Embodiment
The present invention adopts the setting (Set) among the SNMP and obtains session control between (Get) request realization system, when first system needs synchronously specific data, adopts Get and Set request to second system application isochronous resources; If application failure then finish application or continuation application if apply for successfully, then obtains the control of resource and blocks this resource of other system application; Begin request synchronously to the transmission of second system then, set up TCP SOKET by second system and first system and be connected, and carry out the data synchronization operation by this connection and superior system; Finish the resource of back release busy and generate synchronized result in simultaneous operation, first system determines whether synchronous success by the inquiry synchronized result.
Below with the network management system among Fig. 1 be example the present invention is described in detail, wherein, first system is corresponding to superior system, second system is for level system down (management level i.e. a system).
Consult shown in Figure 2ly, concrete handling process is as follows
Step 10: when superior system is wished synchronously specific data, the appropriate tasks of at first downward level system (or claiming row, the corresponding task of row) getrequest message of transmission asks current synchrolock sign (syncLock) of this task and resource to need the value of occupied time (syncTimeOut).
Wherein, synchrolock sign (syncLock) is used for the recognition data current situation of calling synchronously.The time of resource (syncTimeOut) is used to represent that superior system need occupy the time of resource, and unit can be second.
Step 20: following level system judges whether the time that takies resource is overtime, if it is not overtime, then directly return the value of syncLock and syncTimeOut to superior system, if it is overtime, then syncTimeOut is set to 0 and promptly discharges this resource, and returns the value of syncLock and syncTimeOut to superior system.
Following level system is according to the current time in system (sysUpTime.0)-whether the time started (syncStartTime) judges greater than syncTimeOut whether resource occupation is overtime synchronously; If greater than, syncTimeOut=0 then is set, occupy this resource to prevent that superior system is long-term unusually, otherwise do not change the original value of syncTimeOut.
Wherein, the time started (syncStartTime) is used to represent the superior system application resource time started synchronously.
Step 30: superior system judges whether the syncTimeOut that obtains equals 0, if then continue step 40; Otherwise return step 10, continue to send GetRequest and test, equal till 0 up to syncTimeOut.
Step 40: resource was unoccupied when the syncTimeOut of this row equaled 0 expression request, superior system just sends a SetRequest message, the syncLock value that the value K of the syncLock that has just obtained with it is provided with down this object instance in the level system is K, and syncTimeOut value in the level system is set down with the time that superior system need take resource.
Step 50: the task in the following level system judges whether current syncLock value is identical with the syncLock value that the superior system request that receives is provided with.
If identical (illustrating does not have other system to get involved this resource in the meantime) then is provided with success, following level system syncLock value increases progressively 1; SyncTimeOut is set to time that superior system need take resource and blocks the request of its system; The value of also synchronous time started (syncStartTime) is set to the current time in system (sysUpTime.0) simultaneously, and synchronous address (syncIpAddr) and synchronous port (syncIpPort) be set, superior system just temporarily has the ownership of this row like this, has the value that the time is syncTimeOut.
(illustrate in the meantime existing other system get involved this resource) if inequality, then request is provided with failure.
This superior system has been retrieved syncLock and has been attempted being set to same value, is not only having under the intervention situation of other system success to be set.
Step 60: superior system is provided with the querying condition and the overanxious rule of subordinate's synchronize data of system by SetRequest message.
Step 70: the IP port (syncIpPort) that the IP address (syncIpAddr) of the downward level system transmission of superior system receiving isochronous data is connected with the listening port higher level, and the value of descending the synchronous regime (syncStatus) of level system is set to initial state and begins synchronously, waits for that down level system carries out Socket and connects: promptly call SyncAPI::listen (syncIpPort).
Wherein, synchronous regime (syncStatus) is used to control simultaneous operation, and following level system determines next step operation according to the value of this synchronous regime, and value can be:
(1) abandons synchronously: abort (0)
(2) beginning synchronously: start (1)
(3) wait for synchronously: wait (2)
(4) carry out synchronously in or recover synchronously: continue (3)
(5) same EOS: stop (4)
Step 80: following level system receives and begins request synchronously, during synchronized result (syncResult) is set to carry out synchronously (inProgress (1)), and initiatively carries out TCP socket with superior system and is connected.
Use Transmission Control Protocol, just can carry out flow control and avoid the data packet loss.
Step 90: after following level system is successfully set up the socket connection, during synchronous regime (syncStatus) is set to carry out synchronously (continue (3)), and according to synchronous query condition and overanxious rule, synchrodata SyncAPI::sendVBList (vbs, vbcount); Superior system then receives down the data that level system sends.
The value of following level system cyclic check syncStatus in data sync decides next step simultaneous operation, and superior system can end, suspend or continue data sync by the value that syncStatus is set.
Step 100: after following system synchronization finishes, disconnect socket and connect, promptly call SyncAPI::close (), and synchronized result (syncResult) is set.
Possible same frequency end value is as follows:
Success: success (0);
There is not data sync: notData (2);
Abandoned synchronously: abort (3);
Synchronization failure: failed (4);
Following level system can not be carried out: unAbletoRun (5);
Following level system is not supported syncType wheel synchronization type: unSupported (7).
Simultaneously, but also generating run result's detailed description (syncCode).
Step 110: superior system retrieval syncResult and syncCode.Can determine whether synchronous success according to syncResult.
Step 120: the downward level system of superior system sends a SetRequest message, with syncLock=K+1, and syncTimeOut=0, if success is set, then expression abandons having the ownership of isochronous resources, and shows that this is subsynchronous effectively.
If first system and second system take place unusual in the synchrodata process and make first system not discharge the resource of being applied for, then second system according to circumstances discharges this resource automatically, to prevent that resource from being taken unusually.
Though below be example with the network management system, the present invention is not limited only to this, the present invention can be widely used in based on the data sync of carrying out big data between the system of SNMP.
Claims (7)
1, a kind of method that realizes that inter-system data is synchronous communicates by Simple Network Management Protocol (SNMP) between described system; It is characterized in that this method comprises the steps:
Request message among A, the employing SNMP of first system is to second system application isochronous resources; If apply for successfully, then obtain the control of this resource and block this resource of other system application, continue step B, otherwise finish application or continuation application;
B, first system send to second system and begin request and the address of carrying first system's receiving isochronous data in this request synchronously;
C, second system connect with first system by transmission control protocol (TCP) according to described address, and carry out the data synchronization operation by this connection and first system; And
D, after simultaneous operation finishes, discharge described resource by first system, and generate synchronized result by second system.
2, the method for claim 1 is characterized in that, steps A comprises:
A1, first system are to second system request synchrolock sign and occupation condition;
A2, second system judge whether the occupied time of its resource is overtime, if not overtime, then directly return synchrolock sign and occupation condition to first system, otherwise discharge this resource, and return synchrolock sign and occupation condition to first system;
A3, first system judge according to the return messages of second system whether resource is occupied, if, ending request or return steps A 1 then, otherwise carry out steps A 4;
A4, the utilization of first system need take the time of resource and the synchrolock sign of acquisition is provided with second system;
A5, second system judge whether the current synchrolock sign of native system is identical with the synchrolock sign that receives, if identical then permission is provided with, second system increases 1 with the value of this synchrolock sign, and be set and first system need take the resource time the synchronous time started, and return to first system success message is set; Otherwise do not allow to be provided with and return failed message is set to first system.
3, the method for claim 1 is characterized in that, carries out before the step B, and first system also is provided with the querying condition and/or the filtering rule of second synchronize data of system, and second system then is provided with synchrodata according to this.
4, the method for claim 1, it is characterized in that, in second system, also establish a synchronous regime sign, first system can be provided with this sign during data sync, and second system then identifies the simultaneous operation that decides next step according to this synchronous regime in data sync in the cycle.
5, the method for claim 1 is characterized in that, second system also generates simultaneous operation result's detailed description.
6, the method for claim 1 is characterized in that, simultaneous operation finishes back release resource and comprises step:
The synchrolock sign that D1, first system obtain before with simultaneous operation increases by 1, and the time that needs take resource is set to 0;
D2, time and the synchrolock sign of utilizing described needs to take resource are provided with second system;
D3, second system judge whether the current synchrolock sign of native system is identical with the synchrolock sign that receives, if identical then permission is provided with, second system of system need take the resource time and be set to 0 discharging resource, and returns to first system success message is set; Otherwise do not allow to be provided with and return failed message is set to first system.
7, the method for claim 1, it is characterized in that, if first system and second system take place unusual in the synchrodata process and make first system not discharge the resource of being applied for, then second system according to circumstances discharges this resource automatically to prevent that resource from being taken unusually.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200410037024 CN1691667A (en) | 2004-04-21 | 2004-04-21 | Method for implementing inter-system data synchronization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200410037024 CN1691667A (en) | 2004-04-21 | 2004-04-21 | Method for implementing inter-system data synchronization |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1691667A true CN1691667A (en) | 2005-11-02 |
Family
ID=35346793
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200410037024 Pending CN1691667A (en) | 2004-04-21 | 2004-04-21 | Method for implementing inter-system data synchronization |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1691667A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107797896A (en) * | 2017-06-16 | 2018-03-13 | 平安科技（深圳）有限公司 | A kind of data on flows self- recoverage processing method and server |
| CN107959658A (en) * | 2016-10-17 | 2018-04-24 | 北京视联动力国际信息技术有限公司 | A kind of Web conference method of data synchronization and its system |
-
2004
- 2004-04-21 CN CN 200410037024 patent/CN1691667A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107959658A (en) * | 2016-10-17 | 2018-04-24 | 北京视联动力国际信息技术有限公司 | A kind of Web conference method of data synchronization and its system |
| CN107959658B (en) * | 2016-10-17 | 2019-04-26 | 视联动力信息技术股份有限公司 | A kind of Web conference method of data synchronization and its system |
| CN107797896A (en) * | 2017-06-16 | 2018-03-13 | 平安科技（深圳）有限公司 | A kind of data on flows self- recoverage processing method and server |
| US11770199B2 (en) | 2017-06-16 | 2023-09-26 | Ping An Technology (Shenzhen) Co., Ltd. | Traffic data self-recovery processing method, readable storage medium, server and apparatus |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1297078C (en) | Reconnecting a CDMA2000 high speed packet data service from dormant state | |
| CN101079742A (en) | Data synchronization method and system between disaster tolerance home user servers | |
| CN1309233C (en) | Method for supporting PPPoA on wideband switch-in equipment | |
| CN1993961A (en) | Method and device for session control in hybrid telecommunication networks | |
| CN1855916A (en) | Method and system for realizing virtual IP protocol | |
| CN1281080C (en) | Method for realeasing terminal resource in media gateway | |
| CN1949203A (en) | Architecture of interface target machine for miniature computer system and data transmitting method | |
| CN101039263A (en) | Method for processing node overload of core network and mobile switch equipment and communication system | |
| CN1527539A (en) | Long-distance switching-in server with quantity of logic chain-circuit source greater than physical chain-circuit source | |
| CN1567835A (en) | Distributed cluster service management system and service management method in intelligent network | |
| CN101068147A (en) | Method for controlling establishment of terminal connection in network communication | |
| CN1691667A (en) | Method for implementing inter-system data synchronization | |
| CN1886994A (en) | Method and apparatus for efficient simultaneous re-activation of multiple dormant service instances in a CDMA2000 network | |
| CN1968097A (en) | Method and system for device registration | |
| CN1642167A (en) | Method for main node supporting different agreement type secondary unit apparatus on secondary node | |
| CN1558626A (en) | Method for realizing group control function by means of network processor | |
| CN1859251A (en) | Method for realizing communication unit interconnection | |
| CN101035024A (en) | Method for processing the batch configuration and network management device and network system | |
| CN1941733A (en) | Method for grouped issuing message in grouped telecommunication | |
| CN1520209A (en) | General connecting device and method utilized to down load version of base station and manintain not elemonts in centralization | |
| CN1798413A (en) | Method for building remote maintenance channel | |
| CN1870628A (en) | Network equipment and service transmission method for raising reliability of communication system | |
| CN1905562A (en) | Method for determining need configurating link protocol of marginal apparatus serial slot | |
| CN1725720A (en) | Radio link procedure management method in Iub interface | |
| CN101056282A (en) | Implementation method, device and system of the random channel signaling under the H.248 separated architecture |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |