Method, device and server for synchronizing business data based on remote multi-active

Abstract

This specification provides a business data synchronization method, device and server based on multi-site active-active, which is applied to the field of big data technology. Based on this method, the deployment of the first master cache service node and the first slave cache service node can be completed in advance according to the preset construction rules and preset processing rules. When a target business data synchronization request is received, the synchronization type of the business data is determined; according to the synchronization type of the business data, different situations are distinguished, and the required identification information is extracted from the target business data synchronization request; according to the identification information, the target business data to be synchronized is determined by querying and utilizing the cached business data group of the current time period in the replication backlog buffer; and then the synchronization of the target business data is completed by using the corresponding output buffer. Therefore, it can be better applied to big data synchronization scenarios involving more complex multi-site active-active synchronization, and can automatically distinguish different situations, and realize the synchronization of related business data efficiently and accurately.

Description

Technical Field

[0001] This specification belongs to the field of big data technology, and in particular relates to a business data synchronization method, device, and server based on multi-site active-active. Background Art

[0002] In the financial business field, in order to efficiently process massive transaction business data and better serve users, most trading platforms will deploy corresponding data centers in multiple different regions; then, through data centers in different regions, they will provide corresponding services for the massive transaction business data accessed by the trading platform at the same time, and complete the consistent synchronization of related transaction business data.

[0003] However, existing methods often require additional synchronization components between data centers in different regions to synchronize transaction data. This increases deployment costs and compromises the efficiency and reliability of inter-data center synchronization.

[0004] To address the above issues, no effective solutions have been proposed so far. Summary of the Invention

[0005] This specification provides a business data synchronization method, device and server based on remote multi-active, which can be well applied to big data synchronization scenarios involving more complex remote multi-active synchronization. It can automatically distinguish different situations and efficiently and accurately synchronize related business data. At the same time, since there is no need to introduce additional synchronization components, it can also effectively reduce deployment costs and improve the reliability of business data synchronization.

[0006] This specification provides a business data synchronization method based on remote multi-active, which is applied to a first server node, the first server node being deployed in a data center in a first region and connected to a first primary cache service node and a first secondary cache service node; wherein the first primary cache service node includes at least a replication backlog buffer constructed based on a preset construction rule, a secondary node output buffer corresponding to the first secondary cache service node, and a multi-active input buffer and a multi-active output buffer corresponding to data centers in other regions. The method includes:

[0007] Receive and respond to target business data synchronization requests and determine the synchronization type of the business data;

[0008] According to a preset synchronization rule, when it is determined that the synchronization type of the business data is remote multi-active synchronization, at least the node identifier of the first primary cache service node of the synchronization target end, the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, and the node identifier of the second primary cache service node of the synchronization initiator end are extracted from the target business data synchronization request; wherein the second primary cache service node is deployed in a data center in the second region, and the data center in the second region also has a corresponding second secondary cache service node deployed;

[0009] Check whether the node identifier of the first primary cache service node of the synchronization target end matches;

[0010] If it is determined that the node identifier of the first primary cache service node of the synchronization target end matches, detecting whether there is a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer; wherein the replication backlog buffer stores a cache business data group of the current time period obtained by processing based on a preset processing rule;

[0011] If it is determined that the business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer, target business data to be synchronized to the data center of the second region is determined from the cached business data group of the current time period based on the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end;

[0012] The target business data is synchronized to the second primary cache service node of the data center of the second region through the multi-active output buffer corresponding to the data center of the second region.

[0013] In one embodiment, after detecting whether the node identifier of the first primary cache service node of the synchronization target end matches, the method further includes:

[0014] If it is determined that the node identifier of the first primary cache service node of the synchronization target end fails to match, a first type full synchronization process is initiated to traverse the first business database, query and obtain business data whose business processing identifier is greater than the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end as the target business data;

[0015] Writing the target business data into a target relational database file;

[0016] The target relational database file is synchronized to the second primary cache service node of the data center of the second region through the multi-active output buffer corresponding to the data center of the second region.

[0017] In one embodiment, when it is determined that the synchronization type of the service data is remote multi-active synchronization, the method further includes:

[0018] Detecting whether the target service data synchronization request carries a service processing identifier of existing service data associated with the second primary cache service node of the synchronization initiator;

[0019] In the case where it is determined that the target business data synchronization request carries the business processing identifier of the existing business data associated with the second primary cache service node of the synchronization initiator, extracting the business processing identifier of the existing business data associated with the second primary cache service node of the synchronization initiator from the target business data synchronization request;

[0020] Detecting whether there is a business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator in the replication backlog buffer;

[0021] When it is determined that there is no business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator in the replication backlog buffer, a second type of full synchronization process is started, the first business database is traversed, and business data whose business processing identifier is greater than the business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator is queried and obtained as the target business data.

[0022] In one embodiment, after determining the synchronization type of the service data, the method further includes:

[0023] According to the preset synchronization rules, when it is determined that the synchronization type of the business data is local slave node synchronization, the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end are extracted from the target business data synchronization request;

[0024] Check whether the node identifier of the first primary cache service node of the synchronization target end matches;

[0025] If it is determined that the node identifier of the first primary cache service node of the synchronization target end matches, detecting whether there is a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer;

[0026] When it is determined that the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer, the target business data to be synchronized to the first secondary cache service node is determined from the cached business data group of the current time period according to the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end;

[0027] The target business data is synchronized to the first slave cache service node through the slave node output buffer corresponding to the first slave cache service node for synchronous backup.

[0028] In one embodiment, after detecting whether the node identifier of the first primary cache service node of the synchronization target end matches, the method further includes:

[0029] If it is determined that the node identifier of the first primary cache service node of the synchronization target end fails to match, a third type of full synchronization process is initiated to traverse the first business database, query and obtain business data whose business processing identifier is greater than the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, as the target business data;

[0030] Writing the target business data into a target relational database file;

[0031] The target relational database file is synchronized to the first slave cache service node through the slave node output buffer corresponding to the first slave cache service node for synchronous backup.

[0032] In one embodiment, the method further comprises:

[0033] Obtaining initial service data of data center access in the first region;

[0034] Determine the data type of the initial business data;

[0035] Determine an identification parameter for the initial business data according to a preset processing rule and the data type of the initial business data; and mark the initial business data using the identification parameter to obtain marked business data;

[0036] According to a preset processing rule, the marked business data is stored in the cached business data group of the current time period in the replication backlog buffer in the form of a node command.

[0037] In one embodiment, the data types include: a first type and a second type;

[0038] Among them, the first type is business data that has completed business processing in the data center of the first area; the second type is business data that has completed business processing in data centers in other areas except the data center of the first area.

[0039] In one embodiment, determining the data type of the initial service data includes:

[0040] Detect whether the initial service data carries the node identifier of the primary cache service node;

[0041] If it is determined that the initial service data carries the node identifier of the primary cache service node, extracting the node identifier of the primary cache service node;

[0042] Detecting whether a difference between the node identifier of the primary cache service node and the first primary cache service node identifier is less than or equal to a preset first difference threshold;

[0043] When it is determined that the difference between the node identifier of the primary cache service node and the first primary cache service node identifier is less than or equal to a preset first difference threshold, the data type of the initial service data is determined to be the first type.

[0044] In one embodiment, determining the identification parameter for the initial service data according to a preset processing rule and the data type of the initial service data includes:

[0045] In a case where the data type of the initial service data is the first type, the node identifier of the first primary cache service node is used as the node identifier of the primary cache service node of the initial service data;

[0046] Query and use the processing number when the initial business data is processed as the business processing identifier of the initial business data;

[0047] Query and generate a timestamp identifier of the initial business data based on the reception time of the initial business data.

[0048] In one embodiment, determining the identification parameter for the initial service data according to a preset processing rule and the data type of the initial service data further includes:

[0049] When the data type of the initial service data is the second type, retaining the node identifier of the primary cache service node and the service processing identifier carried by the initial service data;

[0050] Query and generate a timestamp identifier of the initial business data based on the reception time of the initial business data;

[0051] Generate a multi-active node synchronization tag for the initial business data.

[0052] In one embodiment, after storing the marked service data in the form of a node command into the cached service data group of the current time period in the replication backlog buffer, the method further includes:

[0053] In the hash table of the replication backlog buffer, the identification parameter associated with the business data after the mark is updated.

[0054] This specification provides a business data synchronization device based on remote multi-active, which is applied to a first server node, wherein the first server node is deployed in a data center in a first region and is connected to a first primary cache service node and a first secondary cache service node; wherein the first primary cache service node includes at least a replication backlog buffer constructed based on a preset construction rule, a secondary node output buffer corresponding to the first secondary cache service node, and a multi-active input buffer and a multi-active output buffer corresponding to data centers in other regions, including:

[0055] A classification module is used to receive and respond to target business data synchronization requests and determine the synchronization type of the business data;

[0056] an extraction module configured to extract, based on a preset synchronization rule and when determining that the synchronization type of the business data is remote multi-active synchronization, at least the node identifier of a first primary cache service node of a synchronization target end, a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end, and the node identifier of a second primary cache service node of a synchronization initiator end from a target business data synchronization request; wherein the second primary cache service node is deployed in a data center in a second region, and a corresponding second secondary cache service node is also deployed in the data center in the second region;

[0057] A first detection module is used to detect whether the node identifier of the first primary cache service node of the synchronization target end matches;

[0058] A second detection module is configured to detect whether, upon determining that a node identifier of the first primary cache service node of the synchronization target end matches, whether a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer; wherein the replication backlog buffer stores a cached business data group of the current time period obtained by processing based on a preset processing rule;

[0059] a determination module configured to, upon determining that a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer, determine, based on the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, target business data to be synchronized to the data center of the second region from the cached business data group in the current time period;

[0060] A synchronization module is used to synchronize the target business data to the second primary cache service node of the data center of the second area through the multi-active output buffer corresponding to the data center of the second area.

[0061] This specification provides a server, including a processor and a memory for storing processor-executable instructions. When the processor executes the instructions, the relevant steps of the business data synchronization method based on multi-site active-active are implemented.

[0062] This specification provides a computer-readable storage medium having computer instructions stored thereon, which, when executed by a processor, implement the relevant steps of the business data synchronization method based on remote multi-active.

[0063] This specification provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the relevant steps of the business data synchronization method based on multi-site active-active.

[0064] Based on the multi-active business data synchronization method, device and server based on remote multi-site provided in this specification, before specific implementation, according to the preset construction rules, the existing functions, structures and advantageous characteristics of the preset cache service can be fully utilized to respectively construct corresponding replication backlog buffers, slave node output buffers corresponding to the slave cache service nodes, and multi-active input buffers, multi-active output buffers, etc. corresponding to the data centers in other regions in the main cache service nodes of the data centers in each region, so as to complete the relevant deployment of the main cache service nodes and the slave cache service nodes; at the same time, according to the preset processing rules, the business data accessed by the data center can be processed, the identification parameters for the business data can be obtained, and the business data can be marked with the identification parameters and stored in the cache business data group of the current time period of the replication backlog buffer. In specific implementation, after receiving the target business data synchronization request, the synchronization type of the business data can be determined according to the preset synchronization rules; then, according to the synchronization type of the business data, different situations can be distinguished and the required identification information can be extracted from the target business data synchronization request; and according to the above identification information, the target business data to be synchronized can be efficiently determined by querying and utilizing the cache business data group of the current time period of the replication backlog buffer; and then the synchronization of the target business data can be completed by using the corresponding output buffer. This makes it well suited for complex big data synchronization scenarios involving multi-site active-active synchronization. It can automatically distinguish and synchronize relevant business data efficiently and accurately for different situations. At the same time, since no additional synchronization components are required, it can also effectively reduce deployment costs and improve the reliability of business data synchronization. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] In order to more clearly illustrate the embodiments of this specification, the following is a brief introduction to the drawings required for use in the embodiments. The drawings described below are only some of the embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0066] Figure 1 This is a flowchart of a business data synchronization method based on remote multi-active provided by an embodiment of this specification;

[0067] Figure 2 This is a schematic diagram of an embodiment of a business data synchronization method based on remote multi-active provided by an embodiment of this specification, in a scenario example;

[0068] Figure 3 This is a schematic diagram of an embodiment of a business data synchronization method based on remote multi-active provided by an embodiment of this specification, in a scenario example;

[0069] Figure 4This is a schematic diagram of an embodiment of a business data synchronization method based on remote multi-active provided by an embodiment of this specification, in a scenario example;

[0070] Figure 5 This is a schematic diagram of an embodiment of a business data synchronization method based on remote multi-active provided by an embodiment of this specification, in a scenario example;

[0071] Figure 6 This is a schematic diagram of an embodiment of a business data synchronization method based on remote multi-active provided by an embodiment of this specification, in a scenario example;

[0072] Figure 7 This is a schematic diagram of an embodiment of a business data synchronization method based on remote multi-active provided by an embodiment of this specification, in a scenario example;

[0073] Figure 8 This is a schematic diagram of the structure of a server provided by an embodiment of this specification;

[0074] Figure 9 This is a schematic diagram of the structure of a business data synchronization device based on remote multi-active provided by an embodiment of this specification;

[0075] Figure 10 This is a schematic diagram of an embodiment of a business data synchronization method based on remote multi-active provided by an embodiment of this specification, in a scenario example;

[0076] Figure 11 This is a schematic diagram of an embodiment of a business data synchronization method based on remote multi-active provided by an embodiment of this specification, in a scenario example;

[0077] Figure 12 This is a schematic diagram of an embodiment of a business data synchronization method based on remote multi-active provided by an embodiment of this specification, in a scenario example;

[0078] Figure 13 This is a schematic diagram of an embodiment of a business data synchronization method based on remote multi-active provided by an embodiment of this specification, in a scenario example;

[0079] Figure 14 This is a schematic diagram of an embodiment of a business data synchronization method based on multi-site active-active provided by an embodiment of this specification, applied in a scenario example. DETAILED DESCRIPTION

[0080] To help those skilled in the art better understand the technical solutions in this specification, the following will provide a clear and complete description of the technical solutions in the embodiments of this specification, in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. All other embodiments derived by those skilled in the art based on the embodiments in this specification without creative effort shall fall within the scope of protection of this specification.

[0081] It should be noted that the user-related information and data involved in the embodiments of this specification are all information and data authorized by the user or fully authorized by relevant parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users or relevant parties to choose to authorize or refuse.

[0082] It should also be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned. They should be regarded as exemplary and their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0083] See Figure 1 As shown, the embodiment of this specification provides a business data synchronization method based on remote multi-active. Among them, the method can be specifically applied to the first server node side. Figure 2 As shown, the first server node is deployed in a data center in a first region and is connected to a first primary cache service node and a first secondary cache service node; wherein the first primary cache service node includes at least a replication backlog buffer constructed based on a preset construction rule, a secondary node output buffer corresponding to the first secondary cache service node, and a multi-active input buffer and a multi-active output buffer corresponding to data centers in other regions. The specific implementation of the method may include the following:

[0084] S101: Receive and respond to a target business data synchronization request, and determine the synchronization type of the business data;

[0085] S102: According to a preset synchronization rule, when it is determined that the synchronization type of the business data is remote multi-active synchronization, extract from the target business data synchronization request at least a node identifier (e.g., serverId) of a first primary cache service node of the synchronization target end, a business processing identifier (e.g., optId) of existing business data associated with the first primary cache service node of the synchronization target end, and a node identifier (e.g., pserverId) of a second primary cache service node of the synchronization initiator end; wherein the second primary cache service node is deployed in a data center of a second region, and a corresponding second secondary cache service node is also deployed in the data center of the second region;

[0086] S103: Detect whether the node identifier of the first primary cache service node of the synchronization target end matches;

[0087] S104: If it is determined that the node identifier of the first primary cache service node of the synchronization target end matches, detecting whether there is a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer; wherein the replication backlog buffer stores a cache business data group of the current time period obtained by processing based on a preset processing rule;

[0088] S105: When it is determined that the business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer, target business data to be synchronized to the data center of the second region is determined from the cached business data group in the current time period according to the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end;

[0089] S106: Synchronize the target business data to the second primary cache service node of the data center in the second region through the multi-active output buffer corresponding to the data center in the second region.

[0090] Among them, the above-mentioned multi-site active-active can refer to deploying independent data centers in different regions. Different data centers in multiple regions provide services for related business processing at the same time and automatically complete the consistency synchronization of related business data.

[0091] The first server node may be deployed with a preset cache service, and accordingly, the first primary cache service node and the first secondary cache service node may be a primary cache node and a secondary cache node based on the preset cache service.

[0092] Specifically, for example, the cache service may be a Redis-based cache service.

[0093] The Redis (Remote Dictionary Server) can specifically refer to a high-performance key-value database. Accordingly, the first primary cache service node can specifically be referred to as the first Redis master node, and the first secondary cache service node can specifically be referred to as the first Redis slave node (or the first Redis backup node).

[0094] Based on the above embodiment, the existing functions and structures of the preset cache service deployed on the first server node can be fully utilized. Without the need to introduce additional synchronization components, it is better suitable for big data synchronization scenarios involving more complex multi-active synchronization in different locations. It can automatically distinguish different situations and realize the synchronization of related business data efficiently and accurately.

[0095] In some embodiments, the aforementioned geo-multi-active business data synchronization method can be specifically applied to a first service node, where the first server node is deployed in a data center in a first region and can be specifically used to access and process transaction business data initiated by the trading platform in the first region and within the jurisdiction of the first region.

[0096] Before implementation, please refer to Figure 2 As shown, based on preset construction rules and utilizing the existing functions and structure of the preset cache service, the first primary cache service node and the first secondary cache service node can be modified to obtain modified first primary cache service nodes and first secondary cache service nodes suitable for complex big data synchronization scenarios involving multi-site active-active synchronization. Specifically, the preset construction rules can be rules generated based on the existing functions and structure of the preset cache service, as well as the performance characteristics of the preset cache service.

[0097] For details, see Figure 2 As shown, according to the preset construction rules, corresponding replication backlog buffers, slave node output buffers corresponding to the first slave cache service node (also referred to as Slave output buffers), and multi-active input buffers and multi-active output buffers corresponding to data centers in other regions (for example, multi-active input buffers corresponding to the data center in the second region, multi-active input buffers corresponding to the data center in the third region, etc., also referred to as Peer output buffers) can be constructed in the primary cache negative nodes of the data center in the first region.

[0098] Specifically, the first master cache service node can be connected to the first slave cache service node via the slave node output buffer. The first master cache service node can be connected to the master cache service nodes of data centers in corresponding other regions via the multi-active input buffer and the multi-active output buffer.

[0099] Among them, the above-mentioned replication backlog buffer is used to temporarily cache the business data that the data center in the first area accesses and completes business processing by itself in the current time period (which can be simply referred to as the first type of business data), and the business data that the data center in the first area obtains by synchronizing with the data centers in other areas and accesses and completes business processing by the data centers in other areas (which can be simply referred to as the second type of business data).

[0100] Specifically, in the above-mentioned replication backlog buffer, according to preset processing rules, business data marked with corresponding identification parameters can be stored in the cached business data group of the current time period of the replication backlog buffer in the form of node commands (for example, cmd commands).

[0101] The first primary cache service node may further include a command processing module. Accordingly, the first server node may invoke the command processing module to execute relevant node commands in the cached service data group for the current time period in the replication backlog buffer, thereby synchronizing the corresponding service data in the replication backlog buffer to the first secondary cache service node and / or data centers in other regions.

[0102] The multi-active input buffer is used to receive and cache business data synchronized from data centers in other corresponding regions. The multi-active output buffer is used to cache and synchronize relevant business data to data centers in other corresponding regions. The slave node output buffer is used to cache and synchronize relevant business data to the first slave cache service node.

[0103] Furthermore, according to preset construction rules, the first primary cache service node may also include a client input buffer and a client output buffer. The client input buffer is used to receive and cache business data (e.g., transaction data) initiated by a client (referred to as a client). The client output buffer is used to cache and feedback the results of business data processing in response to the client.

[0104] Furthermore, the first primary cache service node is connected to the first service database in the data center of the first region via a command processing module. Accordingly, the first server node can also invoke the command processing module to execute relevant node commands in the cached service data group for the current time period in the replication backlog buffer, thereby synchronously updating the corresponding service data in the replication backlog buffer to the first service database.

[0105] Based on pre-defined configuration rules, the first slave cache service node may also be deployed with a corresponding slave node input buffer and command processing module. The slave node input buffer is used to receive and cache business data synchronized from the first master cache service node. The command processing module then synchronizes the business data in the slave node input buffer to the first backup data file maintained by the first slave cache service node.

[0106] Similar to the data center in the first region, similar server nodes, primary cache service nodes, and secondary cache service nodes are deployed in other data centers in other regions according to preset construction rules.

[0107] In this way, without the need for additional synchronization components, we can leverage the existing functionality and structure of the pre-set cache service to build a business data synchronization network system that can reliably connect different data centers in different regions. Subsequently, this business data synchronization network system can be used to implement multi-site active-active business data synchronization processing.

[0108] In this embodiment, the server node may specifically include a background server applied to a data processing system that can implement functions such as data transmission and data processing. Specifically, the server node may be, for example, an electronic device with data computing, storage, and network interaction functions. Alternatively, the server node may be a software program running on the electronic device that provides support for data processing, storage, and network interaction. In this embodiment, the number of servers included in the server node is not specifically limited. The server node may specifically be a single server, several servers, or a server cluster formed by several servers.

[0109] In this embodiment, the client may specifically include a front-end applied to the user side that can implement functions such as data collection and data transmission. Specifically, the client may be, for example, an electronic device such as a desktop computer, tablet computer, laptop computer, or smartphone. Alternatively, the client may be a software application that can run on the above electronic devices.

[0110] In some embodiments, upon detecting that a service data synchronization trigger condition is met, the first slave cache service node, or a master cache service node in a data center in another region (e.g., a second master cache service node deployed in a data center in the second region), may initiate a corresponding target service data synchronization request to the first server node. The target service data synchronization request carries at least the IP address of the initiator.

[0111] The synchronization triggering conditions may specifically include at least one of the following: a failure of device hardware or software, a preset synchronization time interval, first connection to a synchronization network system, and the like.

[0112] Accordingly, in a specific implementation, after receiving the target business data synchronization request, the first server node can first extract the IP address of the initiator; then perform an address difference comparison between the IP address of the initiator and its own IP address to obtain the corresponding address difference comparison result. According to the address difference comparison result, when it is determined that the address difference value between the two IP addresses is less than or equal to the preset address difference threshold, it is determined that the target business data synchronization request comes from the first slave cache service node, and then it can be determined that the synchronization type of the business data requested by the target business data synchronization request is local slave node synchronization. On the contrary, when it is determined that the address difference value between the two IP addresses is greater than the preset address difference threshold, it is determined that the target business data synchronization request comes from the master cache service node of other data centers in other regions, and then it can be determined that the synchronization type of the business data requested by the target business data synchronization request is remote multi-active synchronization.

[0113] In some embodiments, if the synchronization type of the business data is determined to be remote multi-active synchronization, the target business data synchronization request may be further checked for an identity credential associated with the synchronization initiator. If the identity credential is detected, the identity credential is decrypted using a node key corresponding to the first primary cache service node according to a preset decryption algorithm to obtain a corresponding node identifier. This node identifier is then compared with the node identifier of the second primary cache service node of the synchronization initiator, extracted based on the target business data synchronization request, to determine whether the two node identifiers are consistent. If the two node identifiers are consistent, the verification is determined to be successful. The target business data synchronization request may be responded to and subsequent data processing may continue. Conversely, if the two node identifiers are inconsistent, the verification is determined to be unsuccessful. In this case, it can be determined that the target business data synchronization request is likely forged and presents a security risk. To prevent business data leakage, the target business data synchronization request may be temporarily unresponsive. Furthermore, based on the node identifier of the second primary cache service node of the synchronization initiator, an error message regarding the target business data synchronization request may be sent to the second primary cache service node in the data center of the second region.

[0114] In some embodiments, see Figure 3 As shown, after detecting whether the node identifier of the first primary cache service node of the synchronization target end matches, the method may further include the following contents when implemented:

[0115] S1: When it is determined that the node identifier of the first primary cache service node of the synchronization target end fails to match, a first type full synchronization process is initiated to traverse the first business database, query and obtain business data whose business processing identifier is greater than the business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end, as target business data;

[0116] S2: writing the target business data into a target relational database file;

[0117] S3: Synchronize the target relational database file to the second primary cache service node of the data center in the second region through the multi-active output buffer corresponding to the data center in the second region.

[0118] Based on the above embodiment, for remote multi-active synchronization, according to the preset synchronization rules, when it is determined that the node identifier match of the first primary cache service node of the synchronization target end fails, the first business database can be switched to complete the synchronization of relevant business data efficiently and accurately.

