CN113612854B - Communication method, server and terminal based on block chain - Google Patents
Communication method, server and terminal based on block chain Download PDFInfo
- Publication number
- CN113612854B CN113612854B CN202110936643.7A CN202110936643A CN113612854B CN 113612854 B CN113612854 B CN 113612854B CN 202110936643 A CN202110936643 A CN 202110936643A CN 113612854 B CN113612854 B CN 113612854B
- Authority
- CN
- China
- Prior art keywords
- terminal
- blockchain
- edge node
- service
- dynamic
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a communication method, a server and a terminal based on a block chain, wherein the method comprises the following steps: acquiring attribute information of a terminal and first position information between the terminal and a current edge cloud server; determining whether a dynamic edge node based on a block chain needs to be established according to the processing capacity of the current edge cloud server, the attribute information of the terminal and the first position information; under the condition that the dynamic edge node is determined to be established, establishing the dynamic edge node according to a service strategy; and sending synchronous data to the dynamic edge node so that the dynamic edge node provides the blockchain service for the terminal. The dynamic edge node is established according to the service strategy, so that the dynamic edge node can provide communication service for the terminal more quickly, and the communication efficiency between the terminal and the dynamic edge node is improved; and sending synchronous data to the dynamic edge node, so that the dynamic edge node is familiar with the block chain service content of the terminal, and the service quality of the terminal is improved.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a blockchain-based communications method, a server, and a terminal.
Background
The blockchain nodes corresponding to conventional de-centralized applications (e.g., blockchain applications) are typically deployed on the cloud server side or terminal side. When the blockchain nodes are all deployed on the terminal side, the quality and efficiency of network communications between the blockchain nodes is typically affected by the network conditions in which the terminal side is located and the processing capabilities of the terminal (e.g., storage, computing, and communication capabilities of the terminal, etc.). When the blockchain nodes are all deployed on the cloud server side, the communication quality and efficiency between the terminal and the blockchain nodes are generally affected by the service capability of the blockchain nodes and the service capability of the core cloud server. For example, if the blockchain node has limited service capability and needs to process large data volume of communication data, the communication quality and communication efficiency between the terminal and the blockchain node are susceptible to communication delay and data access speed.
How to improve the communication efficiency between the terminal and the blockchain node and ensure the communication quality of the terminal becomes a technical problem to be solved in the art.
Disclosure of Invention
Therefore, the application provides a communication method, a server and a terminal based on a block chain, which solve the problem of how to improve the communication efficiency between the terminal and a block chain node and ensure the service quality of the terminal.
To achieve the above object, a first aspect of the present application provides a blockchain-based communication method, including: acquiring attribute information of a terminal and first position information between the terminal and a current edge cloud server; determining whether a dynamic edge node based on a block chain needs to be established according to the processing capacity of the current edge cloud server, the attribute information of the terminal and the first position information; under the condition that the dynamic edge node is determined to be established, establishing the dynamic edge node according to a service strategy; and sending synchronous data to the dynamic edge node so that the dynamic edge node provides the blockchain service for the terminal.
In some implementations, the service policy includes: a nearby principals policy or a performance priority policy;
under the condition that the dynamic edge node is determined to be established, establishing the dynamic edge node according to the service strategy comprises the following steps:
under the condition that the dynamic edge node is required to be established, the dynamic edge node is established according to a nearby principle policy or a performance priority policy.
In some implementations, obtaining attribute information of a terminal and first location information between the terminal and a current edge cloud server includes:
receiving a service request sent by a terminal;
And carrying out message analysis on the service request to obtain attribute information and first position information of the terminal.
In some implementations, after performing data synchronization with the dynamic edge node to enable the dynamic edge node to provide the blockchain service for the terminal, the method further includes:
acquiring second position information after the terminal is changed under the condition that the position information of the terminal is determined to be changed;
acquiring a change request sent by a terminal, wherein the change request is used for requesting to change an edge cloud server providing communication service for the terminal;
notifying a first dynamic edge node to migrate the blockchain data corresponding to the terminal to a second dynamic edge node, wherein the first dynamic edge node is an edge node for providing blockchain service for the terminal under the condition that the terminal is in first position information; the second dynamic edge node is an edge node for providing block chain service for the terminal under the condition that the terminal is in second position information;
and sending the information of the second dynamic edge node to the terminal so that the terminal can communicate with the second dynamic edge node.
In some implementations, after performing data synchronization with the dynamic edge node to enable the dynamic edge node to provide the blockchain service for the terminal, the method further includes:
And under the condition that the dynamic edge node is determined to be a pre-established node and the service request sent by the terminal is not received within the preset time, sending a deleting message to the dynamic edge node so that the dynamic edge node deletes the blockchain data corresponding to the terminal.
In some implementations, after performing data synchronization with the dynamic edge node to enable the dynamic edge node to provide the blockchain service for the terminal, the method further includes:
destroying the dynamic edge nodes.
In some implementations, the blockchain data corresponding to the terminal includes: and the service data corresponds to the terminal and/or the service data corresponds to the terminal.
To achieve the above object, a second aspect of the present application provides a blockchain-based communication method, including: acquiring first position information between a current terminal and an edge cloud server; generating a service request according to the first position information and the attribute information of the current terminal; and sending a service request to the edge cloud server so that the edge cloud server establishes a dynamic edge node according to the first position information, the attribute information of the current terminal and the service policy, and sending synchronous data to the dynamic edge node by the edge cloud server so that the dynamic edge node provides blockchain service for the terminal.
In some implementations, after sending the service request to the edge cloud server, further comprising:
and under the condition that the distance between the current terminal and at least two edge cloud servers is the same or similar, communicating with at least two edge cloud servers.
In some implementations, after sending the service request to the edge cloud server, further comprising:
acquiring real-time position information of a current terminal;
under the condition that the real-time position information of the current terminal is determined to be changed, acquiring second position information after the current terminal is changed;
searching a plurality of edge cloud servers in a preset range according to the second position information;
acquiring a first edge cloud server corresponding to the first position information;
under the condition that the first edge cloud server is determined not to be in a plurality of edge cloud servers in a preset range, determining that the edge cloud server corresponding to the current terminal needs to be changed;
and sending a change request to the first edge cloud server.
To achieve the above object, a third aspect of the present application provides an edge cloud server, including: the acquisition module is configured to acquire attribute information of the terminal and first position information between the terminal and the current edge cloud server; the determining module is configured to determine whether a dynamic edge node based on the block chain needs to be established according to the processing capability of the current edge cloud server, the attribute information of the terminal and the first position information; the establishing module is configured to establish the dynamic edge node according to the service strategy under the condition that the dynamic edge node is determined to be required to be established; and the synchronization module is configured to send the synchronization data to the dynamic edge node so that the dynamic edge node provides the blockchain service for the terminal.
In order to achieve the above object, a fourth aspect of the present application provides a terminal, including: the acquisition module is configured to acquire first position information between the current terminal and the edge cloud server; the generation module is configured to generate a service request according to the first position information and the attribute information of the current terminal; the sending module is configured to send a service request to the edge cloud server so that the edge cloud server can establish a dynamic edge node according to the first position information, the attribute information of the current terminal and the service policy, and enable the edge cloud server to send synchronous data to the dynamic edge node so that the dynamic edge node can provide blockchain service for the terminal.
According to the blockchain-based communication method, the server and the terminal, the attribute information of the terminal and the first position information between the terminal and the current edge cloud server are acquired through the edge cloud server, so that the edge cloud server can know whether communication service can be provided for the terminal or not; determining whether a dynamic edge node based on a block chain needs to be established according to the processing capacity of the current edge cloud server, the attribute information of the terminal and the first position information so as to ensure the communication quality of the terminal; under the condition that the dynamic edge node based on the block chain is determined to be required to be established, the dynamic edge node is established according to a service strategy, so that the dynamic edge node can provide communication service for the terminal more quickly, and the communication efficiency between the terminal and the dynamic edge node is improved; by sending the synchronous data to the dynamic edge node, the dynamic edge node can be familiar with the content of the blockchain service of the terminal, and the service quality of the terminal is improved.
Drawings
The accompanying drawings are included to provide a further understanding of embodiments of the disclosure, and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure, without limitation to the disclosure. The above and other features and advantages will become more readily apparent to those skilled in the art by describing in detail exemplary embodiments with reference to the attached drawings, in which:
fig. 1 is a flow chart illustrating a block chain based communication method according to an embodiment of the present application.
Fig. 2 is a flow chart of a block chain based communication method according to another embodiment of the present application.
Fig. 3 is a flow chart illustrating a block chain based communication method according to another embodiment of the present application.
Fig. 4 shows a block diagram of an edge cloud server according to an embodiment of the present application.
Fig. 5 shows a block diagram of a terminal according to an embodiment of the present application.
Fig. 6 shows an application scenario diagram of a blockchain-based communication system provided in an embodiment of the present application.
Fig. 7 shows a block diagram of the components of each node in the blockchain-based communication system provided in an embodiment of the present application.
Fig. 8 is a flowchart illustrating an operation method of the blockchain-based communication system according to an embodiment of the present application.
Detailed Description
The following detailed description of specific embodiments of the present application refers to the accompanying drawings. It should be understood that the detailed description is presented herein for purposes of illustration and explanation only and is not intended to limit the present application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present application by showing examples of the present application.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
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.
Fig. 1 is a flow chart illustrating a block chain based communication method according to an embodiment of the present application. The method can be applied to the edge cloud server. As shown in fig. 1, includes:
step S101, acquiring attribute information of a terminal and first position information between the terminal and a current edge cloud server.
The first location information may be determined according to location information of the terminal obtained by a global positioning system or other positioning systems (e.g., a mobile communication system) and location information of a current edge cloud server, so as to ensure accuracy of the first location information. The attribute information of the terminal may include: any one or more of current location information of the terminal, a communication cell to which the terminal belongs, communication requirement information of the terminal, reception power and transmission power of the terminal.
Step S102, determining whether a dynamic edge node based on the block chain needs to be established according to the processing capability of the current edge cloud server, the attribute information of the terminal and the first position information.
Wherein the first location information includes: distance between the terminal and the edge cloud server. For example, according to the distance between the terminal and the edge cloud server, determining whether the edge cloud server is suitable for providing quick blockchain service for the terminal, in the case that the edge cloud server is determined to be suitable, by matching the requirement information of the terminal with the processing capability of the current edge cloud server, in the case that the matching is determined, determining that a dynamic edge node based on a blockchain needs to be established in the current edge cloud server, so that the dynamic edge node can better provide blockchain service for the terminal.
Step S103, under the condition that the dynamic edge node is determined to be required to be established, the dynamic edge node is established according to the service strategy.
The service policy can ensure that the established dynamic edge node can provide optimal blockchain service for the terminal.
Through the service strategy, the most suitable position is selected to establish the dynamic edge node, so that the terminal can be guaranteed to provide the block chain service for the terminal nearby through the dynamic edge node, and the service quality of the terminal is improved.
In some implementations, the service policy includes: a nearby principals policy or a performance priority policy. Under the condition that the dynamic edge node is required to be established, the dynamic edge node is established according to a nearby principle policy or a performance priority policy.
The nearby principle is that according to the position information, the edge cloud server closest to the terminal is determined to establish a corresponding dynamic edge node, and the dynamic edge node is used for providing service for the terminal; the performance priority strategy is used for matching the optimal service strategy for the terminal according to the requirement information of the terminal and the processing performance of the dynamic edge node so that the terminal can obtain the optimal service.
The dynamic edge node is established through different strategies, and the terminal can be matched with an optimal service strategy while the accuracy of the dynamic edge node is ensured, so that the terminal can obtain optimal service.
Step S104, synchronous data is sent to the dynamic edge node.
After the dynamic edge node obtains the synchronous data, the dynamic edge node can provide the blockchain service for the terminal according to the synchronous data. Wherein the synchronization data may include: terminal specific data, and/or blockchain service data corresponding to the terminal.
For example, the blockchain service data corresponding to the terminal may include: any one or more of smart contract data, service module data, blockchain network data.
In this embodiment, attribute information of a terminal and first position information between the terminal and a current edge cloud server are acquired through the edge cloud server, so that the edge cloud server can know whether communication service can be provided for the terminal; determining whether a dynamic edge node based on a block chain needs to be established according to the processing capacity of the current edge cloud server, the attribute information of the terminal and the first position information so as to ensure the communication quality of the terminal; under the condition that the dynamic edge node based on the block chain is determined to be required to be established, the dynamic edge node is established according to a service strategy, so that the dynamic edge node can provide communication service for the terminal more quickly, and the communication efficiency between the terminal and the dynamic edge node is improved; by sending the synchronous data to the dynamic edge node, the dynamic edge node can be familiar with the content of the blockchain service of the terminal, and the service quality of the terminal is improved.
Fig. 2 is a flow chart of a block chain based communication method according to another embodiment of the present application. The method can be applied to the edge cloud server. The difference between this embodiment and the previous embodiment is that: and under the condition that the position information of the terminal is changed, notifying the first dynamic edge node to migrate the blockchain data corresponding to the terminal to the second dynamic edge node, so that the second dynamic edge node can provide better blockchain service for the terminal. As shown in fig. 2, includes:
step S201, acquiring attribute information of a terminal and first location information between the terminal and a current edge cloud server.
In some implementations, obtaining attribute information of a terminal and first location information between the terminal and a current edge cloud server includes: receiving a service request sent by a terminal; and carrying out message analysis on the service request to obtain attribute information and first position information of the terminal.
The service request can combine the attribute information and the first position information of the terminal according to a certain data structure, the combination mode can be a preset combination mode, and the combination mode is obtained when the current edge server can also interact with the terminal; after receiving the service request sent by the terminal, the service request is analyzed according to the combination mode, so that the accuracy of the analyzed attribute information and the first position information of the terminal is ensured, and the terminal is convenient to process subsequently.
Step S202, determining whether a dynamic edge node based on the block chain needs to be established according to the processing capability of the current edge cloud server, the attribute information of the terminal and the first position information.
Step S203, under the condition that the dynamic edge node is determined to be required to be established, the dynamic edge node is established according to the service strategy.
Step S204, synchronous data is sent to the dynamic edge node.
Step S202 to step S204 in the present embodiment are the same as step S102 to step S104 in the previous embodiment, and are not described here again.
In step S205, when it is determined that the location information of the terminal has been changed, second location information after the terminal has been changed is acquired.
The changed second location information may cause the edge cloud server that provides the service for the terminal to change, and it needs to determine which specific edge cloud server provides the service for the terminal at the second location, and prepare for data migration.
Step S206, obtaining a change request sent by the terminal.
The change request is used for requesting to change an edge cloud server providing communication services for the terminal.
When the terminal detects that the self position information is changed and the edge cloud server providing service for the terminal is also changed, a change request is sent to the current edge cloud server, so that the current edge cloud server is ready for data migration. For example, the data of the terminal is mirrored to facilitate data migration.
Step S207, the first dynamic edge node is informed to migrate the blockchain data corresponding to the terminal to the second dynamic edge node.
The first dynamic edge node is an edge node for providing block chain service for the terminal under the condition that the terminal is in first position information; the second dynamic edge node is an edge node that provides blockchain services for the terminal in the case that the terminal is in the second location information.
For example, a data migration request is sent to the first dynamic edge node, so that the first dynamic edge node can migrate data corresponding to the terminal to a new second dynamic edge node, and the second dynamic edge node is convenient for providing services for the terminal.
Step S208, the information of the second dynamic edge node is sent to the terminal, so that the terminal communicates with the second dynamic edge node.
The blockchain data corresponding to the terminal comprises: and the service data corresponds to the terminal and/or the service data corresponds to the terminal.
For example, the service data may include any one or more of smart contract data, service module data, blockchain network data.
It should be noted that, the above service data is only illustrative, and may be set according to actual needs, and other service data that are not illustrated are also within the protection scope of the present application, and are not described herein again.
In this embodiment, under the condition that it is determined that the location information of the terminal is changed, the second location information after the change of the terminal is obtained to determine whether the data of the terminal needs to be migrated, and determine to which edge cloud server the data needs to be migrated specifically to provide services for the terminal, so as to prepare for data migration. After the change request sent by the terminal is obtained, the first dynamic edge node is informed to migrate the blockchain data corresponding to the terminal to the second dynamic edge node, so that the first dynamic edge node can migrate the data corresponding to the terminal to the new second dynamic edge node, and the second dynamic edge node can conveniently provide services for the terminal. And sending the information of the second dynamic edge node to the terminal so that the terminal can communicate with the second dynamic edge node.
The embodiment of the present application provides another possible implementation manner, after the step S204 of sending synchronization data to the dynamic edge node is performed, so that the dynamic edge node provides a blockchain service for a terminal, the method further includes: and under the condition that the dynamic edge node is determined to be a pre-established node and the service request sent by the terminal is not received within the preset time, sending a deleting message to the dynamic edge node so that the dynamic edge node deletes the blockchain data corresponding to the terminal.
And when the dynamic edge node is determined to be a pre-established node, and the service request sent by the terminal is not received within the preset time, the terminal is characterized as not needing the current dynamic edge node to provide the blockchain service for the terminal, so that the dynamic edge node can delete the blockchain data corresponding to the terminal by sending a deletion message to the dynamic edge node.
The dynamic edge node can reduce the occupation ratio of the storage space by deleting the block chain data corresponding to the terminal, and is convenient for storing other information so as to improve the use efficiency of the storage space. And deleting the blockchain data corresponding to the terminal can also ensure that the dynamic edge node can not perform corresponding operation on the terminal, reduce unnecessary information interaction and improve the processing efficiency of the dynamic edge node.
The embodiment of the present application provides another possible implementation manner, after the step S204 of sending synchronization data to the dynamic edge node is performed, so that the dynamic edge node provides a blockchain service for a terminal, the method further includes: destroying the dynamic edge nodes.
It should be noted that, under the condition that the terminal is determined not to need the current dynamic edge node to provide the blockchain service for the terminal, the current dynamic edge node can be destroyed, and related resources of the current edge cloud server can be released, so that the current edge cloud server can have more sufficient resources for providing the blockchain service for other terminals, and the processing performance of the current edge cloud server is improved.
Fig. 3 is a flow chart illustrating a block chain based communication method according to another embodiment of the present application. The method is applicable to the terminal. As shown in fig. 3, includes:
step S301, obtaining first location information between a current terminal and an edge cloud server.
The first position information can be determined according to the position information of the current terminal obtained by the global positioning system and the position information of the edge cloud server obtained by the global positioning system, so that the accuracy of the first position information is ensured.
Step S302, a service request is generated according to the first position information and the attribute information of the current terminal.
Wherein, the attribute information of the terminal may include: any one or more of current location information of the terminal, a communication cell to which the terminal belongs, communication requirement information of the terminal, reception power and transmission power of the terminal.
The terminal is subjected to multi-dimensional information collection to obtain the attribute information of the terminal, so that the service request can be ensured to embody the multi-dimensional information of the current terminal, the service request obtained by the edge cloud server is ensured to be more comprehensive, the edge cloud server can be ensured to know the information of the current terminal to be more comprehensive, and the edge cloud server can provide high-quality blockchain service for the current terminal more accurately.
Step S303, a service request is sent to an edge cloud server.
Under the condition that the edge cloud server is determined to obtain the service request, the edge cloud server analyzes the service request to obtain first position information and attribute information of the current terminal; the edge cloud server can establish a dynamic edge node according to the first position information, the attribute information of the current terminal and the service policy, and enable the edge cloud server to send synchronous data to the dynamic edge node so that the dynamic edge node provides blockchain service for the terminal.
In some implementations, after sending the service request to the edge cloud server, further comprising: and under the condition that the distance between the current terminal and at least two edge cloud servers is the same or similar, communicating with at least two edge cloud servers.
Wherein the terminal may be located at an intersection of service coverage areas of a plurality of edge cloud servers (e.g., a first edge cloud server, a second edge cloud server, a third edge cloud server, … …, an nth edge cloud server, etc., where N is an integer greater than or equal to 2), or the terminal spans the service coverage areas of a plurality of edge clouds within a preset duration due to rapid movement of the terminal, so that one blockchain dynamic edge node may be established in each edge cloud server, and the terminal may simultaneously communicate with a plurality of blockchain dynamic edge nodes.
The plurality of block chain dynamic edge nodes provide the block chain service for the terminal, so that the service quality of the terminal can be ensured, and the situation that the terminal cannot obtain the block chain service is avoided, so that the use experience of the terminal is improved.
In some implementations, after sending the service request to the edge cloud server, further comprising: acquiring real-time position information of a current terminal; under the condition that the real-time position information of the current terminal is determined to be changed, acquiring second position information after the current terminal is changed; searching a plurality of edge cloud servers in a preset range according to the second position information; acquiring a first edge cloud server corresponding to the first position information; under the condition that the first edge cloud server is determined not to be in a plurality of edge cloud servers in a preset range, determining that the edge cloud server corresponding to the current terminal needs to be changed; and sending a change request to the first edge cloud server.
It should be noted that, there may be multiple edge cloud servers in the preset range to meet the use requirement of the terminal, and under the condition that the position of the terminal is determined to be stable, the distance between the terminal and each edge cloud server may be ordered (for example, the distances are arranged in ascending order or descending order, etc.), so that the edge cloud server closest to the terminal provides the blockchain service for the terminal, so that other blockchain dynamic edge nodes are automatically or passively destroyed, thereby avoiding the waste of resources.
For example, when it is determined that the second edge cloud server is the server that is currently most suitable for providing the blockchain service for the terminal, and the source edge cloud server (i.e., the first edge cloud server) that provides the blockchain service for the terminal is not among a plurality of edge cloud servers within a preset range, a change request may be sent to the first edge cloud server, so that the first edge cloud server can synchronize data corresponding to the terminal to the second edge cloud server, avoid communication interruption of the terminal, and ensure that the second edge cloud server can normally provide the blockchain service for the terminal, so as to improve service quality of the terminal.
In the embodiment, by acquiring the first position information between the current terminal and the edge cloud server, the current terminal determines whether the edge cloud server is required to provide the blockchain service for the current terminal; generating a service request according to the first position information and the attribute information of the current terminal; sending a service request to an edge cloud server so that the edge cloud server establishes a dynamic edge node according to the first position information, the attribute information of the current terminal and the service policy, so that the dynamic edge node can provide communication service for the current terminal more quickly, and the communication efficiency between the current terminal and the dynamic edge node is improved; and enabling the edge cloud server to send synchronous data to the dynamic edge node so that the dynamic edge node provides blockchain service for the terminal.
Fig. 4 shows a block diagram of an edge cloud server according to an embodiment of the present application. As shown in fig. 4, the edge cloud server specifically includes:
an acquisition module 401 configured to acquire attribute information of a terminal and first location information between the terminal and a current edge cloud server;
a determining module 402, configured to determine whether a dynamic edge node based on a blockchain needs to be established according to the processing capability of the current edge cloud server, the attribute information of the terminal and the first location information;
a building module 403 configured to build the dynamic edge node according to the service policy in case it is determined that the dynamic edge node needs to be built;
the synchronization module 404 is configured to send synchronization data to the dynamic edge node to cause the dynamic edge node to provide blockchain services for the terminal.
In this embodiment, the edge cloud server acquires attribute information of the terminal and first position information between the terminal and the current edge cloud server through the acquisition module, so that the edge cloud server can acquire whether communication service can be provided for the terminal; the method comprises the steps that a determining module is used for determining whether a dynamic edge node based on a block chain needs to be established according to the processing capacity of a current edge cloud server, attribute information of a terminal and first position information, so that the communication quality of the terminal is guaranteed; under the condition that the establishment module determines that the dynamic edge node based on the block chain needs to be established, the dynamic edge node is established according to a service strategy, so that the dynamic edge node can provide communication service for the terminal more quickly, and the communication efficiency between the terminal and the dynamic edge node is improved; and the synchronous module is used for sending synchronous data to the dynamic edge node, so that the dynamic edge node can be familiar with the content of the block chain service of the terminal, and the service quality of the terminal is improved.
Fig. 5 shows a block diagram of a terminal according to an embodiment of the present application. As shown in fig. 5, the terminal specifically includes:
an obtaining module 501 configured to obtain first location information between a current terminal and an edge cloud server;
a generating module 502 configured to generate a service request according to the first location information and attribute information of the current terminal;
the sending module 503 is configured to send a service request to the edge cloud server, so that the edge cloud server establishes a dynamic edge node according to the first location information, the attribute information of the current terminal and the service policy, and causes the edge cloud server to send synchronization data to the dynamic edge node, so that the dynamic edge node provides blockchain service for the terminal.
In this embodiment, the obtaining module obtains first location information between the current terminal and the edge cloud server, so that the current terminal determines whether the edge cloud server is required to provide the blockchain service for the current terminal; generating a service request by using a generating module according to the first position information and the attribute information of the current terminal; a sending module is used for sending a service request to an edge cloud server so that the edge cloud server can establish a dynamic edge node according to the first position information, the attribute information of the current terminal and the service policy, so that the dynamic edge node can provide communication service for the current terminal more quickly, and the communication efficiency between the current terminal and the dynamic edge node is improved; and enabling the edge cloud server to send synchronous data to the dynamic edge node so that the dynamic edge node provides blockchain service for the terminal.
It should be noted that each module in this embodiment is a logic module, and in practical application, one logic unit may be one physical unit, or may be a part of one physical unit, or may be implemented by a combination of multiple physical units. In addition, in order to highlight the innovative part of the present application, elements that are not so close to solving the technical problem presented in the present application are not introduced in the present embodiment, but it does not indicate that other elements are not present in the present embodiment.
Fig. 6 shows an application scenario diagram of a blockchain-based communication system provided in an embodiment of the present application. As shown in fig. 6, the blockchain-based communication system includes the following devices:
core network device 610, edge network device 620, and terminal device 630.
The core network device 610 may include a plurality of servers (e.g., a first core network server 611, a second core network server 612, a third core network server 613, a fourth core network server 614, a fifth core network server 615, a sixth core network server 616, etc.). The edge network device 620 may also include a plurality of servers (e.g., a first edge server 6201, a second edge server 6202, a third edge server 6203, a fourth edge server 6204, a fifth edge server 6205, a sixth edge server 6206, a seventh edge server 6207, a eighth edge server 6208, a ninth edge server 6209, a tenth edge server 6210, an eleventh edge server 6211, … …, a kk edge server 62kk, etc.) and a plurality of base stations (e.g., a first base station 6221, a second base station 6222, a third base station 6223, a fourth base station 6224, … …, an mth base station 622m, etc.). The terminal device 630 may include a variety of different types of terminals (e.g., notebook 631, desktop 632, cell phone 633, tablet 634, … …, camera 63n, etc.), where k, n, and m are integers greater than or equal to 1.
The terminal device 630 may be a mobile terminal or a fixed terminal. The core network device 610 and the edge network device 620 may be devices in a mobile network or devices in a fixed network.
The first core network server 611, the second core network server 612, the third core network server 613, the fourth core network server 614, the fifth core network server 615, and the sixth core network server 616 may form a core cloud in the core network by being connected to each other. While the first edge server 6201, the second edge server 6202, the third edge server 6203 and the fourth edge server 6204 may be connected to each other to form a first edge cloud in the access network; the fifth edge server 6205, the sixth edge server 6206, the seventh edge server 6207, the eighth edge server 6208, and so on, form a second edge cloud in the access network by being connected to each other, and so on, a plurality of edge clouds in the access network may be obtained.
It should be noted that a conventional blockchain service (i.e., a service based on a blockchain mode) is typically deployed in a core cloud or terminal device 630 of a core network. When all of the blockchain nodes of the blockchain service are deployed at the terminal device 630, the quality and efficiency of network communication between the blockchain nodes is typically affected by the network state corresponding to the terminal device 630; when the blockchain nodes are all deployed in the core cloud of the core network, the network communication quality and efficiency between the blockchain clients and the blockchain nodes are generally affected by the network state corresponding to the terminal device 630 and the service capability of the core cloud of the core network.
If the blockchain nodes are deployed in the edge clouds of the access network, it is not possible to fixedly deploy one blockchain node in each edge cloud for each user or organization due to the limited storage and communication capabilities of the respective edge clouds in the access network, as well as the limited network coverage capabilities. The communication efficiency between the terminal and the blockchain node can be improved by arranging the blockchain dynamic edge node in the edge cloud of the access network.
Fig. 7 shows a block diagram of the components of each node in the blockchain-based communication system provided in an embodiment of the present application. As shown in fig. 7, the blockchain-based communication system includes the following devices:
a plurality of blockchains Yun Jiedian (e.g., blockchain Yun Jiedian, other blockchains Yun Jiedian P, etc.), a plurality of blockchain dynamic edge nodes (e.g., blockchain dynamic edge node 720, other blockchain dynamic edge node 72K, etc.), an edge cloud mobility management service node 740, and blockchain clients 730, etc. Wherein P and K are integers greater than or equal to 1.
Wherein the blockchain dynamic edge node 720 is a mirror of the blockchain nodes deployed at the core cloud (e.g., mirror any one or more of all data, part data, and business logic data of the blockchain nodes of the core cloud).
Without loss of generality, one blockchain edge dynamic node corresponds to one blockchain client deployed in the local network, and one blockchain point deployed in the core cloud, respectively. For example, the blockchain dynamic edge nodes 720 correspond to blockchain clients 730 deployed in the local network, and blockchains Yun Jiedian 710 deployed in the core cloud, respectively.
In the case that it is determined that the location of the terminal corresponding to the blockchain client 730 is changed, the access network corresponding to the terminal (or the edge cloud corresponding to the terminal) may also change, so that the blockchain dynamic edge node 720 corresponding to the blockchain client 730 needs to be migrated to the changed edge cloud.
It should be noted that, the blockchain dynamic edge node 720 may provide the blockchain service to the blockchain client 730 in the near future, and the blockchain dynamic edge node 720 maintains synchronization of data and services with the blockchain cloud nodes 710 in the core cloud.
As shown in fig. 7, the blockchain dynamic edge node 720 includes the following modules: an edge mobility management module 721, a second client service module 722, a second cloud data synchronization module 723, a second cloud contract synchronization module 724, a second inter-node service module 725, a schedule management module 726, and an edge data migration module 727.
Blockchain cloud node 710 includes the following modules: a terminal mobility service module 711, a first client service module 712, a first cloud data synchronization module 713, a first cloud contract synchronization module 714, and a first inter-node service module 715. Blockchain client 730 includes: a client location management module 731 and a client configuration module 732.
The blockchain dynamic edge node 720 interacts with the edge cloud mobility management service node 740 to obtain the mobility state of the blockchain client 730 for online services. The blockchain dynamic edge node 720 interacts with other blockchain dynamic edge nodes 72K, or with the blockchain cloud node 710, to provide blockchain services to the blockchain clients 730.
The terminal mobility service module 711 is configured to track and manage location information of the blockchain client 730, and initiate operations such as migrating or terminating migration on data of the blockchain dynamic edge node 720.
It should be noted that, if the edge cloud where the blockchain client 730 is located supports the blockchain dynamic edge node service, the terminal mobility service module 711 needs to check the data of the blockchain client 730 and generate the blockchain dynamic edge node 720, so that the blockchain dynamic edge node 720 can provide the blockchain service for the blockchain client 730. In the event that the blockchain dynamic edge node 720 generation is determined, the blockchain dynamic edge node 720 may track the data of the blockchain client 730 or the blockchain dynamic edge node 720 may be notified by the terminal mobility service module 711 so that the blockchain dynamic edge node 720 may support migration of blockchain services across edge clouds.
In the event that a determination is made that data for the blockchain dynamic edge node 720 needs to be migrated, the terminal mobility service module 711 can coordinate resources to enable the blockchain dynamic edge node 720 to migrate to other edge clouds. In some implementations, some of the functionality of the terminal mobility service module 711 may also be deployed on the edge cloud, enabling the edge cloud to support the management of the blockchain dynamic edge node 720 by the blockchain Yun Jiedian 710.
The function of the first client service module 712 is the same as the function of the second client service module 722 in the blockchain dynamic edge node 720, both for providing blockchain services to the blockchain clients 730.
A first cloud data synchronization module 713 for supporting interaction with a second cloud data synchronization module 723 in the blockchain dynamic edge node 720 to achieve synchronization of blockchain data.
A first cloud contract synchronization module 714 for supporting interaction with a second cloud contract synchronization module 724 in the blockchain dynamic edge node 720 to enable synchronization of blockchain contracts.
The first inter-node service module 715 functions identically to the second inter-node service module 725 in the blockchain dynamic edge node 720, and can support interaction with other blockchain dynamic edge nodes 72K or blockchain cloud nodes 71P.
The edge mobility management module 721 is configured to obtain location information of the blockchain client 730 from the blockchain client 730 or from the edge cloud mobility management service node 740, and determine whether the blockchain client 730 is about to or is performing edge cloud handover according to the location information. In the event that it is determined that the blockchain client 730 needs to be switched from the source edge cloud to the target edge cloud, the blockchain dynamic edge node 720 corresponding to the blockchain client 730 needs to be simultaneously switched into the target edge cloud. In cooperation with the schedule management module 726, dynamic migration of the blockchain dynamic edge node 720 may be achieved.
A second client service module 722 for providing blockchain services for the blockchain clients 730 and processing blockchain services. And may also be used to receive location information provided by the blockchain client 730 or to obtain location information of the blockchain client 730 from the edge cloud mobility management service node 740.
The second cloud data synchronization module 723 is responsible for interacting with the blockchain cloud node 710 to synchronize blockchain data, thereby implementing a cross-regional blockchain service.
The second cloud contract synchronization module 724 is responsible for interacting with the blockchain cloud node 710 to synchronize blockchain contract states and contract data, thereby implementing a cross-regional blockchain service.
The second inter-node service module 725 is responsible for interacting with other blockchain dynamic edge nodes 72K or other blockchain cloud nodes 71P.
A scheduling management module 726 for coordinating the collaboration between the various modules of the blockchain dynamic edge node 720 and coordinating the collaboration between the source blockchain dynamic edge node and the target blockchain dynamic edge node in the event that mobility migration of the blockchain dynamic edge node 720 is determined.
The edge data migration module 727 is configured to migrate the blockchain data from the source blockchain dynamic edge node to the target blockchain dynamic edge node in a case that it is determined that the blockchain client 730 moves in position and that the blockchain dynamic edge node 720 corresponding to the blockchain client 730 also needs to migrate between different edge clouds.
The client position management module 731 is configured to track its position in real time, and notify the blockchain dynamic edge node 720 if it is determined that the position of the blockchain client 730 changes. For example, the blockchain client 730 tracks its location change information in real time (e.g., whether the terminal needs to perform a handover of a communication cell or a base station, etc.) through a positioning device of the terminal.
A client configuration module 732 for setting connection parameters (e.g., whether to notify a location change, etc.) of the blockchain client 730.
It should be noted that the blockchain dynamic edge node 720 is transparent to the blockchain client 730. The blockchain client 730 may service the blockchain Yun Jiedian 710 regardless of whether it is specifically or the blockchain dynamic edge node 720.
Fig. 8 is a flowchart illustrating an operation method of the blockchain-based communication system according to an embodiment of the present application.
The blockchain dynamic edge node 720 is responsible for management by the terminal mobility service module 711 of the blockchain cloud node 710. The terminal mobility service module 711 is deployed in the core cloud and the edge cloud, and can determine whether to generate and on which edge cloud to generate the blockchain dynamic edge node 720 according to the service policy (e.g., the nearby principle or the performance priority principle, etc.) and the location information of the blockchain client 730. In the event that it is determined that the blockchain dynamic edge node 720 is no longer needed to serve the blockchain client 730, then the blockchain dynamic edge node 720 may automatically destroy or be notified by the terminal mobility service module 711 to destroy.
As shown in fig. 8, the operating method of the blockchain-based communication system mainly includes the following steps:
in step 801, the blockchain client 730 sends a service request to the blockchain Yun Jiedian 710 to obtain blockchain service.
The terminal mobility service module 711 of the blockchain cloud node 710 needs to determine and select according to the service policy.
For example, the service policy may be selected based on factors such as the distance between the blockchain client 730 and the blockchain cloud node 710, and the processing power of the blockchain cloud node 710 or the edge cloud, according to a proximity rule or a performance priority rule.
It should be noted that, in the case where it is determined that the edge cloud does not support the edge cloud blockchain service, the blockchain cloud node 710 directly serves the blockchain client 730.
In step S802, in the case of determining that the edge cloud supports the edge cloud blockchain service, the terminal mobility service module 711 in the blockchain cloud node 710 obtains the location information of the blockchain client 730 from the edge cloud mobility management service node 740, and determines an edge cloud that can provide the blockchain client 730 with the blockchain edge cloud service according to the location information and the nearby principle (or the performance priority principle, etc.).
Optionally, the blockchain client 730 may also provide its own location information to the terminal mobility service module 711 in the blockchain cloud node 710.
In step S803, the terminal mobility service module 711 in the core cloud (e.g., blockchain Yun Jiedian, 710) notifies the terminal mobility service module in the matched edge cloud, generating a blockchain dynamic edge node (e.g., blockchain dynamic edge node 720).
In step S804, if the blockchain dynamic edge node 720 generates successfully, the terminal mobility service module 711 in the blockchain cloud node 710 notifies the blockchain client 730 to turn to the blockchain dynamic edge node 720 to request blockchain services.
In step S805, the blockchain client 730 interacts with the blockchain dynamic edge node 720 in a message to enable the blockchain client 730 to obtain the blockchain service provided by the blockchain dynamic edge node 720.
In step S806, in the process that the blockchain dynamic edge node 720 provides the blockchain service to the blockchain client 730, the blockchain dynamic edge node 720 needs to interact with the blockchain cloud nodes 710 in the core cloud to enable the blockchain dynamic edge node 720 to perform data synchronization (e.g., synchronize blockchain data and contracts) with the blockchain cloud nodes 710.
In step S807, in the service process, the terminal mobility service module 711 in the blockchain cloud node 710 sends a position monitoring message to the edge cloud mobility management service node 740 to continuously track the position of the blockchain client 730, so as to determine whether the blockchain client 730 changes in position and whether the changed position causes the edge cloud providing the service to change according to the obtained position information.
In step S808, if the change in the location of the blockchain client 730 causes a change in the edge cloud that serves it, the terminal mobility service module 711 sends a data migration message to the blockchain dynamic edge node 720.
Wherein the data migration message includes blockchain service data. Optionally, the blockchain dynamic edge node 720 may also be aware of and participate in the migration of the blockchain service data that will occur.
In step S809, the terminal mobility service module 711 in the blockchain cloud node 710 and the edge cloud 1 sends a dynamic edge node generation message to the edge cloud 2 to generate a blockchain dynamic edge node 72K using the edge cloud 2.
In step S810, after the blockchain dynamic edge node 72K is successfully created, a message is exchanged between the blockchain dynamic edge node 720 and the blockchain dynamic edge node 72K so that the blockchain data of the blockchain dynamic edge node 720 can be synchronized to the blockchain dynamic edge node 72K.
In some specific implementations, step S810 may also be implemented as follows:
upon determining that the blockchain dynamic edge node 72K was successfully created, the blockchain dynamic edge node 72K downloads configuration information, initial data information, and the like, required by the blockchain client 730 from the blockchain core cloud node 710. The blockchain dynamic edge node 720 then synchronizes the traffic data of the blockchain client 730 to the blockchain dynamic edge node 72K.
In the event that the blockchain dynamic edge node 720 is determined to provide blockchain services to the blockchain client 730, the blockchain dynamic edge node 720 synchronizes the service information and data for the blockchain client 730 to the blockchain dynamic edge node 72K. Meanwhile, the blockchain dynamic edge node 720 also sends the blockchain dynamic edge node 72K information to the blockchain client 730 to enable the blockchain client 730 to learn information about the nodes for which blockchain services are to be provided.
In determining that the location of the blockchain client 730 has changed (e.g., handed over from one communication cell to another communication cell, etc.), the blockchain client 730 may send application service request information to both the blockchain dynamic edge node 720 and the blockchain dynamic edge node 72K.
Upon determining that both the blockchain dynamic edge node 720 and the blockchain dynamic edge node 72K receive the application service request information sent by the blockchain client 730, the blockchain dynamic edge node 720 may interact with the blockchain dynamic edge node 72K to determine the node that actually provides blockchain service to the blockchain client 730 (typically the newly generated blockchain dynamic edge node 72K). The blockchain client 730 is provided with blockchain services by the blockchain dynamic edge node 72K during subsequent communications.
It should be noted that, in the case that it is determined that the blockchain dynamic edge node 720 does not receive the service request message of the blockchain client 730 any more within a preset period of time (for example, 5 minutes, etc.), the blockchain dynamic edge node 720 may delete the service resource provided for the blockchain client 730 therein, or automatically destroy the blockchain dynamic edge node 720.
Alternatively, in each edge cloud, the edge cloud's own blockchain dynamic edge nodes may be established in advance. In the case where it is determined that the blockchain dynamic edge node 72K receives the service request message sent by the new blockchain client, or receives the mobility synchronization service request sent by other blockchain dynamic edge nodes (e.g., the blockchain dynamic edge node 720), the edge cloud corresponding to the blockchain dynamic edge node 72K allocates the corresponding resource to the blockchain dynamic edge node 72K, so that the blockchain dynamic edge node 72K can provide the blockchain service for the new blockchain client.
Note that the mobility synchronization service request includes: mobility synchronization service data, which is blockchain service data provided by blockchain dynamic edge node 72K to blockchain client 730. The mobility synchronization service data is used to characterize the synchronization data between the source blockchain dynamic edge node and the destination blockchain dynamic edge node in the event of a change in location of the blockchain client 730. If the blockchain dynamic edge node 72K is a pre-established node, then the blockchain dynamic edge node 72K need only delete data corresponding to the blockchain client 730 without destroying itself in the event that it is determined that the blockchain client 730 is no longer requesting blockchain services from it.
Step S811 may also be performed while step S810 is performed.
In step S811, the blockchain cloud node 710 may synchronize the blockchain service data to the blockchain dynamic edge node 720, so that the blockchain dynamic edge node 720 may forward the synchronized data to the blockchain dynamic edge node 72K, thereby making the blockchain data obtained by the blockchain dynamic edge node 72K corresponding to the blockchain client 730 more complete.
In some implementations, the synchronization of the data corresponding to the blockchain client 730 between the blockchain dynamic edge node 720 and the blockchain cloud node 710 in step S811 may include: cloud data synchronization and cloud service synchronization.
Wherein cloud data synchronization includes: the data exclusive to the blockchain client 730 is synchronized between the blockchain cloud node 710 and the blockchain dynamic edge node 720 to ensure consistency of the data corresponding to the blockchain client 730 in the blockchain cloud node 710 and the blockchain dynamic edge node 720.
Cloud service synchronization, which characterizes the synchronization of information required for a blockchain service provided by blockchain client 730. For example, cloud service synchronization data includes: any one or more of smart contract data, service module data, blockchain network data.
In step S812, in the case that it is determined that the blockchain data corresponding to the blockchain client 730 is successfully migrated to the blockchain dynamic edge node 72K, the blockchain cloud node 710 sends a notification message to the blockchain client 730, so that the blockchain client 730 can obtain the blockchain service provided by the blockchain dynamic edge node 72K.
In step S813, the blockchain dynamic edge node 72K interacts with the blockchain client 730 to provide blockchain services to the blockchain client 730.
It should be noted that, after the step S812 is performed, the blockchain dynamic edge node 720 may be destroyed automatically or passively.
In general, a blockchain client may move from the service coverage area of one edge cloud to the service coverage area of another edge cloud. However, in some specific scenarios, the blockchain client 730 may be located at an intersection of service coverage areas of multiple edge clouds, or the device in which the blockchain client 730 is located spans the service coverage areas of multiple edge clouds within a preset duration due to rapid movement of the device in which the blockchain client 730 is located, so that one blockchain dynamic edge node may be established in each edge cloud, and the blockchain client 730 may communicate with multiple blockchain dynamic edge nodes at the same time; and in case that the location of the blockchain client 730 is determined to be stable, only the blockchain dynamic edge node corresponding to the stable location of the blockchain client 730 is used to provide the blockchain service thereto, so that other blockchain dynamic edge nodes are automatically or passively destroyed.
In some implementations, the interaction messages between the blockchain Yun Jiedian and the blockchain dynamic edge node 720, and the interaction messages between the blockchain dynamic edge node 720 and the blockchain dynamic edge node 72K may be encrypted using encryption techniques (e.g., digital signature or hash encryption, etc.) to ensure the security of each interaction message.
It should be noted that, for each blockchain client, all blockchain data (e.g., blockchain ledger data and the like) corresponding to the blockchain client needs to be stored on the blockchain cloud node 710, and the blockchain dynamic edge node 720 or the blockchain dynamic edge node 72K only needs to store part of the data of the blockchain client, where the part of the data can meet the requirements of the blockchain client, so as to avoid the waste of storage resources and improve the utilization efficiency of the storage resources.
In this embodiment, by disposing the blockchain node corresponding to the decentralizing application (for example, the blockchain application) on the edge cloud server, the edge cloud server can establish a blockchain dynamic edge node according to the requirements of the terminal and the processing performance of the current edge cloud server, and provide an optimal service for the terminal by using the blockchain dynamic edge node. Under the condition that the position of the terminal is changed, the data of the terminal can be migrated from the source block chain dynamic edge node to the target block chain dynamic edge node, so that the terminal can always obtain the best service quality, the characteristics and service capability of the terminal, the edge cloud and the core cloud are fully exerted, and the block chain service with elasticity, stability, rapidness and safety is realized.
It is to be understood that the above embodiments are merely illustrative of the exemplary embodiments employed to illustrate the principles of the present application, however, the present application is not limited thereto. Various modifications and improvements may be made by those skilled in the art without departing from the spirit and substance of the application, and are also considered to be within the scope of the application.
Claims (12)
1. A blockchain-based communication method, the method comprising:
acquiring attribute information of a terminal and first position information between the terminal and a current edge cloud server;
determining whether a dynamic edge node based on a block chain needs to be established according to the processing capacity of the current edge cloud server, the attribute information of the terminal and the first position information;
under the condition that the dynamic edge node is determined to be established, establishing the dynamic edge node according to a service strategy;
and sending synchronous data to the dynamic edge node so that the dynamic edge node provides the blockchain service for the terminal, wherein the synchronous data at least comprises blockchain service data corresponding to the terminal, and the service strategy is used for enabling the established dynamic edge node to provide the optimal blockchain service for the terminal.
2. The method of claim 1, wherein the service policy comprises: a nearby principals policy or a performance priority policy;
under the condition that the dynamic edge node is determined to be required to be established, establishing the dynamic edge node according to a service policy comprises the following steps:
and under the condition that the dynamic edge node is required to be established, establishing the dynamic edge node according to the nearby principle policy or the performance priority policy.
3. The method according to claim 1, wherein the acquiring attribute information of the terminal and first location information between the terminal and the current edge cloud server includes:
receiving a service request sent by the terminal;
and carrying out message analysis on the service request to obtain the attribute information and the first position information of the terminal.
4. The method of claim 3, wherein after said sending synchronization data to said dynamic edge node to cause said dynamic edge node to provide blockchain services to said terminal, further comprising:
acquiring second position information after the terminal is changed under the condition that the position information of the terminal is determined to be changed;
Acquiring a change request sent by the terminal, wherein the change request is used for requesting to change an edge cloud server providing communication service for the terminal;
notifying a first dynamic edge node to migrate the blockchain data corresponding to the terminal to a second dynamic edge node, wherein the first dynamic edge node is an edge node for providing blockchain service for the terminal under the condition that the terminal is in first position information; the second dynamic edge node is an edge node for providing block chain service for the terminal under the condition that the terminal is in the second position information;
and sending the information of the second dynamic edge node to the terminal so as to enable the terminal to communicate with the second dynamic edge node.
5. The method of claim 1, wherein after said sending synchronization data to said dynamic edge node to cause said dynamic edge node to provide blockchain services to said terminal, further comprising:
and under the condition that the dynamic edge node is determined to be a pre-established node and the service request sent by the terminal is not received within a preset time period, sending a deleting message to the dynamic edge node so that the dynamic edge node deletes the blockchain data corresponding to the terminal.
6. The method of claim 1, wherein after said sending synchronization data to said dynamic edge node to cause said dynamic edge node to provide blockchain services to said terminal, further comprising:
destroying the dynamic edge node.
7. The method according to claim 4 or 5, wherein the blockchain data corresponding to the terminal includes: and the service data corresponding to the terminal and/or the service data corresponding to the terminal.
8. A blockchain-based communication method, the method comprising:
acquiring first position information between a current terminal and an edge cloud server;
generating a service request according to the first position information and the attribute information of the current terminal;
and sending the service request to an edge cloud server so that the edge cloud server establishes a dynamic edge node according to the first position information, the attribute information of the current terminal and a service policy, and enabling the edge cloud server to send synchronous data to the dynamic edge node so that the dynamic edge node provides blockchain service for the terminal, wherein the synchronous data at least comprises blockchain service data corresponding to the terminal, and the service policy is used for enabling the established dynamic edge node to provide optimal blockchain service for the terminal.
9. The method of claim 8, wherein after the sending the service request to an edge cloud server, further comprising:
and under the condition that the distance between the current terminal and at least two edge cloud servers is the same or similar, communicating with at least two edge cloud servers.
10. The method of claim 8, wherein after the sending the service request to an edge cloud server, further comprising:
acquiring real-time position information of the current terminal;
acquiring second position information after the current terminal is changed under the condition that the real-time position information of the current terminal is determined to be changed;
searching a plurality of edge cloud servers in a preset range according to the second position information;
acquiring a first edge cloud server corresponding to the first position information;
under the condition that the first edge cloud server is determined not to be in a plurality of edge cloud servers in the preset range, determining that the edge cloud server corresponding to the current terminal needs to be changed;
and sending a change request to the first edge cloud server.
11. An edge cloud server, comprising:
The acquisition module is configured to acquire attribute information of a terminal and first position information between the terminal and a current edge cloud server;
a determining module configured to determine whether a dynamic edge node based on a blockchain needs to be established according to the processing capability of the current edge cloud server, the attribute information of the terminal and the first location information;
the establishing module is configured to establish the dynamic edge node according to a service policy under the condition that the dynamic edge node is determined to be required to be established;
and the synchronization module is configured to send synchronization data to the dynamic edge node so that the dynamic edge node provides the blockchain service for the terminal, wherein the synchronization data at least comprises blockchain service data corresponding to the terminal, and the service strategy is used for enabling the established dynamic edge node to provide the optimal blockchain service for the terminal.
12. A terminal, comprising:
the acquisition module is configured to acquire first position information between the current terminal and the edge cloud server;
the generation module is configured to generate a service request according to the first position information and the attribute information of the current terminal;
The sending module is configured to send the service request to an edge cloud server, so that the edge cloud server establishes a dynamic edge node according to the first position information, the attribute information of the current terminal and a service policy, and enables the edge cloud server to send synchronous data to the dynamic edge node, so that the dynamic edge node provides blockchain service for the terminal, wherein the synchronous data at least comprises blockchain service data corresponding to the terminal, and the service policy is used for enabling the established dynamic edge node to provide optimal blockchain service for the terminal.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110936643.7A CN113612854B (en) | 2021-08-16 | 2021-08-16 | Communication method, server and terminal based on block chain |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110936643.7A CN113612854B (en) | 2021-08-16 | 2021-08-16 | Communication method, server and terminal based on block chain |
Publications (2)
Publication Number | Publication Date |
---|---|
CN113612854A CN113612854A (en) | 2021-11-05 |
CN113612854B true CN113612854B (en) | 2023-07-25 |
Family
ID=78308649
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110936643.7A Active CN113612854B (en) | 2021-08-16 | 2021-08-16 | Communication method, server and terminal based on block chain |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN113612854B (en) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114726871B (en) * | 2022-03-22 | 2024-06-11 | 阿里巴巴(中国)有限公司 | Data synchronization method, device and network system |
CN114679467A (en) * | 2022-03-23 | 2022-06-28 | 中国联合网络通信集团有限公司 | Multi-block chain cooperative service method, block chain service system and cooperative service system |
CN115277377A (en) * | 2022-05-19 | 2022-11-01 | 亿点云计算(珠海)有限公司 | Service acquisition method, device, terminal and storage medium based on distributed cloud |
CN115866059B (en) * | 2023-01-13 | 2023-08-01 | 北京微芯区块链与边缘计算研究院 | Block chain link point scheduling method and device |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110266744A (en) * | 2019-02-27 | 2019-09-20 | 中国联合网络通信集团有限公司 | Location-based edge cloud resource dispatching method and system |
CN110753126A (en) * | 2019-10-28 | 2020-02-04 | 国网河南省电力公司信息通信公司 | Service node selection method, device management method, device, system and medium |
CN111083519A (en) * | 2019-11-06 | 2020-04-28 | 石家庄微泽科技有限公司 | VR content distribution system and method based on cloud and edge computing |
CN111797173A (en) * | 2020-09-10 | 2020-10-20 | 联通(浙江)产业互联网有限公司 | Alliance chain sharing system, method and device, electronic equipment and storage medium |
CN111835755A (en) * | 2020-07-09 | 2020-10-27 | 中国联合网络通信集团有限公司 | Mutual authentication method and equipment for Internet of things equipment and Internet of things service system |
AU2020102384A4 (en) * | 2020-09-23 | 2020-11-05 | Ashok, Alaknanda DR | A collaborative mining network (cmn) to execute computationally intense mining tasks in mobile blockchain |
CN112134892A (en) * | 2020-09-24 | 2020-12-25 | 南京邮电大学 | Service migration method in mobile edge computing environment |
CN112217876A (en) * | 2020-09-22 | 2021-01-12 | 远光软件股份有限公司 | Internet of things system, Internet of things communication method and electronic equipment |
CN112689026A (en) * | 2020-12-07 | 2021-04-20 | 中国联合网络通信集团有限公司 | Block chain as service server and block chain sharing method |
CN112968942A (en) * | 2021-01-29 | 2021-06-15 | 南京邮电大学 | Block chain data safety storage frame and method |
CN113065866A (en) * | 2021-03-23 | 2021-07-02 | 北京邮电大学 | Internet of things edge computing system and method based on block chain |
CN113079159A (en) * | 2021-04-01 | 2021-07-06 | 北京邮电大学 | Edge computing network architecture based on block chain |
CN113114790A (en) * | 2021-06-10 | 2021-07-13 | 武汉研众科技有限公司 | Load balancing method and system based on block chain and edge calculation |
CN113114656A (en) * | 2021-04-07 | 2021-07-13 | 丁志勇 | Infrastructure layout method based on edge cloud computing |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6825296B2 (en) * | 2016-10-11 | 2021-02-03 | 富士通株式会社 | Edge server and its encrypted communication control method |
CN108616596B (en) * | 2018-05-09 | 2020-12-25 | 南京邮电大学 | Block chain self-adaptive consensus method based on dynamic authorization and network environment perception |
US10915366B2 (en) * | 2018-09-28 | 2021-02-09 | Intel Corporation | Secure edge-cloud function as a service |
US20210042160A1 (en) * | 2019-04-05 | 2021-02-11 | Mimik Technology Inc. | Method and system for distributed edge cloud computing |
US11606191B2 (en) * | 2019-09-13 | 2023-03-14 | At&T Intellectual Property I, L.P. | Methods, systems, and devices for configuring a federated blockchain network |
US11057471B2 (en) * | 2019-09-24 | 2021-07-06 | Xiamen Wangsu Co., Ltd. | Edge application management method and system |
CN111274031B (en) * | 2020-01-16 | 2023-07-25 | 国家电网有限公司信息通信分公司 | Method and device for dynamic migration authentication of end-cloud cooperative edge service |
CN111722925B (en) * | 2020-06-05 | 2024-03-15 | 中国科学院自动化研究所 | Collaborative scheduling method, system and device for dynamic edge calculation |
CN112799789B (en) * | 2021-03-22 | 2023-08-11 | 腾讯科技(深圳)有限公司 | Node cluster management method, device, equipment and storage medium |
-
2021
- 2021-08-16 CN CN202110936643.7A patent/CN113612854B/en active Active
Patent Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110266744A (en) * | 2019-02-27 | 2019-09-20 | 中国联合网络通信集团有限公司 | Location-based edge cloud resource dispatching method and system |
CN110753126A (en) * | 2019-10-28 | 2020-02-04 | 国网河南省电力公司信息通信公司 | Service node selection method, device management method, device, system and medium |
CN111083519A (en) * | 2019-11-06 | 2020-04-28 | 石家庄微泽科技有限公司 | VR content distribution system and method based on cloud and edge computing |
CN111835755A (en) * | 2020-07-09 | 2020-10-27 | 中国联合网络通信集团有限公司 | Mutual authentication method and equipment for Internet of things equipment and Internet of things service system |
CN111797173A (en) * | 2020-09-10 | 2020-10-20 | 联通(浙江)产业互联网有限公司 | Alliance chain sharing system, method and device, electronic equipment and storage medium |
CN112217876A (en) * | 2020-09-22 | 2021-01-12 | 远光软件股份有限公司 | Internet of things system, Internet of things communication method and electronic equipment |
AU2020102384A4 (en) * | 2020-09-23 | 2020-11-05 | Ashok, Alaknanda DR | A collaborative mining network (cmn) to execute computationally intense mining tasks in mobile blockchain |
CN112134892A (en) * | 2020-09-24 | 2020-12-25 | 南京邮电大学 | Service migration method in mobile edge computing environment |
CN112689026A (en) * | 2020-12-07 | 2021-04-20 | 中国联合网络通信集团有限公司 | Block chain as service server and block chain sharing method |
CN112968942A (en) * | 2021-01-29 | 2021-06-15 | 南京邮电大学 | Block chain data safety storage frame and method |
CN113065866A (en) * | 2021-03-23 | 2021-07-02 | 北京邮电大学 | Internet of things edge computing system and method based on block chain |
CN113079159A (en) * | 2021-04-01 | 2021-07-06 | 北京邮电大学 | Edge computing network architecture based on block chain |
CN113114656A (en) * | 2021-04-07 | 2021-07-13 | 丁志勇 | Infrastructure layout method based on edge cloud computing |
CN113114790A (en) * | 2021-06-10 | 2021-07-13 | 武汉研众科技有限公司 | Load balancing method and system based on block chain and edge calculation |
Also Published As
Publication number | Publication date |
---|---|
CN113612854A (en) | 2021-11-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN113612854B (en) | Communication method, server and terminal based on block chain | |
US10601947B2 (en) | Application service delivery through an application service avatar | |
EP3648401B1 (en) | Method, device, and computer readable storage medium for managing network slice | |
US20200015131A1 (en) | Communication method and communications device | |
CN113726846B (en) | Edge cloud system, resource scheduling method, equipment and storage medium | |
CN113301078B (en) | Network system, service deployment and network division method, device and storage medium | |
Puliafito et al. | Companion fog computing: Supporting things mobility through container migration at the edge | |
US20220022015A1 (en) | Intent-based network configuration method, apparatus, and system | |
CN111800285B (en) | Instance migration method and device and electronic equipment | |
CN113285885A (en) | Service grid-based edge flow control method, device and storage medium | |
CN113068232A (en) | Switching method and device of edge application server | |
CN112969208B (en) | Service server switching control method and device, electronic equipment and storage medium | |
CN113382032B (en) | Cloud node changing, network expanding and service providing method, device and medium | |
WO2022022440A1 (en) | Network reconnection method, and device, system and storage medium | |
Hucheng et al. | Mobility driven network slicing: an enabler of on demand mobility management for 5G | |
WO2023179450A1 (en) | Multi-blockchain collaborative service methods, and systems | |
CN109962834B (en) | Information processing method, system, terminal and computer storage medium | |
CN110650514B (en) | Path updating method, device and system | |
CN114125827B (en) | Terminal management method, device and centralized management system | |
US20230308904A1 (en) | Data processing method, device and storage medium | |
Jaadouni et al. | SDN/NFV architectures for edge-cloud oriented IoT | |
US20220361081A1 (en) | Selecting a network node that supports a slice requirement | |
CN113079191B (en) | Positioning method, device, system and storage medium | |
CN114143778A (en) | Data sharing method and device, edge computing platform and readable storage medium | |
EP3796598A1 (en) | Node switching method, network node, network system, and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |