Method and apparatus for managing location information in a network separate from the data to which the location information pertains

• US 7,233,978 B2
• Filed: 06/01/2001
• Issued: 06/19/2007
• Est. Priority Date: 07/08/1998
• Status: Expired due to Term

• Current Assignee: Kove IO, Inc.
• Original Assignee: Econnectix LLC
• Inventors: Overton, John K., Bailey, Stephen W.
• Primary Examiner(s): Kang; Paul H.
• Application Number:
  US09/872,736
• Publication Number:
  US 20020032787A1
• Time in Patent Office: 2,209 Days
• Field of Search: 718/105, 709/203, 709/206, 709/217, 709/207, 709/223, 709/226, 709/230, 709/232, 709/235, 709/241, 709/242
• US Class Current: 709/217
• CPC Class Codes: G06F 16/58 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 69/26 Special purpose or proprietary protocols or architectures network applications for proprietary or special purpose networking environments H04L67/12
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and method for storing and retrieving location information across a network is disclosed. The system and method utilize a transfer protocol configured to transport an identifier/location relationship to allow one or more locations to be associated with an identifier in the location store of a location server, where the identifier represents a unique entity and the location represents a location of data pertaining to the identifier. The location server contains programming logic operative to provide responses to location queries and capable of scaling a plurality of location servers according to system performance and logistical requirements.

Claims

1. A system having a plurality of location servers for managing location information and providing location information to location queries, the system comprising:

a first location server containing a first set of location information corresponding to at least one entity, the location information comprising an identifier and at least one location string associated with the identifier, wherein the identifier identifies an entity and the location string specifies a location of data pertaining to the entity

a second location server comprising a second set of location information, wherein at least a portion of the second set of location information differs from the first set of location information; and

programming logic stored on each of the location servers responsive to a location query identifying a desired entity to return a location message, the location message comprising at least one location of data pertaining to the desired entity, if the location server receiving the location query contains location information for the desired entity.

2. The system of claim 1, wherein the at least one location comprises a plurality of geographic locations, each of the geographic locations representing a position of the entity at a different time.

3. The system of claim 1, wherein the programming logic further comprises logic responsive to the location query to return one of a location message or a redirect message, wherein the location server receiving the query returns the location message if the queried location server contains location information for the desired entity, and wherein the queried location server returns a redirect message if the queried location server lacks location information for the desired entity, the redirect message comprising information for finding a location server known to have location information relevant to the location query.

4. The system of claim 3, wherein the information for finding the location server known to have location information relevant to the location query comprises a list of location servers and a corresponding list of each of the entities having location information on the location servers.

5. The system of claim 1, wherein each of the location servers stores at least a portion of the location information on a persistent storage device.

6. The system of claim 1, wherein the location information in the location server is maintained in an indexed location store indexed by a hash table.

7. The system of claim 6, wherein the location query identifying the desired entity comprises a unique identifier for the desired entity, and wherein the programming logic stored on the location server further comprises programming logic for applying an index function to the unique identifier to retrieve at least a portion of the location information associated with the unique identifier in the indexed location store.

8. The system of claim 7, wherein the location query is received at a location server in a first node and wherein the redirect message comprises a list of at least one other location server in a node other than the first node that may have location information relevant to the location query.

9. The system of claim 1, wherein the plurality of location servers are arranged in a network topology having a plurality of nodes organized in a logical hierarchy, wherein each node comprises at least one location server and wherein each node is connected to at least one other node in the logical hierarchy.

10. A system having a plurality of location servers for managing location information and providing location information to location queries, the system comprising:

a plurality of location servers containing location information corresponding to a plurality of entities, the location information formatted according to a transfer protocol configured for manipulating location information, and comprising at least one application server address, wherein the plurality of location servers are arranged in a cluster topology such that each location server contains a unique set of location information of an aggregate set of the location information; and

programming logic stored on each of the plurality of location servers responsive to a location query for a desired identifier to return one of a location message, wherein a queried location server returns a location message if the queried location server contains location information for the desired identifier, and a redirect message if the queried location server does not contain location information relevant to the desired identifier, wherein the redirect message comprises information for finding a location server having location information related to the desired identifier.

11. The system of claim 10, wherein the location information comprises geographic location information.

12. The system of claim 10, wherein the location information comprises network address information.

13. The system of claim 12, wherein the network address information comprises a network address of a data repository containing data pertaining to the desired identifier.

14. A method of handling location queries in a network, the network comprising a plurality of location servers, each location server containing a unique set of location information of an aggregate set of location information correlating each of a plurality of identifiers with at least one location, the method comprising:

receiving a location query from a client at one of the plurality of location servers, the location query requesting an entity'"'"'s location;

sending a location response message to the client if the queried location server contains location information relevant to an entity identified in the query, the location response message comprising location information identifying at least one application server containing information relevant to the entity identified in the query; and

sending a redirect message to the client if the queried location server does not contain data location information relevant to the entity identified in the query, the redirect message comprising information for finding a location server storing the entity identified in the query.

15. The method of claim 14, further comprising applying information in the location query from the client to an indexing function to determine if the queried location server contains location information relevant to the entity identified in the query.

16. The method of claim 15, wherein each of the plurality of location servers comprises an indexed table of identifiers and associated locations, and wherein applying information in the location query comprises applying an identifier in the location query to a hash function.

17. A method of scaling at least one of capacity and transaction rate capability in a location server in a system having a plurality of location servers for storing and retrieving location information, wherein each of the plurality of location servers stores unique set of location information of an aggregate set of location information, the method comprising:

providing a transfer protocol configured to transport identifier and location information, the location information specifying the location of information related to the identifier;

storing location information formatted according to the transfer protocol at a first location server;

receiving an identifier and a location relevant to the identifier at the first location server;

storing the received location in a location store at the first data location server, the location store comprising a plurality of identifiers, each identifier associated with at least one location, wherein the received location is associated with the received identifier in the location store; and

transferring a portion of the identifiers and associated locations to a second data location server when a performance criterion of the first location server reaches a predetermined performance limit.

18. The method of claim 17, wherein receiving an identifier and a location comprises receiving the identifier and the location at the first location server from an application server, wherein the location comprises an address for the application server.

19. The method of claim 17, wherein receiving an identifier and a location comprises receiving the identifier and the location at the first location server from a physical object, wherein the identifier identifies the physical object and wherein the location comprises a geographic location for the physical object.

20. The method of claim 19, wherein the physical object comprises a vehicle.

21. The method of claim 19, wherein the physical object comprises a portable telecommunications device.

22. The method of claim 17, wherein transferring a portion of the identifier and location associations comprises:

identifying a portion of identifier and location associations on the first location server to be transferred to the second location server and identifying a data set state of the identified portion at an initial time;

copying a data set for the identified portion corresponding to the identified data set state from the first location server to the second location server and maintaining a second data set containing changes to the identified portion since the initial time;

identifying a data set state for the second data set;

ceasing operation of the first location server with respect to the identified portion and copying the second data set to the second location server, wherein the second data set corresponds to the identified data set state for the second data set; and

initiating operation of the second location server for the identified portion of identifiers and location associations.

23. The method of claim 17, wherein the performance criterion comprises an amount of available persistent storage space in the first location server.

24. The method of claim 17, wherein the performance criterion comprises a transaction rate limit.

25. The method of claim 17, wherein the transaction rate limit comprises a processor speed limit.

26. The method of claim 17, wherein the transaction rate limit comprises a network connection bandwidth limit.

27. The method of claim 17, further comprising transmitting a location server map from the first location server, the location server map comprising information identifying the second location server and a list of identifiers associated with the second location server.

28. The method of claim 27, wherein the first and second location servers are part of a location server cluster comprising a plurality of location servers, and wherein transmitting the location server map comprises transmitting the location server map to each of the plurality of data location servers asynchronously.

29. The method of claim 27, wherein transmitting a location server map comprises transmitting the location server map to a client in response to query received at the first location server from the client regarding an identifier that is not resident on the first location server.

30. The method of claim 17, wherein transferring a portion of the identifiers and associated locations to a second location server when a performance criterion of the first data location server reaches a predetermined performance limit further comprises monitoring the performance criterion and automatically transferring the portion of identifiers and associated locations when the first location server reaches the predetermined limit.

31. A system for managing location information and providing location information to location queries, the system comprising:

a location server operating in accordance with a transfer protocol, the transfer protocol comprising instructions for manipulating an identifier and at least one location associated with the identifier, wherein the identifier uniquely specifies an entity and wherein each location specifies a location of data in a network pertaining to the entity, the location server containing location information corresponding to at least one entity and formatted according to the transfer protocol, and wherein the location of data for the location comprises an application server in communication with the network; and

programming logic stored on the location server responsive to a location query identifying a desired entity to return a location message, the location message comprising locations associated with the desired entity, wherein the location server returns the location message if the location server contains location information for the desired entity.