CN111124696B

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

Info

Publication number: CN111124696B
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: 2023-06-23
Anticipated expiration: 2039-12-30
Also published as: CN111124696A

Abstract

The application provides a method, a device, a unit and a storage medium for creating a unit group and synchronizing data, 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. Thus, the new unit group and the target unit group establish a backup relationship, and the target unit group can synchronize the service data of the target service type to the new unit group, and further, the new unit group can process the service request of the target service type, thereby solving the problem of resource bottleneck of the target unit group.

Description

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

Technical Field

The present disclosure 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, when using a network, generate a large amount of data that is distributed to units capable of performing all business operations for processing. If a major disaster occurs in the area where the unit is deployed, such as a large-scale power outage, an earthquake, a fire, etc., the unit may not work, and thus, the data cannot be processed, and further, the service cannot be performed normally.

In the related art, in order to avoid the above situation, a technician typically constructs a multi-active architecture in different places, i.e. units are deployed in different areas, units located in different areas process data separately, and keep data synchronization with each other, so as to form a unit group. Therefore, when one of the areas is in a serious disaster and the unit deployed in the local area cannot work, the unit deployed in the other area can timely bear the load, and the data can be continuously processed, so that the normal operation of the service is ensured.

When the data volume to be processed of the unit group is larger than the processing capacity of the unit group, the unit group can face the problem of resource bottleneck, and the normal operation of the service is affected. In the related art, there is no method for effectively solving the problem of resource bottleneck. There is therefore a need for a solution to the problem of resource bottlenecks.

Disclosure of Invention

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

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

according to service allocation conditions, a first data synchronization relation 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 relation is used for indicating service data of a target service type between the newly-built unit group and the target unit group, and the service type processed by the target unit group at least comprises the target service type;

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

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

and when the service request of the target service type is received, 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.

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;

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

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

verifying the service data of the target service type stored in the new unit group and the target unit group;

and when the service data of the target service type stored in the new unit group and the target unit group are the same, receiving a service switching instruction.

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

Optionally, before the first data synchronization relationship is established 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 relation with the other units according to the service distribution condition, wherein the second data synchronization relation is used for indicating the units in the newly-built unit group to synchronize the service data which are responsible for the units to the other units.

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

when the service allocation situation is updated, and the updated service allocation situation indicates that the new unit group is responsible for the target service type, if a service request of the target service type is received, processing the service request to obtain service data, and synchronizing the service data obtained after processing to other units in the new unit group and the target 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;

and 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, wherein the method comprises the following steps:

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 steps of:

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:

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

a subscription success response is received.

Optionally, the method further comprises:

after each step of the unit group creation method, performing pressure test or fault exercise on the newly-built unit group to obtain the working 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, executing the next step after the current step.

In another aspect, an embodiment of the present application provides a data synchronization method, applied to a target unit group, where the method includes:

establishing a first data synchronization relationship with a newly-built 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 service data of mutually synchronous target service types 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 types;

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

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

and executing the step of releasing the first data synchronization relation with the newly built 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 in the target unit group before the first data synchronization relationship is established, and the incremental data is data of the target service type stored in the target unit group after the first data synchronization relationship is established;

the sending the service data of the target service type to the new 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 releasing the first data synchronization relationship with the new unit group according to the service switching instruction, the method further includes:

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

receiving a subscription request, wherein the subscription request is sent by the newly-built unit group according to service allocation conditions, 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 comprises:

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

In another aspect, an embodiment of the present application provides a unit group creation device applied to any unit of a newly built unit group, including:

the system comprises a building module, a target unit group and a first data synchronization relation, wherein the building module is used for building a first data synchronization relation with the target unit group according to service distribution conditions, a plurality of units included in each unit group are used for carrying out remote backup, the first data synchronization relation is used for indicating service data of mutually synchronous target service types 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 types;

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

the releasing module is used for releasing the first data synchronization relation with the target unit group according to the 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 new unit group and the target unit group are completed synchronously;

Optionally, the apparatus further includes:

the verification module is used for verifying the service data of the target service type stored in the new 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 new unit group and 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 situation, where the second data synchronization relationship is used to instruct a unit in the new unit group to synchronize service data that is responsible for itself to the other units.

Optionally, the processing module is further configured to, when the service allocation situation is updated, instruct the new unit group to be responsible for the target service type, process the service request if the service request of the target service type is received, obtain service data, and synchronize the service data obtained after processing to other units in the new 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 new 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 new unit group.

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

In another aspect, an embodiment of the present application provides a data synchronization apparatus, applied to a target unit group, where the apparatus includes:

the system comprises a building module, a first data synchronization relation, a second data synchronization relation and a target unit group, wherein the building module is used for building a first data synchronization relation with the new unit group, a plurality of units included in each unit group are used for carrying out remote backup, the first data synchronization relation is used for indicating service data of the target service type between the new unit group and the target unit group, and the service type processed by the target unit group at least comprises 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 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 includes:

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

The storage module is also used for storing the service data;

the processing module is further configured to send the service data to the new unit group.

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

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

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

Optionally, the apparatus further includes:

