Cloud service providing method and apparatus, proxy node, and storage medium

Abstract

The application discloses a cloud service providing method and device, a proxy node and a storage medium. The method comprises the following steps: a proxy node acquires configuration information, wherein the configuration information at least contains registered domain name information associated with the proxy node; the proxy node and the associated cloud service node are deployed in different geographical areas, and the different geographical areas include two geographical areas which need to register domain names in different places; and the cloud service node communicates with the proxy node according to the configuration information, so that the cloud service node provides cloud services to a target object through the proxy node.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a cloud service provision method, apparatus, proxy node, and storage medium. Background Technology

[0002] In related technologies, the joint construction of public cloud refers to the cooperation between the joint construction provider (such as cloud computing vendors) and the joint construction customer (such as network operators) to jointly build a cloud computing infrastructure that can be operated externally, that is, to jointly build and operate a cloud computing platform.

[0003] However, the joint venture model in related technologies cannot meet the cloud deployment needs of joint venture clients. Summary of the Invention

[0004] To address the related technical issues, embodiments of this application provide a cloud service provision method, apparatus, proxy node, and storage medium.

[0005] The technical solution of this application embodiment is implemented as follows:

[0006] This application provides a cloud service provision method applied to a proxy node, including:

[0007] Obtain configuration information, which includes at least the registered domain name information associated with the agent node. The agent node and the associated cloud service node are deployed in different geographical regions, including two geographical regions where the domain name needs to be registered in different locations.

[0008] The cloud service node communicates with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node.

[0009] In the above scheme, the cloud services provided by the cloud service node to the target object through the proxy node include at least one of the following:

[0010] The cloud service associated with the first type of data center, wherein the first type of data center and the cloud service node are deployed in the same geographical area, the first type of data center includes a data center jointly constructed by at least two parties, the at least two parties being associated with the proxy node and the cloud service node, the joint construction including at least the joint management and / or operation of the data center;

[0011] A cloud service associated with a second type of data center, wherein the second type of data center and the cloud service node are deployed in the same geographical area, and the second type of data center is managed and / or operated by a single participant;

[0012] A cloud service associated with a third type of data center, wherein the third type of data center and the agent node are deployed in the same geographical area, and the third type of data center is managed and / or operated by a single participant.

[0013] In the above scheme, the proxy node includes a first proxy node, and the cloud service node includes a first cloud service node; the first cloud service node is used to manage at least one second cloud service node, each second cloud service node is used to manage at least one data center, and the data center corresponding to each second cloud service node is deployed in the same or different geographical areas as the first proxy node; the step of communicating with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node, includes:

[0014] Receive the first data stream sent by the target object;

[0015] The first data stream is forwarded to the first cloud service node, so that the first cloud service node can distribute the first data stream to the at least one second cloud service node for corresponding processing.

[0016] In the above scheme, the proxy node includes a second proxy node, and the cloud service node includes a second cloud service node; the second cloud service node is used to manage at least one data center; the step of communicating with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node, includes:

[0017] The system receives a second data stream sent by a first cloud service node; the first cloud service node manages at least one second cloud service node, and each second cloud service node manages at least one data center; the second data stream is obtained by the first cloud service node after splitting the first data stream of the target object, and the first data stream is forwarded to the first cloud service node by the first proxy node; the data center corresponding to each second cloud service node is deployed in the same or different geographical areas as the first proxy node;

[0018] The second data stream is forwarded to the corresponding second cloud service node for processing.

[0019] The method in the above scheme further includes:

[0020] The system receives the instruction information sent by the first cloud service node and forwards the instruction information to the corresponding second cloud service node; the instruction information is used for the management and / or operation and maintenance of the data center.

[0021] The method in the above scheme further includes:

[0022] The status information of the corresponding second cloud service node is obtained and sent to the first cloud service node so that the first cloud service node can determine the indication information; the status information includes at least the operating status of the servers in the data center.

[0023] The method in the above scheme further includes:

[0024] Cloud services are provided to the target object through local caching.

[0025] In the above scheme, the configuration information further includes an encryption strategy; the method further includes:

[0026] When sending data to the cloud service node, the encryption strategy is used to encrypt the data to be sent, and the encrypted data is sent to the cloud service node.

[0027] This application embodiment also provides a cloud service providing device, disposed on a proxy node, including:

[0028] The acquisition unit is used to acquire configuration information, which includes at least the registered domain name information associated with the agent node. The agent node and the associated cloud service node are deployed in different geographical regions, including two geographical regions where the domain name needs to be registered in different locations.

[0029] The service unit is used to communicate with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node.

[0030] This application also provides an agent node, including: a processor and a memory for storing computer programs that can run on the processor.

[0031] When the processor runs the computer program, it executes the steps of any of the above methods.

[0032] This application also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of any of the above methods.

[0033] The cloud service provision method, apparatus, proxy node, and storage medium provided in this application embodiment include: a proxy node acquiring configuration information, the configuration information including at least the registered domain name information associated with the proxy node; the proxy node and the associated cloud service node being deployed in different geographical regions, the different geographical regions including two geographical regions where the domain name needs to be registered in different locations; and communicating with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node. The solution provided in this application embodiment involves agent nodes and cloud service nodes deployed in different geographical regions communicating based on configuration information that includes at least the registered domain name information associated with the agent node. These different geographical regions include two regions where the domain name registration needs to be performed in different locations. Thus, when the locations of the joint venture customer (e.g., a network operator) and the joint venture provider (e.g., a cloud computing vendor) are different, for example, when the server of the joint venture customer and the cloud service node of the joint venture provider are deployed in different locations, the joint venture customer only needs to deploy agent nodes to achieve joint venture with the joint venture provider (i.e., the cloud service node can provide cloud services to the target object through the agent node), thereby meeting the flexible deployment needs of the joint venture customer. Simultaneously, the joint venture customer does not need to perform off-site domain name registration, i.e., it does not need to register the domain name at the location of the cloud service node; it only needs to register the domain name associated with the agent node locally, thereby simplifying the joint venture process with the joint venture provider. Attached Figure Description

[0034] Figure 1 A flowchart illustrating the method for providing cloud services according to embodiments of this application;

[0035] Figure 2 This is a schematic diagram illustrating the collaborative architecture used in this application.

[0036] Figure 3 This is a schematic diagram of a collaborative hardware architecture used as an application example in this application.

[0037] Figure 4 This application example illustrates a customized page for a managed cloud service.

[0038] Figure 5 This application example provides a customized page illustration for another managed cloud service.

[0039] Figure 6 This is a schematic diagram of a proxy node configuration page as an application example of this application;

[0040] Figure 7 This is a schematic diagram of another proxy node configuration page used in this application example;

[0041] Figure 8This is a schematic diagram of the structure of a cloud service providing device according to an embodiment of this application.

[0042] Figure 9 This is a schematic diagram of the proxy node structure in an embodiment of this application. Detailed Implementation

[0043] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0044] Before describing the embodiments of this application, the following terms will be explained:

[0045] Joint construction refers to the deployment, operation, management and maintenance of cloud computing involving at least two parties. These at least two parties may include a joint construction provider and a joint construction customer. The joint construction provider may include cloud computing vendors (hereinafter referred to as cloud vendors), and the joint construction customer may include network operators (hereinafter referred to as operators).

[0046] Self-operated and self-built means that there is only one participant in the deployment, operation, management and maintenance of the cloud. This participant may include cloud computing vendors or network operators.

[0047] Two joint construction models have been proposed based on relevant technologies. The following description, using examples of joint construction providers including cloud vendors and joint construction customers including telecom operators, illustrates these two models and their existing problems.

[0048] One type of joint construction model involves cloud vendors providing operators with independent domain names through domain name customization or logo customization services. The operators then utilize the cloud vendors' infrastructure, such as their cloud data centers and other resources. Another model involves cloud vendors building and operating a completely independent cloud platform for the operator. This means the cloud vendors use the operator's resources to deploy infrastructure, and the operator independently operates the cloud platform. For example, the joint construction process between operators and cloud vendors may include the following steps:

[0049] Step 1: The operator obtains its own operating domain name scc.customers.clouds.com through the domain name customization service on the cloud vendor's public cloud operation platform - Managed Cloud Control Center (SCC).

[0050] SCC can be understood as the global portal of the public cloud, responsible for the access management of all region-level data centers. In other words, SCC can manage multiple managed cloud data center platforms (SCP, Sangfor Cloud Platform), and each SCP corresponds to one or more region-level data center resources.

[0051] Step 2: The operator builds its own local data center using SCP;

[0052] Step 3: The operator needs to file for the customized domain name and Internet Protocol (IP) address in the location of the SCC, and also needs to file for the domain name of SCP locally. A total of two domain name filings are required.

[0053] Step 4: Operators access their data centers through a customized domain name (scc.customers.clouds.com), and can also provide their customers with service-oriented operation capabilities for data center resources.

[0054] As can be seen from the above description, the joint venture model for related technologies has the following problems:

[0055] Question 1: Jointly built data centers cannot be flexibly deployed, meaning the joint construction model cannot meet the flexible deployment needs of operators. Although operators can reuse (can be understood as using or sharing) cloud vendors' data centers, the assets still belong to the cloud vendors. That is, the cloud vendors manage the entire jointly built data center, which is not friendly to operators' data localization (such as scenarios where operators have high data security requirements) or distributed flexible deployment, thus failing to meet the operators' flexible deployment needs.

[0056] Question 2: Operators need to register their domain names at the location of the cloud provider's global portal. This usually constitutes off-site registration for operators, which cannot meet their cloud deployment needs from the perspectives of operational compliance and localization. Furthermore, the joint construction process is complex.

[0057] Question 3: The data centers jointly built by the cloud vendors are deployed on the operator's local premises. On the one hand, the cost and starting standards (such as the requirements for the number of infrastructure) for cloud vendors to deploy cloud services for operators are relatively high. On the other hand, since the data centers deployed by cloud vendors for operators are independently distributed and operated with the cloud vendors' own data centers, operators cannot reuse the cloud vendors' data centers, and cloud vendors cannot uniformly manage and / or maintain their own data centers and jointly built data centers, such as through upgrades.

[0058] Based on this, in various embodiments of this application, proxy nodes and cloud service nodes deployed in different geographical regions communicate according to configuration information containing at least the registered domain name information associated with the proxy node. The different geographical regions include two geographical regions that require off-site registration of the domain name. Thus, when the locations of the joint venture customer (such as a network operator) and the joint venture provider (such as a cloud computing vendor) are different, for example, when the server of the joint venture customer and the cloud service node of the joint venture provider are deployed in different locations, the joint venture customer only needs to deploy a proxy node to achieve joint venture with the joint venture provider (i.e., the cloud service node can provide cloud services to the target object through the proxy node), thereby meeting the flexible deployment needs of the joint venture customer, i.e., solving the above-mentioned problem 1; at the same time, the joint venture customer does not need to perform off-site registration of the domain name, i.e., it does not need to register the domain name at the location of the cloud service node, but only needs to register the domain name associated with the proxy node locally, thereby simplifying the joint venture process with the joint venture provider, i.e., solving the above-mentioned problem 2.

[0059] In addition, in various embodiments of this application, the cloud services provided by the cloud service node to the target object through the proxy node include at least one of the following:

[0060] The cloud service associated with the first type of data center, wherein the first type of data center and the cloud service node are deployed in the same geographical area, the first type of data center includes a data center jointly constructed by at least two parties, the at least two parties being associated with the proxy node and the cloud service node, the joint construction including at least the joint management and / or operation of the data center;

[0061] A cloud service associated with a second type of data center, wherein the second type of data center and the cloud service node are deployed in the same geographical area, and the second type of data center is managed and / or operated by a single participant;

[0062] A cloud service associated with a third type of data center, wherein the third type of data center and the agent node are deployed in the same geographical area, and the third type of data center is managed and / or operated by a single participant.

[0063] In this way, through the proxy node, both the joint venture customer can reuse the joint venture provider's self-operated and self-built data center (i.e., the second type of data center, which can also be understood as a public cloud), and the joint venture provider can uniformly manage and / or maintain the joint venture customer's self-operated and self-built data center (i.e., the third type of data center, which can also be understood as a private cloud), the joint venture provider's self-operated and self-built data center (i.e., the second type of data center), and the jointly built data center (i.e., the first type of data center), thus solving problem 3 above. Simultaneously, regarding the "target object" in "the cloud service node provides cloud services to the target object through the proxy node," that is, cloud service users (such as operators' users), cloud service users can use both public and private clouds, thus enjoying both the advantages of low price and high cost-effectiveness of public clouds and the advantages of high security of private clouds, thereby improving the user experience.

[0064] This application provides a cloud service provision method, applied to a proxy node, such as... Figure 1 As shown, the method includes:

[0065] Step 101: Obtain configuration information, which includes at least the registered domain name information associated with the agent node. The agent node and the associated cloud service node are deployed in different geographical regions, including two geographical regions where the domain name needs to be registered in different locations.

[0066] Step 102: Communicate with the cloud service node according to the configuration information so that the cloud service node provides cloud services to the target object through the proxy node.

[0067] The cloud services provided by the cloud service node to the target object through the proxy node include at least one of the following:

[0068] Cloud services associated with the first type of data center, such as attached Figure 2 SCP-2-clouds, wherein the first type of data center and the cloud service node are deployed in the same geographical area, the first type of data center includes a data center jointly built by at least two parties, the at least two parties being associated with the proxy node and the cloud service node, the joint construction including at least the joint management and / or operation of the data center;

[0069] Cloud services associated with the second type of data center, such as attached Figure 2 The SCP-1-clouds, wherein the second type of data center is deployed in the same geographical area as the cloud service node, and the second type of data center is managed and / or operated by a single participant;

[0070] Cloud services associated with third-class data centers, such as attached Figure 2 The SCP-1-customers, the third type of data center is deployed in the same geographical area as the agent node, and the third type of data center is managed and / or operated by a single participant.

[0071] Here, it can be understood that for the first type of data center, the at least two participating parties may include a joint construction customer (such as a network operator) and a joint construction provider (such as a cloud computing vendor). The participating party associated with the proxy node refers to the joint construction customer, and the participating party associated with the cloud service node refers to the joint construction provider. Furthermore, the fact that the first type of data center and the cloud service node are deployed in the same geographical area means that the first type of data center is deployed locally on the joint construction provider's premises. In practical applications, the first type of data center can also be referred to as a jointly constructed data center.

[0072] For the second type of data center, one of the participants in management and / or operation refers to the participant associated with the cloud service node, i.e., the joint venture provider. The second type of data center being deployed in the same geographical area as the cloud service node means that the second type of data center is deployed locally on the joint venture provider's premises. In practical applications, the second type of data center can also be understood as a data center self-operated and self-built by the joint venture provider.

[0073] For the third type of data center, one of the participants in its management and / or operation refers to the participant associated with the agent node, i.e., the joint venture client. The fact that the third type of data center and the agent node are deployed in the same geographical area means that the third type of data center is deployed locally on the joint venture client's premises. In practical applications, the third type of data center can also be understood as a data center self-operated and self-built by the joint venture client.

[0074] In practical applications, the proxy node communicates with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node. This can be understood as the proxy node obtaining the ability to provide the cloud services corresponding to the cloud service node to the target object by communicating with the cloud service node.

[0075] In practical applications, the target object can be understood as cloud service users, that is, users of the co-construction customer, such as users of operators.

[0076] In practical applications, the proxy node can also be called a proxy, managed cloud proxy, joint venture cloud proxy, proxy gateway, cloud vendor's application programming interface (API) gateway, cloud management platform, cloud control center, cloud data center platform, etc. This application embodiment does not limit the name of the proxy node, as long as its function (communicating with the cloud service node according to the configuration information so that the cloud service node provides cloud services to the target object through the proxy node) is implemented. The cloud service node can also be called a cloud center, cloud platform, cloud management platform, cloud control center, cloud data center platform, etc. This application embodiment also does not limit the name of the cloud service node, as long as its function (providing cloud services to the target object through the proxy node) is implemented. Furthermore, both the proxy node and the cloud service node can be implemented through hardware and / or software, etc. This application embodiment does not limit the specific implementation method of the proxy node and cloud service node, as long as their functions are implemented.

[0077] In practical applications, the proxy node can be deployed locally at the joint venture client's location, and the cloud service node can be deployed locally at the joint venture provider's location. The phrase "the proxy node and the associated cloud service node are deployed in different geographical regions, including two geographical regions requiring off-site domain name registration" can be understood as the joint venture client and the joint venture provider being located in different provinces, autonomous regions, or municipalities. Thus, through the solution provided in this application embodiment, the joint venture client does not need to perform off-site domain name registration, i.e., it does not need to register the domain name at the location of the cloud service node. It only needs to perform local registration of the domain name corresponding to the proxy node (thereby obtaining the registered domain name information associated with the proxy node included in the above configuration information), thereby simplifying the joint venture process with the joint venture provider.

[0078] In practical applications, considering the size of the cloud service specifications of the cloud service nodes, the cloud service nodes and the proxy nodes can be classified: the cloud service nodes may include a first cloud service node and a second cloud service node, and the proxy nodes may include a first proxy node and a second proxy node. The first proxy node is associated with the first cloud service node, and the second proxy node is associated with the second cloud service node. The first cloud service node may include a global-level public cloud portal, such as the aforementioned SCC (Cloud Control Center); the second cloud service node may include a region-level data center platform, such as the aforementioned SCP (Cloud Data Center Platform).

[0079] In the following description of the embodiments of this application, for the sake of simplicity, the first cloud service node is referred to as SCC, the second cloud service node is referred to as SCP, the first proxy node is referred to as SCC-proxy, the second proxy node is referred to as SCP-proxy, the joint construction provider is referred to as a cloud vendor, and the joint construction customer is referred to as an operator.

[0080] Based on this, in one embodiment, the proxy node may include SCC-proxy, the cloud service node may include SCC, and the SCC-proxy may communicate with the SCC to enable the SCC to provide cloud services to the target object through the SCC-proxy.

[0081] The SCC-proxy can be deployed locally on the operator's premises, while the SCC can be deployed locally on the cloud provider's premises. The SCC can be used to manage at least one SCP, meaning the cloud service corresponding to the SCC can include managing the at least one SCP. Each SCP can be used to manage at least one data center (i.e., one or more data centers, such as the first type, second type, and third type data centers mentioned above), and the data center corresponding to each SCP can be deployed in the same or different geographical regions as the SCC-proxy. In other words, the cloud service corresponding to the SCP can include managing at least one corresponding data center (such as the first type, second type, and third type data centers mentioned above). In other words, the cloud service corresponding to the SCP can be supported by at least one corresponding data center.

[0082] Here, the data center corresponding to each SCP can be deployed in the same or different geographical areas as the SCC-proxy. This can be understood as the data center corresponding to the SCP being deployed either on the SCC-proxy side (i.e., on the operator's local network) or on the SCC side (i.e., on the cloud vendor's local network). In other words, the data center corresponding to each SCP can include one or more data centers from the first type, the second type, and the third type. The specific association between the SCP and the data center can be set according to deployment requirements, and this embodiment does not limit this.

[0083] In practical applications, when the data center corresponding to the SCP is deployed on-premises by the cloud provider, in order to avoid cross-regional domain name registration, the operator needs to deploy an SCP-proxy (e.g., Figure 2 SCP-2-proxy in the context of SCP-2) and its association with the SCP (e.g. Figure 2The SCP-2-clouds can communicate with the target object and obtain the ability to provide the cloud service corresponding to the SCP. From the perspective of the proxy node, the proxy node may include the SCP-proxy, the cloud service node may include the SCP, the SCP may be used to manage at least one on-premises data center of a cloud vendor, and the SCP-proxy may communicate with the SCP to enable the SCP to provide the cloud service to the target through the SCP-proxy. That is, the cloud service corresponding to the SCP may include managing at least one on-premises data center of a cloud vendor. In other words, the cloud service corresponding to the SCP may be supported by at least one on-premises data center of a cloud vendor.

[0084] In practical applications, when the data center corresponding to the SCP is deployed locally by the operator, this data center is actually a self-operated and self-built data center of the operator (i.e., a third-type data center). There is no issue of domain name registration in a different location, meaning the operator can choose not to deploy the SCP (e.g., Figure 2 The SCP-proxy corresponds to SCP-1-customers in the data center. However, the SCC can still manage the SCP corresponding to the data center, that is, the SCC can manage and / or maintain the data center. This working mechanism can be understood as a cloud hosting service (also known as managed cloud service). That is, when operators and cloud providers jointly build data centers, operators can also entrust the cloud providers to maintain and / or manage their self-built data centers.

[0085] As can be seen from the above description, the solution provided in this application allows operators to utilize self-built, locally deployed data centers (i.e., third-type data centers) when they do not need to reuse cloud vendors' locally deployed data centers. In this case, the operator can deploy only one SCC-proxy to communicate with the SCC, enabling the SCC to provide cloud services to the target object through the SCC-proxy, thereby entrusting the localized data center to the cloud vendor. When operators need to reuse cloud vendors' locally deployed data centers, on the one hand, the operator can deploy one SCC-proxy to communicate with the SCC, enabling the SCC to provide cloud services to the target object through the SCC-proxy; on the other hand, the operator can deploy at least one SCP-proxy to communicate with at least one corresponding SCP, enabling the SCP to provide cloud services to the target object through the SCP-proxy, thereby reusing at least one locally deployed data center of the cloud vendor. In this way, operators can independently use their self-operated, locally built data centers, or utilize data center resources provided by cloud vendors. This allows for flexible data center deployment (such as localized deployment, distributed deployment, etc., depending on the operator's needs, and this application embodiment does not limit this) with low deployment costs (i.e., only requiring the addition of SCC-proxy and SCP-proxy overhead). Simultaneously, through the aforementioned proxy nodes (SCC-proxy, SCP-proxy), cloud vendors can access the operator's self-operated, locally built data centers (i.e., third-type data centers, such as...). Figure 2 SCP-1 customers), cloud vendors' self-operated and self-built data centers (i.e., the second type of data center, such as...) Figure 2 SCP-1-clouds and jointly constructed data centers (i.e., Type I data centers, such as...) Figure 2 The unified management and / or maintenance of SCP-2-clouds can reduce the difficulty, cost and expense of cloud vendors managing and / or maintaining data centers.

[0086] In practical applications, the SCC-proxy and SCP-proxy can be implemented using Application Delivery (AD) devices (also known as AD products). For example, multiple different AD devices can be used to act as (i.e., implement) SCC-proxy and SCP-proxy respectively; or, for example, one SCC-proxy and at least one SCP-proxy can be implemented using the same set of AD devices, meaning one AD device can simultaneously act as (i.e., implement) one SCC-proxy and at least one SCP-proxy. The AD device can provide functions such as link load balancing, server load balancing, and Domain Name System (DNS). It can not only achieve real-time monitoring of the status of various data centers, links, and servers, but also allocate user access requests to the corresponding data centers, links, and servers according to preset rules, thereby achieving reasonable data flow allocation and ensuring full utilization of all data centers, links, and servers. Alternatively, the SCC-proxy and SCP-proxy can be implemented using proxy software, such as Nginx. The specific implementation method of the SCC-proxy and SCP-proxy can be set according to cloud deployment requirements, and this application embodiment does not limit this.

[0087] In practical applications, the SCC-proxy can obtain the configuration information locally or from other nodes (such as virtual machines or servers of the operator, which can be set according to the deployment requirements of the operator, and this application embodiment does not limit this; the configuration information can at least include the registered domain name information associated with the SCC-proxy, and can also include relevant information of the SCC, such as domain name, IP address, etc.; the specific method by which the SCC-proxy obtains the configuration information, the specific content of the configuration information, and the specific content of the relevant information of the SCC can be set according to requirements (such as the deployment requirements of the operator and / or cloud vendor), and this application embodiment does not limit this.

[0088] In practical applications, the SCP-proxy can obtain the configuration information locally or from other nodes (such as virtual machines or servers of the operator, which can be set according to the deployment requirements of the operator; this application embodiment does not limit this). The configuration information can at least include the registered domain name information associated with the SCP-proxy, and can also include the relevant information of the SCP corresponding to the SCP-proxy (i.e., the SCP associated with the SCP-proxy), such as the domain name, IP address, etc., and can also include the relevant information of the SCC. The specific method by which the SCP-proxy obtains the configuration information, the specific content of the configuration information, and the specific content of the SCP's relevant information can be set according to requirements (such as the deployment requirements of the operator and / or cloud vendor); this application embodiment does not limit this.

[0089] In practical applications, since the SCC can be used to manage at least one SCP, that is, the SCC can allocate data streams (such as user access requests) to the corresponding SCP; therefore, when the SCC-proxy communicates with the SCC according to the configuration information to enable the SCC to provide cloud services to the target object through the SCC-proxy, it can forward the data stream sent by the target object to the SCC, so that the SCC can divert the data stream to the at least one SCP for corresponding processing.

[0090] Based on this, in one embodiment, the step of communicating with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node, may include:

[0091] The SCC-proxy communicates with the SCC according to the configuration information, so that the SCC provides cloud services to the target object through the SCC-proxy.

[0092] Wherein, the SCC-proxy communicates with the SCC according to the configuration information, so that the SCC provides cloud services to the target object through the SCC-proxy, which may include:

[0093] The SCC-proxy receives a first data stream sent by the target object (which may include user access requests, etc., and can be set according to requirements; this application does not limit the specific content of the data stream).

[0094] The SCC-proxy forwards the first data stream to the SCC, so that the SCC can offload the first data stream to the at least one SCP for corresponding processing.

[0095] In practical applications, after receiving the first data stream, the SCC can split the first data stream according to information such as the domain name of the at least one SCP to obtain a second data stream corresponding to each SCP, and send the obtained second data stream to the corresponding SCP.

[0096] In practical applications, when the data center corresponding to the SCP is deployed locally by the cloud vendor, the SCC can directly send the obtained second data stream to the SCP for corresponding processing; or, the SCC can send the obtained second data stream to the SCP-proxy corresponding to the SCP, and the SCP-proxy will forward the second data stream to the SCP for corresponding processing.

[0097] Based on this, in one embodiment, the step of communicating with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node, may include:

[0098] The SCP-proxy communicates with the SCC according to the configuration information to provide the target object with the cloud service corresponding to the SCC;

[0099] The SCP-proxy communicates with the corresponding SCP (i.e., the SCP associated with the SCP-proxy) according to the configuration information to provide the target object with the corresponding cloud service of the SCP.

[0100] The SCP-proxy communicates with the SCC based on the configuration information to provide the target object with the cloud service corresponding to the SCC, which may include:

[0101] The SCP-proxy receives a second data stream sent by the SCC; the second data stream is obtained by the SCC after splitting the first data stream of the target object, and the first data stream is forwarded to the SCC by the SCC-proxy;

[0102] The SCP-proxy communicates with the corresponding SCP based on the configuration information to provide the target object with the corresponding SCP's cloud services, which may include:

[0103] The SCP-proxy forwards the second data stream to the corresponding SCP for processing.

[0104] In practical applications, since the SCC can be used to manage at least one SCP, meaning the SCC can manage and / or maintain the data center corresponding to the at least one SCP, the SCC can send instruction information to each SCP. This instruction information is used for managing and / or maintaining the data center. Specifically, if the data center corresponding to the SCP is deployed locally by a cloud vendor, the SCC can directly send the instruction information to that SCP; alternatively, the SCC can send the instruction information to the SCP-proxy corresponding to that SCP, which will then forward the instruction information to the SCP.

[0105] Based on this, in one embodiment, the method may further include:

[0106] The SCP-proxy receives the instruction information sent by the SCC and forwards the instruction information to the corresponding SCP; the instruction information is used for the management and / or operation and maintenance of the data center.

[0107] In practical applications, the instruction information can instruct data center server system upgrades and other management and / or operation and maintenance operations. The specific function of the instruction information can be set according to management and / or operation and maintenance needs, and this application embodiment does not limit it.

[0108] In practical applications, during the process of the SCC managing at least one SCP, each second node can report status information to the SCC. This status information can at least include the operational status of the data center's servers, allowing the SCC to determine the indication information based on the received status information. Specifically, if the data center corresponding to the SCP is deployed locally by a cloud vendor, the SCP can directly report the status information to the SCC; alternatively, the SCP can report the status information to the SCC through a corresponding (i.e., associated) SCP-proxy.

[0109] Based on this, in one embodiment, the method may further include:

[0110] The SCP-proxy acquires the status information of the corresponding SCP and sends the acquired status information to the SCC so that the SCC can determine the indication information; the status information includes at least the operating status of the servers in the data center.

[0111] In practical applications, the operating status of the servers in the data center may include server alarm information, etc., which can be set according to requirements. This application embodiment does not limit the specific content of the status information or the form of the server's operating status.

[0112] In practical applications, the SCC-proxy and the SCP-proxy can also provide cloud services, such as cloud data storage, to the target object through local caching.

[0113] Based on this, in one embodiment, the method may further include:

[0114] Cloud services are provided to the target object through local caching.

[0115] Here, the specific service content provided by the SCC-proxy and the SCP-proxy to the target object through local caching can be set according to cloud deployment requirements, and this application embodiment does not limit this.

[0116] In practical applications, to ensure data security, the configuration information may include an encryption strategy. When the SCC-proxy sends data to the SCC, it can use the encryption strategy to encrypt the data to be sent and send the encrypted data to the SCC. Similarly, when the SCP-proxy sends data to the corresponding SCP, it can also use the encryption strategy to encrypt the data to be sent and send the encrypted data to the corresponding SCP.

[0117] Based on this, in one embodiment, the configuration information may further include an encryption strategy; the method may further include:

[0118] When sending data to the cloud service node, the encryption strategy is used to encrypt the data to be sent, and the encrypted data is sent to the cloud service node.

[0119] Here, the specific content of the encryption strategy (such as the type of encryption algorithm) can be set according to cloud deployment requirements, and this application embodiment does not limit this.

[0120] In various embodiments of this application, when the data center corresponding to the SCP is deployed locally by the cloud vendor, the SCP can communicate directly with the SCC, which is also deployed locally by the cloud vendor; or, the SCP can communicate with the SCC through a corresponding (i.e., associated) SCP-proxy deployed locally by the operator, so that the operator can learn about the operating status of the jointly constructed data center (such as the usage of cloud services, etc., which is not limited in this embodiment of the application) through the SCP-proxy for subsequent processing. The specific subsequent processing method can be set according to the needs of the operator, which is not limited in this embodiment of the application.

[0121] The cloud service provision method provided in this application embodiment involves a proxy node acquiring configuration information. This configuration information includes at least the registered domain name information associated with the proxy node. The proxy node and the associated cloud service node are deployed in different geographical regions, including two geographical regions where domain name registration needs to be performed in different locations. The proxy node communicates with the cloud service node based on the configuration information, enabling the cloud service node to provide cloud services to a target object through the proxy node. The solution provided in this application embodiment allows the proxy node and cloud service node deployed in different geographical regions to communicate based on configuration information containing at least the registered domain name information associated with the proxy node. These different geographical regions include two geographical regions where domain name registration needs to be performed in different locations. Thus, when the operator and cloud provider are located in different locations, such as when the operator's server and the cloud provider's cloud service node are deployed in different locations, the operator only needs to deploy a proxy node to achieve joint construction with the cloud provider, thereby meeting the operator's flexible deployment needs. Simultaneously, the operator does not need to perform off-site domain name registration, i.e., does not need to register the domain name at the location of the cloud service node, but only needs to register the domain name corresponding to the proxy node locally, thereby simplifying the joint construction process with the cloud provider.

[0122] In addition, in various embodiments of this application, the cloud services provided by the cloud service node to the target object through the proxy node include at least one of the following:

[0123] The cloud service associated with the first type of data center, wherein the first type of data center and the cloud service node are deployed in the same geographical area, the first type of data center includes a data center jointly constructed by at least two parties, the at least two parties being associated with the proxy node and the cloud service node, the joint construction including at least the joint management and / or operation of the data center;

[0124] A cloud service associated with a second type of data center, wherein the second type of data center and the cloud service node are deployed in the same geographical area, and the second type of data center is managed and / or operated by a single participant;

[0125] A cloud service associated with a third type of data center, wherein the third type of data center and the agent node are deployed in the same geographical area, and the third type of data center is managed and / or operated by a single participant.

[0126] In this way, through the proxy node, operators can independently use their self-operated and self-built localized data centers (i.e., the third type of data center) or use data center resources provided by cloud vendors (i.e., the first and second types of data centers). This allows for flexible deployment of data centers (such as localized deployment, distributed deployment, etc., depending on the operator's needs, and this application embodiment does not limit this) with low deployment costs (i.e., only the overhead of SCC-proxy and SCP-proxy is required). Simultaneously, through the proxy node, cloud vendors can uniformly manage and / or maintain the operator's self-operated and self-built data centers (i.e., the third type of data center), the cloud vendor's self-operated and self-built data centers (i.e., the second type of data center), and jointly built data centers (i.e., the first type of data center), thereby reducing the difficulty, cost, and expense of cloud vendors managing and / or maintaining data centers.

[0127] Furthermore, in various embodiments of this application, the "target object" in "the cloud service node provides cloud services to the target object through the proxy node" refers to cloud service users (such as users of operators). Cloud service users can use both public clouds (i.e., second-type data centers) and private clouds (i.e., third-type data centers), thus enjoying the advantages of low price and high cost-effectiveness of public clouds as well as the advantages of high security of private clouds, thereby improving the user experience.

[0128] The following section provides a more detailed description of this application with reference to application examples.

[0129] In this application example, the co-construction customer is a network operator, referred to as the operator; the co-construction provider is a cloud computing vendor, referred to as the cloud vendor; the first cloud service node includes SCC, and the first proxy node is called SCC-proxy; the second cloud service node includes SCP, and the second proxy node is called SCP-proxy.

[0130] The scenario in this application example is as follows: the operator has a need to build its own independently operated cloud, but since the cloud is a capital investment, the operator needs to avoid building its own cloud completely independently (i.e., avoid being completely responsible for the deployment, operation, management and maintenance of the cloud) in order to reduce costs, and instead cooperate with cloud vendors in the operation and management of the cloud; at the same time, considering data security (i.e. local data protection needs), the operator needs to build some data centers locally.

[0131] The following is combined with Figures 2 to 7 Describe the collaborative architecture of this application example.

[0132] like Figure 2As shown, when operators and cloud providers jointly build infrastructure, they need to deploy SCC-proxy (for communication with SCC), SCP-2-proxy (for communication with SCP-2-clouds, corresponding to the jointly built data center deployed on the cloud provider's side), and SCP-1-customers (corresponding to the operator's self-built data center) locally on the operator's premises; among them, as Figure 3 As shown, SCC-proxy can be implemented by reusing the AD equipment in the operator's local main data center. Simultaneously, the operator needs to register the domain name "customers.clouds.com" locally and customize the domain name on SCC (meaning the operator only needs to register the domain name once, and can expand the data center through subdomains):

[0133] SCC-proxy:scc.customers.clouds.com:IP1;

[0134] SCP-1-customers:region-1.customers.clouds.com:IP2;

[0135] SCP-2-proxy:region-2.customers.clouds.com:IP3.

[0136] Among them, the domains SCC-proxy, SCP-1-customers, and SCP-2-proxy are sibling domains. The operator can customize the domains SCC-proxy and SCP-2-proxy on SCC as follows: Figure 4 As shown, the page on SCC that allows operators to customize the domain name of SCP-1-customers can be viewed as follows: Figure 5 As shown, operators share data center resources (SCC and SCP-2-clouds) with cloud providers through SCC-proxy and SCP-2-proxy, and provide these resources to the operators' users. SCP-1-customers corresponds to the operator's self-built data centers. In other words, operators can provide cloud service capabilities to users through the local domain name "scc.customers.clouds.com", as well as the ability to jointly build data centers with cloud providers. The operator's users can use the operator's self-built data centers (SCP-1-customers) or share the data center resources (SCC and SCP-2-clouds) of cloud providers.

[0137] In this application example, after the operator deploys SCC-proxy and SCP-2-proxy, they need to configure them. SCC-proxy and SCP-2-proxy can be implemented using different AD devices, or they can reuse the same AD device set. When SCC-proxy and SCP-2-proxy are implemented using the same AD device set, the configuration of SCC-proxy and SCP-2-proxy should be as follows: Figure 6 As shown, operators need to upload the Certification Authority (CA) certificates corresponding to SCC and SCP to the AD device. The process of the AD device reading the local certificate can be understood as the process of the agent node obtaining configuration information, that is, the above configuration information may also include the CA certificate.

[0138] In this application example, in actual application, operators can also upload their own Secure Sockets Layer (SSL) certificates to the AD device and configure the SSL offloading and encryption policies for the scc.customers.clouds.com domain. The offloading policy is used to offload the operator's SSL certificate, and the encryption policy is used for encrypted data transmission from the proxies (i.e., SCC-proxy and SCP-2-proxy) to the cloud platform (i.e., SCC and SCP-2-clouds). The configuration information mentioned above may include the SSL offloading and encryption policies.

[0139] In this application example, in actual application, such as Figure 7 As shown, considering that SCP-1-customers may be a dual-active architecture, operators can also configure virtual node pools corresponding to SCP-1-customers on the AD device. SCP-1-customers are data centers operated and built by the operator itself. The configuration information mentioned above may include information related to the virtual node pools.

[0140] In this application example, in actual application, cloud vendor administrators can use the SCC (i.e., from the SCC perspective) to uniformly manage and / or maintain jointly built data centers (SCP-2-clouds) and self-built data centers (cloud vendor-built SCP-1-clouds and carrier-built SCP-1-customers) through Virtual Private Networks (VPNs) and internal domain names.

[0141] In this application example, in actual applications, other proxy software can be used to replace AD ​​devices, such as Nginx. Furthermore, SCC-proxy and SCP-2-proxy are not limited to traffic proxying; they can also extend cloud vendor API gateway services (i.e., SCC-proxy and SCP-2-proxy) to the operator's local network. In other words, SCC-proxy and SCP-2-proxy can provide cloud services through a front-end cache, thereby forming a localized cloud infrastructure service.

[0142] The solution provided in this application example has the following advantages:

[0143] 1) A new cloud operation solution is proposed that can be achieved through joint construction by deploying only AD devices. For the joint construction cloud operation model, operators can start with a lightweight approach (i.e., only deploy AD devices), which reduces operation and maintenance costs and simplifies the joint construction process (only local domain name registration is required, and off-site domain name registration is not required).

[0144] 2) Operators can use their own localized, self-built data centers independently, or they can use data center resources provided by cloud vendors, that is, reuse (can be understood as joint venture) cloud vendors' data center resources. This enables both hyperconverged local cluster deployment of data centers and hyperconverged remote branch deployment of data centers (i.e., data centers include infrastructure deployed in different locations); in other words, it enables flexible deployment of data centers.

[0145] 3) Cloud vendors can manage and / or maintain data centers jointly built by the company and those built by themselves in a unified manner (which can also be understood as operation and maintenance management); in other words, cloud vendors do not need to deploy multiple independent clouds, but can manage data centers in a unified manner based on a single cloud (SCC).

[0146] To implement the method of this application embodiment, this application embodiment also provides a cloud service providing device, which is set on the proxy node, such as... Figure 8 As shown, the device includes:

[0147] The acquisition unit 801 is used to acquire configuration information, which includes at least the registered domain name information associated with the agent node. The agent node and the associated cloud service node are deployed in different geographical regions, including two geographical regions where the domain name needs to be registered in different locations.

[0148] Service unit 802 is used to communicate with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node.

[0149] In one embodiment, the proxy node includes a first proxy node, and the cloud service node includes a first cloud service node; the first cloud service node is used to manage at least one second cloud service node, each second cloud service node is used to manage at least one data center, and the data center corresponding to each second cloud service node is deployed in the same or different geographical areas as the first proxy node;

[0150] Accordingly, the service unit 802 is specifically used for:

[0151] Receive the first data stream sent by the target object;

[0152] The first data stream is forwarded to the first cloud service node, so that the first cloud service node can distribute the first data stream to the at least one second cloud service node for corresponding processing.

[0153] In one embodiment, the proxy node includes a second proxy node, and the cloud service node includes a second cloud service node; the second cloud service node is used to manage at least one data center;

[0154] Accordingly, the service unit 802 is specifically used for:

[0155] The system receives a second data stream sent by a first cloud service node; the first cloud service node manages at least one second cloud service node, and each second cloud service node manages at least one data center; the second data stream is obtained by the first cloud service node after splitting the first data stream of the target object, and the first data stream is forwarded to the first cloud service node by the first proxy node; the data center corresponding to each second cloud service node is deployed in the same or different geographical areas as the first proxy node;

[0156] The second data stream is forwarded to the corresponding second cloud service node for processing.

[0157] In one embodiment, when the proxy node includes the second proxy node, the service unit 802 is further configured to receive indication information sent by the first cloud service node and forward the indication information to the corresponding second cloud service node; the indication information is used for the management and / or operation and maintenance of the data center.

[0158] In one embodiment, when the proxy node includes the second proxy node, the service unit 802 is further configured to obtain the status information of the corresponding second cloud service node and send the obtained status information to the first cloud service node so that the first cloud service node can determine the indication information; the status information includes at least the operating status of the server in the data center.

[0159] In one embodiment, the service unit 802 is further configured to provide cloud services to the target object through local caching.

[0160] In one embodiment, the configuration information further includes an encryption strategy; the service unit 802 is further configured to encrypt the data to be sent using the encryption strategy when sending data to the cloud service node, and then send the encrypted data to the cloud service node.

[0161] In practical applications, the acquisition unit 801 can be implemented by a processor in the cloud service provider device, or by a processor in the cloud service provider device combined with a communication interface; the service unit 802 can be implemented by a processor in the cloud service provider device combined with a communication interface.

[0162] It should be noted that the cloud service providing device provided in the above embodiments is only illustrated by the division of the above program modules when providing cloud services. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the cloud service providing device and the cloud service providing method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0163] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiments of this application, the embodiments of this application also provide a proxy node, such as... Figure 9 As shown, the proxy node 900 includes:

[0164] Communication interface 901 enables information exchange with cloud service nodes and / or other proxy nodes;

[0165] The processor 902 is connected to the communication interface 901 to enable information interaction with cloud service nodes and / or other proxy nodes, and to execute the methods provided by one or more of the above technical solutions when running computer programs;

[0166] The memory 903 stores computer programs that can run on the processor 902.

[0167] Specifically, the processor 902 is used for:

[0168] Obtain configuration information, which includes at least the registered domain name information associated with the agent node. The agent node and the associated cloud service node are deployed in different geographical regions, including two geographical regions where the domain name needs to be registered in different locations.

[0169] According to the configuration information, the cloud service node communicates with the cloud service node through the communication interface 901, so that the cloud service node provides cloud services to the target object through the proxy node.

[0170] In one embodiment, the proxy node 900 includes a first proxy node, and the cloud service node includes a first cloud service node; the first cloud service node is used to manage at least one second cloud service node, each second cloud service node is used to manage at least one data center, and the data center corresponding to each second cloud service node is deployed in the same or different geographical areas as the first proxy node.

[0171] Accordingly, the processor 902 is specifically used for:

[0172] The first data stream sent by the target object is received through the communication interface 901;

[0173] The first data stream is forwarded to the first cloud service node through the communication interface 901, so that the first cloud service node can distribute the first data stream to the at least one second cloud service node for corresponding processing.

[0174] In one embodiment, the proxy node 900 includes a second proxy node, and the cloud service node includes a second cloud service node; the second cloud service node is used to manage at least one data center;

[0175] Accordingly, the processor 902 is specifically used for:

[0176] The communication interface 901 receives a second data stream sent by a first cloud service node; the first cloud service node manages at least one second cloud service node, and each second cloud service node manages at least one data center; the second data stream is obtained by the first cloud service node after splitting the first data stream of the target object, and the first data stream is forwarded to the first cloud service node by the first proxy node; the data center corresponding to each second cloud service node is deployed in the same or different geographical areas as the first proxy node;

[0177] The second data stream is forwarded to the corresponding second cloud service node through the communication interface 901 so that the second data stream can be processed accordingly.

[0178] In one embodiment, when the proxy node 900 includes the second proxy node, the processor 902 is further configured to receive indication information sent by the first cloud service node through the communication interface 901, and forward the indication information to the corresponding second cloud service node; the indication information is used for data center management and / or operation and maintenance.

[0179] In one embodiment, when the proxy node 900 includes the second proxy node, the processor 902 is further configured to obtain the status information of the corresponding second cloud service node through the communication interface 901, and send the obtained status information to the first cloud service node so that the first cloud service node can determine the indication information; the status information includes at least the operating status of the servers in the data center.

[0180] In one embodiment, the processor 902 is further configured to provide cloud services to the target object via local caching.

[0181] In one embodiment, the configuration information further includes an encryption strategy; the processor 902 is further configured to encrypt the data to be sent using the encryption strategy when sending data to the cloud service node through the communication interface 901, and then send the encrypted data to the cloud service node.

[0182] It should be noted that the specific processing procedure of the processor 902 can be understood by referring to the above method, and will not be repeated here.

[0183] Of course, in practical applications, the various components in the agent node 900 are coupled together through the bus system 904. It can be understood that the bus system 904 is used to implement communication between these components. In addition to the data bus, the bus system 904 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 9 The general labeled all buses as Bus System 904.

[0184] The memory 903 in this embodiment is used to store various types of data to support the operation of the agent node 900. Examples of such data include any computer program used to operate on the agent node 900.

[0185] The methods disclosed in the embodiments of this application can be applied to or implemented by the processor 902. The processor 902 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor 902 or by instructions in the form of software. The processor 902 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 902 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the memory 903. The processor 902 reads the information in the memory 903 and combines it with its hardware to complete the steps of the aforementioned method.

[0186] In an exemplary embodiment, the agent node 900 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0187] It is understood that the memory 903 in this embodiment can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0188] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a memory 903 storing a computer program, which can be executed by the processor 902 of the agent node 900 to complete the steps described in the aforementioned method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0189] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0190] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0191] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A method for providing cloud services, characterized in that, Applied to proxy nodes, including: Obtain configuration information, which includes at least the registered domain name information associated with the agent node. The agent node and the associated cloud service node are deployed in different geographical regions, including two geographical regions where the domain name needs to be registered in different locations. The cloud service node communicates with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node.

