|Publication number||US7613817 B2|
|Application number||US 10/466,937|
|Publication date||Nov 3, 2009|
|Filing date||Mar 14, 2002|
|Priority date||Apr 4, 2001|
|Also published as||CA2436888A1, CA2436888C, CN1243428C, CN1505884A, DE60204683D1, DE60204683T2, EP1388084A2, EP1388084B1, US20040073661, US20080249904, WO2002082305A2, WO2002082305A3|
|Publication number||10466937, 466937, PCT/2002/2815, PCT/EP/2/002815, PCT/EP/2/02815, PCT/EP/2002/002815, PCT/EP/2002/02815, PCT/EP2/002815, PCT/EP2/02815, PCT/EP2002/002815, PCT/EP2002/02815, PCT/EP2002002815, PCT/EP200202815, PCT/EP2002815, PCT/EP202815, US 7613817 B2, US 7613817B2, US-B2-7613817, US7613817 B2, US7613817B2|
|Inventors||Wolfgang Eibach, Matthias Gruetzner, Dietmar Kuebler|
|Original Assignee||International Business Machines Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (7), Non-Patent Citations (1), Referenced by (8), Classifications (20), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates generally to computer systems and more particular to the access counting, and billing mechanism for Web-Services based on a SOAP-communication protocol.
A new technology currently evolves in the Internet, the so called Web-Services. Web-Services may be defined as providing existing or new e-business services into a service-oriented architecture (SOA). These Web-Services are normally offered by independent Service-Providers to support other Internet user in managing their Internet activities. Examples of such services may be tax calculation for an online shop, payment handling for internet shops, or document translation into various languages. To support these Web-Services in the Internet, a new architecture was defined, SOA, the Service Oriented Architecture. This new architecture describes how a Web-Service may be found by user, how a potential user can access such Web-Services, and a language describing
The communication protocol for these Web-Services is also a new defined protocol, called SOAP which stands for Simple Object Access Protocol.
SOAP is a way for a program running in one kind of operating system to communicate with a program in the same or another kind of an operating system by using preferably the World Wide Web's Hypertext Transfer Protocol (HTTP) and its Extensible Markup Language (XML) as the mechanisms for information exchange. Since Web protocols are installed and available for use by all major operating system platforms, HTTP and XML provide an already at-hand solution to the problem of how programs running under different operating systems in a network can communicate with each other. SOAP specifies exactly how to encode an HTTP header and an XML file so that a program in one computer can call a program in another computer and pass it information. It also specifies how the called program can return a response.
The basic architecture of SOAP is shown in
The Service-Providers publish the availability of their Web-Services, the Service-Brokers register and categorize the published Web-Services and provide search services, and the Service Requesters using Service-Broker to find a needed Web-Service and then employing that Web-Service.
A typical SOAP-communication architecture as used by the prior art is shown in
Service-Provider offers a Web-Service e.g. a tax-calculation service. Service-Providers publish their Web-Service to Service-Broker. The Service-Provider knows the semantics of the Web-Service and publishes it in the right category in the Service-Broker's taxonomy. What is published by the Service-Provider to the Service-Broker is called service description. Service descriptions are XML documents that describes the semantics and the message API (Application Programming Interface) of a certain Web-Service. For example, the service description for a tax calculation program may include price of the service, availability, functionality, URL, IDL and so on. IDL, or Interface-Definition-Language, defines the input and output data required by that Web-Service. Service requesters, knowing the Web-Service they need, ask the Service-Broker for a list of services in that category. A Service-Requester receives by SOAP-Find response a service description for the requested Web-Service. The Service Requester uses the IDL for converting the input data format generated by the shopping application into a data format required by Web-Service and sends a SOAP-request containing the converted input data to the Web-Service. The Web-Service returns a SOAP response containing the result (output data), e.g. tax result, to the Service Requester.
The SOAP-architecture as discussed above does not address at all the aspect of charging of the new Web-Services. As far as new Web-Services are offered by the Internet today they are either free or financed by commercials.
At present there is no generalized charging model for the SOAP-Web-Service architecture allowing Service-Provider to charge their Web-Services.
It is therefore object of the present invention to provide a generalized charging model for Web-Services which may integrated very easily in the present SOAP architecture.
This object is solved by the features of the independent claims. Further preferred embodiments of the present invention are laid down in dependent claims.
The present invention discloses a system and method for counting Web-Services by means of a Resource-Counter Service offered as an own, independent Web-Service based on a SOAP communication architecture as well as a system and method for using the result of the Resource-Counter Service for calculation of a charge based on the SOAP-communication protocol. The Resource-Counter Service may be accessed by all Service-Provider having access to the service description of the Resource-Counter Service. The service description for the Resource-Counter Service may be preferably created and published by the Service-Provider, categorized by the Service-Broker, and can be found and used to invoke the Resource-Counter Service by all Web-Service-Provider using a charging model. The Resource-Counter Service mainly provides the functionality to create all necessary data allowing calculation of the charge for the use of a Web-Service, e.g. begin time for service, end time for service. The final calculation of the charge itself may be done by a separate specific accounting and bill presentment component which may be also implemented as an extension to the Resource-Counter Service. In addition to bill presentment and calculating charges, the data of the Resource-Counter Service can be used to trigger any kind of electronic payment process. The data of the Resource-Counter can be mapped to different rating models. It therefore supports multiple Service providers with their different business models. Finally, the Resource-Counter Service may provide further functionalities in connection with charging a Web-Service, e.g. create Service Requester accounts and contracts, provide a set of accounting model templates.
The interaction diagram shows a method for execution of a Web-Service at an Application Service Provider machine (ASP) using a HTTP/SOAP based communication protocol. The requested Web-Service is not free of charge, and therefore the Resource-Counter Service is invoked for counting.
The Service Requester sends a HTTP-logon request to the ASP 1. The ASP returns an authentication request 2. For example ASP sends an authentication request containing a random number to the Service Requester. The Service Requester uses its secret key and cryptographic algorithm to encrypt the random number. The Service Requester sends a response to the ASP containing the encrypted random number along with identifying information. The ASP uses the identifying information to retrieve the secret for the Service Requester from its database.
It uses this key to encrypt the same random number sent to the Service-Provider using the same algorithm as the Service Requester. ASP compares the encrypted random number returned by the Service Requester with the result of its own encryption process. If these numbers are the same, then the Service Requester is authentic and is allowed to access the requested Web-Service.
The Service requester, especially its SOAP client, creates a HTTP/SOAP Bind request using the service description for the requested Web-Service preferably provided by a Service-Broker and send the HTTP/SOAP Bind request to the ASP 4. The HTTP/SOAP Bind request is then forwarded to the Application server and SOAP server 5. The SAOP server requests to create an instance of the requested Web-Service 6. The SOAP client creates a HTTP/SOAP request for invoking the Resource-Counter Service using the service description of the Resource-Counter Service preferably provided by the Service-Broker and sends a HTTP/SOAP request to the SOAP server of the Resource-Counter Service 7. Preferably step 7 may be executed only if an additional authentication method for the Service-Provider as explained above has been performed. Then, the Resource-Counter Service is started 8. SOAP server sends HTTP/SOAP response to the requester indicating “Resource-Counter Service started” 8. Now the requested Web-Service is executed 10. When the Web-Service is completed 11, the SOAP client of the Service-Provider sends a HTTP/SOAP request to the Resource-Counter Service to stop counting 12 Then, the Resource-Counter Service is stopped 13. The Resource-Counter Service returns a response to the Service-Provider “Resource-Counter Service stopped” 15. Service-Provider, especially its SOAP server returns a response to the Service Requestor: Service completed, return result.
The following is a sample SOAP request message which can be used to record a client begin time:
<binding name=“AServiceBinding” ......>
The soap:binding binds the Service Requester to the Resource-Counter Service Service-Provider and defines the type of SOAP message and the transport protocol. The Service Requestor identifies himself in the soap:header element, where the ServiceRequesterId is passed to the Service-Provider. This is a sample where this information is passed in the soap:header element. The soap header is an optional part of a SOAP message, and if not available, the ServiceRequesterId may also be passed as part of the soap:body element. The soap:body element carries the actual request to the Resource-Counter Service server, e.g. the client ID, the begin time e.t.c.
The accounting application requests accounting of the Service Requester (client x) (1).
SOAP client sends a HTTP/SOAP request to the SOAP Server of the Resource-Counter Service requesting a usage report for client x for a timeframe y 2. The SOAP Server receives the accounting data for the requested timeframe from the data base 3. SOAP server returns a HTTP/SOAP response with the accounting data to the accounting application 4. Application produces a bill for client x based on the accounting data received from the Resource-Counter Service and the charging model for client x 5. Bill is sent to client x, e.g. e-mail. The bill creation may also be implemented as an extension to the Resource-Counter Service Service.
In that case the Service-Provider will only request the bill and the above disclosed method will be performed at the Resource-Counter Service Service.
In addition to bill presentment and calculating charges, the data of the Resource-Counter Service can be used to trigger any kind of electronic payment process. The data of the Resource-Counter can be mapped to different rating models. It therefore supports multiple Service providers with their different business models.
In summary, the Resource-Counter Service may provide following services:
accounting data for calculating service charge, e.g. record user begin time for the service, record user end time of the service, report total resource usage for a specific user, report used services statistic per user
create Service Requester accounts (e.g. ad-hoc or by contract)
create Service-Provider contracts
answer queries if USERID is allowed for a requested service at this time
maintain Service Requester accounts provide a set of accounting model templates.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5794221 *||Jul 7, 1995||Aug 11, 1998||Egendorf; Andrew||Internet billing method|
|US5960409||Oct 11, 1996||Sep 28, 1999||Wexler; Daniel D.||Third-party on-line accounting system and method therefor|
|US6047051 *||Jun 24, 1997||Apr 4, 2000||Nokia Telecommunications Oy||Implementation of charging in a telecommunications system|
|US20030053459 *||Mar 30, 2001||Mar 20, 2003||Lev Brouk||System and method for invocation of services|
|JP2000031230A||Title not available|
|JPH09146129A||Title not available|
|WO1997003410A1||Jun 6, 1996||Jan 30, 1997||Andrew Egendorf||Internet billing method|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7908286 *||Dec 8, 2004||Mar 15, 2011||Oracle International Corporation||Techniques for providing XQuery access using web services|
|US8375043||Jan 19, 2011||Feb 12, 2013||Oracle International Corporation||Techniques for providing XQuery access using web services|
|US8874745 *||Mar 26, 2010||Oct 28, 2014||Fujitsu Limited||Method and system for providing services|
|US9044504 *||Mar 24, 2011||Jun 2, 2015||Amazon Technologies, Inc.||Using configured application pricing to determine end user fees for use of invocable services|
|US20060122982 *||Dec 8, 2004||Jun 8, 2006||Oracle International Corporation||Techniques for providing XQuery access using web services|
|US20110113061 *||Jan 19, 2011||May 12, 2011||Oracle International Corporation||Techniques for providing xquery access using web services|
|US20110225074 *||Jun 18, 2010||Sep 15, 2011||Microsoft Corporation||System and method for providing information as a service via web services|
|US20110238837 *||Mar 26, 2010||Sep 29, 2011||Fujitsu Limited||Method and System for Providing Services|
|U.S. Classification||709/231, 709/233, 709/232|
|International Classification||G06Q30/00, G06F15/00, H04L29/08, H04L29/06, G06F21/00, G06F15/16, G06F17/00|
|Cooperative Classification||H04L69/329, H04L67/02, G06Q30/04, H04L29/06, G06Q30/0283|
|European Classification||G06Q30/04, G06Q30/0283, H04L29/08A7, H04L29/08N1, H04L29/06|
|Nov 3, 2003||AS||Assignment|
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:EIBACH, WOLFGANG;GRUETZNER, MATTHIAS;KUEBLER, DIETMAR;REEL/FRAME:014099/0936;SIGNING DATES FROM 20030717 TO 20030718
|Oct 19, 2010||CC||Certificate of correction|
|Jun 14, 2013||REMI||Maintenance fee reminder mailed|
|Nov 3, 2013||LAPS||Lapse for failure to pay maintenance fees|
|Dec 24, 2013||FP||Expired due to failure to pay maintenance fee|
Effective date: 20131103