Resource cloud pool information synchronization method for edge nodes of system interoperation system

Abstract

The invention provides a resource cloud pool information synchronization method of an interoperable system edge node. The method comprises the following steps: (1) classifying resource cloud pool synchronization information; the edge node of the resource callout party receives a resource cloud pool callout instruction and a resource list needing to be callout, and takes out information needing to be synchronized from corresponding resources of the node of the resource callout party from a storage medium according to the list and instruction requirements; (2) compressing and signing resource synchronization information; the method comprises the following steps: organizing information into an information stream in a standard format, signing by using a system for a key distributed for each edge node, adding an obtained signature into the information stream, storing the information stream into a local text file after the signature is completed, and compressing the file; then, the file is transmitted to a resource calling-in edge node; (3) verifying and fusing the information; and the calling-in side edge node receives the resource synchronization information transmitted by the calling-out side edge node, after the resource synchronization information is successfully received, file decompression and signature verification are carried out, and after the information is confirmed to be valid, the information is fused into locally stored data.

Description

Technical Field

[0001] The present invention belongs to the technical field of communication of system interoperability systems, and particularly relates to a method for synchronizing resource cloud pool information of edge nodes of a system interoperability system. Background Art

[0002] Modern information systems have changed from traditional large platforms to a systemized and distributed form. Fundamentally speaking, the information system architecture aims to integrate all elements and modules within the system through highly efficient and multi-dimensional complex collaboration to form the greatest joint force to achieve the goal together. The system interoperability system can interconnect and interoperate all elements of the global system, thereby breaking the physical isolation between devices, forming a large platform with efficient interconnection and significantly improving the business processing efficiency. However, in special environments, there are problems such as limited bandwidth in mobile edge networks, large network overhead for data synchronization between nodes, resulting in low synchronization success rates, facing reconstruction tasks of system resource pools being attacked, reallocation of device resources, and optimization and control, thus restricting the performance of the interoperability system.

[0003] Therefore, aiming at the mobile edge network environment with limited bandwidth, to solve problems such as large network overhead for data synchronization between nodes and low synchronization success rates, through a cloud pool synchronization information processing module, an edge node data synchronization module, and a cloud-edge data synchronization module, the function of synchronizing all or part of the resource cloud pool data of a certain edge node to the resource cloud pool of a specified other edge node is realized, the dynamic allocation and deployment of resources in the cloud pool are achieved, and the goals of damaged reconstruction and agile optimization are achieved. It realizes the efficient collaboration, rapid integration, and natural aggregation and dispersion of resource information at different levels of the terminal side, edge side, and cloud side, and has key engineering application value. Summary of the Invention

[0004] To achieve the above object, the present invention proposes a method for synchronizing resource cloud pool information of edge nodes of a system interoperability system, including the following steps:

[0005] (1) Classification of resource cloud pool synchronization information;

[0006] The edge node of the resource transfer-out party receives the resource cloud pool transfer-out instruction and the list of resources to be transferred out, and takes out the information to be synchronized for the corresponding resources of its own node from the storage medium according to the list and the instruction requirements;

[0007] (2) Compression and signature of resource synchronization information;

[0008] Organize the information into a standard format information stream, then sign it using the key assigned by the system for each edge node, attach the obtained signature to the information stream, after completion, save the information stream to a local text file, and compress the file; then transfer the file to the resource receiving edge node;

[0009] (3) Verification and fusion of information;

[0010] After the receiving party's edge node receives the resource synchronization information transmitted by the sending party's edge node and successfully receives it, it performs operations such as file decompression and signature verification. After confirming the validity of the information, it integrates the information into the data stored locally.

[0011] In the above step (1), the basic information of the resource includes the resource unique number, name, corresponding semantic model type, current status of the resource, IP address, port, and communication protocol.

[0012] In the above step (1), the storage media include databases, caches, and local files.

[0013] In the above step (2), the format of the information flow is JSON / XML.

[0014] In the above step (3), according to the process of edge node data synchronization, it includes the following:

[0015] Step 1: The edge node of the resource sending party receives the resource cloud pool sending instruction and the list of resources to be sent. According to the list and the requirements of the instruction, it extracts the basic information, topological relationship information, task scheduling information, and log information that need to be synchronized for the corresponding resources from its own node's resource cloud pool, and performs data signing according to the process. After that, it saves the data as a file and compresses it;

[0016] Step 2: The edge node actively releases the binding relationship with the resources on the sending list and synchronizes the released binding information to the cloud center. At this time, both the edge node of the resource sending party and the cloud center will see that the resources in the sending party's resource cloud pool no longer include the resources on the list;

[0017] Step 3: The receiving party's edge node receives the resource synchronization information transmitted by the sending party's edge node. After successfully receiving it, it performs file decompression and signature verification operations. After confirming the validity of the information, it integrates the information into the data stored locally. Then, the receiving party establishes a binding relationship with the resources on the resource list and reports the binding relationship to the cloud center. At this time, both the receiving party's edge node and the cloud center can see that the resources on the list have appeared in the receiving party's resource cloud pool, and the entire deployment process ends.

[0018] Furthermore, when the network condition between the resource sending edge node and the receiving edge node is poor and cannot meet the data synchronization requirements, or when a certain edge node cannot perform data transmission due to a fault or being destroyed, the process of dynamically allocating the resource cloud pool in the cloud-edge data synchronization mode is as follows:

[0019] First, since the edge nodes of the resource transferor cannot communicate, the cloud center actively unbinds the resources in the transfer list from the resource cloud pool of the transferor's edge nodes;

[0020] Then, the cloud center will extract resource synchronization information from the resource cloud pool of its own nodes according to the resource list specified in the resource list, and perform a series of operations such as signing, saving files, and compressing, and then send the information to the resource importing edge node;

[0021] After the importing edge node receives the resource synchronization information transmitted by the cloud center and successfully receives it, it performs message decompression and signature verification operations. After confirming that the information is valid, it integrates the information into the data stored locally. Then, the resource importer establishes a binding relationship with the resources on the resource list and reports the binding information to the cloud center. At this time, both the importing edge node and the cloud center can see that the resources in the list have appeared in the resource cloud pool of the importer, and the entire allocation process ends.

[0022] The beneficial effects of the present invention are as follows:

[0023] Ensure reliable management when the resource cloud pool changes dynamically, taking into account various types of task requirements such as situation awareness, decision-making deployment, etc. For problems such as large network overhead and low synchronization success rate in data synchronization between nodes, by implementing a cloud pool synchronization information processing module, an edge node data synchronization module, a cloud-edge data synchronization module, etc., realize the function of synchronizing all or part of the resource cloud pool data of a certain edge node to the resource cloud pool of the specified other edge node stably, so as to realize the dynamic allocation and deployment of resources in the cloud pool, and achieve the purpose of damaged reorganization and agile optimization. Realize the efficient collaboration, rapid fusion, and natural aggregation and dispersion of resource information at different levels such as cloud, edge, and terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 It is a flowchart of a method for synchronizing resource cloud pool information of edge nodes of a system interoperability operating system. DETAILED DESCRIPTION OF THE INVENTION

[0025] The technical solutions of the present invention will be further described in detail below in conjunction with the drawings and specific embodiments. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the scope of protection of the present invention.

[0026] A method for synchronizing resource cloud pool information of edge nodes of a system interoperability operating system includes the following specific steps:

[0027] (1) Classification of resource cloud pool synchronization information

[0028] When resources are dynamically allocated between different edge nodes, the resource information must also be synchronized from the original edge node to the cloud pool of the new edge node. This information can be divided into basic resource information, topological relationship information, task scheduling information, resource log information, etc.

[0029] The basic information of resources includes: unique resource number, name, corresponding semantic model type, current resource status, IP address, port, communication protocol, etc. Without this information, it is impossible to communicate and control the resources, so this information must be synchronized.

[0030] Topological relationship information refers to the hierarchical relationship or proxy control relationship between resources, such as gateway devices and their sub-devices. It is also a must-transmit message. Otherwise, after the resources are allocated to the new cloud pool, the resources with the original topological relationship may not be used normally.

[0031] Task scheduling information refers to a set of instructions with a sequence and logical rules that are currently scheduled and issued by the edge node or cloud center that controls the resources. It is optional information. If the synchronous task scheduling information is not transmitted during the resource allocation process, the tasks being executed by the resources will be interrupted.

[0032] Resource log information refers to the operating status, instruction execution status, unexpected errors and other information reported by daily resource data. When resources are allocated between different cloud pools, you can choose whether to synchronize log information based on network conditions and actual needs. For example, when the network bandwidth is very small or extremely unstable, you can choose to give up synchronizing log information to ensure that information synchronization can be completed in a shorter time and achieve a higher transmission success rate. However, this will affect functions such as viewing and statistical analysis of resource historical data at the new edge node.

[0033] (2) Compression and Signature of Resource Synchronization Information

[0034] In order to reduce bandwidth consumption and thus improve data synchronization efficiency, resource synchronization information must be compressed before transmission between edge nodes. At the same time, in order to increase security, signature information needs to be added to the information to ensure the reliability of the information source.

[0035] First, the resource transfer edge node takes out the resource cloud pool information to be synchronized from the corresponding storage medium (database, cache, local file, etc.), and then organizes the information into a standard format (JSON / XML) information stream, and then uses the key assigned by the system to each edge node to sign, and attaches the obtained signature to the information stream. After completion, the information stream is saved to a local text file and the file is compressed. Then the file is transferred to the resource transfer edge node.

[0036] (3) Information verification and integration

[0037] After receiving the cloud pool synchronization information sent by the resource transfer-out edge node, the resource transfer-in edge node first decompresses the information and then performs signature verification on the information. If the verification passes, the resource information is integrated into the resource cloud pool of the local system.

[0038] According to the edge node data synchronization module process, including:

[0039] Step 1: The resource transfer-out edge node receives the resource cloud pool transfer-out instruction and the resource list that needs to be transferred out. According to the list and instruction requirements, it extracts the basic information, topological relationship information, task scheduling information, log confidence, etc. that need to be synchronized for the corresponding resources from its own node's resource cloud pool, and signs the data according to the process, then saves the data into a file and compresses it.

[0040] Step 2: The edge node actively releases the binding relationship with the resources on the call-out list and synchronizes the unbinding information to the cloud center. At this time, both the edge node of the resource call-out party and the cloud center will see that the resources in the list are no longer in the call-out party's resource cloud pool.

[0041] Step 3: The edge node of the transfer-in party receives the resource synchronization information from the edge node of the transfer-out party. After successful reception, it performs file decompression, signature verification and other operations. After confirming that the information is valid, it integrates the information into the locally stored data. The transfer-in party then establishes a binding relationship with the resources on the resource list and reports the binding relationship to the cloud center. At this point, both the edge node of the transfer-in party and the cloud center can see that the resources in the list have appeared in the resource cloud pool of the transfer-in party, and the entire deployment process is completed.

[0042] Step 4: When the network condition between the resource-exporting edge node and the resource-input edge node is poor and data synchronization cannot be met, or when an edge node cannot transmit data due to failure or destruction, the process of dynamically allocating resource cloud pools by means of cloud-edge data synchronization is as follows:

[0043] First, since the edge node of the resource caller cannot communicate, the cloud center proactively unbinds the resources in the call-out list from the resource cloud pool of the edge node of the caller.

[0044] The cloud center will then compare the resource list specified in the resource list, extract resource synchronization information from the resource cloud pool of its own node, and perform a series of operations such as signing, saving files, and compression, and then send the information to the resource transfer edge node.

[0045] After receiving the resource synchronization information from the cloud center, the edge node of the transfer-in party successfully decompresses the message and verifies the signature. After confirming that the information is valid, it integrates the information into the locally stored data. The resource transfer-in party then establishes a binding relationship with the resources on the resource list and reports the binding information to the cloud center. At this point, both the edge node of the transfer-in party and the cloud center can see that the resources in the list have appeared in the resource cloud pool of the transfer-in party, and the entire deployment process is completed.

