System and Method for Usage Billing of Hosted Applications

1. A system, comprising: one or more memory locations configured to provide isolated environments comprising application files and executables on one or more hosts with host operating systems; one or more servers hosting the isolated environments and their hosted applications; and one or more billing interceptors configured to: intercept access to one or more host operating system resources and interfaces; load when the hosted applications are loaded; operate at or above the host operating systems level; and load into the address spaces of each of the hosted applications without requiring any application customizations.

2. The system according to claim 1 , wherein the billing interceptors intercept at least one of: a number of resources open, a number of open files, a number of transactions, a number of concurrent users, a number of processes, and an amount of data flowing through a resource.

3. The system according to claim 1 , further comprising a billing manager for each hosted application within an isolated environment of said isolated environments, wherein the billing manager performs at least one of: profiles the applications, creates one or more billing events based on said profiling of the applications, and aggregates billing information within the isolated environment.

4. The system according to claim 3 , wherein the billing manager profiles at least one of: CPU time, memory usage, and a number of times each application is launched.

5. The system according to claim 3 , wherein the billing interceptors create billing events comprising at least one of: a usage count and an amount of data processed.

6. The system according to claim 5 , wherein said billing events are forwarded to the billing manager.

7. The system according to claim 6 , wherein the billing events are forwarded using at least one of: sockets, named pipes, and an inter-process communication (IPC).

8. The system according to claim 3 , wherein the billing manager's aggregated billing information is placed in a billing events memory storage location and forwarded to an aggregation subsystem of the billing manager.

9. The system according to claim 3 , further comprising a memory buffer configured to receive incoming billing events.

10. The system according to claim 3 , wherein the billing manager aggregates billing events based on usage of at least one application.

11. A system, comprising: at least one memory location configured to store isolated environments comprising one or more application files and executables on one or more hosts with host operating systems; one or more servers hosting the isolated environments and their applications; one or more billing interceptors configured to: intercept access to one or more host operating system resources and interfaces; load when the hosted applications are loaded; operate at or above the host operating systems level; and bad into the address spaces of each of the hosted applications without requiring any application customizations; and at least one central computing device configured to operate a central billing manager.

12. The system according to claim 11 , further comprising at least one billing manager for each application within one of the isolated environments of said isolated environments, wherein the billing manager performs at least one of: aggregates all received billing events into one or more billing manager events and adds a client login to the billing manager events.

13. The system according to claim 12 , wherein the billing manager inserts a client login in all billing events prior to sending the billing manager events to the central billing manager.

14. The system according to claim 11 , wherein the central billing manager sorts incoming billing manager events by client login and interception identifier (ID).

15. The system according to claim 11 , wherein the central billing manager produces a billing summary in one of XML, Microsoft Excel and a custom export format.

16. The system according to claim 13 , wherein said billing events are sent to the central billing manager using at least one of: sockets, named pipes, and an inter-process communication (IPC).

17. The system according to claim 11 , wherein one or more metrics are used to determine application usage, the one or more metrics comprise at least one of: time used, storage used, number of open files, number of records in a database, and number of times the application has been launched.

18. The system according to claim 11 , wherein the billing manager tracks billing manager events via the billing interceptors.

19. The system according to claim 11 , wherein the billing interceptors intercept at least one of a number of resources open, a number of open files, a number of transactions, a number of concurrent users, a number of processes, and an amount of data flowing through a resource.

20. The system according to claim 12 , wherein the billing manager profiles the applications, creates one or more billing events based on said profiling of the applications, and aggregates billing information.