WO2023179450A1

WO2023179450A1 - Multi-blockchain collaborative service methods, and systems

Info

Publication number: WO2023179450A1
Application number: PCT/CN2023/081911
Authority: WO
Inventors: 加雄伟
Original assignee: 中国联合网络通信集团有限公司
Priority date: 2022-03-23
Filing date: 2023-03-16
Publication date: 2023-09-28
Also published as: CN114679467A

Abstract

The present disclosure provides multi-blockchain collaborative service methods, and systems, and relates to the technical field of communications. A method comprises: on the basis of a service access request sent by a blockchain client, determining a first edge cloud currently corresponding to the blockchain client; sending first service notification information to a first slave blockchain service system corresponding to the first edge cloud, so that the first slave blockchain service system synchronizes first blockchain service data from a master blockchain service system, and provides a blockchain service for the blockchain client on the basis of the synchronized first blockchain service data; and returning request response information to the blockchain client, so that the blockchain client accesses the first slave blockchain service system on the basis of the request response information. By means of the collaborative operation of the master and slave blockchain service systems, the present disclosure may achieve an elastic, stable, rapid and secure blockchain service, and is suitable for providing the stable, rapid and secure blockchain service for a mobile terminal.

Description

Multi-blockchain collaborative service method and system

Technical field

The present disclosure relates to the field of communication technology, specifically to a multi-blockchain collaborative service method, a master blockchain service system, a slave blockchain service system and a collaborative service system.

Background technique

Nodes of decentralized applications (for example, blockchain applications) are usually deployed on the device side or in the cloud. However, when decentralized applications are deployed on the device side, decentralized applications are susceptible to the impact of device storage, computing, and communication capabilities. When decentralized applications are deployed on the cloud, decentralized applications are susceptible to communication delays and access speeds.

Contents of the invention

To this end, the present disclosure provides a multi-blockchain collaborative service method, a blockchain service system and a collaborative service system to fully leverage the characteristics and service capabilities of edge clouds and core clouds to achieve elastic, stable, fast and secure Blockchain services.

In order to achieve the above purpose, the first aspect of the present disclosure provides a multi-blockchain collaborative service method, which is applied to the main blockchain service system, and the main blockchain service system is deployed in the core cloud; the method includes:

Based on the service access request sent by the blockchain client, determine the first edge cloud currently corresponding to the blockchain client;

Send the first service notification information to the first slave blockchain service system corresponding to the first edge cloud, so that the first slave blockchain service system can synchronize the first zone from the master blockchain service system. Blockchain service data, and provide blockchain services to the blockchain client based on the synchronized first blockchain service data;

Return request response information to the blockchain client, so that the blockchain client can access the first slave blockchain service system based on the request response information.

Optionally, before sending the first service notification information to the first slave blockchain service system corresponding to the first edge cloud, the method further includes:

Determine whether the first edge cloud corresponds to the first slave blockchain service system;

When the first edge cloud does not correspond to a slave blockchain service system, send slave blockchain creation information to the first edge cloud so that the first edge cloud can create the first slave zone. Blockchain service system.

Optionally, after returning the request response information to the blockchain client, the method further includes:

Receive and store the second blockchain service data sent by the first slave blockchain service system; the second blockchain service data is the first slave blockchain service system for the blockchain client. Service data generated during the process of providing blockchain services.

Optionally, the step of determining the first edge cloud currently corresponding to the blockchain client based on the service access request sent by the blockchain client includes:

Obtain the first location information of the blockchain client based on the service access request;

Determine the first edge cloud currently corresponding to the blockchain client based on the first location information.

When the edge cloud corresponding to the blockchain client is changed from the first edge cloud to the second edge cloud, send the second service notification information to the second slave blockchain service system corresponding to the second edge cloud. , for the second slave blockchain service system to synchronize the third blockchain service data from the main blockchain service system, and based on the synchronized third blockchain service data for the block The chain client provides blockchain services;

Return service change reminder information to the blockchain client, so that the blockchain client can access the second slave blockchain service system based on the service change reminder information.

Optionally, when the edge cloud corresponding to the blockchain client is changed from the first edge cloud to the second edge cloud, the second slave blockchain service system corresponding to the second edge cloud Before sending the second service notification information, the method further includes:

Receive the service migration reminder information sent by the first slave blockchain service system, where the service migration reminder information includes migration data and client location change reminder information;

In response to the client location change reminder information, obtain the second location information of the blockchain client, and determine the second edge cloud currently corresponding to the blockchain client based on the second location information.

Optionally, after returning service change reminder information to the blockchain client, the method further includes:

Send service resource clearing information to the first slave blockchain service system, so that the first slave blockchain service system clears the first block synchronized with the main blockchain service system based on the service resource clearing information. Chain service data or release service resources that provide blockchain services to the blockchain client.

The second aspect of this disclosure provides a multi-blockchain collaborative service method, applied to a slave blockchain service system, and the slave blockchain service system is deployed in an edge cloud; the method includes:

In response to the service notification information sent by the main blockchain service system, the blockchain service data is synchronized from the main blockchain service system; the service notification information is based on the pre-received area of the main blockchain service system. Information sent by the service access request sent by the blockchain client;

When the blockchain client corresponding to the service notification information accesses the slave blockchain service system, a blockchain service is provided to the blockchain client based on the synchronized blockchain service data.

Optionally, when the blockchain client corresponding to the service notification information accesses the slave blockchain service system, the blockchain client is provided with the synchronized blockchain service data based on the synchronized blockchain service data. After the blockchain service, the method also includes:

Send service migration reminder information to the main blockchain service system. The service migration reminder information includes migration data and client location change reminder information for the main blockchain service system to determine the blockchain client. When the edge cloud corresponding to the client changes, service notification information is sent to the slave blockchain service system corresponding to the changed edge cloud.

Optionally, after sending the service migration reminder information to the main blockchain service system, the method further includes:

When the blockchain service is stopped for the blockchain client, a destruction operation is performed to release the resources of the edge cloud occupied from the blockchain service system.

The third aspect of the present disclosure provides a main blockchain service system. The main blockchain service system is deployed in the core cloud. The main blockchain service system includes:

A determination module configured to determine the first edge cloud currently corresponding to the blockchain client based on the service access request sent by the blockchain client;

The first sending module is configured to send the first service notification information to the first slave blockchain service system corresponding to the first edge cloud, so that the first slave blockchain service system can obtain the information from the master blockchain. Synchronize the first blockchain service data in the service system, and provide blockchain services to the blockchain client based on the synchronized first blockchain service data;