2. The method according to claim 1, characterized in that, The cloud services provided by the cloud service node to the target object through the proxy node include at least one of the following: The cloud service associated with the first type of data center, wherein the first type of data center and the cloud service node are deployed in the same geographical area, the first type of data center includes a data center jointly constructed by at least two parties, the at least two parties being associated with the proxy node and the cloud service node, the joint construction including at least the joint management and / or operation of the data center; A cloud service associated with a second type of data center, wherein the second type of data center and the cloud service node are deployed in the same geographical area, and the second type of data center is managed and / or operated by a single participant; A cloud service associated with a third type of data center, wherein the third type of data center and the agent node are deployed in the same geographical area, and the third type of data center is managed and / or operated by a single participant.

3. The method according to claim 1, characterized in that, The proxy node includes a first proxy node, and the cloud service node includes a first cloud service node; the first cloud service node is used to manage at least one second cloud service node, each second cloud service node is used to manage at least one data center, and the data center corresponding to each second cloud service node is deployed in the same or different geographical areas as the first proxy node. The step of communicating with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node, includes: Receive the first data stream sent by the target object; The first data stream is forwarded to the first cloud service node, so that the first cloud service node can distribute the first data stream to the at least one second cloud service node for corresponding processing.

4. The method according to claim 1, characterized in that, The proxy node includes a second proxy node, and the cloud service node includes a second cloud service node; the second cloud service node is used to manage at least one data center; the step of communicating with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node, includes: The system receives a second data stream sent by a first cloud service node; the first cloud service node manages at least one second cloud service node, and each second cloud service node manages at least one data center; the second data stream is obtained by the first cloud service node after splitting the first data stream of the target object, and the first data stream is forwarded to the first cloud service node by the first proxy node; the data center corresponding to each second cloud service node is deployed in the same or different geographical areas as the first proxy node; The second data stream is forwarded to the corresponding second cloud service node for processing.

5. The method according to claim 4, characterized in that, The method further includes: The system receives the instruction information sent by the first cloud service node and forwards the instruction information to the corresponding second cloud service node; the instruction information is used for the management and / or operation and maintenance of the data center.

6. The method according to claim 5, characterized in that, The method further includes: The status information of the corresponding second cloud service node is obtained and sent to the first cloud service node so that the first cloud service node can determine the indication information; the status information includes at least the operating status of the servers in the data center.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: Cloud services are provided to the target object through local caching.

8. The method according to any one of claims 1 to 6, characterized in that, The configuration information also includes an encryption strategy; the method further includes: When sending data to the cloud service node, the encryption strategy is used to encrypt the data to be sent, and the encrypted data is sent to the cloud service node.

9. A cloud service providing device, characterized in that, Configuration on the proxy node includes: The acquisition unit is used to acquire configuration information, which includes at least the registered domain name information associated with the agent node. The agent node and the associated cloud service node are deployed in different geographical regions, including two geographical regions where the domain name needs to be registered in different locations. The service unit is used to communicate with the cloud service node according to the configuration information, so that the cloud service node provides cloud services to the target object through the proxy node.

10. A proxy node, characterized in that, include: The processor and the memory used to store computer programs that can run on the processor. When the processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 8.

11. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8.

Images