A data synchronization management system, method, device, medium and product

Abstract

The embodiment of the application discloses a data synchronization management system, method, device, medium and product, the system comprises: at least two server groups; each of the server groups comprises a data synchronization process and at least one business server; each of the business servers is associated with the data synchronization process; for each server group, the business server is used for generating a data synchronization message containing to-be-synchronized business data when having a data cross-group synchronization demand, and sending the data synchronization message to the associated data synchronization process; the data synchronization process is used for determining a target server group to be cross-group synchronized according to the received data synchronization message, and transmitting the to-be-synchronized business data to a target business server of the target server group through a generated synchronization data packet. The flexibility and effectiveness of application business data synchronization under a large-scale Internet architecture are better ensured, and the generality of data synchronization under the large-scale Internet architecture is better embodied.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of data synchronization, and in particular to a data synchronization management system, method, device, medium and product. BACKGROUND

[0002] With the rapid development of the Internet era, computer storage capacity and complex algorithms are constantly developing, and the amount of data has increased exponentially in recent years. Users have increasingly high quality requirements for data synchronization, and need to ensure the accuracy, timeliness and security of data synchronization.

[0003] In the deployment of enterprise Internet, due to the increasing size of data, the Internet cross-regional deployment of multiple server groups is often considered. Under the cross-regional multi-server group Internet architecture, data synchronization failure often occurs between server groups due to unstable network or abnormal business system. In addition, the existing data synchronization method is often set for a certain business on the server group, and the execution of the method is limited by the business scenario, which lacks applicability. SUMMARY

[0004] Embodiments of the present application provide a data synchronization management system, method, device, medium and product, which are suitable for data synchronization management of different business applications and improve the universality of data synchronization management.

[0005] In a first aspect, the embodiments of the present application provide a data synchronization management system, comprising at least two server groups;

[0006] Each server group comprises at least one business server and a data synchronization process associated with each business server;

[0007] For each server group,

[0008] The business server is configured to generate a data synchronization message containing to-be-synchronized business data when a data cross-group synchronization requirement is met, and send the data synchronization message to the associated data synchronization process;

[0009] The data synchronization process is configured to determine a target server group to be cross-group synchronized according to the received data synchronization message, and transmit the to-be-synchronized business data to the target business server of the target server group through a generated synchronization data packet.

[0010] In a second aspect, the embodiments of the present application provide a data synchronization management method, which is executed by the business server and the data synchronization process in the server group included in the data synchronization management system provided in the first aspect of the embodiments of the present application. The method comprises:

[0011] For each server cluster, when the business servers within it have a need for cross-cluster data synchronization, they generate a data synchronization message containing the business data to be synchronized and send it to the associated data synchronization process.

[0012] The data synchronization process determines the target server group to be synchronized across groups based on the received data synchronization messages, and transmits the business data to be synchronized to the target business server in the target server group through the generated synchronization data packets.

[0013] Thirdly, embodiments of the present invention provide a data synchronization management device, serving as the execution device for the data synchronization process in the server cluster included in the data synchronization management system provided in the first aspect of the present invention, comprising:

[0014] One or more processors;

[0015] Storage device for storing one or more programs;

[0016] One or more programs are executed by one or more processors, such that the one or more processors are used to implement the data synchronization management method provided in the second aspect of the embodiments of the present invention.

[0017] Fourthly, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, characterized in that, when the program is executed by a processor, it implements the data synchronization management method provided in the second aspect of the present invention described above.

[0018] Fifthly, embodiments of the present invention provide a computer program product, characterized in that the computer program product includes a computer program, which, when executed by a processor, implements the data synchronization management method provided in the second aspect of the present invention.

[0019] The embodiment of the application discloses a data synchronization management system, method, device, medium and product. The system comprises: at least two server groups, each server group comprising at least one service server and a data synchronization process associated with each service server; for each server group, the service server is configured to generate a data synchronization message containing to-be-synchronized service data when having a data cross-group synchronization requirement, and send the data synchronization message to the associated data synchronization process; and the data synchronization process is configured to determine a target server group to be synchronized cross-group according to the received data synchronization message, and transmit the to-be-synchronized service data to the target service server of the target server group through a generated synchronization data packet. The technical solution described above can realize effective synchronization of service data from each service server integrated in a server group to other to-be-synchronized server groups through the data synchronization process in the server group when the service server has a data cross-group synchronization requirement. The technical solution, as a general data synchronization management system, can realize data synchronization without considering what kind of service application needs data synchronization on the service server, can directly realize forwarding of the data synchronization message through the associated data synchronization process, and can realize data synchronization of various service types. The technical solution can better guarantee flexibility and effectiveness of application service data synchronization under a large-scale Internet architecture, and better reflect generality of data synchronization under the large-scale Internet architecture.

[0020] It should be understood that the content described in this part is not intended to identify key or important features of the embodiments of the application, nor is it used to limit the scope of the application. Other features of the application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiments. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can be obtained by those skilled in the art without creative labor.

[0022] Figure 1 A structural block diagram of a data synchronization management system provided by the embodiment one of the application is given;

[0023] Figure 2 Another structural block diagram of a data synchronization management system provided by the embodiment one of the application is given;

[0024] Figure 3 A flowchart of a data synchronization management method provided by the embodiment two of the application is given;

[0025] Figure 4 Another flowchart of a data synchronization management method provided by the embodiment two of the application is given;

[0026] Figure 5 A hardware structure schematic diagram of a data synchronization management device provided by Embodiment Three of the present application is given. DETAILED DESCRIPTION

[0027] In order for those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work should fall within the scope of protection of the present application.

[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to the process, method, product or device.

[0029] Embodiment One

[0030] Figure 1 A structure block diagram of a data synchronization management system provided by Embodiment One of the present application is given, which is suitable for the case of data synchronization management of different business applications under a cross-regional Internet architecture, as shown in Figure 1 The data synchronization management system comprises at least two server groups 10.

[0031] Each server group 10 comprises a data synchronization process 102 and at least one business server 101; each business server 101 is associated with the data synchronization process 102;

[0032] For each server group 10,

[0033] The business server 101 is configured to generate a data synchronization message containing to-be-synchronized business data when having a data cross-group synchronization requirement, and send the data synchronization message to the associated data synchronization process 102;

[0034] The data synchronization process 102 is configured to determine a target server cluster to be synchronized according to the received data synchronization message, and transmit the to-be-synchronized service data to a target service server in the target server cluster through a generated synchronization data packet.

[0035] The data synchronization management system provided in the embodiment comprises at least two server clusters 10, each server cluster 10 comprising a data synchronization process 102 and at least one service server 101, and each service server 101 being associated with the data synchronization process 102. The server cluster, i.e., the server cluster, is a large-scale Internet framework that can support different types of service running by centralizing at least two servers. The server cluster can provide service across regions, realize multi-region synchronization of services, and effectively avoid the destruction of the running of clustered resources due to the failure of a server.

[0036] In the embodiment, the data synchronization management system is mainly used for receiving and processing different types of data synchronization tasks transmitted from different clients in each server cluster. Generally, the server cluster can be regarded as a distributed system architecture, and global service deployment can be realized. In the distributed system architecture, the distributed data synchronization management system in the embodiment can be constructed by deploying server clusters in different regions.

[0037] It should be noted that the application scenario of the data synchronization management system can be described as follows: in each server cluster 10, each service server 101 receives a service processing requirement transmitted from a different service client, queries or receives different cross-region data synchronization requirements of each service, and each data synchronization process 102 associated with the service server 101 receives the data synchronization message transmitted by each service server 101. According to the data synchronization message, the to-be-synchronized service data is directly forwarded to each target service server, and the cross-cluster synchronization service of each cross-cluster synchronization requirement is directly performed. Optionally, the server cluster 10 has at least two server clusters. For example, the server cluster 10 can be an Asian server cluster and a European server cluster. The service server 101 in the Asian server cluster receives the data cross-cluster synchronization requirement and transmits it to the target service server in the European server cluster. When there is one or more clients in Asia that respectively initiate data cross-cluster synchronization requirements such as voice call or text message instant communication services to several clients in Europe, the data cross-cluster synchronization requirements are received by different service servers 101 in the Asian server cluster and transmitted to several target service servers in the European server cluster according to the data synchronization process 102, thereby realizing the cross-cluster synchronization service of different service data.

[0038] For each server cluster 10,

[0039] The business server 101 is used to generate a data synchronization message containing the business data to be synchronized when there is a data cross-group synchronization requirement, and send it to the associated data synchronization process 102. At least one business server 101 in the server group 10 is used to operate the business. The business server 101 is set to respond to the business to be processed. Different business servers 101 can respond to different businesses and can provide corresponding execution processing for business matching.

[0040] For example, when a business participant has a certain requirement, the client can generate a business request of this type of requirement. After receiving the business request, the business server 101 can process the business matching the business request. For example, when the client generates a synchronization request of different business types such as instant messaging, video playing, or online meeting, different business servers 101 in the server group 10 can perform corresponding processing on the above different businesses respectively.

[0041] The data cross-group synchronization requirement is a cross-regional or cross-multi-regional data synchronization request generated in the business operation of the client. When the business server 101 responds to the client, the business itself has or the business server 101 queries that the client business has a cross-regional synchronization requirement (data cross-group synchronization requirement), and generates a data synchronization message containing the business data to be synchronized.

[0042] For example, the business server 101 can simultaneously perform business synchronization of different business types. For example, the first business server 101 can support the business synchronization of the instant messaging described above, the second business server 101 can perform the business synchronization of the video playing described above, and the third business server 101 can perform the business synchronization of the online meeting described above. Similarly, each business server 101 in the server group 10 in the present data synchronization management system can simultaneously provide synchronization services for different types of businesses. It should be noted that if the business synchronization has a cross-group synchronization requirement, the business server 101 can also simultaneously implement cross-group data synchronization of multiple business types.

[0043] The business data to be synchronized can be business Binlog (Binary Log) data, which is a binary log file used to record the data update of Mysql or the SQL statement of potential update. When data is written to the database, the updated SQL statement is also written to the corresponding Binlog file. Before using Binlog, it is necessary to confirm whether the Binlog is started.

[0044] The data synchronization message includes the business data to be synchronized. This data is encapsulated into a data synchronization message format and sent by the business server 101 to the data synchronization process 102. In this embodiment, the generation of the data synchronization message can be performed by the business server 101 after receiving a cross-group data synchronization request. Specifically, the business server can obtain the business data to be synchronized, determine the business type of the data, and identify which server group the data should be synchronized to, thereby obtaining the group address information of the desired server group. The business server can encapsulate the obtained data to be synchronized, business type, and group address information of the desired server group to be synchronized to, ultimately forming a data synchronization message.

[0045] In this embodiment, the data synchronization process 102 is used to determine the target server group to be synchronized across groups based on the received data synchronization message, and to transmit the business data to be synchronized to the target business server of the target server group through the generated synchronization data packet. In this embodiment, one data synchronization process 102 is created in one server group 10, that is, one data synchronization process 102 corresponds to one server group 10. The data synchronization process 102 can be created on any server included in the server group 10, and the data synchronization process can establish a communication connection with at least one business server 101 in the server group 10.

[0046] In this embodiment, the data synchronization process 102, which is located in the same server group 10 as the business server 101, can receive the data synchronization message and analyze it to determine the target server group for which the business server 101 needs to synchronize across groups. In this embodiment, the target server group is another server group 10 in the data synchronization management system, which may also contain at least one business server 101 and the data synchronization process 102 created on any server in the server group 10.

[0047] As described above, after determining the target server group, the data synchronization process 102 can generate a synchronization data packet based on the message content contained in the data synchronization message, and send the synchronization data packet to the data synchronization process 102 on the target server group. The target business server can be determined by the data synchronization process 102 in the target server group from among the multiple business servers included in the target server group based on the received synchronization data packet. The target business server can also be business server 101; the two have a relative target relationship, and business server 101 can also exist as a target business server.

[0048] Specifically, the data synchronization process 102 on the target server group can obtain the service type in the synchronization data packet, and then select a service server 101 matching the service type from the plurality of service servers 101 as a target service server; finally, the data synchronization process 102 on the target server group can synchronize the to-be-synchronized service data in the synchronization data packet to the target service server.

[0049] For example, after receiving a service request generated by a client, the service server 101 can determine that the service request has a cross-group data synchronization requirement if it is detected that the service request has cross-group synchronization data during the running of the service request. Then, the service type, target group identifier, to-be-synchronized service data, and synchronization configuration parameters of the service request can be obtained, and the obtained data can be encapsulated according to a set synchronization protocol message format to form a data synchronization message. Finally, the generated data synchronization message can be sent to the data synchronization process 102 created on the server group. After receiving the data synchronization message, the data synchronization process 102 can generate a synchronization data packet, and transmit the synchronization data packet from the data synchronization process 102 of the server group 10 to the target server group according to the target group identifier, so that the target service server group can transmit the to-be-synchronized service data in the synchronization data packet to the target service server determined from the target server group according to the data synchronization process 102 created on the target server group.

[0050] Each of the server groups has a server group configuration file.

[0051] The server group configuration file includes the group identifier and group address of each of the server groups, and the service type and server address of each of the service servers included in each of the server groups.

[0052] The group identifier and group address are identity documents (ID) and Internet Protocol (IP) addresses unique to each of the server groups 10. Similarly, each of the service server addresses is also unique. Each of the server groups 10 and service servers 101 has an identity document and an Internet Protocol address unique to itself. The group address and server address are Internet logical addresses, rather than physical addresses.

[0053] It should be noted that after each service server 101 receives the data synchronization request of different service types corresponding thereto, the service type of the service server, the target group identifier to be cross-group synchronized, the business data to be synchronized and the synchronization configuration parameters can be obtained, and the same is encapsulated according to the set synchronization protocol message format to form a data synchronization message, and the respective synchronization data packet is generated in the data synchronization process 102, and is sent to the corresponding different target server group according to the target group identifier to be cross-group synchronized corresponding to each service type, so as to realize the data cross-group synchronization of the universal multiple service types.

[0054] The data synchronization management system provided by the embodiment one comprises at least two server groups, each server group comprising at least one service server and a data synchronization process associated with each service server, for each service server in each server group, when having a data cross-group synchronization requirement, a data synchronization message containing business data to be synchronized is generated and sent to the associated data synchronization process, and the data synchronization process is used to determine the target server group to be cross-group synchronized according to the received data synchronization message, and the business data to be synchronized is transmitted to the target service server of the target server group through the generated synchronization data packet. Each service server integrated in the server group can effectively synchronize the business data to other server groups to be synchronized through the data synchronization process in the server group when having a data cross-group synchronization requirement. As a universal data synchronization management system, the technical solution does not need to consider what kind of business application needs data synchronization on the service server when realizing data synchronization, and no matter which service server has a cross-group synchronization requirement in the business running, the associated data synchronization process can be directly used to realize the forwarding of the data synchronization message, and the data synchronization of multiple business systems can be supported at the same time. The flexibility and effectiveness of the application business data synchronization under the large-scale Internet architecture are better guaranteed, and the universality of the data synchronization under the large-scale Internet architecture is better embodied.

[0055] As the first optional embodiment of the embodiment, on the basis of the above-mentioned embodiment, the first optional embodiment can be used to execute the following steps:

[0056] a1) When detecting that the service server running has cross-group synchronization data, it is determined that the data cross-group synchronization requirement is met.

[0057] In each server group 10, at least one service server 101 associated with a data synchronization process 102 is included, and the service server 101 receives a service request from different clients.

[0058] Optionally, the service request can be a data interaction between the service server 101 and the data synchronization process 102 in the same server group 10, i.e., the target server group can be the server group 10, and the target service server can be another service server 101 in the server group 10. The data synchronization can be implemented in the same server group 10.

[0059] Optionally, the service request can be a cross-server group service request, i.e., the service server 101 in the server group 10 detects that the data in the service request needs to be synchronized across server groups, and determines that the service request has a cross-group data synchronization requirement.

[0060] b1) obtaining the service type of the service request, the target group identifier to be synchronized across groups, and the data to be synchronized, and obtaining the synchronization configuration parameters relative to the service request.

[0061] The service type is the type of the service request that needs to be synchronized across groups, such as message transmission, video call, or access application. The target group identifier to be synchronized across groups is the identity of the target server group that needs to be synchronized across groups. Each server group 10 has an identity that is unique to the server group. The synchronization configuration parameters relative to the service request can be used to configure the synchronization data, such as the order, properties, or size of the synchronization data according to the preset configuration parameters.

[0062] Specifically, after determining the cross-group data synchronization requirement, the service server 101 starts to obtain the specific information of the service request, such as obtaining the service type, the target group identifier to be synchronized across groups, and the data to be synchronized, and obtaining the synchronization configuration parameters relative to the service request.

[0063] c1) encapsulating the service type, the target group identifier, the data to be synchronized, and the synchronization configuration parameters according to the set synchronization protocol message format to form the data synchronization message, and sending the data synchronization message to the associated data synchronization process.

[0064] The data synchronization message includes the service type, the target group identifier, the data to be synchronized, and the synchronization configuration parameters. The synchronization protocol message format for forming the data synchronization message can be a GRE encapsulation protocol, a TCP / UDP protocol, an IP protocol, or an LCP protocol data message, and the embodiment does not limit the synchronization protocol format for encapsulating the data message. The data synchronization message integrates the above data information and encapsulates the scattered information into one data synchronization message. The service server 101 sends the encapsulated data synchronization message to the associated data synchronization process 102.

[0065] The technical scheme provided by the application can encapsulate the business type of the business to be synchronized, the target group identifier to be cross-group synchronized, the business data to be synchronized, and the synchronization configuration parameter relative to the business into the form of a data synchronization message, directly identify and forward to the target server group and the target business server according to the message content when data synchronization is performed, and does not need to customize a data synchronization mechanism according to a specific business, thereby providing a logical execution basis for general data synchronization under a large-scale Internet architecture and ensuring the flexibility of application business data synchronization.

[0066] As a second optional embodiment of the present embodiment, on the basis of the above-mentioned embodiment, Figure 2 Another structure block diagram of the data synchronization management system provided by the present embodiment is given, and specifically, the second optional embodiment can optimize the data synchronization process 102, as shown in the figure, Figure 2 The data synchronization process 102 includes a first sub-process 1021, a second sub-process 1022, a third sub-process 1023, and a fourth sub-process 1024.

[0067] The first sub-process 1021 is used for analyzing the received data synchronization message to obtain the business type, the target group identifier, the business data to be synchronized, and the synchronization configuration parameter, wherein the synchronization configuration parameter includes a synchronization priority and a compression setting parameter.

[0068] In the data synchronization process 102, first, the data synchronization message from the business server 101 is parsed to obtain the parsed business type, target group identifier, to-be-synchronized business data, and synchronization configuration parameters. The data synchronization message is completed according to the standard synchronization protocol, the to-be-synchronized business data binlog log is read, and the configured binlog storage path is scanned. The synchronization protocol data is parsed and the related field information is extracted. If there is a new incomplete synchronization data file, the file content is parsed according to the synchronization protocol. The synchronization configuration parameters include synchronization priority and compression setting parameters. Based on the synchronization priority, in the to-be-synchronized business sorting in the business server 101, the higher the priority of the data synchronization business, the faster and more accurate the business data is synchronized to the target business server. The compression setting parameters can include whether to compress, compression format, compression method, or compression rate, etc. The to-be-synchronized business data can be compressed into the required target business data according to the compression setting parameters. The specific compression setting parameters are not limited in this embodiment.

[0069] Specifically, the data synchronization message is transmitted according to the standard synchronization protocol. After the data synchronization message is transmitted to the data synchronization process 102, the data synchronization message is parsed in the first sub-process 1021 to obtain the business type, target group identifier, to-be-synchronized business data, and synchronization configuration parameters encapsulated as the data synchronization message, which facilitates effective use of the above information in subsequent processes.

[0070] Optionally, after receiving and parsing the data synchronization message, the data synchronization process 102 persistently saves the data synchronization message, which can effectively prevent data synchronization failure caused by data loss. After data persistence, the data synchronization process 102 accepts the data synchronization message and feeds back to the associated business server 101 that sends the data synchronization message.

[0071] The second sub-process 1022 is configured to determine the target server group to be synchronized across groups based on the target group identifier, and determine the target group address of the target server group by searching the preset server group configuration file.

[0072] The preset server group configuration file is saved in each server group 10, and the server group configuration file includes the group identifier, group address of each server group 10, and the business type and server address of the business server 101 included in each server group 10.

[0073] The target group identifier of the target server group is unique and determined, and the target server group to be synchronized across groups is determined according to the unique target group identifier, and the target group address is determined by searching the server group configuration file according to the target group identifier.

[0074] Specifically, the parsed data synchronization message includes the target group identifier. Based on the target group identifier, the target server group of the service can be accurately determined. Each server group 10 includes its own server group configuration file. Based on the target group identifier, the target group address is found using the server group configuration file, providing a logical location basis for subsequent child processes.

[0075] The third subprocess 1023 is used to determine the synchronization conditions that currently meet the business service based on the synchronization priority, and then form a synchronization data packet according to the business type, compression setting parameters and the business data to be synchronized.

[0076] Based on the synchronization priority, it is determined whether the data to be synchronized for the current service is the first priority synchronization service data. If the current service to be synchronized is not the first priority, the first priority services to be synchronized are packaged into data packets. If the current service to be synchronized is the first priority, the service type, compression settings, and the data to be synchronized are combined to form a synchronization data packet.

[0077] The fourth subprocess 1024 is used to send the synchronization data packet to the target server group according to the target group address.

[0078] Based on the target group address obtained from the server group configuration file, the synchronization data packet is sent from server group 10 to the target server group using a uniquely determined IP address.

[0079] Based on the above embodiments, this second optional embodiment can optimize the third subprocess 1023 to perform the following steps:

[0080] a2) Add the business services to the synchronization cache table according to the synchronization priority.

[0081] The synchronization cache table can store multiple services to be synchronized simultaneously, providing static table caching. The synchronization cache table contains multiple services to be synchronized, and these services are sorted in descending order of priority. The service with the highest priority is ranked first in the synchronization cache table. When data of a service to be synchronized is accessed, the service with the highest priority is accessed first in the synchronization process.

[0082] b2) When the business service is detected to be retrieved from the synchronization cache table, determine that the synchronization conditions of the business service are met.

[0083] The synchronization condition refers to determining that the service to be synchronized from the synchronization cache table has cross-group synchronization requirements and is ranked first in priority in the synchronization cache table. If the synchronization condition of the service can be met, the next synchronization process can be performed.

[0084] c2) If the compression setting parameter is set to compress data, the to-be-synchronized service data is compressed to obtain target service data, otherwise, the to-be-synchronized data is taken as target service data.

[0085] It is determined whether the to-be-synchronized service data is compressed in the compression setting parameter. If data compression is required, the to-be-synchronized service data is compressed according to other compression parameters in the preset compression setting parameter to obtain target service data.

[0086] Specifically, if the compression setting parameter is set to compress data, the to-be-synchronized service data can continue to be compressed according to other compression parameters in the compression setting parameter, such as compression format, compression method or compression rate, etc. The to-be-synchronized service data is compressed according to the compression setting parameter, and target service data is obtained according to the compression result. If the compression setting parameter is set not to compress the to-be-synchronized service data, the to-be-synchronized service data itself is the target service data.

[0087] d2) The service type and the target service data are encapsulated according to the set format to form a synchronization data packet.

[0088] The set encapsulation format is the same as the encapsulation format in the c1 step in the above embodiment, and will not be described in detail in this embodiment. The generation of the synchronization data packet can be performed by the data synchronization process 102 after determining that the synchronization condition is met. Specifically, the first sub-process 1021 obtains a data synchronization message and performs analysis to obtain the service type, target group identifier, to-be-synchronized service data and synchronization configuration parameter contained therein, determines that the synchronization condition is met, that is, the to-be-synchronized service priority is first, and encapsulates the service type and the target service data obtained by analyzing the data synchronization message into a synchronization data packet according to the set format.

[0089] The target service data can be compressed to-be-synchronized service data or to-be-synchronized service data itself. The target service data and the service type are encapsulated according to the set format to form a synchronization data packet.

[0090] The data synchronization process provided by the optional embodiment of the application comprises a first sub-process for parsing a received data synchronization message to obtain a service type, a target group identifier, to-be-synchronized service data, and synchronization configuration parameters; a second sub-process for determining a target server group to be synchronized across groups based on the target group identifier, and determining a target group address of the target server group by searching a preset server group configuration file; a third sub-process for determining a synchronization condition that is currently met by the service after determining the synchronization priority, and forming a synchronization data packet according to the service type, the compression setting parameter, and the to-be-synchronized service data; and a fourth sub-process for sending the synchronization data packet to the target server group according to the target group address. The technical solution of the application determines correct to-be-synchronized service data and generates a synchronization data packet, and sends the synchronization data packet according to the target server group identifier and address corresponding to the service. The synchronization data packet is different from the prior art, and can be directly forwarded to the target server group through the target group identifier and address, thereby effectively confirming the accuracy of the target service data and the efficiency of data transmission across groups.

[0091] As a third optional embodiment of the first embodiment, on the basis of the above embodiment, as shown in Figure 2 The data synchronization process 102 further comprises a fifth sub-process 1025 and a sixth sub-process 1026.

[0092] The fifth sub-process 1025 is configured to persistently save the to-be-synchronized service data obtained from the data synchronization message 102, and feed back a message response result to the service server 101.

[0093] Persistently saving the to-be-synchronized service data obtained from the data synchronization message can effectively prevent data loss during synchronization, that is, the data is saved to a storage device (such as a disk) that can be permanently saved. The main application of persistence is to store objects in the memory in a database, or in a disk file, an XML data file, and the like. Persistence is a mechanism for converting program data between a persistent state and a transient state. After the to-be-synchronized service data is synchronized to the target service server, the persistently saved to-be-synchronized service data can be deleted.

[0094] Specifically, in the data synchronization process 102, the first sub-process 1021 parses the data synchronization message and obtains to-be-synchronized service data in the synchronization data packet. To prevent the situation that the service server 101 fails or the server group 10 fails during the data synchronization process, resulting in data loss and failure to complete the data synchronization service, the to-be-synchronized service data is persistently saved, and the response result of the data synchronization message in the data synchronization process 102 is fed back to the service server 101, thereby completing a small cycle of data synchronization.

[0095] The sixth sub-process 1026 is used for deleting the to-be-synchronized service data which is persistently stored after the synchronization data packet is sent to the target server group, and feeding back the data synchronization result to the service server 101 after receiving the synchronization completion message which is fed back by the target server group.

[0096] Specifically, the to-be-synchronized service data is deleted after the synchronization data packet is sent to the target server group, and the process occurs in the server group 10 at the sending end of the synchronization data packet. The fifth sub-process 1025 of the data synchronization process 102 persistently stores the to-be-synchronized service data, and in the sixth sub-process 1026, the to-be-synchronized service data has been successfully sent to the target server group, so that the data will not be lost in the data synchronization sub-process, and the data can be deleted from the original server group 10. Meanwhile, after receiving the completed data synchronization message which is fed back by the target server group, the data synchronization result is fed back to the original service server 101, the message circulation in the cluster is completed, and it is determined that the synchronization has been completed.

[0097] The data synchronization process provided by the optional embodiment of the application comprises a fifth sub-process which is used for persistently storing the to-be-synchronized service data obtained from the data synchronization message and feeding back the message response result to the service server, and a sixth sub-process which is used for deleting the to-be-synchronized service data which is persistently stored after the synchronization data packet is sent to the target server group, and feeding back the data synchronization result to the service server after receiving the synchronization completion message which is fed back by the target server group. When the data synchronization process is promoted, the to-be-synchronized service data information is stored, the data loss in the incomplete synchronization is effectively prevented, the to-be-synchronized service data is cleaned up and the synchronization completion message is fed back after the data synchronization is completed in stages, the memory occupied by the useless messages is reduced, and the channel is provided for the data synchronization of other services without interference. The safety of the data synchronization is effectively improved, and the high efficiency of the data synchronization management system is embodied.

[0098] As the fourth optional embodiment of the first embodiment, on the basis of the above-mentioned embodiments, as shown in Figure 2 The data synchronization process 102 further comprises a seventh sub-process 1027.

[0099] The seventh sub-process 1027 is used for receiving the synchronization data packet which is sent by the other server group 10, determining the target service server according to the synchronization data packet, and synchronizing the target service data in the synchronization data packet to the target server.

[0100] The synchronization data packet comprises a service type and target service data, and the target service server which is matched with the service type is determined.

[0101] On the basis of the above optimization, the seventh sub-process 1027 can be specifically used to execute the following steps:

[0102] a3) receiving and parsing the synchronization data packet sent by any other server group 10 to obtain the service type and target service data.

[0103] When the server group 10 is a target server group, the synchronization data packet sent by any other server group is received. After persistently saving the synchronization data packet and feeding back the data synchronization result to the server group 10 sending the synchronization data packet, the synchronization data packet is parsed to obtain the service type and target service data.

[0104] b3) searching the preset server group configuration file to determine the target service server corresponding to the service type as the target service server, and obtaining the target server address of the target service server.

[0105] Each server group 10 is configured with a preset server group configuration file, and the server group configuration file includes the group identifier, group address of each server group 10, and the service type and server address of the service server 101 included in each server group 10. According to the association between the service type and the server address in the server group configuration file, the target service server matching the service type is searched, and the target service server address is obtained.

[0106] c3) sending the target service data to the target service server according to the target server address, so that the target service data is synchronized to the target service server.

[0107] The target service server address is unique, and the target service data is sent to the target service server according to the target service server address matching the service type, so as to complete the cross-group data synchronization. After the target service server receives the target service data, it feeds back the data synchronization result to the server group 10 where it is located. After the server group 10 receives the feedback result, it sends the feedback result to the server group 10 initiating the data synchronization service. After the server group 10 initiating the data synchronization service receives the data synchronization result feedback, it sends the feedback result to the service server 101 corresponding to the service.

[0108] The data synchronization process provided by the optional embodiment of the application includes a seventh sub-process for receiving a synchronization data packet sent by another server group, determining a target service server according to the synchronization data packet, and synchronizing target service data in the synchronization data packet to the target server. According to the technical solution, the target service server is accurately queried according to the service type, and the cross-group data synchronization is completed. The data synchronization mechanism does not need to be customized according to the service type, and the universality, flexibility and efficiency of data synchronization are realized.

[0109] In addition, the seventh sub-process can be used to execute the following steps:

[0110] The target service data in the received synchronization data packet is persistently stored to prevent the target service data from being lost and unable to be retrieved in the synchronization process or after being unsynchronized to the target service server. The security of the data synchronization system is improved.