The second sending module is configured to return request response information to the blockchain client, so that the blockchain client can access the first slave blockchain service system based on the request response information.

A fourth aspect of the present disclosure provides a secondary blockchain service system, which is deployed in an edge cloud. The secondary blockchain service system includes:

A synchronization module configured to synchronize blockchain service data from the main blockchain service system in response to service notification information sent by the main blockchain service system; the service notification information is the main blockchain service system. The service system sends information based on the pre-received service access request sent by the blockchain client;

A processing module configured to, when the blockchain client corresponding to the service notification information accesses the slave blockchain service system, provide the blockchain client with the synchronized blockchain service data based on the synchronized blockchain service data. Provide blockchain services.

The fifth aspect of this disclosure provides a collaborative service system. The collaborative service system includes: at least one blockchain client, a main blockchain service system as provided in the third aspect of this disclosure, and at least one as provided in the fourth aspect of this disclosure. From the blockchain service system.

The multi-blockchain collaborative service method applied to the main blockchain service system provided by the embodiment of the present disclosure first determines the first edge cloud currently corresponding to the blockchain client based on the service access request sent by the blockchain client. ; Then, send the first service notification information to the first slave blockchain service system corresponding to the first edge cloud, so that the first slave blockchain service system can synchronize the first block from the master blockchain service system. chain service data, and provide blockchain services to the blockchain client based on the synchronized first blockchain service data; finally, return request response information to the blockchain client for the blockchain client to use based on the request The response information accesses the first slave blockchain service system, which can realize the coordination of the master blockchain service system and the slave blockchain service system to provide blockchain services for the blockchain client. Moreover, due to the master blockchain service The system is deployed in the core network, while the slave blockchain service system is deployed in the edge cloud network. Therefore, the collaborative work of the master blockchain service system and the slave blockchain service system in this multi-blockchain collaborative service method helps It is designed to give full play to the characteristics and service capabilities of edge clouds and core clouds to achieve flexible, stable, fast and secure blockchain services, and is suitable for providing stable, fast and secure blockchain services for mobile devices.

Description of the drawings

The accompanying drawings are used to provide a further understanding of the present disclosure, and constitute a part of the specification. The embodiments are used together to explain the present disclosure, but do not constitute limitations to the present disclosure.

Figure 1 is a flow chart of a multi-blockchain collaborative service method provided by an embodiment of the present disclosure;

Figure 2 is a flow chart of another multi-blockchain collaborative service method provided by an embodiment of the present disclosure;

Figure 3 is a flow chart of yet another multi-blockchain collaborative service method provided by an embodiment of the present disclosure;

Figure 4 is a schematic structural diagram of a main blockchain service system provided by an embodiment of the present disclosure;

Figure 5 is a schematic structural diagram of a slave blockchain service system provided by an embodiment of the present disclosure;

Figure 6 is a schematic diagram of the system composition of a collaborative service system provided by an embodiment of the present disclosure;

Figure 7 is a schematic diagram of the logical structure of a collaborative service system provided by an embodiment of the present disclosure.

Detailed ways

Specific embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described here are only used to illustrate and explain the present disclosure, and are not intended to limit the present disclosure.

As used in this disclosure, the term "and/or" includes any and all combinations of one or more of the associated listed items.

The terminology used in this disclosure is for describing particular embodiments only and is not intended to limit the disclosure. As used in this disclosure, the singular forms "a," "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

When the terms "comprising" and/or "made of" are used in this disclosure, the presence of the stated features, integers, steps, operations, elements and/or components is specified but does not exclude the presence or addition of one or more other Features, integers, steps, operations, elements, components and/or groups thereof.

Embodiments of the present disclosure may be described with reference to plan and/or cross-sectional illustrations, in conjunction with idealized schematic illustrations of the present disclosure. Accordingly, example illustrations may be modified based on manufacturing techniques and/or tolerances.

Unless otherwise defined, all terms (including technical and scientific terms) used in this disclosure have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be construed to have meanings consistent with their meanings in the context of the relevant art and the present disclosure, and will not be construed as having idealized or excessive formal meanings, Unless the disclosure is expressly so limited.

Figure 1 is a flow chart of a multi-blockchain collaborative service method provided by an embodiment of the present disclosure. Among them, the multi-blockchain includes a master blockchain service system and at least one slave blockchain service system. Among them, the main blockchain service system refers to the basic blockchain service system. The main blockchain service system is used to provide blockchain services to the blockchain client when there is no slave blockchain service system. It is also used To provide data synchronization services for the slave blockchain service system; the slave blockchain service system refers to a dynamic blockchain service system that maintains all or part of the data synchronization with the main blockchain service system , providing blockchain services to blockchain clients; the slave blockchain service system can be dynamically created and destroyed, and the data it saves is dynamically synchronized with the main blockchain service system, and the data can also be dynamically destroyed.

It should be noted that traditional blockchain services are usually deployed on the cloud (cloud side) and/or terminals (device side). When all blockchain nodes of the blockchain service are deployed on the terminal side, the quality and efficiency of network communication between blockchain nodes are usually affected by the network conditions of the terminals where they are located. When blockchain nodes are deployed on the cloud side, the quality and efficiency of network communication between the blockchain client and the blockchain node are usually affected by the network status of the terminal and the service capabilities of the blockchain node and the core cloud. .

Therefore, in the multi-blockchain collaborative service method provided by the embodiments of the present disclosure, the main blockchain service system can be deployed in the core cloud, and the slave blockchain service system can be deployed in the edge cloud close to the blockchain terminal. Blockchain terminal refers to the terminal where blockchain clients or blockchain nodes are deployed. It can be a fixed network terminal or a mobile network terminal. Deploying the blockchain service system in the edge cloud can take advantage of the edge cloud. However, due to the limited storage and communication capabilities and network coverage capabilities of the edge cloud of the communication network, it is difficult to allocate fixed resources (for example, storage space) in each edge cloud to provide blockchain services for each blockchain terminal. Therefore, The slave blockchain service system needs to dynamically synchronize data with the main blockchain service system and dynamically manage the synchronized data in order to provide blockchain services to the blockchain terminal.

The multi-blockchain collaborative service method provided by the embodiment of the present disclosure is applied to the main blockchain service system, and the main blockchain service system is deployed in the core cloud.

As shown in Figure 1, the method includes the following steps S101 to S103.

S101. Based on the service access request sent by the blockchain client, determine the first edge cloud currently corresponding to the blockchain client.

Among them, the blockchain client is the application software for organizations or individuals to participate in blockchain services. The blockchain client is deployed on the blockchain terminal, such as through the blockchain client software development kit (SDK). ) Deploy the blockchain client on the blockchain terminal. Blockchain clients access blockchain services by interacting with blockchain nodes. Blockchain nodes are an integral part of the blockchain service system and are the part that specifically provides blockchain service capabilities. Blockchain nodes collaborate with each other to implement and provide blockchain services. The blockchain service system refers to the application system that provides blockchain services, also known as the blockchain platform. The blockchain node group constitutes the blockchain service system. Blockchain services or applications refer to blockchain model services or applications provided by the blockchain service system.

A service access request is a request sent by a blockchain client to access a blockchain service. The service access request includes: at least one of the blockchain client identifier, the type of requested service, the first location information, and the terminal identifier of the blockchain terminal where the blockchain client is located. Among them, the blockchain client identifier is used to uniquely identify the blockchain client; the type of requested service is, for example, storage type, calculation type, etc.; the first location information is the current location of the blockchain terminal where the blockchain client is located. location information.

In one embodiment, the step of determining the first edge cloud currently corresponding to the blockchain client based on the service access request sent by the blockchain client may further include:

Step 1: Obtain the first location information of the blockchain client based on the service access request.

In some implementations, in the case where the service access request includes the first location information, the main blockchain service system may extract the first location information from the service access request.

In other embodiments, when the service access request does not include the first location information, the main blockchain service system can determine from the terminal identifier included in the service access request that the blockchain terminal corresponding to the blockchain client is located. The communication function entity, for example, the mobility management function entity of the communication network, and then obtains the first location information of the blockchain terminal where the blockchain client is located through the communication function entity.

Step 2: Determine the first edge cloud currently corresponding to the blockchain client based on the first location information.

Among them, the first edge cloud currently corresponding to the blockchain client may be less than a predetermined distance from the blockchain terminal where it is located. The edge cloud with the best performance among all edge clouds at a certain distance may also be the edge cloud closest to the blockchain terminal where the blockchain client is located.

In one implementation, after receiving the service access request sent by the blockchain client, the main blockchain service system can determine whether to support the blockchain service mode of the master-slave collaboration mode based on its own preset service policy. If the main blockchain service system does not support the master-slave collaboration model, the main blockchain service system can directly provide blockchain services to the blockchain client or reject the block. The chain client provides blockchain services. If the master blockchain service system supports the master-slave collaboration mode blockchain service mode, the above step S101 can be executed. Through this implementation, it can be beneficial to improve the breadth of the main blockchain service system to which the multi-blockchain collaborative service method provided by the embodiment of the present disclosure is applied, and it is beneficial to improve the main blockchain service that does not support the master-slave collaboration mode. How efficiently the system handles service access requests.

In one embodiment, after determining the first edge cloud currently corresponding to the blockchain client based on the service access request sent by the blockchain client, the method may further include:

Step 1: Determine whether the first edge cloud corresponds to the first slave blockchain service system.

Wherein, the first slave blockchain service system corresponding to the first edge cloud is a slave blockchain service system deployed in the first edge cloud for providing blockchain services.

Step 2: If the first edge cloud does not correspond to the slave blockchain service system, send the slave blockchain creation information to the first edge cloud so that the first edge cloud can create the first slave blockchain service system.

Among them, the creation information from the blockchain is information used to enable the first edge cloud to create the first slave blockchain service system.

It should be noted that there is a logical entity in the first edge cloud in the embodiment of the present disclosure, and the logical entity can be used to receive and process the information sent by the main blockchain service system for searching, creating, and destroying the slave blockchain service system. The command.

In some embodiments, if the first edge cloud ultimately fails to create the first slave blockchain service system, the master blockchain service system can directly provide blockchain services to the blockchain client, or can refuse to provide blockchain services to the blockchain client. The blockchain client provides blockchain services.

Step 3: If the first edge cloud corresponds to the slave blockchain service system, perform the following step S102.

S102. Send the first service notification information to the first slave blockchain service system corresponding to the first edge cloud, so that the first slave blockchain service system can synchronize the first blockchain service data from the master blockchain service system. , and provide blockchain services to blockchain clients based on synchronized first blockchain service data.

The first service notification information is notification information used to enable the first slave blockchain service system to learn that it needs to provide blockchain services to the blockchain client. The first service notification information may include a blockchain client identifier. , terminal identification and other information of the blockchain terminal where the blockchain client is located.

The first blockchain service data is the data needed to provide blockchain services to the blockchain client from the blockchain service system. The first blockchain service data may include: at least one type of data such as on-chain data, off-chain data, and smart contract data, where the on-chain data refers to the data in the blockchain ledger. Off-chain data refers to data that is related to the data in the blockchain ledger but is stored outside the blockchain ledger. It should be noted that during actual application, the first blockchain service data can further add other relevant data according to actual needs.

S103. Return request response information to the blockchain client for the blockchain client to respond based on the request information. Access the first blockchain service system.

The request response information is information used to instruct the blockchain client to access the first slave blockchain service system to obtain the blockchain service. The request response information may include the first slave blockchain service system identifier, the first slave blockchain service system identifier, and the first slave blockchain service system identifier. Information such as the IP address from the blockchain service system.

In one implementation, the blockchain client accesses the first slave blockchain service system based on the request response information, and the first slave blockchain service system provides the blockchain client with the synchronized first blockchain service data based on the synchronized first blockchain service data. Provides blockchain services on the end.

In one embodiment, after returning the request response information to the blockchain client, during the process of providing blockchain services to the blockchain client from the first slave blockchain service system, the method may further include:

Step 1: Receive and store the second blockchain service data sent from the first blockchain service system. Among them, the second blockchain service data is the first service data generated from the process of providing blockchain services to the blockchain client by the blockchain service system.

Step 2: In response to the data synchronization request sent by the first slave blockchain service system, send the data that needs to be synchronized to the first slave blockchain service system.

It should be noted that the description order of the steps does not constitute a limitation on the execution order of the steps. Through this implementation, the nodes in the first slave blockchain service system can continuously synchronize data with the nodes in the master blockchain service system, so that the first slave blockchain service system provides updated data to the blockchain client. High-quality blockchain service, in which the synchronized data can be the first slave blockchain service system to upload data to the main blockchain service system, or it can be the first slave blockchain service system to upload data from the main blockchain service system Download data.

Figure 2 is a flow chart of another multi-blockchain collaborative service method provided by an embodiment of the present disclosure. In one implementation, after returning the request response information to the blockchain client, as shown in Figure 2, the method further includes: step S201-step S202.

Step S201: When the edge cloud corresponding to the blockchain client is changed from the first edge cloud to the second edge cloud, send the second service notification information to the second slave blockchain service system corresponding to the second edge cloud, For the second slave blockchain service system to synchronize the third blockchain service data from the main blockchain service system and based on the synchronized third block Chain service data provides blockchain services to blockchain clients.

Among them, the second edge cloud can be the edge cloud that is closest to the blockchain terminal after the location of the blockchain terminal where the blockchain client is located changes, or the distance to the blockchain terminal is less than The best performing edge cloud among all edge clouds at a preset distance. The second slave blockchain service system corresponding to the second edge cloud is a slave blockchain service system deployed in the second edge cloud for providing blockchain services.

The third blockchain service data is the data needed to provide blockchain services to the blockchain client from the second blockchain service system.

In some embodiments, the third blockchain service data may include the aforementioned first blockchain service data and second blockchain service data, and may also include migration data from the first slave blockchain service system. This migration data is all data generated by the first blockchain service system in the process of providing blockchain services to blockchain clients.

In some embodiments, the second service notification information may also include the first slave blockchain service system identifier, so that the second slave blockchain service system can combine the first slave blockchain service system identifier with the first slave blockchain service system based on the first slave blockchain service system identifier. The blockchain service system interacts to obtain the migration data from the first slave blockchain service system.

It should be noted that when the second edge cloud does not correspond to the second slave blockchain service system, the main blockchain service system can also instruct the second edge cloud to build the corresponding second slave blockchain service system. , for the specific process, please refer to the relevant description of the first edge cloud creating the first slave blockchain service system in the previous embodiment, and will not be described again here.

In one embodiment, when the edge cloud corresponding to the blockchain client is changed from the first edge cloud to the second edge cloud, the second service is sent to the second slave blockchain service system corresponding to the second edge cloud. Before notifying the information, the method may further include:

Step 1: Receive the service migration reminder message sent from the first blockchain service system.

Among them, the service migration reminder information includes migration data and client location change reminder information. This migration data is all data generated by the first blockchain service system in the process of providing blockchain services to blockchain clients.

Step 2: In response to the client location change reminder information, obtain the second location information of the blockchain client, and determine the second edge cloud currently corresponding to the blockchain client based on the second location information.

The second location information is the current location information of the blockchain terminal where the blockchain client is located after the location change occurs. The second edge cloud currently corresponding to the blockchain client may be the edge cloud currently closest to the blockchain terminal where the blockchain client is located, or all edges that are less than a preset distance from the blockchain terminal. The best-performing edge cloud in the cloud.

In another implementation, the main blockchain service system can dynamically track the location change information of the blockchain terminal where the blockchain client is located, and determine in a timely manner whether the edge cloud corresponding to the blockchain client has been changed from the first edge cloud. It is the second edge cloud.

In another embodiment, the blockchain terminal where the blockchain client is located can reconnect to the main area based on changes in its own location and the quality of the accessed blockchain services, and based on the current corresponding second location information of the blockchain terminal. The blockchain service system, or, sends location change reminder information to the main blockchain service system to facilitate migration to a more appropriate slave blockchain service system in the edge cloud.

Step S202: Return service change reminder information to the blockchain client so that the blockchain client can provide services based on The change reminder information is accessed from the second slave blockchain service system.

Among them, the service change reminder information is a reminder information used to indicate to the blockchain client that the blockchain service provider has changed. The service change reminder information may include the second slave blockchain service system identifier, the IP address information of the second slave blockchain service system, etc.

In one embodiment, after returning the service change reminder information to the blockchain client, the method may further include: sending service resource clearing information to the first slave blockchain service system for the first slave blockchain The service system clears the first blockchain service data synchronized with the main blockchain service system based on the service resource clearing information or releases the service resources that provide blockchain services for the blockchain client.

Among them, the service resource clearing information is used to enable the first slave blockchain service system to clear the first blockchain service data synchronized with the main blockchain service system or to release services that provide blockchain services to blockchain clients. The instruction information of the resource, that is, the service resource clearing information, is an instruction for causing the first slave blockchain service system to destroy data according to the service policy or to destroy the first slave blockchain service system.

In another embodiment, when the first slave blockchain service system stops providing blockchain services to any blockchain client, the first slave blockchain service system can actively destroy data and data according to the service policy. First from the blockchain service system.

In one implementation, a blockchain client may move from one edge cloud service area to another edge cloud service area. But in special cases, for example, when the blockchain client is at the intersection of multiple edge cloud service areas, or the blockchain terminal where the blockchain client is located moves quickly, it may occur within a short period of time. When spanning multiple edge cloud service areas, a slave blockchain service system and corresponding slave blockchain nodes can be established in each edge cloud, and the newly generated slave blockchain service system and corresponding slave blockchain Nodes can be treated equally. At this time, when the successor location of the blockchain client is determined, the original and other newly generated slave blockchain service systems and blockchain nodes can be automatically or passively destroyed to release the corresponding edge cloud. Resources are reserved for other blockchain clients to provide blockchain services.

It should be noted that a slave blockchain service system and slave blockchain node can simultaneously provide services for blockchain clients corresponding to multiple edge clouds. That is to say, when the location of the blockchain client changes and moves from one edge cloud to another, if the slave blockchain service system and slave blockchain nodes that provide blockchain services do not change, there is no need to re- Find and create new slave blockchain service systems.

The multi-blockchain collaborative service method provided by the disclosed embodiment deploys a master blockchain service system in the core cloud, deploys a slave blockchain service system in the edge cloud, and the master blockchain service system and slave blockchain services The system collaborates to provide blockchain services for blockchain terminals (clients). In different edge clouds, different slave blockchain service systems can be deployed, and these slave blockchain service systems can synchronize data with the main blockchain service system. This disclosed embodiment focuses on the data collaboration between the master blockchain service system and the slave blockchain service system, and provides blockchain services to blockchain terminals (clients) in a master-slave collaboration manner. Among them, the slave blockchain service system can be dynamically created and destroyed, and the blockchain nodes and data of the slave blockchain service system can also be dynamically created and destroyed. When the blockchain client accesses the blockchain service, it can dynamically migrate from one slave blockchain service system to another slave blockchain service system according to the situation (for example, the location changes). At this time, the two slave blockchain service systems The blockchain service system can provide seamless blockchain service connection.

Figure 3 is a flow chart of yet another multi-blockchain collaborative service method provided by an embodiment of the present disclosure. This multi-blockchain collaborative service method is applied to a slave blockchain service system, which is deployed in the edge cloud. It should be noted that the slave blockchain service system may be the third one in the aforementioned embodiment. The first slave blockchain service system can also be the second slave blockchain service system. As shown in Figure 3, the method includes: step S301-step S302.

Step S301: In response to the service notification information sent by the main blockchain service system, synchronize the blockchain service data from the main blockchain service system.

Among them, the service notification information is information sent by the main blockchain service system based on the service access request sent by the blockchain client received in advance. The service notification information may include the blockchain client identifier, the terminal identifier of the blockchain terminal where the blockchain client is located, and other information. Blockchain service data is the data needed to provide blockchain services to the blockchain client from the blockchain service system. The blockchain service data may include at least one type of data such as on-chain data, off-chain data, and smart contract data, where the on-chain data refers to the data in the blockchain ledger. Off-chain data refers to data that is related to the data in the blockchain ledger but is stored outside the blockchain ledger. It should be noted that during actual application, the first blockchain service data can further add other relevant data according to actual needs.

Step S302: When the blockchain client corresponding to the service notification information accesses the slave blockchain service system, provide blockchain services to the blockchain client based on the synchronized blockchain service data.

In one embodiment, in the process of providing blockchain services to blockchain clients based on synchronized blockchain service data, the slave blockchain service system can dynamically track the location of the blockchain terminal where the blockchain client is located. Location change information to determine whether the blockchain terminal where the blockchain client is located has moved to other edge clouds.

In one embodiment, when the blockchain client corresponding to the service notification information accesses the slave blockchain service system, after providing the blockchain service to the blockchain client based on the synchronized blockchain service data, The method may further include:

When the blockchain terminal where the blockchain client is located moves to another edge cloud, service migration reminder information is sent to the main blockchain service system. The service migration reminder information can include migration data and client location change reminder information. , so that when the main blockchain service system determines that the edge cloud corresponding to the blockchain client has changed, it can send service notification information to the slave blockchain service system corresponding to the changed edge cloud.

Among them, migration data is all data generated from the process of providing blockchain services to blockchain clients by the blockchain service system. The client location change reminder information is used to remind the main blockchain service system that the location of the blockchain terminal where the blockchain client is located has changed, so that the main blockchain service system can obtain the area in response to the client location change reminder information. The current location information of the blockchain terminal where the blockchain client is located, and the current corresponding edge cloud of the blockchain client is determined based on the current location information of the blockchain terminal where the blockchain client is located, and then the main blockchain service The system sends service change reminder information to the blockchain client so that the blockchain client can access other slave blockchain service systems based on the service change reminder information.

In one implementation, after sending the service migration reminder information to the main blockchain service system, the method may further include: when stopping providing blockchain services to the blockchain client, performing a destruction operation to Release edge cloud resources occupied from the blockchain service system.

The multi-blockchain collaborative service method applied to the slave blockchain service system provided by the embodiment of the present disclosure, first of all, affects Synchronize the blockchain service data from the main blockchain service system in response to the service notification information sent by the main blockchain service system, where the service notification information is based on the blockchain client received in advance by the main blockchain service system The information sent by the service access request is sent; then, when the blockchain client corresponding to the service notification information accesses the slave blockchain service system, the blockchain client is provided with a zone based on the synchronized blockchain service data. Blockchain services can realize the collaboration between the main blockchain service system and the slave blockchain service system to provide blockchain services for blockchain clients. Moreover, since the main blockchain service system is deployed in the core network, The slave blockchain service system is deployed in the edge cloud network. Therefore, the collaborative work of the master blockchain service system and the slave blockchain service system in this multi-blockchain collaborative service method helps to give full play to the edge cloud and core cloud. Features and service capabilities to achieve flexible, stable, fast and secure blockchain services, suitable for providing stable, fast and secure blockchain services for mobile devices.

The steps of the various methods above are divided just for the purpose of clear description. During implementation, they can be combined into one step or some steps can be split into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. ; Adding insignificant modifications or introducing insignificant designs to the algorithm or process without changing the core design of the algorithm and process are within the scope of protection of this patent.

Figure 4 is a schematic structural diagram of a main blockchain service system provided by an embodiment of the present disclosure. The main blockchain service system is deployed in the core cloud. As shown in Figure 4, the main blockchain service system 40 includes: a determination module 41, a first sending module 42 and a second sending module 43.

Among them, the determination module 41 is configured to determine the first edge cloud currently corresponding to the blockchain client based on the service access request sent by the blockchain client.

The first sending module 42 is configured to send the first service notification information to the first slave blockchain service system corresponding to the first edge cloud, so that the first slave blockchain service system can obtain the information from the master blockchain service system. Synchronize the first blockchain service data, and provide blockchain services to the blockchain client based on the synchronized first blockchain service data.

The second sending module 43 is configured to return request response information to the blockchain client, so that the blockchain client can access the first slave blockchain service system based on the request response information.

In one implementation, the main blockchain service system may further include a first judgment module.

Wherein, the first judgment module is configured to judge whether the first edge cloud corresponds to the first slave blockchain service system.

The above-mentioned first sending module 42 is also configured to send the slave blockchain creation information to the first edge cloud when the first edge cloud does not correspond to the slave blockchain service system, so that the first edge cloud can create the second blockchain service system. One from the blockchain service system.

In one embodiment, the main blockchain service system 40 may further include a first receiving module and a first storage module. The first receiving module is configured to receive the second blockchain service data sent by the first slave blockchain service system, wherein the second blockchain service data is the first slave blockchain service system for the blockchain client. Service data generated during the process of providing blockchain services. The first storage module is configured to store the second blockchain service data.

In one embodiment, the above-mentioned determination module 41 is configured to obtain the first location information of the blockchain client based on the service access request; and determine the first edge cloud currently corresponding to the blockchain client based on the first location information.

In one embodiment, the above-mentioned first sending module 42 is also configured to send a message to the third edge cloud corresponding to the second edge cloud when the edge cloud corresponding to the blockchain client is changed from the first edge cloud to the second edge cloud. The second slave blockchain service system sends the second service notification information for the second slave blockchain service system to synchronize the third slave blockchain service system with the main blockchain service system. Blockchain service data, and provide blockchain services to the blockchain client based on the synchronized third blockchain service data. The above-mentioned second sending module 43 is also configured to return service change reminder information to the blockchain client, so that the blockchain client can access the second slave blockchain service system based on the service change reminder information.

In one implementation, the main blockchain service system 40 may further include a first acquisition module.

The above-mentioned first receiving module is also configured to receive the first service migration reminder information sent from the blockchain service system. The service migration reminder information may include migration data and client location change reminder information.

The first acquisition module is configured to acquire the second location information of the blockchain client in response to the client location change reminder information.

The above-mentioned determination module 41 is also configured to determine the second edge cloud currently corresponding to the blockchain client based on the second location information.

In one embodiment, the above-mentioned first sending module 42 is also configured to send service resource clearing information to the first slave blockchain service system, so that the first slave blockchain service system clears the slave master based on the service resource clearing information. The first blockchain service data synchronized by the blockchain service system or the service resources that provide blockchain services for the blockchain client are released.

To be clear, the present disclosure is not limited to the specific configurations and processes described in the embodiments above and illustrated in the figures. For the convenience and simplicity of description, detailed descriptions of known methods are omitted here, and for the specific working processes of the systems, modules and units described above, reference can be made to the corresponding processes in the foregoing method embodiments, which will not be described again here.

In the main blockchain service system provided by the embodiment of the present disclosure, the determination module is configured to determine the first edge cloud currently corresponding to the blockchain client based on the service access request sent by the blockchain client; the first sending module is configured To send the first service notification information to the first slave blockchain service system corresponding to the first edge cloud, so that the first slave blockchain service system can synchronize the first blockchain service from the master blockchain service system. data, and provide blockchain services to the blockchain client based on the synchronized first blockchain service data; the second sending module is configured to return request response information to the blockchain client for the blockchain client Accessing the first slave blockchain service system based on the request response information can realize the coordination of the master blockchain service system and the slave blockchain service system to provide blockchain services to the blockchain client, and, because the master zone The blockchain service system is deployed in the core network, while the slave blockchain service system is deployed in the edge cloud network. Therefore, the collaborative work of the master blockchain service system and the slave blockchain service system in the embodiment of the present disclosure is helpful Give full play to the characteristics and service capabilities of the edge cloud and core cloud to achieve flexible, stable, fast and secure blockchain services. It is suitable for providing stable, fast and secure blockchain services for mobile devices.

Figure 5 is a schematic structural diagram of a slave blockchain service system provided by an embodiment of the present disclosure. The slave blockchain service system is deployed in the edge cloud. As shown in Figure 5, the slave blockchain service system 50 includes: a synchronization module 51 and a processing module 52.

Among them, the synchronization module 51 is configured to synchronize the blockchain service data from the main blockchain service system in response to the service notification information sent by the main blockchain service system.

Among them, the service notification information is information sent by the main blockchain service system based on the service access request sent by the blockchain client received in advance.

The processing module 52 is configured to provide blockchain services to the blockchain client based on the synchronized blockchain service data when the blockchain client corresponding to the service notification information accesses the slave blockchain service system. .

In one embodiment, the slave blockchain service system 50 may further include a third sending module. The third sending module is configured to send service migration reminder information to the main blockchain service system. The service migration reminder information includes migration data and client location change reminder information for the main blockchain service system to determine the blockchain. When the edge cloud corresponding to the client changes, service notification information is sent to the slave blockchain service system corresponding to the changed edge cloud.

In one embodiment, the slave blockchain service system 50 may further include an active clearing module. The active clearing module is configured to perform a destruction operation to release the resources of the edge cloud occupied by the blockchain service system when the blockchain service system stops providing blockchain services to the blockchain client.

In the slave blockchain service system provided by the embodiment of the present disclosure, the synchronization module is configured to respond to the service notification information sent by the master blockchain service system, and synchronize the blockchain service data from the master blockchain service system, where, the service The notification information is information sent by the main blockchain service system based on the service access request sent by the blockchain client received in advance; the processing module is configured to access the slave blockchain service on the blockchain client corresponding to the service notification information. In the case of the system, blockchain services are provided to the blockchain client based on synchronized blockchain service data, which can realize the collaboration between the main blockchain service system and the slave blockchain service system to provide blockchain clients with Blockchain service, and because the main blockchain service system is deployed in the core network and the slave blockchain service system is deployed in the edge cloud network, therefore, in the embodiment of the present disclosure, the main blockchain service system and the slave area The collaborative work of the blockchain service system helps to give full play to the characteristics and service capabilities of the edge cloud and core cloud to achieve flexible, stable, fast and secure blockchain services, which is suitable for providing stable, fast and secure mobile devices. Blockchain services.

Figure 6 is a schematic diagram of the system composition of a collaborative service system provided by an embodiment of the present disclosure. The collaborative service system includes: at least one blockchain client 61, at least one master blockchain service system 62, and at least one slave blockchain service system 63.

Among them, the blockchain client 61 is deployed on a blockchain terminal, such as a computer, a mobile phone, etc. Each main blockchain service system 62 is deployed on the core cloud, and communication connections can be made between each main blockchain service system 62. Each slave blockchain service system 63 is deployed on the edge cloud, and each slave blockchain service system 63 can interact with each other through the master blockchain service system 62 or directly.

It should be noted that the working methods of the blockchain client, the main blockchain service system and the slave blockchain service system are detailed in the relevant descriptions in the foregoing embodiments, and will not be described again here.

Figure 7 is a schematic diagram of the logical structure of a collaborative service system provided by an embodiment of the present disclosure. The collaborative service system includes: at least one blockchain client 61, at least one master blockchain service system 62, and at least one slave blockchain service system 63.

Among them, the blockchain client 61 is deployed on the blockchain terminal. The blockchain client SDK is also included on this blockchain terminal. The logical architecture of the master-slave blockchain is transparent to the blockchain client 61 or blockchain terminal. The blockchain client 61 can connect to the designated blockchain service system according to designated information (such as the IP address, port, etc. of the blockchain service system) or its own location information to obtain blockchain services. For the blockchain client 61, there is no need to know whether the main blockchain service system or the slave blockchain service system is providing blockchain services.

In one implementation, the main blockchain service system 62 may include: a first on-chain data synchronization module 621, a first off-chain data synchronization module 622, a first contract synchronization module 623, a first master-slave collaboration module 624, At least one of the blockchain service capability modules 625. The master blockchain service system 62 can adopt the same or similar data storage mode as the slave blockchain service system 63. The stored data includes on-chain data, off-chain data, smart contract data, etc.

Among them, the first on-chain data synchronization module 621 is configured to support interaction with the second on-chain data synchronization module of the slave blockchain service system 63 (or the slave blockchain node in the slave blockchain service system) to Realize on-chain data synchronization (all or part of the on-chain data) with the slave blockchain service system 63. On-chain data usually refers to data in the blockchain ledger. This synchronization refers to the downloading of on-chain data from the slave blockchain node of the blockchain service system 63 from the master blockchain node of the master blockchain service system 62, and the downloading of on-chain data from the slave blockchain node of the blockchain service system 63. The node uploads on-chain data to the main blockchain node of the main blockchain service system 62 .

In some embodiments, when synchronizing on-chain data between the master and slave blockchain service systems, the slave blockchain service system 63 needs to submit the range of synchronized on-chain data (for example, time) to the master blockchain service system 62 scope, regional scope, user scope, etc.), and whether to upload or download, etc. When synchronizing data, the master-slave blockchain service system requires mutual identity authentication and data verification to ensure the security of the data and system.

The first off-chain data synchronization module 622 is configured to support interaction with the second off-chain data synchronization module of the slave blockchain service system to achieve off-chain data synchronization of the blockchain (all or part of the off-chain data). Off-chain data usually refers to data outside the blockchain ledger, which is in turn correlated with data in the blockchain ledger. This synchronization refers to downloading off-chain data from the blockchain service system to the main blockchain service system, and uploading off-chain data from the blockchain service system to the main blockchain service system. When synchronizing off-chain data between the master and slave blockchain service systems, the slave blockchain service system needs to submit the scope of synchronized off-chain data to the master blockchain service system (for example, time range, regional range, user range, etc. ), and whether to upload or download, etc. When synchronizing data, the master-slave blockchain service system requires mutual identity authentication and data verification to ensure the security of the data and system. When the on-chain data of the master-slave blockchain service system is synchronized, the corresponding off-chain data also needs to be synchronized.

The first contract synchronization module 623 supports synchronization of smart contracts with slave blockchain nodes of the slave blockchain service system to achieve synchronization of smart contracts of the master-slave blockchain service system. Generally speaking, smart contracts can be deployed on the main blockchain service system first or on the slave blockchain service system first. Synchronize smart contracts and related information between master-slave blockchain service systems.

The first master-slave collaboration module 624 is configured to dynamically notify the edge cloud to create a slave blockchain service system and its blockchain nodes according to the service access request of the blockchain client (including service type, location information and other information), and Notifications provide blockchain services to blockchain clients from the blockchain service system and its blockchain nodes. It should be noted, In the edge cloud, there is a logical entity that can receive the control information of the first master-slave collaboration module 624, and create and configure the slave blockchain service system and its blockchain nodes according to the control information. When the slave blockchain service system and its blockchain nodes After the creation and configuration of the blockchain node is completed, the slave blockchain service system and its blockchain nodes can collaborate with the main blockchain service system. The logical entity in the edge cloud can also receive other control information from the first master-slave collaboration module 624 to add or destroy slave blockchain nodes or slave blockchain service systems.

The first blockchain service capability module 625 is configured to provide blockchain-related service capabilities (service capabilities of the traditional blockchain itself), including interaction capabilities with blockchain nodes of other main blockchain service systems, etc. .

In one embodiment, the slave blockchain service system 63 includes: a second on-chain data synchronization module 631, a second off-chain data synchronization module 632, a second contract synchronization module 633, a synchronization management module 634, and a data migration module 635. The second blockchain service capability module 636. The master blockchain service system 62 and the slave blockchain service system 63 adopt the same or similar data storage mode, and the stored data includes on-chain data, off-chain data, smart contract data, etc. Data can be synchronized between different slave blockchain service systems 63, and the same or similar data storage mode is also adopted between each slave blockchain service system 63.

The second on-chain data synchronization module 631 supports interaction with the first on-chain data synchronization module of the main blockchain service system to achieve on-chain data synchronization with the main blockchain service system. This synchronization includes downloading on-chain data from the main blockchain node and uploading on-chain data to the main blockchain node.

The second off-chain data synchronization module 632 supports interaction with the first off-chain data synchronization module of the master blockchain service system to achieve off-chain data synchronization with the master-slave blockchain service system. Among them, this synchronization refers to downloading off-chain data from the main blockchain node and uploading off-chain data to the main blockchain node.

The second contract synchronization module 633 supports smart contract synchronization with the main blockchain node of the main blockchain service system to achieve synchronization of smart contracts in the master-slave blockchain service system.

The data migration module 635 supports synchronous data migration with other slave blockchain service systems except the slave blockchain service system. Synchronized migration data includes on-chain data, off-chain data, contract data, and service site data. Among them, the service site data is the context information generated by the slave blockchain service system when it provides blockchain services to the blockchain client, such as operating parameters, environment variables and other information. This context information can be synchronized between different slave blockchain service systems to provide seamless blockchain services when the blockchain client migrates. Information can be synchronized directly between different slave blockchain service systems, or it can be transferred through the main blockchain service system.

The synchronization management module 634 is configured to control data synchronization with the main blockchain service system or data migration with other slave blockchain service systems based on the location change reminder information sent by the blockchain client.

The second blockchain service capability module 636 provides blockchain-related service capabilities (service capabilities of the traditional blockchain itself), including interaction capabilities with other main blockchain service systems. It should be noted that the master-slave blockchain service system has the ability to provide the same blockchain services.

Those of ordinary skill in the art can understand that all or some steps, systems, and functional modules/units in the devices disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may consist of several physical components. Components execute cooperatively. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit . Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is known to those of ordinary skill in the art, the term computer storage media includes volatile and nonvolatile media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. removable, removable and non-removable media. Computer storage media includes but is not limited to Random Access Memory (RAM, abbreviated as RAM, more specifically Synchronous Dynamic Random-Access Memory, abbreviated as SDRAM, Double Data Rate SDRAM, abbreviated as DDR, etc.), Read-Only Memory (Read-Only Memory) , abbreviated ROM), Electrically Erasable Programmable read only memory (EEPROM), flash memory (FLASH) or other memory technology, Compact Disc Read-Only Memory (CD-ROM) , Digital Video Disc (DVD) or other optical disk storage, magnetic cassette, tape, disk storage or other magnetic storage device, or any other medium that can be used to store the desired information and can be accessed by a computer. Additionally, it is known to those of ordinary skill in the art that communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

It should be noted that, in this document, the terms "comprising", "comprising" or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or device that includes a series of elements not only includes those elements, It also includes other elements not expressly listed or inherent in the process, method, article or apparatus. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or device that includes that element.

Those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the present embodiments. within and form different embodiments.

It can be understood that the above embodiments are only exemplary embodiments adopted to illustrate the principles of the present disclosure, but the present disclosure is not limited thereto. For those of ordinary skill in the art, various modifications and improvements can be made without departing from the spirit and essence of the disclosure, and these modifications and improvements are also regarded as the protection scope of the disclosure.

Claims

A multi-blockchain collaborative service method, applied to the main blockchain service system, the main blockchain service system is deployed in the core cloud; the method includes:

Based on the service access request sent by the blockchain client, determine the first edge cloud currently corresponding to the blockchain client;

Send the first service notification information to the first slave blockchain service system corresponding to the first edge cloud, so that the first slave blockchain service system can synchronize the first zone from the master blockchain service system. Blockchain service data, and provide blockchain services to the blockchain client based on the synchronized first blockchain service data;

Return request response information to the blockchain client, so that the blockchain client can access the first slave blockchain service system based on the request response information.
The method according to claim 1, wherein before sending the first service notification information to the first slave blockchain service system corresponding to the first edge cloud, the method further includes:

Determine whether the first edge cloud corresponds to the first slave blockchain service system;

When the first edge cloud does not correspond to a slave blockchain service system, send slave blockchain creation information to the first edge cloud so that the first edge cloud can create the first slave zone. Blockchain service system.
The method according to claim 1, wherein after the request response information is returned to the blockchain client, the method further includes:

Receive and store the second blockchain service data sent by the first slave blockchain service system; the second blockchain service data is the first slave blockchain service system for the blockchain client. Service data generated during the process of providing blockchain services.
The method according to claim 1, wherein the step of determining the first edge cloud currently corresponding to the blockchain client based on the service access request sent by the blockchain client includes:

Obtain the first location information of the blockchain client based on the service access request;

Determine the first edge cloud currently corresponding to the blockchain client based on the first location information.
The method according to claim 1, wherein after the request response information is returned to the blockchain client, the method further includes:

When the edge cloud corresponding to the blockchain client is changed from the first edge cloud to the second edge cloud, send the second service notification information to the second slave blockchain service system corresponding to the second edge cloud. , for the second slave blockchain service system to synchronize the third blockchain service data from the main blockchain service system, and based on the synchronized third blockchain service data for the block The chain client provides blockchain services;

Return service change reminder information to the blockchain client for the blockchain client to use the service based on the The change reminder information accesses the second slave blockchain service system.
The method according to claim 5, wherein when the edge cloud corresponding to the blockchain client is changed from the first edge cloud to the second edge cloud, the second edge cloud corresponding to the second edge cloud is Before sending the second service notification information from the blockchain service system, the method further includes:

Receive the service migration reminder information sent by the first slave blockchain service system, where the service migration reminder information includes migration data and client location change reminder information;

In response to the client location change reminder information, obtain the second location information of the blockchain client, and determine the second edge cloud currently corresponding to the blockchain client based on the second location information.
The method according to claim 5, wherein after returning service change reminder information to the blockchain client, the method further includes:

Send service resource clearing information to the first slave blockchain service system, so that the first slave blockchain service system clears the first synchronized data from the main blockchain service system based on the service resource clearing information. Blockchain service data or release service resources that provide blockchain services for the blockchain client.
A multi-blockchain collaborative service method, applied to a slave blockchain service system deployed in an edge cloud; the method includes:

In response to the service notification information sent by the main blockchain service system, the blockchain service data is synchronized from the main blockchain service system; the service notification information is based on the pre-received area of the main blockchain service system. Information sent by the service access request sent by the blockchain client;

When the blockchain client corresponding to the service notification information accesses the slave blockchain service system, a blockchain service is provided to the blockchain client based on the synchronized blockchain service data.
The method according to claim 8, wherein when the blockchain client corresponding to the service notification information accesses the slave blockchain service system, the synchronized blockchain service data is the After the blockchain client provides the blockchain service, the method further includes:

Send service migration reminder information to the main blockchain service system. The service migration reminder information includes migration data and client location change reminder information for the main blockchain service system to determine the blockchain client. When the edge cloud corresponding to the client changes, service notification information is sent to the slave blockchain service system corresponding to the changed edge cloud.
The method according to claim 9, wherein after sending service migration reminder information to the main blockchain service system, the method further includes:

When the blockchain service is stopped for the blockchain client, a destruction operation is performed to release the resources of the edge cloud occupied from the blockchain service system.
A main blockchain service system, the main blockchain service system is deployed in the core cloud, the main blockchain service system includes:

A determination module configured to determine the first edge cloud currently corresponding to the blockchain client based on the service access request sent by the blockchain client;

The first sending module is configured to send the first service notification information to the first slave blockchain service system corresponding to the first edge cloud, so that the first slave blockchain service system can obtain the information from the master blockchain. Synchronize the first blockchain service data in the service system, and provide blockchain services to the blockchain client based on the synchronized first blockchain service data;

The second sending module is configured to return request response information to the blockchain client, so that the blockchain client can access the first slave blockchain service system based on the request response information.
A slave blockchain service system, the slave blockchain service system is deployed in the edge cloud, and the slave blockchain service system includes:

A synchronization module configured to synchronize blockchain service data from the main blockchain service system in response to service notification information sent by the main blockchain service system; the service notification information is the main blockchain service system. The service system sends information based on the pre-received service access request sent by the blockchain client;

A processing module configured to, when the blockchain client corresponding to the service notification information accesses the slave blockchain service system, provide the blockchain client with the synchronized blockchain service data based on the synchronized blockchain service data. Provide blockchain services.
A collaborative service system, the collaborative service system includes: at least one blockchain client, the master blockchain service system as claimed in claim 11, and at least one slave blockchain service system as claimed in claim 12 .