Nothing Special   »   [go: up one dir, main page]

US20080249904A1 - Counting and billing mechanism for web-services based on a soap-communication protocol - Google Patents

Counting and billing mechanism for web-services based on a soap-communication protocol Download PDF

Info

Publication number
US20080249904A1
US20080249904A1 US12/062,161 US6216108A US2008249904A1 US 20080249904 A1 US20080249904 A1 US 20080249904A1 US 6216108 A US6216108 A US 6216108A US 2008249904 A1 US2008249904 A1 US 2008249904A1
Authority
US
United States
Prior art keywords
service
resource
soap
counter
web
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/062,161
Inventor
Wolfgang Eibach
Matthias Gruetzner
Dietmar Kuebler
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US12/062,161 priority Critical patent/US20080249904A1/en
Publication of US20080249904A1 publication Critical patent/US20080249904A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0283—Price estimation or determination
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • 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.
  • 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.
  • SOA Service-oriented architecture
  • SOA Service Oriented Architecture
  • 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.
  • HTTP World Wide Web's Hypertext Transfer Protocol
  • XML Extensible Markup Language
  • the basic architecture of SOAP is shown in FIG. 1 .
  • the basic architecture comprises three components, the Service-Providers, the Service-Brokers, and the Service requesters.
  • 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.
  • FIG. 2 A typical SOAP-communication architecture as used by the prior art is shown in FIG. 2 .
  • 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.
  • 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 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.
  • 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.
  • 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.
  • FIG. 1 shows the basic structure of a SOAP-Web-Service architecture on which the present invention is based
  • FIG. 2 shows an example for a typical SOAP-Web-Service-communication architecture as used by the prior art
  • FIG. 3 shows the inventive Resource-Counter implemented in a SOAP-Web-Service architecture
  • FIG. 4 shows an existing SOAP-communication architecture as shown in FIG. 2 extended by the inventive Resource-Counter Service
  • FIG. 5 shows an interaction diagram for using the inventive Resource-Counter Service
  • FIG. 6 shows an interaction diagram for creation of a bill based on information received from the inventive Resource-Counter-Service
  • the existing SOAP-architecture will be extended by an Resource-Counter Service being accessible as own Web-Service.
  • the Resource-Counter Service may be invoked via SOAP messages as follows:
  • the Service Requester (client x) 1 uses a Web-Service from the Service-Provider 2 . If this Web-Service is not free of charge, Service-Provider 2 contacts Resource-Counter Service 3 for providing accounting service. It is assumed that the Service-Provider 2 has a contract with the Service-Provider for the accounting service 3 .
  • Resource-Counter Service may be also an internal service of the Service-Provider itself.
  • Service-Provider 2 will send a SOAP message request to the Resource-Counter Service 3 asking for accounting for its Service Requester 1 by providing at least begin time for service and end time of service.
  • FIG. 4 shows a detailed communication protocol for that case.
  • Service-Provider 2 After a certain period (e.g. one week, one month), Service-Provider 2 will request from the Resource-Counter Service-Provider 3 all records for the accounting period. These records are stored on a data base 4 , and will be sent as a SOAP response on request. These records may be used for calculating the charge generated by Service Requester.
  • the Resource-Counter Service mainly provides the functionality to create all necessary data allowing calculation of the charge for the execution 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.
  • FIG. 4 shows a typical SOAP-communication architecture extended by the inventive Resource Counter-Service.
  • Service-Provider 16 , 18 , 20 , 22 offers Web-Services 1 and 2 , e.g. a tax-calculation service.
  • Another Service-Provider 34 offers a Resource-Counter-Service 42 .
  • Both Service-Provider 16 , 34 publish service descriptions 14 , 28 for their Web-Services in the right category in the Service-Broker's taxonomy 44 ; 46 , 48 , 50 , 52 using a SOAP message response (Publish).
  • Service Requester 2 ; 4 , 6 , 8 as well as Service-Provider 16 receive the service description 14 , 28 of the requested Web-Services by a SOAP message response (Find).
  • the Service Requester 2 especially its SOAP client 12 , creates a SOAP message request by using service description 14 of the requested Web-Service for converting the shopping application data 10 , e.g. an order list created by the user, into a data representation required by requested Web-Service 24 , 30 and sends a SOAP message request containing the converted shopping application data 10 as well as authentication data to the Service-Provider 16 . If the authentication succeeds, the SOAP message request is then executed by the Application Server 20 using the SOAP Server 18 for calling up the requested Web-Service 24 , 30 , e.g. tax calculation application. When the Web-Service is completed, Service-Provider 16 sends a stop counting request to the Resource-Counter Service-Provider 34 .
  • service description 14 of the requested Web-Service for converting the shopping application data 10 , e.g. an order list created by the user, into a data representation required by requested Web-Service 24 , 30 and sends a SOAP message request containing the converted shopping application data 10 as well as
  • the Resource-Counter Service 42 stores an account record to the data base. After a certain period of time, the Service-Provider 16 receives the account records for calculating the charges for his Service Requester 2 using an accounting and bill presentment component 32 . In an another embodiment of the present invention, the Resource-Counter Service 42 has the additional functionality to create a bill for each Service Requester 2 based on a billing profile provided by the Service-Provider 16 . The bill may be sent to the Service Requester 2 either by the Service-Provider 16 providing Web-Service or directly from the Resource-Counter Service 42 to the Service Requester.
  • FIG. 5 shows an interaction diagram for using the inventive Resource-Counter Service.
  • 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.
  • ASP Application Service Provider machine
  • 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 .
  • 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.
  • 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 SOAP 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 .
  • step 7 may be executed only if an additional authentication method for the Service-Provider as explained above has been performed.
  • the Resource-Counter Service is started 8 .
  • SOAP server sends HTTP/SOAP response to the requester indicating “Resource-Counter Service started” 8 .
  • the requested Web-Service is executed 10 .
  • the SOAP client of the Service-Provider sends a HTTP/SOAP request to the Resource-Counter Service to stop counting 12
  • 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 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.
  • FIG. 6 shows an interaction diagram for creating a bill based on information received from the inventive Resource-Counter Service.
  • the Service Requester has used Web-Services from ASP for some time, and the accounting and bill presentment application of the Service-Provider creates a bill out of the data from the Resource-Counter Service. Following steps are performed by this method:
  • 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.
  • Service-Provider will only request the bill and the above disclosed method will be performed at the Resource-Counter Service Service.
  • 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.
  • the Resource-Counter Service may provide the 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, the creation of Service Requester accounts (e.g. ad-hoc or by contract) the creation of Service-Provider contracts the answering of queries if USERID is allowed for a requested service at this time, and maintaining Service Requester accounts provide a set of accounting model templates.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Signal Processing (AREA)
  • Marketing (AREA)
  • Computer Security & Cryptography (AREA)
  • Game Theory and Decision Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Detergent Compositions (AREA)

Abstract

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 protocol as well as a system and method for billing Web-Services using the result of the Resource-Counter Service for calculation of a charge. The Resource-Counter Service may be accessed by all Service-Provider having 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 Service-Provider using a charging model for their Web-Services. 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. The final calculation of the charge itself may be done by a separate specific accounting and bill presentment component.

Description

    RELATED APPLICATIONS
  • The present application is a Continuation Application of U.S. patent application Ser. No. 10/466,937 filed on Nov. 6, 2003.
  • 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.
  • 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 FIG. 1. The basic architecture comprises three components, the Service-Providers, the Service-Brokers, and the Service requesters.
  • 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 FIG. 2.
  • 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.
    • BRIEF SUMMARY OF THE INVENTION
  • 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.
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 shows the basic structure of a SOAP-Web-Service architecture on which the present invention is based
  • FIG. 2 shows an example for a typical SOAP-Web-Service-communication architecture as used by the prior art
  • FIG. 3 shows the inventive Resource-Counter implemented in a SOAP-Web-Service architecture
  • FIG. 4 shows an existing SOAP-communication architecture as shown in FIG. 2 extended by the inventive Resource-Counter Service
  • FIG. 5 shows an interaction diagram for using the inventive Resource-Counter Service
  • FIG. 6 shows an interaction diagram for creation of a bill based on information received from the inventive Resource-Counter-Service
    •  DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS OF THE INVENTION
  • In FIG. 3 the basic idea of the present invention is shown. The existing SOAP-architecture will be extended by an Resource-Counter Service being accessible as own Web-Service. The Resource-Counter Service may be invoked via SOAP messages as follows: The Service Requester (client x) 1 uses a Web-Service from the Service-Provider 2. If this Web-Service is not free of charge, Service-Provider 2 contacts Resource-Counter Service 3 for providing accounting service. It is assumed that the Service-Provider 2 has a contract with the Service-Provider for the accounting service 3. Resource-Counter Service may be also an internal service of the Service-Provider itself. Service-Provider 2 will send a SOAP message request to the Resource-Counter Service 3 asking for accounting for its Service Requester 1 by providing at least begin time for service and end time of service. (FIG. 4 shows a detailed communication protocol for that case). After a certain period (e.g. one week, one month), Service-Provider 2 will request from the Resource-Counter Service-Provider 3 all records for the accounting period. These records are stored on a data base 4, and will be sent as a SOAP response on request. These records may be used for calculating the charge generated by Service Requester. The Resource-Counter Service mainly provides the functionality to create all necessary data allowing calculation of the charge for the execution 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.
  • FIG. 4 shows a typical SOAP-communication architecture extended by the inventive Resource Counter-Service. Service- Provider 16, 18, 20, 22 offers Web- Services 1 and 2, e.g. a tax-calculation service. Another Service-Provider 34 offers a Resource-Counter-Service 42. Both Service- Provider 16, 34 publish service descriptions 14, 28 for their Web-Services in the right category in the Service-Broker's taxonomy 44; 46, 48, 50, 52 using a SOAP message response (Publish). Service Requester 2; 4, 6, 8 as well as Service-Provider 16 receive the service description 14, 28 of the requested Web-Services by a SOAP message response (Find). The Service Requester 2, especially its SOAP client 12, creates a SOAP message request by using service description 14 of the requested Web-Service for converting the shopping application data 10, e.g. an order list created by the user, into a data representation required by requested Web- Service 24, 30 and sends a SOAP message request containing the converted shopping application data 10 as well as authentication data to the Service-Provider 16. If the authentication succeeds, the SOAP message request is then executed by the Application Server 20 using the SOAP Server 18 for calling up the requested Web- Service 24, 30, e.g. tax calculation application. When the Web-Service is completed, Service-Provider 16 sends a stop counting request to the Resource-Counter Service-Provider 34. The Resource-Counter Service 42 stores an account record to the data base. After a certain period of time, the Service-Provider 16 receives the account records for calculating the charges for his Service Requester 2 using an accounting and bill presentment component 32. In an another embodiment of the present invention, the Resource-Counter Service 42 has the additional functionality to create a bill for each Service Requester 2 based on a billing profile provided by the Service-Provider 16. The bill may be sent to the Service Requester 2 either by the Service-Provider 16 providing Web-Service or directly from the Resource-Counter Service 42 to the Service Requester.
  • FIG. 5 shows an interaction diagram for using the inventive Resource-Counter Service.
  • 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 SOAP 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:
  •
    1 <binding name=“AServiceBinding”......> <soap:binding
    ......./> <operation name=“AService” <input
    message=“tns:ServiceRequester”> <soap:header
    element=“xsdl:ServiceRequesterId”/> <soap:body
    element=“.........”/> </input </operation> </binding>
  • 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.
  • FIG. 6 shows an interaction diagram for creating a bill based on information received from the inventive Resource-Counter Service. The Service Requester has used Web-Services from ASP for some time, and the accounting and bill presentment application of the Service-Provider creates a bill out of the data from the Resource-Counter Service. Following steps are performed by this method:
  • 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 the 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,
    the creation of Service Requester accounts (e.g. ad-hoc or by contract)
    the creation of Service-Provider contracts
    the answering of queries if USERID is allowed for a requested service at this time, and
    maintaining Service Requester accounts provide a set of accounting model templates.

Claims (17)

1. Service-Provider System for providing chargeable Web-Services for Service-Requesters comprising:
a Service-Provider Web-Service component a Service-Provider communication component (SOAP-server) allowing electronic communication between said Service-Provider system and a Service-Requester system using a SOAP-communication protocol, wherein said Service Requester system having an application which generates digital data to be used by said Web-Service, a service description for accessing said Web-Service via said Service-Provider communication component (SOAP-server) and a communication component (SOAP-client) for exchanging digital data between said application and said Web-Service via said SOAP-server by using a SOAP-communication protocol
characterized by
service description for electronically accessing a Resource-Counter Service provided by another Service-Provider having a communication component (SOAP-client) allowing electronic communication with another Service-Provider systems by using a SOAP-communication protocol, and a Resource-Counter Service providing data for electronic calculation of charges of said Web-Service to be accessed by said Service Requester
a communication component (SOAP-client) for electronically exchanging data with a communication component (SOAP-server) of said Resource-Counter Service by using said service description of said Resource-Counter Service and using a SOAP-communication protocol.
2. Service-Provider System according to claim 1, wherein said service description for accessing said Resource-Counter Service is provided by a Service-Broker using a SOAP-communication protocol.
3. Service-Provider System according to claim 1, wherein said SOAP-communication protocol is based on a HTTP-protocol.
4. Service-Provider System according to claim 1, wherein said service description is a XML document describing the semantics and the message API (Application Programming Interface) of said Resource-Counter Service Service.
5. Service-Provider according to claim 1, further comprising: a bill present component having access to the data provided by said Resource-Counter Service for calculation of charges for Web-Service to be counted.
6. Resource-Counter Service-Provider system for providing Resource-Counter Service for a Service-Provider system as claimed in claim 1 comprising: a Resource-Counter Service component providing data for calculation of Web-Service to be accessed by Service Requester a communication component (SOAP-server) for electronically receiving data from a communication component (SOAP-client) located at the Service-Provider system, electronically passing said data to said Resource-Counter Service component, electronically receiving the result of the Resource-Counter Service component and electronically transmitting said result to the said communication component (SOAP-client) of said Service-Provider providing a Web-Service to be accessed by said Service Requester, wherein the communication protocol used by said component is SOAP.
7. Resource-Counter Service-Provider system according to claim 6, wherein said Resource-Counter Service component is extended by a bill present presentment functionality using the data provided by said Resource-Counter Service functionality and calculating charges' for said Web-Service to be accessed.
8. Resource-Counter Service-Provider system according to claim 6, wherein a service description for accessing said Resource-Counter Service is created and published by said Resource-Counter Service-Provider system in the right category in the Service-Broker's taxonomy using SOAP communication protocol.
9. Resource-Counter Service-Provider system according to claim 8, wherein said SOAP-communication protocol is based on HTTP.
10. Resource-Counter Service-Provider system according to claim 8, wherein said service description is a XML document.
11. Web-Service architecture comprising:
a Service-Requester system comprising:
a communication component (SOAP-client) allowing electronic communication between said Service-Requester system and said Service-Provider system using a SOAP-communication protocol, wherein said Service Requester system having an application which generates digital data to be used by said Web-Service, and a service description for accessing said Web-Service
a Service-Provider system providing a Web-Service for Service Requester systems comprising:
a communication component (SOAP-server) allowing electronic communication of said communication component of said Service-Requester system with said Web-Service using a SOAP-communication protocol service description for electronically accessing a Resource-Counter Service provided by another Service-Provider
a communication component (SOAP-client) for electronically exchanging data with a communication component (SOAP-server) of a Resource-Counter Service by using said service description of said Resource-Counter Service and using a SOAP-communication protocol a Resource-Counter Service-Provider system comprising:
a Resource-Counter Service component for counting of a Web-Service
a communication component (SOAP-server) for electronically receiving data from a communication component (SOAP-client) located at the Service-Provider system providing Web-Service to be accessed, electronically passing said data to said Resource-Counter Service, electronically receiving the result of the Resource-Counter Service and electronically transmitting said result to the communication component of said Service-Provider, wherein the communication protocol used by said component is SOAP.
12. Method for counting and charging of Web-Services using Service-Provider system as claimed in claim 1 to 10, comprising the steps of:
performing an authentication process between Service requester and Service-Provider
receiving a SOAP-Bind request for the requested Web-Service being created by the SOAP-client of said Service-Requester
creating an instance for the Web-Service to be selected
sending a SOAP-Bind request to the SOAP-server of the Resource-Counter Service-Provider for execution of said Resource-Counter Service
receiving a SOAP-response from said Resource-Counter Service-Provider that the Resource is started executing said Web-Service
sending a SOAP-request to said Resource-Counter Service for stopping of counting when said Web-Service is completed
receiving a SOAP-response that the Resource-Counter Service is stopped
sending a SOAP-request to said Service-Requester containing the result of said Web-Service.
13. Method according to claim 12, wherein said SOAP-Bind request for execution of said Resource-Counter Service contains data for authentication of said Service-Provider.
14. Method according to claim 12, wherein an authentication process is performed with said Resource-Counter Service-Provider before said SOAP-Bind request is sent.
15. Method according to claim 12, further including the steps:
receiving a SOAP-response containing Resource-Counter data for said Web-Service being accessed
calculating charges for said Web-Service being accessed by said Service-Requester based on said Resource-Counter data sending a bill to said Service-Requester containing charges of said Web-Service being accessed.
16. Method according to claim 12, further including the step:
receiving a SOAP-response containing a bill being calculated and created by said Resource-Counter Service based on said Resource-Counter data and an account model provided by said Service-Provider
sending said bill to said Service-Requester.
17. Computer program product stored in the internal memory of a digital computer, containing parts of software code to execute the method in accordance with claims 12 to 16 if the product is run on the computer.
US12/062,161 2001-04-04 2008-04-03 Counting and billing mechanism for web-services based on a soap-communication protocol Abandoned US20080249904A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/062,161 US20080249904A1 (en) 2001-04-04 2008-04-03 Counting and billing mechanism for web-services based on a soap-communication protocol

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP01108466 2001-04-04
US10/466,937 US7613817B2 (en) 2001-04-04 2002-03-14 Counting and billing mechanism for web-services based on a SOAP-communication protocol
PCT/EP2002/002815 WO2002082305A2 (en) 2001-04-04 2002-03-14 Counting and billing mechanism for web-services based on a soap-communication protocol
US12/062,161 US20080249904A1 (en) 2001-04-04 2008-04-03 Counting and billing mechanism for web-services based on a soap-communication protocol

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
US10/466,937 Continuation US7613817B2 (en) 2001-04-04 2002-03-14 Counting and billing mechanism for web-services based on a SOAP-communication protocol
PCT/EP2002/002815 Continuation WO2002082305A2 (en) 2001-04-04 2002-03-14 Counting and billing mechanism for web-services based on a soap-communication protocol

Publications (1)

Publication Number Publication Date
US20080249904A1 true US20080249904A1 (en) 2008-10-09

Family

ID=8177044

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/466,937 Expired - Fee Related US7613817B2 (en) 2001-04-04 2002-03-14 Counting and billing mechanism for web-services based on a SOAP-communication protocol
US12/062,161 Abandoned US20080249904A1 (en) 2001-04-04 2008-04-03 Counting and billing mechanism for web-services based on a soap-communication protocol

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/466,937 Expired - Fee Related US7613817B2 (en) 2001-04-04 2002-03-14 Counting and billing mechanism for web-services based on a SOAP-communication protocol

Country Status (11)

Country Link
US (2) US7613817B2 (en)
EP (1) EP1388084B1 (en)
JP (1) JP3902136B2 (en)
KR (1) KR100538751B1 (en)
CN (1) CN1243428C (en)
AT (1) ATE298109T1 (en)
AU (1) AU2002256675A1 (en)
CA (1) CA2436888C (en)
DE (1) DE60204683T2 (en)
TW (1) TW561751B (en)
WO (1) WO2002082305A2 (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110047482A1 (en) * 2009-08-18 2011-02-24 Turning Technologies, Llc Audience response web server
US20110047227A1 (en) * 2009-08-18 2011-02-24 Turning Technologies, Llc Message-service audience response
US7925554B1 (en) 2006-12-29 2011-04-12 Amazon Technologies, Inc. Using configured application pricing to determine end user fees for use of invocable services
US8055586B1 (en) * 2006-12-29 2011-11-08 Amazon Technologies, Inc. Providing configurable use by applications of sequences of invocable services
CN102427451A (en) * 2011-12-06 2012-04-25 宁波电业局 Method and system for acquiring service application
US10853780B1 (en) * 2006-12-29 2020-12-01 Amazon Technologies, Inc. Providing configurable pricing for use of invocable services by applications
US11449580B2 (en) * 2018-06-18 2022-09-20 Fujifilm Business Innovation Corp. Server apparatus and license management system

Families Citing this family (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2405700C (en) * 2002-09-30 2010-05-04 Ibm Canada Limited-Ibm Canada Limitee Web service interfaces used in providing a billing service
US8489742B2 (en) 2002-10-10 2013-07-16 Convergys Information Management Group, Inc. System and method for work management
US8577795B2 (en) 2002-10-10 2013-11-05 Convergys Information Management Group, Inc. System and method for revenue and authorization management
US7342918B2 (en) * 2003-04-15 2008-03-11 American Express Travel Related Services Co., Inc. Transaction card information access web service
US7506162B1 (en) 2003-07-14 2009-03-17 Sun Microsystems, Inc. Methods for more flexible SAML session
US8200775B2 (en) * 2005-02-01 2012-06-12 Newsilike Media Group, Inc Enhanced syndication
FR2859586B1 (en) * 2003-09-04 2006-04-28 Orange France METHOD AND SYSTEM FOR INVOICING A SUBSCRIBER TO A PROVIDER OF ACCESS TO A COMMUNICATION NETWORK FOR USE OF SERVICES
US20050065879A1 (en) 2003-09-18 2005-03-24 Convergys Information Management Group, Inc. System and method for web service billing
US7668093B1 (en) 2004-08-05 2010-02-23 Convergys Information Management Group, Inc. Architecture for balancing workload
US7836510B1 (en) 2004-04-30 2010-11-16 Oracle America, Inc. Fine-grained attribute access control
US7565356B1 (en) * 2004-04-30 2009-07-21 Sun Microsystems, Inc. Liberty discovery service enhancements
US7418501B2 (en) 2004-04-30 2008-08-26 International Business Machines Corporation Dynamic extension of network-accessible services
US7590980B1 (en) 2004-06-14 2009-09-15 Convergys Cmg Utah, Inc. System and method for a functional extensibility framework
US7610225B2 (en) * 2004-08-13 2009-10-27 Qualcomm Incorporated Methods and apparatus for performing resource tracking and accounting at a mobile node
KR100590030B1 (en) * 2004-09-17 2006-06-19 전자부품연구원 Method using an soap operation for leaving out user metadata managed by tv-anytime metadata server
US7908286B2 (en) * 2004-12-08 2011-03-15 Oracle International Corporation Techniques for providing XQuery access using web services
CN1805403B (en) * 2005-01-10 2010-10-06 华为技术有限公司 Method of using communication services with packet user terminal and its system
US8200700B2 (en) 2005-02-01 2012-06-12 Newsilike Media Group, Inc Systems and methods for use of structured and unstructured distributed data
US20080195483A1 (en) * 2005-02-01 2008-08-14 Moore James F Widget management systems and advertising systems related thereto
US20070050446A1 (en) * 2005-02-01 2007-03-01 Moore James F Managing network-accessible resources
US20060265489A1 (en) * 2005-02-01 2006-11-23 Moore James F Disaster management using an enhanced syndication platform
US9202084B2 (en) 2006-02-01 2015-12-01 Newsilike Media Group, Inc. Security facility for maintaining health care data pools
US8347088B2 (en) * 2005-02-01 2013-01-01 Newsilike Media Group, Inc Security systems and methods for use with structured and unstructured data
US20080046471A1 (en) * 2005-02-01 2008-02-21 Moore James F Calendar Synchronization using Syndicated Data
US20070106754A1 (en) * 2005-09-10 2007-05-10 Moore James F Security facility for maintaining health care data pools
US8140482B2 (en) 2007-09-19 2012-03-20 Moore James F Using RSS archives
US8700738B2 (en) * 2005-02-01 2014-04-15 Newsilike Media Group, Inc. Dynamic feed generation
US20080140760A1 (en) * 2005-03-21 2008-06-12 Conner Peter A Service-oriented architecture system and methods supporting dynamic service provider versioning
US20060230118A1 (en) * 2005-04-12 2006-10-12 Digi Chain Information Co., Ltd. Share memory service system and method of web service oriented applications
JP2007086889A (en) * 2005-09-20 2007-04-05 Shin Caterpillar Mitsubishi Ltd Management part side management apparatus for remote management system
CN1941771B (en) * 2005-09-27 2011-09-07 国际商业机器公司 Web service data managing method and system for use of service oriented system structure
CN100444148C (en) * 2005-12-08 2008-12-17 北京北方微电子基地设备工艺研究中心有限责任公司 Control method for factory host and integrated controller system based on web service
US20080140857A1 (en) * 2006-03-21 2008-06-12 Conner Peter A Service-oriented architecture and methods for direct invocation of services utilizing a service requestor invocation framework
US20080046369A1 (en) * 2006-07-27 2008-02-21 Wood Charles B Password Management for RSS Interfaces
CN101150576B (en) * 2006-09-20 2011-09-28 鸿富锦精密工业（深圳）有限公司 Network server access system and its method
US8271941B2 (en) * 2006-10-31 2012-09-18 International Business Machines Corporation Method and apparatus for representing and configuring flexible and extensible presentation patterns
KR100839932B1 (en) 2007-02-23 2008-06-20 성균관대학교산학협력단 Web service charging system for qos guarantee and method thereof
US8166465B2 (en) 2007-04-02 2012-04-24 International Business Machines Corporation Method and system for composing stream processing applications according to a semantic description of a processing goal
US8370812B2 (en) 2007-04-02 2013-02-05 International Business Machines Corporation Method and system for automatically assembling processing graphs in information processing systems
US8117233B2 (en) * 2007-05-14 2012-02-14 International Business Machines Corporation Method and system for message-oriented semantic web service composition based on artificial intelligence planning
CN101282227B (en) * 2008-05-13 2010-09-22 华为技术有限公司 Method, concentrating control equipment and system for charging service
US20100211895A1 (en) * 2009-02-13 2010-08-19 Pragnesh Mistry Method for visualization and integration of business intelligence data
US20110225074A1 (en) * 2010-03-12 2011-09-15 Microsoft Corporation System and method for providing information as a service via web services
US8874745B2 (en) * 2010-03-26 2014-10-28 Fujitsu Limited Method and system for providing services
US8701159B2 (en) * 2010-05-12 2014-04-15 Winshuttle, Llc Dynamic web services system and method
JP2012129674A (en) 2010-12-14 2012-07-05 Nec Corp Network maintenance system, method and device
KR101857020B1 (en) * 2012-01-17 2018-05-14 삼성전자주식회사 Apparatas and method for managing service of providing server in a terminal
US9171464B2 (en) * 2012-06-10 2015-10-27 Apple Inc. Encoded representation of route data
US11935190B2 (en) 2012-06-10 2024-03-19 Apple Inc. Representing traffic along a route
US9588813B1 (en) * 2013-06-07 2017-03-07 Amazon Technologies, Inc. Determining cost of service call
US9501321B1 (en) * 2014-01-24 2016-11-22 Amazon Technologies, Inc. Weighted service requests throttling
CN103957174B (en) * 2014-05-16 2017-02-15 北京信诺瑞得软件系统有限公司 Method for semantic switch loose coupling system to process information
US11171879B2 (en) * 2020-01-02 2021-11-09 Wipro Limited System and method of sharing edge computing resources
US11758012B1 (en) 2023-01-18 2023-09-12 International Business Machines Corporation Computer service invocation chain monitoring and remuneration optimization

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5960409A (en) * 1996-10-11 1999-09-28 Wexler; Daniel D. Third-party on-line accounting system and method therefor
US20030028528A1 (en) * 2001-02-09 2003-02-06 Microsoft Corporation System and method for discovering information about web resources
US20030053459A1 (en) * 2001-03-26 2003-03-20 Lev Brouk System and method for invocation of services
US20030061404A1 (en) * 2001-09-21 2003-03-27 Corel Corporation Web services gateway
US20040268242A1 (en) * 2000-08-09 2004-12-30 Microsoft Corporation Object persister

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5794221A (en) * 1995-07-07 1998-08-11 Egendorf; Andrew Internet billing method
JPH09146129A (en) 1995-11-16 1997-06-06 Fuji Xerox Co Ltd Optical scanner and image forming device
FI113224B (en) * 1996-11-11 2004-03-15 Nokia Corp Implementation of invoicing in a data communication system
JPH10334145A (en) * 1997-06-04 1998-12-18 Ibm Japan Ltd Network charging server
JP2000031230A (en) 1998-07-14 2000-01-28 Mitsubishi Electric Corp Semiconductor device
JP4124308B2 (en) * 2000-02-08 2008-07-23 株式会社あいほっと Information storage system and information storage method

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5960409A (en) * 1996-10-11 1999-09-28 Wexler; Daniel D. Third-party on-line accounting system and method therefor
US20040268242A1 (en) * 2000-08-09 2004-12-30 Microsoft Corporation Object persister
US20030028528A1 (en) * 2001-02-09 2003-02-06 Microsoft Corporation System and method for discovering information about web resources
US20030053459A1 (en) * 2001-03-26 2003-03-20 Lev Brouk System and method for invocation of services
US20030061404A1 (en) * 2001-09-21 2003-03-27 Corel Corporation Web services gateway

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7925554B1 (en) 2006-12-29 2011-04-12 Amazon Technologies, Inc. Using configured application pricing to determine end user fees for use of invocable services
US8055586B1 (en) * 2006-12-29 2011-11-08 Amazon Technologies, Inc. Providing configurable use by applications of sequences of invocable services
US9044504B1 (en) 2006-12-29 2015-06-02 Amazon Technologies, Inc. Using configured application pricing to determine end user fees for use of invocable services
US10726404B2 (en) 2006-12-29 2020-07-28 Amazon Technologies, Inc. Using configured application information to control use of invocable services
US10853780B1 (en) * 2006-12-29 2020-12-01 Amazon Technologies, Inc. Providing configurable pricing for use of invocable services by applications
US10891666B1 (en) 2006-12-29 2021-01-12 Amazon Technologies, Inc. Integration of sequences of invocable services
US20110047482A1 (en) * 2009-08-18 2011-02-24 Turning Technologies, Llc Audience response web server
US20110047227A1 (en) * 2009-08-18 2011-02-24 Turning Technologies, Llc Message-service audience response
CN102427451A (en) * 2011-12-06 2012-04-25 宁波电业局 Method and system for acquiring service application
US11449580B2 (en) * 2018-06-18 2022-09-20 Fujifilm Business Innovation Corp. Server apparatus and license management system

Also Published As

Publication number Publication date
TW561751B (en) 2003-11-11
CA2436888A1 (en) 2002-10-17
EP1388084A2 (en) 2004-02-11
US20040073661A1 (en) 2004-04-15
JP2004534991A (en) 2004-11-18
JP3902136B2 (en) 2007-04-04
CA2436888C (en) 2006-07-11
AU2002256675A1 (en) 2002-10-21
CN1243428C (en) 2006-02-22
DE60204683D1 (en) 2005-07-21
CN1505884A (en) 2004-06-16
KR20040014471A (en) 2004-02-14
WO2002082305A3 (en) 2003-08-28
ATE298109T1 (en) 2005-07-15
KR100538751B1 (en) 2005-12-26
EP1388084B1 (en) 2005-06-15
US7613817B2 (en) 2009-11-03
WO2002082305A2 (en) 2002-10-17
DE60204683T2 (en) 2006-05-18

Similar Documents

Publication Publication Date Title
CA2436888C (en) Counting and billing mechanism for web-services based on a soap-communication protocol
US11157915B2 (en) Automatic creation and configuration of license models and policies
US11734734B2 (en) System and method for web service billing
Tsalgatidou et al. An overview of standards and related technology in web services
US7729954B2 (en) Providing paid access to remote web service in an electronic marketplace
US7526547B2 (en) Intelligent network charging edge
US20020029197A1 (en) Method and system for billing over a wireless application protocol gateway
US20020143819A1 (en) Web service syndication system
US20050091663A1 (en) Integration service and domain object for telecommunications operational support
US7711843B2 (en) Method and a device for making a media file accessible via a web page
US6654600B1 (en) Method and apparatus for authorizing use of cellular telephone units
US7827104B2 (en) Method and system for efficiently billing on-demand service exploitation in computer networks
US7506021B2 (en) Provisioning web services
EP1374047A2 (en) A method and a bridge for coupling a server and a client of different object types
US20090259510A1 (en) Operational Support System for Telecommunication Services
US8700753B2 (en) Distributed computer system for telecommunications operational support
US20050108133A1 (en) Service shopping and provisioning system and method
JP4617309B2 (en) Web service contract selection system
JP2002358290A (en) Providing method, program and system for information processing service
KR20040096976A (en) Method for acting as payment gateway to pay in integrated one&#39;s points on the internet
KR100934339B1 (en) How to Handle Web Service Charges Using Tickets

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION