WO2019184241A1 - Procédé et système de synchronisation de données de réseau - Google Patents

Procédé et système de synchronisation de données de réseau Download PDF

Info

Publication number
WO2019184241A1
WO2019184241A1 PCT/CN2018/103282 CN2018103282W WO2019184241A1 WO 2019184241 A1 WO2019184241 A1 WO 2019184241A1 CN 2018103282 W CN2018103282 W CN 2018103282W WO 2019184241 A1 WO2019184241 A1 WO 2019184241A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
client
interaction
server
service
Prior art date
Application number
PCT/CN2018/103282
Other languages
English (en)
Chinese (zh)
Inventor
凃超
Original Assignee
烽火通信科技股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 烽火通信科技股份有限公司 filed Critical 烽火通信科技股份有限公司
Publication of WO2019184241A1 publication Critical patent/WO2019184241A1/fr

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

Definitions

  • 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.
  • 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 are examples of 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.
  • the deletion order of the service is A4, A3, A2, and A1
  • the client sequentially requests the server to delete the A4, A3, A2, and A1 services.
  • the client requests the server to create and delete a service
  • 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 significantly reduce the efficiency of the server, and even cause server downtime.
  • 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.
  • 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.
  • the method for synchronizing network data includes the following steps:
  • 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 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.
  • 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.
  • S2 further includes the following steps: processing all the services with the creation failure flag according to the step of S1.
  • 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 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 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.
  • the business interaction process is re-entered. If the interaction result information fails to be created, the interaction abnormality is obtained.
  • the interaction service data corresponding to the interaction data information is deleted in the server according to the deletion order of the service.
  • 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.
  • 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.
  • 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
  • data exists but different data C and D the data D on the client is replaced with the data C on the server.
  • 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. .
  • 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.
  • 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.
  • FIG. 1 is a flowchart of a method for synchronizing network data according to an embodiment of the present invention.
  • a method for synchronizing network data in an embodiment of the present invention includes the following steps:
  • 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.
  • Embodiment 1 is a diagrammatic representation of 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.
  • the interaction data information includes an interaction service type, an operation type, and Specific interactive business data
  • 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.
  • 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.
  • 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 is a diagrammatic representation of Embodiment 1:
  • 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 is a diagrammatic representation of Embodiment 3
  • 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 is a diagrammatic representation of 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.
  • the data A that does not exist in the synchronization data is synchronized
  • the data A is added on the client
  • 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
  • the server is detected
  • 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 is a diagrammatic representation of Embodiment 5:
  • 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.
  • SPTN Packet Transport Network
  • the SPTN controller 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.
  • the SPTN controller 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).
  • 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.
  • the SPTN controller 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.
  • the SPTN controller 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.
  • 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:
  • 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.
  • the business interaction process is re-entered. If the interaction result information fails to be created, the interaction abnormality is obtained.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

La présente invention concerne un procédé et un système de synchronisation de données de réseau, se rapportant au domaine de la comparaison et de l'échange de données de réseau. Ledit procédé comprend les étapes suivantes : chaque fois qu'une extrémité client et un serveur réalisent un échange de données de trafic de réseau, l'extrémité client enregistre des informations de données d'échange et des informations de résultat d'échange ; lorsque les informations de résultat d'échange indiquent que l'échange est anormal, l'extrémité client traite des données de trafic correspondantes dans le serveur conformément aux informations de données d'échange associées aux informations de résultat d'échange ; l'extrémité client acquiert des données de synchronisation d'extrémité client et des données de synchronisation de serveur pendant une période de temps spécifiée, les données de synchronisation d'extrémité client étant toutes des données de trafic sur l'extrémité client échangées avec le serveur, et les données de synchronisation de serveur étant toutes des données de trafic sur le serveur échangées avec l'extrémité client ; et synchronise les données de synchronisation d'extrémité client conformément aux données de synchronisation de serveur. La présente invention permet à une extrémité client de traiter automatiquement des données anormales lorsqu'une anomalie se produit pendant un échange entre l'extrémité client et un serveur, assurant ainsi une synchronisation de données entre l'extrémité client et le serveur.
PCT/CN2018/103282 2018-03-28 2018-08-30 Procédé et système de synchronisation de données de réseau WO2019184241A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810264721.1 2018-03-28
CN201810264721.1A CN108494859B (zh) 2018-03-28 2018-03-28 网络数据的同步方法及系统

Publications (1)

Publication Number Publication Date
WO2019184241A1 true WO2019184241A1 (fr) 2019-10-03

Family

ID=63316517

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/103282 WO2019184241A1 (fr) 2018-03-28 2018-08-30 Procédé et système de synchronisation de données de réseau

Country Status (2)

Country Link
CN (1) CN108494859B (fr)
WO (1) WO2019184241A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1996855A (zh) * 2006-12-22 2007-07-11 中国建设银行股份有限公司 一种保持数据一致性的方法及系统
CN106464745A (zh) * 2015-06-30 2017-02-22 华为技术有限公司 Dns的服务器、客户端及数据同步方法
CN106921734A (zh) * 2017-02-13 2017-07-04 上海大学 一种基于选择性缓存与同步的客户端与服务器数据交互方法
WO2018009094A1 (fr) * 2016-07-05 2018-01-11 Общество С Ограниченной Ответственностью "Рм" Dispositif d'informations embarqué du matériel roulant des chemins de fer

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101765100B (zh) * 2009-08-14 2012-08-22 北京握奇数据系统有限公司 一种实现移动办公的方法、系统及装置
CN103368919B (zh) * 2012-04-06 2016-09-28 中国银联股份有限公司 基于瘦终端模式的安全性信息交互系统、终端、服务器及方法
CN103839340B (zh) * 2012-11-27 2016-08-10 中国电信股份有限公司 电子钱包信息同步的方法和系统、空中圈存业务平台
CN103605703B (zh) * 2013-11-08 2017-07-04 北京奇虎科技有限公司 一种多平台之间数据一致性检测的方法和系统
CN106993015A (zh) * 2016-01-21 2017-07-28 阿里巴巴集团控股有限公司 交易的同步方法、系统及证券服务器
CN106130751B (zh) * 2016-05-27 2019-05-17 努比亚技术有限公司 一种升级状态数据管理装置、系统和方法
CN106572173B (zh) * 2016-11-07 2020-06-09 阿里巴巴（中国）有限公司 一种配置信息更新方法、装置和系统
CN106603662B (zh) * 2016-12-14 2019-04-30 日照职业技术学院 物联网与互联网异网同构的综合智能平台的实现方法
CN107146607B (zh) * 2017-04-10 2021-06-18 北京猎户星空科技有限公司 智能设备交互信息的修正方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1996855A (zh) * 2006-12-22 2007-07-11 中国建设银行股份有限公司 一种保持数据一致性的方法及系统
CN106464745A (zh) * 2015-06-30 2017-02-22 华为技术有限公司 Dns的服务器、客户端及数据同步方法
WO2018009094A1 (fr) * 2016-07-05 2018-01-11 Общество С Ограниченной Ответственностью "Рм" Dispositif d'informations embarqué du matériel roulant des chemins de fer
CN106921734A (zh) * 2017-02-13 2017-07-04 上海大学 一种基于选择性缓存与同步的客户端与服务器数据交互方法

Also Published As

Publication number Publication date
CN108494859A (zh) 2018-09-04
CN108494859B (zh) 2020-07-14

Similar Documents

Publication Publication Date Title
CN108600353B (zh) 一种区块链节点的并行块同步方法
US20210256007A1 (en) Blockchain system and blockchain transaction data processing method based on ethereum
US7428657B2 (en) Method for rolling back from snapshot with log
CN104486319B (zh) 适用于高可用系统的配置文件实时同步方法及其系统
CN109688012A (zh) 一种联盟链节点热备切换的方法
US20070088763A1 (en) Methods and systems for validating accessibility and currency of replicated data
EP1950931A1 (fr) Dispositifs, système et procédé de distribution et de synchronisation de données de service
CN106407030A (zh) 一种存储集群系统故障处理方法及系统
CN106911648B (zh) 一种环境隔离方法及设备
CN107357681B (zh) 基于salt的Zookeeper备份管理系统及方法
US20080208958A1 (en) Risk assessment program for a directory service
CN110635941A (zh) 一种数据库节点集群故障迁移方法与装置
WO2017071384A1 (fr) Procédé et appareil de traitement de message
CN110545207B (zh) 一种同步自动化的智能dns系统及配置方法
CN113965578A (zh) 一种集群中主节点的选举方法、装置、设备及存储介质
WO2017016196A1 (fr) Méthode, appareil et système de synchronisation de données
WO2016101409A1 (fr) Procédé, dispositif et système de commutation de données
US20240054054A1 (en) Data Backup Method and System, and Related Device
CN110912979B (zh) 一种解决多服务器资源同步冲突方法
CN110716828B (zh) 一种数据库实时备份方法
WO2019184241A1 (fr) Procédé et système de synchronisation de données de réseau
WO2002001347A2 (fr) Procede et systeme permettant la reattribution automatique d'elements de logiciel d'un hote defaillant
CN110851527B (zh) 一种主备服务器的数据同步方法
CN113765690A (zh) 集群切换方法、系统、装置、终端、服务器及存储介质
CN109257218B (zh) 一种基于snmp协议网络系统孤岛自愈方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18912395

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18912395

Country of ref document: EP

Kind code of ref document: A1