CACHING DATA OBTAINED VIA DATA SERVICE INTERFACES

• US 20110238686A1
• Filed: 03/24/2010
• Published: 09/29/2011
• Est. Priority Date: 03/24/2010
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hsu, Bo-June, Casper, Bert, Bergstraesser, Thomas Frank, Huang, Tai-Yi
• Application Number:
  US12/730,748
• Publication Number:
  US 20110238686A1
• Time in Patent Office: Days
• US Class Current: 707/769
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

A potential user query that can be subsequently received from a user is identified. An interface exposed by a data service is invoked, which includes providing the potential user query to the interface. Search results in response to the potential user query are received from the interface and maintained in a complex data set store. If a user query is subsequently received that maps to a normalized query that is the potential user query, then search results for the normalized query are obtained from the complex data set store and returned as the search results for the user query.

Claims

1. A method comprising:

identifying a potential user query that can be subsequently received from a requester;

invoking an interface exposed by a data service, the invoking including providing the potential user query to the interface;

receiving, from the interface, search results in response to the potential user query; and

maintaining the search results in a complex data set store from which the search results can be returned to the requester if the potential user query is subsequently received from the requester.

2. A method as recited in claim 1, wherein the potential user query is a normalized query that maps to multiple different user queries, and wherein maintaining the search results comprises maintaining the search results in the complex data set store from which the search results can be returned to the requester if one of the multiple different user queries that maps to the normalized query is subsequently received from the requester.

3. A method as recited in claim 1, wherein maintaining the search results comprises:

determining, based at least in part on previous search results received in response to previously invoking the interface including previously providing the potential user query to the interface, whether to replace the previous search results in the complex data set store with the search results received in response to the potential user query; and

storing the search results received in response to the potential user query in the complex data set store only if it is determined that the previous search results in the complex data set store are to be replaced with the search results received in response to the potential user query.

4. A method as recited in claim 3, wherein the determining is based at least in part on whether a number of items in the previous search results received in response to previously invoking the interface is at least a threshold amount greater than a number of items in the search results received in response to the potential user query.

5. A method as recited in claim 1, wherein identifying the potential user query comprises identifying the potential user query based at least in part on a collection of multiple previously entered user queries.

6. A method as recited in claim 1, wherein maintaining the search results comprises storing the search results in the complex data set store indexed by the potential user query.

7. A method as recited in claim 6, wherein maintaining the search results further comprises identifying one or more links in the search results, and for each of the one or more links:

retrieving linked-to data from a location identified by the link; and

storing the linked-to data in the complex data set store as part of the search results.

8. A method as recited in claim 1, wherein the identifying, invoking, receiving, and maintaining is performed independently of whether the potential user query is subsequently received from the requester.

9. A method as recited in claim 1, wherein the interface comprises an application programming interface.

10. A method as recited in claim 1, further comprising:

invoking an additional interface exposed by an additional data service, the invoking the additional interface including providing the potential user query to the additional interface;

receiving, from the additional interface, additional search results in response to the potential user query; and

maintaining the additional search results as part of the search results in the complex data set store.

11. A method as recited in claim 1, further comprising, after the identifying, invoking, receiving, and maintaining:

receiving a user query from the requester;

mapping the user query to a normalized query that is the potential user query;

obtaining, from the complex data set store, the search results for the normalized query; and

returning, to the requester, the search results for the normalized query as the search results for the user query.

12. A method as recited in claim 11, wherein identifying the potential user query comprises obtaining, as the potential user query, one of multiple normalized queries to which user queries can be mapped.

13. A method comprising:

receiving a user query;

mapping the user query to a normalized query;

obtaining, from a complex data set store, search results for the normalized query, wherein the search results are in the complex data set store as a result of the normalized query having been submitted, prior to receiving the user query, to an interface of a data service; and

returning, from the complex data set store, the search results for the normalized query as the search results for the user query.

14. A method as recited in claim 13, wherein the complex data store stores search results for multiple different normalized queries indexed to the multiple different normalized queries.

15. A method as recited in claim 14, wherein the search results include two or more of text data, image data, audio data, and video data.

16. A method as recited in claim 13, wherein the complex data set store includes as the search results both data received from the data service and additional data received from an additional data source.

17. A method as recited in claim 13, further comprising combining the search results with additional search results obtained from searching HyperText Markup Language (HTML) Web pages, and returning the search results from the complex data set store combined with the additional search results obtained from searching HTML Web pages as the search results for the user query.

18. A method as recited in claim 13, wherein the search results are stored in the complex data set store indexed by normalized user queries, and wherein obtaining the search results comprises obtaining search results indexed to the normalized query.

19. A method as recited in claim 18, wherein obtaining search results indexed to the normalized query comprises obtaining an eXtensible Markup Language (XML) document that stores the search results and is associated with the normalized query.

20. A search service comprising:

a complex data set generation module configured to;

identify a potential user query that can be subsequently received from a requester,

invoke an interface exposed by a data service, wherein to invoke the interface is to provide the potential user query to the interface,

receive, from the interface, search results in response to the potential user query, and

maintain the search results in a complex data set store from which the search results can be returned to the requester if the potential user query is subsequently received from the requester; and

a search engine module configured to;

receive a user query from the requester,

map the user query to a normalized query that is the potential user query,

obtain, from the complex data set store, the search results for the normalized query, and

return, to the requester, the search results for the normalized query as the search results for the user query.