Method and System for Managing Relationships Between Location Identifiers

• US 20100198504A1
• Filed: 01/30/2009
• Published: 08/05/2010
• Est. Priority Date: 01/30/2009
• Status: Abandoned Application

• Current Assignee: HERE Global B.V. (HERE Holding Corporation)
• Original Assignee: Navteq North America LLC (HERE Holding Corporation)
• Inventors: Synghal, Rajiv K., Samsalovic, Vojislav, Kurspahic, Tarik
• Application Number:
  US12/362,751
• Publication Number:
  US 20100198504A1
• Time in Patent Office: Days
• US Class Current: 701/207
• CPC Class Codes: G01C 21/206 specially adapted for indoor navigation
• CPC Class Codes: G01C 21/383 Indoor data
• CPC Class Codes: G01C 21/3878 Hierarchical structures, e.g. layering

Abstract

A method and system for managing relationships between location identifiers is disclosed. A relationship includes an originating identifier and a target identifier. A unique relationship is defined by the location codes and relationship types associated with the originating and target identifier. A synonym service, a translation service, and a validation service analyze a new or modified relationship prior to storing the relationship in a relationship store. A graph service, a statistics service, and a reporting service analyze the relationships stored in the relationship store.

Claims

1. A method of providing indoor navigation, comprising:

obtaining data associated with a first location identifier;

obtaining data associated with a second location identifier;

storing data associated with a relationship between the first location identifier and the second location identifier based on the obtained data;

identifying a relationship hierarchy that includes the relationship between the first and second location identifiers; and

using the hierarchy to provide navigation guidance within a building.

2. The method of claim 1, wherein the data associated with the first and second location identifiers includes a location code and a relationship type.

3. The method of claim 2, wherein the data associated with the first and second location identifiers further includes relationship direction.

4. The method of claim 3, wherein the relationship direction is one of unidirectional and bidirectional.

5. The method of claim 1, wherein storing data includes storing a location code and a relationship type for the first and second location identifiers.

6. The method of claim 1, further comprising graphing the relationship hierarchy as a vertical graph.

7. A system for collecting data regarding relationships between two location identifiers, comprising:

an input mechanism that allows a user to enter a first location code and a first relationship type associated with a first location identifier and a second location code and a second relationship type associated with a second location identifier;

a synonym service that determines whether the entered first and second relationship types are synonyms of a preferred relationship type;

a translation service that determines the language used for the first and second relationship types, wherein the translation service assigns a language code to the relationship types based on the determination;

a validation service that determines whether the entered first and second location is codes and first and second relationship types form a valid relationship; and

a relationship store that stores the valid relationship for use by third party systems, wherein the valid relationship includes the preferred relationship type if one of the first and second relationship types is a synonym of the preferred relationship type.

8. The system of claim 7, wherein the input mechanism is one of a user interface and a Web service.

9. The system of claim 7, wherein a location system assigns the first and second location codes.

10. The system of claim 7, wherein the language code is stored with the stored valid relationship.

11. The system of claim 7, wherein the third party system is a navigation system.

12. The system of claim 7, wherein the third party system is a location content management system.

13. A system for providing information regarding a relationship between two location identifiers, comprising:

a statistics service that obtains statistics regarding activities related to creating, modifying, and downloading location relationship data, wherein the location relationship data includes a first location code and a first relationship type associated with a first location identifier and a second location code and a second relationship type associated with a second location identifier; and

a reporting service that generates an output based on the statistics obtained by the statistics service.

14. The system of claim 13, further comprising a data store for storing the obtained statistics obtained by the statistics service.

15. The system of claim 13, wherein the statistics includes a count selected from the group consisting of relationships added to a relationship store, relationships of a particular type, modifications to a relationship, and relationship hierarchies.

16. The system of claim 13, wherein the output of the reporting service includes a chart.

17. The system of claim 16, wherein the chart is a radar chart.

18. The system of claim 13, wherein the output of the reporting service includes a notification.

19. The system of claim 13, wherein the output of the reporting service is provided to a third party system.

20. The system of claim 13, further comprising a graph service that graphs a network of relationships using the location relationship data.

21. The system of claim 20, wherein the graph service generates vertical and horizontal graphs.