Patent Application
20110251937
The present invention generally relates to Cloud computing. Specifically, the present invention relates to software license brokering within a Cloud computing environment.
The Cloud computing environment is an enhancement to the predecessor grid environment, whereby multiple grids and other computation resources may be further abstracted by a Cloud layer, thus making disparate devices appear to an end-user as a single pool of seamless resources. These resources may include such things as physical or logical compute engines, servers and devices, device memory, storage devices, networks, business applications and other software, and the like.
Cloud computing and associated Cloud services are now widely available and becoming a standard services delivery mechanism for businesses of all sizes. In order to control and administer software at all layers of the Cloud stack, there is a requirement for many companies for that software to have an associated license: operating systems; middleware; databases; virtualization; and/or applications. Each of these software products operate on various levels within the Cloud architecture stack. The issue of license management in a Cloud environment is a gradually maturing area in which many challenges still exist that are not adequately addressed by current solutions.
Embodiments of the present invention provide a Cloud License Broker that that can act as an intermediary between various Clouds, providers/vendors, and end-users (consumers). The Cloud license broker will connect users (consumers) and vendors (companies) to allow for flexible access to software at all layers of the Cloud software stack, incorporating (among others): authentication and authorization with regard to the software being used; on-demand and/or pre-arranged software access for an end-user/consumer; accounting, metering, and billing that incorporates flexible discount agreements between consumers and vendors; etc. Since the software stack in a Cloud environment is most often made up of software from many vendors, the combined license management solution discussed herein takes into account how these vendors each monitor their individual license requirements and associated accounting or metering of the software and the billing requirements. In general, embodiments of the invention are based on a license broker for the Cloud, which will resolve the issues described above with a single integrated solution within a multi-vendor environment and across multiple interconnected Clouds (public, private and hybrid).
Specifically, under embodiments of the present invention, a set (at least one) of Clouds, a set of software providers, and a set of Cloud consumers (hereinafter “consumers”) are registered with a Cloud software license broker (hereinafter “broker”). Consumer information will be matched with the set of software providers to determine applicable licenses as well as pricing and usage rates. Use of software within the set of Clouds by the set of Cloud consumers will be tracked, aggregated, and reported. Based on the use, a licensing arrangement (including a price) will be determined. Applicable amounts will then be billed, and payments will be collected and disbursed (e.g., to the set of software providers) in accordance with the licensing arrangements for each software product. Under the present invention, prices/amounts can be determined based on a per-use or on-demand usage of software and/or based on use of the software over an interval of time (e.g., interval-based pricing).
A first aspect of the present invention provides a method for licensing software within a Cloud computing environment, comprising: registering a set of Clouds and a set of software providers to provide software for use via the set of Clouds; tracking a use of the software within the Cloud computing environment by a Cloud consumer; aggregating and reporting the use; and determining a licensing arrangement based on the use, the licensing arrangement comprising a price for the use of the software.
A second aspect of the present invention provides a system for licensing software within a Cloud computing environment, comprising: a memory medium comprising instructions; a bus coupled to the memory medium; a processor coupled to the bus that when executing the instructions causes the system to: register a set of Clouds and a set of software providers to provide software for use via the set of Clouds; track a use of the software within the Cloud computing environment by a Cloud consumer; aggregate and report the use; and determine a licensing arrangement based on the use, the licensing arrangement comprising a price for the use of the software.
A third aspect of the present invention provides a computer readable medium containing a program product for licensing software within a Cloud computing environment, the computer readable medium comprising program code for causing a computer to: register a set of Clouds and a set of software providers to provide software for use via the set of Clouds; track a use of the software within the Cloud computing environment by a Cloud consumer; aggregate and report the use; and determine a licensing arrangement based on the use, the licensing arrangement comprising a price for the use of the software.
A fourth aspect of the present invention provides a method for deploying a system for licensing software within a Cloud computing environment, comprising: providing a computer infrastructure being operable to: register a set of Clouds and a set of software providers to provide software for use via the set of Clouds; track a use of the software within the Cloud computing environment by a Cloud consumer; aggregate and report the use; and determine a licensing arrangement based on the use, the licensing arrangement comprising a price for the use of the software.
These and other features of this invention will be more readily understood from the following detailed description of the various aspects of the invention taken in conjunction with the accompanying drawings in which:
The drawings are not necessarily to scale. The drawings are merely schematic representations, not intended to portray specific parameters of the invention. The drawings are intended to depict only typical embodiments of the invention, and therefore should not be considered as limiting the scope of the invention. In the drawings, like numbering represents like elements.
For convenience, the Detailed Description has the following sections:
The following definitions have been derived from the “Draft NIST Working Definition of Cloud Computing” by Peter Mell and Tim Grance, dated Oct. 7, 2009, which is cited on an IDS filed herewith, and a copy of which is attached thereto.
Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This Cloud model promotes availability and is comprised of at least five characteristics, at least three service models, and at least four deployment models.
Characteristics are as follows:
On-demand self-service: A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed, automatically without requiring human interaction with each service's provider.
Broad network access: Capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Resource pooling: The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, network bandwidth, and virtual machines.
Rapid elasticity: Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured service: Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.
Service Models are as follows:
Cloud Software as a Service (SaaS): The capability provided to the consumer is to use the provider's applications running on a Cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying Cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
Cloud Platform as a Service (PaaS): The capability provided to the consumer is to deploy onto the Cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying Cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
Cloud Infrastructure as a Service (IaaS): The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying Cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
Deployment Models are as follows:
Private Cloud: The Cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.
Community Cloud: The Cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.
Public Cloud: The Cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling Cloud services.
Hybrid Cloud: The Cloud infrastructure is a composition of two or more Clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., Cloud bursting for load-balancing between Clouds).
A Cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability.
As indicated above, embodiments of the present invention provide a Cloud License Broker that can act as an intermediary between various Clouds, vendors, and end-users (consumers). The Cloud license broker will connect users (consumers) and vendors (companies) to allow for flexible access to software at all layers of the Cloud software stack, incorporating (among other): authentication and authorization with regard to the software being used; on-demand and/or pre-arranged software access for an end-user; accounting, metering, and billing that incorporates flexible discount agreements between consumers and vendors; etc. Since the software stack in a Cloud environment is most often made up of software from many vendors, the combined license management solution discussed herein takes into account how these vendors each monitor their individual license requirements and associated accounting or metering of the software and the billing requirements. In general, embodiments of the invention are based on a license broker for the Cloud, which will resolve the issues described above with a single integrated solution within a multi-vendor environment and across multiple interconnected Clouds (public, private, and hybrid).
Specifically, under embodiments of the present invention, a set (at least one) of Clouds, a set of software providers, and a set of Cloud consumers (hereinafter “consumers”) are registered with a Cloud software license broker (hereinafter “broker”). Consumer information will be matched with the set of software providers to determine applicable licenses as well as pricing and usage rates. Use of software within the set of Clouds by the set of Cloud consumers will be tracked, aggregated and reported. Based on the use, a licensing arrangement (including a price) will be determined. Applicable amounts will then be billed, and payments will be collected and disbursed (e.g., to the set of software providers) in accordance with the licensing arrangements. Under the present invention, prices/amounts can be determined based on a per use/on-demand of software and/or based on use of the software over an interval of time (e.g., interval-based pricing).
Referring now to
In Cloud computing node 10, there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed Cloud computing environments that include any of the above systems or devices, and the like.
Computer system/server 12 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules include routines, programs, objects, components, logic, data structures, and so on, that perform particular tasks or implement particular abstract data types. The exemplary computer system/server 12 may be practiced in distributed Cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed Cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.
As shown in
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.
Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.
System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of the invention.
The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store, a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radio-frequency (RF), etc., or any suitable combination of the foregoing.
Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of the invention as described herein.
Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc., one or more devices that enable a user to interact with computer system/server 12, and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via I/O interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.
Referring now to
Referring now to
Hardware and software layer 60 includes hardware and software components. Examples of hardware components include mainframes. In one example: IBM® zSeries® systems and RISC (Reduced Instruction Set Computer) architecture based servers. In one example, IBM pSeries® systems, IBM xSeries® systems, IBM BladeCenter® systems, storage devices, networks, and networking components. Examples of software components include network application server software. In one example, IBM WebSphere® application server software and database software. In one example, IBM DB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter, WebSphere, and DB2 are trademarks of International Business Machines Corporation in the United States, other countries, or both.)
Virtualization layer 62 provides an abstraction layer from which the following exemplary virtual entities may be provided: virtual servers; virtual storage; virtual networks, including virtual private networks; virtual applications; and virtual clients.
Management layer 64 provides the exemplary functions described below. Resource provisioning provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the Cloud computing environment. Metering and pricing provide cost tracking as resources are utilized within the Cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for users and tasks, as well as protection for data and other resources. User portal provides access to the Cloud computing environment for both users and system administrators. Service level management provides Cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment provides pre-arrangement for, and procurement of, Cloud computing resources for which a future requirement is anticipated in accordance with an SLA.
Workloads layer 66 provides functionality for which the Cloud computing environment is utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation; software development and lifecycle management; virtual classroom education delivery; data analytics processing; transaction processing; and software licensing. As mentioned above, all of the foregoing examples described with respect to
It is understood all functions of the present invention as described herein are typically performed by the software licensing function, which can be tangibly embodied as modules of program code 42 of program/utility 40 (
Referring now to
Secure Access, Authentication and Authorization
Vendor Registration
Consumer Registration
Software provider<->Consumer Agreements
Software Library
Broker 102 can also catalogue software for access by consumers 106A-C
Broker 102 provides requested software to consumer's 106A-C Cloud service provider on-demand
Along these lines, broker 102 would act as a third-party intermediary between the Clouds, software providers, and consumers. It is also possible to install the broker 102 within a private Cloud as a standard component that does not have outside-the-firewall Cloud providers.
Referring now to
These concepts are further shown and described in conjunction with the use case depicted in
a. A software provider 108 registers with broker 102, providing access credentials and financial transaction information.
b. Software provider 108 registers individual software packages with broker 102. Each package contains license, authorization, authentication, and pricing information, which will be managed by broker 102.
c. Software provider 108 specifies ad hoc pricing that can be used by “walk up” consumer 106As.
d. Software provider 108 registers its initial consumer 106A list, which includes license keys and rates, including volume discount information.
e. Consumer 106A registers with broker 102, providing access credentials and financial billing information.
f. Software providers register with broker 102.
g. Consumer registers with a private Cloud, for “walk up” use, no pre-registration may be necessary.
h. The broker 102 matches up consumer 106A information with all software providers 108 with which consumer 106A has agreements.
a. Consumer 106A starts using Cloud services from one or more of the software provider 108s. In each case, the Cloud connects to broker 102 to get software usage rates.
b. The Cloud reports usage rates to broker 102 on a defined interval per policy by software provider 108 requirements.
c. Broker 102 tracks usage and rates from all Clouds, public and private.
d. Consumer 106A is billed on a defined interval, specified by the service agreement with such consumer.
END920100016US1 Page 24 of 37
e. Software provider 108 is paid on a defined interval, as specified by the payment policy between the Cloud software provider 108 and the software provider 108.
Referring now to
Web Application Server software such as IBM® Websphere® web application server software (IBM, Websphere, DB2, and related terms are trademarks of IBM Corporation in the United States and/or other countries).
Database software such as IBM® DB2® database software may be used to track all metadata.
Portal software such as IBM® Websphere Portal® software for consumers 106A to obtain data and reports. Along these lines, the following license models could be supported:
These models essentially connect the software providers directly with the consumers. The Cloud provider does not have to pre-purchase licenses as part of their business model. The provider can make licenses available for usage with no parties incurring a risk. This will encourage Cloud resource availability, which will result in provider and consumer benefits. If licensing interoperability becomes a standard, this will reduce costs for providers and consumers.
These functions are summarized in the method flow diagram of
While shown and described herein as a software licensing brokering solution for a Cloud computing environment, it is understood that the invention further provides various alternative embodiments. For example, in one embodiment, the invention provides a computer-readable/useable medium that includes computer program code to enable a computer infrastructure to provide software license brokering functionality as discussed herein. To this extent, the computer-readable/useable medium includes program code that implements each of the various processes of the invention. It is understood that the terms computer-readable medium or computer-useable medium comprise one or more of any type of physical embodiment of the program code. In particular, the computer-readable/useable medium can comprise program code embodied on one or more portable storage articles of manufacture (e.g., a compact disc, a magnetic disk, a tape, etc.), on one or more data storage portions of a computing device, such as memory 28 (
In another embodiment, the invention provides a method that performs the process of the invention on a subscription, advertising, and/or fee basis. That is, a service provider, such as a Solution Integrator, could offer to provide software license brokering. In this case, the service provider can create, maintain, support, etc., a computer infrastructure, such as computer system 12 (
In still another embodiment, the invention provides a computer-implemented method for providing software license brokering functionality. In this case, a computer infrastructure, such as computer system 12 (
As used herein, it is understood that the terms “program code” and “computer program code” are synonymous and mean any expression, in any language, code, or notation, of a set of instructions intended to cause a computing device having an information processing capability to perform a particular function either directly or after either or both of the following: (a) conversion to another language, code, or notation; and/or (b) reproduction in a different material form. To this extent, program code can be embodied as one or more of: an application/software program, component software/a library of functions, an operating system, a basic device system/driver for a particular computing device, and the like.
A data processing system suitable for storing and/or executing program code can be provided hereunder and can include at least one processor communicatively coupled, directly or indirectly, to memory element(s) through a system bus. The memory elements can include, but are not limited to, local memory employed during actual execution of the program code, bulk storage, and cache memories that provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution. Input/output and/or other external devices (including, but not limited to, keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening device controllers.
Network adapters also may be coupled to the system to enable the data processing system to become coupled to other data processing systems, remote printers, storage devices, and/or the like, through any combination of intervening private or public networks. Illustrative network adapters include, but are not limited to, modems, cable modems, and Ethernet cards.
The foregoing description of various aspects of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed and, obviously, many modifications and variations are possible. Such modifications and variations that may be apparent to a person skilled in the art are intended to be included within the scope of the invention as defined by the accompanying claims.
