WO2019184241A1

WO2019184241A1 - Method and system for synchronizing network data

Info

Publication number: WO2019184241A1
Application number: PCT/CN2018/103282
Authority: WO
Inventors: 凃超
Original assignee: 烽火通信科技股份有限公司
Priority date: 2018-03-28
Filing date: 2018-08-30
Publication date: 2019-10-03
Also published as: CN108494859A; CN108494859B

Abstract

Disclosed in the present invention are a method and a system for synchronizing network data, relating to the field of network data exchange and comparison. Said method comprises the following steps: every time a client end and a server perform network traffic data exchange, the client end records exchange data information and exchange result information; when the exchange result information indicates that the exchange is abnormal, the client end processes corresponding traffic data in the server according to exchange data information associated with the exchange result information; the client end acquires client-end synchronization data and server synchronization data within a specified time period, the client-end synchronization data being all the traffic data on the client end exchanged with the server, and the server synchronization data being all the traffic data on the server exchanged with the client end; and synchronizing the client-end synchronization data according to the server synchronization data. The present invention enables a client end to automatically process abnormal data when an abnormality occurs during an exchange between the client end and a server, thereby ensuring data synchronization between the client end and the server.

Description

Network data synchronization method and system

Technical field

The present invention relates to the field of interaction and comparison of network data, and in particular to a method and system for synchronizing network data.

Background technique

With the rapid development of communication technologies, the types of services and service scenarios of the transmission network increase, and the network services for the client and the server to interact are also increasing. The process of the client and the server performing the network service interaction includes: the client requests the server to create the service, and the client requests the server to delete the created service, and one service is created or deleted, and actually creates or deletes multiple sub-services. The process, for example, the process of creating service A is: creating sub-service A1 (service tunnel), sub-service A2 (service pseudo-line), sub-service A3 (service protection), and sub-service A4 (service establishment) in order, and deleting the service Reason.

The process of the client requesting the server to create a service includes: requesting the service to create a service according to the order in which the service is created; for example, the service A is created in the order of A1, A2, A3, and A4, and then the client requests the creation of the server in turn. A1, A2, A3 and A4 services.

The process of the client requesting the server to delete the created service includes: the client requests the server to delete the service according to the deletion order of the service (the reverse order of the service creation order), for example, the deletion order of the service A is A4, A3, A2, and A1, the client sequentially requests the server to delete the A4, A3, A2, and A1 services.

However, when the existing client and the server perform network service interaction, the following defects exist:

When the client requests the server to create and delete a service, if the creation or deletion fails, some of the remaining parts of the server are successfully created. For example, if A1 and A2 are created successfully and A3 fails, the data of A1 and A2 remains in the server. And deleting the failed data, the residual data needs to be manually cleared by the maintenance personnel. In the scenario where the number of services is increasing, it is difficult for maintenance personnel to effectively remove the residual data. When there is more residual data, it is not only inconvenient for data management, but also Seriously reduce the efficiency of the server, and even cause server downtime.

In addition, the data of the client and the server are kept consistent, so that the service in the client is maintained, and the client needs to periodically synchronize the service data with the server. The synchronization method is: the client periodically generates the created service data table. The server requests to generate the created service data table 2, and the maintenance personnel means to compare the service data tables 1 and 2, and then synchronize the data of the service data table 1 according to the data of the service data table 2.

However, when the client and the server synchronize the service data, if the service data is relatively complicated, the precision of the manual comparison of the service data by the maintenance personnel is low, thereby reducing the synchronization quality of the service data between the client and the server.

Summary of the invention

In view of the deficiencies in the prior art, the technical problem solved by the present invention is: how the client automatically processes the abnormal data when the client interacts with the server, so as to maintain the data synchronization between the client and the server.

To achieve the above objective, the method for synchronizing network data provided by the present invention includes the following steps:

S1: When the client and the server perform the network service data interaction, the client records the interaction data information and the interaction result information associated with each other; when the interaction result information represents the interaction abnormality, the client performs the interaction data associated with the interaction result information. Information, processing corresponding business data in the server;

