CN108494859B - Network data synchronization method and system - Google Patents
Network data synchronization method and system Download PDFInfo
- Publication number
- CN108494859B CN108494859B CN201810264721.1A CN201810264721A CN108494859B CN 108494859 B CN108494859 B CN 108494859B CN 201810264721 A CN201810264721 A CN 201810264721A CN 108494859 B CN108494859 B CN 108494859B
- Authority
- CN
- China
- Prior art keywords
- data
- service
- client
- server
- interactive
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
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
Abstract
The invention discloses a method and a system for synchronizing network data, and relates to the field of interaction and comparison of network data. The method comprises the following steps: the method comprises the steps that when a client and a server perform network service data interaction once, the client records interaction data information and interaction result information; when the interaction result information represents that the interaction is abnormal, the client processes corresponding service data in the server according to the interaction data information associated with the interaction result information; the method comprises the steps that a client side obtains client side synchronous data and server side synchronous data in a specified time period, the client side synchronous data are all service data interacted with a server side on the client side, and the server side synchronous data are all service data interacted with the client side on the server side; and synchronizing the client synchronous data according to the server synchronous data. When the interaction of the client and the server is abnormal, the method and the system can enable the client to automatically process abnormal data, and further ensure the data synchronization of the client and the server.
Description
Technical Field
The invention relates to the field of interaction and comparison of network data, in particular to a method and a system for synchronizing network data.
Background
With the rapid development of communication technology, the number of service types and service scenes of a transmission network increases, and more network services are provided for interaction between a client and a server. The process of the network service interaction between the client and the server comprises the following steps: the client requests the server to create a service, and the client requests the server to delete the created service, where 1 service is being created or deleted, which is actually a process of creating or deleting multiple sub-services, for example, the process of creating service a is as follows: the sub-service a1 (service tunnel), the sub-service a2 (service pseudo-wire), the sub-service A3 (service protection) and the sub-service a4 (service establishment) are created in sequence, and the deletion of the services is the same.
The process of the client requesting the server to create the business comprises the following steps: requesting to create a service to a server according to the creation sequence of the service; for example, the creation order of the service a is a1, a2, A3 and a4, then the client requests the server to create a1, a2, A3 and a4 services in turn at this time.
The process that the client requests the server to delete the created service comprises the following steps: the client requests the service end to delete the services according to the deletion order of the services (the reverse order of the creation order of the services), for example, the deletion order of the service a is a4, A3, a2 and a1, and then the client requests the service end to create and delete the services a4, A3, a2 and a1 in sequence.
However, when the existing client and server perform network service interaction, the following disadvantages exist:
when a client requests a service to create and delete a service, if the creation or deletion fails, partial data of successful creation (for example, data of a1 and a2 are left in a service if the creation or deletion fails, and a1 and a2 are successfully created and A3 fails), and the residual data need to be manually removed by a maintenance person, and in a scenario where the service types are increasing, the maintenance person is difficult to effectively remove the residual data, and when the residual data is more, not only is data management inconvenient, but also the working efficiency of the service is seriously reduced, and even the service is down.
In addition, data of the client and the server are kept consistent, so that services in the client are maintained conveniently, the client needs to synchronize service data with the server regularly, and the synchronization method comprises the following steps: the client generates a created service data table 1 regularly, requests the server to generate a created service data table 2, and synchronizes the data of the service data table 1 according to the data of the service data table 2 after the maintenance personnel means compares the service data tables 1 and 2.
However, when the client and the server synchronize the service data, if the service data is complex, the precision of comparing the service data manually by the maintainer is low, and the synchronization quality of the service data between the client and the server is further reduced.
Disclosure of Invention
Aiming at the defects in the prior art, the invention solves the technical problems that: when the interaction between the client and the server is abnormal, how the client automatically processes the abnormal data is to keep the data synchronization between the client and the server.
In order to achieve the above object, the method for synchronizing network data provided by the present invention comprises the following steps:
s1: the method comprises the steps that when a client and a server perform network service data interaction once, the client records interactive data information and interactive result information which are correlated with each other; when the interaction result information represents that the interaction is abnormal, the client processes corresponding service data in the server according to the interaction data information associated with the interaction result information;
s2: the method comprises the steps that a client side obtains client side synchronous data and server side synchronous data in a specified time period, the client side synchronous data are all service data interacted with a server side on the client side, and the server side synchronous data are all service data interacted with the client side on the server side; and synchronizing the client synchronous data according to the server synchronous data.
Based on the foregoing technical solution, the types of network service interaction performed by the client and the server in S1 include: the client requests the service end to create a service, and S1 includes the following steps:
s101: the client takes the first sub-service to be created as an interactive service according to the creation sequence of the service, and goes to S102;
s102: the client initiates a request for creating the interactive service to the server, records interactive data information of the interactive service, and goes to S103;
s103: the client uses the service creation information returned by the server as the interaction result information of the interaction service and is associated with the interaction data information; if the interactive result information is that the interactive service is successfully established, the step goes to S104; if the interactive result information is that the interactive service is failed to be established, representing that the interaction is abnormal, and turning to S105;
s104: the client takes the next sub-service to be created as an interactive service according to the creation sequence of the service, and goes to S102;
s105: and after the client acquires the interactive data information of all interactive services, deleting the interactive service data corresponding to the interactive data information in the server according to the deleting sequence of the services.
On the basis of the above technical solution, after the client deletes the interactive service data in the server in S105, the method further includes the following steps: the client judges whether the times of the service creation failure are above a specified threshold, if so, the service is marked with the creation failure, and the process is finished; if not, go to S101.
On the basis of the above technical solution, S2 further includes the following steps: all services for which there is a creation failure flag are processed according to the step of S1.
On the basis of the above technical solution, when the client synchronization data is synchronized according to the server synchronization data in S2, the method includes the following steps: when data A of the existence of server side synchronous data and the nonexistence of client side synchronous data are monitored, adding the data A on the client side; when data B of the server side synchronous data and the client side synchronous data is monitored to be absent, deleting the data B on the client side; and when the server side synchronous data and the client side synchronous data are monitored to exist but different data C and D, replacing the data D on the client side with the data C on the server side.
The invention provides a network data synchronization system, which comprises a network data interaction module and a network data synchronization module, wherein the network data interaction module and the network data synchronization module are arranged on a client;
the network data interaction module is used for: recording interactive data information and interactive result information which are correlated with each other when the client and the server perform network service data interaction once; when the interaction result information represents that the interaction is abnormal, processing corresponding service data in the server according to the interaction data information associated with the interaction result information;
the network data synchronization module is used for: the method comprises the steps that client side synchronous data and server side synchronous data in a specified time period are obtained, the client side synchronous data are all service data interacted with a server side on the client side, and the server side synchronous data are all service data interacted with the client side on the server side; and synchronizing the client synchronous data according to the server synchronous data.
On the basis of the technical scheme, the types of network service interaction between the client and the server comprise: the client requests the service creation from the server, and at this time, the network data interaction module is specifically configured to: according to the creation sequence of the service, after the first sub-service to be created is taken as an interactive service, entering a service interaction flow;
the service interaction process comprises the following steps: initiating a creation request of an interactive service to a server, recording interactive data information of the interactive service, and using service creation information returned by the server as interactive result information of the interactive service and associating the interactive result information with the interactive data information; if the interactive result information is that the interactive service is successfully established, according to the establishing sequence of the service, the next sub-service to be established is used as the interactive service, and then the service interaction flow is re-entered; and if the interactive result information is that the interactive service is failed to be established, representing that the interaction is abnormal, and deleting the interactive service data corresponding to the interactive data information in the server according to the deleting sequence of the service after acquiring the interactive data information of all the interactive services.
On the basis of the above technical solution, after the network data interaction module deletes the interaction service data in the server, the network data interaction module is further configured to: judging whether the number of times of service creation failure is above a specified threshold value, if so, marking the service creation failure, and ending; if not, the operation is restarted.
On the basis of the above technical solution, the network data synchronization module is further configured to: and processing all services with the creation failure marks according to the working mode of the network data interaction module.
On the basis of the technical scheme, when the network data synchronization module synchronizes the client side synchronization data according to the server side synchronization data, the method comprises the following steps: when data A of the existence of server side synchronous data and the nonexistence of client side synchronous data are monitored, adding the data A on the client side; when data B of the server side synchronous data and the client side synchronous data is monitored to be absent, deleting the data B on the client side; and when the server side synchronous data and the client side synchronous data are monitored to exist but different data C and D, replacing the data D on the client side with the data C on the server side.
Compared with the prior art, the invention has the advantages that:
(1) as can be seen from S1 of the method of the present invention, when the client and the server perform service interaction each time, the method of the present invention records interaction data information and interaction result information; when the interaction result information represents that the interaction is abnormal, the client processes corresponding service data in the server according to the interaction data information associated with the interaction result information, for example, when the service creation fails, the residual data in the server is automatically deleted reversely. Therefore, compared with the prior art of manually clearing residual data in the process of mutual abnormality, the method and the system can immediately clear the abnormal data, not only ensure the data synchronization precision of the client and the server, but also ensure the integrity of a single service.
(2) Compared with the prior art in which synchronization is manually performed by comparing service data, referring to S2 of the method of the present invention, the method of the present invention can automatically synchronize corresponding data of the client according to the data of the server within the specified time period, thereby further improving the data synchronization accuracy of the client and the server.
(3) It can be seen from S2 of the method of the present invention that, after the client and the server interact abnormally, the present invention performs secondary analysis processing on the abnormal service, if the abnormal service fails again, the abnormal service is manually processed, and if the abnormal service succeeds, the abnormal service does not need to be manually processed, so that the probability of manual processing is reduced, the working precision is also improved, the risk of data security and correctness can be minimized, and the consistency of the data of the client and the server is ensured.
Drawings
Fig. 1 is a flowchart of a method for synchronizing network data according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples.
Referring to fig. 1, a synchronization method for network data in an embodiment of the present invention includes the following steps:
s1: the method comprises the steps that when a client and a server perform network service data interaction once, the client records interactive data information and interactive result information which are correlated with each other; and when the interaction result information represents that the interaction is abnormal, the client processes corresponding service data in the server according to the interaction data information associated with the interaction result information.
S2: the method comprises the steps that a client side obtains client side synchronous data and server side synchronous data in a specified time period, the client side synchronous data are all service data interacted with a server side on the client side, and the server side synchronous data are all service data interacted with the client side on the server side; the client synchronization data is synchronized according to the server synchronization data, and the execution time of S2 may be periodically executed, i.e., S2 may be performed before, after, or during the execution of S1.
The process of the invention is illustrated in detail below by means of six examples.
The first embodiment is as follows:
the types of network service interaction between the client and the server in S1 include: the client requests the service end to create a service, and S1 includes the following steps:
s101: the client takes the first sub-service to be created as an interactive service according to the creation sequence of the service, and goes to S102.
S102: the client initiates a request for creating the interactive service to the server (each time 1 time of sending the request is considered as one time of network service data interaction), records interactive data information of the interactive service (the interactive data information includes the interactive service type, the operation type and specific interactive service data), and goes to S103.
S103: the client uses the service creation information returned by the server as interaction result information of the interaction service (if the interaction result information exists, the interaction result information is directly covered) and is associated with the interaction data information; if the interactive result information is that the interactive service is successfully established, the step goes to S104; if the interaction result information is that the interactive service creation fails, the interaction is represented as abnormal, and the process goes to S105.
S104: the client takes the next sub-service to be created as an interactive service according to the creation sequence of the service, and goes to S102; if there is no next sub-service to be created, the service creation is successful, and S1 ends.
S105: after the client acquires the interactive data information of all interactive services, the interactive service data corresponding to the interactive data information are deleted in the server in sequence according to the deletion sequence of the services (the reverse sequence of the creation sequence of the services); for example, the creating process of creating the service a is to create a1, a2, A3 and a4, and if the creation of A3 by the service end fails, data of a2 and a1 are deleted in sequence from the service end, and at this time, a creation failure flag may be further performed on the service to be created, so that manual processing may be performed at a later stage.
The types of network service interaction between the client and the server in S1 include: the client requests the service end to delete the service, and S1 includes the following steps:
s101 a: the client takes the first sub-service to be deleted as an interactive service according to the deletion order of the services, and goes to S102 a.
S102 a: the client initiates a deletion request of the interactive service to the server (each time 1 deletion request is sent, the deletion request is considered to be one service interaction), records interactive data information of the interactive service (the interactive data information includes an interactive service type, an operation type and specific interactive service data), and goes to S103 a.
S103 a: the client side takes the service deletion information returned by the server side as interaction result information of the interaction service (if the interaction result information exists, the interaction result information is directly covered) and is associated with the interaction data information; if the interactive result information is that the interactive service is successfully deleted, the step goes to S104 a; if the interaction result information is that the deletion of the interaction service fails, the interaction is abnormal, and at this time, the deletion failure flag may be performed on the service that needs to be deleted in S101a, so as to perform manual processing at a later stage.
S104 a: the client takes the next sub-service to be deleted as an interactive service according to the deletion sequence of the services, and goes to S102 a; if there is no next sub-service to be deleted, it represents that the service deletion is successful, and S1 ends.
Example two:
on the basis of the first embodiment, after the client deletes the interactive service data in the server in S105, the method further includes the following steps: the client judges whether the number of times of service creation failure is above a specified threshold, if so, the service is created for many times but fails, the creation is likely to be unsuccessful, and in order to improve the working efficiency of the client and the server, the service creation is not carried out at this time, the service is marked with the creation failure, and the process is finished; if not, it can be created again, going to S101.
Example three:
on the basis of the first embodiment, if the interaction result information in S103a is that the deletion of the interaction service fails, the method specifically includes the following steps: the client list judges whether the number of times of service deletion failure is above a specified threshold value, if so, the service is deleted for many times but fails, the service is deleted again with a high probability and cannot be successfully deleted, and in order to improve the working efficiency of the client and the server, the service deletion is not carried out at this time, the service is marked with deletion failure, and the operation is finished; if not, it may be deleted again, and the process goes to S101 a.
Example four:
in S2, synchronizing the client synchronization data according to the server synchronization data, specifically including the following steps: after the same data in the server side synchronous data and the client side synchronous data are filtered, when data A which exist in the server side synchronous data and do not exist in the client side synchronous data are monitored, the data A are added to the client side; when data B of the server side synchronous data and the client side synchronous data is monitored to be absent, deleting the data B on the client side; and when the server side synchronous data and the client side synchronous data are monitored to exist but different data C and D, replacing the data D on the client side with the data C on the server side.
Example five:
on the basis of the first embodiment, S2 further includes the following steps: and processing all services with the created failure marks and the deleted failure marks according to the step of S1, wherein the step is equivalent to performing secondary analysis processing on data which are failed in the previous processing, if the data are failed again, performing manual processing, and if the data are successful, not requiring manual processing, so that the probability of the manual processing is reduced, and the working precision is improved accordingly.
Example six: the client is an SPTN (Packet Transport Network, software defined Packet Transport Network) controller, and the server is a Network management server.
In the daytime, when the SPTN controller and the network management server perform network service data interaction once, the SPTN controller records interactive data information and interactive result information which are mutually associated; the types of network service interaction between the SPTN controller and the network management server include: the SPTN controller requests the network management server for creating service and for deleting service.
When the service a is requested to be created, the SPTN controller takes the sub-service a1 as an interactive service in the order of creation of the service a (sub-services a1, a2, A3, and a 4). The SPTN controller initiates the creation request of the interactive service to the network management server, and records the interactive data information of the interactive service. The service creation information returned by the network management server is service creation failure, at this time, the SPTN controller finds that the interaction is abnormal, and deletes the created interaction service in the network management server according to the deletion order of the service, i.e., a4, A3, a2 and a1 (at this time, deleting the sub-service a 1).
After the SPTN controller fails to create the sub-service a1 again according to the above flow for 2 times (i.e., the total number of failures is 3 times, and the designated threshold is also 3), the SPTN controller marks the creation failure of the service a.
When requesting to delete the service a, the SPTN controller takes the first sub-service a4 to be deleted as an interactive service according to the deletion order of the services (sub-services a4, A3, a2 and a 1). The SPTN controller initiates the deletion request of the interactive service to the network management server, and records the interactive data information of the interactive service. And the service deletion information returned by the network management server is service deletion failure, and the SPTN controller finds interaction abnormity at the moment.
After deleting the sub-service a4 again for 2 times (namely, the total number of failures is 3 times, and the designated threshold is also 3) according to the above flow, the SPTN controller marks the deletion failure of the service a.
And acquiring synchronous data of the SPTN controller and synchronous data of the network management server within 12 hours at the end of the day, wherein the synchronous data of the SPTN controller is all service data interacted with the network management server on the SPTN controller, and the synchronous data of the network management server is all service data interacted with the SPTN controller on the network management server. The method for acquiring the synchronous data of the network management server comprises the following steps: and calling a network management server to obtain a full circuit interface, obtaining the serial number of the network management full circuit and the final processing time of the circuit, and filtering the circuit data of the SPTN controller in the appointed time period through the configuration of the SPTN controller.
The method specifically comprises the following steps of carrying out full detection on the synchronous data of the network management server and the synchronous data of the SPTN controller, wherein the full detection is divided into 2 aspects:
firstly, synchronizing the synchronous data of the SPTN controller according to the synchronous data of the network management server: after the same data in the network management server synchronous data and the SPTN controller synchronous data are filtered, monitoring data A which exists in the network management server synchronous data and does not exist in the SPTN controller synchronous data, and data C and data D which exist in the network management server synchronous data and the SPTN controller synchronous data but are different; and the SPTN controller adds data A and replaces the data D with data C on the network management server.
And secondly, processing all services with the creation failure marks and the deletion failure marks according to a service processing mode in the daytime.
The network data synchronization system in the embodiment of the invention comprises a network data interaction module and a network data synchronization module which are arranged on a client.
The network data interaction module is used for: recording interactive data information and interactive result information which are correlated with each other when the client and the server perform network service data interaction once; and when the interaction result information represents that the interaction is abnormal, processing corresponding service data in the server according to the interaction data information associated with the interaction result information.
The types of network service interaction between the client and the server comprise: the client requests the service creation from the server, and at this time, the network data interaction module is specifically configured to: according to the creation sequence of the service, after the first sub-service to be created is taken as an interactive service, entering a service interaction flow;
the service interaction process comprises the following steps: initiating a creation request of an interactive service to a server, recording interactive data information of the interactive service, and using service creation information returned by the server as interactive result information of the interactive service and associating the interactive result information with the interactive data information; if the interactive result information is that the interactive service is successfully established, according to the establishing sequence of the service, the next sub-service to be established is used as the interactive service, and then the service interaction flow is re-entered; if the interactive result information is interactive service creation failure, representing interactive exception, and deleting interactive service data corresponding to the interactive data information in the server according to the deleting sequence of the service after acquiring the interactive data information of all interactive services; judging whether the number of times of service creation failure is above a specified threshold value, if so, marking the service creation failure, and ending; if not, the operation is restarted.
The network data synchronization module is used for: processing all services with the creation failure marks according to the working mode of the network data interaction module; the method comprises the steps that client side synchronous data and server side synchronous data in a specified time period are obtained, the client side synchronous data are all service data interacted with a server side on the client side, and the server side synchronous data are all service data interacted with the client side on the server side; according to the server side synchronous data, synchronizing the client side synchronous data, wherein the synchronizing mode is as follows: when data A of the existence of server side synchronous data and the nonexistence of client side synchronous data are monitored, adding the data A on the client side; when data B of the server side synchronous data and the client side synchronous data is monitored to be absent, deleting the data B on the client side; and when the server side synchronous data and the client side synchronous data are monitored to exist but different data C and D, replacing the data D on the client side with the data C on the server side.
It should be noted that: in the system provided in the embodiment of the present invention, when performing inter-module communication, only the division of each functional module is illustrated, and in practical applications, the above function distribution may be completed by different functional modules as needed, that is, the internal structure of the system is divided into different functional modules to complete all or part of the above described functions.
Further, the present invention is not limited to the above-mentioned embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and these modifications and improvements are also considered to be within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.
Claims (8)
1. A method for synchronizing network data, the method comprising the steps of:
s1: the method comprises the steps that when a client and a server perform network service data interaction once, the client records interactive data information and interactive result information which are correlated with each other; when the interaction result information represents that the interaction is abnormal, the client processes corresponding service data in the server according to the interaction data information associated with the interaction result information;
s2: the method comprises the steps that a client side obtains client side synchronous data and server side synchronous data in a specified time period, the client side synchronous data are all service data interacted with a server side on the client side, and the server side synchronous data are all service data interacted with the client side on the server side; synchronizing the client synchronous data according to the server synchronous data;
the types of network service interaction between the client and the server in S1 include: the client requests the service end to create a service, and S1 includes the following steps:
s101: the client takes the first sub-service to be created as an interactive service according to the creation sequence of the service, and goes to S102;
s102: the client initiates a request for creating the interactive service to the server, records interactive data information of the interactive service, and goes to S103;
s103: the client uses the service creation information returned by the server as the interaction result information of the interaction service and is associated with the interaction data information; if the interactive result information is that the interactive service is successfully established, the step goes to S104; if the interactive result information is that the interactive service is failed to be established, representing that the interaction is abnormal, and turning to S105;
s104: the client takes the next sub-service to be created as an interactive service according to the creation sequence of the service, and goes to S102;
s105: and after the client acquires the interactive data information of all interactive services, deleting the interactive service data corresponding to the interactive data information in the server according to the deleting sequence of the services.
2. The method for synchronizing network data according to claim 1, wherein: after the client deletes the interactive service data in the server in S105, the method further includes the following steps: the client judges whether the times of the service creation failure are above a specified threshold, if so, the service is marked with the creation failure, and the process is finished; if not, go to S101.
3. The method for synchronizing network data according to claim 2, wherein: s2 further includes the steps of: all services for which there is a creation failure flag are processed according to the step of S1.
4. A method for synchronizing network data according to any one of claims 1 to 3, characterized in that: when the client synchronization data is synchronized according to the server synchronization data in S2, the method includes the following steps: when data A of the existence of server side synchronous data and the nonexistence of client side synchronous data are monitored, adding the data A on the client side; when data B of the server side synchronous data and the client side synchronous data is monitored to be absent, deleting the data B on the client side; and when the server side synchronous data and the client side synchronous data are monitored to exist but different data C and D, replacing the data D on the client side with the data C on the server side.
5. A system for synchronizing network data, comprising: the system comprises a network data interaction module and a network data synchronization module which are arranged on a client;
the network data interaction module is used for: recording interactive data information and interactive result information which are correlated with each other when the client and the server perform network service data interaction once; when the interaction result information represents that the interaction is abnormal, processing corresponding service data in the server according to the interaction data information associated with the interaction result information;
the network data synchronization module is used for: the method comprises the steps that client side synchronous data and server side synchronous data in a specified time period are obtained, the client side synchronous data are all service data interacted with a server side on the client side, and the server side synchronous data are all service data interacted with the client side on the server side; synchronizing the client synchronous data according to the server synchronous data;
the types of network service interaction between the client and the server comprise: the client requests the service creation from the server, and at this time, the network data interaction module is specifically configured to: according to the creation sequence of the service, after the first sub-service to be created is taken as an interactive service, entering a service interaction flow;
the service interaction process comprises the following steps: initiating a creation request of an interactive service to a server, recording interactive data information of the interactive service, and using service creation information returned by the server as interactive result information of the interactive service and associating the interactive result information with the interactive data information; if the interactive result information is that the interactive service is successfully established, according to the establishing sequence of the service, the next sub-service to be established is used as the interactive service, and then the service interaction flow is re-entered; and if the interactive result information is that the interactive service is failed to be established, representing that the interaction is abnormal, and deleting the interactive service data corresponding to the interactive data information in the server according to the deleting sequence of the service after acquiring the interactive data information of all the interactive services.
6. The system for synchronizing network data according to claim 5, wherein: after the network data interaction module deletes the interaction service data in the server, the network data interaction module is further configured to: judging whether the number of times of service creation failure is above a specified threshold value, if so, marking the service creation failure, and ending; if not, the operation is restarted.
7. The system for synchronizing network data according to claim 6, wherein: the network data synchronization module is further configured to: and processing all services with the creation failure marks according to the working mode of the network data interaction module.
8. The system for synchronizing network data according to any one of claims 5 to 7, wherein: the network data synchronization module synchronizes the client synchronous data according to the server synchronous data, and comprises the following steps: when data A of the existence of server side synchronous data and the nonexistence of client side synchronous data are monitored, adding the data A on the client side; when data B of the server side synchronous data and the client side synchronous data is monitored to be absent, deleting the data B on the client side; and when the server side synchronous data and the client side synchronous data are monitored to exist but different data C and D, replacing the data D on the client side with the data C on the server side.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810264721.1A CN108494859B (en) | 2018-03-28 | 2018-03-28 | Network data synchronization method and system |
| PCT/CN2018/103282 WO2019184241A1 (en) | 2018-03-28 | 2018-08-30 | Method and system for synchronizing network data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810264721.1A CN108494859B (en) | 2018-03-28 | 2018-03-28 | Network data synchronization method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108494859A CN108494859A (en) | 2018-09-04 |
| CN108494859B true CN108494859B (en) | 2020-07-14 |
Family
ID=63316517
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810264721.1A Active CN108494859B (en) | 2018-03-28 | 2018-03-28 | Network data synchronization method and system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108494859B (en) |
| WO (1) | WO2019184241A1 (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1996855A (en) * | 2006-12-22 | 2007-07-11 | 中国建设银行股份有限公司 | A method and system for keeping data consistency |
| CN101765100A (en) * | 2009-08-14 | 2010-06-30 | 北京握奇数据系统有限公司 | Method, system and device for realizing mobile office |
| CN103368919A (en) * | 2012-04-06 | 2013-10-23 | 中国银联股份有限公司 | Security information interaction system, terminal, server and method based on thin terminal mode |
| CN103605703A (en) * | 2013-11-08 | 2014-02-26 | 北京奇虎科技有限公司 | Method and system for data consistency detection among multiple platforms |
| CN103839340A (en) * | 2012-11-27 | 2014-06-04 | 中国电信股份有限公司 | Method and system for synchronizing electronic purse information and over-the-air earmarking service platform |
| CN106130751A (en) * | 2016-05-27 | 2016-11-16 | 努比亚技术有限公司 | A kind of upgrade status data administrator, system and method |
| CN106572173A (en) * | 2016-11-07 | 2017-04-19 | 网易无尾熊（杭州）科技有限公司 | Method, apparatus and system for updating configuration information |
| CN106603662A (en) * | 2016-12-14 | 2017-04-26 | 日照职业技术学院 | Realizing method of comprehensive intelligent platform with homogenous Internet-of-things and Internet |
| CN106993015A (en) * | 2016-01-21 | 2017-07-28 | 阿里巴巴集团控股有限公司 | Synchronous method, system and the security server of transaction |
| CN107146607A (en) * | 2017-04-10 | 2017-09-08 | 北京猎户星空科技有限公司 | Modification method, the apparatus and system of smart machine interactive information |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017000144A1 (en) * | 2015-06-30 | 2017-01-05 | 华为技术有限公司 | Dns server, client and data synchronization method |
| DE212016000195U1 (en) * | 2016-07-05 | 2018-04-26 | Obshchestvo S Ogranichennoy Otvetstvennostyu "Rm" | On-board media device for rail vehicles |
| CN106921734B (en) * | 2017-02-13 | 2020-04-03 | 上海大学 | Client and server data interaction method based on selective caching and synchronization |
-
2018
- 2018-03-28 CN CN201810264721.1A patent/CN108494859B/en active Active
- 2018-08-30 WO PCT/CN2018/103282 patent/WO2019184241A1/en active Application Filing
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1996855A (en) * | 2006-12-22 | 2007-07-11 | 中国建设银行股份有限公司 | A method and system for keeping data consistency |
| CN101765100A (en) * | 2009-08-14 | 2010-06-30 | 北京握奇数据系统有限公司 | Method, system and device for realizing mobile office |
| CN103368919A (en) * | 2012-04-06 | 2013-10-23 | 中国银联股份有限公司 | Security information interaction system, terminal, server and method based on thin terminal mode |
| CN103839340A (en) * | 2012-11-27 | 2014-06-04 | 中国电信股份有限公司 | Method and system for synchronizing electronic purse information and over-the-air earmarking service platform |
| CN103605703A (en) * | 2013-11-08 | 2014-02-26 | 北京奇虎科技有限公司 | Method and system for data consistency detection among multiple platforms |
| CN106993015A (en) * | 2016-01-21 | 2017-07-28 | 阿里巴巴集团控股有限公司 | Synchronous method, system and the security server of transaction |
| CN106130751A (en) * | 2016-05-27 | 2016-11-16 | 努比亚技术有限公司 | A kind of upgrade status data administrator, system and method |
| CN106572173A (en) * | 2016-11-07 | 2017-04-19 | 网易无尾熊（杭州）科技有限公司 | Method, apparatus and system for updating configuration information |
| CN106603662A (en) * | 2016-12-14 | 2017-04-26 | 日照职业技术学院 | Realizing method of comprehensive intelligent platform with homogenous Internet-of-things and Internet |
| CN107146607A (en) * | 2017-04-10 | 2017-09-08 | 北京猎户星空科技有限公司 | Modification method, the apparatus and system of smart machine interactive information |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108494859A (en) | 2018-09-04 |
| WO2019184241A1 (en) | 2019-10-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108600353B (en) | Parallel block synchronization method of block chain nodes | |
| CN106407030A (en) | Failure processing method and system for storage cluster system | |
| CN105867837A (en) | Method, equipment and system for updating configurations of clients in distributed high-speed cache systems | |
| CN107357681B (en) | Salt-based Zookeeper backup management system and method | |
| CN109542330B (en) | Data storage method, data query method and device | |
| CN112711496A (en) | Log information full link tracking method and device, computer equipment and storage medium | |
| CN108494859B (en) | Network data synchronization method and system | |
| CN110912979B (en) | Method for solving multi-server resource synchronization conflict | |
| CN107105037B (en) | Distributed video CDN resource management system and method based on file verification | |
| CN112749142B (en) | Handle management method and system | |
| CN113055203B (en) | Method and device for recovering exception of SDN control plane | |
| CN111338573B (en) | Terminal data management method and system, server and communication terminal | |
| CN111090648B (en) | Relational database data synchronization conflict resolution method | |
| CN115543585B (en) | Enterprise number card data synchronization method, server and storage medium | |
| CN105765908B (en) | A kind of multi-site automatic update method, client and system | |
| CN111917826A (en) | PBFT consensus algorithm based on block chain intellectual property protection | |
| CN111241200A (en) | sSQLite database-based main and standby synchronous processing method and device | |
| CN112667449B (en) | Cluster management method and device | |
| CN115809301B (en) | Database processing method and device, electronic equipment and readable storage medium | |
| CN115017235B (en) | Data synchronization method, electronic device and storage medium | |
| CN115396290B (en) | Automatic fault recovery method, device and service system | |
| KR102235670B1 (en) | Apparatus and Method for processing failure of a transport network | |
| CN117061313A (en) | Block chain-based node monitoring method and device, electronic equipment and product | |
| CN116963119A (en) | Service changing method and system | |
| CN106209917B (en) | Control method and system for synchronous server cluster configuration and safety control server |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |