Cloud computing technology-based service access method and system

Abstract

The present application provides a cloud computing technology-based service access method and system. A network access address of a service is determined on the basis of tenant granularity, thereby implementing fine management. The method is applied to a cloud system comprising a service access node and an infrastructure, and the infrastructure comprises a plurality of data centers. The service access node records an additional domain name and a region selection rule of a tenant for a service, wherein the additional domain name indicates tenant information, the region selection rule indicates a plurality of regions, and the same service of the tenant is deployed in data centers of the plurality of regions. The service access node receives a domain name access request sent by a client, wherein the request carries a domain name comprising a primary domain name and the additional domain name, and the primary domain name indicates the domain name of the service. The service access node determines the region selection rule on the basis of the additional domain name, selects, from among the plurality of regions indicated by the region selection rule, a target region having the highest client access efficiency, and sends, to the client, a network access address of the service located in a data center of the target region.

Description

A business access method and system based on cloud computing technology

[0001] This application claims priority to Chinese Patent Application No. 202510107203.9, filed on January 22, 2025, entitled "A Business Access Method and System Based on Cloud Computing Technology", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of cloud computing, and in particular to a business access method and system based on cloud computing technology. Background Technology

[0003] Global server load balancing (GSLB) is an advanced load balancing technology primarily used to distribute network traffic among servers or data centers located in multiple geographically dispersed locations. Its main goal is to improve website availability and response speed, and optimize the use of network resources.

[0004] In related methods, cross-regional services are provided through GSLB, where the service provider offers a unified access area to tenants using the service and performs unified scheduling. For example, in the event of a primary region failure, GSLB can be used to transfer the service traffic of different tenants to the same disaster recovery area.

[0005] In this approach, the access zones for different tenants of the same service are configured and scheduled uniformly by the service provider. If you want to adjust the access zone of a tenant in this service, you need to adjust the access zones of all tenants using the service, which affects the normal use of other tenants, may cause service failures in other tenants, and reduce service quality. Summary of the Invention

[0006] This application provides a business access method and system based on cloud computing technology, which is used to determine the network access address of a business based on tenant granularity, thereby achieving fine-grained management.

[0007] Firstly, this application provides a business access method based on cloud computing technology. This method is applied to a cloud system, which includes business access nodes and infrastructure, including multiple data centers. The method includes:

[0008] The service access node records the tenant's additional domain name for the service and the region selection rules. The additional domain name indicates the tenant's information, and the region selection rules indicate the multiple regions selected by the user. The same service for the tenant is deployed in each of these multiple regions; this service is the service targeted by the additional domain name. For example, consider multiple regions including a first region and a second region. The first region has a first data center, and the second region has a second data center. The tenant's service is deployed in both the first and second data centers; the services deployed in these two data centers are for the same tenant's same service. Furthermore, the first and second data centers are included within the multiple data centers included in the infrastructure. The service access node receives domain name access requests from clients, carrying a domain name. This domain name includes a primary domain name and an additional domain name. The client is deployed outside the cloud system or within the infrastructure; the primary domain name indicates the domain name of the service. The service access node determines the region selection rules based on the additional domain name, selects the region with the highest access efficiency for the client from the first and second regions indicated by the region selection rules as the target region, and sends the network access address of the service located in the data center of the target region to the client.

[0009] In this application, the service access node records the additional domain name and region selection rules for each service. The additional domain name indicates tenant information, meaning that the region selection rules for each tenant's accessed service are recorded separately. When the service access node receives a domain name access request from a client, it determines the accessed service based on the main domain name carried in the request and the tenant initiating the request based on the additional domain name carried in the request, thus determining the region selection rules for that tenant under that service. From the multiple regions indicated by the region selection rules, the region with the highest access efficiency for the client is selected as the target region, and the network access address of the service in the data center located in the target region is returned to the client, completing the resolution of the domain name access request. During the domain name resolution process, the service access node determines the address to be accessed by the domain name access request at the tenant level. The region selection rules for services accessed by different tenants do not affect each other, achieving fine-grained management. Adjusting the network access address of a domain name access request initiated by one tenant will not affect other tenants and will not degrade service quality.

[0010] In some alternative implementations of the first aspect, among the multiple regions indicated by the region selection rule, the region with the highest access efficiency to the client can be any of the following: the region geographically closest to the client, the region with the best network status to the client, or a region in normal working condition. A region in normal working condition can be understood as a region without any failures.

[0011] In this application, the multiple regions indicated by the region selection rule may be the regions with the highest client access efficiency, which can be flexibly selected based on the needs of actual applications, thus enriching the implementation methods and application scenarios of the technical solution of this application.

[0012] In some alternative implementations of the first aspect, the tenant information may include any of the following: instance information, resource information, or tenant identifier.

[0013] In this application, tenant information has multiple possibilities and can be set according to the needs of actual applications, which enriches the presentation of additional domain names and domain names and further enhances the flexibility of the technical solution of this application.

[0014] In some optional implementations of the first aspect, the cloud system also includes a cloud management platform, and the method further includes: the cloud management platform obtaining the tenant's additional domain name and region selection rules for the business input by the tenant. The cloud management platform sends the tenant's additional domain name and region selection rules for the business to the business access node, so that the business access node records the tenant's additional domain name and region selection rules for the business.

[0015] In this application, the cloud system may also include a cloud management platform. The cloud management platform acts as a medium connecting users and business access nodes, transmitting the additional domain names and regional selection rules configured by the user for the business to the business access nodes, which is conducive to realizing personalized configuration by users.

[0016] In some optional implementations of the first aspect, after the business access node records the tenant's additional domain name and region selection rules for the business, the method further includes: the cloud management platform replicating the business deployed in the first data center to the second data center across regions. Alternatively, the cloud management platform replicating the business deployed in the second data center to the first data center across regions. This ensures that the same business of the tenant is deployed in both the first and second data centers.

[0017] This application achieves the deployment of the same service for the same tenant in different data centers set up in different regions by replicating the service across regions. This provides a basis for selecting target regions based on region selection rules, ensuring that the same service is deployed in multiple data centers within multiple regions indicated by the region selection rules, thus guaranteeing the feasibility of the solution.

[0018] Secondly, this application provides a cloud system, including business access nodes and infrastructure, the infrastructure including multiple data centers. The business access nodes are used for:

[0019] Record the additional domain name and region selection rules for the tenant's business. The additional domain name is used to indicate the tenant information, and the region selection rules are used to indicate the first region and the second region. The first region is set up in the first data center where the tenant's business is deployed, and the second region is set up in the second data center where the tenant's business is deployed. The first data center and the second data center are contained in multiple data centers.

[0020] The business access node receives domain name access requests sent by the client. The domain name access request carries the domain name of the business. The domain name includes the main domain name and the supplementary domain name. The client is deployed outside the cloud system or in the infrastructure. The main domain name is used to indicate the domain name of the business.

[0021] The service access node determines the region selection rules based on the additional domain name, selects the region with the highest access efficiency for the client from the first and second regions indicated by the region selection rules as the target region, and sends the network access address of the service located in the data center of the target region to the client.

[0022] The cloud system is used to implement the methods shown in the first aspect or any possible implementation of the first aspect, which will not be elaborated here.

[0023] Thirdly, this application provides a computing device including a processor and a memory. The processor of the computing device is used to execute instructions stored in the memory, causing the computing device to implement the method shown in the first aspect or any possible implementation of the first aspect.

[0024] Fourthly, this application provides a computing device cluster, including at least one computing device, each computing device including a processor and a memory; the processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster implements the method disclosed in the first aspect or any possible implementation of the first aspect.

[0025] Fifthly, this application provides a computer program product containing instructions that, when executed on a processor, implement the method shown in the first aspect or any possible implementation of the first aspect; or, when the instructions are run by a cluster of computer devices, cause the cluster of computer devices to implement the method disclosed in the first aspect or any possible implementation of the first aspect.

[0026] In a sixth aspect, this application provides a computer-readable storage medium storing computer program instructions that, when executed on a processor, implement the method shown in the first aspect or any possible implementation of the first aspect; or, when executed by a cluster of computer devices, cause the cluster of computer devices to implement the method disclosed in the first aspect or any possible implementation of the first aspect.

[0027] The beneficial effects shown in any of the second to sixth aspects are similar to those of the first aspect or any possible implementation of the first aspect, and will not be repeated here. Attached Figure Description

[0028] Figure 1 is a schematic diagram of the architecture of a cloud system provided in an embodiment of this application;

[0029] Figure 2 is a schematic diagram of an architecture of a data center provided in an embodiment of this application;

[0030] Figure 3 is a flowchart illustrating a service access method based on cloud computing technology provided in an embodiment of this application.

[0031] Figure 4 is another flowchart illustrating the business access method based on cloud computing technology provided in an embodiment of this application.

[0032] Figure 5 is another flowchart illustrating the business access method based on cloud computing technology provided in an embodiment of this application.

[0033] Figure 6 is a schematic diagram of a cloud system provided in an embodiment of this application;

[0034] Figure 7 is a schematic diagram of a computing device provided in an embodiment of this application;

[0035] Figure 8 is a schematic diagram of a computing device cluster provided in an embodiment of this application;

[0036] Figure 9 is another schematic diagram of the computing device cluster provided in the embodiment of this application. Detailed Implementation

[0037] This application provides a service access method and system based on cloud computing technology, which is used to determine the network access address of a service based on tenant granularity, thereby achieving fine-grained management.

[0038] The embodiments of this application will now be described with reference to the accompanying drawings. Those skilled in the art will recognize that, with technological advancements and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.

[0039] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of units is not necessarily limited to those units, but may include other units not explicitly listed or inherent to those processes, methods, products, or apparatuses. Additionally, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can be expressed as: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0040] First, please refer to Figures 1 and 2. Figure 1 is a schematic diagram of the cloud system architecture provided in the embodiment of this application, and Figure 2 is a schematic diagram of the data center architecture provided in the embodiment of this application.

[0041] In some optional implementations, the cloud system includes service access nodes and infrastructure. Service access nodes are used to resolve domain name access requests to obtain the network access address corresponding to the request. In the method provided in this application embodiment, the service access node can select a target region from multiple regions indicated by the tenant's region selection rules based on tenant information. The network access address of the domain name resolution request is the network access address of the service corresponding to the domain name access request deployed in the data center of the target region. Specific implementation details will be provided later.

[0042] The infrastructure includes multiple data centers located in different regions. For example, as shown in Figure 1, Region 1 includes Cloud Data Center 1 and Cloud Data Center 2, and Region 2 includes Cloud Data Center 3 and Cloud Data Center 4. Each cloud data center has multiple servers, and these servers run service instances (including at least one of virtual machines, containers, and dedicated hosts). Cloud services are deployed on these service instances. In this embodiment, the same service of the same tenant can be deployed across different regions in data centers. That is, the same service of the same tenant, including all business data of that tenant under that service, is deployed in data centers in different regions.

[0043] In this context, "region" refers to the division based on geographical location and network latency, with resources shared within the same region. This can also be understood as sharing public services such as elastic computing, block storage, object storage, virtual private cloud (VPC) networks, elastic public IP addresses, and images within the same region.

[0044] As exemplified in Figure 2, a data center includes an internal data center network and multiple servers. Service access nodes communicate with these servers via the internal data center network.

[0045] As shown in Figure 1, in some optional implementations, the cloud system also includes a cloud management platform. The cloud management platform can also be called a cloud service platform, cloud platform, etc. The cloud management platform provides access interfaces, such as user interfaces or application programming interfaces (APIs), allowing tenants to remotely access the cloud management platform to register a cloud account and password and log in. After successful login, tenants can further select and purchase virtual machines with specific specifications (such as processor, memory, and disk) on the cloud management platform. After successful purchase, the cloud management platform provides a remote login account and password for the purchased virtual machine, enabling clients to remotely log in to the virtual machine via the internet, install and run the tenant's applications on the virtual machine. In other words, tenants can create, manage, log in to, and operate virtual machines in the cloud data center through the cloud management platform.

[0046] In addition, the cloud management platform also communicates with the business access nodes, sending information from the client (such as tenant information and region selection rules for the business) to the business access solution.

[0047] In the embodiment shown in Figure 1, the client is deployed outside the cloud system. In practical applications, the client can also be located inside the cloud system; specifically, the client is deployed within the infrastructure, such as on a server in a data center, as shown in Figure 2.

[0048] It should be noted that for solutions where the client is deployed outside the cloud system, the terminal device running the client can be a device with wireless transceiver capabilities, also known as a terminal. Specifically, it can refer to user equipment (UE), access terminal, subscriber unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user device. Terminal devices can also be satellite phones, cellular phones, smartphones, wireless data cards, wireless modems, machine-type communication devices, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, communication devices mounted on high-altitude aircraft, wearable devices, drones, robots, terminals in device-to-device (D2D) communication, terminals in vehicle-to-everything (V2X) communication, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, mixed reality (MR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, and wireless terminals in smart cities. This application does not limit the scope of wireless terminals, such as those in a city, smart homes, or future communication networks.

[0049] In addition, in the embodiments of this application, there may be more or fewer terminal devices in the system. The number and type of terminal devices are determined according to actual needs, and are not limited here.

[0050] Please refer to Figure 3 below, which is a flowchart illustrating the business access method based on cloud computing technology provided in the embodiments of this application.

[0051] 301. The business access node records the tenant's additional domain name and region selection rules for the business. The additional domain name is used to indicate the tenant's tenant information, and the region selection rules are used to indicate the first region and the second region. The first region is set up in the first data center where the tenant's business is deployed, and the second region is set up in the second data center where the tenant's business is deployed. The first data center and the second data center are contained in multiple data centers.

[0052] The cloud computing-based business access method provided in this application is applied to a cloud system, which includes business access nodes and infrastructure. The business access node can be a GSLB node, a server participating in traffic distribution within a global server load balancing system. The infrastructure includes multiple data centers located in different regions, each region comprising one or more data centers, and services can be deployed on each data center. Different types of services can be deployed on different data centers within the same region, providing different types of cloud services. For example, Region 1 includes Data Center 1 and Data Center 2; Data Center 1 provides cloud desktop services, and Data Center 2 provides cloud conferencing services. The same or different types of services can be deployed on data centers in different regions, providing the same or different types of cloud services. For example, Region 1 includes Data Center 1 and Data Center 2, and Region 2 includes Data Center 3, Data Center 4, and Data Center 5. Data Center 1 and Data Center 3 are used to provide cloud desktop services, Data Center 2 and Data Center 4 are used to provide cloud conferencing services, and Data Center 5 is used to provide cloud storage services.

[0053] In general, within a cloud system, data centers located in different regions can provide the same services, but a tenant's business may not be deployed across all regions of the cloud system. That is, the region indicated by the region selection rules is included within the regions provided by the cloud system, and may be some or all of the regions provided by the cloud system. Furthermore, for different tenants using the same service, the regions where each tenant's service is deployed may also differ. For example, suppose the cloud system includes five regions: Region 1 to Region 5, and the data centers in each region can provide cloud desktop services. Tenant 1 and Tenant 2's cloud desktop services can be deployed in some or all of these five regions. Tenant 1's cloud desktop service is deployed in Regions 1, 2, and 3 of these five regions, and the same cloud desktop service data for Tenant 1 is included in the data centers of these three regions. Tenant 2's cloud desktop service is deployed in Regions 3 and 5 of these five regions, and the same cloud desktop service data for Tenant 2 is included in the data centers of these two regions. In other words, a tenant's business can be deployed across regions in different data centers in different regions.

[0054] The aforementioned functionality is achieved because, in this embodiment, a region selection rule is configured for the tenant under this service, and the service access node records this region selection rule. More specifically, the service access node records the tenant's additional domain name and region selection rule for the service. The additional domain name indicates the tenant's tenant information and is used to uniquely identify the tenant; the region selection rule indicates multiple regions where the service is deployed. Therefore, the service access node recording the additional domain name and region selection rule for the service can also be understood as the service access node recording multiple deployment regions for a specific tenant's specific service.

[0055] The additional domain name, also known as the tenant-specific name (DSN), is used to indicate the tenant's information. Tenant information can include various types, such as instance information, resource information, or tenant identifiers. Instance information refers to the information about the instance through which the tenant uses the service, and can be represented by an instance identifier. For example, in the domain d-713b7b8cab.idcenter.companyA.com, d-713b7b8cab is the instance identifier. Resource information refers to the information about the cloud service resources used by the tenant, and can be represented by resource names. For example, in the domain portal-name.idcenter.companyA.com, portal-name is the additional domain name. The tenant identifier is used to uniquely identify the tenant; for example, in the domain domain-name.rgc.companyA.com, domain-name is the additional domain name. The tenant information indicated by the additional domain name can be set based on the needs of the actual application. The form of the additional domain name may differ for different services; specific details are not limited here.

[0056] In this application embodiment, there are multiple possibilities for obtaining tenant information, business access nodes, and additional domain names and regional selection rules for tenant services. These can be set based on the needs of actual applications, enriching the presentation of additional domain names and domain names, and further enhancing the flexibility of the technical solution of this application.

[0057] In addition, there are several possible ways for the business access node to obtain the tenant's additional domain name and region selection rules for the business, which will be explained below.

[0058] In some optional implementations, during the service configuration phase, the tenant's region selection rules for the service are set based on system parameters, enabling the service access node to obtain the tenant's additional domain name and region selection rules for the service. In other words, the cloud system sets multiple deployment regions for the tenant's service. For example, tenant 1's service 1 is deployed in both region 1 and region 2. Then, the service access node records tenant 1's additional domain name 1 and region selection rule 1 for service 1. The additional domain name 1 indicates tenant 1's tenant information, and the region selection rule 1 indicates that tenant 1's deployment regions for service 1 include both region 1 and region 2. That is, tenant 1's service 1 is deployed in both the data center set up in region 1 and the data center in region 2.

[0059] In some optional implementations, tenants can configure region selection rules for their services. Specifically, the cloud system also includes a cloud management platform. The cloud management platform obtains the tenant's additional domain name and region selection rules for their services, input by the tenant, through an access interface (e.g., a user interface or API). It then sends these additional domain names and region selection rules to the service access nodes, allowing the service access nodes to record them. Furthermore, tenants can configure the service's deployment region through a user interface, enabling the terminal device displaying the interface to obtain the region selection rules and send them to the cloud management platform. The cloud management platform determines the additional domain name based on the tenant running on the terminal device, thus obtaining the additional domain name and region selection rules for the service. Alternatively, tenants can set the service's deployment region by inputting command lines via an API, enabling the cloud management platform to obtain the region selection rules. Based on the tenant running on the terminal device that received the command line, the cloud management platform then determines the additional domain name, thus obtaining the additional domain name and region selection rules for the service.

[0060] It should be noted that the business access node can record the additional domain names and region selection rules for different tenants for different services. For a tenant, a tenant may only use one service of the cloud system, or it may use multiple services provided by the cloud system. Therefore, for each service, the business access node needs to record the additional domain names and region selection rules for that tenant to clarify the region selection rules for a certain tenant under a certain service.

[0061] For example, in the following example, a tenant's identical service is deployed in both the first data center of the first region setting and the second data center of the second region setting. That is, the service access node records the regions indicated by the tenant's region selection rules for the service, including both the first and second regions. This service is then deployed across regions in both the first data center of the first region setting and the second data center of the second region setting.

[0062] In this embodiment of the application, the cloud system may further include a cloud management platform. The cloud management platform serves as a medium connecting users and business access nodes, transmitting the additional domain names and regional selection rules configured by the user for the business to the business access nodes, which is conducive to realizing personalized configuration by users.

[0063] 302. The business access node receives a domain name access request sent by the client. The domain name access request carries a domain name, which includes the main domain name and the supplementary domain name. The client is deployed outside the cloud system or in the infrastructure. The main domain name is used to indicate the domain name of the business.

[0064] In business access scenarios, business access nodes also receive domain name access requests sent by clients. These requests carry a primary domain name and an additional domain name. The primary domain name indicates the domain name of the business, reflecting the business corresponding to the domain name access request. For example, in the domain name domain-name.rgc.companyA.com, the primary domain name is rgc.companyA.com, indicating that the business is the resource governance center (RGC) service provided by Company A. Company A can be understood as a cloud service provider offering RGC services. The additional domain name indicates the tenant's tenant information. Based on the primary domain name and the additional domain name, it can be determined which tenant is accessing which service in the domain name access request.

[0065] To elaborate further, the client sends a business access request, triggering the business access process. The Domain Name System (DNS) server resolves the business access request, obtaining a domain name access request carrying the domain name. It then forwards the domain name access request to the business access node, enabling the business access node to obtain the domain name access request.

[0066] In addition, the client can be deployed outside the cloud system or in the infrastructure; there are no specific restrictions here.

[0067] 303. The service access node determines the region selection rules based on the additional domain name, selects the region with the highest access efficiency for the client from the first and second regions indicated by the region selection rules as the target region, and sends the network access address of the service located in the data center of the target region to the client.

[0068] The service access node records the tenant's additional domain name and region selection rules for the service, thus recording the region selection rules for a specific tenant under a specific service. After receiving a domain name access request, based on the domain name carried in the request, it determines which tenant is accessing which service. This also determines the current tenant's region selection rules for the service to be accessed. From the multiple regions indicated by the region selection rules, it selects the region with the highest access efficiency for the client as the target region and sends the network access address of the service located in the data center of the target region to the client. The network access address is the source Internet Protocol (IP) address. This process can also be understood as follows: after resolving the domain name access request, the data center in the target region responds to the domain name resolution request, confirming that the network address accessed by the service is the IP address of the service in the data center set in the target region.

[0069] The target region is the region with the highest access efficiency for the client among multiple regions indicated by the region selection rules. In practical applications, the region with the highest access efficiency for the client can be any of the following: the region geographically closest to the client, the region with the best network status for the client, or the region that is in normal working condition.

[0070] In some optional implementations, the service access node determines the region where the client is located based on the IP address of the domain name access request. It then determines the IP addresses of multiple regions indicated by the region selection rules. Based on the client's IP address and the region's IP address, the physical distance between the client and the region is determined. Finally, the region with the shortest physical distance is selected from multiple regions as the geographically closest region. Specifically, the region's IP address refers to the IP address of the data center where the service is deployed within that region.

[0071] In some optional implementations, the service access node compares the network status of communication with the client in multiple regions indicated by the region selection rule, and selects the region with the best network status as the target region. The network status includes throughput and communication latency. The best network status means either the highest throughput or the lowest communication latency.

[0072] In some optional implementations, the region with the highest access efficiency is the region in normal working condition, which is also the region without any faults. Faults can be of various kinds, including power outages, network outages, malicious attacks, natural disasters, and program errors, causing services deployed on the data center in that region to malfunction. Setting the region with the highest access efficiency as the region in normal working condition can be applied in disaster recovery scenarios. Specifically, the region selection rules recorded by the service access node indicate multiple regions, including the primary region and the disaster recovery region. The primary region and the disaster recovery region can be set by the tenant or by the cloud system. In the scenario where the primary region is in normal working condition, the target region is the primary region. In the scenario where the primary region fails, the target region is the disaster recovery region in normal working condition.

[0073] Furthermore, the primary region can be any of the multiple regions indicated by the region selection rules, including the region geographically closest to the client, the region with the best network condition for the client, or a region with compliant access. The disaster recovery region can be preferentially set to any region other than the primary region indicated by the region selection rules, including the region geographically closest to the client, the region with the best network condition for the client, or a region with compliant access.

[0074] In the description of step 301 above, the example used is indicating a first region and a second region using a region selection rule. In this example, the target region is the region with the highest efficiency for client access selected from the first region and the second region.

[0075] In this embodiment of the application, the multiple regions indicated by the region selection rule may be the regions with the highest client access efficiency, which can be flexibly selected based on the needs of actual application, thus enriching the implementation methods and application scenarios of the technical solution of this application.

[0076] As described above, in this embodiment, the service access node records the additional domain name and region selection rules for the service. The additional domain name indicates tenant information, meaning that the region selection rules for different tenants' accessed services are recorded separately. After receiving a domain name access request from a client, the service access node determines the accessed service based on the main domain name carried in the request and the tenant initiating the request based on the additional domain name carried in the request, thereby determining the region selection rules for that tenant under that service. From the multiple regions indicated by the region selection rules, the region with the highest access efficiency for the client is selected as the target region, and the network access address of the service in the data center located in the target region is returned to the client, completing the resolution of the domain name access request. During the domain name resolution process, the service access node determines the address to be accessed by the domain name access request at the tenant level. The region selection rules for services accessed by different tenants do not affect each other, achieving fine-grained management. Adjusting the network access address of a domain name access request initiated by one tenant will not affect other tenants and will not degrade service quality.

[0077] The aforementioned specification briefly describes the deployment of the same service of the same tenant in different regions of the cloud system. Specifically, this is achieved through cross-region replication of the service. For example, in step 301, the service access node records the tenant's additional domain name and region selection rules for the service, where the region selection rules indicate a first region and a second region. This means that the regions to be deployed for this service by the tenant include both the first and second regions. Therefore, the tenant's service should be deployed in both the first data center set up in the first region and the second data center set up in the second region. In a specific implementation, the service may already be deployed in the first data center. In this scenario, after the service access node records the tenant's additional domain name and region selection rules for the service, the cloud management platform replicates the service deployed in the first data center to the second data center. Alternatively, the service may already be deployed in the second data center. In this scenario, after the service access node records the tenant's additional domain name and region selection rules for the service, the cloud management platform replicates the service deployed in the second data center to the first data center. Regardless of the implementation process, the final result is that the service used by the tenant is deployed in multiple regions indicated by the tenant's region selection rules.

[0078] For example, Tenant 1's region selection rule for Service 1 specifies Region 1, Region 2, and Region 3. Before the service access node obtains the region selection rule, only Data Center 1 in Region 1 has Tenant 1's Service 1 deployed. Then, after obtaining the region selection rule, the cloud management platform replicates Tenant 1's Service 1 deployed in Data Center 1 to Data Center 2 in Region 2 and Data Center 3 in Region 3 across regions.

[0079] In this embodiment, cross-regional replication of services enables the deployment of the same service for the same tenant in different data centers located in different regions. This provides a basis for selecting target regions based on region selection rules, ensuring that the same service is deployed in multiple data centers within multiple regions indicated by the region selection rules, thus guaranteeing the feasibility of the solution.

[0080] The foregoing description explained the implementation principle of the cloud computing-based business access method provided in the embodiments of this application. The implementation process of this method will be further illustrated below with specific examples.

[0081] Please refer to Figures 4 and 5, which are schematic flowcharts of the business access method based on cloud computing technology provided in the embodiments of this application.

[0082] In the embodiment shown in Figure 4, it is assumed that object storage services can be provided in data centers located in Region 1, Region 2, and Region 3 of the cloud system. Both tenant A and tenant B use object storage services. Tenant A's region selection rule for this service indicates Region 1 and Region 2, meaning that tenant A's object storage service is deployed in both the data centers located in Region 1 and Region 2. Tenant B's region selection rule for this service indicates Region 2 and Region 3, meaning that tenant A's object storage service is deployed in both the data centers located in Region 2 and Region 3.

[0083] Tenant A sends a service access request to the DSN server via a client. The DSN server parses the request and obtains a domain name access request, which includes a primary domain name and an additional domain name. The primary domain name indicates that the service domain name is the object storage service domain name, and the additional domain name indicates that the tenant seeking access is Tenant A. The service access node determines the region selection rule for Tenant A's object storage service based on the additional domain name. This region selection rule indicates two regions: Region 1 and Region 2. The service access node selects the region with the highest access efficiency for the client from Region 1 and Region 2 as the target region and returns the IP address of the object storage service in the data center located in the target region to the client.

[0084] In proximity-based access scenarios, the area with the highest access efficiency is either the one physically closest to the client or the one with the best network conditions. In disaster recovery scenarios, the area selection rules further specify the roles of Area 1 and Area 2 as the primary area and the disaster recovery area, respectively. When the primary area is functioning normally, the area with the highest access efficiency becomes the primary area. When the primary area fails, the area with the highest access efficiency becomes the disaster recovery area, which is currently functioning normally.

[0085] Similarly, tenant B sends a service access request to the DSN server via a client. The DSN server parses the service access request and obtains a domain name access request. The domain name access request carries a primary domain name and an additional domain name. The primary domain name indicates that the domain name of the service is the domain name of the object storage service, and the additional domain name indicates that the tenant to be accessed is tenant B. The service access node determines the region selection rule for tenant B's object storage service based on the additional domain name. This region selection rule indicates regions 2 and 3. From regions 2 and 3, the service access node selects the region with the highest access efficiency for the client as the target region and returns the IP address of the object storage service in the data center located in the target region to the client.

[0086] In the embodiment shown in Figure 5, it is assumed that the Resource Governance Center service is available in both the data center located in Region 1 and the data center located in Region 2 of the cloud system. Both tenant A and tenant B use this service, and the regions indicated by region selection rule A for this service and the regions indicated by region selection rule B for this service are both Region 1 and Region 2. That is, the Resource Governance Center service for tenant A and the Resource Governance Center service for tenant B are deployed in both the data center located in Region 1 and the data center located in Region 2. Client A running tenant A and client B running tenant B are both physically closest to Region 1.

[0087] Tenant A sends a business access request A to the DSN server via client A. The DSN server parses the business access request A and obtains a domain name access request A. The domain name access request A carries a primary domain name and an additional domain name. The primary domain name indicates that the domain name of the business is the domain name of the resource governance center service, and the additional domain name indicates that the tenant to be accessed is tenant A. The business access node determines the region selection rule A for tenant A for the resource governance center service based on the additional domain name. The region selection rule A indicates the regions, including region 1 and region 2. From region 1 and region 2, the business access node selects region 1, which is physically closest to client A, as the target region and returns the IP address of the resource governance center service in the data center located in the target region to client A.

[0088] Tenant B sends a business access request B to the DSN server via client B. The DSN server parses the business access request B and obtains a domain name access request B, which carries a primary domain name and an additional domain name. The primary domain name indicates that the domain name of the business is the domain name of the resource governance center service, and the additional domain name indicates that the tenant to be accessed is tenant B. The business access node determines the region selection rule B for tenant B's resource governance center service based on the additional domain name. This region selection rule B indicates the regions, including region 1 and region 2. Due to network egress issues of client B, although client B is physically closest to region 2, its access efficiency is lower than that of region 2. Therefore, the business access node selects region 2, which has the highest access efficiency for client B, as the target region and returns the IP address of the resource governance center service in the data center located in the target region to client B.

[0089] As illustrated in Figure 5, although the physically closest regions are the same for different clients running different tenants, and these regions are where the tenants' services are deployed, the target regions responding to domain name access requests from different tenants differ due to varying access efficiency between the clients and different regions. This achieves tenant-level granular region selection.

[0090] In summary, for services with the same functionality provided by a cloud system, the technical solution provided in this application embodiment can determine the region where each tenant deploys the service based on tenant granularity. For a domain name access request initiated by a tenant for that service, the region responding to the domain name access request is determined from multiple regions indicated by the tenant's region selection rules for that service. This achieves tenant-level granular management; a change in the response region for one tenant's service will not affect the services of other tenants, thus ensuring service quality.

[0091] Please refer to Figure 6 below, which illustrates a cloud system provided in an embodiment of this application. As shown in Figure 6, the cloud system 600 includes a service access node 601 and infrastructure 602. The infrastructure includes multiple data centers.

[0092] In some optional implementations, service access node 601 is used for:

[0093] Record the additional domain name and region selection rules for the tenant's business. The additional domain name is used to indicate the tenant information, and the region selection rules are used to indicate the first region and the second region. The first region is set up in the first data center where the tenant's business is deployed, and the second region is set up in the second data center where the tenant's business is deployed. The first data center and the second data center are contained in multiple data centers.

[0094] The system receives domain name access requests sent by clients. These requests carry the domain name of the business, which includes the main domain name and supplementary domain names. The client is deployed outside the cloud system or in the infrastructure. The main domain name is used to indicate the domain name of the business.

[0095] Based on the additional domain name, determine the region selection rules, select the region with the highest access efficiency for the client from the first and second regions indicated by the region selection rules as the target region, and send the network access address of the service located in the data center of the target region to the client.

[0096] In some alternative implementations, the area with the highest access efficiency to the client includes any of the following: the area geographically closest to the client, the area with the best network conditions to the client, or the area that is in normal working order.

[0097] In some alternative implementations, tenant information includes any of the following: instance information, resource information, or tenant identifier.

[0098] In some optional implementations, the cloud system also includes a cloud management platform 603. The cloud management platform 603 is configured to: obtain the tenant's additional domain name and region selection rules for the service input by the tenant; and send the tenant's additional domain name and region selection rules for the service to the service access node.

[0099] In some alternative implementations, the cloud system also includes a cloud management platform 603. The cloud management platform 603 is further configured to: replicate services deployed in the first data center to a second data center across regions; or, replicate services deployed in the second data center to the first data center across regions.

[0100] The business access node 601, infrastructure 602, and cloud management platform 603 can all be implemented through software or hardware. For example, the implementation of business access node 601 will be described below. Similarly, the implementation methods of infrastructure 602 and cloud management platform 603 can refer to the implementation method of business access node 601.

[0101] As an example of a software functional unit, business access node 601 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, or a container. Further, the aforementioned computing instance may be one or more. For example, business access node 601 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed within the same region or in different regions. Further, the multiple hosts / virtual machines / containers used to run the code may be distributed within the same availability zone (AZ) or in different AZs, each AZ including one or more geographically proximate data centers. Typically, a region may include multiple AZs.

[0102] Similarly, multiple hosts / virtual machines / containers used to run this code can be distributed within the same Virtual Private Cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Communication between two VPCs within the same region, as well as between VPCs in different regions, requires a communication gateway to be set up within each VPC to enable interconnection between VPCs.

[0103] As an example of a hardware functional unit, the service access node 601 may include at least one computing device, such as a server. Alternatively, the service access node 601 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be implemented using a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), generic array logic (GAL), or any combination thereof.

[0104] It should be noted that different steps in the cloud computing-based business access method are implemented through the business access node 601, infrastructure 602, and cloud management platform 603, respectively, to realize all the functions of the cloud system 600 and achieve the cloud computing-based business access method provided in this application embodiment. Further details will not be elaborated here.

[0105] Please refer to Figure 7, which is a schematic diagram of a computing device provided in an embodiment of this application. The computing device 700 includes a processor 701, a communication interface 702, a bus 703, and a memory 704. The processor 701, communication interface 702, and memory 704 communicate via the bus 703. In practical applications, communication can also be achieved through other means such as wireless transmission; specific details are not limited here. It should be understood that this application does not limit the number of processors and memories in the computing device 700.

[0106] Processor 701 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0107] The communication interface 702 uses transceiver modules, such as, but not limited to, network interface cards and transceivers, to enable communication between the computing device 700 and other devices or communication networks.

[0108] Bus 703 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one line is used in Figure 7, but this does not imply that there is only one bus or one type of bus. Bus 703 can include pathways for transmitting information between various components of computing device 700 (e.g., memory 704, processor 701, communication interface 702).

[0109] Memory 704 may include volatile memory, such as random access memory (RAM). Memory 704 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0110] The memory 704 stores executable program code, which the processor 701 executes to implement the functions of the aforementioned service access node 601, infrastructure 602, and cloud management platform 603, thereby realizing a service access method based on cloud computing technology. In other words, the memory 704 stores instructions for executing the service access method based on cloud computing technology.

[0111] This application also provides a computing device cluster, which includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some optional embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

[0112] Please refer to Figures 8 and 9, which are schematic diagrams of the structure of the computing device cluster provided in the embodiments of this application.

[0113] As shown in Figure 8, the computing device cluster includes at least one computing device 700. The memory 704 of one or more computing devices 700 in the computing device cluster may store the same instructions for executing the cloud computing-based service access method provided in the embodiments of this application.

[0114] In some alternative implementations, the memory 704 of one or more computing devices 700 in the computing device cluster may also store partial instructions for executing service access methods based on cloud computing technology. In other words, a combination of one or more computing devices 700 can jointly execute instructions for executing service access methods based on cloud computing technology.

[0115] It should be noted that the memory 704 in different computing devices 700 in the computing device cluster can store different instructions, which are used to execute some functions of the cloud system.

[0116] In some alternative implementations, one or more computing devices in a computing device cluster can be connected via a communication interface or a network. The network can be a wide area network (WAN) or a local area network (LAN), etc. Figure 9 illustrates one possible implementation. As shown in Figure 9, two computing devices 700A and 700B are connected via a network. Specifically, they are connected to the network through the communication interfaces in each computing device. In this type of possible implementation, the memory 704 in computing device 700A stores instructions for performing the functions of the service access node 601. Simultaneously, the memory 704 in computing device 700B stores instructions for performing the functions of the infrastructure 602 and the cloud management platform 603.

[0117] It should be understood that the functions of computing device 700A shown in Figure 9 can also be performed by multiple computing devices 700. Similarly, the functions of computing device 700B can also be performed by multiple computing devices 700.

[0118] This application also provides another computing device cluster. The connection relationship between the computing devices in this computing device cluster can be similarly referred to the connection method of the computing device cluster described in Figures 8 and 9, and will not be repeated here.

[0119] This application also provides a computer program product containing instructions. The computer program product may be a software or program product containing instructions, capable of running on a computing device or stored on any usable medium. When the computer program product is run on at least one computer device, it causes the at least one computer device to perform the aforementioned cloud computing-based business access method.

[0120] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium capable of being stored by a computing device, or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the aforementioned cloud computing-based business access method.

[0121] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0122] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of this application.

Claims

1. A business access method based on cloud computing technology, characterized in that, The method is applied to a cloud system, which includes business access nodes and infrastructure, the infrastructure including multiple data centers; the method includes: The service access node records the tenant's additional domain name and region selection rules for the service. The additional domain name is used to indicate the tenant's tenant information, and the region selection rules are used to indicate a first region and a second region. The first region has a first data center where the tenant's service is deployed, and the second region has a second data center where the tenant's service is deployed. The first data center and the second data center are included in the plurality of data centers. The service access node receives a domain name access request sent by the client. The domain name access request carries a domain name, which includes a main domain name and the additional domain name. The client is deployed outside the cloud system or in the infrastructure. The main domain name is used to indicate the domain name of the service. The service access node determines the region selection rule based on the additional domain name, selects the region with the highest access efficiency for the client from the first region and the second region indicated by the region selection rule as the target region, and sends the network access address of the service located in the data center of the target region to the client.

2. The method according to claim 1, characterized in that, The region with the highest access efficiency to the client includes any of the following: The region geographically closest to the client, the region with the best network status to the client, or the region that is in normal working condition.

3. The method according to claim 1 or 2, characterized in that, The tenant information includes any of the following: instance information, resource information, or tenant identifier.

4. The method according to any one of claims 1 to 3, characterized in that, The cloud system also includes a cloud management platform, and the method further includes: The cloud management platform obtains the additional domain name and region selection rules for the service input by the tenant. The cloud management platform sends the tenant's additional domain name and region selection rules for the service to the service access node.

5. The method according to any one of claims 1 to 4, characterized in that, After the service access node records the tenant's additional domain name and region selection rules for the service, the method further includes: The cloud management platform will replicate the services deployed in the first data center to the second data center across regions; or... The cloud management platform will replicate the services deployed in the second data center to the first data center across regions.

6. A cloud system, characterized in that, This includes service access nodes and infrastructure, wherein the infrastructure includes multiple data centers; the service access nodes are used for: Record the additional domain name and region selection rules for the tenant's business. The additional domain name is used to indicate the tenant information of the tenant. The region selection rules are used to indicate a first region and a second region. The tenant's business is deployed in a first data center set up in the first region. The tenant's business is deployed in a second data center set up in the second region. The first data center and the second data center are included in the plurality of data centers. The client receives a domain name access request sent by the client. The domain name access request carries the domain name of the business. The domain name includes the main domain name and the additional domain name. The client is deployed outside the cloud system or in the infrastructure. The main domain name is used to indicate the domain name of the business. The region selection rule is determined based on the additional domain name. The region with the highest access efficiency for the client is selected from the first region and the second region indicated by the region selection rule as the target region. The network access address of the service located in the data center of the target region is sent to the client.

7. The cloud system according to claim 6, characterized in that, The region with the highest access efficiency to the client includes any of the following: The region geographically closest to the client, the region with the best network status to the client, or the region that is in normal working condition.

8. The cloud system according to claim 6 or 7, characterized in that, The tenant information includes any of the following: instance information, resource information, or tenant identifier.

9. The cloud system according to any one of claims 6 to 8, characterized in that, The cloud system also includes a cloud management platform; The cloud management platform is used to obtain the additional domain name and region selection rules for the business input by the tenant. The cloud management platform is used to send the tenant's additional domain name and region selection rules for the service to the service access node.

10. The cloud system according to any one of claims 6 to 9, characterized in that, The cloud system also includes a cloud management platform; the cloud management platform is further used for: The services deployed in the first data center are replicated to the second data center across regions; or... The cloud management platform will replicate the services deployed in the second data center to the first data center across regions.

11. A computing device cluster, characterized in that, It includes at least one computing device, each computing device including a processor and memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the cluster of computing devices to perform the method as described in any one of claims 1 to 5.

12. A computer program product containing instructions, characterized in that, When the instruction is executed by the computing device cluster, the computing device cluster performs the method as described in any one of claims 1 to 5.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer program instructions that, when executed by a cluster of computing devices, cause the cluster of computing devices to perform the method as described in any one of claims 1 to 5.

Images