the acceptance module is used for performing pressure test or fault exercise on the newly-built unit group after each step of the data synchronization method to obtain the working acceptance condition of the newly-built unit group;

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

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

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

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 service data of a target service type to any unit of the newly-built unit group. And according to the service switching instruction, any unit of the target unit group and the newly-built unit group releases the first data synchronization relation. Any unit of the newly-built unit group receives and processes the service request of the target service type, obtains service data, and synchronizes to other units in the newly-built unit group. By establishing a standby relation between the new unit group and the target unit group, the service data of the target service type can be synchronized between the new unit group and the target unit group, so that the service responsible for the target unit group can be split. Under the condition that normal operation of the service is not affected, the new unit group and the target unit group establish a standby relation, so that the condition that service data is lost can be avoided, further, the new unit group can process service requests of target service types originally processed by the target unit group, and 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 of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a method for creating a unit group provided in an embodiment of the present application;

FIG. 2 is a flow chart of a method for synchronizing data according to an embodiment of the present application;

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

fig. 4 is a schematic connection diagram of a new unit group and a target unit group according to an embodiment of the present application;

fig. 5 is a schematic connection diagram of any unit of a newly-built unit group and a target unit group according to an embodiment of the present application;

fig. 6 is a schematic diagram of a new unit set according to an embodiment of the present application after any unit of the new unit set is disconnected from the target unit set;

FIG. 7 is a schematic diagram of another method for creating a unit group and synchronizing data according to an embodiment of the present application;

FIG. 8 is a schematic diagram of another method for creating a unit group and synchronizing data according to an embodiment of the present application;

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

FIG. 10 is a schematic diagram of another method for creating a unit group and synchronizing data according to an embodiment of the present application;

FIG. 11 is a schematic diagram of another method for creating a unit group and synchronizing data according to an embodiment of the present application;

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

FIG. 13 is a schematic diagram of another method for creating a unit group and synchronizing data according to an embodiment of the present application;

FIG. 14 is a schematic diagram of another method for creating a group of units and synchronizing data according to an embodiment of the present application;

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

FIG. 16 is a schematic diagram of another method for creating a group of units and synchronizing data according to an embodiment of the present application;

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

FIG. 18 is a schematic diagram of another method for creating a group of units and synchronizing data according to an embodiment of the present application;

FIG. 19 is a schematic diagram of another method for creating a group of units and synchronizing data according to an embodiment of the present application;

FIG. 20 is a schematic diagram of another method for creating a unit group and synchronizing data according to an embodiment of the present application;

FIG. 21 is a schematic diagram of another method for creating a unit group and synchronizing data according to an embodiment of the present application;

FIG. 22 is a schematic diagram of another method for creating a group of units and synchronizing data according to an embodiment of the present application;

FIG. 23 is a schematic diagram of another method for creating a unit group and synchronizing data according to an embodiment of the present application;

FIG. 24 is a schematic diagram of another method for creating a group of cells and synchronizing data according to an embodiment of the present application;

FIG. 25 is a schematic diagram of another method for creating a group of units and synchronizing data according to an embodiment of the present application;

fig. 26 is a schematic structural view of a unit group creation device provided in the embodiment of the present application;

fig. 27 is a schematic structural diagram of a data synchronization device 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

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the 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, but not all embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

In this application, the terms "first," "second," and the like are used to distinguish between identical or similar items that have substantially the same function and function, and it should be understood that there is no logical or chronological dependency between the terms "first," "second," and "nth," and that there is no limitation on the number and order of execution.

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

Unit group: a cell group includes 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 can synchronize the service data to other units in the unit group. A plurality of units that are mutually reserved in different places form a unit group. The number of units included in each unit group may be set by a relevant technician according to the needs, for example, the number of units may be 2 or 5, which is not limited in the embodiment of the present application.

And (5) carrying out remote backup: multiple units within a unit group are deployed in different regions, each unit being capable of providing the same service, and data synchronization being maintained between the multiple units. When a certain unit fails and is not available, the units deployed in other areas can take over the unavailable units, and service requests are continuously processed, so that normal operation of the service is ensured.

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

101. according to the service allocation situation, a first data synchronization relation 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 relation is used for indicating service data of a target service type between the newly-built unit group and the target unit group, and the service type processed by the target unit group at least comprises 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, releasing the first data synchronization relation with the target unit group.

104. And when the service request of the target service type is received, 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.

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

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 in the target unit group before the first data synchronization relationship is established, and the incremental data is data of the target service type stored in the target unit group after the first data synchronization relationship is established.

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

when the service allocation situation is updated and the updated service allocation situation indicates that the new unit group is responsible for the target service type, if a 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 new unit group and the target unit group.

when receiving the service request of the target service type, the method processes the service request to obtain service data, synchronizes the service data obtained after processing to other units in the newly-built unit group, and comprises the following steps:

the method further comprises the steps of:

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 service allocation conditions, 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 comprises:

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.

The embodiment of the application provides a method for creating a unit group, which is used for receiving and storing service data of a target service type by establishing a first data synchronization relationship with a target unit group, and releasing 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, the spare relation between the newly-built unit group and the target unit group can be established under the condition that normal operation of the service is not affected, the newly-built unit group can receive the service data of the target service type sent by the target unit group, and the condition that the service data is lost 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.

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

201. Establishing a first data synchronization relationship with a new unit group, wherein 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 service data of a target service type between the new unit group and the target unit group, and the service type processed by the target unit group at least comprises the target service type;

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

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

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

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

Optionally, before the releasing the first data synchronization relationship with the newly created unit group according to the service switching instruction, the method further includes:

and receiving service data of the target service type sent by the new unit group, wherein the service data is updated according to service allocation conditions, and when the updated service allocation conditions indicate that the new unit group is responsible for the target service type, the new unit group processes the received service request of the target service type.

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

Optionally, the method further comprises:

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

The embodiment of the application provides a data synchronization method, which is used for establishing a first data synchronization relationship with a new unit group, sending service data of a target service type to the new unit group, and releasing the first data synchronization relationship with the new unit group according to a service switching instruction. Therefore, the backup relationship between the target unit group and the new unit group can be established under the condition that normal operation of the service is not affected, and the target unit group can send the service data of the target service type to the new unit group, so that 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 described above are presented with respect to specific flows of the method for creating a unit group and the method for synchronizing data, starting from a single side of a newly created unit group and a target unit group, respectively, and the specific flows of the methods described above are described with respect to information interaction between the newly created unit group and the target unit group, starting from the embodiment shown in fig. 3. Fig. 3 is a flowchart of a method for creating a unit group and synchronizing data according to an embodiment of the present application. Referring to fig. 3, the method includes:

301. and any unit of the newly-built unit group establishes a first data synchronization relationship with the target unit group according to the service allocation condition.

In the embodiment of the application, a new unit group can be created, the new unit group is used for serving part of service processing services for the original unit group, and a plurality of units included in each unit group are used for carrying out remote backup, so that units in a certain area are failed, and services responsible for the units can be transferred to other units in the unit group. The new unit group can establish a data synchronization relationship with the original unit group needing to split the service, and synchronize part of service data which needs to be responsible for the new unit group to the new unit group, so that after the follow-up service splitting is completed, the new unit group can be responsible for the part of service processing service, and the original unit group can process services other than the part of service processing service.

Therefore, in the creation process of 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 that the target unit group is responsible for processing at least include the service types that the new unit group needs to process subsequently. The service type to be processed in the new unit group is called as the target service type. That is, the first data synchronization relationship is used to indicate service data of a target service type between the newly-built unit group and the target unit group, where the service type processed by the target unit group at least includes the target service type.

The service allocation situation is used to indicate the type of service handled by each unit in the respective unit group. The division of the service types may be implemented according to a certain rule, for example, may be divided according to regions, and for example, may be divided according to service fields, which is not limited in the embodiment of the present application.

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

When the target unit group is one unit group, any unit of the newly-built unit group can only establish a first data synchronization relationship with one target unit group, when the target unit group is a plurality of unit groups, any unit of the newly-built unit group can respectively establish a first data synchronization relationship with each unit group in the target unit group, each unit group respectively synchronizes part of 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 is obtained.

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

In one possible implementation, the first data synchronization relationship may be a subscription relationship, and any element of the newly created element group may subscribe to the service data of the target service type from the target element group. Specifically, any unit of the newly-built 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 newly-built unit group, any unit of the newly-built unit group correspondingly receives the subscription success response, and the first data synchronization relationship is established successfully.

Through the subscription relation, the new unit group can automatically determine the target unit group and establish a first data synchronization relation for synchronizing the service data of the target service type with the target unit group, and compared with the method for manually configuring the data synchronization relation among the unit groups by technicians in the related art, the method has the advantages that the automatic determination of the new unit group to the target unit group and the automatic establishment of the first data synchronization relation between the new unit group and the target unit group are realized, the labor cost is saved, and the efficiency is improved.

In one possible implementation, the new set of units may be created before any unit of the new set of units establishes a first data synchronization relationship with the target set of units according to the service allocation situation. The creation process of the new unit group may be: any unit of the newly-built unit group can be connected with other units in the newly-built unit group, and a second data synchronization relationship is established with the other units according to service allocation conditions. The second data synchronization relationship is used for indicating the units in the newly-built unit group to synchronize the service data obtained by the units to other units.

Through the second data synchronization relationship, any unit of the newly-built unit group and other units automatically form a backup relationship to form the newly-built unit group, and further, the units in the newly-built unit group can automatically synchronize service data obtained by themselves to other units, so that the automation of establishing the data synchronization relationship and synchronizing the service data between any unit of the newly-built unit group and other units 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 firstly applies for various resources of each service in the unit. Specifically, any unit of the newly-built unit group requests corresponding resources from a corresponding server according to the target service type of the service processing service.

For example, the business processing services for which any element of the newly-built element group is responsible include application services, and accordingly, any element of the newly-built element group requests corresponding resources from the application server to deploy the application services and configure the corresponding dependencies. The service processing service may further include a data service, a cache service, and a message queue service, where any element of the newly created element group may request corresponding resources from a corresponding data server, cache server, and 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 element of the newly created element 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 each unit is responsible for processing a different type of traffic. The target unit group comprises a first unit and a second unit, wherein the first unit is a unit responsible for a target service type, and the second unit is a unit other than the first unit. The number of the first units and the second units may be one or more.

Specifically, when the number of the first units is one, any unit of the newly built unit group can 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 can respectively establish a first data synchronization relationship with each first unit.

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

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, the first unit and the second unit of the newly-built unit group are mutually redundant. Any unit of the newly-built unit group can be used as a backup of the target unit group to receive and store the service data sent by the target unit group. If disaster is suffered when the first unit sends 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 service data of the target service type is also stored in the second unit.

And establishing a first data synchronization relationship between any unit of the newly-built unit group and the first unit and the second unit respectively, wherein any unit, the first unit and the second unit of the newly-built unit group are mutually redundant. In the process of synchronizing service data between the target unit group and the newly-built unit group, the disaster recovery capability of the target unit group is not damaged, any unit of the newly-built unit group can be used as a backup, and the disaster recovery capability is improved.

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

In one 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 service data of the target service type sent by the first unit. Specifically, when any unit of the newly-built unit group only establishes a first data synchronization relationship with the first unit or respectively establishes a first data synchronization relationship with the first unit and the second unit, only the first unit can send service data of a target service type to any unit of the newly-built unit group.

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

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-built unit group according to the first data synchronization relationship, so that the situation that the same data are repeatedly synchronized to cause data redundancy, even data errors or data wireless loop replication is 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 that the service data synchronization is performed normally.

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

Correspondingly, for 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; 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 transmits the obtained service data of the target service type to any unit of the newly-built unit group.

In the process of synchronizing the service data, the target unit group continuously receives the service request, divides the service data of the target type into the increment data and the stock data, and adopts different synchronization modes for the increment data and the stock data, so that the service data can be synchronized under the condition that the service is normally performed, and further 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 new unit group is responsible for the target service type, if any unit of the new unit 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 synchronizing the obtained service data to other units and target unit groups in the newly-built unit group by any unit in the newly-built unit group. The target unit group receives service data of the target service type sent by the new unit group.

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

Specifically, before the service allocation situation 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, the service data of the target service type is synchronized to the new unit group according to the first data synchronization relation, after the service allocation situation 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 the service data of the target service type is synchronized to the target unit group according to the first data synchronization relation, and the target unit group does not receive the service request of the target service type any more.

By updating the service allocation situation, any unit of the newly-built unit group starts to receive and process 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, so that unified updating of service allocation is realized, and 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 one possible implementation, when any unit of the newly-built unit group receives a service request of a 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 new unit group can send the obtained first service data of the first sub-service type to other units in the new unit group, and receive the second service data of the second sub-service type sent by other units in the new 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 created cell group may include a fifth cell and a sixth cell, 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 0-99 types, and the sixth unit is used for processing the service requests of 100-199 types. The fifth unit obtains the service data of 0-99 type and sends the service data to the sixth unit, and the sixth unit obtains the service data of 100-199 type and sends the service data to the fifth unit. There is a synchronization relationship of traffic data of the type 0-199 between the fifth unit and the sixth unit.

Through the data replication relation established among the units in the newly-built unit group, a plurality of units in the newly-built unit group respectively process a part of service requests of target service types, and the units are reserved 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 replace the disaster-suffered unit, the service requests are continuously processed, and normal operation of the service is ensured.

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

The service switching instruction is used for indicating to release the first data synchronization relationship between any unit of the newly-built unit group and the target unit group.

Specifically, any unit of the new unit group may send an unsubscribe request to the target unit group, where the target unit group receives the unsubscribe request, and send an unsubscribe success response to any unit of the new unit group, where any unit of the new unit group correspondingly receives the unsubscribe success response, and the first data synchronization relationship is unsuccessfully released.

In one possible implementation, when the synchronization of the service data in the new unit group and the target unit group is completed, the new unit group and the target unit group receive the service switching instruction, and the step of releasing the first data synchronization relationship between any unit of the new unit group and the target unit group is performed.

Specifically, after the first data synchronization relationship is established between the new unit group and the target unit group, the data between the new unit group and the target unit group is always synchronized before the first data synchronization relationship is released. If the service data in the new unit group and the target unit group are synchronously completed, the new unit group is indicated to store the service data of all the target service types, the service allocation situation is updated, the new unit group does not need to acquire the service data of the target unit group any more, and the step of releasing the first data synchronization relationship between any unit of the new unit group and the target unit group can be executed.

When the service data in the new unit group and the target unit group are synchronous, the step of releasing the first data synchronous relation between any unit of the new unit group and the target unit group is executed, so that the step of releasing the first data synchronous relation is ensured to be executed on the premise that the new unit group already receives all the service data of the target service type stored in the target unit group, and the condition that the service data is lost due to poor timing of releasing the first data synchronous relation is avoided.

In a possible implementation manner, the data synchronization may be implemented by a verification manner, specifically, any unit of the new unit group verifies service data of the target service type stored in the new unit group and the target unit group, and when the service data of the target service type stored in the new unit group and the target unit group are the same, a service switching instruction is received.

Specifically, after the first data synchronization relationship is established between the new unit group and the target unit group, the data between the new unit group and the target unit group is always synchronized before the first data synchronization relationship is released. If the service data of the target service type stored in the new unit group and the target unit group are the same, the new unit group is indicated to have received all the service data of the target service type stored in the target unit group, and the new unit group can smoothly synchronize the service data of the target service type to the target unit group. At this time, the first data synchronization relation 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 in the new unit group and the target unit group, whether the service data of the target service type stored in the new unit group and the target unit group are identical 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 in 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 a service request of a 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 involved in 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 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 situation is updated, and will not be described herein.

In one possible implementation manner, after each step, performing pressure test or fault exercise on the new unit group to obtain a working acceptance condition of the new unit group, and executing the next step after the current step when the working acceptance condition indicates that the working condition of the new unit group is normal.

The pressure test may be a test of the capability of the new unit group to process the service request and the synchronous data, the fault exercise may be a test of the working condition of other units by setting a certain unit in the new unit group to be unavailable, or a test of the working condition of the new unit group by setting the target unit group to be unavailable when the new unit group and the target unit group establish the first data synchronous relationship.

Specifically, when the work acceptance condition indicates that the work condition of the new 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 new unit group is abnormal, the next step is not executed, but the new unit group is subjected to fault checking and corresponding repairing steps, and then the pressure test or the fault exercise is performed again.

By performing pressure test or fault exercise on the new unit group, defects in the new unit group can be found in time, and larger loss is avoided.

In one possible implementation, after the first data synchronization relationship is released between the target unit group and the newly-built unit group, the first data synchronization relationship is released between units in the target unit group, and service data of the target service type is cleared.

Wherein the service types that the target unit group is responsible for processing at least include the target service type, it is obvious that 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 0-199 type is released, the data synchronization relationship of 200-499 type is reserved, the service data of 0-199 type stored in the first unit and the second unit are useless data, and the first unit and the second unit clear the service data of 0-199 type.

After the new unit group completely takes over the processing of the service request of the target service type, the data synchronization relation among the units in the target unit group is corrected, and the service data of the target service type is cleared, so that the occurrence of the conditions that the data redundancy and the storage space of the target unit group are occupied is avoided.

In one possible implementation, after the units in the target unit group clear the service data of the target service type, checksum comparison is performed on the service data stored in each unit in the target unit group.

By checking and comparing the service data stored in each unit of the target unit group, the situation that the unit in the target unit group clears the service data of the target service type and the service data of other service types are cleared together by mistake, so that the data is lost 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 service data of a target service type to any unit of the newly-built unit group. And according to the service switching instruction, any unit of the target unit group and the newly-built unit group releases the first data synchronization relation. Any unit of the newly-built unit group receives and processes the service request of the target service type, obtains service data, and synchronizes to other units in the newly-built unit group. Therefore, the backup relationship between the target unit group and the new unit group can be established under the condition that normal operation of the service is not affected, the target unit group can synchronize the service data of the target service type to the new unit group, and the condition that the service data is lost 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.

In the embodiment shown in fig. 3, the specific flow of the method for creating the unit group and synchronizing the data is described from the point of information interaction between the new unit group and the target unit group. A specific embodiment is provided below to exemplarily describe a specific flow of the unit group creation and data synchronization method.

The embodiments of the present application relate to FIGS. 7-25 in which "BJ" and "SH" may represent two different unit deployment regions, e.g., where "BJ" may represent Beijing, "SH" may represent Shanghai, and "SET" may represent a unit. In this embodiment, the original unit group includes two unit groups, the target unit group is a unit group, each unit group includes two units as an example, the target unit group includes SET (unit) 1 and SET3, another unit group in the original unit group includes SET2 and SET4, and the newly-built unit group includes SET5 and SET6. The new unit group is responsible for processing the service request of 0-199 type, the target unit group is responsible for processing the service request of 0-499 type, the other unit group in the original unit group is responsible for processing the service request of 500-999 type, wherein the SET1 is responsible for processing the service request of 0-249 type, the SET2 is responsible for processing the service request of 500-749 type, the SET3 is responsible for processing the service request of 250-499 type, the SET4 is responsible for processing the service request of 750-999 type, the SET5 is responsible for processing the service request of 0-99 type, and the SET6 is responsible for processing the service request of 100-199 type.

As shown in fig. 7, in the initial state, SET1 is responsible for the type 0-249 traffic, and as a backup for SET3, the type 250-499 traffic data, that is, the type 0-499 traffic data storage is replicated; SET3 is responsible for 250-499 types of traffic and as a backup for SET1, replicates 0-249 types of traffic data, i.e., is responsible for 0-499 types of traffic data storage; the SET2 is responsible for 500-749 type business, and as the backup of the SET4, 750-999 type business data are duplicated, namely, 500-999 type business data storage is responsible; the SET4 is responsible for 750-999 type traffic and as a backup for SET2, duplicates 500-749 type traffic data, i.e. is responsible for 500-999 type traffic data storage.

As shown in fig. 8-9, a SET5 and a SET6 are newly built. Specifically, the SET5 and the SET6 request corresponding resources, including application services, data services, cache services, message queue services, and the like, from corresponding servers according to specific types of service processing services, respectively, 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 unit of the newly-built unit group establishes the second data synchronization relationship with other units, any unit of the newly-built unit group first applies for various resources of each service in the unit.

As shown in fig. 10, a traffic data duplication relationship with respect to the 0-199 type is established between the SET5 and the SET6, so that the 0-199 type traffic data can be synchronized between the SET5 and the SET6, and a new cell group is established. That is, in the above embodiment, any unit of the newly-built unit group establishes connection with other units of the newly-built unit group, and establishes a second data synchronization relationship with other units according to the service allocation situation.

As shown in fig. 11, after the service data replication relationship about the 0-199 type is established between the SET5 and the SET6, the new SET is checked and accepted to ensure that the new SET is established successfully. That is, in the above embodiment, the new unit group is subjected to pressure test or fault exercise to obtain the work acceptance condition of the new unit group, and when the work acceptance condition indicates that the work condition of the new unit group is normal, the next step after the current step is executed.

As shown in fig. 12 to 13, the SET5 establishes a traffic data duplication relationship of 0-199 type with the SET1 and the SET3, respectively, and the SET1 can transmit the stored traffic data of 0-199 type to the SET5, and the SET5 satisfies the preparation condition of becoming three redundancy of 0-199 type. As shown in fig. 14 to 15, the SET6 establishes a traffic data duplication relationship of 0-199 type with the SET1 and the SET3, respectively, and the SET1 can transmit the stored traffic data of 0-199 type to the SET6, and the SET6 satisfies the preparation condition of becoming four redundancy of 0-199 type. That is, in the above embodiment, any unit of the newly-built unit group establishes the first data synchronization relationship with the first unit and the second unit of the target unit group, respectively, and any unit, the first unit and the second unit of the newly-built unit group are backup to each other. 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 may be performed simultaneously, which is not limited in the embodiment of the present application.

As shown in fig. 16, the comparison of the stock data and the verification of the incremental data are performed. Before the data synchronization relation of the stock data is established, the data of the target service type stored in the SET1 is established, and after the incremental data is established, the data of the target service type stored in the SET1 target unit group is established. That is, in the above embodiment, any unit of the new unit group performs verification on the service data of the target service type stored in the new unit group and the target unit group.

As shown in fig. 17 to 18, the SET5 receives a 0-99 type service request, the SET6 receives a 100-199 type service request, and the SET1 no longer receives a 0-199 type service request, but starts to receive 0-99 type service data transmitted by the SET5 and 100-199 type service data transmitted 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 a service request of a target service type, the service request is processed to obtain and store service data of the target service type.

As shown in fig. 19, the acceptance of the new SET of units ensures that the SET5 and the SET6 can successfully process the service requests of the 0-99 and 100-199 types, respectively. That is, in the above embodiment, the new unit group is subjected to pressure test or fault exercise to obtain the work acceptance condition of the new unit group, and when the work acceptance condition indicates that the work condition of the new unit group is normal, the next step after the current step is executed.

As shown in fig. 20-21, the SET6 releases the traffic data duplication relationship of the 0-199 type with the SET1 and the SET3, respectively, and the SET1, the SET3 and the SET5 are three backup relationships of the 0-199 type. As shown in fig. 22-23, SET5 releases the traffic data replication relationship of the 0-199 type with SET1 and SET3, respectively, when SET5 and SET6 are two backup relationships of the 0-199 type. That is, in the above embodiment, any unit of the newly-built unit group and the target unit group release the first data synchronization relationship between any unit of the newly-built unit group and the target unit group according to the service switching instruction. 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, which is not limited in the embodiment of the present application.

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

As shown in fig. 25, the check sum of the stock data is compared with that of SET1 and SET3, and acceptance is performed. That is, in the above embodiment, after the units in the target unit group clear the service data of the target service type, checksum comparison is performed on the service data stored in each unit of the target unit group. Thus, the creation of the unit group and the data synchronization are completed.

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

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

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

the establishing module 2601 is configured to establish a first data synchronization relationship with a target unit group according to a service allocation situation, where a plurality of units included in each unit group are used for performing remote redundancy, the first data synchronization relationship is used to indicate service data of a target service type that is mutually synchronized between the newly-built 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 storage module 2602, configured to receive and store service data of the target service type;

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

and 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 the processing to other units in the new unit group.

Optionally, the release module 2603 is specifically configured to receive a service switching instruction when service data in the new unit group and the target unit group are completed synchronously;

Optionally, the apparatus further comprises:

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

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 new unit group and 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 units according to the service allocation situation, where the second data synchronization relationship is used to instruct the unit in the new unit group to synchronize the service data that is responsible for itself to the other units.

Optionally, the processing module 2604 is further configured to, when the service allocation situation is updated, and the updated service allocation situation indicates that the new unit group is responsible for the target service type, process the service request to obtain service data if the service request of the target service type is received, and synchronize the service data obtained after the processing to other units in the new 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-built unit group;

the storage module 2602 is further configured to receive and store second service data of a second sub-service type synchronized by other units in the new 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, the spare relation between the newly-built unit group and the target unit group can be established under the condition that normal operation of the service is not affected, the newly-built unit group can receive the service data of the target service type sent by the target unit group, and the condition that the service data is lost 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: the unit group creation device provided in the above embodiment only illustrates the division of the above functional modules when creating the unit group, and in practical application, the above functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the functions described above. In addition, the unit group creation device and the unit group creation method provided in the foregoing embodiments belong to the same concept, and specific implementation processes of the unit group creation device and the unit group creation method are detailed in the method embodiments, and are not repeated here.

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

the establishing module 2701 is configured to establish a first data synchronization relationship with a new unit group, where a plurality of units included in each unit group are used for performing remote backup, the first data synchronization relationship is used to indicate service data of a target service type that is synchronized with each other 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 new unit group;

A storage module 2702 for storing service data;

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

Optionally, the release module 2703 is specifically configured to receive a service switching instruction when service data in the new unit group and the target unit group are completed synchronously;

Optionally, the apparatus further comprises:

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

Optionally, the processing module 2704 is specifically configured to extract service data of the 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 new set of units.

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

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

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

Optionally, the apparatus further comprises:

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

The embodiment of the application provides a data synchronization device which can establish a first data synchronization relationship with a new unit group, send service data of a target service type to the new unit group, and release the first data synchronization relationship with the new unit group according to a service switching instruction. Therefore, the backup relationship between the target unit group and the new unit group can be established under the condition that normal operation of the service is not affected, and the target unit group can send the service data of the target service type to the new unit group, so that 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 application, the above functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the data synchronization device and the data synchronization method provided in the foregoing embodiments belong to the same concept, and specific implementation processes of the data synchronization device and the data synchronization method are detailed in the method embodiments and are not repeated herein.

The units in each unit group may be terminals shown in fig. 28 described below or servers shown in fig. 29 described below, and the present application is not limited thereto.

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, an MP3 (Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio plane 3) player, an MP4 (Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio plane 4) player, a notebook or a desktop. Terminal 2800 may also be referred to by other names of user devices, portable terminals, laptop terminals, desktop terminals, and the like.

In general, the 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 a 4-core processor, an 8-core processor, and the like. Processor 2801 may be implemented in hardware in at least one of a DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). Processor 2801 may also include a main processor, which is a processor for processing data in an awake state, also referred to as a CPU (Central Processing Unit ); a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, processor 2801 may incorporate a GPU (Graphics Processing Unit, image processor) for rendering and rendering content required to be displayed by the display screen. In some embodiments, the processor 2801 may also include an AI (Artificial Intelligence ) processor for processing computing 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 nonvolatile 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 the cell group creation or data synchronization methods provided by the 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 interfaces 2803 may be connected by a bus or signal lines. The individual peripheral devices may be connected to the peripheral device interface 2803 by buses, signal lines, or circuit boards. Specifically, the peripheral device includes: at least one of radio frequency circuitry 2804, a display screen 2805, a camera assembly 2806, an audio circuit 2807, a positioning assembly 2808, and a power supply 2809.

A peripheral interface 2803 may be used to connect I/O (Input/Output) related at least one peripheral to the processor 2801 and 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, either or both of processor 2801, memory 2802, and peripheral interface 2803 may be implemented on separate chips or circuit boards, which is not limited in this embodiment.

The Radio Frequency circuit 2804 is used to receive and transmit RF (Radio Frequency) signals, also referred to as electromagnetic signals. The radio frequency circuit 2804 communicates with a communication network and other communication devices through 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 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. The radio frequency circuit 2804 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: metropolitan area networks, various generations of 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 2805 is a touch display, display 2805 also has the ability to collect touch signals at or above the surface of display 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 virtual keyboards, also referred to as soft buttons and/or soft keyboards. In some embodiments, the display screen 2805 may be one, providing a front panel of the terminal 2800; in other embodiments, the display 2805 may be at least two, each disposed on a different surface of the terminal 2800 or in a folded configuration; in some embodiments, display 2805 may be a flexible display disposed on a curved surface or a folded surface of terminal 2800. Even more, the display screen 2805 may be arranged in an irregular pattern other than rectangular, i.e., a shaped screen. The display screen 2805 may be made of LCD (Liquid Crystal Display ), OLED (Organic Light-Emitting Diode) or other materials.

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

The audio circuit 2807 may include a microphone and a speaker. The microphone is used for collecting sound waves of users and environments, 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 purposes of stereo acquisition or noise reduction, the microphone may be multiple, each disposed at a different location of the terminal 2800. The microphone may also be an array microphone or an omni-directional pickup microphone. The speaker is used to convert electrical signals from the processor 2801 or the radio frequency circuit 2804 into sound waves. The speaker may be a conventional thin film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, not only the electric signal can be converted into a sound wave audible to humans, but also the electric signal can be converted into a sound wave inaudible to humans for ranging and other purposes. In some embodiments, audio circuit 2807 may also include a headphone jack.

The location component 2808 is used to locate the current geographic location of the terminal 2800 to enable navigation or LBS (Location Based Service, location based services). The positioning component 2808 may be a positioning component based on the United states GPS (Global Positioning System ), the Beidou system of China, the Granati system of Russia, or the Galileo system of the European Union.

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

In some embodiments, the 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 acceleration levels on three coordinate axes of a coordinate system established with the terminal 2800. For example, the acceleration sensor 2811 can be configured to detect components of gravitational acceleration in three axes. The processor 2801 may control the display 2805 to display the user interface in a landscape view or a portrait view based on the gravitational acceleration signal acquired by the acceleration sensor 2811. The acceleration sensor 2811 may also be used for gathering motion data for a game or user.

The gyro sensor 2812 can detect the body direction and the rotation angle of the terminal 2800, and the gyro sensor 2812 can acquire a 3D motion of the user on the terminal 2800 in cooperation with the acceleration sensor 2811. Processor 2801 may perform the following functions based on the data collected by gyro sensor 2812: motion sensing (e.g., changing UI according to a tilting operation by a user), image stabilization at shooting, game control, and inertial navigation.

Pressure sensor 2813 may be located on a side frame of terminal 2800 and/or below display 2805. When the pressure sensor 2813 is provided at a side frame of the terminal 2800, a grip signal of the terminal 2800 by a user may be detected, and the processor 2801 performs left-right hand recognition or quick operation according to the grip signal collected by the pressure sensor 2813. When the pressure sensor 2813 is disposed in the lower layer of the display screen 2805, the processor 2801 controls the operability control on the UI interface according to the pressure operation of the user on the display screen 2805. The operability controls include 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 based on the fingerprint collected by the fingerprint sensor 2814, or the fingerprint sensor 2814 identifies the identity of the user based on the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, the user is authorized by the processor 2801 to perform related sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying for and changing settings, etc. Fingerprint sensor 2814 may be located on the front, back, or side of 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.

The 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 intensity of ambient light collected by optical sensor 2815. Specifically, when the intensity of the ambient light is high, the display brightness of the display screen 2805 is turned up; when the ambient light intensity is low, the display brightness of the display screen 2805 is turned down. In another embodiment, processor 2801 may also dynamically adjust the shooting parameters of camera assembly 2806 based on the intensity of ambient light collected by optical sensor 2815.

A proximity sensor 2816, also referred to as a distance sensor, is typically provided on the front panel of the terminal 2800. The proximity sensor 2816 is configured to collect a distance between a user and the front of the terminal 2800. In one embodiment, when the proximity sensor 2816 detects a gradual decrease in the distance between the user and the front of the terminal 2800, the processor 2801 controls the display 2805 to switch from a bright screen state to a off screen state; when the proximity sensor 2816 detects a gradual increase in the distance between the user and the front of the terminal 2800, the processor 2801 controls the display 2805 to switch from the off-screen state to the on-screen state.

Those skilled in the art will appreciate that the structure shown in fig. 28 is not limiting and that more or fewer components than shown may be included or certain components may be combined or a different arrangement of components may be employed.

Fig. 29 is a schematic structural diagram of a server provided in an embodiment of the present application, where the server 2900 may have a relatively large difference due to configuration or performance, and may include one or more processors (Central Processing Units, CPU) 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 in the foregoing method embodiments. Of course, the server 2900 may also have a wired or wireless network interface, a keyboard, an input/output interface, etc. for inputting/outputting, and the server 2900 may also include other components for implementing the functions of the device, which are not described herein.

In an exemplary embodiment, a computer readable storage medium, such as a memory including instructions executable by a processor to perform the virtual object acquisition method of the above embodiment is also provided. For example, the computer readable storage medium may be Read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), compact disc Read-Only Memory (CD-ROM), magnetic tape, floppy disk, 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 for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the above storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The foregoing description of the preferred embodiments is merely exemplary in nature and is in no way intended to limit the invention, since it is intended that all modifications, equivalents, improvements, etc. that fall within the spirit and scope of the invention.

Claims

1. A method of cell group creation, 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 of claim 1, wherein said releasing the first data synchronization relationship with the target cell group in accordance with a service switching instruction comprises:

3. The method of claim 2, wherein receiving a service switching command when service data synchronization in the new unit group and the target unit group is completed comprises:

4. The method of claim 1, wherein the traffic data for the target traffic type comprises stock data and delta data, the stock data being data for the target traffic type stored by the target unit group prior to the first data synchronization relationship being established, and the delta data being data for the target traffic type stored by the target unit group after the first data synchronization relationship being established.

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

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

6. The method of claim 1, wherein prior to releasing the first data synchronization relationship with the target group of units in accordance with a service switching instruction, the method further comprises:

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

the method further comprises the steps of:

8. The method of claim 1, wherein the set of target units comprises a first unit and a second unit, wherein the first unit is a unit responsible for the target traffic 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:

9. A method of data synchronization, for application to a group of target units, the method comprising:

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

and when the service request of the target service type is received, the new unit group processes the service request to obtain service data, and the service data obtained after processing is synchronized to other units in the new unit group.

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

11. A data synchronization device, characterized in that the device 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, the one or more memories having stored therein at least one instruction loaded and executed by the one or more processors to implement the operations performed by the unit group creation method of any of claims 1 to 8; or operations performed by the data synchronization method of claim 9.

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