S2: The client obtains the client synchronization data and the server synchronization data in the specified time period, the client synchronization data is all the service data that the client interacts with the server, and the server synchronization data is the server interaction with the client. All business data; synchronize the client synchronization data according to the server synchronization data.

On the basis of the foregoing technical solution, the type of network service interaction between the client and the server in the S1 includes: the client requests the service to create a service, and the S1 includes the following steps:

S101: The client uses the first sub-service to be created as an interactive service according to the order in which the service is created, and the process goes to S102;

S102: The client initiates a request for creating an interactive service to the server, and records the interaction data information of the interactive service, and proceeds to S103.

S103: The client sends 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 interaction result information is successfully created for the interaction service, go to S104; if the interaction result information is created for the interaction service If it fails, it means an interaction exception, go to S105;

S104: The client uses the sub-service to be created as the interactive service according to the order in which the service is created, and the process proceeds to S102.

S105: After obtaining the interaction data information of all the interaction services, the client deletes the interaction service data corresponding to the interaction data information in the server according to the deletion order of the service.

On the basis of the foregoing technical solution, after the client deletes the interactive service data in the server, the method includes the following steps: the client determines whether the number of times the service creation fails is greater than a specified threshold, and if so, fails to create a failure flag for the service. , end; if not, go to S101.

Based on the above technical solution, S2 further includes the following steps: processing all the services with the creation failure flag according to the step of S1.

On the basis of the foregoing technical solution, when synchronizing the client synchronization data according to the server synchronization data, the following steps are included in the S2: when the data A of the server synchronization data exists and the client synchronization data does not exist is detected. Adding data A on the client; when monitoring the data that the server synchronization data does not exist and the client synchronizes the data, the data B is deleted on the client; when the server synchronization data and the client synchronization data are detected, When there are different but different data C and D, the data D on the client is replaced with the data C on the server.

The network data synchronization system provided by the invention comprises a network data interaction module and a network data synchronization module arranged on the client;

The network data interaction module is configured to: when the client and the server perform the network service data interaction, record the interaction data information and the interaction result information; when the interaction result information represents the interaction abnormality, according to the interaction associated with the interaction result information Data information, processing corresponding business data in the server;

The network data synchronization module is configured to: acquire client synchronization data and server synchronization data in a specified time period, and client synchronization data is all service data that the client interacts with the server, and the server synchronization data is a server and a client. All business data exchanged by the terminal; synchronization of the client synchronization data according to the server synchronization data.

On the basis of the foregoing technical solution, the type of the network service interaction performed by the client and the server includes: the client requests the service to create a service, and the network data interaction module is specifically configured to: according to the order in which the service is created, After the first sub-service that needs to be created is used as an interactive service, the business interaction process is entered;

The business interaction process is: initiating a request for creating an interactive service to the server, and recording the interaction data information of the interaction service, and using the service creation information returned by the server as the interaction result information of the interaction service and associating with the interaction data information; The result information is that the interactive service is created successfully. After the next sub-service that needs to be created is used as the interactive service, the business interaction process is re-entered. If the interaction result information fails to be created, the interaction abnormality is obtained. After the interaction data of the interaction service, the interaction service data corresponding to the interaction data information is deleted in the server according to the deletion order of the service.

On the basis of the foregoing technical solution, after the network data interaction module deletes the interaction service data in the server, it is also used to: determine whether the number of times the service creation failure is above a specified threshold, and if so, create a failure flag for the service. End; if not, start working again.

On the basis of the foregoing technical solution, the network data synchronization module is further configured to: process all services that have a creation failure flag according to the working mode of the network data interaction module.

On the basis of the foregoing technical solution, when the network data synchronization module synchronizes the client synchronization data according to the server synchronization data, the following steps are included: when the server synchronization data exists and the client synchronization data does not exist, A, the data A is added on the client; when it is detected that the server synchronization data does not exist, the client synchronizes the data B, the data B is deleted on the client; when the server synchronization data is detected and the client synchronizes When data exists but different data C and D, the data D on the client is replaced with the data C on the server.

