Cloud network system, communication method, device, storage medium and program product

By setting up proxy nodes in the second cloud network and configuring forwarding rules, the problem of network segment conflicts in multi-cloud environments is solved, ensuring that access requests are accurately forwarded to the target cloud service, improving user experience and system stability.

CN118488101BActive Publication Date: 2024-11-22ALIBABA CLOUD COMPUTING CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410948677.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-07-15
Publication Date
2024-11-22
Estimated Expiration
2044-07-15

AI Technical Summary

Technical Problem

In a multi-cloud environment, due to overlapping network segments of different cloud manufacturers, resulting in network segment conflict issues, and access requests may be wrongly forwarded to the wrong cloud service, affecting user usage.

Method used

Set up a proxy node in the second cloud network and pre-configure the domain name of the proxy node on the client node corresponding to the cloud service. The client node obtains its IP address based on the domain name of the proxy node and forwards the access request to the proxy node. The proxy node Requests are forwarded to the target service node according to pre-configured forwarding rule information to avoid forwarding to nodes in the same network segment.

Benefits of technology

Effectively avoid network segment conflicts, ensure that access requests are accurately forwarded to the target cloud service, and improve user experience and system stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118488101B_ABST
    Figure CN118488101B_ABST
Patent Text Reader

Abstract

The embodiments of the present application provide a cloud network system, a communication method, a device, a storage medium and a program product. Among them, a proxy node is set in the second cloud network, and the domain name of the proxy node is configured on the client node corresponding to the cloud service. When the client node accesses the cloud service in the second cloud network, the IP address of the proxy node is obtained based on the domain name of the proxy node, and the target access request to access the cloud service in the second cloud network is forwarded to the proxy node according to the IP address of the proxy node; the proxy node forwards the target access request to the target service node providing the target cloud service according to the pre-configured forwarding rule information for describing the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network, rather than forwarding it to the node in the first cloud network that belongs to the same network segment as the target service node, thereby avoiding network segment conflicts.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of network technology, and in particular to a cloud network system, communication method, device, storage medium and program product. Background Art

[0002] With the application and popularization of cloud computing, more and more users are beginning to deploy application systems on the cloud. In order to improve the stability of application systems, multi-cloud environments have become the preferred solution for users to deploy application systems. That is, based on the characteristics of the application system, the requirements for network bandwidth quality, the sensitivity of data and other factors, the application system is deployed by relying on cloud services provided by multiple cloud computing vendors, and the advantages of multi-cloud environments are used to protect users from risks such as system interruptions.

[0003] However, different cloud vendors may have overlapping network segment divisions, that is, cloud services from different cloud vendors may use the same network segment. This may lead to network segment conflicts in a multi-cloud environment. That is, when a user requests to access a cloud service from a certain cloud vendor based on an Internet Protocol (IP) address, the access request may be mistakenly forwarded to a cloud service from another cloud vendor that uses the same network segment, affecting user usage. Summary of the invention

[0004] Multiple aspects of the present application provide a cloud network system, a communication method, a device, a storage medium, and a program product to avoid network segment conflicts between multiple clouds.

[0005] The embodiment of the present application provides a cloud network system, including: a first cloud network and a second cloud network that are independent of each other; a proxy node and at least one service node that provides at least one cloud service are deployed in the second cloud network; wherein the network segment to which the service node belongs is the same as part of the network segment maintained by the first cloud network; the network segment to which the proxy node belongs is different from each network segment maintained by the first cloud network; the cloud network system further includes: a client node corresponding to the at least one cloud service, the client node being pre-configured with a domain name of the proxy node;

[0006] The client node is used to respond to the access demand information of the target service node in the at least one service node, obtain the Internet Protocol IP address of the proxy node based on the domain name of the proxy node; and send a target access request to the proxy node according to the IP address of the proxy node;

[0007] The proxy node is pre-configured with forwarding rule information for forwarding the target access request to the target service node according to the forwarding rule information, wherein the forwarding rule information is used to describe the forwarding relationship between each access request received by the proxy node and the at least one service node.

[0008] The embodiment of the present application also provides a communication method, which is applicable to a client node corresponding to at least one cloud service; the first cloud network and the second cloud network are independent of each other, and the second cloud network is deployed with a proxy node and at least one service node that provides the at least one cloud service; wherein the network segment to which the service node belongs is the same as part of the network segment maintained by the first cloud network; the network segment to which the proxy node belongs is different from each network segment maintained by the first cloud network; the method comprises:

[0009] Obtaining a pre-configured domain name of the proxy node;

[0010] In response to the access demand information of the target service node in the at least one service node, acquiring the Internet Protocol IP address of the proxy node based on the domain name of the proxy node;

[0011] According to the IP address of the proxy node, a target access request is sent to the proxy node, so that the proxy node forwards the target access request to the target service node according to pre-configured forwarding rule information; the forwarding rule information is used to describe the forwarding relationship between each access request received by the proxy node and the at least one service node.

[0012] The embodiment of the present application also provides a communication method, which is applicable to a proxy node deployed in a second cloud network, wherein the second cloud network is independent of the first cloud network, and the second cloud network is further deployed with at least one service node that provides at least one cloud service; wherein the network segment to which the service node belongs is the same as part of the network segments maintained by the first cloud network; and the network segment to which the proxy node belongs is different from each network segment maintained by the first cloud network; the method comprises:

[0013] Receiving a target access request sent by a client node; the client node is a client node corresponding to the at least one cloud service and is configured with a domain name of the proxy node; the target access request is sent by the IP address of the proxy node of the client node; the IP address of the proxy node is obtained by the client node based on the pre-configured domain name of the proxy node;

[0014] According to pre-configured forwarding rule information, the target access request is forwarded to a target service node in the at least one service node; the forwarding rule information is used to describe the forwarding relationship between each access request received by the proxy node and the at least one service node.

[0015] An embodiment of the present application also provides an electronic device, comprising: a memory, a processor and a communication component; wherein the memory is used to store a computer program; the processor is coupled to the memory and the communication component, and is used to execute the computer program to execute the steps in the above-mentioned communication methods.

[0016] An embodiment of the present application also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed by one or more processors, the one or more processors are caused to execute the steps in the above-mentioned communication methods.

[0017] An embodiment of the present application also provides a computer program product, including a computer program. When the computer program is executed by one or more processors, the one or more processors are caused to execute the steps in the above-mentioned communication methods.

[0018] In an embodiment of the present application, a proxy node is set in the second cloud network, and the domain name of the proxy node is pre-configured on the client node corresponding to the cloud service. In this way, when the client node needs to access the cloud service in the second cloud network, the client node can obtain the IP address of the proxy node based on the domain name of the proxy node, and forward the target access request for accessing the cloud service in the second cloud network to the proxy node according to the IP address of the proxy node; the proxy node forwards the target access request to the target service node providing the target cloud service according to the pre-configured forwarding rule information for describing the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network, rather than forwarding it to the node in the first cloud network that belongs to the same network segment as the target service node, thereby avoiding network segment conflicts. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0020] Figure 1 A schematic diagram of the structure of the cloud network system provided for the traditional solution;

[0021] Figure 2a and Figure 2b A schematic diagram of the structure of a cloud network system provided in an embodiment of the present application;

[0022] Figure 3 A schematic diagram of the structure of another cloud network system provided in an embodiment of the present application;

[0023] Figure 4 A schematic diagram of the forwarding rule information configuration process provided in an embodiment of the present application;

[0024] Figure 5 A schematic diagram of the configuration effect of the forwarding rule information provided in the embodiment of the present application;

[0025] Figure 6 and Figure 7 A flow chart of a communication method provided in an embodiment of the present application;

[0026] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0028] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0029] Multi-cloud deployment means that users deploy applications or service systems in cloud services provided by different cloud vendors. For example, users rent servers provided by cloud vendor A and use cloud security services provided by cloud vendor B in these servers to ensure the data security of the servers. In actual use, different cloud vendors may overlap in network segment division, that is, cloud services of different cloud vendors may use the same network segment. For example, cloud vendors are accustomed to reserving 100 network segments for use by cloud vendors' control or service nodes, and will not allocate them to users, which may cause network segment conflicts.

[0030] like Figure 1 As shown, the networks of the first cloud network and the second cloud network are independent of each other. The networks of the first cloud network and the second cloud network are independent of each other, which means that the first cloud network and the second cloud network have independent network environments, are isolated from each other, and have independent IP address segments and autonomous management permissions. Generally, the first cloud network and the second cloud network belong to different cloud vendors, but are not limited to this. Optionally, the first cloud network and the second cloud network may also be different cloud networks belonging to the same cloud vendor. Figure 1The cloud boundary in the term "cloud boundary" refers to the isolation boundary between the first cloud network and the second cloud network. The first cloud network and the second cloud network include at least one service node, which can provide cloud services. The cloud services may be, but are not limited to, cloud security services, cloud communication services, distributed lock services, data storage services, or cloud computing services. In addition, it should be noted that the cloud services provided by service nodes in different cloud networks may be the same or different. In addition to cloud services, service nodes in a cloud network may also provide various computing, storage, network and other resources for users to deploy applications. The user's application may be a cloud service provided by a cloud network, or other applications that rely on cloud services.

[0031] In this scenario, the network segment to which the service node 201 in the second cloud network belongs is the same as the network segment to which the service node 202 in the first cloud network belongs. Figure 1 The example in which both network segments belong to is 100 is used for illustration, but this does not constitute a limitation. Figure 1 In the application scenario shown, the user can deploy an application in the first cloud network, and the application uses the cloud service provided by the second cloud network. For example, the user's application is deployed in a service node of the first cloud network, and the cloud service provided by the service node 201 of the second cloud network is used to provide relevant services for the application deployed in the first cloud network. For the convenience of description and distinction, the node deployed by the user in the first cloud network and needing to use the cloud service provided by the service node 201 in the second cloud network is called the client node 10. Of course, the user can also deploy the application in the second cloud network and use the cloud service provided in the first cloud network; and the user can also deploy the application in the same cloud network and use the cloud service provided in the same cloud network. In this embodiment, the focus is on the scenario in which the user deploys the application in a certain cloud network and uses the cloud service provided in another cloud network, and the user deploys the application in the first cloud network, and the application uses the cloud service provided by the service node 201 in the second cloud network as a client node as an example to start the description.

[0032] The cloud service in the second cloud network may disclose the link address of the cloud service for users to access. When using the cloud service in the second cloud network, the user may access the link address of the cloud service. Accordingly, the client node 10 may respond to the access request information for the cloud service and request the domain name resolution node 30 to resolve the domain name of the cloud service (corresponding to Figure 1 Step 1). The domain name resolution node 30 can perform domain name resolution on the domain name of the cloud service to obtain the IP address of the cloud service, that is, the IP address of the service node 201 providing the cloud service; and return the IP address of the service node 201 providing the cloud service to the client node 10 (corresponding to Figure 1 Step 2).

[0033] Since the service node 201 providing the cloud service and the service node 202 in the first cloud network belong to the same network segment, that is, there is a network segment conflict between the service node 201 providing the cloud service and the service node 202 in the first cloud network, the client node 10 will not send the access request for the cloud service to the service node 201 in the second cloud network, but forward it to the service node 202 in the first cloud network (corresponding to Figure 1 Step 3) causes the access request to be forwarded incorrectly, making it impossible to use the cloud services in the second cloud network, affecting user usage.

[0034] In order to resolve network segment conflicts, in some embodiments of the present application, a proxy node is set in the second cloud network, and the domain name of the proxy node is pre-configured on the client node corresponding to the cloud service. In this way, when the client node needs to access the cloud service in the second cloud network, the client node can obtain the IP address of the proxy node based on the domain name of the proxy node, and forward the target access request for accessing the cloud service in the second cloud network to the proxy node according to the IP address of the proxy node; the proxy node forwards the target access request to the target service node that provides the target cloud service according to the pre-configured forwarding rule information for describing the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network, rather than forwarding it to the node in the first cloud network that belongs to the same network segment as the target service node, thereby avoiding network segment conflicts.

[0035] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0036] It should be noted that the same reference numerals denote the same objects in the following drawings and embodiments, and therefore, once an object is defined in one drawing or embodiment, it does not need to be further discussed in the subsequent drawings and embodiments.

[0037] Figure 2a , Figure 2b and Figure 3 A schematic diagram of the structure of the cloud network system provided in the embodiment of the present application. Figure 2a , Figure 2b and Figure 3 The cloud network system includes: a first cloud network and a second cloud network that are independent of each other. For explanation of network independence, please refer to the above content and will not be repeated here.

[0038] In this embodiment, at least one service node 201 is deployed in the second cloud network. Among them, the service node 201 can provide cloud services. In this application, the cloud service provided by the service node 201 can be a cloud service of any function, such as cloud security services, cloud communication services, distributed lock services, data storage services, cloud computing services, Runtime Application Self-protection (RASP) services and cloud assistant services. One or more. Multiple refers to 2 or more. In an embodiment of the present application, the service node 201 providing the same cloud service can be implemented as one or more physical machines, and multiple refers to 2 or more. Of course, different cloud services can also be deployed on the same physical machine.

[0039] In the embodiment of the present application, the nodes that provide the same cloud service are collectively referred to as a service node. A service node 201 can be implemented as a device, apparatus, virtual machine (VM), container or software functional module that provides cloud services. The device that provides cloud services can be a single server device or a cloud-based server array. In addition, the device that provides cloud services can also refer to other computing devices with corresponding service capabilities, such as terminal devices such as computers (running service programs), etc. In this embodiment, the service node 201 can be deployed in the cloud, such as in a central cloud. Among them, the service node 201 corresponds to the cloud service one-to-one. Accordingly, there is at least one service node that provides at least one cloud service. The number of general service nodes is the same as the number of cloud services.

[0040] In the embodiment of the present application, the user uses the cloud services provided by the first cloud network and the second cloud network to deploy related applications and implement multi-cloud environment deployment. In the embodiment of the present application, only the example of the user's application in the first cloud network needing to use the cloud service in the second cloud network is used for illustrative explanation, but it does not constitute a limitation.

[0041] In addition to the system embodiments provided in the above embodiments, the present application also provides a communication method. The following is an exemplary description of the communication method provided in the embodiments of the present application from the perspectives of the client node and the proxy node. If a user wants to use the cloud service in the second cloud network, the client node 10 corresponding to the cloud service is required. The client node 10 refers to the node where the client corresponding to the cloud service is deployed, and can be deployed with the device, apparatus, VM, container or software function module of the client corresponding to the cloud service. Figure 2a As shown, the client node 10 can be deployed in the first cloud network. Accordingly, if the user's application in the first cloud network wants to use the cloud service in the second cloud network, it is necessary to deploy the client node 10 corresponding to the cloud service in the first cloud network. Figure 2bAs shown, the client node 10 can also be deployed in other cloud networks other than the first cloud network and the second cloud network, such as a third cloud network. The network segments maintained by the third cloud network are different from the network segments maintained by the second cloud network. The third cloud network is also independent of the first cloud network and the second cloud network, such as the third cloud network, the first cloud network, and the second cloud network belong to different cloud vendors.

[0042] In this embodiment, the network segment to which the service node 201 belongs may be partially identical to or different from the network segment maintained by the first cloud network. Since the network segment to which the service node 201 belongs is different from the network segment maintained by the first cloud network, there is no network segment conflict. Therefore, the embodiment of the present application is mainly described for the scenario in which the network segment to which the service node 201 belongs is the same as part of the network segment maintained by the first cloud network. Figure 2a , Figure 2b and Figure 3 In the figure, the network to which the service node 201 belongs is illustrated as the same network segment as the first cloud network, which is the network segment 100, but this does not constitute a limitation.

[0043] In the embodiment of the present application, in order to solve the network segment conflict problem between the first cloud network and the second cloud network, a proxy node 40 is deployed in the second cloud network.

[0044] In the embodiment of the present application, the specific implementation form of the proxy node 40 is not limited. The proxy node 40 can be implemented as a computing device, an apparatus, a VM, a container or a software function module, etc. The proxy node 40 and the service node 201 can be on the same physical machine or on different physical machines.

[0045] In the embodiment of the present application, in order to ensure that the proxy node 40 does not cause a network segment conflict, the network segment to which the proxy node 40 belongs can be configured to be different from the network segments maintained by the first cloud network. Further, the domain name of the proxy node 40 can be pre-configured in the client node 10. When the client node 10 needs to access the cloud service provided by the service node 201, the client node 10 can respond to the access demand information for the service node 201 and obtain the IP address of the proxy node 40 based on the domain name of the proxy node 40. In each embodiment of the present application, for the convenience of description and distinction, the cloud service that the client node 10 needs to access is defined as the target cloud service; and the service node 201 that provides the target cloud service is defined as the target service node 201.

[0046] The client node 10 obtains the access requirement information for the service node 201, and the access requirement information is a trigger condition for the client node 10 to execute the step of obtaining the IP address of the proxy node 40 based on the domain name of the proxy node 40. That is, when the client node 10 has an access requirement for the service node 201, it starts to execute the step of obtaining the IP address of the proxy node 40 based on the domain name of the proxy node 40. The access requirement information refers to the requirement for reflecting the access purpose or intention of the client node 10 to the target cloud service, and may include: the access purpose or intention, and the identification information of the service node 201 or the identification information of the cloud service provided by the service node 201, etc. The client node 10 may determine that the service node 201 belongs to the second cloud network according to the identification information of the service node 201 or the identification information of the cloud service provided by the service node 201 contained in the access description information, and the belonging relationship between the service node 201 and the cloud network, and then obtain the domain name of the proxy node 40 deployed in the second cloud network from the pre-configured domain name of the proxy node, and further perform domain name resolution on the domain name of the proxy node 40 through the domain name server to obtain the IP address of the proxy node 40.

[0047] Accordingly, if Figure 2a and Figure 2b As shown, the client node 10 can respond to the access request information of the target service node 201, and obtain the IP address of the proxy node 40 (corresponding to Figure 2a and Figure 2b Step 1). Specifically, Figure 3 As shown in step 1, the client node 10 may request the Domain Name System (DNS) resolution node 30 in the first cloud network to perform domain name resolution on the domain name of the proxy node 40. Specifically, the proxy node 40 may send a DNS request to the DNS resolution node 30. The DNS request may include the domain name of the proxy node 40 to request the DNS server to perform domain name resolution on the domain name of the proxy node. The DNS resolution node 30 may respond to the DNS request, perform domain name resolution on the domain name of the proxy node to obtain the IP address corresponding to the domain name of the proxy node; and return the IP address corresponding to the domain name of the proxy node to the proxy node 40 (corresponding to Figure 3 Step 2). The IP address corresponding to the domain name of the proxy node is the IP address of the proxy node 40 . Figure 3 The diagram only takes the case where the client node 10 is deployed in the first cloud network as an example. Of course, the client node 10 may also be deployed in other cloud networks other than the first cloud network and the second cloud network, such as the third cloud network.

[0048] Accordingly, the client node 10 may receive the IP address of the proxy node, and send a target access request (corresponding to Figure 2a and Figure 2b Step 2 and Figure 3 Step 3). Specifically, the client node 10 may generate a target access request whose request body is the access requirement information and the destination IP address is the IP address of the proxy node 40. Based on the destination IP address, the proxy node 40 may send the target access request to the proxy node 40, thereby forwarding the target access request for accessing the target service node from the first cloud network instead of forwarding it to a node in the first cloud network that belongs to the same network segment as the target service node, thereby avoiding network segment conflicts.

[0049] Since the client node 10 needs to access the target service node that provides the target cloud service, the proxy node 40 also needs to forward the target access request to the target service node 201. In order to enable the proxy node 40 to forward the target access request to the target service node 201, the proxy node 40 may be pre-configured with a description of the forwarding relationship between each access request received by the proxy node and the service nodes in the second cloud network. Accordingly, the proxy node 40 is pre-configured with forwarding rule information. The forwarding rule information is used to describe the forwarding relationship between each access request received by the proxy node 40 and the service nodes in the second cloud network. Accordingly, the proxy node 40 may forward the target access request to the target service node 201 (corresponding to the forwarding rule information) according to the forwarding rule information. Figure 3 Step 3 and Figure 3 Step 4).

[0050] Specifically, the proxy node 40 can determine the target service node to which the target access request is to be forwarded based on the forwarding rule information used to describe the forwarding relationship between each access request received by the proxy node 40 and the service node in the second cloud network; and forward the target access request to the target service node 201.

[0051] In the embodiments of the present application, the specific implementation form of the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network is not limited. In some embodiments, the port of the proxy node can be bound to the cloud service in advance. The port of the proxy node is a virtual port, which refers to the port inside the proxy node. Optionally, each port of the proxy node can be bound to a cloud service. In this way, for the scenario where there is at least one cloud service in the aforementioned second cloud network, at least one port of the proxy node can be bound to the at least one cloud service. For the scenario where there are multiple cloud services in the second cloud network, multiple ports of the proxy node can be bound to multiple cloud services respectively, wherein one port is bound to one cloud service. Since the cloud service corresponds to the service node, after the port of the proxy node is bound to the cloud service, the service node corresponding to each port is also determined, that is, the service node corresponding to each port is the service node that provides the cloud service bound to the port. Accordingly, the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network may include: a corresponding relationship between at least one port of the proxy node and at least one service node.

[0052] In an embodiment of the present application, the forwarding rule information in the proxy node 40 is pre-configured. For the proxy node 40, the forwarding rule configuration information can be obtained. The forwarding rule configuration information may include: the port to be configured and the identifier of the service node corresponding to the port to be configured. The identifier of the service node corresponding to the port to be configured contained in the forwarding rule configuration information is the identifier of the service node providing cloud services in the second cloud network. The identifier of the service node can be information that uniquely identifies a service node, and can be an IP address, number or identity (Identity, ID) of the service node, etc.

[0053] In the embodiment of the present application, the specific implementation form of the proxy node 40 obtaining the forwarding rule configuration information is not limited. Figure 4 As shown, the proxy node 40 corresponds to the proxy control node 50, and the proxy control node 50 is deployed in the second cloud network. The proxy control node 50 can provide a forwarding rule configuration page ( Figure 4 (not shown), the user or technician can configure the corresponding service node for the port of the proxy node 40 through the forwarding rule configuration page. Further, the proxy control node 50 can obtain the forwarding rule configuration information configured based on the forwarding rule configuration page, that is, obtain the port to be configured and the identifier of the service node corresponding to the port to be configured. Based on this, the proxy node 40 can obtain the forwarding rule configuration information from the proxy control node 50.

[0054] Among them, maintenance personnel can directly configure forwarding rules through the forwarding rule configuration page, without the need for maintenance personnel to learn configuration files such as Extensible Markup Language (XML), which can improve the convenience of forwarding rule configuration and facilitate user use.

[0055] In some embodiments, the proxy control node 50 may send the forwarding rule configuration information to the proxy node 40, and the proxy node 40 receives the forwarding rule configuration information sent by the proxy control node 50. Alternatively, the proxy node 40 may pull the forwarding rule configuration information from the proxy control node 50. Optionally, the proxy node 40 may periodically pull the forwarding rule configuration information from the proxy control node 50 according to a set configuration period.

[0056] The proxy node 40 configures the forwarding rule information based on the obtained forwarding rule configuration information. The forwarding rule configuration information includes: the port to be configured and the identifier of the service node corresponding to the port to be configured. Among them, the port to be configured includes the port of the proxy node 40 mentioned above, such as Figure 4 Port A and port B shown, etc. The identifier of the service node includes: the identifier of the service node in the second cloud network. Further, the proxy node 40 can start the port to be configured according to the identifier of the port to be configured and the service node corresponding to the port to be configured included in the forwarding rule configuration information, and generate a corresponding relationship between the port of the aforementioned proxy node and the service node in the second cloud network.

[0057] The forwarding rule configuration information may include one or more ports to be configured, where multiple refers to two or more. For an embodiment in which there are multiple ports to be configured, multiple ports of the proxy node are bound to multiple cloud services, and the multiple ports correspond to the service nodes corresponding to the multiple cloud services. For example, Figure 5 As shown, port A is bound to the cloud security service, then port A corresponds to the service node that provides the cloud security service; port B is bound to the RASP service, then port B corresponds to the service node that provides the RASP service; port C is bound to the cloud assistant service, then port C corresponds to the service node that provides the cloud assistant service; the extended port is bound to other cloud services, then the extended port corresponds to the service node that provides other services.

[0058] By generating the correspondence between the multiple ports of the proxy node and the multiple service nodes in the second cloud network in the above manner, the proxy multi-tenancy problem is solved, that is, the client nodes 10 corresponding to the multiple cloud services can access the corresponding cloud services in the second cloud network through the proxy node 40, and there is no problem of network segment conflict. The client node 10 can access any cloud service in the second cloud network through the proxy node in the same or similar manner, and can refer to the relevant contents of the above and later embodiments.

[0059] In an embodiment of the present application, the proxy node 40 can obtain new forwarding rule configuration information when the configured port is turned on; and based on the new forwarding rule configuration information, start a new port, and establish a corresponding relationship between the new port and the new service node. In this way, the hot start of the new port and the new forwarding rule information can be achieved without interrupting the forwarding process of the proxy node 40, which helps to improve the service performance of the proxy node.

[0060] In some embodiments, the proxy node 40 may obtain forwarding rule configuration information in the process of forwarding the aforementioned target access request. The ports to be configured included in the forwarding rule configuration information are other ports on the proxy node except for the aforementioned at least one port. The proxy node 40 can start the ports to be configured and start the corresponding relationship between the ports to be configured and their corresponding service nodes according to the identifiers of the ports to be configured and the service nodes corresponding to the ports to be configured included in the currently acquired forwarding rule configuration information without interrupting the forwarding process of the target access request. This is the new forwarding rule information. In this way, the hot start of the new forwarding information rule can be achieved without interrupting the forwarding process of the proxy node 40, which helps to improve the service performance of the proxy node.

[0061] In this embodiment, the binding relationship between the port of the proxy node and the cloud service is open to the public, that is, the proxy node 40 publicly discloses the binding relationship between the port and the cloud service. For the client node 10, the cloud service to be accessed, that is, the target cloud service, can be determined based on the access demand information; and based on the binding relationship between the port of the proxy node and the cloud service, the target port bound to the cloud service to be accessed can be obtained; further, a target access request with the destination IP address being the IP address of the proxy node and the destination port being the target port can be generated. Since the destination IP address of the target access request is the IP address of the proxy node and the destination port is the target port on the proxy node, the client node can send the target access request to the proxy node 40, thereby forwarding the target access request to the target service node from the first cloud network, rather than forwarding it to a node in the first cloud network that belongs to the same network segment as the target service node, thereby avoiding network segment conflicts.

[0062] The proxy node 40 may receive a target access request on the target port. Since the correspondence between the port of the proxy node and the service node in the second cloud network is preconfigured, the proxy node 40 may forward the target access request to the service node corresponding to the target port based on the relationship between the port and the service node in the second cloud network. The service node corresponding to the target port is the target service node.

[0063] Specifically, the proxy node 40 can determine the service node corresponding to the target port based on the correspondence between its port and the service node in the second cloud network, that is, determine the target service node, and establish a network channel between the target port and the target service node; thereafter, the target access request can be forwarded to the target service node through the network channel.

[0064] In this embodiment, a proxy node is set in the second cloud network, and the domain name of the proxy node is pre-configured on the client node corresponding to the target cloud service. In this way, when the client node needs to access the cloud service in the second cloud network, the client node can obtain the IP address of the proxy node based on the domain name of the proxy node, and forward the target access request for accessing the cloud service in the second cloud network to the proxy node according to the IP address of the proxy node; the proxy node forwards the target access request to the target service node providing the target cloud service according to the pre-configured forwarding rule information for describing the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network, rather than forwarding it to the node in the first cloud network that belongs to the same network segment as the target service node, thereby avoiding network segment conflicts.

[0065] To improve the availability of the proxy node, multiple proxy nodes 40 can be set, that is, the cloud network system includes multiple proxy nodes 40, and the working principle of each proxy node 40 is the same as the pre-configured forwarding rule information. Multiple proxy nodes 40 have the same IP address. Multiple proxy nodes 40 can form a load balancing (Server Load Balancing, SLB) cluster. Accordingly, a load balancing (SLB) node (not shown in the figure) can also be deployed in the second cloud network. The SLB node can balance the access request between multiple proxy nodes 40.

[0066] Optionally, the SLB node may balance the access request among multiple proxy nodes 40 according to a preset load balancing strategy. For example, the SLB node may balance the access request among multiple proxy nodes 40 according to a preset polling load balancing strategy. That is, the SLB node may distribute each access request to multiple proxy nodes 40 one by one in chronological order. Alternatively, the SLB node may balance the access request among multiple proxy nodes 40 according to the weight of the proxy node. Among them, the weight is used to specify the polling probability, and the weight of the proxy node is proportional to the access ratio, which is used in the case of uneven performance of the proxy node. The higher the weight of the proxy node, the greater the probability of being accessed. Alternatively, the SLB node may balance the access request among multiple proxy nodes 40 according to the IP hash (IP_hash) strategy. The IP hash strategy refers to hashing the source IP address of each access request, and each access request is distributed to the proxy node according to the hash result of the source IP address, so that each access user's request accesses a fixed proxy node. Alternatively, the SLB node may balance the access request among multiple proxy nodes 40 according to the Fair strategy. The Fair strategy is to distribute access requests according to the response time of multiple proxy nodes, giving priority to allocating access requests to proxy nodes with short response times.

[0067] Figure 6 Schematic diagram of the flow of the communication method provided in the embodiment of the present application. The communication method is mainly applicable to the client node in the first cloud network. Figure 6 As shown, the communication method mainly includes:

[0068] 601. Obtain a domain name of a pre-configured proxy node.

[0069] 602. In response to access demand information of a target service node in at least one service node, obtain an IP address of the proxy node based on the domain name of the proxy node.

[0070] 603. Send a target access request to the proxy node according to the IP address of the proxy node, so that the proxy node forwards the target access request to the target service node according to the forwarding rule information; the forwarding rule information is used to describe the forwarding relationship between each access request received by the proxy node and at least one service node.

[0071] Figure 7 1 is a flow chart of another communication method provided in an embodiment of the present application. The communication method is mainly applicable to the proxy node in the second cloud network. Figure 7 As shown, the communication method mainly includes:

[0072] 701. Receive a target access request sent by a deployed client node; the client node is a client node corresponding to at least one cloud service and is configured with a domain name of a proxy node; the target access request is sent by the IP address of the client node proxy node; the IP address of the proxy node is obtained by the client node based on the pre-configured domain name of the proxy node.

[0073] 702. Forward the target access request to a target service node in at least one service node according to pre-configured forwarding rule information; the forwarding rule information is used to describe the forwarding relationship between each access request received by the proxy node and at least one service node.

[0074] In this embodiment, the first cloud network and the second cloud network are independent of each other, the second cloud network is deployed with a proxy node and at least one service node that provides at least one cloud service; the client node is a client node corresponding to at least one cloud service; wherein the network segment to which the service node belongs is the same as part of the network segment maintained by the first cloud network; the network segment to which the proxy node belongs is different from each network segment maintained by the first cloud network. The client node can be deployed in the first cloud network, or in other cloud networks except the first cloud network and the second cloud network. Figure 6 The communication method shown is mainly applicable to client nodes. Figure 7 The communication method shown is mainly applicable to the proxy node in the second cloud network. Regarding the implementation forms of the service node, proxy node, client node and cloud service, please refer to the relevant content of the aforementioned system embodiment, which will not be repeated here.

[0075] In an embodiment of the present application, in order to solve the problem of network segment conflict between the first cloud network and the second cloud network, a proxy node is deployed in the second cloud network. In an embodiment of the present application, in order to ensure that the proxy node does not cause network segment conflict, the network segment to which the proxy node belongs can be configured to be different from the network segments maintained by the first cloud network. Further, the domain name of the proxy node can be pre-configured on the client node. When the client node needs to access the cloud service provided by the service node, in step 601, the domain name of the proxy node can be obtained; and in step 602, in response to the access demand information for the service node, the IP address of the proxy node is obtained based on the domain name of the proxy node. In each embodiment of the present application, for the convenience of description and distinction, the cloud service that the client node needs to access is defined as the target cloud service; and the service node that provides the target cloud service is defined as the target service node.

[0076] Accordingly, in response to the access requirement information for the target service node, the IP address of the proxy node can be obtained based on the domain name of the proxy node. Specifically, the domain name resolution node in the first cloud network can be requested to perform domain name resolution on the domain name of the proxy node, and the IP address returned by the domain name resolution node can be received as the IP address of the proxy node. Further, in step 603, a target access request can be sent to the proxy node according to the IP address of the proxy node. Specifically, a target access request can be generated with the request body being the access requirement information and the destination IP address being the IP address of the proxy node. Based on the destination IP address, the proxy node 40 can send the target access request to the proxy node, thereby forwarding the target access request to the target service node from the first cloud network instead of forwarding it to a node in the first cloud network that belongs to the same network segment as the target service node, thereby avoiding network segment conflicts.

[0077] Since the client node needs to access the target service node that provides the target cloud service, the proxy node also needs to forward the target access request to the target service node. In order to enable the proxy node to forward the target access request to the target service node, the proxy node may be pre-configured to describe the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network. Accordingly, the proxy node is pre-configured with forwarding rule information. The forwarding rule information is used to describe the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network. Accordingly, for the proxy node, in step 701, the target access request sent by the client node deployed in the first cloud network may be received; and in step 702, the target access request may be forwarded to the target service node according to the forwarding rule information.

[0078] Specifically, the target service node to which the target access request is to be forwarded can be determined based on the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network described in the forwarding rule information; and the target access request is forwarded to the target service node.

[0079] In the embodiments of the present application, the specific implementation form of the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network is not limited. In some embodiments, the port of the proxy node can be bound to the cloud service in advance. The port of the proxy node is a virtual port, which refers to the port inside the proxy node. Optionally, each port of the proxy node can be bound to a cloud service. In this way, for the scenario where there is at least one cloud service in the aforementioned second cloud network, at least one port of the proxy node can be bound to the at least one cloud service. For the scenario where there are multiple cloud services in the second cloud network, multiple ports of the proxy node can be bound to multiple cloud services respectively, wherein one port is bound to one cloud service. Since the cloud service corresponds to the service node, after the port of the proxy node is bound to the cloud service, the service node corresponding to each port is also determined, that is, the service node corresponding to each port is the service node that provides the cloud service bound to the port. Accordingly, the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network may include: a corresponding relationship between at least one port of the proxy node and at least one service node.

[0080] In an embodiment of the present application, the forwarding rule information in the proxy node is pre-configured. For the proxy node, the forwarding rule configuration information can be obtained. The forwarding rule configuration information may include: the port to be configured and the identifier of the service node corresponding to the port to be configured. The identifier of the service node corresponding to the port to be configured contained in the forwarding rule configuration information is the identifier of the service node providing cloud services in the second cloud network. The identifier of the service node may be information that uniquely identifies a service node, and may be an IP address, number or identity (Identity, ID) of the service node, etc.

[0081] In the embodiments of the present application, the specific implementation form of the proxy node obtaining the forwarding rule configuration information is not limited. In some embodiments, the proxy node corresponds to a proxy control node, and the proxy control node is deployed in the second cloud network. The proxy control node can provide a forwarding rule configuration page, and the user or technician can use the forwarding rule configuration page to configure the corresponding service node for the port of the proxy node. Further, the proxy control node 50 can obtain the forwarding rule configuration information configured based on the forwarding rule configuration page, that is, obtain the port to be configured and the identifier of the service node corresponding to the port to be configured. Based on this, the proxy node can obtain the forwarding rule configuration information from the proxy control node.

[0082] Among them, maintenance personnel can directly configure forwarding rules through the forwarding rule configuration page, without the need for maintenance personnel to learn XML and other configuration files, which can improve the convenience of forwarding rule configuration and facilitate user use.

[0083] In some embodiments, the proxy control node may send forwarding rule configuration information to the proxy node, and the proxy node receives the forwarding rule configuration information sent by the proxy control node. Alternatively, the proxy node may pull forwarding rule configuration information from the proxy control node. Optionally, the proxy node may periodically pull forwarding rule configuration information from the proxy control node according to a set configuration period.

[0084] The proxy node is based on the forwarding rule configuration information obtained. The forwarding rule configuration information includes: the port to be configured and the identifier of the service node corresponding to the port to be configured. The identifier of the service node includes: the identifier of the service node in the second cloud network. Further, the proxy node can start the port to be configured according to the port to be configured and the identifier of the service node corresponding to the port to be configured contained in the forwarding rule configuration information, and generate a corresponding relationship between the port of the aforementioned proxy node and the service node in the second cloud network.

[0085] The forwarding rule configuration information may include one or more ports to be configured, where multiple refers to 2 or more. For an embodiment in which there are multiple ports to be configured, multiple ports of the proxy node are bound to multiple cloud services, and the multiple ports correspond to the service nodes corresponding to the multiple cloud services.

[0086] By generating the correspondence between the multiple ports of the proxy node and the multiple service nodes in the second cloud network in the above manner, the proxy multi-tenancy problem is solved, that is, the client nodes corresponding to the multiple cloud services can access the corresponding cloud services in the second cloud network through the proxy node, and there is no problem of network segment conflict. The client node can access any cloud service in the second cloud network through the proxy node in the same or similar manner, and can refer to the relevant contents of the above and later embodiments.

[0087] In an embodiment of the present application, the proxy node can obtain new forwarding rule configuration information when the configured port is opened; and start a new port based on the new forwarding rule configuration information, and establish a corresponding relationship between the new port and the new service node. In this way, the hot start of the new port and the new forwarding rule information can be achieved without interrupting the forwarding process of the proxy node, which helps to improve the service performance of the proxy node.

[0088] In some embodiments, the proxy node may obtain forwarding rule configuration information in the process of forwarding the aforementioned target access request. The ports to be configured included in the forwarding rule configuration information are other ports on the proxy node except for the aforementioned at least one port. The proxy node can start the port to be configured according to the identifier of the port to be configured and the service node corresponding to the port to be configured included in the currently acquired forwarding rule configuration information without interrupting the forwarding process of the target access request, and start the correspondence between the port to be configured and the corresponding service node, which is the new forwarding rule information. In this way, the hot start of the new forwarding information rule can be achieved without interrupting the forwarding process of the proxy node, which helps to improve the service performance of the proxy node.

[0089] In this embodiment, the binding relationship between the port of the proxy node and the cloud service is public, that is, the proxy node discloses the binding relationship between the port and the cloud service. For the client node, the cloud service to be accessed, that is, the target cloud service, can be determined based on the access demand information; and based on the binding relationship between the port of the proxy node and the cloud service, the target port bound to the cloud service to be accessed can be obtained; further, a target access request with the destination IP address being the IP address of the proxy node and the destination port being the target port can be generated. Since the destination IP address of the target access request is the IP address of the proxy node and the destination port is the target port on the proxy node, the client node can send the target access request to the proxy node, thereby forwarding the target access request to the target service node from the first cloud network, rather than forwarding it to a node in the first cloud network that belongs to the same network segment as the target service node, thereby avoiding network segment conflicts.

[0090] For the proxy node, the target access request can be received on the target port. Since the correspondence between the port of the proxy node and the service node in the second cloud network is pre-configured, the proxy node can forward the target access request to the service node corresponding to the target port based on the relationship between the port and the service node in the second cloud network. The service node corresponding to the target port is the target service node.

[0091] Specifically, the proxy node can determine the service node corresponding to the target port based on the correspondence between its port and the service node in the second cloud network, that is, determine the target service node, and establish a network channel between the target port and the target service node; thereafter, the target access request can be forwarded to the target service node through the network channel.

[0092] In this embodiment, a proxy node is set in the second cloud network, and the domain name of the proxy node is pre-configured on the client node corresponding to the target cloud service. In this way, when the client node needs to access the cloud service in the second cloud network, the client node can obtain the IP address of the proxy node based on the domain name of the proxy node, and forward the target access request for accessing the cloud service in the second cloud network to the proxy node according to the IP address of the proxy node; the proxy node forwards the target access request to the target service node providing the target cloud service according to the pre-configured forwarding rule information for describing the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network, rather than forwarding it to the node in the first cloud network that belongs to the same network segment as the target service node, thereby avoiding network segment conflicts.

[0093] In order to improve the availability of the proxy node, multiple proxy nodes can be set, that is, the cloud network system includes multiple proxy nodes, and the working principle of each proxy node is the same as the pre-configured forwarding rule information. Multiple proxy nodes have the same IP address. Multiple proxy nodes can form a load balancing (SLB) cluster. Accordingly, a load balancing (SLB) node can also be deployed in the second cloud network. The SLB node can balance access requests among multiple proxy nodes. For the specific implementation method of SLB balancing access requests among multiple proxy nodes, please refer to the relevant content of the aforementioned system embodiment, which will not be repeated here.

[0094] It should be noted that the execution subject of each step of the method provided in the above embodiment can be the same device, or the method can be executed by different devices. For example, the execution subject of steps 601 and 602 can be device A; for another example, the execution subject of step 601 can be device A, and the execution subject of step 602 can be device B; and so on.

[0095] In addition, in some of the processes described in the above embodiments and the accompanying drawings, multiple operations appearing in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this document or may be executed in parallel, and the sequence numbers of the operations, such as 601, 602, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel.

[0096] Accordingly, an embodiment of the present application also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed by one or more processors, the one or more processors are caused to execute the steps in the above-mentioned communication methods.

[0097] An embodiment of the present application also provides a computer program product, including a computer program. When the computer program is executed by one or more processors, the one or more processors are caused to execute the steps in the above-mentioned communication methods.

[0098] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 8 As shown, the electronic device includes: a memory 80a, a processor 80b and a communication component 80c. The memory 80a is used to store computer programs.

[0099] The processor 80b is coupled to the memory 80a and the communication component 80c, and is used to execute the computer program to execute the steps of the communication method provided in the above embodiments. The specific implementation of each step can be found in the relevant description of the above embodiments, which will not be repeated here.

[0100] In some optional embodiments, such as Figure 8 As shown, the electronic device may also include optional components such as a power supply component 80d, a display component 80e and an audio component 80f. Figure 8 The components are shown schematically only, and do not mean that the electronic device must include Figure 8 The components shown do not necessarily mean that the electronic device can only include Figure 8 Components shown.

[0101] in addition, Figure 8 The components in the dashed box are optional components, not mandatory components, and may depend on the product form of the electronic device. The electronic device of this embodiment may be implemented as a terminal device such as a desktop computer, a laptop computer, a mobile phone, or an IoT device; or it may be various server devices such as a traditional server, a cloud server, or a server cluster.

[0102] In an embodiment of the present application, the memory is used to store a computer program and can be configured to store various other data to support operations on the device where it is located. Among them, the processor can execute the computer program stored in the memory to implement the corresponding control logic. The memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (Static Random-Access Memory, SRAM), electrically erasable programmable read only memory (Electrically Erasable Programmable Read Only Memory, EEPROM), erasable programmable read only memory (Electrical Programmable Read Only Memory, EPROM), programmable read only memory (Programmable Read Only Memory, PROM), read only memory (Read Only Memory, ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0103] In the embodiment of the present application, the processor may be any hardware processing device that can execute the logic of the above method. Optionally, the processor may be a central processing unit (CPU), a graphics processing unit (GPU) or a microcontroller unit (MCU); it may also be a field programmable gate array (FPGA), a programmable array logic device (PAL), a general array logic device (GAL), a complex programmable logic device (CPLD) or other programmable devices; or it may be an advanced reduced instruction set (RISC) processor (Advanced RISC Machines, ARM) or a system on chip (System on Chip, SoC), etc., but not limited thereto.

[0104] In an embodiment of the present application, the communication component is configured to facilitate wired or wireless communication between the device in which it is located and other devices. The device in which the communication component is located can access a wireless network based on a communication standard, such as Wireless Fidelity (WiFi), 2G or 3G, 4G, 5G or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component can also be implemented based on Near Field Communication (NFC) technology, Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology or other technologies.

[0105] In an embodiment of the present application, the display component may include a liquid crystal display (LCD) and a touch panel (TP). If the display component includes a touch panel, the display component may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0106] In an embodiment of the present application, a power supply component is configured to provide power to various components of the device in which it is located. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which the power supply component is located.

[0107] In an embodiment of the present application, the audio component may be configured to output and / or input audio signals. For example, the audio component includes a microphone (Microphone, MIC), and when the device where the audio component is located is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal may be further stored in a memory or sent via a communication component. In some embodiments, the audio component also includes a speaker for outputting an audio signal. For example, for a device with a language interaction function, voice interaction with a user may be achieved through an audio component.

[0108] It should be noted that the descriptions such as “first” and “second” in this article are used to distinguish different messages, devices, modules, etc., and do not represent the order of precedence, nor do they limit “first” and “second” to different types.

[0109] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, compact disc read-only memory (CD-ROM), optical storage, etc.) containing computer-usable program codes.

[0110] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0111] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0112] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0113] In a typical configuration, a computing device includes one or more processors (CPU, etc.), input / output interfaces, network interfaces, and memory.

[0114] Memory may include non-permanent storage in a computer-readable medium, in the form of random-access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0115] Computer storage media is readable storage media, also known as readable media. Readable storage media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, magnetic cassettes, disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0116] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of further restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the above elements.

[0117] The above contents are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A cloud network system, characterized in that: include: Network independent first cloud network and second cloud network; The second cloud network is deployed with a proxy node and at least one service node providing at least one cloud service; wherein the network segment to which the service node belongs is the same as part of the network segments maintained by the first cloud network; and the network segment to which the proxy node belongs is different from each network segment maintained by the first cloud network; The cloud network system further comprises: a client node corresponding to the at least one cloud service; the client node is pre-configured with a domain name of the proxy node; The client node is used to respond to the access demand information of the target service node in the at least one service node, obtain the Internet Protocol IP address of the proxy node based on the domain name of the proxy node; and send a target access request to the proxy node according to the IP address of the proxy node; The proxy node is pre-configured with forwarding rule information, and the forwarding rule information includes: a correspondence between at least one port of the proxy node and the at least one service node; the at least one port is bound to the at least one cloud service; The proxy node is used to forward the target access request to the target service node based on the correspondence between the at least one port and the at least one service node when the target access request is received on the target port. The target service node refers to the service node corresponding to the target port.

2. The system according to claim 1, characterized in that The proxy node publicly discloses the binding relationship between the at least one port and the at least one cloud service; The client node is specifically used to: determine the cloud service to be accessed according to the access requirement information; Acquire the target port bound to the cloud service to be accessed based on the binding relationship; Generate a target access request whose destination IP address is the IP address of the proxy node and whose destination port is the target port, and send the target access request to the proxy node.

3. The system according to claim 2, characterized in that The proxy node is also used for: If forwarding rule configuration information is obtained in the process of forwarding the target access request, then without interrupting the forwarding process of the target access request, the port to be configured is started according to the identifier of the port to be configured and the service node corresponding to the port to be configured contained in the forwarding rule configuration information, and a correspondence between the port to be configured and the corresponding service node is generated; The ports to be configured are other ports on the proxy node except the at least one port.

4. The system according to any one of claims 1 to 3, characterized in that: The client node is deployed in the first cloud network.

5. The system according to any one of claims 1 to 3, characterized in that: There are multiple proxy nodes, and the multiple proxy nodes have the same IP address; the second cloud network is also deployed with a load balancing node; The load balancing node is used to balance the access requests among the multiple proxy nodes.

6. A communication method, characterized in that: Applicable to a client node corresponding to at least one cloud service; the first cloud network and the second cloud network are independent of each other, and the second cloud network is deployed with a proxy node and at least one service node that provides the at least one cloud service; wherein the network segment to which the service node belongs is the same as part of the network segment maintained by the first cloud network; the network segment to which the proxy node belongs is different from each network segment maintained by the first cloud network; The method comprises: Obtaining a pre-configured domain name of the proxy node; In response to the access demand information of the target service node in the at least one service node, acquiring the Internet Protocol IP address of the proxy node based on the domain name of the proxy node; sending a target access request to the proxy node according to the IP address of the proxy node, so that when the proxy node receives the target access request on its target port, the proxy node forwards the target access request to the target service node based on a pre-configured correspondence between at least one port of the proxy node and the at least one service node, The at least one port is bound to the at least one cloud service, and the target service node refers to the service node corresponding to the target port.

7. The method according to claim 6, characterized in that The proxy node publicly discloses the binding relationship between the at least one port and the at least one cloud service; The sending a target access request to the proxy node according to the IP address of the proxy node includes: Determine the cloud service to be accessed based on the access requirement information; Acquire the target port bound to the cloud service to be accessed based on the binding relationship; Generate a target access request whose destination IP address is the IP address of the proxy node and whose destination port is the target port; The target access request is sent to the proxy node.

8. A communication method, characterized in that: A proxy node adapted to be deployed in a second cloud network, the second cloud network being independent of the first cloud network, the second cloud network also being deployed with at least one service node providing at least one cloud service; wherein the network segment to which the service node belongs is the same as part of the network segments maintained by the first cloud network; the network segment to which the proxy node belongs is different from each network segment maintained by the first cloud network; the proxy node is pre-configured with forwarding rule information, the forwarding rule information comprising: a correspondence between at least one port of the proxy node and the at least one service node; the at least one port being bound to the at least one cloud service; The method comprises: Receiving a target access request sent by a client node; the client node is a client node corresponding to the at least one cloud service and is configured with a domain name of the proxy node; the target access request is sent by the IP address of the proxy node of the client node; the IP address of the proxy node is obtained by the client node based on the pre-configured domain name of the proxy node; When the target access request is received on the target port, the target access request is forwarded to a target service node based on the correspondence between the at least one port and the at least one service node, where the target service node refers to the service node corresponding to the target port.

9. The method according to claim 8, characterized in that The proxy node publicly discloses the binding relationship between the at least one port and the at least one cloud service; The destination IP address of the target access request is the IP address of the proxy node, and the destination port is the target port bound to the cloud service to be accessed by the client node.

10. The method according to claim 8, characterized in that The forwarding the target access request to the target service node based on the correspondence between the at least one port and the at least one service node includes: Establishing a network channel between the target port and the target service node according to the corresponding relationship between the at least one port and the at least one service node; The target access request is forwarded to the target service node through the network channel.

11. The method according to claim 9, characterized in that Also includes: If forwarding rule configuration information is obtained in the process of forwarding the target access request, then without interrupting the forwarding process of the target access request, the port to be configured is started according to the identifier of the port to be configured and the service node corresponding to the port to be configured contained in the forwarding rule configuration information, and a correspondence between the port to be configured and the corresponding service node is generated; The ports to be configured are other ports on the proxy node except the at least one port.

12. An electronic device, characterized in that: include: Memory, processor and communication components; wherein the memory is used to store computer programs; The processor is coupled to the memory and the communication component, and is configured to execute the computer program for the steps in the method according to any one of claims 6 to 11.

13. A computer-readable storage medium storing computer instructions, characterized in that: When the computer instructions are executed by one or more processors, the one or more processors are caused to execute the steps in the method according to any one of claims 6 to 11.

14. A computer program product, characterized in that The method comprises a computer program which, when executed by one or more processors, causes the one or more processors to execute the steps of the method according to any one of claims 6 to 11.