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

Abstract

Embodiments of the present disclosure provide a cloud network system, a communication method, a device, a storage medium, and a program product. A proxy node is deployed in a second cloud network, and the domain name of the proxy node is configured on a client node corresponding to a cloud service. When a client node accesses a cloud service in the second cloud network, the client node acquires the IP address of a proxy node on the basis of the domain name of the proxy node, and, on the basis of the IP address of the proxy node, forwards to the proxy node a target access request for accessing the cloud service in the second cloud network. The proxy node, on the basis of preconfigured forwarding rule information used for describing a forwarding relationship between each access request received by the proxy node and a service node in the second cloud network, forwards the target access request to a target service node providing a target cloud service, rather than forwarding the target access request to a node in a first cloud network that belongs to the same network segment as the target service node, thereby preventing network segment conflicts.

Description

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

[0001] The present disclosure claims priority to Chinese Patent Application No. 202410948677.1, filed on July 15, 2024 with the Chinese Patent Office, entitled “Cloud network system, communication method, device, storage medium and program product”, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0002] The present disclosure relates to the technical field of network, and in particular, to a cloud network system, a communication method, a device, a storage medium and a program product. BACKGROUND

[0003] With the application and popularization of cloud computing, more and more users begin to deploy application systems on the cloud. In order to improve the stability of the application system, the multi-cloud environment (Multi-Cloud Environment) has become the preferred solution for users to deploy application systems, that is, according to the characteristics of the application system, the requirements for network bandwidth quality and the sensitivity of data and other factors, relying on the cloud services provided by multiple different cloud computing vendors to deploy the application system, and taking advantage of the advantages of the multi-cloud environment to protect users from risks such as system interruption.

[0004] However, different cloud vendors may have overlaps in network segment division, that is, cloud services of different cloud vendors may use the same network segment, which leads to the problem of network segment conflict in the multi-cloud environment, that is, when a user requests to access a cloud service of a cloud vendor according to an Internet Protocol (IP) address, the access request may be incorrectly forwarded to a cloud service of another cloud vendor that uses the same network segment, affecting user use. SUMMARY

[0005] Aspects of the present disclosure provide a cloud network system, a communication method, a device, a storage medium and a program product to avoid the problem of network segment conflict between multiple clouds.

[0006] The present disclosure provides a cloud network system, comprising: a first cloud network and a second cloud network that are independent of each other; a proxy node and at least one service node providing 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 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 cloud network system further comprises: a client node corresponding to the at least one cloud service, and the domain name of the proxy node is pre-configured on the client node.

[0007] The client node is configured to, in response to access demand information for a target service node in the at least one service node, acquire an Internet Protocol (IP) address of the proxy node based on a 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.

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

[0009] The disclosure also provides a communication method, which is suitable for a client node corresponding to at least one cloud service; a first cloud network and a second cloud network are independent of each other, the second cloud network is deployed with a proxy node and at least one service node providing the at least one cloud service; a network segment to which the service node belongs is the same as part of network segments maintained by the first cloud network; a network segment to which the proxy node belongs is different from each network segment maintained by the first cloud network; and the method comprises the following steps:

[0010] acquiring a pre-configured domain name of the proxy node;

[0011] in response to access demand information for a target service node in the at least one service node, acquiring an Internet Protocol (IP) address of the proxy node based on a domain name of the proxy node;

[0012] sending 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 pre-configured forwarding rule information; and the forwarding rule information is used to describe a forwarding relationship between each access request received by the proxy node and the at least one service node.

[0013] The disclosure also provides a communication method, which is suitable for a proxy node deployed in a second cloud network; the second cloud network and a first cloud network are independent of each other, and the second cloud network is also deployed with at least one service node providing at least one cloud service; a network segment to which the service node belongs is the same as part of network segments maintained by the first cloud network; and a network segment to which the proxy node belongs is different from each network segment maintained by the first cloud network; and the method comprises the following steps:

[0014] receive 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 an IP address of the 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;

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

[0016] The embodiments of the present disclosure further provide an electronic device, comprising a memory, a processor and a communication component; the memory is configured to store a computer program; the processor is coupled to the memory and the communication component, and is configured to execute the computer program to perform the steps in the above communication methods.

[0017] The embodiments of the present disclosure further provide a computer readable storage medium storing computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps in the above communication methods.

[0018] The embodiments of the present disclosure further provide a computer program product, comprising a computer program, which, when executed by one or more processors, cause the one or more processors to perform the steps in the above communication methods.

[0019] In the embodiments of the present disclosure, by setting a proxy node in the second cloud network and pre-configuring a domain name of the proxy node on a client node corresponding to a cloud service, when the client node needs to access a cloud service in the second cloud network, the client node can obtain an IP address of the proxy node based on the domain name of the proxy node, and forward a 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 a target service node providing a target cloud service according to pre-configured forwarding rule information used to describe a forwarding relationship between each access request received by the proxy node and service nodes in the second cloud network, instead of forwarding to a node in the first cloud network belonging to the same network segment as the target service node, thereby avoiding network segment conflicts. BRIEF DESCRIPTION OF DRAWINGS

[0020] The accompanying drawings, which are included to provide a further understanding of the present disclosure and constitute a part of the present disclosure, illustrate the exemplary embodiments of the present disclosure and serve to explain the present disclosure together with the descriptions. In the drawings:

[0021] FIG. 1 is a structural diagram of a cloud network system provided by a conventional scheme;

[0022] FIGS. 2a and 2b are structural diagrams of a cloud network system provided by an embodiment of the present disclosure;

[0023] FIG. 3 is a structural diagram of another cloud network system provided by an embodiment of the present disclosure;

[0024] FIG. 4 is a schematic diagram of a forwarding rule information configuration process provided by an embodiment of the present disclosure;

[0025] FIG. 5 is a schematic diagram of a configuration effect of forwarding rule information provided by an embodiment of the present disclosure;

[0026] FIGS. 6 and 7 are flow diagrams of a communication method provided by an embodiment of the present disclosure;

[0027] FIG. 8 is a structural diagram of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0028] To make the objectives, technical solutions, and advantages of the present disclosure clearer, the technical solutions of the present disclosure will be described below in conjunction with specific embodiments of the present disclosure and corresponding drawings. Obviously, the described embodiments are only some of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present disclosure.

[0029] 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 for analysis, stored data, displayed data, etc.) involved in the present disclosure are all information and data authorized by the user or authorized by all parties, and the collection, use, and processing of related data need to comply with relevant laws, regulations, and standards of relevant countries and regions, and provide corresponding operation portals for users to choose authorization or refusal.

[0030] Multi-cloud deployment refers to that a user deploys an application or a service system in cloud services provided by different cloud vendors. For example, the user rents servers provided by a cloud vendor A, and uses cloud security services provided by a cloud vendor B in the servers to guarantee the data security of the servers. In actual use, different cloud vendors may have overlaps in network segment division, that is, cloud services of different cloud vendors may use the same network segment. For example, cloud vendors are used to reserving a 100 network segment, which is allocated to control or service nodes of the cloud vendor, and will not be allocated to users, which may cause network segment conflicts.

[0031] As shown in FIG. 1, 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 being independent of each other means that the first cloud network and the second cloud network have independent network environments, are isolated from each other, have independent IP address segments, and have independent management permissions. Generally, the first cloud network and the second cloud network belong to different cloud vendors, but are not limited thereto. Alternatively, the first cloud network and the second cloud network can also be different cloud networks belonging to the same cloud vendor. The cloud boundary in FIG. 1 refers to the isolation boundary between the first cloud network and the second cloud network. At least one service node is included in the first cloud network and the second cloud network, and the service nodes can provide cloud services, which can be, but are not limited to, cloud security services, cloud communication services, distributed lock services, data storage services, or cloud computing services, and the like. In addition, it should be noted that the cloud services provided by the service nodes in different cloud networks can be the same or different. In addition to cloud services, the service nodes in the cloud network can also provide various computing, storage, network, and the like resources for users to deploy applications. The user's application can be a cloud service provided by the cloud network, or other applications relying on the cloud service.

[0032] 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, and in FIG. 1, only the network segment to which both belong is taken as an example for illustration, which is the 100 network segment, but does not constitute a limitation. In the application scenario shown in FIG. 1, 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 in the first cloud network, and uses the cloud service provided by the service node 201 in the second cloud network to provide related services for the application deployed in the first cloud network. For the sake of description and distinction, the node in which the user is deployed in the first cloud network and needs to use the cloud service provided by the service node 201 in the second cloud network is referred to as a client node 10. Of course, the user can also deploy an application in the second cloud network and use the cloud service provided by the first cloud network, and the user can also deploy an application in the same cloud network and use the cloud service provided by the same cloud network. In this embodiment, the scenario in which the user deploys an application in a certain cloud network and uses the cloud service provided by another cloud network is focused on, and the scenario in which the user deploys an application in the first cloud network and uses the cloud service provided by the service node 201 in the second cloud network as an example is described.

[0033] The cloud service in the second cloud network can disclose a link address of the cloud service for a user to access. When the user uses the cloud service in the second cloud network, the user can access the link address of the cloud service. Accordingly, the client node 10 can request the domain name resolution node 30 to resolve the domain name of the cloud service in response to access demand information for the cloud service (corresponding to step 1 in FIG. 1). The domain name resolution node 30 can resolve the domain name of the cloud service to obtain an IP address of the cloud service, that is, an 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 step 2 in FIG. 1).

[0034] 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 an 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 step 3 in FIG. 1), resulting in an access request forwarding error, the inability to use the cloud service in the second cloud network, and the impact on user use.

[0035] To solve the network segment conflict, in some embodiments of the present disclosure, 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 a 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 a target service node providing the target cloud service according to pre-configured forwarding rule information describing the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network, instead of forwarding it to a node in the first cloud network belonging to the same network segment as the target service node, thereby avoiding the network segment conflict.

[0036] The technical solutions provided by the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

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

[0038] FIGS. 2a, 2b and 3 are structural schematic diagrams of a cloud network system provided by embodiments of the present disclosure. In combination with FIGS. 2a, 2b and 3, the cloud network system includes a first cloud network and a second cloud network which are network independent. The explanation of network independence can be referred to the foregoing content, which is not repeated here.

[0039] In this embodiment, at least one service node 201 is deployed in the second cloud network. The service node 201 can provide cloud services. In this disclosure, the cloud services provided by the service node 201 can be any functional cloud services, such as one or more of 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. Multiple means 2 or more. In the embodiments of this disclosure, service nodes 201 providing the same cloud service can be implemented as one or more physical machines, and multiple means 2 or more. Of course, different cloud services can also be deployed on the same physical machine.

[0040] In the embodiments of this disclosure, nodes providing 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 function module that provides cloud services. The device providing cloud services can be a single server device, or a cloud-based server array. In addition, the device providing cloud services can also refer to other computing devices with corresponding service capabilities, such as terminal devices (running service programs) such as computers, etc. In this embodiment, the service node 201 can be deployed in the cloud, such as in the central cloud. The service node 201 corresponds to one cloud service. Accordingly, the service node providing at least one cloud service is at least one. Generally, the number of service nodes is the same as the number of cloud services.

[0041] In the embodiments of this disclosure, users use 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 embodiments of this disclosure, only an example is exemplarily illustrated by taking an example of an application of a user in the first cloud network needing to use cloud services in the second cloud network, but this does not constitute a limitation.

[0042] In addition to the system embodiments provided in the above embodiments, the present disclosure also provides a communication method, which is exemplarily described below from the perspective of a client node and a proxy node respectively. To use a cloud service in a second cloud network, a user needs a client node 10 corresponding to the cloud service. The client node 10 refers to a node deploying a client corresponding to the cloud service, and can be a device, an apparatus, a VM, a container, or a software function module, etc. deployed with the client corresponding to the cloud service. As shown in FIG. 2a, the client node 10 can be deployed in the first cloud network. Accordingly, to use a cloud service in a second cloud network, a user needs to deploy a client node 10 corresponding to the cloud service in the first cloud network. Of course, as shown in FIG. 2b, the client node 10 can also be deployed in other cloud networks, such as a third cloud network, outside the first cloud network and the second cloud network. The third cloud network maintains a network segment different from each network segment maintained by the second cloud network. The third cloud network is also independent of the first cloud network and the second cloud network, for example, the third cloud network belongs to a different cloud vendor from the first cloud network and the second cloud network.

[0043] In the present embodiment, the network segment to which the service node 201 belongs can be partially the same as 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 present embodiment mainly describes the scenario in which the network segment to which the service node 201 belongs is partially the same as the network segment maintained by the first cloud network. In FIGS. 2a, 2b, and 3, only the network segment to which the service node 201 belongs is taken as an example of the 100 network segment, but this does not constitute a limitation.

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

[0045] In the present embodiment, 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 in the same physical machine or in different physical machines.

[0046] In the embodiments of the present disclosure, 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 each network segment maintained by the first cloud network. Further, the domain name of the proxy node 40 can be pre-configured at the client node 10, and when the client node 10 needs to access the cloud service provided by the service node 201, the client node 10 can obtain the IP address of the proxy node 40 based on the domain name of the proxy node 40 in response to the access demand information of the service node 201. In the embodiments of the present disclosure, in order to facilitate description and differentiation, the cloud service that the client node 10 needs to access is defined as a target cloud service, and the service node 201 that provides the target cloud service is defined as a target service node 201.

[0047] The client node 10 obtains the access demand information of the service node 201, and the access demand 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 demand for the service node 201, the client node 10 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 demand information refers to information reflecting the demand of the client node 10 to access the target cloud service, and can include an access purpose or intention, and identification information of the service node 201 or identification information of the cloud service provided by the service node 201. The client node 10 can 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 included 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.

[0048] Correspondingly, as shown in FIG. 2a and FIG. 2b, the client node 10 can obtain the IP address of the proxy node 40 based on the domain name of the proxy node 40 in response to the access demand information of the target service node 201 (corresponding to step 1 in FIG. 2a and FIG. 2b). Specifically, as shown in step 1 in FIG. 3, the client node 10 can 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 can send a DNS request to the DNS resolution node 30. The DNS request can 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 can perform domain name resolution on the domain name of the proxy node in response to the DNS request 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 step 2 in FIG. 3). The IP address corresponding to the domain name of the proxy node is the IP address of the proxy node 40. In FIG. 3, only the client node 10 deployed in the first cloud network is taken as an example for illustration, of course, the client node 10 can also be deployed in other cloud networks such as the third cloud network outside the first cloud network and the second cloud network.

[0049] Correspondingly, the client node 10 can receive the IP address of the proxy node, and send a target access request to the proxy node 40 according to the IP address of the proxy node 40 (corresponding to steps 2 and 3 in FIG. 2a and FIG. 2b, and step 3 in FIG. 3). Specifically, the client node 10 can generate a target access request with a request body of the access demand information and a destination IP address of the IP address of the proxy node 40. Based on the destination IP address, the proxy node 40 can send the target access request to the proxy node 40, thereby realizing the transfer of the target access request for accessing the target service node from the first cloud network, instead of forwarding to the node in the first cloud network belonging to the same network segment as the target service node, thereby avoiding network segment conflict.

[0050] Since the client node 10 needs to access the target service node providing 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 forwarding relationship between each access request received by the proxy node 40 and the service node in the second cloud network can be pre-configured in the proxy node 40. Correspondingly, 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 node in the second cloud network. Correspondingly, the proxy node 40 can forward the target access request to the target service node 201 according to the forwarding rule information (corresponding to step 3 in FIG. 3 and step 4 in FIG. 3).

[0051] Specifically, the proxy node 40 can determine the target service node to which the target access request is to be forwarded according to the forwarding relationship between each access request received by the proxy node 40 and the service node in the second cloud network described in the forwarding rule information, and forward the target access request to the target service node 201.

[0052] In the embodiments of the present disclosure, 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 specific implementation forms. In some embodiments, the ports of the proxy node can be bound to cloud services in advance. The ports of the proxy node are virtual ports, which refer to the ports inside the proxy node. Optionally, each port of the proxy node can be bound to one cloud service. Thus, for the scenario that there is at least one cloud service in the second cloud network, at least one port of the proxy node can be bound to the at least one cloud service. For the scenario that there are multiple cloud services in the second cloud network, multiple ports of the proxy node can be bound to the multiple cloud services respectively, where one port is bound to one cloud service. Since the cloud service corresponds to the service node, after the ports of the proxy node are bound to the cloud services, the service nodes corresponding to each port are determined, that is, the service node corresponding to each port is the service node providing 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 can include the correspondence between at least one port of the proxy node and at least one service node.

[0053] In the embodiments of the present disclosure, the forwarding rule information in the proxy node 40 is preconfigured. For the proxy node 40, the forwarding rule configuration information can be acquired. The forwarding rule configuration information can include the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port. The identifier of the service node corresponding to the to-be-configured port included in the forwarding rule configuration information is the identifier of the service node providing the cloud service in the second cloud network. The identifier of the service node can be information for uniquely identifying one service node, which can be an IP address, a number, or an identity (ID) of the service node.

[0054] In the embodiments of the present disclosure, the specific implementation form of the proxy node 40 acquiring the forwarding rule configuration information is not limited. In some embodiments, as shown in FIG. 4, the proxy node 40 corresponds to a proxy management node 50, and the proxy management node 50 is deployed in the second cloud network. The proxy management node 50 can provide a forwarding rule configuration page (not shown in FIG. 4), and a user or a technician can configure the corresponding service node for the port of the proxy node 40 through the forwarding rule configuration page. Further, the proxy management node 50 can acquire the forwarding rule configuration information configured based on the forwarding rule configuration page, that is, acquire the identifier of the to-be-configured port and the service node corresponding to the to-be-configured port. Based on this, the proxy node 40 can acquire the forwarding rule configuration information from the proxy management node 50.

[0055] In the above manner, the forwarding rule configuration information includes the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port. The to-be-configured port includes the port of the proxy node 40, such as the port A and the port B shown in FIG. 4. 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 to-be-configured port according to the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port included in the forwarding rule configuration information, and generate the correspondence between the port of the proxy node and the service node in the second cloud network.

[0056] In some embodiments, the proxy management node 50 can push the forwarding rule configuration information to the proxy node 40, and the proxy node 40 receives the forwarding rule configuration information pushed by the proxy management node 50. Alternatively, the proxy node 40 can pull the forwarding rule configuration information from the proxy management node 50. Optionally, the proxy node 40 can periodically pull the forwarding rule configuration information from the proxy management node 50 according to a set configuration period, etc.

[0057] The proxy node 40 generates the correspondence between the multiple ports of the proxy node and the multiple service nodes in the second cloud network based on the obtained forwarding rule configuration information. The forwarding rule configuration information includes the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port. The to-be-configured port includes the port of the proxy node 40, such as the port A and the port B shown in FIG. 4. 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 to-be-configured port according to the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port included in the forwarding rule configuration information, and generate the correspondence between the port of the proxy node and the service node in the second cloud network.

[0058] In the above manner, the forwarding rule configuration information includes the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port. The to-be-configured port includes the port of the proxy node 40, such as the port A and the port B shown in FIG. 4. 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 to-be-configured port according to the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port included in the forwarding rule configuration information, and generate the correspondence between the port of the proxy node and the service node in the second cloud network.

[0059] In the above manner, the forwarding rule configuration information includes the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port. The to-be-configured port includes the port of the proxy node 40, such as the port A and the port B shown in FIG. 4. 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 to-be-configured port according to the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port included in the forwarding rule configuration information, and generate the correspondence between the port of the proxy node and the service node in the second cloud network.

[0060] In the embodiments of the present disclosure, the proxy node 40 can obtain new forwarding rule configuration information when the configured port is open, and start a new port according to the new forwarding rule configuration information, and establish a corresponding relationship between the new port and a new service node, so that the hot start of the new port and the new forwarding rule information can be realized without interrupting the forwarding process of the proxy node 40, which helps to improve the service performance of the proxy node.

[0061] In some embodiments, the proxy node 40 can obtain the forwarding rule configuration information in the process of forwarding the foregoing target access request. The forwarding rule configuration information contains a to-be-configured port which is a port on the proxy node other than the foregoing at least one port. The proxy node 40 can start the to-be-configured port and start the corresponding relationship between the to-be-configured port and the respective corresponding service node according to the to-be-configured port contained in the currently obtained forwarding rule configuration information and the identifier of the corresponding service node of the to-be-configured port without interrupting the forwarding process of the target access request. The corresponding relationship is the new forwarding rule information. In this way, the hot start of the new forwarding rule information can be realized without interrupting the forwarding process of the proxy node 40, which helps to improve the service performance of the proxy node.

[0062] In the embodiments, the binding relationship between the port of the proxy node and the cloud service is disclosed externally, that is, the proxy node 40 discloses the binding relationship between the port and the cloud service externally. For the client node 10, the to-be-accessed cloud service, that is, the target cloud service, can be determined according to the access demand information, and the target port bound to the to-be-accessed cloud service can be obtained based on the binding relationship between the port of the proxy node and the cloud service. Further, the 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, so that the target access request for accessing the target service node is forwarded out of the first cloud network, rather than being forwarded to the node in the first cloud network belonging to the same network segment as the target service node, thereby avoiding network segment conflict.

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

[0064] 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, i.e., determine the target service node, and establish a network channel between the target port and the target service node; then, the target access request can be forwarded to the target service node through the network channel.

[0065] In the embodiment, by setting a proxy node in the second cloud network and pre-configuring the domain name of the proxy node on the client node corresponding to the target cloud service, 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 describing the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network, instead of forwarding to the node in the first cloud network belonging to the same network segment as the target service node, thereby avoiding network segment conflict.

[0066] To improve the availability of the proxy node, multiple proxy nodes 40 can be set, i.e., the cloud network system contains multiple proxy nodes 40, and each proxy node 40 has the same working principle and pre-configured forwarding rule information. The multiple proxy nodes 40 have the same IP address. The multiple proxy nodes 40 can form a Server Load Balancing (SLB) cluster. Correspondingly, a Server 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 requests among the multiple proxy nodes 40.

[0067] Optionally, the SLB node can balance the access requests among the plurality of proxy nodes 40 according to a pre-set load balancing policy. For example, the SLB node can balance the access requests among the plurality of proxy nodes 40 according to a pre-set round-robin load balancing policy. That is, the SLB node can sequentially distribute each access request to the plurality of proxy nodes 40 in time order. Alternatively, the SLB node can balance the access requests among the plurality of proxy nodes 40 according to weights of the proxy nodes. The weights are used to specify the probability of polling, and the weights of the proxy nodes are proportional to the access rates of the proxy nodes, and are used in the case where the performance of the proxy nodes is uneven. The higher the weight of a proxy node, the greater the probability of being accessed. Alternatively, the SLB node can balance the access requests among the plurality of proxy nodes 40 according to an IP hash (IP_hash) policy. The IP_hash policy refers to performing hash calculation on the source IP address of each access request, and distributing each access request to a proxy node according to the hash result of the source IP address, so that the request of each access user is fixedly accessed to a proxy node. Alternatively, the SLB node can balance the access requests among the plurality of proxy nodes 40 according to a Fair policy. The Fair policy refers to distributing the access requests according to the response times of the plurality of proxy nodes, and preferentially distributing the access requests to the proxy nodes with short response times.

[0068] FIG. 6 is a flow diagram of a communication method provided by an embodiment of the present disclosure. The communication method is mainly applicable to a client node in a first cloud network. As shown in FIG. 6, the communication method mainly includes:

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

[0070] 602. In response to access demand information for 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.

[0071] 603. According to the IP address of the proxy node, send a target access request to the proxy node, so that the proxy node forwards the target access request to the target service node according to 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.

[0072] FIG. 7 is a flow diagram of another communication method provided by an embodiment of the present disclosure. The communication method is mainly applicable to a proxy node in a second cloud network. As shown in FIG. 7, the communication method mainly includes:

[0073] 701、receive a target access request sent by a 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 an IP address of the proxy node of the client node; and the IP address of the proxy node is obtained by the client node based on the preconfigured domain name of the proxy node.

[0074] 702、forward the target access request to a target service node in the at least one service node according to preconfigured forwarding rule information; the forwarding rule information is used to describe a forwarding relationship between each access request received by the proxy node and the at least one service node.

[0075] In the 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 providing 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 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 client node can be deployed in the first cloud network, or can be deployed in other cloud networks except the first cloud network and the second cloud network. The communication method shown in FIG. 6 is mainly applicable to the client node. The communication method shown in FIG. 7 is mainly applicable to the proxy node in the second cloud network. For the implementation forms of the service node, the proxy node, the client node and the cloud service, refer to the related contents of the foregoing system embodiments, which will not be described here again.

[0076] In the embodiments of the present disclosure, in order to solve the network segment conflict problem between the first cloud network and the second cloud network, the proxy node is deployed in the second cloud network. In the embodiments of the present disclosure, 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 each network segment maintained by the first cloud network. Further, the domain name of the proxy node can be preconfigured in 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 of the service node, the IP address of the proxy node is obtained based on the domain name of the proxy node. In the embodiments of the present disclosure, in order to facilitate description and distinction, the cloud service to be accessed by the client node is defined as a target cloud service; and the service node providing the target cloud service is defined as a target service node.

[0077] Accordingly, the IP address of the proxy node can be obtained based on the domain name of the proxy node in response to the access demand information of the target service 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, the target access request can be sent to the proxy node according to the IP address of the proxy node. Specifically, the target access request can be generated with the request body being the access demand 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, achieving the sending of the target access request for accessing the target service node out of the first cloud network, rather than forwarding to the node in the first cloud network belonging to the same network segment as the target service node, thereby avoiding network segment conflict.

[0078] Since the client node needs to access the target service node providing 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 forwarding relationship between each access request received by the proxy node and the service node in the second cloud network can be pre-configured in the proxy node. 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 can be received; and in step 702, the target access request can be forwarded to the target service node according to the forwarding rule information.

[0079] Specifically, the target service node to which the target access request is to be forwarded can be determined according to 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 can be forwarded to the target service node.

[0080] In the embodiments of the present disclosure, the forwarding relationship between the access request received by the proxy node and the service node in the second cloud network is not limited in specific implementation forms. In some embodiments, the port of the proxy node can be bound with a 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 with one cloud service. Thus, for the scenario that there is at least one cloud service in the second cloud network, at least one port of the proxy node can be bound with the at least one cloud service. For the scenario that there are multiple cloud services in the second cloud network, multiple ports of the proxy node can be bound with the multiple cloud services respectively, where one port is bound with one cloud service. Since the cloud service corresponds to the service node, after the port of the proxy node is bound with the cloud service, the service node corresponding to each port is determined, that is, the service node corresponding to each port is the service node providing the cloud service bound with the port. Accordingly, the forwarding relationship between the access request received by the proxy node and the service node in the second cloud network can include the correspondence between at least one port of the proxy node and at least one service node.

[0081] In the embodiments of the present disclosure, the forwarding rule information in the proxy node is preconfigured. For the proxy node, the forwarding rule configuration information can be acquired. The forwarding rule configuration information can include the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port. The identifier of the service node corresponding to the to-be-configured port included in the forwarding rule configuration information is the identifier of the service node providing the cloud service in the second cloud network. The identifier of the service node can be information for uniquely identifying one service node, which can be an IP address, a number or an identity (ID) of the service node.

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

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

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

[0085] The proxy node starts the to-be-configured port based on the obtained forwarding rule configuration information. The forwarding rule configuration information includes the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port. 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 to-be-configured port and generate the correspondence between the port of the proxy node and the service node in the second cloud network according to the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port included in the forwarding rule configuration information.

[0086] The to-be-configured port included in the forwarding rule configuration information can be one or more, and the more means two or more. For the embodiment in which the to-be-configured port is more than one, the 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, respectively.

[0087] The above method generates the correspondence between the multiple ports of the proxy node and the multiple service nodes in the second cloud network, solves the proxy multi-tenancy problem, 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 network segment conflict problem. The client nodes can access any cloud service in the second cloud network through the proxy node in the same or similar way, which can be seen from the related content of the foregoing and subsequent embodiments.

[0088] In the embodiments of the present disclosure, the proxy node can obtain new forwarding rule configuration information when the configured port is started, start a new port according to the new forwarding rule configuration information, and establish a correspondence between the new port and a new service node. In this way, the hot start of the new port and the new forwarding rule information can be realized without interrupting the forwarding process of the proxy node, which helps to improve the service performance of the proxy node.

[0089] In some embodiments, the proxy node can obtain the forwarding rule configuration information in the process of forwarding the foregoing target access request. The forwarding rule configuration information contains a to-be-configured port which is a port of the proxy node other than the foregoing at least one port. The proxy node can start the to-be-configured port and establish a correspondence between the to-be-configured port and a service node corresponding to the to-be-configured port according to the to-be-configured port contained in the currently obtained forwarding rule configuration information and the identifier of the service node corresponding to the to-be-configured port without interrupting the forwarding process of the target access request, and the correspondence is new forwarding rule information. In this way, the hot start of the new forwarding rule information can be realized without interrupting the forwarding process of the proxy node, which helps to improve the service performance of the proxy node.

[0090] In the embodiment, the binding relationship between the port of the proxy node and the cloud service is publicly disclosed, that is, the proxy node publicly discloses the binding relationship between the port and the cloud service. For the client node, the to-be-accessed cloud service, that is, the target cloud service, can be determined according to the access demand information, and the target port bound to the to-be-accessed cloud service can be obtained based on the binding relationship between the port of the proxy node and the cloud service. Further, the 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, so that the target access request for accessing the target service node is forwarded out of the first cloud network instead of being forwarded to a node in the first cloud network belonging to the same network segment as the target service node, thereby avoiding network segment conflict.

[0091] 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 correspondence between the port and the service node in the second cloud network, and the service node corresponding to the target port is the target service node.

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

[0093] In the embodiment, by setting the proxy node in the second cloud network and pre-configuring the domain name of the proxy node on the client node corresponding to the target cloud service, 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 describing the forwarding relationship between each access request received by the proxy node and the service node in the second cloud network, instead of forwarding to the node in the first cloud network belonging to the same network segment as the target service node, thereby avoiding network segment conflict.

[0094] 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 and the pre-configured forwarding rule information of each proxy node are the same. The multiple proxy nodes have the same IP address. The multiple proxy nodes can form a load balancing (SLB) cluster. Correspondingly, a load balancing (SLB) node can also be deployed in the second cloud network. The SLB node can balance the access requests among the multiple proxy nodes. For the specific implementation of balancing the access requests among the multiple proxy nodes by the SLB, reference can be made to the related content of the foregoing system embodiment, which will not be described here.

[0095] It should be noted that the execution subject of each step of the method provided in the foregoing embodiments can be the same device, or the method can also be executed by different devices as the execution subject. 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 the like.

[0096] In addition, in some of the processes described in the foregoing embodiments and the accompanying drawings, a plurality of operations appearing in a specific order are included, but it should be clear that these operations can be executed or performed in parallel without the order in which they appear in the text. The serial numbers of the operations, such as 601, 602, etc., are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. In addition, these processes can include more or fewer operations, and the operations can be executed in sequence or in parallel.

[0097] Correspondingly, the embodiments of the disclosure also provide a computer readable storage medium storing computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the communication method.

[0098] The embodiments of the present disclosure further provide a computer program product comprising a computer program which, when executed by one or more processors, causes the one or more processors to perform the steps of the communication method described above.

[0099] FIG. 8 is a structural schematic diagram of an electronic device provided by the embodiments of the present disclosure. As shown in FIG. 8, the electronic device comprises a memory 80a, a processor 80b and a communication component 80c. The memory 80a is configured to store a computer program.

[0100] The processor 80b is coupled to the memory 80a and the communication component 80c, and is configured to execute the computer program to perform the steps of the communication method provided by the embodiments described above. For the specific implementation of each step, please refer to the related description of the foregoing embodiments, which will not be repeated here.

[0101] In some optional implementations, as shown in FIG. 8, the electronic device can further comprise optional components such as a power supply component 80d, a display component 80e and an audio component 80f. Only part of the components are shown in FIG. 8, which does not mean that the electronic device must contain all the components shown in FIG. 8, nor does it mean that the electronic device can only include the components shown in FIG. 8.

[0102] In addition, the components in the dashed box in FIG. 8 are optional components, not mandatory components, which can be determined according to the product form of the electronic device. The electronic device of the embodiments can be implemented as a desktop computer, a notebook computer, a mobile phone or an Internet of Things device, etc. terminal device; it can also be a traditional server, a cloud server or a server cluster, etc. various server devices.

[0103] In the embodiments of the present disclosure, the memory is configured to store a computer program, and can be configured to store other various data to support the operation on the device where it is located. The processor can execute the computer program stored in the memory to realize the corresponding control logic. The memory can be realized by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0104] In the embodiments of the present disclosure, the processor can be any hardware processing device that can execute the logic of the above method. Optionally, the processor can be a central processing unit (CPU), a graphics processing unit (GPU), or a microcontroller unit (MCU); can also be a programmable device such as a field-programmable gate array (FPGA), a programmable array logic (PAL), a general array logic (GAL), a complex programmable logic device (CPLD), etc.; or can be an advanced reduced instruction set (Reduced Instruction Set Compute, RISC) processor (Advanced RISC Machines, ARM) or a system on chip (System on Chip, SoC), etc., but is not limited thereto.

[0105] In the embodiments of the present disclosure, the communication component is configured to facilitate communication between the device where it is located and other devices in a wired or wireless manner. The device where 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 example embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an example 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.

[0106] In embodiments of the present disclosure, the display component can include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the display component includes the touch panel, the display component can be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense a touch, a slide, and a gesture on the touch panel. The touch sensor can not only sense a boundary of a touch or a slide action, but also detect a duration and a pressure related to a touch or a slide operation.

[0107] In embodiments of the present disclosure, the power supply component is configured to provide power to various components of the device in which the power supply component is located. The power supply component can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the device in which the power supply component is located.

[0108] In embodiments of the present disclosure, the audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC) that is configured to receive an external audio signal when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in a memory or transmitted via the communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals. For example, for a device with a language interaction function, voice interaction with a user can be implemented through the audio component, etc.

[0109] It should be noted that the "first", "second", and the like descriptions herein are used to distinguish different messages, devices, modules, and the like, and do not represent the order of sequence, nor limit the "first" and "second" to be different types.

[0110] Those skilled in the art should understand that embodiments of the present disclosure can be provided as a method, a system, or a computer program product. Therefore, the present disclosure can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present disclosure can take 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 code.

[0111] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0112] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks.

[0113] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0114] In one typical configuration, the computing device includes one or more processors (CPU's and the like), input / output interfaces, network interfaces, and memory.

[0115] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) for example, for storage of information and instructions to be executed by the processor. The memory can also include non-volatile memory, such as read only memory (ROM) and / or flash memory for storage of static information and instructions that are not to be changed, perhaps, by the processor. The memory is an example of computer readable media.

[0116] The storage media of the computer is a readable storage media, also can be called readable media. The readable storage media includes permanent and non-permanent, movable and non-movable media, and can realize information storage by any method or technology. The information can be computer readable instructions, data structure, program module or other data. Examples of the storage media of the computer 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, compact disc read-only memory (CD-ROM), digital video disc (DVD) or other optical storage, magnetic cassette, disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device. According to the definition in this paper, the computer readable medium does not include transitory computer readable media, such as modulated data signals and carriers.

[0117] It should also be noted that the terms "comprising", "including", or any other variant thereof are intended to cover non-exclusive inclusions, so that the process, method, product or equipment including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or includes elements inherent to such process, method, product or equipment. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, product or equipment including the above element.

[0118] The above is only an embodiment of the present disclosure and is not intended to limit the present disclosure. The present disclosure can have various modifications and changes for those skilled in the art. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present disclosure shall be included in the scope of claims of the present disclosure.

Claims

1. A cloud network system, wherein, The application relates to a cloud network system. The cloud network system comprises a first cloud network and a second cloud network; The second cloud network is provided with an agent node and at least one service node providing at least one cloud service; the network segment of the service node is the same as part of the network segments maintained by the first cloud network; the network segment of the agent node 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 domain name of the agent node is preconfigured on the client node; The client node is used for obtaining the IP address of the agent node based on the domain name of the agent node in response to access demand information of a target service node in the at least one service node; and the client node is used for sending a target access request to the agent node according to the IP address of the agent node; The agent node is preconfigured with forwarding rule information, and the agent node is used for forwarding the target access request to the target service node according to the forwarding rule information; the forwarding rule information is used for describing the forwarding relationship between each access request received by the agent node and the at least one service node.

2. The system of claim 1, wherein, At least one port of the agent node is bound with the at least one cloud service, and the agent node publicly discloses the binding relationship between the at least one port and the at least one cloud service; the forwarding relationship comprises a corresponding relationship between the at least one port and the at least one service node; The client node is specifically used for determining a cloud service to be accessed according to access demand information; obtaining a target port bound with the cloud service to be accessed based on the binding relationship; generating a target access request with the IP address of the agent node as a destination IP address and the target port as a destination port; and sending the target access request to the agent node; The agent node is specifically used for forwarding the target access request to the target service node according to the corresponding relationship between the at least one port and the at least one service node in the case that the target access request is received on the target port; the target service node refers to a service node corresponding to the target port.

3. The system of claim 1 or 2, wherein, The agent node is further used for: If forwarding rule configuration information is obtained during the forwarding of the target access request, the agent node is used for starting a to-be-configured port and generating a corresponding relationship between the to-be-configured port and a service node corresponding to the to-be-configured port according to the to-be-configured port and the identifier of the service node corresponding to the to-be-configured port contained in the forwarding rule configuration information without interrupting the forwarding process of the target access request. The to-be-configured port is a port other than the at least one port on the agent node.

4. The system of any one of claims 1-3, wherein, The client node is deployed in the first cloud network.

5. The system of any one of claims 1-4, wherein, There are multiple agent nodes, and the multiple agent nodes have the same IP address; the second cloud network is further provided with a load balancing node; The load balancing node is used for balancing access requests among the multiple agent nodes.

6. A communication method, wherein, The method is suitable for a client node corresponding to at least one cloud service; a first cloud network and a second cloud network are independent of each other, the second cloud network is deployed with an agent node and at least one service node providing the at least one cloud service; wherein a network segment to which the service node belongs is the same as part of network segments maintained by the first cloud network; a network segment to which the agent node belongs is different from each network segment maintained by the first cloud network; The method comprises: obtaining a domain name of the agent node preconfigured; in response to access demand information of a target service node in the at least one service node, obtaining an Internet Protocol (IP) address of the agent node based on the domain name of the agent node; sending a target access request to the agent node according to the IP address of the agent node, so that the agent node forwards the target access request to the target service node according to preconfigured forwarding rule information; the forwarding rule information is used to describe a forwarding relationship between each access request received by the agent node and the at least one service node.

7. The method of claim 6, wherein, at least one port of the agent node is bound to the at least one cloud service, and the agent node publicly discloses a binding relationship between the at least one port and the at least one cloud service; the forwarding relationship comprises a corresponding relationship between the at least one port and the at least one service node; the sending of the target access request to the agent node according to the IP address of the agent node comprises: determining a cloud service to be accessed according to access demand information; obtaining a target port bound to the cloud service to be accessed based on the binding relationship; generating a target access request with a destination IP address being the IP address of the agent node and a destination port being the target port; sending the target access request to the agent node.

8. A communication method, wherein, The method is suitable for an agent node deployed in a second cloud network, the second cloud network and a first cloud network are independent of each other, and the second cloud network is further deployed with at least one service node providing at least one cloud service; wherein a network segment to which the service node belongs is the same as part of network segments maintained by the first cloud network; a network segment to which the agent node belongs is different from each network segment maintained by the first cloud network; 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 agent node; the target access request is sent by the client node and the IP address of the agent node; the IP address of the agent node is obtained by the client node based on the domain name of the agent node preconfigured; forwarding the target access request to a target service node in the at least one service node according to preconfigured forwarding rule information; the forwarding rule information is used to describe a forwarding relationship between each access request received by the agent node and the at least one service node.

9. The method of claim 8, wherein, at least one port of the agent node is bound to the at least one cloud service, and the agent node publicly discloses a binding relationship between the at least one port and the at least one cloud service; The forwarding relationship comprises a corresponding relationship between the at least one port and the at least one service node; The destination IP address of the target access request is an IP address of the proxy node, and the destination port is a target port of a cloud service bound to the client node to be accessed; The method further comprises: In a case where the target access request is received on the target port, the target access request is forwarded to the target service node based on the corresponding relationship between the at least one port and the at least one service node, the target service node being a service node corresponding to the target port.

10. The method of claim 9, wherein, The forwarding of the target access request to the target service node based on the corresponding relationship between the at least one port and the at least one service node comprises: 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; and forwarding the target access request to the target service node through the network channel.

11. The method of claim 9 or 10, wherein, Further comprising: If forwarding rule configuration information is acquired in the process of forwarding the target access request, the forwarding process of the target access request is not interrupted, and a to-be-configured port and an identifier of a service node corresponding to the to-be-configured port included in the forwarding rule configuration information are used to start the to-be-configured port and establish a corresponding relationship between the to-be-configured port and the service node corresponding thereto. The to-be-configured port is a port other than the at least one port on the proxy node.

12. An electronic device, comprising: comprise: a memory, a processor, and a communication component; wherein the memory is configured to store a computer program; the processor is coupled to the memory and the communication component, and is configured to execute the computer program to perform the steps in the method of any one of claims 6-11.

13. A computer readable storage medium having stored thereon computer instructions, wherein, The computer instructions, when executed by one or more processors, cause the one or more processors to perform the steps in the method of any one of claims 6-11.

14. A computer program product, wherein, The computer program, when executed by one or more processors, causes the one or more processors to perform the steps in the method of any one of claims 6-11.

Images