CN104468136B - Charging method, analysis center and charging center - Google Patents

Abstract

An embodiment of the present invention provides a billing method, an analysis center, and a billing center, including: the analysis center queries the partition corresponding to each tenant and the availability zone corresponding to the tenant in each partition according to the identifier of the tenant, and obtains each At least one availability zone corresponding to the tenant, query the project corresponding to each tenant according to the identity of the tenant, query the resource information of the resources used by the tenant under at least one availability zone corresponding to each tenant, and then use each resource Finally, the resource usage information of each tenant is obtained, the resource usage statistics summary table is generated, and the resource usage statistics summary table is sent to the billing center, and the billing center obtains the resource usage statistics summary table of each tenant. Resource usage information, the cost of each tenant is determined according to the resource pricing table and the resource usage information of each tenant. It can realize hybrid billing for resource usage of multiple cloud services, and hybrid billing for multi-partition and multi-cloud platforms.

Description

Billing method, analysis center and billing center

technical field

The embodiment of the present invention relates to the technical field of the Internet, in particular to a charging method, an analysis center and a charging center.

Background technique

Open source infrastructure as a service (English: Infrastructure as a Service, referred to as: IaaS) cloud platform OpenStack is a free software and open source project jointly developed by NASA and the famous cloud computing company Rackspace. OpenStack is not a software , but an open source cloud platform management project. OpenStack supports almost all types of cloud environments. The goal of the project is to provide a cloud computing management platform that is simple to implement, scalable on a large scale, rich, and unified in standards. It provides public and private clouds with A scalable and flexible cloud computing platform. At present, OpenStack is developing very rapidly, and its community already has more than 170 companies and 3,000 developers. These institutions and developers have chosen to use OpenStack to create their own private cloud platforms.

However, as cloud computing gradually enters the stage of combining academic research and commercial applications, the commercial application of cloud computing has gradually become a new direction for the development of cloud computing. Under the influence of this major development trend, OpenStack will gradually develop towards commercialization. However, the current focus of OpenStack has been on virtualization, network, security and other fields. There is no billing mechanism for OpenStack, and some existing billing mechanisms can only bill a single cloud service or a single cloud platform. , does not support hybrid billing for the resource usage of multiple cloud services, nor does it support hybrid billing for multi-region (Region) multi-cloud platforms.

Contents of the invention

The embodiment of the present invention provides a billing method, an analysis center and a billing center, which are used to provide a billing mechanism suitable for OpenStack, which can solve the problem that the existing technology does not support mixed billing for resource usage of multiple cloud services , and does not support hybrid billing for multi-partition and multi-cloud platforms.

In the first aspect, a charging method is provided, which is suitable for charging cloud service resource usage under cloud computing, and the method includes:

Query the partition corresponding to the first tenant according to the identifier of the first tenant, and query the availability zone corresponding to the first tenant in each partition corresponding to the first tenant, and obtain at least An availability zone; wherein the first tenant is any one of all tenants;

Querying the project corresponding to the first tenant according to the identifier of the first tenant to obtain at least one project corresponding to the first tenant;

Query resource information of resources used by each project in the at least one project in the at least one availability zone according to the identifier of the at least one project, and obtain resource information of at least one resource used by the first tenant;

Counting the usage of each resource according to the resource information of the at least one resource to obtain the resource usage information of the first tenant;

Generate a resource usage statistics summary table according to the resource usage information of all tenants;

Send the resource usage statistics summary table to the billing center, so that the billing center can obtain the resource usage information of each tenant according to the resource usage statistics summary table, and determine the resource usage information of each tenant according to the resource pricing table and the resource usage information of each tenant. tenant's fees.

With reference to the first aspect, in a first possible implementation manner, the resource information of the at least one resource includes: a resource identifier and a resource type of the at least one resource;

Wherein, the resource type includes: one of instance, image, simple storage service S3, elastic block storage EBS, elastic load balancing ELB, and traffic.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, the counting the usage of each resource according to the resource information of the at least one resource includes:

If the resource type of any resource in the at least one resource is an instance, count the usage time of the virtual machine corresponding to the any resource as the usage amount of the any resource according to the resource identifier of the any resource;

If the resource type of any resource is a mirror image, then according to the resource identifier of any resource, the usage time of the virtual machine corresponding to the instance to which any resource belongs is taken as the usage amount of any resource;

If the resource type of any resource is EBS, count the usage space size and usage duration of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of any resource is S3, count the usage space size and usage duration of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of any resource is ELB, count the usage time of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of the any resource is traffic, count the traffic value of the any resource corresponding to the any resource according to the resource identifier of the any resource as the usage amount of the any resource.

With reference to the first aspect or any of the above possible implementation manners, in a third possible implementation manner, the querying the partition corresponding to the first tenant and each of the partitions according to the identifier of the first tenant From the availability zone corresponding to the first tenant to the sending of the resource usage statistics summary table to the billing center is a query batch;

After the resource usage statistics summary table is sent to the billing center, the next query batch is executed after a preset period of time.

With reference to the third possible implementation of the first aspect, in a fourth possible implementation, in the resource usage statistics summary table, each resource corresponds to an entry; wherein, the entry corresponding to any resource includes: Tenant ID, resource type, resource ID, resource usage, query timestamp;

Wherein, the tenant ID is the ID of the tenant using the any resource, the resource type is the resource type of the any resource, the resource ID is the resource ID of the any resource, and the resource uses The amount is the usage amount of any resource used by the tenant corresponding to the tenant ID, and the query timestamp is the time point when the resource usage amount is queried, wherein, in the same query batch, the entry corresponding to each resource The query timestamps in are the same.

In the second aspect, a charging method is provided, which is suitable for charging cloud service resource usage under cloud computing, and the method includes:

Receive the summary table of resource usage statistics sent by the analysis center;

Obtain resource usage information of each tenant according to the resource usage statistics table;

Obtain the cost of each tenant according to the resource pricing table and the resource usage information of each tenant;

The resource type of the resource includes: one of instance, image, simple storage service S3, elastic block storage EBS, elastic load balance ELB, and traffic.

With reference to the second aspect, in a first possible implementation manner, each resource in the resource usage statistics summary table corresponds to an entry; wherein, the entry corresponding to any resource includes: tenant identifier, resource type, resource identifier, Resource usage, query timestamp;

Wherein, the tenant ID is the ID of the tenant using the any resource, the resource type is the resource type of the any resource, the resource ID is the resource ID of the any resource, and the resource uses The amount is the usage amount of any resource used by the tenant corresponding to the tenant ID, and the query timestamp is the time point when the resource usage amount is queried, wherein, in the same query batch, the entry corresponding to each resource The query timestamps in are the same.

With reference to the first possible implementation manner of the second aspect, in the second possible implementation manner, the obtaining the resource usage information of each tenant according to the resource usage statistics table includes:

determining the tenant to which each entry belongs according to the tenant identifier in each entry in the resource usage statistics summary table;

The resource usage information of each tenant is obtained according to all entries of each tenant, and the resource usage information of each tenant includes the usage amount of each resource used by each tenant.

With reference to the second possible implementation of the second aspect, in a third possible implementation, the obtaining the cost of each tenant according to the resource pricing table and the resource usage information of each tenant includes:

Query the resource pricing table to obtain the unit price of each resource used by each tenant;

According to the unit price of each resource used by each tenant, calculate the cost of each resource used by each tenant according to the usage of each resource used by each tenant and the preset billing policy;

Calculates the total cost per tenant based on the cost per resource used by each tenant.

In combination with the third possible implementation of the second aspect, in the fourth possible implementation, the usage of each resource used by each tenant includes:

For any tenant, if the resource type of any resource used by the any tenant is an instance, the usage amount of the any resource is the usage time of the virtual machine corresponding to the any resource;

If the resource type of any resource used by any of the tenants is mirroring, the usage of any of the resources is the usage time of the virtual machine corresponding to the instance to which any of the resources belongs;

If the resource type of any resource used by any of the tenants is EBS, then the amount of usage of any of the resources is the size and duration of usage of any of the resources;

If the resource type of any resource used by any of the tenants is S3, then the amount of usage of any of the resources is the usage space and duration of usage of any of the resources;

If the resource type of any resource used by any of the tenants is ELB, the usage amount of any of the resources is the usage time of any of the resources;

If the resource type of any resource used by any tenant is traffic, the usage amount of any resource is the traffic value of any resource.

With reference to the fourth possible implementation of the second aspect, in a fifth possible implementation, the preset charging policy includes:

If the resource type of any resource used by any of the tenants is an instance, the fee for any of the resources used by any of the tenants is the virtual machine usage time corresponding to the any of the resources * the time of use of the any of the resources unit price;

If the resource type of any resource used by any of the tenants is mirror image, the cost for any of the resources used by any of the tenants is the usage time of the virtual machine corresponding to the instance to which any of the resources belongs * the duration of any of the resources the unit price of a resource;

If the resource type of any resource used by any of the tenants is EBS, then the fee for any of the resources used by any of the tenants is the size of the space used by any of the resources * the duration of use * the the unit price of the resource;

If the resource type of any resource used by any of the tenants is S3, then the fee for any of the resources used by any of the tenants is the size of the space used by any of the resources * the duration of use * the the unit price of the resource;

If the resource type of any resource used by any tenant is ELB, the cost for any resource used by any tenant is the usage time of any resource * the unit price of any resource ;

If the resource type of any resource used by any of the tenants is traffic, then the cost for any of the resources used by any of the tenants is the traffic value of any of the resources * the unit price of any of the resources ;

Wherein, the unit price of any resource is determined according to the resource price, price unit and measurement unit of any resource.

In combination with the second aspect or any of the above-mentioned possible implementation manners, in a sixth implementation manner, it also includes:

Obtain the utilization rate of each type of resource counted by the analysis center;

The resource price of this type of resource is adjusted according to the usage rate of each type of resource and the preset price adjustment strategy corresponding to the usage rate of each type of resource.

In a third aspect, an analysis center is provided, which is suitable for billing cloud service resource usage under cloud computing, and the analysis center includes:

A query module, configured to query the partition corresponding to the first tenant according to the identifier of the first tenant, and query the availability zone corresponding to the first tenant in each partition corresponding to the first tenant, to obtain the first tenant At least one availability zone corresponding to a tenant; wherein the first tenant is any one of all tenants;

The query module is further configured to query the project corresponding to the first tenant according to the identifier of the first tenant, and obtain at least one project corresponding to the first tenant;

A collection module, configured to query resource information of resources used by each project in the at least one project in the at least one availability zone according to the identifier of the at least one project, and obtain at least one resource used by the first tenant. resource information of the resource;

An analysis module, configured to count the usage of each resource according to the resource information of the at least one resource, and obtain the resource usage information of the first tenant;

The analysis module is configured to generate a summary table of resource usage statistics according to the resource usage information of all tenants;

An interface module, configured to send the resource usage summary table to the billing center, so that the billing center can obtain the resource usage information of each tenant according to the resource usage statistics table, and according to the resource pricing table and each tenant's Resource usage information determines the cost per tenant.

With reference to the third aspect, in a first possible implementation manner, the resource information of the at least one resource includes: a resource identifier and a resource type of the at least one resource;

Wherein, the resource type includes: one of instance, image, simple storage service S3, elastic block storage EBS, elastic load balancing ELB, and traffic.

With reference to the first possible implementation of the third aspect, in a second possible implementation, the analysis module is specifically configured to:

If the resource type of any resource in the at least one resource is an instance, count the usage time of the virtual machine corresponding to the any resource as the usage amount of the any resource according to the resource identifier of the any resource;

If the resource type of any resource is a mirror image, then according to the resource identifier of any resource, the usage time of the virtual machine corresponding to the instance to which any resource belongs is taken as the usage amount of any resource;

If the resource type of any resource is EBS, count the usage space size and usage duration of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of any resource is S3, count the usage space size and usage duration of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of any resource is ELB, count the usage time of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of the any resource is traffic, count the traffic value of the any resource corresponding to the any resource according to the resource identifier of the any resource as the usage amount of the any resource.

With reference to the third aspect or any of the above possible implementations, in a third possible implementation, the query module queries the partition corresponding to the first tenant and each The availability zone corresponding to the first tenant in the partition to the interface module sends the resource usage statistics summary table to the billing center as a query batch;

After the interface module sends the resource usage statistics summary table to the billing center, the next query batch is executed after a preset period of time.

With reference to the third possible implementation of the third aspect, in a fourth possible implementation, in the resource usage statistics summary table, each resource corresponds to an entry; wherein, the entry corresponding to any resource includes: Tenant ID, resource type, resource ID, resource usage, query timestamp;

Wherein, the tenant ID is the ID of the tenant using the any resource, the resource type is the resource type of the any resource, the resource ID is the resource ID of the any resource, and the resource uses The amount is the usage amount of any resource used by the tenant corresponding to the tenant ID, and the query timestamp is the time point when the resource usage amount is queried, wherein, in the same query batch, the entry corresponding to each resource The query timestamps in are the same.

In a fourth aspect, a billing center is provided, which is suitable for billing resource usage of cloud services under cloud computing, and the billing center includes:

The interface module is used to receive the summary table of resource usage statistics sent by the analysis center;

An acquisition module, configured to acquire resource usage information of each tenant according to the resource usage statistics table;

The billing module is used to obtain the cost of each tenant according to the resource pricing table and the resource usage information of each tenant;

The resource type of the resource includes: one of instance, image, simple storage service S3, elastic block storage EBS, elastic load balance ELB, and traffic.

With reference to the fourth aspect, in a first possible implementation manner, each resource corresponds to an entry in the resource usage statistics summary table; wherein, the entry corresponding to any resource includes: tenant identifier, resource type, resource identifier, Resource usage, query timestamp;

Wherein, the tenant ID is the ID of the tenant using the any resource, the resource type is the resource type of the any resource, the resource ID is the resource ID of the any resource, and the resource uses The amount is the usage amount of any resource used by the tenant corresponding to the tenant ID, and the query timestamp is the time point when the resource usage amount is queried, wherein, in the same query batch, the entry corresponding to each resource The query timestamps in are the same.

With reference to the first possible implementation of the fourth aspect, in the second possible implementation, the acquiring module is specifically configured to:

determining the tenant to which each entry belongs according to the tenant identifier in each entry in the resource usage statistics summary table;

The resource usage information of each tenant is obtained according to all entries of each tenant, and the resource usage information of each tenant includes the usage amount of each resource used by each tenant.

With reference to the second possible implementation of the fourth aspect, in a third possible implementation, the billing module includes:

A unit price query module, configured to query the resource pricing table to obtain the unit price of each resource used by each tenant;

The resource billing module is used to calculate the unit price of each resource used by each tenant, according to the usage of each resource used by each tenant and the preset billing policy. resource costs;

The tenant billing module is used to calculate the total cost of each tenant according to the cost of each resource used by each tenant.

In combination with the third possible implementation of the fourth aspect, in the fourth possible implementation, the usage of each resource used by each tenant includes:

For any tenant, if the resource type of any resource used by the any tenant is an instance, the usage amount of the any resource is the usage time of the virtual machine corresponding to the any resource;

If the resource type of any resource used by any of the tenants is mirroring, the usage of any of the resources is the usage time of the virtual machine corresponding to the instance to which any of the resources belongs;

If the resource type of any resource used by any of the tenants is EBS, then the amount of usage of any of the resources is the size and duration of usage of any of the resources;

If the resource type of any resource used by any of the tenants is S3, then the amount of usage of any of the resources is the usage space and duration of usage of any of the resources;

If the resource type of any resource used by any of the tenants is ELB, the usage amount of any of the resources is the usage time of any of the resources;

If the resource type of any resource used by any tenant is traffic, the usage amount of any resource is the traffic value of any resource.

With reference to the fourth possible implementation of the fourth aspect, in a fifth possible implementation, the preset charging policy includes:

If the resource type of any resource used by any of the tenants is an instance, the fee for any of the resources used by any of the tenants is the virtual machine usage time corresponding to the any of the resources * the time of use of the any of the resources unit price;

If the resource type of any resource used by any of the tenants is mirror image, the cost for any of the resources used by any of the tenants is the usage time of the virtual machine corresponding to the instance to which any of the resources belongs * the duration of any of the resources the unit price of a resource;

If the resource type of any resource used by any of the tenants is EBS, then the fee for any of the resources used by any of the tenants is the size of the space used by any of the resources * the duration of use * the the unit price of the resource;

If the resource type of any resource used by any of the tenants is S3, then the fee for any of the resources used by any of the tenants is the size of the space used by any of the resources * the duration of use * the the unit price of the resource;

If the resource type of any resource used by any tenant is ELB, the cost for any resource used by any tenant is the usage time of any resource * the unit price of any resource ;

If the resource type of any resource used by any of the tenants is traffic, then the cost for any of the resources used by any of the tenants is the traffic value of any of the resources * the unit price of any of the resources ;

Wherein, the unit price of any resource is determined according to the resource price, price unit and measurement unit of any resource.

With reference to the fourth aspect or any of the above-mentioned possible implementation manners, in a sixth implementation manner, the billing center further includes: a price adjustment module, and the price adjustment module is used for:

Obtain the utilization rate of each type of resource counted by the analysis center;

The resource price of this type of resource is adjusted according to the usage rate of each type of resource and the preset price adjustment strategy corresponding to the usage rate of each type of resource.

An embodiment of the present invention provides a billing method, an analysis center, and a billing center. First, the analysis center queries the partition corresponding to each tenant according to the identifier of the tenant, and queries the corresponding tenant in each partition corresponding to each tenant. Availability zone, get at least one availability zone corresponding to each tenant, and also query the project corresponding to each tenant according to the identifier of the tenant, so as to query the resources of at least one resource used by the tenant under at least one availability zone corresponding to each tenant Information, and then count the usage of each resource, finally get the resource usage information of each tenant, generate a resource usage statistics summary table, and send the resource usage statistics summary table to the billing center, the billing center can The resource usage information of each tenant is obtained according to the resource usage statistics table, and the cost of each tenant is determined according to the resource pricing table and the resource usage information of each tenant. It can realize hybrid billing for resource usage of multiple cloud services, and realize hybrid billing for multi-partition and multi-cloud platforms.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without any creative effort.

FIG. 1 is a schematic diagram of the architecture of Openstack in the prior art;

FIG. 2 is a schematic structural diagram of a billing system provided by an embodiment of the present invention;

FIG. 3 is a schematic flowchart of a billing method provided by an embodiment of the present invention;

FIG. 4 is a schematic flowchart of another billing method provided by an embodiment of the present invention;

FIG. 5 is a schematic flowchart of another billing method provided by an embodiment of the present invention;

FIG. 6 is a schematic flowchart of a resource usage statistics method in another charging method provided by an embodiment of the present invention;

FIG. 7 is a schematic flowchart of a tenant fee statistics method in another charging method provided by an embodiment of the present invention;

FIG. 8 is a schematic flowchart of an operation of setting resource pricing in another charging method provided by an embodiment of the present invention;

FIG. 9 is a schematic flowchart of recording the operation of setting resource pricing in another billing method provided by an embodiment of the present invention;

FIG. 10 is a schematic flowchart of an administrator querying fees in another charging method provided by an embodiment of the present invention;

Fig. 11 is a schematic flow chart of a tenant query fee in another charging method provided by an embodiment of the present invention;

FIG. 12 is a schematic flowchart of adjusting resource prices in another charging method provided by an embodiment of the present invention;

Fig. 13 is a schematic structural diagram of an analysis center provided by an embodiment of the present invention;

Fig. 14 is a schematic structural diagram of a billing center provided by an embodiment of the present invention;

Fig. 15 is a schematic structural diagram of another billing center provided by an embodiment of the present invention;

FIG. 16 is a schematic structural diagram of a billing module provided by an embodiment of the present invention;

Fig. 17 is a schematic structural diagram of another billing center provided by an embodiment of the present invention;

FIG. 18 is a schematic structural diagram of another billing center provided by an embodiment of the present invention;

FIG. 19 is a schematic structural diagram of another billing center provided by an embodiment of the present invention;

FIG. 20 is a schematic structural diagram of another billing center provided by an embodiment of the present invention;

Fig. 21 is a schematic structural diagram of another analysis center provided by an embodiment of the present invention;

Fig. 22 is a schematic structural diagram of another billing center provided by an embodiment of the present invention.

detailed description

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

It should be understood that the technical solution of the embodiment of the present invention can be applied to the OpenStack cloud environment, and is suitable for charging the resource usage of cloud services under cloud computing. The system architecture of OpenStack can be shown in Figure 1, and the OpenStack cloud environment can include multiple Region, or also called Data Center (DC for short), region can be understood as a geographical area, which is a physical concept, for example, a region is set up in Beijing. One district is set up in Wuhan, and operators generally deploy a set of OpenStack systems (that is, a set of cloud platforms) in different regions. Availability Zone (English: Availability Zone, referred to as: AZ) is a subdivision within the partition range. Multiple AZs can be included in one area. AZ can actually be understood as the internal availability area of the OpenStack system. One OpenStack system can correspond to one or multiple AZs. The system architecture applied by the technical solution of the embodiment of the present invention can be shown in Figure 2, including: a billing system, and a plurality of partitions to be counted by the billing system, the billing system includes a billing center and an analysis center, the analysis The center is responsible for the collection of raw metering data. It obtains the raw data of resource usage of cloud services of different OpenStack systems from different partitions, stores them in the analysis database (Analysis Data), and then performs analysis and statistics based on the raw data in the analysis database. , to generate a key performance indicator (English: Key Performance Indicator, KPI for short) based on the consumption behavior of the tenant. The KPI is provided to the billing center (Billing Center). Usage amount. The billing center obtains the price of each resource from the billing database (Billing Data), so as to charge the consumption behavior of each tenant according to the KPI, and the billing center can also adjust the price of various resources according to the KPI.

An embodiment of the present invention provides a charging method, which is suitable for charging cloud service resource usage under cloud computing. As shown in FIG. 3, the method includes:

Step 101: Query the partition corresponding to the first tenant according to the identifier of the first tenant, and query the availability zone corresponding to the first tenant in each partition corresponding to the first tenant, and obtain the first tenant Corresponding to at least one availability zone; wherein the first tenant is any one of all tenants.

Step 102: Query the project corresponding to the first tenant according to the identifier of the first tenant, and obtain at least one project corresponding to the first tenant.

Step 103: Query the resource information of the resources used by each project in the at least one project in the at least one availability zone according to the identifier of the at least one project, and obtain the information of the at least one resource used by the first tenant resource information.

Step 104: Count the usage of each resource according to the resource information of the at least one resource to obtain the resource usage information of the first tenant.

Step 105, generating a resource usage statistics table according to the resource usage information of all tenants.

Step 106: Send the resource usage summary table to the billing center, so that the billing center can obtain the resource usage information of each tenant according to the resource usage statistics table, and according to the resource pricing table and the resource usage information of each tenant Information to determine the cost per tenant.

On the other hand, the embodiment of the present invention also provides another charging method, which is suitable for charging cloud service resource usage under cloud computing. As shown in FIG. 4 , the method includes:

Step 201, receiving the resource usage statistics summary table sent by the analysis center.

Step 202. Obtain the resource usage information of each tenant according to the resource usage statistics summary table.

Step 203, obtaining the cost of each tenant according to the resource pricing table and the resource usage information of each tenant.

The resource types of the resources include: instance (Instance), image (Image), simple storage service (English: Simple Storage Service, abbreviated: S3), elastic block storage (English: Elastic Block Store, abbreviated: EBS), elastic load Balance (English: Elastic Load Balancing, referred to as: ELB), and one of the traffic (Traffic).

The embodiment of the present invention provides a billing method. The analysis center queries the partition corresponding to each tenant according to the identifier of the tenant, and queries the available area corresponding to the tenant in each partition corresponding to each tenant, and obtains the corresponding partition of each tenant. At least one availability zone, and query the project corresponding to each tenant according to the identifier of the tenant, so as to query the resource information of at least one resource used by the tenant under at least one availability zone corresponding to each tenant, and then check the resource information of each resource The usage is counted, and finally the resource usage information of each tenant is obtained, the resource usage statistics summary table is generated, and the resource usage statistics summary table is sent to the billing center, which can obtain each tenant according to the resource usage statistics summary table The resource usage information of tenants, the cost of each tenant is determined according to the resource pricing table and the resource usage information of each tenant. It can realize hybrid billing for the resource usage of multiple cloud services, and realize hybrid billing for multi-partition and multi-cloud platforms.

In order to enable those skilled in the art to more clearly understand the technical solutions provided by the embodiments of the present invention, the billing method provided by the embodiments of the present invention will be described in detail below through specific embodiments. For the convenience of description, the first tenant For example, the first tenant can be any tenant in all tenants, as shown in Figure 5, the method includes:

Step 301: The analysis center queries the partition corresponding to the first tenant according to the identifier of the first tenant and queries the availability zone corresponding to the first tenant in each partition corresponding to the first tenant, and obtains the first tenant corresponding to at least one availability zone.

Exemplarily, before the data collection starts, the analysis center can call the interface Get/v3/domains of KeyStone (authentication and authentication module) to query the Domains (domain) list (the domain list includes the information of each partition), and establish The relationship between each tenant, partition, and availability zone. According to the relationship, you can query the partition corresponding to each tenant and the availability zone corresponding to the tenant in each partition.

Therefore, using the above relationship, query the partition corresponding to the first tenant according to the identity of the first tenant (for example, tenant ID), and query the availability zone corresponding to the first tenant in each partition corresponding to the first tenant, you can get the first tenant Corresponding to at least one availability zone, an availability zone list may be generated for the at least one availability zone. Wherein, the identifier of the first tenant may be a tenant ID of the first tenant, and the tenant ID may be, for example, a Token (access) ID.

Step 302: The analysis center searches for projects corresponding to the first tenant according to the identifier of the first tenant, and obtains at least one project corresponding to the first tenant.

Exemplarily, the analysis center can call the interface Get/v3/projects of KeyStone according to the identity of each tenant to query the projects corresponding to the tenant, so according to the identity of the first tenant to query the project corresponding to the first tenant, you can get For at least one project corresponding to the first tenant, a project list may be generated for the at least one project.

Step 303: The analysis center queries the resource information of the resources used by each project in the at least one project under the at least one availability zone according to the identifier of the at least one project, and obtains at least one resource used by the first tenant. Resource information for the resource.

Exemplarily, the analysis center can call the interface Get/v2/meters of Ceilometer (statistical module)? q.op=eq&q.value={value}&q.field={field} query measurement object, the measurement object is the resource used by each project and its resource information.

Therefore, call the interface Get/v2/meters according to the at least one project identifier (for example, project ID)? q.op=eq&q.value={value}&q.field={field} can count the resource information of at least one resource used by the first tenant, and can generate a resource list for the resource information of the at least one resource, This list can be stored in the analysis database for subsequent recall in statistics.

Wherein, the resource information of each resource may include: a resource identifier and a resource type of the resource. Exemplarily, the resource type may be one of: instance, image, S3, EBS, ELB, and traffic. Wherein, if the resource type of a resource is an instance, the resource identifier of the resource is an instance ID, which may be a virtual machine specification name (VM SpecName), where VM represents a virtual machine (Virtual Machine), and Spec represents a specification (Specification), If the resource type of a resource is mirror image, the resource ID of the resource is mirror ID; if the resource type of a resource is EBS, the resource ID of the resource is volume ID or snapshot ID; if If the resource type of a resource is ELB, the resource identifier of the resource is the bucket ELB name (Name). If the resource type of a resource is S3, the resource identifier of the resource is the bucket ID.

Step 304, the analysis center collects statistics on the usage of each resource according to the resource information of the at least one resource, and obtains the resource usage information of the first tenant.

Exemplarily, the analysis center calls the interface Get/v2/meters/{meter_name}/statistics of Ceilometer for a certain resource? period＝{value}&q.op＝eq&q.value＝{value}&q.field＝{field}&groupby＝{value} can be used to obtain the usage of this resource by making statistics, so the resource list of the first tenant of this interface is called cyclically By making statistics on each resource of the first tenant, the usage amount of each resource used by the first tenant can be obtained, and the usage amount of each resource used by the first tenant can be used as the resource usage information of the first tenant.

Among them, for different types of resources, the measurement of their resource usage is also different, for example:

If the resource type of any resource is an instance, count the usage time of the virtual machine corresponding to the resource as the usage amount of the resource according to the resource identifier (VMSpecName) of the resource. Wherein, when counting the usage time of a virtual machine, hours can be used as a measurement unit, and the usage time of less than one hour is counted as one hour.

If the resource type of any resource is a mirror image, the usage time of the virtual machine corresponding to the instance to which the resource belongs is taken as the usage amount of the resource according to the resource identifier (mirror ID) of the resource. It should be noted that since the image is a sub-resource of the instance, the usage of the image is not counted separately, and the usage time of the virtual machine corresponding to the instance to which it belongs is used as the usage of the image.

If the resource type of any resource is EBS, the usage space size and usage duration of the resource are counted according to the resource identifier (volume ID or snapshot ID) of the resource as the usage amount of the resource. Among them, the statistical time can be measured in hours. If the usage time is less than one hour, it will be counted as one hour. The statistical usage space can be measured in GB. It should be noted that due to the limitation of Openstack, it may not be possible to query each volume. Or the usage of snapshots, only the total EBS usage of each project can be queried. At this time, it is only necessary to count the usage of EBS used by each project.

If the resource type of any resource is S3, the usage space size and usage duration of the resource are counted as the usage amount of the resource according to the resource identifier (bucket ID) of the resource. Among them, the statistical duration can be measured in hours, and the usage duration of less than one hour is counted as one hour, and the statistical used space size can be measured in GB (gigabytes). It should be noted that when counting the usage of S3, it is only necessary to record which partition the S3 belongs to, and it is not necessary to record which availability zone the S3 belongs to.

If the resource type of any resource is ELB, count the usage time of any resource as the usage amount of the resource according to the resource identifier (ELB name) of the resource. Similarly, the statistical duration can be measured in hours, and the usage duration of less than one hour is counted as one hour.

If the resource type of any resource is traffic, the traffic value of the resource corresponding to the resource is counted according to the resource identifier of the resource as the usage amount of the resource. Wherein, the traffic value may be measured in GB/hour.

In this way, the statistics of the resource usage information of the first tenant is completed. For the resource usage information of other tenants, the statistical method is exactly the same as that of the first tenant. By repeatedly executing steps 301 to 304, the resource usage information of all tenants can be obtained.

Step 305, the analysis center generates a resource usage statistics summary table according to the resource usage information of all tenants.

Specifically, the analysis center summarizes the resource usage information of all tenants to obtain a resource usage statistics summary table. The resource usage statistics summary table can be called the t_resource_meter table, and the table records the information of each resource used by each tenant. Usage amount.

In the resource usage statistics summary table, each resource corresponds to an entry, and the entry corresponding to any resource may include the tenant ID, resource type, resource ID, resource usage, and query timestamp. The tenant identifier of a resource, the resource type is the resource type of any resource, the resource identifier is the resource identifier of any resource, and the resource usage is the usage of any resource by the tenant corresponding to the tenant identifier The query time stamp is the point in time when the resource usage is queried. In the same query batch, the query time stamps in the entries corresponding to each resource are the same. In addition, other information can also be included, such as the partition and availability zone described by the resource. In addition, the above-mentioned tenant ID can be a tenant ID or a project ID. The usage can be subdivided into usage and duration, and the duration can be subdivided into usage duration (minutes) and added hours. The added hours are used It is used to round up the usage time, and is used to count the usage time of less than one hour as one hour, which can provide a basis for subsequent fee calculations. Exemplarily, an entry of the resource usage statistics summary table may be as shown in Table 1:

Table 1

"VARCHAR" in Table 1 means a variable-length character string, "NUMERIC" means a value, "M" means a must (Must), and the format of TIME_STAMP can be set to "YYYYDDMMHH:MM", where YYYYDDMM means year, day, month, HH :MM indicates hours and minutes. The TIME_STAMP of all entries in the resource usage statistics table obtained in one collection task are the same, and the reserved fields refer to other possible resource types. In addition, regarding the use of newly added hours, for example, for the first collection, USETIME=15 minutes, NEW_ADDED_HOUR=1, billing is calculated according to 1 hour; for the second collection, USETIME=30, NEW_ADDED_HOUR=0, because 15 minutes At that time, it has been billed according to 1 hour, so there will be no repeated billing at 30 minutes, and when USETIME=75, NEW_ADDED_HOUR=1, and so on.

In addition, the resource usage statistics summary table can be backed up regularly, for example, it can be backed up every month. Specifically, at the beginning of each month, the existing resource usage statistics summary table can be renamed and saved as a history table, and then the latest resource usage statistics can be generated. For the general table, for example, assuming that the current month is December, you can name the existing table t_resource_meter_201412, and then create t_resource_meter based on the latest statistical data. In addition, you can also set the storage time of the history table, and automatically delete the history table after the storage time exceeds.

Step 306, the analysis center sends the resource usage statistics summary table to the billing center.

One query batch is completed from step 301 to step 306, and steps 301 to 306 can be executed again after a preset time interval to perform the next query batch.

Step 307, the billing center receives the resource usage statistics summary table sent by the analysis center.

Step 308, the billing center obtains the resource usage information of each tenant according to the resource usage statistics table. Specifically, as shown in Figure 6, the following steps may be included:

Step 3081: Determine the tenant to which each entry belongs according to the tenant identifier in each entry in the resource usage statistics summary table.

Step 3082: Obtain the resource usage information of each tenant according to all the entries of each tenant, and the resource usage information of each tenant includes the usage amount of each resource used by each tenant.

Specifically, according to step 305, there is a tenant identification (TENANT_ID) in each entry, which tenant the entry belongs to can be known according to the tenant identification, so that each tenant can be known according to all entries of each tenant The usage of each resource used by the resource.

Step 309, the billing center determines the fee for each tenant according to the resource pricing table and the resource usage information of each tenant. Specifically, as shown in Figure 7, the following steps may be included:

Step 3091, query the resource pricing table to obtain the unit price of each resource used by each tenant.

Exemplarily, the resource pricing table may be preset and stored in the billing database, and the billing center may query the information in the resource pricing table by accessing the billing database when billing. Wherein, a price entry in the resource pricing table may be as shown in Table 2.

Table 2

"VARCHAR" in Table 2 indicates a variable-length character string, and "NOT NULL" indicates that it is not empty. Under the same partition, resources of the same type but belonging to different AZs have different prices.

Step 3092: Calculate the cost of each resource used by each tenant according to the unit price of each resource used by each tenant, according to the usage amount of each resource used by each tenant and the preset charging policy.

Exemplarily, according to the Unit and MeasurementUnit in Table 2, the unit price of the resource corresponding to the price item can be obtained. Therefore, the unit price of each resource used by each tenant can be obtained by querying the resource pricing table, and then according to the usage amount of each resource used by each tenant obtained in step 3082, the preset billing policy can be used. Calculate the cost per resource used by each tenant.

Among them, the preset billing policy may include:

If the resource type of any resource used by any of the tenants is an instance, the cost for the tenant to use the resource is the usage time of the virtual machine corresponding to the resource * the unit price of the resource;

If the resource type of any resource used by any of the tenants is a mirror image, the cost for the tenant to use the resource is the usage time of the virtual machine corresponding to the instance to which the resource belongs * the unit price of the resource;

If the resource type of any resource used by any of the tenants is EBS, then the cost for the tenant to use the resource is the size of the space used for the resource * the duration of use * the unit price of the resource; where EBS may be a volume or Snapshots, therefore the costs of volumes and snapshots should be counted separately.

If the resource type of any resource used by any of the tenants is S3, the cost for the tenant to use the resource is the size of the resource’s usage space*use duration*the unit price of the resource;

If the resource type of any resource used by any of the tenants is ELB, the cost for the tenant to use the resource is the usage time of the resource * the unit price of the resource;

If the resource type of any resource used by any of the tenants is flow, then the cost for the tenant to use the resource is the flow value of the resource*the unit price of the resource; among them, the flow should be divided into uplink flow, downlink flow Traffic, upstream traffic and downstream traffic are billed separately, and the unit price is the same.

Wherein, the unit price of any resource is determined according to the resource price, price unit and measurement unit of any resource.

Wherein, after obtaining the cost of each resource, a resource billing table can be generated for the cost of each resource, which can be recorded as "t_resource_price", where the resource billing table can be backed up regularly, for example, monthly Backup. Specifically, at the beginning of each month, you can rename the existing resource billing table and save it as a history table, and then generate the latest resource billing table. For example, if the current month is December, you can name the existing table as t_resource_price_201412 , and then create the t_resource_price based on the latest statistical data. In addition, you can also set the storage time of the history table, and automatically delete the history table after the storage time exceeds.

Exemplarily, generating t_resource_price may include:

Among them, PayAccountName is the name of the payment account, LinkedAccountName is the name of the linked payment account, PayerAccountId is the ID of the payer account, LinkedAccountId is the ID of the linked account, CloudType is the cloud type, ProductName is the product name, Region is the partition, TenantID is the tenant ID, ResourceType is the resource type, ResourceID is the resource ID, ResourceSpecificationType is the resource specification type, AllUsage is the usage amount, AllFee is the fee, ItemDescription is the description information, and Time is the billing time.

Step 3093: Calculate the total cost of each tenant according to the cost of each resource used by each tenant.

According to the cost of each resource obtained in step 3092, the total cost of each tenant can be obtained by summing according to the dimension of the tenant, and a resource billing summary table is generated for each tenant. The resource billing table can be recorded as " t_resource_price_total", which can specifically include:

Among them, PayAccountName is the name of the payment account, LinkedAccountName is the name of the linked payment account, PayerAccountId is the ID of the payer account, LinkedAccountId is the ID of the linked account, CloudType is the cloud type, ProductName is the product name, Region is the partition, TenantID is the tenant ID, ResourceType is the resource type, ResourceID is the resource ID, ResourceSpecificationType is the resource specification type, AllUsage is the usage, AllFee is the fee, UsageRound is the usage rounding, ItemDescription is the description information, and Time is the billing time.

From step 301 to step 309, the billing process for each tenant is completed. This process can be repeated at certain time intervals, for example, once a month, so as to obtain the monthly fee of each tenant.

In addition, optionally, as shown in FIG. 8, the charging method provided in this embodiment of the present invention may further include:

Step 401, the billing center receives from the administrator device a resource pricing request triggered by the administrator through the administrator interface; the resource pricing request is one of: a price setting request, a price deletion request, and a price query request .

Step 402, the billing center performs a corresponding operation of setting resource pricing on the resource pricing table according to the resource pricing setting request.

Step 403, the billing center returns a resource pricing response to the administrator device.

Specifically, the administrator interface may be an interactive interface displayed on the administrator device, which is used for the administrator to implement the operation of setting resource pricing through the interactive interface. Exemplarily, the administrator interface may be There are three tab pages, one of which is used for pricing operations on EBS/ELB/S3/traffic, one is used for pricing operations on images, and the other is used for pricing operations on virtual machine specifications . Wherein, each Tab page is provided with an entry of the resource corresponding to the page, and each entry includes resource type, current price, description information, update time, and operation buttons. When an item in a Tab page is selected, clicking the operation button of the item will display the price setting interface on the administrator interface. The price setting interface can usually be set with a price input column and description information input. bar and confirm and cancel buttons. Among them, the price input column is used to input the current target price to be set, and the description information is used to input the description about this operation, for example, the description information can be "administrator A successfully updated the price from 3.88 euros to 5.88 euros, this price Will take effect next month", when the information in the price input field and description information input field is entered, click the OK button to confirm.

After the administrator clicks the confirmation button, it will trigger the call of the corresponding price setting interface to generate a price setting request and send it to the billing center. The price setting interface can be PUT/v1/pricing, where PUT indicates the calling method, /v1/ pricing indicates the URL (Uniform Resource Identifier) of the interface, and the price setting request includes: the resource identifier, resource type, resource price (the target price to be set currently), and the region to which it belongs (the zone to which it belongs, or the partition to which it belongs and availability zone), price unit (such as Euro, US dollar, RMB, etc.) and measurement unit (such as hour, GB or GB/hour). In addition, the price setting request may also include: operator information, description information, etc. Exemplarily, the content of the price setting request may be as shown in Table 3.

table 3

"O" in Table 3 means optional (Optional). In addition, as an example, the price setting request can be as shown in the following message example:

After the billing center receives the price setting request above, it executes the operation corresponding to the price setting request. At this time, in step 402, according to the resource pricing request, the corresponding resource pricing operation is performed on the resource pricing table. Specifically can include:

judging whether there is a price entry corresponding to the resource identifier, the resource type, and the region in the resource pricing table;

If the price entry does not exist, create the price entry, and the price entry includes the resource identifier, the resource type, the resource price, the region to which it belongs, the price unit, and the measurement unit and effective time;

If the price entry exists, modify the resource price in the price entry according to the resource price.

It can be understood that price setting requests can be divided into two types, which are Insert price and Update price. The billing center does not distinguish whether the current operation is inserting price or updating price. When the billing center receives a When adding a price request, first check whether there is a corresponding price entry in the resource pricing table according to the resource identifier in the price setting request, the resource type, and the region to which it belongs. If there is no corresponding price entry, the current operation is considered to be an insertion price , create a new price entry corresponding to the price setting request, and the newly created price entry usually includes: the resource identifier, resource type, resource price, area to which it belongs, price unit, measurement unit, and The effective time, wherein, the resource price in the newly created price entry may usually include the current price and the next month's price, and both the current price and the next month's price should be set as the resource price in the price setting request. If it exists, it is considered that the current operation is to update the price, then the current price in the existing price entry remains unchanged, and the price for the next month is changed to the resource price in the price setting request.

If the resource pricing request is the price setting request, the resource pricing response includes: an operation success message. Exemplarily, the operation success message may be a "STATUS CODE 202Accept" message.

Or, the administrator triggers and calls the corresponding delete price interface through the administrator interface to generate a delete price request and send it to the billing center. The delete price interface can be DELETE/v1/{region}/pricing/{resourceType}/{resourceName} ? az={az}, where DELETE is the calling method, the URL of the delete price interface is /v1/{region}/pricing/{resourceType}/{resourceName}? az={az}, the price deletion request includes: the resource identifier, resource type, and region to which the price is requested to be deleted (the zone to which it belongs, or the zone to which it belongs and the availability zone). Exemplarily, the content of the price setting request may be as shown in Table 4.

Table 4

After receiving the price deletion request, the billing center executes the operation corresponding to the price deletion request. At this time, the operation of setting resource pricing corresponding to the resource pricing table according to the resource pricing setting request in step 402 is specifically Can include:

Finding a price entry corresponding to the resource identifier, the resource type, and the region to which it belongs in the resource pricing table;

Mark the delete bit as delete the corresponding value in the price entry.

It can be understood that the deletion of resource pricing does not directly delete the price entry in the resource pricing table, but marks the flag of the corresponding record as "1 (deleted)", ensuring that the billing operation of the current month will not be affected.

If the resource pricing request is the deletion price request, the resource pricing response includes: an operation success message. Exemplarily, the operation success message may be a "STATUS CODE 204 Not Content" message.

Alternatively, the administrator triggers and calls the corresponding query price interface through the administrator interface to generate a price query request and send it to the billing center. The price query interface can be GET/v1/{region}/{resourceType}/pricing? resourceName={resourceName}&az={az}, where GET is the calling method, and the URL of the price query interface is /v1/{region}/{resourceType}/pricing? resourceName={resourceName}&az={az}, the price query request includes: the resource identifier, resource type and region (partition to which, or partition and availability zone) of the resource for which the price is requested. Exemplarily, the content of the price query request may be as shown in Table 5.

table 5

Exemplarily, the query price request may be as shown in the following message example:

GET /v1/region1/2/pricing? resourceName=test&az=az1

After the billing center receives the query price request, it executes the operation corresponding to the price query request. At this time, the operation of setting resource pricing corresponding to the resource pricing table according to the resource pricing request in step 402 is specifically include:

Finding a price entry corresponding to the resource identifier, the resource type, and the region to which it belongs in the resource pricing table;

Obtain the resource price, price unit, measurement unit, effective time, measurement unit and effective time in the price entry;

If the resource pricing request is the query price request, the resource pricing response includes: the resource identifier, the resource type, the resource price, the price unit, the measurement unit, and the stated effective time. Exemplarily, the resource pricing response is a response to a price inquiry request, and the content of the resource pricing response can be shown in Table 6.

Table 6

parameter name Types of illustrate ResourceID string Resource ID CurrentPrice string Current price NextMonthPrice string price next month unit string price unit MeasurementUnit string Unit of measure ActiveTime string effective time Description string Description

Exemplarily, it can be shown in the following message example:

Or, in another implementation, the query price request may not include a resource identifier, and then in step 402, according to the resource pricing request, perform the corresponding resource pricing operation on the resource pricing table Specifically include:

Finding price entries of all resources corresponding to the resource type and the region in the resource pricing table;

Obtain the resource price, price unit, measurement unit, effective time, measurement unit, and effective time in the price entries of all resources;

If the resource pricing request is the query price request, the resource pricing response includes: resource identifier, resource type, resource price, price unit, measurement unit and effective time of each resource in all resources .

At this time, the price information of at least one resource is set in the resource pricing response, where the content of the price information of each resource is the same as that in Table 6, and will not be repeated here.

It can be understood that, in order to simplify the data processing of the calling end, no distinction is made between batch query or single query, if the query price request carries resource type and resource ID at the same time in addition to the area to which it belongs, the resource ID corresponding to the resource ID will be queried For price information, if the price query request only carries the resource type and does not carry the resource identifier in addition to the region to which it belongs, the price information of all resources corresponding to the resource type under the region will be queried.

In addition, optionally, as shown in Figure 9, for performing the operation corresponding to the price setting request or the operation corresponding to the deletion price request, after step 403 is executed each time, the billing method provided by the embodiment of the present invention can also be include:

Step 404, the billing center adds a history record entry corresponding to the operation of setting resource pricing in the resource pricing operation history table.

The history record entry includes: resource type, resource identifier, region to which the operated resource belongs, operator, operation time and description information of the resource pricing operation.

Wherein, it is worth mentioning that there is no fixed order between steps 401-404 and steps 301-309, and steps 401-404 can be performed at any time.

Correspondingly, the billing method provided by the embodiment of the present invention may also include:

Step 405, the billing center receives from the administrator device. The administrator triggers and calls the corresponding operation record query interface through the administrator interface to generate an operation record query request (shown in the figure) and sends it to the billing center. The operation record query interface can be GET /v1/{region}/{resourceType}/{resourceName}/operatorLog? az={az}&startDate={startDate}&endDate={endDate}, where GET is the calling method, and the interface URL is /v1/{region}/{resourceType}/{resourceName}/operatorLog? az={az}&startDate={startDate}&endDate={endDate}. The operation record query request may include: resource identifier, resource type and region (partition to which, or partition and availability zone to which the operation record is requested to be queried), start time and end time. Exemplarily, the content of the operation record query request may be as shown in Table 7.

Table 7

After receiving the operation record query request, the billing center executes the operation corresponding to the operation record query request.

Then, the administrator device will receive an operation record query response returned by the billing center, and the response may include: operation time (operationTime) and description information (description). Wherein, the operation time is the operation time of the price item of the resource indicated by the operation record query request, and the description information is the specific content of the operation on the item. For example, if the operation record query request is as shown in the following message:

GET /v1/region1/2/testVM/operatorLog? az

=az1&startDate=2014-02-02&endDate=2014-03-02

Correspondingly, the operation record query response can be as shown in the following message:

In addition, optionally, as shown in FIG. 10, the billing method provided in this embodiment of the present invention may further include:

Step 501, the billing center receives from the administrator device a fee query request triggered by the administrator through the administrator fee query interface, and the fee query request includes the tenant ID of the tenant specified by the administrator, and the fee specified by the administrator. Query time.

Wherein, the administrator fee query interface may be a fee query interactive interface displayed on the administrator device, which is used for the administrator to realize the fee query of each tenant through the interactive interface. Exemplarily, the administrator The interface can be set with a query time input column and a tenant ID input column. After the tenant ID and query time are set, the corresponding fee query interface will be called to trigger the generation of the fee query request and send it to the billing center. The fee query interface can be GET /v1/charging/bills/total/{time}? tenantId={tenantId}, where GET is the calling method, /v1/charging/bills/total/{time}? tenantId={tenantId} is the URL of the fee query interface, and the billing center will execute steps 502-503 according to the fee query request after obtaining the fee query request. Wherein, the query time can be specified as a certain year and a certain month. Exemplarily, the content of the fee query request can be shown in Table 8.

Table 8

Step 502, the billing center queries the fee information of the specified tenant within the query time according to the tenant identifier and the query time.

Step 503, the billing center returns a charge inquiry response carrying the charge information to the administrator device.

Wherein, the fee information includes: instance usage fee, EBS usage fee, S3 usage fee, ELB usage fee, traffic usage fee, and total fee, as well as the percentage of the instance usage fee in the total fee limit of the tenant, the The percentage of the EBS usage fee to the total fee limit, the S3 usage fee to the total fee limit, the ELB usage fee to the total fee limit, and the traffic usage fee to the total fee The percentage of the limit and the percentage of the total limit of the said fee. Exemplarily, the content of the fee query response may be as shown in Table 9:

Table 9

Exemplarily, the fee query request may be as shown in the following message:

GET /billingcenter/v1/charging/bills/total/201405

Correspondingly, the fee query response can be as shown in the following message:

Finally, the administrator device that receives the fee query response displays the query result on the administrator fee query interface according to the fee query response. Optionally, the downloaded cases can also be displayed on the administrator fee inquiry interface, so that the administrator can download the inquiry results conveniently.

Or, optionally, as shown in FIG. 11 , the billing method provided in this embodiment of the present invention may further include:

Step 601: The billing center receives a fee query request triggered by the tenant through the tenant fee query interface from the tenant device, and the fee query request includes the tenant ID of the tenant and the query time specified by the tenant.

Wherein, the tenant fee query interface may be a fee query interactive interface displayed on the tenant's equipment, and is used for the tenant to realize the tenant's fee query through the interactive interface. Exemplarily, the tenant member interface can be There is an input column for query time, and when the query time is set, the corresponding fee query interface will be invoked to trigger the generation of the fee query request and send it to the billing center, and the billing center will execute steps 602-603 according to the fee query request.

Step 602, the billing center queries the fee information of the tenant within the query time according to the tenant identifier and the query time.

Step 603, the billing center returns a fee query response carrying the fee information to the tenant device, and the fee information includes: instance usage fee, EBS usage fee, S3 usage fee, ELB usage fee, traffic usage fee and total fee , and the percentage of the instance usage fee to the total fee limit of the tenant, the percentage of the EBS usage fee to the total fee limit, the percentage of the S3 usage fee to the total fee limit, the ELB usage fee The percentage of the fee to the total fee limit, the percentage of the traffic usage fee to the total fee limit, and the percentage of the total fee to the total fee limit.

Among them, except that the tenant can only query its own fee information, the contents of steps 602-603 are completely the same as the other contents of steps 502-503, and will not be repeated here.

Wherein, steps 501-503 and steps 601-603 are mutually independent processes.

Optionally, the billing method provided in the embodiment of the present invention may also include:

According to the percentage of each tenant's fee in the tenant's total fee limit, as well as each tenant's fee percentage soft limit and fee percentage hard limit, the billing center determines whether to issue an expense alarm and the alarm level for the tenant; the fee percentage The hard cap is greater than the stated fee percentage soft cap.

Exemplarily, the total cost limit of each tenant is preset, and according to the acquired cost of each tenant and the preset total cost limit, the cost of each tenant can be obtained as a percentage of the tenant's cost Percentage of total limit. The fee percentage soft limit and fee percentage hard limit are also pre-set.

For any tenant, if the fee of any tenant exceeds the soft limit of the fee percentage but does not exceed the hard limit of the fee percentage, an alarm is issued to the tenant, and the alarm level is an important alarm;

If the fee of any one of the tenants exceeds the hard limit of the fee percentage, an alarm will be issued to the tenant, and the alarm level will be an emergency alarm;

If the fee of any one of the tenants does not exceed the soft limit of the fee percentage, no alarm is issued.

Further, a floating threshold variable (upMount) can also be set, then,

For any tenant, if the fee of any tenant exceeds the soft limit of the fee percentage + the floating threshold variable, but does not exceed the hard limit of the fee percentage + the floating threshold variable, an alarm will be issued to the tenant, and the alarm level is an important alarm ;

If the cost of any of the tenants exceeds the hard limit of the cost percentage + the floating threshold variable, the tenant is alerted, and the alert level is an emergency alert;

If the fee of any tenant does not exceed the fee percentage soft limit + floating threshold variable, no alarm is issued.

In addition, if there has been any of the above-mentioned alarms before, and if the current alarm clearing condition has been reached (the fee does not exceed the soft limit of the fee percentage + the floating threshold variable), the alarm should be cleared. If it was an urgent alarm before, and the current fee is lower than the hard limit of fee percentage + floating threshold variable, but still higher than the soft limit of fee percentage + floating threshold variable, the alarm should be updated as a major alarm.

Optionally, as shown in Figure 12, the charging method provided in this embodiment of the present invention may also include:

Step 701, the billing center obtains the utilization rate of each type of resource counted by the analysis center.

Step 702, the billing center adjusts the resource price of each type of resource according to the usage rate of each type of resource and the preset price adjustment policy corresponding to the usage rate of each type of resource.

It can be understood as a dynamic pricing based on the busy/busy ratio of resources. Exemplarily, the price adjustment strategy can be preset, for example, it can be as follows:

When the resource utilization rate reaches over 70%, the price will be 10% higher than the base price;

When the resource utilization rate reaches over 80%, the price will be 20% higher than the base price;

When the resource utilization rate reaches more than 90%, no new service application will be accepted;

When the resource utilization rate is below 40%, the price will be reduced by 10% from the base price;

When the resource utilization rate is below 20%, the price will be reduced by 20% from the base price;

When the resource usage rate is below 10%, it will be used for free for a certain period of time.

Its specific implementation can include the following steps:

a. After obtaining the usage of each resource of each tenant according to the aforementioned method, sum the same resource used by each tenant to obtain the total usage of each resource, and obtain the total amount of resources of each resource;

b. Obtain the usage of each resource, which can be obtained specifically through the formula K3=K2/K1*100%, where K3 is the usage rate of a certain resource, K2 is the total usage of the resource, and K1 is the resource of the resource total amount;

c. Monitor the value of K3 and compare it with the tiered pricing threshold preset by the administrator. If the threshold is reached, the busy-busy ratio tiered pricing adjustment mechanism will be triggered;

d. K3 reaches the threshold, triggering the busy-busy ratio ladder pricing adjustment mechanism;

e. Adjust the price according to K3, and the price adjustment strategy can refer to the aforementioned price adjustment strategy;

f. Modify the pricing rules and refresh the tenant rate.

In addition, price adjustments can also be made based on other basis. For example, different prices can be set for different partitions, and tenants can be driven to use resources in different partitions through prices to achieve balanced resource utilization efficiency.

Or, tiered pricing based on big data analysis:

The analysis center conducts big data analysis on tenants' behavior and historical data, establishes KPI indicators, and realizes dynamic step-by-step price adjustments based on KPI indicators. For example, the key KPI settings are as follows:

Cloud service duration KPI: the duration of renting cloud service resources, such as the usage duration of a virtual machine and image (mirror) duration;

Cloud service traffic KPI: the specific traffic occupied by leased cloud services, such as ELB service, uplink traffic and downlink traffic;

Cloud service space KPI: the space actually used by renting cloud services, such as S3/EBS storage services, and the specific storage space (GB).

Wherein, the methods for acquiring the above KPIs are as shown in steps 301 to 305 of this embodiment, and will not be repeated here.

Furthermore, stepwise price adjustment can also be realized through the combination of one or more KPIs.

E.g:

Using the cloud service duration KPI (can be the current month), the billing center obtains the cloud service duration KPI for tiered pricing, for example:

Cloud service duration KPI>720 hours, the resource price will be reduced by 10% from the base price;

Cloud service duration KPI>1440 hours, the resource price will be reduced by 20% from the base price;

If the cloud service duration KPI is >2880 hours, the resource price will be reduced by 30% from the base price.

Another example:

Using the cloud service traffic KPI (can be the current month), the billing center obtains the cloud service traffic KPI for tiered pricing, for example:

Cloud service traffic KPI>100GB, the resource price will be reduced by 10% from the base price;

Cloud service traffic KPI>200GB, the resource price will be reduced by 20% from the base price;

If the cloud service traffic KPI is >500GB, the resource price will be reduced by 30% from the base price.

Another example:

Using the cloud service space KPI (can be the current month), the billing center obtains the cloud service space KPI for tiered pricing, for example:

Cloud service space KPI>100GB, the resource price will be reduced by 10% from the base price;

Cloud service space KPI>200GB, the resource price will be reduced by 20% from the base price;

If the cloud service space KPI is >500GB, the resource price will be reduced by 30% from the base price.

Furthermore, mixed pricing can also be carried out.

Combining multiple cloud services together for pricing, such as combining elastic cloud computing (English: Elastic ComputeCloud, referred to as: EC2) services and image services to form a comprehensive instance service, for tenants, only see the instance service cost, and more user-friendly.

Or, according to the KPI hybrid tiered pricing of multiple cloud services, for example, when the resource usage rate is below 40% and the KPI of the tenant's use of cloud services is >720 hours, the price will be reduced by 20% (10% + 10%).

The above several pricing strategies are only exemplary, including but not limited to these, and other possible pricing strategies may also be adopted, which are not listed here.

Among them, it should be noted that the various interfaces mentioned in the embodiments of the present invention are exemplary, including but not limited to this, and may also be other interfaces with the same function, which will not be listed one by one in this embodiment . In addition, the administrator device or tenant device is a device having a communication connection with the billing center, where the administrator device may be a part of the billing center or a device independent of the billing center.

An embodiment of the present invention provides a billing method. The analysis center queries the partition corresponding to each tenant according to the identifier of the tenant, and queries the available area corresponding to the tenant in each partition corresponding to each tenant, and obtains the cost of each tenant. Corresponding to at least one availability zone, also query the project corresponding to each tenant according to the tenant’s identification, so as to query the resource information of at least one resource used by the tenant under at least one availability zone corresponding to each tenant, and then for each The resource usage is counted, and finally the resource usage information of each tenant is obtained, the resource usage statistics summary table is generated, and the resource usage statistics summary table is sent to the billing center, which can be obtained according to the resource usage statistics summary table The resource usage information of each tenant determines the cost of each tenant according to the resource pricing table and the resource usage information of each tenant. It can realize hybrid billing for the resource usage of multiple cloud services, and realize hybrid billing for multi-partition and multi-cloud platforms.

The embodiment of the present invention also provides an analysis center 01, which is suitable for charging cloud service resource usage under cloud computing. As shown in FIG. 13, the analysis center 01 includes:

The query module 011 is configured to query the partition corresponding to the first tenant according to the identifier of the first tenant, and query the availability zone corresponding to the first tenant in each partition corresponding to the first tenant, and obtain the At least one availability zone corresponding to the first tenant; wherein the first tenant is any one of all tenants;

The query module 011 is further configured to query the project corresponding to the first tenant according to the identifier of the first tenant, and obtain at least one project corresponding to the first tenant;

The collection module 012 is configured to query resource information of resources used by each project in the at least one project in the at least one availability zone according to the identifier of the at least one project, and obtain at least one resource used by the first tenant. resource information for a resource;

An analysis module 013, configured to count the usage of each resource according to the resource information of the at least one resource, and obtain the resource usage information of the first tenant;

The analysis module 013 is further configured to generate a summary table of resource usage statistics according to the resource usage information of all tenants;

The interface module 014 is configured to send the resource usage statistics summary table to the billing center, so that the billing center can obtain the resource usage information of each tenant according to the resource usage statistics summary table, and according to the resource pricing table and each tenant resource usage information to determine the per-tenant charges.

Optionally, the resource information of the at least one resource includes: a resource identifier and a resource type of the at least one resource;

Wherein, the resource type includes: one of instance, image, simple storage service S3, elastic block storage EBS, elastic load balancing ELB, and traffic.

Optionally, the analysis module 013 can be specifically used for:

If the resource type of any resource in the at least one resource is an instance, count the usage time of the virtual machine corresponding to the any resource as the usage amount of the any resource according to the resource identifier of the any resource;

If the resource type of any resource is a mirror image, then according to the resource identifier of any resource, the usage time of the virtual machine corresponding to the instance to which any resource belongs is taken as the usage amount of any resource;

If the resource type of any resource is EBS, count the usage space size and usage duration of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of any resource is S3, count the usage space size and usage duration of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of any resource is ELB, count the usage time of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of the any resource is traffic, count the traffic value of the any resource corresponding to the any resource according to the resource identifier of the any resource as the usage amount of the any resource.

Optionally, from the query module to query the partition corresponding to the first tenant and the availability zone corresponding to the first tenant in each partition according to the identifier of the first tenant to the interface module to use the resource The statistical summary table is sent to the billing center as a query batch;

After the interface module sends the resource usage statistics summary table to the billing center, the next query batch is executed after a preset period of time.

Optionally, in the summary table of resource usage statistics, each resource corresponds to an entry; wherein, the entry corresponding to any resource includes: tenant ID, resource type, resource ID, resource usage, query timestamp;

Wherein, the tenant ID is the ID of the tenant using the any resource, the resource type is the resource type of the any resource, the resource ID is the resource ID of the any resource, and the resource uses The amount is the usage amount of any resource used by the tenant corresponding to the tenant ID, and the query timestamp is the time point when the resource usage amount is queried, wherein, in the same query batch, the entry corresponding to each resource The query timestamps in are the same.

This embodiment is used to implement the above-mentioned method embodiments. For the workflow and working principle of each unit in this embodiment, refer to the descriptions in the above-mentioned method embodiments, and details are not repeated here.

An embodiment of the present invention provides an analysis center. The analysis center queries the partition corresponding to each tenant according to the identifier of the tenant, and queries the available area corresponding to the tenant in each partition corresponding to each tenant, and obtains the corresponding partition of each tenant. At least one availability zone, and query the project corresponding to each tenant according to the identifier of the tenant, so as to query the resource information of at least one resource used by the tenant under at least one availability zone corresponding to each tenant, and then check the resource information of each resource The usage is counted, and finally the resource usage information of each tenant is obtained, the resource usage statistics summary table is generated, and the resource usage statistics summary table is sent to the billing center, which can obtain each tenant according to the resource usage statistics summary table The resource usage information of tenants, the cost of each tenant is determined according to the resource pricing table and the resource usage information of each tenant. It can realize hybrid billing for the resource usage of multiple cloud services, and realize hybrid billing for multi-partition and multi-cloud platforms.

The embodiment of the present invention provides a billing center 02, which is suitable for billing cloud service resource usage under cloud computing. As shown in FIG. 14, the billing center 02 includes:

The interface module 021 is used to receive the statistical summary table of resource usage sent by the analysis center;

An acquisition module 022, configured to acquire resource usage information of each tenant according to the resource usage statistics table;

The billing module 023 is used to obtain the cost of each tenant according to the resource pricing table and the resource usage information of each tenant;

The resource type of the resource includes: one of instance, image, S3, EBS, ELB, and traffic.

Optionally, each resource corresponds to an entry in the resource usage statistics summary table; wherein, the entry corresponding to any resource includes: tenant ID, resource type, resource ID, resource usage, query timestamp;

Wherein, the tenant ID is the ID of the tenant using the any resource, the resource type is the resource type of the any resource, the resource ID is the resource ID of the any resource, and the resource uses The amount is the usage amount of any resource used by the tenant corresponding to the tenant ID, and the query timestamp is the time point when the resource usage amount is queried, wherein, in the same query batch, the entry corresponding to each resource The query timestamps in are the same.

Optionally, the acquiring module 022 may be specifically used for:

determining the tenant to which each entry belongs according to the tenant identifier in each entry in the resource usage statistics summary table;

The resource usage information of each tenant is obtained according to all entries of each tenant, and the resource usage information of each tenant includes the usage amount of each resource used by each tenant.

Optionally, as shown in Figure 15, the billing module 023 may include:

A unit price query module 0231, configured to query the resource pricing table to obtain the unit price of each resource used by each tenant;

The resource billing module 0232 is configured to calculate the unit price of each resource used by each tenant according to the usage amount of each resource used by each tenant and the preset billing policy. the cost of a resource;

The tenant billing module 0233 is configured to calculate the total cost of each tenant according to the cost of each resource used by each tenant.

Optionally, the usage of each resource used by each tenant includes:

For any tenant, if the resource type of any resource used by the any tenant is an instance, the usage amount of the any resource is the usage time of the virtual machine corresponding to the any resource;

If the resource type of any resource used by any of the tenants is mirroring, the usage of any of the resources is the usage time of the virtual machine corresponding to the instance to which any of the resources belongs;

If the resource type of any resource used by any of the tenants is elastic block storage EBS, then the usage of any of the resources is the usage space and duration of usage of any of the resources;

If the resource type of any resource used by any tenant is simple storage service S3, then the usage amount of any resource is the usage space size and usage duration of any resource;

If the resource type of any resource used by any tenant is elastic load balancing ELB, the usage amount of any resource is the usage time of any resource;

If the resource type of any resource used by any tenant is traffic, the usage amount of any resource is the traffic value of any resource.

Optionally, the preset charging policy may include:

If the resource type of any resource used by any of the tenants is an instance, the fee for any of the resources used by any of the tenants is the virtual machine usage time corresponding to the any of the resources * the time of use of the any of the resources unit price;

If the resource type of any resource used by any of the tenants is mirror image, the cost for any of the resources used by any of the tenants is the usage time of the virtual machine corresponding to the instance to which any of the resources belongs * the duration of any of the resources the unit price of a resource;

If the resource type of any resource used by any of the tenants is EBS, then the fee for any of the resources used by any of the tenants is the size of the space used by any of the resources * the duration of use * the the unit price of the resource;

If the resource type of any resource used by any of the tenants is S3, then the fee for any of the resources used by any of the tenants is the size of the space used by any of the resources * the duration of use * the the unit price of the resource;

If the resource type of any resource used by any tenant is ELB, the cost for any resource used by any tenant is the usage time of any resource * the unit price of any resource ;

If the resource type of any resource used by any of the tenants is traffic, then the cost for any of the resources used by any of the tenants is the traffic value of any of the resources * the unit price of any of the resources ;

Wherein, the unit price of any resource is determined according to the resource price, price unit and measurement unit of any resource.

Optionally, as shown in FIG. 16, the billing center 02 may further include: a resource pricing management module 024;

The interface module is further configured to receive a resource pricing request triggered by the administrator through the administrator interface from the administrator device; the resource pricing request is: a price setting request, a price deletion request, and a price query request A sort of;

The resource pricing management module is configured to perform a corresponding resource pricing setting operation on the resource pricing table according to the resource pricing setting request;

The interface module is further configured to return a setting resource pricing response to the administrator device.

Optionally, the price setting request includes: the resource identifier, resource type, resource price, region to which the price is requested, the price unit, and the measurement unit of the resource for which price setting is requested;

If the resource pricing request is the new price request, the resource pricing management module 024 can be specifically used for:

judging whether there is a price entry corresponding to the resource identifier, the resource type, and the region in the resource pricing table;

If the price entry does not exist, create the price entry, and the price entry includes the resource identifier, the resource type, the resource price, the region to which it belongs, the price unit, and the measurement unit and effective time;

If the price entry exists, modify the resource price in the price entry according to the resource price;

If the resource pricing request is the price setting request, the resource pricing response includes: an operation success message.

Optionally, the price deletion request includes: the resource identifier, resource type, and region of the resource requesting price deletion;

If the resource pricing request is the deletion price request, the resource pricing management module 024 can be specifically used for:

Finding a price entry corresponding to the resource identifier, the resource type, and the region to which it belongs in the resource pricing table;

mark the delete bit as delete the corresponding value in said price entry;

If the resource pricing request is the deletion price request, the resource pricing response includes: an operation success message.

Optionally, the price query request includes: the resource identifier, resource type, and region of the resource requesting price query;

If the resource pricing request is the query price request, the resource pricing management module 024 can be specifically used to:

Finding a price entry corresponding to the resource identifier, the resource type, and the region to which it belongs in the resource pricing table;

Obtain the resource price, price unit, measurement unit, effective time, measurement unit and effective time in the price entry;

If the resource pricing request is the query price request, the resource pricing response includes: the resource identifier, the resource type, the resource price, the price unit, the measurement unit, and the stated effective time.

Optionally, the price query request includes: the resource type and region of the resource requesting the price query;

If the resource pricing request is the query price request, the resource pricing management module 024 can be specifically used to:

Finding price entries of all resources corresponding to the resource type and the region in the resource pricing table;

Obtain the resource price, price unit, measurement unit, effective time, measurement unit, and effective time in the price entries of all resources;

If the resource pricing request is the query price request, the resource pricing response includes: resource identifier, resource type, resource price, price unit, measurement unit and effective time of each resource in all resources .

Optionally, as shown in Figure 17, the billing center 02 may further include:

The record management module 025 is configured to add a history entry corresponding to the resource pricing operation in the resource pricing operation history table; the history entry includes: the resource type of the resource being operated, the resource identifier, The area to which it belongs, the operator, the operation time, and the description information of the operation of setting resource pricing.

Optionally, as shown in FIG. 18, the billing center 02 may further include: a query module 026;

The interface module 021 is further configured to receive, from the administrator device, a fee query request triggered by the administrator through the administrator fee query interface, the fee query request including the tenant identifier of the tenant specified by the administrator, and the administrator's fee query request. specified query time;

The query module 026 is used to query the fee information of the specified tenant within the query time according to the tenant identifier and the query time;

The interface module 021 is further configured to return a fee query response carrying the fee information to the administrator device, and the fee information includes: instance usage fee, EBS usage fee, S3 usage fee, ELB usage fee, traffic usage fee and the total fee, and the percentage of the instance usage fee in the total fee limit of the tenant, the percentage of the EBS usage fee in the total fee limit, the percentage of the S3 usage fee in the total fee limit, the The percentage of the ELB usage fee to the total fee limit, the percentage of the traffic usage fee to the total fee limit, and the percentage of the total fee to the total fee limit;

or,

The interface module 021 is further configured to receive a fee query request triggered by the tenant through the tenant fee query interface from the tenant device, the fee query request including the tenant ID of the tenant and the query time specified by the tenant;

The query module 026 is used to query the cost information of the tenant within the query time according to the tenant identifier and the query time;

The interface module 021 is further configured to return a fee query response carrying the fee information to the tenant device, and the fee information includes: instance usage fee, EBS usage fee, S3 usage fee, ELB usage fee, traffic usage fee, and The total fee, and the percentage of the instance usage fee to the total fee limit of the tenant, the percentage of the EBS usage fee to the total fee limit, the percentage of the S3 usage fee to the total fee limit, the The percentage of the ELB usage fee to the total fee limit, the percentage of the traffic usage fee to the total fee limit, and the percentage of the total fee to the total fee limit.

Optionally, as shown in Figure 19, the billing center 02 may further include:

The alarm module 027 is used to determine whether the fee for each tenant is determined based on the percentage of each tenant's fee in the tenant's total fee limit, and the fee percentage soft limit and fee percentage hard limit of each tenant after obtaining the fee for each tenant. The tenant issues a fee alarm and the alarm level; the hard limit of the fee percentage is greater than the soft limit of the fee percentage;

Wherein, for any tenant, if the fee of any tenant exceeds the soft limit of the fee percentage but does not exceed the hard limit of the fee percentage, an alarm is issued to the any tenant, and the alarm level is an important alarm;

If the fee of any one of the tenants exceeds the hard limit of the fee percentage, then give an alarm to any one of the tenants, and the alarm level is an emergency alarm;

If the fee of any one of the tenants does not exceed the soft limit of the fee percentage, no alarm is issued.

Optionally, as shown in FIG. 20, the billing center 02 may further include: a price adjustment module 028, and the price adjustment module 028 may be used for:

Obtain the utilization rate of each type of resource counted by the analysis center;

The resource price of this type of resource is adjusted according to the usage rate of each type of resource and the preset price adjustment strategy corresponding to the usage rate of each type of resource.

This embodiment is used to implement the above-mentioned method embodiments. For the workflow and working principle of each unit in this embodiment, refer to the descriptions in the above-mentioned method embodiments, and details are not repeated here.

An embodiment of the present invention provides a billing center. First, the analysis center queries the partition corresponding to each tenant according to the identifier of the tenant, and queries the available area corresponding to the tenant in each partition corresponding to each tenant, and obtains each At least one availability zone corresponding to the tenant, and query the project corresponding to each tenant according to the identifier of the tenant, so as to query the resource information of at least one resource used by the tenant under at least one availability zone corresponding to each tenant, and then query each Statistics on the usage of each resource, and finally obtain the resource usage information of each tenant, generate a resource usage statistics summary table, and send the resource usage statistics summary table to the billing center, which can be based on the resource usage statistics summary table. Obtain the resource usage information of each tenant, and determine the cost of each tenant according to the resource pricing table and the resource usage information of each tenant. It can realize hybrid billing for the resource usage of multiple cloud services, and realize hybrid billing for multi-partition and multi-cloud platforms.

The embodiment of the present invention also provides another analysis center 03, which is suitable for charging cloud service resource usage under cloud computing. As shown in FIG. 21, the analysis center 03 includes: a processor 031, a memory 032, and an interface 033 , the processor 031, the memory 032 and the interface 033 are connected through the bus 034, wherein the interface 033 is used to interact with other network elements, the memory 032 is used to store the computer program 0321, the processor 031 is used to execute the computer program 0321, and the processor 031 executes the computer Procedure 0321 is used to:

Query the partition corresponding to the first tenant according to the identifier of the first tenant, and query the availability zone corresponding to the first tenant in each partition corresponding to the first tenant, and obtain at least An availability zone; wherein the first tenant is any one of all tenants;

Querying the project corresponding to the first tenant according to the identifier of the first tenant to obtain at least one project corresponding to the first tenant;

Query resource information of resources used by each project in the at least one project in the at least one availability zone according to the identifier of the at least one project, and obtain resource information of at least one resource used by the first tenant;

Counting the usage of each resource according to the resource information of the at least one resource to obtain the resource usage information of the first tenant;

Generate a resource usage statistics summary table according to the resource usage information of all tenants;

Send the resource usage statistics summary table to the billing center, so that the billing center can obtain the resource usage information of each tenant according to the resource usage statistics summary table, and determine the resource usage information of each tenant according to the resource pricing table and the resource usage information of each tenant. tenant's fees.

Optionally, the resource information of the at least one resource includes: a resource identifier and a resource type of the at least one resource;

Wherein, the resource type includes: one of instance, image, S3, EBS, ELB, and traffic.

Optionally, the execution of the computer program 0321 by the processor 031 may be specifically used for:

If the resource type of any resource in the at least one resource is an instance, count the usage time of the virtual machine corresponding to the any resource as the usage amount of the any resource according to the resource identifier of the any resource;

If the resource type of any resource is a mirror image, then according to the resource identifier of any resource, the usage time of the virtual machine corresponding to the instance to which any resource belongs is taken as the usage amount of any resource;

If the resource type of any resource is EBS, count the usage space size and usage duration of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of any resource is S3, count the usage space size and usage duration of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of any resource is ELB, count the usage time of any resource as the usage amount of any resource according to the resource identifier of any resource;

If the resource type of the any resource is traffic, count the traffic value of the any resource corresponding to the any resource according to the resource identifier of the any resource as the usage amount of the any resource.

Optionally, the querying the partition corresponding to the first tenant and the availability zone corresponding to the first tenant in each partition according to the identifier of the first tenant to the sending the resource usage statistics summary table to The billing center is a query batch;

After the resource usage statistics summary table is sent to the billing center, the next query batch is executed after a preset period of time.

Optionally, in the summary table of resource usage statistics, each resource corresponds to an entry; wherein, the entry corresponding to any resource includes: tenant ID, resource type, resource ID, resource usage, query timestamp;

Wherein, the tenant ID is the ID of the tenant using the any resource, the resource type is the resource type of the any resource, the resource ID is the resource ID of the any resource, and the resource uses The amount is the usage amount of any resource used by the tenant corresponding to the tenant ID, and the query timestamp is the time point when the resource usage amount is queried, wherein, in the same query batch, the entry corresponding to each resource The query timestamps in are the same.

This embodiment is used to implement the above-mentioned method embodiments. For the workflow and working principle of each unit in this embodiment, refer to the descriptions in the above-mentioned method embodiments, and details are not repeated here.

An embodiment of the present invention provides an analysis center. The analysis center queries the partition corresponding to each tenant according to the identifier of the tenant, and queries the available area corresponding to the tenant in each partition corresponding to each tenant, and obtains the information corresponding to each tenant. At least one availability zone of each tenant, and also query the project corresponding to each tenant according to the tenant's identifier, so as to query the resource information of at least one resource used by the tenant under at least one availability zone corresponding to each tenant, and then query each resource Statistics on the usage of each tenant, and finally obtain the resource usage information of each tenant, generate a resource usage statistics summary table, and send the resource usage statistics summary table to the billing center, the billing center can obtain each tenant according to the resource usage statistics table According to the resource usage information of each tenant, the cost of each tenant is determined according to the resource pricing table and the resource usage information of each tenant. It can realize hybrid billing for the resource usage of multiple cloud services, and realize hybrid billing for multi-partition and multi-cloud platforms.

The embodiment of the present invention provides a billing center 04, which is suitable for billing cloud service resource usage under cloud computing. As shown in FIG. 22, the billing center 04 includes: a processor 041, a memory 042, and an interface 043 , the processor 041, the memory 042 and the interface 043 are connected through the bus 044, wherein the interface 043 is used to interact with other network elements, the memory 042 is used to store the computer program 0421, the processor 041 is used to execute the computer program 0421, and the processor 041 executes the computer Procedure 0421 is used to:

Receive the summary table of resource usage statistics sent by the analysis center;

Obtain resource usage information of each tenant according to the resource usage statistics table;

Obtain the cost of each tenant according to the resource pricing table and the resource usage information of each tenant;

The resource type of the resource includes: one of instance, image, S3, EBS, ELB, and traffic.

Optionally, each resource corresponds to an entry in the resource usage statistics summary table; wherein, the entry corresponding to any resource includes: tenant ID, resource type, resource ID, resource usage, query timestamp;

Wherein, the tenant ID is the ID of the tenant using the any resource, the resource type is the resource type of the any resource, the resource ID is the resource ID of the any resource, and the resource uses The amount is the usage amount of any resource used by the tenant corresponding to the tenant ID, and the query timestamp is the time point when the resource usage amount is queried, wherein, in the same query batch, the entry corresponding to each resource The query timestamps in are the same.

Optionally, the processor 041 executing the computer program 0421 may be specifically used for:

determining the tenant to which each entry belongs according to the tenant identifier in each entry in the resource usage statistics summary table;

The resource usage information of each tenant is obtained according to all entries of each tenant, and the resource usage information of each tenant includes the usage amount of each resource used by each tenant.

Optionally, the processor 041 executing the computer program 0421 may be specifically used for:

Query the resource pricing table to obtain the unit price of each resource used by each tenant;

According to the unit price of each resource used by each tenant, calculate the cost of each resource used by each tenant according to the usage of each resource used by each tenant and the preset billing policy;

Calculates the total cost per tenant based on the cost per resource used by each tenant.

Optionally, the usage of each resource used by each tenant includes:

For any tenant, if the resource type of any resource used by the any tenant is an instance, the usage amount of the any resource is the usage time of the virtual machine corresponding to the any resource;

If the resource type of any resource used by any of the tenants is mirroring, the usage of any of the resources is the usage time of the virtual machine corresponding to the instance to which any of the resources belongs;

If the resource type of any resource used by any of the tenants is elastic block storage EBS, then the usage of any of the resources is the usage space and duration of usage of any of the resources;

If the resource type of any resource used by any tenant is simple storage service S3, then the usage amount of any resource is the usage space size and usage duration of any resource;

If the resource type of any resource used by any tenant is elastic load balancing ELB, the usage amount of any resource is the usage time of any resource;

If the resource type of any resource used by any tenant is traffic, the usage amount of any resource is the traffic value of any resource.

Optionally, the preset charging policy includes:

If the resource type of any resource used by any of the tenants is an instance, the fee for any of the resources used by any of the tenants is the virtual machine usage time corresponding to the any of the resources * the time of use of the any of the resources unit price;

If the resource type of any resource used by any of the tenants is mirror image, the cost for any of the resources used by any of the tenants is the usage time of the virtual machine corresponding to the instance to which any of the resources belongs * the duration of any of the resources the unit price of a resource;

If the resource type of any resource used by any of the tenants is EBS, then the fee for any of the resources used by any of the tenants is the size of the space used by any of the resources * the duration of use * the the unit price of the resource;

If the resource type of any resource used by any of the tenants is S3, then the fee for any of the resources used by any of the tenants is the size of the space used by any of the resources * the duration of use * the the unit price of the resource;

If the resource type of any resource used by any tenant is ELB, the cost for any resource used by any tenant is the usage time of any resource * the unit price of any resource ;

If the resource type of any resource used by any of the tenants is traffic, then the cost for any of the resources used by any of the tenants is the traffic value of any of the resources * the unit price of any of the resources ;

Wherein, the unit price of any resource is determined according to the resource price, price unit and measurement unit of any resource.

Optionally, optionally, the processor 041 executing the computer program 0421 may also be used for:

Receive a resource pricing request triggered by the administrator through the administrator interface from the administrator device; the resource pricing request is: one of a price setting request, a price deletion request, and a price query request;

Execute a corresponding operation of setting resource pricing on the resource pricing table according to the request for setting resource pricing;

A set resource pricing response is returned to the administrator device.

Optionally, the price setting request includes: the resource identifier, resource type, resource price, region to which the price is requested, the price unit, and the measurement unit of the resource for which price setting is requested;

If the resource pricing request is the new price request, the processor 041 executing the computer program 0421 may be specifically used for:

judging whether there is a price entry corresponding to the resource identifier, the resource type, and the region in the resource pricing table;

If the price entry does not exist, create the price entry, and the price entry includes the resource identifier, the resource type, the resource price, the region to which it belongs, the price unit, and the measurement unit and effective time;

If the price entry exists, modify the resource price in the price entry according to the resource price;

If the resource pricing request is the price setting request, the resource pricing response includes: an operation success message.

Optionally, the price deletion request includes: the resource identifier, resource type, and region of the resource requesting price deletion;

If the resource pricing request is the deletion price request, the processor 041 executing the computer program 0421 may be specifically used to:

Finding a price entry corresponding to the resource identifier, the resource type, and the region to which it belongs in the resource pricing table;

mark the delete bit as delete the corresponding value in said price entry;

If the resource pricing request is the deletion price request, the resource pricing response includes: an operation success message.

Optionally, the price query request includes: the resource identifier, resource type, and region of the resource requesting price query;

If the resource pricing request is the query price request, the processor 041 executing the computer program 0421 may be specifically used for:

Finding a price entry corresponding to the resource identifier, the resource type, and the region to which it belongs in the resource pricing table;

Obtain the resource price, price unit, measurement unit, effective time, measurement unit and effective time in the price entry;

If the resource pricing request is the query price request, the resource pricing response includes: the resource identifier, the resource type, the resource price, the price unit, the measurement unit, and the stated effective time.

Optionally, the price query request includes: the resource type and region of the resource requesting the price query;

If the resource pricing request is the query price request, the processor 041 executing the computer program 0421 may be specifically used for:

Finding price entries of all resources corresponding to the resource type and the region in the resource pricing table;

Obtain the resource price, price unit, measurement unit, effective time, measurement unit, and effective time in the price entries of all resources;

If the resource pricing request is the query price request, the resource pricing response includes: resource identifier, resource type, resource price, price unit, measurement unit and effective time of each resource in all resources .

Optionally, the processor 041 executing the computer program 0421 may also be used for:

Add a history entry corresponding to the operation of setting resource pricing in the resource pricing operation history table; the history entry includes: the resource type, resource identifier, region, operator, and operation of the resource being operated The time and description information of the set resource pricing operation.

Optionally, the processor 041 executing the computer program 0421 may also be used for:

receiving a fee query request triggered by the administrator through the administrator fee query interface from the administrator device, the fee query request including the tenant identifier of the tenant specified by the administrator, and the query time specified by the administrator;

Querying the cost information of the specified tenant within the query time according to the tenant identifier and the query time;

Returning a fee query response carrying the fee information to the administrator device, the fee information includes: instance usage fee, EBS usage fee, S3 usage fee, ELB usage fee, traffic usage fee and total fee, and the instance usage fee The usage fee accounts for the percentage of the total fee limit of the tenant, the EBS usage fee accounts for the percentage of the total fee limit, the S3 usage fee accounts for the percentage of the total fee limit, and the ELB usage fee accounts for the fee The percentage of the total limit, the percentage of the traffic usage fee in the total limit of the fee, and the percentage of the total fee in the total limit of the fee;

or,

receiving a fee query request triggered by the tenant through the tenant fee query interface from the tenant device, the fee query request including the tenant ID of the tenant and the query time specified by the tenant;

Querying the cost information of the tenant within the query time according to the tenant identifier and the query time;

Returning a fee query response carrying the fee information to the tenant device, the fee information includes: instance usage fee, EBS usage fee, S3 usage fee, ELB usage fee, traffic usage fee and total fee, and the instance usage fee the percentage of the total fee limit for the tenant, the percentage of the EBS usage fee for the total fee limit, the percentage of the S3 usage fee for the total fee limit, and the ELB usage fee for the total fee limit. The percentage of the quota, the percentage of the traffic usage fee to the total fee limit, and the percentage of the total fee to the total fee limit.

Optionally, the processor 041 executing the computer program 0421 may be further configured to: after the billing center obtains each tenant's fee, according to the percentage of each tenant's fee in the tenant's total fee limit, and the percentage of each tenant's fee The fee percentage soft limit and fee percentage hard limit determine whether to issue a fee alarm and the alarm level for the tenant; the fee percentage hard limit is greater than the fee percentage soft limit;

Wherein, for any tenant, if the fee of any tenant exceeds the soft limit of the fee percentage but does not exceed the hard limit of the fee percentage, an alarm is issued to the any tenant, and the alarm level is an important alarm;

If the fee of any one of the tenants exceeds the hard limit of the fee percentage, then give an alarm to any one of the tenants, and the alarm level is an emergency alarm;

If the fee of any one of the tenants does not exceed the soft limit of the fee percentage, no alarm is issued.

Optionally, the processor 041 executing the computer program 0421 may also be used for:

Obtain the utilization rate of each type of resource counted by the analysis center;

The resource price of this type of resource is adjusted according to the usage rate of each type of resource and the preset price adjustment strategy corresponding to the usage rate of each type of resource.

This embodiment is used to implement the above-mentioned method embodiments. For the workflow and working principle of each unit in this embodiment, refer to the descriptions in the above-mentioned method embodiments, and details are not repeated here.

An embodiment of the present invention provides a billing center. First, the analysis center queries the partition corresponding to each tenant according to the identifier of the tenant, and queries the available area corresponding to the tenant in each partition corresponding to each tenant, and obtains each At least one availability zone corresponding to the tenant, and query the project corresponding to each tenant according to the identifier of the tenant, so as to query the resource information of at least one resource used by the tenant under at least one availability zone corresponding to each tenant, and then query each Statistics on the usage of each resource, and finally obtain the resource usage information of each tenant, generate a resource usage statistics summary table, and send the resource usage statistics summary table to the billing center, which can be based on the resource usage statistics summary table. Obtain the resource usage information of each tenant, and determine the cost of each tenant according to the resource pricing table and the resource usage information of each tenant. It can realize hybrid billing for the resource usage of multiple cloud services, and realize hybrid billing for multi-partition and multi-cloud platforms.

An embodiment of the present invention also provides a billing system, including: the analysis center 01 or 03 described in the foregoing embodiments, and the billing center 02 or 04 described in the foregoing embodiments, and may also include an analysis database and a billing database , wherein the relationship between the analysis center, billing center, analysis database, billing database, and multiple partitions is the same as the system architecture shown in FIG. 1 , and will not be repeated here.

In the several embodiments provided by the present invention, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware, or in the form of hardware plus software functional units.

The above-mentioned integrated units implemented in the form of software functional units may be stored in a computer-readable storage medium. The above-mentioned software functional units are stored in a storage medium, and include several instructions to make a computer device (which may be a personal computer, server, or network device, etc.) or a processor (processor) execute the methods described in various embodiments of the present invention. partial steps. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other various media that can store program codes. .

Those skilled in the art can clearly understand that for the convenience and brevity of description, only the division of the above-mentioned functional modules is used as an example for illustration. The internal structure of the system is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the device described above, reference may be made to the corresponding process in the foregoing method embodiments, and details are not repeated here.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than limiting them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present invention. scope.

Claims (24)

1. A charging method is suitable for charging resource usage of cloud services under cloud computing, and is characterized by comprising the following steps:

inquiring a partition corresponding to a first tenant according to the identifier of the first tenant, and inquiring an available area corresponding to the first tenant in each partition corresponding to the first tenant to obtain at least one available area corresponding to the first tenant; wherein the first tenant is any one of all tenants;

inquiring a project corresponding to the first tenant according to the identifier of the first tenant to obtain at least one project corresponding to the first tenant;

inquiring resource information of resources used by each project in the at least one project under the at least one available area according to the identifier of the at least one project to obtain the resource information of at least one resource used by the first tenant;

counting the usage amount of each resource according to the resource information of the at least one resource to obtain the resource usage information of the first tenant;

generating a resource usage statistics summary table according to the resource usage information of all tenants;

and sending the resource usage statistics summary table to a charging center so that the charging center can acquire the resource usage information of each tenant according to the resource usage statistics summary table, and determine the cost of each tenant according to a resource pricing table and the resource usage information of each tenant.

2. The method of claim 1, wherein the resource information of the at least one resource comprises: a resource identification and a resource type of the at least one resource;

wherein the resource types include: example, one of mirroring, simple storage service S3, elastic block storage EBS, elastic load balancing ELB, and traffic.

3. The method of claim 2, wherein the counting the usage amount of each resource according to the resource information of the at least one resource comprises:

if the resource type of any resource in the at least one resource is an example, counting the use duration of the virtual machine corresponding to the any resource according to the resource identifier of the any resource, wherein the use duration is used as the use amount of the any resource;

if the resource type of any resource is a mirror image, using the virtual machine usage duration corresponding to the instance to which any resource belongs as the usage amount of any resource according to the resource identifier of any resource;

if the resource type of any resource is EBS, counting the size of the use space and the use duration of any resource as the use amount of any resource according to the resource identifier of any resource;

if the resource type of any resource is S3, counting the size of the usage space and the usage duration of any resource as the usage amount of any resource according to the resource identifier of any resource;

if the resource type of any resource is ELB, counting the use duration of any resource as the use amount of any resource according to the resource identifier of any resource;

and if the resource type of any resource is flow, taking the flow value of any resource counted according to the resource identifier of any resource corresponding to any resource as the usage amount of any resource.

4. The method according to any one of claims 1-3, wherein the querying the partition corresponding to the first tenant and the available area corresponding to the first tenant in each partition according to the identifier of the first tenant until the sending of the resource usage statistics total to a charging center is a query batch;

and after the resource usage statistical summary table is sent to a charging center, executing the next query batch after a preset time interval.

5. The method of claim 4, wherein each resource corresponds to an entry in the resource usage statistics summary table; wherein, the entry corresponding to any resource includes: tenant identification, resource type, resource identification, resource usage amount and query timestamp;

the tenant identification is an identification of a tenant using any resource, the resource type is a resource type of any resource, the resource identification is a resource identification of any resource, the resource usage amount is the usage amount of any resource used by the tenant corresponding to the tenant identification, and the query timestamp is a time point for querying the resource usage amount, wherein the query timestamp in the entry corresponding to each resource is the same in the same query batch.

6. A charging method is suitable for charging resource usage of cloud services under cloud computing, and is characterized by comprising the following steps:

receiving a resource usage statistics summary table sent by an analysis center, wherein the resource usage statistics summary table is generated according to resource usage information of all tenants, wherein each resource usage information is obtained by counting the usage amount of each resource according to the resource information of at least one resource of each tenant, the resource information of at least one resource of each tenant is obtained by querying the resource information of the resource used by each project in at least one available area according to the identifier of at least one project of each tenant, at least one project corresponding to each tenant is obtained by querying the project corresponding to each tenant according to the identifier of each tenant, at least one available area corresponding to each tenant is a partition corresponding to each tenant, which is queried by the identifier of each tenant, the usable area corresponding to each tenant in each partition corresponding to each tenant is inquired;

acquiring the resource use information of each tenant according to the resource use statistical summary table;

acquiring the cost of each tenant according to the resource pricing table and the resource use information of each tenant;

the resource types of the resources include: example, one of mirroring, simple storage service S3, elastic block storage EBS, elastic load balancing ELB, and traffic.

7. The method of claim 6, wherein there is one entry for each resource in the resource usage statistics summary table; wherein, the entry corresponding to any resource includes: tenant identification, resource type, resource identification, resource usage amount and query timestamp;

the tenant identification is an identification of a tenant using any resource, the resource type is a resource type of any resource, the resource identification is a resource identification of any resource, the resource usage amount is the usage amount of any resource used by the tenant corresponding to the tenant identification, and the query timestamp is a time point for querying the resource usage amount, wherein the query timestamp in the entry corresponding to each resource is the same in the same query batch.

8. The method of claim 7, wherein the obtaining resource usage information of each tenant according to the resource usage statistics summary table comprises:

determining the tenant to which each entry belongs according to the tenant identification in each entry in the resource usage statistics summary table;

and acquiring the resource use information of each tenant according to all the entries of each tenant, wherein the resource use information of each tenant comprises the use amount of each resource used by each tenant.

9. The method of claim 8, wherein obtaining the cost of each tenant based on the resource pricing tables and the resource usage information of each tenant comprises:

inquiring the resource pricing table to obtain the unit price of each resource used by each tenant;

according to the unit price of each resource used by each tenant, calculating the cost of each resource used by each tenant according to the usage amount of each resource used by each tenant and a preset charging strategy;

the total cost of each tenant is calculated according to the cost of each resource used by each tenant.

10. The method of claim 9, wherein the usage of each resource used by each tenant comprises:

for any tenant, if the resource type of any resource used by the any tenant is an instance, the usage amount of the any resource is the usage duration of a virtual machine corresponding to the any resource;

if the resource type of any resource used by any tenant is a mirror image, the usage amount of any resource is the usage duration of a virtual machine corresponding to the instance to which any resource belongs;

if the resource type of any resource used by any tenant is EBS, the usage amount of any resource is the size of the usage space and the usage duration of any resource;

if the resource type of any resource used by any tenant is S3, the usage amount of any resource is the size of the usage space and the usage duration of any resource;

if the resource type of any resource used by any tenant is ELB, the usage amount of any resource is the usage duration of any resource;

and if the resource type of any resource used by any tenant is flow, the usage amount of any resource is the flow value of any resource.

11. The method of claim 10, wherein the preset charging policy comprises:

if the resource type of any resource used by any tenant is an instance, the cost of any resource used by any tenant is the usage duration of a virtual machine corresponding to any resource and the unit price of any resource;

if the resource type of any resource used by any tenant is a mirror image, the cost of any resource used by any tenant is the usage duration of a virtual machine corresponding to the instance to which any resource belongs and the unit price of any resource;

if the resource type of any resource used by any tenant is EBS, the cost of any resource used by any tenant is the size of the use space of any resource, the use duration and the unit price of any resource;

if the resource type of any resource used by any tenant is S3, the cost of any resource used by any tenant is the size of the usage space of any resource, the usage duration, and the unit price of any resource;

if the resource type of any resource used by any tenant is ELB, the cost of any resource used by any tenant is the using time of any resource and the unit price of any resource;

if the resource type of any resource used by any tenant is flow, the expense of any resource used by any tenant is the flow value of any resource and the unit price of any resource;

wherein the price per unit of the any resource is determined from the price per resource, the price unit, and the measure unit of the any resource.

12. The method according to any one of claims 6-11, further comprising:

acquiring the utilization rate of each type of resource counted by the analysis center;

and adjusting the resource price of each type of resource according to the utilization rate of each type of resource and a preset price adjusting strategy corresponding to the utilization rate of each type of resource.

13. An analysis center adapted to charge for resource usage of a cloud service under cloud computing, the analysis center comprising:

the query module is used for querying the partition corresponding to the first tenant according to the identifier of the first tenant, and querying an available area corresponding to the first tenant in each partition corresponding to the first tenant to obtain at least one available area corresponding to the first tenant; wherein the first tenant is any one of all tenants;

the query module is further configured to query the project corresponding to the first tenant according to the identifier of the first tenant, so as to obtain at least one project corresponding to the first tenant;

the acquisition module is used for inquiring the resource information of the resource used by each project in the at least one project under the at least one available area according to the identifier of the at least one project to obtain the resource information of the at least one resource used by the first tenant;

the analysis module is used for counting the usage amount of each resource according to the resource information of the at least one resource to obtain the resource usage information of the first tenant;

the analysis module is used for generating a resource usage statistics summary table according to the resource usage information of all tenants;

and the interface module is used for sending the resource usage statistics summary table to a charging center so that the charging center can obtain the resource usage information of each tenant according to the resource usage statistics summary table and determine the cost of each tenant according to the resource pricing table and the resource usage information of each tenant.

14. The analysis center of claim 13, wherein the resource information of the at least one resource comprises: a resource identification and a resource type of the at least one resource;

wherein the resource types include: example, one of mirroring, simple storage service S3, elastic block storage EBS, elastic load balancing ELB, and traffic.

15. The analysis center of claim 14, wherein the analysis module is specifically configured to:

if the resource type of any resource in the at least one resource is an example, counting the use duration of the virtual machine corresponding to the any resource according to the resource identifier of the any resource, wherein the use duration is used as the use amount of the any resource;

if the resource type of any resource is a mirror image, using the virtual machine usage duration corresponding to the instance to which any resource belongs as the usage amount of any resource according to the resource identifier of any resource;

if the resource type of any resource is EBS, counting the size of the use space and the use duration of any resource as the use amount of any resource according to the resource identifier of any resource;

if the resource type of any resource is S3, counting the size of the usage space and the usage duration of any resource as the usage amount of any resource according to the resource identifier of any resource;

if the resource type of any resource is ELB, counting the use duration of any resource as the use amount of any resource according to the resource identifier of any resource;

and if the resource type of any resource is flow, taking the flow value of any resource counted according to the resource identifier of any resource corresponding to any resource as the usage amount of any resource.

16. The analysis center according to any one of claims 13 to 15, wherein the resource usage statistics summary is sent to the charging center as a query batch from the query module querying the partition corresponding to the first tenant and the available area corresponding to the first tenant in each partition according to the identifier of the first tenant to the interface module;

and after the interface module sends the resource usage statistical summary table to a charging center, executing the next query batch after a preset time interval.

17. The analysis center of claim 16, wherein in the resource usage statistics summary table, there is an entry for each resource; wherein, the entry corresponding to any resource includes: tenant identification, resource type, resource identification, resource usage amount and query timestamp;

the tenant identification is an identification of a tenant using any resource, the resource type is a resource type of any resource, the resource identification is a resource identification of any resource, the resource usage amount is the usage amount of any resource used by the tenant corresponding to the tenant identification, and the query timestamp is a time point for querying the resource usage amount, wherein the query timestamp in the entry corresponding to each resource is the same in the same query batch.

18. A charging center is suitable for charging resource usage of cloud services under cloud computing, and is characterized by comprising:

an interface module for receiving a resource usage statistics summary table sent by the analysis center, wherein the resource usage statistics summary table is generated according to the resource usage information of all tenants, wherein each resource usage information is obtained by counting the usage amount of each resource according to the resource information of at least one resource of each tenant, the resource information of at least one resource of each tenant is obtained by querying the resource information of the resource used by each project in at least one available area according to the identifier of at least one project of each tenant, at least one project corresponding to each tenant is obtained by querying the project corresponding to each tenant according to the identifier of each tenant, at least one available area corresponding to each tenant is a partition corresponding to each tenant, which is queried by the identifier of each tenant, the usable area corresponding to each tenant in each partition corresponding to each tenant is inquired;

the acquisition module is used for acquiring the resource use information of each tenant according to the resource use statistical summary table;

the charging module is used for acquiring the cost of each tenant according to the resource pricing table and the resource use information of each tenant;

the resource types of the resources include: example, one of mirroring, simple storage service S3, elastic block storage EBS, elastic load balancing ELB, and traffic.

19. The billing center of claim 18, wherein there is an entry for each resource in the resource usage statistics summary table; wherein, the entry corresponding to any resource includes: tenant identification, resource type, resource identification, resource usage amount and query timestamp;

the tenant identification is an identification of a tenant using any resource, the resource type is a resource type of any resource, the resource identification is a resource identification of any resource, the resource usage amount is the usage amount of any resource used by the tenant corresponding to the tenant identification, and the query timestamp is a time point for querying the resource usage amount, wherein the query timestamp in the entry corresponding to each resource is the same in the same query batch.

20. The charging center according to claim 19, wherein the obtaining module is specifically configured to:

determining the tenant to which each entry belongs according to the tenant identification in each entry in the resource usage statistics summary table;

and acquiring the resource use information of each tenant according to all the entries of each tenant, wherein the resource use information of each tenant comprises the use amount of each resource used by each tenant.

21. The billing center of claim 20, wherein the billing module comprises:

the unit price query module is used for querying the resource pricing table to obtain the unit price of each resource used by each tenant;

the resource charging module is used for calculating the cost of each resource used by each tenant according to the unit price of each resource used by each tenant, the usage amount of each resource used by each tenant and a preset charging strategy;

and the tenant charging module is used for calculating the total charge of each tenant according to the charge of each resource used by each tenant.

22. The charging center of claim 21, wherein the usage amount of each resource used by each tenant comprises:

for any tenant, if the resource type of any resource used by the any tenant is an instance, the usage amount of the any resource is the usage duration of a virtual machine corresponding to the any resource;

if the resource type of any resource used by any tenant is a mirror image, the usage amount of any resource is the usage duration of a virtual machine corresponding to the instance to which any resource belongs;

if the resource type of any resource used by any tenant is EBS, the usage amount of any resource is the size of the usage space and the usage duration of any resource;

if the resource type of any resource used by any tenant is S3, the usage amount of any resource is the size of the usage space and the usage duration of any resource;

if the resource type of any resource used by any tenant is ELB, the usage amount of any resource is the usage duration of any resource;

and if the resource type of any resource used by any tenant is flow, the usage amount of any resource is the flow value of any resource.

23. The charging center of claim 22, wherein the preset charging policy comprises:

if the resource type of any resource used by any tenant is an instance, the cost of any resource used by any tenant is the usage duration of a virtual machine corresponding to any resource and the unit price of any resource;

if the resource type of any resource used by any tenant is a mirror image, the cost of any resource used by any tenant is the usage duration of a virtual machine corresponding to the instance to which any resource belongs and the unit price of any resource;

if the resource type of any resource used by any tenant is EBS, the cost of any resource used by any tenant is the size of the use space of any resource, the use duration and the unit price of any resource;

if the resource type of any resource used by any tenant is S3, the cost of any resource used by any tenant is the size of the usage space of any resource, the usage duration, and the unit price of any resource;

if the resource type of any resource used by any tenant is ELB, the cost of any resource used by any tenant is the using time of any resource and the unit price of any resource;

if the resource type of any resource used by any tenant is flow, the expense of any resource used by any tenant is the flow value of any resource and the unit price of any resource;

wherein the price per unit of the any resource is determined from the price per resource, the price unit, and the measure unit of the any resource.

24. The charging center according to any one of claims 18 to 23, wherein the charging center further comprises: a price adjustment module, the price adjustment module to:

acquiring the utilization rate of each type of resource counted by the analysis center;

and adjusting the resource price of each type of resource according to the utilization rate of each type of resource and a preset price adjusting strategy corresponding to the utilization rate of each type of resource.