[0111] When the synchronization completion message is received from the target service server in response to the target service data, the persistently stored target service data is deleted, and a synchronization completion message is fed back to the server group that sent the synchronization data packet. The occupation of the memory in the data synchronization system is effectively reduced, sufficient synchronization space is provided for subsequent service synchronization, and the synchronization efficiency of the data synchronization system is improved.

[0112] Embodiment Two

[0113] Figure 3 A flowchart of a data synchronization management method provided by Embodiment Two of the application is given. The method is applicable to the data synchronization management of different service applications under a cross-regional Internet architecture. The method can be executed by the service servers and data synchronization processes in the server group of the data synchronization management system provided by Embodiment One of the application.

[0114] As shown in Figure 3 The data synchronization management method provided by Embodiment Two of the application can include the following steps:

[0115] Step 301: For each server group, when the contained service servers have a data cross-group synchronization requirement, a data synchronization message containing to-be-synchronized service data is generated and sent to an associated data synchronization process.

[0116] The server group, i.e., the server cluster, is a large-scale Internet framework that can support different types of service running by centralizing at least two servers. It can provide cross-regional service, realize multi-regional synchronization of services, and effectively avoid the destruction of clustered resources due to server failure.

[0117] The service server is used to generate a data synchronization message containing to-be-synchronized service data and send it to an associated data synchronization process when a data cross-group synchronization requirement is met. At least one service server in the server group is a server used to run services. The service server is set to respond to to-be-processed services. Different service servers can respond to different services and can provide corresponding execution processing for service matching.

[0118] For example, when a business participant has a certain requirement, the client can generate a business request of this type of requirement, and the business server can process the business matching the business request after receiving the business request. For example, when the client generates a request for different business types such as instant messaging, video playing, or online meeting, different business servers in the server group provide corresponding processing for each different business.

[0119] The data cross-group synchronization requirement is a cross-regional or cross-multi-regional data synchronization request generated in the client business operation. When the business server responds to the client, the business itself has or the business server queries that the client business has a cross-regional synchronization requirement (data cross-group synchronization requirement), and generates a data synchronization message containing the to-be-synchronized business data. The to-be-synchronized business data can be business Binlog data, which is a binary log file used to record data updates to Mysql or potential update SQL statements. When data is written to the database, the updated SQL statement is also written to the corresponding Binlog file. Before using Binlog, it is necessary to confirm whether Binlog is enabled.

[0120] The data synchronization message includes to-be-synchronized business data, which is encapsulated into the format of the data synchronization message and sent to the data synchronization process by the business server. In this embodiment, the business server can perform the operation of generating the data synchronization message after receiving the data cross-group synchronization requirement. Specifically, the business server can obtain the to-be-synchronized business data, and can also determine the business type of the to-be-synchronized business data, and can determine which server group the to-be-synchronized business data is synchronized to, thereby obtaining the group address information of the server group expected to be synchronized to. The business server can encapsulate the to-be-synchronized data, the business type, and the group address information of the server group expected to be synchronized to, and finally form a data synchronization message. The data synchronization message is sent to the data synchronization process.

[0121] Step 302, the data synchronization process determines the target server group to be cross-group synchronized according to the received data synchronization message, and transmits the to-be-synchronized business data to the target business server of the target server group through the generated synchronization data packet.

[0122] In this embodiment, one data synchronization process is created in one server group, that is, one server group corresponds to one data synchronization process. The data synchronization process can be created on any server in the server group, and the data synchronization process can establish a communication connection with at least one business server in the server group.

[0123] In the embodiment, the data synchronization process in the same server group as the service server can receive the data synchronization message, and can analyze the data synchronization message to determine the target server group to be synchronized by the service server. In the embodiment, the target server group is another server group in the data synchronization management system, and the target server group can also include at least one service server and a data synchronization process created on any server in the server group.

[0124] According to the above description, after determining the target server group, the data synchronization process can generate a synchronization data packet according to the message content in the data synchronization message, and send the synchronization data packet to the data synchronization process in the target server group. The target service server can be determined by the data synchronization process in the target server group according to the received synchronization data packet.

[0125] Specifically, the data synchronization process in the target server group can obtain the service type in the synchronization data packet, and then select a service server matching the service type from the plurality of service servers as the target service server. Finally, the data synchronization process in the target server group can synchronize the service data to be synchronized in the synchronization data packet to the target service server.

[0126] The embodiment of the present application discloses a data synchronization management method. For each server group, when the service server included in the server group has a data cross-group synchronization requirement, a data synchronization message including service data to be synchronized is generated and sent to an associated data synchronization process. The data synchronization process determines a target server group to be synchronized cross-group according to the received data synchronization message, and transmits the service data to be synchronized to a target service server in the target server group through a generated synchronization data packet. The above technical solution can effectively synchronize the service data from each service server in the server group to other server groups to be synchronized through the data synchronization process in the server group when the service server has a data cross-group synchronization requirement. The technical solution does not need to consider which service application needs data synchronization when implementing data synchronization. As long as there is a data synchronization requirement, the data synchronization message can be directly forwarded through the associated data synchronization process. This better guarantees the flexibility and effectiveness of application service data synchronization in large-scale Internet architecture, and better reflects the generality of data synchronization in large-scale Internet architecture.

[0127] In order to better understand the data synchronization management system provided by the above embodiment, the following describes a specific implementation of the data synchronization management method through an application example. Figure 4 An example flowchart of the data synchronization management method provided by the embodiment of the present application is given.

[0128] As Figure 4 shown, taking data synchronization between two server groups under a data synchronization management system as an example, each server group includes a data synchronization process and at least one business server, one of the server groups is taken as a source server group with cross-group synchronized data, and the other server group is taken as a target server group to synchronize business data on the source server group.

[0129] Specifically, the implementation of the data synchronization management method includes the following steps:

[0130] S1, encapsulate the business type, target group identifier, to-be-synchronized business data, and synchronization configuration parameter into a data synchronization message.

[0131] The data synchronization system includes at least two server groups, each server group includes at least one business server and a data synchronization process associated with each business server, for each business server in each server group, when cross-group synchronized data exists in the running of the business service, determine that the data cross-group synchronization requirement exists, obtain the business type of the business service, the target group identifier to be cross-group synchronized, and the to-be-synchronized business data, and obtain the synchronization configuration parameter relative to the business service, encapsulate the business type, target group identifier, to-be-synchronized business data, and synchronization configuration parameter according to the set synchronization protocol message format, and form the data synchronization message. The synchronization configuration parameter includes synchronization priority and compression setting parameter.

[0132] S2, send the data synchronization message.

[0133] The business server sends the encapsulated data synchronization message to the associated data synchronization process.

[0134] S3, compress and persistently save the data synchronization message.

[0135] In the data synchronization process, the data synchronization message is compressed according to the compression setting parameter, and the data synchronization message is persistently saved in the data synchronization process.

[0136] S4, feed back the message response result to the business server.

[0137] After the data synchronization process receives and persistently saves the data synchronization message, the message response result is fed back to the business server that sends the data synchronization message.

[0138] S5, parse the data synchronization message to obtain the contained business type, target group identifier, to-be-synchronized business data, and synchronization configuration parameter.

[0139] S6, determining a target server group to be synchronized across groups based on the target group identifier.

[0140] The target server group to be synchronized across groups is determined based on the target group identifier, and a target group address of the target server group is determined by searching a preset server group configuration file. The server group configuration file includes group identifiers, group addresses of each server group, and service types and server addresses of service servers included in each server group.

[0141] S7, forming a synchronization data packet according to the service type, compression setting parameters, and the to-be-synchronized service data, and sending the synchronization data packet to the target service server group.

[0142] When it is detected that the service service is to be called from the synchronization cache table, a synchronization data packet is formed according to the service type, compression setting parameters, and the to-be-synchronized service data based on the synchronization priority after it is determined that the synchronization condition of the service service is met. If the compression setting parameters are data compression, the to-be-synchronized service data is compressed to obtain target service data, otherwise, the to-be-synchronized service data is taken as the target service data. The service service is added to the synchronization cache table according to the synchronization priority. The service type and the target service data are encapsulated according to a set format to form a synchronization data packet. The synchronization data packet is sent to the target server group according to the target group address.

[0143] Optionally, the to-be-synchronized service data obtained from the data synchronization message is persistently saved, and a message response result is fed back to the service server. After the synchronization data packet is sent to the target server group, the persistently saved to-be-synchronized service data is deleted, and when a synchronization completion message fed back by the target server group is received, a data synchronization result is fed back to the service server.

[0144] S8, persistently saving the synchronization data packet.

[0145] When the server group exists as a target server group, a synchronization data packet sent by another server group is received, and the synchronization data packet is persistently saved.

[0146] S9, feeding back a synchronization completion message to the server group sending the synchronization data packet.

[0147] S10, analyzing the synchronization data packet and obtaining the service type and the target service data.

[0148] The synchronization data packet received when the server group exists as a target server group is analyzed to obtain the service type and the target service data.

[0149] S11, determining a target service server and obtaining a target server address.

[0150] searching a preset server group configuration file, determining a service server corresponding to the service type as a target service server, and obtaining a target server address of the target service server;

[0151] S12, sending the target service data to the target service server.

[0152] According to the target server address, the target service data is sent to the target service server, so that the target service data is synchronized to the target service server.

[0153] S13, feeding back a data synchronization completion message.

[0154] When the synchronization completion message fed back by the target service server relative to the target service data is received, the target service data persistently saved is deleted, and a synchronization completion message is fed back to the server group sending the synchronization data packet.

[0155] The data synchronization management method provided by the second embodiment of the application encapsulates the service type, the target group identifier, the to-be-synchronized service data, and the synchronization configuration parameter into a data synchronization message and sends the data synchronization message to a data synchronization process, compresses and persistently saves the data synchronization message in the data synchronization process, feeds back a message response result of the data synchronization message to a service server, parses the data synchronization message to obtain the service type, the target group identifier, the to-be-synchronized service data, and the synchronization configuration parameter, determines a target server group to be synchronized across groups based on the target group identifier, forms a synchronization data packet according to the service type, the compression setting parameter, and the to-be-synchronized service data, and sends the synchronization data packet to the target service server group, persistently saves the synchronization data packet in the target server group, feeds back a synchronization completion message to the server group sending the synchronization data packet, parses the synchronization data packet to obtain the service type and the target service data, determines a target service server and obtains a target server address, sends the target service data to the target service server, and finally feeds back a data synchronization completion message to the service server sending the data synchronization message. In the technical solution, each service server integrated in the server group can effectively synchronize the service data to other to-be-synchronized server groups through the data synchronization process in the server group when the data cross-group synchronization is needed. The technical solution does not need to consider what kind of service application needs data synchronization on the service server when the data synchronization is implemented. As long as there is a data synchronization demand, the data synchronization message can be directly forwarded through the general data synchronization process. The technical solution better guarantees the flexibility and effectiveness of the application service data synchronization under a large-scale Internet architecture, and better reflects the generality of the data synchronization under the large-scale Internet architecture.

[0156] Embodiment three

[0157] Figure 5 A hardware structure schematic diagram of a data synchronization management device provided in Embodiment Three of the present application is given. The data synchronization management device is provided in the present application.

[0158] As shown in Figure 5 The data synchronization management device 50 includes at least one processor 51, and a memory, such as a read-only memory (ROM) 52, a random access memory (RAM) 53, etc., which is in communication connection with the at least one processor 51, wherein the memory stores a computer program which can be executed by the at least one processor, and the processor 51 can execute various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 52 or the computer program loaded from the storage unit 58 into the random access memory (RAM) 53. In the RAM 53, various programs and data required for the operation of the data synchronization management device 50 can also be stored. The processor 51, the ROM 52, and the RAM 53 are connected to each other through a bus 54. An input / output (I / O) interface 55 is also connected to the bus 54.

[0159] A plurality of components in the data synchronization management device 50 are connected to the I / O interface 55, including: an input unit 56, such as a keyboard, a mouse, etc.; an output unit 57, such as various types of displays, speakers, etc.; a storage unit 58, such as a magnetic disk, an optical disk, etc.; and a communication unit 59, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 59 allows the data synchronization management device 50 to exchange information / data with other devices through a computer network, such as the Internet, and / or various telecommunication networks.

[0160] The present application also provides a computer readable storage medium, which stores a computer program, and the program is executed by a processor to implement the data synchronization management method provided in the present application.

[0161] The present application also provides a computer program product, which includes a computer program, and the computer program is executed by a processor to implement the data synchronization management method provided in the present application.

[0162] It should be understood that the steps shown above can be reordered, added, or deleted, using various forms of flow. For example, the steps described in the present application can be executed in parallel, in sequence, or in different orders, as long as the desired results of the technical solutions of the present application can be achieved, and the present application does not limit this.

[0163] The above detailed description does not limit the scope of the application. Various modifications, combinations, sub-combinations and alternatives can be made to the detailed embodiment disclosed herein without departing from the spirit and the principles of the application. Any modification, equivalent replacement or improvement made within the spirit and principles of the application shall fall within the scope of the application.

Claims

1. A data synchronization management system, characterized in that, Includes at least two server clusters; Each of the server groups includes a data synchronization process and at least one business server; each of the business servers is associated with the data synchronization process; For each server cluster, The business server is used to generate a data synchronization message containing the business data to be synchronized when there is a need for cross-group data synchronization, and send it to the associated data synchronization process. The data synchronization process is used to determine the target server group to be synchronized across groups based on the received data synchronization message, and to transmit the business data to be synchronized to the target business server of the target server group through the generated synchronization data packet. The data synchronization process includes: The first subprocess is used to parse the received data synchronization message to obtain the service type, target group identifier, service data to be synchronized, and synchronization configuration parameters, including synchronization priority and compression setting parameters. The second subprocess is used to determine the target server group to be synchronized across groups based on the target group identifier, and to determine the target group address of the target server group by searching the preset server group configuration file. The third subprocess is used to determine the synchronization conditions that currently meet the business service based on the synchronization priority, and then form a synchronization data packet according to the business type, compression setting parameters and the business data to be synchronized. The fourth subprocess is used to send the synchronization data packet to the target server group according to the target group address; Specifically, the third subprocess is used for: Add the business services to the synchronization cache table according to the synchronization priority; When the business service is detected to be retrieved from the synchronization cache table, it is determined that the synchronization conditions of the business service are met. If the compression setting parameter is set to perform data compression, the data to be synchronized is compressed to obtain the target data; otherwise, the data to be synchronized is used as the target data. The business type and the target business data are encapsulated according to the set format to form a synchronization data packet.

2. The system according to claim 1, characterized in that, The service server is specifically used for: When cross-group synchronization of data is detected during the operation of a business service, it is determined that there is a need for cross-group data synchronization. Obtain the service type, target group identifier to be synchronized across groups, and service data to be synchronized for the service, and obtain the synchronization configuration parameters relative to the service. The data synchronization message is formed by encapsulating the service type, target group identifier, service data to be synchronized, and synchronization configuration parameters according to the set synchronization protocol message format, and then sending it to the associated data synchronization process.

3. The system according to claim 1, characterized in that, The data synchronization process also includes: The fifth subprocess is used to persistently store the business data to be synchronized obtained from the data synchronization message and to send the message response result back to the business server; The sixth subprocess is used to delete the persistently stored business data to be synchronized after sending the synchronization data packet to the target server group, and to send the data synchronization result back to the business server after receiving the synchronization completion message from the target server group.

4. The system according to claim 1, characterized in that, When the server group where the data synchronization process resides is the target server group, the data synchronization process further includes: The seventh subprocess is used to receive synchronization data packets sent by other server groups, determine the target business server based on the synchronization data packets, and synchronize the target business data in the synchronization data packets to the target server.

5. The system according to claim 4, characterized in that, The seventh subprocess is specifically used for: Receive and parse synchronization data packets sent by any other server group to obtain the service type and target service data; Locate the preset server group configuration file, determine the business server corresponding to the business type as the target business server, and obtain the target server address of the target business server; The target service data is sent to the target service server according to the target server address, so that the target service data is synchronized to the target service server.

6. The system according to claim 4, characterized in that, The seventh subprocess is also used for: The target service data in the received synchronization data packets is persistently saved; When a synchronization completion message is received from the target service server relative to the target service data, the persistently stored target service data is deleted, and a synchronization completion message is sent back to the server group that sent the synchronization data packet.

7. The system according to any one of claims 1-6, characterized in that, Each of the aforementioned server clusters stores a server cluster configuration file; The server cluster configuration file includes: the cluster identifier and cluster address of each server cluster, as well as the service type and server address of the service servers contained in each server cluster.

8. A data synchronization management method, characterized in that, The method, executed by the business servers and data synchronization processes in the server cluster included in the data synchronization management system according to any one of claims 1-7, comprises: For each server cluster, when the business servers within it have a need for cross-cluster data synchronization, they generate a data synchronization message containing the business data to be synchronized and send it to the associated data synchronization process. The data synchronization process determines the target server group to be synchronized across groups based on the received data synchronization message, and transmits the business data to be synchronized to the target business server of the target server group through the generated synchronization data packet. The data synchronization process determines the target server group to be synchronized across groups based on the received data synchronization message, and transmits the business data to be synchronized to the target business server in the target server group through the generated synchronization data packet, including: The first subprocess parses the received data synchronization message to obtain the service type, target group identifier, service data to be synchronized, and synchronization configuration parameters, including synchronization priority and compression setting parameters. The second subprocess determines the target server group to be synchronized across groups based on the target group identifier, and determines the target group address of the target server group by searching the preset server group configuration file. After determining the synchronization conditions that currently satisfy the business service based on the synchronization priority through the third subprocess, a synchronization data packet is formed according to the business type, compression setting parameters and the business data to be synchronized. The fourth subprocess sends the synchronization data packet to the target server group according to the target group address. Specifically, after determining the synchronization conditions that currently satisfy the service based on the synchronization priority through a third subprocess, a synchronization data packet is formed according to the service type, compression setting parameters, and the service data to be synchronized, including: Add the business services to the synchronization cache table according to the synchronization priority; When the business service is detected to be retrieved from the synchronization cache table, it is determined that the synchronization conditions of the business service are met. If the compression setting parameter is set to perform data compression, the data to be synchronized is compressed to obtain the target data; otherwise, the data to be synchronized is used as the target data. The business type and the target business data are encapsulated according to the set format to form a synchronization data packet.

9. An electronic device, characterized in that, As a business server and / or execution device that creates a data synchronization process in the data synchronization management system according to any one of claims 1-7, it includes: One or more processors; Storage device for storing one or more programs; The one or more programs are executed by the one or more processors, such that the one or more processors are used to perform the data synchronization management method of claim 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the data synchronization management method as described in claim 8.

11. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the data synchronization management method according to claim 8.

Images