[0119] In some embodiments, specifically detecting whether the node identifier of the first primary cache service node of the synchronization target end matches or passes can include: first detecting whether the node identifier of the first primary cache service node of the synchronization target end obtained based on the target business data synchronization request is the same as the node identifier of the local first primary cache service node; if it is determined that they are the same, further detecting whether the node identifier of the first primary cache service node of the synchronization target end exists in the cache business data group of the current time period of the replication backlog buffer; if so, determining that the node identifier of the first primary cache service node of the synchronization target end matches or passes. Otherwise, determining that the node identifier of the first primary cache service node of the synchronization target end does not match or pass.

[0120] In some embodiments, if it is determined that the node identifier of the first primary cache service node at the synchronization target fails to match, it can be determined that the data center in the second region may be synchronizing business data with the data center in the first region for the first time; or that a long time has passed since the last business data synchronization between the data center in the second region and the data center in the first region, and that the data center in the first region has not directly accessed and processed business data during the current time period. In this case, the first business database can be accessed and queried through the first-type full synchronization process to generate a corresponding target relational data file (e.g., an RDB file) to complete the relevant business data synchronization.

[0121] In some embodiments, when it is determined that the synchronization type of the business data is remote multi-active synchronization, refer to Figure 4 As shown, when the method is implemented, it may also include the following contents:

[0122] S1: Detect whether the target service data synchronization request carries a service processing identifier of existing service data associated with the second primary cache service node of the synchronization initiator;

[0123] S2: When it is determined that the target service data synchronization request carries the service processing identifier of the existing service data associated with the second primary cache service node of the synchronization initiator, extract the service processing identifier of the existing service data associated with the second primary cache service node of the synchronization initiator from the target service data synchronization request;

[0124] S3: Detect whether there is a business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator in the replication backlog buffer;

[0125] S4: When it is determined that there is no business processing identifier of the existing business data associated with the second primary cache service node of the synchronization initiator in the replication backlog buffer, start the second type of full synchronization process, traverse the first business database, query and obtain business data whose business processing identifier is greater than the business processing identifier of the existing business data associated with the second primary cache service node of the synchronization initiator, as the target business data.

[0126] Based on the above embodiment, according to the preset synchronization rules, the target business data to be synchronized can be accurately and completely determined by jointly using the replication backlog buffer and the first business database, so as to accurately complete the business data synchronization.

[0127] In some embodiments, after determining the synchronization type of the business data, refer to Figure 5 As shown, when the method is implemented, it may also include the following contents:

[0128] S1: According to a preset synchronization rule, if the synchronization type of the business data is determined to be local slave node synchronization, extracting from the target business data synchronization request the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end;

[0129] S2: Check whether the node identifier of the first primary cache service node of the synchronization target end matches;

[0130] S3: If it is determined that the node identifier of the first primary cache service node of the synchronization target end matches, detecting whether there is a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer;

[0131] S4: When it is determined that the business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer, target business data to be synchronized to the first secondary cache service node is determined from the cached business data group in the current time period according to the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end;

[0132] S5: Synchronize the target business data to the first slave cache service node through the slave node output buffer corresponding to the first slave cache service node for synchronous backup.

[0133] Based on the above embodiment, for local slave node synchronization, the synchronization backup of relevant business data can be efficiently completed by utilizing the replication backlog cache according to the preset synchronization rules.

[0134] In some embodiments, see Figure 6 As shown, after detecting whether the node identifier of the first primary cache service node of the synchronization target end matches, the method may further include:

[0135] S1: When it is determined that the node identifier of the first primary cache service node of the synchronization target end fails to match, a third type full synchronization process is initiated to traverse the first business database, query and obtain business data whose business processing identifier is greater than the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, as the target business data;

[0136] S2: writing the target business data into a target relational database file;

[0137] S3: Synchronize the target relational database file to the first slave cache service node through the slave node output buffer corresponding to the first slave cache service node for synchronous backup.

[0138] Based on the above embodiment, for local slave node synchronization, according to the preset synchronization rules, when it is determined that the node identifier match of the first main cache service node of the synchronization target end fails, the first business database can be switched to complete the synchronization of relevant business data efficiently and accurately.

[0139] If it is determined that the node identifier of the first primary cache service node at the synchronization target fails to match, it can be determined that this is the first time the first slave cache service node is synchronizing business data with the first primary cache service node; or, a significant period of time has passed since the first slave cache service node's first synchronization of business data with the first primary cache service node, and within the current time period, the data center in the first region is not directly accessing and processing business data. In this case, the first type of full synchronization process can be used to access and query the first business database to generate a corresponding target relational data file (e.g., an RDB file) to complete the synchronization of the relevant business data.

[0140] In some embodiments, see Figure 7 As shown, when the method is implemented, it may also include the following contents:

[0141] S1: Obtaining initial service data of data center access in the first region;

[0142] S2: Determine the data type of the initial business data;

[0143] S3: Determine an identification parameter for the initial business data according to a preset processing rule and the data type of the initial business data; and mark the initial business data using the identification parameter to obtain marked business data;

[0144] S4: According to a preset processing rule, the marked business data is stored in the cached business data group of the current time period in the replication backlog buffer in the form of a node command.

[0145] Based on the above embodiment, the newly accessed initial business data can be processed accordingly according to the preset processing rules to obtain the marked business data that meets the requirements; the marked business data is then stored in the cached business data group of the current time period of the replication backlog buffer in the form of a node command, so as to facilitate subsequent efficient and accurate synchronization of business data with the first slave cache service node and / or with data centers in other regions.

[0146] In some embodiments, according to preset processing rules, the identification parameters generated for the initial service data may specifically include at least one of the following: a node identifier of the primary cache service node (e.g., serverId), a service processing identifier (e.g., optId), a timestamp identifier (e.g., Timestamp), and a multi-active node synchronization tag (e.g., !!!). The multi-active node synchronization tag is used to indicate that the initial service data is service data synchronized after being directly accessed and processed by a data center in another region.

[0147] In some embodiments, the data types may specifically include: a first type and a second type, etc.;

[0148] Among them, the first type is business data that has completed business processing in the data center of the first area; the second type is business data that has completed business processing in data centers in other areas except the data center of the first area.

[0149] Specifically, the first type mentioned above can also be understood as business data that is not synchronized from data centers in other regions. The second type mentioned above can also be understood as business data that is synchronized from data centers in other regions.

[0150] Based on the above embodiment, different types of business data can be distinguished so that the synchronization of relevant business data can be completed more finely and targetedly according to the holding status of different types of business data by the main cache service node and the first slave cache service node of the data center in other regions.

[0151] In some embodiments, the above-mentioned determination of the data type of the initial service data may include the following when specifically implemented:

[0152] S1: Check whether the initial service data carries the node identifier of the primary cache service node;

[0153] S2: if it is determined that the initial service data carries the node identifier of the primary cache service node, extract the node identifier of the primary cache service node;

[0154] S3: Detect whether the difference between the node identifier of the primary cache service node and the first primary cache service node identifier is less than or equal to a preset first difference threshold;

[0155] S4: When it is determined that the difference between the node identifier of the primary cache service node and the first primary cache service node identifier is less than or equal to a preset first difference threshold, determine that the data type of the initial service data is the first type.

[0156] On the contrary, when it is determined that the difference between the node identifier of the primary cache service node and the first primary cache service node identifier is greater than a preset first difference threshold, the data type of the initial service data is determined to be the second type.

[0157] Based on the above embodiment, the type of the initial business data can be automatically and accurately determined.

[0158] In some embodiments, the above-mentioned determination of the identification parameter for the initial business data based on the preset processing rules and the data type of the initial business data may include the following when specifically implemented:

[0159] S1: When the data type of the initial service data is the first type, the node identifier of the first primary cache service node is used as the node identifier of the primary cache service node of the initial service data;

[0160] S2: Query and use the processing number of the initial business data as the business processing identifier of the initial business data;

[0161] S3: Query and generate a timestamp identifier of the initial service data according to the reception time of the initial service data.

[0162] Based on the above embodiment, for initial business data belonging to the first type, relevant identification parameters can be accurately determined according to preset processing rules, and then the initial business data can be marked according to the identification parameters to obtain marked business data that meets the requirements.

[0163] In some embodiments, the above-mentioned determination of the identification parameter for the initial business data based on the preset processing rule and the data type of the initial business data may further include the following contents during specific implementation:

[0164] S1: When the data type of the initial service data is the second type, retain the node identifier of the primary cache service node and the service processing identifier carried by the initial service data;

[0165] S2: Query and generate a timestamp identifier of the initial service data according to the reception time of the initial service data;

[0166] S3: Generate a multi-active node synchronization tag for the initial business data.

[0167] Based on the above embodiment, for initial business data belonging to the second type, relevant identification parameters can be accurately determined according to preset processing rules, and then the initial business data can be marked according to the identification parameters to obtain marked business data that meets the requirements.

[0168] In some embodiments, after storing the marked service data in the form of a node command into the cached service data group of the current time period in the replication backlog buffer, the method may further include:

[0169] In the hash table of the replication backlog buffer, the identification parameter associated with the business data after the mark is updated.

[0170] Here, through a big data analysis of a large number of historical business data synchronization requests, combined with specific business data synchronization requirements, we found that data centers in other regions are more likely to synchronize Type 1 business data directly accessed and processed by the data center in the first region. Conversely, for the first server node, the synchronization frequency for Type 1 business data is much higher than that for Type 2 business data.

[0171] Therefore, in order to further improve the synchronization efficiency of the first type of business data, the identification parameters of the first type of business data, such as the node identification of the primary cache service node, the business processing identification, etc., can be synchronously stored in the corresponding hash table; and a mapping relationship between the identification parameters of the first type of business data in the hash table and the business data in the cache business data group of the current time period of the copy backlog buffer is established.

[0172] Accordingly, when the first type of business data needs to be synchronized, the synchronization of the relevant business data can be completed more efficiently and conveniently by querying the hash table.

[0173] Based on the above embodiments, the synchronization efficiency of the first type of business data can be further improved, thereby improving the overall business data synchronization efficiency.

[0174] In some embodiments, during implementation, newly generated marked service data can be used to overwrite the oldest marked service data in the cached service data group for the current time period in the replication backlog buffer at predetermined intervals or upon accumulation of a specified amount of service data, thereby updating the cached service data group for the current time period. This allows for better utilization of the limited cache resources in the replication buffer, maximizing the cache capacity of service data that is more likely to require subsequent synchronization.

[0175] In some embodiments, during specific implementation, the first business database may be updated by copying the cached business data group of the current time period in the backlog buffer at intervals of a preset first time period to achieve data synchronization of the first business database.

[0176] It is also possible to generate a corresponding AOF file by copying the cached business data group of the current time period in the backlog buffer at intervals of a preset second time period; and store the AOF file in the corresponding disk according to the time information as an index to achieve persistent storage, which is convenient for subsequent backtracking queries and disaster recovery.

[0177] In some embodiments, when the method is implemented, it may also include: detecting whether the business data synchronization trigger condition is currently met; when it is determined that the business data synchronization trigger condition is currently met, determining the data center that needs to be synchronized as the synchronization target end; obtaining the node identifier of the primary cache service node of the synchronization target end by querying the preset data center information list; at the same time, based on the node identifier of the primary cache service node of the synchronization target end, querying the cached business data group of the current time period in the replication backlog buffer, and determining the business processing identifier of the existing business data associated with the primary cache service node of the synchronization target end; and then generating a corresponding target business data synchronization request based on the node identifier of the primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the primary cache service node of the synchronization target end; and then sending the target business data synchronization request to the server node of the synchronization target end to automatically synchronize the business data with the data center.

[0178] As can be seen from the above, the business data synchronization method based on multi-active in different locations provided by the embodiment of this specification can, before being implemented, make full use of the advantages of the relevant cache service according to the preset construction rules, and respectively build corresponding replication backlog buffers, slave node output buffers corresponding to the slave cache service nodes, and multi-active input buffers and multi-active output buffers corresponding to the data centers in other regions in the main cache service nodes of the data centers in each region; at the same time, the accessed business data can be processed according to the preset processing rules, and the identification parameters for the business data can be obtained. After marking the business data with the identification parameters, the data is stored in the cache business data group of the current time period in the replication backlog buffer to complete the relevant deployment. In specific implementation, after receiving the target business data synchronization request, the synchronization type of the business data can be determined according to the preset synchronization rules; according to the synchronization type of the business data, different situations can be distinguished, and the required identification information can be extracted from the target business data synchronization request; then, based on the above identification information, the target business data to be synchronized can be efficiently determined by querying and utilizing the cache business data group of the current time period in the replication backlog buffer; and then the synchronization of the target business data is completed by using the corresponding output buffer. This makes it well-suited for complex big data synchronization scenarios involving multi-site active-active synchronization. It can automatically distinguish different situations and efficiently and accurately synchronize related business data. At the same time, since no additional synchronization components need to be introduced, it effectively reduces deployment costs and improves the reliability of business data synchronization.

[0179] See Figure 8 As shown, the embodiment of this specification further provides a server, wherein the server includes a network communication port 801, a processor 802, and a memory 803, and the above structures are connected through internal cables so that each structure can perform specific data interaction.

[0180] The network communication port 801 may be used to receive a target service data synchronization request.

[0181] The processor 802 can be specifically used to respond to the target business data synchronization request and determine the synchronization type of the business data; according to the preset synchronization rules, when it is determined that the synchronization type of the business data is remote multi-active synchronization, at least the node identifier of the first primary cache service node of the synchronization target end, the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, and the node identifier of the second primary cache service node of the synchronization initiator are extracted from the target business data synchronization request; wherein the second primary cache service node is deployed in the data center of the second area, and the data center of the second area is also deployed with a corresponding second secondary cache service node; detect whether the node identifier of the first primary cache service node of the synchronization target end matches; when it is determined that the node identifier of the first primary cache service node of the synchronization target end matches, detect the replication backlog Whether there is a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end in the buffer; wherein, the cache business data group of the current time period obtained based on the preset processing rules is stored in the replication backlog buffer; when it is determined that there is a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer, according to the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, the target business data to be synchronized to the data center of the second area is determined from the cache business data group of the current time period; the target business data is synchronized to the second primary cache service node of the data center of the second area through the multi-active output buffer corresponding to the data center of the second area.

[0182] The memory 803 may be specifically used to store corresponding instruction programs and intermediately generated target business data.

[0183] Based on the above algorithm, the relevant structural performance of the server can be effectively utilized, the data processing speed of electronic equipment can be improved, and data processing based on remote multi-active business data synchronization can be efficiently realized.

[0184] In this embodiment, the network communication port 801 can be a virtual port that is bound to different communication protocols, thereby being capable of sending or receiving different data. For example, the network communication port can be a port responsible for web data communication, a port responsible for FTP data communication, or a port responsible for email data communication. Furthermore, the network communication port can also be a physical communication interface or communication chip. For example, it can be a wireless mobile network communication chip, such as GSM or CDMA; it can also be a Wi-Fi chip; or it can be a Bluetooth chip.

[0185] In this embodiment, the processor 802 may be implemented in any suitable manner. For example, the processor may take the form of a microprocessor or a processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, an embedded microcontroller, etc. This specification is not intended to limit this.

[0186] In this embodiment, the memory 803 may include multiple levels. In a digital system, anything that can store binary data can be a memory. In an integrated circuit, a circuit with a storage function that has no physical form is also called a memory, such as RAM, FIFO, etc. In a system, a storage device with a physical form is also called a memory, such as a memory stick, TF card, etc.

[0187] The embodiment of this specification also provides a computer-readable storage medium based on the above-mentioned business data synchronization method based on remote multi-active, wherein the computer-readable storage medium stores computer program instructions, which, when executed, implement: receiving and responding to a target business data synchronization request, and determining the synchronization type of the business data; according to a preset synchronization rule, when it is determined that the synchronization type of the business data is remote multi-active synchronization, extracting at least the node identifier of the first primary cache service node of the synchronization target end, the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, and the node identifier of the second primary cache service node of the synchronization initiator from the target business data synchronization request; wherein the second primary cache service node is deployed in a data center of a second area, and a corresponding second secondary cache service node is also deployed in the data center of the second area; detecting whether the node identifier of the first primary cache service node of the synchronization target end matches; and after determining When the node identifier of the first primary cache service node of the synchronization target end matches, it is detected whether there is a business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer; wherein, the replication backlog buffer stores the cache business data group of the current time period obtained based on the preset processing rules; when it is determined that there is a business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer, the target business data to be synchronized to the data center of the second area is determined from the cache business data group of the current time period based on the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end; the target business data is synchronized to the second primary cache service node of the data center of the second area through the multi-active output buffer corresponding to the data center of the second area.

[0188] In this embodiment, the storage medium includes, but is not limited to, random access memory (RAM), read-only memory (ROM), cache, hard disk drive (HDD), or memory card. The memory can be used to store computer program instructions. The network communication unit can be an interface configured in accordance with the standards specified by the communication protocol for network connection communication.

[0189] In this embodiment, the functions and effects specifically implemented by the program instructions stored in the computer-readable storage medium can be explained in comparison with other implementations and will not be repeated here.

[0190] The embodiments of the present specification also provide a computer program product, which at least includes a computer program, and when the computer program is executed by a processor, implements the following method steps: receiving and responding to a target business data synchronization request, and determining the synchronization type of the business data; according to a preset synchronization rule, when it is determined that the synchronization type of the business data is remote multi-active synchronization, extracting at least the node identifier of the first primary cache service node of the synchronization target end, the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, and the node identifier of the second primary cache service node of the synchronization initiator from the target business data synchronization request; wherein the second primary cache service node is deployed in a data center of a second area, and a corresponding second secondary cache service node is also deployed in the data center of the second area; detecting whether the node identifier of the first primary cache service node of the synchronization target end matches; after determining that the first primary cache service node of the synchronization target end matches When the node identifier of the node matches, it is detected whether there is a business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer; wherein, the replication backlog buffer stores the cache business data group of the current time period obtained based on the preset processing rules; when it is determined that there is a business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer, the target business data to be synchronized to the data center of the second area is determined from the cache business data group of the current time period based on the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end; the target business data is synchronized to the second primary cache service node of the data center of the second area through the multi-active output buffer corresponding to the data center of the second area.

[0191] See Figure 9 As shown, at the software level, an embodiment of this specification further provides a business data synchronization device based on remote multi-active, which is applied to a first server node, the first server node being deployed in a data center in a first region and connected to a first primary cache service node and a first secondary cache service node; wherein the first primary cache service node includes at least a replication backlog buffer constructed based on a preset construction rule, a secondary node output buffer corresponding to the first secondary cache service node, and a multi-active input buffer and a multi-active output buffer corresponding to data centers in other regions, and may include:

[0192] The classification module 901 may be specifically configured to receive and respond to a target business data synchronization request and determine a synchronization type of the business data;

[0193] Extraction module 902 may be specifically configured to extract, based on a preset synchronization rule and when determining that the synchronization type of the business data is remote multi-active synchronization, at least the node identifier of the first primary cache service node of the synchronization target end, the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, and the node identifier of the second primary cache service node of the synchronization initiator end from the target business data synchronization request; wherein the second primary cache service node is deployed in a data center in a second region, and a corresponding second secondary cache service node is also deployed in the data center in the second region;

[0194] The first detection module 903 may be specifically configured to detect whether the node identifier of the first primary cache service node of the synchronization target end matches;

[0195] The second detection module 904 may be specifically configured to detect whether, when it is determined that the node identifier of the first primary cache service node of the synchronization target end matches, there is a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer; wherein the replication backlog buffer stores a cached business data group of the current time period obtained by processing based on a preset processing rule;

[0196] Determining module 905 may be specifically configured to, upon determining that a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer, determine, based on the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, target business data to be synchronized to the data center of the second region from the cached business data group in the current time period;

[0197] The synchronization module 906 may be specifically configured to synchronize the target business data to the second primary cache service node of the data center of the second region through the multi-active output buffer corresponding to the data center of the second region.

[0198] In some embodiments, after detecting whether the node identifier of the first primary cache service node of the synchronization target end matches, the device can also be used, when implemented, to: when it is determined that the node identifier of the first primary cache service node of the synchronization target end does not match, start a first type of full synchronization process, traverse the first business database, query and obtain business data whose business processing identifier is greater than the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, as the target business data; write the target business data into the target relational database file; synchronize the target relational database file to the second primary cache service node of the data center of the second area through the multi-active output buffer corresponding to the data center of the second area.

[0199] In some embodiments, when it is determined that the synchronization type of business data is off-site multi-active synchronization, the device can also be used, when implemented, to: detect whether the target business data synchronization request carries a business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator; when it is determined that the target business data synchronization request carries a business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator, extract the business processing identifier of the existing business data associated with the second primary cache service node of the synchronization initiator from the target business data synchronization request; detect whether there is a business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator in the replication backlog buffer; when it is determined that there is no business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator in the replication backlog buffer, start a second type of full synchronization process, traverse the first business database, query and obtain business data whose business processing identifier is greater than the business processing identifier of the existing business data associated with the second primary cache service node of the synchronization initiator as the target business data.

[0200] In some embodiments, after determining the synchronization type of the business data, the device can also be used, when implemented, to: extract the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end from the target business data synchronization request according to the preset synchronization rules; detect whether the node identifier of the first primary cache service node of the synchronization target end matches; and detect whether there is a business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer when it is determined that the node identifier of the first primary cache service node of the synchronization target end matches. the business processing identifier of the existing business data associated with the first master cache service node of the synchronization target end; when it is determined that the business processing identifier of the existing business data associated with the first master cache service node of the synchronization target end exists in the replication backlog buffer, according to the node identifier of the first master cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first master cache service node of the synchronization target end, determine the target business data to be synchronized to the first slave cache service node from the cache business data group of the current time period; synchronize the target business data to the first slave cache service node through the slave node output buffer corresponding to the first slave cache service node for synchronous backup.

[0201] In some embodiments, after detecting whether the node identifier of the first primary cache service node of the synchronization target end matches, the device can also be used, when implemented, to: when it is determined that the node identifier of the first primary cache service node of the synchronization target end does not match, start a third type of full synchronization process, traverse the first business database, query and obtain business data whose business processing identifier is greater than the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, as the target business data; write the target business data into the target relational database file; synchronize the target relational database file to the first slave cache service node through the slave node output buffer corresponding to the first slave cache service node for synchronization backup.

[0202] In some embodiments, when the device is implemented, it can also be used to: obtain the initial business data accessed by the data center in the first area; determine the data type of the initial business data; determine the identification parameters for the initial business data based on preset processing rules and the data type of the initial business data; and use the identification parameters to mark the initial business data to obtain marked business data; according to preset processing rules, store the marked business data in the form of node commands into the cached business data group of the current time period of the replication backlog buffer.

[0203] In some embodiments, the data types may specifically include: a first type and a second type, etc.;

[0204] Among them, the first type is business data that has completed business processing in the data center of the first area; the second type is business data that has completed business processing in data centers in other areas except the data center of the first area.

[0205] In some embodiments, the device can specifically determine the data type of the initial business data in the following manner: detect whether the initial business data carries the node identifier of the primary cache service node; if it is determined that the initial business data carries the node identifier of the primary cache service node, extract the node identifier of the primary cache service node; detect whether the difference value between the node identifier of the primary cache service node and the first primary cache service node identifier is less than or equal to a preset first difference threshold; if it is determined that the difference value between the node identifier of the primary cache service node and the first primary cache service node identifier is less than or equal to the preset first difference threshold, determine that the data type of the initial business data is the first type.

[0206] In some embodiments, the device can specifically determine the identification parameters for the initial business data according to the preset processing rules and the data type of the initial business data in the following manner: when the data type of the initial business data is the first type, the node identifier of the first primary cache service node is used as the node identifier of the primary cache service node of the initial business data; the processing number when the business processing is performed on the initial business data is queried and used as the business processing identifier of the initial business data; and the timestamp identifier of the initial business data is queried and generated based on the reception time of the initial business data.

[0207] In some embodiments, the device can also specifically determine the identification parameters for the initial business data based on preset processing rules and the data type of the initial business data in the following manner: when the data type of the initial business data is the second type, retain the node identification of the primary cache service node carried by the initial business data, and the business processing identification; query and generate a timestamp identification of the initial business data based on the reception time of the initial business data; and generate a multi-active node synchronization tag for the initial business data.

[0208] In some embodiments, after the marked business data is stored in the cached business data group of the current time period of the replication backlog buffer in the form of a node command, the device, when implemented, can also be used to: update the identification parameters associated with the marked business data in the hash table of the replication backlog buffer.

[0209] It should be noted that the units, devices or modules described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. For the convenience of description, the above devices are described in terms of functions and are divided into various modules and described separately. Of course, when implementing this specification, the functions of each module can be implemented in the same or multiple software and / or hardware, or the module that implements the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0210] As can be seen from the above, the business data synchronization device based on remote multi-active provided in the embodiment of this specification can be well applied to big data synchronization scenarios involving more complex remote multi-active synchronization, automatically distinguish different situations, and realize the synchronization of related business data efficiently and accurately; at the same time, since there is no need to introduce additional synchronization components, the deployment cost is effectively reduced and the reliability of business data synchronization is improved.

[0211] In a specific scenario example, the business data synchronization method based on remote multi-active provided in this specification can be applied to implement remote multi-active data synchronization based on Redis. For the specific implementation process, please refer to the following content.

[0212] In this scenario example, considering that most existing synchronization methods introduce an intermediate component to synchronize data bidirectionally between nodes in two data centers, you can refer to Figure 10 shown.

[0213] When the above method is implemented, it often has the following disadvantages: 1) it increases the difficulty of cluster deployment; 2) it increases synchronization delay; 3) it increases the difficulty of operation and maintenance problem investigation.

[0214] To address the above issues, this scenario example considers Redis as the storage node. In response to the defects and shortcomings of the existing methods, based on the community Redis source code, the master-slave data synchronization process is modified. Without introducing third-party components, the Redis node itself has the function of two-way synchronization between multiple active nodes in different locations (that is, the master cache service node and slave cache service node based on the preset cache service in the data center are constructed according to the preset construction rules).

[0215] In this scenario example, the overall synchronization architecture can be found in Figure 11 As shown, each Redis master node in the cluster (e.g., the first master cache service node) receives two types of data, including: 1. request data from normal clients (first type), and 2. synchronization data from Redis nodes in other data centers (second type).

[0216] Accordingly, the command module can process data in categories 1 and 2, update user data (for example, update the first business database), and save the data in the replication backlog buffer. At the same time, the data in the replication backlog buffer can also be synchronized to the AOF file and the Redis backup node (for example, the first slave cache service node). In addition, the data in category 1 of the replication backlog buffer can also be synchronized to the Redis master node in another data center (for example, the second master cache service node).

[0217] In this scenario example, when constructing the copy buffer, you can refer to Figure 12When the command processing module processes a normal client command (business data), four additional pieces of information (identification parameters) are added, including: Timestamp (timestamp parameter), which is the timestamp of the request receipt; serverId (node ​​identifier of the primary cache service node), which is the Redis identifier of the first Redis node that processed the request; optId (business processing identifier), which is the sequence number for processing the request. Each time a Redis node processes a normal write request, optId increases by 1, and this sequence number increases monotonically; and ! ! ! (multi-active node synchronization tag), which indicates that the request has been processed by another node. When the processing module processes a request ending with ! ! ! , it knows that the request was synchronized from another Redis multi-active node.

[0218] In specific implementation, requests processed by the command processing module will be saved in the replication backlog buffer, and all slave nodes and multi-active nodes use the same synchronization data.

[0219] In addition, Redis (for example, the first primary cache service node) maintains an output buffer structure (Peer output buffer) for each multi-active node, which is used to record the optId that has been sent to the multi-active node and the optId that the multi-active node has confirmed to apply. Only requests processed for the first time by this node are synchronized to the multi-active node.

[0220] Redis also maintains an output buffer structure (Slave output buffer) for each slave node (for example, the first slave cache service node) to record the offset that has been sent to the slave node and the offset that the slave node has confirmed to apply (based on the offset of optId).

[0221] Specifically, the replication backlog buffer can be a linked list of buffer blocks. Each buffer block is configured according to the following parameters: capacity is 1Mb, representing a 1Mb data shard; initialOffset records the initial offset; length records the length of valid data; and cmds is a hash table that records the offset and length of each command processed by this node in the buffer.

[0222] In this scenario, the synchronization architecture described above can be used to synchronize data between different nodes. This includes the following: the Redis master node synchronizes data with the slave node and the corresponding multi-active node in real time; synchronized data is cached only in the backlog buffer; all data in the backlog buffer is synchronized to each slave node; and only requests processed by the node in the backlog buffer are synchronized to each multi-active node. These requests are marked in a hash table (cmds) in each cache block.

[0223] During specific implementation, different synchronization types such as the standby node synchronization request processing flow (corresponding to local slave node synchronization) and the multi-active node synchronization request processing flow (corresponding to remote multi-active synchronization) can be distinguished for specific synchronization processing.

[0224] For the standby node synchronization request processing process, please refer to Figure 13 As shown, the following processing contents may be included:

[0225] S1: This process is triggered when the standby node connects to the master node. The parameters carried are the master node identifier (serverId) to be synchronized and the offset (offset) that has been copied.

[0226] S2: When the serverId matches the local node identifier and the requested offset is in the replication backlog buffer, incremental synchronization is performed: the portion of the replication backlog buffer that is greater than the offset is sent to the standby node.

[0227] S3: Otherwise, a full synchronization process is performed with the standby node, including: S3-1, creating a child process to generate a dump.rdb file of the entire database and sending it to the standby node; S3-2, waiting for the standby node to load the rdb file; S3-3, sending the newly processed request during the full synchronization process.

[0228] For the multi-active node synchronization request processing process, please refer to Figure 14 As shown, the following processing contents may be included:

[0229] S1: This process is triggered when a multi-active node connects to a master node, and the parameters carried include: (1) serverId, the identifier of the master node to be synchronized (the node identifier of the first master cache service node at the synchronization target end); (2) optId, the offset that has been copied from the node (the business processing identifier of the existing business data associated with the first master cache service node at the synchronization target end); (3) pServerId, the identifier of the multi-active node (the node identifier of the second master cache service node at the synchronization initiator end); (4) pOptId, the existing offset in the multi-active node (the business processing identifier of the existing business data associated with the second master cache service node at the synchronization initiator end).

[0230] S2: When serverId matches the identifier of this node and the requested offset is in the replication backlog buffer, incremental synchronization is performed: the data processed by this node that is greater than optId in the replication backlog buffer is sent to the multi-active node.

[0231] S3: Otherwise, a full synchronization process is performed with the multi-active node, including: S3-1, traversing the database in the child process; S3-2, writing the keys greater than optId processed by this node and the keys greater than pOptId from pServerId to the rdb file; S3-3, sending the rdb file and waiting for the multi-active node to be loaded; S3-4, sending the requests processed by this node during the full synchronization process.

[0232] Through the above scenario examples, it is verified that the business data synchronization method based on multi-site active-active provided in this manual can reduce multi-site active-active data synchronization components, simplify operation and maintenance deployment costs, and improve data synchronization efficiency and reliability; it can reduce memory consumption by using the same data through the standby node output buffer, multi-active node output buffer, and backlog buffer; it can integrate the multi-site active-active function into the Redis service for easy deployment and operation and maintenance; it can introduce the node identifier (serverId) when using request processing to avoid circular replication; it can also introduce the logical clock (optId) when processing requests to achieve the function of breakpoint resumption, and there is no need to copy the full amount of user data when fully synchronizing multi-active nodes.

[0233] Although this specification provides the method operation steps as described in the embodiments or flow charts, more or fewer operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the device or client product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiments or the drawings (for example, a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment). The term "comprise", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such process, method, product or device. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or device including the elements. Words such as first and second are used to represent names and do not represent any particular order.

[0234] Those skilled in the art will also appreciate that, in addition to implementing the controller in pure computer-readable program code, it is entirely possible to implement the same functionality by logically programming the method steps in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, embedded microcontrollers, and the like. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered structures within the hardware component. Alternatively, the devices for implementing various functions can be considered both software modules implementing the method and structures within the hardware component.

[0235] This specification may be described in the general context of computer-executable instructions, such as program modules, executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, classes, and the like that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer-readable storage media, including storage devices.

[0236] Through the description of the above embodiments, it can be seen that those skilled in the art can clearly understand that this specification can be implemented by means of software plus the necessary general hardware platform. Based on this understanding, the technical solution of this specification can essentially be embodied in the form of a software product. This computer software product can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a mobile terminal, a server, or a network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments of this specification.

[0237] The various embodiments in this specification are described in a progressive manner. References to the common or similar parts of the various embodiments are sufficient. Each embodiment focuses on the differences from the other embodiments. This specification can be used in a variety of general-purpose or specialized computer system environments or configurations. For example, personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable electronic devices, network PCs, minicomputers, mainframe computers, and distributed computing environments that include any of the above systems or devices.

[0238] Although the present specification has been described with reference to the embodiments, those skilled in the art will appreciate that many modifications and variations can be made to the present specification without departing from the spirit of the present specification. It is intended that the appended claims include such modifications and variations without departing from the spirit of the present specification.

Claims

1. A business data synchronization method based on remote multi-active, characterized in that: The method is applied to a first server node, the first server node being deployed in a data center in a first region and connected to a first primary cache service node and a first secondary cache service node; wherein the first primary cache service node includes at least a replication backlog buffer constructed based on a preset construction rule, a secondary node output buffer corresponding to the first secondary cache service node, and a multi-active input buffer and a multi-active output buffer corresponding to data centers in other regions, the method comprising: Receive and respond to target business data synchronization requests and determine the synchronization type of the business data; According to a preset synchronization rule, when it is determined that the synchronization type of the business data is remote multi-active synchronization, at least the node identifier of the first primary cache service node of the synchronization target end, the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, and the node identifier of the second primary cache service node of the synchronization initiator end are extracted from the target business data synchronization request; wherein the second primary cache service node is deployed in a data center in the second region, and the data center in the second region also has a corresponding second secondary cache service node deployed; Check whether the node identifier of the first primary cache service node of the synchronization target end matches; If it is determined that the node identifier of the first primary cache service node of the synchronization target end matches, detecting whether there is a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer; wherein the replication backlog buffer stores a cache business data group of the current time period obtained by processing based on a preset processing rule; If it is determined that the business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer, target business data to be synchronized to the data center of the second region is determined from the cached business data group of the current time period based on the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end; The target business data is synchronized to the second primary cache service node of the data center of the second region through the multi-active output buffer corresponding to the data center of the second region.

2. The method according to claim 1, characterized in that After detecting whether the node identifier of the first primary cache service node of the synchronization target end matches, the method further includes: If it is determined that the node identifier of the first primary cache service node of the synchronization target end fails to match, a first type full synchronization process is initiated to traverse the first business database, query and obtain business data whose business processing identifier is greater than the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end as the target business data; Writing the target business data into a target relational database file; The target relational database file is synchronized to the second primary cache service node of the data center of the second region through the multi-active output buffer corresponding to the data center of the second region.

3. The method according to claim 1, characterized in that When it is determined that the synchronization type of the service data is remote multi-active synchronization, the method further includes: Detecting whether the target service data synchronization request carries a service processing identifier of existing service data associated with the second primary cache service node of the synchronization initiator; In the case where it is determined that the target business data synchronization request carries the business processing identifier of the existing business data associated with the second primary cache service node of the synchronization initiator, extracting the business processing identifier of the existing business data associated with the second primary cache service node of the synchronization initiator from the target business data synchronization request; Detecting whether there is a business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator in the replication backlog buffer; When it is determined that there is no business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator in the replication backlog buffer, a second type of full synchronization process is started, the first business database is traversed, and business data whose business processing identifier is greater than the business processing identifier of existing business data associated with the second primary cache service node of the synchronization initiator is queried and obtained as the target business data.

4. The method according to claim 1, wherein After determining the synchronization type of the service data, the method further includes: According to the preset synchronization rules, when it is determined that the synchronization type of the business data is local slave node synchronization, the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end are extracted from the target business data synchronization request; Check whether the node identifier of the first primary cache service node of the synchronization target end matches; If it is determined that the node identifier of the first primary cache service node of the synchronization target end matches, detecting whether there is a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end in the replication backlog buffer; When it is determined that the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer, the target business data to be synchronized to the first secondary cache service node is determined from the cached business data group of the current time period according to the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end; The target business data is synchronized to the first slave cache service node through the slave node output buffer corresponding to the first slave cache service node for synchronous backup.

5. The method according to claim 4, characterized in that After detecting whether the node identifier of the first primary cache service node of the synchronization target end matches, the method further includes: If it is determined that the node identifier of the first primary cache service node of the synchronization target end fails to match, a third type of full synchronization process is initiated to traverse the first business database, query and obtain business data whose business processing identifier is greater than the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, as the target business data; Writing the target business data into a target relational database file; The target relational database file is synchronized to the first slave cache service node through the slave node output buffer corresponding to the first slave cache service node for synchronous backup.

6. The method according to claim 1, characterized in that The method further comprises: Obtaining initial service data of data center access in the first region; Determine the data type of the initial business data; Determine an identification parameter for the initial business data according to a preset processing rule and the data type of the initial business data; and mark the initial business data using the identification parameter to obtain marked business data; According to a preset processing rule, the marked business data is stored in the cached business data group of the current time period in the replication backlog buffer in the form of a node command.

7. The method according to claim 6, characterized in that The data types include: a first type and a second type; Among them, the first type is business data that has completed business processing in the data center of the first area; the second type is business data that has completed business processing in data centers in other areas except the data center of the first area.

8. The method according to claim 7, characterized in that Determine the data type of the initial business data, including: Detect whether the initial service data carries the node identifier of the primary cache service node; If it is determined that the initial service data carries the node identifier of the primary cache service node, extracting the node identifier of the primary cache service node; Detecting whether a difference between the node identifier of the primary cache service node and the first primary cache service node identifier is less than or equal to a preset first difference threshold; When it is determined that the difference between the node identifier of the primary cache service node and the first primary cache service node identifier is less than or equal to a preset first difference threshold, the data type of the initial service data is determined to be the first type.

9. The method according to claim 6, characterized in that Determine identification parameters for the initial business data based on preset processing rules and the data type of the initial business data, including: In a case where the data type of the initial service data is the first type, the node identifier of the first primary cache service node is used as the node identifier of the primary cache service node of the initial service data; Query and use the processing number when the initial business data is processed as the business processing identifier of the initial business data; Query and generate a timestamp identifier of the initial business data based on the reception time of the initial business data.

10. The method according to claim 6, characterized in that Determining identification parameters for the initial business data based on preset processing rules and the data type of the initial business data also includes: When the data type of the initial service data is the second type, retaining the node identifier of the primary cache service node and the service processing identifier carried by the initial service data; Query and generate a timestamp identifier of the initial business data based on the reception time of the initial business data; Generate a multi-active node synchronization tag for the initial business data.

11. The method according to claim 9, characterized in that After storing the marked service data in the form of a node command into the cached service data group of the current time period of the replication backlog buffer, the method further includes: In the hash table of the replication backlog buffer, the identification parameter associated with the business data after the mark is updated.

12. A business data synchronization device based on remote multi-active, characterized in that: Applied to a first server node, the first server node is deployed in a data center in a first region and is connected to a first primary cache service node and a first secondary cache service node; wherein the first primary cache service node includes at least a replication backlog buffer constructed based on a preset construction rule, a secondary node output buffer corresponding to the first secondary cache service node, and a multi-active input buffer and a multi-active output buffer corresponding to data centers in other regions, including: A classification module is used to receive and respond to target business data synchronization requests and determine the synchronization type of the business data; an extraction module configured to extract, based on a preset synchronization rule and when determining that the synchronization type of the business data is remote multi-active synchronization, at least the node identifier of a first primary cache service node of a synchronization target end, a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end, and the node identifier of a second primary cache service node of a synchronization initiator end from a target business data synchronization request; wherein the second primary cache service node is deployed in a data center in a second region, and a corresponding second secondary cache service node is also deployed in the data center in the second region; A first detection module is used to detect whether the node identifier of the first primary cache service node of the synchronization target end matches; A second detection module is configured to detect whether, upon determining that a node identifier of the first primary cache service node of the synchronization target end matches, whether a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer; wherein the replication backlog buffer stores a cached business data group of the current time period obtained by processing based on a preset processing rule; a determination module configured to, upon determining that a business processing identifier of existing business data associated with the first primary cache service node of the synchronization target end exists in the replication backlog buffer, determine, based on the node identifier of the first primary cache service node of the synchronization target end and the business processing identifier of the existing business data associated with the first primary cache service node of the synchronization target end, target business data to be synchronized to the data center of the second region from the cached business data group in the current time period; A synchronization module is used to synchronize the target business data to the second primary cache service node of the data center of the second area through the multi-active output buffer corresponding to the data center of the second area.

13. A server, characterized in that: The method comprises a processor and a memory for storing processor-executable instructions, wherein the processor implements the steps of the method according to any one of claims 1 to 11 when executing the instructions.

14. A computer-readable storage medium, characterized in that Computer instructions are stored thereon, and when the instructions are executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.

15. A computer program product, characterized in that The invention comprises a computer program, which implements the steps of the method according to any one of claims 1 to 11 when the computer program is executed by a processor.

Images