Metering resource usage in a cloud computing environment

US9129052B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9129052-B2
Application numberUS-63023809-A
CountryUS
Kind codeB2
Filing dateDec 3, 2009
Priority dateDec 3, 2009
Publication dateSep 8, 2015
Grant dateSep 8, 2015

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

An approach that provides assigning and tracking inter-Cloud operational transactions within a Cloud computing environment in order to meter Cloud resource usage when processing a Cloud service request. In one embodiment, there is a Cloud usage and accounting tool, including a route management component configured to define and manage the physical implementation of delineation points between Clouds. The Cloud usage and accounting tool further includes a workflow control component configured to track inter-Cloud operational transactions as they pass through the delineation points.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for metering usage of a plurality of cloud resources in a cloud computing environment when processing a cloud service request, comprising: defining the physical implementation of delineation points on each cloud of a plurality of clouds in the environment, each of the delineation points comprising a network-type barrier that forms an entry point on a communication path to an associated one of the plurality of clouds for communications from another of the plurality of clouds; assigning each of a plurality of inter-cloud operational transactions to a set of delineation points for entry to and exit from a cloud, wherein the each of the plurality of inter-cloud operational transactions is a transaction that utilizes cloud services of an originating cloud and is transferred by the originating cloud to a receiving cloud, and wherein every operational transaction that is transferred from the originating cloud to the receiving cloud passes through a delineation point associated with the originating cloud and through a delineation point associated with the receiving cloud; tracking, by a delineation point for entry, each of a plurality of inter-cloud operational transactions as each transaction passes through the delineation point for entry entering a cloud; tracking, by a delineation point for exit, each of the plurality of inter-cloud operational transactions as each transaction passes through the delineation point for exit exiting a cloud; maintaining a transaction ledger in each of the plurality of clouds; calculating an amount of time each of the plurality of operational transactions was within each of the plurality of clouds; and storing the amount of time in the respective transaction ledger. 2. The method according to claim 1 further comprising: accessing a routes registry in each of the plurality of clouds, the routes registry containing information on the state of each delineation point of the respective cloud; and monitoring the state of each delineation point of each of the plurality of clouds; updating the respective routes registry when the state of at least one delineation point changes. 3. The method according to claim 2 further comprising: blocking routes into each of the plurality of clouds not having at least one delineation point; and storing blocked routes data in the respective routes registry. 4. The method according to claim 1 further comprising accessing a services registry in each of the plurality of clouds, the services registry containing availability and resources of each of the plurality of clouds. 5. The method according to method according to claim 4 further comprising: accessing availability and resources data from the services registry; accessing routing data from a routes registry; and routing the operational transaction along an available route based on at least one of the availability and resources data or the routing data. 6. The method according to claim 5 further maintaining a cloud terms registry, the cloud terms registry containing usage rates for each of the plurality of clouds. 7. The method according to claim 6 further comprising: accessing cloud usage fee rates from the cloud terms registry; accessing the amount of time within each cloud from the transaction ledger of each of the plurality of clouds for all transactions associated with a service request; and calculating a cloud usage fee for processing the service request using data. 8. A Cloud usage and accounting tool for metering cloud resource usage in a Cloud computing environment, comprising: a memory medium comprising instructions; a bus coupled to the memory medium; and a central processing unit coupled to the bus that when executing the instructions causes the Cloud usage and accounting tool to: define the physical implementation of delineation points on each cloud of a plurality of clouds in the environment, each of the delineation points comprising a network-type barrier that forms an entry point on a communication path to an associated one of the plurality of clouds for communications from another of the plurality of clouds; and wherein every operational transaction that is transferred from the originating cloud to the receiving cloud passes through a delineation point associated with the originating cloud and through a delineation point associated with the receiving cloud; assign each of a plurality of inter-cloud operational transactions to a set of delineation points for entry to and exit from a cloud, wherein the each of the plurality of inter-cloud operational transactions is a transaction that utilizes cloud services of an originating cloud and is transferred by the originating cloud to a receiving cloud; track, by a delineation point for entry, each of a plurality of inter-cloud operational transactions as each transaction passes through the delineation point for entry entering the cloud; track, by a delineation point for exit, each of a plurality of inter-cloud operational transactions as each transaction passes through the delineation point for exit exiting the cloud; maintain a transaction ledger in the cloud; calculate amount of time each of the plurality of operational transactions was within the cloud; and store the amount of time in the transaction ledger. 9. The Cloud usage and accounting tool according to claim 8 being further caused to maintain a routes registry in the cloud, the routes registry containing information on the state of each delineation point of the cloud; and monitor the state of each delineation point of the cloud; updating the routes registry when the state of at least one delineation point changes. 10. The Cloud usage and accounting tool according to claim 9 being further caused to block routes into the cloud not containing at least one delineation point; and store information relating to blocked routes in the routes registry. 11. The cloud usage and accounting tool according to claim 8 being further caused to access a services registry, the services registry containing availability and resources of each of the plurality of clouds. 12. The cloud usage and accounting tool according to claim 11 being further caused to access availability and resources data from the services registry; access routing data from a routes registry; and route operational transaction along an available route based on at least one of the availability and resources data or the routing data. 13. The cloud usage and accounting tool according to claim 12 being further caused to access a cloud terms registry, the cloud terms registry containing usage rates for the cloud. 14. The cloud usage and accounting tool according to claim 13 being further caused to access cloud usage fee rates from the cloud terms registry; access the amount of time within the cloud from the transaction ledger of the cloud; and calculate a cloud usage fee based on the data. 15. A computer-readable storage device storing computer instructions, which when executed, enables a computer system to meter usage of a plurality of cloud resources in a cloud computing environment when processing a cloud service request, comprising: define the physical implementation of delineation points on each cloud of a plurality of clouds in the environment, each of the delineation points comprising a network-type barrier that forms an entry point on a communication path to an associated one of the plurality of clouds for communications from another of the plurality of clouds, and wherein every operational transaction that is transferred from the originating cloud to the receiving cloud pas

Assignees

Inventors

Classifications

  • Monitoring of software · CPC title

  • Monitoring of transactions · CPC title

  • involving control of end-device applications over a network · CPC title

  • for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

  • Electricity · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9129052B2 cover?
An approach that provides assigning and tracking inter-Cloud operational transactions within a Cloud computing environment in order to meter Cloud resource usage when processing a Cloud service request. In one embodiment, there is a Cloud usage and accounting tool, including a route management component configured to define and manage the physical implementation of delineation points between Cl…
Who is the assignee on this patent?
Brookbanks Michael D, Coffey Brendan F, Dawson Christopher J, and 3 more
What technology area does this patent fall under?
Primary CPC classification G06F11/3419. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Sep 08 2015 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).