WO2024017286A1 - Procédé d'attribution de largeur de bande de réseau public basé sur un service en nuage public et plateforme de gestion en nuage - Google Patents

Procédé d'attribution de largeur de bande de réseau public basé sur un service en nuage public et plateforme de gestion en nuage Download PDF

Info

Publication number
WO2024017286A1
WO2024017286A1 PCT/CN2023/108101 CN2023108101W WO2024017286A1 WO 2024017286 A1 WO2024017286 A1 WO 2024017286A1 CN 2023108101 W CN2023108101 W CN 2023108101W WO 2024017286 A1 WO2024017286 A1 WO 2024017286A1
Authority
WO
WIPO (PCT)
Prior art keywords
bandwidth
tenant
cloud
bidding
management platform
Prior art date
Application number
PCT/CN2023/108101
Other languages
English (en)
Chinese (zh)
Inventor
宋利伟
杨昌鹏
罗忠城
米鹏辉
Original Assignee
华为云计算技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为云计算技术有限公司 filed Critical 华为云计算技术有限公司
Publication of WO2024017286A1 publication Critical patent/WO2024017286A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching

Definitions

  • the present application relates to the field of cloud technology, and in particular to a public network bandwidth allocation method and a cloud management platform that runs the method in a scenario where the public cloud service is set to be accessible from the public network.
  • cloud instances set up by tenants in cloud data centers that provide public cloud services can be accessed by devices under the cloud through the public network.
  • the public network bandwidth is managed by the cloud management platform, and the public network bandwidth is managed by the tenant in the cloud data center.
  • the cloud management platform is purchased and used by the tenant's cloud instance assigned to the tenant.
  • the existing public network bandwidth allocation method has problems such as low bandwidth utilization and difficulty in utilizing idle bandwidth due to the fixed allocation method.
  • embodiments of the present invention provide a public network bandwidth allocation method and a cloud management platform based on public cloud services, which can effectively solve the problems of low bandwidth utilization and difficult utilization of idle bandwidth in the existing public network bandwidth allocation methods. technical issues.
  • this application provides a public network bandwidth allocation method based on public cloud services.
  • This method is applied on a cloud management platform that manages infrastructure.
  • the infrastructure also includes multiple cloud data centers.
  • the public network bandwidth allocation method includes the following steps: the cloud management platform provides a bandwidth configuration interface, and the bandwidth configuration interface is used to obtain the available public network bandwidth for the first elastic public network IP address input by the first tenant who logs in to the cloud management platform.
  • the cloud management platform determines that there is a first idle bandwidth matching the first bid bandwidth in the target cloud data center, the cloud management platform provides the first idle bandwidth to at least one cloud instance of the first tenant, where the first tenant's The bandwidth fee incurred by at least one cloud instance using the first idle bandwidth to access the public network in the target cloud data center is determined based on the first bidding quotation.
  • the cloud management platform obtains the first bidding bandwidth that the first tenant wants to bid for at least one cloud instance, and queries the target cloud data center where the at least one cloud instance is located for the bandwidth that exists in the target cloud data center.
  • For idle public network bandwidth when it is determined that the target cloud data center has the first idle bandwidth that satisfies the first bidding bandwidth, the first idle bandwidth is provided to at least one cloud instance of the first tenant to realize the tenant's response to the idle public network bandwidth.
  • the cloud side provides an expression interface to tenants, allowing tenants to allocate idle bandwidth of the cloud data center to the tenant's cloud instances through proactive quotation, thereby rationally utilizing idle bandwidth resources, reducing the waste of idle bandwidth resources, and saving costs.
  • the above-mentioned bandwidth configuration interface is also used to obtain the second elastic public network IP address of the second tenant input by the second tenant who logs in to the cloud management platform.
  • the cloud management platform determines whether to continue to provide all of the first idle bandwidth to at least one cloud instance of the first tenant based on the second bidding bandwidth. Bandwidth or part of bandwidth.
  • the cloud management platform determines whether to continue to provide all or part of the first idle bandwidth to at least one cloud instance of the first tenant based on the second bidding bandwidth, This is achieved in the following manner: when the cloud management platform determines that there is remaining idle bandwidth matching the second bidding bandwidth in the target cloud data center, the cloud management platform keeps providing the first idle bandwidth to at least one cloud instance of the first tenant, and provides the first idle bandwidth to the first tenant. At least one cloud instance of the second tenant provides a second free bandwidth that matches the second bid bandwidth
  • the second idle bandwidth matching the second bidding bandwidth is provided to the second tenant, thereby satisfying the second tenant's needs.
  • the demand for the second bidding bandwidth ensures that the bandwidth needs of different tenants can be met on the premise that there is enough idle bandwidth in the target cloud data center, thereby avoiding the waste of idle bandwidth resources to the greatest extent.
  • the bandwidth configuration interface is also used to obtain the available public IP address of the second elastic public network of the second tenant input by the second tenant who logs in to the cloud management platform. Based on the second bidding quotation of the network bandwidth, the bandwidth fee generated by at least one cloud instance of the second tenant using the second idle bandwidth to access the public network in the target cloud data center is determined based on the second bidding quotation.
  • the second tenant when the second tenant obtains the right to use the second idle bandwidth, it will be billed based on the second bidding quotation proposed by it, thereby realizing hierarchical sales of idle bandwidth for the cloud service provider, thus maximizing Minimize the waste of idle bandwidth resources and achieve reasonable revenue.
  • the bandwidth configuration interface is also used to obtain the available public IP address of the second elastic public network of the second tenant input by the second tenant who logs in to the cloud management platform.
  • the cloud management platform determines whether to continue to provide all or part of the first idle bandwidth to at least one cloud instance of the first tenant based on the second bidding bandwidth. This is achieved in the following manner: the cloud management platform determines If there is no remaining idle bandwidth matching the second bidding bandwidth in the target cloud data center, determine whether to continue to provide all the bandwidth of the first idle bandwidth to at least one cloud instance of the first tenant based on the second bidding bandwidth and the second bidding quotation. or partial bandwidth.
  • the target cloud data center does not have a second idle bandwidth that meets the second bidding bandwidth, it means that the target cloud data center has a small amount of idle bandwidth.
  • the new tenant's Bidding quotations and bidding bandwidth continue to compete with old tenants for idle bandwidth, thereby maximizing the use of idle bandwidth.
  • the cloud management platform determines whether to continue to provide all of the first idle bandwidth to at least one cloud instance of the first tenant based on the second bidding bandwidth and the second bidding quotation. Bandwidth or part of the bandwidth is achieved in the following way: when the cloud management platform determines that the second bidding quotation is higher than the first bidding quotation and the second bidding bandwidth is greater than or equal to the first bidding bandwidth, the cloud management platform stops providing services to the first tenant. At least one cloud instance provides first idle bandwidth matching the first bid bandwidth and provides the first idle bandwidth to at least one cloud instance of the second tenant, wherein at least one cloud instance of the second tenant uses the first idle bandwidth in the target cloud data center. The bandwidth fee incurred by using an idle bandwidth to access the public network is determined based on the second bidding price.
  • the cloud management platform determines which tenant to allocate the idle bandwidth to based on the bidding levels of different tenants, so that Make reasonable use of idle bandwidth and ensure maximum idle bandwidth revenue.
  • the cloud management platform determines whether to continue to provide all of the first idle bandwidth to at least one cloud instance of the first tenant based on the second bidding bandwidth and the second bidding quotation. Bandwidth or part of the bandwidth is achieved in the following manner: when the cloud management platform determines that the second bidding quotation is higher than the first bidding quotation and the second bidding bandwidth is smaller than the first bidding bandwidth, it stops providing it to at least one cloud instance of the first tenant.
  • the bandwidth fee generated by the cloud instance using part of the first idle bandwidth to access the public network in the target cloud data center is determined based on the second bidding quotation.
  • the idle bandwidth is determined according to the bidding level of different tenants to which tenant is allocated, so as to make reasonable use of the idle bandwidth. bandwidth and ensure maximum idle bandwidth revenue.
  • the cloud management platform determines whether to continue to provide all of the first idle bandwidth to at least one cloud instance of the first tenant based on the second bidding bandwidth and the second bidding quotation. Bandwidth or part of the bandwidth is achieved in the following manner: the cloud management platform determines that when the second bidding quotation is lower than the first bidding quotation, it keeps providing the first idle bandwidth matching the first bidding bandwidth to at least one cloud instance of the first tenant. bandwidth, and notify the second tenant that the bidding failed.
  • the cloud management platform when the remaining bandwidth of the target cloud data center does not have a second idle bandwidth that meets the second bidding bandwidth, the cloud management platform first compares the tenant's bidding quotations. When the second bidding quotation is lower During the first bidding quotation, the cloud management platform continues to provide the first idle bandwidth to the first tenant without adjustment, and notifies the second tenant that the bidding failed, thereby ensuring that the idle bandwidth is provided to the tenant with the highest bid and achieving the best revenue.
  • the bandwidth configuration interface is also used to obtain the user level of the first tenant and the user level of the second tenant, and the cloud management platform determines the user level according to the second bidding bandwidth and the second The bidding quotation determines whether to continue to provide all or part of the first idle bandwidth to at least one cloud instance of the first tenant in the following manner: the cloud management platform determines whether to continue to provide all or part of the first idle bandwidth to at least one cloud instance of the first tenant according to the second bidding bandwidth, the second bidding quotation, and the users of the first tenant. The level and the user level of the second tenant determine whether to continue to provide all or part of the first idle bandwidth to at least one cloud instance of the first tenant.
  • the cloud management platform can also be used to obtain the user level of the tenant.
  • the cloud management platform can realize the decision based on the user level of the tenant. Management of bandwidth allocation.
  • the cloud management platform determines whether to continue to the third tenant based on the second bidding bandwidth, the second bidding quotation, the user level of the first tenant, and the user level of the second tenant.
  • At least one cloud instance of a tenant provides all or part of the first idle bandwidth in the following manner: the cloud management platform determines that the second bidding quotation is equal to the first bidding quotation and the user level of the second tenant is higher than that of the first tenant. If the user level and the second bidding bandwidth are greater than or equal to the first bidding bandwidth, stop providing the first idle bandwidth that matches the first bidding bandwidth to at least one cloud instance of the first tenant, and provide at least one cloud instance of the second tenant with the first idle bandwidth.
  • the cloud instance provides the first idle bandwidth, wherein the bandwidth fee generated by at least one cloud instance of the second tenant using the first idle bandwidth to access the public network in the target cloud data center is determined based on the second bidding quotation.
  • the cloud management platform when the remaining bandwidth of the target cloud data center does not have a second idle bandwidth that meets the second bidding bandwidth, and the first bidding quotation and the second bidding quotation are equal, the cloud management platform first The user level of one tenant is compared with the user level of the second tenant, and idle bandwidth is provided to the tenant with a higher user level first. This ensures that tenants with higher user levels can first use idle bandwidth at reasonable prices.
  • the cloud management platform determines whether to continue to the third tenant based on the second bidding bandwidth, the second bidding quotation, the user level of the first tenant, and the user level of the second tenant.
  • At least one cloud instance of a tenant provides all or part of the first idle bandwidth in the following manner: the cloud management platform determines that the second bidding quotation is equal to the first bidding quotation and the user level of the second tenant is higher than that of the first tenant.
  • user level and the second bidding bandwidth is less than the first bidding bandwidth, stop providing part of the first idle bandwidth to at least one cloud instance of the first tenant, and provide the third bandwidth to at least one cloud instance of the second tenant.
  • Part of the first idle bandwidth is equal to the second bid bandwidth
  • at least one cloud instance of the second tenant uses part of the first idle bandwidth in the target cloud data center to access the public network.
  • the bandwidth charges incurred are determined based on the second bidding price.
  • the cloud management platform when there is no second idle bandwidth that satisfies the second bidding bandwidth in the remaining bandwidth of the target cloud data center, and the first bidding quotation and the second bidding quotation are equal, the cloud management platform first Compare the user level of the first tenant with the user level of the second tenant, and then compare the second bidding bandwidth with the first bidding bandwidth.
  • the user level of the second tenant is higher than the user level of the first tenant, and the second bidding bandwidth is less than
  • the cloud management platform gives priority to providing idle bandwidth to the second tenant, and adjusts the portion of the first idle bandwidth that meets the second bidding bandwidth from being provided to the first tenant to providing it to the second tenant.
  • a Layer 2 bidding allocation method is formed that determines the priority based on the tenant user level, so that idle bandwidth can be reasonably allocated when the bidding quotations are equal.
  • the cloud management platform determines whether to continue to the third tenant based on the second bidding bandwidth, the second bidding quotation, the user level of the first tenant, and the user level of the second tenant. At least one cloud instance of a tenant provides all or part of the first idle bandwidth in the following manner: the cloud management platform determines that the second bidding quotation is equal to the first bidding quotation and the user level of the second tenant is lower than that of the first tenant. In the case of a user level, keep providing the first idle bandwidth matching the first bidding bandwidth to at least one cloud instance of the first tenant, and notify the second tenant that the bidding failed.
  • the idle bandwidth supply of the first tenant with a higher user level is guaranteed, thereby ensuring that tenants with a higher user level can preferentially use the idle bandwidth at a reasonable price.
  • the cloud management platform provides the first idle bandwidth to at least one cloud instance of the first tenant in the following manner: the cloud management platform provides the first idle bandwidth to the first tenant in a preset time period. At least one cloud instance of the first tenant provides the first idle bandwidth, and the preset time period is a time period set by the first tenant or a time period preset by the cloud management platform.
  • tenants can use idle bandwidth within a preset time period through preset time.
  • the preset time period is, for example, non-busy time or busy time.
  • Tenants can set it according to the working status of the cloud instance. This enables flexible allocation of idle bandwidth based on time periods.
  • the bandwidth configuration interface is also used to obtain the region and availability zone to which the target cloud data center belongs, which is implemented in the following manner: the cloud management platform obtains the region and availability zone according to the bandwidth configuration interface. Regions and Availability Zones Select a target cloud data center from multiple cloud data centers.
  • the cloud management platform can quickly select the target cloud data center through the region and availability zone entered by the tenant.
  • At least one cloud instance includes a virtual machine, a container, a bare metal server, an object storage bucket, an ELB elastic load balancer, a NAT network address translation gateway, and a cloud Any type of cache.
  • cloud instances such as virtual machines, containers, bare metal servers, object storage buckets, ELB elastic load balancers, NAT network address translation gateways, and cloud caches can all use idle bandwidth.
  • the cloud management platform charges the first tenant a bandwidth fee.
  • the available public network bandwidth for the first elastic public network IP address of the first tenant input by the first tenant logging into the cloud management platform is obtained in the bandwidth configuration interface
  • the first bidding bandwidth and the first bidding quotation are realized in the following manner: the cloud management platform prompts the first tenant to the total idle bandwidth existing in the target cloud data center.
  • the cloud management platform prompts tenants with idle bandwidth before they enter bidding bandwidth and bidding quotations, so that tenants can understand the current total idle bandwidth of the target cloud data center where their cloud instances are located, which is helpful. Use it to make judgments on bidding bandwidth and bidding quotations.
  • the bandwidth configuration interface is also used to obtain the basic bandwidth of the available public network bandwidth for the first elastic public network IP address input by the first tenant, where the basic bandwidth The fees incurred are determined based on the pay-as-you-go price or the prepaid price, and the basic bandwidth is not affected by the bidding of other tenants.
  • the bandwidth configuration interface obtains the tenant's basic bandwidth
  • the basic bandwidth is not affected by the bidding of other tenants, ensuring that the cloud instance provides stable Internet services under the guaranteed bandwidth and is not affected by other tenants' bidding.
  • the impact of bidding bandwidth is not limited to the bandwidth configuration interface.
  • the first bidding price is greater than the cost price and less than the on-demand billing price.
  • the bidding price is limited to be greater than the cost price and less than the on-demand billing price, so as to encourage tenants to use idle bandwidth, improve the utilization rate of idle bandwidth, and at the same time reduce the cost of using idle bandwidth.
  • the cloud management platform sends bandwidth status information to the first tenant, and the bandwidth status information includes the actual use of at least one cloud instance of the first tenant. bandwidth.
  • the cloud management platform sends the actual bandwidth used by its cloud instance to the tenant to enable users to monitor the actual bandwidth used.
  • this application provides a cloud management platform for managing infrastructure that provides public cloud services.
  • the infrastructure includes multiple cloud data centers.
  • the cloud management platform includes: a bandwidth configuration interface providing module for providing bandwidth. Configuration interface.
  • the bandwidth configuration interface referred to by the former is used to obtain the first bidding bandwidth and the first bidding quotation for the available public network bandwidth of the first elastic public IP address of the first tenant input by the first tenant who logs in to the cloud management platform.
  • the first elastic public network IP address is bound to at least one cloud instance of the first tenant, and at least one cloud instance of the first tenant is set in a target cloud data center among multiple cloud data centers.
  • the cloud management platform also includes: bandwidth A management module configured to provide the first idle bandwidth to at least one cloud instance of the first tenant when it is determined that the target cloud data center has a first idle bandwidth that matches the first bidding bandwidth, wherein at least one cloud instance of the first tenant The bandwidth fee incurred by the instance using the first free bandwidth to access the public network in the target cloud data center is determined based on the first bidding quotation.
  • the second aspect or any implementation of the second aspect is the device implementation corresponding to the first aspect or any implementation of the first aspect.
  • the description in the first aspect or any implementation of the first aspect is applicable to the second aspect Or any implementation method of the second aspect, which will not be described again here.
  • 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 at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster performs the above-mentioned first aspect and any implementation in combination with the above-mentioned first aspect. method.
  • the present application provides a computer program product containing instructions that, when executed by a cluster of computer equipment, cause the cluster of computer equipment to execute the above-mentioned first aspect and the method combined with any one of the implementations of the above-mentioned first aspect. .
  • the present application provides a computer-readable storage medium, including computer program instructions.
  • the computer program instructions When the computer program instructions are executed by a computing device cluster, the computing device cluster performs the above first aspect and any one of the above first aspects. A method of implementation.
  • Figure 1 is a schematic scenario diagram of a cloud management platform based on the public network bandwidth of public cloud services provided by an embodiment of the present invention
  • Figure 2 is a schematic architectural diagram of a cloud management platform based on public network bandwidth of public cloud services provided by an embodiment of the present invention
  • Figure 3 is a simple flow chart of a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention
  • Figure 4 is a schematic flow chart of a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention
  • Figure 5 is another schematic flow chart of a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention.
  • Figure 6 is another schematic flow chart of a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention.
  • Figure 7 is a schematic structural diagram of a computing device for a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention.
  • Figure 8 is a schematic structural diagram of a computing device cluster based on a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention
  • Figure 9 is another structural schematic diagram of a computing device cluster based on a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention.
  • Figure 10 is another structural schematic diagram of a computing device cluster based on a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention.
  • an embodiment means that a particular feature, structure or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application.
  • the appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those skilled in the art explicitly and implicitly It is understood that the embodiments described herein may be combined with other embodiments.
  • Cloud data center A data center that provides public cloud services, also known as infrastructure.
  • the infrastructure includes multiple cloud data centers.
  • Each cloud data center includes multiple servers.
  • Each server can provide computing, network, and storage resources. .
  • IaaS Infrastructure as a Service
  • users do not need to build a physical data center themselves, but use infrastructure that provides computing, storage, network and other services through leasing.
  • Public cloud services of different tenants are isolated from each other.
  • Tenant A user who rents infrastructure. Tenants can register an account with a public cloud service provider through a browser or other client.
  • the public cloud service provider will record the accounts of different tenants, and realize the isolation of public cloud services of different tenants based on the account. , in the embodiment of the present invention.
  • Cloud management platform A platform provided by the public cloud service provider for interaction with users. Users can register an account on the cloud management platform and rent public cloud services with the account, thereby becoming a tenant of the public cloud service.
  • the cloud management platform is also used for management infrastructure, and achieve isolation between computing, network, and/or storage resources rented by different tenants based on the accounts of different tenants.
  • Cloud instance refers to an instance deployed on a cloud data center in an availability zone in a region for running public cloud services.
  • the cloud instance is used to provide computing, network, or storage resources.
  • Cloud instances include but do not Limited to, for example, elastic cloud servers (ECS), containers, bare metal servers (BMS), object storage service (OBS) buckets, elastic load balancers (ELB), Services such as Network Address Translation Gateway (NAT Gateway) and cloud cache, among which ECS, for example, can be implemented through virtual machines.
  • ECS elastic cloud servers
  • BMS bare metal servers
  • OBS object storage service
  • ELB elastic load balancers
  • Services such as Network Address Translation Gateway (NAT Gateway) and cloud cache, among which ECS, for example, can be implemented through virtual machines.
  • NAT Gateway Network Address Translation Gateway
  • Elastic IP an IP address provided by the cloud service provider to the tenant that can directly access the Internet.
  • the tenant can specify the cloud instance to be bound to the tenant's EIP in the cloud management platform.
  • the cloud instance and After the EIP is bound clients in the cloud can access the cloud instance through the EIP.
  • Region Public cloud service providers set up public cloud data centers in regions located in different geographical locations. Public cloud devices in public cloud data centers in different regions need to communicate through remote connection gateways.
  • Availability Zone A collection of one or more cloud data centers with independent water and electricity. Computing, network, storage and other resources are logically divided into multiple clusters within the Availability Zone. Multiple availability zones in a region are connected through high-speed optical fibers to meet users' needs for building high-availability systems across AZs.
  • Public network bandwidth refers to the amount of data that can be transmitted per unit time between a cloud instance set up in a cloud data center and the public network (i.e., the Internet). Public network bandwidth includes uplink public network bandwidth and downlink public network bandwidth. Uplink public network bandwidth Network bandwidth refers to the outbound bandwidth of a cloud instance, the direction in which traffic flows out of the cloud server to the public network. Downstream public network bandwidth refers to the bandwidth in the direction of traffic flowing from the public network into the cloud server.
  • the download traffic involved is the downstream public network bandwidth, which is also the bandwidth in the direction of traffic flowing from the public network to the cloud instance.
  • the tenant logs in to the cloud instance and deploys a web page in the cloud instance so that clients in the public network can access the web page.
  • the access traffic involved in the client accessing the web page in the cloud instance is the uplink public network bandwidth.
  • cloud service providers charge for the uplink public network bandwidth of cloud instances and charge for the downlink public network bandwidth. No charge.
  • the “bandwidth” involved preferably refers to the uplink public network bandwidth.
  • “bandwidth” may also be the downlink public network bandwidth, which is not limited in the embodiments of the present invention.
  • public network bandwidth is usually provided to tenants in the form of bandwidth packages, and the bandwidth package is bound to the elastic public IP of the tenant's cloud instance.
  • the cloud instance involves The upstream data access traffic will be limited by the amount of data that can be transmitted per unit time limited by the bandwidth package, that is, the upstream data access traffic cannot exceed the amount of data that can be transmitted per unit time limited by the bandwidth package. If it exceeds, the cloud instance network will be managed by The bandwidth allocation device, network card, or cloud instance manager drops excess packets.
  • FIG. 1 is a schematic system structure diagram of a public cloud service system provided by an embodiment of the present invention.
  • the cloud management platform 20 is used to manage the infrastructure 1.
  • the infrastructure 1 includes cloud data center clusters set up in multiple areas.
  • the exemplary multiple areas include area 10, area 11, and area 12.
  • Each area A cloud data center cluster (not shown) is provided.
  • Each cloud data center includes multiple cloud data centers.
  • the exemplary cloud data center in area 10 includes cloud data center 101, cloud data center 102, and cloud data center 103.
  • the cloud data center cluster located in area 11 includes cloud data center 111, cloud data center 112, and cloud data center 113.
  • the cloud data center cluster located in area 13 includes cloud data center 121, cloud data center 122, and cloud data center 123.
  • Each Each cloud data center contains multiple servers.
  • the exemplary data center 101 includes servers 1011, servers 1012...
  • the cloud management platform 20 is used to manage the network infrastructure 1.
  • Tenant A connects to the Internet through the client 21 and logs in with an account bound to tenant A that is pre-registered on the cloud management platform 20.
  • tenant B connects to the Internet through the client 22 and logs in to the cloud management platform 20 with the account bound to tenant B registered in advance on the cloud management platform 20.
  • the cloud management platform 20 provides a configuration interface, and tenant A uses the client 21 to log in to the cloud management platform 20. Access the configuration interface and enter configuration information 1 on the configuration interface.
  • Tenant B accesses the configuration interface through client 22 and enters configuration information 2 on the configuration interface.
  • Cloud management platform 20 obtains configuration information 1 from the configuration interface. According to configuration information 1
  • the cloud management platform 20 obtains the configuration information 2 from the configuration interface, and configures and/or manages the cloud service of tenant B according to the configuration information 2.
  • each cloud data center can be identified by an availability zone (Availability Zone, AZ).
  • Availability Zone AZ
  • Different availability zones correspond to different cloud data centers, and the cloud data center can be set up in one or more computer rooms.
  • the client 21 and the client 22 may be terminal devices such as mobile phones with Internet access functions, personal computers, personal digital assistants, thin clients, vehicle-mounted hosts, or other terminal devices with Internet access functions.
  • Figure 2 is a schematic structural diagram of another public cloud service system provided by an embodiment of the present invention. Specifically, Figure 2 shows the specific structure of the cloud data center in the system shown in Figure 1.
  • the cloud data center 101 includes multiple servers 1011, 1012..., the multiple servers 1011, 1012 are respectively connected to the bandwidth allocation device 1010, where the server 1011 includes a hardware layer and a software layer, and the cloud instance 10111 is set on the server On the software layer of 1011, the software layer of server 1011 also includes the host operating system 10113.
  • the cloud instance manager 101131 is set on the host operating system 10113.
  • the cloud instance manager 101131 is also provided with a cloud management platform client 1011311.
  • the instance manager 101131 is used to manage the cloud instance 10111.
  • the cloud instance manager 101131 communicates with the cloud management platform 20 through the cloud management platform client 1011311.
  • the server hardware layer of server 1011 includes memory 10114, processor 10115, network card 10116, and hard disk 10117.
  • the network card 10116 is connected to the bandwidth allocation device 1010 in the cloud data center.
  • the cloud instance 10111 is connected to the Internet through the network card 10116.
  • the network report of the cloud instance 10111 Messages (including outgoing messages and incoming messages) communicate with devices on the Internet via the bandwidth allocation device 1010.
  • the bandwidth allocation device 1010 can control allocation to predetermined cloud instances (such as cloud instances) according to commands sent by the cloud management platform 20.
  • the outgoing packets of the cloud instance 10111 can be sent to the device connected to the Internet under the premise of meeting the rate of the available bandwidth, and the incoming packets can be sent from the Internet under the premise of meeting the rate of the available bandwidth.
  • the device sends it to cloud instance 10111, so the rate of network packets from cloud instance 10111 cannot exceed the limit of the available bandwidth.
  • the bandwidth allocation device can be implemented through a router, server, virtual machine or other network node commonly used in the art with bandwidth allocation function.
  • the bandwidth allocation device can allocate the available bandwidth purchased by the cloud service provider from the operator to servers in the cloud data center as needed.
  • this application provides a public network bandwidth allocation method and cloud management platform based on public cloud services.
  • This method is applied to the cloud management platform and obtains the bidding bandwidth for the elastic public IP of the tenant input by the tenant.
  • the cloud management platform queries the cloud data center where the cloud instance bound to the elastic public network IP is located for free bandwidth, provides the tenant's cloud instance with idle bandwidth that matches the bidding bandwidth, and uses the free bandwidth of the cloud instance based on the bidding quotation. Bandwidth is billed.
  • the cloud management platform provides an expression interface to tenants, and tenants input bidding information (such as bidding bandwidth, bidding quotation, and elastic public IP) into the expression interface.
  • the cloud management platform uses the bidding information to maximize the Utilize the idle bandwidth of the data center to improve bandwidth utilization.
  • the cloud management platform obtains the bidding bandwidth and bidding quotations of other cloud instances configured in the same cloud data center entered by other tenants, and if the bidding quotations of other tenants are higher than the bidding quotations of the previous tenant, it is determined to stop.
  • the cloud management platform obtains the bidding bandwidth and bidding quotations of other cloud instances configured in the same cloud data center entered by other tenants, and if the bidding quotations of other tenants are higher than the bidding quotations of the previous tenant, it is determined to stop.
  • Figure 3 is a flow chart of a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention. As shown in Figure 3, the method includes but is not limited to the following steps:
  • S301 The cloud management platform provides tenants with a bandwidth configuration interface.
  • the bandwidth configuration interface is used to obtain the bidding bandwidth and bidding quotations input by different tenants.
  • the cloud management platform provides a bandwidth configuration interface for tenants to receive the bidding bandwidth and bidding quotation applied to the EIP purchased by the tenant on the cloud management platform that different tenants log in to the cloud management platform and input in the bandwidth configuration interface.
  • the bidding bandwidth is for the The available public network bandwidth of the EIP. This bidding quotation is used to indicate the billing price that the tenant wants when the cloud instance bound to the EIP uses the bidding bandwidth to communicate with devices on the Internet.
  • the tenant sets the cloud instance on the target cloud data center. Bind to EIP to obtain the ability to access the Internet.
  • the cloud management platform determines the target cloud data center from the multiple cloud data centers shown in Figure 1.
  • the specific details can be based on The region and availability zone corresponding to the cloud instance bound to the EIP determine the target cloud data center.
  • the cloud management platform will set the cloud instance in the target cloud data center based on the region and availability zone selected by the tenant, and the above
  • the number of cloud instances can be one or multiple, and one or more cloud instances of the same tenant are set in the same target cloud data center.
  • the bandwidth configuration interface is also used to obtain the user level of the tenant and the basic bandwidth applied to the EIP.
  • the user level is used to indicate the user level of the tenant's use of the public cloud infrastructure.
  • the cloud management platform can use the same bidding quotation to obtain the user level of the tenant. Prioritize idle bandwidth to tenants with higher user levels.
  • the basic bandwidth is the guaranteed bandwidth provided to the cloud instance bound to the EIP.
  • the basic bandwidth is not affected by other tenants' bidding quotations.
  • the basic bandwidth can ensure that the cloud instance has a stable guaranteed bandwidth.
  • bandwidth configuration interface provided by the cloud management platform is specifically implemented as either a configuration interface or an application program interface (Application Program Interface, API).
  • the cloud management platform determines the target cloud data center to which the cloud instance configured by the tenant belongs based on the EIP.
  • the cloud management platform queries the target cloud data center for the total idle bandwidth, and if it determines that there is sufficient bandwidth to satisfy the bidding, it provides the tenant with idle bandwidth.
  • the cloud management platform 20 can send a control command to the bandwidth allocation device shown in Figure 2.
  • the bandwidth allocation device queries the target cloud data center based on the control command whether there is any idle bandwidth due to bidding bandwidth matching. Bandwidth, if so, allocate the idle bandwidth to the tenant's cloud instance running in the target server in the target cloud data center, so that the packets that the cloud instance communicates with the Internet device can use the idle bandwidth, and the cloud management platform uses The bidding price is used to charge for the idle bandwidth used by the cloud instance.
  • the cloud management platform 20 confirms that the cloud data center 101 in Figure 2 is the target cloud data center, the cloud instance 10111 is the cloud instance bound to the tenant's EIP, and the cloud instance 10111 runs in the server 1011 of the cloud data center 101. Then the cloud management platform 20 sends a control command to the bandwidth allocation device 1010.
  • the bandwidth allocation device 1010 queries the target cloud data center 101 according to the control command whether there is idle bandwidth that matches the bidding bandwidth. If so, allocates the idle bandwidth to The tenant runs the cloud instance 10111 in the target server 1011 in the target cloud data center 101, so that the messages that the cloud instance 10111 communicates with the Internet device can use the idle bandwidth, and the cloud management platform 20 bids the cloud instance 10111 at the bidding price.
  • the idle bandwidth used is billed.
  • bandwidth allocation device in other embodiments of the present invention, there is no need to set up a dedicated bandwidth allocation device in the cloud data center, and the functions of the bandwidth allocation device in each cloud data center can be distributed in each cloud data center.
  • the bandwidth allocation function is implemented through a distributed network card or a virtual network card provided by the cloud instance manager. In this case, each network card (or virtual network card) communicates with each other. Implement bandwidth allocation.
  • Figure 4 is a data interaction diagram of a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention.
  • Figure 4 further introduces the technical solution for competing for idle bandwidth between different tenants on the basis of Figure 3.
  • the method includes the following steps:
  • Step S101 The cloud management platform 20 provides a bandwidth configuration interface.
  • the cloud management platform 20 provides a bandwidth configuration interface through which the cloud management platform can obtain tenants from the client 21 Configuration information for cloud instance 10111 (see Figure 2 for details) input by A (see Figure 1 for details). Moreover, the related functions of the bandwidth configuration interface can be found in the above-mentioned Figure 3 and its corresponding description.
  • Step S102 The client 21 sends the bidding bandwidth and bidding quotation applied to the EIP of tenant A to the cloud management platform 20.
  • Tenant A logs into the cloud management platform 20 through the client 21, and enters the bidding bandwidth and bidding quotation for the available public network bandwidth of its EIP in the bandwidth configuration interface provided by the cloud management platform 20.
  • the bidding bandwidth is not included in the bandwidth that tenant A has purchased and used. The additional available public network bandwidth among the basic bandwidth.
  • Step S103 the cloud management platform 20 obtains the bidding bandwidth and bidding price for the EIP input by tenant A through the bandwidth configuration interface, and determines the target cloud data center.
  • the cloud management platform 20 obtains the bidding bandwidth and bidding quotation for the EIP entered by tenant A through the bandwidth configuration interface. According to the region and availability zone where the cloud instance 10111 bound to the EIP is located, the cloud management platform obtains the bidding bandwidth from multiple clouds. Among the data centers, select cloud data center 101 as the target cloud data center.
  • the cloud management platform 20 prompts tenant A about the total idle bandwidth that exists in the cloud data center 101 where the cloud instance 10111 is located, so that tenant A has a clear understanding of the total idle bandwidth of the target cloud data center and facilitates the tenant to determine the data center. Whether there is enough free bandwidth for cloud instance 10111 to use.
  • Step S104 The cloud management platform 20 sends a control command to the bandwidth allocation device 1010 of the target cloud data center.
  • the cloud management platform 20 sends a message containing a control command to the bandwidth allocation device 1010 of the cloud data center 101 based on the bidding bandwidth and bidding quotation of tenant A obtained in step S103.
  • Step S105 The bandwidth allocation device 1010 determines that the first idle bandwidth needs to be provided to the server 1011 according to the control command.
  • the bandwidth allocation device 1010 determines the first idle bandwidth required by the server 1011 according to the control command sent by the cloud management platform 20 .
  • Step S106 The bandwidth allocation device 1010 provides the first idle bandwidth to the server 1011.
  • the bandwidth allocation device 1010 After receiving the control command message sent by the cloud management platform 20 and determining the idle bandwidth required by the server 1011, the bandwidth allocation device 1010 provides the idle bandwidth to the server 1011.
  • Step S107 The server 1011 provides the first idle bandwidth to the cloud instance of tenant A.
  • the server 1011 After receiving the first idle bandwidth provided to the cloud instance 10111 of tenant A sent by the bandwidth allocation device 1010, the server 1011 provides the first idle bandwidth to the cloud instance 10111 of tenant A running in its software layer.
  • the network card 10116 of the hardware layer of the server 1011 exchanges information with the network cards of other servers, and sends the information to tenant A running on the software layer.
  • Cloud instance 10111 provides the first free bandwidth.
  • Step S108 The server 1011 feeds back a configuration success message to the bandwidth allocation device 1010.
  • the server 1011 forwards the first idle bandwidth to the cloud instance 10111 running therein, the server 1011 feeds back a configuration success message to the bandwidth allocation device 1010.
  • Step S109 The bandwidth allocation device 1010 feeds back a configuration success message to the cloud management platform 20.
  • the bandwidth allocation device 1010 After receiving the configuration success message sent by the server 1011, the bandwidth allocation device 1010 sends a feedback configuration success message to the cloud management platform 20.
  • Step S110 the cloud management platform 20 prompts tenant A that the allocation is successful, and determines the fee based on tenant A's bidding quotation.
  • the cloud management platform 20 after receiving the successful configuration message sent by the bandwidth allocation device 1010, the cloud management platform 20 sends the message to the client 21 to prompt tenant A to successfully allocate the bidding bandwidth, and determine the tenant according to tenant A's bidding quotation. Bandwidth charges incurred by A's cloud instance using idle bandwidth in the target cloud data center.
  • the price of the bidding quotation is greater than the cost price of the bandwidth provided by the public cloud service provider, and is less than the on-demand billing price of the available bandwidth.
  • the charges incurred by the tenant's cloud instance for using idle bandwidth in the target cloud data center are determined based on the tenant's bidding quotation, while the charges incurred by the tenant's cloud instance's basic bandwidth can be determined based on the on-demand billing price or the prepaid price.
  • the embodiment of the present invention does not limit this.
  • the cloud management platform 20 starts billing after the tenant successfully matches the idle bandwidth, and ends when the cloud management platform 20 stops providing idle bandwidth to the tenant.
  • the cloud management platform 20 is set with a refresh time for detecting whether the cloud management platform 20 stops providing idle bandwidth to tenants.
  • Tenant A's bidding price is 1 yuan/min or 5 yuan/h.
  • the cloud management platform 20 provides free bandwidth to tenant A's cloud instance set in the target cloud data center, and notifies tenant A that the bidding is successful, and starts Billing.
  • the cloud management platform 20 is set to have a refresh time of 5 seconds, and detects whether the idle bandwidth provided to tenant A has stopped every 5 seconds.
  • the cloud management platform 20 detects that the idle bandwidth provided to tenant A has stopped, and the bandwidth fee incurred is determined by the bidding quotation and the total duration of the idle bandwidth used.
  • the cloud management platform 20 follows the above steps to provide idle bandwidth to the tenant who first puts forward the bidding request.
  • the idle bandwidth of the target cloud data center is provided to the cloud instance, which improves the overall bandwidth utilization.
  • embodiments of the present invention further disclose the specific situation of idle bandwidth allocation when two tenants participate in bidding. See below:
  • Figure 5 is another schematic flow chart of a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention. As shown in Figure 5, the method includes but is not limited to the following steps:
  • steps S101 to S110 the cloud management platform has provided the first idle bandwidth to the cloud instance 10111 configured by tenant A in the cloud data center 101.
  • the cloud management platform has provided the first idle bandwidth to the cloud instance 10111 configured by tenant A in the cloud data center 101. For details, see Figure 4 and will not be described again.
  • step S111 the client 22 sends the bidding bandwidth and bidding quotation applied to tenant B's EIP to the cloud management platform 20.
  • Tenant B logs into the cloud management platform 20 through the client 22 , and enters the bidding bandwidth and bidding quotation for the available public network bandwidth of its EIP in the bandwidth configuration interface provided by the cloud management platform 20 .
  • Step S112 the cloud management platform 20 obtains the bidding bandwidth and bidding price for the EIP input by tenant B through the bandwidth configuration interface, and determines the target cloud data center 101 .
  • the cloud management platform 20 obtains the bidding bandwidth and bidding quotation for the EIP input by tenant B through the bandwidth configuration interface.
  • the cloud management platform obtains the bidding bandwidth from multiple clouds.
  • Step S113 The cloud management platform 20 sends an idle bandwidth query message to the bandwidth allocation device 1010.
  • the cloud management platform 20 determines that the cloud instance 10112 of tenant B is set in the target cloud data center 101, the cloud management platform 20 queries the bandwidth allocation device 1010 for idle bandwidth to determine whether there is remaining idle that matches tenant B's bidding bandwidth. bandwidth.
  • Step S114 The bandwidth allocation device 1010 queries the remaining idle bandwidth information of the target cloud data center.
  • Step S115 The bandwidth allocation device 1010 sends idle bandwidth information to the cloud management platform 20.
  • Step S116 The cloud management platform 20 determines that there is remaining idle bandwidth that matches tenant B's bidding bandwidth.
  • the cloud management platform 20 makes a judgment based on the remaining idle bandwidth information of the cloud data center 101 sent by the bandwidth allocation device 1010 and the bidding bandwidth of tenant B, and determines that there is remaining idle bandwidth in the cloud data center 101 that matches the bidding bandwidth of tenant B. Free bandwidth.
  • Step S117 The cloud management platform 20 determines to provide the second idle bandwidth to the cloud instance of tenant B.
  • Step S118 The cloud management platform 20 sends a control command to the bandwidth allocation device 1010 of the target cloud data center.
  • the cloud management platform 20 sends a message containing a control command to the bandwidth allocation device 1010 of the cloud data center 101 based on providing the second idle bandwidth to the cloud instance of tenant B determined in step S117.
  • Step S119 The bandwidth allocation device 1010 determines that the second idle bandwidth needs to be provided to the server 1011 according to the control command.
  • Step S120 The bandwidth allocation device 1010 provides the second idle bandwidth to the server 1011.
  • the bandwidth allocation device 1010 After receiving the control command message sent by the cloud management platform 20 and determining the idle bandwidth required by the server 1011, the bandwidth allocation device 1010 provides the second idle bandwidth to the server 1011.
  • step S121 the server 1011 provides the second idle bandwidth to the cloud instance of tenant B.
  • the server 1011 After receiving the second idle bandwidth provided to the cloud instance 10112 of tenant B sent by the bandwidth allocation device 1010, the server 1011 provides the second idle bandwidth to the cloud instance 10112 of tenant A running in its software layer.
  • Step S122 The server 1011 feeds back a configuration success message to the bandwidth allocation device 1010.
  • Step S123 The bandwidth allocation device 1010 feeds back a configuration success message to the cloud management platform 20.
  • Step S124 the cloud management platform 20 prompts tenant B that the allocation is successful, and determines the fee based on tenant B's bidding quotation.
  • the cloud management platform 20 after receiving the successful configuration message sent by the bandwidth allocation device 1010, the cloud management platform 20 sends the message to the client 21 to prompt tenant B to successfully allocate the bidding bandwidth, and determine the tenant based on tenant B's bidding quotation. Bandwidth charges incurred by B's cloud instance using idle bandwidth in the target cloud data center.
  • Embodiments of the present invention disclose that after the first idle bandwidth is provided to tenant A's cloud instance configured in the target cloud data center, and the target cloud data center has remaining idle bandwidth that matches the bidding bandwidth of tenant B, the target cloud data center provides tenant B with the first idle bandwidth.
  • the cloud instance configured in the target cloud data center provides the second idle bandwidth, which enables multiple users to utilize the idle bandwidth and further improves bandwidth usage efficiency.
  • the cloud management platform 20 continues to provide the first idle bandwidth to the cloud instance set by tenant A in the target cloud data center.
  • the cloud management platform 20 needs to determine whether to continue to provide all or part of the first idle bandwidth to tenant A's cloud instance based on tenant B's bid bandwidth.
  • Figure 6 is another schematic flow chart of a public network bandwidth allocation method based on public cloud services provided by an embodiment of the present invention. As shown in Figure 6, the method includes but is not limited to the following steps:
  • Steps 101-115 are all shown in Figure 4 and Figure 5.
  • the target cloud data center 101 does not have bidding bandwidth that matches the bidding bandwidth of tenant B. Based on this:
  • Step S116 ⁇ the cloud management platform 20 determines the remaining idle bandwidth of the target cloud data center and the bidding bandwidth of tenant B. Mismatch.
  • the cloud management platform 20 makes a judgment based on the remaining idle bandwidth information of the cloud data center 101 sent by the bandwidth allocation device 1010 and the bidding bandwidth of tenant B, and determines that the remaining idle bandwidth of the cloud data center 101 is different from the bidding bandwidth of tenant B. match.
  • the cloud management platform 20 determines whether to continue to provide all or part of the first idle bandwidth to the cloud instance configured by tenant A in the target cloud data center based on the bidding bandwidth and bidding quotation of tenant B obtained through the bandwidth configuration interface. bandwidth.
  • Step S117 ⁇ the cloud management platform 20 determines that the bidding price of tenant B is greater than the bidding price of tenant A.
  • Step S118 ⁇ the cloud management platform 20 determines that the bidding bandwidth of tenant B is greater than or equal to the bidding bandwidth of tenant A.
  • the cloud management platform 20 determines to stop providing all first idle bandwidth to the cloud instance of tenant A based on the fact that the bidding bandwidth of tenant B is greater than or equal to the bidding bandwidth of tenant A and the bidding quotation of tenant B is greater than the bidding quotation of tenant A.
  • Tenant B's cloud instance provides the first idle bandwidth.
  • Step S119 ⁇ the cloud management platform 20 sends a control command to the bandwidth allocation device 1010 of the target cloud data center.
  • the cloud management platform 20 determines in step S118′ to stop providing all the first idle bandwidth to the cloud instance of tenant A and to provide the first idle bandwidth to the cloud instance of tenant B, and sends the control to the bandwidth allocation device 1010 of the cloud data center 101. command message.
  • Step S120 ⁇ the bandwidth allocation device 1010 stops providing the allocated first idle bandwidth to the server 1011 according to the control command.
  • the bandwidth allocation device 1010 stops providing the allocated first idle bandwidth to the server 1011.
  • Step S121 ⁇ the bandwidth allocation device 1010 stops providing the first idle bandwidth to the server 1011.
  • the bandwidth allocation device 1010 sends a message to the server 1011 to stop providing the first idle bandwidth to tenant A.
  • Step S122 ⁇ the server 1011 stops providing the first idle bandwidth to the cloud instance of tenant A.
  • the server 1011 After receiving the message to stop providing the first idle bandwidth, the server 1011 stops providing the first idle bandwidth to the cloud instance 10111 of tenant A running in it.
  • Step S123 ⁇ the server 1011 feeds back the stop configuration message to the bandwidth allocation device 1010.
  • Step S124 ⁇ the bandwidth allocation device 1010 feeds back the stop configuration message to the cloud management platform 20.
  • Step S125 ⁇ the cloud management platform 20 provides the first idle bandwidth to tenant B.
  • the cloud management platform 20 provides the first idle bandwidth that has stopped being provided to tenant A to tenant B.
  • Step S126 ⁇ the cloud management platform 20 sends a control command to the bandwidth allocation device 1010 of the target cloud data center.
  • the cloud management platform 20 determines to provide the first idle bandwidth to the cloud instance of tenant B, and sends a message containing the control command to the bandwidth allocation device 1010 of the cloud data center 101.
  • step S127' the bandwidth allocation device 1010 determines that the first idle bandwidth needs to be provided to the server 1011 according to the control command.
  • Step S128 ⁇ the bandwidth allocation device 1010 provides the second idle bandwidth to the server 1011.
  • the bandwidth allocation device 1010 After receiving the control command message sent by the cloud management platform 20 and determining the idle bandwidth required by the server 1011, the bandwidth allocation device 1010 provides the first idle bandwidth to the server 1011.
  • Step S129 ⁇ the server 1011 provides the second idle bandwidth to the cloud instance of tenant B. .
  • the server 1011 After receiving the first idle bandwidth provided to the cloud instance 10112 of tenant B sent by the bandwidth allocation device 1010, the server 1011 provides the first idle bandwidth to the cloud instance 10112 of tenant A running in its software layer.
  • Step S130 ⁇ the server 1011 feeds back a configuration success message to the bandwidth allocation device 1010.
  • Step S131 ⁇ the bandwidth allocation device 1010 feeds back a configuration success message to the cloud management platform 20.
  • Step S132 ⁇ the cloud management platform 20 prompts tenant B that the allocation is successful, and determines the fee based on tenant B's bidding quotation.
  • the cloud management platform 20 after receiving the successful configuration message sent by the bandwidth allocation device 1010, the cloud management platform 20 sends the message to the client 21 to prompt tenant B to successfully allocate the bidding bandwidth, and determine the tenant based on tenant B's bidding quotation. Bandwidth charges incurred by B's cloud instance using idle bandwidth in the target cloud data center.
  • Step 133 ⁇ the cloud management platform 20 prompts tenant A to stop providing the first idle bandwidth and charges the bandwidth fee to tenant A.
  • the cloud management platform 20 After receiving the configuration success message sent by the bandwidth allocation device 1010, the cloud management platform 20 sends a message to the client 21, prompting tenant A to stop providing the first idle bandwidth, and charges tenant A for the used bandwidth. cost of
  • the above embodiment discloses that when it is determined that there is no remaining idle bandwidth in the cloud data center 101 that matches the bidding bandwidth of tenant B, and the bidding quotation of tenant B is higher than the bidding quotation of tenant A, and the bidding bandwidth of tenant B is greater than or equal to tenant A,
  • the public network bandwidth allocation method is based on public cloud services.
  • the bidding quotation of tenant B is higher than the bidding quotation of tenant A.
  • the bidding bandwidth of B is smaller than the bidding bandwidth of tenant A.
  • the cloud management platform 20 determines that the remaining idle bandwidth of the cloud data center 101 does not match tenant B's bidding bandwidth, and tenant B's bidding quotation is higher than tenant A's bidding quotation, and tenant B's bidding bandwidth is smaller than tenant A's bidding bandwidth.
  • the cloud management platform 20 sends a control command to the bandwidth allocation device 1010 of the cloud data center 101, and the bandwidth allocation device 1010 stops providing part of the first idle bandwidth to the server 1011, and sends a message to stop providing part of the first idle bandwidth to the server 1011. , after receiving the message, the server 1011 stops providing part of the first idle bandwidth to the cloud instance 10111 running in it.
  • the server 1011 feeds back the configuration stop message to the bandwidth allocation device 1010, and the bandwidth allocation device 1010 feeds back the configuration stop message to the cloud management platform 20.
  • the cloud management platform 20 After receiving the configuration stop message, the cloud management platform 20 provides a portion of the first idle bandwidth to tenant B, and sends a control command to the bandwidth allocation device 1010 of the cloud data center 101 .
  • the bandwidth allocation device 1010 determines that part of the first idle bandwidth needs to be provided to the server 1011 according to the control command, and sends the partial bidding bandwidth package message to the server 1011.
  • the server 1011 provides part of the first idle bandwidth to the cloud instance 10112 of tenant B.
  • the server 1011 feeds back a configuration success message to the bandwidth allocation device 1010.
  • the bandwidth allocation device 1010 After receiving the message, the bandwidth allocation device 1010 feeds back a configuration success message to the cloud management platform 20.
  • the cloud management platform 20 prompts tenant B that the bandwidth bidding is successful, and prompts tenant A to stop providing part of the first idle bandwidth to tenant
  • the cloud management platform 20 determines that there is no remaining idle bandwidth in the cloud data center 101 that matches the bidding bandwidth of tenant B, and the bidding quotation of tenant B is lower than the bidding quotation of tenant A, the cloud management platform 20 prompts tenant B that the bidding has failed. .
  • the existence cloud management platform 20 determines that the user level of tenant B is high. Based on the user level of tenant A, the bidding bandwidth of tenant B is greater than or equal to the bidding bandwidth of tenant A.
  • the cloud management platform 20 determines that the remaining idle bandwidth of the cloud data center 101 does not match the bid bandwidth of tenant B.
  • the bidding quotation of tenant B is equal to the bidding quotation of tenant A. It is also determined that the user level of tenant B is higher than the user level of tenant A.
  • the bidding bandwidth of tenant B is greater than or equal to the bidding bandwidth of tenant A.
  • the cloud management platform 20 sends a control command to the bandwidth allocation device 1010 of the cloud data center 101, and the bandwidth allocation device 1010 stops providing the first idle bandwidth to the server 1011, and sends a message to stop providing the first idle bandwidth to the server 1011.
  • the server After receiving the message, 1011 stops providing the first idle bandwidth to the cloud instance 10111 running in it.
  • the server 1011 feeds back the configuration stop message to the bandwidth allocation device 1010, and the bandwidth allocation device 1010 feeds back the configuration stop message to the cloud management platform 20.
  • the cloud management platform 20 After receiving the stop configuration message, the cloud management platform 20 provides the first idle bandwidth to tenant B, and sends the control command to the bandwidth allocation device 1010 of the cloud data center 101.
  • the bandwidth allocation device 1010 determines that the first idle bandwidth needs to be provided to the server 1011 according to the control command, and sends the partial idle bandwidth provision message to the server 1011.
  • the server 1011 provides the first idle bandwidth to the cloud instance 10112 of tenant B. After the configuration is successful, the server 1011 feeds back a configuration success message to the bandwidth allocation device 1010. After receiving the message, the bandwidth allocation device 1010 feeds back a configuration success message to the cloud management platform 20.
  • the cloud management platform 20 prompts tenant B that the bandwidth bidding is successful, and prompts tenant A to stop providing the first idle bandwidth to tenant A.
  • the existence cloud management platform 20 determines the user level of tenant B.
  • the user level is higher than that of tenant A, and the bidding bandwidth of tenant B is smaller than the bidding bandwidth of tenant A.
  • the cloud management platform 20 determines that the remaining idle bandwidth of the cloud data center 101 does not match the bidding bandwidth of tenant B.
  • the bidding quotation of tenant B is equal to the bidding quotation of tenant A. It is also determined that the user level of tenant B is higher than the user level of tenant A. Tenant B B's bidding bandwidth is smaller than tenant A's bidding bandwidth.
  • the cloud management platform 20 sends a control command to the bandwidth allocation device 1010 of the cloud data center 101, and the bandwidth allocation device 1010 stops providing part of the first idle bandwidth to the server 1011, and sends a message to stop providing part of the first idle bandwidth to the server 1011. , after receiving the message, the server 1011 stops providing part of the first idle bandwidth to the cloud instance 10111 running in it.
  • the server 1011 feeds back the configuration stop message to the bandwidth allocation device 1010, and the bandwidth allocation device 1010 feeds back the configuration stop message to the cloud management platform 20.
  • the cloud management platform 20 After receiving the configuration stop message, the cloud management platform 20 provides a portion of the first idle bandwidth to tenant B, and sends a control command to the bandwidth allocation device 1010 of the cloud data center 101 .
  • the bandwidth allocation device 1010 determines that it needs to provide part of the first idle bandwidth to the server 1011 according to the control command, and sends the partial idle bandwidth provision message to the server 1011.
  • the server 1011 provides part of the first idle bandwidth to the cloud instance 10112 of tenant B.
  • the server 1011 feeds back a configuration success message to the bandwidth allocation device 1010.
  • the bandwidth allocation device 1010 After receiving the message, the bandwidth allocation device 1010 feeds back a configuration success message to the cloud management platform 20.
  • the cloud management platform 20 prompts tenant B that the bandwidth bidding is successful, and prompts tenant A to stop providing part of the first idle bandwidth to tenant A
  • the management platform 20 determines that tenant B's user level is lower than tenant A's user level.
  • the cloud management platform 20 determines the user level of tenant B. If the user level is lower than that of tenant A, the cloud management platform 20 prompts tenant B that the bidding failed.
  • the cloud instance in the embodiment of the present invention can be a virtual machine, a container, a bare metal server, an object storage bucket, an ELB elastic load balancer, a NAT network address translation gateway, and a cloud cache, without limitation.
  • the cloud management platform 20 sets a preset time.
  • the preset time period may be a time period set by the tenant or a time period preset by the cloud management platform 20 .
  • the cloud management platform 20 provides free bandwidth to tenants within the above-mentioned preset time period. Width.
  • the time can also be preset through the cloud management platform, which is more conducive to the tenants' expectations for the time period for using the bidding bandwidth. .
  • the bandwidth configuration interface provided by the cloud management platform 20 is also used to obtain the region and availability zone to which the cloud data center belongs.
  • the cloud management platform 20 can obtain the EIP bound to the cloud instance set by the tenant on the cloud data center. Determine the region and availability zone where the cloud data center is located. By identifying the region and availability zone where the cloud data center is located, precise positioning at the hardware level can be achieved, further locating the server and bandwidth allocation equipment, and then allocating the bidding bandwidth and idle bandwidth by configuring the bandwidth allocation equipment and network card.
  • the cloud management platform 20 charges the idle bandwidth actually used by the tenant according to the tenant's bidding quotation, and the cloud management platform 20 sends prompt information to the tenant when the tenant's idle bandwidth usage ends.
  • This billing method is based on the tenant's bidding quotation and is calculated based on the length of time the tenant uses the idle bandwidth.
  • the cloud management platform calculates and collects it after the tenant finishes using the idle bandwidth. It does not conflict with the basic bandwidth fee and is passed Different charging nodes and calculation methods are distinguished to realize the management of idle bandwidth usage fees.
  • the bandwidth configuration interface provided by the cloud management platform 20 prompts the tenant to the total idle bandwidth in the cloud data center where the cloud instance bound to its EIP is located before obtaining the tenant's input of bidding bandwidth and bidding quotation. It allows tenants to intuitively and quickly understand the total idle bandwidth currently existing in the cloud data center where their cloud instances are located, so that they can use this information to match their bidding bandwidth requirements.
  • the bandwidth configuration interface provided by the cloud management platform 20 is also used to obtain the basic bandwidth of the available public network bandwidth of the EIP bound to the tenant cloud instance.
  • the cloud management platform 20 allocates idle bandwidth based on the bidding quotation, it does not assign the bandwidth to the tenant cloud.
  • the existing basic bandwidth of the instance is changed to ensure that the cloud instance is guaranteed to have basic bandwidth usage when the bidding fails.
  • the cloud management platform 20 sets the tenant's bidding price to be greater than the bandwidth cost price and less than the on-demand billing price.
  • the cloud management platform 20 records the status information of the tenant's actual use of idle bandwidth, and feeds the status information back to the tenant, so that the tenant can learn the usage status of its own idle bandwidth in a timely manner.
  • the above is the public network bandwidth allocation method based on public cloud services in the same cloud data center between two tenants based on the available public network bandwidth of the EIP bound to their respective cloud instances.
  • This application also provides a cloud management platform, taking Figure 2 as an example, including:
  • the bandwidth configuration interface providing module is used not only to provide a bandwidth configuration interface, but also to select the cloud data center 101 where Tenant A's cloud instance 10111 is located from multiple cloud data centers based on the region and availability zone obtained by the bandwidth configuration interface.
  • the bandwidth management module is configured to provide the idle bandwidth to the cloud instance 10111 of tenant A when it is determined that the cloud data center 101 has idle bandwidth that matches the bid bandwidth of tenant A.
  • the preset time period is a time period set by tenant A or a time period preset by the cloud management platform 20 .
  • the bandwidth accounting module is used to charge tenant A for the bandwidth fees generated by tenant A's cloud instance 10111 using the above-mentioned idle bandwidth to access the public network in the cloud data center 101.
  • the idle bandwidth prompt module obtains the information for tenant A entered by tenant A who logs in to the cloud management platform through the bandwidth configuration interface.
  • the bidding bandwidth of the available public network bandwidth of the EIP and the total idle bandwidth existing in the cloud data center 101 are prompted to tenant A before bidding.
  • the bandwidth notification module sends bandwidth status information to tenant A.
  • the bandwidth status information includes the actual bandwidth used by tenant A's cloud instance 10111.
  • tenant A in the above embodiment can be replaced by multiple other tenants.
  • a tenant can have multiple cloud instances in the same cloud data center.
  • the above modules can all implement corresponding technical functions. In this regard, the embodiment of the present invention Not limited.
  • the bandwidth configuration interface provision module, bandwidth management module, bandwidth accounting module, and idle bandwidth prompt module can all be implemented by software or can be implemented by hardware.
  • the following takes the bandwidth configuration interface providing module as an example to introduce the implementation method of the bandwidth configuration interface providing module.
  • the implementation of the bandwidth management module, bandwidth accounting module, and idle bandwidth prompt module can refer to the implementation of the bandwidth configuration interface module.
  • a module provides a bandwidth configuration interface module that 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, and a container.
  • the above computing instance may be one or more.
  • the bandwidth configuration interface provider module may include code running on multiple hosts/virtual machines/containers. It should be noted that multiple hosts/virtual machines/containers used to run this code can be distributed in the same region or in different regions. Furthermore, multiple hosts/virtual machines/containers used to run the code can be distributed in the same availability zone or in different availability zones. Each availability zone includes a data center or multiple geographically close locations. of data centers. Typically, a region can include multiple availability zones.
  • the module may include at least one computing device, such as a server, etc.
  • the bandwidth configuration interface providing module can also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD).
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL), or any combination thereof.
  • CPLD complex programmable logical device
  • FPGA field-programmable gate array
  • GAL general array logic
  • the bandwidth configuration interface providing module can be used to perform any steps in the public network bandwidth allocation method based on public cloud services, and the bandwidth management module can be used to perform public network bandwidth allocation based on public cloud services. Any step in the allocation method, the bandwidth accounting module can be used to execute any step in the public network bandwidth allocation method based on public cloud services, and the idle bandwidth prompt module can be used to execute any step in the public network bandwidth allocation method based on public cloud services. Any step.
  • the bandwidth notification module provides a module that can be used to perform any step in the public network bandwidth allocation method based on public cloud services.
  • the bandwidth configuration interface provides module, bandwidth management module, bandwidth billing module, idle bandwidth prompt module, and bandwidth notification module. The steps responsible for implementation can be specified as needed. Different steps in the public network bandwidth allocation method based on public cloud services are implemented through the bandwidth configuration interface provision module, bandwidth management module, bandwidth billing module, idle bandwidth prompt module, and bandwidth notification module. Realize all functions of the cloud management platform.
  • FIG. 7 is a schematic structural diagram of a computing device based on a public network bandwidth allocation method based on a public cloud service provided by an embodiment of the present invention.
  • Computing device 300 includes: bus 307, processor 308, memory 306, and communication interface 309. The processor 908, the memory 306 and the communication interface 309 communicate through the bus 307.
  • Computing device 300 may be a server or a terminal device. It should be understood that this application does not limit the computing device The number of processors and memories in the device 300.
  • the bus 307 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one line is used in Figure 7, but it does not mean that there is only one bus or one type of bus.
  • Bus 307 may include a path that carries information between various components of computing device 300 (eg, memory 306, processor 308, communications interface 309).
  • the processor 308 may include a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP) or a digital signal processor (DSP). any one or more of them.
  • CPU central processing unit
  • GPU graphics processing unit
  • MP microprocessor
  • DSP digital signal processor
  • Memory 306 may include volatile memory, such as random access memory (RAM).
  • the processor 308 may also include non-volatile memory (non-volatile memory), such as read-only memory (ROM), flash memory, mechanical hard disk drive (hard disk drive, HDD) or solid state drive (solid state drive). drive, SSD).
  • ROM read-only memory
  • HDD hard disk drive
  • SSD solid state drive
  • the memory 306 stores executable program code, and the processor 308 executes the executable program code to respectively implement the bandwidth configuration interface provision module 301, the bandwidth management module 302, the bandwidth accounting module 303, the idle bandwidth prompt module 304, and the bandwidth notification.
  • the function of module 305 is used to realize the public network bandwidth allocation method based on public cloud services. That is, the memory 306 stores instructions for the cloud management platform to execute the public network bandwidth allocation method based on public cloud services.
  • the communication interface 309 uses transceiver modules such as, but not limited to, network interface cards and transceivers to implement communication between the computing device 300 and other devices or communication networks.
  • An embodiment of the present application also provides a computing device cluster.
  • the computing device cluster includes at least one computing device.
  • the computing device may be a server, such as a central server, an edge server, or a local server in a local data center.
  • the computing device may also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.
  • Figure 8 is a schematic structural diagram of a computing device cluster based on the public network bandwidth allocation method based on public cloud services according to an embodiment of the present application.
  • the cluster of computing devices includes at least one computing device 300 .
  • the same cloud management platform may store instructions in the memory 306 of one or more computing devices 300 in the computing device cluster for executing the public network bandwidth allocation method based on public cloud services.
  • one or more computing devices 300 in the computing device cluster may also be used to execute part of the instructions of the cloud management platform for executing the public network bandwidth allocation method based on public cloud services.
  • a combination of one or more computing devices 300 can jointly execute the instructions of the cloud management platform for executing the public network bandwidth allocation method based on the public cloud service.
  • the memory 306 in different computing devices 300 in the computing device cluster can store different instructions for executing some functions of the cloud management platform. That is, the instructions stored in the memory 306 in different computing devices 300 can implement one or more of the bandwidth configuration interface provision module 301, the bandwidth management module 302, the bandwidth accounting module 303, the idle bandwidth prompt module 304, and the bandwidth notification module 305. function of a module.
  • Figure 9 is a schematic structural diagram of another computing device cluster based on the public network bandwidth allocation method based on public cloud services according to this embodiment of the present application.
  • two computing devices 300A and 300B are connected through a communication interface 309 .
  • the memory in the computing device 300A stores the bandwidth configuration interface providing module 301 and the bandwidth meter.
  • Stored on memory in computing device 300B are instructions for performing the functions of bandwidth management module 302 .
  • the memories 306 of the computing devices 300A and 300B jointly store instructions used by the cloud management platform to execute the public network bandwidth allocation method based on public cloud services.
  • connection method between computing device clusters shown in Figure 9 can be based on the fact that the public network bandwidth allocation method based on public cloud services provided by this application requires real-time calculation of idle bandwidth, and also requires multi-tenant bidding for idle bandwidth. It is necessary to calculate and allocate idle bandwidth.
  • the bandwidth management module 302 in order to avoid overloaded calculations on the computing device 300A, the functions implemented by the bandwidth management module 302 are handed over to the computing device 300B for execution.
  • computing device 300A shown in FIG. 9 may also be performed by multiple computing devices 300.
  • the functions of computing device 100B may also be performed by multiple computing devices 300 .
  • Figure 10 is a schematic structural diagram of another computing device cluster based on the public network bandwidth allocation method based on public cloud services according to the embodiment of the present application.
  • one or more computing devices in a cluster of computing devices may be connected through a network.
  • the network may be a wide area network or a local area network, etc.
  • Figure 10 shows a possible implementation.
  • two computing devices 300C and 300D are connected through a network.
  • the connection to the network is made through a communication interface in each computing device.
  • the memory 306 in the computing device 300C stores instructions for executing the functions of the bandwidth configuration interface provision module 301, the bandwidth accounting module 303, the idle bandwidth prompt module 304, and the bandwidth notification module 305. At the same time, instructions for performing the functions of the bandwidth management module 302 are stored in the memory 306 in the computing device 300D.
  • connection method between the computing device clusters shown in Figure 10 can be: Considering that the public network bandwidth allocation method based on public cloud services provided by this application requires real-time calculation of idle bandwidth, it needs to be allocated according to the bidding requirements of multi-tenants for idle bandwidth. Free bandwidth is allocated for calculation. Moreover, notification, billing, and prompting require network connection, and the execution of these functions is relatively independent. In order to optimize storage and computing performance, it is considered that the functions implemented by the bandwidth management module 302 are handed over to the computing device 300D for execution.
  • computing device 300C shown in FIG. 10 may also be performed by multiple computing devices 300.
  • the functions of computing device 300D may also be performed by multiple computing devices 300 .
  • the memory 306 of one or more computing devices 300 in the computing device cluster may also store part of the instructions for executing the public network bandwidth allocation method based on public cloud services.
  • a combination of one or more computing devices 300 may jointly execute instructions for performing a public network bandwidth allocation method based on a public cloud service.
  • An embodiment of the present 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 in any available medium.
  • the computer program product is run on at least one computer device, at least one computer device is caused to execute the above-mentioned method applied to a cloud management platform for executing public network bandwidth allocation based on public cloud services.
  • An embodiment of the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that a computing device can store or a data storage device such as a data center that contains one or more available media.
  • the available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media (eg, solid state drive), etc.
  • the computer-readable storage medium includes instructions, which instruct the computing device to execute the above-mentioned method applied to a cloud management platform for executing public network bandwidth allocation based on public cloud services.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente demande concerne un procédé d'attribution de largeur de bande de réseau public basé sur un service en nuage public et une plateforme de gestion en nuage. Le procédé comprend les étapes suivantes : une plateforme de gestion en nuage fournit une interface de configuration de largeur de bande, l'interface de configuration de largeur de bande étant utilisée pour acquérir une largeur de bande d'enchère et une cotation d'enchère pour une largeur de bande de réseau public disponible d'une adresse IP de réseau public élastique d'un locataire qui se connecte à la plateforme de gestion en nuage, lesdites largeur de bande d'enchère et cotation d'enchère sont entrées par le locataire, et une instance en nuage du locataire est définie dans un centre de calcul en nuage cible parmi une pluralité de centres de données en nuage et est liée à un IP de réseau public élastique ; et lorsque la plateforme de gestion en nuage détermine qu'il existe une largeur de bande inactive dans le centre de calcul en nuage cible, ladite largeur de bande inactive correspond à la largeur de bande d'enchère, la plateforme de gestion en nuage fournit la largeur de bande inactive pour l'instance en nuage du locataire, le coût de largeur de bande, qui est généré par l'instance en nuage du locataire accédant à un réseau public en utilisant la largeur de bande inactive dans le centre de calcul en nuage cible, étant déterminé sur la base de la cotation d'enchère. Au moyen de la présente demande, un locataire attribue une largeur de bande inactive dans un centre de calcul en nuage à une instance en nuage du locataire au moyen d'une enchère, de telle sorte que des ressources de largeur de bande au repos sont utilisées de manière rationnelle, ce qui permet de réduire le gaspillage des ressources de largeur de bande au repos, et de réduire le coût.
PCT/CN2023/108101 2022-07-19 2023-07-19 Procédé d'attribution de largeur de bande de réseau public basé sur un service en nuage public et plateforme de gestion en nuage WO2024017286A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210847423 2022-07-19
CN202210847423.1 2022-07-19
CN202211274973.5A CN117459397A (zh) 2022-07-19 2022-10-18 基于公有云服务的公网带宽分配方法及云管理平台
CN202211274973.5 2022-10-18

Publications (1)

Publication Number Publication Date
WO2024017286A1 true WO2024017286A1 (fr) 2024-01-25

Family

ID=89580466

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/108101 WO2024017286A1 (fr) 2022-07-19 2023-07-19 Procédé d'attribution de largeur de bande de réseau public basé sur un service en nuage public et plateforme de gestion en nuage

Country Status (2)

Country Link
CN (1) CN117459397A (fr)
WO (1) WO2024017286A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160112281A1 (en) * 2014-10-15 2016-04-21 Cisco Technology, Inc. Dynamic Cache Allocating Techniques for Cloud Computing Systems
CN111903109A (zh) * 2018-06-26 2020-11-06 英特尔公司 可超额预订资源分配
CN113626199A (zh) * 2021-08-19 2021-11-09 京东科技信息技术有限公司 闲置云计算资源的管理方法、装置、电子设备和存储介质
CN114072767A (zh) * 2019-09-11 2022-02-18 阿里巴巴集团控股有限公司 资源调度、申请与定价方法、设备、系统及存储介质
CN114461374A (zh) * 2020-10-22 2022-05-10 华为云计算技术有限公司 一种实例分配方法、系统及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160112281A1 (en) * 2014-10-15 2016-04-21 Cisco Technology, Inc. Dynamic Cache Allocating Techniques for Cloud Computing Systems
CN111903109A (zh) * 2018-06-26 2020-11-06 英特尔公司 可超额预订资源分配
CN114072767A (zh) * 2019-09-11 2022-02-18 阿里巴巴集团控股有限公司 资源调度、申请与定价方法、设备、系统及存储介质
CN114461374A (zh) * 2020-10-22 2022-05-10 华为云计算技术有限公司 一种实例分配方法、系统及装置
CN113626199A (zh) * 2021-08-19 2021-11-09 京东科技信息技术有限公司 闲置云计算资源的管理方法、装置、电子设备和存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
GHAVAMI ABOUZAR; LI ZHUOZHAO; SHEN HAIYING: "On-Demand Bandwidth Pricing for Congestion Control in Core Switches in Cloud Networks", 2016 IEEE 9TH INTERNATIONAL CONFERENCE ON CLOUD COMPUTING (CLOUD), IEEE, 27 June 2016 (2016-06-27), pages 867 - 870, XP033047995, DOI: 10.1109/CLOUD.2016.0125 *

Also Published As

Publication number Publication date
CN117459397A (zh) 2024-01-26

Similar Documents

Publication Publication Date Title
US11080084B1 (en) Managing resources in virtualization systems
US9438484B2 (en) Managing multi-level service level agreements in cloud-based networks
US8606667B2 (en) Systems and methods for managing a software subscription in a cloud network
JP7260470B2 (ja) クラウドシステムにおけるオンライン課金のための方法、システム、およびデバイス
US10268522B2 (en) Service aggregation using graduated service levels in a cloud network
US8935692B2 (en) Self-management of virtual machines in cloud-based networks
US9363198B2 (en) Load balancing in cloud-based networks
US9497139B2 (en) Client-allocatable bandwidth pools
US7886038B2 (en) Methods and systems for user identity management in cloud-based networks
US8495648B1 (en) Managing allocation of computing capacity
US9059944B2 (en) Method and arrangement for enabling service delivery in a telecommunications network
US8914511B1 (en) Managing resources in virtualization systems
US11922196B2 (en) Cloud-based utilization of software entitlements
US8612615B2 (en) Systems and methods for identifying usage histories for producing optimized cloud utilization
US9870541B2 (en) Service level backup using re-cloud network
US9842004B2 (en) Adjusting resource usage for cloud-based networks
US9306870B1 (en) Emulating circuit switching in cloud networking environments
US20120130873A1 (en) Systems and methods for generating multi-cloud incremental billing capture and administration
US20090300608A1 (en) Methods and systems for managing subscriptions for cloud-based virtual machines
WO2020177497A1 (fr) Procédé et système pour effectuer un traitement de facturation sur un client de tranche de réseau, et dispositif associé
US11563636B1 (en) Dynamic management of network policies between microservices within a service mesh
JP2023514487A (ja) 分散ストレージシステムにおけるマスターデータ配置
WO2018145475A1 (fr) Procédé, appareil et système de facturation
US20230259415A1 (en) Dynamic management of network policies between microservices within a service mesh
WO2021057981A1 (fr) Procédé et appareil de facturation en nuage, plateforme et système de gestion en nuage, et support de stockage

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23842348

Country of ref document: EP

Kind code of ref document: A1