CN111124696A

CN111124696A - Unit group creation method, unit group creation device, unit group data synchronization method, unit group data synchronization device, unit and storage medium

Info

Publication number: CN111124696A
Application number: CN201911399019.7A
Authority: CN
Inventors: 李康
Original assignee: Beijing Sankuai Online Technology Co Ltd
Current assignee: Beijing Sankuai Online Technology Co Ltd
Priority date: 2019-12-30
Filing date: 2019-12-30
Publication date: 2020-05-08
Anticipated expiration: 2039-12-30
Also published as: CN111124696B

Abstract

The application provides a unit group creation method, a unit group creation device, a data synchronization method, a data synchronization device, a unit and a storage medium, and belongs to the technical field of computers. Any unit in the newly-built unit group receives and stores the service data of the target service type by establishing a first data synchronization relationship with the target unit group, and releases the first data synchronization relationship with the target unit group according to the service switching instruction. And when receiving the service request of the target service type, processing the service request, and synchronizing the obtained service data to other units in the newly-built unit group. Therefore, the newly-built unit group and the target unit group establish a backup relationship, the target unit group can synchronize the service data of the target service type to the newly-built unit group, and the newly-built unit group can process the service request of the target service type, so that the problem of resource bottleneck of the target unit group is solved.

Description

Unit group creation method, unit group creation device, unit group data synchronization method, unit group data synchronization device, unit and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a unit and a storage medium for creating a unit group and synchronizing data.

Background

In the field of computer technology, users generate a large amount of data when using a network, and the data is distributed to units capable of completing all business operations for processing. If a major disaster occurs in a region where the unit is deployed, such as a large-scale power failure, an earthquake, a fire, etc., the unit may not work, and thus data cannot be processed, and further, a service cannot be normally performed.

In the related art, in order to avoid the above situation, a technician usually constructs a multi-site architecture, that is, deploys units in different regions, and the units in different regions respectively process data and keep data synchronization with each other to form a unit group. Therefore, when a unit deployed in one area cannot work due to a serious disaster, the unit deployed in the other area can timely bear the load, continue to process data and ensure normal operation of the service.

When the data amount to be processed by the cell group is greater than the processing capacity of the cell group, the cell group faces the problem of resource bottleneck, which affects the normal operation of the service. In the related art, there is no method for effectively solving the problem of resource bottleneck. Therefore, a method for solving the problem of resource bottleneck is needed.

Disclosure of Invention

In view of this, embodiments of the present application provide a method, an apparatus, a unit and a storage medium for creating a unit group and synchronizing data, which can solve a resource bottleneck problem of the unit group when a service is normally performed. The technical scheme is as follows:

in one aspect, an embodiment of the present application provides a cell group creating method, which is applied to any cell of a newly-created cell group, where the method includes:

according to the service distribution condition, establishing a first data synchronization relationship with a target unit group, wherein a plurality of units in each unit group are used for performing remote backup, the first data synchronization relationship is used for indicating that service data of a target service type are mutually synchronized between the newly-established unit group and the target unit group, and the service types processed by the target unit group at least comprise the target service type;

receiving and storing the service data of the target service type;

according to a service switching instruction, the first data synchronization relation is released with the target unit group;

and when receiving the service request of the target service type, processing the service request to obtain service data, and synchronizing the processed service data to other units in the newly-built unit group.

Optionally, the releasing the first data synchronization relationship with the target unit group according to the service switching instruction includes:

when the service data in the newly-built unit group and the target unit group are synchronously completed, receiving a service switching instruction;

executing the step of releasing the first data synchronization relationship with the target unit group.

Optionally, when the service data in the new unit group and the service data in the target unit group are completed synchronously, receiving a service switching instruction includes:

checking the service data of the target service type stored by the newly-built unit group and the target unit group;

and receiving a service switching instruction when the service data of the target service type stored by the newly-built unit group and the target unit group are the same.

Optionally, the service data of the target service type includes stock data and incremental data, the stock data is data of the target service type stored by the target unit group before the first data synchronization relationship is established, and the incremental data is data of the target service type stored by the target unit group after the first data synchronization relationship is established.

Optionally, before establishing the first data synchronization relationship with the target unit group according to the service allocation condition, the method further includes:

establishing connection with other units in the newly-built unit group;

and establishing a second data synchronization relationship with the other units according to the service distribution condition, wherein the second data synchronization relationship is used for indicating the units in the newly-established unit group to synchronize the service data responsible by the units to the other units.

Optionally, before the first data synchronization relationship is released from the target unit group according to the service switching instruction, the method further includes:

when the service distribution condition is updated and the updated service distribution condition indicates that the newly-built unit group is responsible for the target service type, if the service request of the target service type is received, the service request is processed to obtain service data, and the processed service data is synchronized to other units in the newly-built unit group and the target unit group.

Optionally, the target service type includes multiple sub-service types, and each unit in the newly-built unit group is used for being responsible for a service of one sub-service type;

when receiving the service request of the target service type, processing the service request to obtain service data, and synchronizing the processed service data to other units in the newly-built unit group, including:

when a service request of a first sub-service type is received, processing the service request to obtain first service data, and synchronizing the first service data to other units in the newly-built unit group;

the method further comprises the following steps:

and receiving and storing second service data of a second sub-service type synchronized by other units in the newly-built unit group.

Optionally, the target unit group includes a first unit and a second unit, where the first unit is a unit responsible for the target service type, and the second unit is a unit other than the first unit;

the receiving and storing the service data of the target service type includes:

and receiving and storing the service data of the target service type sent by the first unit.

Optionally, the establishing a first data synchronization relationship with the target unit group according to the service allocation condition includes:

sending a subscription request to the target unit group according to the service distribution condition, wherein the subscription request is used for subscribing the data of the target service type;

and receiving a subscription success response.

Optionally, the method further includes:

after each step of the unit set creating method, performing pressure test or fault drilling on the newly-built unit set to obtain the work acceptance condition of the newly-built unit set;

and when the work acceptance condition indicates that the work condition of the newly-built unit group is normal, executing the next step after the current step.

On the other hand, an embodiment of the present application provides a data synchronization method, which is applied to a target unit group, and the method includes:

establishing a first data synchronization relationship with a new unit group, wherein a plurality of units included in each unit group are used for performing remote backup, the first data synchronization relationship is used for indicating that service data of a target service type are mutually synchronized between the new unit group and the target unit group, and the service types processed by the target unit group at least comprise the target service type;

sending the service data of the target service type to the newly-built unit group;

and according to the service switching instruction, the first data synchronization relation is released with the newly-built unit group.

and executing the step of releasing the first data synchronization relation with the new unit group.

Optionally, the service data of the target service type includes stock data and incremental data, the stock data is data of the target service type stored by the target unit group before the first data synchronization relationship is established, and the incremental data is data of the target service type stored by the target unit group after the first data synchronization relationship is established;

the sending the service data of the target service type to the newly-built unit group includes:

extracting service data of a target service type from the stored service data;

when a service request of a target service type is received, processing the service request to obtain service data;

and storing the service data and sending the service data to the newly-built unit group.

Optionally, before the removing the first data synchronization relationship with the newly-built cell group according to the service switching instruction, the method further includes:

and receiving the service data of the target service type sent by the newly-built unit group, wherein the service data is updated according to the service distribution condition, and when the updated service distribution condition indicates that the newly-built unit group is responsible for the target service type, the newly-built unit group processes the received service request of the target service type to obtain the service request.

receiving a subscription request, wherein the subscription request is sent by the newly-built unit group according to a service distribution condition, and the subscription request is used for subscribing the data of the target service type;

and sending a subscription success response to the new unit group.

Optionally, the method further includes:

after each step of the data synchronization method, performing pressure test or fault drilling on the newly-built unit group to obtain the work acceptance condition of the newly-built unit group;

On the other hand, an embodiment of the present application provides a unit group creation apparatus, which is applied to any unit of a newly created unit group, where the apparatus includes:

the system comprises a building module, a service configuration module and a service configuration module, wherein the building module is used for building a first data synchronization relationship with a target unit group according to service distribution conditions, a plurality of units in each unit group are used for performing remote backup, the first data synchronization relationship is used for indicating that service data of a target service type are mutually synchronized between a newly built unit group and the target unit group, and the service types processed by the target unit group at least comprise the target service type;

the storage module is used for receiving and storing the service data of the target service type;

the release module is used for releasing the first data synchronization relation with the target unit group according to a service switching instruction;

and the processing module is used for processing the service request to obtain service data when receiving the service request of the target service type, and synchronizing the service data obtained after processing to other units in the newly-built unit group.

Optionally, the release module is specifically configured to receive a service switching instruction when service data in the newly-built cell group and the target cell group are synchronized;

Optionally, the apparatus further comprises:

the verification module is used for verifying the service data of the target service type stored by the newly-built unit group and the target unit group;

and the release module is further configured to receive a service switching instruction when the service data of the target service type stored in the newly-built unit group and the service data of the target service type stored in the target unit group are the same.

Optionally, the establishing module is further configured to establish a second data synchronization relationship with the other units according to a service allocation condition, where the second data synchronization relationship is used to instruct the unit in the newly-established unit group to synchronize service data in charge of the unit with the other units.

Optionally, the processing module is further configured to, when the service allocation condition is updated and the updated service allocation condition indicates that the newly-built unit group is responsible for the target service type, if a service request of the target service type is received, process the service request to obtain service data, and synchronize the service data obtained after processing to other units in the newly-built unit group and the target unit group.

the processing module is specifically configured to, when receiving a service request of a first sub-service type, process the service request to obtain first service data, and synchronize the first service data to other units in the newly-built unit group;

the storage module is further configured to receive and store second service data of a second sub-service type synchronized by other units in the newly-built unit group.

the storage module is specifically configured to receive and store the service data of the target service type sent by the first unit.

On the other hand, an embodiment of the present application provides a data synchronization apparatus, which is applied to a target cell group, and the apparatus includes:

the establishing module is used for establishing a first data synchronization relationship with the newly-built unit group, a plurality of units included in each unit group are used for performing remote backup, the first data synchronization relationship is used for indicating that service data of a target service type are mutually synchronized between the newly-built unit group and the target unit group, and the service types processed by the target unit group at least comprise the target service type;

the processing module is used for sending the service data of the target service type to the newly-built unit group;

the storage module is used for storing the service data;

and the releasing module is used for releasing the first data synchronization relation with the newly-built unit group according to the service switching instruction.

Optionally, the apparatus further comprises:

Optionally, the processing module is specifically configured to extract service data of a target service type from the stored service data;

the storage module is further used for storing the service data;

and the processing module is further configured to send the service data to the newly-built cell group.

Optionally, the storage module is further configured to receive service data of the target service type sent by the newly-built unit group, where the service data is updated according to a service allocation condition, and when the updated service allocation condition indicates that the newly-built unit group is responsible for the target service type, the newly-built unit group processes the received service request of the target service type.

Optionally, the establishing module is specifically configured to receive a subscription request, where the subscription request is sent by the new creating unit group according to a service allocation condition, and the subscription request is used to subscribe to data of the target service type;

and sending a subscription success response to the new unit group.

Optionally, the apparatus further comprises:

the acceptance module is used for carrying out pressure test or fault drilling on the newly-built unit group after each step of the data synchronization method to obtain the work acceptance condition of the newly-built unit group;

In one aspect, a unit is provided that includes one or more processors and one or more memories having stored therein at least one instruction that is loaded and executed by the one or more processors to perform an operation performed by the unit group creation method; or operations that the instructions are loaded and executed by the one or more processors to implement the data synchronization method.

In one aspect, a computer-readable storage medium having at least one instruction stored therein, the instruction being loaded and executed by a processor to implement operations performed by the cell group creation method; or operations that the instructions are loaded and executed by the one or more processors to implement the data synchronization method.

The beneficial effects brought by the technical scheme provided by the embodiment of the application at least can comprise:

in this embodiment of the present application, a first data synchronization relationship is established between any unit of the newly-created unit group and the target unit group, and the target unit group sends service data of the target service type to any unit of the newly-created unit group. And according to the service switching instruction, the first data synchronization relation between the target unit group and any unit of the newly-built unit group is released. Any unit of the newly-built unit group receives and processes the service request of the target service type to obtain service data, and synchronizes to other units in the newly-built unit group. The newly-built unit group and the target unit group establish a backup source relation, and service data synchronization of the target service type can be carried out between the newly-built unit group and the target unit group, so that services responsible by the target unit group can be split. Under the condition that normal operation of the service is not influenced, the newly-built unit group and the target unit group establish a standby source relationship, the condition that service data are lost can be avoided, and then the newly-built unit group can process the service request of the target service type originally processed by the target unit group, so that the problem of resource bottleneck of the target unit group is solved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a flowchart of a method for creating a cell group according to an embodiment of the present application;

fig. 2 is a flowchart of a data synchronization method provided in an embodiment of the present application;

fig. 3 is a flowchart of a method for creating a cell group and synchronizing data according to an embodiment of the present application;

fig. 4 is a schematic diagram illustrating connection between a newly-built cell group and a target cell group according to an embodiment of the present application;

FIG. 5 is a schematic diagram of connection between any cell of a newly created cell group and a target cell group according to an embodiment of the present application;

fig. 6 is a schematic diagram of a newly-built cell group after any cell is disconnected from a target cell group according to an embodiment of the present application;

fig. 7 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 8 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 9 is a schematic diagram of another method for creating a cell group and synchronizing data according to an embodiment of the present application;

fig. 10 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 11 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 12 is a schematic diagram of another method for creating a cell group and synchronizing data according to an embodiment of the present application;

fig. 13 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 14 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 15 is a schematic diagram of another method for creating a cell group and synchronizing data according to an embodiment of the present application;

fig. 16 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 17 is a schematic diagram of another method for creating a cell group and synchronizing data according to an embodiment of the present application;

fig. 18 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 19 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 20 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 21 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 22 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 23 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 24 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 25 is a schematic diagram of another method for creating and synchronizing cell groups according to an embodiment of the present application;

fig. 26 is a schematic structural diagram of a unit group creation apparatus according to an embodiment of the present application;

fig. 27 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present application;

fig. 28 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 29 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

It should be noted that the embodiments described below are some embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In this application, the terms "first," "second," and the like are used for distinguishing between similar items and items having substantially the same function, and it should be understood that "first," "second," and "n" have no logical or temporal dependency, nor are they limited in number or order of execution.

The terms referred to in the present application are explained below.

A unit group: a cell group comprises a plurality of cells, each of which is capable of performing all operations required for a service. The unit is used for receiving and processing the service request of the target service type, obtaining and storing the service data, and synchronizing the service data to other units in the unit group. A plurality of units which are mutually backed up in different places form a unit set. The number of cells included in each cell group may be set by a person skilled in the art according to requirements, for example, the number of cells may be 2 or 5, which is not limited in the embodiment of the present application.

Remote backup: multiple units within a unit group are deployed in different regions, each unit is capable of providing the same service, and data synchronization is maintained among the multiple units. When one unit fails to be available, the units deployed in other areas can take over the unavailable unit to continue processing the service request, so that normal operation of the service is ensured.

Fig. 1 is a flowchart of a method for creating a cell group according to an embodiment of the present application, and is applied to any cell of a newly-created cell group. Referring to fig. 1, the method includes:

101. according to the service distribution condition, a first data synchronization relationship is established with a target unit group, a plurality of units included in each unit group are used for carrying out remote backup, the first data synchronization relationship is used for indicating that service data of a target service type are mutually synchronized between the newly-established unit group and the target unit group, and the service types processed by the target unit group at least comprise the target service type.

102. And receiving and storing the service data of the target service type.