[0046] Unlike edge node data synchronization, during the cloud-edge data synchronization process, it is impossible to determine whether the reason why resources are transferred out of the edge node is due to damage or temporary network problems that cause the connection with the center to be lost. In order to avoid conflicts in issuing instructions and reporting data, after the cloud center unbinds the resource cloud pool that transfers resources out of the edge node, an exclusive flag will be set to refuse to receive the relevant resource data reported by the previous edge node. At the same time, a corresponding flag is also set on the end side. After establishing a binding with the new edge node, it only receives downlink instructions from the currently bound edge node.

[0047] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for synchronizing resource cloud pool information of edge nodes of a system interoperability system, characterized in that: The steps include: (1) Classification of resource cloud pool synchronization information; The resource transfer-out party edge node receives the resource cloud pool transfer-out instruction and the resource list to be transferred out, and retrieves the information that needs to be synchronized from the corresponding resources of its own node from the storage medium according to the list and the instruction requirements; (2) Compression and signing of resource synchronization information; Organize the information into a standard format information stream, then use the key assigned by the system to each edge node to sign it, and attach the obtained signature to the information stream. After completion, save the information stream to a local text file and compress the file; then transfer the file to the resource transfer edge node; (3) Verification and fusion of information; The edge node of the incoming party receives the resource synchronization information from the edge node of the outgoing party. After successful reception, it decompresses the file and verifies the signature. After confirming that the information is valid, it integrates the information into the locally stored data.

2. According to claim 1, a resource cloud pool information synchronization method for edge nodes of a system interoperability system, characterized in that: In the step (1), the basic information of the resource includes the resource unique number, name, corresponding semantic model type, current state of the resource, IP address, port, and communication protocol.

3. The method for synchronizing resource cloud pool information of edge nodes of a system interoperability system according to claim 1, characterized in that: In step (1), the storage medium includes a database, a cache, and a local file.

4. The method for synchronizing resource cloud pool information of edge nodes of a system interoperability system according to claim 1, characterized in that: In the step (2), the format of the information flow is JSON / XML.

5. The method for synchronizing resource cloud pool information of edge nodes of a system interoperability system according to claim 1, characterized in that: In the step (3), the process of synchronizing edge node data includes the following: Step 1: The resource transfer-out edge node receives the resource cloud pool transfer-out instruction and the resource list to be transferred out. According to the list and instruction requirements, it extracts the basic information, topological relationship information, task scheduling information, and log confidence of the corresponding resources that need to be synchronized from the resource cloud pool of its own node, and signs the data according to the process, and then saves the data into a file and compresses it; Step 2: The edge node actively unbinds the resources on the call-out list and synchronizes the unbinding information to the cloud center. At this time, both the edge node and the cloud center will see that the cloud pool of the call-out party no longer has the resources on the list. Step 3: The edge node of the transfer-in party receives the resource synchronization information from the edge node of the transfer-out party. After successful reception, it decompresses the file and performs signature verification operations. After confirming that the information is valid, it integrates the information into the locally stored data. The transfer-in party then establishes a binding relationship with the resources on the resource list and reports the binding relationship to the cloud center. At this point, both the edge node of the transfer-in party and the cloud center can see that the resources in the list have appeared in the resource cloud pool of the transfer-in party, and the entire deployment process is completed.

6. A resource cloud pool information synchronization method for edge nodes of a system interoperability system according to claim 5, characterized in that: When the network condition between the resource-exporting edge node and the resource-input edge node is poor and data synchronization cannot be achieved, or when an edge node cannot transmit data due to a failure or destruction, the process of dynamically allocating resource cloud pools through cloud-edge data synchronization is as follows: First, since the edge node of the resource transfer party cannot communicate, the cloud center actively unbinds the resources in the transfer list from the resource cloud pool of the edge node of the transfer party; The cloud center will then compare the resource list specified in the resource list, extract resource synchronization information from the resource cloud pool of its own node, sign, save files, compress a series of operations, and then send the information to the resource transfer edge node; After receiving the resource synchronization information from the cloud center, the edge node of the transfer-in party successfully decompresses the message and verifies the signature. After confirming that the information is valid, it integrates the information into the locally stored data. The resource transfer-in party then establishes a binding relationship with the resources on the resource list and reports the binding information to the cloud center. At this point, both the edge node of the transfer-in party and the cloud center can see that the resources in the list have appeared in the resource cloud pool of the transfer-in party, and the entire deployment process is completed.

Images