Cloud network communication method, device, electronic equipment and system

By adopting reverse tunneling policy and encryption authentication mechanism between public and private clouds, traditional VPN tunnels have been solved, and the problems of complex configuration, limited scalability, large performance impact and high security risks are achieved, and safe, stable and efficient Data transmission.

CN119052236APending Publication Date: 2024-11-29GLODON CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411023614.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-29
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

The message transmission between the public and private clouds of traditional VPN tunnels has problems such as complex configuration, limited scalability, large performance impact and high security risks.

Method used

Adopting the reverse tunneling strategy, by placing access requests on the engine channel in the hub node of the public cloud, the service nodes of the private cloud actively detect and obtain them, establishing a secure channel for encryption authentication, avoiding firewall rules, NAT and routing configurations, and Implement redundant backup mechanism.

Benefits of technology

It realizes seamless connection between public and private clouds, ensures data transmission security, improves system stability and response speed, and reduces communication latency and unauthorized access risks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119052236A_ABST
    Figure CN119052236A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of wireless communication, and discloses a cloud network communication method, device, electronic equipment and system, and the method comprises the steps: receiving an access request sent by a client, searching whether a central node and a service node which are matched with a target private cloud environment identifier exist in a metadatabase, and if the central node and the service node exist, executing the step 1; if yes, a target hub node and a target service node are determined, the access request is added to an engine channel of the target hub node, and the access request on the engine channel is allowed to be detected and acquired by the target service node; and receiving a response result reported through the engine channel after the target service node obtains the access request, and sending the response result to the client. According to the method, seamless connection between the public cloud environment and the private cloud environment is realized, and the security of the data transmission process is ensured. And firewall rules, network address translation (NAT) and routing configuration do not need to be carried out, and the method is not influenced by distance.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of wireless communication technologies, and in particular to a cloud network communication method, device, electronic equipment and system. Background Art

[0002] Public cloud is a computing resource provided to the general public. It is operated by cloud service providers, and users access and use these resources through the Internet. In a public cloud, the infrastructure is owned by the cloud service provider, and multiple tenants share these resources. Public cloud computing has the characteristics of low cost, high flexibility, and easy access, but there are problems such as data security and privacy protection, because the data is stored in the facilities of the cloud service provider, and users need to trust the provider to properly protect their data. Private cloud is a cloud computing environment for internal use by an enterprise or organization. It is usually deployed in the organization's local data center or on proprietary physical hardware, and is managed and controlled by the organization itself. In a private cloud, both data and applications are stored in the organization's internal network, so it has higher security and controllability.

[0003] At present, Google Cloud Platform (GCP) is used to perform public cloud computing. GCP provides a wealth of computing resources, including virtual machine instances, containers, Kubernetes engines, etc., which can meet the needs of different types of applications. When GCP receives an external request from a user, it forwards the request to the Virtual Private Cloud (VPC) routing. The VPC routing is responsible for managing network traffic and forwarding network traffic from one subnet to another subnet or external network. For example, network traffic is forwarded to a specific server through a pre-established VPN tunnel, which processes the request, generates a response, and returns along the path of the request, and finally returns to the user who initiated the request through the private cloud's VPN gateway, encrypted tunnel, and CloudVPN gateway.

[0004] The above process of forwarding traffic using VPN tunnel has the following defects:

[0005] First, the configuration is complex: Traditional VPNs require complex network-level configuration, including setting firewall rules, Network Address Translation (NAT) and routing policies.

[0006] Second, scalability limitations: VPN scalability may be limited, especially in terms of number of connections and throughput. As the size of the enterprise expands, more hardware and bandwidth resources may be required.

[0007] Third, performance impact: VPN tunnel transmission may reduce network performance during the encryption and decryption process, especially in long-distance communication with high latency, which has a greater impact on transmission performance.

[0008] Fourth, security risks: If the VPN is not configured properly, security vulnerabilities may be introduced. Summary of the invention

[0009] In view of this, the present invention provides a cloud network communication method, device, electronic device and system to solve the many defects of using traditional VPN tunnel to transmit messages between the public cloud and private cloud. The specific scheme is as follows:

[0010] In a first aspect, the present invention provides a cloud network communication method, which is applied to a hub cluster of a public cloud environment, wherein the hub cluster includes at least one hub node, and each hub node is connected to at least one service node of a private cloud environment, and the method includes:

[0011] Receive an access request sent from a client, where the access request includes an identifier of a target private cloud environment that the user requests to access;

[0012] Searching in a metadata database whether there is a hub node and a service node that match the target private cloud environment identifier, wherein the metadata database pre-stores a correspondence between at least one hub node, at least one private cloud environment identifier and a corresponding service node;

[0013] If so, the matching hub node and service node are used as the target hub node and target service node, and the access request is added to the engine channel of the target hub node. The engine channel is used to connect to the target service node, and the access request on the engine channel is allowed to be detected and obtained by the target service node;

[0014] Receive the response result reported by the target service node through the engine channel after obtaining the access request;

[0015] Send the response result to the client.

[0016] In combination with the first aspect, in a possible implementation, a search is performed in the metadata database to determine whether there are hub nodes and service nodes that match the target private cloud environment identifier, including: searching in a pre-stored correspondence to determine whether there is a target correspondence, where the target correspondence is the correspondence between the target private cloud environment identifier, the target hub node, and the target service node.

[0017] In combination with the first aspect, in another possible implementation, before receiving an access request sent from a client, it also includes: obtaining registration information reported by at least one central node in the central cluster, the registration information including: a service node identifier, a private cloud environment identifier where the service node is located, and a central node connected to the service node through an engine channel; determining the correspondence between each central node, the private cloud environment identifier and the service node based on each registration information; and storing at least one determined correspondence in a metadata database.

[0018] In combination with the first aspect, in another possible implementation, before receiving an access request sent from a client, it also includes: judging in real time through heartbeat detection whether the connection with at least one hub node in the hub cluster is normal; if the detection of the first hub node in at least one hub node fails for N consecutive times, it is determined that an abnormality has occurred in the first hub node, and the connection between it and the first hub node is disconnected, and the resources on the first hub node are released.

[0019] In combination with the first aspect, in another possible implementation, the method also includes: when an abnormality is detected in the first hub node, determining a second hub node in the hub cluster that has a backup relationship with the first hub node; transferring relevant information of the first service node and the first private cloud environment connected to the first hub node to the second hub node, and establishing a wireless connection with the second hub node; when an access request is received from the client to the first hub node, forwarding the access request to the second hub node, so that the second hub node sends the access request to a matching service node and obtains a response result.

[0020] In a second aspect, the present invention further provides a cloud network communication method, which is applied to any hub node in a public cloud environment, and the method comprises:

[0021] Obtaining an access request sent from the metadata repository module, where the access request includes an identifier of a private cloud environment that the user requests to access;

[0022] Determine an engine channel corresponding to the private cloud environment identifier, add an access request to the engine channel, the engine channel is used to connect to a service node, and the access request on the engine channel is allowed to be detected and obtained by the service node;

[0023] The receiving service node receives the response result reported through the engine channel after obtaining the access request;

[0024] The response result is sent to the metadata repository module, so that the metadata repository module forwards the response result to the client.

[0025] In combination with the second aspect, in a possible implementation, before obtaining an access request sent from the metadata database module, it also includes: receiving registration information sent from the service node, the registration information including: service node identifier, private cloud environment identifier; sending the registration information to the metadata database module, so that the metadata database module establishes a correspondence between the service node identifier, the private cloud environment identifier and the central node according to the registration information, and stores it in the metadata database.

[0026] In combination with the second aspect, in another possible implementation, the method further includes: creating an engine channel on the central node, and establishing a tunnel between the central node and the service node through the engine channel, the tunnel being used to transmit the client's request message and the corresponding response result.

[0027] In combination with the second aspect, in another possible implementation, after receiving the registration information sent from the service node, it also includes: broadcasting metadata through a synchronization protocol, the metadata including the registration information, the identification and status of the central node, so as to synchronize the information of each central node in the central cluster; when the central node serves as a backup node and the main node fails, a new engine channel is created, and at least one service node associated with the main node is connected through the new engine channel, so as to take over the main node to respond to access requests.

[0028] In a third aspect, the present invention further provides a cloud network communication device, the device comprising:

[0029] A receiving module, used to receive an access request sent from a client, where the access request includes an identifier of a target private cloud environment that the user requests to access;

[0030] A search module is used to search in a metadata database whether there is a hub node and a service node that matches the target private cloud environment identifier, wherein the metadata database pre-stores a correspondence between at least one hub node, at least one private cloud environment identifier and a corresponding service node;

[0031] Add a module to find out if there is a matching hub node and service node, and use them as the target hub node and target service node, and add the access request to the engine channel of the target hub node. The engine channel is used to connect to the target service node, and the access request on the engine channel is allowed to be detected and obtained by the target service node;

[0032] The receiving module is also used to receive the response result reported by the target service node through the engine channel after obtaining the access request;

[0033] The sending module is used to send the response result to the client.

[0034] In a fourth aspect, the present invention further provides a cloud network communication device, the device comprising:

[0035] An acquisition module, used to acquire an access request sent from the metadata repository module, wherein the access request includes an identifier of a private cloud environment that the user requests to access;

[0036] An adding module is used to determine the engine channel corresponding to the private cloud environment identifier, and add the access request to the engine channel. The engine channel is used to connect to a service node, and the access request on the engine channel is allowed to be detected and obtained by the service node;

[0037] A receiving module is used to receive the response result reported by the service node through the engine channel after obtaining the access request;

[0038] The sending module is used to send the response result to the metadata repository module, so that the metadata repository module forwards the response result to the client.

[0039] In a fifth aspect, the present invention also provides an electronic device, comprising a memory and a processor, wherein the memory and the processor are connected; computer instructions are stored in the memory; and the processor executes the computer instructions to execute the cloud network communication method described in the first aspect or any embodiment of the first aspect, or executes the cloud network communication method described in the second aspect or any embodiment of the second aspect.

[0040] In addition, the present invention also provides a computer-readable storage medium, on which computer instructions are stored, and the computer instructions are used to enable a computer to execute the cloud network communication method described in the first aspect or any embodiment of the first aspect, or to execute the cloud network communication method described in the second aspect or any embodiment of the second aspect.

[0041] In a sixth aspect, the present invention further provides a cloud network communication system, the system comprising: a hub cluster and a client located in a public cloud environment, and at least one service node located in a private cloud environment; wherein the hub cluster comprises a metadata library module and at least one hub node;

[0042] A client, used for sending an access request to the metadata repository module of the central cluster;

[0043] A metadata repository module, configured to receive an access request and execute the cloud network communication method described in the first aspect or any one of the implementations of the first aspect;

[0044] A target hub node in at least one hub node, used to execute the cloud network communication method described in the second aspect or any one of the implementations of the second aspect;

[0045] The target service node in at least one service node is used to detect and obtain the access request added by the target hub node to the engine channel; execute the access request to generate a response result; and report the response result to the target hub node through the engine channel.

[0046] The cloud network communication method, device, equipment and system provided in this embodiment adopts a cleverly designed reverse tunnel strategy, that is, the central node in the public cloud places the access request in a safe location, that is, on the engine channel, and the service node in the private cloud actively detects and obtains it on the engine channel, rather than the central node actively sending the access request to the service node. This method not only realizes seamless connection between the public cloud and private cloud environments, but also ensures the security of the data transmission process.

[0047] In addition, since a secure channel is established between the central node of the public cloud and the service node of the private cloud, and the secure channel is pre-encrypted and authenticated, it breaks the physical network boundary and strengthens the defense measures, effectively preventing unauthorized access and data leakage. There is no need for firewall rules, network address translation NAT and routing configuration, and it is not affected by distance. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0049] Figure 1 It is a scene diagram of a cloud network communication system provided by an embodiment of the present invention;

[0050] Figure 2 is a flow chart of a cloud network communication method provided by an embodiment of the present invention;

[0051] Figure 3 It is a signaling flow chart of a cloud network communication method provided by an embodiment of the present invention;

[0052] Figure 4 is a flow chart of another cloud network communication method provided by an embodiment of the present invention;

[0053] Figure 5 It is a structural block diagram of a cloud network transmission device provided by an embodiment of the present invention;

[0054] Figure 6 is a structural block diagram of another cloud network transmission device provided by an embodiment of the present invention;

[0055] Figure 7 It is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0056] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0057] The technical solution provided by the embodiment of the present invention is applied to public cloud and private cloud network architecture. It aims to optimize the instruction transmission and task execution process between public cloud and private cloud, especially to address the many challenges of traditional VPN tunnel methods, such as high latency, instability, limited scalability and security vulnerabilities. The technical solution of the embodiment of the present invention substantially improves the transmission efficiency of operation instructions and the immediacy of task execution by adopting a new network architecture, and significantly enhances the stability and response speed of the system.

[0058] First, the system architecture of this technical solution is introduced.

[0059] See also Figure 1 , is a scene diagram of a cloud network communication system provided in this embodiment. The system includes: a public cloud environment platform, a private cloud environment platform and at least one client.

[0060] The public cloud environment platform (hereinafter referred to as the public cloud environment) includes a central cluster, which includes at least one central node. Figure 1 It is shown that there are two central nodes, namely central node 1 and central node 2. In addition, more or fewer nodes such as central node 3 and central node 4 may be included.

[0061] In addition, the hub cluster may also include a metadata database module and a communication unit, wherein the metadata database module is connected to at least one hub node via the communication unit.

[0062] The metadata repository module may be a core storage module (Metadata Store), which is responsible for maintaining the system status and configuration data and providing a persistent information foundation for the system.

[0063] The communication unit (Informers) is used to provide an event notification mechanism. When the system state changes, the notification is broadcast to related components, such as notifying at least one hub node. The communication unit is also used to establish a communication connection between at least one hub node and the metadata database module, so that each hub node and the metadata database can communicate and transmit.

[0064] Each hub node can be a network node, such as a network server (Pivot Server), providing service discovery for the runtime, and a controller for tunnel communication between hub nodes and engines. Figure 1 As shown, each pivot node includes: a control unit (Pivot Controller), an engine channel (Engine Tunnel) and a registration unit (Meta Register). In addition, each pivot node may also include other more or fewer units or modules, which is not limited in this embodiment.

[0065] Further, Pivot Server: is a network server software used to support Pivot function. Pivot is a data analysis technology that can quickly summarize, classify and analyze large amounts of data. PivotServer provides a centralized platform that can connect to different data sources and perform pivot operations on the server side. It can handle complex data queries and analysis, provide real-time results and visual reports, and facilitate users to make data-driven decisions and insights. Pivot Server can be used in business intelligence and data warehouse systems.

[0066] The Engine Tunnel is used to build a cross-service communication bridge to support data transmission and instruction exchange between different services. The Meta Register is used to manage the registration information of the private cloud environment, ensure that the system's service registration and discovery information is up to date, and achieve real-time data synchronization.

[0067] In addition, other cloud nodes can also be included in the public cloud environment, such as Figure 1 As shown, a cloud node is connected to the client and the hub cluster, and the cloud node includes a runtime service module (Runtime) or (Pivot Runtime). The runtime service module is used to provide the operation of the private cloud SDK (Software Development Kit) and is responsible for all communications between the hub and the service.

[0068] Runtime is a runtime environment used to support running and using Pivot functionality in applications. It is provided by Pivot Server and is used to perform Pivot operations on client computers. By using Pivot Runtime, developers can integrate Pivot functionality into applications, enabling users to perform pivot analysis, summary, and visualization of data. Pivot Runtime provides a set of APIs and tools so that developers can flexibly control the behavior and appearance of Pivot. It can be integrated with different programming languages ​​and development frameworks, enabling applications to take advantage of Pivot functionality to provide more powerful data analysis and visualization capabilities.

[0069] Furthermore, the cloud node may also include one or more functional software. The following three software modules and corresponding functions set on the cloud node are exemplified:

[0070] 1. Action Ops module: used to perform command-type operations, designed to quickly respond to and process short, immediate requests.

[0071] 2.Task Ops module: used to handle task-based operations and support complex task execution processes for time-consuming operations.

[0072] 3. Pivot Discovery module: responsible for the service discovery mechanism, ensuring that system components can dynamically discover and connect to the required services and resources.

[0073] In addition, the cloud node may also include other functional modules, which are not listed one by one in this embodiment.

[0074] A private cloud environment may include at least one service node, and each service node may belong to a private cloud environment. Figure 1 As shown in , private cloud environment 1 includes service node 1, and private cloud environment 2 includes service node 2. It should be understood that one or more service nodes may also be included in a private cloud environment. Optionally, the service node 1 or service node 2 may be a private cloud server, such as an engine server.

[0075] Each Engine Server can be a server-side component used to manage and control specific services or functions in a private cloud environment. In addition, the Engine Server also has the function of executing client access requests. Each Engine Server corresponds to a private cloud environment.

[0076] Each service node includes a connection channel, a processing unit, and a K8s service module. The connection channel is used to establish a secure tunnel with the engine channel for ping / pong communication.

[0077] In this embodiment, the service node acts as a powerful backend (as an edge-deployed server) for executing specific tasks, and can host Shell and Python executors, as well as scalable action processing capabilities. It provides operations and task execution such as K8s, Shell, Python, and supports containerized deployment within a Kubernetes (K8s) cluster. Kubernetes is an open source container orchestration platform for automated deployment, expansion, and management of containerized applications. It can manage multiple containerized applications and provide automated load balancing, self-healing capabilities, and dynamic scheduling of containers.

[0078] exist Figure 1 In the public cloud environment, each hub node communicates with the service node in the private cloud environment through a tunnel. The tunnel is a private communication channel created on the public network and connected to the engine channel of the hub node for secure data transmission.

[0079] According to an embodiment of the present invention, a cloud network communication method embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0080] In this embodiment, a cloud network communication method is provided, which can be applied to Figure 1 More specifically, a metadata repository module in a central cluster may be applied, and the metadata repository module may be set / integrated on a network node.

[0081] like Figure 1 As shown, the process includes:

[0082] Step 101: receiving an access request sent from a client, wherein the access request includes an identifier of a target private cloud environment that the user requests to access.

[0083] In one implementation, a user generates an access request to a private cloud through a client, and the access request includes a target private cloud environment identifier, such as private cloud environment 1, and is sent to a cloud node on a public cloud through the access request. After receiving the access request from the client, the cloud node forwards the access request to the metadata repository module in the central cluster, and the metadata repository module receives the access request accordingly.

[0084] Step 102: Search the metadata database to see whether there are hub nodes and service nodes that match the target private cloud environment identifier.

[0085] The metadata database pre-stores a correspondence between at least one central node, at least one private cloud environment identifier and a corresponding service node.

[0086] This step specifically includes: searching whether there is a target corresponding relationship in the pre-stored corresponding relationship, and the target corresponding relationship is the corresponding relationship between the target private cloud environment identifier, the target hub node and the target service node. For example, searching whether there is a private cloud environment identifier 1 in the pre-stored corresponding relationship, if so, then continue to search whether there is a corresponding relationship in the private cloud environment table 1, that is, a corresponding relationship between (private cloud environment table 1, service node) and the hub node, if so, then determine that the corresponding relationship is the target corresponding relationship. In this example, assuming that a corresponding relationship is pre-established between private cloud environment table 1, service node 1 and hub node 1, then the corresponding relationship is determined as the target corresponding relationship.

[0087] On the contrary, if the private cloud environment table 1 is not found, or the private cloud environment table 1 exists but there is no corresponding relationship established with the private cloud environment table 1, it is determined that the matching hub node and service node are not found. This access request fails.

[0088] Step 103: If the search in step 102 exists, the matching hub node and service node are used as the target hub node and target service node, and the access request is added to the engine channel of the target hub node.

[0089] The engine channel is used to connect to the target service node, and the access request on the engine channel is allowed to be detected and obtained by the target service node.

[0090] Specifically, when the metadata database module determines that the target service node is service node 1 and the target hub node is hub node 1 after searching in step 102, it is determined that the user's request to access private cloud environment 1 has a corresponding relationship with service node 1 and hub node 1. The access request is added to the message queue, which is set on the engine channel of hub node 1. The access request on the engine channel can be detected and obtained in real time by the service node 1 connected thereto.

[0091] Step 104: receiving a response result reported by the target service node through the engine channel after obtaining the access request.

[0092] Specifically, the target service node obtains the access request, parses and executes the access request to generate a response result, and then transmits the response result to the engine channel of the target hub node through a secure tunnel. The target hub node then sends the corresponding result to the metadata database module through a communication unit.

[0093] In the private cloud, the target service node retrieves the request data from the tunnel through the ping / pong communication mechanism. After receiving the instruction, the target service node performs the operation specified by the request. After the operation is completed, the response result is sent back to the tunnel through the same ping / pong communication mechanism and then transmitted to the target hub node.

[0094] The metadata database module receives the response result reported by the target central node.

[0095] Step 105: The metadata database module sends the response result to the client.

[0096] Complete an access request and response operation process.

[0097] The cloud network communication method provided in this embodiment adopts a cleverly designed reverse tunnel strategy, that is, the central node in the public cloud places the access request in a safe location, that is, on the engine channel, and the service node in the private cloud actively detects and obtains it on the engine channel, rather than the central node actively sending the access request to the service node. This method not only realizes seamless connection between the public cloud and private cloud environments, but also ensures the security of the data transmission process.

[0098] In addition, since a secure channel is established between the central node of the public cloud and the service node of the private cloud, and the secure channel is pre-encrypted and authenticated, it breaks the physical network boundary and strengthens the defense measures, effectively preventing unauthorized access and data leakage. There is no need for firewall rules, network address translation NAT and routing configuration, and it is not affected by distance.

[0099] Optionally, in a possible implementation of this embodiment, the above step 101, before receiving the access request sent by the client, further includes:

[0100] Obtain registration information reported by at least one central node in the central cluster, the registration information including: a service node identifier, a private cloud environment identifier where the service node is located, and a central node connected to the service node through an engine channel; determine the correspondence between each central node, the private cloud environment identifier and the service node based on each of the registration information; and store at least one of the determined correspondences in the metadata database.

[0101] For example, when service node 1 or service node 2 is connected to a private cloud environment, it must first be registered. Through the registration unit on the central node, its own node identifier and the private cloud environment identifier are registered in the registration unit, so that the registration unit establishes a corresponding relationship between (private cloud environment identifier, service node) and (central node), and stores the corresponding relationship in the metadata database in preparation for finding the corresponding target central node and target service node in subsequent access requests (cloud requests).

[0102] It should be noted that a central node can be connected to one or more private cloud environments, and then the registration unit of each central node can obtain the registration information of one or more service nodes.

[0103] In addition, the method provided in this embodiment further includes, before step 101: receiving an access request sent from a client:

[0104] Heartbeat detection is used to determine in real time whether the connection with at least one hub node in the hub cluster is normal; if the detection of the first hub node in at least one hub node fails N times in a row, it is determined that an abnormality has occurred in the first hub node, and the connection between it and the first hub node is disconnected, and the resources on the first hub node are released.

[0105] Heartbeat detection: The system uses a two-way heartbeat mechanism to ensure the stability of network connections and the activity of nodes. The central node performs regular heartbeat detection on the engine. If the detection fails several times in a row, the connection with the engine will be disconnected and related resources will be released. Conversely, the engine will also perform heartbeat detection on the central node so that it can quickly perform failover when a central node fails to ensure the continuity of task processing.

[0106] In some possible implementations, the method of this embodiment also includes a redundant backup switching step. Specifically, when an abnormality is detected in the first hub node, a second hub node having a backup relationship with the first hub node is determined in the hub cluster; relevant information of the first service node and the first private cloud environment connected to the first hub node is transferred to the second hub node, and a wireless connection with the second hub node is established.

[0107] Assume that there is a master-slave relationship between the first hub node (hub node 1) and the second hub node (hub node 2), the first hub node is the master node, and the second hub node is the backup node. When receiving an access request from a client to the first hub node, the access request is forwarded to the second hub node, so that the second hub node sends the access request to a matching service node and obtains a response result.

[0108] In the active-standby redundant node relationship, the metadata repository synchronizes the messages / data of the two nodes in real time. One synchronization method is to broadcast metadata updates between each hub node in the hub cluster through a synchronization protocol to ensure that the data remains consistent and up-to-date during the failover process of any node. The hub node design includes multi-node redundant deployment, each node can independently process requests and synchronize status. When the primary node, such as hub node 1, fails, the backup node (hub node 2) can take over seamlessly and continue to process instructions from the Runtime and management engine tasks.

[0109] See also Figure 3 , is a signaling flow chart of a cloud network communication method provided by another embodiment of the present invention. Figure 1 The system architecture comprises the following steps:

[0110] First, the preparation stage: the private cloud link registration stage: establish a correspondence between at least one central node, at least one private cloud environment identifier and the corresponding service node, and store it in the metadata database.

[0111] Preparation process 1: During the registration phase of the private cloud, the central cluster establishes N corresponding relationships, each of which is an association between a service node, such as an Engine server, and at least one central node, such as a Pivot server.

[0112] Among them, a Pivot server can establish an association relationship with one or more Engine servers. Since each Engine server corresponds to a private cloud environment, for example, different private cloud environments can be distinguished by environment ID, so the above-mentioned establishment of a corresponding relationship is equivalent to establishing a corresponding relationship between each group (including private cloud environment ID, Engine server) and Pivotserver module. In this example, assuming N = 2, two corresponding relationships are established, as follows:

[0113] A first correspondence between (private cloud environment ID 1, service node 1) and hub node 1;

[0114] The second correspondence between (private cloud environment ID 2, service node 2) and central node 2.

[0115] The metadata database module stores these corresponding relationships in the core storage module (Metadata Store).

[0116] Preparation process 2: Establish the engine channel.

[0117] The hub cluster establishes a secure tunnel between the engine channel of each hub node and the connection channel of the service node. For example, secure tunnel 1 is established between Engine server 1 and Pivot server module 1, and secure tunnel 2 is established between Engine server 2 and Pivot server module 2.

[0118] In this example, the secure tunnel 1 and the secure tunnel 2 are both ping / pong tunnels.

[0119] Secondly, access the execution phase of the request method:

[0120] Step 201: The client generates an access request based on a user operation, which is a cloud request, and sends the access request to a cloud node of the public cloud.

[0121] Correspondingly, the cloud node of the public cloud (including the runtime module) receives an access request from the client, and the access request includes the ID of the target private cloud environment requested for access.

[0122] Step 202: After receiving the access request, the cloud node forwards the access request to the metadata repository module in the central cluster.

[0123] Step 203: After receiving the access request, the metadatabase module searches for a target pivot node (Pivot server) and a target service node (Engine server) that match the target private cloud environment ID in at least one corresponding relationship stored in the metadatabase.

[0124] Assuming that the target private cloud environment ID carried in the access request is private cloud environment ID 1, the metadata database stores the correspondence between the private cloud environment ID 1, service node 1 and the hub node. The correspondence is established and stored in the above-mentioned "preparation step", and after searching, it is determined that the matching target hub node is hub node 1 and the target service node is service node 1.

[0125] Step 204: The metadata repository module determines the engine channel and adds the access request to the engine channel of the target hub node.

[0126] If the target hub node is connected to two or more service nodes of the private cloud environment, the target private cloud environment and the target service node are first determined according to the target correspondence. Since the target service node is only connected to one engine channel, the engine channel connected to the target service node can be determined, and then the metadata library module adds the access request to the engine channel of the target hub node. At the same time, the channel monitoring function is started.

[0127] In this example, the hub node 1 adds the access request to its corresponding engine channel so that the service node 1 can detect and obtain the access request in real time.

[0128] Step 205: The target service node detects in real time whether there is an access request on the secure tunnel; if yes, execute step 206. If no, continue to detect and monitor.

[0129] Step 206: When the target service node detects an access request on the engine channel, it reversely obtains the access request, executes the access request, and generates a response result.

[0130] For example, service node 1 obtains the access request from the engine channel of hub node 1, that is, retrieves the access request data from secure tunnel 1 through the ping / pong communication mechanism. After receiving the access request, service node 1 performs the operation specified in the request. After the operation is completed, a response result is generated.

[0131] Step 207: The target service node reports the response result to the target hub node through the engine channel.

[0132] The target service node sends the corresponding results back to the tunnel through the same ping / pong mechanism, and then transmits them to the target hub node.

[0133] Step 208: The target central node monitors the channel, and once it detects that a target service node has fed back a response result, it obtains the response result and sends the response result to the metadata database module.

[0134] In this example, the central node 1 sends the response result to the metadata database module through the communication unit Informers.

[0135] Step 209: After receiving the response result, the metadata database module sends the response result to the cloud node, which then forwards it to the client, completing the entire request-response cycle.

[0136] The method provided by this implementation transmits access requests, feedback response results, and intermediate data packets and messages, which complies with the communication protocol and implements a reverse communication mechanism by introducing raw connection support, thereby improving network transmission security.

[0137] In addition, in the above step 204, after receiving the metadata information, the target hub node also determines if a custom authentication method is set, and then performs connection authentication, and initializes the corresponding tunnel of the engine channel for use in turnover, mailing and forwarding request data.

[0138] In another embodiment of the present invention, Figure 4As shown, a cloud network communication method is also disclosed, which is applied to any hub node in a public cloud environment, such as the target hub node or hub node 1 in the above embodiment, and the method includes:

[0139] Step 301: Obtain an access request sent from a metadata repository module, wherein the access request includes an identifier of a private cloud environment that a user requests to access.

[0140] Step 302: Determine the engine channel corresponding to the private cloud environment identifier, and add the access request to the engine channel. The engine channel is used to connect to a service node, and the access request on the engine channel is allowed to be detected and obtained by the service node; this step is the same as step 204 of the previous embodiment. The specific process is described in the previous embodiment, and will not be repeated here.

[0141] Step 303: The receiving service node reports a response result through the engine channel after obtaining the access request.

[0142] Step 304: Send the response result to the metadata repository module, so that the metadata repository module forwards the response result to the client. The specific process corresponds to step 207 and step 208 of the above embodiment, please refer to the description of the above embodiment, and will not be repeated here.

[0143] Optionally, in some specific implementations, step 301, before obtaining the access request sent from the metadata database module, further includes: receiving registration information sent from the service node, the registration information including: service node identifier, private cloud environment identifier; sending the registration information to the metadata database module, so that the metadata database module establishes a corresponding relationship between the service node identifier, the private cloud environment identifier and the hub node according to the registration information, and stores it in the metadata database. This process corresponds to the method flow of the "registration phase" of the aforementioned embodiment, and will not be repeated here.

[0144] Optionally, in some other specific implementations, the method further includes: creating an engine channel on the hub node, and establishing a tunnel between the hub node and the service node through the engine channel, the tunnel being used to transmit the client's request message and the corresponding response result. Figure 1 As shown, the tunnel is a secure tunnel between the engine channel and the connection channel, and is also a ping / pong tunnel.

[0145] Optionally, in some further specific implementations, after receiving the registration information sent from the service node, the hub node further includes:

[0146] Metadata is broadcasted through a synchronization protocol, wherein the metadata includes the registration information, the identifier and the status of the hub node, so as to synchronize the information of each hub node in the hub cluster.

[0147] When the central node serves as a backup node and a main node fails, a new engine channel is created, and at least one service node associated with the main node is connected through the new engine channel to take over the main node to respond to access requests.

[0148] This implementation is mainly used for failover. The central node design includes multi-node redundant deployment. Each node can independently process requests and synchronize status. When the main node fails, the backup node can take over seamlessly and continue to process instructions from the Runtime and manage engine tasks, thereby ensuring uninterrupted service.

[0149] In this embodiment, a cloud network communication device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0150] This embodiment provides a cloud network communication device, which can be used to implement part or all of the functions of the metadata library module, such as Figure 5 As shown, the device comprises:

[0151] The receiving module 510 is used to receive an access request sent from a client, where the access request includes an identifier of a target private cloud environment that the user requests to access.

[0152] The search module 520 is used to search in the metadata database whether there is a central node and a service node that match the target private cloud environment identifier. The metadata database pre-stores the correspondence between at least one central node, at least one private cloud environment identifier and the corresponding service node.

[0153] Adding module 530 is used to find and, if they exist, use the matching hub node and service node as the target hub node and target service node, and add the access request to the engine channel of the target hub node. The engine channel is used to connect to the target service node, and the access request on the engine channel is allowed to be detected and obtained by the target service node.

[0154] The receiving module 510 is further configured to receive a response result reported by the target service node through the engine channel after obtaining the access request.

[0155] The sending module 540 is used to send the response result to the client.

[0156] In addition, in another embodiment, the present invention also provides another cloud network communication device, which can be used to implement part or all of the functions of the aforementioned hub node, such as Figure 6 As shown, the device comprises:

[0157] The acquisition module 610 is used to acquire an access request sent from the metadata repository module, wherein the access request includes an identifier of a private cloud environment that a user requests to access.

[0158] Adding module 620 is used to determine the engine channel corresponding to the private cloud environment identifier, add the access request to the engine channel, the engine channel is used to connect to a service node, and the access request on the engine channel is allowed to be detected and obtained by the service node.

[0159] The receiving module 630 is used to receive a response result reported by the service node through the engine channel after obtaining the access request.

[0160] The sending module 640 is used to send the response result to the metadata repository module, so that the metadata repository module forwards the response result to the client.

[0161] It should be noted that the above Figure 5 or Figure 6 The device shown may also include other more or fewer modules, such as a storage module, etc., which is not limited in this embodiment.

[0162] In addition, the cloud network communication device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC circuit, a processor and a memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions. The further functional description of each of the above modules and units is the same as that of the above corresponding embodiment, and will not be repeated here.

[0163] In addition, an embodiment of the present invention further provides a cloud network communication system, the system comprising: a hub cluster and a client located in a public cloud environment, and at least one service node located in a private cloud environment; wherein the hub cluster comprises a metadata library module and at least one hub node. Specifically, the architecture of the system can be found in Figure 1 and the aforementioned Figure 1 The corresponding embodiment description will not be repeated here.

[0164] Wherein, the client is used to send an access request to the metadata library module of the central cluster;

[0165] Metadatabase module, used to receive access requests and execute Figure 2Steps 101 to 105 shown in FIG. 101, or execute steps 101 to 10 Figure 3 Step 203 is shown.

[0166] At least one of the target hub nodes is used to execute Figure 4 The method steps shown, or Figure 3 Step 204 and step 207.

[0167] The target service node in at least one service node is used to detect and obtain the access request added to the engine channel by the target hub node; execute the access request to generate a response result; and report the response result to the target hub node through the engine channel. That is, the aforementioned steps 205 and 206 are executed.

[0168] For the specific process, please refer to the previous Figure 3 The embodiment shown is not described in detail here.

[0169] The system provided by the embodiment of the present invention has the following beneficial effects:

[0170] 1. Enhanced throughput: The design of multiple parallel tunnels has greatly improved the throughput of data transmission, ensuring smooth data flow even during peak load periods.

[0171] 2. Enhanced security architecture: More sophisticated access control mechanisms and security policies have been introduced to adapt to evolving security threats, providing a solid layer of protection for sensitive data transmission.

[0172] 3. Reduced communication delay: By optimizing the network communication process, unnecessary transfer and processing are reduced, further reducing the overall delay of command transmission and task execution, providing users with a faster interactive experience.

[0173] The embodiment of the present invention also provides an electronic device having the above Figure 5 or Figure 6 The cloud network communication device shown.

[0174] Figure 71 is a schematic diagram of the structure of an electronic device provided by an optional embodiment of the present invention, the electronic device includes: one or more processors 10, a memory 20 and at least one communication interface 30, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the electronic device, including instructions stored in or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple electronic devices can be connected, and each device provides part of the necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 7 A processor 10 is taken as an example.

[0175] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0176] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the cloud network communication method shown in the above embodiment.

[0177] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function; the data storage area may store data / information such as access requests or response results. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the electronic device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0178] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0179] The electronic device also includes an input and output device. The processor 10, the memory 20, and the input and output device can be connected via a bus or other means. Further, the input device can receive input digital or character information, and generate key signal input related to the user settings and function control of the electronic device, such as a touch screen, a keypad, a mouse, a trackpad, a touchpad, an indicator rod, one or more mouse buttons, a trackball, a joystick, etc. The output device may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display.

[0180] It should be noted that the electronic device in this embodiment may be any node in the aforementioned embodiments, such as a hub node or a service node, or may also be a cloud node including a metadata library module, etc.

[0181] In addition, the structure of the client sending the access request can also be as follows Figure 7 The structure shown may also be other structures, which are not limited in the present invention.

[0182] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be downloaded through a network and originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor or hardware, the cloud network communication method shown in the above embodiment is implemented.

[0183] An embodiment of the present invention provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the cloud network communication method of any embodiment of the present invention.

[0184] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A cloud network communication method, characterized in that: A central cluster applied to a public cloud environment, wherein the central cluster includes at least one central node, each central node is connected to at least one service node of a private cloud environment, and the method includes: Receiving an access request sent from a client, wherein the access request includes an identifier of a target private cloud environment that the user requests to access; Searching in a metadata database whether there is a hub node and a service node that matches the target private cloud environment identifier, wherein the metadata database pre-stores a correspondence between at least one hub node, at least one private cloud environment identifier and a corresponding service node; If so, the matching hub node and service node are used as the target hub node and target service node, and the access request is added to the engine channel of the target hub node, the engine channel is used to connect to the target service node, and the access request on the engine channel is allowed to be detected and obtained by the target service node; Receiving a response result reported by the target service node through the engine channel after obtaining the access request; The response result is sent to the client.

2. The method according to claim 1, characterized in that The searching in the metadata database for whether there is a hub node and a service node matching the target private cloud environment identifier includes: A search is performed to determine whether a target corresponding relationship exists in the pre-stored corresponding relationships, wherein the target corresponding relationship is a corresponding relationship between the target private cloud environment identifier, the target hub node, and the target service node.

3. The method according to claim 1, characterized in that: Before receiving the access request sent by the client, the method further includes: Acquire registration information reported by at least one hub node in the hub cluster, the registration information including: a service node identifier, a private cloud environment identifier where the service node is located, and a hub node connected to the service node through an engine channel; Determine the correspondence between each hub node, the private cloud environment identifier and the service node according to each of the registration information; The determined at least one corresponding relationship is stored in the metadata database.

4. The method according to any one of claims 1 to 3, characterized in that: Before receiving the access request sent by the client, the method further includes: Determine in real time through heartbeat detection whether the connection with at least one hub node in the hub cluster is normal; If the detection of the first hub node among at least one hub node fails N times in succession, it is determined that the first hub node is abnormal, and the connection between it and the first hub node is disconnected, and the resources on the first hub node are released.

5. The method according to claim 4, characterized in that The method further comprises: When detecting that the first hub node is abnormal, determining a second hub node in the hub cluster that has a backup relationship with the first hub node; Transferring information related to the first service node and the first private cloud environment connected to the first hub node to the second hub node, and establishing a wireless connection with the second hub node; When receiving an access request sent from the client to the first hub node, the access request is forwarded to the second hub node, so that the second hub node sends the access request to a matching service node and obtains a response result.

6. A cloud network communication method, characterized in that: Applied to any hub node in a public cloud environment, the method includes: Obtaining an access request sent from a metadata repository module, wherein the access request includes an identifier of a private cloud environment that a user requests to access; Determine an engine channel corresponding to the private cloud environment identifier, and add the access request to the engine channel, where the engine channel is used to connect to a service node, and the access request on the engine channel is allowed to be detected and obtained by the service node; receiving a response result reported by the service node through the engine channel after obtaining the access request; The response result is sent to the metadata repository module, so that the metadata repository module forwards the response result to the client.

7. The method according to claim 6, characterized in that Before obtaining the access request sent by the metadata repository module, the method further includes: Receiving registration information sent from the service node, the registration information including: a service node identifier and a private cloud environment identifier; The registration information is sent to the metadata database module, so that the metadata database module establishes a corresponding relationship between the service node identifier, the private cloud environment identifier and the hub node according to the registration information, and stores the corresponding relationship in the metadata database.

8. The method according to claim 6, characterized in that The method further comprises: An engine channel is created on the central node, and a tunnel is established between the central node and the service node through the engine channel. The tunnel is used to transmit the client's request message and the corresponding response result.

9. The method according to claim 8, characterized in that After receiving the registration information sent by the service node, the method further includes: Broadcasting metadata through a synchronization protocol, the metadata including the registration information, the identifier and status of the hub node, so as to synchronize information of each hub node in the hub cluster; When the hub node serves as a backup node and a main node fails, a new engine channel is created, and at least one service node associated with the main node is connected through the new engine channel to take over the main node to respond to access requests.

10. A cloud network communication device, characterized in that: The device comprises: A receiving module, configured to receive an access request sent from a client, wherein the access request includes an identifier of a target private cloud environment that the user requests to access; A search module, used to search in a metadata database whether there is a hub node and a service node that match the target private cloud environment identifier, wherein the metadata database pre-stores a correspondence between at least one hub node, at least one private cloud environment identifier and a corresponding service node; An adding module, used for finding and using the matching hub node and service node as the target hub node and target service node if they exist, and adding the access request to the engine channel of the target hub node, the engine channel is used to connect to the target service node, and the access request on the engine channel is allowed to be detected and obtained by the target service node; The receiving module is further used to receive a response result reported by the target service node through the engine channel after obtaining the access request; A sending module is used to send the response result to the client.

11. A cloud network communication device, characterized in that: The device comprises: An acquisition module, used to acquire an access request sent from a metadata repository module, wherein the access request includes an identifier of a private cloud environment that a user requests to access; An adding module, used to determine an engine channel corresponding to the private cloud environment identifier, and add the access request to the engine channel, wherein the engine channel is used to connect to a service node, and the access request on the engine channel is allowed to be detected and obtained by the service node; A receiving module, configured to receive a response result reported by the service node through the engine channel after obtaining the access request; The sending module is used to send the response result to the metadata database module, so that the metadata database module forwards the response result to the client.

12. An electronic device, characterized in that: comprising a memory and a processor, wherein the memory and the processor are connected; The memory stores computer instructions; The processor executes the cloud network communication method according to any one of claims 1 to 5 or any one of claims 6 to 9 by executing the computer instructions.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute any one of claims 1 to 5, or any one of claims 6 to 9.

14. A cloud network communication system, characterized in that: The system comprises: a hub cluster and a client located in a public cloud environment, and at least one service node located in a private cloud environment; wherein the hub cluster comprises a metadata library module and at least one hub node; The client is used to send an access request to the metadata repository module of the central cluster; The metadata library module is used to receive the access request and execute the cloud network communication method according to any one of claims 1 to 5; The target hub node in the at least one hub node is used to execute the cloud network communication method described in any one of claims 6 to 9; The target service node in the at least one service node is used to detect and obtain the access request added by the target hub node to the engine channel; execute the access request to generate a response result; and report the response result to the target hub node through the engine channel.