SYSTEM AND METHOD FOR PROVIDING INFORMATION AS A SERVICE VIA WEB SERVICES

• US 20110225074A1
• Filed: 06/18/2010
• Published: 09/15/2011
• Est. Priority Date: 03/12/2010
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bouw, Rene, Mall, Roger Soulen, Swedberg, Greg, Gwozdz, Lukasz, Khosravy, Moe, Liensberger, Christian
• Application Number:
  US12/818,371
• Publication Number:
  US 20110225074A1
• Time in Patent Office: Days
• US Class Current: 705/34
• CPC Class Codes: G06F 2209/462 Lookup
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

Aspects are disclosed for providing information as a service via web services. Access to at least one application programming interface (API) database is facilitated and requests for a requested API are parsed. Here, such API requests facilitate a processing of data provided by at least one content provider. In an aspect, each request includes a key associated with a developer of the requested API and a unique identifier associated with a user of the requested API. A usage of the requested API is then tracked based on the key and/or unique identifier.

Claims

1. An apparatus configured to facilitate providing information as a service via web services, the apparatus comprising:

a processor configured to execute computer executable components stored in memory, the components including;

an interface component configured to facilitate access to at least one application programming interface (API) database;

a parsing component configured to parse a request for a requested API, wherein the request facilitates a processing of data provided by at least one content provider, and wherein the request includes a key associated with a developer of the requested API and a unique identifier associated with a user of the requested API; and

a tracking component configured to track a use of the requested API based on at least one of the key or the unique identifier.

2. The apparatus of claim 1, further comprising a generation component configured to generate the request based on a selection of the requested API.

3. The apparatus of claim 2, the interface component configured to display a plurality of selectable APIs stored in the at least one API database, the requested API included in the plurality of selectable APIs.

4. The apparatus of claim 3, the interface component configured to facilitate a search of the at least one API database, the plurality of selectable APIs corresponding to results of the search.

5. The apparatus of claim 4, the search based on an input, the input identifying at least one of a desired operation, a desired content provider, or a desired content type.

6. The apparatus of claim 1, the interface component configured to upload an external API onto the at least one API database.

7. The apparatus of claim 1, the use corresponding to a multi-seat use of the requested API, the parsing component configured to extract multiple unique identifiers from the requested API, wherein the multiple unique identifiers identify multiple users associated with the multi-seat use.

8. The apparatus of claim 1, further comprising an audit component configured to automatically audit a usage history of at least one of the plurality of APIs.

9. The apparatus of claim 1, further comprising a billing component configured to automatically bill an external entity based on a usage history of at least one of the plurality of APIs.

10. The apparatus of claim 1, the request further including a partner identifier associated with an affiliate of the requested API, wherein the tracking component is further configured to track the use of the requested API based on the partner identifier.

11. A method that facilitates providing information as a service via web services, including:

employing a processor to execute computer executable instructions stored on a computer readable storage medium to implement a series of acts including;

providing access to at least one application programming interface (API) database;

receiving a request identifying a requested API, the request facilitating a processing of data provided by at least one content provider;

parsing the request to ascertain a key associated with a developer of the requested API and a unique identifier associated with a user of the requested API; and

tracking a use of the requested API based on at least one of the key or the unique identifier.

12. The method of claim 11, further comprising automatically auditing a usage history of at least one API stored in the at least one API database.

13. The method of claim 11, further comprising automatically billing an external entity based on a usage history of at least one API stored in the at least one API database.

14. The method of claim 11, the parsing comprising extracting multiple unique identifiers from the requested API, wherein the multiple unique identifiers identify multiple users associated with a multi-seat use of the requested API.

15. The method of claim 11, the request further including a partner identifier associated with an affiliate of the requested API, wherein the tracking further comprises tracking the use of the requested API based on the partner identifier.

16. The method of claim 15, further comprising inserting at least one of the key, the unique identifier, or the partner identifier into the request.

17. A method that facilitates providing information as a service via web services, including:

employing a processor to execute computer executable instructions stored on a computer readable storage medium to implement a series of acts including;

providing access to at least one application programming interface (API) database;

uploading a received API onto the API database, the received API facilitating a processing of data provided by at least one content provider;

parsing a request for the received API to ascertain a key associated with a developer of the received API and a unique identifier associated with a user of the received API; and

tracking a use of the received API based on at least one of the key or the unique identifier.

18. The method of claim 17, further comprising automatically auditing a usage history of the requested API.

19. The method of claim 17, the parsing comprising extracting multiple unique identifiers from the requested API, wherein the multiple unique identifiers identify multiple users associated with a multi-seat use of the requested API.

20. The method of claim 17, the parsing comprising parsing the request to ascertain a partner identifier associated with an affiliate of the requested API, wherein the tracking further comprises tracking the use of the requested API based on the partner identifier.