System and method for usage billing of hosted applications
A system, method, and computer readable medium for usage billing of one or more hosted applications serving one or more clients. The hosted applications are contained within one or more isolated environments or run without isolated environments. The system may include usage billing based on one or more of resources open, amount of data flowing through resources, number of open files, number of transactions, number of concurrent users, number of processes, CPU utilization and memory usage, The system may further include a management interface where administrators may add, remove and configure isolated environments, configure client policies and credentials, and force upgrades. If using isolated environments, the isolated environments may be isolated from other applications and the host operating system on the clients and applications within the isolated environments may run without performing an application-installation on the client.
1. A system, comprising:
one or more clients each with an operating system configured to execute applications; and
one or more billing interceptors configured to:
intercept access to resources of the one or more client operating systems; and
load into one or more address spaces of the applications or address spaces of the one or more client operating systems upon execution of each of the applications, which permits a billing manager to track billing events via the loaded billing interceptors.
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 that flows through a resource of the one or more client operating system.
3. The system according to claim 1 , wherein the one or more clients are configured to operate the billing manager that performs at least one of: profiles the applications, creates one or more billing events based on the profiled applications, and aggregates billing information.
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 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. The system according to claim 1 , further comprising at least one computing device configured to operate the billing manager.
12. The system according to claim 11 , 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 11 , wherein the billing manager inserts a client login in all billing events prior to the billing events being sent to a central billing manager.
14. The system according to claim 11 , wherein the billing manager sorts incoming billing manager events by client login and interception identifier (ID).
15. The system according to claim 11 , wherein the billing manager produces a billing summary.
16. The system according to claim 13 , wherein said billing events are sent to the billing manager using at least one of: sockets, named pipes, and an inter-process communication (IPC).
17. The system according to claim 1 , wherein the one or more billing interceptors are configured to intercept access to at least one or more of the following system resources: application execution time used, application storage used, number of open files by application, of records in a database, and number of times the application has been launched.