SYSTEM AND METHOD FOR MANAGING CREATED LOCATION CONTEXTS IN A LOCATION SERVER

• US 20100248740A1
• Filed: 03/26/2009
• Published: 09/30/2010
• Est. Priority Date: 03/26/2009
• Status: Active Grant

• Current Assignee: CommScope Technologies, LLC (CommScope Holding Company, Inc.)
• Original Assignee: Andrew LLC (CommScope Holding Company, Inc.)
• Inventors: Justusson, Gary Neil, Winterbottom, Anthony James
• Granted Patent: US 8,391,884 B2
• Time in Patent Office: Days
• US Class Current: 455/456.100
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 4/40 for vehicles, e.g. vehicle-to-pedestrians [V2P]

Abstract

A system and method for handling a location request for a target device using a location uniform resource identifier (“URI”). A location request may be received for a target device from a requesting entity, the target device having a location context information represented by a location URI and including starting information, initial validating information and policy information. The form of the location URI may be verified by a location information server (“LIS”), the form including at least an encrypted context string. This string may be extracted and decrypted by the LIS and it may be determined whether the request can continue as a function of the policy information. If the request can continue, then an estimated location of the target device may be determined as a function of the starting information. Additional validating information may be collected and correlated the initial validating information. If these validating information correlate, then the estimated location of the target device may be provided to the requesting entity.

Claims

1. A method for handling a location request for a target device using a location uniform resource identifier (“

URI”

), comprising the steps of;

(a) receiving a location request for a target device from a requesting entity, the target device having a location context information represented by a location URI and including starting information, initial validating information and policy information;

(b) verifying the form of the location URI by a location information server (“

LIS”

), the form including at least an encrypted context string;

(c) extracting and decrypting the encrypted context string by the LIS;

(d) determining if the location request can continue as a function of the policy information;

(e) determining an estimated location of the target device as a function of the starting information;

(f) collecting additional validating information;

(g) correlating the additional validating information with the initial validating information; and

(h) providing the estimated location of the target device to the requesting entity.

2. The method of claim 1 wherein the form of the location URI further includes a host address of the LIS and addressing information based on protocol, routing, and network details.

3. The method of claim 1 wherein the LIS comprises one or more processing units at one or more processing sites.

4. The method of claim 3 wherein the step of extracting and decrypting further comprises using shared knowledge between the one or more processing units at one or more processing sites.

5. The method of claim 1 further comprising the step of returning an error to the requesting entity if the additional validating information fails to correlate with the initial validating information.

6. The method of claim 1 wherein the requesting entity is the target device or a location client.

7. The method of claim 1 wherein the location URI includes a uniform resource name (“

URN”

), a uniform resource location (“

URL”

), and combinations thereof.

8. The method of claim 1 wherein the starting information includes information for initiating a location determination for the target device.

9. The method of claim 1 wherein the initial and additional validating information includes information correlating the starting information with the target device.

10. The method of claim 1 wherein the policy information includes information indicating whether a location of the target device may be provided to the requesting entity.

11. The method of claim 1 wherein the location request is for a geodetic location or a civic location of the target device.

12. The method of claim 1 wherein the target device is selected from the group consisting of:

cellular device, text messaging device, computer, portable computer, vehicle locating device, vehicle security device, communication device, and wireless transceiver.

13. A location information server (“

LIS”

) comprising;

(a) circuitry for receiving a location request for a target device, the target device having a location context information represented by a location URI and including starting information, initial validating information and policy information;

(b) circuitry for verifying the form of the location URI, the form including at least an encrypted context string;

(c) circuitry for extracting and decrypting the encrypted context string;

(d) circuitry for determining if the location request can continue as a function of the policy information;

(e) circuitry for determining an estimated location of the target device as a function of the starting information;

(f) circuitry for collecting additional validating information;

(g) circuitry for correlating the additional validating information with the initial validating information; and

(h) circuitry for providing the estimated location of the target device to the requesting entity.

14. The LIS of claim 13 wherein the form of the location URI further includes a host address of the LIS and addressing information based on protocol, routing, and network details.

15. The LIS of claim 13 wherein the LIS comprises one or more processing units at one or more processing sites.

16. The LIS of claim 15 wherein the LIS is adaptable to use shared knowledge between the one or more processing units at one or more processing sites.

17. The LIS of claim 13 wherein the requesting entity is the target device or a location client.

18. The LIS of claim 13 wherein the location URI includes a uniform resource name (“

URN”

), a uniform resource location (“

URL”

), and combinations thereof.

19. The LIS of claim 13 wherein the starting information includes information for initiating a location determination for the target device.

20. The LIS of claim 13 wherein the initial and additional validating information includes information correlating the starting information with the target device.

21. The LIS of claim 13 wherein the policy information includes information indicating whether a location of the target device may be provided to the requesting entity.

22. The LIS of claim 13 wherein the location request is for a geodetic location or a civic location of the target device.

23. The LIS of claim 13 wherein the target device is selected from the group consisting of:

cellular device, text messaging device, computer, portable computer, vehicle locating device, vehicle security device, communication device, and wireless transceiver.

24. In a location information server (“

LIS”

) that has received a location request for a target device, the target device having location context information represented by a location uniform resource identifier (“

URI”

), a method for handling the location request for the target device using a location URI, comprising the steps of;

(a) verifying the form of the location URI by the LIS, wherein the location context information further includes starting information, initial validating information and policy information;

(b) if the location request can continue as determined by the policy information, then determining an estimated location of the target device as a function of the starting information;

(c) collecting additional validating information and correlating the additional validating information with the initial validating information; and

(d) providing the estimated location of the target device to a requesting entity.