The advantages of the present invention over the prior art are:

(1) Referring to S1 of the method of the present invention, the present invention records interaction data information and interaction result information each time the client and the server perform business interaction; when the interaction result information represents an interaction exception, the client bases The interaction data information associated with the interaction result information is used to process the corresponding service data in the server. For example, when the service fails to be created, the residual data in the server is automatically reversed. Therefore, compared with the residual data when the interaction abnormality is manually cleared in the prior art, the present invention can immediately clear the abnormal data, which not only ensures the data synchronization precision between the client and the server, but also ensures the integrity of the single service. .

(2) Compared with the method of manually comparing the service data in the prior art, referring to S2 of the method of the present invention, the present invention can automatically synchronize the corresponding data of the client according to the server data in the specified time period. , further improving the data synchronization accuracy between the client and the server.

(3) Referring to S2 of the method of the present invention, after the abnormal interaction between the client and the server, the present invention performs secondary analysis processing on the abnormal service, and if it fails again, it is manually processed, and if successful, no manual processing is required. In turn, the probability of manual processing is reduced, and the accuracy of the work is also improved, and the risk of data security and correctness can be minimized to ensure the consistency of data between the client and the server.

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 further described in detail below with reference to the accompanying drawings and embodiments.

Referring to FIG. 1 , a method for synchronizing network data in an embodiment of the present invention includes the following steps:

S1: When the client and the server perform the network service data interaction, the client records the interaction data information and the interaction result information associated with each other; when the interaction result information represents the interaction abnormality, the client performs the interaction data associated with the interaction result information. Information, processing corresponding business data in the server.

S2: The client obtains the client synchronization data and the server synchronization data in the specified time period, the client synchronization data is all the service data that the client interacts with the server, and the server synchronization data is the server interaction with the client. All service data; according to the server synchronization data, the client synchronization data is synchronized, and the execution time of S2 can be performed periodically, that is, S2 may be performed before, after, or during S1 execution.

The method of the present invention will be described in detail below by means of six embodiments.

Embodiment 1:

The type of the network service interaction between the client and the server in the S1 includes: the client requests the service to create a service, and the S1 includes the following steps:

S101: The client uses the first sub-service that needs to be created as the interactive service according to the order in which the service is created, and the process goes to S102.

S102: The client initiates a request for creating an interactive service to the server (each time the creation request is considered to be a network service data interaction), and records the interaction data information of the interaction service (the interaction data information includes an interaction service type, an operation type, and Specific interactive business data), go to S103.

S103: The client creates the service creation information returned by the server as the interaction result information of the interaction service (if the interaction result information already exists, directly covers the information), and associates with the interaction data information; if the interaction result information is successfully created for the interaction service, Go to S104; if the interaction result information is that the interaction service creation fails, it represents an interaction exception, and go to S105.

S104: The client forwards the sub-service to be created as the interactive service to the S102 according to the order in which the service is created. If the sub-service that needs to be created is not the next one, the S1 ends.

S105: After the client obtains the interaction data information of all the interaction services, the interaction service data corresponding to the interaction data information is deleted in the server according to the deletion order of the service (the reverse order of the service creation order); for example, the service A is created. The creation process is to create A1, A2, A3, and A4. If the A3 fails to be created on the server, the A2 and A1 data are deleted in the server. In this case, the creation failure flag can be created for the service to be created. deal with.

The type of network service interaction between the client and the server in S1 includes: the client requests the server to delete the service, and the S1 includes the following steps:

S101a: The client moves the first sub-service that needs to be deleted as an interactive service according to the deletion order of the service, and the process goes to S102a.

S102a: The client initiates a deletion request of the interactive service to the server (the transmission request is considered to be a business interaction every time the deletion request is sent), and records the interaction data information of the interaction service (the interaction data information includes the interaction service type, the operation type, and the specific Interactive business data), go to S103a.

S103a: The client deletes the service deletion information returned by the server as the interaction result information of the interaction service (if the interaction result information already exists, directly covers the information), and associates with the interaction data information; if the interaction result information is that the interaction service is deleted successfully, Go to S104a; if the interaction result information is that the interactive service deletion fails, the interaction is abnormal. In this case, the deletion failure flag may be marked on the service to be deleted in S101a, so as to be manually processed later.

S104a: The client sends the next sub-service to be deleted as the interactive service to S102a according to the deletion order of the service; if there is no sub-service to be deleted, the service is deleted successfully, and S1 ends.

Embodiment 2:

On the basis of the first embodiment, after the client deletes the interactive service data in the server, the method includes the following steps: the client determines whether the number of times the service creation fails is greater than a specified threshold, and if yes, the service has been created multiple times. However, all of them fail. If they are created again, there is a high probability that they will not succeed. In order to improve the working efficiency of the client and the server, the service is not created at this time, the creation failure flag is marked for the service, and the process ends; if not, it can be created again. Go to S101.

Embodiment 3:

On the basis of the first embodiment, if the interaction result information in the S103a is the deletion of the interactive service, the method includes the following steps: the client determines whether the number of times the service deletion fails is greater than a specified threshold, and if yes, the service has been deleted multiple times. However, all of them fail, and there is a high probability that the deletion will not succeed. In order to improve the working efficiency of the client and the server, the service deletion is not performed at this time, and the deletion failure flag is marked for the service, and the process ends; if not, the deletion can be performed again. Go to S101a.

Embodiment 4:

S2 synchronizes the client synchronization data according to the server synchronization data, and specifically includes the following steps: after filtering the same data in the server synchronization data and the client synchronization data, when the server synchronization data is detected, the client exists. When the data A that does not exist in the synchronization data is synchronized, the data A is added on the client; when the data B in which the server synchronization data does not exist and the client synchronization data exists is detected, the data B is deleted on the client; when the server is detected When both the synchronous data and the client synchronization data exist, but different data C and D, the data D on the client is replaced with the data C on the server.

Embodiment 5:

On the basis of the first embodiment, S2 further includes the following steps: processing all the services with the creation failure flag and the deletion failure flag according to the step of S1, which is equivalent to the data that has been previously processed and then analyzed twice, if it fails again. , it is manually processed, if it is successful, no manual processing is required, thereby reducing the probability of manual processing, and thus improving the working precision.

Embodiment 6: The client is an SPTN (S Packet Transport Network) controller, and the server is a network management server.

During the daytime, the SPTN controller records the interrelated interaction data information and the interaction result information when the SPTN controller interacts with the network management server. The types of network service interaction between the SPTN controller and the network management server include: SPTN control. The device requests the NMS server to create a service and request to delete the service.

When requesting to create service A, the SPTN controller uses sub-service A1 as an interactive service according to the order in which service A is created (sub-services A1, A2, A3, and A4). The SPTN controller initiates a request for creating an interactive service to the network management server, and records interactive data information of the interactive service. The service creation information returned by the network management server fails to be created. In this case, the SPTN controller finds that the interaction is abnormal. After the service is deleted, the A7, A3, A2, and A1 are deleted. A1).

After the SPTN controller creates the sub-service A1 again twice according to the above procedure (that is, the total number of failures is 3 and the specified threshold is also 3), the service A fails to be created.

When requesting to delete service A, the SPTN controller uses the first sub-service A4 to be deleted as the interactive service according to the service deletion order (sub-services A4, A3, A2, and A1). The SPTN controller initiates a deletion request for the interaction service to the network management server, and records the interaction data information of the interaction service. The service deletion information returned by the NMS server is that the service deletion fails. At this time, the SPTN controller finds that the interaction is abnormal.

After the SPTN controller deletes the sub-service A4 again twice according to the above procedure (that is, the total number of failures is 3 and the specified threshold is also 3), the service A is marked with a deletion failure flag.

At the end of the day, the synchronization data of the SPTN controller and the network management server are synchronized within 12 hours. The synchronization data of the SPTN controller is all the service data exchanged with the network management server on the SPTN controller. The synchronization data of the network management server is the interaction with the SPTN controller on the network management server. All business data. The synchronization data of the network management server is obtained by calling the network management server to obtain the full circuit interface, obtaining the full circuit number of the network management system and the last processing time of the circuit, and configuring the SPTN controller to filter the circuit data of the specified time period of the SPTN controller.

The network management server synchronization data and the SPTN controller synchronization data are fully detected, which are divided into two aspects:

1. Synchronize the synchronization data of the SPTN controller according to the synchronization data of the network management server: after filtering the same data in the synchronization data of the network management server and the synchronization data of the SPTN controller, the synchronization data of the network management server is detected, and the synchronization data of the SPTN controller is not The existing data A, and the network management server synchronization data and the SPTN controller synchronization data exist, but different data C and D; the SPTN controller adds data A to replace the data D with the data C on the network management server.

Second, according to the day-to-day business processing method, all the services with the creation failure flag and the deletion failure flag are processed.

The network data synchronization system in the embodiment of the present invention includes a network data interaction module and a network data synchronization module disposed on the client.

The network data interaction module is configured to: when the client and the server perform the network service data interaction, record the interaction data information and the interaction result information; when the interaction result information represents the interaction abnormality, according to the interaction associated with the interaction result information Data information, processing corresponding business data in the server.

The type of the network service interaction between the client and the server includes: the client requests the server to create a service, and the network data interaction module is specifically configured to: according to the service creation order, the first sub-service to be created. After the interactive service, enter the business interaction process;

The business interaction process is: initiating a request for creating an interactive service to the server, and recording the interaction data information of the interaction service, and using the service creation information returned by the server as the interaction result information of the interaction service and associating with the interaction data information; The result information is that the interactive service is created successfully. After the next sub-service that needs to be created is used as the interactive service, the business interaction process is re-entered. If the interaction result information fails to be created, the interaction abnormality is obtained. After the interaction data of the interactive service is deleted, the interaction service data corresponding to the interaction data information is deleted in the server according to the deletion order of the service; and the number of times the service creation failure is determined to be above a specified threshold, and if so, the service fails to be marked. , end; if not, start working again.

The network data synchronization module is configured to: process all the services with the creation failure flag according to the working mode of the network data interaction module; acquire the client synchronization data and the server synchronization data in the specified time period, and the client synchronization data is the client and the service. All service data exchanged by the server, the server synchronization data is all service data interacting with the client on the server; according to the server synchronization data, the synchronization data of the client is synchronized, and the synchronization mode is: when the synchronization data of the server is detected When the client synchronizes the data A that does not exist in the data, the data A is added to the client; when the data of the client synchronization data does not exist and the client synchronizes the data, the data B is deleted on the client; when monitoring When the server-side synchronization data and the client-side synchronization data exist, but different data C and D, the data D on the client is replaced with the data C on the server.

It should be noted that, when the system provided by the embodiment of the present invention performs inter-module communication, only the division of the above functional modules is illustrated. In actual applications, the function distribution may be completed by different functional modules as needed. The internal structure of the system is divided into different functional modules to complete all or part of the functions described above.

Further, the present invention is not limited to the above embodiments, and those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. These improvements and refinements are also considered as the present invention. Within the scope of protection. The contents not described in detail in the present specification belong to the prior art well known to those skilled in the art.

Claims

A method for synchronizing network data, characterized in that the method comprises the following steps:

S1: When the client and the server perform the network service data interaction, the client records the interaction data information and the interaction result information associated with each other; when the interaction result information represents the interaction abnormality, the client performs the interaction data associated with the interaction result information. Information, processing corresponding business data in the server;

S2: The client obtains the client synchronization data and the server synchronization data in the specified time period, the client synchronization data is all the service data that the client interacts with the server, and the server synchronization data is the server interaction with the client. All business data; synchronize the client synchronization data according to the server synchronization data.
The method for synchronizing network data according to claim 1, wherein the type of the network service interaction between the client and the server in the S1 includes: the client requests the server to create a service, and the S1 includes the following steps:

S101: The client uses the first sub-service to be created as an interactive service according to the order in which the service is created, and the process goes to S102;

S102: The client initiates a request for creating an interactive service to the server, and records the interaction data information of the interactive service, and proceeds to S103.

S103: The client sends 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 interaction result information is successfully created for the interaction service, go to S104; if the interaction result information is created for the interaction service If it fails, it means an interaction exception, go to S105;

S104: The client uses the sub-service to be created as the interactive service according to the order in which the service is created, and the process proceeds to S102.

S105: After obtaining the interaction data information of all the interaction services, the client deletes the interaction service data corresponding to the interaction data information in the server according to the deletion order of the service.
The method for synchronizing network data according to claim 2, wherein after the client deletes the interactive service data in the server, the method further includes the following steps: the client determines whether the number of times the service creation fails is above a specified threshold. If yes, the creation failure flag is marked for the service, and if not, go to S101.
The method for synchronizing network data according to claim 3, characterized in that: S2 further comprises the step of processing all the services having the creation failure flag in accordance with the step of S1.
The method for synchronizing network data according to any one of claims 1 to 4, wherein: when synchronizing the client synchronization data according to the server synchronization data in S2, the method includes the following steps: when the server is monitored When the synchronous data exists and the client synchronizes the data A that does not exist, the data A is added to the client; when the data of the client synchronization data does not exist and the client synchronizes the data, the data B is deleted on the client. When it is detected that both the server synchronization data and the client synchronization data exist, but different data C and D, the data D on the client is replaced with the data C on the server.
A synchronization system for network data, characterized in that: the system comprises a network data interaction module and a network data synchronization module arranged on the client;

The network data interaction module is configured to: when the client and the server perform the network service data interaction, record the interaction data information and the interaction result information; when the interaction result information represents the interaction abnormality, according to the interaction associated with the interaction result information Data information, processing corresponding business data in the server;

The network data synchronization module is configured to: acquire client synchronization data and server synchronization data in a specified time period, and client synchronization data is all service data that the client interacts with the server, and the server synchronization data is a server and a client. All business data exchanged by the terminal; synchronization of the client synchronization data according to the server synchronization data.
The network data synchronization system according to claim 6, wherein the type of the network service interaction between the client and the server comprises: the client requests the server to create a service, and the network data interaction module is specifically used by the client. In: according to the order in which the business is created, after the first sub-service that needs to be created is used as an interactive service, the business interaction process is entered;

The business interaction process is: initiating a request for creating an interactive service to the server, and recording the interaction data information of the interaction service, and using the service creation information returned by the server as the interaction result information of the interaction service and associating with the interaction data information; The result information is that the interactive service is created successfully. After the next sub-service that needs to be created is used as the interactive service, the business interaction process is re-entered. If the interaction result information fails to be created, the interaction abnormality is obtained. After the interactive data is exchanged, the interactive service data corresponding to the interaction data information is deleted in the server according to the deletion order of the service.
The network data synchronization system according to claim 7, wherein the network data interaction module is configured to: determine whether the number of times the service creation failure is above a specified threshold, if the interaction data is deleted in the server, if , create a failure flag for the business, and end; if not, restart the work.
The network data synchronization system according to claim 8, wherein the network data synchronization module is further configured to: process all the services with the creation failure flag according to the working mode of the network data interaction module.
The network data synchronization system according to any one of claims 6 to 9, wherein the network data synchronization module synchronizes the client synchronization data according to the server synchronization data, and includes the following steps: when monitoring When the server synchronous data exists and the client synchronizes the data A that does not exist, the data A is added to the client; when the server synchronous data does not exist and the client synchronizes the data B, the client deletes the data B. Data B; when it is detected that both the server synchronization data and the client synchronization data exist, but different data C and D, the data D on the client is replaced with the data C on the server.