|Publication number||US7506021 B2|
|Application number||US 10/666,869|
|Publication date||Mar 17, 2009|
|Filing date||Sep 18, 2003|
|Priority date||Sep 30, 2002|
|Also published as||CA2405673A1, CA2405673C, US20040068565, US20090182645|
|Publication number||10666869, 666869, US 7506021 B2, US 7506021B2, US-B2-7506021, US7506021 B2, US7506021B2|
|Inventors||Michael G. Polan, Marika Joannidis, Stephen P. Roberts, John W. Stephenson, Gabi Rothenstein|
|Original Assignee||International Business Machines Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (21), Referenced by (26), Classifications (20), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention relates to the field of web services, and in particular to the provisioning of web services.
Web services are computer operations or functions that can be invoked remotely using an Internet based protocol over the web.
Communication between the client and server takes place over the Internet using standard Internet protocols. Simple Object Access Protocol (SOAP) over Hypertext Transfer Protocol (HTTP) is commonly used. A web service can be invoked from any machine that has Internet access, and the services themselves can be hosted in any data center that provides HTTP access.
As well, web services are currently defined using the Web Services Definition Language (WSDL). WSDL is a meta-description of web services. In addition to being readable by a human user, WSDL is easily read and processed by computer applications. This enables better web service client and server composition tools, as well as dynamic discovering, binding and use classes of applications.
Web services exchange data through the use of text based XML documents. These documents may be specified in a fashion that is computer language and computer platform neutral. As a result, web services may be invoked from any client to any server without requiring the client and server to utilize the same language or operating system.
Web Services Flow Language (WSFL) is a standard that supports the composition of web services into business process models. It does this by capturing the orchestration and choreography of a given composition of services.
Many computer applications exist for the modeling of business processes. These applications enable the creation of the models to automate the business process. The modeled processes are called workflows. The component of an application, which performs the process automation, is called a workflow engine.
Certain web services, particularly those for which fees and financial accounts are involved typically require significant provisioning or preparation of associated resources.
Accordingly, the inventors have recognized the need to provide systems and methods for provisioning web services.
An aspect of the present invention is directed towards a web service provisioning system for provisioning at least one web service.
The provisioning system includes a subscription system having web service description data correlated to the at least one web service, and provisioning processes data correlated to the at least one web service. The provisioning system also includes an invocation system operatively coupled to the subscription system.
The provisioning system may also include a service catalog system configured to select at least one web service. The service catalog system may also be configured to determine user profile data. Preferably, the invocation system includes a workflow execution engine configured to receive user profile data and provisioning processes data, and configured to invoke provisioning processes data.
Another aspect of the present invention is directed towards a method of provisioning at least one web service, the method comprising the following steps:
Embodiments of the present invention will now be described, by way of example only, With reference to the following drawings, in which like reference numerals refer to like parts and In which:
The procedure used to complete a task within a business is called a business process. Consider the process followed when a request to purchase a stock is performed over the phone. The customer representative (CR) first verifies the identity of the caller who is requesting the purchase, and finds the customer account. Next the CR forwards the request to the trader to make the purchase. Once completed, a confirmation of the purchase must be provided back to the customer, and the customer's account debited for the cost of the transaction. There maybe an approval step involved, for example if the purchase was for a significant number of shares, or for an amount that exceeded the customer's current account balance.
A business process can be represented with a process description language. If the steps of the process can be automated, a program that can interpret the process description language may be used to manage the process from start to completion. A description that represents a business process is often referred to as a workflow.
Consider the process to purchase stocks on behalf of a customer described above. Each of the steps of that process could be implemented as a web service that can be invoked remotely via the Internet. Such a complex process could be described as a composition of web services. As will be understood by one skilled in the art, the Web Services Flow Language (WSFL) can be used to represent compositions of web services.
A simple web service could be developed to determine a stock quote: getStockQuote(String symbol);
A service of this type is a remote procedure call (RPC) that would be invoked by a client application. As will be understood, the stock “symbol” is a parameter which is required to invoke the procedure call. A typical implementation of this web service would be the conversion of the request into a proprietary call over a local connection to retrieve the current stock price from an application which keeps track of stock prices. The result would be converted back to SOAP format and returned to the client application.
Such a web service can be invoked without requiring information about the identity of the caller. As noted, the only required parameter is the stock symbol. Many organizations offer this type of web service free of charge.
Consider now the implementation of a web service that is used to purchase a stock. This call might appear as:
purchaseStock(String symbol, String accountID, Int numberOfShares);
In this example, the required parameters include the referenced account (“accountID”). The account must be known to the system providing the web service beforehand, in order to verify the account information and to assign the ownership of the purchased stocks appropriately. Typically, a commission would be charged against the account (often based on the value of the stock purchased), in addition to a fixed charge for using the web service.
Accordingly, before a customer can use the purchaseStock web service, an account must be established for that customer, and other information such as the customer's name and address must be provided. The data center network infrastructure must be configured to route the web service requests and responses appropriately. These steps are a business process. Configuring a system with account and other information sufficient to allow a particular consumer to access a particular web service is referred to as “provisioning”.
The components 12 of the web service system 10 may include a Security System 20 or module, which will need to be provided with a user identity and/or password in order to authenticate the consumer 14 when using the web service 16. The Security System 20 will also often require a list of the system 10 resources to which the consumer 14 will need access to use the web service 16. A Billing System 22 or module may also be required in order to charge the consumer 14 for the use of the web service 16. Accordingly, the Billing System will need to be provisioned with a billing account for that consumer 14. A User Profile System 24 or module is also common. Typically, the User Profile System 24 will be provisioned with and record personal information or user profile data about the consumer, such as the consumer's name, address and phone number. While not shown, other components will often require provisioning for elaborate commercial web services.
As will be understood, the steps in the provisioning process for the web service system 10 would typically include: configuring the Security System 20 with the consumer's 14 identity and/or password; creating an account for the consumer 14 in the Billing System 22; storing the consumer's 14 user profile data in the User Profile System 24; and informing the component providing the web service 16 that the consumer 14 is ready to access the web service 16.
The subscription system 110 includes a service catalog system or module 114, as well as a web service provisioning database 116. The provisioning database 116 contains web service description data 118 (ie. a WSDL description correlated to each web service 16), and WSFL provisioning process (or workflow) data 120 corresponding to the web service steps required for provisioning each web service 16. The service catalog module 114 is configured to present to the user 14 each of the available web services (including web service 16), as well as the correlated WSDL description for each available web service. Through the service catalog module 114, the user 14 may then select one or more desired web services 16.
The service catalog module 114 is also configured to determine and store user profile data 122 (shown on
Once the user has selected a web service 16, the service catalog module 110 passes the WSFL provisioning process data 120 correlated to the web service 16, as well as the user profile data 122, to the invocation system 112. Typically, the WSFL provisioning process data 120 and the user profile data 122 are stored and transferred as text based XML documents.
As illustrated in
By way of example only, the following illustrates a simple provisioning workflow. The first node 134 may be designed to invoke a web service which establishes a user identity and/or password on the security system 20 corresponding to the consumer 14. Similarly, the second node 136 may invoke a web service for storing the user profile data 122 in the user profile system 24. The third node 138 may invoke a web service for creating a billing account corresponding to the user 14 on the billing system 22. A fourth node 140 may also be required to invoke a web service for informing the component providing the web service 16 that the consumer 14 is ready to access the web service 16. As noted previously, however, a comprehensive commercial web service system 10 may include other components which require provisioning, and which will result in additional corresponding nodes 132 in the provisioning process data 120.
As will be understood, one or more of the nodes 132 in a provisioning process may be interruptible. Such interruptible workflow steps may require decision-making or other human interaction by the service provider. For example, an interruptible workflow step or node 132 may be provided which allows the service provider to determine if the web service 16 for a particular user 14 will be operate on a fast server or a slower one, possibly based on the user's 14 anticipated requirements.
Referring now to
Thus, while what is shown and described herein constitutes preferred embodiments of the subject invention, it should be understood that various changes can be made without departing from the subject invention, the scope of which is defined in the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5930777||May 23, 1997||Jul 27, 1999||Barber; Timothy P.||Method of charging for pay-per-access information over a network|
|US6026365||Aug 18, 1997||Feb 15, 2000||Fuji Xerox Co., Ltd.||Workflow support system and method of the same|
|US6349238||Sep 16, 1998||Feb 19, 2002||Mci Worldcom, Inc.||System and method for managing the workflow for processing service orders among a variety of organizations within a telecommunications company|
|US6633907 *||Sep 10, 1999||Oct 14, 2003||Microsoft Corporation||Methods and systems for provisioning online services|
|US20020194045 *||Apr 30, 2002||Dec 19, 2002||Izhar Shay||System and method for automatically allocating and de-allocating resources and services|
|US20030036917 *||Apr 25, 2002||Feb 20, 2003||Metallect Corporation||Service provision system and method|
|US20030041131 *||Apr 23, 2002||Feb 27, 2003||Microsoft Corporation||System and method to automate the management of computer services and programmable devices|
|US20030055624 *||Sep 19, 2001||Mar 20, 2003||International Business Machines Corporation||Dynamic, real-time integration of software resources through services of a content framework|
|US20030055878 *||Sep 19, 2001||Mar 20, 2003||International Business Machines Corporation||Programmatic management of software resources in a content framework environment|
|US20030061404 *||Sep 23, 2002||Mar 27, 2003||Corel Corporation||Web services gateway|
|US20030084177 *||Oct 26, 2001||May 1, 2003||Nokia Corporation||Mobile client provisioning web service|
|US20030105864 *||Jan 11, 2002||Jun 5, 2003||Michael Mulligan||Network services broker system and method|
|US20030120502 *||Apr 23, 2002||Jun 26, 2003||Robb Terence Alan||Application infrastructure platform (AIP)|
|US20030135628 *||Jan 15, 2002||Jul 17, 2003||International Business Machines Corporation||Provisioning aggregated services in a distributed computing environment|
|US20030163513 *||Feb 22, 2002||Aug 28, 2003||International Business Machines Corporation||Providing role-based views from business web portals|
|US20030210657 *||Dec 24, 2002||Nov 13, 2003||Sanjeev Mahajan||Data based over the air provisioning for wireless services|
|US20040034540 *||Aug 15, 2002||Feb 19, 2004||Commerce One Operations, Inc.||Dynamic interface between BPSS conversation management and local business management|
|EP1009175A2||Aug 31, 1999||Jun 14, 2000||Nortel Networks Corporation||Method and system for HLR access over an IP network|
|JP2000358282A||Title not available|
|WO1999033228A1||Dec 22, 1998||Jul 1, 1999||Mediaone Group, Inc.||Auto-provisioning of user equipment|
|WO2001080083A1||Apr 10, 2001||Oct 25, 2001||Gensym Corporation||Intelligent transaction mining system|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7925554||Dec 29, 2006||Apr 12, 2011||Amazon Technologies, Inc.||Using configured application pricing to determine end user fees for use of invocable services|
|US8055586 *||Dec 29, 2006||Nov 8, 2011||Amazon Technologies, Inc.||Providing configurable use by applications of sequences of invocable services|
|US8307003 *||Apr 3, 2009||Nov 6, 2012||Amazon Technologies, Inc.||Self-service control environment|
|US8335765||Oct 26, 2009||Dec 18, 2012||Amazon Technologies, Inc.||Provisioning and managing replicated data instances|
|US8433822 *||Mar 9, 2005||Apr 30, 2013||Research In Motion Limited||System, method and apparatus for optimized wireless messaging|
|US8612396||Sep 15, 2012||Dec 17, 2013||Amazon Technologies, Inc.||Cloning and recovery of data volumes|
|US8631283||Nov 10, 2011||Jan 14, 2014||Amazon Technologies, Inc.||Monitoring and automated recovery of data instances|
|US8676753||Oct 26, 2009||Mar 18, 2014||Amazon Technologies, Inc.||Monitoring of replicated data instances|
|US8706764||Sep 15, 2012||Apr 22, 2014||Amazon Technologies, Inc.||Control service for relational data management|
|US8713060||Mar 31, 2009||Apr 29, 2014||Amazon Technologies, Inc.||Control service for relational data management|
|US8713061||Sep 15, 2012||Apr 29, 2014||Amazon Technologies, Inc.||Self-service administration of a database|
|US8713091 *||Oct 3, 2008||Apr 29, 2014||Microsoft Corporation||Network based JIT on a priori knowledge of a set of disparate clients|
|US9044504||Mar 24, 2011||Jun 2, 2015||Amazon Technologies, Inc.||Using configured application pricing to determine end user fees for use of invocable services|
|US9135283||Oct 7, 2009||Sep 15, 2015||Amazon Technologies, Inc.||Self-service configuration for data environment|
|US9207984||Mar 31, 2009||Dec 8, 2015||Amazon Technologies, Inc.||Monitoring and automatic scaling of data volumes|
|US9218245||Oct 25, 2013||Dec 22, 2015||Amazon Technologies, Inc.||Cloning and recovery of data volumes|
|US9298728||Nov 25, 2013||Mar 29, 2016||Amazon Technologies, Inc.||Failover and recovery for replicated data instances|
|US9336292||Sep 15, 2012||May 10, 2016||Amazon Technologies, Inc.||Provisioning and managing replicated data instances|
|US20060205420 *||Mar 9, 2005||Sep 14, 2006||Research In Motion Limited||System, method and apparatus for optimized wireless messaging|
|US20100088359 *||Oct 3, 2008||Apr 8, 2010||Microsoft Corporation||Network based jit on a priori knowledge of a set of disparate clients|
|US20100250748 *||Mar 31, 2009||Sep 30, 2010||Swaminathan Sivasubramanian||Monitoring and Automatic Scaling of Data Volumes|
|US20100251242 *||Mar 31, 2009||Sep 30, 2010||Swaminathan Sivasubramanian||Control Service for Relational Data Management|
|US20100251339 *||Mar 31, 2009||Sep 30, 2010||Mcalister Grant Alexander Macdonald||Managing Security Groups for Data Instances|
|US20110083138 *||Oct 7, 2009||Apr 7, 2011||Swaminathan Sivasubramanian||Self-service configuration for data environment|
|US20110099146 *||Oct 26, 2009||Apr 28, 2011||Mcalister Grant Alexander Macdonald||Monitoring of replicated data instances|
|US20110099147 *||Oct 26, 2009||Apr 28, 2011||Mcalister Grant Alexander Macdonald||Provisioning and managing replicated data instances|
|U.S. Classification||709/201, 719/328, 709/225, 709/230, 719/330, 709/223, 709/229, 709/221|
|International Classification||H04L12/16, G06F3/00, G06Q30/00, G06F9/46, G06F15/16, G06F9/44, G06F15/177, G06F13/00|
|Cooperative Classification||G06Q30/02, G06Q30/0601|
|European Classification||G06Q30/02, G06Q30/0601|
|Sep 18, 2003||AS||Assignment|
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:POLAN, MICHAEL G.;JOANNIDIS, MARIKA;ROBERTS, STEPHEN P.;AND OTHERS;REEL/FRAME:014533/0895
Effective date: 20020727
|Oct 29, 2012||REMI||Maintenance fee reminder mailed|
|Jan 28, 2013||FPAY||Fee payment|
Year of fee payment: 4
|Jan 28, 2013||SULP||Surcharge for late payment|
|Jul 18, 2016||FPAY||Fee payment|
Year of fee payment: 8