LOCATION-BASED SERVICE MIDDLEWARE

• US 20110087685A1
• Filed: 10/09/2009
• Published: 04/14/2011
• Est. Priority Date: 10/09/2009
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sundararajan, Arjun, Lin, Jyh-Han
• Application Number:
  US12/577,054
• Publication Number:
  US 20110087685A1
• Time in Patent Office: Days
• US Class Current: 707/765
• CPC Class Codes: G06F 16/9537 Spatial or temporal dependent retrieval, e.g. spatiotemporal queries

Abstract

A middleware system is provided that is situated between the user applications and the various content databases that are to be searched in order to simplify the creation of user applications for mobile devices that use location-based services that employ ontology-based search systems. The middleware system exposes one or more services to the user application. For example, a service exposes a service that allows the user to annotate and/or tag known semantic locations. As another example, a service provides a list of suggested semantic POIs to user applications in response to user queries. The suggested semantic POIs are selected based on a user'"'"'s location and possibly context-dependent information. The suggested semantic POIs also may be based on user-dependent information obtained from a user-profile or the like and the suggested semantic locations that are provided to the user applications may be ranked and presented in an order beginning with those semantic locations that may be of greatest interest.

Claims

1. A location-based service middleware system configured for operation between a user application residing on a mobile device and data sources that include semantic locations or other points-of interest (POIs), the middleware comprising the following computer-implemented components:

a semantic location tagging component for exposing a service to the user application that allows a user of the mobile device to augment semantic locations with personalized information;

a semantic location lookup component for receiving a user query posed via the user application and developing a refined query based on the user query, user-dependent information and contextual information available from the mobile device and the data sources; and

a matching engine for querying the data sources based on the refined query developed by the semantic location lookup component.

2. The location-based service middleware system of claim 1 further comprising a semantic location suggest component for exposing a service to the user application that provides a list of suggested semantic locations or other POIs obtained from the data sources in response to the user query posed via the user application, the suggested semantic locations or other POIs being selected based on the user-dependent information and contextual information available from the data sources.

3. The location-based service middleware system of claim 1 in which the personalized information includes attributes and tags.

4. The location-based service middleware system of claim 3 in which the personalized information is associated with a user ID of the user.

5. The location-based service middleware system of claim 1 in which the data sources include data representing location-based service (LBS) taxonomies, LBI, POIs and domain-specific content.

6. The location-based service middleware system of claim 2 in which the semantic location lookup component receives suggested semantic locations from the matching engine in response to the refined query and further comprising a semantic location ranking component for ranking the suggested semantic locations and providing the suggested ranked semantic locations to the semantic location suggest component.

7. The location-based service middleware system of claim 1 further comprising a semantic location discovery component for exposing a service to the user application that provides a list of newly discovered semantic locations or other POIs obtained from the data sources, the suggested semantic locations or other POIs being selected based on the user-dependent information and the contextual information available from the data sources.

8. A hierarchical application programming interface (API) system implemented using computer-executable code stored on one or more computer readable storage media configured for operation between a user application residing on a mobile device and data sources that include semantic locations or other POIs, the application programming interface comprising:

a first set of APIs for exposing a service to the user application that receives user queries from the user application and in response returns suggested semantic locations or other POIs obtained from the data sources; and

a second set of APIs for exposing a service to the user application that allows a user to augment semantic locations with personalized information.

9. The hierarchical application programming interface (API) system of claim 8 further comprising a third set of APIs for exposing a service to the user application that provides to the user application a list of newly discovered semantic locations or other POIs obtained from the data sources, in which the newly discovered semantic locations or other POIs are selected based on user-dependent information as well as contextual information available from the data sources.

10. The hierarchical application programming interface (API) system of claim 8 further comprising.

a semantic location lookup component for receiving the user queries from the first set of APIs and developing a refined query based on the user query, user-dependent information as well as contextual information available from the data sources, and

a matching engine for querying the data sources based on the refined query developed by the semantic location lookup component.

11. The hierarchical application programming interface (API) system of claim 10 further comprising a semantic location ranking component for ranking the suggested semantic locations and providing the suggested ranked semantic locations to the first set of APIs.

12. The hierarchical application programming interface (API) system of claim 8 in which the user-dependent information includes information obtained from a user profile.

13. The hierarchical application programming interface (API) system of claim 11 in which the matching engine poses domain-specific ontology queries.

14. The hierarchical application programming interface (API) system of claim 8 in which the second set of APIs allows the personalized information to be made available to users of other mobile devices.

15. A computer-implemented method for providing location-based services, the method comprising the steps of:

receiving a user query from a user application residing on a mobile device;

refining the user query based at least in part on user-dependent content and contextual information available from a plurality of data sources;

obtaining a list containing at least one semantic location or other POI from at least one of the data sources in response to the refined query; and

exposing a first API to the user application for providing the list to the user application.

16. The computer-implemented method of claim 15 in which refining the user query includes developing a domain specific ontology query.

17. The computer-implemented method of claim 15 further comprising a step of exposing a second API to the user application for providing newly discovered semantic locations or other POIs based on user-dependent information as well as contextual information available from the data sources.

18. The computer-implemented method of claim 15 further comprising a step of exposing a third API to the user application for allowing a user to augment, via the user application, semantic locations or other POIs with personalized information.

19. The computer-implemented method of claim 18 in which exposing the third API includes exposing the third API to the user application for allowing the user to augment the semantic locations with an attribute or tag.

20. The computer-implemented method of claim 19 in which the third API allows the user to selectively determine if the attribute or tag is to be made available to users of other mobile devices.