CN109672712A - Method of data synchronization, device, super controller, domain controller and storage medium - Google Patents
Method of data synchronization, device, super controller, domain controller and storage medium Download PDFInfo
- Publication number
- CN109672712A CN109672712A CN201710967367.4A CN201710967367A CN109672712A CN 109672712 A CN109672712 A CN 109672712A CN 201710967367 A CN201710967367 A CN 201710967367A CN 109672712 A CN109672712 A CN 109672712A
- Authority
- CN
- China
- Prior art keywords
- data
- change log
- data change
- synchronized
- domain controller
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the present invention provides a kind of method of data synchronization, device, super controller, domain controller and storage medium, by the way that the data change log for recording object to be synchronized is arranged, when the data for presetting object to be synchronized on domain controller change, the modification information for presetting object to be synchronized is recorded in data change log；Super controller obtains data change log to be synchronized from domain controller, data change log according to the data change log of acquisition to the domain controller in local terminal synchronizes, and processing is synchronized based on data of the data change log after synchronizing to corresponding object to be synchronized, it does not need for all data on domain controller to be synchronized in super controller, synchronous redundant data can be greatly reduced, the synchronous efficiency of data and practicability are promoted, and improves the flexibility of data synchronously control.
Description
Technical field
The present invention relates to the communications field more particularly to a kind of method of data synchronization, device, super controller, domain controllers
And storage medium.
Background technique
Under SDN (Software Defined Network, software defined network) framework, by controller to telecommunications network
Network is managed, and controller can, controller different according to demand by tree-shaped stratification tissue, to be associated with large scale network
It is layered, is typically divided into upper layer and lower layer.The direct managed network element of lower layer is domain controller (Domain
Controller can be abbreviated as D-Controller or D-C), the controller on upper layer is super controller (Super
Controller can be abbreviated as S-Controller or S-C), the not direct managed network element of super controller, but manage multiple domains
Controller realizes the inter domain management to practical catenet.
In real network management, the range and emphasis of the domain controller management of the super controller and lower layer on upper layer are
Difference, super controller pays close attention to cross-domain service, the direct managed network element of domain controller, and carries out service management in this controller area.
Between super controller and domain controller, need to carry out real time data to basic resource object such as network element, link and business same
Step, is just able to achieve the integrated management of network.It is traditional that the data synchronization mechanism of super controller and domain controller, which uses, at present
Network Management System (Network Management System, NMS) and Element management system (Element Management
System, EMS) data synchronization mechanism, data all on domain controller directly synchronize up, are then passed through again by super controller
Automatic discovery calculating etc. realizes that super controller is synchronous with the data of domain controller.And in real network management, network may
It is very big, there are tens of thousands of a network element nodes, tens of thousands of links, hundreds of thousands of business, this results in the data item on domain controller non-
The redundant data that super controller is not concerned with can be also synchronized in super controller by Chang Duo, above-mentioned synchronization mechanism, be reduced same
The efficiency and practicability of step.
Summary of the invention
A kind of method of data synchronization, device, super controller, domain controller and storage provided in an embodiment of the present invention are situated between
Matter, mainly solving the technical problems that: the data synchronization mechanism between existing super controller and domain controller can be by super control
The redundant data that device processed is not concerned with is synchronized in super controller, and synchronous efficiency and practicability are low.
In order to solve the above technical problems, the embodiment of the present invention provides a kind of method of data synchronization, comprising:
Obtain data change log to be synchronized from domain controller, the data change log for record preset it is to be synchronized
The modification information of object；
Data change log according to the data change log of acquisition to the domain controller in local terminal synchronizes processing；
According to the modification information in the data change log after local terminal synchronization process to the data of corresponding object to be synchronized into
Row synchronization process.
The embodiment of the present invention also provides a kind of method of data synchronization, comprising:
When the data for presetting object to be synchronized on domain controller change, it is default that this is recorded in data change log
The modification information of object to be synchronized；
The data change log is issued to the super controller on upper layer.
The embodiment of the present invention also provides a kind of data sync control device, comprising:
Log acquisition module, for obtaining data change log to be synchronized, the data change log from domain controller
For recording the modification information for presetting object to be synchronized；
Synchronization control module, the data for the data change log according to acquisition to the domain controller in local terminal change
Log synchronizes processing, and according to the modification information in the data change log after local terminal synchronization process to corresponding to be synchronized
The data of object synchronize processing.
The embodiment of the present invention also provides a kind of data synchronous maintenance device, comprising:
Log maintenance module, when being changed for the data for presetting object to be synchronized on domain controller, in data
The modification information for presetting object to be synchronized is recorded in change log；
Sending module, for the data change log to be issued to the super controller on upper layer.
The embodiment of the present invention also provides a kind of super controller, and the super controller includes first processor, first deposits
Reservoir and the first communication bus；
First communication bus is for realizing the connection communication between first processor and first memory；
The first processor is for executing one or more first program stored in first memory, to realize such as
Above the step of method of data synchronization.
The embodiment of the present invention also provides a kind of domain controller, and the domain controller includes second processor, second memory
And second communication bus；
Second communication bus is for realizing the connection communication between second processor and second memory；
The second processor is for executing one or more second program stored in second memory, to realize such as
Above the step of method of data synchronization.
The embodiment of the present invention also provides a kind of computer storage medium, and the computer-readable recording medium storage has one
Or multiple first programs, one or more of first programs are executed by one or more processor, it is as above to realize
The step of described method of data synchronization；
Or,
The computer-readable recording medium storage has one or more the second program, and one or more of second
Program is executed by one or more processor, the step of to realize method of data synchronization as described above.
The beneficial effects of the present invention are:
Method of data synchronization, device, super controller, domain controller and the storage provided according to embodiments of the present invention is situated between
Matter, the data for presetting object to be synchronized by the way that the data change log for recording object to be synchronized is arranged, on domain controller
When changing, the modification information for presetting object to be synchronized is recorded in data change log；Super controller can be from domain
Controller obtains data change log to be synchronized, according to the data change log of acquisition to the domain controller local terminal data
Change log synchronizes, and synchronizes place based on data of the data change log after synchronizing to corresponding object to be synchronized
Reason.Namely the super controller in the present invention and it can be preset between domain controller and need synchronous object, and pass through data
Change log records using the foundation synchronous as follow-up data, when follow-up data is synchronous only the alteration of these objects
It need to synchronize, not need all data on domain controller are all synchronous for the object to be synchronized in data change log
Onto super controller, synchronous redundant data can be greatly reduced, promote the synchronous efficiency of data and practicability, and improve
The flexibility of data synchronously control.
Other features of the invention and corresponding beneficial effect are described in the aft section of specification, and should be managed
Solution, at least partly beneficial effect is apparent from from the record in description of the invention.
Detailed description of the invention
Fig. 1 is the method for data synchronization flow diagram of the super controller side of the embodiment of the present invention one；
Fig. 2 is that the first of the embodiment of the present invention one builds phase data synchronous method flow diagram；
Fig. 3 is method of data synchronization flow diagram in the holding link process of the embodiment of the present invention one；
Fig. 4 is the method for data synchronization flow diagram in the chain rupture link re-establishment stage of the embodiment of the present invention one；
Fig. 5 is the method for data synchronization flow diagram of the domain controller side of the embodiment of the present invention one；
Fig. 6 is the data sync control device structural schematic diagram of the embodiment of the present invention three；
Fig. 7 is the data synchronous maintenance apparatus structure schematic diagram of the embodiment of the present invention three；
Fig. 8 is the controller system of the embodiment of the present invention three；
Fig. 9 is the super controller structural schematic diagram in Fig. 8；
Figure 10 is the domain controller structural schematic diagram in Fig. 8.
Specific embodiment
In order to make the objectives, technical solutions, and advantages of the present invention clearer, below by specific embodiment knot
Attached drawing is closed to be described in further detail the embodiment of the present invention.It should be appreciated that specific embodiment described herein is only used to
It explains the present invention, is not intended to limit the present invention.
Embodiment one:
In order to which super controller can be not related to by the data synchronization mechanism solved between existing super controller and domain controller
The redundant data of note is synchronized in super controller, synchronous efficiency and the low problem of practicability, is present embodiments provided a kind of new
Method of data synchronization, it is synchronous which is suitable for data between super controller and domain controller.But it should
Understand, which is not limited to the data being applied between super controller and domain controller and synchronizes, and also fits
It is synchronous for the data between other communication equipments.Method of data synchronization provided in this embodiment is by setting for recording to same
The data change log for walking object can pre-set between super controller and domain controller and need synchronous object,
And it is recorded by alteration of the data change log to these objects using the foundation synchronous as follow-up data, subsequent number
According to it is synchronous when only need to synchronize for the object to be synchronized in data change log, without by the institute on domain controller
There are data to be synchronized in super controller, the redundant data for being not concerned with super controller is avoided to be synchronized to super controller
On, data synchronous efficiency and resource utilization are promoted, and improve the synchronous practicability of data and flexibility.
It should be understood that according to practical application scene demand, the present embodiment is between super controller and domain controller
The mode for presetting object to be synchronized can be flexible and changeable.Such as object to be synchronized can be directly arranged on each domain controller clear
Single, super controller can be obtained from domain controller；It can also flexible configuration waits for according to actual needs in super controller
Then synchronization object inventory is handed down to domain controller, or directly configured in super controller and domain controller it is to be synchronized right
As inventory.When object inventory to be synchronized is arranged, can specifically be configured by middle configuration file, for example including but be not limited to
Xml configuration file, ini configuration file, config configuration file.
It should be understood that the object to be synchronized in the present embodiment between super controller and domain controller can be according to reality
Border demand flexibly sets and changes, such as object to be synchronized may include but be not limited to network element, business, link, interface, according to reality
Demand can increase or decrease object to be synchronized.Such as in a kind of application scenarios, super controller can only focus on network element and
Business, then presetting at this time can only include network element and business in object inventory to be synchronized, without including link and interface, with
The change of application scenarios or other demands, the object to be synchronized preset in object inventory to be synchronized in the present embodiment can be adjusted flexibly
It is whole, therefore can largely promote synchronous flexibility, specific aim and practicability.
It should be understood that being directed to different objects to be synchronized in the present embodiment, the data change log for its setting can
With identical, objects to be synchronized all at this time uses identical data change log.Certainly, for different objects to be synchronized,
Data change log flexibly can also be set for it according to the characteristic of each object to be synchronized itself, set data change log is all
It can should at least record the modification information of object to be synchronized.Modification information in the present embodiment includes but is not limited to change the time, become
Furthermore, specifically at least one of change movement, the specific change movement in the present embodiment include but is not limited to creation, delete
And modification.
Domain controller is after getting object inventory to be synchronized, can be with when a certain object data of local terminal changes
The object to be synchronized whether object belongs in object inventory to be synchronized is judged, if so, then becoming for one data of the object maintenance
More log, specifically can include:
If it is newly creating an object to be synchronized, and the object to be synchronized is currently without corresponding data change log
When, then a data change log is created for it；
It is deleted if it is to the object to be synchronized, then record should be in the data change log of the object to be synchronized
The delete operation of synchronization object；
It modifies if it is to the object to be synchronized, then record should be in the data change log of the object to be synchronized
The modification of synchronization object operates.
Certainly, in application scenes and embodiment, specific change can not also be recorded in data change log is
Creation is deleted or is modified, and the situation of change by super controller directly to data change log and object data to be synchronized
Carry out determining obtain of analysing and comparing.Being specifically chosen which kind of mode can flexibly set.
Based on above-mentioned setting, to facilitate the understanding of the present invention, the present embodiment is controlled separately below with super controller side and domain
The data synchronization process of device processed is illustrated for example.
Shown in Figure 1, a kind of method of data synchronization in super controller side includes:
S101: obtaining data change log to be synchronized from domain controller, as described above, data change log is for recording
Preset the modification information of object to be synchronized.
Communication process between super controller and domain controller keeps chain after generally comprising first link setup, link setup success
It connects, chain rupture, the several processes of link re-establishment after chain rupture.Super controller obtains data change log packet to be synchronized from domain controller
Include the process obtained in above-mentioned several link setup stages.
S102: the data change log according to the data change log of acquisition to the domain controller in local terminal synchronizes
Processing.
S103: according to the modification information in the data change log after local terminal synchronization process to the number of corresponding object to be synchronized
It is handled according to synchronizing.
In order to make it easy to understand, being illustrated below using above-mentioned several link setup stages as example.
After super controller and the first link setup of domain controller, since the absolutely not domain controls in super controller at this time
The data information of log information and object to be synchronized on device obtains data to be synchronized from domain controller at this time and changes day
Will, and according to the data change log of acquisition to the domain controller the data change log of local terminal synchronize processing referring to
Shown in Fig. 2, comprising:
S201: all data change logs on domain controller are obtained.
S202: all data change logs obtained from domain controller are stored in local terminal.
In the present embodiment, (namely the corresponding data of object to be synchronized become the data change log obtained from domain controller
More log) include: the identification information of object to be synchronized, object to be synchronized current log serial number, object to be synchronized change
Information can also flexibly increase other information, such as object data type (such as network element, business etc.) according to application scenarios certainly.
Object to be synchronized often does primary change, and corresponding log serial number is updated to maximum flowing water in current data change log
Number；
All data change logs obtained from domain controller, which are carried out storage in local terminal, at this time includes:
The data change log that will acquire synchronizes storage in local terminal, and is arranged in pieces of data change log and is used for
The consistent coherency state mark of data in the data and domain controller of the corresponding object to be synchronized of characterize data change log.
Namely all has in the pieces of data change log of local terminal storage and be used for the corresponding object to be synchronized of characterize data change log
Data and domain controller on data consistent coherency state mark.
That is, will increase " coherency state mark " column in data change log information in super controller side, it is used for
Whether consistent characterize data of the object to be synchronized in data and domain controller in super controller.In the present embodiment, one
Cause property status indicator includes but is not limited to conflict mark, consistency mark and inconsistent mark.Wherein conflict mark is to indicate super
Grade controller has carried out change operation to a certain object to be synchronized, and the change operation not synchronized on domain controller, unanimously
Property mark show that the data in the data and domain controller of the object to be synchronized in super controller are consistent；It is inconsistent, be
Change operation has been carried out to a certain object to be synchronized on domain controller and has not been synchronized in super controller and changes operation.
When super controller and the first link setup of domain controller, super controller directly acquires all data change logs on domain controller
It synchronizes, and directly synchronizes storage from the data for obtaining object to be synchronized in data change log on domain controller, because
The data of object to be synchronized are consistent on the data of object to be synchronized and domain controller in super controller at this time for this, therefore consistent
Property status indicator is set as " consistent ".
During super controller and domain controller link setup successfully keep link setup, if a certain to be synchronized on domain controller
Change operation has occurred in object, such as newly creates, deletes or be modified, and domain controller is corresponding to the object to be synchronized
Data change log carries out corresponding operation (such as modification information in a newly-built log, log corresponding update etc.) can be to
Super controller sends Notification of Changes.Super controller obtains data change log to be synchronized and root from domain controller at this time
According to acquisition data change log to the data of data change log and object to be synchronized synchronize processing it is shown in Figure 3,
Include:
S301: keeping in link process with domain controller, receives domain controller and becomes in the data of object to be synchronized
The Notification of Changes sent when more.
S302: data change log corresponding with Notification of Changes is obtained from domain controller according to the Notification of Changes received.
S303: the data change log according to the data change log of acquisition to the domain controller in local terminal synchronizes place
Reason, comprising:
The data change log that judgement obtains whether there is in local terminal, if so, more by the original data change log of local terminal
The new data change log to obtain；Otherwise, the data change log that will acquire carries out newly-increased storage in local terminal.
It should be understood that during super controller and domain controller link setup successfully keep link setup, on domain controller
If change operation has occurred in a certain object to be synchronized, Notification of Changes can not also be sent to super controller, and by super control
Device timing is inquired.
It should be understood that when domain controller sends Notification of Changes to super controller in the present embodiment, it can will be specific
Change operation and change data carrying issue super controller together in the notification, such super controller can directly be sent
The data that corresponding change operation and change are extracted in the notice carry out accordingly the data of corresponding log and object to be synchronized
Synchronized update.Certain domain controller can also notify the data for not carrying specific change operation and change, and by super
Controller is inquired on domain controller.
Super controller and domain controller will disconnect link after link setup due to various reasons.In different application scenarios
In, some application scenarios allow data of the super controller during chain rupture to data change log and corresponding object to be synchronized
Change operation, some application scenarios do not allow then super controller during chain rupture to data change log and accordingly to
The data of synchronization object change operation.Domain controller normally monitors object to be synchronized and obtains alteration and to right during chain rupture
The data change log answered normally is safeguarded, such as may will create new object to be synchronized during chain rupture, it is also possible to
The object to be synchronized created before will be deleted, it is also possible to modify to the object to be synchronized created before.
After super controller and domain controller chain rupture again link setup, it can be directly acquired from domain controller all
Data change log, and with local terminal before store be compared, which to be distinguished during chain rupture on local terminal and domain controller
A little data change logs are changed.Can also using to analyze before chain rupture the data change log for the treatment of process no longer into
The efficient process mode of row analysis processing, at this time super controller from domain controller obtain data change log to be synchronized and
Processing institute referring to fig. 4 is synchronized to the data of data change log and object to be synchronized according to the data change log of acquisition
Show,
S401: super controller on the domain controller of key chain, obtains log serial number and is greater than local terminal one from local terminal and again
The data change log of cause property max log serial number.
Consistency maximum serial number in the present embodiment is that local terminal coherency state is identified as consistent all data changes
Maximum log serial number in log.Such as assume that the domain controller that link re-establishment is corresponded in super controller has the change of five datas
More log, and wherein the serial number of a data log is 0006, its consistency status indicator is conflict, remaining four data
The serial number of log is 0001,0003,0004,0005, then is directed to the domain controller, local terminal consistency max log flowing water at this time
Number be 0005.
S402: the data change log according to the data change log of acquisition to the domain controller in local terminal synchronizes
Processing.In the present embodiment, a kind of example process is as follows:
When there is domain controller newly created data change log during chain rupture in the data change log of acquisition, by this
Data change log synchronizes storage in local terminal；
When the data change log for thering is domain controller to modify during chain rupture in the data change log of acquisition, it incite somebody to action this
Corresponding data change log is held to synchronize modification；
When the data change log for thering is local terminal to modify during chain rupture in the data change log of acquisition, using uploading
The Synchronous Principle data of lower layer's domain controller (be subject to) or downloading the Synchronous Principle data of upper layer super controller (be subject to)
Processing is synchronized to the data of object to be synchronized in the data change log and the data change log；Local terminal is in the chain rupture phase
Between modify to some data change log after, by the data change log coherency state mark be set as rushing
It is prominent.
It should be understood that three cases above, which obtains processing sequence, flexibly to be set, such as can be set to first locate
The case where managing above-mentioned first and second kinds of situations, finally handling the third conflict.
In the present embodiment, when modification information includes creation, modification and deletes, according to the data after local terminal synchronization process
Modification information in change log, which synchronizes processing to the data of corresponding object to be synchronized, can use following example processing side
Formula:
When the modification information in the data change log after local terminal synchronization process is creation, obtaining from domain controller should
The data of object to be synchronized in data change log are stored in local terminal；
When the modification information in the data change log after local terminal synchronization process is modification, obtaining from domain controller should
The data of object to be synchronized in data change log are updated the object to be synchronized in the data of local terminal；
It, will be in the data change log when the modification information in the data change log after local terminal synchronization process is to delete
Object to be synchronized deleted in the data of local terminal.
It should be understood that the modification information in data change log in the present embodiment may include the change time, this
When whether more the object to be synchronized in some data change log can be judged according to the change time in data change log
Change (such as creation, modification or deletion), such as the change time is different from the time recorded before, then shows to be changed,
Then the data for obtaining corresponding object to be synchronized are gone to get if change is delete processing from corresponding domain server
For sky；If it is newly created, the data of the unexistent object to be synchronized of local terminal can be got from domain controller；If it is
Modification, then the data of object to be synchronized are got from domain controller, and local terminal also there are corresponding data.Certainly, it more converts to
Breath can also flexibly include other data according to demand.
As above analysis, in the present embodiment for different objects to be synchronized can using identical data change log strategy into
Row management can also be managed using different data change logs.Such as it can be according to the characteristics of object to be synchronized and again
The property wanted distinguishes, and designs different data change log strategies, a kind of example design rules are as follows:
1, infrequently and the relatively stably and controllable object to be synchronized of extremely important, data volume for data change, one to
Synchronization object designs data change log record, and this data change log is referred to as the change of single pair image data in the present embodiment
Log, the object identification information to be synchronized in single pair image data change log are the identification information of single object to be synchronized.It is a kind of
Object to be synchronized in example in single pair image data change log includes at least one of network element, link.
2, for data change frequently, the very big object to be synchronized of data volume, according to sort key information (such as rate,
Type etc.) it distinguishes, it is subdivided into the object to be synchronized of a variety of small types, a kind of one number of object designs to be synchronized of small type
According to change log, this data change log is referred to as multiple object data change log in the present embodiment, and multiple object data changes day
Object identification information to be synchronized in will is the Classification and Identification information (namely above-mentioned sort key information) of object to be synchronized, one
Classification and Identification information corresponds at least one object to be synchronized.
In the present embodiment, when the single pair for including from the data change log to be synchronized obtained on a domain controller
When image data change log item number is more than or equal to preset threshold, single object number is obtained from domain controller using full dose acquisition modes
Processing is synchronized according to the data of the object to be synchronized in change log；Otherwise, it can be controlled using increment synchronization method from the domain
The data that object to be synchronized is obtained on device processed synchronize processing.The specific value of preset threshold can be according to tool in the present embodiment
Body application scenarios are flexibly set.
When including multiple object data change log from the data change log to be synchronized obtained on a domain controller
When, using full dose acquisition modes from the data of the object to be synchronized obtained on the domain controller in multiple object data change log into
Row synchronization process.
Method of data synchronization in domain controller side is shown in Figure 5, comprising:
S501: it when the data for presetting object to be synchronized on domain controller change, is recorded in data change log
This presets the modification information of object to be synchronized.
As described above, domain controller can first be sentenced when detecting that the changes such as creation, modification or deletion occur for certain an object
Whether the object that breaks is object to be synchronized, if so, then recording this in corresponding data change log presets object to be synchronized
Modification information；Otherwise, can not keep a record processing.
S502: the super controller that data change log issues upper layer is subjected to data change log and object to be synchronized
The synchronization of data.
As noted above, in the present embodiment, domain controller, can will be local all when for the first time with super controller link setup
Data change log issues super controller and carries out data synchronization processing, keeps in link setup operational process with super controller,
The data change log changed only can be issued into super controller, it, then can be according to super control after chain is rebuild in chain rupture
Corresponding data change log is issued super controller so that it carries out data synchronization processing by the rule searching of device processed.For domain
Details are not described herein for synchronization process process needed for controller corresponds to super controller.
It is same can flexibly to set needs for method of data synchronization provided in this embodiment between super controller and domain controller
The object to be synchronized of step, then domain controller can be changed when detecting that object to be synchronized is changed by corresponding data
Log is recorded and is issued super controller, and it is same that super controller can carry out targetedly data based on data change log
Step, rather than data all on domain controller blindly synchronize, it avoids synchronizing up redundant data, while can be promoted
The flexibility of data synchronously control, data synchronous efficiency and practicability.
Embodiment two:
In order to better understand the present invention, it is to show that the present embodiment, which combines a kind of method of data synchronization of specific application scenarios,
Example is illustrated.
In this example, it is configured by xml configuration file and is needed between upper layer super controller and lower layer's domain controller
Synchronous data type namely object to be synchronized, for example including network element, link, interface, business etc..This example is with to be synchronized right
As being illustrated for network element.
The network element data change log for designing upper layer super controller and lower layer's domain controller, since network element corresponds to reality
The specific equipment of management, belongs to the metastable data of extremely important and quantity, so according to one data of Network element object
The single pair image data change log of change log is designed.Certainly in some instances, it is also contemplated that according to equipment class
Type is finely divided, the network element of every kind of device type, designs a data change log.
Data change log field design in this example for Network element object is as follows:
LogID: the log serial number id of network element data change
ModifyTime: change time
ModifyType: change movement, creation are deleted, modification
ModifyOwner: become furthermore, upper layer super controller title or lower layer's domain controller title
ObjectValue: the unique identification of network element
ObjectType: the data type of object is here network element
ConsistState: coherency state, including the values such as conflict conflict, consistent consist, inconsistent, this
Only upper layer super controller needs consistState in example.
The field of data change log in this example it is not limited to the above example definition format, can flexibly increase or
It deletes.Modification information in this example includes modifyTime, modifyType, modifyOwner, and certain modification information includes
Content can also be with flexibly adjustment.
Based on above-mentioned setting, when upper and lower level controller respectively carries out data configuration, day is changed all in accordance with the data of data
Will design rule records data change log, and the information of each essential record includes log stream water number, changes the time, and change is dynamic
Make, reviser etc., upper layer super controller needs additional setting coherency state field.
When upper layer super controller and lower layer's domain controller carry out data initialization for the first time (namely built for the first time
After chain, the also referred to as first docking), upper layer super controller obtains number in such a way that full dose is inquired, from lower layer's domain grade controller
According to completion upper layer data initialization.It was managed specifically, upper layer super controller and lower layer's domain controller carry out docking for the first time
Journey is as follows:
Before docking management, data are sky in super controller (sc001), it is assumed that are managed on domain controller (dc001)
A, tri- network elements of b, c, at this point, the network element data change log on domain controller is participated in shown in table 1:
Table 1
| logID | modifyTime | modifyType | modifyOwner | objectValue |
| 1000000001 | 20170825101010 | create | dc001 | UUID-a |
| 1000000002 | 20170826101010 | create | dc001 | UUID-b |
| 1000000003 | 20170827101010 | create | dc001 | UUID-c |
About the data change log of domain controller to be empty in super controller, so full dose obtains net from domain controller
Metadata, and the data synchronization change log of domain controller is obtained, after the completion of data initialization, controlled in super controller about domain
The data change log of device processed is identical as domain controller holding, only more fields of a data consistency, referring specifically to table 2
It is shown:
Table 2
| logID | modifyTime | modifyType | modifyOwner | objectValue | consistState |
| 1000000001 | 20170825101010 | create | dc001 | UUID-a | consist |
| 1000000002 | 20170826101010 | create | dc001 | UUID-b | consist |
| 1000000003 | 20170827101010 | create | dc001 | UUID-c | consist |
The data synchronization process of super controller and the normal link setup operation (namely keeping link setup process) of domain controller:
Assuming that creating network element d on domain controller, and the attribute of network element c is had modified, domain controller is sent to super controller
Network element data Notification of Changes twice, the data change log ginseng on domain controller are shown in Table 3:
Table 3
| logID | modifyTime | modifyType | modifyOwner | objectValue |
| 1000000001 | 20170825101010 | create | dc001 | UUID-a |
| 1000000002 | 20170826101010 | create | dc001 | UUID-b |
| 1000000005 | 20170829101010 | modify | dc001 | UUID-c |
| 1000000004 | 20170828101010 | create | dc001 | UUID-d |
Super controller carries out corresponding log and object handles to be synchronized, synchronization process according to the Notification of Changes received
Data change log afterwards is referring to shown in table 4 are as follows:
Table 4
| logID | modifyTime | modifyType | modifyOwner | objectValue | consistState |
| 1000000001 | 20170825101010 | create | dc001 | UUID-a | consist |
| 1000000002 | 20170826101010 | create | dc001 | UUID-b | consist |
| 1000000005 | 20170829101010 | modify | dc001 | UUID-c | consist |
| 1000000004 | 20170828101010 | create | dc001 | UUID-d | consist |
Super controller and domain controller chain rupture, it is assumed that following data change has occurred during chain rupture:
After super controller and domain controller chain rupture, respectively network element data is changed, it is assumed that as follows, domain controller
Network element e is successively newly created, the attribute of network element d is had modified, and deletes network element b, the data change log of this time domain controller
Referring to shown in table 5 are as follows:
Table 5
| logID | modifyTime | modifyType | modifyOwner | objectValue |
| 1000000001 | 20170825101010 | create | dc001 | UUID-a |
| 1000000008 | 20170903101010 | delete | dc001 | UUID-b |
| 1000000005 | 20170829101010 | modify | dc001 | UUID-c |
| 1000000007 | 20170902101010 | modify | dc001 | UUID-d |
| 1000000006 | 20170901101010 | create | dc001 | UUID-e |
Assuming that super controller has modified the attribute of network element a, the data change log of super controller is referring to table 6 are as follows:
Table 6
| logID | modifyTime | modifyType | modifyOwner | objectValue | consistState |
| 1000000006 | 20170903101010 | modify | sc001 | UUID-a | conflict |
| 1000000002 | 20170826101010 | create | dc001 | UUID-b | consist |
| 1000000005 | 20170829101010 | modify | dc001 | UUID-c | consist |
| 1000000004 | 20170828101010 | create | dc001 | UUID-d | consist |
The coherency state of network element a is revised as " conflict ", indicates data collision, lower layer's domain controller is for net at this time
First a does not synchronize modification.
Data synchronization process after super controller and domain controller link re-establishment:
It is regular according to the acquisition of data synchronization log after super controller and domain controller link re-establishment, in super controller
Labeled as the record of " consist " state, the corresponding logID of its consistency max log serial number idMax is 1000000005,
So super controller should inquire all data change logs that logID on domain controller is greater than 1000000005, inquire
Result ginseng be shown in Table 7:
Table 7
| logID | modifyTime | modifyType | modifyOwner | objectValue |
| 1000000008 | 20170903101010 | delete | dc001 | UUID-b |
| 1000000007 | 20170902101010 | modify | dc001 | UUID-d |
| 1000000006 | 20170901101010 | create | dc001 | UUID-e |
Data change log of the logID greater than 1000000005 only has one in super controller, and ginseng is shown in Table 8:
Table 8
| logID | modifyTime | modifyType | modifyOwner | objectValue | consistState |
| 1000000006 | 20170903101010 | modify | sc001 | UUID-a | conflict |
The synchronization rules of data change log are, for the data of non conflicting, the logID of data change log is controlled with domain
Subject to device, the data of conflict are finally individually handled.
For e network element, will be updated data in super controller, create network element e, for d network element, super controller equally into
Row data update, and for b network element, labeled as deleting, the conflict of a network element is finally handled super controller.Network element is handled
E, after d and b, the data synchronization log in super controller is referring to table 9 are as follows:
Table 9
The data of conflict, i.e. network element a are finally handled, since network element a data do not change on domain controller, it is assumed that this
Scape very unwise move slightly downloads Synchronous Principle, then needs to modify the logID and coherency state of network element a, the number of final super controller
According to change log referring to table 10 are as follows:
Table 10
| logID | modifyTime | modifyType | modifyOwner | objectValue | consistState |
| 1000000009 | 20170903101010 | modify | sc001 | UUID-a | consist |
| 1000000008 | 20170903101010 | delete | dc001 | UUID-b | consist |
| 1000000005 | 20170829101010 | modify | dc001 | UUID-c | consist |
| 1000000007 | 20170902101010 | modify | dc001 | UUID-d | consist |
| 1000000006 | 20170901101010 | create | dc001 | UUID-e | consist |
Due to being the downloading principle used, need to modify on domain controller the data change log of a network element modification time,
Reviser and logID, final data change log is referring to shown in table 11 are as follows:
Table 11
| logID | modifyTime | modifyType | modifyOwner | objectValue |
| 1000000009 | 20170903101010 | modify | sc001 | UUID-a |
| 1000000008 | 20170903101010 | delete | dc001 | UUID-b |
| 1000000005 | 20170829101010 | modify | dc001 | UUID-c |
| 1000000007 | 20170902101010 | modify | dc001 | UUID-d |
| 1000000006 | 20170901101010 | create | dc001 | UUID-e |
It is related to single pair image data change log in this example, it, can be abundant in the comparison procedure of data change log
The Integral synchronous efficiency of consideration system, is analyzed in conjunction with the threshold value of setting, such as the network element total amount in domain controller is 10000
It is a, and analyzed by data change log as a result, finding there are 2001 network elements to be changed, the threshold value of default is
2000, it indicates to obtain if the network element changed in system is more than 2000 (also can be converted into ratio value certainly) using full dose
Strategy carries out data synchronization updating.Because the incrementally synchronous method of data, needs the keyword according to network element, controlled from domain
Obtain 2001 network elements in device system processed one by one, inquiry times are 2001 times, and overall efficiency may be simultaneously pessimistic, and it is disposable or
Iteration obtains whole network elements from domain controller, and carries out data update by way of comparing one by one, and efficiency is higher instead.This
The flexible strategy of kind can be further improved the synchronous effect of data between super controller and domain controller under special scenes
Rate further promotes the practicability of method of data synchronization.
When object to be synchronized includes link, the synchronization process process class of synchronization process process and network element for link
Seemingly, it will not be described in detail here.And it should be understood that those skilled in the art can also be by other on the basis of the present embodiment
Object to be synchronized carries out method using the synchronous method of the present embodiment introduction.
Embodiment three:
To facilitate the understanding of the present invention, a kind of data sync control device is present embodiments provided, shown in Figure 6, packet
It includes:
Log acquisition module 61, for obtaining data change log to be synchronized, the data change log from domain controller
For recording the modification information for presetting object to be synchronized.Log acquisition module 61 in the present embodiment is in each stage from domain controller
The mode of data change log is obtained referring to shown in above-described embodiment, details are not described herein.
Synchronization control module 62, the data for the data change log according to acquisition to the domain controller in local terminal become
More log synchronizes processing, and for according to the modification information in the data change log after local terminal synchronization process to corresponding
The data of object to be synchronized synchronize processing.The data of synchronization control module 62 progress data change log and object to be synchronized
Synchronization process process referring also to shown in above-described embodiment, also repeat no more herein.
It should be understood that the data sync control device in the present embodiment can be set in super controller, log
The function of obtaining module 61 and synchronization control module 62 can be realized by the first processor of super controller.
The present embodiment additionally provides a kind of data synchronous maintenance device, shown in Figure 7, comprising:
Log maintenance module 71, when being changed for the data for presetting object to be synchronized on domain controller, in number
According to recording the modification information for presetting object to be synchronized in change log.Log maintenance module 71 detects the data of object to be synchronized
The maintenance process of change and progress data change log occurs referring to shown in above-described embodiment, details are not described herein.
Sending module 72, for data change log is issued upper layer super controller carry out data change log and to
The synchronization of the data of synchronization object.
Sending module 72 in domain controller for the first time with super controller link setup when, all data on domain controller can be become
More log issues super controller and carries out data synchronization processing, keeps link setup operational process in domain controller and super controller
In, the data change log changed only can be issued into super controller, it, then can be according to super after chain is rebuild in chain rupture
Corresponding data change log is issued super controller so that it carries out data synchronization processing by the rule searching of controller.
It should be understood that the data synchronous maintenance device in the present embodiment can be set on domain controller, log dimension
Shield module 71 and the function of sending module 72 can be realized by the first processor of domain controller.
The present embodiment additionally provides the controller system in a kind of SDN network, shown in Figure 8, including the super of upper layer
Controller 81 and the domain controller of lower layer 82, in which:
Shown in Figure 9, super controller 81 includes first processor 811, first memory 812 and the first communication bus
813；
First communication bus 813 is for realizing the connection communication between first processor 811 and first memory 812；
First processor 811 is for executing one or more first program stored in first memory 812, to realize
The step of method of data synchronization in as above embodiment one and embodiment two.
Shown in Figure 10, domain controller 82 includes second processor 821, second memory 822 and the second communication bus
823；
Second communication bus 823 is for realizing the connection communication between second processor 821 and second memory 822；
Second processor 821 is for executing one or more second program stored in second memory 822, to realize
The step of method of data synchronization in as above embodiment one and embodiment two.
The present embodiment additionally provides a kind of computer storage medium, can be applied in various communication equipments.In a kind of reality
It applies in example, which has one or more the first program, one or more first program
It is executed by one or more first processor, to realize the step of the method for data synchronization in embodiment one and embodiment two as above
Suddenly.
In another embodiment, which has one or more the second program, described
One or more second program is executed by one or more second processor, to realize embodiment one and embodiment two as above
In method of data synchronization the step of.
In order to better understand the present invention, on the basis of above system, the present embodiment combines a kind of specific application scenarios
It is illustrated for example.In this example, object to be synchronized includes business, and in this example, upper layer super controller is mainly
Checked, do not allow to be modified offline namely chain rupture during not permitted super controller modify.
In this example, (matching for extended formatting can also be selected according to concrete application scene certainly yet by xml configuration file
Set file) synchronous data type is needed between upper layer super controller and lower layer's domain controller to configure, such as network element, chain
Road, interface, business etc.；This example is business.
In this example, since the change of business datum is very frequent, and data volume is also very big, so according to sort key
Information-rate (can also be layer rate) is finely divided, the business of every kind of rate, one data change log of design i.e. object again
Data change log, i.e. business in system, add up to how many kinds of rate, just how many corresponding data change log, at this time
Rate be just object to be identified identification information.
In this example, the data change log field of business object is as follows:
LogID: network element data change log serial number id
ModifyTime: change time
ModifyOwner: become furthermore, super controller title or lower layer's controller D-C title
Rate: the rate of business
ObjectType: the data type of object is here business
ConsistState: coherency state, including the values such as conflict conflict, consistent consist, inconsistent, only
Super controller needs.
Based on above-mentioned setting, when upper and lower level controller respectively carries out data configuration, day is changed all in accordance with the data of data
Will design rule records data change log, and the information of each essential record includes log stream water number, changes the time, and change is dynamic
Make, reviser etc., upper layer super controller needs to be arranged coherency state field.
Upper layer super controller carries out the synchronous of docking management (namely first link setup) with lower layer domain controller for the first time
Journey are as follows:
Before docking management, data are sky in super controller, it is assumed that tri- business of a, b, c have been managed on domain controller,
Its corresponding rate is followed successively by 10001,10002,10003, at this point, the business datum change log on domain controller is referring to table 12
It is shown:
Table 12
| logID | modifyTime | rate | modifyOwner | objectValue |
| 1000000001 | 20170825101010 | 10001 | dc001 | UUID-a |
| 1000000002 | 20170826101010 | 10002 | dc001 | UUID-b |
| 1000000003 | 20170827101010 | 10003 | dc001 | UUID-c |
It should be understood that each field in data change log exemplified by table 12 can be adjusted flexibly, such as can delete
Except mono- column objectValue, other fields can also be increased.
About the data change log of domain controller to be empty in super controller, so the data for obtaining domain controller are synchronous
Change log, and business datum is obtained from domain controller according to the modification information full dose in the data change log after synchronizing.
After the completion of data initialization, the data change log in super controller about controller D-C is identical as controller D-C holding,
The only more field of a data consistency, ginsengs are shown in Table 13:
Table 13
| logID | modifyTime | rate | modifyOwner | objectValue | consistState |
| 1000000001 | 20170825101010 | 10001 | dc001 | UUID-a | consist |
| 1000000002 | 20170826101010 | 10002 | dc001 | UUID-b | consist |
| 1000000003 | 20170827101010 | 10003 | dc001 | UUID-c | consist |
Super controller and the data of the normal link setup operational process of domain controller are synchronous as follows:
Assuming that the rate of new business d on domain controller, d are 10004, and have modified business c during normal link setup
Attribute, domain controller modifies corresponding data change log and simultaneously sends business datum Notification of Changes twice to super controller,
The data change log ginseng of this time domain controller is shown in Table 14:
Table 14
| logID | modifyTime | rate | modifyOwner | objectValue |
| 1000000001 | 20170825101010 | 10001 | dc001 | UUID-a |
| 1000000002 | 20170826101010 | 10002 | dc001 | UUID-b |
| 1000000005 | 20170829101010 | 10003 | dc001 | UUID-c |
| 1000000004 | 20170828101010 | 10004 | dc001 | UUID-d |
Super controller carries out corresponding data change log synchronization process according to the Notification of Changes received, and to same
The data synchronization processing of object is walked, the data change log after synchronization process is referring to shown in table 15 are as follows:
Table 15
| logID | modifyTime | rate | modifyOwner | objectValue | consistState |
| 1000000001 | 20170825101010 | 10001 | dc001 | UUID-a | consist |
| 1000000002 | 20170826101010 | 10002 | dc001 | UUID-b | consist |
| 1000000005 | 20170829101010 | 10003 | dc001 | UUID-c | consist |
| 1000000004 | 20170828101010 | 10004 | dc001 | UUID-d | consist |
Super controller and domain controller chain rupture, it is assumed that following data change has occurred during chain rupture:
Business datum is changed after domain controller chain rupture, it is assumed that as follows, domain controller successively newly creates business
E, the rate of the business are 10001, have modified the attribute of business d, and delete business b, the data change of this time domain controller
Log is referring to shown in table 16 are as follows:
Table 16
Since the rate of two business of e and a is identical, so the two shares same data change log, directly modify
The corresponding data change log record of 10001 rates.
Since system does not allow super controller to carry out business datum configuration under domain controller chain rupture state, so upper layer
The business datum change log of super controller will not change.
Data synchronization process after super controller and domain controller link re-establishment are as follows:
It is regular according to the acquisition of data synchronization log after super controller and domain controller link re-establishment, in super controller
Labeled as the record of " consist " state, the corresponding logID of its consistency max log serial number idMax is 1000000005,
So super controller should inquire all data change logs that logID on domain controller is greater than 1000000005, inquire
Result ginseng be shown in Table 17:
Table 17
| logID | modifyTime | rate | modifyOwner | objectValue |
| 1000000006 | 20170825101010 | 10001 | dc001 | UUID-e |
| 1000000008 | 20170903101010 | 10002 | dc001 | UUID-b |
| 1000000007 | 20170902101010 | 10004 | dc001 | UUID-d |
According to the synchronization rules of data change log, the business of rate 10001,10002,10004 is changed, institute
With super controller need full dose from D-C obtain all rates be 10001,10002,10004 business, and with existing super control
Existing business is compared in device processed, analyzes the specific business that wound is revised, and is synchronized to complete data, after the completion, super
Data synchronization log on controller is consistent again with D-C, only more one columns of coherency state, specific to participate in such as following table
Shown in 18.
Table 18
When object to be synchronized includes interface, the synchronization process process class of synchronization process process and business for interface
Seemingly, it will not be described in detail here.And it should be understood that those skilled in the art can also be by other on the basis of the present embodiment
Object to be synchronized carries out method using the synchronous method of the present embodiment introduction.
As it can be seen that the method for data synchronization and super controller and domain controller that provide through the embodiment of the present invention, it can be right
Data progress on domain controller is targetedly synchronous with selectivity, rather than the direct of blindness will be all on domain controller
Data are synchronized in super controller, can be promoted the synchronous efficiency of data and practicability, also simultaneously provided one kind for data
Completely new synchronization mechanism.
In addition, existing traditional method of data synchronization, when being business datum for object to be synchronized, when lower layer's domain controller
On data change after, one point data is synchronized in the super controller on upper layer, and the super controller on upper layer needs pass through
Automatic discovery deletes the original business datum in original super controller come when regenerating business datum, will lead
Cause some important self-defined informations (such as some important remark informations) in original business datum that will lose,
It need to be reset in new business datum if necessary.And the method for data synchronization provided through the embodiment of the present invention is super
Custom information (such as remark information) can't be deleted on grade controller, therefore not need to be redefined, it can be with
Further promote data synchronous practicability and convenience.
Obviously, those skilled in the art should be understood that each module of the embodiments of the present invention or each step can be used
General computing device realizes that they can be concentrated on a single computing device, or be distributed in multiple computing device institutes
On the network of composition, optionally, they can be realized with the program code that computing device can perform, it is thus possible to by them
It is stored in computer storage medium (ROM/RAM, magnetic disk, CD) and is performed by computing device, and in some cases, it can
With the steps shown or described are performed in an order that is different from the one herein, or they are fabricated to each integrated circuit dies
Block, or single integrated circuit module is maked multiple modules or steps in them to realize.So the present invention does not limit
It is combined in any specific hardware and software.
The above content is combining specific embodiment to be further described to made by the embodiment of the present invention, cannot recognize
Fixed specific implementation of the invention is only limited to these instructions.For those of ordinary skill in the art to which the present invention belongs,
Without departing from the inventive concept of the premise, a number of simple deductions or replacements can also be made, all shall be regarded as belonging to the present invention
Protection scope.
Claims (15)
1. a kind of method of data synchronization, comprising:
Data change log to be synchronized is obtained from domain controller, the data change log presets object to be synchronized for recording
Modification information；
Data change log according to the data change log of acquisition to the domain controller in local terminal synchronizes processing；
It is carried out according to data of the modification information in the data change log after local terminal synchronization process to corresponding object to be synchronized same
Step processing.
2. method of data synchronization as described in claim 1, which is characterized in that described to obtain data to be synchronized from domain controller
Change log includes:
With after the first link setup of the domain controller, all data change logs on the domain controller are obtained；
Data change log of the data change log according to acquisition to the domain controller in local terminal synchronizes processing
It include: that all data change logs that will be obtained from the domain controller are stored in local terminal.
3. method of data synchronization as described in claim 1, which is characterized in that described to obtain data to be synchronized from domain controller
Change log includes:
It is kept in link process with the domain controller, the data for receiving the domain controller in object to be synchronized change
When the Notification of Changes that sends, the domain controller is corresponding to the object to be synchronized when the data of object to be synchronized are changed
Data change log carries out corresponding change；
Data change log corresponding with the Notification of Changes is obtained from the domain controller according to the Notification of Changes；
Data change log of the data change log according to acquisition to the domain controller in local terminal synchronizes processing
Include:
The data change log that judgement obtains whether there is in local terminal, if so, the original data change log of local terminal is updated to
The data change log obtained；Otherwise, the data change log that will acquire carries out newly-increased storage in local terminal.
4. method of data synchronization as described in claim 1, which is characterized in that the data obtained from the domain controller change day
Will further include: the current log serial number of object to be synchronized, after object change to be synchronized, corresponding log serial number is updated to
Maximum serial number in current data change log；
The data change log that will acquire has in pieces of data change log after local terminal synchronizes processing and is used for table
The data and the whether consistent consistent character of data on the domain server for levying the corresponding object to be synchronized of data change log
State mark.
5. method of data synchronization as claimed in claim 4, which is characterized in that described to obtain data to be synchronized from domain controller
Change log includes:
With after the domain controller chain rupture link re-establishment, from local terminal and the domain controller, obtains log serial number and be greater than
The data change log of local terminal consistency max log serial number, the consistency maximum serial number are local terminal coherency state mark
Knowing is maximum log serial number in consistent all data change logs.
6. method of data synchronization as claimed in claim 5, which is characterized in that the data change log according to acquisition is to institute
It states domain controller and synchronizes processing in the data change log of local terminal and include:
There is the domain controller during chain rupture when newly created data change log in the data change log of acquisition, by the number
Newly-increased storage is carried out in local terminal according to change log；
When the data change log for thering is the domain controller to modify during chain rupture in the data change log of acquisition, by local terminal
Corresponding data change log synchronizes modification；
When the data change log for having local terminal to modify during chain rupture in the data change log of acquisition, original is synchronized using uploading
Then or downloading Synchronous Principle synchronizes the data of object to be synchronized in the data change log and the data change log
Processing；After local terminal modifies to some data change log during chain rupture, by the consistency in the data change log
Status indicator is set as conflicting.
7. method of data synchronization as claimed in any one of claims 1 to 6, which is characterized in that the modification information include creation,
Modification and deletion；
The modification information in data change log after the synchronization process according to local terminal to the data of corresponding object to be synchronized into
Row synchronization process includes:
When the modification information in the data change log after local terminal synchronization process is creation, obtaining from the domain controller should
The data of object to be synchronized in data change log are stored in local terminal；
When the modification information in the data change log after local terminal synchronization process is modification, obtaining from the domain controller should
The data of object to be synchronized in data change log are updated the object to be synchronized in the data of local terminal；
When the modification information in the data change log after local terminal synchronization process is to delete, by the data change log to
Synchronization object is deleted in the data of local terminal.
8. method of data synchronization as claimed in any one of claims 1 to 6, which is characterized in that the data change log includes single
Object data change log and multiple object data change log, the Object identifying to be synchronized in the single pair image data change log
Information is the identification information of single object to be synchronized, and the object identification information to be synchronized in the multiple object data change log is
The Classification and Identification information of object to be synchronized, a Classification and Identification information correspond at least one object to be synchronized；
When the single pair image data change log item for including from the data change log to be synchronized obtained on a domain controller
When number is more than or equal to preset threshold, the single pair image data change day is obtained from the domain controller using full dose acquisition modes
The data of object to be synchronized in will synchronize processing；
When from the data change log to be synchronized obtained on a domain controller including multiple object data change log, adopt
With full dose acquisition modes from the data for obtaining the object to be synchronized in the multiple object data change log on the domain controller
Synchronize processing.
9. method of data synchronization as claimed in claim 8, which is characterized in that in the single pair image data change log to same
Walking object includes at least one of network element, link；Object to be synchronized in the multiple object data change log include business,
At least one of interface.
10. a kind of method of data synchronization, comprising:
When the data for presetting object to be synchronized on domain controller change, it is default to same that this is recorded in data change log
Walk the modification information of object；
The data change log is issued to the super controller on upper layer.
11. a kind of data sync control device, comprising:
Log acquisition module, for obtaining data change log to be synchronized from domain controller, the data change log is used for
Record presets the modification information of object to be synchronized；
Synchronization control module, for according to the data change log of acquisition to the domain controller local terminal data change log
Synchronize processing, and for according to the modification information in the data change log after local terminal synchronization process to corresponding to be synchronized
The data of object synchronize processing.
12. a kind of data synchronous maintenance device, comprising:
Log maintenance module when changing for the data for presetting object to be synchronized on domain controller, is changed in data
The modification information for presetting object to be synchronized is recorded in log；
Sending module, for the data change log to be issued to the super controller on upper layer.
13. a kind of super controller, the super controller includes first processor, first memory and the first communication bus；
First communication bus is for realizing the connection communication between first processor and first memory；
The first processor is for executing one or more first program stored in first memory, to realize such as right
It is required that the step of method of data synchronization described in any one of 1 to 9.
14. a kind of domain controller, the domain controller includes second processor, second memory and the second communication bus；
Second communication bus is for realizing the connection communication between second processor and second memory；
The second processor is for executing one or more second program stored in second memory, to realize such as right
It is required that the step of method of data synchronization described in 10.
15. a kind of computer storage medium, the computer-readable recording medium storage has one or more the first program, institute
It states one or more first program to be executed by one or more processor, to realize such as any one of claims 1 to 9 institute
The step of method of data synchronization stated；
Or,
The computer-readable recording medium storage has one or more the second program, one or more of second programs
It is executed by one or more processor, the step of to realize method of data synchronization as described in claim 10.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710967367.4A CN109672712A (en) | 2017-10-17 | 2017-10-17 | Method of data synchronization, device, super controller, domain controller and storage medium |
| PCT/CN2018/109878 WO2019076236A1 (en) | 2017-10-17 | 2018-10-11 | Data synchronization method and device, super controller, domain controller, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710967367.4A CN109672712A (en) | 2017-10-17 | 2017-10-17 | Method of data synchronization, device, super controller, domain controller and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109672712A true CN109672712A (en) | 2019-04-23 |
Family
ID=66141443
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710967367.4A Pending CN109672712A (en) | 2017-10-17 | 2017-10-17 | Method of data synchronization, device, super controller, domain controller and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109672712A (en) |
| WO (1) | WO2019076236A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110225077A (en) * | 2019-04-25 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Synchronous method, device, computer equipment and the computer storage medium of change supply data |
| CN110851413A (en) * | 2019-11-08 | 2020-02-28 | 深圳市元征科技股份有限公司 | Data synchronization method and device, electronic equipment and storage medium |
| CN112865998A (en) * | 2019-11-28 | 2021-05-28 | 华为技术有限公司 | Intention processing method and related device |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113176771B (en) * | 2021-04-16 | 2023-04-14 | 重庆长安新能源汽车科技有限公司 | Method for monitoring running state of vehicle domain controller |
| CN114442941B (en) * | 2022-01-05 | 2023-05-12 | 杭州宏杉科技股份有限公司 | Data migration method, system, storage medium and equipment |
| CN115314356B (en) * | 2022-08-09 | 2023-11-24 | 中电云计算技术有限公司 | Cross-region distributed SDN control device and method based on OVN |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101631134A (en) * | 2008-07-14 | 2010-01-20 | 李�真 | Network message exchange service manager for distributed type computing environment |
| US20130053985A1 (en) * | 2009-12-15 | 2013-02-28 | At&T Intellectual Property I, L.P. | Proxy Remote Control |
| CN103020242A (en) * | 2012-12-19 | 2013-04-03 | 中国人民解放军第二炮兵装备研究院第四研究所 | Data synchronization method based on oracle database |
| CN105262831A (en) * | 2015-10-30 | 2016-01-20 | 北京奇艺世纪科技有限公司 | Method, device, and synchronizing system for synchronizing data among memory systems |
| CN106802892A (en) * | 2015-11-26 | 2017-06-06 | 阿里巴巴集团控股有限公司 | For the method and apparatus of master/slave data consistency verification |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4248510B2 (en) * | 2005-03-24 | 2009-04-02 | 株式会社東芝 | Computer system, disk device, and data update control method |
| CN103780638B (en) * | 2012-10-18 | 2019-02-19 | 腾讯科技（深圳）有限公司 | Method of data synchronization and system |
| CN104506643A (en) * | 2014-12-30 | 2015-04-08 | 北京奇虎科技有限公司 | Server of distributed storage system and data synchronizing method between servers |
| CN105245593A (en) * | 2015-09-29 | 2016-01-13 | 北京邮电大学 | Software defined network (SDN) controlling system, method and device |
-
2017
- 2017-10-17 CN CN201710967367.4A patent/CN109672712A/en active Pending
-
2018
- 2018-10-11 WO PCT/CN2018/109878 patent/WO2019076236A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101631134A (en) * | 2008-07-14 | 2010-01-20 | 李�真 | Network message exchange service manager for distributed type computing environment |
| US20130053985A1 (en) * | 2009-12-15 | 2013-02-28 | At&T Intellectual Property I, L.P. | Proxy Remote Control |
| CN103020242A (en) * | 2012-12-19 | 2013-04-03 | 中国人民解放军第二炮兵装备研究院第四研究所 | Data synchronization method based on oracle database |
| CN105262831A (en) * | 2015-10-30 | 2016-01-20 | 北京奇艺世纪科技有限公司 | Method, device, and synchronizing system for synchronizing data among memory systems |
| CN106802892A (en) * | 2015-11-26 | 2017-06-06 | 阿里巴巴集团控股有限公司 | For the method and apparatus of master/slave data consistency verification |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110225077A (en) * | 2019-04-25 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Synchronous method, device, computer equipment and the computer storage medium of change supply data |
| CN110851413A (en) * | 2019-11-08 | 2020-02-28 | 深圳市元征科技股份有限公司 | Data synchronization method and device, electronic equipment and storage medium |
| CN112865998A (en) * | 2019-11-28 | 2021-05-28 | 华为技术有限公司 | Intention processing method and related device |
| CN112865998B (en) * | 2019-11-28 | 2022-10-18 | 华为技术有限公司 | Intention processing method and related device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019076236A1 (en) | 2019-04-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109672712A (en) | Method of data synchronization, device, super controller, domain controller and storage medium | |
| US11010358B2 (en) | Data migration method and system | |
| CN109493076B (en) | Kafka message unique consumption method, system, server and storage medium | |
| CN100547583C (en) | Database automatically and the method that dynamically provides | |
| US20140195482A1 (en) | Data synchronization in a storage network | |
| DE202016107158U1 (en) | System for automatic cloud-based full data backup and recovery of mobile devices | |
| CN105518641B (en) | Point-to-Point Data clone method, equipment and system and host node switching method, equipment and system | |
| CN102098342A (en) | Transaction level-based data synchronizing method, device thereof and system thereof | |
| CN104679841A (en) | Consumption terminal data flow copying method and system | |
| US10063651B2 (en) | Parallel streams to maintain a target data transfer rate | |
| CN109710586B (en) | A kind of clustered node configuration file synchronous method and device | |
| US10972296B2 (en) | Messaging to enforce operation serialization for consistency of a distributed data structure | |
| CN109978290A (en) | A kind of operation flow backspacing processing method of extensive makeup, flow engine and operation system | |
| CN109726192A (en) | The system and method for master data model version and field separate management function is realized based on big data environment | |
| CN102857949A (en) | Method and device for planning data consistency guarantees | |
| US20220391244A1 (en) | Decentralized cluster federation in computer network node management systems | |
| CN108574718A (en) | A kind of cloud host creation method and device | |
| CN111708835A (en) | Block chain data storage method and device | |
| CN111382199A (en) | Method and device for synchronously copying database | |
| CN100486177C (en) | Method of synchronously operating network element by network management and its system | |
| CN107342944B (en) | A kind of distribution of ID mark and persistence method and system | |
| CN110196786A (en) | Rollback database synchronizes the control method and equipment of middle memory | |
| CN115858486A (en) | Data processing method and related equipment | |
| CN109710401A (en) | A kind of cloud computing resources Cost Optimization Approach | |
| CN114553917A (en) | Intelligent network management method based on block chain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190423 |