103. And according to the service switching instruction, the first data synchronization relation is released with the target unit group.

104. And when receiving the service request of the target service type, processing the service request to obtain service data, and synchronizing the processed service data to other units in the newly-built unit group.

and executing the step of releasing the first data synchronization relationship with the target unit group.

Optionally, when the service data in the newly-built unit group and the service data in the target unit group are synchronized, receiving a service switching instruction, where the receiving includes:

establishing connection with other units in the newly-built unit group;

Optionally, the target service type includes a plurality of sub-service types, and each unit in the newly-built unit group is used for being responsible for a service of one sub-service type;

the method further comprises the following steps:

and receiving and storing second service data of the second sub-service type synchronized by other units in the newly-built unit group.

the receiving and storing the service data of the target service type includes:

receiving a subscription request, wherein the subscription request is sent by the newly-built unit group according to the service distribution condition, and the subscription request is used for subscribing the data of the target service type;

and sending a subscription success response to the newly-built unit group.

Optionally, the method further includes:

after each step of the unit set establishing method, carrying out pressure test or fault drilling on the newly-built unit set to obtain the work acceptance condition of the newly-built unit set;

The embodiment of the application provides a unit group creation method, which receives and stores service data of a target service type by establishing a first data synchronization relationship with a target unit group, and removes the first data synchronization relationship with the target unit group according to a service switching instruction. And when receiving the service request of the target service type, processing the service request, and synchronizing the obtained service data to other units in the newly-built unit group. Therefore, under the condition of not influencing the normal operation of the service, the newly-built unit group and the target unit group can establish a backup relationship, and the newly-built unit group can receive the service data of the target service type sent by the target unit group, thereby avoiding the occurrence of the condition of service data loss. Furthermore, the newly-built unit group can process the service request of the target service type originally processed by the target unit group, and the problem of resource bottleneck of the target unit group is solved.

Fig. 2 is a diagram of a data synchronization method applied to a target cell group according to an embodiment of the present application. Referring to fig. 2, the method includes:

201. establishing a first data synchronization relationship with the newly-built unit group, wherein a plurality of units in each unit group are used for performing remote backup, the first data synchronization relationship is used for indicating that service data of a target service type are mutually synchronized between the newly-built unit group and the target unit group, and the service types processed by the target unit group at least comprise the target service type;

202. sending the service data of the target service type to the newly-built unit group;

203. and according to the service switching instruction, the first data synchronization relation is released with the newly-built unit group.

extracting service data of a target service type from the stored service data;

Optionally, before the first data synchronization relationship is released from the newly-built cell group according to the service switching instruction, the method further includes:

and sending a subscription success response to the newly-built unit group.

Optionally, the method further includes:

The embodiment of the application provides a data synchronization method, which is characterized in that a first data synchronization relationship is established with a newly-built unit group, service data of a target service type is sent to the newly-built unit group, and the first data synchronization relationship is released with the newly-built unit group according to a service switching instruction. Therefore, under the condition of not influencing the normal operation of the service, the backup relation is established between the target unit group and the newly-built unit group, the target unit group can send the service data of the target service type to the newly-built unit group, and the condition of service data loss is avoided. Furthermore, the newly-built unit group can process the service request of the target service type originally processed by the target unit group, and the problem of resource bottleneck of the target unit group is solved.

The embodiments of fig. 1 and fig. 2 describe the specific flows of the cell group creation method and the data synchronization method from the single side of the newly-built cell group and the target cell group, respectively, and the specific flows of the methods are described below from the perspective of information interaction between the newly-built cell group and the target cell group through the embodiment shown in fig. 3. Fig. 3 is a flowchart of a method for creating a cell group and synchronizing data according to an embodiment of the present application. Referring to fig. 3, the method includes:

301. and establishing a first data synchronization relationship between any unit of the newly-built unit group and the target unit group according to the service distribution condition.

In this embodiment of the present application, a new cell group may be created, the new cell group shares part of the service processing services with an original cell group, and a plurality of cells included in each cell group are used for performing remote backup, so that a cell in a certain area fails, and a service in charge of the cell may be transferred to other cells in the cell group. The newly-built unit group can establish a data synchronization relationship with an original unit group needing service splitting, and synchronize part of service data subsequently required to be responsible by the newly-built unit group to the newly-built unit group, so that after the subsequent service splitting is completed, the newly-built unit group can be responsible for the part of service processing services, and the original unit group can process services except the part of service processing services.

Therefore, in the process of creating the new unit group, a first data synchronization relationship needs to be established with the target unit group to perform data synchronization, and the service types processed by the target unit group at least include the service types to be processed subsequently by the new unit group. The service type to be processed subsequently by the newly created cell group is referred to as a target service type hereinafter. That is, the first data synchronization relationship is used to indicate that the service data of the target service type is synchronized between the new set of units and the target set of units, and the service types processed by the target set of units at least include the target service type.

The traffic allocation is used to indicate the type of traffic handled by each element in the respective group of elements. The service type may be divided according to a certain rule, for example, the service type may be divided according to a region, or may be divided according to a service domain, which is not limited in the embodiment of the present application.

When the new unit group is created, the new unit group can obtain the service distribution condition, and according to the service distribution condition, the target unit group is determined from the plurality of unit groups. Specifically, the newly created cell group determines the cell group responsible for the target service type in the service allocation case as the target cell group. The target cell group may be one cell group or a plurality of cell groups. If there is only one set of cells responsible for the target traffic type, the target set of cells is one set of cells. If one of the plurality of cell groups is responsible for a portion of the target service type and the other cell groups are responsible for another portion of the target service type, then the target cell group is a plurality of cell groups.

When the target unit group is a plurality of unit groups, any unit of the newly-built unit group can establish a first data synchronization relationship with only one target unit group, each unit of the newly-built unit group can establish a first data synchronization relationship with each unit group in the target unit group, each unit group respectively synchronizes a part of the service data of the target service type to the newly-built unit group, and the newly-built unit group receives the service data sent by the plurality of unit groups, so that the service data of the target service type can be obtained.

For example, as shown in fig. 4, taking an original cell group as two cell groups, a target cell group as one cell group, each cell group including two cells as an example, the target cell group includes a first cell and a second cell, another cell group in the original cell group includes a third cell and a fourth cell, and a new cell group may include a fifth cell and a sixth cell. And numbering the service requests according to the last three digits of the sending addresses of the service requests to obtain 1000 types of the service requests of 000-999. The service distribution condition indicates that a target unit group is responsible for processing service requests of 000-499 types, a unit group consisting of a third unit and a fourth unit is responsible for processing service requests of 500-999 types, a newly-built unit group is responsible for processing service requests of 000-199 types, and the 000-199 types are target service types. And the newly-built unit group establishes a first data synchronization relation with a target unit group which is responsible for processing the service types and comprises the target service types according to the service distribution condition. The first data synchronization relationship is used for indicating that the service data of 0-199 types are mutually synchronized between the newly-built unit group and the target unit group.

In a possible implementation manner, the first data synchronization relationship may be a subscription relationship, and any unit of the newly-built unit group may subscribe to the service data of the target service type from the target unit group. Specifically, any unit of the new unit group sends a subscription request to the target unit group, the target unit group receives the subscription request and sends a subscription success response to any unit of the new unit group, any unit of the new unit group correspondingly receives the subscription success response, and the first data synchronization relationship is successfully established.

Through the subscription relationship, the newly-built unit group can automatically determine the target unit group and establish a first data synchronization relationship for synchronizing the service data of the target service type with the target unit group.

In one possible implementation manner, the new created unit group may be created before any unit of the new created unit group establishes the first data synchronization relationship with the target unit group according to the service allocation condition. The creating process of the new unit group may be: any unit of the newly-built unit group can establish connection with other units in the newly-built unit group, and establish a second data synchronization relationship with other units according to the service distribution condition. The second data synchronization relationship is used for indicating the unit in the newly-built unit group to synchronize the service data obtained by the unit to other units.

Through the second data synchronization relationship, any unit of the newly-built unit group automatically forms a backup relationship with other units to form the newly-built unit group, and then the units in the newly-built unit group can automatically synchronize the service data obtained by the units to other units, so that the automation of establishing a data synchronization relationship between any unit of the newly-built unit group and other units and synchronizing the service data is realized, the labor cost is saved, and the efficiency is improved.

Before any unit of the newly-built unit group establishes a second data synchronization relationship with other units, any unit of the newly-built unit group applies for various resources of each service in the unit. Specifically, any unit of the newly-built unit group requests a corresponding server for a corresponding resource according to the target service type of the service processing service.

For example, the service processing service for which any unit of the newly-built unit group is responsible includes an application service, and accordingly, any unit of the newly-built unit group requests a corresponding resource from the application server to deploy the application service and configure a corresponding dependency. The service processing service may further include a data service, a cache service, and a message queue service, and any unit of the newly-built unit group may request a corresponding resource from a corresponding data server, a corresponding cache server, and a corresponding message queue server, which is not limited in this embodiment of the present application.

302. And the target unit group sends the service data of the target service type to the newly-built unit group according to the first data synchronization relation.

303. Any unit of the newly-built unit group receives and stores the service data of the target service type.

After the first data synchronization relationship is established between the target unit group and the new unit group, the target unit group can send the stored service data of the target service type to any unit of the new unit group, and any unit of the new unit group can receive and store the service data of the target service type.

In one possible implementation, the target unit group includes a plurality of units, and the types of services handled by the respective units are different. The target unit group comprises a first unit and a second unit, wherein the first unit is a unit responsible for the target service type, and the second unit is a unit except the first unit. The number of the first unit and the second unit may be one or more.

Specifically, when the number of the first units is one, any unit of the newly-built unit group may establish a first data synchronization relationship with the first unit, and when the number of the first units is multiple, any unit of the newly-built unit group may respectively establish a first data synchronization relationship with each first unit.

For example: the target unit group can include two first units, which are respectively responsible for service data of 0-249 and 250-499, and if the target service type is 200-399, any unit of the newly-built unit group can respectively establish a first data synchronization relationship with the two first units in the target unit group. The unit responsible for the service data of 0-249 type sends the service data of 200-249 type to any unit of the newly-built unit group, the unit responsible for the service data of 250-499 type sends the service data of 250-399 type to any unit of the newly-built unit group, and any unit of the newly-built unit group receives and stores part of the service data of the target service type sent by the two first units respectively, so that the service data synchronization is realized.

Any unit of the newly-built unit group can also establish a first data synchronization relationship with the first unit and the second unit respectively, so that any unit of the newly-built unit group, the first unit and the second unit are mutually redundant. Any unit of the newly-built unit group can be used as a backup of the target unit group, and receives and stores the service data sent by the target unit group. If the first unit is in disaster when sending the service data of the target service type to any unit of the newly-built unit group, the second unit can continue to send the service data of the target service type to any unit of the newly-built unit group because the second unit also stores the service data of the target service type.

Any unit, the first unit and the second unit of the newly-built unit group are mutually backed up by establishing a first data synchronization relationship between the any unit of the newly-built unit group and the first unit and the second unit respectively. The method can ensure that the disaster tolerance capability of the target unit group is not damaged in the process of synchronizing the service data of the target unit group and the newly-built unit group, and any unit of the newly-built unit group can also be used as a backup, thereby improving the disaster tolerance capability.

For example, as shown in fig. 5, taking the target unit group including a first unit and a second unit as an example, the first unit may be responsible for processing service requests of types 0 to 249, the second unit may be responsible for processing service requests of types 250 to 499, and a service data synchronization relationship of types 0 to 499 is established between the first unit and the second unit. The target service type is 0-199 type, a fifth unit of the newly-built unit group establishes a first data synchronization relationship with the first unit and the second unit respectively, the first unit sends the service data of 0-199 type to the fifth unit of the newly-built unit group, and the fifth unit of the newly-built unit group receives and stores the service data of 0-199 type sent by the first unit.

In a possible implementation manner, the target unit group includes a first unit and a second unit, the first unit is a unit responsible for the target service type, the second unit is a unit other than the first unit, and any unit of the newly-built unit group receives and stores the service data of the target service type sent by the first unit. Specifically, when a first data synchronization relationship is established between any one of the units of the newly-built unit group and only the first unit or between the any one of the units of the newly-built unit group and the first unit and the second unit, respectively, only the first unit can send the service data of the target service type to any one of the units of the newly-built unit group.

For example, any unit of the new unit group establishes a first data synchronization relationship with the first unit and the second unit of the target unit group, and any unit of the new unit group, the first unit and the second unit are redundant to each other. The first unit can send the service data of the target service type to the second unit and any unit of the newly-built unit group, but any unit of the newly-built unit group and the second unit can not send the received service data of the target service type out again.

Through the arrangement, in the process of creating the unit group and synchronizing the data, the second unit cannot send the received service data of the target service type to the first unit of the newly-created unit group according to the first data synchronization relationship, so that the situations that the same data is repeatedly synchronized to cause data redundancy, even data errors, or wireless data loop replication can be avoided.

It should be noted that, when the first unit is damaged and cannot be used, the second unit can send the stored service data of the target service type to any unit of the newly-built unit group, so as to ensure normal operation of service data synchronization.

In a possible implementation manner, during the process of performing service data synchronization, the target unit group may continuously receive the service request, process the service request, and obtain the service data, so that the service data of the target service type includes stock data and incremental data, the stock data is data of the target service type stored by the target unit group before the first data synchronization relationship is established, and the incremental data is data of the target service type stored by the target unit group after the first data synchronization relationship is established.

Correspondingly, for the stock data, the target unit group can extract the service data of the target service type from the stored service data and send the service data to any unit of the newly-built unit group; and for the incremental data, the target unit receives and processes the service request of the target service type to obtain the service data of the target service type, and stores and sends the obtained service data of the target service type to any unit of the newly-built unit group.

In the process of synchronizing the business data, the target unit group continuously receives the business request, divides the business data of the target type into the incremental data and the stock data, and adopts different synchronization modes for the incremental data and the stock data, so that the business data can be synchronized under the condition that the business is normally performed, and the resource bottleneck problem of the target unit group is effectively solved.

In some possible embodiments, when the service allocation situation is updated and the updated service allocation situation indicates that the newly-built cell group is responsible for the target service type, if any cell of the newly-built cell group receives a service request of the target service type, the service request is processed to obtain and store service data of the target service type. And any unit of the newly-built unit group synchronizes the obtained service data to other units and the target unit group in the newly-built unit group. And the target unit group receives the service data of the target service type sent by the new unit group.

The service distribution condition is updated to indicate any unit of the newly-built unit group to be responsible for processing the service request of the target service type, and correspondingly, the target unit group does not receive the service request of the target service type any more. The service distribution situation can be updated by the access layer located at the upper layer of the newly-built unit group and the target unit group.

Specifically, before the service allocation condition is updated, the target unit group receives and processes the service request of the target service type to obtain and store the service data of the target service type, synchronizes the service data of the target service type to the new unit group according to the first data synchronization relationship, after the service allocation condition is updated, the new unit group receives and processes the service request of the target service type to obtain and store the service data of the target service type, and synchronizes the service data of the target service type to the target unit group according to the first data synchronization relationship, and the target unit group does not receive the service request of the target service type any more.

Through the updating of the service distribution condition, any unit of the newly-built unit group starts to receive and process the service request of the target service type, correspondingly, the target unit group does not receive the service request of the target service type any more, the unified updating of the service distribution is realized, compared with the manual configuration of the target unit group and the newly-built unit group by technicians, the operation steps are simplified, and the working efficiency is improved.

In a possible implementation manner, when any unit of the newly-built unit group receives the service request of the first sub-service type, the service request may be processed to obtain first service data of the first sub-service type. Any unit of the newly-built unit group can send the obtained first service data of the first sub-service type to other units in the newly-built unit group and receive second service data of the second sub-service type sent by other units in the newly-built unit group.

The target service type comprises a plurality of sub-service types, the newly-built unit group comprises a plurality of units, and each unit is used for processing a service request of one sub-service type.

For example, the newly-built unit group may include a fifth unit and a sixth unit, the first sub-service type may be a type of 0 to 99, and the second sub-service type may be a type of 100 to 199. The fifth unit is used for processing the service requests of types 0-99, and the sixth unit is used for processing the service requests of types 100-199. The fifth unit obtains the service data of 0-99 types and sends the service data to the sixth unit, and the sixth unit obtains the service data of 100-199 types and sends the service data to the fifth unit. And a synchronization relation of 0-199 types of service data exists between the fifth unit and the sixth unit.

Through the data replication relationship established among the units in the newly-built unit group, the plurality of units in the newly-built unit group respectively process a part of service requests of the target service type, the plurality of units are mutually backup in different places, when one unit in the newly-built unit group is unavailable due to disaster, other units in the newly-built unit group can take over the disaster-suffered unit, the service requests are continuously processed, and the normal operation of the service is ensured.

304. And removing the first data synchronization relation between any unit of the newly-built unit group and the target unit group according to the service switching instruction.

The service switching instruction is used for indicating that the first data synchronization relation between any unit of the newly-built unit group and the target unit group is released.

Specifically, any unit of the newly-built unit group may send a unsubscribe request to the target unit group, the target unit group receives the unsubscribe request, and sends a unsubscribe success response to any unit of the newly-built unit group, and any unit of the newly-built unit group correspondingly receives the unsubscribe success response, and the first data synchronization relationship is successfully unsubscribed.

In a possible implementation manner, when the service data synchronization in the new set of cells and the target set of cells is completed, the new set of cells and the target set of cells receive the service switching instruction, and the step of releasing the first data synchronization relationship between any cell of the new set of cells and the target set of cells is executed.

Specifically, after the first data synchronization relationship is established between the new cell group and the target cell group, and before the first data synchronization relationship is released, the data is always synchronized between the new cell group and the target cell group. If the service data synchronization between the newly created unit group and the target unit group is completed, it indicates that the newly created unit group stores all the service data of the target service type, and the service allocation condition is updated, and the newly created unit group does not need to acquire the service data of the target unit group any more, and can execute the step of removing the first data synchronization relationship between any unit of the newly created unit group and the target unit group.

By executing the step of releasing the first data synchronization relationship between any unit of the newly-built unit group and the target unit group when the service data synchronization in the newly-built unit group and the target unit group is completed, the step of releasing the first data synchronization relationship is ensured to be executed on the premise that the newly-built unit group already receives all the service data of the target service type stored by the target unit group, and the condition that the service data is lost due to the poor timing of releasing the first data synchronization relationship is avoided.

In a possible implementation manner, the data synchronization can be achieved by checking, specifically, any one of the new set of units checks the service data of the target service type stored in the new set of units and the target set of units, and when the service data of the target service type stored in the new set of units and the target set of units are the same, receives the service switching instruction.

Specifically, after the first data synchronization relationship is established between the new cell group and the target cell group, and before the first data synchronization relationship is released, the data is always synchronized between the new cell group and the target cell group. If the service data of the target service type stored by the new creation unit group and the target unit group are the same, it indicates that the new creation unit group has received all the service data of the target service type stored by the target unit group, and the new creation unit group can also smoothly synchronize the service data of the target service type to the target unit group. At this time, the first data synchronization relationship between any unit of the newly-built unit group and the target unit group is released, and the newly-built unit group can smoothly process the service request of the target service type.

By the method for verifying the service data of the target service type stored by the new unit group and the target unit group, whether the service data of the target service type stored by the new unit group and the target unit group are the same or not is judged, so that the new unit group can be ensured to receive all the service data of the target service type stored by the target unit group, and further the new unit group can be ensured to smoothly process the service request of the target service type.

305. When any unit of the newly-built unit group receives the service request of the target service type, the service request is processed to obtain and store service data, and the service data is synchronized to other units in the newly-built unit group.

The embodiment related to receiving and processing the service request of the target service type after any unit of the newly-built unit group releases the first data synchronization relationship with the target unit group is similar to the above-mentioned embodiment in which the unit in the newly-built unit group receives and processes the service request of the target service type after the service allocation condition is updated, and details are not repeated here.

In a possible implementation manner, after the above steps, a pressure test or a fault drilling is performed on the newly-built unit group to obtain a work acceptance condition of the newly-built unit group, and when the work acceptance condition indicates that the work condition of the newly-built unit group is normal, the next step after the current step is executed.

The pressure test may be to test the capability of the newly-built cell group to process the service request and the synchronization data, and the fault drilling may be to set a certain cell in the newly-built cell group as unavailable to test the working conditions of other cells, or to set the target cell group as unavailable to test the working conditions of the newly-built cell group when the newly-built cell group and the target cell group establish the first data synchronization relationship.

Specifically, when the work acceptance condition indicates that the work condition of the newly-built unit group is normal, the next step after the current step is executed, and when the work acceptance condition indicates that the work condition of the newly-built unit group is abnormal, the next step is not executed, instead, the newly-built unit group is subjected to troubleshooting and a corresponding repairing step, and then, the pressure test or the fault drilling is performed again.

Through carrying out pressure test or fault drilling to newly-built unit group, can in time discover the defect in the newly-built unit group, avoid bigger loss.

In a possible implementation manner, after the target unit group and the newly-created unit group release the first data synchronization relationship, the units in the target unit group release the first data synchronization relationship, and the service data of the target service type is removed.

The service types handled by the target unit group at least include the target service type, and obviously, the type range of data synchronization between units in the target unit group is larger than the target service type. Specifically, the first data synchronization relationship is released between the units in the target unit group, the synchronization relationship of other data is maintained, and the service data of the target service type is cleared.

For example, as shown in fig. 6, between the first unit and the second unit in the target unit group, the data synchronization relationship of types 0 to 199 is released, the data synchronization relationship of types 200 to 499 is reserved, the business data of types 0 to 199 stored in the first unit and the second unit are useless data, and the business data of types 0 to 199 are cleared by the first unit and the second unit.

After the newly-built unit group completely takes over the processing of the service request of the target service type, the data synchronization relationship among the units in the target unit group is corrected, and the service data of the target service type is eliminated, so that the situations that data redundancy exists and the storage space of the target unit group is occupied are avoided.

In a possible implementation, after the unit in the target unit group clears the service data of the target service type, the check sum comparison is performed on the service data stored in each unit of the target unit group.

By checking and comparing the service data stored in each unit of the target unit group, the situation that the service data of other service types are mistakenly cleared together when the unit in the target unit group clears the service data of the target service type, so that the data loss is caused is avoided.

In the embodiment of the application, a first data synchronization relationship is established between any unit of the newly-built unit group and the target unit group, and the target unit group sends the service data of the target service type to any unit of the newly-built unit group. And according to the service switching instruction, the first data synchronization relation between the target unit group and any unit of the newly-built unit group is released. Any unit of the newly-built unit group receives and processes the service request of the target service type to obtain service data, and synchronizes to other units in the newly-built unit group. Therefore, under the condition of not influencing the normal operation of the service, the backup relation is established between the target unit group and the newly-built unit group, the target unit group can synchronize the service data of the target service type to the newly-built unit group, and the condition of service data loss is avoided. Furthermore, the newly-built unit group can process the service request of the target service type originally processed by the target unit group, and the problem of resource bottleneck of the target unit group is solved.

The embodiment shown in fig. 3 describes a specific flow of the cell group creation and data synchronization method from the perspective of information interaction between the newly-built cell group and the target cell group. A specific embodiment is provided below to exemplify a specific flow of the cell group creation and data synchronization method.

"BJ" and "SH" in fig. 7-25 related to the embodiments of the present application may represent two different unit deployment regions, for example, "BJ" may represent beijing, "SH" may represent shanghai, and "SET" may represent one unit. In the embodiment of the present application, an original cell group includes two cell groups, a target cell group is a cell group, each cell group includes two cells as an example, the target cell group includes SET (cell) 1 and SET3, another cell group in the original cell group includes SET2 and SET4, and a new cell group includes SET5 and SET 6. The newly-built unit group is responsible for processing service requests of types 0-199, the target unit group is responsible for processing service requests of types 0-499, another unit group in the original unit group is responsible for processing service requests of types 500-999, wherein the SET1 is responsible for processing service requests of types 0-249, the SET2 is responsible for processing service requests of types 500-749, the SET3 is responsible for processing service requests of types 250-499, the SET4 is responsible for processing service requests of types 750-999, the SET5 is responsible for processing service requests of types 0-99, and the SET6 is responsible for processing service requests of types 100-199.

As shown in FIG. 7, in the initial state, the SET1 is responsible for the type 0-249 services, and as the SET3 is backed up, the type 250-499 service data is duplicated, i.e. it is responsible for the type 0-499 service data storage; the SET3 is responsible for 250-499 type services and is used as a backup for the SET1, service data of 0-249 type is copied, namely responsible for storing the service data of 0-499 type; the SET2 is responsible for 500-749 types of services and is used as a backup of the SET4, service data of 750-999 types are copied, namely, the SET2 is responsible for storing the service data of 500-999 types; the SET4 is responsible for 750-999 types of traffic, and is used as a backup for the SET2, and 500-749 types of service data are copied, namely, the SET4 is responsible for 500-999 types of service data storage.

As shown in FIGS. 8-9, a SET5 and a SET6 are newly created. Specifically, the SET5 and the SET6 respectively request corresponding resources including application services, data services, cache services, message queue services, and the like from corresponding servers according to a specific type of service processing service, deploy services and configure corresponding dependencies, so that the SET5 and the SET6 can be used to receive and process service requests. That is, in the above embodiment, before any cell of the newly-built cell group establishes the second data synchronization relationship with other cells, any cell of the newly-built cell group applies for various resources of each service in the cell.

As shown in FIG. 10, a replication relationship of type 0-199 service data is established between the SET5 and the SET6, so that type 0-199 service data can be synchronized between the SET5 and the SET6, and a newly-created cell group is established. That is, in the above embodiment, any unit of the new unit group establishes a connection with other units in the new unit group, and establishes a second data synchronization relationship with other units according to the service distribution condition.

As shown in fig. 11, after the business data replication relationship of types 0 to 199 is established between the SET5 and the SET6, the new tuple is checked and accepted to ensure that the new tuple is successfully established. That is, in the above embodiment, the new unit set is subjected to a pressure test or a fault drilling, so as to obtain the work acceptance condition of the new unit set, and when the work acceptance condition indicates that the work condition of the new unit set is normal, the next step after the current step is executed.

As shown in fig. 12 to 13, the SET5 establishes a 0-199 type service data replication relationship with the SET1 and the SET3, respectively, the SET1 can send the stored 0-199 type service data to the SET5, and the SET5 satisfies a preparation condition for becoming a 0-199 type triple-backup. As shown in fig. 14 to 15, the SET6 establishes a 0-199 type service data replication relationship with the SET1 and the SET3, respectively, the SET1 can send the stored 0-199 type service data to the SET6, and the SET6 satisfies a preparation condition for being a four-backup of 0-199 type. That is, in the above embodiment, any unit of the new unit group establishes the first data synchronization relationship with the first unit and the second unit of the target unit group, and any unit of the new unit group, the first unit and the second unit are mutually redundant. The steps of establishing the service data replication relationship between the SET5 and the SET6 and the SET1 and the SET3 respectively may be performed step by step or simultaneously, and the embodiments of the present application are not limited thereto.

As shown in fig. 16, the stock data comparison and the incremental data verification are performed. Before establishing the data synchronization relationship with the stock data of 0-199 types, the SET1 stores the data of the target service type, and after establishing the data synchronization relationship with the incremental data of 0-199 types, the SET1 stores the data of the target service type by the target unit group. That is, in the above embodiment, any one of the new unit groups checks the service data of the target service type stored in the new unit group and the target unit group.

As shown in FIGS. 17-18, the SET5 receives type 0-99 service requests, the SET6 receives type 100-199 service requests, and the SET1 no longer receives type 0-199 service requests but begins to receive type 0-99 service data sent by the SET5 and type 100-199 service data sent by the SET 6. That is, in the above embodiment, when the service allocation situation is updated, if any unit of the newly-built unit group receives the service request of the target service type, the service request is processed, and the service data of the target service type is obtained and stored.

As shown in fig. 19, the newly-built cell group is accepted to ensure that the SET5 and the SET6 can smoothly process the service requests of types 0 to 99 and 100 to 199, respectively. That is, in the above embodiment, the new unit set is subjected to a pressure test or a fault drilling to obtain the work acceptance condition of the new unit set, and when the work acceptance condition indicates that the work condition of the new unit set is normal, the next step after the current step is performed.

As shown in FIGS. 20-21, the SET6 releases the 0-199 type service data replication relationship with the SET1 and the SET3, respectively, and the SET1, the SET3 and the SET5 are 0-199 type triple-backup relationships. As shown in FIGS. 22-23, the SET5 releases the 0-199 type traffic data replication relationship with the SET1 and the SET3, respectively, in which case the SET5 and the SET6 are 0-199 type two-backup relationships. That is, in the above embodiment, according to the service switching instruction, any cell of the new cell group and the target cell group release the first data synchronization relationship between any cell of the new cell group and the target cell group. The steps of releasing the service data replication relationship between the SET5 and the SET6 and the SET1 and the SET3 may be performed step by step or simultaneously, and the embodiments of the present application are not limited thereto.

As shown in FIG. 24, the data replication relationship between the SET1 and the SET3 is modified from type 0-499 to type 200-499, and traffic data of type 0-199 is cleared. That is, in the above embodiment, after the target unit group and the newly-created unit group release the first data synchronization relationship, the units in the target unit group release the first data synchronization relationship, and clear the service data of the target service type.

As shown in fig. 25, the SET1 and SET3 were checked and compared for inventory data and accepted. That is, in the above embodiment, after the unit in the target unit group clears the service data of the target service type, the check sum comparison is performed on the service data stored in each unit of the target unit group. At this point, cell group creation and data synchronization is completed.

In a terminal state, the SET1 is responsible for the services of types 200-249, and as a backup of the SET3, 250-499 types of service data are copied, namely, the SET1 is responsible for the storage of 200-499 types of service data; the SET3 is responsible for 250-499 type services and is used as a backup for the SET1, service data of 200-249 type is copied, namely responsible for storage of service data of 200-499 type; the SET2 is responsible for 500-749 types of services and is used as a backup of the SET4, service data of 750-999 types are copied, namely, the SET2 is responsible for storing the service data of 500-999 types; the SET4 is responsible for 750-999 type services and is used as a backup of the SET2, 500-749 type service data is copied, namely, the SET4 is responsible for storing 500-999 type service data; the SET5 is responsible for the type 0-99 services and is used as a backup for the SET6, and 100-199 types of service data are copied, namely, the SET5 is responsible for the storage of the type 0-199 service data; the SET6 is responsible for 100-199 types of services, and as a backup of the SET5, the SET6 duplicates 0-99 types of service data, i.e., is responsible for storage of 0-199 types of service data.

It should be noted that the above embodiments are only optional embodiments of the present application, and are not intended to limit the present application.

Fig. 26 is a schematic structural diagram of a cell group creation apparatus according to an embodiment of the present application, which is applied to any cell of a newly created cell group. Referring to fig. 26, the apparatus includes:

an establishing module 2601, configured to establish a first data synchronization relationship with a target unit group according to a service allocation condition, where multiple units in each unit group are used for performing remote backup, the first data synchronization relationship is used to indicate that service data of a target service type is synchronized between the newly-established unit group and the target unit group, and a service type processed by the target unit group at least includes the target service type;

a storage module 2602, configured to receive and store the service data of the target service type;

a removing module 2603, configured to remove the first data synchronization relationship with the target unit group according to the service switching instruction;

the processing module 2604 is configured to, when receiving the service request of the target service type, process the service request to obtain service data, and synchronize the service data obtained after processing to other units in the newly-built unit group.

Optionally, the releasing module 2603 is specifically configured to receive a service switching instruction when the service data in the newly-created cell group and the service data in the target cell group are synchronized;

Optionally, the apparatus further comprises:

the releasing module 2603 is further configured to receive a service switching instruction when the service data of the target service type stored in the newly-built unit group and the service data of the target service type stored in the target unit group are the same.

Optionally, the establishing module 2601 is further configured to establish a second data synchronization relationship with the other unit according to the service allocation condition, where the second data synchronization relationship is used to instruct the unit in the newly-established unit group to synchronize the service data that is in charge of the unit with the other unit.

Optionally, the processing module 2604 is further configured to, when the service allocation condition is updated and the updated service allocation condition indicates that the newly-built unit group is responsible for the target service type, if a service request of the target service type is received, process the service request to obtain service data, and synchronize the service data obtained after processing to other units in the newly-built unit group and the target unit group.

the processing module 2604 is specifically configured to, when receiving a service request of a first sub-service type, process the service request to obtain first service data, and synchronize the first service data to other units in the newly-created unit group;

the storage module 2602 is further configured to receive and store second service data of the second sub-service type synchronized with other units in the newly created unit group.

the storage module 2602 is specifically configured to receive and store the service data of the target service type sent by the first unit.

The embodiment of the application provides a unit group creation device, which can establish a first data synchronization relationship with a target unit group, receive and store service data of a target service type, and release the first data synchronization relationship with the target unit group according to a service switching instruction. And when receiving the service request of the target service type, processing the service request, and synchronizing the obtained service data to other units in the newly-built unit group. Therefore, under the condition of not influencing the normal operation of the service, the newly-built unit group and the target unit group can establish a backup relationship, and the newly-built unit group can receive the service data of the target service type sent by the target unit group, thereby avoiding the occurrence of the condition of service data loss. Furthermore, the newly-built unit group can process the service request of the target service type originally processed by the target unit group, and the problem of resource bottleneck of the target unit group is solved.

It should be noted that: in the above embodiment, when creating the cell group, the cell group creating apparatus is described by taking the division of the functional modules as an example, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the apparatus is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the embodiment of the unit group creation apparatus and the embodiment of the unit group creation method provided in the above embodiments belong to the same concept, and specific implementation processes thereof are described in detail in the embodiment of the method and are not described herein again.

Fig. 27 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present application, applied to a target cell group. Referring to fig. 27, the apparatus includes:

an establishing module 2701, configured to establish a first data synchronization relationship with a new unit group, where multiple units included in each unit group are used to perform remote backup, the first data synchronization relationship is used to indicate that service data of a target service type are synchronized between the new unit group and the target unit group, and the service type processed by the target unit group at least includes the target service type;

a processing module 2704, configured to send service data of the target service type to the newly-built cell group;

a storage module 2702, configured to store service data;

a releasing module 2703, configured to release the first data synchronization relationship with the newly created cell group according to the service switching instruction.

Optionally, the releasing module 2703 is specifically configured to receive a service switching instruction when the service data in the newly-built cell group and the service data in the target cell group are synchronized;

and executing the step of releasing the first data synchronization relationship with the new unit group.

Optionally, the apparatus further comprises:

the releasing module 2703 is further configured to receive a service switching instruction when the service data of the target service type stored in the newly created cell group and the target cell group are the same.

Optionally, the processing module 2704 is specifically configured to extract service data of a target service type from the stored service data;

the storage module 2702 is further configured to store the service data;

the processing module 2704 is further configured to send the service data to the newly created unit group.

Optionally, the storage module 2702 is further configured to receive service data of the target service type sent by the new set of units, where the service data is updated according to a service allocation condition, and when the updated service allocation condition indicates that the new set of units is responsible for the target service type, the new set of units processes the received service request of the target service type.

Optionally, the establishing module 2701 is specifically configured to receive a subscription request, where the subscription request is sent by the new creation unit group according to a service allocation condition, and the subscription request is used to subscribe to data of the target service type;

and sending a subscription success response to the newly-built unit group.

Optionally, the apparatus further comprises:

The embodiment of the application provides a data synchronization device, which can establish a first data synchronization relationship with a newly-built unit group, send service data of a target service type to the newly-built unit group, and release the first data synchronization relationship with the newly-built unit group according to a service switching instruction. Therefore, under the condition of not influencing the normal operation of the service, the backup relation is established between the target unit group and the newly-built unit group, the target unit group can send the service data of the target service type to the newly-built unit group, and the condition of service data loss is avoided. Furthermore, the newly-built unit group can process the service request of the target service type originally processed by the target unit group, and the problem of resource bottleneck of the target unit group is solved.

It should be noted that: in the data synchronization device provided in the above embodiment, only the division of the above functional modules is used for illustration when synchronizing data, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above described functions. In addition, the data synchronization device and the data synchronization method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.

The cells in each cell group may be terminals shown in fig. 28 described below, or may be servers shown in fig. 29 described below, which is not limited in the present application.

Fig. 28 is a schematic structural diagram of a terminal according to an embodiment of the present application. The terminal 2800 may be: a smart phone, a tablet computer, an MP3(Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3) player, an MP4(Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4) player, a notebook computer or a desktop computer. Terminal 2800 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, and so on.

Generally, terminal 2800 includes: one or more processors 2801 and one or more memories 2802.

Processor 2801 may include one or more processing cores such as 4-core processors, 8-core processors, and so forth. The processor 2801 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 2801 may also include a main processor and a coprocessor, where the main processor is a processor for processing data in an awake state, and is also referred to as a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 2801 may be integrated with a GPU (Graphics Processing Unit) that is responsible for rendering and drawing the content that the display screen needs to display. In some embodiments, the processor 2801 may further include an AI (Artificial Intelligence) processor for processing computational operations related to machine learning.

Memory 2802 may include one or more computer-readable storage media, which may be non-transitory. Memory 2802 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer-readable storage medium in memory 2802 is used to store at least one instruction for execution by processor 2801 to implement a cell group creation or data synchronization method provided by method embodiments herein.

In some embodiments, terminal 2800 may also optionally include: a peripheral interface 2803 and at least one peripheral. The processor 2801, memory 2802, and peripheral interface 2803 may be connected by a bus or signal line. Various peripheral devices may be connected to peripheral interface 2803 by buses, signal lines, or circuit boards. Specifically, the peripheral device includes: at least one of a radio frequency circuit 2804, a display screen 2805, a camera assembly 2806, an audio circuit 2807, a positioning assembly 2808, and a power supply 2809.

The peripheral interface 2803 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 2801 and the memory 2802. In some embodiments, processor 2801, memory 2802, and peripheral interface 2803 are integrated on the same chip or circuit board; in some other embodiments, any one or both of the processor 2801, the memory 2802, and the peripheral interface 2803 may be implemented on separate chips or circuit boards, which are not limited in this embodiment.

The Radio Frequency circuit 2804 is used to receive and transmit RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuit 2804 communicates with a communication network and other communication devices by electromagnetic signals. The radio frequency circuit 2804 converts an electric signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electric signal. Optionally, the radio frequency circuit 2804 comprises: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 2804 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generation mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 2804 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.

The display screen 2805 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When display screen 2805 is a touch display screen, display screen 2805 also has the ability to capture touch signals on or over the surface of display screen 2805. The touch signal may be input to the processor 2801 as a control signal for processing. At this point, the display 2805 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, display 2805 may be one, providing a front panel of terminal 2800; in other embodiments, display 2805 may be at least two, each disposed on a different surface of terminal 2800 or in a folded design; in some embodiments, display 2805 may be a flexible display disposed on a curved surface or a folded surface of terminal 2800. Even further, the display screen 2805 may be arranged in a non-rectangular irregular pattern, i.e., a shaped screen. The Display 2805 may be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or the like.

The camera assembly 2806 is used to capture images or video. Optionally, camera assembly 2806 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 2806 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.

The audio circuit 2807 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 2801 for processing or inputting the electric signals to the radio frequency circuit 2804 for voice communication. For stereo capture or noise reduction purposes, multiple microphones may be provided, each at a different location of terminal 2800. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 2801 or the radio frequency circuit 2804 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuit 2807 may also include a headphone jack.

The positioning component 2808 is operable to locate a current geographic location of the terminal 2800 to implement a navigation or LBS (location based Service). The positioning component 2808 can be a positioning component based on the GPS (global positioning System) in the united states, the beidou System in china, the graves System in russia, or the galileo System in the european union.

Power supply 2809 is used to provide power to various components within terminal 2800. Power supply 2809 can be alternating current, direct current, disposable batteries, or rechargeable batteries. When power supply 2809 includes a rechargeable battery, the rechargeable battery can support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, terminal 2800 also includes one or more sensors 2810. The one or more sensors 2810 include, but are not limited to: acceleration sensor 2811, gyroscope sensor 2812, pressure sensor 2813, fingerprint sensor 2814, optical sensor 2815, and proximity sensor 2816.

The acceleration sensor 2811 can detect the magnitude of acceleration on three coordinate axes of a coordinate system established with the terminal 2800. For example, the acceleration sensor 2811 may be used to detect components of gravitational acceleration in three coordinate axes. The processor 2801 can control the display screen 2805 to display a user interface in a landscape view or a portrait view based on the gravitational acceleration signal collected by the acceleration sensor 2811. The acceleration sensor 2811 may also be used for game or user motion data acquisition.

The gyro sensor 2812 may detect a body direction and a rotation angle of the terminal 2800, and the gyro sensor 2812 may collect a 3D motion of the user with respect to the terminal 2800 in cooperation with the acceleration sensor 2811. From the data collected by the gyro sensor 2812, the processor 2801 may perform the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.

Pressure sensors 2813 may be disposed on side frames of terminal 2800 and/or underlying display 2805. When the pressure sensor 2813 is disposed in a side frame of the terminal 2800, a user's grip signal on the terminal 2800 can be detected, and the processor 2801 performs right-left hand recognition or shortcut operation based on the grip signal acquired by the pressure sensor 2813. When the pressure sensor 2813 is disposed below the display screen 2805, the processor 2801 controls operability controls on the UI interface in accordance with a user's pressure operation on the display screen 2805. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.

The fingerprint sensor 2814 is configured to collect a fingerprint of a user, and the processor 2801 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 2814, or the fingerprint sensor 2814 identifies the identity of the user according to the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, the user is authorized by the processor 2801 to perform relevant sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying for and changing settings, etc. The fingerprint sensor 2814 may be disposed on a front, back, or side of the terminal 2800. When a physical key or vendor Logo is provided on the terminal 2800, the fingerprint sensor 2814 may be integrated with the physical key or vendor Logo.

Optical sensor 2815 is used to collect ambient light intensity. In one embodiment, processor 2801 may control the display brightness of display screen 2805 based on the ambient light intensity collected by optical sensor 2815. Specifically, when the ambient light intensity is high, the display luminance of the display screen 2805 is adjusted high; when the ambient light intensity is low, the display luminance of the display screen 2805 is turned down. In another embodiment, processor 2801 may also dynamically adjust the imaging parameters of camera assembly 2806 based on the intensity of ambient light collected by optical sensor 2815.

The proximity sensor 2816, also called a distance sensor, is generally provided on the front panel of the terminal 2800. Proximity sensor 2816 is used to gather the distance between the user and the front face of terminal 2800. In one embodiment, when proximity sensor 2816 detects that the distance between the user and the front face of terminal 2800 is gradually decreasing, display 2805 is controlled by processor 2801 to switch from a bright screen state to a dark screen state; when proximity sensor 2816 detects that the distance between the user and the front surface of terminal 2800 becomes gradually larger, display screen 2805 is controlled by processor 2801 to switch from a breath-screen state to a bright-screen state.

Those skilled in the art will appreciate that the architecture illustrated in fig. 28 is not intended to be limiting of terminal 2800 and that it may include more or fewer components than those illustrated, or that it may combine some components, or use a different arrangement of components.

Fig. 29 is a schematic structural diagram of a server according to an embodiment of the present application, where the server 2900 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 2901 and one or more memories 2902, where the one or more memories 2902 store at least one instruction, and the at least one instruction is loaded and executed by the one or more processors 2901 to implement the methods provided by the above method embodiments. Of course, the server 2900 may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface for inputting and outputting, and the server 2900 may also include other components for implementing device functions, which are not described herein.

In an exemplary embodiment, there is also provided a computer-readable storage medium, such as a memory, including instructions executable by a processor to perform the cell group creation method or the data synchronization method in the above embodiments. For example, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is intended to be exemplary only, and not to limit the present application, and any modifications, equivalents, improvements, etc. made within the spirit and scope of the present application are intended to be included therein.

Claims

1. A cell group creation method, applied to any cell of a newly created cell group, the method comprising:

receiving and storing the service data of the target service type;

2. The method according to claim 1, wherein said releasing the first data synchronization relationship with the target unit group according to the service switching instruction comprises:

3. The method according to claim 2, wherein said receiving a service switching command when the service data in the new cell group and the target cell group are synchronized, comprises:

4. The method according to claim 1, wherein the business data of the target business type comprises stock data and incremental data, the stock data is the business data of the target business type stored by the target unit group before the first data synchronization relationship is established, and the incremental data is the business data of the target business type stored by the target unit group after the first data synchronization relationship is established.

5. The method according to claim 1, wherein before establishing the first data synchronization relationship with the target unit group according to the service allocation, the method further comprises:

establishing connection with other units in the newly-built unit group;

6. The method according to claim 1, wherein before the releasing the first data synchronization relationship with the target unit group according to the service switching instruction, the method further comprises:

when the service distribution condition is updated and the updated service distribution condition indicates that the newly-built unit group is responsible for the target service type, if the service request of the target service type is received, the service request is processed to obtain service data, and the service data obtained after processing is synchronized to other units in the newly-built unit group and the target unit group.

7. The method of claim 1, wherein the target service type comprises a plurality of sub-service types, and each element in the newly created element group is responsible for a service of one sub-service type;

when receiving the service request of the target service type, processing the service request to obtain service data, and synchronizing the service data obtained after processing to other units in the newly-built unit group, including:

the method further comprises the following steps:

8. The method of claim 1, wherein the target cell group comprises a first cell and a second cell, wherein the first cell is a cell responsible for the target traffic type, and the second cell is a cell other than the first cell;

the receiving and storing the service data of the target service type includes:

9. A data synchronization method applied to a target cell group, the method comprising:

10. A unit group creation apparatus, characterized in that the apparatus comprises a plurality of functional modules for executing the unit group creation method of any one of claims 1 to 8.

11. A data synchronization apparatus, characterized in that the apparatus comprises a plurality of functional modules for performing the data synchronization method of claim 9.

12. A unit comprising one or more processors and one or more memories having stored therein at least one instruction that is loaded and executed by the one or more processors to perform operations performed by a unit group creation method according to any one of claims 1 to 8; or the operations performed by the data synchronization method of claim 9.

13. A computer-readable storage medium having stored therein at least one instruction, which is loaded and executed by a processor to perform operations performed by the cell group creation method of any one of claims 1 to 8; or the operations performed by the data synchronization method of claim 9.